yashsingh1/xdaforums huggingface dataset:
[Droid 2 Android Development] facelessuser:
That is me trying to kill rage because I am not sure if it hung or not. This was an experiment. Sometimes, when running rage (the exploit) on the phone, it never kicks back to the script. I thought maybe the process was hanging, but it turns out the process exits fine, but adb does not reset because it was not successfully killed by rage. I need to revise what I am doing.

Just run again.
[Droid 2 Android Development] Shadowlore:
Addition for Darkonion and Faceless

Just wanted to add, that if someone installs the official R2D2 Rom, and they lose root from doing so, just redoing the 1-click install will NOT restore root.

People will have to do the unroot first, and then redo the root again. Not sure why.. but here's what I noted:

Upon updating the rom to the R2D2 version (wanted to get rid of some of the network disconnection issues that are prevalent with AES encrypted wireless connections...) the device still had SU installed, and didn't see a problem with it.

However, upon trying to run su, the device would never prompt for permission, and would just hang there for 20-30seconds until it timed out and said permission denied.

Rerunning the doroot.bat (1, 2, 50x) would go through all the steps, and report that the device IS rooted.

Attempting to run any root required app (Titanium backup, wireless tether, Adfree) would kick back that it couldn't request root level access.

Rebooting the device, nor the PC made no difference at all... but forcing the device to unroot, and then doroot, seemed to fix the problem entirely.

(I've spent the last 3 hours trying to track this down, and I can reproduce it every single time)
[Droid 2 Android Development] facelessuser:
I updated to R2D2 fine and had no root issues. Usually if you root and there was remnants of a previous root, you just have to reboot after the reroot. I won't make that an all inclusive statement though; things can go wrong.

But like I said. I upgraded to R2D2 then did the procedure for super clean, I had no issues like you described. I rooted fine.

Edit: You probably lost the superuser.apk on flash, and R2D2 rom buts busybox in xbin opposed to bin like we do. I think I was aware of that and did some stuff to compensate. Hmm. Well, if it becomes a bigger issue, I can address it.
[Droid 2 Android Development] Shadowlore:
Note: I didn't use Motoboy's roms.. I used the ones directly posted on mydroidworld.com... the 'OEM' ones without root already applied to them. (dumb me, I used the original files... forgot I'd DL'd both sets)

.. and again.. I've reproduced it every time now. (tested it 3x to make sure that was the issue) Just used Motoboy's and the result is different... root stays in place :)

Still, it's not that big a deal.. I'm fully comfortable digging into the device to fix what needs fixing... allows me to learn more in the process too
[Droid 2 Android Development] facelessuser:
Hmm. The mydroidworld one may be wiping certain things that are not getting wiped in motoboys. I do know this, usually if I loose root from a flash and try and reroot, I always reboot before testing root apps. This is to kill all current running processes and make sure the environment is running as it should. I cannot know for certain without duplicating your issue, not really looking to do that right now:).

If this becomes a bigger issue (a more frequent issue with users) then I will address. Looks like you pushed through it though, and I am sure you learn some stuff. Thanks for the heads up.
[Droid 2 Android Development] fatalfuryy:
Hi,

I have a couple of questions about the rooting because i am new to this. Will this work on the R2D2 verison and once i root my phone could i uninstall all those preinstall apps which are on the phone?

Also thanks to darkonion and facelessuser for coming up with this. I will be donating after i root my device
[Droid 2 Android Development] darkonion:
I think hardware is the same, so I don't see why it wouldn't. I don't know the answer for sure though. I don't think there is any harm in trying. Even on the regular D2, it doesn't hurt to try, even if it fails.
[Droid 2 Android Development] fatalfuryy:
sounds good. thanks for the reply back. once i get home ill try it and provide some feedback
[Droid 2 Android Development] facelessuser:
It should work. If it fails, run it again. Sometimes you have to run it multiple times on the original droid2. The phones can be a little stubborn sometimes.
[Droid 2 Android Development] OCCOMBILL:
Thank you kindly. Theoretically, I'm rooted... and now I'm wondering what to do next. is there a page that shows how to get rid of the excess crapware? And thanks again!
[Droid 2 Android Development] CurlyDE:
Check out the thread titled "[TUT] 'Removing' some of the bloat". Apparently I am too "new" to post a link to it.
[Droid 2 Android Development] yamaharider:
Help phone is connecting but getting a error

