yes my is hero !
right now im stuck at accessing the recovery page. The red triangle just appear wheneven i press off + home button. Does anyone how do i go about solving this problem?-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Universal Eris Root for Dummies!
- Thread starter erisuser1
- Start date
-
- Tags
- htc droid eris
yes my is hero !
right now im stuck at accessing the recovery page. The red triangle just appear wheneven i press off + home button. Does anyone how do i go about solving this problem?
yes my is hero !
Nehneh,
You'll need to visit the Hero root forums (Hero - All Things Root - Android Forums) and post a question or two for those fine folks-- you are currently in the HTC Droid Eris root forums.
Check out the http://androidforums.com/hero-all-t...ting-guide-updated-13-06-gmt-12-oct-10-a.html that Xyro published.
I'm sure there's someone there than can guide you with Hero-specific knowledge.
Good luck and cheers!
Houstatlanavegas
Well-Known Member
ok i downloaded evil eris and nothing seems to work right and i also downloaded the apps.zip file too... is there anything else i need to do cause everything is force closing PLEASE HELP
did the 1 click eris method, worked on mine, then my girl's got to the recovery step and her trackball only scrolls right, so i can't scroll down to flash, is there anything i can do maybe a different recovery method that has flash at the top choice or something, or a way to fix the trackball
Houstatlanavegas,
Don't have much experience with Evil Eris (fairly old ROM by the way), but did you do both wipes before flashing: Wipe data/factory reset, and Wipe Dalvik-cache?
This might explain the force closes.
trybal057,
Check out this thread to see if it will help with your trackball issues:
http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
scary alien, thx for reply but i just ripped out the ball and poked the button on the bottom, the thing is on the left if holding phone upside down, so you push it to that side, if the roller thing breaks (as mine did), just put the needle in there and poke it, ..... on a lighter note, can i get a good link(s) explaining ROMs and what they entail, and what i can do now that its rooted?
oh yea, how do i enable security on wireless tether?
Glad you got a good trackball workaround (first I've heard of someone actually popping it out, lol).
Well, we really should keep this thread focused on its main purpose, so its not proper thread etiquette to address all of your question here. But there is lots of good info in the Eris root main stickied thread:
http://androidforums.com/eris-all-t...ed-18-november-2010-10-47-am-central-u-s.html
Also, check out these threads over at XDA:
Droid Eris Android Development - xda-developers
Droid Eris Q&A - xda-developers
You'll certainly be able to find answers to your questions or a good place to start a new thread.
Cheers and good luck!
lol, I think folks are just letting go of VOL-UP too soon? I've seen this a lot, so its common, but I think its just a matter of releasing VOL-UP too early:
FWIW, when I boot into custom recovery, I:
1. power-down the phone
2. press and hold VOL-UP
3. press the power (red/green END/PWR) button (still pressing VOL-UP)
4. release the power (red/green END/PWR) button (still pressing VOL-UP) when I see the phone powering-up
5. finally releasing VOL-UP once I see Amon_RA's recovery menu
edit: If the above doesn't work, then try (thanks to those that had issues and posted this):
1. power-down the phone
2. press the VOL-DOWN button AND the power (red/green END/PWR) buttons simultaneously
3. you should then see the normal "HBOOT" menu with two choices:
4. now press the VOL-UP to select / see Amon_RA's custom recoveryCode:[B][COLOR=blue]HBOOT[/COLOR][/B] [COLOR=red][B]<SEND> FastBoot Mode[/B][/COLOR] [B][COLOR=green]<VOL UP> Recovery[/COLOR][/B]
Bottom-line: do whatever works and gets you into recovery
P.S. this is what the custom recovery menu looks like:
Note: the power button (red/green END/PWR) is on the bottom right of the phone: View attachment 8718Code:[B][FONT=Courier New][COLOR=green]Android system recovery[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- Reboot system now[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- USB-MS toggle[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- Backup/Restore[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- Flash zip from sdcard[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- Wipe[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- Partition sdcard[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- Other[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]- Power off[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]------------------------------[/COLOR][/FONT][/B] [B][FONT=Courier New][COLOR=green]Build : RA-eris-v1.6.2[/COLOR][/FONT][/B]
hey guy, i am trying to root my Eris with 'erisone010.apk' and cannot figure out how to get it on the phone in the proper places! When I start up the phone with the downloaded and unzipped file on the sd card and internal memory, I get the fastboot and recovery screens and press vol down for recovery but all i get is a picture of the phone with a red exclamation mark! Please help! I cannot stand the lag on this phone and need to root it to overclock it!
voit1984,
First off, welcome to Android Forums.
Second, you have mixed your rooting-method threads here a little bit. You are in erisuser1's Universal Root for Dummies thread but you are talking about jcase's 1-click universal root application (which also has it own thread (http://androidforums.com/eris-all-t...is-app-apk-no-pcs-no-scripts-needed-easy.html)). The .apk suffix denotes an Android application, so its not a custom ROM or installable update.zip-type file.
No worries though, let's see if we can get you straightened-out a little bit here.
So, since you've already got the 1-click app, let's work with that. Firstly, do not unzip it (there's not much you can do with an unzipped .apk file other than poke-around).
Download and launch Astro File Manager (or a reasonable facsimile) and navigate to where you have the erisone010.apk file and short-press that file name. You should be prompted with a pop-up window that has an option "Open App Manager"; press that button. You might be prompted with something that tells you that you have to enable / allow non-market apps from being installed (go to Settings -> Applications -> make sure the "Unknown Sources" checkbox is checked; then return to where you were in Astro). The app manager should give you the option to install the application.
Now that you got the application installed, I'll direct you go the 1-click thread (i.e., the link that I posted above) to follow the instructions in there. Just follow the instructions and you'll be fine. Please note that when step #3 tells you to reboot, that means power your phone off and then back on. When you do, you'll have Amon_RA's custom recovery installed and you can finish your rooting activities from there.
Good luck and cheers!
By the way, you are encouraged to read through this thread that you have posted in. There is no better set of instructions for teaching one about the typical steps involved in rooting, making Nandroid backups, flashing ROMs, doing the wipes, etc.
Just wanted to say thanks for the instructions. I've been putting off rooting my Eris for some time. Even though I'm technically adept, I can't really afford to replace a brick, just in case. 
This method was quick and easy and I'm now happy running KaosFroyo V39. It's like having a new phone!
This method was quick and easy and I'm now happy running KaosFroyo V39. It's like having a new phone!
I read a lot about rooting the Eris and wasn't sure if I really want to try. But well, I finally had enough and tried it today. And thank you so much, it worked ... just now start to redo my apps and everything!
Thanks for that detailed walkthrough, you really did a good job
Just wanted to say thanks for the instructions. I've been putting off rooting my Eris for some time. Even though I'm technically adept, I can't really afford to replace a brick, just in case.
This method was quick and easy and I'm now happy running KaosFroyo V39. It's like having a new phone!
Just rooted and installed my first ROM. All thanks to this thread, everything went smoothly. Much appreciated! Eris runs MUCH better now.
All,
Be sure to also click the "Thanks" button on one of erisuser1's first posts in this thread if you haven't already done so -- your posts of thanks I'm sure are also much appreciated, but I'm sure erisuser1 would also appreciate the "Thanks" too for all of his past and continued contributions to AndroidForums and the Eris root threads in particular.
Cheers!
blakiexcharles
Lurker
looking forward to using this as soon as my phone comes from UPS.
funkymusic
Lurker
Yeah. I got the same error and I'm currently running koasfroyov39. And I have the Droid Eris. I don't know what to do....
funkymusic,
Are you trying to re-root? (you already have KaosFroyo v39, so are you attempting to re-install the custom recovery for some reason?).
P.S. Welcome to the AndroidForums!
funkymusic
Lurker
funkymusic,
Are you trying to re-root? (you already have KaosFroyo v39, so are you attempting to re-install the custom recovery for some reason?).
P.S. Welcome to the AndroidForums!
I am trying to get root. I was to believe I rooted my phone but some apps had told me I needed rooted. I have hboot 1.49.0000. So I'm not sure how I got koasfroyo on here but I do and now I need to root. Some help please lol.
Well, if you have Kaos Froyo, you already are rooted...
What problem are you trying to solve (or what issue are you having that leads you to believe you are not rooted)?
funkymusic
Lurker
I am trying to run wifi tether and it keeps telling me I news root. I just don't know what exactly is wrong.
If you launch the SuperUser app from your app drawer (this is one good indication that you are rooted too), do you see an entry for the wi-fi tether app and is its status set to "Allow" (my entries have a little green dot on the right-hand side (indicating "allow", I believe)?
When I launch my wi-fi tether app, I told it "deny" and there is now a red dot with a dashed white line in it.
Perhaps someone told the SuperUser app "deny" and had the "Remember" checkbox checked... If this is indeed the case, simply long-press that entry and tell the SuperUser app to "allow" and then retry your wi-fi app.
You can also verify that you are root by installing the Android Terminal Emulator (free in the Market) and typing "su" at the "$" prompt and hitting the "carriage-return" softkey (if the keyboard doesn't come up when you first launch it, you can long-press the menu key to bring-up the keyboard). This should make the prompt turn into a "#" if you are indeed rooted and have Kaos Froyo installed.
The pop-up from Superuser only lasts for a short period of time (I suppose to prevent "application not responding" messages); if you don't click on it, it automatically defaults to "deny". Gotta watch the screen carefully the first time you run an app that needs root!
I'm sort of fuzzy on the details, but there have been recent dev ROMs that had pre-installed versions of WiFi Tether that didn't work correctly.
For the longest time, I have been using an older .apk ("wireless_tether_2_0-pre10.apk") from the Android WiFi Tether Project. It looks to me like they have moved on to platform-specific versions, but my old copy seems to still be working (CELB Froyo 4.1) - just tested it right now.
cheers
I've been testing some root-only features for my BattMonX app that I wrote for the Droid X (controls the LED light to indicate what the current state of the battery is) and I've had to deal with invoking the "su" program and subsequently the permission request with the SuperUser app. The hard part was dealing with my set-on-boot functionality when you've forgotten to set "remember" checkbox when requested by the SuperUser whitelist (i.e., handling it gracefully without hanging).
Perhaps this was the reason why there is a timeout--i.e., for rooted apps that launch on boot that need to request permission just to prevent the hang ("not responding" behavior) that you proposed?
Sounds plausible to me.
funkymusic
Lurker
Yeah well the app wont recognize root. The superuser