zeest

Android Enthusiast
Nov 22, 2012
413
78
53
So... I managed to brick again. I can get into e-mode and start the phone, but after the boot animation, it just freezes saying metropcs. I have tried restoring the firmware, and it didn't make any difference. I can't seem to get it to factory reset either (volume down + power, correct?). Fastboot and adb do not find the phone, either. Any ideas?
 
So... I managed to brick again. I can get into e-mode and start the phone, but after the boot animation, it just freezes saying metropcs. I have tried restoring the firmware, and it didn't make any difference. I can't seem to get it to factory reset either (volume down + power, correct?). Fastboot and adb do not find the phone, either. Any ideas?

What did you do? Just do I don't do it?
 
Volume down + power =safe mode. You have to hold both rockers and power when you feel it vibrate tap the back and home button fast repeatedly.;)
 
Volume down + power =safe mode. You have to hold both rockers and power when you feel it vibrate tap the back and home button fast repeatedly.;)

But... I don't feel it vibrate... just goes to e-mode

EDIT: firmware c btw, not d
EDIT2: Ok, unplugged it and now it vibrates, but goes immediately to e-mode.
 
That's weird. Take the battery out for a minute or two. I had the same problem a while back. What um telling you to do is how I finally got mine to reset.


Try it with the volume down rocker only maybe I'm confused. Just remember to stay taping home and back when you feel the vibrate
 
I spent like 45 min trying to get this thing to reset that night. Liked you mine kept going to download mode but I finally got it to reset
 
Yes try pulling the battery for a few and try flashing firmware d. Although it sounds like you need adb access to reflash your boot image (mtdblock7 if I recall). Before working on a rom you must be sure to remove any mtdblock flashes in the recovery, they are very different from phone to phone. No telling what you flashed where without seeing the script.
 
Yes try pulling the battery for a few and try flashing firmware d. Although it sounds like you need adb access to reflash your boot image (mtdblock7 if I recall). Before working on a rom you must be sure to remove any mtdblock flashes in the recovery, they are very different from phone to phone. No telling what you flashed where without seeing the script.

I made sure to change it to flash to 7, so idk... I removed a lot w/o testing though, so that was probably why I had a problem. Followed this MS770 - Factory Reset - YouTube trying multiple times, didnt work. My phone is now no longer stuck at metropcs, but looping the bootanimation. Will now download and flash firmware d, see if that helps.
 
Try a factory reset, there's a way to do it with the soft keys, I just don't know how. You may have to look through the manual.

Both volume rockers and power. When it vibrate start taping back and home keys fast and repeatedly;) its tricky but it works
 
pull battery

volume down and power at same time

when it vibrates let go of both buttons

swipe buttons left to right ( I spammed it to finally get it to work)

Android should show up if done right

THANK YOU! Worked on the fifth try.
 
Yeah dont do that =-) You dont need a boot.img file in our roms for the 2int recovery at all since we cant edit them and you would only be flashing what is pre-existing.
 
plasticarmyman, i like you so im gunna step on in before you spend a bunch of time wiping your sdcard and restoring it etc...

the reason why the nook devs all say boot from sdcard is because thats where the bootloader of that device was found to check for software. the odds of lg making their phones with a new bootloader that would replicate this similar setup would be very hard to believe. they have emergency mode, as well as fastboot to flash factory signed software images. they have no reason to need sdcard access.

the nook on the other hand was B&N's first attempt and by leaving sdcard booting it its what ultimately led to the cracking of the device. lg would be sure to make sure they didnt make the same mistake when they are trying to lock their devices down :/
 
plasticarmyman, i like you so im gunna step on in before you spend a bunch of time wiping your sdcard and restoring it etc...

the reason why the nook devs all say boot from sdcard is because thats where the bootloader of that device was found to check for software. the odds of lg making their phones with a new bootloader that would replicate this similar setup would be very hard to believe. they have emergency mode, as well as fastboot to flash factory signed software images. they have no reason to need sdcard access.

the nook on the other hand was B&N's first attempt and by leaving sdcard booting it its what ultimately led to the cracking of the device. lg would be sure to make sure they didnt make the same mistake when they are trying to lock their devices down :/

Most likely you are correct, but I just figured I'd give the guy what he wanted, just in case it worked.