PLEASE NO LINKING OF THESE DOWNLOAD LINKS OR REHOSTING!!! Please direct users to this thread!!!!
This thread is an all in one recovery thread.
Prereqs:
1. You must have a rooted device
2. Adb setup on computer (terminal on phone can be used in place of adb but adb is preferred)
Supported devices:
LG Ally (aloha)
LG Optimus S
LG Optimus V
LG Optimus M
LG Vortex
LG Chic (alessi)
LG Optimus P500, Optimus T P509 (thunderg)
HTC Droid Incredible See link here Xda
LG Shine Plus
Gz'One Commando
Optimus C
HTC Incredible2 (vivow)
HTC Rezound (vigor)
HTC Merge (lexikon)
HTC Thunderbolt (mecha)
HTC EVO 4G (supersonic)
Updates for 3.06:
Recovery and some binaries are recompiled for arm6-vfp or armv7a-neon which on most devices gives a notable increase in speed.
Added gui ability to restore clockwork mod 3x, 4x, & 5x backups.
Added the developer menu: see below for many new features.
Lg devices I figured out the kernel api to reset the FACT_RESET_3 from doing a privacy wipe. This mode will automatically be checked & reset to FACT_RESET_6 so you will not get stuck in recovery.
Added ability to wipe /system & /sdcard
Key mapping on aloha & shine plus now use Vol-up & Vol-dn power and back so keyboard is no longer used.
Removed battery % check from nandroid.
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup to restore
Nand Restore Clockwork : browse to and restore cwn backup
As of 2.2.1 sd-ext is backed up as whole so link2sd users should work fine
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse. (Fixed dir-browsing)
Toggle Signature Verify : Turn of signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe system
Wipe sdcard
Wipe .android secure : Wipes froyo native .android_secure on sdcard
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (requires kernel support for ext4 which all but shine have)
Mounts:
Gui mounts to avoid typing in terminal to mount and cd into a dir to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix Permissions
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Check Battery Lvl
Developer menu:
Make and flash boot from zimage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
I have included flash_eraseall binary to recovery which can be used to fix/erase corrupted partitions that will not mount correctly to nandroid restore to.
Useage from adb shell is : flash_eraseall /dev/mtd/mtd4 (where mtd4 is the number of the partition from "adb shell cat /proc/mtd" you want to erase)
Trouble Shooting:
1. Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log. It should have detailed cause of error.
2. If you get an out of memory error reboot device and do it on a fresh reboot.
3. If you get a file not found on the "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak" skip it and move to the next step as this file will not be in your rom unless it has recieved an ota-update and if so needs to be disabled.
4. Permission denied means you are not root user (#)
5. If rebooting into recovery you get a little android guy with a ! and does not look like picture above you still have stock recovery and did not remove the install-recovery.sh.
6. You did check the md5sum for a match before flashing correct?
Please check all the above issues before posting. This is the format I request to be used for troubleshooting.
Device :
Recovery Version :
Error :
Please upload the recovery.log AS AN ATTACHMENT that you moved to sdcard and read. Posts without this log will be ignored!!!
Please no PM's!!!!!
1. Download and unzip recoveryflash.zip onto sdcard. You should have a folder called recoveryflash on sdcard after unzipping.
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)
3. Reboot phone and wait for sdcard to mount (about 5 - 10 seconds) after you see home screen.
4. Become root user in abd shell or terminal emulator with command without quotes "su" & you should have a # prompt
5. Enter these commands in terminal emulator or adb shell # prompt one at a time and press enter after each line. If anyone has trouble with the 1st line you can also use a root enabled explorer like root explorer or estrongs and copy/paste the recoveryflash.sh into /data/local and then start with the 2nd line.
6. It will automatically install & reboot you into new recovery. Using the script above your old recovery.img was copied to /sdcard/dump-recovery.img. If you had the stock recovery copy that file to a safe place as running the script again will overwrite it.
Old manual way:
Download your device specific recovery and check md5sum for a match before flashing. Download flash_image.zip and unzip it to root of your sdcard. (Not in any folder)
Copy your devices recovery.img to root of sdcard.
Below can be done via adb shell or terminal emulator on phone via root # shell not a $ shell
Note do not type the # or $ as they are for reference only!
Example for LG Ally above would be:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Device specific recovery keys:
Key mapping for Optimus Line & Vortex:
Move up & down = Vol-up & Vol-down
Select = Menu
Backup = Back
Boot recovery from device off: Vol-down + Home + Power and release at LG logo.
Chic(alessi): Vol-up + Vol-down + Power
LG Ally & LG Shine Plus:
Move up & down = Up & down on sliding keyboard | vol-up & vol-dn on 3.06
Select = Enter on keyboard | Power on 3.06
Backup = Vol-down | back on 3.06
Boot recovery Ally: Send + Menu + Power
Boot recovery Shine Plus: Vol-down + Home + Power
Commando:
There is no known way to boot recovery from device powered off. To enter recovery its adb reboot recovery or use many of the apps from market to reboot into recovery. This means that if you flash a bad rom or boot.img you cannot enter recovery to fix and will have to get a new phone. Be carefull!!! You have been warned.
Adb reboot recovery can also be used to boot custom recovery on most devices.
Amon_Ra for his awesome source and a few pointers. His original Source Link Buy him a redbull
Worstenbrood's desire recovery Link
My many testers (too many to name one by one)
Device(s): Lg Velocity(ALLY)/Retired
Samsung Fascinate, TeamHacksung CM9-ICS, Glitch V14beta2 kernel
Carrier: Not Provided
Thanks: 133
Thanked 25 Times in 23 Posts
????
Reserved for future use. Thread still under construction.
__________________
Samsung Fascinate, TeamHacksung's CM9 ICS, Glitch V14 beta3 kernel
Get your own personal Dropbox now!!!! Sync your files online and across computers with Dropbox. 2GB account is free! And get extra free space from referrals http://db.tt/3IsIYJB
Last edited by getitnowmarketing; May 6th, 2011 at 10:16 AM.
doesn't work on the optimus v followed directions to the letter. when reboots go to lg screen flashes then boots to android.
Can you try to do "adb reboot recovery" and try? Perhaps I have the keys to boot wrong. You also removed the install-recovery.sh correct? If still having issues I'll need the exact kernel config from stock. With the most current stock rom can you pull me a kernel config with "adb pull /proc/config.gz" and upload that for me please? I used LG's defconfig for opt V as I didnt have a actual device config handy. There have been issues with bad defconfig files in other LG sources.
This is great that you are making a recovery for the commando. It's been rough these past two weeks running a stock rom after coming from cm7 on my incredible. I'm in the early stages of a rom for the commando now, but had no idea how I was going to get it on my phone when finished.
I had your recovery utility ver. 1.2.5 installed on my Ally. I tried to install 2.2.1 using adb shell and the seven lines of code shown in your original post above.
At the 5th command (the mv line), I received an error message: File not found. I checked the directory, and install-recovery.sh did not exist, so it makes sense that it couldn't be renamed.
At the next line (the flash_image line), all the instructions scrolled up the screen with the message "Out of memory". This makes no sense. There is 20MB free in internal memory.
Please advise how to correct. At the moment, if I boot into Recovery, all I get is a blue screen, and I have to pull the battery to proceed.
I had your recovery utility ver. 1.2.5 installed on my Ally. I tried to install 2.2.1 using adb shell and the seven lines of code shown in your original post above.
At the 5th command (the mv line), I received an error message: File not found. I checked the directory, and install-recovery.sh did not exist, so it makes sense that it couldn't be renamed.
At the next line (the flash_image line), all the instructions scrolled up the screen with the message "Out of memory". This makes no sense. There is 20MB free in internal memory.
Please advise how to correct. At the moment, if I boot into Recovery, all I get is a blue screen, and I have to pull the battery to proceed.
Thanks - sorry - missed the troubleshooting section because it came before the installation instructi
ons.
However....I rebooted, went through the instructions from the top (except for the mv) and am still getting the out of memory error.
That oom error is for virtual mem not actual free space on /data btw. No idea why you get that after fresh reboot. Must have a bad ram leak in an app. If you already have a version of my recovery boot into recovery and type:
Code:
adb shell
mount /sdcard
flash_image recovery /sdcard/recovery-RA-aloha-2.2.1.1-GNM.img
As I mentioned in my first post, when I boot into recovery, I just get a blue screen. If there's any text, it appears as microscopic white specks. Have to pull the battery to boot phone.
As I mentioned in my first post, when I boot into recovery, I just get a blue screen. If there's any text, it appears as microscopic white specks. Have to pull the battery to boot phone.
You aren't still using 2.1 eclair are you? The new one requires you to have froyo. The blue screen is fastboot. You can use the android sdk to flash the recovery via the blue fastboot screen on ally. Command is fastboot flash recovery nameofrecovery.img
Else grab my slightly older 2.2.1 from rom manager which will work on both eclair and froyo.
Last edited by getitnowmarketing; May 11th, 2011 at 10:07 AM.
>>You can use the android sdk to flash the recovery via the blue fastboot screen on ally. <<
Can you give me a few more specifics, please? Here's what I did:
Booted phone to recovery mode. Blue screen (fastboot) appears.
Connected phone to computer via USB.
Computer doesn't recognize the USB device.
Launched adb shell
Error message (after starting daemon): device not found.
Edited a few minutes later:
Adb shell is probably not the right command.
From computer at command prompt, launched fastboot devices. Received error message that AdvWinApi.dll is missing from computer. I'll reinstall SDK.
I'm not having any luck communicating with the phone when it's in fastboot. When I the phone is in fastboot and connected to the computer via USB, the computer says "USB device not recognized", etc. Not a good sign, and I don't know how to install the driver. And then when I issue the command "fastboot devices" from the cmd prompts, the devices don't display. The cursor just comes back at the DOS prompt. There is no error message.
The phone connects to the computer and accepts adb shell commands with no problem if it's not in recovery mode.
Nwh10 no idea why you are having so much trouble use the version in rom manager to make it easy. Fyi if using windows you need fastboot driver I wrote for aloha. Its in original ally recovery thread.
hello guys, i have a little problem, can't restore a 1 day old backup... error " : Verifying backup images... md5sum: WARNING: 1 of 1 computed checksums did -match Error: md5sum mismatch . "
and 1 more question, are the backup done whit the 2.2.1 custom recovery compatible whit the 1.1.0 ?
if using windows you need fastboot driver I wrote for aloha. Its in original ally recovery thread.
Yes, I'm using Windows.
To recap:
From normal phone operation, when I hold down the power button & select Recovery, the phone boots to a blank blue screen with no writing.
Then I connect the phone to the computer.
The computer reports "USB device not recognized."
I replaced the Android SDK I was using with the one contained in the rar. There were slight differences.
Rebooted the computer.
From the blue screen (fastboot) mode & connected to the computer, I have gone to Device Manager and updated the Unknown Device driver by pointing to android_winusb.inf. The computer says the device is already using the best driver.
From a DOS prompt, the fastboot command either waits forever for a device or doesn't find the device.
The path to the directory containing the driver is in the environment variables. The computer has been rebooted several times. The phone has been rebooted to the blue screen several times, and is still not recognized by the computer.
So I guess there's still something wrong between the fastboot driver and the device. What step am I missing to force the device, when in blue screen fastboot & connected to the computer, to be recognized by the computer?
If I can't get past that problem, how can I get around the out of memory error (described upthread) that occurs when I run flash_image from adb shell?
Can you try to do "adb reboot recovery" and try? Perhaps I have the keys to boot wrong. You also removed the install-recovery.sh correct? If still having issues I'll need the exact kernel config from stock. With the most current stock rom can you pull me a kernel config with "adb pull /proc/config.gz" and upload that for me please? I used LG's defconfig for opt V as I didnt have a actual device config handy. There have been issues with bad defconfig files in other LG sources.
As soon as I can get to a computer ill send it my computer is fried. I'm running the optimus v so if someone could pull the file needed and post it it would be a big help.
Last edited by wrath_00; May 13th, 2011 at 02:17 PM.
GNM, just want to report the outcome of the problems I was having. I went to IRC #ally per your PM suggestion, and found a person there who got everything straightened out. It wasn't pretty....he ended up going back to stock rom and moving forward from there. It involved several utilities, forcing a key to write to the registry, and more. But I'm back in business running Velocity 1.1 and your 2.2.1 recovery.
Thanks for your efforts and for pointing me in the right direction.
Okay so tried this on my Optimus V same thing as Wrath00. Using both the key combo and adb reboot recovery it just stalls then boots normally. I have the config.gz file I just need to know where to upload it to be honest. Zipped the config and made it an attachment.
Last edited by chefjw; May 15th, 2011 at 01:29 AM.
Reason: added config
The Following 2 Users Say Thank You to chefjw For This Useful Post:
Okay so tried this on my Optimus V same thing as Wrath00. Using both the key combo and adb reboot recovery it just stalls then boots normally. I have the config.gz file I just need to know where to upload it to be honest. Zipped the config and made it an attachment.
Cool. Thanks maybe when GNM gets a chance he can rework the recovery.
Last edited by wrath_00; May 15th, 2011 at 12:20 PM.
If you could please sir put a sticky with a link to this in the optimus m - all things root. The only way to find this thread over there is to search thru the older methods to find the post with the link.
Okay so I was able to get into recovery once but it locked up and could not makes choices or anything. And now when I go back to adb shell its not letting me SU its saying permission denied. Not sure wth is going on cause I have SU installed and Titanium Backup and have made backups of stuff and installed SetCPU for root
Today i successfully rooted my P500 (with z4root) and installed custom recovery (Custom Recovery P500/Thunderg v1.2). it was late night i stopped here.
when i used the custom recovery for taking back up, i got the menu as mentioned by you with options:
Today i successfully rooted my P500 (with z4root) and installed custom recovery (Custom Recovery P500/Thunderg v1.2). it was late night i stopped here.
when i used the custom recovery for taking back up, i got the menu as mentioned by you with options:
Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 442 Times in 289 Posts
Has anyone playing around with 2.2.2 on the ally noticed Amonra recovery 2.2.1 will not stick? I can flash it, and boot into Amonra but after I reboot it goes back to Verizon's stock recovery and I must flash Amonra again to use it, then it goes back to Verizon's stock recovery again on the next reboot.
**Edit** the phone boots up into 2.2.2 fine but when I try to go back into recovery its always Verizon's unless i reinstall Amonra before reboot.
Last edited by dautley; May 22nd, 2011 at 09:47 AM.
Reason: more info
Thats an old version please use the one listed on downloads in this thread. You want version 2.2.1
When tried to install V 2.2.1 with the following commands:
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
/sdcard/flash_image: No such file or directory
I got the above error "no file....", but in fact the flash_image was there in the sd card. what may be problem
Before using V2.2.1 should i uninstall older version or upgrade. I did not do this in the above case. If i have to uninstall upgrade, how should i do it. Pls help me.
Battery is more than 60%
Free space of about 1GB on sd card
Last edited by santhoshs; May 22nd, 2011 at 10:55 AM.
Reason: to add last two lines
Has anyone playing around with 2.2.2 on the ally noticed Amonra recovery 2.2.1 will not stick? I can flash it, and boot into Amonra but after I reboot it goes back to Verizon's stock recovery and I must flash Amonra again to use it, then it goes back to Verizon's stock recovery again on the next reboot.
**Edit** the phone boots up into 2.2.2 fine but when I try to go back into recovery its always Verizon's unless i reinstall Amonra before reboot.
You must remove install-recovery.sh as per directions.
Quote:
Originally Posted by santhoshs
When tried to install V 2.2.1 with the following commands:
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
/sdcard/flash_image: No such file or directory
I got the above error "no file....", but in fact the flash_image was there in the sd card. what may be problem
Before using V2.2.1 should i uninstall older version or upgrade. I did not do this in the above case. If i have to uninstall upgrade, how should i do it. Pls help me.
Battery is more than 60%
Free space of about 1GB on sd card
You must unzip flash_image.zip into root directory of sdcard (not in any folder)
The Following User Says Thank You to getitnowmarketing For This Useful Post:
May I know is it the same method for me to update my custom recovery ? And how to check my current version of custom recovery ? Newbie here. Anyway, Big thank first
You must remove install-recovery.sh as per directions.
You must unzip flash_image.zip into root directory of sdcard (not in any folder)
Yes i ensured that the file is unzipped and the file was present at the root directory of sd card.
I had no issues when i first rooted and installed the custom recovery. Today i tried to install the same V 1.2, i got the same error. Is it because the flash_image file is already present in the bin.?
I am attaching the pics of root dir, battery level, free space availibility and the commands used by me to install V 2.2.1. I have also attached the recovery log file.
i got error msg after second line of command.
V2.2.1 was not intalled.
Pls let me know the solution.
Last edited by santhoshs; May 25th, 2011 at 11:05 AM.
Reason: addnl input and file attachments
Device(s): LG Optimus V, Palm Treo 700 p (oh, Android only? Sorry...)
Carrier: Not Provided
Thanks: 179
Thanked 12 Times in 6 Posts
I'm having the same problem on my LG Optimus V, as well. I didn't have any trouble while following the directions. (I didn't have the install-recovery.sh file to delete.)
But when I try to boot to Recovery, I get just a black screen after the LG logo. If I keep holding the buttons, it usually reboots again into the normal mode. If I let go, it seems to just stay on a black screen until I pull the battery.
I guess I should have read the whole thread before trying. (I also should have grabbed a copy of my oren stock recovery to fall back on.)
Out of curiosity, what is the difference between the stock flash_image and the provided replacement?
I'm having the same problem on my LG Optimus V, as well. I didn't have any trouble while following the directions. (I didn't have the install-recovery.sh file to delete.)
But when I try to boot to Recovery, I get just a black screen after the LG logo. If I keep holding the buttons, it usually reboots again into the normal mode. If I let go, it seems to just stay on a black screen until I pull the battery.
I guess I should have read the whole thread before trying. (I also should have grabbed a copy of my oren stock recovery to fall back on.)
Out of curiosity, what is the difference between the stock flash_image and the provided replacement?
More options. With this recovery your able to flash roms stock you can't. I tried the optimus s version on the optimus v and worked just the home and menu buttons are switched maybe try that one untill the optimus v version is fixed.
Last edited by wrath_00; May 26th, 2011 at 09:39 PM.
Device(s): LG Optimus V, Palm Treo 700 p (oh, Android only? Sorry...)
Carrier: Not Provided
Thanks: 179
Thanked 12 Times in 6 Posts
Quote:
Originally Posted by wrath_00
More options. With this recovery your able to flash roms stock you can't.
Yeah, I've learned the difference between the recovery images themselves. I was wondering what the difference is between the versions of the "flash_image" program itself (between the one that is already in /system/bin/ and the one we download and overwrite it with).
I did find another Recovery .img that worked for me. It identifies itself as "RA-thunderc-1.1.0-GNM". So, thanks GNM! (Yes, the menu and home keys appear to be switched.)
So i believe i followed everything correctly (but since im having trouble apparently i havent. lol)
I have an LG Optimus V
so i type everything in the command prompt and when i enter the line where you type in the recovery image name i get the following:
usage: flash_image partition file.img
then when i type in sync.
from this point i expected it to reboot automatically but nothing happened. So i fiddle around with my phone, turning it off, and pushing the home volume down and power button simultaneuously, but i cannot boot into recovery mode.
So i believe i followed everything correctly (but since im having trouble apparently i havent. lol)
I have an LG Optimus V
so i type everything in the command prompt and when i enter the line where you type in the recovery image name i get the following:
usage: flash_image partition file.img
then when i type in sync.
from this point i expected it to reboot automatically but nothing happened. So i fiddle around with my phone, turning it off, and pushing the home volume down and power button simultaneuously, but i cannot boot into recovery mode.
any suggestions?
If your using the optimus v version its not working yet as far as I know. I'm using the optimus s version. The home and menu buttons are swapped but no big deal. Are you switching from stock or a custom recovery?
Last edited by wrath_00; May 31st, 2011 at 10:26 AM.
Device(s): HTC EVO 4-g, running EVOlvedROM r3chargeD.
Carrier: Not Provided
Thanks: 13
Thanked 14 Times in 13 Posts
Quote:
Originally Posted by getitnowmarketing
PLEASE NO LINKING OF THESE DOWNLOAD LINKS OR REHOSTING!!! Please direct users to this thread!!!!
This thread is an all in one recovery thread.
Prereqs:
1. You must have a rooted device
2. Adb setup on computer (terminal on phone can be used in place of adb but adb is preferred)
3. Phone charged 30% or greater is required to use nandroid.
Supported devices:
LG Ally (aloha)
LG Optimus S
LG Optimus V
LG Optimus M
LG Vortex
LG Chic (alessi)
LG Optimus P500, Optimus T P509 (thunderg)
HTC Droid Incredible See link here Xda
LG Shine Plus
Gz'One Commando (in testing)
USB-MS Toggle :mounts sdcard as mass storage
(dinc only) mount /Emmc
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup to restore
As of 2.2.1 sd-ext is backed up as whole so link2sd users should work fine
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse. (Fixed dir-browsing)
Flash Zip From Emmc (Dinc only)
Toggle Signature Verify : Turn of signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe .android secure : Wipes froyo native .android_secure on sdcard
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (requires kernel support for ext4 which all but shine have)
Mounts:
Gui mounts to avoid typing in terminal to mount and cd into a dir to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix apk uid mismatches
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Wipe Sdcard
(Dinc only)
Format /data as ext3 | ext4 : format(reformat) /data between ext3,ext4. (This wipes /data also) Requires modification of init.inc.rc & and compatible rom kernel see dinc thread link above
I have included flash_eraseall binary to recovery which can be used to fix/erase corrupted partitions that will not mount correctly to nandroid restore to.
Useage from adb shell is : flash_eraseall /dev/mtd/mtd4 (where mtd4 is the number of the partition from "adb shell cat /proc/mtd" you want to erase)
Trouble Shooting:
1. Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log. It should have detailed cause of error.
2. If you get an out of memory error reboot device and do it on a fresh reboot.
3. If you get a file not found on the "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak" skip it and move to the next step as this file will not be in your rom unless it has recieved an ota-update and if so needs to be disabled.
4. Permission denied means you are not root user (#)
5. If rebooting into recovery you get a little android guy with a ! and does not look like picture above you still have stock recovery and did not remove the install-recovery.sh.
6. You did check the md5sum for a match before flashing correct?
Please check all the above issues before posting. This is the format I request to be used for troubleshooting.
Device :
Recovery Version :
Error :
Please upload the recovery.log AS AN ATTACHMENT that you moved to sdcard and read. Posts without this log will be ignored!!!
Please no PM's!!!!!
Download your device specific recovery and check md5sum for a match before flashing. Download flash_image.zip and unzip it to root of your sdcard. (Not in any folder)
Copy your devices recovery.img to root of sdcard.
Below can be done via adb shell or terminal emulator on phone via root # shell not a $ shell
Note do not type the # or $ as they are for reference only!
Example for LG Ally above would be:
mount -o remount,rw -t yaffs2 dev/block/mtdblock4 /system
Device specific recovery keys:
Key mapping for Optimus Line & Vortex:
Move up & down = Vol-up & Vol-down
Select = Menu
Backup = Back
Boot recovery from device off: Vol-down + Home + Power and release at LG logo.
Chic(alessi): Vol-up + Vol-down + Power
LG Ally & LG Shine Plus:
Move up & down = Up & down on sliding keyboard
Select = Enter on keyboard
Backup = Vol-down
Boot recovery Ally: Send + Menu + Power
Boot recovery Shine Plus: Vol-down + Home + Power
Adb reboot recovery can also be used to boot custom recovery on most devices.
WARNINGS:
Do not flash a radio.img
Do not factory reset your device via Android OS. Use wipe in recovery.
Amon_Ra for his awesome source and a few pointers. His original Source Link Buy him a redbull
Worstenbrood's desire recovery Link
My many testers (too many to name one by one)
doesn't work on the optimus v followed directions to the letter. when reboots go to lg screen flashes then boots to android.
I'm having the same issue, theres no way to get any files on or off of it, adb wont work because my computer no longer recognizes my phone when i plug it in,, recovery doesnt work because i can no longer boot to recovery ( even with key combo) just keeps booting to android screen and thats it,, i have vortex as well...
Optimus V has a comfirmed bug in it and I have not yet had time to investigate the cause of it. For now optimus v users please use the Optimus S recovery.
Optimus V has a comfirmed bug in it and I have not yet had time to investigate the cause of it. For now optimus v users please use the Optimus S recovery.
I'm having the same issue, theres no way to get any files on or off of it, adb wont work because my computer no longer recognizes my phone when i plug it in,, recovery doesnt work because i can no longer boot to recovery ( even with key combo) just keeps booting to android screen and thats it,, i have vortex as well...
Optimus V and Vortex are not the same and not interchangeable and if you flashed optimus v to vortex thats a recovery that has a bug in it. I would suggest restoring your phone via LGNPST and then flashing the correct recovery to it.
2Likes
All In One Recovery Thread
