Root HTC Eris RUU won't run

[scotty85]

dammit! yall beat me to the sense/gb punch while i was editing my post with the gin tazz sense link,lol

 

[jonzey231]

I think you're all set. I'm so glad that this worked. So, we have two official recovery from Clockwork brickings that we know about so far, which is good to know.

I would really do only these few things, to make sure that they work:

(First, do make sure that there is no PB00IMG.zip file on your SD card. If you did not do this already, make sure that you delete that file from the phone.)

Second, I would make sure that you can start HBOOT. You can do it one of two ways with GSB: either long-press the power key with the phone running, press "Reboot" and then choose "bootloader", or power down the phone and hold VolDn while you restart the phone. You don't start HBOOT very often, but it's good to know how to do.




There is a Sense GB ROM, yes. (rom) Gin-Sen-Tazz 6/4/11-GINGER SENSE-2.3.3 - xda-developers

Read that first post, especially the part about the stuff that does not work (mainly Bluetooth and, strangely, powering down hangs up the phone.) There is an app in the market called Quick Boot that you can use to shut down the phone, restart in Recovery, start HBOOT, etc. https://market.android.com/details?id=com.siriusapplications.quickboot&feature=search_result

All that said, GinSenTazz seems to work fine, but I found it a little slow compared with other rooted ROMs. If you do try it and have questions, you can either look through the thread on xda-developers (I saw your post over there, so I know you have an account) or you can ask here - I've played around with it a bit and got it tweaked a little to get it to work fine.

If you want an excellent Sense-based ROM, the best is easily xtrSENSE: [ROM][GPL][3/15/2011] xtrSENSE5.0.1 [cache2cache,apps2sd,oc,jit]-HTC Sense - xda-developers

I use my phone in weekly cycles of CondemnedSoul's CM7, GSB's CM7, and xtrSENSE. I still think that, unless you really need Gingerbread features, xtrSENSE is the best ROM for the Eris. (Those features would be voice actions and the really nice Gingerbread text cursor placement and selection controls.)

Congratulations on getting your girlfriend's Eris back, though. Good work!

Thank you so much for everything. You and the others here deserve the "good work", no you deserve a "great work". You guys really came through for me and it was all voluntary and with nothing in it for you other then satisfaction. I'll definitely stay close with this site and take part in helping others as much as I can and it's all because of what you guys have helped me learn and because I know I wouldn't be the only generous one out there.

I will definitely try xtrsense right now actually because I know she really liked the sense interface and wouldn't give two sh!*s if it's gingerbread or not.

Thanks again for everything and to both doogald and scotty, I will stay away from rom manager and clockwork at all costs lol. It's just weird to because clockwork is the safe haven when it comes to my Droid X and now I have to stay away lol.

Anyways, thank you so much guys and I will surely work with you again, hopefully it is helping someone else though.

 

[scotty85]

you are quite welcome. we are glad it worked out,for sure

i actually use Amon recovery on my incredible as well,im not really a huge fan of clokwork on any phone. i have to use it on my TB,as its the only thing that exists,right now,lol.

just make sure to let us know if you cant manually enter hboot/recovery or if any other wierd issues pop up. but im pretty sure youre good to go,now

 

[jonzey231]

yay! another "bricked" eris brought back from the dead. thats awsomwe congrats on a great job with this,its not something alot of folks would have been able to do. most would have just thrown it in the trash can and been done.

definately kudos to you for not giving up on the lil guy,lol.



sorry,i fell asleep too i cannot think of anything that you should do now,except unplug the phone from the pc and check:
1)that it boots on normally when you power it on
2)that power on/volume down will take you to hboot
3)assuming that #2 works,that you can get to recovery by selecting it with the volume rocker and power buttons

other than that... just make sure that you do not use rom manager or clockwork to make backups,flash roms,etc. as was said,Amon's recovery is much,much safer for the eris. ive flashed more roms than i can count on mine... not to mention the numerous times ive unrooted and re rooted it for various reasons,plus my various adb experiements now that its working again,it should be a tough lil bugger. the reason ive never have issue is that im cautious... i check md5s,and ive only used clockwork a couple times(for specific reasons) and those times i was even more cautious than usual

just double check the md5s of things you want to flash,and only use amon and you should be fine



