Database Users

CW Rom Manager can't boot into recovery - freeze at HTC splash screen

Searched, but couldn't find an answer to this. I rooted and installed ROM Manager so I can do a nandroid backup before installing a custom ROM. However, when I press back up in ROM Manager, it restarts and hangs/freezes on the HTC MyTouch 4g splash screen.
What am I doing wrong?

Have you flashed CWM recovery after installing Rom Manager. You must flash the recovery before you can backup/restore or install roms. I almost did that myself but luckily i read the thread concerning it again and flashed REcovery before trying to back up rom.

Yeah, I did that first and the problem remains. I just uninstalled and reinstalled ROM Manager and am about to try "backup current rom" again (unless I should reboot into recovery and back up from clockwork recovery?).

FWIW; Current recovery is ClockworkMod 2.5.1.2

anyone?

Did you ever find a solution to this problem? I just started getting exactly the same. Cant reboot manually into clockwork recovery or from Rom manager :/

If you have flashed a recovery beyond that supported by ROM manager, you will not be able to perform recovery functions from the app (i.e. backup). CW3 is required for CM7 ROMs, but will not be supported by ROM manager until the CM7 RC drops. You can still manually boot to recovery (I always Vol up when powering then select Recovery) and if you have CM7 nightly installed, it has a "reboot to recovery" option in the reboot menu.

You need CWM3 to use CM7.

neronian said:
anyone?
Click to expand...
Click to collapse
Sometimes it is necessary to flash clockwork recovery more than once before it will actually stick. Also, occasionally it will freeze on the splashscreen after a backup, but a battery pull and turning out the phone should be fine.
Sent from my HTC Glacier using XDA App

Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.

hammondnav said:
Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.
Click to expand...
Click to collapse
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.

TeeJay3800 said:
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.
Click to expand...
Click to collapse
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...

hammondnav said:
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...
Click to expand...
Click to collapse
You said "the Clockworkmod Recovery that you can download from the Market", and that kinda does. No biggie though.

Just an update for my problem, it turned out that clockwork recovery had corrupted for whatever reason and couldn't be reinstalled from rom manager. As I wanted to test Cm7 anyways I just ended up flashing clockwork recovery 3 manually through fastboot and its all gravy again
Sent from my Desire HD using XDA App

How to flash clockwork recovery from fastboot or fron clockwork recovery 2.51?
Sent from my SGH-T959 using XDA App

Thanks, everyone. What happened with mine, I have no idea, but I randomly opened rom manager and was greeted with an update to the recovery. So I downloaded it and voila - I can now boot into recovery and do backups, etc...

[Warining!!!]The CWM Recovery 3.0.0.5 may not be working properly!

