[TouchPad General] vmax007:
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