I have tried this on three computers all with the same success. I have updated everything and followed the video step by step and the other steps. When in the process at the end I get this message.

adb connection will be reset. restat adb server on desktop and re-login.

could not kill pid 12073: No such process

The error number is different at times, please help me!
[Droid 2 Android Development] darkonion:
I think as long as it says you got root, you should be okay. That particular error is... well... not really an error. More of a warning.
[Droid 2 Android Development] facelessuser:
Ignore the pid error. I was trying to fix an issue that turns out wasn't really the issue. Keep trying.
[Droid 2 Android Development] chromadroid:
I've been trying to follow along, using 2.1.4 on windows xp.

one thing that I don't understand are these references to "type XXX" where do I type this? Looking in *sdk*/tools I see no terminal or anything else that makes me think I can use it.

I *was* having major issues with the root, but it finally worked.

steps/settings used:

PC mode (took me a while to figure out how to turn that on)

USB Debugging on (though notification didn't show it)

ran the doroot.bat

got to the "restart adb server" line

my phone rebooted itself.

unplugged / replugged usb cable.

script continued

says all is good.

root confirmed via wifi tethering app

now I'm trying to install "superuser" app but that's not working. posted in another thread about it already.

Thanks guys. I was super frustrated, and then it just worked. I probably tried it 6 or 7 times before it did that device reboot and all was well.
[Droid 2 Android Development] facelessuser:
Okay, the terminal is just the command line in windows.

I am a little confused that your phone rebooted after restarting adb. Did it reboot at the end of the script, or in the middle? At most, it should only reboot at the end. If it was in the middle, possibly the export crashed the OS, but did't reset the ADB root shell, that would be a new one.:)

How did you confirm via wifi tethering app, did you see superuser app pop up asking you to allow root?

Assuming you did verify root, are you trying to install Superuser.apk from the Market? You already have a Superuser.apk on your phone; they are not the same, so Market is not going to be able to install on top of it. If you want the one on market, you will have remove Superuser.apk from your /system folder on your phone, and then install the new Superuser app.
[Droid 2 Android Development] Smoochy:
New user here with a question about rooting.

Trying to root a Droid 2, 2.2 with a Mac.

I've been trying use the 1-2-3 Droid Root.

I've gotten past opening the adbdl.sh in terminal and launched the update program where I rejected everything but the top one (the 2.2).

I was then instructed to in the terminal to start up dorootv2.sh.

I typed the chmod 0755 & all that, got the doroot going, but then another program launched asking me what packages I wanted to install.

That is where I am stuck. I looked around online through other forums and I don't see anyone mentioning this part. The top choice was to install SDK API 8, revision 1.

I believe under that was 7. I just wasn't sure if I should keep them all checked for install or what.

I did notice if I did any sort of change (like rejecting), I would get a message in the terminal asking if I was ready to root.

Do I need the Motorola drivers? Its never mentioned during this rooting process, but I see people talking about it needing them when rooting.

Thanks
[Droid 2 Android Development] facelessuser:
I wrote the rooting script, but I did not write adbdl.sh, but I have looked it over. As I understand adbdl is supposed set up adb and pull down what you need and set it up. You should not have to chmod anything except adbdl.sh.

You do not need moto drivers.

You need to be in PC mode or charge only on the mac.

You need to have debugging enabled.

I am confused that anything would instruct you to chmod doroot in the terminal if you are using adbdl, unless darkonion changed it. It sounds like you are trying to do two methods at the same time. I am going to have to look at what darkonion is doing again, before I give any advice.
[Droid 2 Android Development] facelessuser:
It appears the opening page is getting confusing for mac and linux.

We have one thing telling users to download dorootv3.sh.

We have another thing telling them to download adbdl.sh.

And then we have actual root script if you have adb installed doroot.sh.

You should only have to download one of these. So if you are having issues, start with telling me which method you have chosen. Then I can help.

@darkonion I think we really need to clean up the opening page. We have too many versions going on right now.
[Droid 2 Android Development] Smoochy:
Ok, here is what I did

One Click for Linux and Mac

New for Linux/Mac! This is a simple script that will download Android-SDK, extract it, and start it up for you to update it, and download the doroot.sh file. Essentially, it does all of step #1 for you. All you have to do is update and start doroot.sh after you finish updating.

Instructions for running the script that downloads Android SDK, doroot.sh

1. Download the file.- Done

2. Double-click the file to run the script.- wouldn't start so went to 2a

2a. If the script does not run, navigate to the directory the file that it is located in terminal, and run the next two commands.

2b. chmod 0755 adbdl.sh- Done

2c. ./adbdl.sh- Done

3. The script will run. It will download the Android SDK for your OS, unzip it, and place it in your home directory. It will also download the doroot.sh into the tools folder.- Done

4. After it finishing downloading, it'll launch the update program. You only need to updated/install the 2.2 environment. You can reject everything else.- Done. Installed Android SDK Tools Revision 7 & SDK Platform 2.2, API 8 Revision 2

5. After the update, and closing the update program, the terminal will prompt if you would like to continue on to rooting your phone. Here is where I am having the problem. (Copy & pasted from terminal) "After updating Android SDK, you will be ready to run doroot.sh.

No command line parameters provided, launching UI.

See 'android --help' for operations from the command line."

This is where I thought I had to start with dropping the doroot.sh in and doing the "chmod 0755" thing. After I do that, it continued with launching the update program asking me what packages I wanted.

Make sure your phone is in a mode that has the USB debugging icon, (PC Mode and/or Charge Only), and choose the "yes" option in terminal.

6. Your rooting process should now start!
[Droid 2 Android Development] facelessuser:
Just let me know if you are still having trouble. I know it can be a little frustrating when things don't quite work the first time and your not even sure what is supposed to happen. It is both the fun and pain of hacking your phone.
[Droid 2 Android Development] Smoochy:
Yeah, I have to admit, the hassle part (which I'm sure I'm causing myself) is still a lot of fun. :D
[Droid 2 Android Development] darkonion:
That's weird. That sounds like your are starting up the update again.
[Droid 2 Android Development] justcausetx:
1st try with one step on droid x non ota 2.2 worked like a charm. thanks for all your hard work!!
[Droid 2 Android Development] Smoochy:
Right.

Even with no past experience rooting any phone, I didn't think that seemed right. I'm just not given the option to root until I manually start doroot. I went through the steps to start doroot, the program started up asking what program(s) I wanted to install, I selected just the "API 8" option and then doroot started up in my terminal, then asking if If I wanted to root.

I stopped there because I wasn't sure if running adbdl & then having to run doroot was a good idea or not.
[Droid 2 Android Development] jbink16:
i cant get my computer to recognize my d2. anyone know if there is a one touch for d2? it would be a lot easier
[Droid 2 Android Development] darkonion:
Sorry dude. That'd be the ideal way to go, but currently, this is the only method. Go to the information directory. It is stickied. There is a way to root your phone w/o using a computer.
[Droid 2 Android Development] darkonion:
If you still need help, PM me, or email me at darkonion@kimete.com.
[Droid 2 Android Development] egypt78:
So not working for me....im stuck when I double click doroot from adk tools it just says checking devices....*daemon not running. Starting it now on port 5037*....then says* daemon started successfully*....then does nothing ans its there forever? What am I doing wrong please.....???
[Droid 2 Android Development] darkonion:
You need to fumble with the usb connection settings. Try pc mode, or charge only. and restart the program. If those don't work, try each mode again, but try disabling usb debugging and enabling it again.
[Droid 2 Android Development] egypt78:
Ok......then it opens up the command window and wont let me close it to try again without having to start the computer again.....is that right?
[Droid 2 Android Development] egypt78:
Stupid question everyone knows im sure but am I supposed to accept all the packages in the SDK manager or just the the latest version? Beginner sorry.....
[Droid 2 Android Development] facelessuser:
Accept (you mean update?). I don't really think it matters; I don't even think you have to update, but if you do, update the 2.2 related stuff.
[Droid 2 Android Development] yaooitsbrett:
I'm getting an error message after the script tells me that adb is resetting.

the error is "could not kill pid 24618: no such process"

I've tried searching for this error but I'm guess the numbers throw it off and I get such scattered results with no success haha.

does anybody know what this means?
[Droid 2 Android Development] facelessuser:
Yeah, the exploit is having a tough time killing adbd on your phone, so the script times out and tries to kill the exploit (I thought it was hanging, but it isn't ). So, it tries to kill the exploit, but the exploit isn't running. That is why you get that error. Just try again; I have seen people have more sucess by rebooting the phone and trying again.
[Droid 2 Android Development] yaooitsbrett:
Thanks a lot.

I actually retried the script after I got the error and it completed perfectly fine without error.
[Droid 2 Android Development] facelessuser:
Congrats on your root.
[Droid 2 Android Development] jbink16:
Can you show me a way to the root without computer. Also has there been a bootloader unlock for the x and 2 yet?
[Droid 2 Android Development] ChrisXKE:
Same problem

I am having the exact same issue. Please help. (Droid X owner)
[Droid 2 Android Development] derte:
One Step Root

Droid 2

PC = win 7 ultimate

1 step root process went flawlessly. After reading all the other users issues I was able to get this on first run, and within like 45 seconds. Thanks to all developers for your hard work!
[Droid 2 Android Development] darkonion:
I'll have to look at the code. So, it keeps launching the update thing? Did you guys close the UI after updating?
[Droid 2 Android Development] facelessuser:
In the next day or two, I am going to see if I can eliminate the step of installing the SDK.
[Droid 2 Android Development] darkonion:
I am planning to spend some time after class working on the Linux and Mac script. I'll touchbase with facelessuser and see if we can figure out a way to either get rid of SDK or at least lean it out.
[Droid 2 Android Development] Smoochy:
When the update comes up, I kept the SDK platform 2.2 API 8 Revision 2 (the top one). I rejected everything else.

After it updated & installed, I closed out the update completely. At that point, I thought doroot was to automatically start up in the terminal. Instead the message "After updating Android SDK, you will be ready to run doroot.sh.

No command line parameters provided, launching UI.

See 'android --help' for operations from the command line."

It just sits and does nothing.

I'm not in any big rush to get my D2 rooted. You guys are doing an awesome job doing whatever voodoo magic you do.
[Droid 2 Android Development] facelessuser:
Okay Linux/Mac 2.2.0 is hopefully coming tonight. I have most of it done; I just need to test.

1. No need to install SDK (I have my fingers crossed)

2. No more hanging if exploit fails (I have my fingers crossed)

3. When unrooting, remove busybox at alternate location as well (/system/xbin)

4. When installing busybox, check to see if there is a busybox at alternate location and remove it (/sytem/xbin)

5. Check for adb and halt progress if it isn't there
[Droid 2 Android Development] jbink16:
how do i get the computer to recognize my phone. it just searches forever.
[Droid 2 Android Development] facelessuser:
I need more info what platform: windows, mac, linux?

What USB mode is your phone in: USB mass storage, PC mode, Charge only?

Is debugging enabled on your phone?
[Droid 2 Android Development] facelessuser:
Linux 2.2.0 works great with no SDK installation.:)

Now to test Mac.
[Droid 2 Android Development] facelessuser:
Mac worked flawless as well! 2.2.0 is a success.:)

