Database Develop

[Q] ROM Manager CWM Recovery completely unavailable?

Hey guys, I posted this over at Rootz but it's not getting any action. I really appreciate the help...
Hey Gents,
I couldn't wait any longer so I installed Alpha2 on my Touchpad and was happy as a pig in sh*t after spending about two days on it. Then I got curious about the Nightly builds and came across a problem that is killing me. I can not boot into Recovery mode. I've tried everything, I've searched up and down on the forums but it seems like everyone can at least get into recovery. Moboot has "boot webOS Recovery" option but no "boot clockworkmod". I've tried through ROM Manager, I've tried through ROM Toolbox, etc. Nothing. I uninstalled the Alpha2 through ACMEUninstaller and then reinstalled the latest Nighty Build through ACMEIntstaller2 with the other files needed for Android. Nothing. I tried booting into recovery on my S2 Skyrocket, no problem. I'm pulling my hair out here.
Any ideas?
here's exactly what I did:
1- installed novacom driver
2- copied ACMEInstaller2 over to the Palm, Inc folder in Program Files
3- plugged in Touchpad via USB and copied the gapps, Cyanogenmod9, recovery_update_tenderloin and moboot zipped files to my folder I created "cminstall"
4- unplugged TP, put it in USB recovery mode, reattached it via USB and ran the command prompt
5- Ran perfectly smooth, played with Android for a few days.
- ROM Manager is installed, Google apps work perfectly, dual boot is alive and well, etc.
everything works great but RECOVERY. When I reboot and hit recovery or when I go straight into ROM Manager and hit recovery, I end up at the boot screen.
another weird thing... when I checked out my files in "cminstall" via Astro, the recovery one was still there as a zipped file. All the other files were gone. Not sure if this means anything but I figure the more info the better.

I am not totally sure on this so may get blasted, but check the filename of the zip in the cminstall folder. I had this impression that the zip files needed to start 'update-' for AcmeInstaller to handle them. I think some of the cwm zips have other filenames, but it doesn't hurt to rename and try AcmeInstaller2 again.

You probably need to clear up some room in the boot partition. I had the same issue with initial install of cm7. Recovery wouldn't flash properly because there was not enough room. Make enough room in your /boot and flash through ACMEinstaller.
Sent from my PG06100 using Tapatalk 2

Ok, so you mean on the Touchpad I need to get rid of a bunch of data? Like where I store music and movies and all that? I have a HUGE amount of free space on there. Easily 60% of the 32GB is free.

on a side note, would I be able to flash continuously through ACMEInstaller2 rather than CWM Recovery? Like say an official beta comes out, could I just run the command lines without all the other zip folders right over the version installed??

copene said:
Ok, so you mean on the Touchpad I need to get rid of a bunch of data? Like where I store music and movies and all that? I have a HUGE amount of free space on there. Easily 60% of the 32GB is free.
Click to expand...
Click to collapse
in your /boot folder you may have too much stuff... do some reading and delete everything that shouldnt be there
copene said:
on a side note, would I be able to flash continuously through ACMEInstaller2 rather than CWM Recovery? Like say an official beta comes out, could I just run the command lines without all the other zip folders right over the version installed??
Click to expand...
Click to collapse
you could but why would you want to

yup, that was the problem! the CWM file I DL'd from precentral didn't start with "update". I grabbed the file directly from Rootz and it installed perfectly. Thank you so much, everything is working as it should now.
Thanks a lot guys.

In your /boot, if you wanna just have the stuff for WebOS and Alpha2, you should have the following in your /boot:
Folders:
bin/
dev/
etc/
lib/
lost+found/
proc/
realroot/
sbin/
sys/
usr/
Files:
boot-genesis.tar.gz
boot-images.tar.gz
boot.bin
config-2.6.35-palm-tenderloin
genesis-update.xml
image-update.xml
moboot.default
moboot.splash.CyanogenMod.tga
moboot.splash.webOS.tga
moboot.timeout <== You might not have this.
System.map-2.6.35-palm-tenderloin
uImage
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod <== You apparently don't have this
uImage.CyanogenMod
uImage.moboot
uImage.webOS
updatefs-info
If you have other files in there aside from those listed, feel free to delete the extras. Your /boot partition is only 30 MB, so you need to have some room left in there. The uImage.ClockworkMod is about 5 megs, and if you have nothing BUT WebOS and CM9 installed (I have the last official nightly), you should have 22 megs or so used.
Hope that helps, mate.

