Related
First I shall describe the problem i had:
Here is what I did
1. Installed CM7 on my touchpad successfully.
2. Installed CM7 2.1 perfect.
3. Found that there is only 1.3GB left for apps and rest.
4. Connected to the computer and it asked me to format disk to open, so formatted.
5. Copied files and found it was not accessible via CM7 (this is when I should have asked for help)
6. Booted into WebOS and erased everything there.
7. Still not accessible and the size had not improved either.
8. Bad part starts; tried to redo the entire thing, and started up webos doctor, which got stuck at 12%
9. Ran via cmd and it displayed "Trenchcoat: Cluster xxxxx out of range" and a blinking cursor, which did not allow me do anything
10. then started novacom and tried ACMEUninstaller which told me "Cannot Start LVM and Reboot!"
Solution (I did not develop any of the steps, but only managed to find the right combination of troubleshooting):
If the webOS Doctor continually disconnects at 12%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).
If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.
First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):
1.Make sure your TP is in recovery and your computer recognizes as Novacom (bootie) device (found uninstalling webos and all older drivers helps too)
2.If you have uninstalled all drivers, install novaterm, and novacom drivers
Installing Novacom
Change the file extension from .jar to .zip and then extract the archive.
Browse to the folder webosdoctorp100ewwsprint/resources/. Click in the address bar and copy the full path of this folder to the clipboard.
Click on //Run...// in the Start Menu, and in the box enter: msiexec.exe /a "{copied_path}\NovacomInstaller_x86.msi" /qb TARGETDIR="{copied_path}\NovacomInstaller_x86" (for 32-bit Windows) or msiexec.exe /a " {copied_path}\NovacomInstaller_x64.msi" /qb TARGETDIR="{copied_path}\NovacomInstaller_x64" (for 64-bit Windows). Instead of typing {copied_path}, each time you see it, paste in the path you copied to the clipboard instead.
Now you should see a new folder called NovacomInstaller_x86 (or NovacomInstaller_x64) inside the resources folder. Open this folder, and then inside that, open the PFiles folder. Copy the Palm, Inc folder to C:\Program Files\.
You should now have a C:\Program Files\Palm, Inc folder. Browse to this folder, then inside that, open the novacom folder. Run the dpinst.exe program that you find there.
Right-click and //Save As// either novacomd_x86.reg (for 32-bit Windows) (http://github.com/bsiegel/novacom_win7/raw/master/reg/novacomd_x86.reg) or novacomd_x64.reg (for 64-bit Windows) (http://github.com/bsiegel/novacom_win7/raw/master/reg/novacomd_x64.reg). Double-click the .reg file you downloaded to add it to the registry.
Restart your computer. This step is not optional.
3. This should enable you to run install image using cmd (similar to installing CM for the first time)
Extract the Acme Installer you downloaded in Step 2 to your desktop or wherever you want. Open up cmd ( in windows) or terminal ( in linux or mac). cd to the directory where you just extracted your Acme Installer.zip and go to step 6 for install.
Now type this in the command prompt after you have done cd
novacom boot mem:// < ACMEInstaller
NOTE: windows users might have to manually move the novacom.exe and/or AcmeInstaller into c:\programfiles\palm folder and run the above command from there.
4. novacom boot mem:// < nova-installer-image-topaz.uImage
uImage:http://www.4shared.com/file/A3U7LyA6/nova-installer-image-topaz.html...
5. After it boots, run novaterm:
novaterm (file you downloaded earlier)
Once connected to the device, type:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
then type:
mkdosfs -f 1 -s 64 /dev/store/media
6.Once that completes, put the device back into recovery mode and run the webOS Doctor.
TaDa...WebOS Doctor moves on to 13% and beyond....Back to WebOS...NOw you can reinstall CM7
How do I extract the uImage?
vmax007 said:
After it boots, run novaterm:
novaterm
Once connected to the device, type:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
then type:
mkdosfs -f 1 -s 64 /dev/store/media
Once that completes, put the device back into recovery mode and run the webOS Doctor.
TaDa...WebOS Doctor moves on to 13%
Click to expand...
Click to collapse
Okay...I'm having the same problem stuck at 12% WebOS Doctor...I'm a newbie When i run Novaterm is it from the WebOS directry on my PC or do I need to install a android version. Any additional steps for a newbie would be greatly appreciated ...I'm pretty much bricked my HP Touchpad at this point.
Thanks
Thanks a lot dude for this helpful trick ! I recover my touchpad now !!
for everybody, here is the source :
webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
the uImage is available in the jar of webosdoctor (open it with 7zip for instance) at this location :
webosdoctorp304hstnhwifi.jar\resources\webOS.tar\.\nova-installer-image-topaz.uImage
good luck !
I have the same issue
I tried doing the same thing and now I am stuck on Recovery Mode. I am tech savy but this is way out of my league.. I am trying to follow along but could someone please put a step by step process to help the fix. We are probably one of the first to do it but more to come.. This will help out everyone that does this to there touchpad. I thought I made myself a very expensive paper weight. Hopefully I can get the info I need to recover. Should I be doing everything from the CMD.. The launch of webosdoc the novacom etc?? Thanks In Advance.
PLease help! I've already tried everything..
Webos dr stops at 12% with this:
Code:
...
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68856 out of range (46147256 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68857 out of range (113262600 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68858 out of range (5792464 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68859 out of range (53487384 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68860 out of range (119554056 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68861 out of range (549696 > 352169). Setting to EOF.
How to fix this?
what i've tried to do:
1)
Code:
[email protected]:/# mkdosfs -f 1 -s 64 /dev/store/media
[email protected]:/# mkdosfs -f 1 -s 64 /dev/store/media
mkdosfs 2.11 (12 Mar 2005)
no effect, it does nothing, just says: mkdosfs 2.11 (12 Mar 2005)
2)
Code:
[email protected]:/# dosfsck -r /dev/mapper/store-media
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
FSINFO sector has bad magic number(s):
Offset 0: 0x0000003b != expected 0x41615252
Offset 484: 0x00000000 != expected 0x61417272
Offset 510: 0x0000 != expected 0xaa55
1) Correct
2) Don't correct (FSINFO invalid then)
? 1
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 1
Cluster 68857 out of range (113262600 > 352169). Setting to EOF.
Cluster 68858 out of range (5792464 > 352169). Setting to EOF.
Cluster 68859 out of range (53487384 > 352169). Setting to EOF.
... <a lot of text>
Cluster 68860 out of range (119554056 > 352169). Setting to EOF.
Cluster 68861 out of range (549696 > 352169). Setting to EOF.
Cluster 68990 out of range (137968576 > 352169). Setting to EOF.
Cluster 68991 out of range (33554432 > 352169). Setting to EOF.
Cluster 68992 out of range (213581824 > 352169). Setting to EOF.
/ÿÿÿÿ.ÿ\017
Bad file name.
1) Drop file
2) Rename file
3) Auto-rename
4) Keep it
<I drop them>
/ÿÿÿÿ.ÿ
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
/ÿÿÿÿ.ÿ
<...a lot of text>
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/037°\203\037\[email protected]ü.
Directory has non-zero size. Fixing it.
/037°\203\037\[email protected]ü.
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/åÿÿÿÿ\017
File size is 32768 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
/å\000\000\000Àÿÿ
Start cluster beyond limit (4293984255 > 352169). Truncating file.
/å\000\000\000Àÿÿ
File size is 394239 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
Reclaimed 105493 unused clusters (-838172672 bytes).
Free cluster summary uninitialized (should be 311515)
1) Set it
2) Leave it uninitialized
?
1
Perform changes ? (y/n) y
/dev/mapper/store-media: 1792 files, 40653/352168 clusters
Any ideas?
AniWarlock said:
PLease help! I've already tried everything..
Webos dr stops at 12% with this:
Code:
...
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68856 out of range (46147256 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68857 out of range (113262600 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68858 out of range (5792464 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68859 out of range (53487384 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68860 out of range (119554056 > 352169). Setting to EOF.
13.12.2011 19:50:56 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Cluster 68861 out of range (549696 > 352169). Setting to EOF.
How to fix this?
what i've tried to do:
1)
Code:
[email protected]:/# mkdosfs -f 1 -s 64 /dev/store/media
[email protected]:/# mkdosfs -f 1 -s 64 /dev/store/media
mkdosfs 2.11 (12 Mar 2005)
no effect, it does nothing, just says: mkdosfs 2.11 (12 Mar 2005)
2)
Code:
[email protected]:/# dosfsck -r /dev/mapper/store-media
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
FSINFO sector has bad magic number(s):
Offset 0: 0x0000003b != expected 0x41615252
Offset 484: 0x00000000 != expected 0x61417272
Offset 510: 0x0000 != expected 0xaa55
1) Correct
2) Don't correct (FSINFO invalid then)
? 1
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 1
Cluster 68857 out of range (113262600 > 352169). Setting to EOF.
Cluster 68858 out of range (5792464 > 352169). Setting to EOF.
Cluster 68859 out of range (53487384 > 352169). Setting to EOF.
... <a lot of text>
Cluster 68860 out of range (119554056 > 352169). Setting to EOF.
Cluster 68861 out of range (549696 > 352169). Setting to EOF.
Cluster 68990 out of range (137968576 > 352169). Setting to EOF.
Cluster 68991 out of range (33554432 > 352169). Setting to EOF.
Cluster 68992 out of range (213581824 > 352169). Setting to EOF.
/ÿÿÿÿ.ÿ\017
Bad file name.
1) Drop file
2) Rename file
3) Auto-rename
4) Keep it
<I drop them>
/ÿÿÿÿ.ÿ
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
/ÿÿÿÿ.ÿ
<...a lot of text>
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/ÿÿÿÿ.ÿ
Directory has non-zero size. Fixing it.
/ÿÿÿÿ.ÿ
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/037°\203\037\[email protected]ü.
Directory has non-zero size. Fixing it.
/037°\203\037\[email protected]ü.
Start cluster beyond limit (4294967295 > 352169). Truncating file.
/åÿÿÿÿ\017
File size is 32768 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
/å\000\000\000Àÿÿ
Start cluster beyond limit (4293984255 > 352169). Truncating file.
/å\000\000\000Àÿÿ
File size is 394239 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
Reclaimed 105493 unused clusters (-838172672 bytes).
Free cluster summary uninitialized (should be 311515)
1) Set it
2) Leave it uninitialized
?
1
Perform changes ? (y/n) y
/dev/mapper/store-media: 1792 files, 40653/352168 clusters
Click to expand...
Click to collapse
you have truly messed up your partitions!
this link is not the perfect solution but it might help
try (the filesystem below is for 32GB touchpad)
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
OR
http://www.infogenra.com/hp-touchpa...pre-alpha-build-courtesy-team-touchdroid.html (better description)
and start from the original post...
good luck
I couldnt get the registry files, does anyone else have the files?
this might work
Windows-x32: http://palm.cdnetworks.net/opensourc...com-win-32.tgz
Windows-x64: http://palm.cdnetworks.net/opensourc...com-win-64.tgz
I couldn't get those links to work aswell, It gives 404 aswell. You can mail to saisri.2k2 At gmail dot com
---------- Post added at 05:42 PM ---------- Previous post was at 05:37 PM ----------
I dont know why this forum is kinda eating away the Urls
I should note, the instructions to manually unpack the Novacom installer and then use the .reg files to register them are extremely out of date. Palm has been providing x64 builds of Novacom for some time now. As vmax007 pointed out, you just need to download them direct from Palm:
palm.cdnetworks.net/opensource/novacom/novacom-win-32.tgz
palm.cdnetworks.net/opensource/novacom/novacom-win-64.tgz
Skip step 2 from the original post and just run the installer for your system (32-bit or 64-bit Windows). You will need a tool to unpack the .tgz file first - I believe 7zip can handle this, as well as numerous other unzip tools.
Okay...I'm having the same problem stuck at 12% WebOS Doctor...I'm a newbie When i run Novaterm it just wont run, I've been trying all the steps one by one but could not get the novaterm to run. Any additional steps for a newbie would be greatly appreciated ...I'm pretty much bricked my HP Touchpad at this point.
Thanks
Need help
My touchpad stopped charging showed a question while charging.
I followed some instructions connected to Linux and was able to make it to start charging again.
Now I cant mount the device. I had CM installed so it comes to the boot menu but I cant do anything after that. It doesnt mount system / boot or something.
Any thoughts.
Someone in Delhi, India who can take a look at that
successful till step 4.
when I tried next step a window opended, with a java logo on the left top corner and written "NovaTerm:" on top center. I tried to copy the cmds one by one and tried in that window. But no instruction worked instead it replied that "command not found". pls help me what to do.
SAITEJA PARSI said:
successful till step 4.
when I tried next step a window opended, with a java logo on the left top corner and written "NovaTerm:" on top center. I tried to copy the cmds one by one and tried in that window. But no instruction worked instead it replied that "command not found". pls help me what to do.
Click to expand...
Click to collapse
Its a longer process but followed it step by step and got my TP back to working state http://forum.xda-developers.com/showthread.php?t=1426244
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
This is for all those people who want to start over. I made the mistake of using webOS Doctor without removing the Android and Linux partitions. That left me with a deer turd for an HP TouchPad. So after about 2 hours of slaving, I figured out what to do
I. What you need
Novacom - Click
Novaterm - Click (or found in C:\Program Files\Palm, Inc\terminal. Run novaterm.bat)
Recovery uImage - Click
WebOS Doctor 3.0.0 - Click
WebOS Doctor 3.0.4 (optional) - Click
II. What to do
1) Install Novacom and extract Novaterm.
2) Open a command prompt and navigate to your Palm, Inc folder (usually \Program Files\Palm, Inc)
3) Move the recovery uImage to the Palm, Inc folder.
4) Boot your Touchpad into recovery (Power + Volume Up from power off)
5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage ) (without the parenthesis)
6) Once run, all you'll see on the Touchpad is the HP logo. This is good. Now open Novaterm and hit Connect
7) If you see a prompt that says something like "[email protected] device" this is good, now run these commands IN ORDER and these commands are CASE SENSITIVE
(For 32GB Touchpads only)
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Click to expand...
Click to collapse
(16GB Touchpads)
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 1618 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Click to expand...
Click to collapse
8) When done, reboot the Touchpad into recovery (Power + Center/Home until screen off, then Power + Volume Up)
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
Branch 1) You can stop here to have 3.0.0 as your webOS version. You've just completed a downgrade that was before thought impossible.
Branch 2) If you want webOS 3.0.4, continue on.
10) When webOS Doctor is complete, hold down Power and Center, and when the screen turns off, immediately hold Power and Volume Up.
11) You'll see the USB icon again, just run webOS Doctor 3.0.4 and you're done.
Have fun.
_____________________________
For those having problems with novaterm:
LordGibson said:
I had the same problem with the downloaded novaterm on three different win7x64 machines. If you've run WebOS Doctor at all you should have a Palm, Inc/terminal/ folder with a novaterm.bat in it. Try using that instead.
Click to expand...
Click to collapse
For those having problems with Java:
lafester said:
got it working by adding the path to java.
set PATH =%PATH%;c:\program files (x86)\java\jre6\bin.
Click to expand...
Click to collapse
If someone can, can they provide the partition layout for 16GB Touchpads?
How could we find the partition layout ?
Edit :
--
I ran the following command on my 16GB TouchPad :
Code:
lvm.static vgdisplay
And I get :
Code:
Free PE / Size 1683 / 13.15 GB
Is it what you're looking for ?
spadewalk said:
How could we find the partition layout ?
Edit :
--
I ran the following command on my 16GB TouchPad :
Code:
lvm.static vgdisplay
And I get :
Code:
Free PE / Size 1683 / 13.15 GB
Is it what you're looking for ?
Click to expand...
Click to collapse
Can you run lvm.static lvdisplay ?
Sure.
Here you have :
Code:
lvm.static lvdisplay
--- Logical volume ---
LV Name /dev/store/root
VG Name store
LV UUID Aq5Mpj-p1ou-AMwd-j0YJ-1ytK-nHVn-NlOGUR
LV Write Access read/write
LV Status available
# open 1
LV Size 568.00 MB
Current LE 71
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 0
Block device 254:0
--- Logical volume ---
LV Name /dev/store/var
VG Name store
LV UUID 1OQAZu-Zx0P-fK6M-xdYj-8T0z-CoDw-2pwy00
LV Write Access read/write
LV Status available
# open 1
LV Size 64.00 MB
Current LE 8
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 1
Block device 254:1
--- Logical volume ---
LV Name /dev/store/update
VG Name store
LV UUID 9Cpv99-Al2S-eCWp-ioAi-AGMS-T10i-qba3pn
LV Write Access read/write
LV Status available
# open 0
LV Size 16.00 MB
Current LE 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 2
Block device 254:2
--- Logical volume ---
LV Name /dev/store/log
VG Name store
LV UUID jaNcqX-uRU7-uwWi-yvZE-KHiN-K5RX-mh3jkJ
LV Write Access read/write
LV Status available
# open 1
LV Size 24.00 MB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 3
Block device 254:3
--- Logical volume ---
LV Name /dev/store/mojodb
VG Name store
LV UUID 7nT2OX-nlbV-U6HQ-UrVi-Pja6-nDwP-BpHsTR
LV Write Access read/write
LV Status available
# open 1
LV Size 256.00 MB
Current LE 32
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 4
Block device 254:4
--- Logical volume ---
LV Name /dev/store/filecache
VG Name store
LV UUID oH0jt0-AcIO-pFTF-3wD7-cYC2-W88I-H0UqPj
LV Write Access read/write
LV Status available
# open 1
LV Size 136.00 MB
Current LE 17
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 5
Block device 254:5
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID NWNspe-aKe5-glCM-c0mb-15sM-32Mu-64e8jx
LV Write Access read/write
LV Status available
# open 1
LV Size 12.64 GB
Current LE 1618
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 6
Block device 254:6
--- Logical volume ---
LV Name /dev/store/swap
VG Name store
LV UUID TOq7Y8-2XCB-diKE-3D7s-3pIp-Ksbl-4LbZP0
LV Write Access read/write
LV Status available
# open 1
LV Size 512.00 MB
Current LE 64
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 7
Block device 254:7
spadewalk said:
Sure.
Here you have :
Code:
lvm.static lvdisplay
--- Logical volume ---
LV Name /dev/store/root
VG Name store
LV UUID Aq5Mpj-p1ou-AMwd-j0YJ-1ytK-nHVn-NlOGUR
LV Write Access read/write
LV Status available
# open 1
LV Size 568.00 MB
Current LE 71
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 0
Block device 254:0
--- Logical volume ---
LV Name /dev/store/var
VG Name store
LV UUID 1OQAZu-Zx0P-fK6M-xdYj-8T0z-CoDw-2pwy00
LV Write Access read/write
LV Status available
# open 1
LV Size 64.00 MB
Current LE 8
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 1
Block device 254:1
--- Logical volume ---
LV Name /dev/store/update
VG Name store
LV UUID 9Cpv99-Al2S-eCWp-ioAi-AGMS-T10i-qba3pn
LV Write Access read/write
LV Status available
# open 0
LV Size 16.00 MB
Current LE 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 2
Block device 254:2
--- Logical volume ---
LV Name /dev/store/log
VG Name store
LV UUID jaNcqX-uRU7-uwWi-yvZE-KHiN-K5RX-mh3jkJ
LV Write Access read/write
LV Status available
# open 1
LV Size 24.00 MB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 3
Block device 254:3
--- Logical volume ---
LV Name /dev/store/mojodb
VG Name store
LV UUID 7nT2OX-nlbV-U6HQ-UrVi-Pja6-nDwP-BpHsTR
LV Write Access read/write
LV Status available
# open 1
LV Size 256.00 MB
Current LE 32
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 4
Block device 254:4
--- Logical volume ---
LV Name /dev/store/filecache
VG Name store
LV UUID oH0jt0-AcIO-pFTF-3wD7-cYC2-W88I-H0UqPj
LV Write Access read/write
LV Status available
# open 1
LV Size 136.00 MB
Current LE 17
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 5
Block device 254:5
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID NWNspe-aKe5-glCM-c0mb-15sM-32Mu-64e8jx
LV Write Access read/write
LV Status available
# open 1
LV Size 12.64 GB
Current LE 1618
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 6
Block device 254:6
--- Logical volume ---
LV Name /dev/store/swap
VG Name store
LV UUID TOq7Y8-2XCB-diKE-3D7s-3pIp-Ksbl-4LbZP0
LV Write Access read/write
LV Status available
# open 1
LV Size 512.00 MB
Current LE 64
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 7
Block device 254:7
Click to expand...
Click to collapse
Thank you. I was able to make the correct commands for 16GB Touchpads.
Good, that's awesome.
where is the novacom installer?
and the webdoctor, for that matter?
did i have to read 20 other threads / posts before this one?
lol
serialteg said:
where is the novacom installer?
and the webdoctor, for that matter?
did i have to read 20 other threads / posts before this one?
lol
Click to expand...
Click to collapse
If you even bothered to look at the post, you'd see that next to each one, there is a word that says "click". And if you clicked on them, you'd see that they are DIRECT links to what you need.
Just wanted to say this worked for me too; in case anyone is worried. I had Ubuntu native, CM9, and Webos (duh) installed but my /media/internal partition was messed up (webos and windows 7 said it was 22GB while lvscan said 14GB). I tried doctoring but just got a hp logo boot loop. These commands got me back to webos.
same here, but after following this tutorial my touchpad iz back to life, thank you !
Wow this is a great tut and I bet there is a lot of people who wI'll
Be needing this soon!!
Thanks
saved my TP thanks!!! but my app catalog has a yellow triangle in the corner....any ideas?
Sadly, this did not work for me. The WebOS Doctor 3.0.0 completes successfully but the TP never boots up fully - rolls right back into the boot loop. Just for the hell of it I ran the 3.0.5 update afterwards. That also completes successfully, but lands right back into the boot loop.
I've just finished my third attempt from start to finish with no luck. Guess I must be looking at a hardware problem. . . Any other ideas?
LordGibson said:
Sadly, this did not work for me. The WebOS Doctor 3.0.0 completes successfully but the TP never boots up fully - rolls right back into the boot loop. Just for the hell of it I ran the 3.0.5 update afterwards. That also completes successfully, but lands right back into the boot loop.
I've just finished my third attempt from start to finish with no luck. Guess I must be looking at a hardware problem. . . Any other ideas?
Click to expand...
Click to collapse
Did you run the comands in order and did you use the proper partition setup for your touchpad?
rr5678 said:
Did you run the comands in order and did you use the proper partition setup for your touchpad?
Click to expand...
Click to collapse
Affirmative. By the third time through I was pretty anal about doing everything perfectly and exactly as indicated.
LordGibson said:
Affirmative. By the third time through I was pretty anal about doing everything perfectly and exactly as indicated.
Click to expand...
Click to collapse
Start it. And while it's doing the boot loop, see if you can connect with novaterm.
It's a refurb unit, so it's probably a hardware problem - just strange that the doctors seemingly work so well.
Maybe I'll try 16gb just for the hell of it. Perhaps it was mis-labeled. . .
---------- Post added at 10:27 PM ---------- Previous post was at 10:23 PM ----------
rr5678 said:
Start it. And while it's doing the boot loop, see if you can connect with novaterm.
Click to expand...
Click to collapse
No joy. Windows signals a connection, but can't find device in novaterm.
---------- Post added at 10:54 PM ---------- Previous post was at 10:27 PM ----------
LordGibson said:
Maybe I'll try 16gb just for the hell of it. Perhaps it was mis-labeled. . .
Click to expand...
Click to collapse
For future reference, I would recommend against this course of action.
LordGibson said:
---------- Post added at 10:27 PM ---------- Previous post was at 10:23 PM ----------
No joy. Windows signals a connection, but can't find device in novaterm.
Click to expand...
Click to collapse
Boot it into the recovery uImage and check what's in the boot folder.
LordGibson said:
---------- Post added at 10:54 PM ---------- Previous post was at 10:27 PM ----------
For future reference, I would recommend against this course of action.
Click to expand...
Click to collapse
You could have had yourself a doorstop.
Code:
[email protected]:/boot# ls -la
drwxr-xr-x 2 root root 1024 Jul 30 2011 .
drwxr-xr-x 17 root root 1024 Jul 30 2011 ..
-rw-r--r-- 1 root root 490764 Jul 30 2011 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119371 Jul 30 2011 boot-images.tar.gz
-rw-r--r-- 1 root root 115392 Jul 30 2011 boot.bin
-rwxr-xr-x 1 root root 1131 Jul 30 2011 genesis-update.xml
-rwxr-xr-x 1 root root 2224 Jul 30 2011 image-update.xml
lrwxrwxrwx 1 root root 29 Jul 30 2011 uImage -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 3333228 Jul 30 2011 uImage-2.6.35-palm-tenderloin
hey everyone, yes im abit of a noob and need some help.
i was trying to install Arch on my touchpad and hit an error. now my touchpad keeps cycling the hp logo and wont turn on or off. ive tried webos doctor and still this problem is still here.
please help
thank you for any help given
give us some details on how did it occur and what were you doing when it gave you an error (what was the last command you run for example)
"curl -O http://archlinuxarm.org/mirror/touchpad/ArchLinuxARM-touchpad-latest.tar.gz"
this was the last command i wrote, and it downloaded about 39mb and failed. before this i had partitioned the hard drive too.
is this fixable?
sissons87 said:
before this i had partitioned the hard drive too.
Click to expand...
Click to collapse
i think the keyword for the problem is here, can you recall what commands exactly did you run?
also just like chessmaster w/nook asked you, do you have moboot installed?
Holding down the power and home key always reset my tp. And with HP its pretty impossible to brick ur device HP doc
okay heres a detailed explanation of what i done.
i put my touchpad in to dev mode.
accessed novaterm from my ubuntu window.
i then followed all of these commands:
"mount -o rw,remount /boot
cd /tmp
curl -O http://moboot.googlecode.com/files/moboot_0.3.5.zip
unzip moboot_0.3.5.zip
mv uImage.moboot_0.3.5 /boot/uImage.moboot
cd /boot
rm uImage
ln -s uImage.moboot uImage
ln -s uImage-2.6.35-palm-tenderloin uImage.webOS
echo "yes" > moboot.verbose.ArchLinuxARM
sync
curl -O http://archlinuxarm.org/mirror/touchpad/uImage.ArchLinuxARM
curl -O http://archlinuxarm.org/mirror/touchpad/moboot.splash.ArchLinuxARM.tga
cd /tmp
pkill -SIGUSR1 cryptofs
umount /media/internal
echo "STOP HERE AND READ 'RESIZE FAT' BEFORE CONTINUING" # See below
resizefat /dev/store/media ****M
lvm.static lvresize -L -4096M /dev/store/media
lvm.static lvcreate -L 4096M -n arch-root store
mkfs.ext3 /dev/store/arch-root
mkdir linux
mount /dev/store/arch-root linux
cd linux
curl -O http://archlinuxarm.org/mirror/touchpad/ArchLinuxARM-touchpad-latest.tar.gz
tar xzf ArchLinuxARM-touchpad-latest.tar.gz # Will take a long time
rm ArchLinuxARM-touchpad-latest.tar.gz
cd ..
umount linux
reboot # The first few times, this may error out - try again"
where the ****M is i put 7944M i think this may be the issue.
when i got to this command it started downloading and then got an error at 39mb:
"curl -O http://archlinuxarm.org/mirror/touchpad/ArchLinuxARM-touchpad-latest.tar.gz"
ive then ran webos doctor numbers of times but no luck. it wont even let me novaterm back in not sure what to do :/ any help would be great.
sissons87 said:
hey everyone, yes im abit of a noob and need some help.
i was trying to install Arch on my touchpad and hit an error. now my touchpad keeps cycling the hp logo and wont turn on or off. ive tried webos doctor and still this problem is still here.
please help
thank you for any help given
Click to expand...
Click to collapse
I had that same bootloop problem. Try this: http://forum.xda-developers.com/showthread.php?t=1426244
rr5678 said:
I had that same bootloop problem. Try this: http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
All has worked okay but having problems creating swap store. Error im getting is:
Redundant stripes arguement: default is 1
Insufficiant free extents (0) in volume group store: 64 required
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
sissons87 said:
All has worked okay but having problems creating swap store. Error im getting is:
Redundant stripes arguement: default is 1
Insufficiant free extents (0) in volume group store: 64 required
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Did you enter
"lvm.static lvcreate -l 1761 -i 1 -M y --major 254 --minor 6 -n media store"
or
"lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store"?
rr5678 said:
Did you enter
"lvm.static lvcreate -l 1761 -i 1 -M y --major 254 --minor 6 -n media store"
or
"lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store"?
Click to expand...
Click to collapse
I entered " "lvm.static lvcreate -l 1648 -i 1 -M y --major 254 --minor 6 -n media store" i wouldnt let me put 1761 cus i got the same sort of error.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
sissons87 said:
I entered " "lvm.static lvcreate -l 1648 -i 1 -M y --major 254 --minor 6 -n media store" i wouldnt let me put 1761 cus i got the same sort of error.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Okay, try it again, except this time, enter
"lvm.static lvcreate -l 1584 -i 1 -M y --major 254 --minor 6 -n media store"
Okay how do i undo what ive just done? Run all commands again?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
sissons87 said:
Okay how do i undo what ive just done? Run all commands again?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Yes, running them again will erase all the necessary stuff so you can rebuild it.
Okay thank you, i will try that now
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Hii !
I got exactly the same problem ! And I followed a tutorial I found on rootzwiki (dumb I can't post the link cuz this is my first message).
Anyway look for that on Google (with the quotes) :"HOW TO make a larger cm7 data partition" touchpad
It's a txt file and it worked all fine on mine. Hope it would help you.
would like to thank you all for all your help rr5678 you were a great help! im going to and try install arch again or another os now. wish me luck dnt learn with out try eh
Thanks a lot rr5678 too for your tutorial, I figured that the tutorial I found wasn't good as yours.
sissons87 said:
would like to thank you all for all your help rr5678 you were a great help! im going to and try install arch again or another os now. wish me luck dnt learn with out try eh
Click to expand...
Click to collapse
Glad to hear that it worked for you.
Hi guys,
I started having this issue that every-time I use the Touchpad on CM9 or WebOS it just freezes and reboots/resets...
Take a look:
No mater what I do (I've tried this souldevteam.net/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad it always goes back to reboot/reset loop as soon as I start to use it.
I have this Touchpad since new and never had any issues in the pass.
I would like some pointers in what can I do to repair, is the problem at the mainboard? memory? hdd? I could use this place to get parts: portatronics.com
Thanks!
It does it both in CM9 and WebOS? If so, I'd just run the ACMEUninstaller, run WebOS Doctor and once thats all finished, boot into WebOS (DONT install Android yet) and see if it continues bootlooping.
This thread may be of use to you. http://forum.xda-developers.com/showthread.php?t=1564938
allstar319 said:
It does it both in CM9 and WebOS? If so, I'd just run the ACMEUninstaller, run WebOS Doctor and once thats all finished, boot into WebOS (DONT install Android yet) and see if it continues bootlooping.
This thread may be of use to you. http://forum.xda-developers.com/showthread.php?t=1564938
Click to expand...
Click to collapse
Yes on both, same thing:
I did use ACMEUninstaller and then wiped the partitions:
Code:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Then I do a WebOS 3.0 then 3.05, same thing.
I guess it is highly probable to be a Hardware problem, do you know who can fix this besides HP?
Thanks!
Jor3lBR said:
Yes on both, same thing:
I did use ACMEUninstaller and then wiped the partitions:
Code:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Then I do a WebOS 3.0 then 3.05, same thing.
I guess it is highly probable to be a Hardware problem, do you know who can fix this besides HP?
Thanks!
Click to expand...
Click to collapse
Sorry, nope. Unless someone else can think of a way to fix it, seems it could be a hardware issue. If you're still in warranty, just open up a request with HP and ship it to them. Just be sure to wipe Android completely. If not, search around town and see if any of those phone repair shops can take a look at it or see if HP can fix it for a price.
allstar319 said:
Sorry, nope. Unless someone else can think of a way to fix it, seems it could be a hardware issue. If you're still in warranty, just open up a request with HP and ship it to them. Just be sure to wipe Android completely. If not, search around town and see if any of those phone repair shops can take a look at it or see if HP can fix it for a price.
Click to expand...
Click to collapse
Well I bought it in 12/2011 as a Refurb, so it's out of the warranty.
I could try here but nobody seams to ever heard of this store: www portatronics com
when did it start doing this? before or after you flashed CM9? If it didnt always do this, then it's likely not a hardware issue. if not then try to think of what changes you made that may have done this.
SOLVED
haxin said:
when did it start doing this? before or after you flashed CM9? If it didnt always do this, then it's likely not a hardware issue. if not then try to think of what changes you made that may have done this.
Click to expand...
Click to collapse
Hi I was able to fix it finally!
Because I paid $115 refurb for this brand new I didn't want to send anywhere to pay over $200 for repairs...
So I followed this guide:
HP TouchPad Take Apart Repair Guide Be careful not to brake the clips!
After opening the TP I removed the mainboard only.
I placed the mainboard only inside a non-stick foil paper and placed it in the oven at 395o.F for 10 minutes (like I used to do to my broken video cards in the old days)...
After that I let it rest and the following morning I put everything back together!
Amazingly the TP powered up right away and now is free of the reboot loop issues!!!!!! :evil:
I couldn't believe it but it did work.
My conclusion is that is was a hardware error, most likely weak solder joints in the MB.
That's awesome.
Let's face it, these tablets have had a good run but they're just unusably slow and laggy with any remotely modern version of android. Unfortunately going back to stock is not the simplest in 2022, especially if you've tried one of the more extreme android installs which wipes WebOS and rebuilds the partition table. I spent the morning collecting files and putting together a process from about 25 different websites dating back to 2012. The most comprehensive guide I found was Here but it still didn't fully work for me and some commands had to be done differently, particularly when rebuilding the partitions.
Keep in mind I wasn't kidding when I called this the nuclear option. If you can use any other less extreme method you probably should. This one is a risky pain and basically boils down to nuking the whole thing from orbit before rebuilding the partitions line by line by hand in a terminal.
Necessary files
Everything can be found in this mega folder
ACMEUninstaller2
Novacom
devicetool.jar
WebOS doctor jars (versions 3.0.0 and 3.0.5 in conjunction with devicetool should let you skip the now broken WebOS activation step)
7zip or similar program that can open jar files
Recovery image (nova-installer-image-topaz.uimage)
Java
WebOS quick install
Setup
Make sure Java is installed and working on your system
Make sure your touchpad is fully charged
Open Novacom files.zip and find the right version for your architecture. Odds are that's win-64. If you're on linux check your distro's repos first
Reboot (esp if you're on windows)
Find the Palm, Inc (lowercase L, capital i) folder. On windows this defaults to c:/Program Files/Palm, Inc
Place nova-installer-image-topaz.uimage in your Palm, Inc folder
Place ACMEUninstaller2 in your Palm, Inc folder
Boot your touchpad into WebOS recovery mode, either via bootloader or by holding power+volumeup (can take up to ~30secs)
Open a terminal window and navigate to your Palm, Inc folder
Run one of the below commands. THIS IS THE POINT OF NO RETURN.
Windows: novacom.exe boot mem:// < ACMEUninstaller2
Mac: ./novacom boot mem:// < ACMEUninstaller2
You should see a bunch of text scrolling and two images of a penguin around the top to one side. When it's finished it will warn you there's nothing installed it recognizes.
Try to reboot into recovery mode. You will probably get an exclamation mark with www.palm.com/ROM below it, or just the HP logo
In the Palm, Incterminal execute the below command (capitalization matters):
novacom boot mem:// < nova-installer-image-topaz.uimage
Navigate your terminal to the terminal subfolder and execute novaterm.bat
A small java window named "NovaTerm:" should pop up on your screen
In the NovaTerm: window click file and then connect
Another popup should appear titled Select device to connect with a really long string of letters and numbers ending in (usb, topaz-linux) in it. Click OK
If not check the dropdown arrow, make sure your USB is connected, reboot if all else fails and try again
Now that NovaTerm:says it's connected go back to your terminal and execute the below:
Windows: novacom -t open tty://
Everything else: novaterm should have been enough
Your terminal should now say [email protected]:/# or the like. There may be some extra gibberish if you pressed an arrow key or something.
Now you need to rebuild all your partitions. Execute ONE of the code blocks below these instructions in exact order, one line at a time. You should not see any errors about something being mounted or the like. If you do reboot your touchpad and try to restart from step 13, that's what I did.
Once that is done try to reboot into recovery mode again, you'll probably only get the HP logo instead of the big USB symbol.
Open a new terminal window and navigate to wherever you're keeping the WebOS Doctor jar files
start WebOS doctor 3.0.0 (the only version that can deal with partition issues) from inside the terminal so you can see the output: java -jar webosdoctorp300hstnhwifi_customhpactivationbypass.jar
Don't touch the WebOS doctor window. Moving it to other monitors seems to break it for some reason.
If you see errors where it's trying to find the device and can't try unplugging/replugging the touchpad. If that doesn't work try rebooting. One person said uninstalling novacom at this point and letting WebOS reinstall the drivers fixed it. It seems hit or miss if there's weird USB detection issues on Win10.
WebOS doctor should complete without issues and have you reboot.
When the touchpad successfully reboots it'll ask start asking you for a language and first time activation. HP's master servers are down, this won't work. Reboot into recovery again
Navigate your terminal to wherever you're keeping devicetool.jar and execute it: java -jar path/to/devicetool.jar
Your terminal should say "found device: topaz-bootie" and then talk about configuring things and volumes for a while.
Once the terminal says Device is ready. reboot once final time.
That should be it. Once you've got everything installed and WebOS up and running there's still a few steps needed to deal with the lack of auth servers and expired certificates.
Enable developer mode by putting webos20090606 into the "Just Type" bar on the homepage and hitting enter
Run WebOS-Quick-Install-4-7-2.jar just as if it were a normal application (no need for terminal). It's basically a replacement app store that runs on the PC.
You should see the HP Touchpad recognized by WebOs Quick Install. If it is click the globe on the right side of the app's window
Search for "Preware" in the popup (you need to click the magnifying glass after typing)
Install Preware, which is a replacement app store that runs on the touchpad itself
32gb touchpad partitions
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
16gb touchpad partitions
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 1618 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Troubleshooting
If your touchpad's home button has an LED blinking from side to side the battery isn't charged enough. Use the stock charger if available and leave it until it boots itself up. This could potentially take days. Mine only took about 12 hours.
If instead of recovery mode you get either a plain HP logo or an exclamation mark with www.palm.com/ROM below it this means your disk is wiped and there isn't even a recovery or anything. You'll need to use novacom to force nova-installer-image-topaz.uimage onto the touchpad and then connect to it externally using the novaterm utility. Once you run ACMEUninstaller2 this is the expected result.
If you're getting errors about the exclusivity of mmcblk0p14 and asking if it's mounted something went weird while running all of the partitions, try rebooting and starting again.
If you want to download the original WebOS doctor files you need to edit your hosts file and add 195.22.200.42 downloads.help.palm.com
A list of all the resources I used to compile this:
https://hroy.eu/tips/webos-touchpad-restore/ (massive credit to Hroy here, this is by far the most complete guide though it still needed tweaks to the partition rebuilding commands)
Code:
https://www.webos-internals.org/wiki/WebOS_Doctor_Versions
https://forum.xda-developers.com/t/q-touchpad-seems-bricked.1971859/page-2#post-57616293
https://www.webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
https://www.webosarchive.org/docs/activate/
https://forums.webosnation.com/hp-touchpad/330977-how-restore-hp-touchpad.html
https://pivotce.com/2015/06/24/tip-how-to-bypass-activation/
https://pivotce.com/2015/12/13/the-ultimate-bypass-activation-tool/
https://forums.webosnation.com/hp-touchpad/329655-hp-tp-server-error.html
https://forums.webosnation.com/hp-touchpad/317164-activation-bypass-touchpad.html
https://forum.xda-developers.com/t/need-help-webos-fails-at-8-for-hp-tp-due-to-insufficient-free-extents-0-in-volume.3275076/
https://forum.xda-developers.com/t/solved-bricked-and-webos-doctor-wont-help.1564938/
https://forums.webosnation.com/hp-touchpad/325404-recurring-maps-download-failed-error-2.html
https://forum.xda-developers.com/t/guide-factory-condition-restoration-downgrade-to-webos-3-0-0.1426244/
https://forums.webosnation.com/hp-touchpad/332616-getting-restarted-touchpad.html
https://forums.webosnation.com/canuck-coding/274461-webos-quick-install-v4-6-0-a.html
https://forum.xda-developers.com/t/tools-touchpad-toolbox-updated-2015-02-25.2756314/page-4#post-52922166
[MEDIA=youtube]VP-FH6fS2GI[/MEDIA]
[MEDIA=youtube]wFAIJiS8g4o[/MEDIA]
https://forum.xda-developers.com/t/rom-guide-how-to-install-android-on-the-hp-touchpad-the-easy-way.2147284/#post-37965549
https://forums.webosnation.com/hp-touchpad/309309-hp-touchpad-booting-issues.html
https://www.rootzwiki.com/threads/the-official-fix-your-touchpad-8-12-stopped-no-sd-opps-reformat-crap-thread.14249/
https://forum.xda-developers.com/t/guide-video-how-to-bypass-webos-activation-on-the-hp-touchpad.3636750/
https://pivotce.com/2015/06/15/tip-edit-your-hosts-file-for-access-to-old-palm-servers/
hi thanks for the guide,
I agree with you android roms lag quite.
Tired too I restored webOs ,having many of your problems, but unfortunately it is a dead operating system.
Despite the fluidity there is no way to use it. I will go back to android testing all the roms.
Unfortunately this tablet is of its age