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

[jayej8]

What is the stat of your phone? Is it booted up normally, or are you in recovery (Home + Vol- + Power)?

If you are in recovery, then you need to run the mount command before you can cat anything over to it.

If you are in normal android, then you need to remount the /system partition before you can write to it because it is mounted as read only

mount -o rw,remount /system

Im in normal android, and i do this step "mount -o rw,remount /system" and it works. then i do " cat /sdcard/flash_image > /system/bin/flash_image" and it says "/sdcard/flash_image:invalid legth" idk what to do.

 

[mercrapper]

Im in normal android, and i do this step "mount -o rw,remount /system" and it works. then i do " cat /sdcard/flash_image > /system/bin/flash_image" and it says "/sdcard/flash_image:invalid legth" idk what to do.

what do you get when you do

ls /sdard/flash_image

If the file does not exist, then yes, you have to unzip the file you go and put flash_image in the root of your sdcard

 

[jayej8]

what do you get when you do

ls /sdard/flash_image

If the file does not exist, then yes, you have to unzip the file you go and put flash_image in the root of your sdcard

Ok. Thanks, that worked. But now im getting stuck at

mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

when i type that in i get "no such file or directory"

whats wrong now?

 

[debh945]

Ok. Thanks, that worked. But now im getting stuck at

mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

when i type that in i get "no such file or directory"

whats wrong now?

Nothing's wrong. Ignore it and continue with the next command.

 

[jayej8]

I did it. now my screen is stuck with a "!" inside a triangle with a android under it. what do i do?

 

[jayej8]

my android system recovery say " android sytem recovery <3> is that supposed to be there?

 

[ichihollow]

Nothing's wrong. Ignore it and continue with the next command.

ONLY IF YOUR COMING OFF OF/UPGRADING ANOTHER RECOVERY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

my android system recovery say " android sytem recovery <3> is that supposed to be there?

AND THIS IS WHY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

now you get to follow the guide for how to unbrick a phone...

 

[jayej8]

ONLY IF YOUR COMING OFF OF/UPGRADING ANOTHER RECOVERY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



AND THIS IS WHY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

now you get to follow the guide for how to unbrick a phone...

its not bricked (thank god) but i dont think i got the custom recovery in...any idea whats wrong?

 

[ichihollow]

mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

this line is meant to hide the file that automatically restores the stock recovery should anything happen to it, if AND ONLY IF your coming off of another custom recovery or your upgrading your existing custom recovery this code line is not needed as it's already been done during the installation of the previous custom recovery.

if your phone is not bricked and you can boot into it, i'd just try again.

 

[debh945]

ONLY IF YOUR COMING OFF OF/UPGRADING ANOTHER RECOVERY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



AND THIS IS WHY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

now you get to follow the guide for how to unbrick a phone...

ichihollow - I had the same error when I FIRST INSTALLED custom recovery (NOT UPGRADING or SWITCHING from other custom recovery) and relied on the information below:

Keep going. The move command is to rename the file. It's saying the file doesn't exist so you cant rename it. You're fine.

When this phone came out some had a file called install-recovery.sh while others didnt. This command was added because if those that did have the file didnt rename it (move command) then after they boot into recovery the first time it would return to stock recovery.

No scary warning about BRICKING my phone, just that custom recovery would not be installed if this file wasn't renamed.

I was just replying to his issue as about 50 other people have in this same thread but I didn't give the full explanation of why he received the error. My bad on that part. Really no need to make me feel like an idiot.

I'll go back to lurking and stop trying to help people since you seem to have it all under control here.

 

[ichihollow]

ichihollow - I had the same error when I FIRST INSTALLED custom recovery (NOT UPGRADING or SWITCHING from other custom recovery) and relied on the information below:



No scary warning about BRICKING my phone, just that custom recovery would not be installed if this file wasn't renamed.

I was just replying to his issue as about 50 other people have in this same thread but I didn't give the full explanation of why he received the error. My bad on that part. Really no need to make me feel like an idiot.

I'll go back to lurking and stop trying to help people since you seem to have it all under control here.

lol sorry, not trying to make you feel like an idiot, just jumped a bit i guess. the more the merrier. Its been a while since that was posted and i'm not used to seeing it in the context of first installs. Anyways keep on keeping on, sorry for being rude.

 

[jayej8]

I am not uprgading my recovery. Its my VERY FIRST TIME installing a custom recovery. So im kind of confused now..... What do i do then? Ignore the response from that certain command and enter the following, or what do i do?

 

[jayej8]

I tried again and it still went to Android Recovery <3e>. whats wrong!?!?

 

[pcubed]

I tried again and it still went to Android Recovery <3e>. whats wrong!?!?

Can you try to outline all the steps you've taken up to this point? What commands did you type? Where are you typing them into? Is you phone in the USB debugging mode, etc.?

 

[jayej8]

Can you try to outline all the steps you've taken up to this point? What commands did you type? Where are you typing them into? Is you phone in the USB debugging mode, etc.?

I went through all the steps but instead of typing in "# cat /sdcard/flash_image > /system/bin/flash_image" i type in " ls /sdcard/flash_image" then "> /system/bin/flash_image" thats because the "cat"one doesnt work for me for some reason. and my USB debugging mode is on. but other than that step, i do every other step word for word.

 

[sfhub]

I went through all the steps but instead of typing in "# cat /sdcard/flash_image > /system/bin/flash_image" i type in " ls /sdcard/flash_image" then "> /system/bin/flash_image" thats because the "cat"one doesnt work for me for some reason. and my USB debugging mode is on. but other than that step, i do every other step word for word.

You really need to examine the results of each step and not just type things in blindly from one step to the next.

try typing in the "cat" command without the "#"

cat /sdcard/flash_image > /system/bin/flash_image

If that doesn't work, stop there, do not continue. You need to figure out why that failed first as the subsequent steps depend on this command working.

If it works, then continue with the instructions after the "cat" command.

 

[jayej8]

My mistake. I put in the "#" above. Ignore that. But i do the "cat" command and it says "/sdcard/flash_image:invalid length". Idk what might be the problem...

 

[pcubed]

My mistake. I put in the "#" above. Ignore that. But i do the "cat" command and it says "/sdcard/flash_image:invalid length". Idk what might be the problem...

It seems like your problem might have been solved by mercrapper from a previous post...Did you take these steps?

what do you get when you do

ls /sdard/flash_image

If the file does not exist, then yes, you have to unzip the file you go and put flash_image in the root of your sdcard

 

[jayej8]

It seems like your problem might have been solved by mercrapper from a previous post...Did you take these steps?

Yes, i did the "ls" step. And the rest of the commands went through, but no custom recovery. When it reboots recovery, android system recovery <3e> comes up.

 

[pcubed]

Yes, i did the "ls" step. And the rest of the commands went through, but no custom recovery. When it reboots recovery, android system recovery <3e> comes up.

The "ls" step is not part of the process to getting the custom recovery to go through. It's to check to see if your flash_image is present. Since you were getting the "invalid length" message, you should use the "ls" step to see what that says to see if you need to place the flash_image file onto your SD card...