yashsingh1/xdaforums huggingface dataset:
[Droid 2 Android Development] enzojrc:
nah no offense taken, as far as I am concerned you are among the Jedi and I am Jar jar binks when it comes to android stuff lol

On a side note RSDlite registers that my device is connected....
[Droid 2 Android Development] darkonion:
Hmmm. Alrighty. So we are eliminating things... ADB is unhappy. And/or the phone is unhappy or unhappy with ADB.
[Droid 2 Android Development] enzojrc:
should I reinstall ADB?
[Droid 2 Android Development] enzojrc:
ugh I am about to give up I can't understand how I @$##ed this thing up......this is all a bad joke connected to that damn SBF file I downloaded from MDW.....

to reiterate step by step:

I data wiped and cache wiped.

I did a factory reset.

I tried the OTA update.

It failed.

I downloaded the 2.3 from MDW

I flashed it with RSDlite

It completed fine.

Realized I didn't unroot before I did it

I tried to Flash 2.2 back

Failed

Spent 3 hours stressing over bootloader, flashing several times from 2.2 to 2.3

Flashed 2.3 back on.

RSDLite sees my device

The computer sees my device in USB and PC mode with debugging on

Superoneclick, DoRoot and TDR stuck on waiting for device

I am stuck with a stock POS....anyone want to trade? lol
[Droid 2 Android Development] snakernetb:
Can't re-root either

I did some how get it to unroot. But to save my life I can not get the thing to re-root. I am not sure why, I have a sneaking suspicion that it has some thing to do with ADB. I will keep you posted on progress.
[Droid 2 Android Development] biotech88:
I rooted my Droid 2 with this method before it was automated. I updated this morning to 2.3.20.A995 and now none of my apps that require root work. Any ideas, do I need to redo the root, will it work with my new update?
[Droid 2 Android Development] backwardsone:
I ran dounroot to avoid any problems with the 2.3.20 update. Ran the update and saw that it worked. The kernel revision was the same, so I thought to run doroot again and it worked without issue. (Don't forget to enable USB Debugging)
[Droid 2 Android Development] snakernetb:
Re-rooted 2.3.20: A success story!

Well, apparently I wasn't letting the script run long enough. That or I have something terribly misconfigured on my main laptop. I just hooked up my D2 to my netbook turned on the hotspot plugged it in and left the script running over lunch. I came back and the script reported a successful rooting! I opened a terminal emulator up and su'd right over. Thanks to everyone and I really appreciate all the help.
[Droid 2 Android Development] facelessuser:
Glad it worked. It can take a while for the exploit to work. Usually people give up if it isn't immediate. I usually let it go for about 5 min before I give up, and if it does fail, usually a reboot of the phone and a 2nd attempt does it.
[Droid 2 Android Development] enzojrc:
maybe that is my problem too, I am being very impatient! lol

I will hook it up and walk away tonight and check it later!

Thanks again for all of you putting up with our mistakes! :)
[Droid 2 Android Development] enzojrc:
did you leave it at waiting for device? Or did it start with the rooting script?
[Droid 2 Android Development] snakernetb:
Instant gratification

As a sysadmin I should know better and to just let the script so the heavy lifting. But as part the of microwave mentality generation X, I want my root NOW! Thanks for putting together such a great set of scripts! The levity during the different steps almost made me fall out of my chair. "The tears of 1000 unicorns" part tore me up... :)
[Droid 2 Android Development] enzojrc:
:D....so I tried it on my moms laptop....WORKED LIKE A MOTHA LOVIN CHARM!!!!!

Facelessuser, Darkonion and Snakernetb....YOU ARE AWESOME!!!

Faceless and Onion for the app...Snaker for the idea to use a different laptop!!!

I IS ROOTED!:D
[Droid 2 Android Development] kurtle:
It appears that the script worked. I have the # prompt in adb shell which I think it means I have root. But when I launch su on the shell, I don't get a prompt for anything on my phone and I also launch root only apps and they fail. Just updated to 2.3.20 from Verizon.
[Droid 2 Android Development] darkonion:
Try unrooting and rooting again.
[Droid 2 Android Development] kurtle:
Ran unroot.bat

been haning on

[*] adb connection will be reset. restart adb server on desktop and re-login.

for about 15 minutes

