• 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

HackADecive said:
First I would like to thank you hashtag because this is the closest I've came to rooting my elite but I'm not that advanced with technology and I'm still getting stuck in the second stage (driver setup)

I would just also like to ask if the unlock root or super one click would work for the elite or if there is something like those programs that work for the elite.
-Thank You
Click to expand...

Neither super one click or unlock root will work, Android 2.3.7 has blocked them from working on said devices.
 
I got the phone into DIAG mode, downloaded the drivers with zadig, and then ran the last step, but I didn't get Exploit was called successfully. Instead, I got this:

Starting Command Prompt...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\android\platform-tools>cd C:\android\platform-tools

C:\android\platform-tools>lgoeExploit.exe
Warning: Line: 404 libusb_open_device_with_vid_pid()
Error: libusb: 0.000000 warning [init_device] could not get node connection information for device '\\.\USB#VID_0BC2&PID_5021#NA037JDH': [87] The parameter is incorrect.
Error: libusb: 0.000000 warning [init_device] could not get node connection information for device '\\.\USB#VID_1004&PID_6310#A0000031D508E7': [87] The parameter is incorrect.

C:\android\platform-tools>
C:\android\platform-tools>
Click to expand...

When I press continue from here, I get this:

C:\android\platform-tools>adb shell
$

$ echo ro.kernel.qemu=1 > /data/local.prop

cannot create /data/local.prop: permission denied

$

$ cat ./data/local.prop

./data/local.prop: No such file or directory

$

$ exit
Click to expand...

Did I miss something earlier in the thread?
 
caspian915 said:
I got the phone into DIAG mode, downloaded the drivers with zadig, and then ran the last step, but I didn't get Exploit was called successfully. Instead, I got this:



When I press continue from here, I get this:



Did I miss something earlier in the thread?
Click to expand...

You might want to try unplugging/plugging-in your phone again and also unplug any other USB devices/peripherals you have connected to your computer.
 
get this error

C:\android\platform-tools>cd C:\android\platform-tools

C:\android\platform-tools>lgoeExploit.exe
libusb_claim_interface(0) failed (-12)

C:\android\platform-tools>
C:\android\platform-tools>

then i click continue

C:\android\platform-tools>adb shell


echo ro.kernel.qemu=1 > /data/local.prop



cat ./data/local.prop



exit





$

$ echo ro.kernel.qemu=1 > /data/local.prop

cannot create /data/local.prop: permission denied

$

$ cat ./data/local.prop

./data/local.prop: No such file or directory

$

$ exit

then i click reboot
phone reboots and i do the other steps but phone is not rooted what did i do wrong


Program Forced close on while it was rebooting and now keeps booting up
 
What I've taken from this you choose the 7 android driver in zadig

Also, I'd the driver setup is done incorrectly will you brick your phone?
 
So what I've taken from the posts is that in zadig you choose the Android driver with the number 7 but then change it to what because I see win and a bunch of numbers
-Also can doing this incorrect can u brick your phone?
 
This Phone has all updates vm696 LG Elite

Starting Command Prompt...
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Android\platform-tools>cd C:\android\platform-tools

C:\Android\platform-tools>lgoeExploit.exe
Line: 472 MSL:

00000000 33393938 3935 399895
Line: 1da Found a device running in Diag Mode
Line: 1f5 2a
Exploit called successfully

C:\Android\platform-tools>
C:\Android\platform-tools>
C:\Android\platform-tools>adb shell <<<---( it all looks good till here ) p.s by the way thks for your work i will send a don to u after all this !!!!!!!!!!!!) u will be happy!! G;"]>
Error: error: device not found

C:\Android\platform-tools>
Error: The system cannot find the path specified.
C:\Android\platform-tools>echo ro.kernel.qemu=1 > /data/local.prop
Error: 'cat' is not recognized as an internal or external command,

Error: operable program or batch file.
C:\Android\platform-tools>
Error:
C:\Android\platform-tools>cat ./data/local.prop

C:\Android\platform-tools>
C:\Android\platform-tools>exit

at this point i dont even get a reboot help Plz lol
XP and files in the right folder G:"]>
 
AnmFreak said:
then i click reboot
phone reboots and i do the other steps but phone is not rooted what did i do wrong


Program Forced close on while it was rebooting and now keeps booting up
Click to expand...

I have a similar issue (got it working before, thanks ktb). I get the message that the exploit was successfully called. I press continue, and then reboot. The message at the top says to press finish when the logo comes up, but I can't do that because the program crashes. The phone then goes into constant reboot loops.

I took the battery out, rebooted and got it to stop. Then I downloaded a couple different apps to check for root/su, and all three said it wasn't rooted.

Any suggestions for a way forward? What am I doing to cause the program to crash?

UPDATE: I did the process again, had the same issue and now even when I take the battery out of the phone, I can't get the phone to stop reboot looping.... :confused:

uh oh...?
 
thats what was happening to me b4 i fix the usb drivers but look at my post am still having trbs NO ROOT FOR ME !
 
I'm sorry to those who are having trouble. I will be back at my computer on Friday and I will be able to help more then.

