HP touchpad in QHSUSB_DLOAD mode per device manager and won't turn on

[P-eezy]

I have an HP touchpad that won't turn on and will only show up as QHSUSB_DLOAD when i connect it to my computer. Can someone point me to a thread that details how to fix it or a repair place i can send it to since it's out of the 1 year HP warranty, thanks for your time.

[con500]

Sorry don't know if this is the same issue but there is some active discussion on something similar over at

Touchpad Backup with QPST -- need this for unbricking - HP Touchpad - RootzWiki

Again sorry if its not what your after but may be worth having a peek.

[GMMan]

Minor hint: The majority of the bootloader files are included in webOS Doctor.

[cyberprashant]

we're starting to see a lot of dead TP's. Anyone here offering a repair service of any kind? (Any electronics repair services out there?).

[TopTongueBarry]

Significant advances have been made in the last week. Access to a TP GO 's eMMC partitions and its filesystem data has been acheived by installing a temporary bootloader using QPST. Previously, the device appeared to be dead, couldn't be booted into recovery mode, wouldn't load and connect using novacom, novaterm ,WOSQI or or anything. It would only connect in qualcomm download mode (QHUSB_DLOAD)

There's more work to be done. A basic (minimum) understanding of linux storage device configuration, linux commands, webOS and windows is necessary. One incorrect keystroke or missed step could render the device inaccessable and / or truly bricked, useful only as the paperweight you previously thought it was.

- Here is a link to a webOSnation thread located in the Pre 3 forum here where members have also been collaberating and working on a fix for this.

Dead Pre 3 (QHUSB-DLOAD mode)

- The post and thread the next link points to is located on xda and there's documents and files you can use to install a temporary bootloader onto a MSM8660 device in order to gain access to its sdcard (filesystems) for partition recreation and restoral of backups and/or factory provided eMMC images. I advise reading through the thread. There's some links scattered throughout it pointing to a few other threads on xda where people have been independently working on fixing this problem too. The MSM8660 is a widely used chipset fouind in many devices.

[JTAG,BRICK]SHV-E160L Korean model - Page 9 - xda-developers

For our dead webOS devices, the process after we install a temporary bootloader is to boot the device from it, then recreate the rest of the partition table / partition information.

After that we'd restore data to the the bootie partition and to the two other partitions bootie uses to chain boot the device.

In theory, once those three partitions are restored and readable , it should be possible to boot the device into recovery mode for doctoring.

TTB

[TopTongueBarry]

I need someone with a 64 GB Touchpad Topaz to run the following 3 commands from a WOSQI command prompt and post the output here in this thread please! Your device will not be harmed, these commands only pull information about the filesystems and output to the terminal.

cat /proc/partitions
blockdev --report /dev/mmcblk0
blockdev --report /dev/mmcblk0p14

mmcblk0 and mmcblk0p14 sizes are consistent between the topaz and the opal.
I need data from a 64GB device before I can proceed.

Thanks in advance!

Here's what I've pulled from a 32GB Touchpad Opal -

cat /proc/partitions
major minor #blocks name

179 0 31160320 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 500 mmcblk0p5
179 6 750 mmcblk0p6
179 7 2500 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 30504960 mmcblk0p14

blockdev --report /dev/mmcblk0
RO RA SSZ BSZ StartSec Size Device
rw 256 512 4096 0 31908167680 /dev/mmcblk0
rw 256 512 4096 1 104857600 /dev/mmcblk0p1
rw 256 512 4096 204801 512000 /dev/mmcblk0p2
rw 256 512 4096 205801 1536000 /dev/mmcblk0p3
rw 256 512 1024 208801 1024 /dev/mmcblk0p4
rw 256 512 4096 262144 512000 /dev/mmcblk0p5
rw 256 512 2048 393216 768000 /dev/mmcblk0p6
rw 256 512 4096 524288 2560000 /dev/mmcblk0p7
rw 256 512 4096 655360 10485760 /dev/mmcblk0p8
rw 256 512 4096 786432 1536000 /dev/mmcblk0p9
rw 256 512 4096 917504 3145728 /dev/mmcblk0p10
rw 256 512 4096 1048576 3145728 /dev/mmcblk0p11
rw 256 512 4096 1054720 4194304 /dev/mmcblk0p12
rw 256 512 4096 1062912 33554432 /dev/mmcblk0p13
rw 256 512 4096 1179648 31237079040 /dev/mmcblk0p14

