[How-To] Root LG Optimus S

Status
Not open for further replies.
Hey guys, i am attempting to root my lg optimus s, i downloaded everything, i open up cmd, and then go away entering the commands, all is well until i get to the ./rageagainstthecage it completes this proccess successfully and my phone disconnects twice but when i go to type abd shell it pops up with $ sign, i have repeated proccess at least 15 times now. I'm not sure what to do.
rage exploits a race condition that doesn't always hit gold. It can seriously be 1 - 50 attempts before it hits.

If you have V8/V9 Android you can use z4root which usually works on the first try.
 
Well - with the firmware push this morning which killed my quick settings / hotspot ability, I guess I am going to have to attempt a phone root.

I see so many different options and so many different ways people say "this is best, that is best" and I also see things like "if you have this, don't do that" and I"m unsure what I am suppose to do next.

And, with the rapid changes, is any of the rooting stuff effective if I already got hit with this firmware update ?
Everything you need is in the ZVD root thread. It references the revert thread in my signature. You need to revert to V9 before going back to VD to get your root back. You can also choose to go back to VC and get your stock hotspot. Otherwise TR1.8.x is what you want of if you want hotspot with VD.
 
UGH!

Okay, i've done everything in the beginning and when i start to enter the abd into the cmd it always says this...
" 'abd' is not recognized as a internal or external command, operable program or batch file. "

