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.
Related
I followed the guide over at cyanogenmod for installing ICS. I had all of the files in the cminstall folder, moboot, recovery etc. I successfully installed CM9 but the recovery did not install. Rest of the files are no longer present in the cminstall folder, must have been deleted? But the recovery file is still there. So how do I install recovery so I can flash the gapps and so forth.
Thanks
This happened to me a couple days ago, what i did was the following:
1. place update-cwm_tenderloin-1012.zip in the cminstall folder in your touchpad. get another copy of the zip for the next step
2. Your going to run CWM through novacom, so unzip the update-cwm_tenderloin-1012.zip file wherever your novacom file is.
3. boot the Webos recovery
4.connect to pc, and run "novacom boot mem:// < uImage.ClockworkMod" (remove "") this should take you to CWM
5. goto install from zip, go to the cminstall folder and install the update-cwm_tenderloin-1012.zip . Reboot.
6. It should be there now... well it was for me
Thanks a lot, everything worked out perfectly
I had the same problem after following the guide on webOS Nation . I finally figured out what i did wrong and here is what i posted on there site.
The download link for ClockworkMod Recovery at CyanogenMod is WRONG use the mirror as you need update-cwm_tenderloin-1012.zip NOT recovery-clockwork-tenderloin-1012.zip if you use the wrong one as I did recovery will not be installed and you will probably spend hours or days as i did trying to figure why recovery is not in you boot menu . That said and done i LOVE the Android option and your easy install guide.
I hope this will help your members who may have had the same problem .
Many Thanks to the starter of this thread who helped me get my brain into gear.
Great Forum
sstar said:
I had the same problem after following the guide on webOS Nation . I finally figured out what i did wrong and here is what i posted on there site.
The download link for ClockworkMod Recovery at CyanogenMod is WRONG use the mirror as you need update-cwm_tenderloin-1012.zip NOT recovery-clockwork-tenderloin-1012.zip if you use the wrong one as I did recovery will not be installed and you will probably spend hours or days as i did trying to figure why recovery is not in you boot menu . That said and done i LOVE the Android option and your easy install guide.
I hope this will help your members who may have had the same problem .
Many Thanks to the starter of this thread who helped me get my brain into gear.
Great Forum
Click to expand...
Click to collapse
I second this. I had this happen to me. Just get the right zip file and replace the old one on your computer then run ACMEinstaller again the same way you did the first time. The ClockworkMod zip should be the only file in that folder this time though.
CWM still not installing?
i have tried the correct file, and used acmeinstaller. I current have TWRP, but it is not flashing nightlies.. how do i install CWMRecovery now? any ideas?
https://www.box.com/shared/479acdb6ef9c99fc7b92
You guys ROCK!!!
After following, re-following, re-following, etc 8-10 different tutorials with virtually the same exact instructions, I finally found a thread that hit the nail on the head.... I successfully installed Alpha 2, and was able to access moboot to switch back and forth with WebOS, but despite my efforts, I simply couldn't get CWM Recovery or CM9 nightly installed.... Thank you sooooooooo much for helping me FINALLY get CWM Recovery 5.0.2.6 and 20120816 nightly successfully installed on my Touchpad!!!
NEVERMIND -- Fixed it.
Follow the instructions in here exactly and you won't have any issues. Make sure you're using the correct CWM zip file. (i.e. the one that starts with "update", download it here).
Also, make sure you have the updated, correct novacom file in Palm, Inc. See this helpful description and download link.
Also, as others have said, you can simply place ACMEInstaller2 in your Palm, Inc directory, and flash like you would normally by typing novacom boot mem:// < ACMEInstaller2
Spot on. Thanks.
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!
Hey guys, I am here because I was incredibly stupid. I have no idea how this could have happened.
I tried updating the TWRP to the latest version with Goo manager, unfortunatly, it deleted my old one without flashing a new one. The ADB drivers didn't really work, so I tried flashing the twrp.img via the app "flashify". Problem is, I flashed the .img as a boot image and not as a recovery image, no idea how I could overlook that.
So now my Touchpad only boots into the webOS download mode and shows an error if I try to boot regularly (obviously). palm.com/ROM it says.
So my question is, how do I flash the correct boot image again? Last time I have flashed the boot image of the touchpad was when Ice cream sandwich wasn't even announced, I have no idea how to fix my mums tablet.
So it would be so great if you could help me, I'm feeling so stupid and quite helpless. Thanks so much
Axe Homeless said:
Hey guys, I am here because I was incredibly stupid. I have no idea how this could have happened.
I tried updating the TWRP to the latest version with Goo manager, unfortunatly, it deleted my old one without flashing a new one. The ADB drivers didn't really work, so I tried flashing the twrp.img via the app "flashify". Problem is, I flashed the .img as a boot image and not as a recovery image, no idea how I could overlook that.
So now my Touchpad only boots into the webOS download mode and shows an error if I try to boot regularly (obviously). palm.com/ROM it says.
So my question is, how do I flash the correct boot image again? Last time I have flashed the boot image of the touchpad was when Ice cream sandwich wasn't even announced, I have no idea how to fix my mums tablet.
So it would be so great if you could help me, I'm feeling so stupid and quite helpless. Thanks so much
Click to expand...
Click to collapse
You will want to run acmeuninstaller
followed by WebOS Doctor
and then moboot, CWM, CM10.2
some help with fixing a situation like yours is here http://forum.xda-developers.com/showthread.php?t=1426244
latest files can be found here: invisiblek.org/tenderloin/
Holy ****, so I do have to uninstall everything, delete the partitions and then repartition and reinstall everything? Isn't there a way just to flash moboot again or something?
Axe Homeless said:
Holy ****, so I do have to uninstall everything, delete the partitions and then repartition and reinstall everything? Isn't there a way just to flash moboot again or something?
Click to expand...
Click to collapse
to install moboot you need to get a copy of it on the touchpad in the cminstall folder and then run
novacom boot mem:// < ACMEInstaller3
to get moboot there you need to see if you can boot into CWM.
Get a copy of update-CWM6_tenderloin-20121215.zip and extract uImage.ClockworkMod
on your Windows PC in command window:
cd C:\Program Files\Palm, Inc
novacom boot mem:// < uImage.ClockworkMod
go to mounts and storage
mount /boot
mount /sdcard
mount USB storage
create a directory cminstall
you can copy CWM, moboot and then try ACMEinstaller3
E:
Well, I can get into CWM, but I can't mount anything, error mounting /boot and /everything else, and it doesn't do anything when I'm mounting USB storage. damn. Any other tipps? I'm really grateful for your help, but I would rather first exhaust the options before killing everthing and then rebuilding it.
Axe Homeless said:
E:
Well, I can get into CWM, but I can't mount anything, error mounting /boot and /everything else, and it doesn't do anything when I'm mounting USB storage. damn. Any other tipps? I'm really grateful for your help, but I would rather first exhaust the options before killing everthing and then rebuilding it.
Click to expand...
Click to collapse
If you are getting mount errors then my guess is your partitions are messed up and should rebuild from scratch. Only other think I would try is just acmeuninstaller and see if you can get webos to boot after that.
Disclaimer: I'm relatively new to the realm of modding the the kindle. I have a 2012 7" hd. I rooted it and loaded a 2nd bootloader and recovery via various tutorials. I attempted to to load a rom (lolipop 5.1 and corresponding gapps). The process seemed to go fine and when it booted into android the initial setup screens appeared (connect to wifi etc); but then I got a message that the setup wizard had failed. I tried "skipping" screens etc and regardless of what I did I couldn't get past that screen. I clearly either did something wrong or didn't have a good rom file. I was an idiot and didn't create a backup before flashing the new rom. So I mounted it in recovery and loaded a factory image that way and flashed back to norm. My intention was to start things over. I rooted again, went through the whole process; however, I'm seeing a weird phenomenon. When I am in windows (or ES explorer for that matter) and access the files on the sd card partition...I can load files onto there (for flashing in recovery etc); however, once I am actually in recovery and go to "install" the partition that I view in recovery is the files I had from the very first flash. I can create new files in windows or ES explorer and everything works as expected....but once in recovery, none of those folders are present...and the only zip files that are available to "install" are the ones I used the first time that didn't work. I'm clearly looking at some other partition or image in recovery than I am in windows. I have cleared cache and everything I can think of (again I'm a complete amateur). Does anyone have a suggestion of what I am doing wrong or how to resolve? Thanks in advance.
Cranky
The issue with your first problem was that it could have been a bad gapps, in the future try different gapps if you see weird problems like that, to your second problem, when flashing lollipop on a device that had ICS it'll change the directory of the SDcard, no biggie though, just search in recovery data/media/legacy or data/media/0 it should be in one of those that your files are in.
Sent from my Nexus 9 using Tapatalk
Try this.
Try to send files over using adb whilst in recovery. If you do not know how then watch this youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
golfnut22 said:
Yes, I know, I should have backed up...but did not. So, this TP, I cannot go into usb mode or recovery mode. For some reason, I get a weird 4 block pattern. Before I messed up, I was able to use TWRP 2.8.3 to load different gapps and roms in the ttinstall file by mounting. Well, I decided Lollipop was not quite what I wanted and wanted to go back to KitKat. Anyway, in my zeal of trying to fix what may be causing the recovery mode issue, I wiped everything and formatted everything...including the ttinstall file. I can still boot to twrp 2.8.3, but honestly, the sequence of invents I have tried to create a new folder called ttinstall and place in there rom and gapps, it will not load. In fact, I'm not sure where the twrp file is located. So, I would appreciate it if someone has detailed instructions beginning with opening twrp 2.8.3. What sd card to use and folder to create where, and so forth. I can mount the TP and load files via the pc, but I don't quite know where they actually go on the tablet. The device shows up as 1gb on the pc and this is a 32gb TP so I know I messed it up. I was spoiled by the TPToolbox when I was able to use the usb recovery mode and make all changes there.
Any help would be appreciated. I did do a search, but I have not found clear instructions for me. I even saw a youtube, but again, it was more confusing. Thanks.
Click to expand...
Click to collapse
Edit: Well, that was easy. I just set up the ttinstall folder, then copied the rom and gapps zip files there, unmounted, then selected install from the twrp menu (rom first then gapps), rebooted and presto...running again.