yashsingh1/xdaforums huggingface dataset:
[Droid 2 Android Development] facelessuser:
It shouldn't hang for more than 5 minutes. If it does, close the window unplug your phone and reboot your phone. Try again.

I don't think we are getting as many hangs as we used to. The exploit essentially is trying to kill adb on your phone's side, and when it does, it comes back with root privileges, which allows us to put what we need to on your phone to keep root.

If it hangs a long time ( > 5 minutes ), I always have people reboot their phone in case they have a partial root. Rebooting clears this.
[Droid 2 Android Development] briankeith513:
Should the phone reboot? And if it does? Is that the end? Well, it did reboot, but it's been sitting on the Droid Eye screen for somewhere around forever.
[Droid 2 Android Development] facelessuser:
No, I am telling you to reboot the phone. I want you to run the script again after you reboot the phone. Since the script never finished and just hung, I don't know if you have root in ADB or not.

The easiest thing for me to tell you is to reboot the phone (this clears a ADB root) and try the script again. I don't want you to run the script if you have root in ADB; that could cause your phone to crash (it will be fine, but still not desirable).
[Droid 2 Android Development] facelessuser:
Try pulling your battery. I think you must have ran the script again with partial root.

I'm going to have to put a check in for partial root.
[Droid 2 Android Development] briankeith513:
Haha, after restarting my phone, now I get the "adb is not recognized..." errors again.
[Droid 2 Android Development] facelessuser:
Your computer is possessed man. :). I mean, if it is in the same folder as adb, it should find it, if it can't find it in the same folder...it is something I would have to remote in to look at or be sitting in front of to troubleshoot. I mean, if it ran once, it should run again.:confused:

Maybe darkonion can swoop in on this one. I know he has remoted in to help others.
[Droid 2 Android Development] blustosa:
Hey all,

I just followed the steps and I keep getting the message "adb is not recognized as an internal or external command, operable program or batch file".

I tried with PC Mode, with Charge only, nothing, it keeps giving me that same message. I have updated the drivers, I followed the steps and all.

May this have anything to do with the fact I use ADW home instead of original home?

Any help is very much so appreciated.
[Droid 2 Android Development] darkonion:
Sure, I can help. I will PM you Gtalk info.

-Kevin
[Droid 2 Android Development] darkonion:
You don't have android-sdk or you didn't put the files where you are suppose to.

You need to put the files from the DoRoot zip file into the tools folder of android-sdk.
[Droid 2 Android Development] facelessuser:
Are you running the batch file from inside the SDK/tools folder? It will not be able to find it unless it is in the same folder as adb.

Or if adb is in your environmental variables, but that is a bit complicated for a lot of people. I am just trying to get the basics right now.
[Droid 2 Android Development] JohnnyConfidence:
Having a little bit of trouble curious if anyone has suggestions. I had a rooted 2.1 Droid X, did the official OTA update this morning and lost root so I'm attempting this method. I have ADB connection and USB debugging all working. The root process seems to be going fine but I get stuck with an error message here

Remounting system as RW

Copying files to system
-->Superuser.apk
-->su
-->busybox

Rooting failed.
ERROR 06: Failed to give proper permissions system files.

Enter exit once to exit terminal.

Reset everything and attempted again with the same results. Not sure what to try from here.
[Droid 2 Android Development] facelessuser:
Hmm, if it got that far, you were almost rooted. Are you on windows? I think I need to put some waits in between those steps. PM if you are on windows, mac, or linux and give me your email, I will modify the script for you to hopefully push past this for you, or if you got that far and want to finish it manually I can tell you how.
[Droid 2 Android Development] darkonion:
Or hit me up. I like to take a look.
[Droid 2 Android Development] facelessuser:
Yeah, a guy earlier never got busybox (chmod I guess), but it appeared to do everything else. I once saw myself it not remount system as RW because the media was busy. So, I think putting waits in between these steps will allow for the system to finish writing and be ready for the next step.
[Droid 2 Android Development] facelessuser:
I have a new sleepy set of scripts I am sending to darkonion.

