Oshi- Brick?

[Irate Iguana]

Call VM, the phone has a 1 year warranty on it, no idea if they service user damage done though.
You could try the fast boot root method, no idea how that will work with water damage.

 

[Jim8181]

Call VM, the phone has a 1 year warranty on it, no idea if they service user damage done though.

Thanks Irate, I'm doing that as last resort. I thought since it does go into fastboot and I can get it into the emergency mode, that maybe all was not lost...

 

[kaivorth]

I'm still going through this fast boot crap as we speak. Can't get into custom recovery or anything.

 

[kaivorth]

I got the same blue screen. I planned to install a new ROM and I followed the instruction on how to install a new ROM:Wipe data/factory reset, wipe cache partition, Under Partitions menu (or Mounts & Storage in 3.0.0.6) in recovery: Format boot, system, data, cache. Under advanced: wipe Dalvik Cache. Then I press "Reboot" by mistake, so I came here.

I have the same situation and tried to do the above, after I run the fastbootroot.bat, it showed "error: device not found <waiting for device>" , but I'm sure I connected my phone via USB with my computer, looks like it couldn't recognize my phone. I tried to reinstall the LG driver to my computer(running in Windows7 64Bit), it still can't recognize my phone. What's the problem????

PS: When I start the phone, this is the messages shown on the screen:
Fastboot mode started
gpio_i2c: invalid khz:0
bl:i2c write error
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --

I did the SAME exact thing. Only difference is I'm on Windows 7 32bit. Downloading fastbootroot now.

Fastboot recognizes my Optimus, but adp doesnt?

Upon downloading the drivers from fastbootroot page, I get the error Driver is not intended for this platform.?

 

[flowing]

Stuck in recovery loop

Hey Guys I have the same issue... did a factory reset and now I'm stuck on a recovery loop. I tried those two lines but the second one fails:

C:\Windows\system32>adb shell flash_eraseall /dev/mtd/mtd8
/sbin/sh: flash_eraseall: not found

Any other ideas....

Thanks

Flash the other recovery (thunderc-v-1.2.0-GNM). I did the same freak'n thing the other day (LG style wipe). There is also a command you need to run in adb to clear the default recovery from wiping apron every reboot. If I find it again, I will share it here.

(I copied the recovery to system, because for some reason I could not access my sd card)

adb remount
adb push recovery.img /system
adb shell
flash_image recovery /system/recovery.img

This should get you back to a functioning recovery. But once you try to load a rom, and it will just reboot back to recovery. Let me hunt for the command that helped me get past this.

Edit: OK found it, one of these two commands fixed the recovery boot loop. Not sure if any of this information will help. But it's here if you need it. (got to get adb going again before you will be able to do anything)

adb shell strings /dev/mtd/mtd8
adb shell flash_eraseall /dev/mtd/mtd8

 

[sstoner]

You can try flashing a recovery via adb

Flash recovery using: ADB

1. Download the Recovery.
2. Copy the recovery.img to root of the SD card.
3. Boot the phone into recovery or whatever it is your getting. Should be able to run ADB. If ADB dont work dont attempt this.
4. Open command prompt, cd to the Android SDK directory & type the following commands:

adb shell
mount /sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery

5. Your phone should now reboot into the Recovery.

I've been working on my phone for 6 hours... wish I would have found this post earlier, fixed EVERYTHING for me... ty so much

 

[kcls]

You did a factory reset? NOOOO!!!!