Develop Bugs

[Q] Most stable CM recovery

Hey, just a quick question;
the CyanogenMod 7 update guide states
'NOTE: the ClockworkMod version 2.5.0.7 installed by Unrevoked3 is widely reported not to work with new "PVT4" batches of the Desire. To find out version of the device: '
I have found this to be true, and two times have I had the problem of having a phone which cannot mount an sd card.
So, what is the most stable version of the recovery for my HTC Desire? In Rom Manager I have the options of versions 2.5.0.7, 2.5.1.3 and 2.5.1.1.
Thanks!

I'm currently using 3.0.0.5 I believe it is, works fine apart from it no longer supports the installation of ROM's/Mods that use the old style install-script.

CM 2.5.1.8 is most stable for me coz working fine, try this

Ok so if I want to use the new 3.0.0.5, all I need to do is download the .zip and flash it like I would a rom through recovery? I actually think I may be using AmonRa 2.0.1; Rom Manager is lying to me - so will i also be safe if I flashed it from AmonRa? Sorry for being cautious; I'm sick of the command prompt.

No. Using a zip file only fake flashes the recovery so it's only there for the one time and when you reboot it it's gone. You need to actually permanently flash the .img file. You need S-Off for this. You can use fastboot or the Android Flasher, either way is fine. Also Rom Manager is gay for the Desire. Don't use it. BTW, I'm using 3.0.0.5 built by Kali. I have the fake flash 2.5.0.7.zip file incase I need it.

Meaple said:
No. Using a zip file only fake flashes the recovery so it's only there for the one time and when you reboot it it's gone. You need to actually permanently flash the .img file. You need S-Off for this. You can use fastboot or the Android Flasher, either way is fine. Also Rom Manager is gay for the Desire. Don't use it. BTW, I'm using 3.0.0.5 built by Kali. I have the fake flash 2.5.0.7.zip file incase I need it.
Click to expand...
Click to collapse
Oh ok. Thanks, that was useful! I will probably stick with the recovery I have now and just not use Rom manager then (after all that may be the cause of my problems) , I'm not too keen on S-Offing right now.
So why would someone want to fake flash a recovery?

[Q] How to update from ClockworkMod recovery 2.5.0.7 to 3.0.0.5?

Need to update my recovery for successful flash of baadnewz desire S
port. Ive got the image, cant find the option in bootloader to install it
though. I am s-off. Searched everywhere but cant find a direct answer.
Any help is appreciated.

Use the fastboot commands to flash it, or the flasher app in ROM Development

EddyOS said:
Use the fastboot commands to flash it, or the flasher app in ROM Development
Click to expand...
Click to collapse
Thanks for the quick answer. Im going to try that now. Another question if i may, sorry if its
noobish just not up to date on this stuff, will say Leedroid or sense roms still work if i have
CM7 hboot?
Edit : Anyone in the same boat go here :
[UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.6.1](15/01/11)

Now i really need help. My phone is hanging in fasboot mode while i was
flashing hboot with the flasher. what to do next?

esk02k said:
Now i really need help. My phone is hanging in fasboot mode while i was
flashing hboot with the flasher. what to do next?
Click to expand...
Click to collapse
Can you get into recovery? If so, you could try restoring nandroid and checking that the hboot file downloaded OK - if it came with an MD5 it's worth checking that - before giving it another go.
I've never used the flasher, just adb commands. Never had a problem flashing hboot tables.

00droid said:
Can you get into recovery? If so, you could try restoring nandroid and checking that the hboot file downloaded OK - if it came with an MD5 it's worth checking that - before giving it another go.
I've never used the flasher, just adb commands. Never had a problem flashing hboot tables.
Click to expand...
Click to collapse
Yea my own stupidity i guess. well im gonna pull the battery. lets see what
happens then.
edit : its ok regained control after unpluging usb. how do i know if it installed.
i am familiar with adb. how do i flash the cm7 hboot via that?