I may sound like a complete tard (I'm totally new to this whole rooting thing)

Everytime i try to enter the first 'abd' cmd it always shoots this!
I'm frustrated and it may just be something I did wrong in the beginning....blah.

Any help?? :(


(i've tried to find the Z4root in the market and i guess sprint might have taken it out...can't find it :( )
 
Okay, i've done everything in the beginning and when i start to enter the abd into the cmd it always says this...
" 'abd' is not recognized as a internal or external command, operable program or batch file. "

I may sound like a complete tard (I'm totally new to this whole rooting thing)

Everytime i try to enter the first 'abd' cmd it always shoots this!
I'm frustrated and it may just be something I did wrong in the beginning....blah.

Any help?? :(


(i've tried to find the Z4root in the market and i guess sprint might have taken it out...can't find it :( )

You have to cd to the directory where your adb is located. For example, it could be:

>cd c:\android-sdk-windows\platform-tools or
>cd c:\android-sdk-windows\tools

Then try running the adb commands.
As far as z4 goes, Google search. It is available for download at Xda.



Sent from my VEGAn-TAB using Tapatalk
 
I stupidly accepted the system update that broke free-tethering on 3/15. Was going to root, but I see this is foiled as well! Bah to LG and Sprint for being such dingos. Lesson learned now I guess.

Anyway, any chance for a new root process that works around this, or is this thing locked up tight now?

Either way, I want to thank much for all the wonderful work you are doing.
 
I stupidly accepted the system update that broke free-tethering on 3/15. Was going to root, but I see this is foiled as well! Bah to LG and Sprint for being such dingos. Lesson learned now I guess.

Anyway, any chance for a new root process that works around this, or is this thing locked up tight now?

Either way, I want to thank much for all the wonderful work you are doing.

Here you go. http://forum.androidcentral.com/lg-...-guide-rooting-software-version-ls670zvd.html

Thats how you root now.
 
downloaded the link for JRE and installed, then downloaded SDK and tried to install it and the installer told me i needed JDK. twice now on two different computers even after i installed JDK and tried to install again. it keeps telling me in need jdk and it wont let me go any further. guess i'm stuck..
 
Last edited:
downloaded the link for JRE and installed, then downloaded SDK and tried to install it and the installer told me i needed JDK. twice now on two different computers even after i installed JDK and tried to install again. it keeps telling me in need jdk and it wont let me go any further. guess i'm stuck..

1) Are you running Windows 64-bit?
2) If the answer to the above is yes, did you install the 32-bit or 64-bit JDK?
3) If the answer to the above is 64-bit, you need the 32-bit JDK. You can blame Google for this.
 
downloaded the link for JRE and installed, then downloaded SDK and tried to install it and the installer told me i needed JDK. twice now on two different computers even after i installed JDK and tried to install again. it keeps telling me in need jdk and it wont let me go any further. guess i'm stuck..
I had the installer throw up the same problem for me. (win7 x86 here)

Try just grabbing the zip version of the android sdk. I unzipped it, ran the sdk manager, installed the platform tools, added the platform-tools folder to my system path, and adb works perfectly. I've had no problems using the lg mobile support tool to go from v9 to vd, nor using adb shell. Maybe I'd run into problems if I were actually developing with the android sdk, I dunno, but I honestly think it's just a detection glitch with their installer.
 
I had the installer throw up the same problem for me. (win7 x86 here)

Try just grabbing the zip version of the android sdk. I unzipped it, ran the sdk manager, installed the platform tools, added the platform-tools folder to my system path, and adb works perfectly. I've had no problems using the lg mobile support tool to go from v9 to vd, nor using adb shell. Maybe I'd run into problems if I were actually developing with the android sdk, I dunno, but I honestly think it's just a detection glitch with their installer.

No kidding detection glitch. You can also rip the platform-tools out of the OSCC 2.0.000 alpha build and use it without the Android SDK itself :cool:. As soon as I get some replacement RAM from Crucial (which will take about a week and a half), I'm gonna make a platform-tools installer for the folks that don't necessarily NEED the full SDK.
 
i have one of each. i looked at a different forum and the post said to try to install it and on the screen where it tells you you need jdk press back then press next again and it should work.. what do you know it worked for both the 64 and the 32 bit pc's. sdk is installed now i"m trying to figure out the rest of the craziness. Am I allowing sdk to install all the horribly long revisions before i can type in my prompts?..
 
Last edited:
You have to cd to the directory where your adb is located. For example, it could be:

>cd c:\android-sdk-windows\platform-tools or
>cd c:\android-sdk-windows\tools

Then try running the adb commands.
As far as z4 goes, Google search. It is available for download at Xda.



Sent from my VEGAn-TAB using Tapatalk
I did do the cd directory first...
I was in the "tools" already and it still would NOT accept the "abd" command line...
this is what i get each time....
:(
 
Last edited:
I did do the cd directory first...
I was in the "tools" already and it still would NOT accept the "abd" command line...
this is what i get each time....
:(
It is adb (not abd).

Just search the android sdk folder for "adb.exe" and go to that directory.
 
Sorry typo,
anyways i think i found the problem...
found the note in the files that told me that adb has moved..trying to fix that as i type...

thanks everyone trying to help me out :)
 
so sdk keeps asking me for packages to install and i am not able to actually get to a cmd line. i have not been having good luck with this....
 
Well I'm having new problems now :D yippeee!

Whenever i enter
adb shell
and press enter
it gives me this
$

and no matter if i restart my phone,and retrying it over and over it never works!
HELP!
 
Well I'm having new problems now :D yippeee!

Whenever i enter
adb shell
and press enter
it gives me this
$

and no matter if i restart my phone,and retrying it over and over it never works!
HELP!
That's what it is supposed to give you initially.

If you have rooted (installed "su") already, then turn on your phone, make sure you aren't on the lock screen, type "su" in your adb shell session, look for a prompt on your phone asking for root privileges, and allow that.

If you haven't rooted yet, then you need to choose which method you want to use, rage or z4root.

Given where we are today in terms of updates from Sprint, I'm wondering if you are even on the right thread. There is a different root procedure depending on which version of the OS you are on.

You can see which version you are running in menu->settings->about phone

Then pick the appropriate rooting thread.

NOTE: LS670ZVC and LS670ZVD are not directly rootable. You'll need to revert to LS670ZV9 first. It is all covered in the ZVD rooting thread.
 
  • Like
Reactions: Mindyyyx
Need Help!

Hi!
My phone is LG Optimus One. It's v10e. This is what i have;

C:\Users\Seyhan>cd c:\android-sdk-windows\platform-tools

c:\android-sdk-windows\platform-tools>adb push rageagainstthecage-arm5.bin /data
/local/tmp/rageagainstthecage
43 KB/s (5392 bytes in 0.120s)

c:\android-sdk-windows\platform-tools>adb push su /data/local/tmp/
641 KB/s (26264 bytes in 0.040s)

c:\android-sdk-windows\platform-tools>adb push busybox /data/local/tmp/
1710 KB/s (1926944 bytes in 1.100s)

c:\android-sdk-windows\platform-tools>adb shell
$ chmod 4755 /data/local/tmp/rageagainstthecage
chmod 4755 /data/local/tmp/rageagainstthecage
$ chmod 4755 /data/local/tmp/busybox
chmod 4755 /data/local/tmp/busybox
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3341, 3341}
[*] Searching for adb ...
[+] Found adb as PID 1927
[*] 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-sdk-windows\platform-tools>adb shell
error: device not found

c:\android-sdk-windows\platform-tools>

it's coming to here;
[*] adb connection will be reset. restart adb server on desktop and re-login.
then nothing happens. Usb connection is removing itself, but not connecting after remove. Every time same problem. Already 4 days. I tried it 100 times. Please help me!

Thanks for your interests.
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
956,396
Messages
6,968,045
Members
3,163,538
Latest member
boone