yashsingh1/xdaforums huggingface dataset:
[Droid 2 Android Development] facelessuser:
I am starting to think the ERROR6 is not what I thought it was. Anyone who is getting ERROR6, right after you get ERROR6 please contact me (don't restart your phone, don't run the script again). I want you to run a new script to see if I can log the actual failure so I can get rid of it.
[Droid 2 Android Development] patchm00:
Hey Dark, Just a quick update. Last night my battery ran out in the middle of flashing with Linux (it was going well too) but had to quit. This AM I found someone with a Droid and borrowed their battery. I start up the phone and it goes right to Bootloader and says: Code Corrupt/Battery OK/OK to Program/Transfer Mode: USB

I tried the Linux flash first and it downloads the first part, says ramloader stuff then "waiting for phone" and just stays there.

So I tried the windows sbf flash next and I load RSD Lite as admin and it says S Flash OMAP3630 MI connected (which i thought was supposed to say A955 according to instructions but a video showed same as mine).

I point to the sbf file but Start is greyed out

Any suggestions?
[Droid 2 Android Development] mstras:
Hey guys i know you are super busy with perfecting the root. facelessuser and darkonion ty so much again for getting this out the door. You guys are lifesavers and awesome. I was wondering however if you could post up the unroot .bat file. for unrooting by this method. All of your help is appreciated.
[Droid 2 Android Development] patchm00:
Ok, i got my phone back! WHEW. That took a while :) Final fix was to load UBUNTU on a real box (not vmware) and then it ran the sbf just fine and all is good. I'll root it again and I do have backup so I'll try that but I think I'll wait for more news on that new leaked patch before trying that again!

Thanks for all your help(s)
[Droid 2 Android Development] facelessuser:
Right now it is only in mac and Linux.

./doroot.sh unroot

I haven't written it for windows yet. I've been trying to figure out this ERROR6 issue with the script. I can't reproduce it, and I am trying to find someone who is having this issue. I am also trying to to fix the exploit hang issue (I may have fixed it with the latest script).

As soon as I address these issues, or this weekend (whichever comes first), I will write the unroot portion. I am trying to minimize how many people I need to help who have legitimate issues. Less issues means I have time for adding stuff. But soon, it will come soon, I won't forget.
[Droid 2 Android Development] patchm00:
Hey, just some info,

I ran the one-step on Linux box (this time NOT a vmware) and first time failed, say yes to retry and I chose yes and it worked.

For your reference :)
[Droid 2 Android Development] facelessuser:
That's fine. It's the exploit not the script failing. You just have to run it until the exploit succeeds. I didn't write the exploit, just the script.
[Droid 2 Android Development] Shortyspitfire:
Everytime i run the two click method or one click method it says adb not recognized as an internal or external command as soon as i begin to run doroot.bat. Any help would be appreciated.
[Droid 2 Android Development] facelessuser:
Did you copy the files to your SDK/tools folder. (Not the folder in the zip, just the files; I am going to take that folder out of the zips in the future)
[Droid 2 Android Development] HellomotoX:
ERROR6

Here is the error readout from my MotoX. I am running Windows Vista 32bit.
[Droid 2 Android Development] facelessuser:
Hang tight. I got someone to run a special script to get some debug info. I know what the problem is. I need to find a work around. If you are game to test a possible fix, PM me.
[Droid 2 Android Development] facelessuser:
Anyone who has had the ERROR6 error.

When you got the ERROR6 using this one click script, was this the first time you ever rooted your phone, or did you successfully root it once before you got the ERROR6?
[Droid 2 Android Development] facelessuser:
All right peeps. ERROR6 is becoming less and less of a mystery. I think I know what is up. But I am going to confirm with a couple more people.
[Droid 2 Android Development] facelessuser:
ERROR6 uncovered

I was half right. I am having an issue copying system files. Under any normal circumstance, this is not an issue. But those with ERROR6 are not normal.

This means you lost root somewhere along the way, but wanted to try my easy way. But your phone still had remnants of your last root. Specifically busybox. Busybox was still there and probably had permissions to execute. So when I tried to copy over him, I couldn't because he was still being used. I couldn't even force copy over him because he was actively being called or doing something.