EDIT: Ran it again. Unrooted just fine. Ran Root. Rooted fine now. Thanks man.
[Droid 2 Android Development] darkonion:
Yeah. I need to spend some time and put new and updated directions into the first post. Just been busy with school.

For all you guys, check out my new website. Been working on a page for hosting the DO stuff, and a way for people to buy my ChickMagnet Tshirt. Hahaha. www.kimete.com
[Droid 2 Android Development] stanleyg:
Updating Rooted Droid

Thanks to a step by step walkthrough from facelessuser, I was able to root my droid about a month ago. I have been loving it, particularly my new wifi tethering capability. A few days ago, I got a message saying that an update was available for my currently running Froyo 2.2. I am unable to go through with this update because my phone is rooted, and am wondering how I would go about that. Alternatively, if the update is too difficult and would result in very little improvement, then I would love to know how to get rid of the frequent messages that an update is available.

I hope someone can help me out with this, I would love to update my phone, and just don't know how!
[Droid 2 Android Development] PWOB:
Noob rooting issues

Im on DX 2.2 with using a macbook. I've got dorootv3.sh and i've tried about 6 times now to root this thing to no avail.

List of what i have done

1st time through:

no debug icon

in pc mode

stuck at the first "Checking for devices...

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

* daemon started successfully *"

2nd time through:

reset phone and pulled battery

left in pc mode

still no debug icon

hung up in the same place "checking for devices" left it to run for over 10 minutes

3rd time through:

full phone restart

switched to mass storage

debug icon appears

ran through whole process until the second checking for devices

same as round 2 left to run for over 10 minutes

closed terminal and started over

4th same as above, 5th same

6th time:

rather than selecting full install (option 1) i selected option 2

hung up at the second checking devices

every run through except for the 6th time i selected the full instal and when prompted in terminal i selected yes to replace files

I don't have sdk, i've restarted while connected to the usb and not connected.

Im trying to be thorough in providing what i have and haven't done because i dont know what make a difference or not. Any help would be great, it seems like i must be close not sure at all what i'm dong wrong.
[Droid 2 Android Development] PWOB:
so after all of that i just wrote i ran one more time and it worked.

The one thing i did differently was switch to charge only rather than mass storage. The only thing i noticed that did change from that was my computer did not get pissed during the reset telling me about properly disconnecting usb devices.
[Droid 2 Android Development] troy2001dwg:
everytime i try to open do root

i d/l the do root files both sets and both are infected or are being detected by kaspersky as infected by trojans??? and both zips will not open says invalid files:confused:
[Droid 2 Android Development] facelessuser:
We already covered why antivirus goes off. Searching this thread will help you find answers faster.

The script HACKS an EXPLOIT on your phone, so it triggers antivirus because of its methods, but it is safe to use, because you want it to exploit your phone. You want it to do what antivirus is warning you about.
[Droid 2 Android Development] lukesdiesel:
Took my D2 back to stock last night and got the 2.3.20 OTA update. This morning I used this program to Re-Root my D2. The first time I tried to UNzip the DoRoot file it said it was empty. I re-downloaded the DoRoot and it worked Perfect. Thanks guys you ROCK!!!!

Luke
[Droid 2 Android Development] uncensy:
rooting after 2.3.20 OTA fails...

Here is something that may help people that [possibly] had the same problem as me.

I was rooted when I updated to 2.3.20 and it took away root, obviously.

When I went to unroot, it said it was successful but when I checked my phone it still had superuser on it. So I tried to root anyway...

It failed, failed, failed! Tried to unroot again. Fail. Rinse, repeat. Nothing worked.

So then I remembered I put the newest superuser on a while back. So I went on my phone, un-installed superuser, tried to root... YAYZ! It worked.

I don't know if this was really the reason rooting was successful, but I do know that after many failed attempts, right after un-installing superuser it worked on the first try.

If anyone has any ideas on this, please share!

Hope this helps anyone that may be wondering wtf is going on.
[Droid 2 Android Development] firebrain:
Droid 2 Global?

Does this method work with the Droid 2 Global released today?

Also is this root a full root? or just a userland one?