Trouble installing moboot

Hi there everyone, I hope someone can help me out because I can't figure it out myself!
I used to have webOS and CWM 7 installed as dualboot on my touchpad.
However CWM 7 had tons of bugs and I decided to remove it.
I removed it by using webOSdoctor (and something else too perhaps)
Now when i tried to install android ICS using ACMEinstaller2, everything seems to go fine.
I get no error with the cmdprompt and there are bunches of lines passing through my touchpad.
When that's finished, it's supposed to reboot into moboot.
For some strange reason it doesn't.
I put all my files in cminstall folder on the touchpad as prescribed and acmeinstaller2 in the palm folder.
I get no erros, but I just can't boot into moboot because it goes straight to webOS as it would normally.
Anybody has any ideas or guides to I could follow in order to install Android afterall?
Thanks!

Did the moboot zip file you used have a filename that started with 'update-'. If not, AcmeInstaller2 would not have installed it. You should be able to just rename the zip file and run AcmeInstaller2 again.

It did not have update- in front of it.
I edited the filename and retried, yet results remain the same.
I re-ran the ACMEuninstaller once more,retried installing it and moboot seems to be installed as it should.
Thanks anyway!

Clockwork mod missing

Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero

zeroman9121 said:
Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero
Click to expand...
Click to collapse
Do you still have "ulmage.ClockworkMod" in the boot folder, it sounds like it must be gone or it should show up as an option in moboot? With mine when I installed TWRP it didn't change the options in moboot, moboot still says ClockworkMod but when that is selected it goes into TWRP and there is no "ulmage.TWRP" in my boot folder. I thought that was how TWRP was meant to install on the TP. I'm not sure if there is another way to install CWM other than with the ACME2installer, might be worth a search.
Did you make sure "update-cwm_tenderloin-1012" was in the "cminstall" folder when you ran ACME2?
You could move your backup to comp, run ACMEuninstaller and webos doctor and start from scratch and install CM9. Then just restore from your backup. I've done that a few times for other reasons.
Good Luck

Thanks for the help man, the CWM i was using was called recovery_cwm and i just had to change the name to update_cwm and let acmeinstaller do the rest. Saved me alot of time by avoiding uninstalling everything and restoring.
- Zero

CWM gone while installing TWRP through gooMan
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.

avisekhg said:
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.
Click to expand...
Click to collapse
If you have the install zip from sd card option, then flash jcsullins' recovery. Use the 12/15 version.
You can also install the same recovery using acmeinstaller 3.
There's a moboot cleaning utility, on the classic nerds' site (use it if you need to get rid of 'ghost' uimages).
Edit : here's the link to jcsullins' recovery : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Edit 2 : here's another link that would be useful : http://forum.xda-developers.com/showthread.php?t=2030675&page=4

Complete Installation Guide for JB or ICS on a Nexus One (Updated 12/29/12)

