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

Root [GUIDE] 100% Stock LG Optimus V (All Versions)

2.2.1, it was made from the earlier version of the phone.
Actually i have 2.2.2 on my older one so there are two versions that come with 2.2.2. this is where none of the tutorials make sense as they dont work for me . Mine checked out using a novatek screen but came stock with 2.2.2 so these files dont works on it . gingerbreak2.1 roots fine but when it comes to putting a recovery on it so i can do backups and flashes it has not happened .. no matter what i do it still has the stock recovery that looks like this :

Android system recovery <3e>

Android system recovery utility

reboot system now
apply sd-card:update.zip
wipe data/factory reset
wipe cache partition

only the last 4 options are selectable plus there is NO fastboot on both 2.2.2 's
 
hello i did these steps -Unzip "optimusV_stock_nandroid_and_recovery.zip" until you see the "BCDS-20110203-0357" folder
-copy it
-plug in phone and mount it
-open sdcard
-open the folder "clockworkmod" (if it's not there create it)
-open the folder "backup" (if it's not there create it).
-copy the folder "BCDS-20110203-0357" inside the folder "backup"
-unmount "usb storage" from the notification bar and unplug the phone
-power it off
-boot it up by holding first home, volume down, and power until you see the lg symbol
-now release buttons controls:volume keys = up,down; camera key = select; back key = back; home = hide all text
-select "wipe data/factory reset"
-select yes
-select "wipe cache partition"
-select yes
-select "mounts and storage"
-select "format /system"
-select yes
-hit the back button after it's complete
-select "advanced"
-select "wipe dalvik cache"
-select yes
-hit the back button after it's complete (you may or may not have to I am pretty sure the screen flashes and main menu comes back up)
-select "backup and restore"
-select "restore" then it says no files found plz help :(
 
Having a problem with terminal editor please held cannot get the second mount comand to work correctly. Here is the actual text from my editor

$ export PATH=/data/local/bin:$PATH
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#

I have tried multiple times with no success please help
 
In the line of code that has mount,rw and the one that has mount,ro try this:
mount -o remount,rw -t yaffs2 /system /system
mount -o remount,ro -t yaffs2 /system /system

This code is case sensitive, you must have the spaces in the right place as well.
If you get a # after each line of code your good.
 
Just FYI - The easiest way to return to stock now is to install BobZhome's recovery, then install the Virgin Mobile Security Update. Once you install it, you will be 100% stock.

If you want to root it later, it's very easy. ;)
 
Just FYI - The easiest way to return to stock now is to install BobZhome's recovery, then install the Virgin Mobile Security Update. Once you install it, you will be 100% stock.

If you want to root it later, it's very easy. ;)
Duh! I don't know why I didn't snap to that. I'll see if I can get PerkinsII to change his first post to reflect that. It's the easiest way to revert back to unrooted Stock no matter what OS version a member has.
 
Duh! I don't know why I didn't snap to that. I'll see if I can get PerkinsII to change his first post to reflect that. It's the easiest way to revert back to unrooted Stock no matter what OS version a member has.
Fixed terminal mistake and updated guide with info from Jerryscript
 
First came 2.2.1 with the Novatek screen and drivers. Then in late July-early Agust came the 2.2.2 still using the Novatek screen and drivers. Then in Late August came the 2.2.2 with the Hitachi screen and drivers. That's why if you want to flash the same firmware for the 2.2.2 (ZV5) that came with the phone, you have to make sure you have the right version. One version is for the Novatek screen and drivers. The other version is for the Hitachi screen and drivers.
 
The screen drivers are specific to the screen version. That is why you have to be careful what screen version you have when installing recovery's and ROM's. The Novatek screen and drivers will allow you to install everything. The Hitachi screen and drivers might give you a black screen in the recovery and ROM depending on what you installed. If you have a Hitachi screen make sure you double check what you are trying to install.
The ZV9 update is really just a software patch. It was designed to work with both screen versions.
 
You are so right. How did I manage to get my head so far up where it was? Will change my post. Thank you for pointing out the glaringly obvious. D'ouh. The drivers are specific to the screen version. The screens drivers can be updated, but the two different screens will probably never have the same drivers due to each ones differences/requirements.
 
This thread is truly confusing. PerkinsII has 20+ step methods for both stock ROM and Recovery, and then JerryScript says:

Just FYI - The easiest way to return to stock now is to install BobZhome's recovery, then install the Virgin Mobile Security Update. Once you install it, you will be 100% stock.

If you want to root it later, it's very easy. ;)

My OV 2.2.1 Novatek is now at Cyanogenmod -7.2.0-RC1_BACKside-IHO, eng.jerryscript-20120502.032319.

What do I have to do to install the VM Stock ROM (preferably the update with with ZV9 radio)? Do I install a recovery first? PerkinsII's sequence indicates you would first install the ROM, then the recovery.

What does JerryScript really mean? Is he leaving out a few steps, like clearing caches etc.?
 
Steps: Recovery (2.2.1)
-Open the folder holding the stock nandroid/recovery
-copy "recovery.img"
-plug in phone and mount it
-open sdcard
-paste it in the root of the sdcard (not inside any folders)
-extract "flash_image.zip" it till you have "flash_image"
-go to folder holding "flash_image" (it won't have an extension or picture in windows if you can getting a folder with zipper you didn't unzip)
-copy "flash_image"
-open sdcard
-paste it in the root of the sdcard (not inside any folders)
-copy "term.apk"
-paste it in the root of the sdcard (not inside any folders)
-extract "Superuser 3.0.7.zip"
-copy "Superuser.apk"
-paste it in the root of the sdcard (not inside any folders)
-unmount "usb storage" and unplug the phone
-hit home button
-open the app "ES File Explorer"
-click "Yes" if a popup comes up
-scroll down until you see "Superuser.apk"
-click on it
-there should be 2 choices "Install" or "Cancel"
-select "Install
-click "Done"
-scroll down until you see "Term.apk"
-click on it
-there should be 2 choices "Install or "Cancel"
-select "Install"
-select open after done installing
-type "su" and hit enter
-a message should come up saying "Allow" or "Deny"
-select "Allow"
-hit the back key
-open "Terminal Emulator" again
-*Note be very carefully entering in the commands, it's always a good idea to double or triple check to see if you entered it right
-type "su" (a # symbol should be right under the $ symbol) and hit enter
-type "mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system" and hit enter
-type "cat /sdcard/flash_image > /system/bin/flash_image" and hit enter
-type "chmod 755 /system/bin/flash_image" and hit enter
-type "mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system" and hit enter
-type "flash_image recovery /sdcard/recovery.img" and hit enter
-type "reboot recovery"
-now you should go into 100% Stock Recovery
-after it boots into recovery select "reboot phone"
-uninstall "Terminal Emulator and "Superuser"
-Enjoy :D
First of all I would like to thank you for the post as it worked perfectly!! I have a suggestion, you may want to either inform people that they need to download es file explorer from the internet once they have gone back to stock rom to avoid logging in or you may want to modify the stock rom so it includes es file explorer.
 
Should I be able to return to stock 2.2.1/Novatek using the current COT recovery?

Is there some reason why I would be better off changing the recovery to say VM670NH_recovery.img first?
 
Back
Top Bottom