• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Click rooting your LG Optimus Elite

Hashtag

Hashtag

Android Enthusiast
Edit 9/23/2012- This method is outdated. There now is a method that is the simplest I've ever seen, its an app. Just search the forums for it.

Step 1-Download and install the default LG Drivers(Must install before you do anything else)
Step 2-Download file, and extract the .zip to "C:\android\platform-tools"
Step 3-Run the Program. It's called LG Optimus Elite Click Root.
Step 4-Follow the instructions, and when you finish download superuser in the market.

Credits go out to giantpune for this. Make sure to send him a thanks.

If anybody has any problems with it, please post back here.

Download link(It's my personal account, so please don't spam it)- https://www.box.com/s/oybobbcxhk6nlc7d4mey

Download link for default LG drivers- https://www.box.com/s/m7h8hbfoez3rsl3alhat

Some common problems:

1)"The program says that adb was not found command"- You didn't put it in the right place. Make sure that the "android" folder is in the root directory of the C drive.

2)"The program waits-for-device and won't do anything"- You need to install the default LG drivers. The link is here- https://www.box.com/s/m7h8hbfoez3rsl3alhat

3)"It tells me something like libusb error 404"- Your drivers that you setup in zadig were not installed correctly. Go back and make sure that all the stuff is good to go.

4)"zadig doesn't show any devices"- Go to options, then list all devices.
 

Attachments

  • Click Root1.png
    Click Root1.png
    184.6 KB · Views: 534
  • Click Root2.png
    Click Root2.png
    173.2 KB · Views: 379
I was already rooted but you have done some cool things for Elite users and I know a lot of people will appreciate this.
 
im working on trying this if i can ever get the other big files downloaded, all are corrupt that i have d/l from android police site thingy, but a forum member is helping me there.
 
It didn't work for me. It scrolled a bunch of text, and prompted me to push the button on my phone, and rebooted it, but I still can't run 'su' through adb shell or modify files with a file explorer app.

Did I do something wrong?
 
Quriosity said:
It didn't work for me. It scrolled a bunch of text, and prompted me to push the button on my phone, and rebooted it, but I still can't run 'su' through adb shell or modify files with a file explorer app.

Did I do something wrong?
Click to expand...

Alright, I fixed it. Thank you so much for speaking up, because from the looks of the code, it should have been failing for everybody but me. You're the first person to say anything though, so thanks.
 
I didn't run the "verify adb" button because I had already checked the adb through the terminal myself. But now that it looks like you may have taken the files down, I tried the 'verify adb' button and it froze up and did not display any output in program's GUI.