I initially looked for a complete update guide on here and eventually found all the information I needed, but it was in multiple places and sometimes hard to find. After getting everything installed on my N1 I thought I would write a guide for other noobs like me that want to try out ICS or JB but would like a step-by-step guide. I hope that it is helpful. SpazeDog ROMs (both ICS and JB) are working wonderfully on my N1 - its a very nice update from CM7 with only minor issues so far.
Note: this was initially written specifically for SpazeDog roms, but as they have not been updated in a while I have provided links to other popular roms as well. If you would like to try a different ICS or JB rom this guide should work, just substitute with the appropriate rom and depending on the one you choose, you may also need to install Google apps.
If you looking at this guide and don't know the basics yet, check out the Newbie Friendly thread first.
Links to popular roms that will work using this guide:
Evervolv JB 4.2
Evervolv JB 4.1
CM 10, JB 4.1.2 by vijendrahs
CM 10, JB 4.2.1 by vijendrahs
Spazedog ICS/JB
Disclaimer: This guide involves making changes to your phone that potentially could brick your phone leaving it unusable. I am not liable for any changes you make or problems you may have with your phone. You should at least be familiar with entering commands using command prompt. This procedure will erase ALL the data on your phone. Make sure you have a backup of everything. A nandroid backup is highly recommended. Proceed at your own risk.
Before we get started make sure you have the following: a rooted Nexus One, a USB cable to attach your phone to a computer, and the Android SDK. If you are just now installing the Android SDK, open the SDK manager and make sure to install the "Tools" and in "Extras" the "Google USB Driver" are checked off and download them. Alternatively, you just download ADB and Fastboot (search this forum or google). If you have a Mac see this thread to get started with ADB and Fastboot.
If you Nexus One is NOT already rooted, then follow this guide from Cyanogenmod to root your phone. If you plan to use the adb commands below (they are optional) make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Step 1 - Download everything you will need:
4EXTRecovery Updater - the first link will download the .apk to your computer or phone.
BlackRose - go down to bottom of the first post to "Attached Files" and download the latest BlackRose zip file. If you don't want to do it yourself, check out this thread to flash a pre-made partition scheme. Often the developers (Evervolv) will also have a partition schemes that you can flash via Fastboot from your PC as well.
Your rom of choice - go to the downloads section and choose which rom you would like to try. Download the zip installation file.
Since you will be decreasing the size of your partition that apps can be stored on consider something like Mounts2SD or AD2SDX to move apps to your SD card.
Step 2 - Install and use 4EXTRecovery Updater on your phone:
The easiest thing to do is go to the 4ext link above, download and install it, directly from your nexus one. You can also install it by copying the APK file to your SD card, then using a file manager to find it and install it or you can use command prompt by opening command prompt, cd to the location of the Android SDK tools, and then type in the following command (replacing "path" with the path to where the APK is located on your computer):
Code:
adb install /path/4EXTRecoveryUpdater.apk
After you have installed 4ext open the 4EXT Recovery Updater. Tap "Settings" → "Allow" superuser request → "Yes" to connect to 4ext to get new data. Now select "Online install/upgrade" → "Yes" assuming it detects your nexus one correctly → select and install the latest 4ext recovery (at the top of the list).
After 4ext has installed, it will have placed a recovery image on your SD card - find it (its called recover.img) and it should be located in SD/Download/4EXT_Recovery_Touch/ folder. Copy this to your computer in case something goes wrong later and you need to re-flash the recovery image!
After installation of the 4ext recovery turn off your phone and boot into recovery by turning off your phone, turning it on again while holding the trackball down. This will boot into the bootloader, then press the power button once, use Volume Down to select "recovery" and press the trackball to select. Alternatively you can use the command prompt:
Code:
adb reboot recovery
Your phone should now boot into the 4ext recovery menu. Before moving on make sure you have any important stuff backed up because you are about to erase your entire SD card! Select "tools" →“partition sd card” → “remove all partitions and start from scratch.” Then for the 1st partition select “1024″ for a 1GB partition (this will be where ICS will be able to put your applications & data). Select "skip" for the 2nd partition and for the swap partition. Finally select the system “ext4″.
Step 3 - Copy the Evervolv, SpazeDog, or whatever zip installation file you have chosen to your phone's SD card
Download the ICS or JB zip file above and copy it to the root of your newly formatted SD card.
Step 4 - Installing and using BlackRose to resize the system partition:
Download the BlackRose application and install it on your computer. (Alternatively people have made flash-able partition schemes that you can just flash from your PC - usually links and instructions are provided in the installation rom's thread, Evervolv's here. If you do have access to a computer you can check out this thread).
Make sure your nexus one is attached via USB to your computer.
Open the BlackRose application - it will install and reboot your phone. Then follow along as shown in this video to resize your partitions for a JB ROM.
If you plan to install the ICS rom then use the video above as a guide but use the numbers (sizes) for the different partitions as indicated below.
After BlackRose has installed you will need to restart the application. After it has started up and recognized your device select "apply stock/custom blackrose" by typing in 1 and enter.
Then select "custom blackrose" by typing in 2.
Then type "resize" when prompted.
Now you will need to change the sizes of the system partition to 220 for ICS or 260 for JB.
Change the cache size to 8.
Finally name the new system partition, either "ICS" or "JB" depending on what you plan to install.
Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip.
Step 5 - Install JB or ICS:
Now turn your phone off and boot into recovery as you did in step 2.
4ext will load. Select "wipe/format" → "format all partitions (except sdcard)" and then also "wipe data/factory reset."
Now go back and select "install from sdcard" → "choose zip from sdcard" → and then select the ICS or JB zip you copied to the SD card in step 3.
Now either the ICS/JB installer will load or it will just install in one step. Just follow the prompts to install and enjoy.
Depending on the ROM you chose you may need to install Google apps (see the specific ROM thread for details) and will also likely want to flash an apps-to-SD script as mentioned above so you do not run out of space.
This method worked perfectly for me, hopefully it will work well for you as well. Enjoy.

Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!

