• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Possibly bricked lg optimus v?

Rc1993 said:
C:\SDK\platform-tools>adb shell
(pressed enter then this came)
- exec ' /system/bin/sh' failed: No such file or directory <2> -
Click to expand...

The adb shell is not executing since you're in the incorrect directory. Assuming Windows 7, try from the DOS command window:

Code: 
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
then:

Code: 
adb shell
if successful, the superuser prompt # would be displayed and ready for more commands. HTH...
 
Figures, I just got your version of the SDK up and running, and you get good advice while I'm gone. ;) For the record, I did have to adjust the directions on the adb webpage, they got the steps close, but not quite right.
 
Snap! After reading tli's post I remembered how to find out the OP's path to the adb.exe., no matter what windows OS he's running. I don't have a PC to remember exactly but you will understand how to get him there brotherswing when I say environmental variables.
 
That was what was wrong in the instructions on the download page. They described the steps wrong. Well, actually, they skipped a step. I didn't bother with the environmental variables, I just navigated to the folder manually and ran from there.
 
What I'm trying to say is that to find his correct path to the adb.exe he needs to go to the environmental variables then select edit? Scroll to "path" select edit? The path should be right there in that narrow window.
 
There's a little window in the box. Scroll to "path" and select it then select edit. A new window should show toward the top of the box. This will have the correct path to adb.exe
I don't have a PC to check this with but it's should be right.
 
That is the correct path. You ought to be able to run adb commands from a command prompt ANYWHERE on your system. If not, try rebooting your PC, then try again.
 
the error you're listing means:
adb is working fine,
the boot.img is intact and working but /system is boogered up.
it is hard to fix.
i forgot from reading the thread, do you get the same error using adb shell after trying to boot into recovery first?
using a linux system or live cd, you can chmod 4755 a copy of busybox on the pc, then
adb remount
then
adb push busybox /system/bin/sh
after that you might be able to use adb shell and continue.
i or someone else can upload busybox binary for you if you want to try that route.
 
When the OP opens a command prompt and types in adb devices with his phone plugged into PC, it gives that long number. This indicates adb is established. Were missing something so ridiculously simple. I just can't see it yet.
 
bigsupersquid said:
the error you're listing means:
adb is working fine,
the boot.img is intact and working but /system is boogered up.
it is hard to fix.
i forgot from reading the thread, do you get the same error using adb shell after trying to boot into recovery first?
using a linux system or live cd, you can chmod 4755 a copy of busybox on the pc, then
adb remount
then
adb push busybox /system/bin/sh
after that you might be able to use adb shell and continue.
i or someone else can upload busybox binary for you if you want to try that route.
Click to expand...
Thanks for jumping in and giving such incredible advice. The OP isn't real phone tech, DOS savy. I'll try to translate if needed and or possible.
 
To the. OP: As per bigsupersquids instructions ; try to reboot into your recovery, then plug phone into PC and try to run the commands in a command prompt.
 
The # indicates you're phone is rooted and adb has been given superuser permission. The rest well have to wait on from bigsupersquid. When he talks you should listen. There's only a handful of members whose knowledge and experience cannot even be measured. He's is one of them.
 
If not, I'll try to translate. I didn't know squat back in May. Everthing I learned I learned on these forums.Especially here.
 
heh, i have problems with simple English.
right now, your blacked-out recovery is the only thing keeping your phone from being a brick. it's dangerous to replace it without fixing the rom first. a bad recovery flash right now would leave you holding an expensive paperweight.
to avoid this, you can temporarily flash a usable recovery into the /boot partition.
Code: 
adb shell
mount /dev/block/mmcblk0p1 /sdcard
flash_image boot /sdcard/vrecovery.img
reboot
you'll hopefully be in a working recovery. until you flash a rom or backup with it, which will overwrite the temporary /boot partition recovery. this recovery will start from a regular boot, no key combination when turning on the phone.
use it immediately to flash a previous backup or a new rom.
once the rom boots you can use flash_image gui or adb or terminal to flash that vrecovery.img to the recovery partition.
the important thing is not to risk borking your adb access until you can boot into a working rom.
@Andy, feel free to translate! :p
 
Hang on, I'm fluent in Linux, I can translate...
bigsupersquid said:
the error you're listing means:
adb is working fine,
the boot.img is intact and working but /system is boogered up.
it is hard to fix.
i forgot from reading the thread, do you get the same error using adb shell after trying to boot into recovery first?
Click to expand...
He says it's going to take doing things you don't understand
bigsupersquid said:
using a linux system or live cd, you can chmod 4755 a copy of busybox on the pc,
Click to expand...
He says go to Ubuntu.com and download the live cd. Burn as normal, then reboot your computer using it. Then type in the cryptic command
Code: 
 chmod 4755
followed by the path (directory path down to the binary)
bigsupersquid said:
then
adb remount
then
adb push busybox /system/bin/sh
Click to expand...
Reboot, without the Ubuntu CD, as these are specific commands you need to run while booted into windows. He's assuming you have a command prompt running. This is where you need to start typing.
bigsupersquid said:
after that you might be able to use adb shell and continue.
i or someone else can upload busybox binary for you if you want to try that route.
Click to expand...
If you can't seem to get the whole CHMOD thing he's offering to supply you with one, ready to be pushed. Sorry,that's about as good as the translations get.
 
bigsupersquid said:
heh, i have problems with simple English.
right now, your blacked-out recovery is the only thing keeping your phone from being a brick. it's dangerous to replace it without fixing the rom first. a bad recovery flash right now would leave you holding an expensive paperweight.
to avoid this, you can temporarily flash a usable recovery into the /boot partition.
Code: 
adb shell
mount /dev/block/mmcblk0p1 /sdcard
flash_image boot /sdcard/vrecovery.img
reboot
you'll hopefully be in a working recovery. until you flash a rom or backup with it, which will overwrite the temporary /boot partition recovery. this recovery will start from a regular boot, no key combination when turning on the phone.
use it immediately to flash a previous backup or a new rom.
once the rom boots you can use flash_image gui or adb or terminal to flash that vrecovery.img to the recovery partition.
the important thing is not to risk borking your adb access until you can boot into a working rom.
@Andy, feel free to translate! :p
Click to expand...


Can you translate this part? I wanna do it right and im sorry for asking to have your posts translated for me @squid

Andalso do I type said commands even with the squiggle line and # there?
 
You got it.
From a command prompt, type this
Code: 
adb shell
mount /dev/block/mmcblk0p1 /sdcard
flash_image boot /sdcard/vrecovery.img
reboot
immediately to flash a previous backup or a new rom.
once the rom boots you can use flash_image gui (hit the android market for this) to flash that vrecovery.img
the important thing is not to risk borking your adb access until you can boot into a working rom.
@Andy, feel free to translate! :p
If you need to, the above code can be copied and pasted into the command prompt. DO NOT REBOOT OR PULL THE BATTERY UNTIL YOU FLASH A NEW ROM. That would put you right back here, but worse.
Sorry for the heavy editing, Squid.
 
You must log in or register to reply here.
Back
Top Bottom