Root HTC Eris RUU won't run

[erisuser1]

Note that the fastboot command that doogald provided starts with "fastboot boot" rather than "fastboot flash".

That is what you should be attempting right now - a "soft" boot of the recovery rather than from a copy of it (possibly) flashed into the recovery partition.

 

[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

I am really sorry! I just realized the difference in commands.
I have to do
>fastboot boot recovery-RA-eris-v1.6.2-trackball-optional.img

NOT

>fastboot flash recovery-RA-eris-v1.6.2-trackball-optional.img

I am goignto try and see what happens!

 

[huntdilan]

Note that the fastboot command that doogald provided starts with "fastboot boot" rather than "fastboot flash".

That is what you should be attempting right now - a "soft" boot of the recovery rather than from a copy of it (possibly) flashed into the recovery partition.

Thank you very much for mentioning the difference in commands
I am going to try

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

NOT

>fastboot flash recovery-RA-eris-v1.6.2-trackball-optional.img

and I will let you know what I get.

 

[doogald]

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.

I actually think that you did; since we see

sending 'recovery' <3834 KB>... OKAY
writing 'recovery'... OKAY

I think it flashed fine. However, as I happened to Jonzey, one of the partitions - one of the misc partitions, I think - is messed up and will not allow a boot to continue.

I see that EU1 pointed out that you missed the subtle difference in the "fastboot boot" command line, though. I hope that this will work, as we know it worked for two others in the past.

 

[huntdilan]

I actually think that you did; since we see



I think it flashed fine. However, as I happened to Jonzey, one of the partitions - one of the misc partitions, I think - is messed up and will not allow a boot to continue.

I see that EU1 pointed out that you missed the subtle difference in the "fastboot boot" command line, though. I hope that this will work, as we know it worked for two others in the past.

Haha
Hahahahahahahahahaha.

Thank you very much! You guys are awesome!

Here are the results

C:\sdk\platform-tools>fastboot boot recovery-RA-eris-v1.6.2-trackball-optional.img
downloading 'boot.img' ... OKAY
booting... OKAY

C:\sdk\platform-tools>

The Phone vibrated and now it has this!

Thank you again!

Many thanks to

erisuser1
doogald
scotty85

 

[scotty85]

Yay!

 

[scary alien]

huntdilan,

Sounds like your pretty close to being all the way back!

Just to be clear, you actually see "[trackball optional]" at the bottom of the custom recovery screen, right?

I just want to make sure that you've really got the tweaked recovery for if (when? ) your trackball might goes south on you...

I'll let the other guys finish-up their fine work with you. You've been a very good student, by the way .

Kudos and props again to Scotty, doogald, and especially for erisuser1 for all his mind-blowing work that he's done for everyone re. our little Erii.

Cheers!

 

[erisuser1]

huntdilan,

I'm sort of late to the party on this thread** (and haven't read all of your posts), but I think what you should do now is:

1) From the "soft-booted" recovery, apply the ErisMTDNuke_v0.9.zip fix

Note that (as doogald pointed out a long time ago in this thread) that will cause the recovery to be over-written with the standard Amon_RA recovery (the one that uses the trackball), so you will need to

2) Repeat the "fastboot flash recov...." step that you did earlier

3) Turn the phone off and see if you *now* can boot into recovery with the either the VolUp+Power or VolDown+Power (+ Hboot menu traversal) methods.

If #3 succeeds, the next steps are to apply a ROM of your choice and start enjoying your phone.

eu1


** again, I didn't read the whole thread - do you know what sequence of events got your Eris into it's crisis state in the first place?

PS doog, scotty, scary: sorry for butting in.

 

[huntdilan]

huntdilan,

Sounds like your pretty close to being all the way back!

Just to be clear, you actually see "[trackball optional]" at the bottom of the custom recovery screen, right?

I just want to make sure that you've really got the tweaked recovery for if (when? ) your trackball might goes south on you...

I'll let the other guys finish-up their fine work with you. You've been a very good student, by the way .

Kudos and props again to Scotty, doogald, and especially for erisuser1 for all his mind-blowing work that he's done for everyone re. our little Erii.

Cheers!

Oh yes, I am almost there!

Yes, I see the ""[trackball optional]" at the bottom of the custom recovery screen.

Thank you!

To be honest with you, I don't what I can say! But I am so happy! Thanks to all those guys again.

 

[scary alien]

PS doog, scotty, scary: sorry for butting in.

LOL, no flies on you, eu1! (none of us would ever complain about any of your interjections...you are always welcome).

