ARCHIVED: [Custom Recovery] Optimus S/ Thunderc-sprint

[sammyesb]

i figured it out guys! I found the drivers at this link:

Index of /zefie/files/cell/LG670/drivers - Mystic Midnight Files

also i figured you need to install super user on the andriod phone to get the su command to work...

I hope this will help newbies like myself who missed those steps

 

[dvine1]

I finally got the recovery file to install correctly around midnight! I got ao excited I passed (went to sleep... probably was the rum cake!). Anyway thanks to everyone for your help. Now I can't wait for all the custom roms to start showing up......!

 

[ericizzy1]

anyone plans to do a one click install for this?
that would be greatly appreciated. thank you

 

[drellisdee]

anyone plans to do a one click install for this?
that would be greatly appreciated. thank you

I prefer that you don't. For one its good to understand terminal commands if you are tinkering with your phone. Also, when people make such apps and .bat files and I issue an update on recovery many people end up using the older version embedded in it and miss important bug fixes etc.

 

[watters33]

i had same thing but was able to use su

so first u do adb shell
that takes u to $
then type su and press enter
it should change to #

question, any idea why when I go to adb shell it gives me the $ sign but when I enter su to change to # it says denied??

 

[drellisdee]

question, any idea why when I go to adb shell it gives me the $ sign but when I enter su to change to # it says denied??

Either you aren't rooted or if rooted haven't allowed permissons for adb shell in superuser.

 

[LoganShepp]

so i've done everything perfectly, yet i dont get the custom recovery screen, please help =[

 

[fortyhands]

I think I bricked my phone...

Hey guys,

I followed the instructions in the original post (I think so, at least) - rooted my phone and then moved the additional image files to the rot of the SD card and then attempted recovery mode using the new image...

...now all I get is the LG logo. Sometimes it will flash on and off a few times, but nothing more.

Recovery button combo no longer works and ADB shell is not available.

Can anyone lend some advice? Would be much appreciated.

I will continue to plunk away on this and see if I can fix the issue and report back if I manage to resolve this.

Thanks in advance.

 

[watters33]

any idea why when I go to adb shell I get the $ and when I do what the post says and enter su it tells me permission denied????

 

[watters33]

Either you aren't rooted or if rooted haven't allowed permissons for adb shell in superuser.

I am rooted and think I have permissions for adb shell, I'm still kinda new to this so any help would be appreciated

 

[drellisdee]

Hey guys,

I followed the instructions in the original post (I think so, at least) - rooted my phone and then moved the additional image files to the rot of the SD card and then attempted recovery mode using the new image...

...now all I get is the LG logo. Sometimes it will flash on and off a few times, but nothing more.

Recovery button combo no longer works and ADB shell is not available.

Can anyone lend some advice? Would be much appreciated.

I will continue to plunk away on this and see if I can fix the issue and report back if I manage to resolve this.

Thanks in advance.

Sounds like you didn't remove the install-recovery.sh.

 

[drellisdee]

New version

Need a tester for this new recovery version before I roll it out for all the optimus line as the recovery binary is shared across all of them. Please post feedback.

changelog: v1.2.0
Allow flashing of zips from directories like clockwork does.
Updated wipe menu and is no longer using script to wipe.
updated kernel to allow ext3 & ext4 formatting in recovery.
changed some sd-ext stuff for better apps2sd ability.

Link pulled

md5 1a455af64abed8bf9d3e49d932f3fd38

As always please verify md5sum before flashing.

follow 1st post instructions to flash but change this line as the recovery name is different

flash_image recovery /sdcard/recovery-thunderc-s-RA-1.2-GNM.img

 

[zefie]

Need a tester for this new recovery version before I roll it out for all the optimus line as the recovery binary is shared across all of them. Please post feedback.

changelog: v1.2.0
Allow flashing of zips from directories like clockwork does.
Updated wipe menu and is no longer using script to wipe.
updated kernel to allow ext3 & ext4 formatting in recovery.
changed some sd-ext stuff for better apps2sd ability.

Download recovery-thunderc-s-RA-1.2-GNM.img.zip

md5 1a455af64abed8bf9d3e49d932f3fd38

As always please verify md5sum before flashing.

follow 1st post instructions to flash but change this line as the recovery name is different

flash_image recovery /sdcard/recovery-thunderc-s-RA-1.2-GNM.img

Oh idk if this addresses it or not but there was a strange bug on 1.1.0 where if you chose "wipe .android_secure" you had to confirm twice, and it would say done twice. Oddly once with a period, and once with an exclamation mark. Perhaps that was the script?-

Also can you please add the "format system" option clockwork has? For some reason if the MTD partition gets so screwed up that it cannot be mounted, nandroid fails. The only way to restore it is to format it using recovery. If system gets foobar'd, it'd be nice to have the format option. Perhaps put it under "Other" so people don't hit it accidently, idk.

I'll give this one a try.

Edit: For some reason each submenu says "press VOL-DOWN to return" instead of "press BACK to return". the keys themselves however function as intended.

 

[drellisdee]

This one should have the vol-down fixed

Download recovery-thunderc-s-RA-v1.2-GNM.img.zip fixed

md5 154f1b8f73c02d0d1ccad4b6e5ec3562

 

[LoganShepp]

so i cant get the custom recovery to load, and now im getting an "invalid length" error after the second line of code

 

[mfldmike]

Ok...quick question for you.

I'm just curious as to why flashing a radio would potentially brick our phone using this recovery?

Also, is it possible that an update to the recovery would be able to allow us to "eventually" flash a radio?

 

[dishe]

The only backup you need is the very first one called nand backup. The others are for people who are using ext partitions on their SD for data and apps or people who may be running CM stuff and need to backup gaps due to the proprietary crap and CM not allowed to include them.

backing up nand will grab everything in system and everything in data.

Ok, forgive me if this has already been answered (trying to make sure I understand it all) but I've got a couple of questions here:

Backing up the NAND will back up all your apps and data from the main memory, correct?

But you still can't restore apps from a different rom to a new one, correct? This is just so that you can put everything back the way it was before if you change your mind? Can we save app data to restore onto a new rom?

Also, what about apps that are stored on your SD card, and their data? Can that be recovered into a new rom?
I know a lot of this is really Android 101 and not much to do with the Optimus in particular... did some searching on the forum and finding a lack of stickies on the subject, really.

 

[foolforfood]

Can somebody help me please? When I follow the instructions in the first post (I'm trying to upgrade to the newer version) this is what I get.

mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory

I don't know where install-recovery.sh is can somebody help me finish this please? Thanks in advance!

 

[drellisdee]

Can somebody help me please? When I follow the instructions in the first post (I'm trying to upgrade to the newer version) this is what I get.

mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory

I don't know where install-recovery.sh is can somebody help me finish this please? Thanks in advance!

If its there it needs to be renamed/removed as per that command if its not move on.

 

[foolforfood]

So do I need to rename it as install-recovery.sh or leave it as .sh.bak?