first off,by "stock" i assume you mean htc stock... to me,"stock" would be the AOSP pure gingerbread that you were tryin to install when everything went haywire sense is htcs skin and ui that is mixed in with the AOSP code.

if your GF wants a sense,stock type rom... does she need gingerbread? xtrsense is an excellent stock type rom you could put on for her.

as has been mentioned,GSB and CCM7 are also both excellent roms that are cyanogen mod-slightly modded AOSP. im personally a huge fan of cm and try to run it on all my phones as my daily driver rom.

there is a port of a port of a sense GB rom for the eris: http://androidforums.com/eris-all-things-root/338756-gin-sen-tazz-gingerbread-sense-rom.html

it actually does work pretty well,but its not somethin id neccessarily reccomend that you put it on a phone for someone who is not phone savy. the rom itself is complex,and huge... wich is is one of its biggest issues. doogald found that once he installed his main,core group of "cant live without" apps that the phone only had about 28 mb of free memory. you would have to clear caches constantly to keep from running out,and as time goes on the rom will prolly become slow and laggy,with launcher redraws(meaning everytime you push the "home" softkey the homescreens will have to reload as the phone shuts down the launcher to try and free up memory)

but feel free to give it a shot and see what you think of it.

i still wish CS would whip us up a cm-free AOSP 2.3.4 rom. it would be an excellent eris choice... with the smoothness of his other roms,and it would have a tiny footprint-leaving the eris with more much needed memory.

Thank you so much for everything Scotty, you've been more help then I ever could've asked for as well.

And I second your motion about the cm-free AOSP rom.

Like I said in my reply to doogald, I hope to work with you again on this forum or another, just hopefully it is helping someone else.

 

[scotty85]

Like I said in my reply to doogald, I hope to work with you again on this forum or another, just hopefully it is helping someone else.

amen to that!

 

[nomarsgirl]

Love to see a happy ending!

 

[CondemnedSoul]

i still wish CS would whip us up a cm-free AOSP 2.3.4 rom. it would be an excellent eris choice... with the smoothness of his other roms,and it would have a tiny footprint-leaving the eris with more much needed memory.

You really want one of those?
I'm still considering this once I get everything ironed out with CCM7 ... Maybe one for Dinc too? lol

 

[scotty85]

You really want one of those?
I'm still considering this once I get everything ironed out with CCM7 ... Maybe one for Dinc too? lol

yes please. once for each. the cm feature id miss the most is the ability to turn mms to black background. so if you want to,you can include that

but i think a good running,purely AOSP rom would be cool for folks to see what its like to have a nexus 1 or S,and see what is AOSP,and hwat are CM tweeks.

 

[Bob Cat]

You really want one of those?
I'm still considering this once I get everything ironed out with CCM7 ... Maybe one for Dinc too? lol

 

[erisuser1]

It booted into recovery from the command prompt nice and easily, mounted nicely, and just flashed the ErisMTDNuke_v0.9.zip and I didn't get any error messages at all whatsoever. Copied all the files and it's complete.

I'm glad that ErisMTDNuke was useful to you. It is definitely a method of last resort; but when it's needed... it's needed.

eu1/bftb0

 

[scotty85]

thanks for the tool that has resurrected the dead eris,eu1. we have been wondering if you would appear on this thread at some point

 

[huntdilan]

That's why we are here, right?



Thanks to me for the memory of an elephant.

Ok, I should have done this sooner, but I just downloaded and expanded that ErisMTDNuke zip file. It's very interesting. One thing to note is that it will flash the old, trackball-required version of Amon_RA Recovery version 1.6.2 as part of its process.

The first thing that it does is to do the same thing as jcase's "Flash any RUU" procedure, which rewrites the misc.img file. JCase put this together, I believe, back in the early root and leak image days, to give people a method to flash any known PB00IMG.zip or RUU file after rooting the phone, or even after flashing the leak ROM, when it promoted the bootloader to 1.49.0000. See here: HowTo: Flash Any Ruu - xda-developers

