• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root making an hboot flashable recovery

meh!

I downloaded and ran the RUU and tried to find where he was extracting the files to grab the hboot file...

...I'm thinking that since I didn't plug my Eris in, that he hadn't reached the point where he extracts the files (I've never run the RUU, lol -- this was a first for me ;)).

I did a quick search of the hboot file eu1 listed above and couldn't find an obvious download of it. I'm sure he has it extracted separately, but what fun is that?! :)

Also, see eu1's (bftb0's) thread re. this too: xda-developers - View Single Post - [ROM][03/06/2011]FlashBack21 v2 -Return to Factory Stock - March 2011 OTA

Gimme a few minutes and I'll hook-up my Eris and try to let the RUU run and see if I can find the file.
 
Okay,

Yep, you gotta hook your phone up and let the RUU run up until it asks you if you are ready to update. Then, you can just go into Windows Explorer and search on the file name or go to the Windows Prompt (DOS/command prompt) and do a "dir/s rom.zip" search and it will tell you where the RUU extracted his temporary files to. Go to that directory and grab the hboot file from there.

Be sure to double-check the MD5 sum. Here's what I got:

38899da4e5e002e3be22900f5f4eb6f7 *hboot_7501a_1.47.0000_091023.nb0

which matches the value eu1 listed here: [Reference] HTC Signed Eris ROM MD5 (md5sum) Signatures - xda-developers

Here's the file I extracted: View attachment hboot_7501a_1.47.0000_091023.zip (I had to put it in a .zip in order to post it here).

Don't forget that after you do this, you won't be able to fastboot flash until you get the S-OFF bootloader back on.

Good luck!
 
scary alien said:
Be sure to double-check the MD5 sum. Here's what I got:

38899da4e5e002e3be22900f5f4eb6f7 *hboot_7501a_1.47.0000_091023.nb0
Click to expand...

scary,i was getting ready to play with this some more,but im unable to do an md5 hash of the .nb0 file. ive done one of your .zip,and its nothing like what you listed above! :eek:

when i right click on the .nb0 file,i dont get the option to use my file verifer. i can only get it to work on the .zip.

any advice? or can you verify that your above sum is different than what it would be for the .zip file and list that one?

as always,thanks for your assistance :D
 
scotty85 said:
scary,i was getting ready to play with this some more,but im unable to do an md5 hash of the .nb0 file. ive done one of your .zip,and its nothing like what you listed above! :eek:

when i right click on the .nb0 file,i dont get the option to use my file verifer. i can only get it to work on the .zip.

any advice? or can you verify that your above sum is different than what it would be for the .zip file and list that one?

as always,thanks for your assistance :D
Click to expand...

Yeah, here's the MD5 sums for both files:

C:\android-sdk-windows\tools>md5sum hboot*
38899da4e5e002e3be22900f5f4eb6f7 *hboot_7501a_1.47.0000_091023.nb0
0742264b74a1326e7393bf87190ebd93 *hboot_7501a_1.47.0000_091023.zip

Lemme dig up the link where I got my Windows MD5 utility from (I always do them from the DOS prompt)...brb...

edit: here's a portion of what I posted in one of my (really old) threads: http://androidforums.com/eris-all-things-root/107329-basic-root-troubleshooting-guide-htc-droid-eris.html:

In the browser of your (Windows) PC, navigate to http://www.md5summer.org/download.html

About three-fourths of the way down the page, find the "DOS Command Line MD5sum utility".

Right-click and download this version (should be http://www.md5summer.org/md5sum.zip)

Cheers!
 
grrr all of a sudden my puter is not seeing my phone in fastboot :mad: it was working fine the other day... ive tried starting a new session,moving the plug to different ports,and restarting the pc. wtf!

still seeing it fine in charge and in recovery :mad: :(
 
scotty85 said:
grrr all of a sudden my puter is not seeing my phone in fastboot :mad: it was working fine the other day... ive tried starting a new session,moving the plug to different ports,and restarting the pc. wtf!

still seeing it fine in charge and in recovery :mad: :(
Click to expand...

lol...when I connected-up my Eris the other night and ran the RUU, it goobered-up my Moto Droid X drivers and I have to de-install the HTC drivers that the RUU installed and completely re-install my Moto Connect drivers. Very frustrating like you said, but it finally worked.

You'll get there...I have faith :).
 
Get a Mac, everybody. No driver install required to communicate with an Eris - unzip the SDK, open the Terminal, chdir to that directory and you're adbing and fastbooting, no problem.

Or at the very least dual boot Linux and do your Eris connecting work that way. In fact, you could install the (free) VirtualBox and set up Linux within a VirtualBox virtual machine and do all of your Eris connections there.
 
doogald said:
Get a Mac, everybody.
Click to expand...
:eek::rolleyes:;)

its become even more fustrating. i tired to uninstall then reinstall,and the drivers install fine and show up as android bootloader interface in device manager. restarted adb command and got the message that the daemon wasnt running,starting it now on port xxxx,and it started successfully. however,still nothing in the device list and no communication :mad:

went ahead and plugged in my incredible and same deal. went ahead and plugged in th TB and again same deal. so now all 3 phones are invisible in fastboot despite my best efforts. :mad:
 
scotty85 said:
:eek::rolleyes:;)

its become even more fustrating. i tired to uninstall then reinstall,and the drivers install fine and show up as android bootloader interface in device manager. restarted adb command and got the message that the daemon wasnt running,starting it now on port xxxx,and it started successfully. however,still nothing in the device list and no communication :mad:

went ahead and plugged in my incredible and same deal. went ahead and plugged in th TB and again same deal. so now all 3 phones are invisible in fastboot despite my best efforts. :mad:
Click to expand...

Scotty I put a second hdd in my computer and loaded it with Ubuntu so I could use windows or linux. Give linux a try if you can.
 
well,i still doesnt appear when i list adb devices. but for sh*ts and giggles i ran the command line,and it worked :eek:

apparently im a dumb ass and the phone doesnt need to appear in the device list? :confused: so all this fustration was for nothing,lol.

powered off and back into hboot and voila! back to s-on 1.47.000. rebooted,moved the root rom to she sd card and let it update. after it rebooted,i deleted that,and moved our hboot tracball optional recovery to the sd card and let that update. after it rebooted i downloaded the superuser app from the market and now im back on a rooted 2.1 :)

guess i can restore my GSB backup now. :D this has been quite an educational experience!
 
You must log in or register to reply here.
Back
Top Bottom