yashsingh1/xdaforums huggingface dataset:
[Droid 2 Android Development] facelessuser:
:confused:

Not sure what you mean. If you are rooted, bootstrapped, and deodexed...

We are Droid 2 users here, and I am not sure what you think the significance of the 2.2 SBF is.

I guess, if you flashed the 2.2 OTA and then rooted, then if something goes very wrong, use the 2.2 SBF.

If you never did the 2.2 OTA and have 2.1 and you have just been using roms that install 2.2 system apps, then use the 2.1 SBF if things go really bad.

If nothing goes bad, forget about the SBFs and enjoy your phone.
[Droid 2 Android Development] matrix2004:
awesome.......thanks
[Droid 2 Android Development] ChrisXKE:
I am in the terminal and change permissions and execute dooroot.sh and then the next line reads

"ERROR 27: Adb is not found. Please acquire or install it."

What should I do? (Mac OS X, Droid X)
[Droid 2 Android Development] facelessuser:
:confused: Is adb in the same folder with doroot.sh?

How are you launching it (what is the exact command you are giving it)?
[Droid 2 Android Development] ChrisXKE:
Yes adb is in the same folder. I run chmod 0755

christopher-lexows-macbook:~ ChrisLexow$ chmod0755/Users/ChrisLexow/Desktop/DoRootMac/doroot.sh

-bash: chmod0755/Users/ChrisLexow/Desktop/DoRootMac/doroot.sh: No such file or directory

christopher-lexows-macbook:~ ChrisLexow$ /Users/ChrisLexow/Desktop/DoRootMac/doroot.sh

ERROR 27: Adb is not found. Please acquire or install it.

Enter exit once to exit terminal.

christopher-lexows-macbook:~ ChrisLexow$

Please also understand that I am a newb at this.
[Droid 2 Android Development] darkonion:
christopher-lexows-macbook:~ ChrisLexow$ chmod0755/Users/ChrisLexow/Desktop/DoRootMac/doroot.sh

You are missing two spaces. Should look like this:

christopher-lexows-macbook:~ ChrisLexow$ chmod 0755 /Users/ChrisLexow/Desktop/DoRootMac/doroot.sh
[Droid 2 Android Development] facelessuser:
Thanks for the specifics, this explains everything. You are launching the script from ChrisLexow; therefore ChrisLexow is your default directory; therefore it is looking for adb in ChrisLexow.

This will put you in DoRootMac and make DoRootMac your default location...get it:)

cd /Desktop/DoRootMac

Then run

./doroot.sh
[Droid 2 Android Development] ChrisXKE:
I got it to work! I entered this

Last login: Thu Oct 14 18:41:55 on ttys000

christopher-lexows-macbook:~ ChrisLexow$ chmod 0755 /Users/ChrisLexow/Desktop/DoRootMac/doroot.sh

christopher-lexows-macbook:~ ChrisLexow$ cd /

christopher-lexows-macbook:/ ChrisLexow$ cd //Users/ChrisLexow/Desktop/DoRootMac

christopher-lexows-macbook:DoRootMac ChrisLexow$ /Users/ChrisLexow/Desktop/DoRootMac/doroot.sh

Welcome to DarkOnion Root
[Droid 2 Android Development] facelessuser:
Cool.

Command line can be a little tricky if you don't use it often, but luckily it is only like three commands you have to know.
[Droid 2 Android Development] darkonion:
I am currently away from the computer right now. But I will get it up as soon as I am home. I will take a look at the code and see if I can port it over to windows.
[Droid 2 Android Development] facelessuser:
I can always help with windows if you have issues. I know my way okay with batch files too. I can see no reason why this can't be done with one batch file. One click and then root.:)
[Droid 2 Android Development] cktodd:
First -I want to thank all of you for helping us newbies work through this. If it wasn't for people like you all who are willing to help - most of us would never get past the first post.

As a windows XP user I just want to clarify - I start the process with the:

