12% WebOS Doctor Fix; CM7 Install - TouchPad General

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