Rooting 2.2.2

Devcomm

Member
Feb 12, 2011
22
1
0
Anyone able to point me in the right direction on rooting 2.2.2? I got a warranty replacement phone from VM and it came preinstalled with 2.2.2. I've tried the normal method of using SuperOneClick that worked on 2.2.1, but it fails everytime on 2.2.2. I've searched around and havent come up with anything specific to the V.

That being said, is there any way I can help out by making a dump of my phone since it has 2.2.2 and the V5 radio preinstalled? Maybe this would allow the devs to incorporate it into their ROMs.
 
Anyone able to point me in the right direction on rooting 2.2.2? I got a warranty replacement phone from VM and it came preinstalled with 2.2.2. I've tried the normal method of using SuperOneClick that worked on 2.2.1, but it fails everytime on 2.2.2. I've searched around and havent come up with anything specific to the V.

That being said, is there any way I can help out by making a dump of my phone since it has 2.2.2 and the V5 radio preinstalled? Maybe this would allow the devs to incorporate it into their ROMs.
Use Gingerbreak
 
i successfully shell rooted and pushed busybox and su through ADB on a 2.2.2 Optimus V recently.

no troubles at all.
 
Gingerbreak doesn't work either. It's been "Rooting" and "Running Exploit" for about 15 minutes now and it's not rebooting or showing any signs of progress.

watskyhotsky, mind explaining the steps you went through to root via ADB?
 
Gingerbreak doesn't work either. It's been "Rooting" and "Running Exploit" for about 15 minutes now and it's not rebooting or showing any signs of progress.

watskyhotsky, mind explaining the steps you went through to root via ADB?

the EXACT same steps in the how to root guide. worked on 6 Optimus Vs so far, one was the 2.2.2 V.


one a 2.2.1 V I accidentily clicked "root" in SuperOneClick, and it automatically did all the steps, pushed busybox and su on its own, but everytime I restarted the phone I lost root, and it was a nightmare to fix.

on THAT phone I ended up having to manually replace a lot of files with stock files in the Shell Root via ADB. then do the entire process over again using shell root and ADB to push the busybox and SU files that are downloadable from the HowToRoot thread. only when I re did the process in this way did the phone keep a permanant root.

its the exact process used in the How To Root thread.

it worked on the next phone which was a 2.2.2
 
Gingerbreak doesn't work either. It's been "Rooting" and "Running Exploit" for about 15 minutes now and it's not rebooting or showing any signs of progress.

Go to Settings > Applications > Development. Make sure USB debugging is checked.
 
I've succesfully rooted 3 2.2.1 OVs using the methods outlined in the rooting post. However it just is not working like expected with my 2.2.2 OV. Here is what SuperOneClick has to say:

SuperOneClick v1.6.3.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1449 KB/s (585731 bytes in 0.394s)
OK
chmod psneuter...
error: closed
FAILED


I then updated to the newest version of SuperOneClick, got the same thing:

SuperOneClick v1.9.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1505 KB/s (585731 bytes in 0.379s)
OK
chmod psneuter...
error: closed
FAILED


I also tried it using the GingerBreak Exploit in the new SuperOneClick. Same Result except replace psneuter with GingerBreak in the above. I'm at my wit's end here. No clue why it would work fine for someone else's 2.2.2 OV but not mine. It seems to push the exploit fine, but then has trouble when using the chmod command to change the permissions. Any tips/help would be much appreciated. I just want to get a recovery on here!

Edit: when I try to run the adb shell command it returns "error: closed" just like in the SuperOneClick log. Not sure why that would happen.
 
Last edited:
You root it like any other developer phone.

ADB and Fastboot if you don't already have them: Windows (drivers) Linux
Recovery: http://download.clockworkmod.com/recoveries/recovery-clockwork-3.2.0.1-thunderc.img
Superuser: http://downloads.androidsu.com/superuser/su-2.3.2-efgh-bin-signed.zip
Busybox: http://cmw.22aaf3.com/common/busybox.zip

Put superuser.zip on your sdcard, decompress busybox and put it there too.
Enable usb debugging in Settings -> Applications -> Development
Then enter these commands

adb reboot bootloader
fastboot flash recovery recovery-clockwork-3.2.0.1-thunderc.img
fastboot reboot
adb reboot recovery

Flash superuser from recovery, reboot.

adb remount
adb shell
su
cd /system/bin
cat /sdcard/busybox > busybox
chmod 4755 busybox
exit

You're done. Isn't an unlocked bootloader great ladies and gents?
Also maybe you could help a few people out and dump the firmware for people here to use :)
 
Last edited:
I appreciate the information uber. I followed your instructions to the letter. However, when I type "adb reboot bootloader" it just restarts the device like normal, into android. I even tried "adb reboot-bootloader" like it suggests in the adb help to no avail. Trying to run the fastboot commands after that just results in "waiting for device" indefinitely.
 
Both should technically work unless LG is now locking the bootloader on phones (which would be a very bad thing). ADB - CyanogenMod Wiki

