How to completely fix a Bricked Touch Pad.

[Ventus221]

This method will completely fix your Touch Pad if you are suffering from any form of boot loops or anything. It is important that you have all the required prerecuisites of having Novacom and etc on your computer and this has proven to work on both my Windows 7 and Windows 8 machines. This will NOT fix any hardware issues. So if this method does not work that more than likely it is a hardware issue or you can not boot into recovery, then it's a corrupted bootloader and it will be beyond this threads help to fix unless you go to to Toptoungebarry's suggestion below.

This will only work if you are able to put your Touch Pad into recovery mode. If you can not then there is a post two below this one with the right directions.

This method will also restore any missing data partitions as a result of a botched Ubuntu or Android or other Linux distro install

Important: this method will also create a CM7 partition that is easy to remove, just run acme uninstaller as if you were uninstalling Android even if it is not there. That way you will have a perfect WebOS tablet.

Note: This Method will NOT work on a Touch Pad Go I promise, also I'm not aware if it works on a Touch Pad 4G so do not try it on a Touch Pad 4G.

Also the most important thing to note is that you must follow every line in this method precisely or else it will NOT fix your Touch Pad. Its important to note that you can copy and paste the lines to save alot of time. but read every line carefully as some sections change in the later parts of this method.

Also in order to update from 3.0.4 to 3.0.5 you must update manually not via WebOS doctor.

I got this method from this forum on the XDA site so do NOT thank me for this thank them.

Here is the original thread: [SOLVED] BRICKED and WebOS Doctor Won't Help... - xda-developers

And here are the directions;

HOWTO for anyone interested: Updated on 2011 12-13
Update: resolved 'major:minor pair unavailable'
Update: Works for 32GB HP Touchpad and 16GB HP Touchpad

Credits to:
webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
for the 32GB HP Touchpad filesystem creation example

[FIRST]
1) THIS PROCESS WILL COMPLETELY WIPE YOUR TOUCHPAD! WEBOS, CM7,
& ANYTHING ELSE YOU'VE INSTALLED!!
2) This process also assumes you can get functional terminal to your HP
Touchpad already via novaterm, novacom open TTY://, or with putty.
3) This process also assumes you know how to install CM7 already.

YOU WILL ALSO NEED:
webOS Doctor version 3.0.0
webOS Doctor version 3.0.4
from All HP WebOS Doctor Versions:
webos-internals.org/wiki/Webos_Doctor_Versions

[NOW START]
1) Put your HP Touchpad in webOS Recovery Mode:
a. Power off the HP Touchpad or reset it with [Power Button] + [Home]
b. Hold [Up Volume] + [Power Button] until you see a usb symbol on screen.
2) Start up taskmanager in Windows:
a. [CTRL]+[ALT]+[DEL] and select task manager
3) Run webOS Doctor and let it run to 8% then use taskmanager to end task
on webOS doctor.
4) Open up windows command prompt and type in: novacom open TTY://
5) Run the following commands [CASE SENSITIVE] type it exactly as shown
and make sure to get the numbers after --minor correct:

[Note: Don't bother customizing webOS partitions because in this process
webOS doctor will re-size them back to the following anyways.]

a. lvm.static vgscan --ignorelockingfailure
b. lvm.static vgchange -ay --ignorelockingfailure
c. lvm.static vgremove store
d. lvm.static vgscan --ignorelockingfailure
e. lvm.static vgchange -ay --ignorelockingfailure
f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
g. lvm.static vgscan --ignorelockingfailure
h. lvm.static vgchange -ay --ignorelockingfailure
i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store

NOTE: THE FOLLOWING --minor JUMPS to 7 from 5 above
o. lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store

NOTE: THE FOLLOWING MAKES CM7 PARTITIONS, I specified a 5GB cm-data
partition, you can do more or less. 1 Physical Extent (PE) is 8MB.
The number after -l is the number of Physical Extents for
the partition.
p. lvm.static lvcreate -l 96 -M y --major 254 --minor 8 -n cm-system store
q. lvm.static lvcreate -l 32 -M y --major 254 --minor 9 -n cm-cache store
r. lvm.static lvcreate -l 640 -M y --major 254 --minor 10 -n cm-data store

NOTE: The following creates the media partition used as SDCARD and sets
it to --minor 6, make sure you set it to --minor 6, the SDCARD is
specified as dm-6 in CM7. This will save you from having to edit
/etc/vold.fstab in CM7.
s. lvm.static vgscan --ignorelockingfailure
t. lvm.static vgchange -ay --ignorelockingfailure
u. lvm.static vgdisplay
i. this command displays information on the Volume Group: store
at the bottom you should see:
Free PE/Size X / XX
where X is the number of Physical Extents free and XX is the size free.
ii. write down the number of X (Physical Extents free) to use in the
next command
v. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
w. lvm.static vgscan --ignorelockingfailure
x. lvm.static vgchange -ay --ignorelockingfailure
y. mkdosfs -f 1 -s 64 -F 32 /dev/store/media
z. mkfs.ext4 /dev/store/cm-system or mkfs.ext3 /dev/store/cm-system
za. mkfs.ext4 /dev/store/cm-cache or mkfs.ext3 /dev/store/cm-cache
zb. mkfs.ext4 /dev/store/cm-data or mkfs.ext3 /dev/store/cm-data
zc. run webOS Doctor 3.0.0 and let it complete and let it reboot to
the language selection screen
zd. reset the HP Touchpad with [POWER BUTTON] + [HOME] and put it into
webOS Doctor recovery mode with [POWER BUTTON] + [VOLUME UP].
ze. run webOS Doctor 3.0.4 and let it complete and let it reboot and
complete webOS install and go into webOS.

