This guide will walk you through the process of getting your phone up-to-date with the latest rooted rom. The current rooted rom is based on the 2.1 leak kernel. Unfortunately, there is still no solution if you installed the original 2.1 leak.
This guide is only for those who are running either Android 1.5, or who are running the original rooted 2.1 rom.
**UPDATE (3/24/10) Now includes 2.1 Official kernel**
I've put together an all-in-one package. This package includes batch scripts to automate most of the tasks in this guide. If you aren't too comfortable with the command prompt, you might want to try this option. Here is the README file in the package to see everything it will do:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
You can download the all in one root script here: http://www.multiupload.com/B9LOBJRCR3
Instructions: Unzip the file into your \tools\ directory of your Android SDK. Then run install_root.bat, and follow the options in order. MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THIS WON'T WORK!!!!
* If you already installed the rooted 2.1 rom, please skip ahead to section II.
** You need the Android SDK installed and functioning.
You will want to do this process ASAP!! After the original root rom was released, it was discovered it MIGHT have an expiration date. It's unknown if this is 100% accurate, or what will happen if it does expire. Once the ROM expires though if you haven't installed it already and upgraded to our new rom, you may not be able to get root at all until we find a new exploit in 2.1, so GET IN ON ROOT WHILE YOU CAN!! Don't worry though, once you get our new ROM installed, you'll be fine and won't be affected if it does expire. If you fail to upgrade to our new root rom and it expires on you, your phone won't be bricked though don't worry, but you may lose your root opportunity.
A. Pre-requisite: Android SDK
1. Visit this page to download the SDK: Android SDK
2. Install the latest version of Java: www.java.com
3. Extract the .zip file and run "SDK Setup.exe"
4. You will probably need to click Settings and check the box to force HTTP instead of HTTPS.
5. Now click Available Packages. Install the SDK for 1.5, 2.1, as well as the USB Driver package. (to make it easier you can just install every available package, it won't hurt)
6. Put your phone into USB debugging mode: Settings > Applications > Development > check USB Debugging
7. Connect your phone via USB to your PC.
8. Right-click My Computer > Properties, and go to Device Manager. You should see a device with a yellow exclamation next to it, this is your phone (if you don't see it you probably forgot to enable USB debugging mode)
9. Right-click the device, select Update Driver. Browse to your Android SDK directory, and you should see a "USB Driver" folder in it now. If you don't, you forgot to download the USB Driver package when in "SDK Setup.exe". Select the driver in that folder.
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.
11. If you get a Java error, you probably need to add your Java \bin\ directory to your PATH variable. To do this, find the full directory to your Java \bin\ folder, usually similar to C:\Program Files (x86)\Java\<version#>\bin. Right-click My Computer > Properties > Advanced tab > Envorinment Variables. Scroll down, find PATH, click Edit, at the end of the line put a ; followed by that full path. Now try the adb command again.
I. Rooting your phone (the easiest part)
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down + Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands: (MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THESE COMMANDS WON'T WORK! MAKE SURE IT IS ON "CHARGE ONLY")
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
2. Place the file eris21official-root.zip on the root of your sdcard
3. Reboot your phone into recovery mode.
4. Go to Wipe, and do a wipe of data/factory reset, as well as dalvik-cache wipe.
5. Go back to the main menu and select "Flash Zip from SDcard"
6. You should see eris21official-root.zip. Select it. Press the trackball to flash it.
7. That's it! You're now running the latest version of the root rom. You will use the same process in this section most likely to flash future updates to the root rom, so remember how to do this method with the recovery partition.
IV. Questions?
Visit the IRC chatroom: irc.thefuzz4.net, channel #ErisRootHelp
Also, if you encounter any bugs in the new eris_0_2.zip rom, please let me know, or join the IRC chatroom and tell someone! So far we haven't found any bugs, but they're sure to exist. It's stable though, and everything we've tried works.
If anyone can mirror the ROM files, please let me know.
Thanks to ivan, amon, jcase, and everyone else that helped in making/testing!
Last edited by GrdLock; April 1st, 2010 at 02:38 PM.
The Following 106 Users Say Thank You to GrdLock For This Useful Post:
am I reading this right.. there "should" be a new rom today? I have not rooted yet.... waiting for a more stable rom... if there is a new one.. do we know if it fixes anything?
The Following User Says Thank You to etherguy For This Useful Post:
am I reading this right.. there "should" be a new rom today? I have not rooted yet.... waiting for a more stable rom... if there is a new one.. do we know if it fixes anything?
If i remember correctly, you must have rooted ROM and recovery before the new ROM is released.
That is completely understood. I have the rom sitting on my phone as we speak. I just didn't want to pull the trigger until I knew there was a more stable ROM out there.
I thanked you because you are providing such valuable info to those who want to root even though I am excluded from the list of those who are able at this point. Come on 2.1 root! Seriously...haven't been able to go into the channel today...are there concerted efforts being made to root 2.1 or are most concentrating on making ROM's for rooted 1.5?
A couple people are working on the 2.1 leak issue. I'm not sure the status though because a lot of the effort is being done behind closed doors, since most of the devs have 2.1 leak phones themselves.
Thank you thank you thank you Grdlock. You are awesome and providing a valuable service for free. Keep it coming. I wish there was a way I could buy you a beer.
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 get the amazing error when I try to connect through command prompt.
*daemon not running, start is now *
*daemon started successfully*
error: device not found.
Also, I am rooted!
__________________
Galaxy Nexus || HP Touchpad
|Android Open Kang Project|
Are you on the PB00IMG.zip step? It will search for a bunch of images, won't find them, then it'll load the PB00IMG and ask you to update, you say yes.
Are you on the PB00IMG.zip step? It will search for a bunch of images, won't find them, then it'll load the PB00IMG and ask you to update, you say yes.
thats what i figured.. i was just following the steps to the t, and didnt see that one
ok, now I am trying to do the recovery image, and when i do
adb push recovery.img /sdcard
I get a failed to copy, read only file system
what am i doing wrong?
i had the card mounted, I should have known. that was a doh moment. so now when i do
adb shell chmod 755 /system/bin/flash_image
a lot of info goes flying by and then when i do the last step it says permission denied..
btw thanks for your patience.. I am usually good with computers. this is my first time getting into the rooting world. learning as i go along.
New problem: when I want to do step 3 in the recovery image installation, I am having problems in getting error saying:
can't stat "recovery.img" does not exist.
I have unzipped Recovery.zip into the \tools\ twice now and it still does not recognize that the file is there...But when I run the command prompt to open just that file (without the adb command) it recognizes that the file is there, but windows cannot open it.
Confused. Any explanations would be very helpfull. And if this is timed I'm not liking the fact that I'm on a clock to get the new rom installed when I can't get past step 2.
Last edited by Thats; March 18th, 2010 at 03:09 AM.
New problem: when I want to do step 3 in the recovery image installation, I am having problems in getting error saying:
can't stat "recovery.img" does not exist.
I have unzipped Recovery.zip into the \tools\ twice now and it still does not recognize that the file is there...But when I run the command prompt to open just that file (without the adb command) it recognizes that the file is there, but windows cannot open it.
Confused. Any explanations would be very helpfull. And if this is timed I'm not liking the fact that I'm on a clock to get the new rom installed when I can't get past step 2.
Same thing here. recovery.img no such file or directory. BTW it is a lower case "r" in the file name.
EDIT ***************************
Got it to work. Good thing my computer smarts (hah) goes back to DOS daze. Even though I have my tools folder "pathed" I had to change directories within the command prompt into the tools directory then use the push commands ... worked like a charm.
Last edited by gluis; March 18th, 2010 at 10:19 AM.
"8. Right-click My Computer > Properties, and go to Device Manager. You should see a device with a yellow exclamation next to it, this is your phone (if you don't see it you probably forgot to enable USB debugging mode)"
Debugging is on, but still no yellow exclamation next to an icon.
Should I just right click the "My HTC" in "Android USB Devices"?
"8. Right-click My Computer > Properties, and go to Device Manager. You should see a device with a yellow exclamation next to it, this is your phone (if you don't see it you probably forgot to enable USB debugging mode)"
Debugging is on, but still no yellow exclamation next to an icon.
Should I just right click the "My HTC" in "Android USB Devices"?
That's what I did and it worked just fine. Might have something to do with if/how you installedyou phone onto it computer previously.
The Following User Says Thank You to Ruh17 For This Useful Post:
This is made with OTA updates disabled, Amazon.com uninstalled, and a few apparent bug fixes. It seems stable, my Facebook contacts synced, Google login bug existed still (for me), and everything so far (including WiFi) seems to work.
Edit: Oh, and WiFi being fixed (dhcp, rather) is part of this.
Last edited by pkopalek; March 18th, 2010 at 02:56 PM.
The HTC Droid Eris launched for Verizon Wireless on November 6th in part as the carrier's first Android Phone. However it was overshadowed by the other member of the inaugural Verizon Droid duo - the Motorola Droid. The Droid Eris might look fa... Read More
GUIDE: From stock 1.5 to the latest root 2.1
