All In One Recovery Thread

Never mind

Sorry if it's a dumb question, but in the first post:

getitnowmarketing said:

2. Place the recovery.img you downloaded in this folder in /sdcard/recoveryflash and then turn off sdcard as mass storage . (Do not rename the recovery.img from the download)

Click to expand...

But I can't find recovery.img anywhere? Am I doing something wrong? Or does he mean recovery-ra-allessi-3.06-gnm.img (for lge720/allessi).

Thanks in advance

I ammuse your 'yes' reffers to my last sentence? haha.
Thanks for the answer

BlitzAuto said:

A few questions for GNM or anyone that REALLY knows.
Please forgive my noobness.

After reading this thread (and a few others), I'm a bit confused as to exactly which recovery file(s) I need to download and use?

I have an Optimus M (LGMS690).
Android 2.2.1
It is rooted.

If I use home+volume down+power on buttons, it will boot into a recovery mode with a box & arrow and android image. Whenever I do that, it seems to reset the phone to stock and I lose all my downloaded apps (do i assume this is normal?).
Is this the stock recovery and, is it good or bad?
It doesn't bring up the options that you guys speak of here but rather just the home screen.

Also, I have found a program on the market called "Flash Image GUI" that claims to work on the Optimus series phones, does anyone know of this program?

I also have read NOT to use the ROM Manager & CWM, is this true or false?
I have downloaded it but the Optimus M is not in the list so I'm afraid to try it's flash recovery.

Should the Android 2.2.1 be updated to a newer version?

Any help is greatly appreciated as I do not want to brick it.

Click to expand...

Yes that was stock recovery, performing a factory reset. I don't have an Optimus M so how CWM works on it.

You need the optimus m recovery which the OP lists.

Nevermind

Apparently I'm the dumbest MF'r here cause I just don't understand all this.

So I followed step by step. After prompts it said recovery installed and would boot into recovery in 5 seconds but never does anything else. Doesn't freeze or anything. I've even tried booting from power off with the instructions given but still no luck..am I missing something somewhere? Help!

So I am stuck at "Place the recovery.img you downloaded in this folder"

Not sure where to get the recovery.img? If anyone can help guide me to the recovery.img for the lg vortex, that would be great...

Mac

Edit: For those of you stuck at this part, I just googled "recovery-RA-vortex-2.2.1-gnm.img" and found my recovery.img for the vortex. If you have something other than the vortex just replace the your phones name where vortex and you will probably find a download for you supported device. May be there is a link in the OP, but I could not find it.

After finding the recovery.img, the adb commands worked like a charm.

Okay, I'm on CM7 and I cannot flash any other rom. This recovery uses AMEND scripting and not EDIFY?

Any help would be appreciated.

Vortex. On 2,2

getitnowmarketing said:

Mike what device? Vlad it uses both amend and edify.

Click to expand...

Well, when trying to flash from cm7 to any other rom it tells me about how AMEND scripting was cancelled in 1.5 and to use EDIFY scripting. Then "installation aborted"

What exactly am I missing here?

So I have read and re-read the directions and tried everything it says multiple times. Basically I do not have a install-recovery.sh file on my commando and it still gives me the android guy with the exclamation point when I log on. I have entered all the code correctly, looked for the file as was instructed and it is not there. Please help me on this one.

Hi how to make WIPE boot in AmonRA 3.0.6

every time I try to perform a NAND backup the recovery reboots back into normal mode; it does that at seemingly random times during the backup. It also reboots to normal at any other random time; when I am just sitting in the recovery menu, when I am trying to boot into recovery it may begin to load but then reset. Very very unstable for me:

The last attempt into recovery mode I moved the recovery.log to the SD card; that was successful. Then I tried to do a backup and then it rebooted. Below is the log starting from moving the recovery.log:

Device : LG Optimus V model number VM670
Recovery Version : recovery-RA-optV-2.2.1-GNM.img
Error :

Move recovery.log to SD
Press Menu to confirm,
any other key to abort.

Moving : ./sbin/um: line 3: can't create /sys/devices/platform/msm_hsusb/gadget/lun0/file: nonexistent directory

Click to expand...

Trying to attach "recovery.log" resulted in 'invalid file' error so I changed the file to "recovery.txt".



EDIT: Ok...let me be the first to admit that I have terrible reading comprehension sometimes. I tried using the Optimus S recovery that was recommended due to an optimus V bug; that worked great and I good to go.

Capslock118 said:

every time I try to perform a NAND backup the recovery reboots back into normal mode; it does that at seemingly random times during the backup. It also reboots to normal at any other random time; when I am just sitting in the recovery menu, when I am trying to boot into recovery it may begin to load but then reset. Very very unstable for me:

The last attempt into recovery mode I moved the recovery.log to the SD card; that was successful. Then I tried to do a backup and then it rebooted. Below is the log starting from moving the recovery.log:

Device : LG Optimus V model number VM670
Recovery Version : recovery-RA-optV-2.2.1-GNM.img
Error :


Trying to attach "recovery.log" resulted in 'invalid file' error so I changed the file to "recovery.txt".



