Here's a guide written for non-linux users on how to root your droid. What you do beyond that, well, I have another thread set up for that. Let's get going!
Once you have all these files downloaded, extract them all into a new folder at C:\Android
You should now connect your Droid to your computer and Mount the SD Card through the phone (A dialogue will pop up on your phone asking to connect your SD Card. Click Mount)
Courtesy of Fadelight:
(go to Device Manager. There you will see your droid (A855) with a yellow "!" next to it. Right click. Select "Update driver" and point it to the android folder. That is where the drivers are.)
Go to the C:\Android folder you created. Rename the file droid-root.zip to update.zip. Then take update.zip and move it to the SD Card on your phone.
Once this is done, unplug your phone and turn it off by holding the top button, then selecting Power Off.
Open your phone's keyboard. Hold down the letter X key on the keyboard and power your phone on WHILE HOLDING THIS KEY DOWN. You will see the Motorola logo, followed by a graphic with an ! mark on it. At this time let go of the X key and the power button. Press and hold the Volume + key on the side of your phone, then press the camera button while holding the Volume + key.
Now you will be presented with a menu. Navigate to "update" using the D-pad, and click the middle button. Now wait for the process to finish.
When it is complete, your phone will power up again. Go to Settings->Applications->Development and check the USB Debugging checkbox.
Connect your Droid to the Computer again.
Click Start on your computer, and click run. Type cmd in the box, and hit ok. Now type the following, pressing Enter after each line:
cd c:\Android\tools
adb push su /data/local
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
mv su osu
cat /data/local/su > su
chmod 6755 su
ls -l *su
(you should see the following)
-rwsr-sr-x root root 76200 2008-08-01 05:00 osu
-rwsr-sr-x root root 76200 2009-05-30 11:28 su
(now continue typing these following lines to finish)
Here's a guide written for non-linux users on how to root your droid. What you do beyond that, well, I have another thread set up for that. Let's get going!
Once you have all these files downloaded, extract them all into a new folder at C:\Android
You should now connect your Droid to your computer and Mount the SD Card through the phone (A dialogue will pop up on your phone asking to connect your SD Card. Click Mount)
Go to the C:\Android folder you created. Rename the file droid-root.zip to update.zip. Then take update.zip and move it to the SD Card on your phone.
Once this is done, unplug your phone and turn it off by holding the top button, then selecting Power Off.
Open your phone's keyboard. Hold down the letter X key on the keyboard and power your phone on WHILE HOLDING THIS KEY DOWN. You will see the Motorola logo, followed by a graphic with an ! mark on it. At this time let go of the X key and the power button. Press and hold the Volume + key on the side of your phone, then press the camera button while holding the Volume + key.
Now you will be presented with a menu. Navigate to "update" using the D-pad, and click the middle button. Now wait for the process to finish.
When it is complete, your phone will power up again. Go to Settings->Applications->Development and check the USB Debugging checkbox.
Connect your Droid to the Computer again.
Click Start on your computer, and click run. Type cmd in the box, and hit ok. Now type the following, pressing Enter after each line:
cd c:\Android
adb push su /data/local
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
mv su osu
cat /data/local/su > su
chmod 6755 su
ls -l *su
(you should see the following)
-rwsr-sr-x root root 76200 2008-08-01 05:00 osu
-rwsr-sr-x root root 76200 2009-05-30 11:28 su
(now continue typing these following lines to finish)
When it is complete, your phone will power up again. Go to Settings->Applications->Development and check the USB Debugging checkbox.
Connect your Droid to the Computer again.
Click Start on your computer, and click run. Type cmd in the box, and hit ok. Now type the following, pressing Enter after each line:
cd c:\Android\tools
adb push su /data/local
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
mv su osu
cat /data/local/su > su
chmod 6755 su
ls -l *su
(you should see the following)
-rwsr-sr-x root root 76200 2008-08-01 05:00 osu
-rwsr-sr-x root root 76200 2009-05-30 11:28 su
(now continue typing these following lines to finish)
haha I was gonna ask the same thing. I'm semi geeky but why would I wanna root my phone for? id rather leave this up to the experts and their custom roms than mess around with it on my own. unless there are some stuff that even non geeks can do after rooting the phone.
haha I was gonna ask the same thing. I'm semi geeky but why would I wanna root my phone for? id rather leave this up to the experts and their custom roms than mess around with it on my own. unless there are some stuff that even non geeks can do after rooting the phone.
Well, I am a linux-illiterate geek. Does that count?
I rooted my phone for a couple of reasons. The first is to delete the default apps that I don't want or use, such as amazon MP3 and Facebook.
The rest I can't remember because I've been up for about 22 hours now... the last 6 trying to remember everything I once knew and have since lost about basic linux commands. My brain is bluescreening.
Im trying to root this, but when i type adb shell it gives error: device not connected. The phone is connected into the usb. And is the su file suppose to be in c:\android\tools file or just android?
Im trying to root this, but when i type adb shell it gives error: device not connected. The phone is connected into the usb. And is the su file suppose to be in c:\android\tools file or just android?
I'm stuck at the same point. I'm using a force updated to 2.01 Droid and a Windows 7 64-bit PC. Any ideas? USB Debugging is on...tried restarting both.
Im trying to root this, but when i type adb shell it gives error: device not connected. The phone is connected into the usb. And is the su file suppose to be in c:\android\tools file or just android?
android\tools
And make sure you installed the USB drivers for the phone.
go to Device Manager. There you will see your droid (A855) with a yellow "!" next to it. Right click. Select "Update driver" and point it to the android SDK folder. That is where the drivers are.
After that, it should be smooth sailing with the connection.
OP - perhaps you should edit the instructions to include installing the drivers?
Fadelight
Thank you for your help. I was just looking at that as you posted. Just a couple notes. The link to the SDK from Google in the OP isn't correct. I copied and pasted the URL and it directs you to a d/l of an SDK which I downloaded and extracted, but the USB drivers aren't included there. I did a quick search and found a link here http://www.smilepak.com/temp/Droid_USB_Driver.zip
No problems after this...it was smooth as you stated.
Let the games begin...
Fadelight
Thank you for your help. I was just looking at that as you posted. Just a couple notes. The link to the SDK from Google in the OP isn't correct. I copied and pasted the URL and it directs you to a d/l of an SDK which I downloaded and extracted, but the USB drivers aren't included there. I did a quick search and found a link here http://www.smilepak.com/temp/Droid_USB_Driver.zip
No problems after this...it was smooth as you stated.
Let the games begin...
Are you using XP? I am using W7 64bit, and the drivers were included in the SDK - 2.0.1
When I enter "adb push su /data/local" i am getting "cannot stat 'su': no such file or directory. I have the su in the folder c:/android. The icon for su is a white paper "its not compatible/i need a program to open it". Can someone please help. I am pretty comfortable with linux which is why I thought this would be a walk in the park.
Forget all that upthere ^^^^^ i got to the end but I am not getting those numbers. I am getting:
-rwsr-xr-x root root 72188 2009-12-09 11:58 osu
-rwsr-sr-x root root 76232 2009-12-09 12:38 su
Last edited by gcroberson; 12-09-2009 at 11:40 AM.
I went ahead and finished even with the numbers above. How can I tell if it was successful?
download "android terminal emulator" from the market and then type "su" you should get a message "su: access granted, courtesy of www.magicandroidapps.com" and then a # sign that means you have root access. You can type "reboot" and it will reboot your phone, you can't do that without root access.
Last edited by dbarrett480; 12-09-2009 at 12:02 PM.
download "android terminal emulator" from the market and then type "su" you should get a message "su: access granted, courtesy of www.magicandroidapps.com" and then a # sign that means you have root access. You can type "reboot" and it will reboot your phone, you can't do that without root access.
Thank you for the response. I'm rooted and ready to go!
I think it's been said already but the link in the original post to the android SDK is wrong, it actually points to the su tool instead. The text of the link is correct but the underlying URL is not. Android SDK is at:
Okay, I don't what happened. Everything seemed to have worked. At the last command line: reboot, it restarted the phone. I then downloaded android terminal emulator, typed su and got permission denied. So then I tried to redo everything through command and after I type su, it says permission denied just like in the phone.
Okay, I don't what happened. Everything seemed to have worked. At the last command line: reboot, it restarted the phone. I then downloaded android terminal emulator, typed su and got permission denied. So then I tried to redo everything through command and after I type su, it says permission denied just like in the phone.
So right now, the only things that root access gives us is super-user access in the terminal? How are we supposed to delete the useless apps that come with the phone (Amazon MP3, Facebook...) like this? Do we manually have to rm a specific directory via the terminal?
So right now, the only things that root access gives us is super-user access in the terminal? How are we supposed to delete the useless apps that come with the phone (Amazon MP3, Facebook...) like this? Do we manually have to rm a specific directory via the terminal?
I'm having problems with the driver update part on windows 7. It says that the drive is already the latest. Do I just continue to the next step or is win 7 just being a pain?
And the SDK Link takes me to su.zip also.
Nevermind! su needs to be in the tools folder. and On win 7 the Motorola A855 with the ! didnt show up in device manager untill after i put it in usb debug mode.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Robert>cd c:\android\tools
c:\android\tools>adb push su /data/local
791 KB/s (76232 bytes in 0.094s)
c:\android\tools>adb shell
$ su
su
# mount -o remount,rw -t yaffs2/dev/block/mtdblock3/system
mount -o remount,rw -t yaffs2/dev/block/mtdblock3/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# cd/system/bin
cd/system/bin
cd/system/bin: not found
# cd system/bin
cd system/bin
# mv su osu
mv su osu
failed on 'su' - Read-only file system
#
Followed your instructions, but my OSU permissions weren't the same. SU was OK though. So you might add chmod 6755 osu to the instructions as well for those who's OSU permissions differ from what you've posted.
Is there any reason why I can SU from a terminal and get "access granted courtesy of magicandroidapps.com"
Yet all apps I run tell me I don't have root access? It's like I have root at the terminal but not through GUI apps? Wasup with that?
NEVERMIND, PROBLEM SOLVED.
Apparently the latest droid root technique works. For some reason the original technique (posted above) didn't seem to work. This is what worked for me...
Is there any reason why I can SU from a terminal and get "access granted courtesy of magicandroidapps.com"
Yet all apps I run tell me I don't have root access? It's like I have root at the terminal but not through GUI apps? Wasup with that?
NEVERMIND, PROBLEM SOLVED.
Apparently the latest droid root technique works. For some reason the original technique (posted above) didn't seem to work. This is what worked for me...
I was hoping I'd be able to use my superuser powers to be able to tweak the sqlite database for an app I'm developing rather than having to do the tweaking programmatically.
However I can't find the sqlite3 command for anything either adb shelling or using terminal emulator. All my attempts return "sqlite3: not found".
so I got the cd c:\Android\tools part to work but if I put in adb push su /data local it tells me: 'adb' is not recognized as an internal or external, operable command, or batch file
The gui doesn't run as root, so the apps won't have root access either.
That isn't entirely true. If the root was done correctly, the apps should have root access. At least, that has been my experience. I am currently running Root Explorer, Drocap2, and Backup... all of which require root, and all of which work perfectly.
Quote:
Originally Posted by T0LLPHR33
so I got the cd c:\Android\tools part to work but if I put in adb push su /data local it tells me: 'adb' is not recognized as an internal or external, operable command, or batch file
what am I doing wrong...
what happens if you just type "adb"? Does it bring up a list of commands?
How to Root Your Droid (For Non-Linux/Non-Geeks)