WHAT I HAVE DONE:
Backuped my rom with 3.0.0.5 to mess up with my rom.
Replaced framework-res.apk to get some new icons.
New framework-res.apk crashed my phone.
Tried to restore backup with 3.0.0.5.
Find myself stucked at "HTC".
Tried to flash MIUI rom from official MIUI website, MD5 checked.
Still stucked.
Went back to recovery 2.5.1.3.
Tried to restore backup created by 3.0.0.5.
Everything is OK now.
ORIGINAL PROBLEM:
Under 3.0.0.5 Backup restore failed+Flash MIUI ROM failed+HBOOT OK+Tested 13 times!!!!
symptom: Stuck at "HTC"
Went back to 2.5.1.3 and Flash MIUI ROM OK.
Now trying to restore backup created by 3.0.0.5...
Hope no more bricked DHD....
Want more discuss...
This recovery come with CWM Rom Manager 3.0.0.7 following recovery flash from Internet.
MD5: 5E457EDCC2CC8AF60E7B8EB10E1BBF8A
UPDATE: My DHD alive again...
Anybody would like to give it a try may follow this:
Make sure you are using version 3.0.0.5.
Backup your current rom (Make sure you have enough rom on your TF card, there won't be an warning if you failed because of lack of disk space!!! 2GB free recommend). (The backup function seemed OK...)
Mess your system up. (Delete some important files such like framework-res.apk...)
restore backup...
Here I get stucked at "HTC" (AKA first boot screen, defined by manufactor.)
RESTORING:
Boot into HBOOT, then fastboot, flash CWM Recovery 2.5.1.3. (Attached)
restore....
It's alive now...

Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.3

Are you certain of this?
I need the devs and Senior Members opinion's please.

Kelthizar said:
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.13
Click to expand...
Click to collapse
I don't think recovery have anything to do with my rom. According to my 3 years android messing up history.
On the other hand, if that's true, there should be an warning when I flash my recovery through CWM Rom Manager.

CWM 3.x is fine. Been flashing roms with it since january (or december). A lot of people actually.
Edit: recovery has to do with the roms. Cwm 3 requires the updater script(edify). Also, cwm 3.0.0.5 from rom manager works fine for backup/restore. If you flashed it on your own before it was made available through rom manager, then its probably the test version which had probs restoring.
Sent from my Desire HD using Tapatalk

M_T_M said:
Are you certain of this?
I need the devs and Senior Members opinion's please.
Click to expand...
Click to collapse
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..

jkoljo said:
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
Click to expand...
Click to collapse
Restored my backup created by 3.0.0.5 using 2.5.1.3, strange result according to your opinion...

It also depends on the ROM and it's filesystem, but the rule of thumb is, don't even try it.

Kelthizar said:
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.3
Click to expand...
Click to collapse
phunkycow said:
CWM 3.x is fine. Been flashing roms with it since january (or december). A lot of people actually.
Edit: recovery has to do with the roms. Cwm 3 requires the updater script(edify). Also, cwm 3.0.0.5 from rom manager works fine for backup/restore. If you flashed it on your own before it was made available through rom manager, then its probably the test version which had probs restoring.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
jkoljo said:
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
Click to expand...
Click to collapse
Post updated, a little bit long to read it through... but please...
My "ROM" is referring to the current system+user data+whatever else inside my nand, not the one in my update.zip. If you would like to know.
Once I learned recovery backup rom exactly the way it is, just like what Norton Ghost do to your hard disk, so if backup and restore not working, the files must be broken. Otherwise it's the recovery's fault.

[Q] Stock ROM->Cyanogen Via Androot and RomManager?

Is it possible to go from Stock ROM to CyanogenMod via this path:
1. Using Universial Androot to root
2. Install RomManager from the market
3. Install Clockworkmod recovery 3.0.6 from Rom Manager
4. Install CyanogenMod from RomManager
That would be very easy compared to using adb. And it does not require a PC like the various one click root methods.
It should work?

I am asking because these optiions are already in the cyanogenmod wiki (some of them put there by me)
And if it works without problems, it should probably be the recommended update path.
I might try it out myself, but it requires me to go back to stock rom, which I haven't done before. If I understand correctly, it is not possible to flash a 1.6 ROM from a new Clockworkmod recovery, I would have to go back to maverick or amon ra recevery?
I am running Cyanogenmod nb 12, and clockworkmod recovery 3.0.6 at the moment.

to get back to stock rom, you just have to connect your phone to the PC, and double click the .exe of the ROM

I am not using windows, and do not have a rom exe file. I rooted and flashed my phone via adb on linux. I do have a nandroid backup of my stock room after it was rooted though.

Then flash back the old amonra recovery, before restoring your backup because it won t work with the latest clockworkmod

christick said:
Then flash back the old amonra recovery, before restoring your backup because it won t work with the latest clockworkmod
Click to expand...
Click to collapse
Ok thanks, I just heard from some one at cyanogen that using RomManager to flash the recorvery on a rooted stock rom won't work. So I guess the update path in the first post is not valid...

finnk said:
It should work?
Click to expand...
Click to collapse
Uhm... I think not: is missing the "insmod tattoo-hack.ko" and it will fail the "remount" operation (and then the flash).
IMHO.
Bye
Diego

diego72 said:
Uhm... I think not: is missing the "insmod tattoo-hack.ko" and it will fail the "remount" operation (and then the flash).
IMHO.
Bye
Diego
Click to expand...
Click to collapse
Yes, I think you are right. Stock rom needs the tattohack loaded before flashing a recovery.

finnk said:
Yes, I think you are right. Stock rom needs the tattohack loaded before flashing a recovery.
Click to expand...
Click to collapse
Well, i had a CyanogenMod "installed" on my tatto, and i flashed it back to the stock 1.6 rom without installing anything, without problem.
i guess that's the question, isn't it?

I used the method you're saying, Androot+Flash Recovery from Rom Manager to the latest ClockworkMod and unfortunately it's not working.
I don't know if it is because the new clockworkmod but my advice is don't use this method. I posted some questions in other threads but nobody could help me.
I reflashed Clockwork several times even to 3.0.6, but the startup recovery menu still the same.

[Q] Cannot Install Rom with CWM .... Worked before!

Hi,
Installed CM Nightlies and now wanted to install pre 2.3 roms.
When I select the zip from CWM I'm getting and error saying there is a scripting error and that edify is not supported from 1.5 etc .... hopefully its a common error.
I tried reflashing 3.2.0.0 recovery but didnt help.
Is there an easy solution for this? As I cannot installed any ROM.

You need Clockworkmod 2.5 for this. So you can either change your main clockworkmod Recovery, or, you can use ROM Manager App from within CM7 ROM. Open ROM Manager, then select "Install CLockworkmod Recovery", then select "Reboot into Recovery" from within the ROM Manager App. This will take you to Clockworkmod 2.5, and you can install Sense based ROMs normally.
Or, if you wish to replace your "main" Clockworkmod 3.x with 2.5.0.7 (Not from within ROM Manager), the Recovery.img file can be found here:
http://www.multiupload.com/PSIIJNBD4E

Ah ..... easy solution then....
So my quesiton is originally I was able to install roms with 3.x Recovery and now I can't, how come this has happened?
I take it that going back to 2.5.0.7 I'll be stuck with the off-line charging bug to?
Thanks for the great help!

This is because Sense ROMs (and Radios) use an older scripting technique (called Amend, which is no longer supported in Clockworkmod 3.x). All the new ROMs like CM have moved to the newer scripting technique called Edify.
And Yes, any version below 3.1.0.2, and you will be stuck with offline charging bug, Which is why it is probably better to install this via Clockworkmod 2.5.0.7 using ROM Manager. This way, you wont get the offline charging bug, and you keep to get both Clockworkmods, 2.x and 3.x

[Solved]Can't boot CWM 2.5.x through ROM Manager - keeps going to CWM 3.2

Hi
I am currently running the latest CM 7 nightly build. However, I have issues with GPS which doesn't find any satellites.
In order to re-flash the radio (which I have tried previously), I need to use ClockWorkMod Recovery 2.5.x. Currently I have 3.2.0.0.
I have previously used ROM Manager to do this, but now when I install 2.5.0.7 through ROM manager and select Reboot to recovery it simply reboots into 3.2.0.0.
I have tried reinstalling ROM Manager from Android Market after complete uninstall. But the same things keeps happening.
Any suggestions?
BR, Martin / mhca

Is a small "bump" allowed...?
I haven't found a solution yet. I have even played around with different ROMs without success. Is it a bug in ROM Manager?
Do I have to first upgrade CWM to 5.0.0.2 and then afterwards try to use ROM Manager to hopefully reboot into CWM 2.5.0.7 ?

Flash this ZIP in your existing CWM3/4/5 setup. Then you can get temporary 2.5.0.7 without touching the ROM Manager app:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
(It's the same temp 2.5.0.7 which ROM Manager downloads.)

Thanks a ton!
I just realised that this was even written with small text in The Complete Wildfire index, right next to the links to the radio. But somehow I missed that.
Really glad that you gave me a fail-safe method which doesn't require Rom Manager.

Radio didn't flash with CWM - used Android Flasher
Although I got a working CWM 2.5.0.7 with the above-mentioned method, I couldn't properly flash the radio.
I got error message "no space left on device", must likely due to custom partition sizes.
I found out that I could use the Windows app Android Flasher to flash the radio. And now my GPS works