I will hand this off to darkonion. No more SDK installation if you do not want to!

Windows, your next...tomorrow.:cool:
[Droid 2 Android Development] facelessuser:
@darkonion I'm sorry, but now you are going to have to change the procedure. No more installing SDK.

Check your inbox 2.2.0 is waiting for you. Linux and Mac are now separate since I am packaging their respective adb binary with the script. In the future, we can probably make so that it pulls down the correct one on its own, but I am tired of sitting in front of my computer tonight.
[Droid 2 Android Development] darkonion:
No problem! Uploading 2.2.1 now!
[Droid 2 Android Development] Spectrum17:
I'm having an issue getting my droid to to root.

Have followed the instructions to a T and cannot get it past the first batch file.

It sees the droid but it appears that when my windows PC tried to push anthing out to the droid it failed. example <0 bytes in 5392.000s>

Then when it tried to execute rageagainstthecage-arm5.bin if our course could not and kixks to

$

any pointers?
[Droid 2 Android Development] facelessuser:
This may seem like a silly question, but you mean "Droid 2" right?

What USB mode is your phone in?

And is debugging enabled?

Is your phone connected directly to your PC or through a USB hub?
[Droid 2 Android Development] Nalgous:
I had a question and I was wondering if you guys could help me with it. After I rooted my phone, I deleted some bloatware, but now it is unable to update properly. I assume its because some of the .apk's are missing or something. How can I make it so that my phone is able to update to motorola's update? I wouldn't mind have to re root it if it takes that, although I'm cautious to try anything that would involve possibly bricking it.
[Droid 2 Android Development] facelessuser:
I don't understand. Are you talking about motorola's OTAs? Traditionally when you root, you can no longer do OTAs. People usually just install Roms based on the latest OTA.