The next thing that it does is flash erase the boot, /system, and /data partitions. (So, before flashing a new ROM, there shouldn't be any need to wipe data/factory reset.) I believe that the flash_erase also will mark any bad blocks in those flash areas, so there should be reduced chance of corruption of those areas going forward. Or perhaps it clears what the flash controller thinks are bad block but which are not - I can't remember which.

Next it copies Amon_RA recovery to the /cache partition, and then flashes that to recovery.

The last thing it does is to erase anything in the /cache partition and then format it.

This is way too much info probably, but knowing that it flashes the old-school Amon_RA is good to know. And, if flashing the tool does report some errors, that would tell you what those errors may be coming from.

Hello googald,
I have the exact same problem as jonzey231's. I have tried everything in this post but I can't get the S-OFF bootloader.

I have battling with the phone for about full 24 hours with no success.

This is as far as I can go:

"PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
Feb 8 2010, 00:08:56

RUU

Parsing...[downloaded ZIP]
[1]Boot -Failed-PU
[2]Radio_VZ -OK
[3]Recovery -OK
[4]System -Failed-PU
[5]Userdata - OK
Partition update fail!
Update Fail

I have almost everything you guys talked about on this thread but I can't proceed because I can't get the phone to S-OFF.

I was wondering if you may outline the steps in a clear way. Step by step. I may be doing something wrong especially when to change the PB00IMG.zip to rom.zip.

I will highly appreciate your sacrifice.
http://forum.xda-developers.com/showthread.php?t=909921

 

[huntdilan]

Thank you so much for everything Scotty, you've been more help then I ever could've asked for as well.

And I second your motion about the cm-free AOSP rom.

Like I said in my reply to doogald, I hope to work with you again on this forum or another, just hopefully it is helping someone else.

Hello jonzey231,
I have the exact same problem as yours. The RUU won't run. I have tried everything in this post but I can't get the S-OFF bootloader.

I have battling with the phone for about full 24 hours with no success.

This is as far as I can go:

"PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
Feb 8 2010, 00:08:56

RUU

Parsing...[downloaded ZIP]
[1]Boot -Failed-PU
[2]Radio_VZ -OK
[3]Recovery -OK
[4]System -Failed-PU
[5]Userdata - OK
Partition update fail!
Update Fail

I have almost everything you guys talked about on this thread but I can't proceed because I can't get the phone to S-OFF.

I was wondering if you may outline the steps in a clear way. Step by step. I may be doing something wrong especially when to change the PB00IMG.zip to rom.zip.

I will highly appreciate your sacrifice.

 

[doogald]

I was wondering if you may outline the steps in a clear way. Step by step. I may be doing something wrong especially when to change the PB00IMG.zip to rom.zip.

It's hard to list this step-by-step. As I understand it, when you run the RUU utility, it copies some files into your temp directory on your PC. When you get to the step in the RUU utility when it is ready to flash the ROM to the phone, you need to leave the RUU application. Then you need to find out where those files are located; in particular, you need to find out where the file "rom.zip" is stored. Once you find that file, you need to replace it (either by copying over, or erasing it) with the root ROM PB00IMG.zip file, which must be in that directory and named rom.zip. Then you go back to the RUU utility and let it try to finish.

I can't think of anything that can be more step-by-step than this post: xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?

 

[scotty85]

Hello jonzey231,
I have the exact same problem as yours. The RUU won't run. I have tried everything in this post but I can't get the S-OFF bootloader.

I have battling with the phone for about full 24 hours with no success.

This is as far as I can go:

"PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
Feb 8 2010, 00:08:56

RUU

Parsing...[downloaded ZIP]
[1]Boot -Failed-PU
[2]Radio_VZ -OK
[3]Recovery -OK
[4]System -Failed-PU
[5]Userdata - OK
Partition update fail!
Update Fail

I have almost everything you guys talked about on this thread but I can't proceed because I can't get the phone to S-OFF.

I was wondering if you may outline the steps in a clear way. Step by step. I may be doing something wrong especially when to change the PB00IMG.zip to rom.zip.

I will highly appreciate your sacrifice.

first,are you 100% sure youre using the rootrom? i dont see anything about hboot in your info,so it makes me wonder exactly what RUU youre using. the download youre using should have an md5 sum of: 63eacc5ede3b179f95dc22d8ef585f94 do you have a way to check it on your PC?

i actually got this to work(tho in my case it successfully flashed the entire root rom since im not bricked). im on windows 7,so if youre on something else it may be a lil different.
1)verify youre using the correct root rom.
2)run installer
3) you will get to a screen that says the following:
you are now ready to update your rom. the update will take approximately 10 minutes to finish
during the process the following things will occur:
-the android phone will be prepaired for the update process
-the process will be displayed on your pc and android phone
-the update completed screen will be displayed on your pc