diegolm said:
Great work, your guide is amazing!!! I followeed it and ended with an infinite bootanimation , I'm trying to discover what I did wrong :fingers-crossed:, but the guide was superb!
Click to expand...
Click to collapse
I am sorry to hear that. Can you boot into recovery or is that broken as well? If you can boot into ext recovery try selecting "wipe/restore" → "wipe data/factory reset" and then try to install BCM again. I probably should have added that above, I will do that now.
If your recovery is broken but you can get into the bootloader (holding down trackball while starting up), you should be ok. You will probably need to flash Amon_Ra's Recovery using Hboot as was described in the guide from cyanogenmod link above. If there is a way to directly hboot flash 4ext recovery I don't know how to do it. Then you can try installing BCM again from the Amon_Ra's recovery and re-install 4ext after you get everything working.

I tried the Texasice ROM and it worked, but I didn't like it! Later I tried again BCM and It worked! I dont know, maybe I did something wrong... Anyway thanks again for the guide!!

Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2

intel415 said:
Does work the same if using fastboot method? Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I am not sure which part you are referring to, but, yes, a few of the above instructions could be replaced with fastboot commands.

The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2

intel415 said:
The adb commands, instead using adb I can use fastboot commands right. That's what I used to root my n1 kinda familiar with fastboot. Thx
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
I used the adb commands above because you can use adb to reboot directly into recovery (fastboot you can only reboot normally or into the bootloader) and you can also use adb to directly install apk files - fastboot cannot do those two things - it is more for flashing images (recovery, roms, etc). In order for adb to work make sure you have usb debugging enabled: go to "Settings" → "Applications" → "Development" → enable "USB debugging."
Note that adb commands are not required - you can reboot into recovery and install the 4ext manually.
It won't let me post a link right now, but just google "adb commands" to find a list of all the commands you can use.
Hope that helps.

Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2

intel415 said:
Thx. All I need it was to install black rose and partition it. Put zip on SD card wipe and flash. Installation was easier than I thought it would be lol
Also on ur guide you forgot to put 200 for the data part. You only had 220 and 16
Thx again got ics installed on my n1 smoother than cm 7.2
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, its not bad - glad you got it working! ICS has been smoother than cm 7.2 for me as well.
Blackrose didn't ask me about userdata - it just assumed that automatically after putting in 220 system and 16 cache... I'll make note of that in the guide so its clearer. Thanks.

Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.

Look for "recovery.img"
bobbyphoenix said:
Got the issue with not being able to get into recovery after step 4, but I don't have the recovery image to flash. Once the SD card was formatted in step 2 I don't have a download folder. I attached what is in my SD card right now. Help please.
Click to expand...
Click to collapse
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.

c2med said:
Try to find if there is a "recovery.img" anywhere on your SD card, perhaps in the 4ext folder?
If you can't find it, do not worry, you can just go to the first page of this thread, click on the link labeled "follow this guide from Cyanogenmod" and then go to the section on how to download and install Amon_Ra's Recovery. Once you get Amon_Ra's recovery flashed you will be able to install any ROM of your choice.
You can reinstall the 4ext recovery later if you want.
Click to expand...
Click to collapse
OK I'm stuck on what the path name is suppose to be. I tried it every way I can think of. Can you take a look at my screen shot, and tell me where I'm going wrong? The recovery image is on my desktop, so I'm not sure what exactly I should be replacing "path" with. I tried it from the link, and how you have it in your note. You don't have the "/to/" after path as in the CM link.

