Stuck in Blue Fastboot....am I screwed?

Adb connect.

Wasn't that for wifi?

Adb connect 192.xxx.x.x:5555

Sent from my LG-VM670 using Tapatalk 2 Beta-4

Probably... I have never needed adb and just set it up yesterday, and was playing around with it.

Sent via the Postal Service
 
So I've tried using a couple different flash images. Different versions of the xionia clock work mod. No clue why it is having a problem with the image. :'(

I'll try the whole process on a PC tonight, rather than my Mac.
 
I'll try the whole process on a PC tonight, rather than my Mac.

Good call, if that doesn't work the only other thing I can think of (I don't actually know how to do you would have to research it) would be to take images of working recovery, system and boot partitions from someone elses phone and flashing the partition images directly (which can be done in fastboot I just don't know the syntax etc). I'm not actually sure if that will work being that you can't flash a recovery.img but you could research it and give it a shot anyway.

On second thought I do have a secondary theory (could be entirely wrong of course), some manufacturers require oem switches for fastboot to properly function. I don't know the device codes for the Optimus V but an example would be stock fastboot usage for the kindle fire 'fastboot -i 0x1949 reboot' in that case 1949 is the Lab126 device code for the Kindle Fire, with a little bit of research you might be able to find a device code for the Optimus V which may or may not be useful in flashing your image. (I know 'fastboot reboot' worked for you, but some commands seem to be more finicky than others)
 
Last edited:

Trending Posts

Forum statistics

Threads
957,093
Messages
6,971,447
Members
3,163,717
Latest member
sonmaria6