4)this is where you need to stop. dont click next till youve found and replaced the file.
5)you need to make sure your hidden files are visible.
6)search your c drive for "rom.zip" or maybe just for "rom" since .zip is a file extension,not part of the name. when you find it,right click,then show in folder,or simply navigate to it in a windows explorer window. delete "rom.zip". drag the root rom to this exact location. rename it "rom.zip"(again,on windows,you prolly just want to name it "rom" as windows will automagically add the ".zip" and i dont believe you want the file to be named "rom.zip.zip )

* heres a lil tidbit- its in a different place every time you run it. so if you find it once and want to run it again,youll need to find rom.zip and swap it out each time you run the ruu.

7)once youve replaced rom.zip with the correct root rom,go to the installer and click next.
8) cross fingers

since your not getting a "bootloader fail/pass" or "hboot fail/pass" on the display,i think youre just flashing a RUU without a bootloader upate.... so i think there is hope for you

luckily,the ruu is trying to flash. if you were unfortunate enuff to be on the v3 leak rom,the ruu will not run,and no s-off bootloader. again,this indicates there is hope.

anyway,i hope that helps.

 

[huntdilan]

first,are you 100% sure youre using the rootrom? i dont see anything about hboot in your info,so it makes me wonder exactly what RUU youre using. the download youre using should have an md5 sum of: 63eacc5ede3b179f95dc22d8ef585f94 do you have a way to check it on your PC?

i actually got this to work(tho in my case it successfully flashed the entire root rom since im not bricked). im on windows 7,so if youre on something else it may be a lil different.
1)verify youre using the correct root rom.
2)run installer
3) you will get to a screen that says the following:
you are now ready to update your rom. the update will take approximately 10 minutes to finish
during the process the following things will occur:
-the android phone will be prepaired for the update process
-the process will be displayed on your pc and android phone
-the update completed screen will be displayed on your pc

4)this is where you need to stop. dont click next till youve found and replaced the file.
5)you need to make sure your hidden files are visible.
6)search your c drive for "rom.zip" or maybe just for "rom" since .zip is a file extension,not part of the name. when you find it,right click,then show in folder,or simply navigate to it in a windows explorer window. delete "rom.zip". drag the root rom to this exact location. rename it "rom.zip"(again,on windows,you prolly just want to name it "rom" as windows will automagically add the ".zip" and i dont believe you want the file to be named "rom.zip.zip )

* heres a lil tidbit- its in a different place every time you run it. so if you find it once and want to run it again,youll need to find rom.zip and swap it out each time you run the ruu.

7)once youve replaced rom.zip with the correct root rom,go to the installer and click next.
8) cross fingers

since your not getting a "bootloader fail/pass" or "hboot fail/pass" on the display,i think youre just flashing a RUU without a bootloader upate.... so i think there is hope for you

luckily,the ruu is trying to flash. if you were unfortunate enuff to be on the v3 leak rom,the ruu will not run,and no s-off bootloader. again,this indicates there is hope.

anyway,i hope that helps.

Thank you very much for your help!

I am going to fully address to every question you asked.

Yes, I am 100% sure that I am using the right rom. I downloaded it from here: [HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers

and the following is what I downloaded:

[ 2.19.605.1 ] a.k.a. "Root ROM" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip
107,427,740 bytes; MD5 signature: 63eacc5ede3b179f95dc22d8ef585f94
MultiUpload.com - Eris_RootROM_v2.19.605.1_PB00IMG.zip
OTA: n/a

I can't talk about the HBOOT and I still don't have the S-OFF bootloader

The RUU that I am using I got it from here too:
[HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - xda-developers

And the following is what I downloaded:

[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU) - (Eclair/2.1)
RUU: RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
130,323,038 bytes; MD5 signature: 74035b1685b279b1aa4f17fafdbec78b
MultiUpload.com - RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe


Yes, I have a way of checking the MD5 sum on my computer. I downloaded the MD5 Check Utility v2.31 from CNET and this is what I got

MD5 Checker - Free software downloads and software reviews - CNET Downloads

and how I could check the MD5 sum of the above two downloads.

I am using an old computer with Windows XP SP3 in 32bit. I used my laptop with Win 7 64bit in order to have something into the temp folder. The XP didn't give me anything but 7 did.

1) Before running the Installer, I didn't have anything on my SD card? The SD card was empty then to 2

2) I run the Installer
then
3)
then
4)
then
5)
then
6)
then
7)
then
8)

and here below are the results:

"PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
Jan 24 2010,22:35:57

RUU

Parsing...[downloaded ZIP]
[1]Boot -Failed-PU
[2]Radio_VZ -OK
[3]Recovery -OK
[4]System -Failed-PU
[5]Userdata - OK
Partition update fail!
Update Fail"

And I can't stop screaming like a girl!

But as you can see, I am not at HBOOT yet!

RUU gave me this again despite getting S-OFF bootloder:

"ERROR[110]: FILE OPEN ERROR

The ROM Update Utility cannot open the requested files or the files are damaged. The RUU cannot continue with the update.

Please get a complete RUU package and try again."


Now, what is next? What Am I supposed to do!

Thank you very much!

 

[scotty85]

excellent! looks like you have the s-off bootloader now

are you able to enter hboot via volume down/power (make sur you push volume down slightly before power)? if so there is something we can try *grins and nudges scary alien*

if not,basically youll need to start reading at post 25.

a basic outline:
1)attempt to flash recovery in fastboot. if a menu doesnt appear,try to boot into it from powered off and unplugged state via volume up and power. if it works,go to step 3
2)use adb fastboot command to launch recovery directly into memory
3)flash the tool created by eu1
4)if you get no errors,flash a small rom. id reccomend the GSB that jonzey used,since it worked well for him.

if those steps work, check the following(from post 123):
1)that it boots on normally when you power it on
2)that power on/volume down will take you to hboot
3)assuming that #2 works,that you can get to recovery by selecting it with the volume rocker and power buttons

if those things work,youre good to go. in the future DO NOT use rom manager or clockwork recovery(assuming thats what caused the mess) to flash/wipe/backup. use Amon_Ra... its much,much safer. gotta get ready for work,and then ill be driving all day so its a lil harder to respond,but im sure all of us will be watching so see if you have further questions

good luck!

 

[scotty85]

Parsing...[downloaded ZIP]
[1]Boot -Failed-PU
[2]Radio_VZ -OK
[3]Recovery -OK
[4]System -Failed-PU
[5]Userdata - OK
Partition update fail!
Update Fail"[/CENTER]

Parsing...[downloaded ZIP]
[1]Boot -Failed-PU
[2]Radio_VZ -OK
[3]Recovery -OK
[4]System -Failed-PU
[5]Userdata - OK
Partition update fail!
Update Fail"

your results look just like jonzeys,so im sure that vol down/power is not going to take you to hboot. no biggies,youll just have to launch recovery directly into memory like he did.

again,start reading at post 25 and hopefully you can get everything downloaded goin.

just wanted to post this,since youre getting the same errors,im hopeful the recovery will turn out for you as it did for him... with a happy ending

 

[huntdilan]

excellent! looks like you have the s-off bootloader now

are you able to enter hboot via volume down/power (make sur you push volume down slightly before power)? if so there is something we can try *grins and nudges scary alien*

if not,basically youll need to start reading at post 25.

a basic outline:
1)attempt to flash recovery in fastboot. if a menu doesnt appear,try to boot into it from powered off and unplugged state via volume up and power. if it works,go to step 3
2)use adb fastboot command to launch recovery directly into memory
3)flash the tool created by eu1
4)if you get no errors,flash a small rom. id reccomend the GSB that jonzey used,since it worked well for him.

if those steps work, check the following(from post 123):
1)that it boots on normally when you power it on
2)that power on/volume down will take you to hboot
3)assuming that #2 works,that you can get to recovery by selecting it with the volume rocker and power buttons

if those things work,youre good to go. in the future DO NOT use rom manager or clockwork recovery(assuming thats what caused the mess) to flash/wipe/backup. use Amon_Ra... its much,much safer. gotta get ready for work,and then ill be driving all day so its a lil harder to respond,but im sure all of us will be watching so see if you have further questions

