[How-To] Root LG Optimus S

Status
Not open for further replies.
Did you install Java SE Runtime Environment? There are many options for Java so you need to be careful what you install. Follow the link in the first post and install that one
 
Did you download the x64 Windows one? I downloaded that one the first time and I still couldn't install the Android SDK but I then installed the normal Windows JDK and it worked.
 
Can I get Some...

help?

right now im reading the Idiots guide and well you can say im pretty dumb ha, but
i've done steps 1-5 and now im starting up command prompt.

C:\AndroidSDK\tools

then

C:\AndroidSDK\tools\adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage

error: device was not found

if i can get some help i could finally flash!! so please!
 
First of all did you follow the prerequisites before starting the shell?

#1. Install - Java
#2. Install - LG Drivers
#3. Install - Android SDK (please note if you have the "new" SDK it's going to be - Platform Tools - and not just "Tools")
#4. Enable USB Debugging ON YOUR PHONE.
#5. Did you plug your phone into your PC?

Just a few thoughts....
 
help?

right now im reading the Idiots guide and well you can say im pretty dumb ha, but
i've done steps 1-5 and now im starting up command prompt.

C:\AndroidSDK\tools
Don't know if this was just a mistype on your end but the command is actually cd C:\[enter your path to tools]. I noticed you weren't doing the change directory command.
then

C:\AndroidSDK\tools\adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
Again, same as before but thats the wrong command completely. You'r pushing and you should already be in the tools directory assuming you did the change directory i mentioned above.

That means the command would be
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
Which is whats typed in post #1
error: device was not found

if i can get some help i could finally flash!! so please!
You should watch THIS video

literally it's just copy and paste, which iamlillysdad does, just copies from post #1 pastes.
 
well I've doen what you said and this is what i got back

*daemon not running. starting it now *
*daemon starterd successfully*
error: device not found
 
well I've doen what you said and this is what i got back

*daemon not running. starting it now *
*daemon starterd successfully*
error: device not found

see now were getting somewhere lol

Ok now what you should do is this....
1) Make sure usb debugging is enabled. It doesn't matter if you checked it 10 minutes ago, for the sake of not wasting anyones time, check it again please. Menu > Settings > Applications > Development - check mark usb debugging.
2) Ensure your phone is not mounted as a usb drive. To do this when you connect to your computer pull down the status bar and click the usb mount option. When you click this the android should be GREEN. If he's ORANGE you are mounted and that's bad.
3) With the phone plugged in, USB debugging enabled, and not mounted as a drive (green android), try doing this ...

1) Launch the SDK. You'd do this by going to your android folder and click SDK Setup.exe.
2) It will ask you to chose a package to install if any are available. click cancel. (leave the SDK open for now)
3) Go down to the start button on the lower left hand of your screen (if you on windows) click it, click run, type CMD
4) A command prompt should now be open in front of you. Try it now.
 
Damn dude im dumb as hell, I had the new version, so I had to change the directory to platforms-tools .does that mean I have to change my enviormental variable too?
 
Damn dude im dumb as hell, I had the new version, so I had to change the directory to platforms-tools .does that mean I have to change my enviormental variable too?

The only thing you'll need to adjust is the same thing anyone/everyone needs to adjust to suit their specific setup which is the very first command where you CD into the tools folder.

Everything will be the exact same except for the first line. everyones first line could be different.

My home PC is cd C:\android\tools
My work PC is cd C:\android_stuff\android-sdk-windows\tools

so even for me depending on which PC im on in order to change to the tools directory in a command prompt the line changes.
 
  • Like
Reactions: JoejDE
Damn dude im dumb as hell, I had the new version, so I had to change the directory to platforms-tools .does that mean I have to change my enviormental variable too?

New SDK moved that stuff into platform-tools and not just "tools", huh? I updated my Idiots Guide to make note of that. KSmith, perhaps you should update the first post here as well to reflect people who might be using the new SDK. They might go to "Tools", like you recommend, and find it doesn't work.
 