If you did everything right, you now have an HP Touchpad tablet with a fresh
webOS 3.0.4 and pre-created CM7 partitions. Now, just follow the standard
CM7 install procedure after you boot into webOS 3.0.4 to install CM7.
ACMEInstaller will use the cm-system, cm-cache, and cm-data file system
you've already created. Enjoy.

webOS Doctor 3.0.0 is required. If you do not run this first, other webOS
Doctor version will fail. webOS Doctor 3.0.0 resizes and formats partitions
as needed, the other versions seem to no longer have this and fail when
the webOS partitions aren't perfect in format/size.

There you go. Enjoy WebOS again

[Ventus221]

Bump

[TopTongueBarry]

Originally Posted by Ventus221

This method will completely fix your Touch Pad if you are suffering from any form of boot loops or anything.

[NOW START]
1) Put your HP Touchpad in webOS Recovery Mode:

.... anything. ????????????
Hmmmm, Not so fast Ventus221. There are bricked Touchpads, Pre 3's and Touchpad GO's that are unable to get into recovery mode because the bootloader is damaged. On webOS devices, the bootloader is required not only to boot these device's into the OS, a functional bootloader is required to load novacom, which is necessary to boot into recovery mode. You cannot even memboot without functional novacom drivers.

webOS devices with a corrupt bootloader will not complete step 1 of your guide. There is hope for these devices though. It is not the method you describe.

A solution created by jcsullins, (do you know of him by chance???) and darkspr1te for devices with qualcomm chips that have damaged bootloaders is detailed on rootzwiki and on xda. I have a Touchpad GO fully recovered using this method. It works (or has the potential to work) on not only 16GB and 32GB Touchpads, but also on any webOS device manufactured with a Qualcomm chipset (Pre 3, Touchpad wifi, Touchpad 4G, and Touchpad GO).

TPDebrick v0.1 - HP Touchpad - RootzWiki

If you have a dead Touchpad Wi Fi device that can get into recovery mode, but will not successfully complete webOS doctor, or boot loops after running the doctor, then yes the method you describe will work. If the device doesn't meet that specific criteria, then no, it will not work.

Always do your research before posting a solution!
TTB

[Ventus221]

Ahh that's right....I should state that this will fix your touch pad if your able to boot into recovery mode ill edit that immediately. Thank you for pointing it out

[makemyday21]

Originally Posted by TopTongueBarry

.... anything. ????????????
Hmmmm, Not so fast Ventus221. There are bricked Touchpads, Pre 3's and Touchpad GO's that are unable to get into recovery mode because the bootloader is damaged. On webOS devices, the bootloader is required not only to boot these device's into the OS, a functional bootloader is required to load novacom, which is necessary to boot into recovery mode. You cannot even memboot without functional novacom drivers.

webOS devices with a corrupt bootloader will not complete step 1 of your guide. There is hope for these devices though. It is not the method you describe.

A solution created by jcsullins, (do you know of him by chance???) and darkspr1te for devices with qualcomm chips that have damaged bootloaders is detailed on rootzwiki and on xda. I have a Touchpad GO fully recovered using this method. It works (or has the potential to work) on not only 16GB and 32GB Touchpads, but also on any webOS device manufactured with a Qualcomm chipset (Pre 3, Touchpad wifi, Touchpad 4G, and Touchpad GO).

TPDebrick v0.1 - HP Touchpad - RootzWiki

If you have a dead Touchpad Wi Fi device that can get into recovery mode, but will not successfully complete webOS doctor, or boot loops after running the doctor, then yes the method you describe will work. If the device doesn't meet that specific criteria, then no, it will not work.

Always do your research before posting a solution!
TTB

Great info gentlemen! Where does the question mark of death issue fall? Should I be able to boot into recovery mode with the ? on my touchpad?

[GMMan]

The question mark problem is due to the system not recognizing the battery. Somehow the battery failed to communicate or validate, so the system refuses to boot with it.

Musing: there's an environment variable or something in the bootloader stage named "checkbatt". What if it's changed or removed?

[con500]

Originally Posted by makemyday21

Great info gentlemen! Where does the question mark of death issue fall? Should I be able to boot into recovery mode with the ? on my touchpad?

The question mark issue has just been solved for one user over at TPDebrick v0.1 - HP Touchpad - RootzWiki

Apparently it was rather straight forward following @jcsullins instruction. The guy basically was able to flash the A6 chip from within Linux. I hope there will be a guide for other users with this issue

However it was noted that flashing the A6 could "potentially" result in a permanent Brick.