good luck!

I am going to battle with it and when you come back from work and have time to get here you will have my success or failure posted.
Thank you again and good day!

 

[scotty85]

I am going to battle with it and when you come back from work and have time to get here you will have my success or failure posted.
Thank you again and good day!

you are quite welcome

ill have my phone with me... i monitor the forums all day,so ill be watching for sure. i can only reply,when im stopped somewhere,or when theres downtime at the warehouse... but scary,doogald,alot of us will be watching so post up if you have any questions or hit any temporary roadblocks

 

[erisuser1]

The next thing that it does is flash erase the boot, /system, and /data partitions... the flash_erase also will mark any bad blocks in those flash areas, so there should be reduced chance of corruption of those areas going forward. Or perhaps it clears what the flash controller thinks are bad block but which are not - I can't remember which.

FYI,

The flash_erase command is used in the script with the "-N" command-line option.

In addition to erasing all pages, THIS CLEARS ALL "BAD PAGE" FLAGS - EVEN FOR PAGES WHICH ARE (IN FACT) ACTUALLY BAD.

That's exactly why ErisMTDNuke should only be used in emergencies (such as "Failed PU") - some (small) level of bad pages are quite normal for flash memory devices; some phones actually come straight from the factory with a few bad pages in one or more partitions.

So, you can introduce bad pages back into the free pool of erased pages when using ErisMTDNuke. (The good news is that if the bad pages have "hard" or "stuck-at" fault characteristics, they will be automatically re-marked as bad and transparently skipped during the first attempted write to that page).



eu1

 

[huntdilan]

you are quite welcome

ill have my phone with me... i monitor the forums all day,so ill be watching for sure. i can only reply,when im stopped somewhere,or when theres downtime at the warehouse... but scary,doogald,alot of us will be watching so post up if you have any questions or hit any temporary roadblocks

This is what I have and what I did!

What I have:

"PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
Jan 24 2010,22:35:57

RUU

Parsing...[downloaded ZIP]
[1]Boot -Failed-PU
[2]Radio_VZ -OK
[3]Recovery -OK
[4]System -Failed-PU
[5]Userdata - OK
Partition update fail!
Update Fail"

What I did:

After getting the phone into the S-OFF bootloader I know that the next step is to fastboot the recovery image into the phone by using the windows cmd and sdk.

1. I downloaded sdk for windows from
Android SDK | Android Developers

and successfully installed it.

I took this (android-sdk_r11-windows.zip) http://dl.google.com/android/android-sdk_r11-windows.zip

and put it put it to the root of my C drive or here C:\

I extracted it and it read as C:\android-sdk_r11-windows

I shortened the name to sdk and it read as C:\sdk


Before launching the green SDK manager from inside the C:\sdk folder I downloaded JDK or Java for Windows 32bit which is: jdk-6u26-windows-i586.exe

which I got from here:

Java SE Development Kit 6u26

and of course as I mentioned above it suceessfully installed and it put some folders inside the platform folder and it created another folder with other files. The folder's name is platform-tools which read like this
C:\sdk\platform-tools

and that is where the adb.exe this adb_has_moved was.

I then downloaded the Fastboot from
here: HTC - Developer Center for which the right file for Windows Platform under Fastboot Tool is this:

fastboot.exe
size (bytes): 992202
MD5 Checksum: 6bbf05d97585c3c515bdb172eb9e7d12

I put fastboot.exe inside the platform-tools that is inside
C:\sdk\platform-tools folder because that is where AdbWinApi.dll is. I therefore run the fastboot.exe and nothing clearly happened. But, it was succesfully installed too.

Then I went to Start>>run>>cmd and Enter which brought me to

C:\Documents and Settings\"My Computer Name">

I then did this

C:\Documents and Settings\"My Computer Name">cd \sdk\platform-tools and hit Enter and it brought me to this

C:\sdk\platform-tools>

Then I downloaded t the recovery-RA-eris-v1.6.2-trackball-optional.img

from here this link:

http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

and downloaded the
New ("1.7.1") version:

https://sites.google.com/site/scary...ecovery-RA-eris-v1.6.2-trackball-optional.img

