[reelburner]

Hello to all.

Recently purchased the LG Optimus V. VM is my carrier.
Bricked it while trying to root to Backside IHO.
In a nutshell, my laptop sees the phone as a removeable disk even with the
LG drivers installed. Furthermore, when attempting to open that drive, it
prompts me to insert a disk. I cannot gain access to the phone to run a recovery.
I've tried all phone button combinations in a attempt to access the booting option.
No luck, other than I can get to my Emergency mode but thats it.
I have attached a pic of my phone screen when I turn the phone on.
This is where it freezes.
I have also noticed when I plug the phone in my laptop(I've tried another data cable as well), ,I repeatedly hear the audiable
tone that Windows sounds when it detects a USB device,as if its trying to connect to laptop
over and over again. Don't know if this is relavent. Wondering if this is an indication that the phone is stuck
in a boot loop?

Thank you to all in advance for everyones help and with some luck(hopefully)
I will have my phone working again.
.

[steven1droid]

I think you're going to need to KDZ in emergency mode with sprint firmware (LS670ZV9) which will make your phone act like a sprint phone. From that point, you can follow this thread

[FIX] No data/wrong SW version after VM ROM flash from Sprint ROM

LS670ZV9 Firmware -

KDZ -

[reelburner]

I'm beginning to suspect my phones interface may be failing.
When the phone is plugged in via USB and I boot to emergency mode, its not even showing up on my laptop at all, and every 20-30 seconds or so, the LG logo and "download in progress do not disconnect cable" screen keeps flashing on and off with the audible tone from Windows as if its trying to connect with the laptop.

[crickie]

Check out all the guides written by LeslieAnn under Optimus V Rooting, ROMS & Hacks. All that info WILL save your **** here. YouTube has a video library of How To's.. on this phone of ours. Read thru everything carefully. You only have a "soft brick " at this point. Nothing that
can't be fixed. We've all (or most of us) have been where you are. If you used an update for LS 670 instead of VM670 that maybe where you have the problem. the VM670 requires files to run that the LS 670 doesn't. That update was for the Optimus S (Sprint), not the Optimus V
(Virgin Mobile). You'll need to re-flash your recovery before you can begin to fix any other issues. The Optimus V takes the update found on VirginmobileUSA website. (a copy has been posted on this forum for us) Your phone HAS TO BE UNROOTED before you can flash that update. Do your research carefully FIRST! Once you get your phone working, don't sweat about that update cause it doesn't work with Backside IHO yet. (see the work posted by Jerry Script & LeslieAnn) . Research it all & good luck!

[kwknott]

Can you get into recovery. With power off hold home, volume down and power until you see LG logo for a second or 2. If so wipe and reflash the rom. I'd download a new copy of the rom and gapps in case you had bad download

[reelburner]

Cannot get into recovery using home, power and volume combination, screen
just goes black.

[reelburner]

Upon doing more reading on this matter and after many many attempts
to gain access to my phone with several methods, all of which have the
same result. My laptop refuses to talk to my phone despite all the files and drivers
I've downloaded and installed. Makes no difference If it's drivers for the optimus v or s
The laptop sees my wifes LG Rumor Touch just fine, showing the SD card.
My phones shows up only as a removeable disk that prompts you to insert a disk
when you open it. the only way I can see my SD card is to remove it from phone
and plug it in my media slot, then and only then does my laptop see the SD card
in all it's glory. Now, bear in mind, that when the phone is connected via USB, the
laptop WILL install drivers, it does see the phone in that manner. But after a sucessful
install of the drivers it still will not see the SD card while in the phone. As far as the
LG Mobile Support Tool, that was useless as well. Bottom line: no matter what I do
the phones shows as a removeable drive only that prompts for a disk.
Is the bootloader damaged beyond restore/recovery?
How the heck do I get the phone and laptop to communicate again

On a side note: What is cosidered the "root" of the SD card?
probably a dumb question but I need to ask.

A Big Thank you to all once again.

[droidmyme]

Upon doing more reading on this matter and after many many attempts
to gain access to my phone with several methods, all of which have the
same result. My laptop refuses to talk to my phone despite all the files and drivers
I've downloaded and installed. Makes no difference If it's drivers for the optimus v or s
The laptop sees my wifes LG Rumor Touch just fine, showing the SD card.
My phones shows up only as a removeable disk that prompts you to insert a disk
when you open it. the only way I can see my SD card is to remove it from phone
and plug it in my media slot, then and only then does my laptop see the SD card
in all it's glory. Now, bear in mind, that when the phone is connected via USB, the
laptop WILL install drivers, it does see the phone in that manner. But after a sucessful
install of the drivers it still will not see the SD card while in the phone. As far as the
LG Mobile Support Tool, that was useless as well. Bottom line: no matter what I do
the phones shows as a removeable drive only that prompts for a disk.
Is the bootloader damaged beyond restore/recovery?
How the heck do I get the phone and laptop to communicate again

On a side note: What is cosidered the "root" of the SD card?
probably a dumb question but I need to ask.

A Big Thank you to all once again.

Umm that is pretty typical, Windows doesnt see the SD card automatically, you have to tap "Turn USB storage on" first.

Sent from my VM670 using Tapatalk 2

[reelburner]

How do I enable USB when I can't access the phone, and my laptop is not communicating
with phone? There is no way for me to turn on that feature without first being able to either
have a phone that boots and then I can enter the settings menu and enable USB, or have a connection between the laptop and phone that will enable me to do it that way.
This is my problem. Is it essential that the phone and laptop connect in order to
perform a recovery? If so, I may be screwed. How can I move vital files that need to be on SD card while in the phone, when my laptop sees no SD card?
This is quite frustrating, I done my research(obviously not enough) prior to rooting.
I bit off more than I can chew, and for that I apologize to everyone if I
appear ignorant or have trouble understanding the methods suggested to me to use.

Thanks again.

[Nate456]

Have you tried using ADB and flashing a recovery from there.

Sent from my VM670 using Tapatalk

[reelburner]

No, I have not tried ADB, I did try Android SDK with no sucess. You think that's
all I need to get back on track. Where can I get it, and will it tell me how to use it?

[droidmyme]

Lets get the basics covered first, then there wont be any confusion.

It sounds like you are making a simple driver/OS error, tbh. Dont worry about getting ADB setup for now, first thing you need to resolve is the driver issue.

1) What is your OS?
2) What LG driver are you using, and are you sure it is for your OS?
3) You should uninstall ALL the other LG and phone drivers-