Been out of the Android game for a while so please forgive me for my lack of knowledge.
[Droid 2 Android Development] darkonion:
Not sure about Droid 2 Global. Someone try it and let us know.
[Droid 2 Android Development] :
Script worked out like a charm. Had to try a few times because it didn't work for me in "PC Mode"...once I switched to "Charge Only" it worked great. The comment about "that Steve Job OS" was hilarious. :p Thanks for the great work. :)

I'm new to "Droid 2 development" and noticed that the clockworkMod works a little bit different than how it works on my Incredible (currently running Ruby). I noticed that I have to run the "Bootstrap" options every time before I boot into recovery. Is this normal? For example, I did it one time in order to backup my data right after rooting. Then I booted again normally and went through the app switch back to recovery without the bootstrap option. When I mount system and data to move unwanted apps I couldn't get adb shell to detect my phone. It wasn't until I bootstrapped again when it finally let me use the adb commands. Is this normal?
[Droid 2 Android Development] darkonion:
Not exactly sure how it works, but this is what I understand. The Kernel to the Droid 2 is locked, so in order to get into the recovery mode, you have to work around it. Hence the Koush Bootstrapper. Yeah...

Glad the script worked for you.
[Droid 2 Android Development] :
I apologize if I misunderstood the above post, but it seems you don't use Koush's Bootstrapper. Is there another alternative? Just curious. :)
[Droid 2 Android Development] facelessuser:
You only have to bootstrap once and then you just select reboot recovery every time after that. Even after reboot, you should still be bootstrapped.

You only need to bootstrap again if you flash a rom or something that upsets the bootstrap.
[Droid 2 Android Development] :
Cool!!! Thanks, that clears things up. I guess since I've flash so many ROMs on my Dinc I've been brainwashed into how clockworkmod should work :)
[Droid 2 Android Development] darkonion:
Koush Boostrapper includes Clockwork Recovery Mod something. :P
[Droid 2 Android Development] burntgti:
I am using a Macbook Pro and I am stuck on "Checking for devices..." However my DX is connected because I am looking at the Drive labled "Droid X" on my desktop. Please help!!
[Droid 2 Android Development] darkonion:
Put your phone into PC Mode or into Charge Only or toggle between the two until the script continues. You may also try enable or disabling usb debugging or unplugging, then plugging in your phone again. Just try fumbling with it until it goes.
[Droid 2 Android Development] Liepo:
No go on the new Droid 2 Global.. fails everytime. :-/

FYI, the System Version is listed as Version.2.4.29.A956.Verizon.en.US
[Droid 2 Android Development] facelessuser:
What error do you get. I don't see a reason why it shouldn't work. Try rebooting your phone and try again. The exploit isn't really phone specific, not unless have a different security on the phone, but the exploit should work on Froyo. I don't have a global to test on, so I really can't guarantee it will work until someone proves it so.
[Droid 2 Android Development] Liepo:
It just says "Root failed. Do you want to try to run the exploit again (y/n)?".. I've run it many times now..
[Droid 2 Android Development] facelessuser:
Rooting is finicky. Sometimes it will do the same thing on a supported phone. What it means, is that it is having a difficult time forcing adbd to die and return with root. The fact that it is getting that far is a good sign. It means we are able to push the files and execute them on your phone. That is why I suggested rebooting your phone, sometimes that helps. Also, make sure you have debugging enabled, but if it is getting that far, it is probably okay.

I understand if you are frustrated, the process isn't always 100% every time. You can try again, or stop trying. I completely understand either way, since we can not guarantee it will be fruitful.
[Droid 2 Android Development] Liepo:
Oh, no.. I'm all about getting this to work. I've been manually doing the steps.. what I'm reading is that I should expect a # instead of a $ after reconnecting to the phone once rageagainstthecage-arm5.bin is run? That isn't happening.. when I try the mount command, I get Operation not permitted.
[Droid 2 Android Development] facelessuser:
Yeah, mount won't work without the "#" sign. That means you have root privileges. Without that, there is no way to push su to the system.

The actual hack is relying on a security hole in Froyo's adbd. The exploit forks it to the firmware limit, which causes the system to kill it, and when it pops back up...root access. Now if it isn't getting killed properly, you will never get root.

The question is, does this exploit still work on the Global. The problem is, people have the issues you describe even on Droid 2 and Droid X where it is known to work, so it is hard to say if the exploit works or not looking at one users experience. I guess once more people try it, we will have enough data to make a valid assessment as to if it works or not..