The script will sleep for a little in between each copy and each time we set a permission. This will give the media ample time to do the next task. I would rather this take a couple seconds longer, than have issues not completing tasks.
[Droid 2 Android Development] darkonion:
Seems like Brian problem is due to the rage exploit. The exploit seems to kick him out a little fast. A little skeptical about this, I asked him to check adb shell where he got the $ prompt. Asked him to run ./rage again and that didn't help. Kicked out again, but this time, it gave a device error. Said device not connected or something. It was weird because you run adb device and the device is listed.
[Droid 2 Android Development] facelessuser:
Odd. What phone is he running this on? This is all strange...does he have the moto drivers. The phone may sorta work without them, but does he have them?
[Droid 2 Android Development] darkonion:
Uploading now!
[Droid 2 Android Development] Droopie28:
I can never get anything to work on my mac's terminal, and when i open terminal it always spits this out at me:

Last login: Wed Sep 22 13:32:52 on ttys000

-bash: sdkfolder: No such file or directory

-bash: sdkfolder: No such file or directory

Drew:~ Drew$
[Droid 2 Android Development] facelessuser:
not critical, but I am going to change the cp commands in the script in the future from "cp" to "cp -f". In case there is a failure during the copying of system files, the script may return an error if it tries to copy a file on top of the existing file.

"-f" will force the copy to occur and not return an error. This will allow people to complete the script in this rare occurrence. With the new waits in place, this may never be an issue, but I want to make sure. I just helped a guy in this scenario before I released the new scripts.
[Droid 2 Android Development] facelessuser:
You are going to have to be more specific. What do you enter to get that output?
[Droid 2 Android Development] chewybang:
That's the exact error I get
[Droid 2 Android Development] facelessuser:
When did you first try this, earlier today. And would you be willing to be a test rat for a new script? I think I know how to fix your issue.

If so, PM your email and tell me if you are Windows, Mac, or Linux.

