Here is a screen shot of whats going down.
i tried this without having SDK first. then i was informed that i needed it so i installed that.
any help is appreciated.
im trying to post a screen shot of this but a mod needs to verify me! and ill post it asap.
or just remove the spaces
http:// img.photo bucket. com/albums /v379 /omgzkoolaid/ Untitled-4.jpg
edit with different link
http:// img.phot obucket.com/ albums/v379 /omgzkoolaid/ Untitled-4.jpg?t=1285885727
Image has been deleted.
Jakeslimberg1 said:
Here is a screen shot of whats going down.
i tried this without having SDK first. then i was informed that i needed it so i installed that.
any help is appreciated.
im trying to post a screen shot of this but a mod needs to verify me! and ill post it asap.
or just remove the spaces
http:// img.photo bucket. com/albums /v379 /omgzkoolaid/ Untitled-4.jpg
Click to expand...
Click to collapse
Without being able to see your image, let me make an educated guess as to what's going on:
You are connected to adb and running the Rage exploit. It does its thing, which looks like this:
# ./rage.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2933
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
#
(your prompt here)
Click to expand...
Click to collapse
So it does it's thing, then a little later kicks you all the way back out to your terminal window. If this is correct, then it is doing just what it's supposed to do.
Like it says in the rooting thread:
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
Click to expand...
Click to collapse
When it's done, you will have to re-establish an adb connection to your phone.
Once again, Google's your buddy.
Hope this helps...
i edited it with a new link that works try the second one.
i was not doing the manual method i was doing the one click one!
Having the same problem with one-click root.
Exploited Successfully
Pushing Permanent Root and Removing Temp Files
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
RESTARTING...
Error Device Not Found
Done.
broncobiker said:
Having the same problem with one-click root.
Exploited Successfully
Pushing Permanent Root and Removing Temp Files
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
Error Device Not Found
RESTARTING...
Error Device Not Found
Done.
Click to expand...
Click to collapse
reflash your system back to stock. then try again
Im already at stock. I had to after I bricked last night.
Ill try again after dinner and let you know if it works. Just for an update, if I launch the app again immidiately after failing it doesnt show my phone there, and then my phone freezes and needs to be pulled.
here's a thought, do the manual method. It's not hard by any means, just takes a few more minutes.
now proceeding with your regularly scheduled program.
mackeydesigns said:
here's a thought, do the manual method. It's not hard by any means, just takes a few more minutes.
now proceeding with your regularly scheduled program.
Click to expand...
Click to collapse
What he said! It's a few more minutes and you really learn a lot about what you're doing.
Sent from my SCH-I500 using XDA App
I can't find it haha everywhere I look its the OCR process. Ill check into it, I would really prefer doing it manually, thats what I did on my Eris.
--EDIT--
Following the manual instructions worked, that one click has been buggy from the start. I'd suggest doing that. Flashing the new ROM now and everything seems to be working perfect. Thank you guys, appreciate the support of the members and the work of the devs.
I had to insert a pause here or there and i finally got the one click working.
It seems like they expected the phone to reboot at the speed of light..
Related
This is made for any HTC Android 2.1 device based from the HTC Legend OTA exploit
Originally created by @Eugene_373, scripted/modified by @WesGarner
Download and extract these according to your platform:
http://bit.ly/wesaspin#285
Report Issues: http://code.google.com/p/wgbuild/issues/list
In a command shell, run rootme. The stuff below is a copy of what is prompted to you in the shell
At this point, your phone should be booted as normal
Make sure these three things:
USB Debugging Enabled - Settings/Applications/Development
USB Connection Type - Charge Only (select on your notifications bar)
ADB Server needs to be pre-started (can do this via sudo adb start-server)
[Asks you to press the enter key]
This will reboot your phone into recovery, hopefully with adb working via the loop exploit
To access the controls in recovery, press Volume Up+Power
From here, use the Volume buttons to go up and down and the Power button to select
[Asks you to press the enter key to begin the loop exploit]
Once the phone is rebooted into recovery, you will see one of the following outputs:
Successful: - exec '/system/bin/sh' failed: No such file or directory (2) -
Unsuccessful: error: device not found
If successful, then run rootme2
If unsuccessful, reboot your phone then rerun this script
To access the controls in recovery, press Volume Up+Power
From here, use the Volume buttons to go up and down and the Power button to select
Press CTRL+C to end the loop script
Your phone will now reboot into recovery, press enter
[Run rootme2 if successful]
OK! Congratulations, your phone is almost ready to be rooted
Here is the tricky part...
To access the controls in recovery, press Volume Up+Power
From here, use the Volume buttons to go up and down and the Power button to select
IMPORTANT:
You will select apply update.zip, but within 1/2 sec of doing this you must press enter to continue this script
Also, it helps to stare at the screen until you see a progress bar under the text
If it is not done in the timely manner, you can try again by rerunning this script
From here, you should see ClockWork Recovery by Koush, and can install any ROM you would like!
Wes Garner
Twitter: http://twitter.com/wesgarner
Donation: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=10254127
Eugene_373
Twitter: http://twitter.com/Eugene_373
Donation: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8574353
Hey wes, use the New Root.zip I posted regarding the Update.zip
Once the Update is ran, everything is Golden.. Su / Superuser.apk & everything is Fixed & installed at once..
Kudos for a legible guide, and an effective root method.
As someone who spent an entire afternoon trying to root my slide, I know how grateful people will be with this method available.
Good work sir.
slobatch said:
Kudos for a legible guide, and an effective root method.
As someone who spent an entire afternoon trying to root my slide, I know how grateful people will be with this method available.
Good work sir.
Click to expand...
Click to collapse
Yes legible, It just automates everything for you
I understand people are having trouble with it, but I honestly thought mine was easy to understand..
Major Kudos Wes, for making this Noob Friendly
~Eugene
eugene373 said:
Yes legible, It just automates everything for you
I understand people are having trouble with it, but I honestly thought mine was easy to understand..
Major Kudos Wes, for making this Noob Friendly
~Eugene
Click to expand...
Click to collapse
I understood yours perfectly.
I know this will be totally noobish but I don't care at this point (4 hours in to attempting root). What is sudo adb start-server? I tried typing it in but I got "'sudo' is not recognized as an internal or external command, operable program or batch file. I tried finding it on google but no real luck. I don't mean to clog up the forums but I am getting desperate.
Edit: I now have root but used the original way. Had some major problems. Please place on the disclaimer that this works best with a class 2 card. I couldn't get it to work with a Class 6 and only found that was an issue after snooping through hundreds of posts. Thanks Wes, Eugene, and all involved!!!!!
eugene373 said:
Yes legible, It just automates everything for you
I understand people are having trouble with it, but I honestly thought mine was easy to understand..
~Eugene
Click to expand...
Click to collapse
You bet it was! I was understandably cautious in rooting my first android. I read your guide 3 times and went for it. Took 10 minutes with lots of tripple checks. Soooooo easy. I thank you greatly for your work and I am a rom switching junkie thanks to it!!
simplyTravis said:
I know this will be totally noobish but I don't care at this point (4 hours in to attempting root). What is sudo adb start-server? I tried typing it in but I got "'sudo' is not recognized as an internal or external command, operable program or batch file. I tried finding it on google but no real luck. I don't mean to clog up the forums but I am getting desperate.
Edit: I now have root but used the original way. Had some major problems. Please place on the disclaimer that this works best with a class 2 card. I couldn't get it to work with a Class 6 and only found that was an issue after snooping through hundreds of posts. Thanks Wes, Eugene, and all involved!!!!!
Click to expand...
Click to collapse
"Sudo" is a linux command to run as root and as such is only needed if your running linux. If your using Windows you would just type "adb start-server" (I think, it's been a while since I've used Windows). But glad you got root with original method.
heybobitsme said:
"Sudo" is a linux command to run as root and as such is only needed if your running linux. If your using Windows you would just type "adb start-server" (I think, it's been a while since I've used Windows). But glad you got root with original method.
Click to expand...
Click to collapse
You are correct, Good advice
eugene373 said:
You are correct, Good advice
Click to expand...
Click to collapse
Thank you, sir!
Now, about Froyo... Just kidding!
Anyone know if this root method gets Root Explorer and Metamorph working?
So I ran into a problem using the SimpleRoot v1.3 Linux. I tried to follow the instructions, and was able to do the rootme. When I try to execute the rootme2 script I run into a problem. When trying to "select apply update.zip, but within 1/2 sec of doing this you must press enter to continue this script" I get one of two errors. This is what comes up on my phones screen. Any idea what it is? Or why this is happening?
Code:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
or
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
slughappy1 said:
So I ran into a problem using the SimpleRoot v1.3 Linux. I tried to follow the instructions, and was able to do the rootme. When I try to execute the rootme2 script I run into a problem. When trying to "select apply update.zip, but within 1/2 sec of doing this you must press enter to continue this script" I get one of two errors. This is what comes up on my phones screen. Any idea what it is? Or why this is happening?
Code:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
or
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
Looks like you pressed the enter key too fast - look for the bar behind the text and give it a go
Need help
Could someone please help me with pre starting the ADB server. I dont know if this is the reason but my mt3gs wont boot to recovery mode automatically. My phone is in debugging mode and charge only. When i ran rootme from command prompt my device was not detected. I hope thats enough info to figure out my problem. Thanks in advance.
Ratard
So I had absolutely no issues rooting my G1 or my original MyTouch, but I can not make it work on the slide. It never sees my phone except for a split second after it reboots. After that it just cant see the phone at all. I've retried it multiple times to no avail. Any suggestions?
I knew this would happen. It took me a week to root my slide the hard way, now this is out
Let's hear some noise for the impatient!
Great job on another release Wes!
Thanks for your hard work
wesgarner said:
Successful: - exec '/system/bin/sh' failed: No such file or directory (2) -Unsuccessful: error: device not found
If successful, then run rootme2
If unsuccessful, reboot your phone then rerun this script
/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8574353[/url]
Click to expand...
Click to collapse
I just got my slide today and followed your instructions to the letter about 5 times and each time I get the same unsuccessful result. I get into the recovery menu using vol+up and power but the loop script never finds the device at this point.
When the device is fully booted and powered on, I'm able to adb shell into it just fine, but after it reboots and goes into recovery, I looked in device manager and there are no adb drivers present and no hardware missing drivers. Any suggestions?
not to say that i am not grateful(i deffinately am) but why do we make it easier and easier to root our phones? isn't rooting supposed to be for the advanced users that know what can be done after root? shouldn't we just discover one method and leave it at that? i wrote a script as well that does this on the windows box, but i didn't see a point in fixing it as you have honestly just made it too easy to root(and therefore screw) your phone. i like the old way of doing things where we had to work it out on our own and if we wanted scripts and such we needed to write them ourselves. just throwing these thoughts out there
P.S. eugene your way took 10 minutes and my script took 8 minutes, your way worked fine except my power flickered while rooting so i had to wait for comp to reboot so i could continue.
P.P.S. thank you wes for this
tubaking182 said:
not to say that i am not grateful(i deffinately am) but why do we make it easier and easier to root our phones? isn't rooting supposed to be for the advanced users that know what can be done after root? shouldn't we just discover one method and leave it at that? i wrote a script as well that does this on the windows box, but i didn't see a point in fixing it as you have honestly just made it too easy to root(and therefore screw) your phone. i like the old way of doing things where we had to work it out on our own and if we wanted scripts and such we needed to write them ourselves. just throwing these thoughts out there
P.S. eugene your way took 10 minutes and my script took 8 minutes, your way worked fine except my power flickered while rooting so i had to wait for comp to reboot so i could continue.
P.P.S. thank you wes for this
Click to expand...
Click to collapse
back in my day we had to walk 15 miles up hill and we liked it...in the snow...naked
the other methods weren't exactly full proof, getting the loop to catch and stay in offline mode was a huge pain in the ass and the only known working method was to buy an a 16GB microSD. So yes, easier is better.
It's not like this is an exclusive club or anything...android is supposed to be open.
Not saying this should be exclusive, just saying that there are some people out there that are just too dumb to figure out how to do it and by making it easier we are just making more threads on main page telling us that WE broke their phone and that its <enter dev name here>'s fault that it didn't work. Not trying to fight just figured that we should stick to the stuff that means people have to know how to use a computer
So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
I have an LG Enlighten (Verizon Wireless), not an LG Optimus Slider (Virgin Mobile), running Android 2.3.4 (Gingerbread). I am in desperate need of a root solution. I have searched the online forums to no avail. I have put the phone up for sale for fear that this device may never be rooted. I am calling on XDA Developers to produce a working root before I ultimately rid myself of this thing. To add, I tried running Android SDK (adb). No go. The instructions threw me even after trying them repeatedly on several different occasions. It could be that my laptop
has no internet access, but I'm not entirely sure.
I really enjoy this phone and have customized it to the point of
exhaustion. All I'm waiting for now is ROOT! Please help ASAP...
Have you attempted to root it? Have you tried Superoneclick, z4root, and/or Gingerbreak?
Re: Have you tried to root it?
Yes, I have. Unfortunately, with no success. Results are as follows:
Z4Root - The end result is my phone takes me back to the previous screen (internet, home, games, music, etc.). It begins the rooting process... acquiring shell root. Then it just sticks for approximately 30 seconds and then closes. I have repeated the process on several occasions in the event that something unusual happened the first time around. But the result is always the same.
Gingerbreak - This app just ultimately hangs, endlessly. Approximately two hours worth before I just quit in frustration. But all online forums claim it should take no more than 15 minutes tops. I should also note that I read Z4Root and Gingerbreak will not work on rooting Android 2.3.4 due to the patching of an exploit. However, I did not update my phone to this firmware. It came preinstalled. And I have not found a procedure for downgrading (sbf'ing) an LG Enlighten.
SuperOneClick - This is the one I'm currently trying still. I can't recall the website, but in addition to SOC, it also requires the use of adb from Android SDK. The problem I'm coming across is the laptop I'm using to perform this action is without internet access (which I've tried feverishly to restore to no avail). And I'm thinking this is what the issue may be, but I'm not entirely sure. The only access I have to the internet currently is on my phone. However, I make a weekly trip to the college library (no restrictions on installing, downloading, etc.). So maybe I can try something there.
For the past month, I've been doing extensive research online trying to find any and all information in regards to resolving this matter. A few sites have blamed Verizon for crippling their Android devices from performing certain functions. For instance, this particular device has no "boot into recovery mode" (which I confirmed with a Verizon tech support person). Had it, I easily could've updated with the .zip file from my SD card (which I've now deleted since it's rendered useless).
I did read today that the next version of SuperOneClick v2.3 (to come out at a later date) will include the option for the forced inclusion of adb debugging/android files which could be the solution to my problems. Possibly.
I apologize if this reply post seems a little long-winded. But I wanted to provide you with all the information I have available in order to better recieve instruction as how to proceed forward. I will continue to try the SuperOneClick in hopes that I will acquire root. But if not, I will rely on the expertise of those in the XDA community.
Thanks,
Centim6
Rooting LG Enlighten
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Hi, I too have an LG Enlighten from Verizon wireless. I was just wondering how your root process went? Did the phone work well afterwards? Also do you by any chance have a link to or at least remember the name of the video you watched which helped you to get your phone rooted.
thanks in advance, Angel
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Can you link to the video?
Sparky42 said:
Can you link to the video?
Click to expand...
Click to collapse
seeing as there is no link, I would say no.
secondly, the video posted and my own research indicates that root was possible only if it was v. 2.3.3. There isn't anything available for 2.3.4.
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
fsdfgasgfisd said:
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
Click to expand...
Click to collapse
I think it would a great idea to include which firmware you used this on. I kbow for a fact that it fails on v4 and v5.
And its not that I don't believe you (I do btw) its just the lack of specifics are going to excite someone and they'll leave you a nasty message cause they thought it would work. So, just a heads up:
Android version:
Firmware version:
Sent from my LG-VS700 using xda premium
I can confirm that the new VS700ZV5 update crippled the ability of this phone to root. I just tried the gingebreak and it didnt work. Any way around this?
Same here, android 2.3.4; firmware VS700ZV5.
I haven't been able to get root to work with SoC....
Any chance someone will figure a way around this update?
please reply to root on you tube PLEASE!
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Extremely frustrated and hoping you will share this link. I to have tried everything to root my Enlighten to no avail and would appreciate your help more than I can explain! Please! Thank you and congats!
I had my phone rooted, then verizon put out an update, and now I can't root it. I think we're screwed until sombody figures out a new method.
Model: LGVS700
Firmware: VS700ZV5
im not sure if this will help but here, i found this claiming to be able to root the phone.
First, you need the file hboot_2.xx_soff-V8.9.zip, download it.
Unzip it into c:evoroot on your pc.
Second, put your LG Enlighten into development mode by
going to Settings->Applications->Development and turn USB
debugging on.
Third, connect your LG Enlighten to your computer and set
your USB to Just charge.
Fourth, if you get errors with drivers, install their HTC drivers.
(You can also install HTC Sync, but it is bulky!)
Fifth, open up a command prompt by typing cmd.
Sixth, type the following commands: (Or copy and paste,
easier!)
Code:
cd evoroot
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb -d install -r root/z4root.apk
Seventh, go to your phone and launch Z4Root app. Then select
temp root and wait until its done.
Eighth,go back to command prompt and type:
Code:
adb shell
su
If you get a pound(#) sign, that means you have temp root,
which just gives you temporary root so we can now install
permanent root.
ninth, go back to command prompt and type the following:
Code:
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
And reboot to bootloader mode by typing:
Code:
reboot bootloader
When bootloader mode starts up, it will look for PC36IMG.zip
and after about 3 minutes ask you if you want to install
PC36IMG.zip.
Say Yes by hitting the volume up button, it should now install
the new zip file, should take about 10 minutes. Go grabs some
coffee and come back.
Eleventh, reboot when its done by hitting the volume up
button.
It will reboot into the OS and we dont want that so takes the
battery out and puts it back in it. Then go back to the
bootloader by hitting the power button while holding down
the volume down button.
Choose Bootloader and wait until you get the triangle sign and
type:
Code:
adb push recovery /
adb shell busybox Cinstall /sbin
adb shell nohup /sbin/recovery
&
Go back to your LG Enlighten and you should see green
menus.
Choose install zip from sd card and choose unrevoked-
forever.zip
After that installs, Choose MS-USB
Go to your computer and delete PC36IMG.zip, then rename
PC36IMG-MR.zip to PC36IMG.zip.
Then power off your LG Enlighten, power back on by pressing
Power Button while holding down the Volume Down button,
this should get you back into bootloader mode.
Simply wait and when it asks to install the update, hit the
Volume Up button.
then reboot your LG Enlighten, your device should now be
rooted with Recovery menu then you can flash new ROMs for
LG Enlighten.
LG Enlighten root
I have lg enlighten running 2.3.4 and it is rooted with super user and rom toolbox working. I used POOT.APK which can be found on google. It worked well and everything went smooth. It is a simple and easy to use application. (You can use either SU or SSU)
any way to update it to ics? i have one
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
i just got the Q for my girl, i was wondering the same, just to remove the bloat. can someone please point me to the right direction?
Just checking in to see if anyone has found any answers.
Network24 said:
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
Click to expand...
Click to collapse
where can i find these threads? can you point me to it... maybe i can try and find something, or do something different and help out with solving it.
EDIT: did these threads say for the MTQ or was it just a thread for a random 2.3.4 device?
The threads I saw were just for a random 2.3.4 device. I saw another thread on xda with someone trying to root this phone but just like this thread no one is answering.
Has anyone found any methods to root this phone?
Success!
After several attempts to root via SuperOneClick 2.2, I tried something totally random from another LG rooting thread that seems to have worked. Install ADB, then do:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Then run SuperOneClick 2.2 and it should root properly.
I will have to give this a try on one of my Windows PC's. Linux and SuperOneClick are not playing nice together right now.
+1
Good Job Man....Worked for me. Have root and superuser.
Ditto! Root, & Superuser
== Instructions that worked for me ==
- Download myTouch Q drivers (Search "mytouch Q usb drivers" - Can't post links yet! XD )
- Check that adb recognizes device: C:\> adb devices
- Follow eamondaly's instructions:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Click to expand...
Click to collapse
- Run SuperOneClick v2.2
- Wait for phone to reboot (SuperOneClick seems to be paused)
- Reset USB debugging (mine was turned off after reboot)
- Wait for SuperOneClick to finish.
- Enjoy rooted phone
Thanks
Okay thanks for the root methods greatly appreciated but now I am starting to get into developing anyone can teach me how to make a system dump to try and make my own roms I am a fast learner ort at least point me in right direction thanks again
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
DMOYER said:
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
Click to expand...
Click to collapse
you are running under admin right I know silly question but had to as lol
Thanks eamondaly
I just want to thank eamondaly for this method. I just ran superoneclick 2.3.1 and it worked perfectly. I don't know if it was your method that worked or if superoneclick 2.3.1 fixed it but all that matters is my phone is now rooted. Thanks.
Thanks a lot for the root method, I've been waiting patiently for this. Now can we get to making mods for this phone now?
Edit: Anyone having trouble sending/receiving MMS messages? I cant seem to send or receive them.
I was having an issue with receiving MMS on both my wife's and my phone. Ditching the stock messaging client and downloading Handcent resolved it for both.
Switching MMS apps didn't work. Tried a number of countless APN setups. I just decided to unroot and factory reset. Everything is working again.
titanium pro back up image
hey all,
Im sure this is a random spot for this but, since we dont have a home yet.
Im looking for a stock back up image (Titanium backup pro)with all apps and system settings. I think I may have cleared out a system file or two when cleaning out all the Tmo bloat.
Any help or other suggestions would be great.
I found another way to root easily. http://www.unlockroot.com download, install and click root. I had issues with superoneclick and the adb method but this gave me full root with superuser and now I am happy that all the t-mobile crapware is gone
I'm trying to root my T-Mobile MyTouch Q and not having any luck. It's Android 2.3.6, but I tried running "echo 1 > /data/local/lge_adb.conf" and I get a permission denied error. I tried SuperOneClick version 2.2 and 2.3.3. SuperOneClick gets to step 7 than hangs and nothing happens. It says waiting for device. I also tried Unlock Root and it fails to get shell root. I searched all over google and the xda forums, but all say to run that command then run SuperOneClick and that hasn't worked for me. Anyone have any ideas?
I've got an Iconia tablet with a broken recovery (I've been using CWM and Thor's ICS ROM). I'm going to follow the steps outlined here
http://forum.xda-developers.com/showthread.php?t=1129873
but.... when I look up the UID from every method, all I get is 0123456789ABCDEF.
Given all the dire warnings about not being able to recover if/when things go wrong without the real UID... this 123 UID isn't the real UID.... is it safe to proceed with the repair here? Or are things really messed up?
I have not messed with ICS myself, but my understanding from reading the ICS threads in the Iconia forums is that the device is no longer using the uid for usb serial number. So it seems you can't get it that way if you have installed any of the ICS updates.
The suggestion I have seen is to look for androidboot.serialno in dmesg directly after booting, but that does not seem to help everyone.
Another option might be to get the device into APX mode and do a usb bulk read, the first read should return 8 bytes that is the UID. I would assume this to still work even after you have installed ICS but I have not tried. I pasted some code for opening the device, reading and printing the uid (using libusb, tested on Linux) on the Iconia forum earlier this week.
Hmm OK that's helpful info. Thanks.
I tried the androidboot.serialno in dmesg, but I wasn't able to find the string.... I will try that again after a clean boot.
I've been doing all the debugging from my one Windows machine... I haven't tried plugging it into my Linux PC yet... that's next... I haven't discovered APX mode yet. Time to do some more reading, thanks for the pointers.
Edit 1: OK checked lsusb -v and I serial also shows 0123456789ABCDEF
Edit 2: Clean boot and did a new dmesg dump.. parsed the output and no sign of androidboot.serialno or anything that even resembles it.
OK, things are not getting better here. I've been tinkering a lot, and in some respect I've just made things worse.
I still cannot find the UID with any of the documented methods here on XDA. I've tried
using adb devices
using Linux lsusb -v
checking the output of dmesg for androidboot.serialno
plugging in to Windows and looking at the USB mount info using USBDeview
looking at the device manager in Windows and checking the "Parent" field
I have also booted into APX mode and to discover the UID that way too... and nothing.
All I get is 0123456789ABCDEF
At this point the frustration level was getting high enough for me to be a bit reckless... I copied "itsmagic" into /data made it executable and ran it. No errors.
I rebooted into Recovery mode, and there I get scrambled graphics on the screen (it's the Acer logo duplicated several times with loads of tearing and distortion) and the tablet vibrates constantly.. non stop until I reboot it.
I can boot normally into the current ROM (Thor2002ro v96) so I haven't busted it completely. If I try to use my existing CWM manager to install any other ROM or use the manager to reboot into recovery mode, it goes back to the scrambled screen and vibrating constantly.
Does anyone have any ideas or suggestions here? I'd be happy to even roll back to stock and start fresh. There is nothing on the tablet that needs to be saved... except the functionality of the tablet itself.
When you write nothing about APX mode, does that mean literary nothing or nothing different?
If you have root you can see if you have anything interesting in /proc/cmdline.
If not I'm out of ideas on how the get the UID for now.
While i very much doubt 0x0123456789ABCDEF is the UID used to generate the SBK of the device you could try reading and decrypting the beginning of mmcblk0 using the SBK that would give (0xA9EA7E00 0xF12BEB06 0x3AD20804 0x364A5F03) to verify this.
You could probably overwrite the restore partition from your running system, I have never done that myself though.
OK, it's SOLVED.
After much swearing and crying and a little help from the forum here and in other posts the solution to fixing the broken tablet was actually quite easy.
Based on the information here:
http://forum.xda-developers.com/showthread.php?t=1459821
- I downloaded recovery-ra-iconia-3.16-gnm.img using teh links provided on the thread above
- I ran itsmagic
- Then I did these steps:
Code:
adb push recovery-ra-iconia-3.16-gnm.img /mnt/sdcard
adb shell
su
dd if=/mnt/sdcard/recovery-ra-iconia-3.16-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
This booted a working recovery mode (FINALLY), and I was able to successfully flash the latest Thor2002ro ICS ROM.
Thanks for your help and suggestions eppeP, they got me thinking in the right direction.
Hello guys I am trying to bypass screen lock via adb but when I write adb devices it shows "0123456789ABCDEF Device" and then when I type adb shell then it shows"$" after that whatever I type it shows permission denied(even if I write adb).Please Help
please clear up Google
account lock