How long did you wait after ./rageagainstthecage before doing adb shell? Try waiting like 10 minutes.
Yea I Gave up after 20+ tries, and just used z4root. SOO much easier. I wasn't doing anything wrong, as soon as I rooted it I had no issue gaining su privileges. Popup did come up asking to grant.


C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system


C:\android-sdk-windows\tools>
 
  • Like
Reactions: Sparty73
alright need some help. whenever I open sdk the the command prompt opens up then android sdk & AVD manager pops open then a thing that says choose packages to install. I cant type anything in the command propt window and if I close the other stuff it closes the command prompt. what am i doing wrong?
 
alright need some help. whenever I open sdk the the command prompt opens up then android sdk & AVD manager pops open then a thing that says choose packages to install. I cant type anything in the command propt window and if I close the other stuff it closes the command prompt. what am i doing wrong?

HERE

Specifically for you, step 2-2 (towards the end of the post)
 
  • Like
Reactions: weenerdog3443
HERE

Specifically for you, step 2-2 (towards the end of the post)

alright thanks got me a lil farther..

still must be doing something wrong... this is what i got now.


C:\Android\tools>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagains
tthecage
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\Android\tools>cd c:\android\platform-tools

C:\Android\platform-tools>adb push rageagainstthecage-arm5.bin /data/local/tmp/r
ageagainstthecage
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
cannot stat 'rageagainstthecage-arm5.bin': No such file or directory

C:\Android\platform-tools>
 
alright well got pass that part but but now I am to the part where you do the adb shell and are suppose to get # but I keep getting $
 
What am i missing?

I've followed the tutorial multiple times, watched the video, triple checked but still cannot root. Here is my cmd window:

Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\android\platform-tools>adb push rageagainstthecage-arm5.bin /data/local/tmp/r
ageagainstthecage
337 KB/s (5392 bytes in 0.015s)

C:\android\platform-tools>adb push su /data/local/tmp/
820 KB/s (26264 bytes in 0.031s)

C:\android\platform-tools>adb push busybox /data/local/tmp/
1012 KB/s (1926944 bytes in 1.859s)

C:\android\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={3374, 3374}
[*] Searching for adb ...
[+] Found adb as PID 4437
[*] 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.
$ adb
C:\android\platform-tools>adb shell
$ exit
exit

C:\android\platform-tools>

Is there something blatantly obvious I am missing? I am using the new android SDK and have adjusted accordingly. I just can't get the # shell prompt. Thanks for all that everyone does.

EDIT: It sounds like the phone actually cycles the USB connection twice after ./rageagainstthecage before I can 'adb shell'. From what I have read it sounds like this should only cycle once. Not sure if this is helpful.
 
I'm having the same problem, not able to root, keep getting the $ sign, and i've literally read through every part of this thread, trying everything, to no avail. just hoping i could get some help here.

I've followed the tutorial multiple times, watched the video, triple checked but still cannot root. Here is my cmd window:

Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\android\platform-tools>adb push rageagainstthecage-arm5.bin /data/local/tmp/r
ageagainstthecage
337 KB/s (5392 bytes in 0.015s)

C:\android\platform-tools>adb push su /data/local/tmp/
820 KB/s (26264 bytes in 0.031s)

C:\android\platform-tools>adb push busybox /data/local/tmp/
1012 KB/s (1926944 bytes in 1.859s)

C:\android\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={3374, 3374}
[*] Searching for adb ...
[+] Found adb as PID 4437
[*] 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.
$ adb
C:\android\platform-tools>adb shell
$ exit
exit

C:\android\platform-tools>

Is there something blatantly obvious I am missing? I am using the new android SDK and have adjusted accordingly. I just can't get the # shell prompt. Thanks for all that everyone does.

EDIT: It sounds like the phone actually cycles the USB connection twice after ./rageagainstthecage before I can 'adb shell'. From what I have read it sounds like this should only cycle once. Not sure if this is helpful.
 
Had a similar issue when I tried to make a custom recovery (I'd rooted using z4root). See if typing "su" on the adb prompt works.
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
956,657
Messages
6,969,358
Members
3,163,596
Latest member
vedinke1