If LG did indeed do this with newer revision phones you're going to be stuck unless you can run an exploit like gingerbreak.
 
the V5 radio looks interesting, it's not something we can get with all the custom ROMs right? maybe it has better signal reception... or better 3G... Would it even be possible to flash that on our V's?
 
Leslieann is working on getting the new radio ported over now. She has already posted a patch for the new market, mms, and email app from the new 2.2.2 stock rom. Give her some time and I'm sure she'll get the radio working for us.
 
Both should technically work unless LG is now locking the bootloader on phones (which would be a very bad thing). ADB - CyanogenMod Wiki

If LG did indeed do this with newer revision phones you're going to be stuck unless you can run an exploit like gingerbreak.

Is there a way to figure out for sure whether or not the bootloader has been locked? I'm thinking this is the case since nothing I've tried seems to work at all, but even adb doesn't seem to work right from time to time with the "error: closed" response. I just want to get this thing rooted!

As for the radio update, so far I'm not very pleased with it. It seems that battery life is much worse for me on 2.2.2 over stock 2.2.1 and horrendous compared to the ROMs that are available. Not sure whether this is due to the radio update or due to the software updates. According to Spare Parts, Email uses a ton of battery under partial wake and seems to be unkillable. Maybe they changed the way push retrieval works or something.
 
I ran Gingerbreak, and it doesnt boot into recovery or fastboot, im guessing the bootloader is locked?
 
I ran Gingerbreak, and it doesnt boot into recovery or fastboot, im guessing the bootloader is locked?

Gingerbreak only allows you to gain root access after reboot. It doesn't flash a new recovery image, boot into recovery, or do much of anything else. To verify that you have root, run 'su' in a terminal emulator and see if you can become super-user.
 
Gingerbreak only allows you to gain root access after reboot. It doesn't flash a new recovery image, boot into recovery, or do much of anything else. To verify that you have root, run 'su' in a terminal emulator and see if you can become super-user.

Right, but if Gingerbreak doesn't cause the phone to reboot like it says it will do upon completion, then you're not going to have root access. That is the problem that I am having anyway. Maybe elalan5 is experiencing something else. Gingerbreak will say it's doing it's thing indefinitely, which makes me think that the bootloader is now locked, but I have no way of confirming this.

Elalan5: Have you tried rooting the "normal" way from the rooting thread yet? If not try that and report back here please.

If anyone knows of a way to confirm whether or not the bootloader is now coming locked on these phones it would be very much appreciated.
 
Anyone have any further information about this? It would be much appreciated if I could figure out a way to root, or figure out whether or not the bootloader is now coming locked down.
 
Gingerbreak.apk will work.EDIT: make sure USB debugging is checked. It can sometimes be a little picky about the SD card.Delete the Gingerbreak.apk that is on your phone. Try putting the stock 2G sd card into PC using supplied adapter. If you need to save anything that's on the SD card make a new folder a move those items into it. Go to start/computer/right click on SD card. A window will pop up select Format, another window will pop up. Select Restore device defaults. Select start. When done move just the Gingerbreak.apk to the SD card.(make sure you have a file manager in the phone).Safely remove SD card and reinsert into phone. mount SD card. Using file manager select the Gingerbreak.apk and open it up click on install. Once it installs select done and exit.Reboot phone. Open up app drawer and select Gingerbreak.apk. Run exploit. If it has not installed after 12min. pull battery and try again(It sometimes takes a couple of tries). Every failed attempt you need to reboot.That's essentially what you are doing with a battery pull. It will work. if not on the first or second try then on the third. When done go to the market and download Busybox installer. Using a file manager find out where su was installed,either /system/bin or /system/xbin. Install Busybox in the same place as su. Go to the market and update su. If you want you can download root checker and run it for peace of mind. Then go back and transfer the data you put in the folder on your PC back into the SD card. I ROOTED with the Gingerbreak.apkEdit: Gingerbreak will not install the proper flash_image to flash a recovery.If not using ROM Manager to flash CWM 3.2.0.1 then you will have to flash the proper one using command prompts.
 
Last edited:
I just received an exchange phone from virgin mobile today because my other phone had freezing issues... so my new phone shipped with 2.2.2 and the first thing I did was root the phone with gingerbreak and the phone restarted in 2 mins and I have superuser. I have an unrelated question? Can I download clockmod recovery and download and install 2.3.4 using android 2.2.2 ?
 
I just received an exchange phone from virgin mobile today because my other phone had freezing issues... so my new phone shipped with 2.2.2 and the first thing I did was root the phone with gingerbreak and the phone restarted in 2 mins and I have superuser. I have an unrelated question? Can I download clockmod recovery and download and install 2.3.4 using android 2.2.2 ?

Yep same as 2.2.1 as long as you have root.


---
- Sent from my LG Optimus V using Tapatalk
 

Trending Posts

Forum statistics

Threads
956,900
Messages
6,970,515
Members
3,163,643
Latest member
stonefruit