[How-To] Root LG Optimus S

Status
Not open for further replies.
Hi!
My phone is LG Optimus One. It's v10e. This is what i have;



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.

You realize this is the Optimus *S* forum right? We may not know exactly what is going on because we don't generally use the phone you have.

From what you describe, it could be that you have a firmware version that is not rootable. Don't know the specifics of which versions do what on Optimus One. If that is what is going on, you might be able to revert to an earlier version.
 
I followed the instructions all the way through to "./rageagainstthecage" and haven't gotten a # yet, only $
Rage depends on a race condition which doesn't always hit gold. It can take 1 or 50 tries or more. It just depends on the timing. Sometimes sprinkling in a few adb kill-server, and/or reboot of PC, and/or reboot of phone helps with the timing.

Eventually it does work assuming you are running something that is rootable like V9 Android or Recovery. VC/VD are not but you wouldn't be getting the $ prompt back with those versions, your phone just wouldn't respond to adb.
 
Last edited:
Hello, i read through a few pages and did numerous searches but couldnt find the answer i am looking for.

My Optimus S is rooted with ThundeRom 1.7. Before i rooted phone I could connect to any computer via usb and have the computer recognize the sd card as a hard drive. Now when i connect nothing happens with my phone at all unless i have the drivers from lg installed. I have tried Recovery>usb/ms as well but still nothing. Is there a way around this? Everynow and then i want to transfer a file to my work computer but i cant install programs on it or check personal email. Thanks!
 
I tried the rageagainstthecage exploit and did everything. Now my device is not found, when I try adb shell. what can I do to finish rooting. I pushed all the files over and ran the exploit. It talks about how it's making babies and how I should donate.
 
I tried the rageagainstthecage exploit and did everything. Now my device is not found, when I try adb shell. what can I do to finish rooting. I pushed all the files over and ran the exploit. It talks about how it's making babies and how I should donate.
You are probably running ZVC or ZVD software. If so you need to follow different instructions. See the stickie on how to root ZVD.
 
I got this to work... almost flawlessly. It took a few tries and some uninstall/reinstall of drivers on my PC, but I finally got it. Installed the Clockwork recovery also. Thanks for the instructions! They were a life saver...
 
I downloaded the OptimusRoot.zip file, but my antivurs detects a trojan.
anybody else has the problem?
 
Yeah it makes no sense to me either. But it is what it is.

well its a good measure (for people that use windows) 75% of you are connecting to a linux server in some way or manner.

All it sounds like is the devs of your virus software kept that in mind and included possible malicious code within linux even if you are on another os
 
well its a good measure (for people that use windows) 75% of you are connecting to a linux server in some way or manner.

All it sounds like is the devs of your virus software kept that in mind and included possible malicious code within linux even if you are on another os

True, but most Linux servers don't have ARM processors. And the rage exploit technically only targets the Android-ified Linux kernel so unless your ARM Linux server runs the Android kernel, the chance of the "virus" doing anything malicious is zero.
 
hey I gotta big problem, after writing this:

cd /data/local/tmp
./busybox cp su /system/bin

it returns
./busybox not found
 
i'm new to the android scene and i have hit a snag. i DL all the files i followed the vid and on the first line i got the error of device not found. anyone have advice ?
 
i'm new to the android scene and i have hit a snag. i DL all the files i followed the vid and on the first line i got the error of device not found. anyone have advice ?

Read my post above yours. If your device has LS670ZVD (I bet it does) then this guide won't work. Follow the guide in the stickies. Same with LS670ZVC.
 
Hi...and thanks for everyone's hard work!

Hello everyone!

This is my first post. I first want to thank everyone for contributing to this thread and I'd like to help if I can. I have some questions at the end of my post, but first let me see if I can be of help. I am rooted and I think I've discovered a few things along the way that can help others.

I know that many are frustrated and repeat over and over the instructions at the beginning of this thread. I'd like to offer some insight and a shortcut.

