[How-To] Root the LG Optimus V

[Ticojpunk]

The instructions here are outdated. Use the new Gingerbreak, install .apk and run it on the phone (no need to even connect to a PC, except to transfer the .apk file for installation.

Does everything work with Gingerbreak? Like all apps and phone functionality?


Sent from my VM670

 

[krings]

I got a replacement phone from VM. They gave me OS version 2.2.2.

The only method that worked is the gingerbread exploit method. I checked using terminal emulator and it showed the su command worked fine.

 

[Whyzor]

GingerBREAK is an .apk to root the Optimus V among other devices, not to be confused with Gingerbread (Android 2.3)

[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers

After that, I would suggest installing ROM Manager from the app market, and from there install a recovery (either xionia recovery image for flashing Harmonia Froyo 2.2 based ROM, or clockworkmod recovery image for flashing IHO/BACKside CM7.1 (Gingerbread 2.3 based ROM).

To summarize:

1. GingerBREAK to root the phone
2. ROM Manager to flash a recovery image (xionia or clockworkmod)
3. In recovery mode, wipe data, cache, dalvik cache, format /system, /data...etc.
4. Flash custom ROM in recovery mode (recommend Harmonia or IHO/BACKside)

 

[Ticojpunk]

GingerBREAK is an .apk to root the Optimus V among other devices, not to be confused with Gingerbread (Android 2.3)

[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers

After that, I would suggest installing ROM Manager from the app market, and from there install a recovery (either xionia recovery image for flashing Harmonia Froyo 2.2 based ROM, or clockworkmod recovery image for flashing IHO/BACKside CM7.1 (Gingerbread 2.3 based ROM).

To summarize:

1. GingerBREAK to root the phone
2. ROM Manager to flash a recovery image (xionia or clockworkmod)
3. In recovery mode, wipe data, cache, dalvik cache, format /system, /data...etc.
4. Flash custom ROM in recovery mode (recommend Harmonia or IHO/BACKside)

Thanks for the breakdown. Unfortunately, a lot of that is still Greek to me. And I have read a lot already on rooting.

Basically, all I want to do is root so I can use link2sd to make more room available for apps on my Optimus V. Really not interested in custom ROMs or anything.

What's the best way for me to accomplish that? I don't want my phone to look or act any different, and I definitely cannot risk bricking.

 

[Whyzor]

Thanks for the breakdown. Unfortunately, a lot of that is still Greek to me. And I have read a lot already on rooting.

Basically, all I want to do is root so I can use link2sd to make more room available for apps on my Optimus V. Really not interested in custom ROMs or anything.

What's the best way for me to accomplish that? I don't want my phone to look or act any different, and I definitely cannot risk bricking.

One runs the risk of bricking as soon as they have root. Installing a recovery image actually allows you to make a backup of the original ROM before changing things. In your case you could just use gingerbreak to get root & then install link2sd, but if you don't make backups (via a custom recovery image), who knows if a buggy link2sd app released in the future could brick your system (since it has root access, it has the possibility of doing more damage than a non-rooted phone.

Actually Froyo already has the feature to move some parts of apps (if the developer allows it) to the sdcard. In the settings - applications - specific app, there's a 'move to sdcard' button. It's probably safer to just use that.

 

[Ticojpunk]

Actually Froyo already has the feature to move some parts of apps (if the developer allows it) to the sdcard. In the settings - applications - specific app, there's a 'move to sdcard' button. It's probably safer to just use that.

I've already used the built in utility to move everything that can be moved to the sd card. Unfortunately if I have everything installed that I want to use it leaves me with 10-20MB free.

 

[Ticojpunk]

The instructions here are outdated. Use the new Gingerbreak, install .apk and run it on the phone (no need to even connect to a PC, except to transfer the .apk file for installation.

So does Gingerbreak do essentially exactly the same thing as the step by step in this sticky? Are there any differences in results or risk?

 

[Whyzor]

So does Gingerbreak do essentially exactly the same thing as the step by step in this sticky? Are there any differences in results or risk?

I believe Gingerbreak is simpler, so there's less chance of messing up (risk?). If it doesn't work (maybe in the recent VM 2.2.2 ROMs), then you'll have to try another method. The ultimate goal here is to gain root access (think of it as hacking into a windows machine to get Administrator rights).

 

[Ticojpunk]

I believe Gingerbreak is simpler, so there's less chance of messing up (risk?). If it doesn't work (maybe in the recent VM 2.2.2 ROMs), then you'll have to try another method. The ultimate goal here is to gain root access (think of it as hacking into a windows machine to get Administrator rights).

Cool. I fully understand rooting. I have some unix/Linux experience. The part that's unclear is flashing a custom recovery. I know the term "flashing" as in flashing a BIOS, which would be updating/replacing a bios in a computer motherboard. When you flash a custom recovery, are you replacing the software on the phone? Or is it something different?

 

[Whyzor]

Cool. I fully understand rooting. I have some unix/Linux experience. The part that's unclear is flashing a custom recovery. I know the term "flashing" as in flashing a BIOS, which would be updating/replacing a bios in a computer motherboard. When you flash a custom recovery, are you replacing the software on the phone? Or is it something different?

The recovery image is a separate bootsector (not exactly sure if that's technically correct). It's separate from the main OS. Custom recovery images have basic features that the stock recovery image that came with LG doesn't, like backup/restore images, flashing newer zips by name, wiping partitions...etc. So flashing a custom recovery image allows the main OS partition to be modified without using it. Even if the main OS partition gets corrupted or hosed, one usually can boot into the recovery image to restore an older backup. BTW 'flashing' is the term used because on phones the permanent storage is the ROM.

 

[txrngr]

everytime i run superoneclick i get this msg any idea what i need to do
Could not load type 'AdbInterface.AdbCommands.RunExploit' from assembly 'AdbInterface, Version=1.0.1.0, Culture=neutral, PublicKeyToken=null'.
FAILED

 

[psnowatzki]

Yada yada post

 

[koopakid08]

everytime i run superoneclick i get this msg any idea what i need to do
Could not load type 'AdbInterface.AdbCommands.RunExploit' from assembly 'AdbInterface, Version=1.0.1.0, Culture=neutral, PublicKeyToken=null'.
FAILED

It sometimes takes 5 to 10 times for it to work. Just keep trying.


Sent from my LG Optimus V using Tapatalk

 

[Whyzor]

everytime i run superoneclick i get this msg any idea what i need to do
Could not load type 'AdbInterface.AdbCommands.RunExploit' from assembly 'AdbInterface, Version=1.0.1.0, Culture=neutral, PublicKeyToken=null'.
FAILED

I hate to sound like a broken record, but use the newer GingerBreak to root instead of superoneclick, it's easier and less chance of messing up.

[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers

 

[SecularSanity]

The LG tool downloads but i keep getting some message that says it will be down for maintenance from 7-3 to 7-4. It won't load. Any suggestions?

 

[allcaps33]

thank you revolutionred!!! it worked... but after a few modded steps.... for whatever reason i had to go back and chmod superuser. i also had to chmod my wifi tethering app too. at first i thought that didn't work. but i remembered seeing somewhere that if i had difficulties with anything, to try booting in "recovery" mode. Unfortunately, I don't know the difference between "recovery" and "Safe" mode... but I was able to boot into "Safe" mode. BAM! right when the home screen loads there they were, superuser and wifi tether. (For those who don't know, only stock apps appear in "Safe" mode, which means if you downloaded an app, it will NOT appear when booting into "Safe" mode.) It took some work, but I finally got it! Thank you very much for this How-To!!!

 

[allcaps33]

This add-lib assumes you use Windows.

Here's what I did:

Followed all instructions... (duh)
It actually took 2 or 3 times. All with negative results. I shut down the program and rebooted my phone. For some reason- when I reconnected my phone, it installed several sets of drivers that did not install before...

After that, I unrooted my phone. Then I started all over, this time I only went through the process once.
I clicked "Shell Root", followed the instructions. When I tried several apps that required root, they did not work. I ran the root checker (available in the Android Market) and it said I was rooted. Hmm...

Most people think you need the Android SDK to use adb. This is a lie. Since you've already downloaded SuperOneClick, open the folder. Copy the "ADB" folder, and paste it to C:

Make sure your phone is connected, and SuperOneClick is STILL RUNNING.
Open up the command line (cmd.exe), cd to C:\ADB.
Now type:

adb shell
cd data
cd app

Now find the app you want to run with root permissions.
I wanted to run my wifi tether to so I typed this:

chmod 4755 android.tether-1.apk

Now find the superuser file (it should be something like "android.superuser-1.apk") and chmod to 4755.

Now close SuperOneClick, unplug the phone and shut it down completely. Press and hold the camera button, the home button, and the volume up button. While HOLDING all of these, turn the phone on. If done correctly, the phone should boot into "Safe" mode.

Any apps that you've changed the permissions on should appear on the home screen, or where ever you keep them.

Run Superuser, then press the home button. Now run the app you want to give permanent permissions to. Just before the app starts, you will get a screen that asks if you want to allow or deny the app to run. Click allow for the apps you want run. Now reboot your phone.

Now run the program(s) again, and superuser will pop up, asking if you want to allow the app to run.

Whew, that's it! you're done! Hopefully I have helped in some way. I did right this addendum a bit fast, so if you have any questions, please post and I will re-write what I did.

I am new to the site, but if its possible for you to email, or PM me, then go ahead, I will explain it in better detail.

Thanks again RevolutionRed!!!

 

[teameno2]

i am good with computers but i cant get this to work at all from super1click. this is what keeps coming up on the screen.
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...

OK 0.08s

Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

OK 4.19s

Waiting for device...

OK 130.62s

Checking if rooted...
False
OK 0.70s

Getting manufacturer...
LGE
OK 0.06s

Getting model...
VM670
OK 0.08s

Getting version...
ZV5.41C0E845
OK 0.03s

2.2.2
Rooting device... - Step #1
523 KB/s (585731 bytes in 1.092s)

OK 1.22s

Rooting device... - Step #2

OK 0.03s

Rooting device... - Step #3

OK 0.05s

Rooting device... - Step #4


property service neutered.

killing adbd. (should restart in a second or two)


OK 0.03s

Rooting device... - Step #5

OK 8.19s

and that is it. does not do nothing else. i then tried to do the command promp. i get to the part where i enter adb shell and it comes back saying closed. can someone pleae help. thank you

 

[jdcnosse]

Just curious...I tried searching the forums but apparently my search terms are too short.

Does it matter if I install the x86 or x64 version of the JDK? I figured to install the x86 since my phone isn't 64-bit...

 

[zedorda]

If the host desktop has a 64-bit OS use the x64 drivers. There is a better way to root check the sticky threads.