Whether or not this is a mistake on my part (I quadruple checked everything to make sure I was following directions, but I'm not exactly a pro at this) or the program is beyond me.

When I ran the "verify adb" button, it kinda froze up, and when I opened a terminal while it was freaking out it repeated the 'adb devices' command in the new terminal over and over, too many times to count.

Don't know if this helps

ETA: Sorry, you responded before I submitted this post. The above pertains to the old code, I'll try the new stuff now.
 
Quriosity said:
I didn't run the "verify adb" button because I had already checked the adb through the terminal myself. But now that it looks like you may have taken the files down, I tried the 'verify adb' button and it froze up and did not display any output in program's GUI.

Whether or not this is a mistake on my part (I quadruple checked everything to make sure I was following directions, but I'm not exactly a pro at this) or the program is beyond me.

When I ran the "verify adb" button, it kinda froze up, and when I opened a terminal while it was freaking out it repeated the 'adb devices' command in the new terminal over and over, too many times to count.

Don't know if this helps

ETA: Sorry, you responded before I submitted this post. The above pertains to the old code, I'll try the new stuff now.
Click to expand...

Yeah, I just took a look at that and you're right, so I'll post the new copy real quick. I had forgotten to update the ADB Verifier when I rewrote the rest of it. give me just a minute

Edit:Okay, v1.9 is up. Use the new link.
 
The verifier is working for me now. When I run giantpune's method step one, it works fine for the first click. After the first 'continue', it displays the following towards the end:

Code: 
$ am start -n org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity

Starting: Intent { cmp=org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity }

Error type 3

Error: Activity class {org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity} does not exist.

By the way, thanks so much for writing this program. You're a saint.
 
Quriosity said:
The verifier is working for me now. When I run giantpune's method step one, it works fine for the first click. After the first 'continue', it displays the following towards the end:

Code: 
$ am start -n org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity

Starting: Intent { cmp=org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity }

Error type 3

Error: Activity class {org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity} does not exist.
By the way, thanks so much for writing this program. You're a saint.
Click to expand...


Lol, no problem. Thanks for trouble shooting it. Those lines mean are the commands that try and start the Ministro app that gets your phone ready for root. Make sure that your debugging mode is on, and watch your phone. Dont let the screen dim and dont have it locked. Also, go to the phones settings>applications, and check the box that allows installation of non-market apps.
 
Yeah, all that was done so I just tried tinkering (probably a recipe for disaster, but whatever).

I circumvented the last error by pulling up the terminal and manually installing the apps and pushing the 'su' command to the proper directory.

Now it's displaying

Code: 
$ am start -n org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity

Starting: Intent { cmp=org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity }


I DL'd the extra libraries via the phone, pressed 'Push Me,' and switched the app to put DIAG on 'enable'

Now every time I hit continue on the program it flashed another line of:

Code: 
C:\android\platform-tools>

I realize I've kind of broken off from strictly pushing the buttons and troubleshooting, so maybe I shouldn't be expecting it to work?
 
Quriosity said:
Yeah, all that was done so I just tried tinkering (probably a recipe for disaster, but whatever).

I circumvented the last error by pulling up the terminal and manually installing the apps and pushing the 'su' command to the proper directory.

Now it's displaying

Code: 
$ am start -n org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity

Starting: Intent { cmp=org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity }
I DL'd the extra libraries via the phone, pressed 'Push Me,' and switched the app to put DIAG on 'enable'

Now every time I hit continue on the program it flashed another line of:

Code: 
C:\android\platform-tools>
I realize I've kind of broken off from strictly pushing the buttons and troubleshooting, so maybe I shouldn't be expecting it to work?
Click to expand...

Once you click the continue button, you have to click back to menu and move onto the next step.
 
Alright... My phone says DIAG, and I turned it to 'enable.' I went to the driver step, though, and clicking the button didn't do anything. Does that mean that I'm not really in DIAG mode?
 
Quriosity said:
Alright... My phone says DIAG, and I turned it to 'enable.' I went to the driver step, though, and clicking the button didn't do anything. Does that mean that I'm not really in DIAG mode?
Click to expand...

What button? If your taking about the driver software button then you have to select the device first.
 
I'm just gonna have to find a way to incorporate the other files into the program itself. Most of the problems are stemming from having to drag them into the program, because rather than being a regular command prompt it's a shell command prompt. So ADB is having a hard time doing a proper adb shell, because the CMD it's running in is a shell itself.
 
Just downloaded and installed the OTA update then used the click root above to root my wife's phone and it worked. You rock Hashtag !! The process was a little fumbley and took 2 tries but it was successful. I am running 64bit vista and my adb was in C:\Program Files (x86)\Android\android-sdk\platform-tools, so I just copied them to C:\android\platform-tools and ran the program.
Sweeeet.
Thanks again :)
 
codmerc said:
Just downloaded and installed the OTA update then used the click root above to root my wife's phone and it worked. You rock Hashtag !! The process was a little fumbley and took 2 tries but it was successful. I am running 64bit vista and my adb was in C:\Program Files (x86)\Android\android-sdk\platform-tools, so I just copied them to C:\android\platform-tools and ran the program.
Sweeeet.
Thanks again :)
Click to expand...

Awesome! Glad it worked put for you :) would you mind telling me what was a little bit fumbly please? That way I might be able to make it better :P
 
First I'm no pro, so some of it was probably my fault. And I'm stoked it worked so not complaining. I did need to reopen the program after each step, not sure if that was because of my OS or what. Near the end of the msl workaround part my drivers lost my device. I restarted my computer and reinstalled them and from there it went pretty smoothly. There was once or twice that I wasn't sure if I was done with that step or not but since it worked I'm guessing I was. After reading the other methods I'm sure this was a lot easier. I would recommend using it.
So, thanks again and thanks to the others who contributed the process.
 
Thanks for the feedback. I know what the problem is with having to exit, so ill get that taken care of. The drivers are weird. They seem to be really touch and go, so I'm going to decompile the zadig.executive and see if I can just have it manually install it. And I think Im gonna try to figure out how to put a progress bar on the stuff so you can tell when it's done. Thanks for the feedback, it'll help for future users :)
 
I found out why you were having to close it every time youbwanted to redo a step. I made it to where the program would load the shells into the ram to make it faster, but I didn't write the code to flush it out when you pressed the back button. Ill fix that then put up the new version.

EDIT: Put up the new version. The old files get flushed out now. It's much more stable. Thanks to codmerc for pointing it out.
 
C:\android isn't where adb gets installed anymore can you update the app to reflect? It goes into program files now
 
make a new folder in your c drive and name it "android" then cut and paste all files including platform-tools and tools into it and make sure you edit your enviromental settings
 
You must log in or register to reply here.
Back
Top Bottom