Database Develop

Stuck booting into recovery

SO i was running nook color version 1.1.0 and i used the autonooter to get clockwork installed. I then tried to use the monster rootpack to install phiremod but after it says install is complete i rebooted but now every time i reboot it goes directly to clockwork and i cant get it to boot up normally. is there anything i can do besides a restore to stock to install phiremod/cm7 or exit recovery? BTW i did remove the monster sd card so thats not the reason its booting that way....

When booted to CWR, use adb:
adb shell
Check that rom is mounted with:
mount
You should see /rom somewhere in the returned result.
If it's mounted, do:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
If not:
mkdir /rom
mount /dev/block/mmcblk0p2 /rom
Then use previous command.
If that doesn't help, you can always flash my cwr remover .zip, found on my nook color restore to stock thread.
Sent from my HTC Desire using XDA App

thanks im going to try that right now.

So i am trying to run adb but it says device not found and i cant figure out how to get the device to mount

I had the same thing happen. In recovery, install the zip file in this post to remove recovery and keep it rooted. You will then be able to reboot normally.
http://forum.xda-developers.com/showthread.php?t=914690
I read that it does that with autonooter 3.0. What you need to do is reboot normally after flashing recovery (don't reboot into recovery immediately after flashing). Afterwards you can reboot into recovery.

Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.

krisslake said:
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
Click to expand...
Click to collapse
Not really sure what you are saying was your problem. But I have a lot of solutions to booting problems in my nook color tips thread linked in my signature. See items A8 and A12. And there is my partition repair thread.
Sent from my BNTV400 using Tapatalk

[Q] Warning sign with exclamation mark on boot

Hi,
I installed CM7 months ago, updated to WebOS 3.0.4, re-installed moboot via ACMEInstaller and am now running XRONified 2.9.1 odex and I was a happy geek until now.
Yesterday I booted into WebOS (as every day to video chat with my gf) and this morning I rebooted the device to load Android (again, as every day).
Then after shutting down and coming up again instead of loading moboot and booting into Android it showed me a nice warning sign with an exclamation mark and the text "www . palm . com / ROM".
Following that link on my computer leads to the Meta Doctor page so I think something got messed up mysteriously.
A few days ago WebOS showed up a notification for the WebOS 3.0.5 update which I didn't install.
I guess maybe it auto-updated over night and something went wrong ... ?!
Whatever, my question is:
Is it safe to simply doctor the device or do I first have to uninstall Android via ACMEUninstaller because of the partitions or such (read about some partition problems with the doctor ...) or do I need to do other preparations for doctoring?
EDIT
For a way to fix this without doctoring see post 5

real_sl4cker said:
Hi,
I installed CM7 months ago, updated to WebOS 3.0.4, re-installed moboot via ACMEInstaller and am now running XRONified 2.9.1 odex and I was a happy geek until now.
Yesterday I booted into WebOS (as every day to video chat with my gf) and this morning I rebooted the device to load Android (again, as every day).
Then after shutting down and coming up again instead of loading moboot and booting into Android it showed me a nice warning sign with an exclamation mark and the text "www . palm . com / ROM".
Following that link on my computer leads to the Meta Doctor page so I think something got messed up mysteriously.
A few days ago WebOS showed up a notification for the WebOS 3.0.5 update which I didn't install.
I guess maybe it auto-updated over night and something went wrong ... ?!
Whatever, my question is:
Is it safe to simply doctor the device or do I first have to uninstall Android via ACMEUninstaller because of the partitions or such (read about some partition problems with the doctor ...) or do I need to do other preparations for doctoring?
Click to expand...
Click to collapse
Firstly try a reinstall of moboot and recover your android settings and apps. I use backup everything with everything "ticked".
Then docter and start a fresh total reinstall of everything.
Boot into Android.
Restore your apps first, check they all run OK and then restore your settings.

Would love to re-install moboot but I can't boot at all, neither into WebOS nor into Android, no sign of moboot, just the mentioned warning sign when turning the device on.
So I don't need to uninstall Android (remove the android partitions) before using WebOS Doctor?

real_sl4cker said:
Would love to re-install moboot but I can't boot at all, neither into WebOS nor into Android, no sign of moboot, just the mentioned warning sign when turning the device on.
So I don't need to uninstall Android (remove the android partitions) before using WebOS Doctor?
Click to expand...
Click to collapse
I had to doctor my TP also. I didn't remove android (the files were still there). After doctoring, I reinstalled moboot using acmeinstall and restored a backup with cwm. Everything is working fine (so far).

Fixed it!
For reference:
Follow the steps from RootzWiki:
Still nothing? Or maybe you have a dreaded triangle-with-an-exclamation-mark on the screen?
Another "emergency" idea (for advanced folks only) is to boot ClockWorkMod Recovery *directly* from your computer via USB cable rather than from the TouchPad's internal storage. To try this, find an "update...zip" file that contains ClockWorkMod. Inside this zip file is a file called something like "uImage.ClockWorkMod". Extract/unzip that file to your computer, then use novacom (which you used with ACME installer) to "inject" ClockworkMod into your TouchPad.
This process should be familiar to you-- very similar in fact to using ACME Installer. It's done by starting the tablet with the up-volume key held down. When you see the USB icon, connect your computer to the TouchPad via USB, then, in a Terminal, navigate on your computer to where the uImage.ClockWorkmod file is, and type:
novacom boot mem:// < uImage.ClockworkMod
Assuming everything went well and ClockworkMod did start up, you may now use CWM to re-install "update...zip" files, restore from backups, format partitions, or reset everything to factory settings.
Click to expand...
Click to collapse
Then ...
In CWM mount USB storage
If not exist create "cminstall" dir and put the moboot file into it from your computer
Reboot System and hold VOL UP again to get into recovery mode
Launch ACMEInstaller and let it install moboot
I'm now able to boot into WebOS via moboot but Android ends up in a boot loop so I will use ACMEUninstaller and setup everything again (just to be sure) ...
Sure reflashing and clearing caches will do as well but it's not bad to start fresh (see EDIT 2 for confirmation)
EDIT
Seems a failed update for UberKernel causes the problem. When trying to update UberKernel via Preware (I'm still on WebOS 3.0.4) it says something like "only xxxx of xxxx mb" extracted. When I reboot after that moboot is gone and the triangle is back and I have to repeat the process.
EDIT 2
Just for the sake of completeness (for those who don't want to start fresh): Clearing Cache and Dalvik cache and re-flashing XRONified 2.9.1 again solved the boot loop. All Data, Apps and stuff are still there. I will do a Titanium backup now, uninstall via ACMEUninstaller, Wipe the whole thing, setup WebOS and re-install Android. Spring Cleaning

chicle_11 said:
I had to doctor my TP also. I didn't remove android (the files were still there). After doctoring, I reinstalled moboot using acmeinstall and restored a backup with cwm. Everything is working fine (so far).
Click to expand...
Click to collapse
Maybe it's version-related. Which version of WebOS-Doctor did you use?

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

TWRP Install renames to CWM - I want both

I downloaded the new 2.1 TWRP and installed it using CWM I discovered that on the moboot menu it still reads CWM but boots TWRP. I would like to keep both on the tablet for now. Any ideas on how to install CWM and have both TWRP and CWM show up on the mobbot menu? Thanks.

buffalo_guy said:
I downloaded the new 2.1 TWRP and installed it using CWM I discovered that on the moboot menu it still reads CWM but boots TWRP. I would like to keep both on the tablet for now. Any ideas on how to install CWM and have both TWRP and CWM show up on the mobbot menu? Thanks.
Click to expand...
Click to collapse
Fastboot CWM again.
I did it last night and now I am stuck with both. I wanted only CWM but I can't get rid of TWRP. When I hit reboot to recovery, I go to TWRP but I can choose CWM from Moboot.
Sent from my Galaxy Nexus using xda app-developers app

Solved with another method
SOLVED: I since have learned that TWRP replaces CWM and as a convenience to the user and renames TWRP so it appears as CWM for purposes of going into recovery. There were a number of solutions to add back CWM. The one I used requires a file manager with root access. I extracted the CWM image from the zip file and copied it into the boot directory and renamed it uimage.CWM2. I reset the permissions to match the the other moboot images found in boot. Once the tablet is restarted moboot inventories the images found in boot and adds them to the menu. For the time being I now have both TWRP and CWM. The only caution is to make sure you have enough room in the boot directory. You can also remove entries from the moboot menu by deleting image files. Proceed with caution and always backup before proceeding.

"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