I also had problem with the flasher when I started in windows, then the phone just couldnt start or flash a new rom, but when I started the phone with backbottom ipressed and then started Android flasher all worked perfect.

esk02k said:
Yea my own stupidity i guess. well im gonna pull the battery. lets see what
happens then.
edit : its ok regained control after unpluging usb. how do i know if it installed.
i am familiar with adb. how do i flash the cm7 hboot via that?
Click to expand...
Click to collapse
Good news! To check your recovery you can either just boot into recovery and see what version you have, or remain booted and look in /sdcard/clockworkmod.settings (open as text file) to see the version number.
To flash hboots - check the instructions on the Alpharev site: www.alpharev.nl
EDIT: I found this post helpful as the instructions at alpharev are a little minimal at first sight. Obviously you are using the CM7 table not the Oxygen one!
http://forum.xda-developers.com/showthread.php?t=882758

Hi guys, I'm a little stuck/confused. When I boot my phone in Recovery Mode it says I'm running Clockwork Mod v2.5.0.1.
I installed a new version of ROM Manager (v3.0.1.0) flashed ClckworkMod Recovery and that says I have v 2.5.0.7 - so:
1. How do I ensure that the recovery mode is v 2.5.0.7
2. Do I need to unistall ROM Manager or,
3. Just leave it be?
System details:
Rooted HTC Desire
Android version 2.2.1
Baseband version 32.54.00.32U_5.14.05.17
Kernel 2.6.32.36_rcmix_11032
Build number
RCMix HD v3.6.1 D2Ext Rotate
The numbers above don't mean much to me - I'm not a dev.
Thanks in advance.
*EDIT*
I've since downladed and installed the .zip found here: http://forum.xda-developers.com/showthread.php?t=839640
It worked but ROM Manager still says the current recovery is version 2.5.0.7 although when I rebooted the writing was orange. I hope that makes sense to someone...

djkaija said:
It worked but ROM Manager still says the current recovery is version 2.5.0.7 although when I rebooted the writing was orange. I hope that makes sense to someone...
Click to expand...
Click to collapse
This is perfectly normal as 3.0.0.5 isn't an 'official'/final release yet.

Cannot flash CWM 5.0.2.0 with rom manager in miui

Hello everyone,
i used to have rom manager and cwm 2.5.0.7 working fine under MIUI.Then i decided to replace the cwm files with the 4ext recovery.All went ok and i was able to fakeflash with rom manager and boot into 4ext until one i day i decided to fakeflash via rom manager the newest cwm 5.0.2.0 Although it says flashing complete when i try to reboot into recovery it gets me to the old 2.5.0.7
Any ideas?

Are you s-off? If yes, flash recovery via fastboot.

No, i m not
Actually i dont want to replace my permanent recovery.Just to be able to use the fakeflash version in rom manager!

Follow these instructions:
go to settings > applications > manage applications > ROM Manager > #uninstall#
End of all your problems. ROM Manager is a third party app that just causes problems, it is a lot safer to just boot into recovery manually (power off, hold volume down & power, use volume keys to navigate RECOVERY, press power to boot into recovery)
If you want to fakeflash through recovery, all you need is the recovery.zip, and fakeflash it like you'd flash a ROM.

Ivanovic said:
Hello everyone,
i used to have rom manager and cwm 2.5.0.7 working fine under MIUI.Then i decided to replace the cwm files with the 4ext recovery.All went ok and i was able to fakeflash with rom manager and boot into 4ext until one i day i decided to fakeflash via rom manager the newest cwm 5.0.2.0 Although it says flashing complete when i try to reboot into recovery it gets me to the old 2.5.0.7
Any ideas?
Click to expand...
Click to collapse
I agree with the other: dont use rom manager
anyway, u can't flash it beacuase the last version of rom manager do not use fakeflash anymore, it's need s-off now
so, u must s-off, then better if u flash it with fastboot, and use the recvoery manually

