Develop Bugs

Unrevoked and install the original android recovery

Hi, I'm thinking about to root the phone with Unrevoked, but I don't want to lose the original android recovery,
1. is there a method to flash the original recovery instead of the Clockwork mod recovery?
because I like to use it with fake flash and it is the best way to use always the latest updated Clockwork.

not possible with unrevoked i belive.
but what's the problem ? just use it, you will get CWM 2.5.0.7 and keep a fake-flash.zip on sd and launch it from 2.5.0.7

No, I like to leave the original android recovery because are 2 times that I have to send him to assistance and I don't like to send it with a custom recovery.

dzumagos said:
not possible with unrevoked i belive.
but what's the problem ? just use it, you will get CWM 2.5.0.7 and keep a fake-flash.zip on sd and launch it from 2.5.0.7
Click to expand...
Click to collapse
Quick question out of curiosity: why is CWM 2.5.0.7 flashed on a GSM Desire by default? They're up to 3.2.0.0 at least. Is there something wrong with later versions?

Is a metod to reflash the original android recovery from clockwork mod recovery?

You can't use the stock recovery to flash a custom ROM so it's just not worth it. Keep the RUU for your phone for if you need to go back to stock

ninpoumike said:
Hi, I'm thinking about to root the phone with Unrevoked, but I don't want to lose the original android recovery,
1. is there a method to flash the original recovery instead of the Clockwork mod recovery?
because I like to use it with fake flash and it is the best way to use always the latest updated Clockwork.
Click to expand...
Click to collapse
Sorry not possible, because you cannot use fakeflash from the original unmodified recovery(it was made for the old root method, which modífied the recovery to allow test-keys, so even though it looked like the original HTC recovery, it weren't).
However you can easily just use fakeflash(via rommanager) even though you have clockwork mod installed as well. It'll just open the fake flash recovery instead when the update.zip is flashed, so just root normally using unrevoked.

Sintel said:
Quick question out of curiosity: why is CWM 2.5.0.7 flashed on a GSM Desire by default? They're up to 3.2.0.0 at least. Is there something wrong with later versions?
Click to expand...
Click to collapse
Newest clockworkmod version uses a newer script for flashing. Some developed things (roms, etc.) does not support this script yet. So one won't be able to flash things.

[Q] New Clockwork Recovery 5.0.0.0

Hi... I just found that Clockwork Recovery has new version from their website but in zip format. Try to install it through ROM Manager and recovery mode but it is just temporary recovery. Every time I enter recovery mode by pressing power and vol down and choose recovery it is back to old recovery.
Does anyone try this new recovery and how to make it permanent or is it available in img format so I can flash it using Android Flasher.
for your reference please find it here :
hxxp://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.zip (please change hxxp into http)
*** sorry for my horrible English and grammar

it is cause you use the fake-flash method, launching CWM 5.0.0 by flashing a .zip file from your current recovery.
in order to permanently change your recovery you would have to be S-OFF and have a .img file of the new recovery

My HTC Desire already S-OFF but where to find this img file of new CWM Recovery?
I have search over Google and this forum but did not found. Is it possible to change this zip file into img file?

The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt

davebugyi said:
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
Click to expand...
Click to collapse
Thank you very much... how can I missed that

davebugyi said:
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
Click to expand...
Click to collapse
You are smart
CWM website folder can browse
got it
http://download.clockworkmod.com/recoveries/
recovery-clockwork-5.0.0.0-bravo.img 30-Aug-2011 23:25 3106816
recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt 30-Aug-2011 23:25 92

Easier just to look here:
http://www.clockworkmod.com/recovery_images.html

EddyOS said:
Easier just to look here:
http://www.clockworkmod.com/recovery_images.html
Click to expand...
Click to collapse
Yes but not all file available.
like HTC Bravo only latest recovery in zip format only.
Thanks

Yeah, but as this thread is for v5.0.0.0 then people will want the newest will they not?

someone already did some test?
for example backup the current rom (maybe one with ext partition), then flash an other rom (just for test), and then restore the backup (and see if boots and everything ok)?
i will try later anyway, but of course will be nice to already know if its work or have some problems

Has any one had the edify script error with CWM 5.0.0.0 recovery ?
I flashed CWM 5.0.0.0 today via fastboot and it works fine - however I tried flashing Cool 3D V9 Rom and then when i flashed the boot loop fix & got the edify scripting error does any one know of a work around ??? I did a search and i found some code by coolexe and baadnews but not sure if there is a way to fix this ?
-Dan

danw1million said:
Has any one had the edify script error with CWM 5.0.0.0 recovery ?
I flashed CWM 5.0.0.0 today via fastboot and it works fine - however I tried flashing Cool 3D V9 Rom and then when i flashed the boot loop fix & got the edify scripting error does any one know of a work around ??? I did a search and i found some code by coolexe and baadnews but not sure if there is a way to fix this ?
-Dan
Click to expand...
Click to collapse
ask the dev to update the script in the flashable zip or flash a 2.x recovery (amend script is no more supported from 3.x and up, only edify is supported)

anyone have a changelog? cant find one anywhere!

andQlimax said:
ask the dev to update the script in the flashable zip or flash a 2.x recovery (edify script is no more supported from 3.x and up)
Click to expand...
Click to collapse
Thanks for the advice will do.

sjknight413 said:
anyone have a changelog? cant find one anywhere!
Click to expand...
Click to collapse
follow koush or clockworkmod on twitter..5.x has faster backups (now it used .tar files) and preserve the file system of each partition (if ur sd-ext is ext3, it will be backup and restore as ext3, if u have ext4 it will be ext4, etc..with previous cwm recoveries the sdext was restored always as ext3)
also a new color sheme..now is blue light
edit: new recovery seems available 5.0.1.0 http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.1.0-bravo.img

I read from a koush twit :
"Desire and Desire CDMA users: I have just switched you to real flashing rather than fakeflash. You will need to S-OFF. with unrevoked."
so, out of curiosity, how Rom Manager can flash the recovery for real?
I always use fastboot, and i though there was no other way than that and the PB99IMG.zip method..
Someone know how that works (i mean the flashing through an app)?

i'm fine with 4.xxxx

andQlimax said:
I read from a koush twit :
"Desire and Desire CDMA users: I have just switched you to real flashing rather than fakeflash. You will need to S-OFF. with unrevoked."
so, out of curiosity, how Rom Manager can flash the recovery for real?
I always use fastboot, and i though there was no other way than that and the PB99IMG.zip method..
Someone know how that works (i mean the flashing through an app)?
Click to expand...
Click to collapse
Well there have always been another way just not on desire, since s-on users couldn't write to system or recovery while system was booted. But with s-off using a flash_image script will work just fine, which is pretty much what rom manager does(i assume).
So I asked koush on twitter to change us to native recovery flashing since s-off have been around for quite some time for desire
edit: so for everyone s-off that means: to update just install/open rommanager and press "flash clockworkmod recovery"(tested and working just fine)

mortenmhp said:
Well there have always been another way just not on desire, since s-on users couldn't write to system or recovery while system was booted. But with s-off using a flash_image script will work just fine, which is pretty much what rom manager does(i assume).
So I asked koush on twitter to change us to native recovery flashing since s-off have been around for quite some time for desire
edit: so for everyone s-off that means: to update just install/open rommanager and press "flash clockworkmod recovery"(tested and working just fine)
Click to expand...
Click to collapse
Thanks to ur tips, i found how it works!
from the terminat emulator on the phone:
Code:
flash_image recovery /sdcard/recovery.img
that should flash the recovery (even other partition i though), without use fastboot and without use the pc! thats nice!
On AOSP roms the flash_image utility is already included on /system/bin..in other roms (like stock ones) it should be downloaded and placed on the phone and used in the same way
that probably what rom manager does

So there is no way to get the latest version of ClockworkMod Recovery if we are on S-ON ?

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