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?
Related
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.
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!
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
I first installed Schizoid 2.10_jb-22Jul2013 and then reverted to skz_tenderloin-2.10_jb_4.2.2-29JUN2013-130837.zip. This is probably my error in installing so I can't blame the ROM. This screwup resulted in wiping out all other boot options so that I could only reboot to Cyangen Mod. Reboot to recovery or bootloader from Schizoid all resulted in a boot back to Schizoid. I've tried using GooManager and Rom Manager but it appears that they cannot get Superuser authority.
SYMPTOMS:
a) In Terminal Emulator, the 'su' command gets '/system/bin/sh: su not found'.
b) GooManager issues 'Preparing to Flash' message but never does the command.
c) Rom Manager issues "You must root your phone fo ROM Manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su" Use Google Search on you computer to find instructions to root your phone.'
d) Tried installing CWM recovery from ROM Manager but get 'Unspported Device'.
d) I tried pressing down both the Power and Home buttons but I get 'Please release keys'.
While it appears that the ROM works OK for most apps and I have a USB device driver that works, I'd like to be able to backup and update when improvements are made.
SOLUTION:
I first tried holding the HOME and POWER buttons but that did nothing. I then tried holding down both the Power and Volume Up buttons at startup. This brings up the USB logo on the screen. I have it tethered to my computer running Windows 7. This failed to install the Palm device driver. I had to download WebOS Docter 3.0.5 to go back to Web OS stock.
The following link walks you through the re-install process.
http://theunlockr.com/2011/10/18/how...e-hp-touchpad/
You need an account with HP WebOS. Here's the link for the download of WebOS.
http://ws.hpwebos.com/webosdoctor/webosdoctor.htm?
The process took over an hour but I was able to boot to the stock HP WebOS. I did not lose my data files but it wiped out all my boot-loader and Android entries.
After the return to stock, I followed the very detailed instructions to install CWM recovery (Great stuff!):
http://forum.xda-developers.com/wiki/HP_Touchpad
The only thing different I would suggest is to download ACMEInstaller3 instead of ACMEInstaller2. I had a problem later that caused me to repeat the process again which I think is a result of the way ACMEInstaller2 divides the partitions.
My process came up with CWM recovery, WEB OS, and WEB OS recovery on the boot menu. From here I installed Cyanagenmod 9. After booting to CM 9, I installed GooManager and the latest TWRP. A boot to TWRP allowed a restore of my good backup and a return to my setup prior to the screwup and brought me back to my regular setup.
Get USB sign with Power and Volume UP
See main text above.
Re-install WebOS
See main text above.
Restoring Multiboot with CM9
See main text above.
As the Title says,
I installed a new ROM, that is Evervolv AOSP 4.3, most apps didn't work(eg: Subway Surf), I think because GApps is missing. I decided to restore from CWM Backup
Ok, I rebooted, selected ClockworkMod in Moboot, Gone into "backup and restore", selected restore and gone into the latest backup.
I plugged in the charger and left it for 10-15 minutes. I went to take a cup of coffee. When I came and see what has happened it showed
"Error: Unable to restore Boot".
Ok, I used novacom to boot into CWM by uImage.ClockworkMod
It showed some annoying errors like Error Unable to muount cache, Unable to open /blah blah.
Now I decided only with webOS Doctor.
But I should not get removed the webOS apps. Because, I downloaded those apps in U.S. Palm HP App Catalog.
Now I am in India. So i can't get those.
Please Help ME:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
superboy123 said:
As the Title says,
I installed a new ROM, that is Evervolv AOSP 4.3, most apps didn't work(eg: Subway Surf), I think because GApps is missing. I decided to restore from CWM Backup
Ok, I rebooted, selected ClockworkMod in Moboot, Gone into "backup and restore", selected restore and gone into the latest backup.
I plugged in the charger and left it for 10-15 minutes. I went to take a cup of coffee. When I came and see what has happened it showed
"Error: Unable to restore Boot".
Ok, I used novacom to boot into CWM by uImage.ClockworkMod
It showed some annoying errors like Error Unable to muount cache, Unable to open /blah blah.
Now I decided only with webOS Doctor.
But I should not get removed the webOS apps. Because, I downloaded those apps in U.S. Palm HP App Catalog.
Now I am in India. So i can't get those.
Please Help ME:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
this thread should get you fixed up.
http://rootzwiki.com/topic/38786-tpdebrick-v004/
Your situation sounds eminently debrickable. Best of luck.