Oshi- Brick?

[Irate Iguana]

In CWMA I was wiping everything so I could flash a new ROM and accidentally chose the 'LG style wipe' option (I was distracted and tired >.<) So now my phone boots straight into a blue screen that says

Fastboot mode started
gpio_i2c: invalid khz: 0
bl: i2c write error
udc_start()

So I pull the battery to shut it off (no other way to turn it off), and try to boot into recovery (holding power/vol down/home) and it boots into the LG style wipe and repeats by booting into fastboot.

Is there anyway I can fix this? I hope I don't have a $150 paperweight >.<.

 

[Liquidplacidity]

In CWMA I was wiping everything so I could flash a new ROM and accidentally chose the 'LG style wipe' option (I was distracted and tired >.<) So now my phone boots straight into a blue screen that says

Fastboot mode started
gpio_i2c: invalid khz: 0
bl: i2c write error
udc_start()

So I pull the battery to shut it off (no other way to turn it off), and try to boot into recovery (holding power/vol down/home) and it boots into the LG style wipe and repeats by booting into fastboot.

Is there anyway I can fix this? I hope I don't have a $150 paperweight >.<.

You can always flash a new recovery via fastboot. Also.. LG style wipe? I don't have that option on mine.

 

[00_wrath_00]

Lg factory wipe is on Xionia recovery. Atleast on the ones I have used.

Sent from my VM670 using Tapatalk

 

[Irate Iguana]

How do you flash a recovery in fastboot? And I think LG style wipe is under advanced near dalvik wipe.

 

[prime0025]

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.

 

[00_wrath_00]

There's a guide on this forum for fast boot that may help. If I wasn't on my phone I would post the link.

Sent from my VM670 using Tapatalk

 

[Kiernon]

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.

Bestesteiest way to do it for me.

Hoping for a good outcome, Iguana. Those times always make me a bit nervous. Best of luck, man.

Also, if memory serves, CWMA .4 offers this LG style wipe and I want to say .6 does not? Anyone confirm/deny? So I don't have to be unlazy on a Saturday?

 

[Kreatur3]

Not to cut into others suggestions but for me using ROM Tools is the easiest way. Don't have to type out any adb commands. Granted if you can't boot I'm not sure it will work. I believe as long as your phone is on it will work. I got that blue screen when I was using clockwork recovery and accidentally close the format /recovery option...OOPS! lol. Zefie ( believe who makes the CWMA recovery) removed that option in the .6 version due to this exact issue.

 

[00_wrath_00]

Good call lol. .6 version doesn't have the factory restore just looked because that's what I'm using on my v. So u can use rom tools on fastboot screen? Just curious for future reference.

Sent from my VM670 using Tapatalk

 

[Irate Iguana]

This is not good... I keep getting an Error: device not found in both the fastbootroot and romtools.

 

[Kreatur3]

Yeah I was wondering one day if there was a newer version of CWMA because .4 couldn't mount my ext partition. Therefore couldn't format and such. Found it on the S forums and it works perfect for me other than the Bumblebee rom...weird.

Irate. Unfortunately I didn't see the warning anywhere here but there was a brick warning on the S thread about that version of the CWMA recovery regarding that wipe option. I'm sure there is a way to get your phone back to working order but might want to search THEN post, if you cant find information, in the Optimus Sprint thread about this recovery. I'm sure there will be information in the thread about fixing it since I'm sure others have done it otherwise Zefie wouldn't have known about the issue to begin with. Best of luck. Let us know how you get it fixed WHEN you do...not IF.

 

[00_wrath_00]

I don't know if anyone has made a. cab file to use with kp500 for the v. If so then that would be the way to go. I'm not sure but I know you can get into emergency mode on the s but not sure if you can on the v. But if there is a cab file for the v and was able to get into emergency mode then maybe that be a option.

Sent from my VM670 using Tapatalk

 

[Irate Iguana]

Well, I can't seem to be able to flash a new recovery. Windows is acting as though it cannot recognize my phone when i plug it in...

 

[00_wrath_00]

Have u tried reinstalling the optimus v drivers?

Sent from my VM670 using Tapatalk

 

[Irate Iguana]

Yup, Just reinstalled the drivers.

 

[00_wrath_00]

Yup, Just reinstalled the drivers.

Keep us posted lol

Sent from my VM670 using Tapatalk

 

[Kiernon]

After refreshing drivers, and basically re-following RevolutionRed's sticky, you are unable through either adb or ROMTools to flash a custom recovery, is that right?

Just trying to follow your steps, here.

DON'T YOU ******* DIE ON ME, OPTIMUS V! CLEAR!!

-K

 

[Takenover83]

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

 

[Irate Iguana]

Kiernon, correct. I just get a message telling me
error: device not found

EDIT: It seems as though I need some drivers that will allow me to access my phone while it's in fastboot...

 

[asadullah]

What operating system is on your computer right now. your stuck in fastboot aka bootloader.

if you have windows 7 check out this video it should help you and it could help you on windows of any kind.
http://www.youtube.com/watch?v=aTE30yd-P_U