EDIT: Ok...let me be the first to admit that I have terrible reading comprehension sometimes. I tried using the Optimus S recovery that was recommended due to an optimus V bug; that worked great and I good to go.

Click to expand...

That is the recovery that has a bug in it, the new one (download link is right below the link for the older version), the RA-OptV 3.0.6 is the one that I have and is very stable. It is the only one that has worked on my phone, but the menu key is what you use to select whatever you to do in Recovery.
In fact I just used it to reinstall the Bumblebee ROM, with a cleaner install then with CWM 5.

I have 2.2.2 android on my optimus V virgin mobile rooted with gingerbreak1.2 . I went thru the steps to try and put Amons on .There was no install-recovery.sh on my phone . the first command didn't work so i manually put that recoveryflash.sh into /data/local and then started with the 2nd line .it did nothing then the third line there was a whole bunch of stuff i could not read and the phone rebooted . i now had a stock recovery just as before except now i have this recovery screen in blue :

Android system recovery <3e>

Android system recovery utility

reboot system now
apply sd-card:update.zip
wipe data/factory reset
wipe cache partition


and i have the green android with a triangle with a ! in the middle and in yellow below that says Android system recovery...
then under that do not pull out the battery!!

What now ?
I know that my device has the old screen and not the hatichi .
i can reboot and phone powers up normally .. the reason i need Amons is to downgrade to 2.2.1 because no data on 2.2.2 . help please . I am stupid with linux .


edit one more thing .. in your device system path you said Optimus V: /dev/block/mtdblock5
Mine is /dev/block/mtdblock6 and also i have NO recovery.log on my phone ..

I have used Amons ra oneclick on my eris but it was a lot easier that this optimus v because it actually worked . I have searched till i have vertigo and want to commit suicide

well problem solved . got up with a tech3 at vm and they are overnighting me a new phone . see ya later ..BTW i have the direct number for tier three support at Vm if anyone interested.
Oh rather than unrooting i just stuck the stun gun to her . jK .

Hi. I have been lurking on this post for some time reading, re-reading. Thinking and wondering. SORRY.

I have the Casio GZ'one Commando running GingerBread 2.3.3 OTA. It is a replacement for a mistake I made in modifying the framework-res .xml's which caused me to bootloop with no way back.

My question is... If I install this recovery, will it enable me to rescue my phone from a bootloop situation?

Specifically, I have set up some themeing options using UOT kitchen that I would like to install. But I'm scared to death of the changes to framework-res.apk and SystemUI.apk causing a bootloop that I cannot recover from.

I understand the idea of a backup as I have rooted all of my Android phones and used a recovery on them all to recover from errors that I made. However, with no way of booting into recovery using hard keys, I'm wondering if installing this recovery is even worth my while.

I DO NOT plan on swapping out kernals, radios, or build props. My only plans are to change framework-res.apk and SystemUI.apk files for themeing purposes. ( I HATE the stock colors in GingerBread!!! )

Any help or advice on this is GREATLY appreciated. THANK YOU

Thnx... I got new RaTunderg 3.0.6

GeneRs said:

Hi. I have been lurking on this post for some time reading, re-reading. Thinking and wondering. SORRY.

I have the Casio GZ'one Commando running GingerBread 2.3.3 OTA. It is a replacement for a mistake I made in modifying the framework-res .xml's which caused me to bootloop with no way back.

My question is... If I install this recovery, will it enable me to rescue my phone from a bootloop situation?

Specifically, I have set up some themeing options using UOT kitchen that I would like to install. But I'm scared to death of the changes to framework-res.apk and SystemUI.apk causing a bootloop that I cannot recover from.

I understand the idea of a backup as I have rooted all of my Android phones and used a recovery on them all to recover from errors that I made. However, with no way of booting into recovery using hard keys, I'm wondering if installing this recovery is even worth my while.

I DO NOT plan on swapping out kernals, radios, or build props. My only plans are to change framework-res.apk and SystemUI.apk files for themeing purposes. ( I HATE the stock colors in GingerBread!!! )

Any help or advice on this is GREATLY appreciated. THANK YOU

Click to expand...

Assuming you've been lurking around my thread as well, I can inform you that i've used adb to call recovery at least once while modifying the framework-res.apk and other associated files beyond the UOT kitchen. Nothing from the kitchen however caused my bootloops. If you are just using the kitchen you are fine, as none of the mods on there have caused bootloops. However if you are going further into modifying them, you are still relatively safe if you have the recovery installed. I've never had to do an adb wait-for-device reboot recovery because i always had time and it failed during the last part of the boot.

Bottom line. get it. it will save your phone. and since there is no way of hardbooting into recovery this helps even more because without it, you wont have a chance at all.

I switched go launcher to a system app which funked everything up, caused boot loop. I used adb wait for device reboot recovery and saved my day.

When you say "2. Place the recovery.img you downloaded in this folder in /sdcard/recoveryflash and then turn off sdcard as mass storage."

What exactly do you mean? Where is the recovery.img file?