I've only interjected my one recent post above while watching these recent events play-out...(doogald and Scotty have been the "man").

Cheers!

 

[erisuser1]

Oh yes, I am almost there!

To be honest with you, I don't what I can say! But I am so happy! Thanks to all those guys again.

Don't leave us hanging!... put up a post when you've got a ROM running and everything seems normal.

And (also) I have a keen interest in any details you can provide about how your Eris got into it's wedged state in the first place. Was ROM Manager or ClockworkMod recovery involved?

eu1

 

[huntdilan]

huntdilan,

I'm sort of late to the party on this thread** (and haven't read all of your posts), but I think what you should do now is:

1) From the "soft-booted" recovery, apply the ErisMTDNuke_v0.9.zip fix

Note that (as doogald pointed out a long time ago in this thread) that will cause the recovery to be over-written with the standard Amon_RA recovery (the one that uses the trackball), so you will need to

2) Repeat the "fastboot flash recov...." step that you did earlier

3) Turn the phone off and see if you *now* can boot into recovery with the either the VolUp+Power or VolDown+Power (+ Hboot menu traversal) methods.

If #3 succeeds, the next steps are to apply a ROM of your choice and start enjoying your phone.

eu1


** again, I didn't read the whole thread - do you know what sequence of events got your Eris into it's crisis state in the first place?

PS doog, scotty, scary: sorry for butting in.

Results

1. After flashing ErisMTDNuke_v0.9.zip
- Fash zip from sdcard
Install from from sd card complete.

2. After "Install from sd card complete"
I did
C:\sdk\platform-tools>fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img

but the cmd window hangs here
C:\sdk\platform-tools>fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img
< waiting for device >

Ever since it said "Install from sd card complete", I disconnected the usb cable once and reconnected to see if the cmd will pick it but it didn't. And I have not turned off yet.

3. I can't go here yet.

** I will explain in full words later, but my problem was as in post #1 of this thread
http://androidforums.com/eris-all-things-root/350856-htc-eris-ruu-wont-run.html

So what do I do now? It is still waiting for the device

I am also going to use the

GSBv3.5-ODEX-cm-7.1.0-RC0-Eris-signed.zip
http://defy.bz/ws/roms/eris-roms/GSBv3.5-ODEX-cm-7.1.0-RC0-Eris-signed.zip

as jonzey231

 

[erisuser1]

So what do I do now? It is still waiting for the device

Turn the phone off and re-start it so that it goes into fastboot mode.

Normally that is done by

- Phone powered off
- simultaneously press & hold Send+End

and then (your) step #2

You got the phone into fastboot mode once - it should be even easier to do so now (I think/I hope).

[ Edit ] I went back and looked at your posts, and noted your previous mention of the screen image of "HTC surrounded by triangles in all four corners of the screen".

That is a variant of what is known as "RUU" or "oem-78" mode. If I am parsing your posts correctly, it sounds like your phone was (initially) going directly into this mode no matter what buttons you pressed when you started it up. Is that correct? Is it still behaving that way after you flashed the "ErisMTDNuke_v0.9.zip" fix?

(Note that "RUU" mode is a variant of fastboot mode, as you discovered - you can use fastboot commands when the screen is displaying that image).

eu1

 

[erisuser1]

Note that if your phone is in a normal, rooted condition, you should be able to launch the recovery boot (flashed onto the phone) from a cold-start - either

Power Off -> VolUp+End

or

Power Off -> VolDown+End -> navigate HBOOT menu to select RECOVERY

While I suppose you could still operate a phone that needed to be booted with the aid of a computer, that is not very practical. I am assuming that the (prior?) difficulty that the bootloader was having in loading the recovery from flash memory has something to do with the "misc" partition... which was over-written by the ErisMTDNuke_v0.9.zip flash.

Can you *now* get into recovery from a cold start, without having to perform a fastboot "soft-boot" ?

 

[doogald]

PS doog, scotty, scary: sorry for butting in.

As I am sure that you know, all of this was from your work previously with Stick2e and SoSicWiTiT, so you are far from butting in.

I'm usually around more frequently, but today's been busy. Thanks for being around.

 

[doogald]

One thing to note: the trackball-only version of Amon_RA recovery is normally just fine with the 1.49.2000 S-OFF bootloader, so you can always fastboot flash the new recovery after you have the phone up and running with GSB 3.5.

Do use 3.5 for now, as it is a one-step flash. GSB 3.6 requires you to download and flash a separate Google apps flash file.

