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

Root GUIDE: From stock 1.5 to the latest root 2.1

On Win 7 you have to click Browse my computer, then Let me pick from list. From there click on show all and then click have disk. It works from there.

I just can't get passed the out of memory error on the recovery.
 
Frisco said:
In Windows 7, what happened when you went to the Device Manager, saw the yellow icon in "others," and right-clicked it then selected "update driver?"

It is at that point that we used "browse my computer for driver software," then kept clicking folders until we were at the path to the "usb drivers" folder.. there we saw i386 and clicked it (first try) and it yielded nothing.

We then clicked the usb driver folder itself with the same result.

We then typed in the path, including the name of the driver, "android_winusb.inf," nothing except a message saying "unreachable."

At that point we began our snickering and laughter.. :rolleyes:
Click to expand...

There were USB drivers included in the instructions / download area with Eclips3's Eris Master Application (for root) that I initially used [note: the app is currently down, but the USB drivers are still there]. Not really sure if these were different / better than the stock ones that come installed with Windows... But, I know I did a lot of the same stuff you did too (and I know others have also). There's a whole littany of things to try and double-check...argh!!! :eek:
 
He and I are both getting a little angry.

He called telling me it was "impossible" to download the rooted ROM because of spam and redirect links that are made to look like the download link.

So, I went to the link in the first post and I swear I cannot for the life of me get a download from that link; it continually sends my browser to goofy sites for everything from YouTube to unmentionable places.

Is that file, or one like it, available anywhere now?

Or did the spammers hijack the old link?

Editing in another question, does it matter which ROM to put in his phone at this stage? He did get all the other steps done, but isn't sure if his phone is rooted, "it just started me over," he said. .. says he lost all his settings, etc.. I need for him to show me the phone, but I won't be getting over there for another two days.

Anyway.. let me know.. I'll copy and email your responses to him.
 
Frisco said:
He and I are both getting a little angry.

He called telling me it was "impossible" to download the rooted ROM because of spam and redirect links that are made to look like the download link.

So, I went to the link in the first post and I swear I cannot for the life of me get a download from that link; it continually sends my browser to goofy sites for everything from YouTube to unmentionable places.

Is that file, or one like it, available anywhere now?

Or did the spammers hijack the old link?

Editing in another question, does it matter which ROM to put in his phone at this stage? He did get all the other steps done, but isn't sure if his phone is rooted, "it just started me over," he said. .. says he lost all his settings, etc.. I need for him to show me the phone, but I won't be getting over there for another two days.

Anyway.. let me know.. I'll copy and email your responses to him.
Click to expand...

Yeah, I think I remember the early posts about the availability of the root base ROM doing the spam thing to some people (but not everyone). Let me search for the other download links and try a few. I'll also recompute the MD5 sums and verify that what I download matches what I already have (that I've already verified with others in AF). He should also double-check the MD5 sums on each ROM he downloads (and erisuser1 also advises checking the MD5 sums AFTER you copy the ROMs to the /sdcard to, just to be sure).

I'll re-reply in a few...

Also, the final custom ROM doesn't matter, but the first base root ROM must be the first ROM that you install, so the best thing to do is only download and have the base root ROM around so you don't get it mixed-up with any of the 2.1 leak versions (that would be bad :eek:).

Back in a sec...
 
scary alien said:
Yeah, I think I remember the early posts about the availability of the root base ROM doing the spam thing to some people (but not everyone). Let me search for the other download links and try a few. I'll also recompute the MD5 sums and verify that what I download matches what I already have (that I've already verified with others in AF). He should also double-check the MD5 sums on each ROM he downloads (and erisuser1 also advises checking the MD5 sums AFTER you copy the ROMs to the /sdcard to, just to be sure).

I'll re-reply in a few...

Also, the final custom ROM doesn't matter, but the first base root ROM must be the first ROM that you install, so the best thing to do is only download and have the base root ROM around so you don't get it mixed-up with any of the 2.1 leak versions (that would be bad :eek:).

Back in a sec...
Click to expand...

Frisco,

Okay, here's the scoopage:

Best place to download the base root ROM is Gridlock's site: HTC Droid Eris ROM Site

Navigate to the "PB00IMG Roms" directory.

In there, you'll find the base root ROM (i.e., the ROM you need to install to actually get root / root permissions) called "PB00IMG-root.zip".

Ignore the "PB00IMG-21-official.zip"--this is a 2.1 LEAK (ack!) version 2, apparently. DO NOT DOWNLOAD or INSTALL!

Download / save the "PB00IMG-root.zip" file. You'll also notice the comments with the file name:

"Original root rom. Rename to PB00IMG.zip before using.
MD5: 63eacc5ede3b179f95dc22d8ef585f94"

So, after the download completes, rename "PB00IMG-root.zip" to "PB00IMG.zip". This is the first file that you will transfer to the phone's top directory of the /sdcard.

I re-did this download myself (no spam or viruses from this site!) and checked the MD5 sum against the comments above and my copy of the base root ROM (downloaded long ago). They all matched perfectly (at least to my eyes :)). Here are the details:

Here's the MD5 sum reported from the download location:
63eacc5ede3b179f95dc22d8ef585f94

Here's my MD5 sum of the newly downloaded file:

C:\android>md5sum.exe c:\temp\PB00IMG-root.zip
\63eacc5ede3b179f95dc22d8ef585f94 *c:\\temp\\PB00IMG-root.zip

And here's the MD5 sum of my old copy of the base root ROM:

C:\android>md5sum.exe c:\android\roms\root-stuff\first-root-rom-PB00IMG.zip
\63eacc5ede3b179f95dc22d8ef585f94 *c:\\android\\roms\\root-stuff\\first-root-rom-PB00IMG.zip

And finally, the MD5 sum listed as being needed from this thread's instructions:

63eacc5ede3b179f95dc22d8ef585f94

You might want to find / download an MD5 sum utility (such as Home of the MD5summer). The one I used is an old DOS one that still works okay, so I haven't actually used any Windows GUI-based ones. Okay, that's enough of MD5 sums. :D

So, all this looks good.

Now your friend should be ready for this thread's "I. Rooting your phone (the easiest part)"...assuming the SDK / USB issues have been addressed. After doing step #1, the phone will be rooted, just with a very old, buggy, version of 2.1. This will allow you to continue on and install Amon-RA's recovery image and then install flash a nifty custom ROM of your choosing (Ivan's Eris Official 1.0 w/OC is a good one to start with).

Any questions? Cheers!
 
All right, to heck with this third party stuff..

..I'm rooting mine.

Henry is a great person, a good friend.. I'm feeling bad about just playing this distant of a role on this root thing.. besides, I need to learn about it so I can at least participate in an intelligent discussion about it around here, let alone with him.

Another thing, you've gone to a lot of trouble over this..

..I'll report back when my device is rooted.

..and thank you. ;)
 
I'm moving along, he's stuck on "boot the phone into recovery mode," he can't find a way to do that and I don't know..

..how is that done?
 
Frisco said:
I'm moving along, he's stuck on "boot the phone into recovery mode," he can't find a way to do that and I don't know..

..how is that done?
Click to expand...

If you have Amon's recovery loaded already, you start the phone while holding down Volume Up.
 
Frisco said:
I'm moving along, he's stuck on "boot the phone into recovery mode," he can't find a way to do that and I don't know..

..how is that done?
Click to expand...

Okay! :) So, you must be in step III and you've already downloaded and installed the base root ROM (step I), installed Amon's recovery image (step II).

Step III is actually easy: step II #4 tells you that you can boot into recovery (you've replaced the stock recovery with Amon's custom recovery s/w). So, you can launch into recovery mode from the command line (like you did the other steps in II via "adb shell reboot recovery" OR you can power-off the phone, then manually boot into recovery by holding "volume-up" and "power-on" buttons at the same time. This will take you to Amon's Recovery. (trying to find a picture of it for you...--it should be pretty obvious though).

Anyway, see if that works...sounds like you are almost there...

By the way, you've got the custom ROM placed on your /sdcard right? (also, if you are rooted, you will no longer need the PB00IMG.zip file on your /sdcard (doesn't hurt, you might just want to move it or rename it)).

I'll be here if you need me! Cheers!
 
Holy sh*&!!! Frisco I bust my eris and leave you alone for 2 weeks and your rooting already!????

****checking for signs of the impending Apocalypse****
 
Thanks for all your help, folks.

My device is rooted and I've been exploring the ROMs and the possibilities.

It went well with mine.. the original instructions on page #1 here, along with your posts, Scarey Alien, were enough to get me to thinking about what really goes on at each step. I am grateful to you, and of course to Grdlock.. fine work!

The area with the most bumps (besides that infernal link to Spamville, purportedly the "eris21-root.zip" :rolleyes:) , to me, was the eleven step prerequisite regimen, and that, taken slowly and in order, went fine in the end.

The command line stuff for the recovery image was smooth as snot on a door knob, being a bit of an amateur linux shell freak myself. ;)

Hank's Eris had to be restored and re-activated back to stock 2.1 (he'd received the OTA about 4 days into its release); failures occurred as he attempted to get the rooted ROM flashed.. he came over with his laptop and phone to show me what was going on:

- Windows 7 was unable to see the Eris as anything other than a "phone," as listed in Device Manager but with the report that it was "working properly" and the drivers were not in need of upgrading.

That was resolved, to his consternation, by reminding him of settings > applications > development > debug mode.

- The real problem happened when he pressed volume up and power on following download of the ROM; the phone would do nothing.. it remained dead.. black screen, off, dead, no activity until about a five minute wait with us thinking it was bricked.. but it did power up eventually and went through the procedure as if it were being upgraded from 1.5 to 2.1.

We went over the steps he took at home before bringing the device over to my place, and they sounded normal with the exception of his forgetting about debug mode.

Something happened between the time we ran the recovery image commands and when the phone was powered down (the battery was nearly full).
 
Frisco, congratulations! I must say I was a bit worried when you dropped off the grid last night...not knowing how things were going :eek:. I was hoping that everything was really okay and that you were just reveling in the joys of rooting :). Glad to know everything worked-out in the end.

Welcome to the club! Cheers.
 
Thanks. No worries (nice of you to do that, though) because I did it very slowly.. my method was to look at each step, re-read the following steps, and then search for posts here and mainly at XDA about what problems came up at that point for some and what the resolution was.

It took a lot of time; I did not finish until about 90 minutes past my usual bed time. zzzzzzzz.. :o .. but I could not end my day without having my phone's settings in familiar ground and, of course, my "scenes" set up to my liking.

The actual rooting of the device, once the preparation/research was finished, took me about 30 minutes, the rest of it was configuration.

Struggling with Henry's phone took up some time, as well.. but he ended up with a fresh install of 2.1 and seems happy to not have "fried" it, as he puts it.

My attraction to rooting is rooted (pun intended :D) in my fascination for linux distros, which began a long time ago when I was looking for alternatives to my Windows 95 and its ongoing BSODs and "illegal operation" diseases. RedHat 5.2 was my first foray into the open source world and now here I am in 2010 messing with something like that again on a cell phone! :)
 
Frisco said:
Thanks. No worries (nice of you to do that, though) because I did it very slowly.. my method was to look at each step, re-read the following steps, and then search for posts here and mainly at XDA about what problems came up at that point for some and what the resolution was.

It took a lot of time; I did not finish until about 90 minutes past my usual bed time. zzzzzzzz.. :o .. but I could not end my day without having my phone's settings in familiar ground and, of course, my "scenes" set up to my liking.

The actual rooting of the device, once the preparation/research was finished, took me about 30 minutes, the rest of it was configuration.

Struggling with Henry's phone took up some time, as well.. but he ended up with a fresh install of 2.1 and seems happy to not have "fried" it, as he puts it.

My attraction to rooting is rooted (pun intended :D) in my fascination for linux distros, which began a long time ago when I was looking for alternatives to my Windows 95 and its ongoing BSODs and "illegal operation" diseases. RedHat 5.2 was my first foray into the open source world and now here I am in 2010 messing with something like that again on a cell phone! :)
Click to expand...

+1 on all of the above! :)

I think its humorous that those of us that have been around computers "for a while" ;), proceeded more cautiously than others. Some breezed right through without care or problems and that will only reinforce their next attempts along the same vein.

These phones are really amazing little computers that happen to make phone calls (well, for most people, most of the time :D). Not sure everyone appreciates far and fast things have progressed even in the last five years or so.

I've worked with HP-UX, AIX (currently), and dabbled a long time ago with the RedHat 5.1. The first app that I downloaded was the 'android terminal emulator' so I could go poking around the filesystem on the phone's tiny keyboard (much cooler but much slower than doing 'adb shell' :p).

Anyway, let us know what custom ROM you settled on and why. Thanks!
 
I am trying to root my droid with 2.1 ota 1.47 hboot

I got stuck at the part where it says

10. You can test to make sure everything is working by going to a command prompt, go to the \tools\ directory of the Android SDK, and type: "adb shell". If you see a "$" (or "#" if you're already rooted) sign you're good.
I don
 
deslovedroid said:
I am trying to root my droid with 2.1 ota 1.47 hboot

I got stuck at the part where it says

10. You can test to make sure everything is working by going to a command prompt, go to the \tools\ directory of the Android SDK, and type: "adb shell". If you see a "$" (or "#" if you're already rooted) sign you're good.
I don’t know what a command prompt is??? Where should I be typing this?
Click to expand...

If your computer is a Windows flavor (XP, Vista or 7), just use search and enter "cmd.exe." Click that and it will bring up a black window that is the command prompt.

How did you get the recovery in without the command prompt? You had to run:


  • adb shell mount -o rw,remount /dev/block/mtdblock3 /system
  • adb push recovery.img /sdcard
  • adb push flash_image /system/bin
  • adb shell chmod 755 /system/bin/flash_image
  • adb shell flash_image recovery /sdcard/recovery.img

following download of http://www.sendspace.com/file/jje5xr (recovery.zip).
 
bjanow said:
What?? I seem to recall the "cold day in.." before I root. Very cool, Frisco. Nothing like peer pressure.
Click to expand...

I just thought it was time for the despots of the past to start shivering uncontrollably in below zero blizzards down there in Hades for a few thousand years.. they were likely getting used to the silly flames and brimstone and stuff. :D

No, it's linux, man, it's linux. ;)
 
Frisco said:
I just thought it was time for the despots of the past to start shivering uncontrollably in below zero blizzards down there in Hades for a few thousand years.. they were likely getting used to the silly flames and brimstone and stuff. :D

No, it's linux, man, it's linux. ;)
Click to expand...

Now, you gotta put a 'red hat' on your avatar! :D
 
I should be getting a rootable Eris in the next week or two. I've done all the prep work, this should be fun. I ran Linux for a month or so way back when and DR Dos you know when, so I'm pretty comfortable with command line stuff.
 
bjanow said:
I should be getting a rootable Eris in the next week or two. I've done all the prep work, this should be fun. I ran Linux for a month or so way back when and DR Dos you know when, so I'm pretty comfortable with command line stuff.
Click to expand...

The entire process is fun, bjanow. I particularly enjoyed the commands to get the recovery image at the ready on the card.

I have to admit it was also satisfying to watch the ROM install after the two wipe procedures in recovery mode (I like that menu, that area in general).

When it was time to boot I felt great.

I'm hoping that new rooters will just take their time about it, and first read around so that the steps themselves have meaning rather than just mysterious things to do to get the device rooted; the whole thing is quite intuitive, as all know who've gone through the process carefully.
 
Thanks, I'm excited. Which ROM do you have? Did you overclock and how do you find the root? So many questions...
 
bjanow said:
Thanks, I'm excited. Which ROM do you have? Did you overclock and how do you find the root? So many questions...
Click to expand...

I went ahead and snagged the eris21official-root.zip ROM; I am taking things gradually, in baby steps so that I understand what I'm doing as I go along.

There are a couple of ROMs out there that seem to be getting a lot more attention than others, so I'm nearly sure my device will be seeing a new one at some point, for now, however, I'm fine with this one.

There is an application included called, "Superuser Permissions" which I have opened but found blank.. I'll be searching around to read about that.

I have yet to do anything other than move files around. I'll be installing apps next. I need to look at the overclocking apps and threads posted about them.

Following that I plan to find out how to get rid of the stock applications included that I have no use for.
 
superuser permissions is the program that gives you an interface to deny or allow root access to programs that need it. Its not really a stand alone app

ie when you download an app like say , cache cleaner, when you run it for the first time superuser permission needs to be granted for that app. a screen will pop up giving you the option to deny or allow it permission to run. Thats what Superuser permissions does.
 
You must log in or register to reply here.
Back
Top Bottom