[How-To] Root LG Optimus S

Status
Not open for further replies.
Well, I like how the Mac write-up was handled - a link to it in the first post, to keep everything in one thread. I agree with you if it was a whole new set of instructions, but in the Mac case, it was really just a different set of initial instructions to get the Mac people up to the point where they can do the adb stuff.

Anyway, I was going to do the same for Ubuntu, but when I googled an issue related to the sdk manager, I discovered that someone already did it:
Setting Up ADB/USB Drivers for Android Devices in Linux (Ubuntu) ? Esau Silva

Following this set of instructions, I was able to get everything set up in minutes all the way up to step 4 of post 1 of this thread.

Holy smokes, and to think I figured I'd be able to muddle my way through it! Certainly a bit more complicated than the Windows setup, but seems straightforward. Thanks!
 
I sent him a thanks even though I don't use a Mac. As an Ubuntu user, I know what it is like to try to adapt Windows-specific instructions to meet my needs. I just got my phone last night and was able to root it at work this morning on my work XP machine, but tonight I'm going to try to get it working on Ubuntu. If successful, I'll post a similar Ubuntu guide to mfldmike's Mac guide.

Any luck man? Im running Ubuntu as well but cant really figure it out. gbhil gave me a tip on another thread but I was still unsuccessful:
You don't need any drivers on Linux. Make sure USB debugging is on on the phone, connect to a high speed USB port, and in a terminal:

Code:
sudo su
*password*
cd /home/path/to/sdk/tools/directory/
./adb-kill server
./adb-start-server
exit

You can then use adb as a regular user. You can script the above commands, or look for the udev rules for LG Android phones and you won't need to start the server as root any longer.

Tried working that into these instructions but had no luck, hopefully you have a better time :cool:

*edit*
Nevermind, didnt see the post at the top of this page haha
 
*edit*
Nevermind, didnt see the post at the top of this page haha

Yeah, between the content of that link I posted and the comments of that linked post, writing up my own mini-tutorial was pretty unnecessary.
 
Yeah, between the content of that link I posted and the comments of that linked post, writing up my own mini-tutorial was pretty unnecessary.

I'd still say to do it. write it up and post it here. Your not in those other places supporting users who may have issues, your here :)
 
I'd still say to do it. write it up and post it here. Your not in those other places supporting users who may have issues, your here :)

Who are you to tell me what to...oh, wait...nevermind. Coming right up.

EDIT: Heh...actually, not coming *right* up...I'm at work at the moment, stuck in Windows land, and I'm going away this weekend, but I'll definitely do it.
 
Who are you to tell me what to...oh, wait...nevermind. Coming right up.

lmfao!!! nobody, some poor dude with a crazy obsession with a mobile operating system :confused:

I'm watching the thread, you post it and I'll toss a permalink up to your post in #1. I really appreciate you guys writing these up and i know people do too! Keep up the great work!
 
followed all the steps until 4. shell isn't opening up with root, still getting $. Is it possible this has been patched? I tried the Z4root as well and it didnt work either.
 
followed all the steps until 4. shell isn't opening up with root, still getting $. Is it possible this has been patched? I tried the Z4root as well and it didnt work either.

At step 4, type "su". Look at your phone right away, see if it asks you to confirm superuser.
 
At step 4, type "su". Look at your phone right away, see if it asks you to confirm superuser.

got it to work. it didnt give any notice on the phone, but it simply popped up with # this time. very interesting since i had tried it 3-4 times. maybe their patch wasnt as good as they thought lol
 
got it to work. it didnt give any notice on the phone, but it simply popped up with # this time. very interesting since i had tried it 3-4 times. maybe their patch wasnt as good as they thought lol

I've had that happen to me a few times as well. Sometimes "adb shell" takes me right to #, other times it takes me to $ and I have to 'su' to get to #. I'm sure there is a method to the madness, but I haven't picked up on it yet. Anyway, if you ever to it again and get $, type 'su' while the phone screen is on and unlocked, and then quickly approve the permission request that pops up on the phone. You should only have to do that once, and then going forward any time you need to 'su' to get to #, it will work right away.
 
looks like z4root is now gone in the market. at least i cant find it! so the only way to do it know is the step by step way in the first post.
 
Well, I like how the Mac write-up was handled - a link to it in the first post, to keep everything in one thread. I agree with you if it was a whole new set of instructions, but in the Mac case, it was really just a different set of initial instructions to get the Mac people up to the point where they can do the adb stuff.

Anyway, I was going to do the same for Ubuntu, but when I googled an issue related to the sdk manager, I discovered that someone already did it:
Setting Up ADB/USB Drivers for Android Devices in Linux (Ubuntu) ? Esau Silva

Following this set of instructions, I was able to get everything set up in minutes all the way up to step 4 of post 1 of this thread.

There's two big typos in the instructions in that link above. Took me forever for my sleep addled brain to figure out why the path wouldn't work.

Instruction 8.2 should read:
Add the following line at the end: export PATH=${PATH}:/home/user/android-sdk-linux_x86/tools

NOT

Add the following line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools

Note the lack of ~ in my version, as well as the addition of "x" to "linux_86".

That'll teach me to copy/paste......:mad:
 
  • Like
Reactions: ccrs8
Jeez louise.

Well, adb works on Ubuntu 10.10 now, but when I do "adb devices" I get:
Code:
List of devices attached 
????????????	no permissions

Doing
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
gets me
Code:
error: insufficient permissions for device

....ideas?
 
There's two big typos in the instructions in that link above. Took me forever for my sleep addled brain to figure out why the path wouldn't work.

Instruction 8.2 should read:


NOT



Note the lack of ~ in my version, as well as the addition of "x" to "linux_86".

That'll teach me to copy/paste......:mad:

Good catch. I renamed the folder to just "android" just like in the Windows instructions in post 1 of this thread, so I didn't catch that second one. As for the first error, I'm familiar with setting up PATH variables so once I read that that's what I needed to do, I didn't actually look at the exact code the author had recommended.
 
Jeez louise.

Well, adb works on Ubuntu 10.10 now, but when I do "adb devices" I get:
Code:
List of devices attached 
????????????	no permissions

Doing
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
gets me
Code:
error: insufficient permissions for device

....ideas?

Did you replace '0bb4' with '1004' in step 5?
 
Did you replace '0bb4' with '1004' in step 5?

GOT IT.

Yeah, I'd done that. Apparently the server needs to be started while in su, but I don't know how to access the adb path while in su, so I had to go:

Code:
cd ~/{android_sdk_folder}/tools

sudo su

./adb kill-server

./adb start-server

exit

now "adb devices" works.

EDIT: and now I'm rooted. Thanks all!!!!
 
Last edited:
So has anyone used the 1 step way? i have a evo i rooted but wanted to root my Daughters optimus s the fastest way i can does it really work on this model?
 
Im not having any luck with the instructions at all, it never grants root access, and z4 doesnt work either. Now when I try on my mac side I get permission denied when using adb, any ideas?
 
Hi. New here and first time rooter. I followed all the directions, but like many others I can't get the # symbol. I tried at least 10 times and I only get a $. I've tried closing tasks rebooting, nothing is working. When I try to type 'su' on the $ promt afterwards it just says su: permission denied. Any tips?
 
Status
Not open for further replies.