I helped the last guy manually fix his, but I think I can get the script to correct this.
[Droid 2 Android Development] chewybang:
It took a few tries (it failed twice) but it worked! Thank you so much!
[Droid 2 Android Development] facelessuser:
Cool, then I will get this fix to darkonion tonight.
[Droid 2 Android Development] patchm00:
Hmm, I think I'm in trouble. I rooted using Linux 1 step and it worked fine. I tried to install the new leaked update 2 2..3.1.5 update because I need corporate sync without PIN and now I get stuck at the M logo on boot. I've tried battery pulls, hard reset with factory wipe/reset and nothing is working. I think maybe I did something wrong or out of order :( Where can I find something that may fix this?

thanks

EDITED: When I get to the reset screen I see E:Can't open /cache/recovery/command
[Droid 2 Android Development] matrix2004:
I also get the 'ADB' not recognized message several times but at the end it says i'm rooted. I'm confused. Win 7 64 bit
[Droid 2 Android Development] darkonion:
Hmmm. I dunno. Test if you are really rooted by installing an app that requires root. Try Wireless Tether.
[Droid 2 Android Development] terpitude71:
dumb question. i am at the step where it says "adb connection will be reset. restart adb server on desktop and re-login." how is this done?
[Droid 2 Android Development] matrix2004:
It doesn't work. Says i need root. I have a feeling the problem is with the Java SDK and where its placed and what files go where. I read all the previous posts and i don't get it. I run the .exe file then am i supposed to let it install in the default directory or where? Then after its installed, you mentioned something about a script and files. Where do i find these things and what are they called? I didn't see any 'script'.
[Droid 2 Android Development] darkonion:
Android Sdk comes in either a .zip or a .tar.gz file. You just double click the folder and what you need to do is extract (drag and drop) the whole folder to somewhere. Preferably the C:\ drive if you are on Windows or onto the desktop or your root directory if you are on Mac or Linux. From there, you run the sdk manager program. You need to update the 2.2 platform. After that, you take the DoRoot zip file, and extract the files to the tools folder which is inside the Android SDK. From there, you follow the directions on post #2.
[Droid 2 Android Development] darkonion:
You let it run. No need to do anything. If you are running the scripts from post #1, you will eventually be kicked by to the command line. If you are running the one-click version, it'll just run and finish up for you.
[Droid 2 Android Development] Macaroni86:
Wow this was super easy. I've been trying to get the hang of adb but no need! I'm still gonna read up on it and such, but I was wondering where the script pushed busybox to, /system/bin or /system/xbin? I'm guessing xbin is the place it goes but I just wanna double check as I'm new. Thanks for the great work!
[Droid 2 Android Development] patchm00:
hey Dark and sorry if you saw this but i just want to make sure you didn't miss my post on the previous page (last post). Do you know if there is anythihng I can do at this point? I'm pretty frustrated since I've tried all the usual stuff I've found serching.
[Droid 2 Android Development] Macaroni86:
Nevermind

Learned how to list whats in a directory and found it in /system/bin/. Thanks anyway!
[Droid 2 Android Development] darkonion:
Hmmm. That doesn't sound good. I haven't patched to the leaked 2.3.1.5 yet. But it sounds like you need to reflash back to 2.2 using the SBF method. What's nice is that you are on Linux/Mac which is much better than RSD Lite.

http://xdaforums.com/showthread.php?t=775913
[Droid 2 Android Development] slainte79:
error 06

I'm also experiencing this error:

Rooting failed.

ERROR 06: Failed to give proper permissions system files.

How might I be able to get ahold of an updated script, once it's ready?

Great work on this...it seems very easy!
[Droid 2 Android Development] darkonion:
Droid 2 peeps copy it to /bin/, though I've heard some Droid X peeps copy to /xbin/.
[Droid 2 Android Development] facelessuser:
Edit ........
[Droid 2 Android Development] facelessuser:
This issue is not related to root. Clean your data and cache.
[Droid 2 Android Development] facelessuser:
In a meeting. Will contact you in a bit.
[Droid 2 Android Development] JohnnyConfidence:
Just wanted to say thanks. Facelessuser got me all up and running and resolved my problem. Well beyond the call of duty. Thanks for the help!
[Droid 2 Android Development] facelessuser:
Is there a 64 bit version of ADB? Maybe that is the issue. darkonion? Do you know?
[Droid 2 Android Development] facelessuser:
Automagically. What you are seeing is the exploit running on your phone. If it works (and sometimes when it doesn't) it kicks you out back to your PC. The script then kills the adb server, waits, starts the server, waits, and then waits to see your phone.
[Droid 2 Android Development] facelessuser:
Going offline till later tonight. I will get dark onion a new script to fix ERROR6 issues somewhere in that time.
[Droid 2 Android Development] darkonion:
I don't think so, but I think from what I've heard, it doesn't matter.
[Droid 2 Android Development] matrix2004:
When i click sdk manager the window pops up for like half a second then disappears.
[Droid 2 Android Development] darkonion:
I am going to PM you my info. I am going to see if I can help you before I have to leave.
[Droid 2 Android Development] darkonion:
Updated files just posted!
[Droid 2 Android Development] anonymous-x:
Congrats making the front page & giving us something new to work with. :cool:
[Droid 2 Android Development] kdkinc:
I rooted with Linux with no real problems after a few false starts do to my errors.

When I copied the commands over to the Terminal on the last attemp the phone hung in the Terminal Konsole.

I was going to attempt again but while still connected by usb I switched from "Charge" mode to "PC" mode.

Took off like a rocket ship on the Command Konsole. ROOT SUCESS !!:):)

Maybe the mode switching may help ???

:cool::cool:
[Droid 2 Android Development] facelessuser:
Pc mode is only needed for linux. Okay, I am really going offline now.
[Droid 2 Android Development] matrix2004:
Many thanks to Darkonion....he was able to help me root DX. Had to repeat the process 3 times and it hung when it got to the Rage part.
[Droid 2 Android Development] Hashbaz:
i'm having the same error, i have as far as i can tell followed the instructions to a T. It says over and over while running " 'adb' is not recognized as an internal or external command, operable program or batch file" it goes through the process repeating this many times then says at the end "Congratulation, you should now be rooted. No Errors"

But i'm not actually rooted, programs requireing root will not work and the files for su, superuser.apk, and busybox don't copy over during the process. I can't figure out why.

EDIT: I figured out why, sort of, I had transferred the folder containing doroot.bak and such to the tools folder instead of putting the files directly into the tools folder. When i transferred the files out to the tools folder it ran without the error, but now i sit at a screen that says "adb connection will be reset. restart adb server on desktop and relogin"

How do i do that, if i click on adb.exe it only pops up for a half a second then goes away again.

EDIT2: While i wasn't looking my phone apparently rebooted, it is now stuck on the red droid eye. Pulling the battery.