Thanks for the replies people

Nothing wrong with 2.5.0.7, it does the job. Remember to press the 'Thanks' button rather than just saying "thanks".

Offcourse its nothing wrong.But i used a fake flash version of 4ext recovery via rom manager thats why i started this thread.Because i m no longer able to fakeflash another recovery via rom manager.I know it can be done via permanent recovery.

Ivanovic said:
Offcourse its nothing wrong.But i used a fake flash version of 4ext recovery via rom manager thats why i started this thread.Because i m no longer able to fakeflash another recovery via rom manager.I know it can be done via permanent recovery.
Click to expand...
Click to collapse
as i said, latest rom manager does not support fakeflash anymore!

I had the same problem, then I go s-off and was able to flash recovery also via RomManager...

I believe ROM manager doesn't support fake flash on the desire as this was breaking many desires that had true flash versions of recovery.
It got so bad at Android forums, we had to create a thread warning people.
http://androidforums.com/desire-all-things-root/356192-warning-do-not-use-rom-manager.html
Anyway for me 2.5.0.7 is still my favourite recovery.
Don't really understand the need for ROM manager anymore. It made lots of sense before Unrevoked came along. Now it seems to me just helping the lazy get lazier (but of course this is just my opinion)

rootSU said:
ROM manager doesn't support fake flash on the desire as this was breaking many desires that had true flash versions of recovery.
It got so bad at Android forums, we had to create a thread warning people.
http://androidforums.com/desire-all-things-root/356192-warning-do-not-use-rom-manager.html
Anyway for me 2.5.0.7 is still my favourite recovery.
Don't really understand the need for ROM manager anymore. It made lots of sense before Unrevoked came along. Now it seems to me just helping the lazy get lazier (but of course this is just my opinion)
Click to expand...
Click to collapse
Created a thread in Desire General section with the same topic and linked to your post respectively to the one on androidforums.

Updgrading Clockwork mod

During the summer I rooted my phone and i have Clockworkmod v2.5.0.7 installed.
I am trying to upgrade to the latest version and it never seems to stick.
Using Rom manager. It says that im flashed to v5.0.2.0 yet when i boot to recovery from rom manager it loads to v2.5.0.7. Does the same thing if i choose to flash a rom though ROM MANAGER. each time v2XXX loads
So i fire up recover and try loading the zip. Bingo it works. The screen turns from green to blue and V5.0.2.0 is now there for me to use. But if i reboot and later return to recovery its back to the old V2xxxx..
Any ideas why this is happening? Is it really necessary to move on to the V5xxxx versions? I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Thanks in advance..

When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.

Meaple said:
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Click to expand...
Click to collapse
if your Desire is s-off, then ROM Manager flashes recovery normally.
Sent from my HTC Desire using XDA App

rom manager now works only if u have s-off..no fake flash anymore is possible

revolutionary.io will upgrade cwm if you want

I think this thread answers one of my own questions but will ask it anyway to confirm; when I rooted my Desire (via Unrevoked) a few months back, the ROM Manager app that continues to be updated via the market offers the option to upgrade the version of CWM... is it OK to proceed with this?
I've been wary of upgrading from the version installed via the rooting process, just in case, but seeing this thread has made me think there isn't actually an issue with whatever version of recovery you have installed?

TKG26 said:
I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Click to expand...
Click to collapse
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.

To upgrade recovery (or hboots) I always use Fastboot Commander and it's very easy to use and never let me down.

erklat said:
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
Click to expand...
Click to collapse
I agree. Unless you need to maintain an ext 4 partition (as 2.5.0.7 converts it to lower apparently when backing up) I see no reason to change from 2.5.0.7.
I use it even today. Best recovery IMHO.

Wildfire ROM update - backup questions

Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards

1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)

As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App

slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.

150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App

You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?

The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer

nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.

Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.

Yes, fastboot is available.
Thank you.

Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.

Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards

The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself