• 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!

I followed all steps to the letter, but I get the following:

Performing backup : .............
.....
Error : Run 'nandroid-mobile.sh' via adb!

When trying to Nand Backup using the phone method. Anybody have a clue why this is?

This is during the Nandroid backup. I think we've all gotten this before at one time or another. Try re-running the Nandroid backup...that's what I did and it worked the second time.
 
Upvote 0
Ok.. so I have used this guide and am now using a custom ROM Sense-able 3.1 ... Only issue I'm having is I have installed SetCPU and it doesn't seem to be working because it's not able to get ROOT access? I thought that's what all this has done? Given me root access to the Eris? Did I miss something?

Can you get root with other things? I.e., if you download and install Android Terminal Emulator (free in the Market) and type "su", do you get a "#" (root) or a "$" prompt?

You should be prompted by the SuperUser app asking if you want to allow or deny permission to run for an app seeking root access. Maybe you chose "deny" for setCPU?

You can also download and install "drocap2" (screen capture app). It requires root access to to ru. Try it you and see if you get prompted and it works.
 
Upvote 0
Ok. Thanks scary alien. Hoped I would have caught one of you before I clocked in for work. Will keep trying when I get home and all charged up. I did try it multiple times already, but perseverance is key, right?

Yeah, I've seen others report this same error message, but haven't ever heard of a good explanation for why this happens...:thinking: The only thing I could think of would be a wonky /sdcard (because I think when it happened to me, the nandroid.md5 file that normally gets created in the Nandroid backup folder was not there--implying, to me, at least, that the backup could not calculate / verify the MD5 sum of the backup he just made). I also think there might be a log file somewhere that could be checked, but I don't know exactly where it might be. I'll poke around some tomorrow and see what I can find. Like I said, I just retried mine immediately after it happened, and it worked just fine. Good luck!
 
  • Like
Reactions: jaboda79
Upvote 0
Can you get root with other things? I.e., if you download and install Android Terminal Emulator (free in the Market) and type "su", do you get a "#" (root) or a "$" prompt?

You should be prompted by the SuperUser app asking if you want to allow or deny permission to run for an app seeking root access. Maybe you chose "deny" for setCPU?

You can also download and install "drocap2" (screen capture app). It requires root access to to ru. Try it you and see if you get prompted and it works.

Thanks for the tip.. I downloaded and installed the Android Terminal Emulator and typed "su" .. it went to a black screen with a grey bar at the top that says "SU Request" but nothing is there.. blank black screen...then after a while I get a prompt box that says "Activity SU Request (in application Superuser Permissions) is not responding" I can press Force close or Wait.. Also I have a concern that since some of the ROM's I have looked at are saying "based on the leaked 2.1" is this the official release from OTA updates? Also are the last round of updates included in any of these ROM's? I have asked in other forums with no answers...
 
Upvote 0
Thanks for the tip.. I downloaded and installed the Android Terminal Emulator and typed "su" .. it went to a black screen with a grey bar at the top that says "SU Request" but nothing is there.. blank black screen...then after a while I get a prompt box that says "Activity SU Request (in application Superuser Permissions) is not responding" I can press Force close or Wait.. Also I have a concern that since some of the ROM's I have looked at are saying "based on the leaked 2.1" is this the official release from OTA updates? Also are the last round of updates included in any of these ROM's? I have asked in other forums with no answers...

jbarcus81,

I didn't see anything in the Sense-able thread over at XDA that talked about this issue specifically.

I did a search on the su-request force-close issue and found a couple of things with ideas that might help you:

1. This first suggestion is pretty easy to try/test. Make sure that "USB debugging" is checked (Settings -> Applications -> Development -> USB debugging (checked)). Here's the thread that mentioned this:

http://androidforums.com/all-things-root-eris/63224-superuser-permission-question.html

2. There's a note in this the xtrROM3 thread over at XDA that talks about superuser force-closes. Here's the text from that post:

In case anybody else has this problem the fix is below.

Superuser Permissions program hangs (usually with a black screen or even a force close) at the “SU request” screen?

