|12/11/2012, 07:18 AM||#1 (permalink)|
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
for the 32GB HP Touchpad filesystem creation example
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:
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
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
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
Verizon Pre 3. ATT HP Touchpad. Touchstone 2.
Last edited by Ventus221; 12/17/2012 at 04:56 AM.
|12/15/2012, 12:57 PM||#3 (permalink)|
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!
I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s positions, strategies or opinions.
Last edited by TopTongueBarry; 12/15/2012 at 01:07 PM.
|12/17/2012, 04:44 AM||#4 (permalink)|
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
Verizon Pre 3. ATT HP Touchpad. Touchstone 2.
|12/29/2012, 10:58 AM||#5 (permalink)|
|12/29/2012, 03:53 PM||#6 (permalink)|
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?
Contact: @GMMan_BZFlag (me on Twitter)
webOS Releases: Change your App Catalog country: TouchPad/PC | TouchPad/webOS Resources | Search suggestion patch for browser | Cycling Email Notifications | Don't Doctor! Make a good support request. | How to post logs | webOS Charge Monitor
|12/29/2012, 05:09 PM||#7 (permalink)|
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.
|09/15/2013, 02:01 PM||#8 (permalink)|
Thank You very much Ventus221. Your suggestions are awesome. It saved my Touch Pad.
Only one suggestion that I want you to add please.
Please provide this link Page 1 of comments on Fix A Bricked HP TouchPad - Fix All Boot Loops & Software Issues - YouTube
|09/18/2014, 09:06 AM||#10 (permalink)|
|09/19/2014, 05:05 AM||#11 (permalink)|
You can also use Touchpad Toolbox by jcsullins
[TOOLS] Touchpad Toolbox | HP Touchpad | XDA Forums
1. Complete Data Reset
2. Create WebOS Volume
3. Run WebOS Doctor
Also allows you to install android and resize volumes and reflash A6 battery firmware
|07/30/2015, 04:13 PM||#13 (permalink)|
Just made an account to post this if anyone else ever happens to come across this thread.
At first pressing any button combination did nothing. I got the already broken TouchPad from a friend (where he got it from idk) and had no idea what had been done to mess it up, whether it was hardware/software or whatever.
First I tried to turn it on, nothing. So I plugged it in and forgot about it for around 2 days thinking the battery might be dead. I had the stock HP cable but used an iPad brick to plug it in the wall.
After 2 days I held power+home and got the little home button led to flash left and right, but nothing else. Somehow through a series of button holds/presses (power+home, power+down/up+home, etc.) I got the battery with question mark symbol to come up.
Tried holding power+home then power+vol.up again but it wouldn’t go into USB symbol mode
Searched and found jcsullins’ TPDebrick v004 (TPDebrick v004 - HP Touchpad - RootzWiki)
I have a Mac but was able to install Linux using Parallels
Got the “all done” from the debrick program, plugged the TouchPad back into the wall for about a day.
Held power+home again, now it didn’t show the battery question mark, but would freeze at the HP logo. Still no luck getting into usb mode and all that would work is power+home to turn it off and on, but nothing I tried would get it through the logo.
Thought maybe I used the wrong storage size in the debrick program (since I had no idea if it was a 16, 32, or 64gb) so I did the 32 instead of 16. Still no luck. Tried 16 again, froze on the logo again. I held home+power to turn it off, then plugged the TouchPad into the wall and it started bootlooping (not frozen) at the HP logo. Okay, that’s at least a difference, but still no usb symbol..
The power+vol.up combo wouldn’t do anything at all, power+home would just turn it off where nothing would work until I did the same combo again and it went back to looping. During one loop I just held down the vol.down button, the thing went off, then I did power+home got it back to looping, then held just the vol.up during one of the loop resets and VOILA! White USB symbol appears and I’m now in recovery mode.
Now I could finally follow this thread (How to completely fix a Bricked Touch Pad.).
But had to now install Windows on Parallels (probably could have used Linux but it scares me) to follow the procedure.
But of course Windows couldn’t recognize the TouchPad since I didn’t have novaterm and novacom and the hp drivers etc. I had no idea what any of these programs were so it took a while but I found this thread ([Guide] Factory condition restoration / Downâ€¦ | HP TouchPad | XDA Forums), got novacom/novaterm, the recovery image, and webOS Doctor 3.00 and 3.04.
Followed the instructions there to install the programs, but whenever I tried typing in novacom in terminal I would get “novacom is not recognized as an internal or external command..” Ugh.
This thread (Installation Help! - HP Touchpad - RootzWiki) said I needed to put acmeinstaller in the same folder as the novacom.exe file in the Palm, Inc folder. So many threads I went to would never have the files I needed or lead to broken websites because of HP discontinuing support, but I was able to get acmeinstaller from here (How to Install CyanogenMod on the Hewlett Packard Touchpad ("tenderloin") - CyanogenMod) and put it in the Palm, Inc folder. Also found all the webOS doctors here (https://web.archive.org/web/20140214...ions#Wifi_Only).
Terminal still wouldn’t recognize novacom...
So I uninstalled it completely, rebooted, then found this thread (WebOS Quick Install v4.6.0) and used the WebOS Quick Install tool to get novacom installed and that finally worked. I knew it worked because I checked it with the method here (REVTV - Problems with Novacom).
That whole time the TouchPad was still on the recovery mode USB symbol and I was just praying it wouldn’t run out of battery or something while I had to do all that extra searching. So I finally met all the requirements, and was able to successfully complete the process again at this thread (How to completely fix a Bricked Touch Pad.).
Followed everything to the dot, copying and pasting lines so I wouldn’t screw up, then the TouchPad rebooted (took a looong time to get passed the pulsing logo though) and sent me to the language selection screen holy crap something actually worked.
Went through the beginning of the setup stuff, but OF COURSE I couldn’t finish setup because HP servers were down, so I couldn’t login or even make a WebOS account. FML.
So I searched and searched and found this thread (Activation Bypass for TouchPad) that told me how to bypass the activation.
The link in this thread (Bypass-Activation download??? link broken) let me download the tool since the one in the above website was down.
Once I did that the TouchPad rebooted, froze on the HP logo for about 10 minutes, then stayed on the pulsing logo for around 15-20 minutes, then booted to a frozen, inoperable webOS…
Found this thread about jcsullins’ TouchPad toolbox (How to use TouchPad Toolbox to install Android, erase webOS on the HP TouchPad - Liliputing)
So I held power+home, as soon as it started to reboot held power+vol.up and got into recovery mode. Downloaded the toolbox, followed the instructions in the above thread, and was FINALLY able to get it 100% working and on android!
The whole process took me about a week and a day of trial and error since I had no idea what I was doing on 90% of the steps. Everywhere I went people seemed to be saying that the TouchPad was unbrickable and I found it hard to believe, but after going through everything I did to finally get it working it could be true. I feel like I hit every roadblock possible, but at least it paid off in the end. If it wasn’t for all the random advice and success stories I found on various forums I would’ve never been able to do it, so here’s mine hoping it’ll help you! Good luck!!