[How To] One-Click Root Your Droid X [Official 2.2 OTA]
- Thread starter doctorlove316
- Start date
ok i did all that , black window says im rooted now , i just restarted the phone and now what all looks the same...
Whenever I tried to download this file I got warning message from my virus scanner " exploit.linux.lotoor.q". I tried other program and got same error messages. Is it ok install this program?
ambrodsky
Well-known member
- Jul 11, 2010
- 63
- 0
- 0
Trying to root for the first time. Used to install new OSs on my Blackberry all the time. Not a novice. Followed steps listed to a tee, and it won't work. Here's the error I'm getting. Thoughts? And thanks in advance for your help!
Welcome to DarkOnion Root
Presented by: darkonion and facelessuser
Special thanks to: Sebastian Krahmer at C skills
If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled, and you are set to PC
mode
Checking for devices...
List of devices attached
015A7A370900901D device
Transfering payload.
-->Superuser.apk
168 KB/s (27688 bytes in 0.160s)
-->su
2563 KB/s (26248 bytes in 0.010s)
-->busybox
1516 KB/s (1926944 bytes in 1.241s)
-->rageagainstthecage-arm5.bin
5 KB/s (5392 bytes in 1.000s)
We will begin to apply the tears of 1000 unicorns to root your phone.
This could take as long as 5 minutes. Please be patient...
10 seconds.
5 seconds.
4
3
2
1
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3815, 3815}
[*] Searching for adb ...
[-] Cannot find adb: No such file or directory
Welcome to DarkOnion Root
Presented by: darkonion and facelessuser
Special thanks to: Sebastian Krahmer at C skills
If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled, and you are set to PC
mode
Checking for devices...
List of devices attached
015A7A370900901D device
Transfering payload.
-->Superuser.apk
168 KB/s (27688 bytes in 0.160s)
-->su
2563 KB/s (26248 bytes in 0.010s)
-->busybox
1516 KB/s (1926944 bytes in 1.241s)
-->rageagainstthecage-arm5.bin
5 KB/s (5392 bytes in 1.000s)
We will begin to apply the tears of 1000 unicorns to root your phone.
This could take as long as 5 minutes. Please be patient...
10 seconds.
5 seconds.
4
3
2
1
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3815, 3815}
[*] Searching for adb ...
[-] Cannot find adb: No such file or directory
OK... New to Android, but am usually quite tech savvy... having a bit of a problem. Installed the SDK and the drivers from the links, but I don't seem to have ADB as an available program (can't seem to find adb.exe anywhere on my HD either... nor online unfortunately)... here's what I get...
'adb' is not recognized as an internal or external command, operable program or batch file.
Any suggestions? Followed instructions to the letter and can't seem to get this working...
'adb' is not recognized as an internal or external command, operable program or batch file.
Any suggestions? Followed instructions to the letter and can't seem to get this working...
after i click doroot the cmd prompt just says could not find the file specified for each action, then says your phone should now be rooted. i installed adk and jdk so i have no idea whats wrong. help!
Well I ran the .bat file, and it went smoothly until the actual exploit. When the adb connection reset, Windows 7 detected it as a USB Mass Storage device (in devmgr). It hung on "Checking for device...", so I rebooted the phone, and it changed back to an adb connection. The exploit found the device, but then told me the exploit had failed and asked if I wanted to try again. I went through this process 3 more times to no avail.
Any suggestions?
*Many* thanks,
Matt
*EDIT:
I fixed it to stay as an adb connection, but when the adb server resets, devmgr recognizes it, but the adb doesn't.
Any suggestions?
*Many* thanks,
Matt
*EDIT:
I fixed it to stay as an adb connection, but when the adb server resets, devmgr recognizes it, but the adb doesn't.
Last edited:
boweveljoe
Member
- Jul 31, 2010
- 16
- 0
- 0
What do I do when it says adb is not a recognized internal or external command? I have downloaded the motorola drivers and updated them, I have downloaded all of the android developer kit etc and I have unzipped the 5 files into the android sdk/tools folder on my C: drive...what am I doing wrong? This is driving me crazy :-(
yeah i'm at the same place it seems as these last few posts. rolls through and applies "1000 tears of a unicorn..." resets adb connection but when it tries coming back up with daemon started successfully, it sits and waits at Checking for device...
the Device Manager on the win7 64bit laptop doesnt show it any more in Devices either...it does initially but goes away on that 2nd search i've described above.
the Device Manager on the win7 64bit laptop doesnt show it any more in Devices either...it does initially but goes away on that 2nd search i've described above.
Please forgive me for what I think is a really dumb question, but what does "Install Motorola Drivers" mean? Install them from where? Is this in the SDK, or onto my computer generally? In either case, where do I get them?
http://forum.androidcentral.com/mot...0-how-root-your-droid-x-official-2-2-ota.html
It's found in that post there...first post I believe.
It's found in that post there...first post I believe.
Please help. . .error
I am trying to run the linux version but I keep getting the following error
./doroot.sh: 499: ./adb: not found
I am trying to run the linux version but I keep getting the following error
./doroot.sh: 499: ./adb: not found
Nevermind, I figured it out.
I just copied adb from ~/android-sdk-linux/platform-tools to ~android-sdk-linux/tools
No matter what I do, I continue to get 'adb' is not recognized as an internal or external command, operable program or batch file' on everything. I'm not quite sure why...I keep following the directions step by step and the same thing happens constantly. I even tried RootMyX2 and it still fails saying that the phone isn't detected...or it just fails after being stuck on "waiting for device." I rooted my Samsung Fascinate with no problem earlier...so I'm beginning to think this is just a Motorola thing.
Any ideas or answers?
Any ideas or answers?
@Untouchable
What this means is that the script 'adb' isn't in your path of execution. What OS are you running?
What this means is that the script 'adb' isn't in your path of execution. What OS are you running?
Similar threads
Facebook
Twitter
Instagram