1-Select Settings > Applications > Development.
2-Make sure that USB Debugging is checked. If not, check it.

If that fixes your problem, you are done. If not:

1-Select Settings > Applications > Manage applications.
2-Find Superuser Permissions on the list. Tap it.
3-Tap “Clear data” and “Clear cache” if they’re enabled.

I don't know if this suggestion is xtrROM-specific...here's the post I got it from: xda-developers - View Single Post - [ROM 7/15/2010] xtrROM3.0.3 [apps2sd,jit,lwp,nav,oc]-Vanilla that embraces HTC

3. I found a post (and the ones right before it in the thread) that is probably the right answer since it fits more in-line with what you are seeing (you also need to have USB debugging set for this one, so the first item above is not all in vain). It says you'll need to, at least once after flashing a new ROM, make an su request adb from your PC. Yeah, this kinda sucks if you chose this rooting method because it doesn't need using adb. Anyway, here's what you do:

- install the Android SDK
- start-up a Windows Command Prompt
- cd to the tools directory of the Android SDK
- type "adb shell" from the Command Prompt
- when you see the "$" prompt, now type "su" and press return
- you should be prompted on your phone again for a SuperUser request--be sure to select "allow"

Here's the post I referenced:

http://androidforums.com/all-things...pps-roms-updated-05-06-2010-a.html#post503496

4. A third option is flash a different ROM that doesn't have this problem. Ivan's Eris Official 1.0 (which I use) is purported to not this this issue (but I don't remember if I had the issue, since I'm sure I had USB debugging enabled and did the "adb shell" / "su" thing early-on). Anyway, here's the devs thread for this ROM:

[ROM] Eris_Official 1.0 Alpha With Controllable Overclocking! [5/9/2010] - xda-developers

You can obtain it from HTC Droid Eris ROM Site in "Ivan's ROM" subdirectory (HTC Droid Eris ROM Site Roms&). Be sure to get the "1.0" version if you do (it does require a wipe before you install per the dev's thread).

Good luck!

edit: I almost forgot your question about "latest round of updates". The devs have started building and/or re-building their ROMs to include the latest July 2010 updates for 2.1. There are a few apparently. This ROM (http://forum.xda-developers.com/showthread.php?t=726467) supposedly has the July patch in it. You'll have to search the XDA threads for others, its kind of hit-and-miss.
 
  • Like
Reactions: smileythom
Upvote 0
Thanks for the tip.. I downloaded and installed the Android Terminal Emulator and typed "su" .. it went to a black screen with a grey bar at the top that says "SU Request" but nothing is there.. blank black screen...then after a while I get a prompt box that says "Activity SU Request (in application Superuser Permissions) is not responding" I can press Force close or Wait.. Also I have a concern that since some of the ROM's I have looked at are saying "based on the leaked 2.1" is this the official release from OTA updates? Also are the last round of updates included in any of these ROM's? I have asked in other forums with no answers...

T2Noobs latest version of plain jane is based off the latest OTA.

http://androidforums.com/all-things-root-eris/115419-rom-plainjanet2-stock-2-1-oc-a2sd.html
 
Upvote 0
I have noticed that some ROMs have other files that need to be flashed after the ROM itself (i.e. White Widow or xtrROM). How do you do this? Do you basically flash the *.zip file over the ROM without wiping the phone? Sorry for the noob question. I need step-by-step instructions.

Yes
1. run a nand backup
2. flash the rom
3. flash the additional zip (like the google apps on for White Widow and suave smush)
4. reboot

When I flashed Suave Smush the first time I still had problems with the google apps so I had to wipe and re-flash both the rom and the google apps zip. This is a good first step if you are having problems after flashing a new rom. Hope that helps.
 
Upvote 0
Same for me!

I'm glad you posted this. I though I had messed up.

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:

Code:
[B][COLOR=blue]HBOOT[/COLOR][/B]
 
[COLOR=red][B]<SEND> FastBoot Mode[/B][/COLOR]
[B][COLOR=green]<VOL UP> Recovery[/COLOR][/B]

4. now press the VOL-UP to select / see Amon_RA's custom recovery

Bottom-line: do whatever works and gets you into recovery :)

P.S. this is what the custom recovery menu looks like:

Code:
[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]

Note: the power button (red/green END/PWR) is on the bottom right of the phone: eris-front-bottom.jpg
 
Upvote 0
Just wanted to thank all for helping, I had the issue where Vol Up - End did nothing.

But by pressing End-Call (green-red) and then selecting Recovery, it booted into Amon_RA's recovery where everything else went as laid out.

Excellent write up... long time reader, first time ROOT.. and it's awesome. OC'd to 710, much better battery life due to SetCPU profiles. Performance at 710 is so much smoother, it just works now!

Running PlainJane 2.1.
 
Upvote 0
My great thanks to the person who did this write up. I also thank the person who found it. I did it over my summer vacation. And being that the evil eris 3.0 seems to be a mimic copy of the stock software, I plan to do this a few times and try different roms.


My only question is if I select the "SU" option, will I have more options in the settings menu?
 
Upvote 0
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:

Code:
[B][COLOR=blue]HBOOT[/COLOR][/B]
 
[COLOR=red][B]<SEND> FastBoot Mode[/B][/COLOR]
[B][COLOR=green]<VOL UP> Recovery[/COLOR][/B]

4. now press the VOL-UP to select / see Amon_RA's custom recovery

Bottom-line: do whatever works and gets you into recovery :)

