Here's the text: "Amon_RA runs adbd by default, so you can push/pull files to the SD card no matter what OS (even none) is loaded, and the trackball isn't needed for that.
You can also run nandroid-mobile.sh with Amon_RA booted from the command line (from an adb shell) to either backup or restore prior backups. This does not require the use of the trackball; nor does it have any dependency on "USB drivers".
I think that many other entries in the Amon_RA recovery are implemented as scripts, so probably many things you think you can't do (because of a broken trackball) are indeed possible using an adb shell.
It is possible that your trackball assembly got so bolluxed up that it was also responsible for the loss of USB connectivity; in that case none of this matters.
Bottom line, though - even though it won't fix a trackball problem, is that if you have either the 1.49.2000 S-OFF bootloader running on the phone, or Amon_RA, you can "unbrick" from the state you described.
If USB is gone because of a mechanical/electrical issue, things are a bit more grim than that.
bftb0"
I don't know if the above is applicable and/or will take care of this or be helpful with the issues mentioned.
Also, there's a reference in a g1/Dream version of Amon_RA's reciovery to using the CALL-ANSWER key in Amon_RA to select in case you can't do a trackball press (but I don't know if this is supported in the Eris version). This is discussed in this thread: NEW ! Amon RA Recovery v1.6.2 for the g1/dream(12/13) [Archive] - Android Forums
I've also read that plugging-in your USB cable and gently jiggling it might make you be able to select / move from item-to-item in Amon_RA's recovery menu (i.e., because of the proximity of the USB port to the trackball).
Good luck!
Last edited by scary alien; July 21st, 2010 at 11:32 AM.
likewise. Also, approx how much time does this take? Im about to head out on a trip for the weekend and my time is very limited. Dont want to not have a phone if something gets screwed on my end due to myself screwing it up.
And, do I need to have the same SD card in at all times afterwords? I have my stock 8GB one that I'm not using, and like my PSP that I hacked years ago, I had a second SD card for doing the dirty work, while keeping my good one for normal everyday use.
The result this produces is identical to the manual method. It is provided for people who have trouble with PC drivers, command lines, etc. The only thing which is unique about it currently is the fact that you can achieve root without using a PC and the Android SDK tools & driver
It takes longer to read the instructions than it takes to perform them. That said, it does take a while to configure a new ROM from scratch, so I would wait if I were you.
Some ROMs will auto-configure A2SD/APPS2SD if they detect a partitioned SD card. If both of your cards are unpartitioned, it should not matter. It is possible that it matters only if you load a ROM that automatically configures A2SD.
I literally need to run out the door right now, and will be AFK until at least next Monday - fun stuff to do IRL. If any one else wants to pitch in and help out with questions, I would be grateful.
That quote from bftb0 (over on XDA) seems correct, but it applies to Nandroid backups - I'm not sure if there are command line ways to initiate ROM installs from the command line.
I'll have to review the Android sources for recovery.c to see if /sbin/recovery can be invoked from the (Amon_RA) command line to install a ROM from the SD - if it is possible, it might need to be renamed "update.zip" first.
But you are correct that there is a non-trackball possibility... with some amount of work. (And, it also involves the PC, so... ugh).
Help I followed your directions to a T and I got to the last one to flash a new rom and I can't find the rom I downloaded All I have is gscript.zip and pb00img.zip any ideas? Thanks
If you downloaded it using the web browser, it is in the /sdcard/downloads folder... and that is why Amon_RA does not find it, because it only looks in the root folder ("/sdcard") of the SD card.
You can move it to the root folder the same method that was used to move the "gscript.zip" file to the root folder. (Just don't "unzip" it, only move it!)
You can safely reboot your phone and use the normal OS anytime you want after "part2" is done to do things like this. Just go back to the Amon_RA recovery the same way (power down phone, power back up with Vol-Up & End) once you have the ROM file in place.
eu1
OK, now I need to bail (15:54 Zulu 2010.07.21) - see you folks next week.
Last edited by erisuser1; July 21st, 2010 at 10:55 AM.
The Following User Says Thank You to erisuser1 For This Useful Post:
Here's the text: "Amon_RA runs adbd by default, so you can push/pull files to the SD card no matter what OS (even none) is loaded, and the trackball isn't needed for that.
You can also run nandroid-mobile.sh with Amon_RA booted from the command line (from an adb shell) to either backup or restore prior backups. This does not require the use of the trackball; nor does it have any dependency on "USB drivers".
I think that many other entries in the Amon_RA recovery are implemented as scripts, so probably many things you think you can't do (because of a broken trackball) are indeed possible using an adb shell.
It is possible that your trackball assembly got so bolluxed up that it was also responsible for the loss of USB connectivity; in that case none of this matters.
Bottom line, though - even though it won't fix a trackball problem, is that if you have either the 1.49.2000 S-OFF bootloader running on the phone, or Amon_RA, you can "unbrick" from the state you described.
If USB is gone because of a mechanical/electrical issue, things are a bit more grim than that.
bftb0"
I don't know if the above is applicable and/or will take care of this or be helpful with the issues mentioned.
Also, there's a reference in a g1/Dream version of Amon_RA's reciovery to using the CALL-ANSWER key in Amon_RA to select in case you can't do a trackball press (but I don't know if this is supported in the Eris version). This is discussed in this thread: NEW ! Amon RA Recovery v1.6.2 for the g1/dream(12/13) [Archive] - Android Forums
I've also read the plugging-in your USB cable and gently jiggling it might make you be able to select / move from item-to-item in Amon_RA's recovery menu (i.e., because of the proximity of the USB port to the trackball).
Good luck!
thank you I will have to ttyry the trackball jiggle thing and see if it helps. I dont think ma trackball is completely broken, because it wourk everywhere else and I can still mout sd card to comp through usb so thankfully things arnt that bad for me yet lol i do appreciate the help thou and will try this.
ok question is this since I was able to get my phone to look like image 31, am I rooted now? and just not able to do a nand back u, wipe , or flash a rom because of my track ball? cause i was going to go home and try the computer method after work and see if that works. but if the phone is already rooted I wont waste my time.
ok question is this since I was able to get my phone to look like image 31, am I rooted now? and just not able to do a nand back u, wipe , or flash a rom because of my track ball? cause i was going to go home and try the computer method after work and see if that works. but if the phone is already rooted I wont waste my time.
You mean the image that says "congratulations, you have root!"?
No, not rooted yet, if you see image #31 then you just installed a custom recovery partition installed--you just can't flash a custom ROM because of your trackball issues.
You don't actually get root until you install a custom, rooted ROM (i.e., that has the su program and/or Superuser.apk installed).
To test if/when you phone has root capability, download "Android Terminal Emulator" (free from the Market) and type "su". When/if you do indeed see a "#" prompt, then you have root!
Last edited by scary alien; July 22nd, 2010 at 06:31 PM.
The Following User Says Thank You to scary alien For This Useful Post:
You mean the image that says "congratulations, you have root!"?
Yes, if you see image #31 then you have root capability and a custom recovery partition installed--you just can't flash a custom ROM because of your trackball issues. So, your current phone has root capability (you can test this by downloading "Android Terminal Emulator" (free from the Market) and typing "su". If you do indeed see a "#" prompt, then you have root!
ok soooo I downloaded this but when I type su it says permission denied im not meant to root this phone im thinkin
lol
ok soooo I downloaded this but when I type su it says permission denied im not meant to root this phone im thinkin
lol
kamots, I'll admit that I'm a little late to this particular new root method party, lol (I rooted the "old" / original way). I have read through this thread and the companion threads here and over on XDA. But I'm not in position to download the gscript.zip file to examine the scripts in detail at the moment.
I think I remember reading that even wag3slav3's and jcase's methods sometimes took more than one try to get it to "stick". So perhaps someone who has actually done this and needed to run it more than once can verify or share their experience?
You can always do the "su" thing to see when/if you have root.
edit: you'll only see the "#" (root) prompt after flashing a custom rooted ROM.
Last edited by scary alien; July 22nd, 2010 at 06:33 PM.
The Following User Says Thank You to scary alien For This Useful Post:
ok soooo I downloaded this but when I type su it says permission denied im not meant to root this phone im thinkin
lol
I know it's a little confusing but you actually don't have root yet. This process only gives you the ability to obtain root through one of two methods:
1. Flashing a rom with root
2. Flashing engtools.zip that jcase provided which gives your current stock rom root
Unfortunately since you are having issues using recovery because of the trackball, this is preventing you from doing one of the methods above.
The Following 2 Users Say Thank You to Papadroid For This Useful Post:
I know it's a little confusing but you actually don't have root yet. This process only gives you the ability to obtain root through one of two methods:
1. Flashing a rom with root
2. Flashing engtools.zip that jcase provided which gives your current stock rom root
Unfortunately since you are having issues using recovery because of the trackball, this is preventing you from doing one of the methods above.
Ah, Papadroid, thanks! I sort of assumed that these root scripts (at least part 1) did the engtools.zip thing behind the scenes...(which is why I really want to look at them to verify this--I can't do the download here at work ).
When I do Vol- and End I get the typical white recovery screen. I tried this with 80% battery life and also the first two parts with the scripts worked perfectly even to the point where it says 'Congrats you have root' but alas, I cannot get to the black recovery screen for nothing
Disclaimer: Im not especially techy, so you'll have to excuse me, but I am eager to learn. Heres the issue. I am making it all the way to the last step and only have the gscript.zip and pb00img.zip as options (just like Almac), but I instead downloaded the rom on my Mac and placed the whole PlainJaneT2_V2 in the root of the SD card folder. The only part I don't understand about the instructions (and I imagine is what is tripping me up) is in the introduction:
"1) Did you choose a ROM, download it to your SD card, and check the MD5 signature/file length on the copy of the file on your SD card?"
I downloaded the large ROM file, and copied the whole folder onto the root of my SD card, but it simply says PLainJaneT2_V2 and Im not sure how to check for the MD5?
If I have the same problem as Almac, I am sorry for the double post, but I didnt download the ROM on my phones browser like he did.
When I do Vol- and End I get the typical white recovery screen. I tried this with 80% battery life and also the first two parts with the scripts worked perfectly even to the point where it says 'Congrats you have root' but alas, I cannot get to the black recovery screen for nothing
Make sure that you are holding both buttons until it takes you into recovery. If it still doesn't work then try the power/end and call buttons, this should take you to a menu where you can either go to fastboot or recovery, I think. Sorry I'm not as familiar with the Eris as I am with my device, I'm just going off of memory from rooting my wife's eris.
Disclaimer: Im not especially techy, so you'll have to excuse me, but I am eager to learn. Heres the issue. I am making it all the way to the last step and only have the gscript.zip and pb00img.zip as options (just like Almac), but I instead downloaded the rom on my Mac and placed the whole PlainJaneT2_V2 in the root of the SD card folder. The only part I don't understand about the instructions (and I imagine is what is tripping me up) is in the introduction:
"1) Did you choose a ROM, download it to your SD card, and check the MD5 signature/file length on the copy of the file on your SD card?"
I downloaded the large ROM file, and copied the whole folder onto the root of my SD card, but it simply says PLainJaneT2_V2 and Im not sure how to check for the MD5?
If I have the same problem as Almac, I am sorry for the double post, but I didnt download the ROM on my phones browser like he did.
I think Macs have a reputation for opening zip files. If it is a folder and not a zip you are not going to be able to install and recovery won't recognize it. You have to download and make sure that it remains a zip file, if this is indeed your problem.
I think Macs have a reputation for opening zip files. If it is a folder and not a zip you are not going to be able to install and recovery won't recognize it. You have to download and make sure that it remains a zip file, if this is indeed your problem.
I think I remember having this same problem when I would try to install one of the new leaks. It became a folder instead of the desired .zip. Now to remember how I kept those files as .zips! I have to figure this out fast because this stock HTC is not awesome.
Make sure that you are holding both buttons until it takes you into recovery. If it still doesn't work then try the power/end and call buttons, this should take you to a menu where you can either go to fastboot or recovery, I think. Sorry I'm not as familiar with the Eris as I am with my device, I'm just going off of memory from rooting my wife's eris.
holding Call & End & + got me into the old recovery
Holding End and Vol+ and not letting go had no effect.. ended up booting as normal despite my holding both buttons the whole time
feeling like a dummy at the moment
Last edited by Hypo Luxa; July 21st, 2010 at 01:39 PM.
I think I remember having this same problem when I would try to install one of the new leaks. It became a folder instead of the desired .zip. Now to remember how I kept those files as .zips! I have to figure this out fast because this stock HTC is not awesome.
could I simply just compress the folder into a .zip and delete the folder from my sd card? Is it just that simple?
could I simply just compress the folder into a .zip and delete the folder from my sd card? Is it just that simple?
I'm not too positive but I think that may be a bad idea, and even if you did try this you don't want to compress you want to store as an option when zipping the folder. Are you unable to download and save the file as a zip? I wish I could help you with that but I don't use a mac.
The Following User Says Thank You to Papadroid For This Useful Post:
holding Call & End & + got me into the old recovery
Holding End and Vol+ and not letting go had no effect.. ended up booting as normal despite my holding both buttons the whole time
feeling like a dummy at the moment
Unfortunately I don't have an eris in my hands to help you but it doesn't make sense to me that you get the old recovery. I would maybe try again from the beginning.
I know it's a little confusing but you actually don't have root yet. This process only gives you the ability to obtain root through one of two methods:
1. Flashing a rom with root
2. Flashing engtools.zip that jcase provided which gives your current stock rom root
Unfortunately since you are having issues using recovery because of the trackball, this is preventing you from doing one of the methods above.
Quote:
Originally Posted by scary alien
Ah, Papadroid, thanks! I sort of assumed that these root scripts (at least part 1) did the engtools.zip thing behind the scenes...(which is why I really want to look at them to verify this--I can't do the download here at work ).
kamots, Papadroid,
Okay, I downloaded the gscript.zip file to my DX and reviewed the root_part1.sh and root_part2.sh scripts.
From what I can tell, all root_part1.sh does is allow you to install a custom recovery partiton by changing its security (using wag3slav3's mid.txt exploit). This allows you to run root_part2.sh to be able to flash/install Amon_RA's custom recovery. At the end of root_part2.sh, it un-installs (restores, really) the mid.txt exploit back.
edit: okay, now that I'm looking at the contents of engtools.zip, I see it contains the superuser.apk and a replacement su command. I guess I don't really understand how the mid.txt link exploit actually gains you root (or rather, what it does to allow you to install the custom recovery image). Still looking......back soon...
2nd edit: okay, I got it! Papadroid is absolutely right! You do need to install a custom ROM and/or the engtools.zip in order to get root access.
The way the mid.txt exploit works is to soft link the recovery partition (/dev/mtd/mtd1) to a file (/data/local/rights/mid.txt) that already has full access ("a=rwx") permissions. This is what allows you to overwrite the recovery partition with a custom recovery and subsequently allow you to install a root (custom) ROM.
Last edited by scary alien; July 22nd, 2010 at 06:39 PM.
The Following User Says Thank You to scary alien For This Useful Post:
Okay, I downloaded the gscript.zip file to my DX and reviewed the root_part1.sh and root_part2.sh scripts.
From what I can tell, all root_part1.sh does it basically give you root (using wag3slav3's mid.txt exploit). This allows you to run root_part2.sh to be able to flash/install Amon_RA's custom recovery. At the end of root_part2.sh, it un-installs (restores, really) the mid.txt exploit back (i.e., basically taking away your root capability that you got in root_part1.sh). So, if you had run root_part2.sh to install the custom recovery (which I'm sure you did), then you momentarily un-rooted yourself.
So, kamots, I think you can just re-run root_part1.sh to gain root and run the "su" command from the Android Terminal Emulator to see if you get the "#" prompt.
You definitely sound more knowledgable than myself on this but wouldn't he still neeed superuser permissons app?
The Following User Says Thank You to Papadroid For This Useful Post:
I actually unrooted my phone by flashing the RUU, then installed the 7-17 update and used this to root the phone again and it took only a mtter of minutes to do it. Thanks guys this is fantastic work.
I didn't flash a rom though just the engineering tools to get superuser, then I flashed the overclocking kernel.
@ Papadroid: I figured out how to download the file as a .zip. Once the download finishes, I will be trying the process again. Thanks a lot for your help!
You definitely sound more knowledgable than myself on this but wouldn't he still neeed superuser permissons app?
Well, I think that's just an app that allows you to control (selectively grant superuser permission to) new applications that are launched. Plus, its a really cool little app [you've obviously already need to have root to use this app...otherwise, rooting would be really easy ]
I think kamots could be our tester and re-do the root_part1.sh part like the thread says, then type "su" in via Android Terminal Emulator to see if he gets the "#" prompt which should show that he's rooted or not.
[edit: nope, this won't give him root, just the ability to install a custom recovery; the engtools.zip contains both the superuser.apk app and the su command; the su command is what gives you root and the superuser.apk helps you manage access to root]
Last edited by scary alien; July 22nd, 2010 at 06:42 PM.
The Following User Says Thank You to scary alien For This Useful Post:
Well, I think that's just an app that allows you to control (selectively grant superuser permission to) new applications that are launched. Plus, its a really cool little app [you've obviously already need to have root to use this app...otherwise, rooting would be really easy ]
I think kamots could be our tester and re-do the root_part1.sh part like the thread says, then type "su" in via Android Terminal Emulator to see if he gets the "#" prompt which should show that he's rooted or not.
Then, he could download and install the SuperUser.apk if wanted/needed.
Please don't think that I'm arguing, I'm actually trying to understand and learn as much as I can, but everything I've ever done on my phone including terminal emulator has needed the superuser app to give permission otherwise it's denied.
The Following User Says Thank You to Papadroid For This Useful Post:
Please don't think that I'm arguing, I'm actually trying to understand and learn as much as I can, but everything I've ever done on my phone including terminal emulator has needed the superuser app to give permission otherwise it's denied.
Papadroid, not at all a problem...
I could be waaay off (really hope I'm not or I have a few posts to edit and redact).
I think the superuser app is just a safety measure so that you can selectively grant which apps you want to have root access to scary (if you will ) capabilities on your phone. Notice that you can tell it to remember the setting for the future so it won't ask / prompt you again for apps you trust. This ends-up being a whitelist for apps that you trust and a blacklist for ones you don't want to run. This app is also typically installed on the custom ROMs we install, but, by then, of course, we are already rooted.
I don't have my Eris with me and its already rooted...I'm not yet brave or knowledgable enough like eu1 to un-root it and test a lot of this stuff!
P.S., my Android Terminal Emulator has never been asked for permission from the superuser app...I don't remember if I told it to remember and whitelisted it or what a long time ago or not... [edit: I believe that I must have whitelisted it]
Last edited by scary alien; July 21st, 2010 at 08:49 PM.
I was wondering if I wanted to use KAOSFROYO V24 as the custom ROM that I want to install going through the process outlined by EU1, would I run into problems???
I guess I am really asking for a breakdown of what the MD5 signature is and how do I know if KAOSFROYO V24 is compatible.
btw---this is an amazing write up EU1---thanks...
" 1) Did you choose a ROM, download it to your SD card, and check the MD5
signature/file length on the copy of the file on your SD card? "
I know it's a little confusing but you actually don't have root yet. This process only gives you the ability to obtain root through one of two methods:
1. Flashing a rom with root
2. Flashing engtools.zip that jcase provided which gives your current stock rom root
Unfortunately since you are having issues using recovery because of the trackball, this is preventing you from doing one of the methods above.
Sweet! Then that means that one method is still available. Last question,and I will leave you guys alone. Would my phone blown up if I un installed the gscript and everything, re downloaded and started from scratch.? I know that amon ra is already on my phone, but will also need installation write over it. Ok so it seems like I have a few options. 1 installation the engtools.zip however I don't know how, and i'm not familiar with it. 2nd start fresh with new install and hope for the best 3rd wait to see if anyone has had this problem and what they did to fix it. And the least desirable 4th option. Stick it out till Oct when eligible for an upgrade and get the samsung facinate
Thanks you everyone, for trying to help I appreciate it and hopefully we can get something to work
kamots, read through the posts above where Papadroid and I were discussing your issue.
Can you test the first part of using root_part1.sh? (as per the guide instructs--you shouldn't have to re-download things, just re-run the root_part1.sh in Gscript, then power off/on and see if you have root (via "su" from the Android Terminal Emulator)). Don't run part 2 (you've already done it and I believe that it removes your root access).
P.S. you don't have to do this if you are not comfortable...no pressure...just curious. Thanks.
P.P.S. nevermind...you won't get root access after doing the root_part1.sh--you've got to be able to flash .zips from Amon_RA's custom recovery (which you can't b/c of the trackball). Sorry dude.
Last edited by scary alien; July 21st, 2010 at 08:48 PM.
The Following User Says Thank You to scary alien For This Useful Post:
I know it's a little confusing but you actually don't have root yet. This process only gives you the ability to obtain root through one of two methods:
1. Flashing a rom with root
2. Flashing engtools.zip that jcase provided which gives your current stock rom root
Unfortunately since you are having issues using recovery because of the trackball, this is preventing you from doing one of the methods above.
Papadroid rules! You are absolutely correct. I did a little more research and finally figured-out how I think the mid.txt exploit works (devilishly simple, actually). Anyway, I edited my original reply to your post to include the following:
edit: okay, now that I'm looking at the contents of engtools.zip, I see it contains the superuser.apk and a replacement su command. I guess I don't really understand how the mid.txt link exploit actually gains you root (or rather, what it does to allow you to install the custom recovery image). Still looking...
2nd edit: okay, I got it! Papadroid is absolutely right! You do need to install a custom ROM and/or the engtools.zip in order to get root access. The su command in engtools.zip gives you root and superuser.apk helps you manage access to root.
The way the mid.txt exploit works is to soft link the recovery partition (/dev/mtd/mtd1) to a file (/data/local/rights/mid.txt) that already has full access ("a=rwx") permissions. This is what allows you to overwrite the recovery partition with a custom recovery and subsequently allow you to install a root (custom) ROM.
I don't think anyone has actually explained how the exploit works before (state secret?) or maybe I just hadn't run across it yet...
Sorry for the confusion, but I really learned a lot from researching this!
Last edited by scary alien; July 22nd, 2010 at 06:45 PM.
The Following User Says Thank You to scary alien For This Useful Post:
How do you put froyo 2.2 on the Eris after root???
There's a Froyo custom ROM that you flash using the custom recovery image. Here's the developer's (punk.kaos) thread: [ROM]KaosFroyo V24 [07/21] [FROYO] - xda-developers
(its not "official" from Google or VZW, and has a few bugs, but its getting better each day...read through the thread for more information)
I'm trying to do my homework before I root my Eris. I'm learning a lot thanks to everyone on this forum! My next question is, if I get v24 kaosFroyo (For Example) Does that mean when v25 comes out, in order to install it I have to wipe my phone, and start all over again?
When I do Vol- and End I get the typical white recovery screen. I tried this with 80% battery life and also the first two parts with the scripts worked perfectly even to the point where it says 'Congrats you have root' but alas, I cannot get to the black recovery screen for nothing
Got the same problem. Did both steps in Gscript just fine, but can't get the Vol+/End to do anything but start the phone up normally. Vol-/End and Call/End buttons do the same original bootloader, not the one listed in the next step.
Going to try and start over from the beginning shortly and see what happens.
I decided after having alot of problems with my Eris that I was going to root it. I went through your instructions here, and got up to the point where it said "You now have ROOT". After that, when I went to restart it, it would freeze at the Droid screen when I held Power and Volume+. The alternate way to reach there (holding call and power) doesn't do anything at all.
Ran through the steps a second time, same thing. All the way through the second step with it saying " you have root" and reboot. Hold Vol+ and End at the same time and it boots normal.....
Hi, im new here, and i went through the first of the posts with some trouble getting gscript to create a folder, so i created one on my computer and unzipped gscript too. i got the tools, part one and two in the folder and went ahead to create new scripts. while doing part 2, there was an errors saying i didnt have enough space, but then it said i had rooted. i tried booting up with the vol up and call/end key pushed in at the same time and all i got was the regular booting screen. Can anyone tell me whats wrong? By the way, im running on OTA 2.1.
part1 = OK
part2 = OK
REBOOT with volume+ / end = NORMAL STARTUP
REBOOT with volume- / end = STOCK BOOTLOADER
I followed the directions exactly as stated. I even went back and executed part1 / rebooted / executed part2 / rebooted and the same results were reached.
The only difference which should not matter ( at least I dont believe so ) is that I downloaded the files on my computer and transferred them over to their correct directories on the phone through USB.
part1 = OK
part2 = OK
REBOOT with volume+ / end = NORMAL STARTUP
REBOOT with volume- / end = STOCK BOOTLOADER
I followed the directions exactly as stated. I even went back and executed part1 / rebooted / executed part2 / rebooted and the same results were reached.
The only difference which should not matter ( at least I dont believe so ) is that I downloaded the files on my computer and transferred them over to their correct directories on the phone through USB.
ERIS 2.1 OTA
I did the same, and it seems the other person did as well.. could that really be the issue?
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
).
]