"Open command prompt.

cd c:\android-sdk-windows\tools

doroot1.bat"

Sorry to be so lame, but what are the steps after that? I've read that some have had to chmod files or use any other commands?

If someone could describe in detail the steps us windows users have to do after running the .bat file, I would very much appreciate it!

Thanks so much!
[Droid 2 Android Development] vampireincubi:
Running

XP
[Droid 2 Android Development] darkonion:
Depends on what version you are on. If you are using the link from the second post, you need to now launch doroot2.sh.

So...

adb shell

cd data/local/tmp

chmod 0777 doroot2.sh

./doroot2.sh
[Droid 2 Android Development] event121:
Really appreciate your steps and detail.

Win7 64-bit

doroot2.sh not found as others have posted.

was going to run the long(er) method since I know that works, but I want to see you make this one-clicker happen.

Keep up the good work!
[Droid 2 Android Development] facelessuser:
Do you get that error with the command "./doroot2.sh", if so, I would try "sh ./doroot2.sh". If the file is there it should run. You can always try the new beta Linux script to. It requires you to enter No commands.
[Droid 2 Android Development] event121:
Would if I had linux.
[Droid 2 Android Development] facelessuser:
Oh, you are on windows? Run doroot2.bat. I think he has that trying to execute the doroot3.sh on the phone.
[Droid 2 Android Development] darkonion:
Yeah. Run the Windows beta version. Two-click root. I think you can get away with double-clicking doroot1.bat. Letting it run until it kicks you back to MS-Dos. Then click the doroot2.bat.
[Droid 2 Android Development] facelessuser:
I have scripted up a revision of the new linux beta one click root. It should have more robust error checking to let you know exactly what went wrong and clean up sloppy code to make it more maintainable. I want to test it on my phone tonight first to ensure it does in fact work. I will hand it off to darkonion after testing.

Don't want to blow up your phone without testing :D.
[Droid 2 Android Development] Kenny Strife:
I got the same error on Windows 7 x64. I found out what was up, and this might be sort of esoteric... I don't know if it will help anyone else, but I figured I should mention it anyway just in case.

Make sure that you've got the USB debug icon in your notification bar. I had it turned on in Settings>Applications>Development, but the icon still wasn't showing up. I had to plug into my computer via USB in PC mode, then switch it to USB mass storage mode while still plugged in. This made the USB debugging icon appear in the notification try. Then I switched back to PC mode and was able to root manually.
[Droid 2 Android Development] event121:
That did happen to mine as well.

Same steps to get it to show up.
[Droid 2 Android Development] Mijobar:
I still cant get it to be rooted.. I am running windows 7 64 bit I tried the two step batch files they they both close when they are done and nothing happens on my phone =/
[Droid 2 Android Development] facelessuser:
Don't worry, we have an idea of what is wrong. I am working with darkonion to figure out how to get windows up and running. I have given him some ideas to make it have a better success rate.
[Droid 2 Android Development] darkonion:
I just updated a new file like 30 seconds ago. I am going to post a new link. Hit me up on Gtalk in a few minutes. PMing you info.

-Kevin
[Droid 2 Android Development] event121:
Win7 64-bit

Ran it. Looked great... but here's what happened (is happening):

cmd prompt

cd c:\android-sdk-windows\tools

adb shell

$

su

su: permission denied

so it looks like root, but I can't access superuser permissions?

superuser app says there's an update but i must install a .zip from recovery

koush reinstall and cannot bootstrap or boot recovery

ideas?

UPDATE:

I did everything from the How to Root thread and achieved su permissions. EDIT: rage command was iffy.

Here's what I typed in adb shell to make it work:

adb shell

- cd data/local/tmp

- chmod 0755 rageagainstthecage-arm5.bin

- ./rageagainstthecage-arm5.bin

- let the process run until it 'kicks' you out (may take a minute or two) to c:/Droid2Root

