[BRICK WARNING]Dont clear phone via Menu>Privacy after custom rec
Yea so I just bricked my LG optimus when i was flashing thunder-rom i linked the wrong gmail account and decided to do a clear settings via Privacy to remove the email. After I did that, it rebooted and now its stuck in the Recovery Menu and just keeps booting into it. I tried reflashing and restore NAND, but that doesnt work and still boots into the same screen.
This is just a heads up for those that might be doing the same. I wish someone warned me ahead of time, but hopefully this thread helps someone before for they do any clearing.
Hopefully a fix will come out for this one day.
Please subscribe to this thread if this happened to you too.
** UPDATE 12/27 **
Right now if your bricked your phone like i did. You can unbrick it by following the UNROOTING thread which is stickied on this main forum. basically what it does it load up a custom recovery file and then you nand flash with the provided file in that unrooting thread. And it worked after that. It took me about 10-15 min to do all of that. wasnt hard at all if your used to the ADB shell.
** UPDATE 1/19/2011 **
Fixed another one with the same problem. Solution is confirmed A-OKAY!
Last edited by box0112; 01-20-2011 at 12:38 AM.
- 12-22-2010, 09:10 AM #2
Once you have a custom recovery, you can/should do a wipe through recovery (wipe factory/data). This will wipe all your data. For whatever reason, once a custom recovery is installed, when you try to wipe from the privacy menu, you'll screw your phone up.
It should be clarified that ANYONE WITH A CUSTOM RECOVERY on their optimus S should not do the wipe through privacy. It doesn't matter if you are on LG's stock ROM or not. Once you have a custom recovery, wiping through privacy will mess up your phone. Stock phones, or rooted phones with a stock recovery are absolutely fine. This would only impact phones that have a custom recovery.
Someone is probably going to miss me saying this so it's worth repeating .... IF YOU HAVE A CUSTOM RECOVERY, YOU NEED TO DO YOUR DATA WIPES THROUGH THE RECOVERY (wipe factory/data) NOT THROUGH THE PRIVACY MENU UNTIL THIS GETS SORTED OUT!!!
Last edited by KSmithInNY; 12-22-2010 at 09:23 AM.[CENTER][URL="https://plus.google.com/u/0/+KPSmith/posts"]Follow me on Google +
- 12-22-2010, 09:54 AM #3
Someone who has a bricked phone, can you please attempt to achieve an adb connection?
Can you please attempt to achieve an adb connection?"I love talking about nothing. It is the only thing I know anything about." - Oscar Wilde
- 12-22-2010, 09:56 AM #4
- 12-22-2010, 09:58 AM #5"I love talking about nothing. It is the only thing I know anything about." - Oscar Wilde
- 12-22-2010, 09:59 AM #6
alright now that the warning is out of the way ..... I'd love to get my hands on one of these "bricked" phones to see truly how bricked they are. I'm not going to brick my phone for the sake of science (my phone has done enough for the community lol) so I'm hoping someone with ADB knowledge and some free time has one of these phones in their hand.
I feel like, as long as you can get to recovery, 99% of all problems can be solved with a little ADB work.
1) Does ADB recognize the phone (must be in recovery).
2) Does wiping factory/data/cache help?
3) Have you tried flashing a custom ROM? (make special note of any errors)
4) Have you tried following the instructions to bring your phone back to stock?
Just need to know what has or has not been done which will assist in future ideas.[CENTER][URL="https://plus.google.com/u/0/+KPSmith/posts"]Follow me on Google +
- 12-22-2010, 10:12 AM #7ROM Developer
- 32 Posts
- 12-22-2010, 10:15 AM #8
- 12-22-2010, 10:18 AM #9
- 12-22-2010, 10:39 AM #10
- 275 Posts
Might take it out, though I'd post have it up in the custom recovery thread. Aside from that, iirc it asks you several times if you're sure you really want to wipe your phone.
Though good thing someone posted this, I was having issues with an app crashing my phone and almost got to the point of doing a privacy wipe and starting over...
- 12-22-2010, 11:02 AM #11
- 12-22-2010, 11:24 AM #12
- 12-22-2010, 11:46 AM #13
- 12-22-2010, 11:51 AM #14
can you tear open the smali and see if you can tell which reboot command its issuing... most apps have to send a reboot command like "recovery" "bootloader" "oem-##", which make the phone reboot and perform random functions.
HOWEVER, we can intercept this in the kernel. So for the sake of example say this function sends reboot "oem-81". in my kernel I can just hook that into a standard reboot or a recovery reboot.
see if its something like "flasherase" or "eraseall" or some thing.
- 12-22-2010, 12:57 PM #15
- 12-22-2010, 01:24 PM #16
When you can get to recovery, 99% of the time you'll be just fine
I am still curious about what happens if someone flashed a custom ROM if:
a) Does it throw an error during flashing?
b) No errors but still won't boot?
c) All is good and well.
To test this, someone with a phone in this condition could just download a ROM onto your PC and transfer it onto the root of the SD card either by using a card reader connected to their PC or by connecting their phone to the PC using mount as usb. Once you have the ROM on the root of SD, wipe factory, cache, and dalvik and flash the ROM. Again please pay very close attention to any errors shown on the screen and the behavior post flashing. Replying with something like "it didn't work" isn't going to help anybody.[CENTER][URL="https://plus.google.com/u/0/+KPSmith/posts"]Follow me on Google +
ok i can connect it to the computer and i can adb shell into the phone. now on the root of the shell i see this after ls:
/ # ls -l
drwxrwx--x 1 1000 1000 2048 Dec 22 07:34 cache
drwxrwx--x 2 0 0 0 Jan 1 1970 data
-rw-r--r-- 1 0 0 5597 Jan 1 1970 default.prop
drwxr-xr-x 13 0 0 3140 Dec 22 23:20 dev
drwxr-xr-x 2 0 0 0 Jan 1 1970 etc
-rwxr-x--- 1 0 0 111924 Jan 1 1970 init
-rwxr-x--- 1 0 0 611 Jan 1 1970 init.rc
dr-xr-xr-x 67 0 0 0 Jan 1 1970 proc
drwxr-xr-x 3 0 0 0 Jan 1 1970 res
drwx------ 2 0 0 0 Oct 13 13:55 root
drwxr-x--- 2 0 0 0 Dec 22 23:20 sbin
drwxr-xr-x 2 0 0 0 Jan 1 1970 sd-ext
drwxrwxrwx 10 0 0 16384 Dec 22 23:26 sdcard
drwxr-xr-x 12 0 0 0 Jan 1 1970 sys
drwxr-xr-x 2 0 0 0 Jan 1 1970 system
drwxr-xr-x 2 0 0 0 Dec 22 23:20 tmp
i also pushed the new thunderrom15.zip to the root. or does it have to be elsewhere?
- 12-22-2010, 11:11 PM #18
adb push thunderrom15.zip /sdcard/
mounting sdcard is important if you are going through ADB since its not mounted by default.
try to flash using normal methods.
If that doesn't work, I'll give you step my step to restore your nand partitions.
Also kSmith keep me up to date about that reboot command.
nope its not working. i just flashed the thunderROM 1.5 and same thing just goes to the Android system recovery... i still have the existing nand i first backed up in the sdcard/nandroid if that helps.
also i read on the other thread about unrooting your phone. i got up to the point where i had to do flash_image recovery recovery.img (but for the nand backup i have, there is no recovery.img).
- 12-23-2010, 04:40 AM #20
doesnt sound like a flash issue it is either android booting it back because it doesnt think its done or the bootloader. try connecting adb shell in recovery
adb shell reboot recovery
let it come back to recovery
adb shell reboot
see if that works
- 12-23-2010, 09:44 AM #21
confirmed working.. thanks everyone for the help....
Unbricked by using this method:
Basically you get hit back to v8 unrooted rom. which is stock.
- 12-24-2010, 09:32 PM #23
- 12-25-2010, 10:21 PM #24
- 01-07-2011, 09:29 AM #25