[How-To] Root LG Optimus T

I see a couple of things that concern me right off the bat. Please don't let my opinion steer you away but heres my thoughts ....

1) The author doesn't provide you with the commands it runs. I have no idea if, when you download this and run it it may open a terminal and you can visually see the commands or not, but I want to physically verify the commands run on my phone first, not during.
2) This teaches people that root is simple as a click of the button. You gain absolutely no command line skills and if you think you can escape the android root underworld without knowing and loving Android Debugging Bridge you'll be sorely mistaken.

Realistically if the app did something malicious someone would have called the dev out by now. BUT without seeing the actual commands, i cannot tell you to use this or not use this. My commands are laid out and simple and you can see exactly what I'm telling you to do.

As the saying goes, there's more than 1 way to skin a cat.

I will add my personal experience to this. When I had my EVO I had problems doing certain things that I really wanted to do. When it came right down to it the only way to troubleshoot it was to use ADB. I had no clue how to do that, and even though I had been rooted for months I couldn't troubleshoot it. So I was playing catch up to fix problems. Had I done the long method of rooting that involved ADB troubleshooting woulda been a lot easier for me and the people helping me.
 
I HAVE ROOOOOOOOOOOOTTTTTTTT!!!!!!!!!!!!
Sorry im over exited! now I see what I didnt understand before!
THANK YOU SO MUCH!

Awesome. I'm glad the video helped. Just out of curiosity what did you need to do differently?

Sent from my Optimus T
 
Followed the steps verbatim, no root. I got all the way to the part where you go back into the adb shell to see if you've got #, and I still have a $. I also tried the z4root app and did abosultely nothing for me, spun for awhile, said it was working, restarted, and no root. I did install an OTA update a couple days ago, so I'm guessing I'm SOL until whatever that changed gets hacked, huh?

EDIT: Despite not being able to see the # in adb shell, Superuser did get installed fine and I downloaded and installed Titanium Backup, and it seems to be running fine and got superuser access as well. So everything's peachy? I think... I'm still confused as to why when I go into adb shell and try to su I get a "Permission Denied."
 
Last edited:
Has anyone received the OTA update to enable WiFi Calling w/ root? I haven't accepted the OTA due to having root. Also if I do will I loose root? Thanks.
 
Followed the steps verbatim, no root. I got all the way to the part where you go back into the adb shell to see if you've got #, and I still have a $. I also tried the z4root app and did abosultely nothing for me, spun for awhile, said it was working, restarted, and no root. I did install an OTA update a couple days ago, so I'm guessing I'm SOL until whatever that changed gets hacked, huh?

EDIT: Despite not being able to see the # in adb shell, Superuser did get installed fine and I downloaded and installed Titanium Backup, and it seems to be running fine and got superuser access as well. So everything's peachy? I think... I'm still confused as to why when I go into adb shell and try to su I get a "Permission Denied."

When you have your phone connected and are in adb shell, type su and look at your phone. It should have a pop up requesting access that you have to grant.
 
Has anyone received the OTA update to enable WiFi Calling w/ root? I haven't accepted the OTA due to having root. Also if I do will I loose root? Thanks.

I'm not sure anyone has taken the OTA that has root, or taken it and then tried to root. So I don't think there's an answer yet.
 
I'm not sure anyone has taken the OTA that has root, or taken it and then tried to root. So I don't think there's an answer yet.

Figured as much, but just wanted to ask and throw it out there. Thanks for the reply. I'll wait then............don't really need WiFi calling as of right now.
 
Figured as much, but just wanted to ask and throw it out there. Thanks for the reply. I'll wait then............don't really need WiFi calling as of right now.

The standard rule of thumb is this ...

1) If you're already rooted do not ever accept an OTA (until its verified it does nothing to prevent root) as it could block root.
2) Devices will be selling soon with the OTA pre-installed and those people will want to root. They will be able to tell you if it was successful or not. Until then just hang tight.

If LG would be so kind to either just put out a RUU for each release or publish update.zip's for each release this whole thing would be much easier. The update software they have now, LG mobile update, is garbagio. Yeah ... i said it :)
 
When you have your phone connected and are in adb shell, type su and look at your phone. It should have a pop up requesting access that you have to grant.

Ah, that was it, thanks! I was doing it with the screen locked and off, so I wasn't seeing that.

Also you guys seemed to have missed it: I installed the OTA from a few days ago and got wifi calling, and then rooted my phone a day later. Works fine now. Probably not something I should have done while wanting to root my phone later, but hey, worked out this time.
 
Awesome that root still works. We've honestly been waiting for someone to try it. Thanks for letting us know.
 
unable to get root

Hi all, I had rooted my phone prior to the OTA update. All was well except for the fact that I had no service where I needed it. Therefore I was going to install the OTA update. I then unrooted the phone with SuperOneClick to install the OTA update. I now have a phone that will make calls over WIFI as I needed (despite being a crock that they still will charge minutes from my plain for using my resources) and unable to attain root....

I have pushed the files to /data/local/tmp, did the chmod's, ran ./rageagainstthecage. The adb server drops the connection to the phone. I wait and am unable to respawn an adb shell unless I reboot the phone.

I do get the warning Im guessing from a file lock if I were to mount the SD card so something is in use.

I can get logs if wanted.

I thank anyone for some other options to try,

warranty.is.now.gone


**EDIT**
I was poking around the Optimus S section and read about z4root. I gave it a try and it worked.
 
Last edited:
I accepted the OTA Update as well and then soft rooted with z4root. I am disappointed there's no aosp kernel for this yet. I want CyanogenMod. I really want to overclock my processor. It's disappointing that our phone has so much potential, and yet we can't overclock, etc. My Quadrant standard score was 466 and that's alot better than some of the guys I was talking to with CM on their myTouch 3G.
 
I accepted the OTA Update as well and then soft rooted with z4root. I am disappointed there's no aosp kernel for this yet. I want CyanogenMod. I really want to overclock my processor. It's disappointing that our phone has so much potential, and yet we can't overclock, etc. My Quadrant standard score was 466 and that's alot better than some of the guys I was talking to with CM on their myTouch 3G.

This phone is AOSP. If you have a little patience you will have a ROM. The custom kernel will come a little after the ROM. (it's out there but won't be bundled with the ROM right away)
 
After you do "su", there is a prompt on the phone for you to allow access. Did you see and respond to that?
 
Since Android SDK r08 has been released I think the instructions need to be updated. We know have to install "platform-tools" to obtain adb.exe. This also changes the folder location.
 
can anyone help answer me why I keep on getting 'adb' is not recognized as an internal or external command. i have everything installed right down the line and followed everstep until
adb push rageagainstthecage-arm5.bin/data/local/tmp/rageagainstthecage
 
can anyone help answer me why I keep on getting 'adb' is not recognized as an internal or external command. i have everything installed right down the line and followed everstep until
adb push rageagainstthecage-arm5.bin/data/local/tmp/rageagainstthecage

cd c:\wherever-your-sdk-tools-folder-is (mine for example is C:\android\tools)

^^ Needs to be changed to

cd c:\wherever-your-sdk-tools-folder-is (mine for example is C:\android\platform-tools)