Root Click rooting your LG Optimus Elite

[Hashtag]

Does the root work?

Yes, the root works. But it wont work for yours until you find a way to stop the bootloop and fix it back to normal.

 

[climberwill]

alright ive gotten step one a bit further im getting

C:\android\platform-tools>ls -l /data/img
Info: 'ls' is not recognized as an internal or external command,
Info: operable program or batch file.

im a total newb here just wondering if anyone can help me

 

[climberwill]

alright i uninstalled everything and reinstalled it and this is what i get now when i run step 1

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

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

C:\android\platform-tools>adb wait-for-device shell
rm /data/img/image.bmp

ln -s /data/local.prop /data/img/image.bmp

ls -l /data/img

exit



$ rm /data/img/image.bmp

$ ln -s /data/local.prop /data/img/image.bmp

$ ls -l /data/img

lrwxrwxrwx shell shell 2012-08-16 16:44 image.bmp -> /data/local.prop

$ exit


C:\android\platform-tools>adb install -r Ministro2.apk
Info: can't find 'Ministro2.apk' to install

 

[Hashtag]

alright i uninstalled everything and reinstalled it and this is what i get now when i run step 1

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

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

C:\android\platform-tools>adb wait-for-device shell
rm /data/img/image.bmp

ln -s /data/local.prop /data/img/image.bmp

ls -l /data/img

exit



$ rm /data/img/image.bmp

$ ln -s /data/local.prop /data/img/image.bmp

$ ls -l /data/img

lrwxrwxrwx shell shell 2012-08-16 16:44 image.bmp -> /data/local.prop

$ exit


C:\android\platform-tools>adb install -r Ministro2.apk
Info: can't find 'Ministro2.apk' to install

You don't have the stuff in the right spot. When you download he file, you need to unzip it, and then put the files INSIDE the extracted folders in "C:\android\platform-tools". The zadig.exe, ministro2.apk, all of those need to be in the same folder as adb.

 

[climberwill]

ive downloaded the sdk plus, platform tools, and google usb. all under android, and the quick root program i unzipped to platform tools, do i need to move more files? thanks for you patience i really appreciate it

 

[Hashtag]

Here is what's required foe the root to work. These need to be in "C:\android\platform-tools"

adb.exe
LG_OE_DiagMode-debug-unaligned.apk
lgoeExploit.exe
Ministro2.apk
LG Optimus Elite Click Root.exe
su
zadig.exe



As long as you have those files in "C:\android\platform-tools", you'll be fine. And as long as the driver setup goes as planned

 

[mcgraham89]

Hi Hashtag, if I may make a suggestion maybe you should include the pictures in post: http://androidforums.com/4778345-post47.html with your download. Seems people are not understanding where the files need to be.

 

[ianreecej]

I start step one the green bar goes all the way across but nothing ever comes up.

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

C:\Android\platform-tools>adb wait-for-device shell

is all the displays in the text prompt


The phone is on and plugged in. The usb drivers are there. SDK is installed and updated. and files are located in C:\Android\platform-tools

Suggestions?

 

[humina]

same. Any help would be great

 

[David Dubz]

I found that if I turn off diag mode and turn usb storage on, THEN do the 3rd step of the root, it works. Don't worry about what it says at the bottom, no matter how many errors you get.

 

[danowic]

I found that if I turn off diag mode and turn usb storage on, THEN do the 3rd step of the root, it works. Don't worry about what it says at the bottom, no matter how many errors you get.

As David Dubz mentioned, if you turn off DIAG mode before step three, the phone will root. I have been trying for weeks to get the root clicking method to work , to no avail. Last night I clicked the first two buttons and then disabled DIAG mode on the phone before clicking step 3. The phone eventually rebooted and went into a bootloop. I then started the the
Click Root program again and pressed the step 3 button once more. The phone rebooted normally and now I have root!

 

[tbdsonicx]

i start step one the green bar goes all the way across but nothing ever comes up.

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

c:\android\platform-tools>adb wait-for-device shell

is all the displays in the text prompt


the phone is on and plugged in. The usb drivers are there. Sdk is installed and updated. And files are located in c:\android\platform-tools

suggestions?

same here. Can someone please explain what we are doing wrong. Thanks.

 

[tbdsonicx]

I finally got through all three steps, but my phone remains unrooted... i have a feeling it has something to do with the driver installation process. :l

 

[rayannerenae]

I'm trying to root my phone, and this just isn't making any sense to me. I am definatley not a pro. I'm racking my brain trying to figure this out. Help?

 

[Hashtag]

Make sure that your drivers are installed right. To do this, go to your device manager(start>right click my computer>manage>devices)

Near the bottom of the list, there should be a USB section that only had three things in it(CDC serial, lgusb android device, and another lg usb android device).

If it is not like this, then your driver setup is wrong.

Oh, and if would copy and paste the code from the box here, it makes it a lot easier to figure out the problem

 

[tbdsonicx]

