I installed the latest CM6 nightly, but I kept getting bootloops. I figured I'd restore my nandroid, but I needed to flash ClockworkMod recovery to get it to work. I went in ROM Manager, told it to flash the recovery, got confirmation that it worked, but when I reboot it only goes to fastboot. I tried flashing AmonRA again, but it doesn't stick either. Please help me remedy this!
Edit: I was finally able to restore using ROM Manager. I just had to delete the /system one and restore it using Titanium Backup before it would flash. Delete this.
Related
Hi everyone. I'm having some problems with my Recovery which I can't seem to figure out:
I tried to mod my phone with CM6.1 the other day using ROM Manager. ROM downloaded and started to install, no problems. When it tried to boot up again, it got stuck in a loop at the CM loading screen. When I tried to reboot in to Clockword Mod Recovery, all I got was a picture of a phone with a triangle (can't remember which colour - think it was green). Eventually I realised that was a stock recovery and managed to get my phone restored to my backup but I can't seem to get my recovery to go to anything but the stock one. Rom Manager reports Clockwork Recovery reports ClockworkMod 2.5.0.7 installed and I've tried using Rom Manager, Android Commander and UnrEVOked to flash ClockworkMod and Amon-Ra and nothing works - I'm still at the built-in recovery.
Now, If I boot in to recovery, I get the red triangle and a message on screen stating "E:Can't open /cache/recovery/command".
If I do use the built-in recovery to flash ClockworkMod as an update.zip, ClockworkMod launches but when I reboot, it's gone again and I'm back to stock.
Any ideas?
Thank you!
"Android Commander and UnrEVOked to flash ClockworkMod and Amon-Ra and nothing works" make sure youre trying to flash a .img file
"Clockwork Recovery reports ClockworkMod 2.5.0.7 installed" that because the recovery (.zip) is saved on the SDCARD. When booting Recovery from ROM Manager, youre fake-flashing the file (.zip)
"If I do use the built-in recovery to flash ClockworkMod as an update.zip, ClockworkMod launches but when I reboot, it's gone again and I'm back to stock." thats fake-flashing
what HBOOT are you on??
EDIT: You should S-OFF your Desire "http://alpharev.nl/".
WARNING: When using S-OFF your flashing a custom HBOOT. If that goes wrong, it may brick your Desire. If you use S-OFF, then you can flash a permanent recovery using fastboot
Thanks Chris. Any idea why it would have reverted though? I used to have a permanent version of ClockworkMod until the other week
Edit: HBOOT just says 0.80.0000 and has 3 androids on skateboards
Sent from my HTC Desire using XDA App
Go back to stock, download the original ruu for you phone. After that try rooting again.
Rats - had a feeling that may be the answer. Think I'll be able to restore a backup?
Sent from my HTC Desire using XDA App
I fake-flash all the time. I once messed up a ROM's installation and got stuck because it messed up the recovery too.
The loop startup is probably caused by older cache from your previous ROM. Just boot up recovery again, clear cache and restore factory settings and then flash your CM again. Should do the trick.
Chris016 said:
what HBOOT are you on??
EDIT: You should S-OFF your Desire "http://alpharev.nl/".
WARNING: When using S-OFF your flashing a custom HBOOT. If that goes wrong, it may brick your Desire. If you use S-OFF, then you can flash a permanent recovery using fastboot
Click to expand...
Click to collapse
Flashed my HBOOT with AlphaRev - those guys are brilliant, coding that!
Thank you for your help!
Bingo!
Think I've nailed it now!
I used Fastboot Commander [v.1.0] to flash Amon-RA which took and stayed!
To confirm: I installed AlphaRev bootloader to S-OFF then Fastboot Commander to flash Amon-RA. Hopefully, I'll now be able to flash Clockwork Recovery again (as I use Rom Manager) and be back up and running!
Think I may skip CM6.1...
I've been having trouble with ROM installs and Nandroid backup / restores since I used ROM Manager to update recovery from ClockworkMod Recovery v2.5.0.5 to v2.5.1.2.
I would like to revert back to v2.5.0.5. I have the recovery-clockwork-2.5.0.5-inc.img and recovery-clockwork-2.5.0.5-inc.zip. If I run the .zip file from the 2.5.1.2 recovery, it temporarily shows "ClockworkMod Recovery v2.5.0.5" as the running recovery, but slips back to 2.5.1.2 upon reboot.
At this point my ROM / backups aren't booting. I can get to the adb shell while in v2.5.1.2 recovery. Is there a way to flash back to ClockworkMod Recovery v2.5.0.5 from adb shell?
Thanks,
Dan
I renamed recovery-clockwork-2.5.0.5-inc.zip to update.zip and put it on the root of my SD card. I rebooted into hboot and it ran the update.zip, then booted into ClockworkMod Recovery v2.5.0.5. Unfortunately when I rebooted into recovery again, it was back to v2.5.1.2.
Someone has to have done this before... At this point my phone is dead to me, so if anyone has any suggestions, I'm anxious to hear them.
Place this PB31IMG.zip on the root of your sd card and install through HBOOT.
Being an older version, it may or may not work, but is worth a shot.
"No image or wrong image" when trying to boot that from HBOOT. It won't install it.
Xylite said:
"No image or wrong image" when trying to boot that from HBOOT. It won't install it.
Click to expand...
Click to collapse
Make sure your sd card is formatted to FAT32 rather than FAT and that your computer didn't inadvertently rename the file to PB31IMG.zip.zip or pb31img.zip.
Thanks for the quick response. The file is named PB31IMG.zip (capitalized properly, no extra .zip extension). The SD card is FAT32. I was able to flash a update.zip this morning using the same setup. Would it be advisable to rename the PB31IMG.zip to update.zip just to get it to flash?
What is this PB31IMG.zip? Is it back to the stock RUU or is it the ClockworkMod 2.5.0.5 Recovery?
It's CWM, downloaded straight from Koush's site and inserted into a zip by me.
Another alternative, if you are able to do so, is to use Unrevoked to install the recovery image.
I thought of the same thing this morning. I'll have to try to get a ROM to boot to use Unrevoked, correct?
I tried running Unrevoked while my phone was in recovery, but the Unrevoked 3.2 tool didn't like that too much.
My problem is that after installing a new ROM or restoring a Nandroid backup, the white HTC Incredible splash screen appears indefinitely. It doesn't seem to hand off into the ROM properly. I have gotten a ROM to boot all the way to the desktop before but it bootloops shortly thereafter.
I guess my path forward at this point is to try to get a ROM to boot to the homescreen, then run Unrevoked. Can I run Unrevoked on an already rooted ROM?
unrEVOked tool reports that it should not be run on any device that is not in perfect working order or it risks permanent damage.
PLEASE!!! Anyone that knows how I can flash back to a prior version of recovery please help.
Maybe I'm doing something else wrong... The only ROM I can successfully flash is Incredibly Re-engineered. Unfortunately this ROM has a bootloop issue after some time (known issue, see the development thread and lots of people have the same problem). To install a different ROM, I'm downloading via ROM Manager (SkyRaider or Virtuous for instance), clearing data and cache in recovery (with system and data mounted), running ROM .zip selected from SD card. After the ROM successfully installs and I choose to reboot, my phone sits on the white HTC Incredible splash screen indefinitely. Is there something else I'm missing to flash from Incredibly Re-engineered to another ROM?
Beware of ClockworkMod Recovery 2.5.1.2 on your Incredible!
Xylite said:
unrEVOked tool reports that it should not be run on any device that is not in perfect working order or it risks permanent damage.
PLEASE!!! Anyone that knows how I can flash back to a prior version of recovery please help.
Maybe I'm doing something else wrong... The only ROM I can successfully flash is Incredibly Re-engineered. Unfortunately this ROM has a bootloop issue after some time (known issue, see the development thread and lots of people have the same problem). To install a different ROM, I'm downloading via ROM Manager (SkyRaider or Virtuous for instance), clearing data and cache in recovery (with system and data mounted), running ROM .zip selected from SD card. After the ROM successfully installs and I choose to reboot, my phone sits on the white HTC Incredible splash screen indefinitely. Is there something else I'm missing to flash from Incredibly Re-engineered to another ROM?
Click to expand...
Click to collapse
Well, I've found some success. I couldn't figure out how to install an old version of CWM Recovery outright, but ROM Manager was able to successfully install the "alternate" recovery RA_GNM. I used this recovery to flash SkyRaider 3.5. Luckily, SkyRaider 3.5 comes with ROM Manager v2.5.0.7, which thinks ClockworkMod 2.5.0.5 is the most recent recovery. So I was then able to flash back to CWM 2.5.0.5 using ROM Manager before it realized that 2.5.1.2 was the most recent version.
To summarize, I think my phone is back to normal.
PLEASE tread lightly when upgrading your Incredible to 2.5.1.2!
Okay so here's what happened:
I saw S-Off was released.
I decided to install the latest nightly before applying it. I was intoxicated.
I forgot to wipe data/factory reset. I DID NANROID, HOWEVER. I flashed the rom and gapps.
When I rebooted, it sits at the myTouch 3g Slide splash page.
At this page I have access to ADB on my pc, but for some reason can't write to any of the folders I tried.
Holding back while I reboot brings me too fastboot.
Fastboot will not flash the current nightly for me to my phone, when renamed update.zip. Fastboot also gives me an error trying to restore my nandroid piece by piece. It won't erase boot or recovery, nor will it flash those or the other pieces. It says it can send the file, but it fails on writing them.
In case the solution is to start from scratch and reroot etc., I tried that, but I cannot copy exploid to my phone, it says it doesnt have permission (same error as before).
I know this is fixable, and if anyone can help I'd be eternally grateful.
Also, I can provide any more details necessary.
Also, I can get to fastboot, hboot, recovery (not clockworkmod, the blank one with a phone icon and red arrow), and the splash page which seems to have limited ADB functionality.
HELP!
If you can get into the stock recovery, you can flash the clockwork update.zip and get into clockwork recovery. You need to do that and then reflash a ROM. If you broke root in all of this, then you won't be able to do that. I'm also assuming your s-off failed, it still is s-on? If so, that's probably why it isn't writing the partitions from your nandroid, but I'm not positive about that, since recovery can write to those partitions. If you need the clockwork update.zip, let me know and I'll attach it when I get home, I know their site is down at the moment. But yeah, get that clockwork update.zip on the root of your sd card and try flashing it through the stock recovery and then a custom ROM again. Report back whether it was successful or not
I just got a Kindle today and decided to root it. Here are my exact steps.
Downloaded latest KFU
Ran it, ran input 2 for permanent root
installed TWRP and FireFireFire
made a backup of my current rooted stock ROM
wiped everything
flashed CM9 reloaded ICS ROM
didn't like the ROM, so I went back into recovery
wiped everything
flashed AOKP ROM
reboot
and nothing.. the screen went black
I click the power button and the green light will come on and then everything goes black again
I reinstalled the drivers and got it to boot in recovery. I wiped cache, dalvik, and factory reset. I tried to boot but it won't boot into anything, it just turns off.
I'll try to restore my nandroid and see what that does
Edit: It rebooted into my nandroid of the stock ROM. Was it just a bad AOKP download? Should I run the perm root =, TWRP recovery instal and FireFireFire install on KFU again?
kendallc123 said:
I reinstalled the drivers and got it to boot in recovery. I wiped cache, dalvik, and factory reset. I tried to boot but it won't boot into anything, it just turns off.
I'll try to restore my nandroid and see what that does
Edit: It rebooted into my nandroid of the stock ROM. Was it just a bad AOKP download? Should I run the perm root =, TWRP recovery instal and FireFireFire install on KFU again?
Click to expand...
Click to collapse
I have no idea why your AOKP install failed, but you should check the MD5 sum on those zip files before you flash any new ROM. You don't need to root stock again if you intend to flash a new ROM, but make sure you have TWRP 2.1.1 and FFF 1.4a installed on your device before you try it again. As long as you have those two piece in place, you can get back to recovery and flash something again if anything else should go wrong.
Download a new update zip and give it a try!! check md5 sum first!!
Alright I have never checked an md5sum. I never really knew it was important! I found out how yo do it and what program to use, so I will definitely do that next time! Thanks
I rooted, installed TWRP and was running a custom ROM for awhile. I wanted to go back to stock, went into recovery wiped everything and restored my stock backup, now it won't boot or go into recovery, just says [4750]Fastboot node started. I need help
OK, I managed to get back into recovery TWRP and re-installed my custom ROM but now I get google FCs, I can't do anything. I have other ROMs and stock zip but I don't know how to use ADB, I never worked with it, could someone help me with using adp?
Kaflex said:
I rooted, installed TWRP and was running a custom ROM for awhile. I wanted to go back to stock, went into recovery wiped everything and restored my stock backup, now it won't boot or go into recovery, just says [4750]Fastboot node started. I need help
OK, I managed to get back into recovery TWRP and re-installed my custom ROM but now I get google FCs, I can't do anything. I have other ROMs and stock zip but I don't know how to use ADB, I never worked with it, could someone help me with using adp?
Click to expand...
Click to collapse
since you can get into recovery, flash stock ROM with bootstack. Don't restore backup! Start fresh and see how it works out. Don't forget to flash SU and twrp just for good measure.