Phone rebooted fine. Tried again and it got to the same line then said

"*daemon not running. starting it now on port 5037 *"

* daemon started successfully *

Checking for device...

List of devices attached

015D941A9008023 device

Root Failed. Do you want to try to run the exploit again (y/n)?
[Droid 2 Android Development] patchm00:
Hey Dark,

That's not working unfortunately. Two things, the instructions say to turn off phone plug in USB and hit the up arrow on the keyboard to get to recovery. I have not read that anywhere - #1 When I plug in my USB the phone starts the boot process without me hitting any key and #2 up arrow does nothing if I don't have the USB plugged in and just did a battery pull/replace.

Secondly, when I do get to the Android Recovery Console using "x" and the search key, I plug in the USB into my computer and nothing! I have downloaded moto drivers but even so I should get something about device not found or something right? Am I at the wrong place to get this phone recognized by the PC?

thanks
[Droid 2 Android Development] facelessuser:
You don't have to do anything. Let the script do what it needs too. If it hangs too long, you can quit the script and try again. The reboot was probably caused by the exploit (it is a hack, so it sometimes can do this; I didn't write the exploit). Just keep trying, it will eventually take.
[Droid 2 Android Development] facelessuser:
Select y
[Droid 2 Android Development] Hashbaz:
LOL that post makes me laugh :)

Out of frustration i tried it the manual 3 step way instead of the one click. Worked like a charm. I have no idea why, but whatev, i'm root now.
[Droid 2 Android Development] facelessuser:
Lol. Well I'm glad I made you laugh. Sorry we couldn't root you with the one click, but at least you're rooted.
[Droid 2 Android Development] bojangalz:
I can't seem to get anywhere with my Droid X using the 1 click method. I either completely time out at adb reset or get past that and error out after copying superuser.apk, su, and busybox... At that point I get an "ERROR 06: Failed to give proper permissions system files"

http://img831.imageshack.us/f/capturesg.png
[Droid 2 Android Development] marty1966:
Stay with it. Took me three tries.
[Droid 2 Android Development] facelessuser:
Check your PM.
[Droid 2 Android Development] DetCochese:
This is frustrating.

I OTA'd the 2.3.15 update while rooted on stock 2.1...

(I never added or deleted anything, just rooted for WiFi Tether)

When I completed the OTA update to 2.2/Froyo, I noticed my Superuser permissions were still there. I figured I was lucky and tried using WiFi Tether. All I would get was "Unable to start tethering, please try again."

I figured maybe I wasn't so lucky, so I uninstalled and re-installed WiFi Tether. After removing root permissions from the Superuser/Ninja icon for that app.

Once I reinstalled WiFi Tether, it does not attempt to get SU permissions. The ninja is still there, but no luck with Wifi Tether.

So, I attempted the root process using these steps. I tried on two computers. I let all the drivers install with and without debugging on to make sure everything had a driver. I cannot get USB Debugging to come on with PC Mode.

I tried the one click root method about twenty times, in every mode, with and without debugging on. It fails each time, although it makes the connection, transfers all of the files like it wants to work. It just says, root failed. Do you want to run the exploit again?

Will someone please help me. I'm losing it! :D
[Droid 2 Android Development] facelessuser:
OTA always kill root. You have to reroot. Oh, and another thing, you can no longer SBF with 2.1 SBF on X. Just something to know. Moto changed your bootloader, you will need a new 2.2 SBF.
[Droid 2 Android Development] DetCochese:
I tried to re-root twenty times. It will not work.

"Root exploit failed, would you like to try again?"

