Quick Question: Using Rom Manager to Flash Recovery?

[watskyhotsky]

had clockworkmod recovery on my phone for a long time.

Today I used FastBootRoot to flash a different recovery so I could install some other roms.

In one of my 2.2 roms, I installed Rom Manager, and used the app to flash the newest ClockWorkMod.

The phone is rooted, however, it started flashing without asking me for root access.

when it was DONE, it finally requested root access and I had to tap OK.

Rom Manager then Force Closed, and I rebooted the phone into recovery, it loaded up clockworkmod just like I remembered it.

I then wiped everything, and tried to install the 6/01 .zip of aospCM7 that I had stored on the root of the card.

it failed saying it could not get.build.prop and i saw thunderc in quotation marks.

it wouldnt install.

I started to worry, then I tried restoring a backup and that worked perfect. so now Im back into my aosp installation.

I want to know what went wrong? how can I fix clockworkmod recovery? can I flash it again from Rom Manager on the restored version of my previous rom?

has this happened to anyone else?

I tried to be as detailed in my actions I tookso I can get the best answers.

thanks


Maybe a nice detailed answer on how to avoid this would be helpful to anyone else who might experience this

 

[contramancarl]

I flashed my recovery through Rom Manger too. I got the same error trying to flash 06/01, and none of my backups would boot. I finally flashed zomg rom and tried to flash another version of clockwork but it would only go to the version i got from rom manger. (camera button is enter instead of setting button) so until i figure something out it looks like im stuck with it

 

[rockneo]

i would just manually flash another cwm recovery

 

[skullet11]

I am in the same boat. still running 2.2.

 

[JerryScript]

The recommended recovery for aospCM7 is linked in the thread for that ROM.

I know alot of people use different recoveries sucessfully with various ROMs, including some releases of aospCM7. However, various recoveries use different types of scripting, example edify vs amend. Some ROMs require one or the other type of scripting, and there may (I don't know this for sure) be other dependencies aospCM7 has due to it being the only ROM at 2.3.4.

I would love a reliable quick and easy solution like ROM Manager, but this is my only phone, and I like to keep it functional, so I'll stick to the tried and true 5 steps to flashing a ROM

1) BACKUP!!!
2) Flash newest recovery linked by the ROM's dev via terminal: su <enter> flash_image recovery /sdcard/aospCWMod-VM670-xxxxxxxx.img <enter>
3) In recovery, wipe cache and dalvik cache, format system and data (formatting is optional if upgrading the same ROM)
4) Flash ROM
5) Flash gapps (not always necessary, but is if you format system and data)

I have only had one install where I had to go back and do something again after following these steps, and that time was due to a corrupt download.

 

[Kreatur3]

Only trouble I've had with rom managers recovery is that it errors when trying to backup my ext partition. For some reason it always fails when trying to flash a recovery through terminal.

Sent from my LG-VM670 using Tapatalk