If you just want to phone to work as it used to with stock (with non of stock's delays and out-of-memory errors), you may want to consider xtrSENSE once you have GSB 3.5 up and running. We can walk you through that as well. It's purely up to you.

 

[erisuser1]

Paging huntdilan...

You've been at this a while, so no problem if you need to take a break, eat, or get some sleep - whatever. You have made excellent progress, and I am optimistic that completion is right around the corner.

If we're not here when you come back online, post a time (including timezone) when you will next be online - I'll try and be present. I only have one major errand to run yet today which will have me afk (Away From Keyboard) for some time.

eu1

[ Edit ] Just found out my errand begins now. I will be AFK until at least 1830 EDT

 

[huntdilan]

Don't leave us hanging!... put up a post when you've got a ROM running and everything seems normal.

And (also) I have a keen interest in any details you can provide about how your Eris got into it's wedged state in the first place. Was ROM Manager or ClockworkMod recovery involved?

eu1

Alright! Hooray! Everything is perfectly working now!

I have the room running perfectly now!
I have used/flashed this: http://defy.bz/ws/roms/eris-roms/GSBv3.5-ODEX-cm-7.1.0-RC0-Eris-signed.zip

Here is how it all started. and Yes, it involved ClockworkMod recovery!

I bought a used (in excellent condition) HTC Droid Eris from ebay.
It came with a stock 1.5 and with no sd card but I went to best buy to get one.
I went back home to root the Eris.
I visited the following site How To: Root the HTC Droid Eris (Unrevoked Method) since I previously used it to root and flash another Eris of mine which I later gave to a friend and I also successfully flashed it to cricket using this method How to flash HTC Droid Eris to Cricket with Talk, Text, Wap and MMS 5/3/2010 - xda-developers
till the end and made a nandroid backup to fully have youtube run without errors.

Then I successfully rooted the Eris with the unrEVOked3 recovery reflash tool

Then I flashed
MacRom_MR5_06152011
It was under here: [ROM][UPDATE] MacRom MR6 / CM7 RC1 [6/26/11 Nightlies] - xda-developers But it is no longer there.

Anyway, I did erase everything without making a backup!

Then after the ROM was successfully installed. I had to accept and have it run.
When those skating guys came on, they didn't want to leave. I put the phone aside for about 5 minutes. then I got angry.
I removed the battery.
Then I started it again it stayed on those droids.
I immediately flashed another Custom Rom and it failed!

It said:

symlink dumpstate SYSTEM:bin/dumpcrash and the error line was I think 15.

I didn't know what the RUU was by then. Then I downloaded one:

RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver

hoping that it was going to fix it, I run it and killed it completely meaning the [110] error. And I didn't know what that was either.

By the grace of God I desperately typed RUU won't run and I got here. And now the phone is back to life and I am going to ROOT it so that I can flash it to cricket and give it to another friend of mine.

Thank you to everyone on this thread.
If these people want me I can put all the details STEP BY STEP of how I did it so that it could hep others in the future.

Thank you again!

A question though is there any other way to root the eris so that I could flash it to another carrier without using unrEVOked?

I am going to search and see, but if you have another idea let me know! Later.

The time is 5:37PM EST (Buffalo, NY)

 

[doogald]

Alright! Hooray! Everything is perfectly working now!

Excellent!

Here is how it all started. and Yes, it involved ClockworkMod recovery!

I think that we all guessed this, but it would have been interesting if something else happened.

If these people want me I can put all the details STEP BY STEP of how I did it so that it could hep others in the future.

It might be best for people to take it one step at a time. I would think that there are some for whom the RUU flash will actually work to completion, or at least to the ability to start in HBOOT, and the rest of the procedures that you used would then be unnecessary.

I also successfully flashed it to cricket using this method How to flash HTC Droid Eris to Cricket with Talk, Text, Wap and MMS 5/3/2010 - xda-developers
till the end and made a nandroid backup to fully have youtube run without errors.

A question though is there any other way to root the eris so that I could flash it to another carrier without using unrEVOked?

I'll start by saying that I am a VZW customer so I have never flashed to another carrier.

Well, looking through that Cricket method and is says that you need to have QPST, so that, I think, precludes any of the Froyo or Gingerbread ROMs. However, both xtrSENSE and xtrROM do support QPST, so I would try flashing one of those and see what happens.

[ROM][GPL][3/15/2011] xtrSENSE5.0.1 [cache2cache,apps2sd,oc,jit]-HTC Sense - xda-developers
[ROM][GPL] xtrROM5.0.1 odex,cache2cache,apps2sd,jit,lwp,oc[3/29/2011] - xda-developers

You've done an excellent job learning things like MD5 hash checking, so you should be all set to flash this. That said, just to say it, I would use this procedure:

- move xtrSENSE or xtrROM to the SD card
- check the MD5, just in case
- restart in Recovery
- Nandroid backup
- Wipe data/factory reset
- Wipe Dalvik cache
- Flash xtrSENSE or xtrROM
- restart the phone

Try then with that Cricket procedure and see if it works.

 

[huntdilan]

Note that if your phone is in a normal, rooted condition, you should be able to launch the recovery boot (flashed onto the phone) from a cold-start - either

Power Off -> VolUp+End

or

Power Off -> VolDown+End -> navigate HBOOT menu to select RECOVERY

While I suppose you could still operate a phone that needed to be booted with the aid of a computer, that is not very practical. I am assuming that the (prior?) difficulty that the bootloader was having in loading the recovery from flash memory has something to do with the "misc" partition... which was over-written by the ErisMTDNuke_v0.9.zip flash.

Can you *now* get into recovery from a cold start, without having to perform a fastboot "soft-boot" ?

Well, I didn't do another fastboot flash after I successfully installed the ErisMTDNuke_v0.9.zip.

I powered off the the phone, the held VolDn and it booted in HBOOT. I pressed the VolUp and when into Recovery and installed
the GSBv3.5-ODEX-cm-7.1.0-RC0-Eris-signed.
The trackball works fine and other keys under Android Recovery System are okay!

 

[huntdilan]

Turn the phone off and re-start it so that it goes into fastboot mode.

Normally that is done by

- Phone powered off
- simultaneously press & hold Send+End

and then (your) step #2

You got the phone into fastboot mode once - it should be even easier to do so now (I think/I hope).

[ Edit ] I went back and looked at your posts, and noted your previous mention of the screen image of "HTC surrounded by triangles in all four corners of the screen".

That is a variant of what is known as "RUU" or "oem-78" mode. If I am parsing your posts correctly, it sounds like your phone was (initially) going directly into this mode no matter what buttons you pressed when you started it up. Is that correct? Is it still behaving that way after you flashed the "ErisMTDNuke_v0.9.zip" fix?

(Note that "RUU" mode is a variant of fastboot mode, as you discovered - you can use fastboot commands when the screen is displaying that image).

eu1

I am so sorry I have not answered all your questions. And I am also glad for these technical terms.

That is a variant of what is known as "RUU" or "oem-78" mode. If I am parsing your posts correctly, it sounds like your phone was (initially) going directly into this mode no matter what buttons you pressed when you started it up. Is that correct?

Yes that is what was happening!

Is it still behaving that way after you flashed the "ErisMTDNuke_v0.9.zip" fix?

No, it didn't! It stayed into the Android Recovery System

(Note that "RUU" mode is a variant of fastboot mode, as you discovered - you can use fastboot commands when the screen is displaying that image).

Yes now I know!

 

[huntdilan]

Excellent!



I think that we all guessed this, but it would have been interesting if something else happened.



It might be best for people to take it one step at a time. I would think that there are some for whom the RUU flash will actually work to completion, or at least to the ability to start in HBOOT, and the rest of the procedures that you used would then be unnecessary.





I'll start by saying that I am a VZW customer so I have never flashed to another carrier.

Well, looking through that Cricket method and is says that you need to have QPST, so that, I think, precludes any of the Froyo or Gingerbread ROMs. However, both xtrSENSE and xtrROM do support QPST, so I would try flashing one of those and see what happens.

[ROM][GPL][3/15/2011] xtrSENSE5.0.1 [cache2cache,apps2sd,oc,jit]-HTC Sense - xda-developers
[ROM][GPL] xtrROM5.0.1 odex,cache2cache,apps2sd,jit,lwp,oc[3/29/2011] - xda-developers

You've done an excellent job learning things like MD5 hash checking, so you should be all set to flash this. That said, just to say it, I would use this procedure:

- move xtrSENSE or xtrROM to the SD card
- check the MD5, just in case
- restart in Recovery
- Nandroid backup
- Wipe data/factory reset
- Wipe Dalvik cache
- Flash xtrSENSE or xtrROM
- restart the phone

Try then with that Cricket procedure and see if it works.

Thank you again!

 

[huntdilan]

Yay!

Thank you! It is over now.

 

[erisuser1]

Congrats!

I am still on my errand - the hell on earth known as "going to Costco with the GF".

More later.

 

[huntdilan]

Congrats!

I am still on my errand - the hell on earth known as "going to Costco with the GF".

More later.

Thanks!

Haha she would be mad if you didn't tag along when she wanted you to!

Later!