1. Now, I can do a couple of things. I can look for the PID and try to kill busybox and copy over him.

2. Keep trying until it's not busy and copy over him.

3. Or (and this is my favorite) see if he is there, and if so, ignore the copy step. I can still try and chmod him; though I suspect if he is busy, I don't need to.

I will work on implementing this fix and will update you when I have it going.
[Droid 2 Android Development] Shortyspitfire:
Yeah I tried that. It ran through and said exploit failed. I said yes to retry and now it seems to be stuck on the adb connection will be reset. restart adb server on desktop and re-login.
[Droid 2 Android Development] facelessuser:
When you say stuck. Did you wait 5 minutes at that point?

And when did you download the version of the scripts you are using?

In the latest version I have a new kill method if it goes on longer than 5 minutes.
[Droid 2 Android Development] darkonion:
That should be okay. Exploit can take awhile. Keep letting it run.
[Droid 2 Android Development] Shortyspitfire:
Yeah I waited closer to 15 minutes. I just downloaded the scripts today and i did kill it. I disconnected my phone from computer after it was killed. Now phone is not registering a usb connection on my pc at all.
[Droid 2 Android Development] facelessuser:
Reboot. I think the exploit killed adbd on the phone, but it didn't respawn as root.
[Droid 2 Android Development] pinhead875:
DX user here on 2.2OTA - did not work first time, but did work 2nd time. Thanks!
[Droid 2 Android Development] Shortyspitfire:
I rebooted. Still not registering a usb connection.
[Droid 2 Android Development] facelessuser:
Turn off. Let sit. Turn on. Try again.

Are you on Charge Only or what?

It is either an issue server side or client side. If that doesn't work, from command line adb kill-server and then adb start-server; you must be in the tools folder on command line. If you don't know how to do that, restart your computer.
[Droid 2 Android Development] facelessuser:
I sent out some test scripts to some lab rats. Waiting for an update from them on the ERROR6 fix.
[Droid 2 Android Development] Shortyspitfire:
I am in charge only because i can not see the usb debugging icon in the notificaitons bar during pc mode. I restarted my computer and ran the script again. It said root successful with no errors but did not actually root my phone.
[Droid 2 Android Development] facelessuser:
Is it saying things like "adb not found" or "adb is not a command"? The only way it goes through and gives a false positive is if adb does not exist.
[Droid 2 Android Development] Shortyspitfire:
No. It didn't say anything like that. It took about five minute to reset adb then it ran the script.
[Droid 2 Android Development] facelessuser:
How do you know you don't have root.

Reboot your phone, and type in su in a terminal emulator from the market. And see if you have root. You may not have busybox, but you should have root.
[Droid 2 Android Development] phwlee:
This is my first rooting experience. I have followed this thread for a few days and it sounds pretty straight forward. For this latest (Version 2.0) do you still have to extract and update or is it a simple one click? And there is no option to unroot at this time is there? And once I am rooted, how does the updating work? obviously no more OTA updates. Thanks in advance.
[Droid 2 Android Development] facelessuser:
What do you mean extract and update?

It should be a simple one click if you have adb installed and moto drivers. Make sure debugging is enabled as well and that you are in Charge only mode if on Windows or Mac.

Drop the 5 files in your SDK tools folder (not the doroot folder, just the files). Click the bat, cross your fingers.
[Droid 2 Android Development] Shortyspitfire:
You were right, i do in fact have root. Thank you for the scripts & for taking the time to help out an android newbie :)
[Droid 2 Android Development] facelessuser:
No problem. I know my code will enough to know that if it said you had root, you had root.
[Droid 2 Android Development] darkonion:
Well, no matter what the case is, you still have to "extract" adb (android-sdk). Whether you need to update it or not is debatable. I would update it. Though i don't think it is totally necessary.
[Droid 2 Android Development] Shortyspitfire:
How can I tell if my droid is deodexed or odexed
[Droid 2 Android Development] facelessuser:
Well if you deodexed, then it is deodexed. Or if you installed a deodexed rom, you are. If you really need to know, download a file manager from the market and browse to /system/app if you see the odex files, you are not deodexed.
[Droid 2 Android Development] phwlee:
Yes! I am rooted! Thanks for all your help. I downloaded wireless tether and it works, so I know I have root. Keep up the good work!