You have multiple phone drivers installed, that is one of your issues. That will glitch.

4) You have USB debugging enabled on your phone?

Sent from my VM670 using Tapatalk 2

[droidmyme]

Post 2: If you can get to recovery mode, you should be able unbrick the phone

Sent from my VM670 using Tapatalk 2

[Nate456]

Just follow the instructions on the site to set it up. How exactly did you brick your phone btw.

[reelburner]

Just follow the instructions on the site to set it up. How exactly did you brick your phone btw.

Used Gingerbreak to run the exploit, which reported as successful as the phone rebooted.
Rebooted fine, then ran ROM Manager(big mistake) after making not one but 2 backups.
One with Clockworkmod and the other with Titanium backup.
After that, using ROM Manager I installed IHO Basckside using the "install from SD card.
when it rebooted it hung up at the LG start screen, but I could remove the battery and it would boot fine, but still with the stock ROM.
So, I went directly to the IHO app on my SD card and ran it.
When prompted, I wiped the Delvik cache and the phone proceeded to reboot to its
current state. See pic in original post.
Since then my laptop cannot communicate with the phone.

[reelburner]

Lets get the basics covered first, then there wont be any confusion.

It sounds like you are making a simple driver/OS error, tbh. Dont worry about getting ADB setup for now, first thing you need to resolve is the driver issue.

1) What is your OS?
2) What LG driver are you using, and are you sure it is for your OS?
3) You should uninstall ALL the other LG and phone drivers-

You have multiple phone drivers installed, that is one of your issues. That will glitch.

4) You have USB debugging enabled on your phone?

Sent from my VM670 using Tapatalk 2

1) OS Windows7 32/64bit
2) Would have to verify compatibility on LG drivers to be absolutely sure.
3) I will uninstall ALL irrelevant drives and their software.
4) USB debugging was enabled prior to bricking. No way to gain access
to phone now to check if it is still enabled.

Ok, I've uninstalled ALL drivers for the phone till I'm sure I
have the correct driver. Is there a specific driver,
other than it being for Wiindows7, that I need to look for?

Update: Found the driver for Windows7, downloaded them and found
that they were the same drivers I just uninstalled.
So, there must be some update for that driver, cuz this one
didn't work.
I currently have NO LG drivers installed, since they didn't work anyway,
In fact I've uninstalled everything related to LG or Virgin Mobile for now.
Where do I go from here?
Is it time to panic yet?

