-
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
- Thread starter Hashtag
- Start date
-
- Tags
- lg optimus elite
HackADevice
Well-Known Member
so if i click all steps on step 3 and it goes into bootloop i click all step 3 and it will kick me out of it rooted? Because i really want this root and im stumped
Hashtag
Android Enthusiast
No the the you clicking it twice, yes to the it will kick you out of bootloop. You only have to click step 3 one time, it has timers setup to automatically run the scripts at the proper time.
If you're not comfortable doing it, just download teamviewer, PM me your ID and password, and I'll root it for you.
HackADevice
Well-Known Member
ok i sent it to you
2048ghz
Lurker
Thank you Mr. Hashtag
For all your hard work I know we all thank you! G:"
And Thank you all for your work ! G:"
http://androidforums.com/members/hashtag.html
For all your hard work I know we all thank you! G:"
And Thank you all for your work ! G:"
http://androidforums.com/members/hashtag.html
HackADevice
Well-Known Member
Hashtag just rooted my phone using teamviewer he's legit and won't mess with your computer
U ROCK HASHTAG!!!!!!!
U ROCK HASHTAG!!!!!!!
anotheruser1
Newbie
ok i got step 1 and 2 of giantpunes root. this is what i keep getting
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 error [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_138A&PID_0005#00A0E0E7F085': [31] A device attached to the system is not functioning.
C:\Android\platform-tools>
C:\Android\platform-tools>
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 error [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_138A&PID_0005#00A0E0E7F085': [31] A device attached to the system is not functioning.
C:\Android\platform-tools>
C:\Android\platform-tools>
Hashtag
Android Enthusiast
Okay, that "404 libusb" stuff means that your computer can't find your phone. Most likely, the driver step wasn't done right for some reason. Run step 2 again, and make sure to install drivers for CDC serial interface 0, LG Android USB interface 2, and LG Android USB interface 3. And make sure that you have DIAG mode enabled. Then try again.
anotheruser1
Newbie
CDC serial interface 0, LG Android USB interface 2, and LG Android USB interface 3. are not in the dropdown menu. i installed every driver that had lg on it. the diag mode is on the screen of the phone and enabled. a side note the device verify thingy showed the listed devices text so i think it sees the phone
anotheruser1
Newbie
after rebooting CDC serial interface 0, LG Android USB interface 2, and LG Android USB interface 3. show up and are installed.now i get 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
Line: 472 MSL:
00000000 30303331 3734 003174
Line: 1da Found a device running in Diag Mode
Line: 1f5 2a
Error: libusb: 0.000000 error [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_138A&PID_0005#00A0E0E7F085': [31] A device attached to the system is not functioning.
Exploit called successfully
C:\Android\platform-tools>
C:\Android\platform-tools>
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
Line: 472 MSL:
00000000 30303331 3734 003174
Line: 1da Found a device running in Diag Mode
Line: 1f5 2a
Error: libusb: 0.000000 error [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_138A&PID_0005#00A0E0E7F085': [31] A device attached to the system is not functioning.
Exploit called successfully
C:\Android\platform-tools>
C:\Android\platform-tools>
Hashtag
Android Enthusiast
Hmm, why don't you try putting it into another usb port. And make sure that the winUSB drivers are installed in zadig.
anotheruser1
Newbie
now i am getting 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
Line: 472 MSL:
00000000 30303331 3734 003174
Line: 1da Found a device running in Diag Mode
Line: 1f5 2a
Error: libusb: 0.000000 error [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_138A&PID_0005#00A0E0E7F085': [31] A device attached to the system is not functioning.
Exploit called successfully
C:\Android\platform-tools>
C:\Android\platform-tools>
thanks for your help and patience
Hashtag
Android Enthusiast
Okay, try to clear your cache. On your phone, turn it off. Once it's off, turn it back on by holding down the power key and the down volume until you are brought to something called a recovery menu. From there, use the volume keys to navigate to the clear cache option, then hit the menu button at the bottom of your phone. Once that gets done, go up to reboot system and select it to restart your phone. As far as your computers cache, right click on the desktop, new>shortcut. Then, when it asks for the location, put in "%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks". Save that new shortcut to your desktop, then right click, run as administrator, and then wait a second. After you do these, try again. If you can't get it after that, then download teamviewer, and PM me with your teamviewer ID and Password. I'll see what I can do for you. Good luck
Android311
Android Enthusiast
When I connect my phone to my computer using "mass storage" option my phone connect's and disconnects all the time by it's self, do you think it may be because during the one click root we had to reinstall different usb drivers?
Hashtag
Android Enthusiast
Possibly. You don't need those drivers anymore, so you can install the regular LG drivers if you'd like.
Android311
Android Enthusiast
Ok thanks I'll give that a try and report
anotheruser1
Newbie
Okay, try to clear your cache. On your phone, turn it off. Once it's off, turn it back on by holding down the power key and the down volume until you are brought to something called a recovery menu. From there, use the volume keys to navigate to the clear cache option, then hit the menu button at the bottom of your phone. Once that gets done, go up to reboot system and select it to restart your phone. As far as your computers cache, right click on the desktop, new>shortcut. Then, when it asks for the location, put in "%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks". Save that new shortcut to your desktop, then right click, run as administrator, and then wait a second. After you do these, try again. If you can't get it after that, then download teamviewer, and PM me with your teamviewer ID and Password. I'll see what I can do for you. Good luck
OK, I will do that first thing in the morning. My brain has had enough for tonight. Thank you for your time and patients.
anotheruser1
Newbie
ok i did exactly as you said with the cache .
jcase root gives
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 push su /data/local/tmp/su
Error: 1399 KB/s (22364 bytes in 0.015s)
C:\Android\platform-tools>adb push jc.sh /data/local/tmp/jc.sh
Error: 0 KB/s (258 bytes in 1.000s)
C:\Android\platform-tools>shell chmod 755 /data/local/tmp/jc.sh
Error: 'shell' is not recognized as an internal or external command,
Error: operable program or batch file.
C:\Android\platform-tools>adb reboot
C:\Android\platform-tools>
giantpunes root gives
C:\Android\platform-tools>cd C:\android\platform-tools
C:\Android\platform-tools>lgoeExploit.exe
Line: 472 MSL:
00000000 30303331 3734 003174
Line: 1da Found a device running in Diag Mode
Line: 1f5 2a
Error: libusb: 0.000000 error [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_138A&PID_0005#00A0E0E7F085': [31] A device attached to the system is not functioning.
Exploit called successfully
C:\Android\platform-tools>
C:\Android\platform-tools>
i am going to look up teamviewer and see what i can do there. One question though, is it possible that it is windows 7 causing this issue? I know it has a lot of crap blocked where i have to go thru hell to get around it, so is there anything like the user account control that might be the cause. I have admin privilages , firewalls and virus scan are off, i even choose run as admin on the root program. thanks again
jcase root gives
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 push su /data/local/tmp/su
Error: 1399 KB/s (22364 bytes in 0.015s)
C:\Android\platform-tools>adb push jc.sh /data/local/tmp/jc.sh
Error: 0 KB/s (258 bytes in 1.000s)
C:\Android\platform-tools>shell chmod 755 /data/local/tmp/jc.sh
Error: 'shell' is not recognized as an internal or external command,
Error: operable program or batch file.
C:\Android\platform-tools>adb reboot
C:\Android\platform-tools>
giantpunes root gives
C:\Android\platform-tools>cd C:\android\platform-tools
C:\Android\platform-tools>lgoeExploit.exe
Line: 472 MSL:
00000000 30303331 3734 003174
Line: 1da Found a device running in Diag Mode
Line: 1f5 2a
Error: libusb: 0.000000 error [cache_config_descriptors] could not access configuration descriptor (dummy) for '\\.\USB#VID_138A&PID_0005#00A0E0E7F085': [31] A device attached to the system is not functioning.
Exploit called successfully
C:\Android\platform-tools>
C:\Android\platform-tools>
i am going to look up teamviewer and see what i can do there. One question though, is it possible that it is windows 7 causing this issue? I know it has a lot of crap blocked where i have to go thru hell to get around it, so is there anything like the user account control that might be the cause. I have admin privilages , firewalls and virus scan are off, i even choose run as admin on the root program. thanks again
Hashtag
Android Enthusiast
Are you using that from my program? The program I made hasn't had jcase root for several versions now. Use the updated one. And yeah, just PM your teamviewer stuff when you get it. And now, windows 7 is not the problem because most people have it and are rooting with it.
AnonymousRUDEV
Lurker
But now I'M not sure how to CWM or which phone model to pick when I try to
Hashtag
Android Enthusiast
We don't have a CWM for this phone yet. If you'd like to get one, then you can go over to the donate thread and contribute to the dev fund.
anotheruser1
Newbie
I have been using the click root 2.0, I am d/l the new version and see what happens
Thanks again
climberwill
Lurker
i hit "start step 1" and i just keep waiting nothing pops up on my phone