For your knowledge... No problems during the rooting process. No errors either. The whole process took less than 3 minutes.
[Droid 2 Android Development] oo7above:
ERROR 06

Did you find a fix yet for the Error 06? And yes I had my phone rooted prior to the 2.2 update via easyroot, if this helps... Thank you for everything!!!
[Droid 2 Android Development] facelessuser:
Yes I just got a fix working. Due to the limitation of batch files I was running in circles, and then I figured out how to do it. It will be 100x easier in Linux and Mac. But my fix right now is only for windows. I will post give it to darkonion in the hour.
[Droid 2 Android Development] oo7above:
Ok cool... will u let me know in this thread? Thanks for reply, and I can use mac or pc...
[Droid 2 Android Development] facelessuser:
I sent darkonion the ERROR6 fix. Windows 2.1 will be up when he posts it.

To those who were patient and willing to test my attempts to fix it, check your inbox.

I need to go work out now.
[Droid 2 Android Development] graveghoul:
If i didnt do these steps but still have root, is that ok?

"5. Follow the instructions. You will enter into the shell and be prompted with a $.

6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes before it boots you out.

6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthecage again by entering the command from step six.

6b. If you see the #, exit the shell by typing exit.

7. After being booted from shell and back to DOS, enter or double click doroot2.bat"
[Droid 2 Android Development] sovrce:
I've gotten as far as:

Checking for devices. . .

*daemon not running. starting it now on port 5037

*daemon started successfully

_

And that bottom cursor just flashes for 10, 15, 20 minutes until I close the program. Is it even rooting right now? Or just "connected"/seen? For what it's worth, I already have su, SuperUser.apk, busybox etc on my phone from the 2.1 root, I just can't run any apps that require SU permission. Any ideas?

I should also add that whenever I plug my X into my computer it pops up with the 'Install New Hardware' prompt and even after it finds 'Motorola ADB Interface', it will still say that it failed to properly install the hardware. I've tried all the methods I can find to install the right drivers but when I go to device manager it still shows a question mark even though it also displays 'Motorola ADB Interface' under 'Other devices'....?? Any help?
[Droid 2 Android Development] facelessuser:
I posted the ERROR6 fix on darkonion's server. 2.1 should be available for download. darkonion will update the changelog later.
[Droid 2 Android Development] facelessuser:
You have root? Did you do the one click? If you did the one click, there is no need for all of that doroot2 or doroot3 stuff. I changed the process into one script that does it on autopilot. That is unless you download the old 3 part method.
[Droid 2 Android Development] facelessuser:
I posted after you, so you may need to download the one click again for the ERROR6 fix. Since you already have busybox, I had to patch the script to ignore busybox if you already have it, or it would fail with an error.

Put your phone in Charge Only for windows. Try again. The exploit is finicky, so if it doesn't work the first time, try it again.

I put check in their to skip the exploit if it worked the first time and your phone didn't reconnect, so it is safe to run it until you get the congrats message at the end.
[Droid 2 Android Development] sovrce:
The link in the second post still says 2.0... is that the right version?
[Droid 2 Android Development] facelessuser:
I only have access to darkonion's server. I can't change his post. He will change it later.
[Droid 2 Android Development] sovrce:
Oh OK. Thank you.
[Droid 2 Android Development] CharlesBeebe:
I keep getting the ERROR 05, right after it attempts to copy the su file. I have tried it on both, the USB MS, and charge mode. I am on Mac.

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 1150

[*] 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...

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

* daemon started successfully *

Checking for devices...

List of devices attached

015A7A370B01A01C	device

Remounting system as RW

Copying files to system.

-->Superuser.apk

-->Copying su

ERROR 05: Failed to copy system files.

Rooting failed.

Enter exit once to exit terminal.
[Droid 2 Android Development] facelessuser:
Sounds similar to the Error6 issue. Are you already rooted?

I will look at the code tomorrow and let you know what I think.

