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...
sounds like a path problem. if you're not in the directory with adb.exe, you can't type "adb" as it wont be in your path.
Jarek, the ADB method of rooting is way too complex. Why not have them use the NON ADB root/superuser method. It's like 10x easier.
1) update phone with 2.0.1
2) update with the root/superuser.apk exploit.zip
UPDATE: 2009-12-09 NOTE: APPLYING THE ROOT EXPLOIT DOES NOT UPDATE YOUR PHONE TO 2.0.1. PLEASE UPDATE TO 2.0.1 BEFORE APPLYING THIS IF YOU WANT 2.0.1
New exploit zip, including Superuser from CyanogenMod
1) get signed-voles-ESD56-from-ESD20.84263456.zip (md5sum 3af35446905040a3123ec09195299596)
2) get droid-superuser.zip (this file, md5sum e517995a7d1fe233c61df17c7f7c2a63)
3) append this file to the end of signed-voles-ESD56-from-ESD20.84263456.zip
* Windows: copy /b signed-voles-ESD56-from-ESD20.84263456.zip+droid-superuser.zip update.zip
* Linux: cat signed-voles-ESD56-from-ESD20.84263456.zip droid-superuser.zip > update.zip
The md5sum of update.zip will be cf653352967253e99d967498ffd9ce69
4) Copy the update.zip to the sdcard on the phone
5) Boot the phone to recovery mode (hold X and power the phone on)
* You'll get a triangle + exclamation point if done right
6) Apply the update by pressing Volume Up + Camera
If you are asking, then you probably wouldn't want to.
When you find things that bug the crap out of you and you can't change them... then you will know why you might want to root.
I am a girl newb so don't flame me too bad. Will rooting void my warranty? Are there dangers to rooting? Is there any value in rooting if I am not a programmer?
I am a girl newb so don't flame me too bad. Will rooting void my warranty? Are there dangers to rooting? Is there any value in rooting if I am not a programmer?
Gender has nothing to do with anything. I know a ton of girls who are insanely smarter than any of my male friends.
So I thought I was following the directions pretty well but apparently I'm doing something wrong. When I go to install the update.zip file from boot I get an error message. I have tried to install the update.zip file both zipped and un zipped figuring I was just making a stupid mistake but either way I get this same message.
"E: Can't Open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: Failed to open /sdcard/update.zip (No such file or directory)
E: signature verification failed
Installation Aborted"
So I thought I was following the directions pretty well but apparently I'm doing something wrong. When I go to install the update.zip file from boot I get an error message. I have tried to install the update.zip file both zipped and un zipped figuring I was just making a stupid mistake but either way I get this same message.
"E: Can't Open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: Failed to open /sdcard/update.zip (No such file or directory)
E: signature verification failed
Installation Aborted"
Alright, I thought this was gonna be just fine, did everything up to this point, and can't get past it. When I type the cmd in the run, then cd c:\Android\tools and press enter, I get "cannot find specified path" ? What stupid thing did I mess up here?
A day later, I re-did this from step one, and still, "cannot find specified path" when I type the first command? cd c: \Android\tools.
Also when I did the update, at the end, when it said it was done, I clicked "reboot system", it did not reboot itself? Is that correct or no, did I just not wait long enough for it to reboot itself maybe? What am I doing wrong here? Help please.
A day later, I re-did this from step one, and still, "cannot find specified path" when I type the first command? cd c: \Android\tools.
Also when I did the update, at the end, when it said it was done, I clicked "reboot system", it did not reboot itself? Is that correct or no, did I just not wait long enough for it to reboot itself maybe? What am I doing wrong here? Help please.
So, i'm sure you followed the directions verbatim... When you created the Android folder and extracted the android sdk zipped folder to it, another android sdk folder was created within it (unzipped). You have to move the contents of the new extracted android sdk folder (i.e tools, platforms etc etc) into just the Android folder. And move the unzipped "su" file into your tools folder as well. After you have done all that then run your commands and your pc will be able to find the files.
After you do the steps in the first thread is the phone supposed to retain the chmod settings? After I typed the last two lines "sync" and "reboot" and I disconnected the usb cable the phone seems to lose the settings. I was able to edit an xml file on the phone while the phone was plugged in and the adb shell was running but now that file is back to being read only. It seems this rooting only works while your in the adb shell under CMD.
can not get started - type adb push su /data/local and get this: 'adb' is not recognizable as an internal or external command, operable program or batch file. How do i overcome this?
can not get started - type adb push su /data/local and get this: 'adb' is not recognizable as an internal or external command, operable program or batch file. How do i overcome this?
Make sure CMD (command prompt) is set to the directory where adb.exe is. If you extracted the android-sdk-r04-windows.zip to c:\ then adb.exe should be in C:\Android\tools
Go to start, click run, type cmd and click enter then in the command prompt window type chdir c:\android\tools and click enter from there you should be able to get adb push su /data/local to work. Then just follow the rest of the guide.
Hey guys Im pretty new to Android. This might be a stupid question, but when I get my Droid rooted how will I be able to upgrade to 2.1 when it comes out? Will the rooting prevent me receiving updates? or how will I be able to upgrade in the future? thanks..
I have read countless threads on rooting and flashing various cooked 2.1 ROMs and I want to do this very badly but a couple of things are holding me back.
There seems to be several different methods to rooting, some involving just a few steps, while others are much more complicated with more room to screw up. Why are there so many different ways to root and is the end result the same??
There are a number of different 2.1 versions floating around out there. Is one more stable and bug free than another?
I would try it if I fully understood how to back up my current system and restore it in the event of a screwup. I know that Nandroid is somehow involved in this but again the process is described differently in multiple threads.
I am not well versed in Linux, but I do have a computer science degree (from a LONG time ago) and am typically very good at doing this sort of thing. I just like to have a better understanding of what the steps are before I begin rather than just blindly following a cookbook recipe of steps.
Canefan - The reason for all the different root guides is because when we first figured out how to do it we only had access to it through an adb shell, and then we had to use adb to make it local on the DROID. The newer guides with the 2.0.1 update W/ root exploit built in are the best ones to use, and all you need to do is copy the .zip to your sdcard (make sure it is named update OR update.zip if you show file extensions on your computer) then hold x and power when turning your DROID on, when you see the yellow triangle you just hit volume up and half click the camera button at the same time. When you see some options appear use the dpad to select apply update.zip, after it is done you can reboot.
Next step is to get the droidroothelper app which should be in the big 2.1 thread or somewhere on alldroid.org, after you finish flashing everything from it then you can put 2.1 on your DROID, personally I think the first release of it is the most stable, from there you can apply whatever fixes you need to it (keyboard backlight, paid apps, animated wallpapers etc etc). The big 2.1 thread has most of this stuff in pages 4-7, and instructions to fix the keyboard backlight. You will need the Android SDK to use ADB, you use it from cmd which I imagine you know what that is. Do some browsing of the big 2.1 thread and you should find all your answers, anything else shoot me a PM or post in that thread.
__________________ So I'm guessin' there's questions that need addressin' like how he fresh in the adolescence and wreckin em' Rules & Guidelines, Zero Tolerance Policy.
When I go to my Device Manager and look for the A855. The first thing I notice is that there is no "!" next to the name. Then when I go to update the driver and select C:\Android as the folder to browse, it tells me that it is already up to date. Am I doing something wrong here?
EDIT: Nevermind, looks like the phone appears in two different sections under the Device Manager, found the one with the exclamation and successfully updated the drivers. Phone is now rooted
Last edited by thegift_curse; December 26th, 2009 at 11:05 PM.
Reason: edit
I have read countless threads on rooting and flashing various cooked 2.1 ROMs and I want to do this very badly but a couple of things are holding me back.
There seems to be several different methods to rooting, some involving just a few steps, while others are much more complicated with more room to screw up. Why are there so many different ways to root and is the end result the same??
There are a number of different 2.1 versions floating around out there. Is one more stable and bug free than another?
I would try it if I fully understood how to back up my current system and restore it in the event of a screwup. I know that Nandroid is somehow involved in this but again the process is described differently in multiple threads.
I am not well versed in Linux, but I do have a computer science degree (from a LONG time ago) and am typically very good at doing this sort of thing. I just like to have a better understanding of what the steps are before I begin rather than just blindly following a cookbook recipe of steps.
So I was bored yesterday and thought well - I'll just apply the root update and see what happens. So I did ... and nothing bad.
Then I thought, okay now I'll just try to install DroidRootHelper and see what happens. So I did ... and nothing bad.
Then I thought, let me see if I can make a Nandroid backup of my current 2.0.1 system. Easy. Now I'm getting confident.
So yada yada I have 2.1 running on my phone.
Btw, the new Gallery is absolutely sick. One thing that I haven't seen mentioned is that it links to Picasa and pulls in any galleries that you have on PicasaWeb. I clicked the gallery and thought "whoa - where did all of those pictures come from"? It also does automatic face detection if you are adding a picture to a contact from the gallery. The gallery is a really elegant app now. The live wallpapers are very very cool. Voice entry with the screen keyboard works really well. Overall, very impressed.
Last edited by Canefan; December 28th, 2009 at 02:48 PM.
Hi, earlier today I tried to do this from a terminal emulator and after I did
cd /system/bin
mv su osu
cat /data/local/su > su
I got an error, I don't remember exactly, about that location not existing. Then I managed to fat finger my way out of the terminal before I could figure out how to fix it. Ever since then I've had sort of a psuedo sudo if you will. So long as I say su, the terminal doesn't argue with me and pretends to perform an action, but it doesn't actually do the things I tell it to do. I tried removing the terminal from the remembered apps in the super user permissions, but it hasn't asked me to grant it permission again. Anyone have any idea on how to fix this? If not does anyone know if a factory reset would fix it? And would I need to reactivate the phone or anything with Verizon if I did that?
Last edited by odsquad64; December 28th, 2009 at 10:12 PM.
Let me give some more information to see if anyone can help me. After mv su osu, I can't use su because su isn't anything anymore. I can't go in to fix it because I would need su to fix su. I tried to osu instead, but it says I'm not allowed to, specifically "uid 10046 not allowed to su." Is there any way I could get su back without resetting the phone? (Additionally, would resetting the phone to factory default fix this?)
The su command should be stored on your computer under c:\android\tools\system\bin . You also should have downloaded su.zip and should be able to extract that file to said location if needed. If you have the superuser permissions app icon on your phone try running it while going through the steps it may prompt you to authorize the changes at some point. Check the box on the prompt and OK it.
Another option is to download an app called droidroothelper and install it on the phone. It will give you a graphical UI with buttons to mount mtdblock3, su, chmod, etc.
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.)
.....
I can not get these drivers to load on my W7 64bit machine -- any ideas? I point to the folder, which contains:
Im running Win7 x64 and when I mount my droid and look in device manager, I try to update the driver with the usb driver file, but it says windows cannot find the necessary drivers?
its an AMD 6000+ x2 processor btw
I followed everything, drivers installed, update.zip applied, and when i go to enter in the commands, it doesnt recognize them. On the first command, it says the path could not be specified, and all the rest it says are invalid. Whats wrong?
I followed everything, drivers installed, update.zip applied, and when i go to enter in the commands, it doesnt recognize them. On the first command, it says the path could not be specified, and all the rest it says are invalid. Whats wrong?
When you're in CMD (command prompt) make sure it's pointed to the right location. Typically it defaults to C:\Documents and Settings\yourusername>
Determine where the \Android\Tools directory is and then point CMD to that location.
were you able to install the update.zip before? should only have to install it once. Here's a tool called DroidRootHelper, it's actually meant for putting the unofficial android 2.1 OS on the Droid so it has a lot of features that aren't needed for just rooting but it can be used for rooting. instead of typing the strings into the ADB shell via command prompt DroidRootHelper lets you click buttons to perform the same actions.
BTW: Android 2.1 OS official for the Droid and Droid Eris is rumored to be released on the 22nd so you may want to wait until that update is pushed OTA before rooting your phone.
were you able to install the update.zip before? should only have to install it once. Here's a tool called DroidRootHelper, it's actually meant for putting the unofficial android 2.1 OS on the Droid so it has a lot of features that aren't needed for just rooting but it can be used for rooting. instead of typing the strings into the ADB shell via command prompt DroidRootHelper lets you click buttons to perform the same actions.
BTW: Android 2.1 OS official for the Droid and Droid Eris is rumored to be released on the 22nd so you may want to wait until that update is pushed OTA before rooting your phone.
Im running 2.0.1, the recovery screen says rooting your phone, installation complete, then it reboots. I havent entered any commands into any program, but i thought it was successful. Then when i go to better terminal emulator, it says su: uid 10090 not allowed to su. What should i do? It would say something like no su detected before this, so i know something has happened. I dont have busybox or any program like that on my phone.
Sorry, I didn't clarify, I meant what OS are you running on your computer.
So you're using a terminal emulator on the Droid instead of ADB Shell from command prompt?
Another question, under apps menu is there an app called Superuser Permissions?
I've personally never used a terminal emulator on my Droid so I'm not clear on whether that method will work especially since in the guide on the first post you get the su.zip file thus when you're running ADB Shell in command prompt mode and you type su you're actually using the su file from the PC not the phone.
Sorry, I didn't clarify, I meant what OS are you running on your computer.
So you're using a terminal emulator on the Droid instead of ADB Shell from command prompt?
Another question, under apps menu is there an app called Superuser Permissions?
I've personally never used a terminal emulator on my Droid so I'm not clear on whether that method will work especially since in the guide on the first post you get the su.zip file thus when you're running ADB Shell in command prompt mode and you type su you're actually using the su file from the PC not the phone.
Ok. Im running windows vista ultimate 64 bit. I never typed in anything into any program yet. No there is not. I thought that to check if your rooted you do type su from the terminal emulator on the phone.
The Motorola Droid - the first ever Verizon Android Phone - exploded onto the mobile market with an incredibly successful ad campaign that brough Android to the masses. With a huge and vibrant touchscreen, solid metal body, full QWERTY keyboard, 5M... Read More
I can make money grow on trees!
