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

Root LG Optimus V Need Help Please

MonsterNo7

Member
Feb 20, 2012
95
12
ATX
Okay, so I've been up for the last 20 hours trying to get this fixed. This forum seems to be the most helpful, so I'm posting this here.

I believe that I've bricked my OV. I bought it new on Amazon about 4 days ago, so it's new. But I'm not sure if I'll be able to return it, so I really need to get this fixed.

The backstory:
Got my OV, loved it, but wanted to tweak the appearance, settings, etc. I installed the BACKside IHO version of CM7, all went well. I spent the whole day tweaking it, getting things just right, etc. Later that day I decided that I wanted to install a theme. Somewhere along the line something went wrong, and I decided that I wanted to restore it to factory settings. I (for some god awful reason) completely forgot the rule: don't use the factory restore button. Not only did I USE the factory restore button, I also formatted my SD card. At some point I got stuck in recovery mode, unable to start my phone. I restored from a backup, and then tried to flash a new rom. I think that this rom was one made for the wrong screen, because now I have the following symptoms:

Black Recovery Screen
Black Emergency Mode
Phone only boots to the LG logo, then freezes there

Please understand, I've been scavenging the web for every possible solution. I've tried ADB, Android Screencast, and Droid@Screen. I've also tried flash_image, Xionia, and a dozen other solutions that haven't worked. One main problem, apart from the black recovery screen, is that I can't connect my phone to my computer via USB, it never gets recognized. Also I should mention I'm completely new to Android, but I've done my best to read tutorials thoroughly.

FYI I believe I have the newer screen model, as my phone is brand new and came with Froyo 2.2.2 If there's any way to tell on the hardware just let me know and I'll check, but I haven't found anything yet.

Again, please help me, my girlfriend just bought this phone and can't afford a new one. Sadly, I couldn't afford the first one. I'll be checking this thread throughout the day, so I'll try to reply as quickly as possible.
 
I didn't use ROM Manager at any time. I never even downloaded it.

I'm trying to help you recover your phone. I asked you to read the thread.

Here is what you need to read..


"If you already flashed the recovery from ROM Manager and or a ROM and got a black screen, here's the way to workaround the black screen in the recovery and allow you to still flash the proper ROM and Gapps.
Go here first http://www.support-4-you.com/main/index.php?option=com_content&view=article&id=60:ne w-pre-packaged-adb-installation&catid=40:how-tos&Itemid=57
After installing the ADB then go here Download Free Java Software
After install go here Droid@Screen | RiboComments
The droid at screen will allow you to connect your phone to the PC and see your recovery menu screen on your PC, even though you can't see it on your phone. Without having to put an app on the phone, which you just can't do.
There is a slight lag so you need to slow down, but if you make sure you have the proper ROM and Gapps on your sd card then you just have to follow the normal wipe and format procedure as well as the proper install of ROM and Gapps.
Once you get the ROM installed and rebooted twice, then download the proper recovery (VM670NH) and a terminal emulator and follow the recovery install procedure here Do not Factory Reset your Rooted Phone"
 
Upvote 0
I followed the instructions, I installed the adb SDK, and when I try to run adb a Command window opens up for a second, flashes through some code and then closes. Same thing when I try to run Droid@Screen, except it only takes half a second. AndroidScreencast just times out because no devices are found. And yes that's all with the drivers now installed.
 
Upvote 0
Did you install the Java 6 as instructed, will not work with Java 7? this is important. I have got Droid@Screen to work with Windows Vista and XP. Windows 7 should work as well. You have to install the Java 6 and watch the video tutorial in the Droid at screen site.
I have it working flawlessly right now and all I did was follow the instructions in the Droid@Screen site, and watched the video.
 
Upvote 0
If the Zip worked you shouldn't need the SDK installer. If you did everything the video asks to do then ADB should be in your system path. You should already had an SDK folder on the Root of your C: drive, with the path to the adb.exe in your enviromental variables set.
I confussed?

I meant the zip works as far as using adb. I can just open a command window in platform tools and run it that way. The env file in the zip would not set the enviromental variables. It doesn't really need to anyway because the .jar from Droid@screen will let you select the path to the adb.exe. Even so, I couldn't get the .jar to work with just Java 6 and the adb.zip file.

After downloading the adb.exe and the JDK, I was able to use the .jar and point it to the adb/platform tools path. Possibly it has something to do with Norton 360. I'm not sure. I'm going to experiment some more when I have time.
 
Upvote 0
You have to point the Droid at screen to the path to the adb.exe. If it's not established in the system variables already you can't point it at it. It has to be in the system path for it to work as planned, with just the things downloaded that where in my tut.
I don't know why the Env File didn't work. It should have. That's what's wrong.
You did extract all the files for the ADB installer like the tutorial said, Right? Your continually referring to it as the adb.zip is confusing me.
 
Upvote 0
You did extract all the files for the ADB installer like the tutorial said, Right? Your continually referring to it as the adb.zip is confusing me.

Sorry, I guess I should have said the sdk.zip. Yes, they were extracted.

I'm at work now. I'll have to check when I get home and see if adb is in the variables from running the installer.exe. I think maybe I'll delete everything and start over. I was just thinking, maybe I should have tried selecting the Env file and 'run as administrator' since just double clicking did not work.
 
Upvote 0
Okay, sorry guys I fell asleep. I really do appreciate everybody trying to help. So I still haven't gotten Droid@Screen to work on Windows. I should mention that when I say Windows, I mean my Mac running Parallels. Windows is a virtual machine, not a separate PC. Anyways, that Windows was running 7, so I'm going to downgrade it to XP (my preferred version anyway) and try again.

In the meantime, the video on Droid@Screen clearly shows that he's doing it on a Mac. And I can get Droid@Screen running, and I targeted the adb file, and all that is good. I just can't get my phone to connect. Does anyone have any ideas for that? This is all going to be pretty moot if I can't get the phone to be recognized.
 
Upvote 0
Does anyone have any ideas for that? This is all going to be pretty moot if I can't get the phone to be recognized.

I'm not sure which way to go. Maybe AndyOpie will have some idea. I looked for some LG Mac drivers to see if that might help but haven't found any. I did find this from someone else who was looking for the same thing.

*Plug it into your pc/mac, I use a mac
*Download the LG Mobile Driver for the Optimus V, its on google bud.
*Run appinventor
*Open block editor
*Connect to device
*select your lg optimus v

Is appinventor something on a Mac?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones