Sebastian (the magician who gave us gingerbreak) says that it only works in an ADB shell environment. It MIGHT work in Terminal Emulator but don't be surprised if it doesn't.
[How-To] Rooting LS670ZVD with GingerBreak (no reverting and OTA works too!)
- Thread starter drewwalton19216801
- Start date
Sebastian (the magician who gave us gingerbreak) says that it only works in an ADB shell environment. It MIGHT work in Terminal Emulator but don't be surprised if it doesn't.
I can do it using adb, I was just curious. It seemed logical to me that it could work. Don't know if I'll try or not but if I do I'll let you know how it goes. 
What if I am already rooted but on android version 2.2.2? How would I get Gingerbread while rooted still? Thanks.
What happens if I don't install a custom recovery and don't make a nandroid back up? Only asking cuz I finally got ROOTED, thanks to EVERYBODY, but I'm not sure how to install Xionia CWMA recovery kernel. I downloaded the files and extracted the RAR. Now what?
Well, IMO, you miss out on all the good stuff - flashing roms, customizations, etc. For safety purposes, you should make nandroids and you should clean caches, etc., as a prerequisite to flashing a rom, which is all supported in the custom recovery. In terms of installing CWMA, just follow the directions on the OP of that thread. If you are rooted, you are almost there, so don't give up now!
The easiest way is to flash one of the two available roms, in either zefie's (Scott Pilgrim) or pfer10's (AOSPCMod) threads. Or you can wait a while till gingergread is officially released for the Optimus and I'm sure KSmith, et. al., will be making a rom based on it.
Yes, even with OTA zvd update (see page 1). So much easier than jumping through all those hoops we had to jump through before!
Excellent! I'm so glad I happened upon this forum. You guys are great.
Keep up the good work!
Thanks!
Thanks a bunch for the new root method. I was sticking with V9 because I couldn't keep root in ZVD. This method is awesome! I tried it on my phone, and it worked on the first try. Then my wife's phone, which took two attempts. I really enjoy a pixel density of 140 and removing some apps like swype and talkback gives me precious memory back. Oh, and that loud boot sound is gone! Thanks again. Now I can schedule a reboot in the middle of the night.
Thanks a bunch for the new root method. I was sticking with V9 because I couldn't keep root in ZVD. This method is awesome! I tried it on my phone, and it worked on the first try. Then my wife's phone, which took two attempts. I really enjoy a pixel density of 140 and removing some apps like swype and talkback gives me precious memory back. Oh, and that loud boot sound is gone! Thanks again. Now I can schedule a reboot in the middle of the night.
I can get all the way to step 4 but once I copy and past everything cmd keeps telling me illegal number and permission denied. What am I doing wrong?
Thanks OP.
I was able to root my phone, A question 4 u , how do i unroot it to stock?
The thread just below this thread that says
http://forum.androidcentral.com/lg-...45403-how-unroot-your-phone-return-stock.html
How long is gingerbreak supposed to take?
I'm on my 2nd attempt and gingerbreak is failing ... I haven't been timing how long (I can do that if you want) but it's been at least 20 minutes.
So ... how long is gingerbreak supposed to take? I can revert to V9 and root that, but what a PITA.
I reverted to stock ZVD using KP500/LG Update tool and have verified that I have stock LG recovery.
Here's the gingerbreak command output:
I'm on my 2nd attempt and gingerbreak is failing ... I haven't been timing how long (I can do that if you want) but it's been at least 20 minutes.
So ... how long is gingerbreak supposed to take? I can revert to V9 and root that, but what a PITA.
I reverted to stock ZVD using KP500/LG Update tool and have verified that I have stock LG recovery.
Here's the gingerbreak command output:
Code:
$ ./gingerbreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to 7-4-3-C@web.de if you like
[**] Exploit may take a while!
[+] Detected Froyo!
[+] Found system: 0xafd14129 strcmp: 0xafd1cb9d
[+] Found PT_DYNAMIC of size 264 (33 entries)
[+] Found GOT: 0x000142a8
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0066 GOT start: 0x000142a8 GOT end: 0x000142e8
[*] vold: 0066 idx: -3072 fault addr: 0x000131d8
[+] fault address in range (0x000131d8,idx=-3072)
[+] Calculated idx: -1996
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[*] vold: 0945 idx: -0001996
[-] sendmsg() failed? # 150 more times!Picasticks: try running gingerbreak from a clean reboot (reboot and don't do anything else but follow the guide)
Gingerbreak should not take any longer than 30 seconds.
Gingerbreak should not take any longer than 30 seconds.
Running a third time now ... slightly less failure this time, it again identified fault address in range (0x000131d8,idx=-3072) and idx -1996 but this time is at least decrementing a little bit, after 20 minutes it is down to -1982.
I guess this is just some kind of buffer overflow exploit and it's just brute-forcing memory registers?
I'll let it go a while longer, but it has slowed down a lot and counting down to idx -0 could take weeks at this speed, so at some point I guess I'll give up and go to V9 and rageagainstthecage. Now that is a reliable instant exploit, none of this buffer overflow silliness!
I guess this is just some kind of buffer overflow exploit and it's just brute-forcing memory registers?
I'll let it go a while longer, but it has slowed down a lot and counting down to idx -0 could take weeks at this speed, so at some point I guess I'll give up and go to V9 and rageagainstthecage. Now that is a reliable instant exploit, none of this buffer overflow silliness!
picasticks,
how'd you get it to work on the 4th try? Is it just a matter of persistence? If it fails should I restart my phone and try again?
nvm got it now, now I'm trying to install the recovery, but I'm lost
how'd you get it to work on the 4th try? Is it just a matter of persistence? If it fails should I restart my phone and try again?
nvm got it now, now I'm trying to install the recovery, but I'm lost
Last edited:
Yeah, I just kept restarting and rerunning gingerbreak. This should do it to flash your recovery, no need to reboot or anything first. I would use a second terminal window for the 2 adb push commands while leaving yourself logged into the first terminal with the "#" adb root prompt for the three commands you enter via adb shell.
Code:
adb push flash_image /data/local/tmp/
cat /data/local/tmp > /system/bin/flash_image # from adb shell
chmod 755 /system/bin/flash_image # from adb shell
adb push your-recovery-of-choice.img /sdcard/
flash_image recovery /sdcard/your-recovery-of-choice.img # from adb shellThe root ran right after I posted that comment, however I'm not sure if it worked. I'm trying to flash the recovery rom but my phone dont seem to be taking it. Is there a way to confirm that my phone is rooted?
Similar threads
Trending Posts
-
Samsung Galaxy Tab A9 Plus (SM-X210) stuck in EDL Mode after USB port replacement – Need Firehose & XML files
- Started by aloha17
- Replies: 10
-
-
-
-
Facebook
Twitter
Instagram