Have a big problem. Hoping you can help. Had eris flashed to cricket already and it worked with calls and text only. Took it to kid that got web/mms enabled. But phone did not work. Took it back to him, fixed the phone part. But he could not get mms working. And there I am today. Now, I have ran some things that say that it needs permissions. I ran your Eris Root for Dummies! and I get the same error when I run the gscript file. It won't install. I'm one more 'try this' away from ripping my white hairs out. Please HELP!!! grrrr
Does this method work with evil Eris 3.0? I've been wanting and trying to root to it on my Alltel HTC hero.
EDIT: I get a screen stating "ERROR: This script is only for the device: desirec Your phone is reported to be a : heroc" when I attempt script root_part1
Last edited by tomcat025; July 27th, 2010 at 08:02 PM.
Been almost a week with my phone rooted through this process. Other than having to try and customize everything all over, it has been an excellent experience! Finally have swype and wifi hotspot enabled! This phone is several times faster than before, and is a lot more fun! When its time to upgrade come next March, Ill have to be sure that I can easily root my new phone again.
Have a big problem. Hoping you can help. Had eris flashed to cricket already and it worked with calls and text only. Took it to kid that got web/mms enabled. But phone did not work. Took it back to him, fixed the phone part. But he could not get mms working. And there I am today. Now, I have ran some things that say that it needs permissions. I ran your Eris Root for Dummies! and I get the same error when I run the gscript file. It won't install. I'm one more 'try this' away from ripping my white hairs out. Please HELP!!! grrrr
becki023,
Sounds like you've had quite a time with this. We're going to need a little more information from you about exactly what problem it is your're having. Don't know anything about Cricket (another carrier, I presume). Post some more details and maybe someone will have a suggestion for you. Thanks.
Does this method work with evil Eris 3.0? I've been wanting and trying to root to it on my Alltel HTC hero.
EDIT: I get a screen stating "ERROR: This script is only for the device: desirec Your phone is reported to be a : heroc" when I attempt script root_part1
tomcat025,
Yep...erisuser1 added that check to make sure you didn't try to install the Eris-specific version of Amon_RA's custom recovery partition on a non-Eris device.
Sounds like you've had quite a time with this. We're going to need a little more information from you about exactly what problem it is your're having. Don't know anything about Cricket (another carrier, I presume). Post some more details and maybe someone will have a suggestion for you. Thanks.
Details eh? Here goes:
I followed all the steps. Downloaded the appropriate files, installed ES file explorer as well as GScript. I went through and prepped each script as told in the sections prior to and including fig: 28. I got to fig:29 and got the message detailed in my last post.
I followed all the steps. Downloaded the appropriate files, installed ES file explorer as well as GScript. I went through and prepped each script as told in the sections prior to and including fig: 28. I got to fig:29 and got the message detailed in my last post.
There's lots and lots of ROMs out there. Which one is best is subjective (I prefer Ivan's Eris Official 1.0). You'll have to read through the forum threads for various discussions about the ROMs that folks have tried. You can also read/research on the XDA forums where the devs hang-out and host their main threads about each ROM: Droid Eris Android Development - xda-developers
Happy ROM hunting!
Here's another for dummies question: Installing a new ROM...I would just do the latter part of this process from AFTER obtaining root, since I've already rooted the phone, right? And just download and install the .zip ROM of my choosing, correct? Is rooting kind of like formatting your hard drive?
Here's another for dummies question: Installing a new ROM...I would just do the latter part of this process from AFTER obtaining root, since I've already rooted the phone, right? And just download and install the .zip ROM of my choosing, correct? Is rooting kind of like formatting your hard drive?
Well, I wouldn't necessarily compare it to formatting a hard-drive .
Rooting is gaining root (super-user) access, so you can do things that VZW / HTC don't necessarily want you to do.
The Eris has been a very tough nut to crack, rooting-wise, since there was no "root-only" exploit discovered.
This thread/method uses utilizes an exploit that allows you to install a custom recovery partition by gaining full-access to the recovery partition (i.e., to write over the stock recovery with a custom one). This is what the first parts of this thread does.
This custom recovery is then used to flash a custom ROM, which has root / superuser access already baked-in to it. This is what the "Finishing Up" part of the instructions in the first post does.
There are some other scenarios, but it might muddy the waters at this point .
Does that help and/or make sense?
Last edited by scary alien; July 27th, 2010 at 10:07 PM.
Sweet. I recently lost my Eris, and was worried that my replacement wouldn't be rootable if it came with 1.49. Don't know what I would do if I couldn't root.
Well, I wouldn't necessarily compare it to formatting a hard-drive .
Rooting is gaining root (super-user) access, so you can do things that VZW / HTC don't necessarily want you to do.
The Eris has been a very tough nut to crack, rooting-wise, since there was no "root-only" exploit discovered.
This thread/method uses utilizes an exploit that allows you to install a custom recovery partition by gaining full-access to the recovery partition (i.e., to write over the stock recovery with a custom one). This is what the first parts of this thread does.
This custom recovery is then used to flash a custom ROM, which has root / superuser access already baked-in to it. This is what the "Finishing Up" part of the instructions in the first post does.
There are some other scenarios, but it might muddy the waters at this point .
Does that help and/or make sense?
So, basically, I would start again from step 1 if I decide to try a different ROM, right? So far, I like Evil Eris just fine. But of course, that might change.
So, basically, I would start again from step 1 if I decide to try a different ROM, right? So far, I like Evil Eris just fine. But of course, that might change.
Well, you only do the first part (posts #1 through #3) once for setup/preparation and to install the custom recovery partition.
Before you do this step, you would have selected and downloaded the (presumably new/different) custom ROM and placed it in the top-level of your /sdcard.
This is the lather-rinse-repeat part of rooting if you want. Make sense?
Last edited by scary alien; July 28th, 2010 at 04:48 PM.
The Following User Says Thank You to scary alien For This Useful Post:
I got my eris replaced this morning and i followed the tutorial above. I was Rooting from 2.1 stock. I completed the g script activities of running both part 1 and part 2 scrips. When i boot I see the Amon recovery window. I complete the nand backup, and the wipe but when i try to flash any rom my phone always hangs on the skateboard boot screen for up to 2 hours. I have had no luck with white widow, and suave smush. Any suggestions?
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.
Rooted now from 2.1 OTA to Sense-able 3.1. It took probably 4 hours (moving VERY VERY slowly to make sure to get it right as this was my first root) and now I am all set up again. It truly is like a whole new phone! I will probably try EvilEris soon. Thanks to everyone involved in developing this process. Your work is greatly appreciated!!!
The only thing I have to add is that for my phone to get into the bootloader I had to start my phone holding the volume down button and power. I thought I saw that a few other people reported this. Maybe it has something to do with when your phone was manufactured? I have no evidence of this just an idea.
Can I do this with out installing a custom rom or is a custom rom necessary?
I wanted to post partially to answer jbarcus81's question (because I spent most of my day wondering about that) and also to share my specific experience (all good!) with using this method.
First off thanks to EU1 and everyone here for all the fantastic info. I was a root noob, and this way WAY easy for me. It almost felt wrong that it was so dang easy.
Anyhow, like jbarcus, I didn't want to install a custom rom. Really all I wanted to do was be able to wifi tether. Luckily I read through all of the posts here and learned about the engtools.zip - so I didn't need to mess with a custom rom - really had no interest (yet!) - here's how it worked for me:
I pretty much followed the instructions step by step* until I got to the recovery portion.
Once in recovery, I did do the nand backup (probably not a bad idea).
But, I DID NOT wipe. Totally skipped that step. (I may have opened myself up to some jokes there... whatever)
Then I continued on to the flashing portion, but instead of flashing a custom rom, I just flashed ONLY the engtools.zip (note: once I actually downloaded it, it was called engtools3.zip, but worked just the same).
Rebooted, which didn't take any longer than normal - Rooted, with no custom ROM, just my same ol' eris, but with SU access.
I installed Wireless Tether and am using right now to make this post!
*The ONLY area where I ran into any problems was booting into recovery mode. All of the instructions say to hold Volume-Up and Power, but this did not work for me (and I noticed a lot of frustrated posts on here mentioning the same thing). So, I held Volume-Down and Power, and it worked like a charm. If the instructions ever get revised, you might want to make a note that it may be either Up or Down and if one doesn't work to try the other. Sounds like this was the case for a few people.
Other than that though, too easy. Big thanks to everyone who posted here and all of the developers for helpin' a noob like me enter the world of root. Also, I hope my post maybe helps some folks!
Now, off to see what other doors may have opened for me!
The Following User Says Thank You to mattchee For This Useful Post:
Once in recovery, I did do the nand backup (probably not a bad idea).
But, I DID NOT wipe. Totally skipped that step. (I may have opened myself up to some jokes there... whatever)
Then I continued on to the flashing portion, but instead of flashing a custom rom, I just flashed ONLY the engtools.zip (note: once I actually downloaded it, it was called engtools3.zip, but worked just the same).
Rebooted, which didn't take any longer than normal - Rooted, with no custom ROM, just my same ol' eris, but with SU access.
I installed Wireless Tether and am using right now to make this post!
Two things that I want to confirm from your post as you have done them correctly.
1. Doing a nandroid is always good practice before flashing anything.
2. When flashing engtools.zip you do NOT want to wipe. This allows you to achieve superuser access without losing any data.
I got my eris replaced this morning and i followed the tutorial above. I was Rooting from 2.1 stock. I completed the g script activities of running both part 1 and part 2 scrips. When i boot I see the Amon recovery window. I complete the nand backup, and the wipe but when i try to flash any rom my phone always hangs on the skateboard boot screen for up to 2 hours. I have had no luck with white widow, and suave smush. Any suggestions?
Try booting back into recovery and do another wipe/factory reset along with a wipe dalvik-cache, then reboot.
Before you do this step, you would have selected and downloaded the (presumably new/different) custom ROM and placed it in the top-level of your /sdcard.
This is the lather-rinse-repeat part of rooting if you want. Make sense?
Thanks! You answered my exact question! Perfectly clear now!
Just wanted to says thanks for making this so easy. Also I almost panicked after wiping when I realized I forgot to put my ROM .zip in the sdcard root (it was stills in downloads). Luckily I saw the USB-MS toggle option in the recovery and was able to move it over through windows.
Last edited by smileythom; July 29th, 2010 at 04:04 PM.
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?
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.
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.
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?
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... 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!
The Following User Says Thank You to scary alien For This Useful Post:
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...
Last edited by jbarcus81; July 30th, 2010 at 08:09 AM.
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:
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.
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"
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:
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.
Last edited by scary alien; July 30th, 2010 at 09:52 AM.
The Following User Says Thank You to scary alien For This Useful Post:
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.
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.
BTW I used this method for my first-time root and it was fairly easy. Took me about an hour or so but no real problems.
Now I am running Suave Smush rom with LauncherPro home, overclocked to 807, and awesome battery life. Thanks so much!!
Just wanted to pop in and thank everyone for their input with an extra thank you to Papadroid for helping us get through the issue where it wouldn't boot into recovery.
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:
HBOOT<SEND> FastBoot Mode<VOL UP> Recovery
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:
Android system recovery- Reboot system now- USB-MS toggle- Backup/Restore- Flash zip from sdcard- Wipe- Partition sdcard- Other- Power off------------------------------Build : RA-eris-v1.6.2
Note: the power button (red/green END/PWR) is on the bottom right of the phone: eris-front-bottom.jpg
Last edited by scary alien; July 31st, 2010 at 04:02 PM.
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!
Device(s): Eris+Incredible+boredom and extra cash= Incredible 2
Thanks: 8
Thanked 3 Times in 3 Posts
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?
__________________
I blindly put leaked stuffs on my phone. I regularly regret it. But I keep going.
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:
HBOOT<SEND> FastBoot Mode<VOL UP> Recovery
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:
Android system recovery- Reboot system now- USB-MS toggle- Backup/Restore- Flash zip from sdcard- Wipe- Partition sdcard- Other- Power off------------------------------Build : RA-eris-v1.6.2
Note: the power button (red/green END/PWR) is on the bottom right of the phone: 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
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.
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:
HBOOT<SEND> FastBoot Mode<VOL UP> Recovery
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:
Android system recovery- Reboot system now- USB-MS toggle- Backup/Restore- Flash zip from sdcard- Wipe- Partition sdcard- Other- Power off------------------------------Build : RA-eris-v1.6.2
Note: the power button (red/green END/PWR) is on the bottom right of the phone: 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.
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
The Following 3 Users Say Thank You to erisuser1 For This Useful Post:
Thank you eu1 for the awesome write up. Running Froyo as we speak. Thank you to scary alien as well for talking me down the other day. I was about to pull my hair out over the Nand backup thing. Everything is smooth sailing for me now, and I have you two to thank.
Linking to pirated/illegal software: It's a shame I actually have to touch on this. Don't do it. It will be removed and repeat offenses will result in a ban.
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?
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
.