[droidmyme]

1) OS Windows7 32/64bit
2) Would have to verify compatibility on LG drivers to be absolutely sure.
3) I will uninstall ALL irrelevant drives and their software.
4) USB debugging was enabled prior to bricking. No way to gain access
to phone now to check if it is still enabled.

Ok, I've uninstalled ALL drivers for the phone till I'm sure I
have the correct driver. Is there a specific driver,
other than it being for Wiindows7, that I need to look for?

Update: Found the driver for Windows7, downloaded them and found
that they were the same drivers I just uninstalled.
So, there must be some update for that driver, cuz this one
didn't work.
I currently have NO LG drivers installed, since they didn't work anyway,
In fact I've uninstalled everything related to LG or Virgin Mobile for now.
Where do I go from here?
Is it time to panic yet?

Aha, that answers my question then. And yours too. Since the phone cant enable USB debugging, there is no way to "recognize" it in the traditional way.

But the good news is at least now, you are 100% certain you have the,correct driver. And thats good, because you will need that.

What you need to do next is (just a basic outline):

Get the Android SDK installed. You may also need Java runtime I believe.

I think you have to use the SDK to run ADB (Android Debug Bridge) and commands. The command terminal will tell you if it actually sees the phone or not. Then you have to push an old but working recovery to your phone via ADB and flash it (called Xionia recovery).

Im sorry I can only give you a rough outline at this point. But I know that with a little patience you can get your phone back 100% ( except any personal data, unfortunately).

I must bow out now and wish you well in the rest, but there are other threads detailing the steps

Sent from my VM670 using Tapatalk 2

[Nate456]

For more info, check the 2nd and 3rd stickies in the rooting section.

Sent from my VM670 using Tapatalk

[reelburner]

Aha, that answers my question then. And yours too. Since the phone cant enable USB debugging, there is no way to "recognize" it in the traditional way.

But the good news is at least now, you are 100% certain you have the,correct driver. And thats good, because you will need that.

What you need to do next is (just a basic outline):

Get the Android SDK installed. You may also need Java runtime I believe.

I think you have to use the SDK to run ADB (Android Debug Bridge) and commands. The command terminal will tell you if it actually sees the phone or not. Then you have to push an old but working recovery to your phone via ADB and flash it (called Xionia recovery).

Im sorry I can only give you a rough outline at this point. But I know that with a little patience you can get your phone back 100% ( except any personal data, unfortunately).

I must bow out now and wish you well in the rest, but there are other threads detailing the steps

Sent from my VM670 using Tapatalk 2

I thank you very much for your help.

[droidmyme]

I thank you very much for your help.

My pleasure

Sent from my VM670 using Tapatalk 2

[droidmyme]

More help - direct from a thread in which I made a huge *** of myself. . Ah well.

Cliffs:
Install SDK with ADB
Boot phone to recovery and connect to computer
Open ADB console
Run the commands...

Don't worry, you can recover your phone, it's just going to take some time and patience.

To get ADB working, check the stickies in this forum, they have step by step instructions. ADB is simply a means of using a command window to control your phone.

Once you have ADB installed, you will boot your phone into recovery, then hook it up to your computer. On your computer, (W7/XP) press your start button, then type in cmd and press enter. A command window should open up. Now look at where ADB was installed (usually the adb folder /platform-tools). You need to "cd" into that directory. So if it's C:\android-sdk\platform-tools, type in:

cd c:\android-sdk\platform-tools
adb shell

ADB should start up, then once it connects to your phone, you should see a different prompt. Now exit the shell by typing in exit and pressing return. You should now be back to the normal command prompt.

Download the , the img file, and the ROM zip file you want to use (and gapps in needed) and place them all on your sdcard by using the ADB push command:
(Note- only the ROM and gapps should be zip files, the flash_image binary has no extension, and xionia should be an img file)

adb push c:\PATH_TO_FILES\flash_image /sdcard/flash_image
adb push c:\PATH_TO_FILES\flash_image /sdcard/NAME_OF_XIONIA_RECOVERY.img
adb push c:\PATH_TO_FILES\flash_image /sdcard/NAME_OF_ROM.zip
adb push c:\PATH_TO_FILES\flash_image /sdcard/NAME_OF_GAPPS.zip

Now, type in adb remount. If this succeeds, you are still rooted, a good thing. If it fails, stop now and see note at end of post.

