Root Problems After ClockworkMod Updated to 3.0.0.5

[Internetpilot]

I rooted my Evo with unrevoked and flashed Myn's Warm 2.2 RLS5 and Netarchy ToastMod CFS More HAVS no-SBC. The whole process went fine and dandy, and I've been loving the "new" phone for a couple of weeks now. I upgraded (paid) to ROM Manager Premium, and today when I was dinking around with boot animations, ROM Manager informed me that there was a new version of ClockworkMod Recovery available. Thinking nothing of it (and having never noticed this "pop-up" before), I figured I should update CWM to 3.0.0.5.

Ugh.

Yeah, that didn't go over too well, and my poor Evo could not boot into recovery, whether I went through ROM Manager or using Myn's reboot option, or even doing the power +vol(-) button trick. When I tried the power+vol(-) button trick, my Evo vibrated three times and then wouldn't even turn on...at all. After cleaning my soiled pants and drying my tears, I took off my triple layer Seidio case, pulled and reinstalled the battery, and then my poor Evo would finally power on again. Whew!

After trying unsuccessfully to boot into recovery a couple more times, I realized that I probably needed to downgrade my CWM version. After reading everything I could find on XDADevelopers forum on the matter (and subsequently thinking, "O...M....G....what have I gotten myself into?!"), I realized that there is a CWM downgrade option in ROM Manager. The only option that wasn't 3.X is 2.5.0.7, and I'm pretty sure that's not what I was running before (I think it was 2.6.0.1). I did find THIS WONDERFUL THREAD which provided me with a way to upgrade from 2.5.0.7 to 2.6.0.1, and everything seems to be working fine again (except that ROM Manager still claims I'm using 2.5.0.7 and still offers the 3.0.0.5 update every time I start the app), but I am definitely running CWM 2.6.0.1 now.

Another "Whew!"....however, I do have some questions:

1. What does this do for my Nand backups? I should be able to restore (if necessary), right? I'm particularly worried about WiMax keys.

2. My brain hurts after trying to figure this out myself -- can anyone explain this whole Amend vs Edify thing in more plain language? Specifically, I'm wondering how it applies to me, especially why updating to 3.0.0.5 would cause so much problems on my phone to the point that 3.0.0.5 won't even boot?

3. Is there anything else I need to worry about or double-check as a result of this fiasco? I'm new to Android and rooting, I'm a techie type of guy but this is new territory for me, so although I can usually figure things out and/or get by on my own, this incident has me a little paranoid/worried about my backups and the current status of my phone in general.

Sorry for the long post. I'm hoping this is all a bunch of nothing and I'm just being a worry-wart. Thanks for any help, info, and confirmation of sanity that you can provide!

 

[Mr. Ed]

1. your backups should be fine. If you want to test...create a new back up..then try flashing an old backup ....you will have the new backup to go back to if something goes wrong

2. Simple answer...we are at an in between stage. Gingerbread Roms are going to require the new Edify script...older roms run on amend. Clockwork is just a step ahead preparing for it.

3. ditch rom manager and clockwork and go to aman ra. I have very little faith in either of those after using them for months I started having major issues. I occasionally will use clockwork to flash some mods that just won't flash in aman ra...but my trust is in aman ra now

decent link
http://forum.xda-developers.com/showthread.php?t=901119

 

[Internetpilot]

Thanks, Mr. Ed! I was thinking the same thing about switching to Aman Ra, and I just might do that.

Now, correct me if I'm wrong, but Aman Ra will not be able to restore my backups that I did in CWM, right? If I'm correct, then if I ever wanted to go back to MY stock ROM, etc., I would need to re-flash CWM to do it, right?

 

[Mr. Ed]

that is correct....

 

[akazabam]

Not sure if you've seen this, but here's a pretty good explanation for the difference between edify and amend:

[NOTICE] ClockworkMod Recovery 3.0+ and update-script - xda-developers

It's very easy to tell if a flashable zip is written in amend or edify. Simply open the zip and go to META-INF/com/google/android. If all you see is an update-script, it's amend. If you see an updater-script (note the different name) and an update-binary, it's edify. As I'm sure you know now, CW 3.0.0.5 can only flash script written in edify. Most flashable zips have been updated to support it, and for those that haven't you *could* just fix it yourself (not *that* hard to do) or you could give something like this a shot:

[TOOL] amend2edify Script converter [Zip] [Batch] - xda-developers

I have no idea if it works, as I haven't exactly tried it. In any case, it's much easier to use CW 2.6.0.1, so just use that.

It sounds like Mr. Ed answered your other questions. As for ROM manager it *is* the easiest way to flash a different recovery...when it works. Did you ever try just uninstalling it and reinstalling it? Sometimes (most of the time) that fixes it. Either way, feel free to forget about it, and just use PC36IMG.zip files (or flash_image from the command line with .img files). They're a little more reliable.

As for backups made in RA and CW, you are correct - they are not compatible. Just go ahead and keep the PC36IMG.zip for CW 2.6.0.1 on your sdcard (renamed, of course) just in case you want it back. Flash it first, then restore your backup if you need it. Until then, I agree that RA is the better of the two options.

 

[Mr. Ed]

^for the record...I have been continuing to mess with different recovery flashes...and I am 90% positive my corrupt recovery images were coming from rom manager

I keep the images in akazabam's recovery thread on my sd card. one for clockwork named renamepc36imgcw.zip and renamepc36imgra.zip and rename them and flash from hboot as needed.

 

[Internetpilot]

Thanks a ton, folks! I'm off to download the Aman Ra image from Akazabam's recovery thread to add to the CWM image I already downloaded from the same thread. I'll just look at the $ I paid for the ROM Manager Premium upgrade as a donation to the CWM cause...haha. I don't mind doing things the more manual way, especially if I can avoid scary noob debacles like this.

Thanks again. It's good to know I didn't mess things up too much. When my Evo wouldn't power up I was definitely getting worried.

 

[akazabam]

Yep, that's pretty much what I do, as well. If you'd still like to flash recovery without turning off the phone, I've uploaded flash_image to the same location as the PC36IMG.zip files here. It's a flashable zip, so put it on the root of your sdcard, reboot into recovery, flash it, then whenever you want to flash a recovery image, open up the PC36IMG.zip for whatever recovery you want, take the recovery.img out, and put it on the root of your card. Open the terminal, and type this:

su
cd /sdcard
flash_image recovery recovery.img

You can do the above commands as many times as you want while booted up, as you only need to flash flash_image to /system/bin once. That way, you get the same benefit of flashing from within android as you do with ROM manager, but you don't have to use ROM manager. Still, keep PC36IMG.zip files around all the time. You never know when you might not be able to boot into the system or recovery.

 

[Internetpilot]

Yep, that's pretty much what I do, as well. If you'd still like to flash recovery without turning off the phone, I've uploaded flash_image to the same location as the PC36IMG.zip files here. It's a flashable zip, so put it on the root of your sdcard, reboot into recovery, flash it, then whenever you want to flash a recovery image, open up the PC36IMG.zip for whatever recovery you want, take the recovery.img out, and put it on the root of your card. Open the terminal, and type this:

su
cd /sdcard
flash_image recovery recovery.img

You can do the above commands as many times as you want while booted up, as you only need to flash flash_image to /system/bin once. That way, you get the same benefit of flashing from within android as you do with ROM manager, but you don't have to use ROM manager. Still, keep PC36IMG.zip files around all the time. You never know when you might not be able to boot into the system or recovery.

That's an excellent solution, Akazabam! Thank you. I've always kept about four different backups on my SD card since I rooted/flashed, but it never really occurred to me that I could have problems booting to recovery (ooooops....).

So, I take it that ROM Manager is from the same developer of ClockworkMod? If so, it is actually nice of him to provide an alternative recovery (RA) as an option in the app, even though that causes ROM Manager to lose a lot (most) of its functionality. I guess it's also a little disconcerting that he acknowledges that we sometimes need an alternate recovery, eh?

I got my feet wet in the technology arena back in the days of MS-DOS and even CP/M, so commandline/terminal stuff doesn't bother me at all. I think I'll just do things your way for a while.

Thanks again, to you and Mr. Ed! I see you two seem to have the same sleep schedule I do...haha.

 

[akazabam]

That's an excellent solution, Akazabam! Thank you. I've always kept about four different backups on my SD card since I rooted/flashed, but it never really occurred to me that I could have problems booting to recovery (ooooops....).

So, I take it that ROM Manager is from the same developer of ClockworkMod? If so, it is actually nice of him to provide an alternative recovery (RA) as an option in the app, even though that causes ROM Manager to lose a lot (most) of its functionality. I guess it's also a little disconcerting that he acknowledges that we sometimes need an alternate recovery, eh?

I got my feet wet in the technology arena back in the days of MS-DOS and even CP/M, so commandline/terminal stuff doesn't bother me at all. I think I'll just do things your way for a while.

Thanks again, to you and Mr. Ed! I see you two seem to have the same sleep schedule I do...haha.

Yep, it's much more reliable than ROM manager . Clockwork and ROM manager are, indeed, from the same developer. Their designed to work together, but it can be pretty buggy (as you've seen). It's generally a good idea to just do things manually.

 