P.S. this is what the custom recovery menu looks like:

Code:
[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]

Note: the power button (red/green END/PWR) is on the bottom right of the phone: View attachment 8718




I had the same problem. Holding down the power on and vol up buttons wouldn't bring up the Amon stuff. So, I did the Unlockr method

theunlockr.com/2010/03/16/how-to-root-the-htc-droid-eris/

Then, I was able to do the root one root two install and get the Amon screen up. I bet HTC did something to block this in the latest update. Use a good backup program and you retain most of your stuff and settings. I then flashed it with one of these kernals to get overclocking.

forum.xda-developers.com/showthread.php?t=679102

Kind of dumb for me. After all the time I wasted I just should've slapped a version of froyo on there. I just wanted the phone a bit faster. Hated when it stalled and locked on me when texting/making calls and having anything else runnings. So far it seems really good. The only thing that doesn't seem speeded up is viewing photos. I imagine if I bought a better flash card that would help.
 
Upvote 0
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:

Code:
[B][COLOR=blue]HBOOT[/COLOR][/B]
 
[COLOR=red][B]<SEND> FastBoot Mode[/B][/COLOR]
[B][COLOR=green]<VOL UP> Recovery[/COLOR][/B]

4. now press the VOL-UP to select / see Amon_RA's custom recovery

Bottom-line: do whatever works and gets you into recovery :)

P.S. this is what the custom recovery menu looks like:

Code:
[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]

Note: the power button (red/green END/PWR) is on the bottom right of the phone: View attachment 8718



Man, I wish I had seen this yesterday. Would have been much easier if this had worked. I restarted my phone at least 15 times holding that damn vol up and power button. Would've saved me hours if I could've tried this.
 
Upvote 0
Wanted to stop in here and give a big shout out to Scary Alien and Papadroid for all the support they have given to folks that used this method and then had questions. I started to read through all the posts last night, and got exhausted trying to take it all in... and was amazed at the detailed responses that people got.

You two have given selflessly a bunch of your time to help out perfect strangers - for nothing in return. I hope those folk appreciate what you've done for them.

You rock.

+1000
 
Upvote 0
Okie, I'm having a small issue of storage space....or lack thereof. It's important to note that IRL, I am a major packrat of the "I might need that!" sort. So, I'm disinclined to delete things. I see on xda that there is an Apps2SD. Will that help my storage problems? Is there anything special to know about using Apps2SD? Is there a ROM that includes Apps2SD already? Or will I need to install it on its own?

~Amy~
 
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