:(
[Droid 2 Android Development] FYASK0:
Had some difficulty achieving root with 2.2 OTA on the X.

It would run through 3/4 of the one-click on my Mac, but then gave me an "Exploit Failed" error. I was turning up empty handed from my searches for support.

The solution: change USB Mode to "USB Mass Storage" instead of "PC Mode" or "Charge Only" [as posted in the instructions].

Can't really explain the fix as I dont know too much about the whole process, but I can confirm that I was able to achieve root using this quick fix.

Hope this helps

-Drew
[Droid 2 Android Development] DetCochese:
I also tried Universal Androot v1.6.1

Unroot: Failed, you still have the power my lord.

Root: Your device is already rooted! Root again?

Yes---> "Failed! No ~~~ Fu goo ~~~"

I don't understand. Phone thinks it is still rooted. WiFi tether isn't working though.
[Droid 2 Android Development] DetCochese:
Thanks for the contribution.

I tried it with USB MSM and Charge Only and PC and Media, no luck.
[Droid 2 Android Development] facelessuser:
Are you still using the one you first rooted with, try downloading it again. It is a newer one. It may be failing on the copy since some of those files might still be there. The new one force copies over them.
[Droid 2 Android Development] DetCochese:
I'm sorry, try downloading what again?

I rooted my phone originally with the one click root app when it came out 6 weeks ago or more.

I guess I am not understanding you.
[Droid 2 Android Development] facelessuser:
darkonion doesn't put version numbers. Download the one click again, it is a newer version.
[Droid 2 Android Development] DetCochese:
I am using the newest. I downloaded 10 minutes ago.

Still no luck, I'm afraid.
[Droid 2 Android Development] facelessuser:
Where does it fail exactly and with what error code?
[Droid 2 Android Development] DetCochese:
With the one step root, using doroot, not the three step.

It fails after:

Welcome to DarkOnion Root

Presented by: darkonion and facelessuser

Special thanks to: Sebastian Krahmer at http://c-skills.blogspot.com/

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

015A48270401100A device

Transfering payload.

-->Superuser.apk

54 KB/s (27688 bytes in 0.494s)

-->su

194 KB/s (26248 bytes in 0.132s)

-->busybox

361 KB/s (1926944 bytes in 5.205s)

-->rageagainstthecage-arm5.bin

329 KB/s (5392 bytes in 0.016s)

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 ...

[+] Found adb as PID 7707

[*] Spawning children. Dont type anything and wait for reset!

[*]

[*] If you like what we are doing you can send us PayPal money to

[*] 7-4-3-C@web.de 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.

Reconnecting in 20 sec...

* server not running *

* daemon not running. starting it now *

* daemon started successfully *

Checking for device...

List of devices attached

015A48270401100A device

Root failed. Do you want to try to run the exploit again (y/n)?

Type y or n, then press ENTER:
[Droid 2 Android Development] DetCochese:
Well, this is new. I switched again to Charge only, since debugging wouldn't show up with PC Mode:

Says I was successful. I tried to copy the CMD text to paste here but it went away. Rebooting phone now. I tried wifi tether again. NOW IT WORKS after reboot.

hahahaha

These phones are fun to stress out over!

Thank you for your help guys.

Just needed to do it 100 times.
[Droid 2 Android Development] facelessuser:
Yeah, the exploit is failing. Nothing I can do there. I didn't write the exploit, just the script that applies it.
[Droid 2 Android Development] facelessuser:
The exploit is kind of a dirty hack. It is great, but not always guaranteed to work.
[Droid 2 Android Development] darkonion:
Sometimes, you just have to apply the script multiple times to get the desired effect. Going to put the new version up now!

New version will be up shortly in a few minutes!
[Droid 2 Android Development] DetCochese:
I very much appreciate your help, all the same. :)
[Droid 2 Android Development] darkonion:
Run the program again. Just ran the script on friend's DX and it works perfect. I know it's tough, but sometimes, you just need to run it a few times.

-Kevin

P.S. Hit me up on Gtalk if you need help. I will PM you my info.
[Droid 2 Android Development] DetCochese:
I will hold onto that, just in case ( I appreciate it!) but I got it working, using Charge only mode with debugging.

I tried following this:

http://blogs.computerworld.com/1701...e_android_2_2_froyo_droid_x_pc_driver_problem

...to correct the driver issue with PC mode and debugging but it wouldn't work.

Charge Only mode finally came through!

Thanks guys.
[Droid 2 Android Development] darkonion:
Cool. Yeah. As long as you have USB debugging symbol, it is good! If the script hangs for a long time, don't be afraid to close and rerun the script!
[Droid 2 Android Development] facelessuser:
I think in the future we will start releasing these with version numbers. That way we can easily track which fixes are in your current script.

Anyways, it's bed time.
[Droid 2 Android Development] darkonion:
Alrighty. We'll start with 2.0 for this latest one!

1.0 for the original multi-step roots!