I currently have Amon RA recovery installed. I can't boot any roms. I've been trying CM7 nightly build #27 and CM6.1. I have a nandroid backup taken from earlier yesterday when I had stock 2.2 Sense rom. I haven't been able to work with this nandroid backup from BAMod recovery or Amon RA recovery. I've been trying to flash clockwork mod. It finds the PB31IMG.zip on my sd and sprawls some stuff pretty quickly, the last thing being parsing PB31IMG.zip, it abruptly returns to the HBOOT screen after this without asking me to perform the update. I've tried a few different versions of clockwork. None of them take. I can install roms with both of the other recoveries successfully but I never get past the white HTC Incredible splash screen.
I am s-off, hboot 0.77.xx, radio 2.15.xx
I can see the device on my pc with fastboot but not adb.
Anyone dealt with this? Have suggestions?
Try updating your hboot first to .92
I updated hboot to .92.
I still can't flash any clockwork mod recoveries. They all get to parsing zip and then jump back to Hboot screen. Tried flashing Cyanogen Mod 6.1, says it was successful but its still hanging on HTC Incredible splash screen. The splash screen briefly flickers but thats it.
Solved!
solution here:
http://www.incredibleforum.com/foru...kwork-hangs-htc-incredible-splash-screen.html
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...
Well, I have a problem. The problem is that the recovery simply won't work. Okay, so I go into ROM Manager and flash the ClockWork Recovery. So then I reboot my Evo and I'm stuck at the Splash Screen. I thought that since I flashed a new ROM, it might just be gathering all the information up to start the recovery. So I return one hour later, and it's still on the Splash Screen. So I have to take off the battery and start it up normally and flash the Amon RA recovery. So then I reboot into recovery and it works fine. Anyone know why?
I think I read some where that rooting hwd004 phones with everything updated only recovery that is stable is ra
CrazyTechnoBoy said:
Well, I have a problem. The problem is that the recovery simply won't work. Okay, so I go into ROM Manager and flash the ClockWork Recovery. So then I reboot my Evo and I'm stuck at the Splash Screen. I thought that since I flashed a new ROM, it might just be gathering all the information up to start the recovery. So I return one hour later, and it's still on the Splash Screen. So I have to take off the battery and start it up normally and flash the Amon RA recovery. So then I reboot into recovery and it works fine. Anyone know why?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
But I have Hardware 003. And I can flash the ClockWork Recovery from the Amon RA recovery.
So Amon Ra is working but Clockwork isnt? Just stick to Amon Ra if you have that working recovery.
I recently tried to flash the non rooted stock rom for the evo 4g from the bootloader. However, when the update got to system, it failed with this next to it, "Failure-PU." I have done this procedure before and it succeeded without problems. However now, it won't work. The update as a whole failed obviously, and when I try to boot into recovery, it gets stuck at the htc evo 4g splash screen. I have used fastboot and the bootloader itself to flash both amon ra and clockwork. It says it was completed everytime. However, I still can't boot into recovery. It continues to hang up. I need urgent help! I can't afford to replace my phone!
EDIT: Finally fixed it. Cleared storage in HBOOT and reflashed Amon RA.
I'm trying to change the amon ra recovery to cwm5 but even though rom manager says that recovery is flashed succesfully the old amon ra still pops up when i reboot to recovery. I've also tried to flash cwm3 through amon ra and from amon ra reboot to recovery boots then to cwm3 but then after phone reboot amon ra is back. What gives?
Is it because the phone is still s-on? Are there any guides on how to get s-off on a 0.83 hboot and maybe cwm5 to work?
unrevoked seems to support only the newer 0.93 hboot.
Any help with this?
Just download alpharev 1.8 and burn to cd and boot to it. Follow instructions. You need to have a rooted stock Froyo Rom installed
Sent from my HTC Desire using XDA App
So I just rooted my fiancees phone, I have Superuser permissions and ROM Manager seems to work fine. But recovery doesn't. I've tried flashing the latest CWM in ROM Manager while telling it to erase recovery first, but even then I'm having the same issue. What am I doing wrong here? I've never had this issue on my phone before.
Try flashing clockwork thru hboot as a PB31IMG.zip you can get it below. Or try flashing to amonra or the stock recovery, and then back to clockwork again.
http://pvillecomp.com/?page_id=28
The black screen with two vertical bars is caused by an incompatible recovery on a SLCD screen. Try CWM 3.0.0.7 or Amon's.