[Droidster]

2. Simple answer...we are at an in between stage. Gingerbread Roms are going to require the new Edify script...older roms run on amend. Clockwork is just a step ahead preparing for it.

question... I was not into my rooting addiction during the changeover to froyo.... did they have these issues then?
To bad clockwork is not downward compatible like the playstation platform
Oh wait, they bailed on there promise after ps2

Edit: question 2 will Armon back up and restore the gingerbread edify stuff?

 

[akazabam]

question... I was not into my rooting addiction during the changeover to froyo.... did they have these issues then?
To bad clockwork is not downward compatible like the playstation platform
Oh wait, they bailed on there promise after ps2

Edit: question 2 will Armon back up and restore the gingerbread edify stuff?

Clockwork is backwards compatible as long as you're using version 2.6.0.1, which was specially made after 3.0.0.x because a lot of flashable zips out there still use amend.

As far as the difference, it has nothing to do with backing up. Basically, Amend and Edify are different ways of scripting to flash (or install) the system (or portions of the system, since we have root). Edify has been around since after Android 1.5. These recoveries (CW and RA) or just based off the recovery for a particular Android version. Since Gingerbread recovery doesn't have Amend build in, neither does Clockwork 3.0.0.x, which it was based on. All that means is, to use a recovery system that was designed to work with Gingerbread, you *must* use Edify scripts; it will not work with Amend. That being said, we're not all on Gingerbread, yet, so older systems can still use Amend if the developer wants to (no good reason for it). Since that is the case, current recoveries must support both scripting types. All this concerns is the method by which the OS (or in our case, mods as well, since we have root) is flashed. Once the system is flashed, you're done. No need to care about how it was flashed anymore. I'm not exactly sure what you were asking, so does this help clear anything up?

 

[Droidster]

so does this help clear anything up?

Yep... thank you sir. My issue being a root newbie..kinda, anyway CM updated yesterday telling me to switch to 3.0.xx
I did. I was flashing a couple roms yesterday. After done playing I went to do a restore and bam! found out 3.0.xx does not work with the 2.0.5?xx that the nand was made with..
Spent some panic time like the OP here

 

[vwgtiturbo]

Thanks for this. I inadvertently updated to CW3, and could no longer install the GB keyboard or coconut font, along with a few other zips, and I was lost without a clue.

 

[MNTowguy]

OK Newbie here having some issues. Yes I am running ROM Manager and I updated to 3.0.0.5 I was trying some different roms and cannot get anything to install what so ever. tried switching to an alternate recovery and while rom manager says that I am in the alternate when I boot to recovery it still says Clockworkmod. I cannot get clockwork to go away to save my life. Help Please

 

[Xtremedays]

You might need to uninstall rom manager and flash the PC36IMG.zip file from hboot for amon ra 2.3. You can find instructions and the file here: http://androidforums.com/evo-4g-all-things-root/259446-clockwork-amon-ra-pc36img-files.html

Remember though that all of your backups from clockwork will not work on Amon RA. You should make a new backup after flashing to Amon.

 

[ExSaint]

When I had Amon I couldn't flash the new Z rom or even the nightlys. It said i required clockwork. Nor did clockwork work due to it being too new of a version. So i downgraded clockwork and everything seem to work fine.

 

[andygu3]

When I had Amon I couldn't flash the new Z rom or even the nightlys. It said i required clockwork. Nor did clockwork work due to it being too new of a version. So i downgraded clockwork and everything seem to work fine.

I've flashed every rom available with no troubles using amon ra v2.3. No troubles with nandroids or nandroid restores, just fyi

 

[evomattnc]

I switched to amon ra and then converted all my back ups from cw to ra and moved my original cw back up to my laptop. It was time consuming but i didnt have a motley group of back ups anymore lol.

Also I was tight for space on my 8 g card, and ra backups are smaller, until today, purchasing the 16gb patriot class 10 card today!! Hell i may even go 32gb lol.

 

[MNTowguy]

You might need to uninstall rom manager and flash the PC36IMG.zip file from hboot for amon ra 2.3. You can find instructions and the file here: http://androidforums.com/evo-4g-all-things-root/259446-clockwork-amon-ra-pc36img-files.html

Remember though that all of your backups from clockwork will not work on Amon RA. You should make a new backup after flashing to Amon.

Tried that, while it was something I had not tried and still no good! always clockworkmod 3.0.0.5 grrrrrr

 

[ocnbrze]

Tried that, while it was something I had not tried and still no good! always clockworkmod 3.0.0.5 grrrrrr

what happens when you transfer the renamed PC36IMG file? does it scan? do you get an error? are you naming the file PC36IMG exactly?