Alright so i reinstalled the drivers like ... 3+ times and it shows the ones you're talking about in a little notification bubble towards the bottom of my screen which says theyre ready to use, and i reboot my computer, but they don't show up in my device manager or the zagid program (however you spell it) - so ... i dont know lol , ugh *sigh*

could we use that teamviewer method perhaps ??

 

[tbdsonicx]

>>>

 

[kwknott]

Hashtag I finally got a chance to try out your method and it worked perfectly for me. Glad you and greatpune could get these new methods worked out for everyone.

 

[ktb83]

Nevermind

 

[Dark One]

I finally broke down and took the ota update, and now I'm trying to get rooted again.


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

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

C:\android\platform-tools>adb wait-for-device shell
rm /data/img/image.bmp

ln -s /data/local.prop /data/img/image.bmp

ls -l /data/img

exit



$ rm /data/img/image.bmp

$ ln -s /data/local.prop /data/img/image.bmp

$ ls -l /data/img

lrwxrwxrwx shell shell 2012-08-22 01:42 image.bmp -> /data/local.prop

$ exit


C:\android\platform-tools>adb install -r Ministro2.apk
Info: can't find 'Ministro2.apk' to install

C:\android\platform-tools>adb install -r LG_OE_DiagMode-debug-unaligned.apk
Info: can't find 'LG_OE_DiagMode-debug-unaligned.apk' to install

C:\android\platform-tools>adb push su /data/local/tmp/su
Info: 1213 KB/s (22364 bytes in 0.018s)

C:\android\platform-tools>adb shell
$ 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.

$ exit


My adb stuff is in C:/android/platform-tools. Is it a driver issue? I have rooted and flashed the stock firmware using jcase's method. Here is my device manager:

 

[kwknott]

You also need to put the files from the one click root in the platform-tools folder along with adb. Well you can run the actual one click program from anywhere but it looks for the other files in c:\android\platform-tools.

I just put everything there and runs fine.

 

[neothejedi]

Thanks for putting up with us dunderheads!
I run the program put all files where there supposed to be i think?
do step one two then on step three i get to the second reboot program crashes no root but i get this in the program view before it crashes
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>adb wait-for-device shell
rm /data/img/image.bmp
ln -s /data/local.prop /data/img/image.bmp
ls -l /data/img
exit

$ rm /data/img/image.bmp
rm failed for /data/img/image.bmp, No such file or directory
$ ln -s /data/local.prop /data/img/image.bmp
$ ls -l /data/img
lrwxrwxrwx shell shell 2012-08-22 07:50 image.bmp -> /data/local.prop
$ exit

C:\android\platform-tools>adb install -r Ministro2.apk
pkg: /data/local/tmp/Ministro2.apk
Success
Info: 5113 KB/s (490122 bytes in 0.093s)
C:\android\platform-tools>adb install -r LG_OE_DiagMode-debug-unaligned.apk
pkg: /data/local/tmp/LG_OE_DiagMode-debug-unaligned.apk
Success
Info: 3362 KB/s (537135 bytes in 0.156s)
C:\android\platform-tools>adb push su /data/local/tmp/su
Info: 1399 KB/s (22364 bytes in 0.015s)
C:\android\platform-tools>adb shell
$ 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 }
$ exit

C:\android\platform-tools>cd C:\android\platform-tools
C:\android\platform-tools>
C:\android\platform-tools>zadig.exe
C:\android\platform-tools>cd C:\android\platform-tools
C:\android\platform-tools>lgoeExploit.exe
Warning: Line: 404 libusb_open_device_with_vid_pid()
Info: libusb: 0.000000 warning [init_device] could not get node connection information for device '\\.\USB#VID_046D&PID_C404#6&35B93047&0&3': [87] The parameter is incorrect.
Info: libusb: 0.249601 warning [init_device] could not get node connection information for device '\\.\USB#VID_1004&PID_6310#A0000031D57387': [87] The parameter is incorrect.
C:\android\platform-tools>adb wait-for-device 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

C:\android\platform-tools>adb reboot
C:\android\platform-tools>adb wait-for-device shell

running windows ultimate 7 64 bit
Help? pleaseeeeee

 

[Hashtag]

That line 404 means that the drivers weren't installed right. Check it again, and make sure your phone is in diag mode.

 

[Curtis1973]

yeah this root method works well,you do need everything in correct folders,etc and be patient while it does its thing. thanks hashtag.

 

[Dark One]

I rebooted my phone and tried again.

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

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

C:\android\platform-tools>adb wait-for-device shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
rm /data/img/image.bmp

ln -s /data/local.prop /data/img/image.bmp

ls -l /data/img

exit



adb install -r Ministro2.apk

adb install -r LG_OE_DiagMode-debug-unaligned.apk

adb push su /data/local/tmp/su

adb shell

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

exit

$ rm /data/img/image.bmp

$ ln -s /data/local.prop /data/img/image.bmp

$ ls -l /data/img

lrwxrwxrwx shell shell 2012-08-22 21:12 image.bmp -> /data/local.prop

$ exit

Any ideas? The jcase method will not work after the update right?