- cd c:/wherever-your-sdk-tools-folder-is

- adb kill-server

- adb devices (to verify the connection)

- adb shell (you should now have a # prompt, if not return to ./rage step above)

- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system

- cp /sdcard/Superuser.apk /system/app/Superuser.apk

- cp /sdcard/su /system/bin/su

- cp /sdcard/busybox /system/bin/busybox

- chmod 4755 /system/bin/su

- chmod 4755 /system/bin/busybox

- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system

- exit

- exit

Then I did this to get the latest SuperUser:

adb shell

su

mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system

rm /system/app/Superuser.apk

pm uninstall com.noshufou.android.su

That all worked for me.

EDIT: so I guess the warning here is, if you don't get the #, run the ./rage line again
[Droid 2 Android Development] darkonion:
Hit me up on GTalk. I think you are doing too much work.

-Kevin
[Droid 2 Android Development] facelessuser:
Got the one click linux revision done. I think it works pretty good. I tried it multiple times. It will give a unique error code if something goes wrong so we can tell exactly how far you got. darkonion I sent it to you. Lets get this in peoples hands, I think it should be pretty stable.
[Droid 2 Android Development] darkonion:
Thank you sir! Just posted in post #2. I will start working on porting it to Windows hopefully tomorrow!
[Droid 2 Android Development] ChrisXKE:
so I am here after 10 min

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

Do I keep waiting or do I need to restart the adb server?
[Droid 2 Android Development] facelessuser:
It is a pain to get that sucker to kick out when it fails. Try this. Close the terminal. Reboot your phone (I've seen greater success when people reboot their phone fresh). And run again, if it hangs for 10 min again, close terminal and run again.

The actual rooting sometimes fail (this is what you are seeing). Just keep trying it will eventually work.
[Droid 2 Android Development] darkonion:
Yeah... facelessuser and I see enough of the roots to know that the exploit isn't 100%. Just rerun the script.

-Kevin
[Droid 2 Android Development] ChrisXKE:
I appreciate the help!
[Droid 2 Android Development] ChrisXKE:
ROOTED!

Officially rooted! Thank you!:)
[Droid 2 Android Development] Spectrum17:
Indeed I do
[Droid 2 Android Development] Spectrum17:
Please see attached

here is what I'm getting
[Droid 2 Android Development] facelessuser:
Oh wow. You are using an old version. Download the one click.
[Droid 2 Android Development] kd7uxg:
Droid 2 FRG22D, rooted and works great in terminal emulator mode and with apps, but when I go back to the adb shell, it shows $ prompt and wont allow any permisisons. When I first rooted it, I did get the # prompt and everything worked as your instructions said it should. I tried running the rage binary again, but it stayed at the $ prompt for over 30 minutes and never kicked me out. Any idea how I can get root access back from the adb shell program? Other root functions work just fine on the phone, just can't get the adb shell (or the root file explorer for windows) to gain root access.
[Droid 2 Android Development] Spectrum17:
Well, 23rd times a charm.

rooted!
[Droid 2 Android Development] theecho:
What happens if you type "su" from shell?
[Droid 2 Android Development] facelessuser:
bootstrap your phone if you want a constant root in adb shell. By default, every time you reboot, you loose adb shell root.

Rage will get it back root in adb shell untill you reboot, but rage sometimes fail (hence your hanging after 30 min), and you have to keep trying until you get it.

You can usually just type "su" in adb shell, and press accept on your in Superuser dialog on your phone as well.
[Droid 2 Android Development] kd7uxg:
Standard "permission denied" comes up, and back to the $ bash user prompt.

I should add I am running WIN 7 64 bit incase that makes any diff.
[Droid 2 Android Development] kd7uxg:
I will try that when I get home. I was wondering if the superuser app was not allowing SDK to gain root access somehow. Dont see a way to manually allow specific programs without actually running them first. Never noticed anything pop up on the droid while trying the adb shell but wasn't really watching the phone either.
[Droid 2 Android Development] facelessuser:
I've heard of it not popping up sometimes, but bootstrapping will give you always on root in adb shell.
[Droid 2 Android Development] kd7uxg:
I'll let you know. Just about finished with my new Linux box - Ubuntu, should make a lot of stuff go smoother... I'm an old Slackware guy myself - used to admin my own ISP before the big guys all jumped in it, but I figure I should try the new stuff out.
[Droid 2 Android Development] facelessuser:
I use Ubuntu as well. Easy to configure, widely supported. It is very targeted to average consumer use, which is nice, but you can reconfigure it any which way to suit your needs.
[Droid 2 Android Development] theecho:
i prefer a tri boot of MAC/WIN/Ubuntu :-)
[Droid 2 Android Development] facelessuser:
I use to do the same until my MacBookPro motherboard died...out of waranty :mad:. Now I use my wife's MacBook when I need to do Mac stuff, and I have some random Linux and Windows hardware.
[Droid 2 Android Development] darkonion:
I dual boot Windows XP/ubuntu. If I need access to a Mac, I try to borrow a friend's.
[Droid 2 Android Development] pure_guava:
This is killing me...

