Phone bricked, can't adb, please help

mrp_bbs

Member
Feb 20, 2011
5
2
0
Visit site
I rooted the optimus V, flashed thunderc custom recovery, and then did a wipe through Privacy, now the phone stuck in recovery menu. I tried reflashing and restore NAND, but did not work and still boots into the same screen.

I know this can be fixed by unrooting the phone, flashing with the stock recovery, however I can not get to adb shell through USB connection. I think I have turned the USB debugging off before I did the wipe. I am wondering is there any way to get to adb shell in this situation?

Thanks in advance!!
 

mrp_bbs

Member
Feb 20, 2011
5
2
0
Visit site
I did wipe everything and tried restore, I also tried to flash a new Rom. Both restore and rom flashing were completed, but the phone only booted to the custom recovery menu after reboot.
This was reported in the Optimus S forum as a brick warning not to do Privacy wipe after installing custom recovery. Seems the only way to fix is to flash with stock recovery. But with USB debugging turned off, SuperOneClick can not recognize the phone, I don't know if there is any other way to get to adb shell...
 

spawn50

Member
Feb 12, 2011
9
2
0
Visit site
made the same mistake. Any way you don't have to use superoneclick to do temp root when you can boot into custom recovery because the phone is all ready rooted. That's why you can wipe everything in custom recovery.

There is a thread that shows you how to go back to mostly stock.
 

manormortal

Member
Mar 1, 2011
14
0
0
Visit site
made the same mistake. Any way you don't have to use superoneclick to do temp root when you can boot into custom recovery because the phone is all ready rooted. That's why you can wipe everything in custom recovery.

There is a thread that shows you how to go back to mostly stock.

im getting this error when i try to nand restore: run nandroid-mobile.shrestore vai adb but i can't get my device to be recognized by adb
 

spawn50

Member
Feb 12, 2011
9
2
0
Visit site
you have a corrupted nand backup. Not much you can do. Just wipe everything and reflash the ROM. I like using titaniumbackup for my backups. so I do both a nand and a titanium backup just in case.

on the adb shell not connecting make sure you have the lg usb drivers installed. When you connect to the shell make sure you are in the same directory as adb.exe
 

manormortal

Member
Mar 1, 2011
14
0
0
Visit site
you have a corrupted nand backup. Not much you can do. Just wipe everything and reflash the ROM. I like using titaniumbackup for my backups. so I do both a nand and a titanium backup just in case.

on the adb shell not connecting make sure you have the lg usb drivers installed. When you connect to the shell make sure you are in the same directory as adb.exe

i keep wiping everything and reflashing a stock rom that i found but everytime the phone reboots it goes into the RA-thunderc-v-1.2.0-GNM custom recovery menu
 

mrp_bbs

Member
Feb 20, 2011
5
2
0
Visit site
First I did a NAND restore with the stock backup posted in the forum.

http://forum.androidcentral.com/optimus-v/58106-how-return-your-phone-stock-mostly.html

Don't reboot, connect phone with USB, run cmd, go to Android\platform tools

26) adb shell
27) mount /sdcard (if this throws an error about "device or resource busy", just ignore it)
28) cd /sdcard/nandroid/mem=477M/the NAND backup folder
29) flash_image recovery recovery.img (put the stock recovery.img found in download in the backup folder)
30) reboot
 
Last edited:
  • Like
Reactions: lwlamar and perksa

manormortal

Member
Mar 1, 2011
14
0
0
Visit site
First I did a NAND restore with the stock backup posted in the forum.

http://forum.androidcentral.com/optimus-v/58106-how-return-your-phone-stock-mostly.html

Don't reboot, connect phone with USB, run cmd, go to Android\platform tools

26) adb shell
27) mount /sdcard (if this throws an error about "device or resource busy", just ignore it)
28) cd /sdcard/nandroid/mem=477M/the NAND backup folder
29) flash_image recovery recovery.img (put the stock recovery.img found in download in the backup folder)
30) reboot

edit: thank you thank you thank you. i finally manage to get it done but i used
cd\
cd AndroidSDK\tools\
adb devices
adb shell

to get into shell & then

27) mount /sdcard (if this throws an error about "device or resource busy", just ignore it)
28) cd /sdcard/nandroid/mem=477M/
29) flash_image recovery /sdcard/recovery.img
30) reboot recovery

& it worked. again thank you very much & i highly doubt i'll be messing around with roms anymore. thanks again man
 
Last edited:

spawn50

Member
Feb 12, 2011
9
2
0
Visit site
edit: thank you thank you thank you. i finally manage to get it done but i used
cd\
cd AndroidSDK\tools\
adb devices
adb shell

to get into shell & then

27) mount /sdcard (if this throws an error about "device or resource busy", just ignore it)
28) cd /sdcard/nandroid/mem=477M/
29) flash_image recovery /sdcard/recovery.img
30) reboot recovery

& it worked. again thank you very much & i highly doubt i'll be messing around with roms anymore. thanks again man

Don't let it scare you off from messing around with roms. The important thing is that you know what you need to do if it happens again. Just don't wipe your phone with the factory data wipe in the OS. Use the custom recovery wipe tools. Read up on the ADB tools over at android.com
 

anon(161369)

Well-known member
Feb 6, 2011
142
6
0
Visit site
hey guys sorry to hijack this post but im pretty new to all of this but successfully rooted my phone, everything was fine up to the point where i made this same mistake and am now stuck in the same loop and when i attempt to follow you posted instructions all i get is a "not recognized as an internal or external command, operable program or batch file, after i wiped the cache and dalvik and data and did the stock recovery
is there anything i could have done wrong thanks for any help you can spare
 

Forum statistics

Threads
949,413
Messages
6,942,592
Members
3,161,462
Latest member
nbpinteriordesigner04