I don' t know what you removed, so I don't even know if you unrooted and did the OTA if it would work or not. If you want, you can always use the SBF to restore your phone to stock, update, and then root your phone.
[Droid 2 Android Development] samiusmc:
Does this work on the Droid 2 regardless of which OS build it's using? My Droid 2 received an update a few weeks ago. That being the case, is it still possible for me to root it using this method? Thanks.
[Droid 2 Android Development] facelessuser:
Haven't heard of the exploit not working on the Droid 2 yet.

The exploit works on Froyo, so I think you are okay. The exploit may not work on future OS like Gingerbread, but currently if you have Froyo, it should work.

If it fails just give it another go. It isn't perfect, but it always gets the job done eventually.
[Droid 2 Android Development] samiusmc:
Thanks for the quick reply. This is for my wife's Droid 2. I have a Droid 1 and she wants her font size larger like mine. I know I'm able to do it on my Droid 1 but does this exploit for the Droid 2 allow me to increase the font size? Thanks again.
[Droid 2 Android Development] facelessuser:
:confused:

The exploit allows you to root your phone...and only root the phone.

Rooting allows you to change and tweak things. With root you could probably increase the font size, but you have to know how to do that.
[Droid 2 Android Development] darkonion:
Sometimes, updates require you to have certain apps installed. If you don't have the app installed, you might be out of luck with updates.
[Droid 2 Android Development] facelessuser:
Windows 2.2.2 is looking good. I just need to test it.