The only way I can seem to get it to detect anything is by USB Mass Storage.

From there I get

- daemon not running... starting on port 5037

- started successfully

- still not running... cant connect to daemon

Over and over. Occasionally I get the ADB ACK thing...

(I have ended adb.exe prior to running. Although strangely, it always seems to run 2 of them...)

It seems like people run across this, but somehow get it fixed easily. Any help?
[Droid 2 Android Development] pure_guava:
Oh, I forgot the other stuff.

Windows 7, all suggested moto drivers are installed.
[Droid 2 Android Development] facelessuser:
Might be a bad usb cable or port. Are you on windows, and if so did you install the drivers?
[Droid 2 Android Development] facelessuser:
Beat me to it. It might be that your cable is iffy.
[Droid 2 Android Development] pure_guava:
I can transfer files back and forth, with no issues.
[Droid 2 Android Development] sapko:
Regarding 3.0 instructions and video dont mention what mode I should put phone in.
[Droid 2 Android Development] darkonion:
Ideally PC Mode with USB debugging enabled. Otherwise, charge only with usb debugging enabled.
[Droid 2 Android Development] sapko:
Just wanted to make sure, thanx fire the quick reply. Btw does anyone know why must people can't get debuging mode to work in pc mode?
[Droid 2 Android Development] facelessuser:
More than likely drivers. On linux and mac it works fine.
[Droid 2 Android Development] sapko:
I'll try again, but I couldn't get it to show up and I am using a mac.
[Droid 2 Android Development] sapko:
Using mac just rooted worked on second try, thanks alot guys.
[Droid 2 Android Development] theecho:
you could always install an x86 port of mac on your desktop.
[Droid 2 Android Development] pure_guava:
Anybody? :)
[Droid 2 Android Development] theecho:
Have you tried a different cable?
[Droid 2 Android Development] jbink16:
ROOTED droid 2. changed the cable and it worked. if you are not getting recognized, try a new cable ( i used my dads en v 3 cable)
[Droid 2 Android Development] samiusmc:
Worked great on my Droid 2. Awesome job! Simple as pie.
[Droid 2 Android Development] anducly:
will root work if i updated my droid 2 to 2.2.2
[Droid 2 Android Development] darkonion:
It should.
[Droid 2 Android Development] awillis22:
Rooted successfully, everything works great except for wifi. I am able to use the Barnacle Tether Wifi for another device, but no such luck for my D2. It will say "connecting..." then just stay at "Disconnected"

A few things:

I used root explorer to change the file extensions of some of the bloatware to prevent them from running. (Blockbuster, Kindle, My Verizon, Amazonmp3, Cardock, CityID)

And I used AdFree, blocking the host files etc.