Well I tried a couple more times, and I can get it to seemingly do it, but it just hangs on this: (see screen shot) I get no error, and if I try to enter recovery on the phone I still get the reboot to the android and triangle with the ! in it.

place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk

And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".

n1newbie said:
place the recovery under the folder which contains fastboot.exe and rename it to recovery.img
now use the command
fastboot flash recovery recovery.img from platform-tools directory
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
tommert38 said:
And right-click this folder while pressing the SHIFT key on your keyboard. Then choose "Open command window here".
Click to expand...
Click to collapse
WOW Thank you both. I spent literally hours yesterday trying to get it to work. Tried your suggestions, and in five minutes it was up and running!
---------- Post added at 12:31 PM ---------- Previous post was at 11:33 AM ----------
I may have spoke too soon. I followed the instructions to the end. Installed the ROM, and rebooted, but now after the X I get the Spazdog splash screen with the big Z in the middle and green dots moving, but it stays there forever. I waited 20 minutes one time. Tried reflashing, but I get the same thing.
---------- Post added at 01:17 PM ---------- Previous post was at 12:31 PM ----------
Just giving an update on progress (in case someone else is in my boat too) Flashed back to stock GB. Reinstalled recovery, and reflashed Spaz. Got past the X, and the splash screen, but now it's stuck on the Android logo that looks like the night rider beam that goes across the word. Been there now for about 10 minutes.

You do have Blackrose, right?

Yep. Installed everything according to OP. I think it may be the partition sizes as I think flashing back to GB messed with them. It says 220 and 10, but after checking some threads, it looks like there is one missing (userdata). I tried flashing a custom GB from here http://forum.xda-developers.com/showthread.php?t=1214543&page=98 and I was able to install everything. Got it up and running, so I'm going to start over for ICS, or do you think I can flash one of these for ICS http://forum.xda-developers.com/showthread.php?t=1637166 , and then just flash the ROM after?

220/10 means that you have 220MB for system and 10MB for cache, everything that's left will be userdata, so it doesn't ask (total is ~436MB, so userdata will be ~206MB in that case).
In HBOOT you can check how large your partitions are, or you could use the FreeSpace app for example. Always make sure your system partition is large enough before flashing a ROM.

"Big" troble with moboot and firmware

Greetings!
If this question was early on this forum please forgive for double it, because my search gives no result.
Today wanted update my old CM7 for a new CM9, because last update was about 2 years ago. So I went to thematic forums and remind myself how to do this, i guided this and some of this
So I download palm drivers, then moboot 0.3.5, then ACMEInstaller3 and ACMEUninstaller and last CM9 (cm-9-20130714-NIGHTLY-tenderloin.zip )
Then,I uninstall old android with ACMEUninstaller (operation was succes) after I login In webOS and use Full erase.
After Install moboot and CM9, BUT I forget to add a Clockworckmod.zip in cminstall folder. So I use an ACMEUninstaller, but nothing happened, all uninstall process was very fast (about 2-5 sec, and table goes to reboot)
So I load in CM9, add clockworcmode.zip in cminstall directory, reboot in Recovery mode to use ACMEInstaller3 with Clockworckmode.
But again - nothing only 4menu was available . So I load webOS and use Secure Erase.
After reboot in moboot menu I was not able to load webOS.And I decide to use webOSDoctor (3.0.5) then check tablet and start to instal some files and stuck at 4% then touchpad reboot.
When table powered on moboot loaded again... I was surprised... when I use load webOS option - table goes in reboot and doctor don't answered, then I choose Recovery, doctor progress bar down to 1% and all starts over and over.
I decided to close doctor with task manager.
CM9 loads every 1 of 3 try's (when I choose load CyanogenMod)so I used it to update/renew files incminstall I was confuseed...
Then I uninstall from my PC palm/webdoctor/acme and install older or this same programs again, but it reinstalling wasn't helps.Older versions of moboot3.4/acme2/CM was useless.
I try to folow this instruction (Factory condition restoration / Downgrade to webOS 3.0.0), after step 5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage )
When table start a reboot process it was failed, because of moboot that load after table powered.
So at this moment I have a working moboot without clockwockmod, and recover mode.
I don't know what to do, please help some advice. Iam in desper