I am bumping the revision to 2.2.2 because I have to fix something in Linux and Mac (minor issue), and I want them at the same version number because their functionality and fixes are the same.

Windows 2.2.2

-No SDK needed

-Removal of busybox at alternate location in rooting and unrooting

-Check if adb exists, quit if it doesn't

-Fix hang if exploit fails in rooting and unrooting (forgot it in unrooting: Mac and Linux 2.2.1)

-Fix hang on remounting after unroot (remounting as RO isn't necessary, so if it fails we ignore it and reboot anyways. This was also in Mac and Linux 2.2.1)

-A little clean up
[Droid 2 Android Development] jbink16:
I am on windows vista with charge only with debugging on.
[Droid 2 Android Development] darkonion:
You are stuck at that daemon starting thing right?

You are in terminal. If you are in PC mode with usb debugging enabled and you are stuck at the daemon message, and it won't go anywhere, try changing it to charge mode. If it doesn't kick up, go back to PC mode and then disable usb debugging and enable it again. If that doesn't work, go back to charge mode and disable Usb debugging and enable it again.
[Droid 2 Android Development] jbink16:
I tried to change to PC Mode but this didnt work. It was stuck on "checking for devices..."

Is there any other way to root besides the command line root? thanks
[Droid 2 Android Development] GL525:
Successful Root Droid x! Big shout out to all who spend hours helping out!
[Droid 2 Android Development] darkonion:
You can try the terminal app method. Before doing that though, have you tried unplugging your phone while it is waiting for the device and replugging it back in?
[Droid 2 Android Development] Spectrum17:
Yes indeed it is a droid 2,

using Charge only USB(the only way I could get debugging enabled )

Direct connection to my XP machine
[Droid 2 Android Development] facelessuser:
Hmm. You have Motorola drives installed?
[Droid 2 Android Development] ChrisXKE:
2.2.2 download?

Thanks for all the hard work you guys do to root these devices. Where can I get 2.2.2? (Mac OS X)
[Droid 2 Android Development] facelessuser:
There is no 2.2.2 yet. It will contain a very minor fix. I do not believe you will need it, but 2.2.1 is on the opening page; it does not need the SDK.
[Droid 2 Android Development] matrix2004:
darkonion helped me root Droid X a few weeks ago. I have bootstrap and ROM manager/clockwork mod.

Do i need to do anything now that there's this 2.2 SBF?

Also, am i considered 'deodexed'?