If I can't copy over su, then it means it is being used. It can't be used unless it is executable. Makes me think you are rooted. But let me look at the code.
[Droid 2 Android Development] Itaintrite:
How do you tell if the phone's rooted already? I ran the regular script and everything SEEMED fine and closed by itself. But nothing on the phone. Tried installing superuser from market but unsuccessful.
[Droid 2 Android Development] darkonion:
Don't need to install Superuser. Try downloading Wireless Tether and see if that works.
[Droid 2 Android Development] oo7above:
Can you check the new Window 2.1 update... I seems to be getting an extracting error after I download and try to unzip the package... I have tried on a windows and a mac..,

Thank you
[Droid 2 Android Development] 1320ms:
Also getting errors extracting busybox

Any word on the unroot for windows?

Thanks

Matt
[Droid 2 Android Development] facelessuser:
Weird, something screwy going on. Before I upload it, it is fine. After I re-upload it, it is corrupted.

Edit: It appears fixed now
[Droid 2 Android Development] facelessuser:
Okay, it is not corrupted on the server.

Edit: No longer corrupted on server.
[Droid 2 Android Development] oo7above:
Can u pm me the ftp file address? Or I can wait on the forum post to be updated...
[Droid 2 Android Development] facelessuser:
Sorry, not my server. Ftp access is for us to manage uploads etc. You will need to wait for darkonion to make that call or to fix whatever the issue is on his end.
[Droid 2 Android Development] HellomotoX:
I would just like to thank @Facelessuser for all his work on this. DroidX running 2.2 rooted now. New 2.1 worked flawless. Thanks again from one of your lab rats. lol
[Droid 2 Android Development] oo7above:
That's cool and yes I second all the hard work that has went on... amazing!
[Droid 2 Android Development] facelessuser:
We will get the link thing sorted out, I don't know when, but keep an eye out. We have day jobs, so when we get a chance we will clear it up.

Heads up.

Plans for this weekend:

Windows 2.1.1

-Better error resolution and handling in certain parts of the code

-Probably some cleanup

-unroot

Mac and Linux will jump to 2.1.1 as well

-Refine the unroot

-Address ERROR6

-Better error resolution and handling in certain parts of the code

-Probably some cleanup

So hang tight. We may cram some other stuff in there as well, we will just have to see.
[Droid 2 Android Development] oo7above:
The new updated file extracted and rooted without the error6... successful!!! Thanks again!
[Droid 2 Android Development] facelessuser:
Looks like the server was still serving a cache of the old corrupted version. I think it is now serving up a good version now. So download!
[Droid 2 Android Development] darkonion:
I reuploaded the file. I hope I didn't f' it up again.

-Kevin
[Droid 2 Android Development] facelessuser:
Do you know what the issue was? I re upped it this morning when people were complaining, and I could download it corruption free via ftp, but via http it was corrupted.

Was it serving up a cache of the old one still?
[Droid 2 Android Development] darkonion:
Not sure. I was able to download it via HTTP and extracted it just fine.
[Droid 2 Android Development] db306:
Quick question. I rooted using your guys method and was wondering if there was a way to unroot should I want to for some reason? Thanks
[Droid 2 Android Development] facelessuser:
Maybe its an issue from my side. Email me what FTP server you are using and version number. I will try and make sure I am compatible.
[Droid 2 Android Development] facelessuser:
patience...see post #338
[Droid 2 Android Development] darkonion:
Alrighty. I will do when I find the info.
[Droid 2 Android Development] lbp102:
ERROR 06: Failed to give proper permissions system files.

Can I get a PM too on how to fix this?
[Droid 2 Android Development] facelessuser:
What platform are you on? Windows, Mac,...
[Droid 2 Android Development] CharlesBeebe:
I was previously rooted, before I went through and installed a leaked 2.2 update called "tranquility" thats tweaked for the droidX. When i go into the busybox installer 1.17.1 is says i am rooted, but it cannot do anything that you can do with root access?
[Droid 2 Android Development] facelessuser:
What you describe sounds vague. Does it fail on install of 1.17.1 busybox? If so, it busybox is probably busy or something. You can remove the old busybox via a root file manager, then it should install just fine.