Even without moboot's "boot webOS recovery" option working [which I have never had the misfortune of experiencing], you can still enter that mode by powering on the TP with the Volume Up button held down.
If that doesn't work, try using tpdebrick... but follow the instructions exactly, and if you have ANY questions - do not proceed. Ask on this forum post.

castrwilliam said:
Even without moboot's "boot webOS recovery" option working [which I have never had the misfortune of experiencing], you can still enter that mode by powering on the TP with the Volume Up button held down.
If that doesn't work, try using tpdebrick... but follow the instructions exactly, and if you have ANY questions - do not proceed. Ask on this forum post.
Click to expand...
Click to collapse
Yeah, i still can load webos recovery mode, but all what i use in that mode is not helping, webosdoctor and other commands like ACME. Just when touchap restart, he still load that same bugged moboot menu

FreeDooMF1 said:
Greetings!
If this question was early on this forum please forgive for double it, because my search gives no result.
Today wanted update my old CM7 for a new CM9, because last update was about 2 years ago. So I went to thematic forums and remind myself how to do this, i guided this and some of this
So I download palm drivers, then moboot 0.3.5, then ACMEInstaller3 and ACMEUninstaller and last CM9 (cm-9-20130714-NIGHTLY-tenderloin.zip )
Then,I uninstall old android with ACMEUninstaller (operation was succes) after I login In webOS and use Full erase.
After Install moboot and CM9, BUT I forget to add a Clockworckmod.zip in cminstall folder. So I use an ACMEUninstaller, but nothing happened, all uninstall process was very fast (about 2-5 sec, and table goes to reboot)
So I load in CM9, add clockworcmode.zip in cminstall directory, reboot in Recovery mode to use ACMEInstaller3 with Clockworckmode.
But again - nothing only 4menu was available . So I load webOS and use Secure Erase.
After reboot in moboot menu I was not able to load webOS.And I decide to use webOSDoctor (3.0.5) then check tablet and start to instal some files and stuck at 4% then touchpad reboot.
When table powered on moboot loaded again... I was surprised... when I use load webOS option - table goes in reboot and doctor don't answered, then I choose Recovery, doctor progress bar down to 1% and all starts over and over.
I decided to close doctor with task manager.
CM9 loads every 1 of 3 try's (when I choose load CyanogenMod)so I used it to update/renew files incminstall I was confuseed...
Then I uninstall from my PC palm/webdoctor/acme and install older or this same programs again, but it reinstalling wasn't helps.Older versions of moboot3.4/acme2/CM was useless.
I try to folow this instruction (Factory condition restoration / Downgrade to webOS 3.0.0), after step 5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage )
When table start a reboot process it was failed, because of moboot that load after table powered.
So at this moment I have a working moboot without clockwockmod, and recover mode.
I don't know what to do, please help some advice. Iam in desper
Click to expand...
Click to collapse
You should probably stick with the most recent and updated Install guide. Did you happen to read this note?
3)Note: When using the acmeinstaller2/3, the Rom and Gapps files must begin with update-xxxx. If update- is not present the Rom and gapps may not install. You can add update- to the Rom & Gapps file names if it is missing.
I noticed you didn't use gapps, are you sure you read my guide?

RolandDeschain79 said:
You should probably stick with the most recent and updated Install guide. Did you happen to read this note?
3)Note: When using the acmeinstaller2/3, the Rom and Gapps files must begin with update-xxxx. If update- is not present the Rom and gapps may not install. You can add update- to the Rom & Gapps file names if it is missing.
I noticed you didn't use gapps, are you sure you read my guide?
Click to expand...
Click to collapse
yes i forget about gapps at all. I didnt add it in cminstall folder on my tablet when i use acminstaller...
so what to do now? how erase all data and load webos again?

Problem solved
FreeDooMF1 said:
ok, topic can be close.
it's all about that i inattentive fool.
I dont reneme install files in cminstall folder that i added on table, and because of it ACME dont work right.
now all ok, i have full functional moboot and newest CM9 with play market.
Click to expand...
Click to collapse
Glad to hear you got it all working (@ RootzWiki), you just needed the right info to get started Time to enjoy all that Android goodness on your TouchPad! Don't forget to make a Nandroid backup and transfer it to your computer. If anything goes wrong in the future, you will be fully prepared