and after double checking its size and md5 sum shown here below
File size: 3,926,016 bytes
MD5 checksum: 3217768b831a3841180699942204762d
I placed it into the platform-tools directory or here:
C:\sdk\platform-tools\recovery-RA-eris-v1.6.2-trackball-optional.img

Then into the command window I already had

C:\sdk\platform-tools>

then I added

C:\sdk\platform-tools>fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img

and the results were:

< waiting for device > (I had it turned off to save the battery) then I turned it on with the htc screen still surrounded with the triangles
then it said
sending 'recovery' <3834 KB>... OKAY
writing 'recovery'... OKAY

and the black command window went back here to saying

C:\sdk\platform-tools>

Then I removed the USB cable and I removed the battery and waited for about 60 seconds to make sure that it completely tuned off although I exaggerated on waiting time.

Then I held the:
-Volume Down and pressed the power button once. It powered up with a black screen (and I was still holding the Volume Up).

Removed the battery then again
-Volume Up and pressed the power button once. It powered up with a black screen (and I was still holding the Volume Up).

I tried various combinations of powering it up but I couldn't get into
Android System Recovery.

Which I believe is where I headed.

Now the phone is out of power and I am charging the battery again.

After fastboot results I tried

C:\sdk\platform-tools> adb devices
and I got this

C:\sdk\platform-tools> adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

C:\sdk\platform-tools>

That's all. Nothing was displayed and the phone was connected to the PC and it was on the htc surrounded with the triangles on the corners

Again this gives me

C:\sdk\platform-tools>fastboot devices
HT9BLHG18660 fastboot


C:\sdk\platform-tools>

I also did this below and the results are displayed

C:\sdk\platform-tools>adb reboot recovery
error: device not found

C:\sdk\platform-tools>

Also this

C:\sdk\platform-tools>adb shell
error: device not found


C:\sdk\platform-tools>

Honestly, I don't know what I am doing wrong. I am dying to get to this

 

[doogald]

I am not going to quote your whole thing, but you are doing fine, and this pretty much matches what we have seen twice before - flashing recovery still does not allow you to restart in recovery.

It's quite normal for adb not to be responding while fastboot does - your phone can be in one state or the other, and yours is in fastboot mode right now.

What hopefully will work is to try what is in this post: http://androidforums.com/eris-all-things-root/350856-htc-eris-ruu-wont-run-2.html#post2799438

fastboot boot recovery-RA-eris-v1.6.2-trackball-optional.img

(make sure that the command is right - spaces between fastboot and boot, and between boot and recovery, but nowhere else.)

Does that bring you to the Recovery screen?

 

[huntdilan]

I am not going to quote your whole thing, but you are doing fine, and this pretty much matches what we have seen twice before - flashing recovery still does not allow you to restart in recovery.

It's quite normal for adb not to be responding while fastboot does - your phone can be in one state or the other, and yours is in fastboot mode right now.

What hopefully will work is to try what is in this post: http://androidforums.com/eris-all-things-root/350856-htc-eris-ruu-wont-run-2.html#post2799438

Thank you for the info. But If you look to my lengthy post before this one you will see that I did

C:\sdk\platform-tools>fastboot flash recovery recovery-RA-eris-v1.6.2-trackballoptional.img

and the results were:

< waiting for device > (I had it turned off to save the battery) then I turned it on with the htc screen still surrounded with the triangles
then it said
sending 'recovery' <3834 KB>... OKAY
writing 'recovery'... OKAY

and the black command window went back here to saying

C:\sdk\platform-tools>

I have concluded that I have not successfully flashed Amon_RA (v1.6.2) using fastboot, and I am unable to boot in to Amon_RA.

Which means that I cannot therefore go to

Does that bring you to the Recovery screen above? I hope so.

I'm going to be in and out this morning, but if this works there are a few more steps. Actually, you may want to try downloading the file attached to this post (called ErisMTDNuke_v0.9.zip). Maybe scotty or Scary or bobcat can walk you through using the USB-MS option in recovery to copy that file over, then remove drive safely from windows, then press trackball, then flash that file. Then you'd wipe data/factory reset and try flashing that Gingerbread ROM again (which one was it? If it was KaosGingerbread, DO NOT FLASH THAT ONE.)

 

[erisuser1]

*eu1 crosses fingers*