• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Guide(s) to EVERYTHING Root related! Updated for 2.1

@ dren, bryanc1, and resqgirl911

You'll need to read and prolly won't get to see the neat pictures, but if you follow these instructions, you'll be good to go and shouldn't be bothered with anyone's inability to pay their bills. :D

Most (if not all) of the links are down on the page, so an alternate location for your update.zip can be found by clicking HERE.


I tried using the file update.zip from the link, but it's not working. All I am getting is this:

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.

The file was on the sd card because it said it found it, but it won't install. Am I doing something wrong? PLEASE HELP!
 
Upvote 0
Had the phone for a total of about 6 hours so far...

Successfully rooted and backed up with recovery.99.3b
also flashed the new baseband update.

Thanks for the guides!

Might want to check the update section instructions for SBrecovery. they didn't work for me as written, but some trial and error got it done.

Now I'm off to install nexbeast and overclock.
 
Upvote 0
i have rooted and downloaded SDK. when i get to the point of typing ADB to test, it says adb is not recognized as an internal or external command, operable program or batch file. in cmd prompt i can get the directory right, i just cant succesfully send adb command

got it, no matter how i copied couldnt get it. put cmd in address/directory bar (vista) worked like a charm
 
Upvote 0
I tried following the steps to root my phone and was able to get all the way up to the recovery portion of the Steps.

After I chose apply sdcard:update.zip I got this message:

E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Installation aborted.

I manually did a 2.1 update a week ago FYI.

Any help would be greatly appreciated.

Thanks.

 
Upvote 0
I tried following the steps to root my phone and was able to get all the way up to the recovery portion of the Steps.

After I chose apply sdcard:update.zip I got this message:

E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Installation aborted.

I manually did a 2.1 update a week ago FYI.

Any help would be greatly appreciated.

Thanks.


You're trying to root your phone but that's not gonna happen with the 2.1 update on it. You have to go back in time to root.

http://androidforums.com/all-things-root-droid/47349-now-you-can-live-without-fear-bricking.html

That guide will take you through flashing your phone back to stock 2.0.1. THEN you come back here and root your phone.
 
Upvote 0
That makes total sense. So, in time would we all be able to have a rooted 2.1???:D

Probably.

A good portion of the rooted community - I might even go so far as to say most - did not bother getting the 2.1 update in the first place as it is inferior to custom roms. If they did then they also aren't too bothered about having to flash the .sbf to 2.0.1 to go back to root.

I think this means that there's not as much of an imperative to root 2.1 as there would have been to root 2.0.1 or 2.0. I'm sure it will be rooted not too long from now though.
 
  • Like
Reactions: UBRocked
Upvote 0
That makes total sense. So, in time would we all be able to have a rooted 2.1???:D

I just want to clarify that you can have 2.1 once you are rooted (the build is ESE81...and we have that as custom ROMs are being made using the OTA build). There are modified versions of the 2.1 update (ESE81) that allow you to keep root, you just can root when you are on the stock 2.1 OTA from Verizon...make sense?
 
Upvote 0
I am trying to follow the guide. I downloaded the SDK software. I extracted busybox to the tools folder. I get in the command prompt, cd to the right path, enter in ADB and get the list of commands. The first time I enter the first line of commands "adb push busybox /data/local/busybox", I got this message "* daemon not running. starting it now * * daemon started successfully * error: device not found, then after that I attempted the same command 3 more times each time receiving "error: device not found", I then tried ADB and hit enter and received the command list again. I attempted to type in the "adb push busybox /data/local/busybox" and received "error: device not found". Is there something I'm missing? Is this common? Does anyone know of a fix?

I manually updated to 2.1 on Sunday realized I wanted to root my phone, so I rolled it back to 2.0.1 and rooted it yesterday.
 
Upvote 0
The real problem, got to the cd/data/local command then executed says it's not found. I looked in the folder named data on my droid and there are no folders within that folder, as in no 'local' folder...but when i pushed the busy box to the droid it says 1505 Kb/s as if the push was successful...what should i do?

The problem has been solved for some reason i had to enter cd /data then cd /local in order for the command to take. Thanks obelisk79 [shouting from the mountain tops].
 
Upvote 0
"i am unable to go to su in command prompt. I have done everything before that..... I pointed it to the tools area, the tried to go into su, but it said access denied.... any ideas why? any help would be really appreciated. "


It might be that when you entered the 'su' command in your computer, that you didn't accept it on your phone. When you enter the 'su' command a message box opens up on your phone and if you don't answer yes to that message box it won't allow you to move forward.
 
  • Like
Reactions: Papadroid
Upvote 0
So I went from 2.1, flashed back to 2.0.1 (phone went back to stock), rooted, and then flashed Cyanogenmod.

I was just wondering if I hadn't taken that route, would I have been able to use this update.zip to root my 2.1? Or is it required to go back to 2.0.1 first?

Also, what if my phone wasn't on 2.1 yet. Would rooting with this update.zip delete all of my data and apps?
 
Upvote 0
Im trying to get abd to work but I'm stuck on the part where I enter the tools file path into the command prompt. Ive tried everything I can think of! I have windows xp and my android-sdk-windows folder is on the desktop. I did exactly what the instructions said....

type, "cd \Desktop\android-sdk-windows\tools" then press enter. Everytime, I get the system cannot find the file path specified. Please help?
 
Upvote 0
Having problems installing busybox. First one is when I get to the part where I have to type in:

./busybox

when i hit enter it tells me "permission denied"

I then (just out of curiousity) moved on to the next commands and got all the way to:

/data/local/busybox cp /data/local/busybox /system/xbin

Then I got "permission denied" again! Can anyone help?
 
Upvote 0
I am also having trouble with the ABD route. I've been using the DroidMod guide and am stuck on the first abd shell command. I've tried it while directed in the tools folder and the folder where the su and SuperUser files are, and i even tried putting them in the tools folder, but it just says it could not find the specified destination (or something to that avail). I have SPRecover installed and running and I have a backup made. What am I doing wrong?
 
Upvote 0
adb push busybox /data/local/busybox
Copies the busybox.zip file from your tools folder into the Local Data directory on your Droid.
adb shell
Initiate the Unix terminal emulator so that Unix commands may be sent.
su
Connect as a “substitute user” to gain permissions for the following commands.
cd /data/local
Change to the Local Data directory on your Droid.
chmod 755 busybox
Changes the permissions to the busybox file so that anyone can read/execute but only the owner can write to it.
./busybox
Executes the Busybox shell script.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Readies the mtdblock4 and System filesystems.
mkdir /system/xbin
Creates a new directory called “xbin” in the system filesystem.
/data/local/busybox cp /data/local/busybox /system/xbin
Copies Busybox from the Local Data directory to the newly created xbin directory.
/data/local/busybox cp /data/local/busybox /system/bin
Copies Busybox from the Local Data directory to the System Bin directory.
cd /system/xbin
Change to the newly created xbin directory on your Droid.
busybox ––install .
Installs and executes Busybox in xbin.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
Unmounts the mtdblock4 and System filesystems that are no longer in use.
sync
Synchronizes all the aforementioned commands to the Droid.
reboot
Reboots the Droid
You have now successfully installed Busybox and can now utilize its functionality in future hacks!

I can not get this to work for the life of me. I boot with SPRecovery
Mount /system

Get the first 2 steps done and get a # rather than a $. So when I type in su, it says su: not found

Su is in the same folder as adb, system 32

so I also tried to do it in terminal emulator using this:
http://benno.id.au/blog/2007/11/14/android-busybox

but got to $ adb push busybox /data/busybox/busybox and got the message Permission Denied

I have a rooted 2.1 and overclocked it already so I am pretty sure I haven't messed up in rooting it?

also, after looking into the "data" folder using astro, there is no "local" folder within it?

Have I missed something?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones