[How-To] Root LG Optimus S
- Thread starter KSmithInNY
- Start date
- Status
Even though it doesn't work, you are getting a different error so it isn't working for a different reason. Please post the output.
I don't see anything obviously wrong.
Does the recovery menu come up?
Are you using custom or stock recovery?
Try shutting down, pulling the battery, and boot into recovery. See if there is any difference.
I can have you reset the /persist partition, but want you to try the stuff above first.
Will do in the morning. Question though - at the very beginning, we had to download 3 files into the tools folder. Should those have gone into the platform-tools folder instead?
Sfhub i used bothe recovery ra
gnm-thunderc-s
and recovery thunderc-s ra-v1.2
it makes no different still same problem
e;canot presiste
gnm-thunderc-s
and recovery thunderc-s ra-v1.2
it makes no different still same problem
e;canot presiste
That's the kicker. Put the files in the platform-tools directory and start over from the beginning.
They should have gone in whichever directory contained adb.exe.
The commands to "adb push" them to your phone should not have failed.
So, I got this far but then sort of confused about starting over. Do I "adb shell" on the same screen (see below) or do I open a completely new cmd? If a new cmd, what command prompt do I start with? Sorry for the noobie questions - I'm a wanna be geek. 
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3374, 3374}
[*] Searching for adb ...
[+] Found adb as PID 79
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\Android\android-sdk\platform-tools>adb shell
$
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3374, 3374}
[*] Searching for adb ...
[+] Found adb as PID 79
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\Android\android-sdk\platform-tools>adb shell
$
Yes, you just keep going through the iterations of running rage, getting kicked out of adb shell, starting a new adb shell.So, I got this far but then sort of confused about starting over. Do I "adb shell" on the same screen (see below) or do I open a completely new cmd? If a new cmd, what command prompt do I start with? Sorry for the noobie questions - I'm a wanna be geek.
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3374, 3374}
[*] Searching for adb ...
[+] Found adb as PID 79
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\Android\android-sdk\platform-tools>adb shell
$
It can take 1-30+ times to get the "#" prompt instead of the "$" prompt. You just keep doing it until it is successful in giving you "#" prompt, then continue with the instructions.
I don't recall what version of the LG software you are running. If it is ZV9, then you can use z4root.apk instead of running rage. It will get you root faster.
ZVD, I looked at that option already.
I guess I know what I'll be doing the rest of today! You'll hear me scream when I finally get it. ha!
Did you revert to ZV9? ZVD isn't directly rootable, so you'd be wasting your time. You should actually be following the ZVD rooting thread, not this one, which is for an older release.ZVD, I looked at that option already.
I guess I know what I'll be doing the rest of today! You'll hear me scream when I finally get it. ha!
http://forum.androidcentral.com/lg-...-guide-rooting-software-version-ls670zvd.html
I thought I read somewhere ZVC wasn't rootable, or maybe just this process wouldn't work for it. I'll go to the other thread and see what happens.
you have to go to V9 first. Then root it with z4root. Did you already do this?
Sent from my LS670 using Tapatalk
ZVC and ZVD are not directly rootable. You need to revert to ZV9 first. Instructions are in the thread I referred you to above.
This no longer works.
I've been back and forth with this the better part of a day. Apparently since Virgin upgraded to 2.2.1 sometime earlier this year, the new SW Version is VM670ZV4 and the directions are no longer valid.
It looks like without a PC I'm screwed.
I've been back and forth with this the better part of a day. Apparently since Virgin upgraded to 2.2.1 sometime earlier this year, the new SW Version is VM670ZV4 and the directions are no longer valid.
It looks like without a PC I'm screwed.
rooting the lg optimus s
I did everything up to the when the disconnect and when it reconnect i wait for like 5 minutes and then put the "adb shell" in and i still get the $ sign can some one please help me
thank you
WARNING - This is a cat and mouse game we play with manufacturers. I guarantee you an update will come from LG that patches this exploit and will prevent people from rooting. It will also close your root access if you've already rooted using this method. Long story short, NEVER ACCEPT OTA UPDATES FROM THE CARRIER OR MANUFACTURER.
As my prediction above stated ......
WARNING WARNING!!! Sprint is pushing out an updated named LS670ZVC starting on 2/7/2011. This update breaks this root process. Open Menu > Settings > about phone > if SW Version = LS670ZVC then this process will not work for you. WARNING WARNING!!!
Notice: There is now an application available called z4root which roots your phone using the same method detailed below. This has been confirmed to work on the Optimus line. Click THIS for more information. I feel the knowledge gained by doing this process yourself rather than a 1-click method will prove to be invaluable down the road if/when you encounter any issues but either way works.
To MAC users: Please see THIS POST by mfldmike to get you going.
For those who learn visually, iamlilysdad has put together an awesome walkthrough video of this process which you can find HERE
Complete Idiots guide to Rooting the Optimus S can be found HERE. Thanks Dishe.
What You'll Need:
- Sun JRE, FOUND HERE
- The Android SDK, FOUND HERE. Install this on the root of your computer so the path is C:/android
- Drivers for the LG phone installed on your computer. Instructions can be FOUND HERE courtesy of our favorite android hacker, modder, developer, blogger (jack of all trades) gbhil
- And the file I have attached to this post. Download it, unzip it, and put the 3 files inside in your android-sdk-windows\tools folder created from installing the SDK.
/\You need to have installed/done all of the stuff in the "what you'll need" section. From this point on I'll assume you've done that./\
This method has been confirmed on V6, V8, and V9 versions of the Optimus S software.
Ready?:
Step 1: Plug your phone into your PC with the USB cable.
Step 2: Make sure the phone is charge only (don't mount as USB drive) and USB debugging is enabled. Menu > Settings > Applications > Development > check mark USB debugging
Step 3: Launch the SDK manager, should be something like C:/Android-sdk-windows SDK Manager
Step 4: Open a CMD window and type the following:
cd c:\wherever-your-sdk-tools-folder-is (mine for example is C:\android\tools however in the new SDK the correct directory would be "Platform Tools", and not just "tools". See what you have on your directory)
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb shell
chmod 4755 /data/local/tmp/rageagainstthecage
chmod 4755 /data/local/tmp/busybox
cd /data/local/tmp
./rageagainstthecage (let things sit a couple minutes (2), your phone will disconnect from the computer and you'll be removed from your ADB session)
adb shell This should return a "#" symbol instead of a "$" symbol. If it does you're good. If not go back and start from the beginning of step 4
mount -o remount,rw -t yaffs2 /system /system
cd /data/local/tmp
./busybox cp su /system/bin
./busybox cp busybox /system/bin
cd /system/bin
chmod 4755 su
chmod 4755 busybox
exit
exit
Step 5: Go to the android market on your phone and download "Superuser"(free). The developer will be listed as ChainsDD.
Donations:
What I ask is, if this helps you root, tweak, or modify your phone, please watch this thread and help someone who may be experiencing issue. Yes, I am asking you to donate your time. The same donation I made while writing this so you could root your phone
Thanks:
gbhil - as always thanks, you rock rainman lol.
Sebastian Krahmer - Without your exploit many phones would not be rooted today.
iamlilysdad - for making the walkthrough video and sticking around and providing so much support for new users during this process.
I did everything up to the when the disconnect and when it reconnect i wait for like 5 minutes and then put the "adb shell" in and i still get the $ sign can some one please help me
thank you
good luck
Well, first I would recommend confirming you don't have root by typing 'su' without the '' in your adb shell. If you still do not get a #, than you definitely don't have root.
Rather than going through rage again, I'd recommend glancing back at a few other replies, I tried rage myself; found it was not worth the time used.
Did z4 worked perfect.
Skip to z4
Well, first I would recommend confirming you don't have root by typing 'su' without the '' in your adb shell. If you still do not get a #, than you definitely don't have root.
Rather than going through rage again, I'd recommend glancing back at a few other replies, I tried rage myself; found it was not worth the time used.
Did z4 worked perfect.
Skip to z4
Last edited:
error: device not found
Hi,
I have a problem with my LG P500h.
after executing rageagainstthecage the session restarts ok but when I run "adb shell" again I got the following error:
The android version installed is 2.2
and the firmware ver. is V10a
Thanks!!
Jorge.
Hi,
I have a problem with my LG P500h.
after executing rageagainstthecage the session restarts ok but when I run "adb shell" again I got the following error:
Code:
$ ./rageagainstthecage
./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3337, 3337}
[*] Searching for adb ...
[+] Found adb as PID 1290
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email]7-4-3-C@web.de[/email] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\android-sdk\platform-tools>adb shell
error: device not foundThe android version installed is 2.2
and the firmware ver. is V10a
Thanks!!
Jorge.
This isn't the right forum for your phone.
It is likely your Android version isn't 2.2, but actually 2.2.2
They blocked rooting in 2.2.2.
You'll probably need to downgrade to an older version, but we don't have the specifics for your phone on this forum.
It is likely your Android version isn't 2.2, but actually 2.2.2
They blocked rooting in 2.2.2.
You'll probably need to downgrade to an older version, but we don't have the specifics for your phone on this forum.
- Status
Similar threads
Trending Posts
-
-
-
-
Question Android 14: Is there a Do Not Disturb Feature?
- Started by tinker1234
- Replies: 1
-
Facebook
Twitter
Instagram