• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Optimus V Fresh Start

N

Nebotec

Lurker
Hello Everyone, new to the forum and seeking help. Thanks in advance for taking your time to read this over and possibly help me out!

Down to business.

I received an Optimus V from a friend of mine who claims it is 'bricked', so i'm trying to see if i can't crack this little brick open.

What I did NOT receive was the Micro SD card, so I went out and bought an 8 gig class 10 micro SD card + adapter. As of right now, the phone starts up when plugged in and sits at the blue bootloader screen with this text

Fastboot mode started
gpio_i2c: invalid khz:0
b1: 12c write error
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
fastboot: processing commands

I've installed the Samsung usb drivers and my computer (windows 7) recognizes the phone under ADB Interface as 'Fastboot Interface (google USB ID)'
BUT
When I try to access the adb shell in cmd, it says the device is not found. Also, no device is found when I do ' adb devices ' there are no listed devices.

Again, thank you for taking your time to read through this, but what is my next move?
 
I downloaded the LG drivers and installed them.

I also ran all of these commands listed in another post by Joneidy I stumbled upon, but no dice, it still sits at the bootloader.
cd C:\Fastboot\android-sdk-windows\tools
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery C:\Fastboot\Recovery\recovery-RA-optm-2.2.1-GNM.img
fastboot reboot
 
Nebotec said:
When I try to access the adb shell in cmd, it says the device is not found. Also, no device is found when I do ' adb devices ' there are no listed devices.
Click to expand...

Is the platform-tools folder in your path? Are you in that folder when trying ADB? Try this. Use windows explorer, go to C:\android-sdk\platform-tools (or where ever your platform-tools folder is), hold down shift key, right click in an open area in that folder, choose 'open command window here'. Now try 'ADB Devices' again.

If it still can't find the phone, it is a bricked brick. There was a post by someone who put Optimus S firmware on theirs and was able to at least get WiFi to work.
 
The platform-tools folder is in fact in my path.

the 'open command prompt here' bit still had no change though. The device still isn't listed but IS listed under the device manager.

The back+volup+power also hasn't worked.
someone else also recommended home+volup+power, still nothing.
 
You need bigsupersquid, he can help you. The thing is, he hasn't been on here in some time. You can find him over at XDA, though.
 
Nebotec said:
I downloaded the LG drivers and installed them.

I also ran all of these commands listed in another post by Joneidy I stumbled upon, but no dice, it still sits at the bootloader.
cd C:\Fastboot\android-sdk-windows\tools
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery C:\Fastboot\Recovery\recovery-RA-optm-2.2.1-GNM.img
fastboot reboot
Click to expand...

Do you have the recovery file in that location?
C:\Fastboot\Recovery\recovery-RA-optm-2.2.1-GNM.img

Per LGE's instructions:
--unplug the phone from the PC
--uninstall all phone usb drivers
--reinstall drivers from this link: LGE USB DRIVERS
--reboot PC
--hook up phone via usb to PC

This has worked for many others, but your circumstances are a bit different, so ymmv. ;)
 
brotherswing-
Through my searches bigsupersquid was the go-to guy for anything and he'd get it fixed one way or another. I'll see what I can do about getting ahold of him.
~EDIT~
Seems like hes off the grid on xda as well, hasn't been online in 10 days. Most i'll be able to do is drop him an e-mail. Still...worth a shot.

JerryScript-
Yes,the recovery file is in the C:\fastboot location. I follewed the instructions and unzipped the file to C:, ran everything he said to ( minus the drivers because they were already installed from the phone ) and it still sits at the bootloader, but i'll give the drivers you posted a shot! what do i have to lose, right? :D

~Edit~
Uninstalled/reinstalled drivers. nothing has changed. adb still won't recognize the device.
 
I have made progress through some miracle.

Went searching and found the clockworkmod recovery restore.img, put that in the directory w/ adb and fastboot. in cmd

fastboot boot recovery.img

Booted into clockworkMod Recovery v.3.0.0.6

Now, I work more.


ALSO

~good tip that lead me to the answer~
ADB is only useful once you're booted into recovery.
If you're in fastboot, you can only use fastboot.
 
You must log in or register to reply here.
Back
Top Bottom