[P-eezy]

Has there been any advancements or another thread to resolve this issue?

[GMMan]

There was a link to XDA about someone who managed to restore a TouchPad using Qualcomm's tools.

[TopTongueBarry]

Originally Posted by GMMan

There was a link to XDA about someone who managed to restore a TouchPad using Qualcomm's tools.

TPDebrick v0.1 - HP Touchpad - RootzWiki - Page 20

TTB

[wdiggums]

Originally Posted by P-eezy

I have an HP touchpad that won't turn on and will only show up as QHSUSB_DLOAD when i connect it to my computer. Can someone point me to a thread that details how to fix it or a repair place i can send it to since it's out of the 1 year HP warranty, thanks for your time.

try plugging the barrel charger into the wall socket by itself, then attach the mini usb to your touchpad and plug the other end into a usb port on your computer. then remove the usb plug from the computer and plug it into the barrel charger you already have plugged into the wall, this owrked for me when the battery issue hit ;-) best wishes

[GMMan]

Originally Posted by wdiggums

try plugging the barrel charger into the wall socket by itself, then attach the mini usb to your touchpad and plug the other end into a usb port on your computer. then remove the usb plug from the computer and plug it into the barrel charger you already have plugged into the wall, this owrked for me when the battery issue hit ;-) best wishes

I'm sure it's a more complicated problem than that.

[wdiggums]

Originally Posted by GMMan

I'm sure it's a more complicated problem than that.

most likely haha
the fix i described is for the touchstone charger battery problem where the pad has to remain uncharged for weeks before it will allow to be charged again , or whatever solution others have found. the answer that worked for me to wake it up so to speak was the comp usb to barrel wall charger thing, it worked right away. if not placed exactly right on the touchstone the touchpad will appear to basically die. wont turn on, wont charge etc etc etc :-)

[GMMan]

Originally Posted by wdiggums

most likely haha
the fix i described is for the touchstone charger battery problem where the pad has to remain uncharged for weeks before it will allow to be charged again , or whatever solution others have found. the answer that worked for me to wake it up so to speak was the comp usb to barrel wall charger thing, it worked right away. if not placed exactly right on the touchstone the touchpad will appear to basically die. wont turn on, wont charge etc etc etc :-)

But we're talking about a completely borked device that can't find its firmware. Power trouble is unlikely unless the charging circuit has some dependence on the device's ability to initialize up until bootie.

[P-eezy]

Originally Posted by TopTongueBarry

TPDebrick v0.1 - HP Touchpad - RootzWiki - Page 20

TTB

TTB, did you see my private message?

[P-eezy]

Does anyone recover HP touchpads in qhsusb_dload mode or know where i can send mine to be recovered? Thanks.

[johnjcbs]

Originally Posted by P-eezy

Does anyone recover HP touchpads in qhsusb_dload mode or know where i can send mine to be recovered? Thanks.

Fixed mine here > TPDebrick v0.1 - HP Touchpad - RootzWiki

[P-eezy]

I don't have access to a linux machine. I was hoping that someone could recover mine or tell me where i can send mine to be recovered.

[onthemark1957]

Originally Posted by P-eezy

I don't have access to a linux machine. I was hoping that someone could recover mine or tell me where i can send mine to be recovered.

I am having the same issue P-eezy and I don't have access to a linux machine either. Can you please let me know if you get anywhere and I will do the same for you?

Thanks,
Mark

[P-eezy]

Originally Posted by onthemark1957

I am having the same issue P-eezy and I don't have access to a linux machine either. Can you please let me know if you get anywhere and I will do the same for you?

Thanks,
Mark

Sounds like a plan onthemark1957. I was hoping somebody was in the same boat as me.

[Herrie]

You can always run Linux in VirtualBox on a Windows PC or use a LiveCD?

-- Sent from my TouchPad using Communities