As a general rule, if the lgoeExploit spits out something like (lib_USB interface(12)" or something like "usb line 404", then your drivers are not installed properly. Redo the steps with a new USB port.

And to the person who asked, in the zadig menu you choose,CDC seriasl interface 0, lg android USB interface 2 and lg android USB interface 3. And bricking is highly unlikely with this method but anything is possible.

I have plans to make this easier to use. The current program version only has about 15 hours put into it and then I had to leave town for a week. I will improve it when. I get back. Thanks foe your patience.
 
Er...I hate to be a pain, I appreciate your response to the thread (and the work), but... is my phone bricked because of the constant reboot loop?

Does anyone else have a suggestion? Taking the battery out does not help :(
 
Oh, and one more thing to those who are getting stuck in bootloops. I'm sorry for that, I'll work out the compatibility problems when I get back home. If you could pm me what problem exactly you're having, and what os you're on I would appreciate it. And to get out of it you can just do the giantpune manual root which can be found in the forums.
 
No, your phone is not bricked. Boot loop is suppossed to happen. The root can't be accomplished without kicking it into bootloop mode. You can either run the program again and just skip to the part you were last at, or do the manual giantpune root and scroll down to the bootloop section.
 
I tried this but am failing somewhere.

My phone has LG-OE_Diagm installed on it, when I enable it, It just sits there and says Trying to start DIAG menu.

I'm on the ZV5 update.

Also if I try to run the LG Optimus Elite Root v2.0 and try to verify the phones connected, it does not show up anymore. Restarted phone and computer.

Any ideas?
 
Yes, I managed to get myself out of boot loop using the method in the PDF in this thread:

http://androidforums.com/elite-all-...te-ultimate-rooting-guide-good-newcomers.html

and scrolling down to where it says Step 11 exit ./adb reboot, and following the instructions right after that using the terminal window.

(The instructions say I should be rooted after that, but still not, so I'm starting over at the top of the giantpune manual method for Windows.)
 
caspian915 said:
Yes, I managed to get myself out of boot loop using the method in the PDF in this thread:

http://androidforums.com/elite-all-...te-ultimate-rooting-guide-good-newcomers.html

and scrolling down to where it says Step 11 exit ./adb reboot, and following the instructions right after that using the terminal window.

(The instructions say I should be rooted after that, but still not, so I'm starting over at the top of the giantpune manual method for Windows.)
Click to expand...
Im so confused if u could help me im a newbie at this kind of stuff
 
try changing all your "adb shell" commands to "adb wait-for-device shell". it sounds like your script is running too fast and trying to connect adb while the phone isnt ready for it. the "wait-for-device" will make adb block until it sees a device to talk to.

Thats what that "error device not found" means.

and then it goes on to run some commands meant for the phone but its running them on the person's computer.
Code: 
C:\Android\platform-tools>
Error: The system cannot find the path specified.
C:\Android\platform-tools>echo ro.kernel.qemu=1 > /data/local.prop
Error: 'cat' is not recognized as an internal or external command,

Good thing the steps didnt include something like "rm -rf /" or you would have deleted the OS from his computer :D
Its also not a bad idea to actually check the return values from all those programs you are running. they usually return 0 if everything went well and something not 0 if an error happened.
 
Sure, no problem. All of this assumes that you downloaded all the files and drivers needed and put the important stuff in the folder C:\android\platform-tools. If not, you have to get that done first.

Go to that linked thread and download the PDF in the first post:

http://androidforums.com/elite-all-...te-ultimate-rooting-guide-good-newcomers.html

Open that up and the second page is the Index (table of contents). Chapter 3 says giantpune root (to clarify, giantpune is the username of the forum member who developed the root method). The second one says for Windows, which I assume for now that's what you have.

Scroll down to that section. Continue through that section til you get to Step 11:

Step 11-Type the following to exit the adb shell and reboot the phone

exit
./adb reboot
Click to expand...

After that, it says:

NOTE:When the phone reboots, it will be stuck in a boot loop. Your computer may not be able
to see it with ./abd. What worked for me, was I had to unplug the phone, take out the battery,
and then reboot my PC, and then plug the phone
back in. If your PC cannot see the device with ./adb after rebooting the phone, then reboot the
PC. You must then
Open up a terminal, go into the ./adb directory, and continue from there.
Click to expand...

I luckily didn't need to do all that, but you might. Make sure your phone is connected, via USB, even though it's boot looping.

Now for step 12, first go to your windows start button, and in the search box type cmd. The terminal window will come up. Type in (no quotes) "cd C:\android\platform-tools\". This will put you in that folder. Now start typing each line in Step 12, pressing enter afte each. (You can ignore the ./ part before adb since you're already in the folder. Just type

"adb shell" (don't put quotes) and press enter. Etc...

When you get to the last line "adb reboot" (no quotes), your phone should reboot, and if yours is like mine, then the stupid opening phone chime should come back during this reboot, and you will be back to normal. Hopefully.

From there, you can scroll up to the top of the Windows section and try this method of rooting via the cmd line.

I hope that helps.
 
I go on command prompt and put in ./adb shell so it looks like this

C:\User\Josiah>./adb shell
' . ' is not recgonized as an internal or external command, operable program or batch file

Im stuck!!
 
You're in the wrong directory. You have first change directories:

1) go into cmd
2) type (no quotes) "cd C:\android\platform-tools\"
hit enter
3) the terminal will come back with C:\android\platform-tools>
4) from there you can just type (no quotes) "adb shell" (you don't need the period front slash "./")... and the other commands, etc.

This assumes that your files are in that directory when you were following the directions for the easy click app in this thread. If you didn't, you won't get anywhere.
 
@Hastag or anyone that can help me, I have rooted about 4 optimus elites using the flashing firmware method through LGPNST, I just got a new elite (not rooted) and installed the OTA update, my question is can I still root my phone using the Original way? (LGPNST Way) Will my phone mess up? Or should it all be the same? Thanks alot guys
 
You must log in or register to reply here.
Back
Top Bottom