LG optimus v wont restore and keeps going back to recovery
i wiped cache,dalvik cahe,data then went to backup/restore chose restore picked the stock rom backup loaded it then at the end it says skipping sd-ext.img and android_secure.img not found skipping then it says complete so i reboot the system and it goes back to clockworkmod recovery 5.0.2.7 plz help i also tryed installing from zip aosp7 and it wouldnt do it so i have an optimus v that doesnt have any android base.
I'm going to need help with this as well. I originally rooted my phone but never flashed a custom ROM so I ended up forgetting that I did it altogether.
Lo and behold, I factory restored it...
And I never backed up my data but I'm not too worried about that because I did export my contacts.
So I am stuck in ClockworkMod Recovery v3.2.0.1
So I put the microSD into my computer (USB doesn't seem to be working) and place this ROM (forums.androidcentral[DOT]com/optimus-v-rooting-roms-hacks/73446-rom-basic-stock.html) in a folder named "ROMS."
I place the microSD back into my phone.
I have "wipe data/factory reset" three times, "wipe cache partition", "wipe Dalvik Cache", and formatted "/boot", "/cache", "/data" and "/system."
I then go to "install zip for sdcard." I find the folder and I find the ZIPPED zip file.
It finishes installing and I reboot my phone directly after.
But I end up back in the ClockworkMod Recovery v3.2.0.1 menu.
What I am basically looking for is a "ABSOLUTE DUMMIES "let me hold your hand" GUIDE" to fixing this problem. I read the other posts on how to fix it and they are way over my head (I know, if it is then I should have never rooted in the first place). I feel like I might be missing a major step or I might have bigger problems on my hands.
Help would be appreciated!
-DTV
Last edited by deeteevee; March 2nd, 2012 at 10:42 AM.
Reason: I wrote the opposite of what I meant.
The ROM,Gapps,Theme,Boot Animations,Kernels',Patches,Updates have all got to remain Zipped. The only thing you ever want to have unzipped is the recovery.img and the flash_image.bin.
The Xionia recovery v1.2518.6 in a zipped form is also handy to have on the uSD card as you can use this to get yourself out of a boot loop should you cause it to happen. But this is the only time you want to have a recovery zipped.
The Xionia recovery v1.2518.6 in a zipped form is also handy to have on the uSD card
Do you know where I can find that? I searched yesterday and can only find the one for the older phones in zip. Will it still be the same if I just put the recovery in a zip?
Sorry. I realized in my original post I said it was "UNZIPPED" but I meant it was "Zipped."
And you're partially losing me already. Sorry for my lack of knowledge.
So I install this ZIPPED ROM (OV-STOCK-ROM) but what do I do with the recovery.img and the flash_image.bin? It is in a ZIPPED folder(OV-STOCK-RECOVERY). Should I unzip it?
And where should I place them in the microSD? And what method do I use to install them?
-DTV
Last edited by deeteevee; March 2nd, 2012 at 11:11 AM.
Reason: adding important info in order to get a proper answer
So new update.
I installed a zip from my SD called Xionia_CWMA+12518.4_VM_Recovery.zip and rebooted and it now brings me to a blue screen with tiny white letters.
It says:
Fastboot mode started
gpio_i2c: invalid khz:0
bl:i2c write error
udc_start()
Lets back up to when you first rooted. What phone version do you have, 2.2.1 or 2.2.2? What screen version do you have, Novatek or Hitachi? What have you done since rooting the phone, ie: have you installed a custom recovery? What name and version? what method did you use to install the recovery, if you installed the recovery already? Have you made a nandroid backup(an entire ROM/system backup) in your recovery?etc., etc.
Got Ninja'd. Have you tried pulling your battery and holding the power button down for 30 sec.? Try not to do anything until you read this Do not Factory Reset your Rooted Phone
When trying to determine your screen version the straight up/down line is in the ALT symbols key board registry.
Then let me know what going on with your phone.
Last edited by AndyOpie150; March 2nd, 2012 at 02:03 PM.
I rooted it way back. Realized it was too complicated for me (as you see) and just ended up restoring my original backup. I forgot that I rooted at all. I didn't have ROM manager or superuser or any of these apps installed. I honestly thought I was back to its original state.
I factory reset it yesterday and am currently in this dilemma.
I'm currently having trouble getting into recovery mode since I installed that last ZIP.
I hold down the home and volume button simultaneously then press the power button as well. LG flashes then it goes into "Android Recovery System..." reboots and leads me to that blue screen.
Do you know where I can find that? I searched yesterday and can only find the one for the older phones in zip. Will it still be the same if I just put the recovery in a zip?
Ok. Do you have a terminal emulator? Download the flash_image and the VM670NH recovery.img (this is the best for Gingerbread and ICS Rom's). Follow the instructions on how to install them in the link I gave you. I'll keep my I out for any questions you might have.
If all turns out well make a backup of your system/ROM (this is called a nandroid ) in your recovery in the backup and restore section. Then let me know that everything's good to that point.
Ok just download one from the market and get out your reading glasses (the print is very small when typing), make sure you double check each line of code before you hit the enter key.
When you type in the first line superuser asks for permission, say ok. You will probably lose the keyboard, that's ok. Hit the menu button and select toggle soft keys.
Ok I'll need to do some research on how to get out of the bootloader screen, it's been a while since anybody's been stuck there. Have you tried pulling the battery and holding the power for 30sec then re-installing battery and powering up?
You have a Novatek screen, this is very good thing. You can use any recovery and ROM for the V. Hitachi screens have a very limited number of ROM's they can use and the screen colors aren't quite right.
Last edited by AndyOpie150; March 2nd, 2012 at 02:50 PM.
Reason: fix typo
Thanks I appreciate it.
Yeah I've attempted that a few times but no luck. It just ends up going back to "Android System Recovery...", Reboots, and gets stuck at the bootloader.
OK. You need to put the flash_image and the recovery.img on the SD card. When that's done let me know.
Make sure the flash_image.bin and recovery.img say exactly that. If they have .zip on the end you need to unzip them.
Sorry for the wait. Life goes on.
OK. You need to open up a command prompt and type in:
cd..(hit the enter key)
cd..(hit the enter key)
This wil get you to the root of your C drive. Then type in:
cd SDK/platform-tools(hit the enter key)
you should get: SDK/platform-tools>
Then type in: adb shell(hit the enter key)
You should get a #
Then type in:
(line #2) mount_-o_remount,rw_-t_yaffs2_/system_/system(return)
(line #3) cat_/sdcard/flash_image_>_/system/bin/flash_image(return)
(line #4) chmod_755_/system/bin/flash_image(return)
(line #5) flash_image_recovery_/sdcard/recovery.img(or however it's named exactly, on the sd card) (return)
If you get a # after typing all that in, continue with the sixth line of code. If you did not, or got an error anywhere, start over.
(line #6) reboot_recovery(return)
EDIT: The red underscores are where the spaces should be, do not type them.
(return)=do not type this. Just hit the enter key(the one on the bottom right)
(line #) don't type this in.
Last edited by AndyOpie150; March 2nd, 2012 at 04:38 PM.
I know I have all three LG drivers properly installed and I restarted my computer after to ensure it was installed fully.
Whenever I plug in my phone using the USB, it automatically turns on, boots up, and get stuck on the blue bootloader screen. And everytime I unplug and replug the usb "-- suspend --" pops up on the bootloader
I've also tried connecting it via USB on another computer running Linux and it does the same thing. The computer itself doesn't detect anything connecting whatsoever.
The same "-- suspend --" message pops up whenever I plug it into a wall charger.
Ok. I've got the "Shell Answer Man" coming to the rescue(JerryScript). Just put in a request. His memory is better than mine.
All my searches came up empty, and so did my memory(most be getting to many holes in it).
Hang tough.
The Following User Says Thank You to AndyOpie150 For This Useful Post:
Will your PC recognize you phone in Emeregency Mode(phone plugged into PC with charging battery icon on screen, then hold down back button and then power button, hold both at the same time until it goes into Emergency mode)?
Here is what it looks like currently. Each "-- suspend --" is each time I plug in the usb cable.
I was in the same fastboot mode screen several months ago and all my backup files and recovery tools could not help me because my PC just wouldn't connect to my LG Optimus V. Fortunately, I found the following link and I got my phone back to life by following the step-by-step instructions. It is in LG Optimus M forum, but it works for V without any issues.
I started to follow the guide and I seem to get tied up almost immediately when it asks me to connect the phone and find it under Device Manager. How did you get your computer to recognize the phone?
I started to follow the guide and I seem to get tied up almost immediately when it asks me to connect the phone and find it under Device Manager. How did you get your computer to recognize the phone?
After I installed the lgandbus64.sys(lgandbus was not working for my PC) ,then my PC started talking to my V. I was so happy to see my V started rebooting after I sent the command to my phone.
I am pretty sure one of the device driver will recognize your phone
The Following User Says Thank You to BrickSurvivor For This Useful Post:
I started to follow the guide and I seem to get tied up almost immediately when it asks me to connect the phone and find it under Device Manager. How did you get your computer to recognize the phone?
In our case, we could not skip to step 2, we have to manually install the fastboot device driver.
Its not simply that Windows does not "recognize" the phone and I just need to install the correct drivers.
Its that my computer doesn't see anything when I plug it in. It doesn't even see it as a unknown, unrecognized device. It simply doesn't show.
If it doesn't show, it's most likely drivers interfering with each other.
Unsinstall all the LGE drivers, then reboot your PC.
Follow the steps in the links posted, and only install the drivers mentioned at the times the instructions say to.
I don't have personal experience with fastboot (knock on wood), but everything I have read over the past year indicates it's a matter of drivers most of the time.
Also, be sure you are using W7, I don't know if XP fastboot drivers work.
Its not simply that Windows does not "recognize" the phone and I just need to install the correct drivers.
Its that my computer doesn't see anything when I plug it in. It doesn't even see it as a unknown, unrecognized device. It simply doesn't show.
I prepared several step-by-step screen shots but it seems too large and could not post it
That's what you need to do and it is in Windows XP.
1. Go to Control Panel
2. select Add Hardware.
3. Scroll to the bottom, select Add a new hardware device.
4. Select the hardware that I manually select from a list[Advanced]
5. Select Show All Devices
6. Don't bother to select manufactory, just click Have Disk
7. Browse to Program files/LG Electronics/LG United Mobile Driver, and select lgandbus.inf
8. continue until you can select Google. Inc and Android Platform Sooner ADB interface
9. Start installation.
After this, you will see your phone!
The Following User Says Thank You to BrickSurvivor For This Useful Post:
Then I started to follow BrickSurvivor's guide. Steps 1-6 went easy enough but step 7 is when things started to change. I went to Program files (x86)/LG Electronics/LG United Mobile Driver, and selected lgandbus.inf ... But there was also a lgandbus64.inf available.
I then selected Google Inc. but I didn't have "Android Platform Sooner ADB interface" but instead I had "Android Platform Sooner Single ADB interface 1.0.10.0 4/1/2010" and "Android Platform Sooner Single ADB interface 1.4.1.0 7/21/10"
Well I decided to try out the 4 possible combinations between "lgandbus64.inf" or "lgandbus.inf" and "Android Platform... 1.0.10.0" or "Android Platform... 1.4.1.0"
All four ended up with a "An error occurred during the installation of the device. The system cannot find the file specified" message.
Then I started to follow BrickSurvivor's guide. Steps 1-6 went easy enough but step 7 is when things started to change. I went to Program files (x86)/LG Electronics/LG United Mobile Driver, and selected lgandbus.inf ... But there was also a lgandbus64.inf available.
I then selected Google Inc. but I didn't have "Android Platform Sooner ADB interface" but instead I had "Android Platform Sooner Single ADB interface 1.0.10.0 4/1/2010" and "Android Platform Sooner Single ADB interface 1.4.1.0 7/21/10"
Well I decided to try out the 4 possible combinations between "lgandbus64.inf" or "lgandbus.inf" and "Android Platform... 1.0.10.0" or "Android Platform... 1.4.1.0"
All four ended up with a "An error occurred during the installation of the device. The system cannot find the file specified" message.
I am sorry I gave you the wrong INF file name, it should be lgandadb.inf. I double checked my device driver and it is using lgandadb, and the guide is also clearly shown lgandadb.inf. My mistake.
So I tried it out with the lgandadb.inf file and I still got the "An error occurred during the installation of the device. The system cannot find the file specified" message.
So I tried it out with the lgandadb.inf file and I still got the "An error occurred during the installation of the device. The system cannot find the file specified" message.
Anyone have any idea why I may be getting this message?
Anyone have any idea why I may be getting this message?
The drivers mentioned in the Guild LGUnitedMobileDriver_S497CA20_WHQL_ML_Ver_1.0 has the size of 4826 K, but the driver I downloaded from LG Official site , LG United Mobile Driver.exe has 10387 KB.
You can download the drivers from this link, and let us know if can install the driver this time.
So I uninstalled everything I've installed since this problem started. Restarted my computer.
Downloaded the LG United Mobile Drive.exe with 10387KB and let it install.
When I installed the lgandadb.inf file from the LgUnitedMobileDrive folder, it gives me the "An error occurred during the installation of the device. The system cannot find the file specified" message.
When I installed the lgandadb.inf file that is inside another folder called 64bitADB which is within the LgUnitedMobileDrive folder, I got a "The software for this device is now installed but may not work correctly. This device cannot start. (Code 10)" message.
So I uninstalled everything I've installed since this problem started. Restarted my computer.
Downloaded the LG United Mobile Drive.exe with 10387KB and let it install.
When I installed the lgandadb.inf file from the LgUnitedMobileDrive folder, it gives me the "An error occurred during the installation of the device. The system cannot find the file specified" message.
When I installed the lgandadb.inf file that is inside another folder called 64bitADB which is within the LgUnitedMobileDrive folder, I got a "The software for this device is now installed but may not work correctly. This device cannot start. (Code 10)" message.
Did you connect your phone, and issue the fastboot command, after reboot it? Just give it a try. May be it will auto connect by itself, you never know.
So I uninstalled everything I've installed since this problem started. Restarted my computer.
Downloaded the LG United Mobile Drive.exe with 10387KB and let it install.
When I installed the lgandadb.inf file from the LgUnitedMobileDrive folder, it gives me the "An error occurred during the installation of the device. The system cannot find the file specified" message.
When I installed the lgandadb.inf file that is inside another folder called 64bitADB which is within the LgUnitedMobileDrive folder, I got a "The software for this device is now installed but may not work correctly. This device cannot start. (Code 10)" message.
I tried to install it again, and sure enough I got (Code 10) too. So, maybe you've already had it installed? Did you see an ADB Interface tree node in the Device Manager?