The good news is, you can't really hurt your phone using this exploit, it will either work, or it won't.
[Droid 2 Android Development] jy3ng4:
Hey brahs, I just attempted this (both the manual and one-click) on my Droid 2 Global, with no success. If anyone can figure out how to root the D2 Global I would be more than happy to donate for your effort :)
[Droid 2 Android Development] sjmena:
I re-rooted using windows and got the message on the phone, "congratulations you should now be rooted". however my apps for rooted phone do not work. rooted phone was working fine, then upgrade to 2.3.30 made rooted apps not work. One app states, "unable to get root access". another example, wireless tether wont start anymore and says "requires 'su' to access the hardware, make sure you have root access". is there a simple solution to fix this as i'm not too good with computers?
[Droid 2 Android Development] facelessuser:
Unroot, then Root. People need to stop updating without unrooting. But no worries, the script can unroot you even after update.
[Droid 2 Android Development] facelessuser:
I read an article today that points that the exploit still works on Global.

http://androidcommunity.com/still-t...bal-already-bootstrapped-and-rooted-20101111/

So, this should work; try rebooting your phone and try again, or try another method if you prefer. On phone method, SuperOneClick, and this all use the exact same exploit. The hack works on Froyo, so it should work on the Global. It doesn't always work the 1st, 2nd, or 3rd time. This is an issue with how the hack works. Don't give up, it eventually works. Rebooting the phone and then trying might help you. Also, make sure you have debugging enabled.
[Droid 2 Android Development] jy3ng4:
I don't know if this will help determine the problem, but here is where it stops for me on my Droid 2 Global (I'm too new to hyperlink, sorry):

img826.imageshack.us/img826/1632/77221410.jpg

It was already mentioned but the D2 Global is on firmware 2.4.29
[Droid 2 Android Development] facelessuser:
No big deal. This is a common issue. When you get stuck there, try unplugging your phone and replugging it. Or, alternatively, you can switch USB mode to something and switch back.

What that means is, adb is having an issue reconnecting to your phone after doing the exploit. By disconnecting and reconnecting, adb will probably see your phone again, and finish the process.
[Droid 2 Android Development] jy3ng4:
Thanks bro, I'll keep trying
[Droid 2 Android Development] Liepo:
Got my Droid 2 Global rooted following this guide using a terminal emulator on my droid!

But I guess I'm disallowed from posting the link to the guide..
[Droid 2 Android Development] facelessuser:
The link I posted a couple of posts back leads back to what you are talking about. It uses the same exploit this script uses. Either way, glad you got rooted.
[Droid 2 Android Development] sjmena:
thank you so much. any specific link you recommend with downloads for unrooting my droid 2.3.20, much appreciated.

donation is in order, thanks for your assitance.
[Droid 2 Android Development] facelessuser:
yeah, download the doroot script on the opening page.

If you just run it with the unroot parameter:

Windows: doroot.bat unroot

Linux/Mac: ./doroot.sh unroot

If you are using darkonion's wrapper script, then I think there is an option for unrooting in the menu.
[Droid 2 Android Development] phwlee:
I think their latest one click version has an unroot option as well. I saw it there when I opened the script.
[Droid 2 Android Development] jy3ng4:
I also managed to get my D2 Global rooted using the manual method via terminal emulator. All the one-click/script methods were giving me issues. It'd be nice to get a one-click root option at some point though because typing in all that stuff manually into terminal emulator is just so tedious
[Droid 2 Android Development] darkonion:
Can you elaborate what type of issues you were coming across? All the script does is pass commands to the phone and tells it to run the commands you are doing in the on phone/emulator mode.
[Droid 2 Android Development] Rennert:
Hello,

Works the script also on milestone 2?

system: Version.62.2.13.A953Blur.Vodafone.en.De

model: MotoA953

build: MS_2.2.13

kernel: 2.6.32.9-ge 506ceb

When i starts doroot2.1.4.bat the device found an copied superuser busybox su an rageagainstthecage to sdcard.

after restart adb the device not found and hangs. After reboot phone is device found. Sometimes devices after restart adb found, but root failed.

Testet on windows 7, linux and windows xp