Now you will install the flash_image binary, and use it to flash the xionia recovery image to your phone, then reboot so it can fix the bootloop issue.

adb shell
mv /sdcard/flash_image /system/bin/flash_image
chmod 0777 0655 /system/bin/flash_image
flash_image recovery /sdcard/NAME_OF_XIONIA.img
exit

adb reboot recovery

Note- the last line is typed in the normal command window after exiting the ADB shell.
If you get errors at any step, it's probably due to not having root, post the errors so we can help.

Now, if everything worked, you'll be in xionia recovery. In here, you should wipe cache, then under advanced wipe dalvik-cache, then under mounts you should format boot, system, data, and cache.

Now go back to the main menu, and choose to install zip from sdcard. First install the ROM zip, then do the same steps to flash the gapps zip.

Now go back to the main menu, and reboot. Be patient, the first boot after doing all this may take a long time (rebuilding files). If the phone doesn't boot up after 10 full minutes, let us know.
[NOTE]If any of this fails, please use the forum's thread search feature. Click on one of the sticky threads, then near the top right, you'll see the link to search the thread. I recommend choosing show posts.

If you can't find the solution, let us know and we will attempt to help out.

The reason some people are being hostile is because all of this information has been posted over and over and over, and is included in the stickied threads. You may be new to these types of forums, and not be aware of the wealth of information available in most forum's stickied posts. Check them out, read them all the way through, and soon you'll be the one answering questions around here! [/NOTE]

Sent from my VM670 using Tapatalk 2

Sent from my VM670 using Tapatalk 2

[reelburner]

I'am making progress. Downloaded the new pre-packaged ADB installation, and heres where I'm at. I can now send commands to the phone through the new ADB.
Verified this by doing a reboot from the command prompt, and the phone rebooted.
Now I need to figure out how to perform a recovery this way. Do I need to unroot
my phone prior to the recovery? I'm sure there's a how to on youtube.
I feel this is a step in the right direction, but with the list of all the commands
while in ADB, I'm not sure what command to use to continue with the recovery from this point.
It gets a bit overwelming

[droidmyme]

I'am making progress. Downloaded the new pre-packaged ADB installation, and heres where I'm at. I can now send commands to the phone through the new ADB.
Verified this by doing a reboot from the command prompt, and the phone rebooted.
Now I need to figure out how to perform a recovery this way. Do I need to unroot
my phone prior to the recovery? I'm sure there's a how to on youtube.
I feel this is a step in the right direction, but with the list of all the commands
while in ADB, I'm not sure what command to use to continue with the recovery from this point.
It gets a bit overwelming

Great! Glad your making progress. Im a sucker 4 nice folks in a tight spot so ill help u out some more.

Off the top of my head:

No, you dont need to unroot the phone. You need the Xionia recovery, and the flash_image BINARY file (not the GUI). You will use the command "ADB push" to move those files from your computer to your SD card, eg "ADB push c:/your/folder/xionia.img /mnt/sdcard". (may need to type ADB with caps off) Once the files are on, then you flash Xionia "ADB flash_image recovery /mnt/sdcard/xionia.img". Then when Xionia is on, you can push another ROM on and flash, should work at this point

*edit* this thread has links to xionia and the flash_image binary http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/168903-please-help.html
Sent from my VM670 using Tapatalk 2

[darthdrewsiff]

I'am making progress. Downloaded the new pre-packaged ADB installation, and heres where I'm at. I can now send commands to the phone through the new ADB.
Verified this by doing a reboot from the command prompt, and the phone rebooted.
Now I need to figure out how to perform a recovery this way. Do I need to unroot
my phone prior to the recovery? I'm sure there's a how to on youtube.
I feel this is a step in the right direction, but with the list of all the commands
while in ADB, I'm not sure what command to use to continue with the recovery from this point.
It gets a bit overwelming

I'm having the same problem, but I still can't get adb to see my phone. Installed the new pre-packaged adb sdk, followed the tut on setting environment variables, have all drivers installed and rebooted computer. Still no luck. HELP!!!!

[droidmyme]

I'm having the same problem, but I still can't get adb to see my phone. Installed the new pre-packaged adb sdk, followed the tut on setting environment variables, have all drivers installed and rebooted computer. Still no luck. HELP!!!!

Can you give us what commands you are inputting in ADB, and what the output is? When you opened the ADB terminal, did you first type

adb shell
exit

Should connect you.

Try to stay calm, this can be fixed.

Sent from my VM670 using Tapatalk 2