[How-To] Root LG Optimus T

Ahh, well that makes things a bit easier. Hadn't tried that yet XD. All I wanna do is run some custom roms and whatnot. The g1 was wayyyy easier than this.
 
Same with me android 2.2 Optimus T ... seems to work correctly... but the device is never actually rooted...
 
WTF?

I don't think anyone with answers reads this forum anymore. ERROR: DEVICE NOT FOUND. AFTER THE SECOND ADB SHELL. IS THERE ANYONE OUT THERE WITH THE F'IN ANSWERS?! PLEASE HELP! SOS! SOMEBODY! ANYBODY! MAYDAY! DO YOU READ!?(not an insult to anyone, I mean does anyone hear me?
 
Yes we do. Read the thread. It seems that people are having luck after the first reconnect.

It can take more than one try. If you're getting the device not found error either you didn't wait long enough for it to reconnect or you did something wrong.
 
I wait for it to reconnect. I know because on my phone it says I'm connected. USB debugging is enabled. I think they just locked us out with the OTA they sent us, but someone claims to have gotten the same update and they got rooted still. I don't know what's going on.
 
what OTA? when did you get it? what's your software version number? as far as I knew (because I don't have this phone anymore) the only OTA was for WIFI calling. if that's all it is then you should still be able to root it.

did you watch the video I made? the only thing that's really changed is the directory for the tools folder. everything else is still spot on.
 
I just updated to the newest version through LG's update utility so I could make a stock dump for deodexing, and rage still worked for me for temporary root, and z4root still worked for permanent root.
 
Help at step 4!

This is what happens when i type this into the cmd


Untitled.png
 
To: Congdo 11
You have to be mindful of your slashes. Read the whole forum on this process.

To: lilysdad
Yeah, it was just for wifi calling. I don't know what I'm doing wrong. The part where I should receive my "#" or "$", I get the device-not-found-error.
 
I've tried to open anything on the cmd mod, but nothing appears. It just gives me that msg about internal and external. I've tried all the "slashes".
 
This is what happens when i type this into the cmd


Untitled.png

Here're the steps I believe you need to take.

From the SS you posted, your CMD is starting in the following directory: "C:\Users\Thanh\" when your SDK/ADB Shell is located at: "C:\Android\android-sdk-windows\tools" or "C:\Android\android-sdk-windows\platform-tools" depending on whether or not you're running the latest SDK. So when you start up your CMD keep inputing "cd.." until you're at the "C:\" directory. From there input "cd C:\Android\android-sdk-windows\tools" or "cd C:\Android\android-sdk-windows\platform-tools" and you should be good to go with the next steps in the walkthrough.


My recommendation is that you completely understand the guide in full considering a mistake made during the actual flashing may or may not be so easily fixed. I hope that this guides you in the right direction.
 
Last edited:
Help!!!

I'm having problems with the first part of step 4 using the Command Prompt.

I open it and go to the file for Android SDK Platform tools. Then I enter

adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage

and it come up saying [ device not found ].

I have the LG drivers installed on my pc and the usb cable plug in on

Charge only and USB debugging enabled. I have tried several time with no

luck and at a lose. Can someone help me please!!

Thank you,
Scott


I have gotten past the first part of step 4. Now when I get to the second ADB SHELL it come up again [ Device not Found ]

It is not reconnecting back to adb server. I even waited for 10 minutes and still a no go. Why would this happen? Any Ideas.

Thanks in advance.



Is there anyone out there who can help with this PLEASE????????????

:confused::confused::confused::confused::confused::confused::confused::confused:
 
Last edited:
Error:device not found is there anyone out there who has had this error come up for the second adb shell and overcome it? Anyone?
 
I'm having the same issue, after running ./rageagainstthecage, and then waiting for upwards of 20 minutes (even though the adb session is terminated after about 30 seconds, and my phone reconnects to my computer nearly immediately), I can't restart adb.

It always says "error: device not found", and the only way I can restart adb is to reboot my phone. When I do that, and then restart adb shell, I still have $ instead of #.

P.S. Using Z4Root, everything works just fine.
 
Last edited:
I just got an Optimus T and returned my Optimus S within the 30-day window (CA law). I was frustrated with the uninstallable bloatware on the T and pissed that all my installed apps are at the bottom under 'downloads', forcing me to scroll down every time or put everything on the home screen. Since I had both the S and the T side by side, I decided to root them both and compare since there are some obvious differences in the UI.

The short of it is that I was unable to root the S, which had a current OTA, but I was able to root the T. The behavior of the S was that it did everything as expected when running the rootkit, but I could never get a root prompt (#) or su in as root.

After rooting the T, I installed the free version of Titanium Backup and started messing around. I backed everything up completely (I thought) and did a test uninstalling and re-installing a non-system app. So far so good. I then decided to do the same with some bloatware, specifically the Namco Pacman demo. Unfortunately I didn't look carefully before uninstalling it. Titanium Backup only saves data from system apps, and doesn't save the actual apps. I exchanged emails with Joel (the author of Titanium Backup), who is very helpful and confirmed this.

The phone works fine without the PacMan demo. Do I need to reinstall it in order to ever receive an OTA or if I possibly had to return the phone? If so, is doing this as simple as installing an APK and possibly an ODEX in the /system/app dir? And if so, would someone be willing to help me out? I don't see the demo in the android market.

Next, I upgraded to the Pro version of Titanium Backup and started freezing stuff I thought was unnecessary. I froze the wrong thing because the screen turned black except for the status bar, and when I tried to reboot the phone it hung. I had to reset the phone and start over.

I started looking around at the command prompt in the /system/app dir. Being a noobie but an experienced Unix user, I thought that perhaps the way 'freezing' works is to change permissions on the files in this dir, and 'defrosting' changes the permissions back. If that were the case, I could fix the problem that happened to me by changing permissions back on the right APK at the command prompt.

That's not the way it works. Could someone explain what freezing does, or point me to an explanation of it?

TIA.
 

Trending Posts

Members online

Forum statistics

Threads
956,526
Messages
6,968,759
Members
3,163,561
Latest member
JessieMcMa