Been playing around with it but have had no luck:confused:... any help is appreciated
[Droid 2 Android Development] CurlyDE:
I had issues connecting to Wifi Tether if Access Control was enabled on my D2. Leaving that disabled works fine for me with any device that can make an ad-hoc connection.

Some wifi devices might not support ad-hoc connections ... I have a Realtek 8187 based USB device that can not connect to ad-hoc networks using the default Linux 2.6.32 kernel module.
[Droid 2 Android Development] awillis22:
Realized my wording here was a little confusing... I meant to say that I can connect a device (i.e. my laptop) using an ad-hoc connection (Barnacle) through my Droid 2.

However, I cannot simply connect my D2 to my wireless home network. It will say "connecting..." then switch to and stay at "Disconnected"
[Droid 2 Android Development] theecho:
Try to tick the Wifi check box to turn it off and then turn it back on.
[Droid 2 Android Development] awillis22:
No dice. I've tried it multiple times, and have done a few battery-pulls.

Now watching it, i see that it goes from Scanning, to Connecting, to Disconnected (for about 5 seconds) and then repeats. over. and over. and over. :confused:

I've also tried 'forgetting' and then re-adding my network, still, no such luck.
[Droid 2 Android Development] theecho:
I had this issue as well and had to manually check the wifi box box and then uncheck it and it worked.
[Droid 2 Android Development] snakernetb:
Linux?

I use fedora and I can't get the one click method to work. Has anyone else used fedora 13 to root an adroid2? My attempt just hangs at this:

[*] adb connection will be reset. restart adb server on desktop and re-login.
[Droid 2 Android Development] darkonion:
It is suppose to take awhile at that step. If it takes longer than 10 minutes, rerun the script file.

-Kevin
[Droid 2 Android Development] ogreinside:
I just successfully used this root on my Droid X from Fedora 13 x86_64. I will admit I was a little confused at this step too after running "Enter ./data/local/tmp/rageagainstthecage-arm5.bin" since it says:

However, this is referring to your own local system prompt, NOT the adb $ prompt. Apparently "rageagainstthecage-arm5.bin" runs in the background and returns you to the adb prompt ($) but this step is not complete yet. You must wait until adb itself exits and you get your original system prompt back. Then run "./adb shell" to verify it is a root prompt (#). You can then exit adb and run ./doroot2.sh.

For reference my "rageagainstthecage-arm5.bin" background step took about 3 minutes.

Here is my output if it helps:

[ogreinside@mysystem tools]$ [b]./doroot1.sh[/b]

<output omitted>

Enter ./data/local/tmp/rageagainstthecage-arm5.bin
This process can take up to 15 minutes.
After being kicked back to command prompt,
enter ./doroot2.sh

$ [b]./data/local/tmp/rageagainstthecage-arm5.bin[/b]

[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

<output omitted>

[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$

<3 minutes later - notice there is a carriage return missing>

$ [ogreinside@mysystem tools]$ [b]./adb shell[/b]
# [b]exit[/b]

[ogreinside@mysystem tools]$ [b]./doroot2.sh [/b]
Welcome to DarkOnion Root Part 2

<output omitted>

I had to power off/on my Droid X after my first couple of tries, then it worked.

darkonion: you may want to make this message a little bit more clear that adb will exit on it's own, and wait for your system prompt. Or try calling ./doroot2.sh at the end of doroot1.sh, so when the adb shell exits it will just run it. I didn't test this but it should work. Then it would truly only be one command to enter!

Thanks for putting this together!
[Droid 2 Android Development] darkonion:
I think that is from an old version. But glad it worked. All the new version stuff was moved from post #2 to post #1.
[Droid 2 Android Development] ogreinside:
Ah, I wrongly assumed the 1st post has the latest updates (I see it does now).

Nice Windows bias in the script, btw ;)
[Droid 2 Android Development] darkonion:
Hahahahaha. Not really. If you run the windows script, I call them out and tell them they need to be a real man and run Linux.
[Droid 2 Android Development] shagdaddy:
App Market Gone???

Ok so i just finished rooting, and my app market is gone...when i click the icon(not the same icon, just a blue computer screen and a gear) it says application is not installed on your phone? Any ideas would be appreciated, cuz its not actually my phone, its a friends. I told her not to worry id get it taken care of, but the sooner i can assuage her doubts the better lol thanks in advance:confused:

I followed the youtube instructions by the way lol
[Droid 2 Android Development] darkonion:
Easier 1-2-3 Root for Windows is now standalone. Extract the folder and run doroot.bat!
[Droid 2 Android Development] ogreinside:
HA! I didn't even look at the Windows script, that's great!
[Droid 2 Android Development] SevereDeceit:
I used this program yesterday to root my Droid 2 and it worked the first time flawlessly. Thanks for helping me accomplish this in such an easy way, cheers!
[Droid 2 Android Development] GoogleisGod:
Thank you so much Worked like a Charm!
[Droid 2 Android Development] msanto:
Clicking through, it says there's a virus ...

WARNING: ProxyAV has detected a virus/PUS in this

file!

File has been dropped.

ProxyAV Administrator: it-reports-network@good.com

2010-10-25 11:33:58-07:00PDT

Hardware serial number: 1407105003

ProxyAV (Version 3.2.3.3(40511)) - http://www.BlueCoat.com/

Antivirus Vendor: Kaspersky Labs

Scan Engine Version: 8.0.1.23

Pattern File Version: 101025.125100.4173058 (Timestamp: 2010.10.25 12:51:00)

Machine name: ProxyAV-rws1

Machine IP address: 10.101.160.22

Server: 98.136.92.79

Client: 10.101.101.12

Protocol: ICAP

Virus/PUS: "Exploit.Linux.Lotoor.g" found!

URL: http://www.kimete.com/droid/beta/DoRootWin_2.1.4.zip
[Droid 2 Android Development] facelessuser:
LOL. That is funny. There is no virus. They are just simple scripts. If you think we are hiding something, open them up in a notepad. You can look at all of the source code and see nothing fishy is going on.

My my scan with Eset Nod32 turns up no viruses.
[Droid 2 Android Development] theecho:
http://theunlockr.com/2010/09/27/how-to-root-the-htc-hero-androot-method/

Its similar to this. See below for further information.
[Droid 2 Android Development] facelessuser:
It isn't really a false positive. The virus scan is scanning the exploit "rageagainstthecage-arm5.bin" and probably throwing that virus warning, because the code is shady. It is an exploit that is trying to gain root which shouldn't normally be allowed, so its methods are deemed shady by anti-viruses. The exploit is simply forking the adbd process on your phone until it reaches the limit in your kernel. After that, your kernel sends back a message saying "we reached the limit, let's kill this process (adbd)", so it does. Afterwards, it starts up again; this time it has root access. So yeah, it is dirty code that exploits your linux OS on your phone to get you root, but that is how you get root.
[Droid 2 Android Development] theecho:
Ah. Thanks ill update.
[Droid 2 Android Development] facelessuser:
People forget that getting root access by force should never be allowed; so what is happening in the exploit probably should be flagged by anti-viruses, and probably patched in the kernel or adbd (from a security standpoint). From a "I want root, but the manufactures won't give it to me stance", I don't mind.
[Droid 2 Android Development] msanto:
I don't think you are, but I'm hoping someone knows a way around it ...
[Droid 2 Android Development] facelessuser:
It is probably scanning the exploit, which technically is malicous code since we are attacking an weakness in your phone's linux OS to get you root (which shouldn't be allowed). The only way around it, would probably be to temporarily disable checking, use it, and renable virus checking.

I know. No one likes to disable anti-virus, but I guess, by definition, the exploit is a form of "malware", except in this situation where we want to use its "unsavory ways" to our advatage.:)