If you've done your pushes and chmod instructions, there's a simple way to verify that you've done all of that correctly. If you can do that, you're well on your way to "root". Once you've done this verification, there are only a few simple steps that you need to repeat until you "get it".

Get into the shell by performing the following (what you need to type is in bold, results/output are in bold blue):

adb shell
cd /data/local/tmp
./busybox ls -la rageagainstthecage su busybox


You should get the following (you may have line wrapping):

-rwsr-xr-x 1 2000 2000 1926944 Sep 30 2010 ?[1;32mbusybox?[0m
-rwsr-xr-x 1 2000 2000 5392 Nov 6 00:14 ?[1;32mrageagainstthecage?[0m
-rw-rw-rw- 1 2000 2000 26264 Oct 1 2010 ?[0;0msu?[0m


The important thing is that for each line/file, the first characters should be "-rwsr-xr-x" (within the "" chars). If this is the case, you've not only pushed the files to the proper directory, you've also properly changed the permissions of the three files. Now type this:

./busybox md5sum rageagainstthecage su busybox

The md5 hash for each file is:

860a3cd4cad692d8628d8cc84eb07519 rageagainstthecage
eafd6ce052f80a7f217d2e6033b2ce15 su
cdcef8277370c1c2cf9a974169d486db busybox


If it is, you not only have the files in the proper location, but you can verify that the md5 hashes for the files are correct. Having done this and getting these results, there is no need to repeat any of the push commands or chmod commands. You only need to do the following repeatedly until you get the proper results (the elusive # prompt). I can predict when these commands will work properly. When I get one disconnect (from windows) and one reconnect I will then adb shell in and I'll be rooted (# prompt). When it doesn't work, I'll get several disconnect/reconnect sequences and when I adb shell in, I won't have # symbol for a prompt. Only the following commands need to be repeated (assuming you've gotten the results I've displayed above) until you get it.

adb shell
cd /data/local/tmp
./rageagainstthecage


I originally thought that my root was only temporary, but I discovered after getting root, you need to look at the phone after the adb shell and subsequent su command to give the superuser application permission to allow root access. I believe that has been made clear in previous posts.


Now I have a question. First of all, I'm rooted. I also have Superuser, Minfreemanager and drellisdee's Custom Recovery recovery-thunderc-s-RA-v1.2-GNM.img installed. I did all this with version zv9. Do I need to (or should I) upgrade to zvd? I'm happy to have root (and my wireless tethering which is what prompted me to root in the first place) and don't know if it's necessary to upgrade to a later version. If so, I've found this link, but I'm not completely sure which way is the best/safest. It appears that I can use either part-6 or part-8. Could someone please advise?

Thanks in advance for any help and I hope I may have helped someone as well.

gvp
 
Last edited:
adb shell
cd /data/local/tmp
./busybox ls -la rageagainstthecage /system/bin/su /system/bin/busybox


You should get the following (you may have line wrapping):

-rwsr-xr-x 1 0 2000 1926944 Apr 3 16:08 ?[1;32m/system/bin/busybox?[0m
-rwsr-xr-x 1 0 2000 26264 Apr 3 16:08 ?[1;32m/system/bin/su?[ 0m
-rwsr-xr-x 1 2000 2000 5392 Nov 6 00:14 ?[1;32mrageagainstthecage?[0m


The important thing is that for each line/file, the first characters should be "-rwsr-xr-x" (within the "" chars). If this is the case, you've not only pushed the files to the proper directory, you've also properly changed the permissions of the three files.
...
Having done this and getting these results, there is no need to repeat any of the push commands or chmod commands. You only need to do the following repeatedly until you get the proper results (the elusive # prompt).
...
adb shell
cd /data/local/tmp
./rageagainstthecage
If you have setuid root (-rwsr-xr-x 1 0 2000) on /system/bin/su there is no point in running rageagainstthecage

You cannot push files to /system/bin until you have run rageagainstthecage successfully
 
Status
Not open for further replies.