11-01-2012 10:18 PM
125 12345
tools
  1. sdfgdsfgdfsg's Avatar
    I followed the instructions but my phone won't go past the 'LG" screen. Some help please?
    And yes, I did "Fix the Recovery Loop".
    02-10-2012 12:11 AM
  2. ehoser's Avatar
    I just burned BACKside and it worked. In fact I just waited on first bootup and it finally finished after a minute or two. I didn't need to pull the battery.

    I went about halfway through some other guides before I found this one. I did this all from Linux on a laptop. I rooted with Gingersnap (there were a couple of steps left out on the Linux instructions, like you have to chmod +x and then run the executable - duh.) I then installed the VM670NH_recovery using FlashImageGUI. That went OK. Then I found this saw this guide down the first page of the forum.

    Works fine now.

    One weird thing, and it doesn't have anything to do with this, when I went to connect to my wifi network it was listed as Open and didn't require a key.

    Update: I think it's GreenMachine that is causing the bootloop problem. I did not load it the first time and I didn't have to pull the battery. I went back tried it with GM and it hung on the boot. (BTW you should have pointed out that there are three phases of boot splashes - I.H.O. screen followed by BACKside screen and finally the Green Android "Always Backup" screen. Mine hung on the 3rd one.") I had to go back and redo it without GM since the recovery I used doesn't seem to have the Fix Boot Loop option.

    Also, I was able to boot back into recovery from an adb console without pulling the battery.
    02-12-2012 10:28 PM
  3. ehoser's Avatar
    Update2: No joy with Green Machine. I went back in an loaded the Xionia recovery, reloaded Backside plus GM and gapps. After it got stuck I booted into recovery and selected "Fix Boot Loop" but it still got stuck. Tried several times. maybe there is a version problem. I found that latest BACKside but used the GM from the OP.
    02-13-2012 04:30 PM
  4. LeslieAnn's Avatar
    Let me guess, newer Optimus...
    Run an md5 check on the file, ON THE SDCARD.
    Go into recovery, do "factory wipe" (in recovery!), then wipe data, system, boot, and in advanced wipe dalvik.
    Repeat.
    Now flash the zip, and repeat.

    Your phone isn't properly writing Framework or the launcher.
    Fickle memory is common on newer OV's.
    02-13-2012 04:46 PM
  5. ehoser's Avatar
    Let me guess, newer Optimus...
    Run an md5 check on the file, ON THE SDCARD.
    Go into recovery, do "factory wipe" (in recovery!), then wipe data, system, boot, and in advanced wipe dalvik.
    Repeat.
    Now flash the zip, and repeat.

    Your phone isn't properly writing Framework or the launcher.
    Fickle memory is common on newer OV's.
    It's a "newer" phone in an older box. It was running 2.2.2 so that's why I went to this guide.

    I just did md5sum on the three files I am flashing and they match with the ones I downloaded on my PC.

    Is there anything special about removing the battery? If I can run a shell from adb and do 'reboot recovery' is that the same thing?
    02-13-2012 05:11 PM
  6. LeslieAnn's Avatar
    However you get into recovery is fine.
    02-13-2012 05:25 PM
  7. ehoser's Avatar
    However you get into recovery is fine.
    Still no workee. I think I will just stick with plain BACKside for now.

    Thanks for the help.
    02-13-2012 06:02 PM
  8. paulkruger's Avatar
    See next post...sorry for typo in this entry.
    02-14-2012 10:43 AM
  9. paulkruger's Avatar

    Congratulations, your Optimus V is now rooted!

    Open up Terminal Emulator and type:

    1. su
    2. mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
    3. cat /sdcard/flash_image > /system/bin/flash_image
    4. chmod 755 /system/bin/flash_image
    5. mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
    6. flash_image recovery /sdcard/recovery.img
    7. reboot recovery

    This sequence of commands will install, and reboot you into, the (hopefully) working recovery.
    I am not sure what to do after step 2. This instruction does not state what the response to this line should be? What I get in terminal is:
    Usage: mount [-r] [-w] [-o options] [-t type] device directory
    Is this the expected and correct response to line 2? I tried twice with same result.

    Do I just continue with the next line?

    [ Optimus V, Android 2.2.2 ]
    02-14-2012 10:51 AM
  10. ehoser's Avatar
    A "Usage:" response means it didn't work. There was something wrong in the syntax of you command line. Either you didn't type it exactly or there is something wrong with the procedure. For myself, by the time I found this guide I had already flashed a recovery using a different method, so I skipped this step.

    I am pretty sure there is no response if the mount command works (in typical Unix fashion).

    Edit: I just tried various good and bad versions of the mount command. If it works all you get is the next command prompt: #. When I type in something with bad syntax I get a full page of help.
    celestelugo0 likes this.
    02-14-2012 11:36 AM
  11. paulkruger's Avatar
    A "Usage:" response means it didn't work. There was something wrong in the syntax of you command line. Either you didn't type it exactly or there is something wrong with the procedure. For myself, by the time I found this guide I had already flashed a recovery using a different method, so I skipped this step.

    I am pretty sure there is no response if the mount command works (in typical Unix fashion).
    Can you let me know what the other method you used was? I typed very carefully the command provided twice with same result. As far as this method goes I am at a stand still. At least being rooted allowed me to uninstall some of the crap-ware. I still wish to upgrade to a newer version of Android so I can install Flash 11 to access more content.
    02-14-2012 11:47 AM
  12. ehoser's Avatar
    Can you let me know what the other method you used was? I typed very carefully the command provided twice with same result. As far as this method goes I am at a stand still. At least being rooted allowed me to uninstall some of the crap-ware. I still wish to upgrade to a newer version of Android so I can install Flash 11 to access more content.
    Edit: I actually don't recall. There are several version floating around. I used Gingersnap to root, then it was kind of a mishmash of commands to flash. I did most of it from adb on Linux.

    You might want to try the mount command a few more times. Make sure you have spaces where they should be and no spaces where they shouldn't be. E.g. space after 'mount', space after '-o' (make sure it's lower case o, not zero), space after 'remount,rw', space after '-t', space after 'yaffs2', and space after '/dev/block/mtdblock5'.
    02-14-2012 12:07 PM
  13. riggerman's Avatar
    If you have already downloaded the recovery you want to install, search the market for " flash image GUI". I have read some threads on people using this to install their recovery for the first time
    celestelugo0 likes this.
    02-14-2012 12:32 PM
  14. ehoser's Avatar
    If you have already downloaded the recovery you want to install, search the market for " flash image GUI". I have read some threads on people using this to install their recovery for the first time
    You just jogged my memory. That's what I used.
    02-14-2012 12:59 PM
  15. Encerspay45's Avatar
    I did all the steps through Step 3, and after I typed "reboot recovery" and hit enter, it showed the LG logo, followed by a blank screen. Help!!
    02-18-2012 01:42 PM
  16. SuppliedRelic's Avatar
    Thanks for the tutorial, it helped me root my Optimus V.

    Sent from my LG-VM670 using Tapatalk
    02-26-2012 07:23 PM
  17. highhacker's Avatar
    STANDARD WARNING-- Flashing any custom ROM may semi-brick your phone!
    Follow the installation instructions to the letter!
    Always backup your apps, and do a backup in recovery before flashing!
    This is a WIP (work in progress)
    !


    Every mod from this guide will void your warranty
    . While an unscrupulous person will hide the fact that they modded their phone and request an in warranty exchange in the event of bricking, we know that your are too honest of a person to try such a thing. Realize that bricking and crying may result from any one of these mods. If you depend on your phone, consider the consequences of making your phone inoperable.


    Hi everyone,

    I have not seen a complete Tutorial out there for Root, Recovery, and installing a rom on the new 2.2.2 Android version Optimus V so....... Here it is--------------------------------------------------->

    Special Thanks to: Liquidsword76, bigsupersquid, blarfiejandro, JerryScript, a guest, RevolutionRed , and mmarz.


    STEP ONE

    Insure you are attempting this on a 2.2.2 Optimus V. Do this by going to "Settings" "About Phone" and look for heading titled "Android Version" it should say 2.2.2

    Next, download from the Android Market: OI File Manager and Terminal Emulator. Place these apps on your home screen. Now its time to un-mount your sdcard and mount it into your computer. Download the following:

    GingerBreak-v1.20.Apk (Place all files in folder named "CM7" unless otherwise noted) --- GingerBreak-v1.20.apk - 4shared.com - online file sharing and storage - download

    Xionia_CWMA_12518.6_VM_Recovery-signed (Unzip and place on root of sdcard, rename "recovery") --- http://forums.androidcentral.com/lg-...-2518-6-a.html

    Flash_image (unzip and place on root of sdcard) --- http://forums.androidcentral.com/lg-...-2518-6-a.html

    BACKside-IHO-VM670-11222011 --- BACKside-IHO-VM670-11222011.zip

    gapps-gb-20110828-signed --- Latest Version/Google Apps - CyanogenMod Wiki

    GreenMachineTheme-11222011 --- (Optional) GreenMachineTheme-11222011.zip

    Activate_Bootsound-signed --- (Optional) Activate_Bootsound-signed.zip

    Blackmart Alpha 0.49_b92.Apk --- (App Market) Blackmart Alpha 0.49_b92.apk - 4shared.com - online file sharing and storage - download

    KeyLights-0.2.Apk --- (Optional, Makes hard keys light up per notification) KeyLights-0.2.apk


    STEP TWO: ROOT

    Re-mount sdcard back into phone.

    Make sure USB debugging is enabled. Menu > Settings > Applications > Development > check mark USB debugging

    Open up OI File Manager and access your "CM7" folder and click on "GingerBreak". Follow prompts. Once inside GingerBreak app click "Root device". Your phone should now reboot, to make sure you successfully rooted your phone check your app drawer for SuperUser, If you have it your good. Another way to check is to go back into GingerBreak, if it gives you the option to un-root you know your good.

    Congratulations, your Optimus V is now rooted!


    STEP THREE: RECOVERY

    Open up Terminal Emulator and type:

    1. su

    2. mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

    3. cat /sdcard/flash_image > /system/bin/flash_image

    4. chmod 755 /system/bin/flash_image

    5. mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

    6. flash_image recovery /sdcard/recovery.img

    7. reboot recovery

    This sequence of commands will install, and reboot you into, the (hopefully) working recovery.


    STEP FOUR: CM7+ Bonus

    Note: use Volume rocker up and down to go up and down and the camera button to select

    VERY IMPORANT , Do not do anything else before you make a backup of your current rom in case something bad happens. Go to "backup and restore" and click "backup". Next click on "wipe cache partition" click ok. Next click on "advanced" then click on "wipe dalvik cache". Now we need to format some partitions, click on "format boot" do the same for "system" "data" "cache".

    Now for the fun, .

    Click on "install zip from sdcard" and then click on "choose zip from sdcard". Now click on folder "CM7" and choose each one and apply them. Once finished go back to the main screen in the Xionia cwma and click "reboot system now". Your first boot will get stuck in a bootloop on the bootsplash screen but dont worry. Pull your battery and then enter Xionia cwma by holding the "home" button, the "volume up rocker" and the "power button". Hold all three buttons until you see the blue text then release. Click on "advanced" "Fix recovery boot loop". Your phone should restart and be runnimg CM7. The only diffrance between phones running 2.2.1 and 2.2.2 is that in 2.2.2 your boot-splash screen freezes, but it still loads.

    If you wish to change the boot animation so your not "stuck" with the stuck animation visit this link --- [APP] Bootanimation Utility - 1.0.8 - xda-developers [APP] Bootanimation Utility - 2.0.5 - xda-developers

    Congratulations, your Optimus V is now running CM7!


    BONUS

    Re-download OI File Manager from the Android Market and enter your folder "CM7". Click on "KeyLights" then install, . Now, be off and customize away. Thank you everyone!!!!!!!!


    Photos

    https://www.facebook.com/media/set/?...1&l=6586ed4590
    there are Major problems with this tutorial . Number one is there are two versions of optimus v . both have 2.2.2 . one has the novatek screen and the other has the hatichi . this is for what version /? they are different . I have yet to see a definitive easy guide for both 2.2.2 versions . if you flash the wrong one it will be hell on earth to get it back to normal .
    02-27-2012 03:56 PM
  18. Shady24's Avatar
    there are Major problems with this tutorial . Number one is there are two versions of optimus v . both have 2.2.2 . one has the novatek screen and the other has the hatichi . this is for what version /? they are different . I have yet to see a definitive easy guide for both 2.2.2 versions . if you flash the wrong one it will be hell on earth to get it back to normal .
    I'm actually the op of this thread, just under a different screen name. Look at this link for info on finding out what screen you have. I'm pretty sure the phones I did this too were had the new screens but I'm not 100% sure. Ill do some research and update this. I've neglected this thread and I'm sorry, it should. Be updated in the next day or so.

    Different gen phones? - Android Forums

    terminal emulator: Code: dmesg | grep hitachi dmesg | grep novatek

    if you get output with the novatek line, you have an old (first-gen) OV. if you get output with the hitachi line, you have a new (2nd-gen) OV.

    the newer ones just have a different screen (and froyo 2.2.2 instead of 2.2.1, plus zv5 radio baseband instead of zv4.)
    02-27-2012 08:13 PM
  19. Julius910's Avatar
    Im gonna try this befor I do wat are some bonus things I can do with phone once its rooted beside become hot spot. I want to root so I can speed up the grp card and cpu so I can play ps1 games smoother. Thnks
    03-03-2012 07:39 AM
  20. rhea's Avatar
    I was able to flash recovery-clockwork-3.0.2.4-ov.img to my OV, 2.2.2 w/ hitachi screen which I downloaded from https://sites.google.com/site/bobzhomeroms/vm670 using Flash_ImageGUI, and it does seem to work (shows up with backup/restore option), but have read I should flash VM670NH_recovery.img. Should I do this before attempting the rom flash (CM7.2RC1-VM670-BobZhome-030312)? I'm just concerned that the wrong recovery may not flash the rom correctly. I have some experience through my rooted and rom'd pandigital novel and toshiba thrive, but each device is so different.

    If I do replace the recovery, can I flash the new recovery using the current recovery? I can use terminal or even try the Flash_ImageGUI app but was curious.

    As far as gapps goes, I perform a regular recovery zip-flash from sd card using that file AFTER I have flashed the rom and checked that all is working? Is that a correct assumption?

    I tried to send this via private message to BobZhome but haven't posted enough times.
    Thanks so much for your help.
    03-12-2012 11:34 AM
  21. DizzmalDan420's Avatar
    As long as you're currently able to boot into recovery, it won't hurt anything to flash a new ROM with the recovery you have installed. Just make a backup of your current OS before flashing. If you end up getting a bad flash, it's a simple matter to just go back into recovery and do a restore.

    One thing to be aware of, NEVER flash a new recovery AND a new ROM at the same time. Always be sure that at least one of them is working. If you have a working recovery you can fix a bad ROM flash and, conversely, if your OS is intact but a botched recovery, you can fix that from within the OS.

    You can flash a new recovery via your existing one assuming it's in a flashable .zip format. If it's an .img, flash image GUI should work fine.

    As far as Gapps goes, you flash the ROM first, then flash Gapps. No need to reboot in between.
    rhea likes this.
    03-12-2012 12:10 PM
  22. rhea's Avatar
    Thanks, dizzmaldan420. Duh, of course it has to be zip. I totally forgot about that. The recovery files are .img. You've given me what I need to take the plunge.

    Sent from my AT100 using Tapatalk

    EDIT: I flashed the newer recovery then bobzhome's latest+gapps. All appears to work well. I'm re-installing apps rather than TB restore. And, my Rii bluetooth keyboard with trackpad works! Thanks for your help.
    03-12-2012 02:12 PM
  23. clone_zeta's Avatar
    Thanks for the tutorial, I'm a total noob and made it through first time around without (serious) issues. One thing I have discovered is that now my Home button doesn't work anymore - is that a know issue? I also can't get into Android Market. I really liked Swype, can I get it back?
    03-13-2012 01:45 AM
  24. DizzmalDan420's Avatar
    Weird that your home key isn't working. Is it possible that you just need to define it's default action somewhere in the settings? When you say you can't get into Android Market, what exactly do you mean? Is the Market program giving you a force close when you try to open it? Or is the Market program missing completely? There are keyboards on the Market that have Swype incorporated into them, once your Market issue is straightened out.
    03-13-2012 01:54 AM
  25. clone_zeta's Avatar
    Weird that your home key isn't working. Is it possible that you just need to define it's default action somewhere in the settings? When you say you can't get into Android Market, what exactly do you mean? Is the Market program giving you a force close when you try to open it? Or is the Market program missing completely? There are keyboards on the Market that have Swype incorporated into them, once your Market issue is straightened out.
    re: Home key - I tried to set it's action via Settings>CyanogenMod settings>Input and there is no default for short pressing the key, just a long press setting. Either way, Long or Short press of Home doesn't do anything.
    re: Market - I am getting "Server Error" either on WiFi or 3G, using a previously working account
    03-13-2012 02:06 AM
125 12345
LINK TO POST COPIED TO CLIPBOARD