Hi,
I have installed ClockworkMOD v3 recently. I heard that I cannot flash radio directly trough it, so I thought about downgrading to CWM v2.5. Can it be done? Is it like normal installing of CWM or there are some additional steps?
And yes, I have S-Offed my phone with AlphaRevX and rooted following this guide:
http://forum.xda-developers.com/showthread.php?t=1130044
Just in case that it is needed to mention.
It isn't needed to flash an older version.
Go into ROM manager and hit Flash Recovery, it will be version 2.5.0.7, and then boot into it from the app.
Booting normally into recovery will enter whatever version you flashed, but if you boot from ROM manager it will be temporarily 2.5.0.7.
AloneInShadow707 said:
It isn't needed to flash an older version.
Go into ROM manager and hit Flash Recovery, it will be version 2.5.0.7, and then boot into it from the app.
Booting normally into recovery will enter whatever version you flashed, but if you boot from ROM manager it will be temporarily 2.5.0.7.
Click to expand...
Click to collapse
Thank you for quick and precise response
Glad to help
Related
Some time ago i rooted my phone with Unrevoked, at that time it flashed Clockworkmod 2.5.0.1 to my phone. Since then i've been upgrading my recovery through ROM Manager, or so i thought anyway. Because using "Reboot into recovery" from ROM Manager, takes me to recovery with version 2.5.0.7 of Clockworkmod, but if i manually go into recovery, by turning the phone off and holding down the volume and the power button, i get to Clockworkmod 2.5.0.1 still.
Why is it like this? Almost like there is "different levels" of recovery modes? Do i have two different recoveries installed on the phone or something? And how do i flash my recovery so that when i boot into recovery the manual way, it's the latest as well?
Been doing some thinking, the reason ROM Manager doesn't seem to update the version when am booting into recovery the manual way, is it because of this S-ON thingy?
Did some reading on: http://alpharev.shadowchild.nl/ and there is some kind of security on /system and /recovery(which Alpharev can remove, but i haven't tried it yet), is this the reason why ROM Manager doesn't flash the recovery?
If so, when i click "reboot into recovery" from inside ROM Manager, what kind of recovery does it take me to, since the version obliviously is updated there?
Edit: Maybe it's only doing a "fake-flash" of the recovery from inside ROM Manager? Because of this security thingy on /recovery? If so, how do i permanently update the recovery? Is it only possible through unrevoked? And if i use Alpharev, will ROM Manager then be able to permanently update the recovery?
Yes you are right assuming it has to do with s-off. Koush circumvented this by using fakeflash which is automatic applied when rebooting using Rom manager.
And yes making the phone s-off will make Rom manager able to flash the recovery, but it won't because at the time it was made s-off wasn't available. So it will need an update from koush.
To flash a recovery you download it as an img file to your computer and flash it using fastboot.
Okay, thanks for the answer.
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...
guys help!
rooted my DHD successfully using visionary, installed ROM manager and flashed clockworkmod recovery 2.5.1.3 all fine.
when i boot into recovery i get this:
image 1
and when i try to apply a rom via sdcard:update.zip it says this:
image 2
phone just restarts and nothing is flashed...
I checked for root in Terminal Emulator and it was still there..
Seems you didn't apply S-OFF. Without it everything you do will be undone when you reboot.
andyharney said:
Seems you didn't apply S-OFF. Without it everything you do will be undone when you reboot.
Click to expand...
Click to collapse
not true, the nand protection is only inplace while the device is booted not in recovery.
suprastar said:
guys help!
rooted my DHD successfully using visionary, installed ROM manager and flashed clockworkmod recovery 2.5.1.3 all fine.
when i boot into recovery i get this:
image 1
and when i try to apply a rom via sdcard:update.zip it says this:
image 2
phone just restarts and nothing is flashed...
I checked for root in Terminal Emulator and it was still there..
Click to expand...
Click to collapse
you havent flashed a recovery, thats the stock recovery, download rom manager and install cwm
AndroHero said:
you havent flashed a recovery, thats the stock recovery, download rom manager and install cwm
Click to expand...
Click to collapse
he has but as he is S-ON you can't install cwm
but in Rom manager it said I had flashed to CWM 2.5.1.3 successfully....
i haven't done the s-OFF yet, i was kind of holding back on that because the guide said it was "optional"
suprastar said:
but in Rom manager it said I had flashed to CWM 2.5.1.3 successfully....
i haven't done the s-OFF yet, i was kind of holding back on that because the guide said it was "optional"
Click to expand...
Click to collapse
thats the problem, without s-off you have no write access to the recovery partition, so although rom manager thought you had flashed the recovery ok, any changes made would of been reverted on boot
That was it, S-OFF was applied via One Click, then as soon as i booted into recovery, I had the proper CWM booted.
Thanks guys!
I am trying to update my clockwork mod through recovery, flash .zip, locate the updated zip and flash. It all seems ok with the version but when I boot in the phone and back in recovery it comes the old one. How can I solve this ? Thanks.
DiWizard said:
I am trying to update my clockwork mod through recovery, flash .zip, locate the updated zip and flash. It all seems ok with the version but when I boot in the phone and back in recovery it comes the old one. How can I solve this ? Thanks.
Click to expand...
Click to collapse
if you have s-off you can just flash the recovery image file from fastboot
Use unrevoked to flash it.
You're using fake-flash to run the latest one (or the crap ROM Manager) - as said either run unrEVOked again or, if S-OFF, flash it manually
I have a rootet Desire (via unrevoked) with s-off and Oxygen 2.1.3 ROM. I flashed a new clockwork version (3.0.0.5) .img file via ADB. If I boot my phone and enter the clockwork recovery the new version is used. If I reboot the phone using ROM manager it enters the old version of clockwork recovery.
So I think, I have 2 recovery versions on my phone. How can this be avoided? I just want to have the new one.
Found this in Cyanogenmod forum.
CWM 3.0.0.5 is permanently flashed so it's always there. 2.5.0.7 is a temporary recovery as when you reboot with rom manager, it uses the zip file that comes with it
Click to expand...
Click to collapse