I see that the root process also works on phone with terminal emulator. Is the rageagainstthecage-arm5.bin the same like using adb on pc?

where can i found the rageagainstthecage for use without adb?

Many thanks
[Droid 2 Android Development] darkonion:
Ah, as for the script... that's normal. Sometimes it does that. You might need to fumble with the connection settings to get it running. That's not out of the norm. Try running it multiple times. Yeah.
[Droid 2 Android Development] jy3ng4:
In the terminal emulator method, after running rageagainstthecage, you have to manually force stop and then open it up again to complete the rest of the commands...it seems that's around where the script has issues. I tried the proposed workarounds several times (rebooting, turning on/off USB debugging at certain times in the process) with no luck. I posted a screenshot a few posts up on the previous page to show where it was freezing for me
[Droid 2 Android Development] facelessuser:
The reason why your phone froze is because ADB could not find your phone; switching debugging on and off, will not help you. I gave you some advice about disconnecting and reconnecting your phone. Did you try this? This usually always works. I mean physically pull the cable out and reconnect.

I am sorry that our method didn't work, but we also give very specific instructions to help, based on our experience with the way the phone responds to certain scenarios. If you choose not to follow said instructions, I cannot promise it will work.

The way the the Global connects via ADB should be no different than any other Droid2; therefore, I expect the Global to be plagued with the same USB issues as the Droid2. All Droid2s have the potential to get stuck at the point you described for the same reasons. We kill the ADB server on your computer and restart it waiting to see your phone again, sometimes the phone doesn't register itself until the physical connection is broken and reestablished. This can be done by changing from Charge Only Mode to PC Mode etc, or by unplugging and replugging your phone. Switching debugging will probably do nothing because that action does not usually register until the phone establishes a new connection.
[Droid 2 Android Development] jy3ng4:
Ahh lol I don't remember :o Now that I'm rooted perhaps someone else with the D2 Global can try and let us know if that works?
[Droid 2 Android Development] stixaw:
I could never get droid2.sh to run but opened it and ran the commands in it manually and rooted no problem

thanks for the great initiating batch and the commands that I could easily copy and paste out of the files.:D
[Droid 2 Android Development] nylyon:
My first post :-) My Droid comes today, I have already setup the on-click Linux version on my Mac so when my phone comes I plan on clicking! One error check which you may want to include and that is the existence of the adb in the directory you're in (or to see if it's in the path). The code looks excellent and an un-root version would be handy as well (un-root before upgrades then root again?)

I do have a lingering question though. I am planning on using root for tethering. If I have any issues with my phone would just removing the 3 files installed be sufficient in un-rooting or are there other logs / traces which would need to be removed as well?
[Droid 2 Android Development] facelessuser:
Thanks. I hope it works well for you.

Checking for adb may not be a bad idea. Since the purpose of this is to make rooting as simple as possible; the more checking we do, the less questions we will we get. Granted, if adb isn't installed the whole script will already fail because the shell will return complaints when we try adb. But a nice message telling the user to install adb would be nice. I will look into it.

I have actually been thinking about doing an unroot option where the script determines if you have root, and if so will unroot you instead. I believe all that needs to be done is remove the three files...and reboot. I think the exploit only lasts as long as you have su on your phone. Basically, the exploit causes adbd to crash on your phone, and when it restarts, it happens to start as root. So then we shove on su, busybox, etc. to keep root for the user account after a reboot. I need to verify though.

Let me know if it works. I tried it multiple times and it worked flawlessly, but I only have feedback on my system. The more people who try it, the better we can make it.
[Droid 2 Android Development] facelessuser:
Timeline for one click

1. Get feedback on actual people successfully one click rooting on Linux.

2. Get working on Mac. They both run shell scripts, so this should be as easy as running the linux version on Mac.

3. Get feedback on actual people successfully one click rooting on Mac.

4. Help port this over to windows. I don't have a Windows box at my house right now...that works :(. I only have Macs and Linux boxes. I use a Windows box at work, but I should be working when I am at work ;). That is why I am saving this for the end even though most people run Windows. Sorry.

5. Add improvements like unroot, even better checking (unless we run in to problems sooner). If people are having issues with partial root, I will add special parameters to do certain phases of the rooting process and skip the stuff that has already happened.

Just a heads up for the people.