-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root HTC Eris RUU won't run
- Thread starter jonzey231
- Start date
-
- Tags
- htc droid eris
How do I flash amon? I still can't boot into anything.
The only reason I knew I was s-off was because after the failed ruu, it shows it once the phone is disconnected.
Holy crap, you guys are seriously awesome. I am now at hboot - 1.49.2000 as well as S-OFF.
Now what? lol
The guy who fooled around with this and discovered this method is the awesome one.
I'm away from a real computer, so the next step will be brief, but next you will want to download a copy of Scary Alien's version of Amon_RA Recovery. You can find it at this link. Scroll down until you find this part:
That's the one that you want. This will be downloading not a zip file, but a file called recovery-RA-eris-v1.6.2-trackball-optional.img.
The next step would be to get fastboot downloaded and verified communicating with the Eris. Here is where I call on somebody else for more help - I am a Mac user and that's much different. And, of course, I am not now at a computer in which I can try to figure this out. I think fastboot requires that the Android SDK be installed. Do you have that set up on your Windows computer yet?
Here is some info about installing the SDK and fastboot: HTC - Developer Center
The SDK download and I think some instructions are here: Android SDK | Android Developers
The download for Fastboot is here (the link above) but you can stop reading after the fastboot download - you don't need to download image packages, etc., and you already have the USB driver installed.
So, the next step would be to get the SDK set up, cable the phone to the computer (see if you can now start the HBOOT by starting with VolDn pressed when you power up - hold the VolDn until you see the skating Androids), and see if you can get to fastboot mode (press VolDn when prompted after the HBOOT starts) and do a "fastboot devices" from a Windows command line.
Hopefully somebody can walk you through some of these steps if you have some trouble. I do have a Windows partition on one of my Macs at home so I could fool around with that later if nobody else gets to it.
LOL...hate to stick my nose in here after all that's been written, but I was hoping to see Scotty (or thinking that he might) suggest using the HBOOT flashable Amon_RA custom recovery installer that he suggested in a thread earlier this year.
I can't give too much attention to helping the OP out at the moment, but I could when I get home from work later this afternoon.
I'll reference that thread here, with the stipulation that I think the OP should hold-off doing anything that he is not certain about doing or explicitly directed to do (don't want to muck anything up):
http://androidforums.com/eris-all-things-root/301173-making-hboot-flashable-recovery.html
but the OP could read through it just to become familiar.
The file that I think would be needed is this one, referenced in the above thread:
https://sites.google.com/site/scary..._ra_trackball-optional.zip?attredirects=0&d=1
The OP should also probably get rid of / rename the base root ROM (PB00IMG.zip) that he used to get the S-OFF bootloader. This file will conflict with my HBOOT flashable version of Amon_RA's custom recovery that I just mentioned.
I'll let Scotty weigh-in too and I'll check back here after I get off work.
Cheers!
edit: LOL again...I do see that Scotty already previously mentioned using the HBOOT installer a few posts up...
I can't give too much attention to helping the OP out at the moment, but I could when I get home from work later this afternoon.
I'll reference that thread here, with the stipulation that I think the OP should hold-off doing anything that he is not certain about doing or explicitly directed to do (don't want to muck anything up):
http://androidforums.com/eris-all-things-root/301173-making-hboot-flashable-recovery.html
but the OP could read through it just to become familiar.
The file that I think would be needed is this one, referenced in the above thread:
https://sites.google.com/site/scary..._ra_trackball-optional.zip?attredirects=0&d=1
The OP should also probably get rid of / rename the base root ROM (PB00IMG.zip) that he used to get the S-OFF bootloader. This file will conflict with my HBOOT flashable version of Amon_RA's custom recovery that I just mentioned.
I'll let Scotty weigh-in too and I'll check back here after I get off work.
Cheers!
edit: LOL again...I do see that Scotty already previously mentioned using the HBOOT installer a few posts up...
scotty85
Extreme Android User
So if you power on holding volume down,do you still get just a black screen? Or can you now get into hboot(white screen with colored letters)?
Did you install the Android SDK first?
Yes, I already have it installed. I went to update all my files though so I could get the Google USB Driver, and access was denied to every single download.
It said a file path wasn't found for each one.
Ok, you're going to have to wait for a person with Windows SDK experience for this one. I'm not sure what the Google USB driver is, though. Based on this:
I don't think that you need the Google USB driver. You already installed the HTC sync thing, which installs the driver for the Eris (as I understand it.) You just need to install the SDK from here:
Android SDK | Android Developers
(the one that says "recommended", I would think).
Like I said earlier, I already have the SDK installed. I have for quite some time. I'll try reinstalling though.
Ok, I think I understand it. The fastboot.ext is not an installer - it is the command line tool.
If I understand how Windows does this correctly, the easiest thing to do is to move that file to the SDK install directory, where the adb file is. Then also copy the amon_ra recovery .img file to that same directory as well.
The you want to start a command prompt (start run cmd.exe, I think). At the command window prompt, you want to change directory to the location where fastboot and the abd tool are (cd \whateverthatpathis ) and then, with the Eris powered on and connected by USB:
fastboot devices
Hopefully it will return something that looks like HTC and a bunch of numbers - if you are seeing that, that's good news.
Scary or scotty, please pipe in if I am getting this wrong...
scotty85
Extreme Android User
so what happens if you open a command window,plug in the phone,and type adb devices?
i dont recall doing anything special other than installing the android sdk. i also dont remember exactly what i did about drivers... i had downloaded htc sync for those drivers,but ive also downloaded these drivers: http://androidforums.com/incredible...ivers-adb-bootloader-disk-drive-htc-sync.html
ive got 3 htc phones,so its a lil fuzzy at this point what worked with what
It is not fastboot.ext, it is fastboot.exe. Therefore it is a windows executable file. Someone please let me know if I am wrong.
The only progress I've made on this device so far is getting the S-off and the correct hboot.
I just need to know what to do next.
scotty85
Extreme Android User
this^
once you get adb to see your phone. this directory will usually be in "tools" assuming you have also copied all of platform tools into the tools directory. im still new to all this also,so hopefully scary can chime in with a lil more info.
try
adb devices
fastboot devices
when the phone is plugged in
a lil more on the changing directorys...if you put the sdk in C like i did,open your command window and type:
cd c:\android-sdk-windows\tools
this will get you setup to push the recovery image to the phone via fastboot,from the tools directory.
When I try adb devices it just tells me "adb is not recognized as an internal or external command"
Plus, I may be wrong, but won't adb only work if usb debuggins is turned on? I mean, it was on when the phone was last working but would it still be active?
scotty85
Extreme Android User
open the command window,plug in the phone,and try the commands:
adb devices
fastboot devices
i did not run any executable files to make fastboot work.
scotty85
Extreme Android User
did you try directing the prompt to the location where the sdk is stored?
Nope, I know for a fact that fastboot.exe (the ext was a typo) is a command line tool. Before I had all Macs I was all Windows and before that DOS, and I have run plenty of non-Windows .exe files in my lifetime. It's been a long lifetime. So far.
(Well, to be technical, if it requires a .dll it probably is a Windows app, but one that does not actually run in a graphical window.)
scotty85
Extreme Android User
i dont know if this will help,but this is exactly what i did to set up adb to root my TB:
YouTube - ‪ANDROID SDK Tools (How-To Install)‬‏
afterward,i could do things on my incredible and my eris.
YouTube - ‪ANDROID SDK Tools (How-To Install)‬‏
afterward,i could do things on my incredible and my eris.
Guys, sorry I've been tied-up this evening and just got back to this thread.
Hopefully jonzey231 has the older version of the Android SDK installed, since the adb.exe utility is in the "tools" directory. It has been moved to the "platform-tools" directory, which is a separate download and install for the newer version of the Android SDK.
Also, won't jonzey231's phone need to be booted into FASTBOOT mode in order for the fastboot flash to work? We should probably establish that he can actually bring up the FASTBOOT screen first, eh?
Thanks!
Hopefully jonzey231 has the older version of the Android SDK installed, since the adb.exe utility is in the "tools" directory. It has been moved to the "platform-tools" directory, which is a separate download and install for the newer version of the Android SDK.
Also, won't jonzey231's phone need to be booted into FASTBOOT mode in order for the fastboot flash to work? We should probably establish that he can actually bring up the FASTBOOT screen first, eh?
Thanks!
Yes, I think it stays on. Yes, I think adb requires it in order to do anything while the phone is running Android (right now it's not.) And, if adb devices does not work, how about fastboot devices?
And, let me just repeat: find out where the adb.exe file is stored. Move the fastboot.exe file to that directory. If that directory is c:\AndroidSDK, make sure that you start the command prompt and type:
cd \AndroidSDK
as the first command before you try fastboot devices
Oh, and if there are spaces in the directory path to the storage location of adb.exe and fastboot,exe, do the cd command with quotes, like this:
cd "\path to the adbfile"
(Really not sure windows usually puts this...)
I am hoping that's not the case, as he (she? sorry, don't know... ) cannot seem to start in hboot mode.