I have ran into this issue were busybox installer has a hard time installing a busybox. Though this is is more of a general root question than a script question. Or better yet this is more like a busybox installer question.
[Droid 2 Android Development] phwlee:
I just got root the other day from the one click method. Thanks. I also installed Wireless Tether and want to know if there are any time limitations regarding being wirelessly tethered. Can I stay tethered all day? (I am monitoring the temp to make sure it doesn't go hot) oh, and I have the unlimite data plan. Thanks in advance.
[Droid 2 Android Development] facelessuser:
Umm. I don't know. This question is a bit out off topic for this thread. I only use wireless tether for a little while. Like when I really need access on my laptop, and I don't have any other way, which doesn't happen too often.
[Droid 2 Android Development] darkonion:
I don't see why you couldn't. Don't know why you would want to tether all day though. That thing drains battery like no one's business.
[Droid 2 Android Development] CharlesBeebe:
When I run through the 1-click process, I get the error 05 right after the attempt to copy system files.

-

"Copying files to system.

-->Superuser.apk

-->Copying su

ERROR 05: Failed to copy system files.

Rooting failed."

I then thought it might have had something to do with the busybox installer like you had first mentioned. When I go into the busybox installer it says my phone is rooted, but then fails to install the current version of busybox. I have no idea whats going on, any help is greatly appreciated, Thanks!
[Droid 2 Android Development] darkonion:
Looks like busybox won't copy over. I think facelessuser is working on this. We talked briefly about it via email.
[Droid 2 Android Development] facelessuser:
I think he is rooted. If su is not executable and doing stuff, there is nothing stopping it from being written. He is having an issue using busybox installer. Sometimes busybox isntaller can't replace busybox; it has happened to me, and I had root.

He thinks he doesn't have root, so he is trying to reroot, but it won't work because he is probably rooted.

I believe he should follow my advice a couple posts back. Remove busybox via command line or file manager after remounting system as RW. Then try and install busybox via busybox installer.

I will add a su check during the script, but it will not fix his busybox installer issue, unless he does what I mentioned, or he gets lucky and busybox isn't doing something. I just went through this on my phone yesterday.

Even if I get the script to root him again, busybox installer sometimes has that issue.
[Droid 2 Android Development] CharlesBeebe:
I will go back and find the post on removing the busybox, and give it another shot. Ill let ya know what happens. Thanks guys
[Droid 2 Android Development] facelessuser:
Cool I will have a workaround that will get you past ERROR 5 in the future. Basically it means I will not copy su because it is already there. I hope you see what I am saying, and why I think you are rooted. If perchance su is there and permissions are screwed up, my new script should fix that.

The script was designed to root virgin phones. My unroot will return your phone to that expected state, but I am adding checks and work arounds for all you non root virgins.:)
[Droid 2 Android Development] CharlesBeebe:
Party on, you guys are great! I really appreciate your help. I will just sit tight and wait for the update that will work around the busybox/permissions issue.

I do think that this will do the trick because I never get any kind of superuser requests, nor will any "root" app besides the busybox installer recognize that im rooted.

Thanks again!
[Droid 2 Android Development] xliderider:
Thanks, this worked great on my Droid X running the 2.2 OTA update.

No problems whatsoever, worked the first time. :)
[Droid 2 Android Development] davidukfl:
downloaded version 2.1 for windows and it worked great. Had to do it in charge mode. It failed the first time cos i got a text message but then i just retried it and it went through quickly with no problems.

thanks
[Droid 2 Android Development] facelessuser:
Current links are not accurate wait until you here a post from either darkonion or me saying it is cleared up. The downloads lead to old versions. This occured after XDA's crash last night. We will fix the post when we have time.

Windows 2.1.2 with unroot is coming soon.

Linux and Mac 2.1.2 with full unroot coming soon. (right now it only unroots bootstrapped roms, and people that have not rebooted after initial root.)
[Droid 2 Android Development] darkonion:
My bad. The link to Mac/Linux is now 2.1.1.
[Droid 2 Android Development] darkonion:
Just uploaded 2.1.2 and an updated adb install script.
[Droid 2 Android Development] db306:
Does this version include the process to unroot? Thanks.