• 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

one last thing comes to mind... if you can get to recovery,you can toggle usb storage on and off from there to manipulate things to and from the sd card. you wont need to keep pulling it and putting it in another phone. :)

ill defaintely check on your progress in the morning :cool:
 
scotty85 said:
if you get the 2nd part of after running the command,im not sure what will happen. if your phone does not just come on,and have the menu,you can make sure the phone is still being seen,then try:

adb reboot recovery

or

adb shell

then

reboot recovery

i dont think those commands will work,but they are worth a try.

if they dont work,unplug the phone,pull the battery and try the key combinations again...

vol down/power
vol up/power
send/end

and see if any of those things work.
vol up/power should take you to recovery
vol down/power should take you to hboot,where you could pick recovery with the volume and power keys.

if you can get this far,place a very small footprint(small MB size) rom on the sd card and try to flash it

if adb quits seeing your phone at any time,try unplugging for a couple minutes,then plug back in.
Click to expand...

Okay, those commands did nothing. The computer doesn't and never did see it as an adb device, only as a fastboot device.

None of the key combinations did anything, but it is still recognized as a fastboot device.
 
Okay so I've been playing around with the fastboot just to get comfortable with it. I haven't done anything outside of repeating steps we've already done so that I don't mess anything up lol.

I was thinking though, what if I went ahead and erased the recovery partition, and then flashed amon's back onto it? Just so we know it is a fresh install.
 
Also, is there anyway that I could use the "flashall" command with a stock rom? Once again, tell me if I'm completely wrong and out of line as I am not familiar with the ins and outs of this.
 
jonzey231 said:
Nevermind, I read back through it and saw i forgot the .img part of the command.
I just did it again, and it was a success! :)
Click to expand...

jonzey231 said:
Okay so I've been playing around with the fastboot just to get comfortable with it. I haven't done anything outside of repeating steps we've already done so that I don't mess anything up lol.

I was thinking though, what if I went ahead and erased the recovery partition, and then flashed amon's back onto it? Just so we know it is a fresh install.
Click to expand...

When you did the fastboot flash command you did put Amon's Recovery on the phone.

Try restarting while holding VolUp. I'm not 100% confident that this will work (i.e., start Amon's Recovery), but... hopefully it will look like this:

Main_Menu.jpg
 
im not real familiar with the ins and outs of it,either. ive used to fastboot to flash recoveries,but thats about it.

we need to figure out a way to get you into recovery,tho at this point im not sure how. maybe try a battery pull and the key combos again?

reading in post 7 of this thread,seems after they flashed the recovery,things started working. [Q] semi-Bricked?? fix? - xda-developers

ill start reading,hopefully scary and doogald will be along with some other ideas :)

you are trying the keycombos with the phone unplugged from the PC,yes?

what happens when you unplug from the ruu mode screen,with the triangles,and it flashes to the hboot screen? does it stay on that screen? are there any more options other than RUU? what happens if you plug it back in while its still on that screen?
 
Ok, Jonezy. I know that you have tried this, but...

Try turning the phone off. Make sure that it is fully powered off (no sign of backlight or lights behind the capacitive home, menu, etc. buttons on the bottom.) Then, hold VolUp and press and release the power key. Keep holding the VolUp until you see skating keyboards, or about 20 seconds - whichever comes first.

Do you get the Recovery screen, as I showed a few posts above?

If not, reconnect by cable and go back to your terminal session. Make sure that fastboot is communicating by verifying that "fastboot devices" shows your device.

If all of that happens, try this:

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 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.)
 
doogald said:
When you did the fastboot flash command you did put Amon's Recovery on the phone.

Try restarting while holding VolUp. I'm not 100% confident that this will work (i.e., start Amon's Recovery), but... hopefully it will look like this:

Main_Menu.jpg
Click to expand...

I can't get into recovery at all. It doesn't matter what key combinations I do or how many battery pulls I do. I've tried everything.

Anyways, my alarm didn't go off because of bad storms again and now I'm late to work. I'll be back on here later this evening around 9 or 10., If that's too late, we can resume work tomorrow. Thanks for everything guys.
 
One last thing / idea: have you tried, from the phone being in a powered-off state, turning the phone on by pressing the call/send and end/pwr buttons (the two hard buttons on the bottom of the phone) at the same time?

That's a different way of getting you to one of the menus...I don't recall if this was suggested or not...
 
jonzey231 said:
I can't get into recovery at all. It doesn't matter what key combinations I do or how many battery pulls I do. I've tried everything.

Anyways, my alarm didn't go off because of bad storms again and now I'm late to work. I'll be back on here later this evening around 9 or 10., If that's too late, we can resume work tomorrow. Thanks for everything guys.
Click to expand...

I thought that you might not get into Recovery. I was hoping, but...

Anyway, of course I can wait. You are showing amazing patience. Thanks for sticking with us here. I am running a 5K tonight and will be home after 8-ish, but I think that there is enough here for Scary Alien or Scotty to guide you through next steps. Gentlemen, I am thinking that we should get xtrSENSE on the phone first, just to make sure that things are good - and it's a simple, single flash - and (after a Nandroid) perhaps we can walk Jonezy through CondemnedSoul's CM7 if he (well, his girlfriend) still wants Gingerbread.

Perhaps I am getting ahead of things too much here. Anyway, back to Jonezy. Before you do this (mainly, the part in bold):

doogald said:
reconnect by cable and go back to your terminal session. Make sure that fastboot is communicating by verifying that "fastboot devices" shows your device.

If all of that happens, try this:

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 above? I hope so.

[Y]ou 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.
Click to expand...

I think that you really need to read this post, particularly the part that I quote below:

xda-developers - View Single Post - [SOLVED] Anyway to Unbricked a Droid Eris?

ErisMTDNuke_v0.9.zip IS EXTREMELY DANGEROUS AND SHOULD NOT BE USED WILLY-NILLY. IT'S ONLY USE IS FOR DESPERATE, LAST-RESORT MEASURES - CLOCKWORK "SOFT BRICKINGS" WHERE PARTITION CORRUPTION IS EVIDENT.

We could use this in stick2e's case because his phone had been soft-bricked for months, and if things went south, the situation could not have gotten worse.

YOU HAVE BEEN WARNED.
Click to expand...

You should know before you flash that ErisMTDNuke file that it may not fix your phone, and I am not sure if I could walk you through getting it fixed. However, quoting your results of the RUU from earlier:

jonzey231 said:
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"[/CENTER]
Click to expand...

Notice the parts that I bolded.

I really think that you are in dire straits here. I am hoping that this will work as it did for Stick2e over on xda-developers (the link from earlier.) If this does, in fact, work, all thanks go to the following xda-developers users:

bftb0 (known on these forums as Erisuser1) for incredible knowledge, guidance, and for that ErisMTDNuke flash

SoSicWiTiT for discovering that fantastic method of replacing the rom.zip file generated by the RUU utility with the rooted PB00IMG.zip file with the S-OFF bootloader

Stick2e for his patience and follow-through on getting his Eris recovered from the Clockwork "bricking"

I've linked them before, but see these threads: [SOLVED] Anyway to Unbricked a Droid Eris? - xda-developers and [Q] semi-Bricked?? fix? - xda-developers
 
How big is xtr sense? We have the best chance of getting a rom to flash and boot that is small... The smaller the better.

I'm thinking none of the key combos are working case the boot partition is corrupt? If the fastboot reboot recovery doesn't work,we may have to try and fastboot flash the boot partition before we can proceeded?

At any rate,I think the next step is get fastboot seeing your phone again,then try this that doogald mentioned above:

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

And see what happens. Hopefully that will bring among up on the phone. :)
 
scotty85 said:
How big is xtr sense? We have the best chance of getting a rom to flash and boot that is small... The smaller the better.

I'm thinking none of the key combos are working case the boot partition is corrupt? If the fastboot reboot recovery doesn't work,we may have to try and fastboot flash the boot partition before we can proceeded?

At any rate,I think the next step is get fastboot seeing your phone again,then try this that doogald mentioned above:

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

And see what happens. Hopefully that will bring among up on the phone. :)
Click to expand...

That ErisMTDNuke tool will wipe the boot image, /system and /data partitions, and i would imagine if things work as they did for Stick2e that the ROM will flash just fine.

If xtrSENSE doesn't flash then something smaller would be better. I like xtrSENSE solely because it's most compatible, etc., and still fast as heck. And a single flash to install - no separate Google apps flash.
 
How will he flash it if he can't boot to recovery? Admittedly, I haven't had a chance to look at your last links yet...
 
Oooooh I get it now :D

I didn't realize that's what that command was doin. :o

I think I'm up to speed now...
-Download the tool and xtr sense
-Run that command
-Toggle USB Storage and move xtrsense and tool to SD card
-Flash tool
-Flash xtr
-Collect proffits(sorry,couldn't resist... Its from south park ;))
-Rejoice if it boots :)

Sound about right?
 
scotty85 said:
How will he flash it if he can't boot to recovery? Admittedly, I haven't had a chance to look at your last links yet...
Click to expand...

Scotty, LOL...you already posted / referenced the "fastboot boot" command in post #87 above...

Sorry, was going back and re-reading things...lots of stuff going on here, obviously. If its confusing for us, imagine how the OP feels :eek:.

The good news is that there's still a little hope that he'll be able to recover, since this does look very similar to the threads that doogald posted where SuperMan (i.e., bftb0 / erisuser1) swooped in and saved the day (or the phone, as the case may be).

Cheers!

Also, there's going to need to be a slot / step for booting into recovery somewhere in your list, before flashing xtr.
 
scotty85 said:
Oooooh I get it now :D

I didn't realize that's what that command was doin. :o

I think I'm up to speed now...
-Download the tool and xtr sense
-Run that command
-Toggle USB Storage and move xtrsense and tool to SD card
Click to expand...

- cross fingers and toes, get all good luck talismans lined up

-Flash tool
Click to expand...

Before flashing anything else, Jonzey, let us know if there are any error messages from the ErisMTDNuke flash. I'm not sure what they would look like, but any error messages that pop up may be helpful.

-Flash xtr
-Collect proffits(sorry,couldn't resist... Its from south park ;))
-Rejoice if it boots :)

Sound about right?
Click to expand...

Yep, that sounds about right to me.
 
scary alien said:
Also, there's going to need to be a slot / step for booting into recovery somewhere in your list, before flashing xtr.
Click to expand...

To be honest, I think that the best thing is to stay in Recovery and let it install a ROM and then worry about seeing if the phone will start the Recovery partition. Once the ROM is up and running you can always use your GScript method to put Amon_RA recovery on.

However, I think that the reason that Jonezy cannot start recovery is the corruption in the boot partition, which is hanging the bootloader. Once that is cleared then hopefully all will be, as they say, copacetic.
 
doogald said:
To be honest, I think that the best thing is to stay in Recovery and let it install a ROM and then worry about seeing if the phone will start the Recovery partition. Once the ROM is up and running you can always use your GScript method to put Amon_RA recovery on.

However, I think that the reason that Jonezy cannot start recovery is the corruption in the boot partition, which is hanging the bootloader. Once that is cleared then hopefully all will be, as they say, copacetic.
Click to expand...

Yes, I agree. By the way doogald, kudos and thanks to you and Scotty for staying and working with the Jonezy so dilligently. I also think its a great testament to eu1/bftb0 for laying the groundwork (along with the others that have suffered through this issue before that you've kindly cited) and making such informative posts and documentation that allows this type of help to be provided.

You guys really do embody what AndroidForums and XDA are all about.

I'll try to not muck up the thread too much with spurious posts so that the OP can hear a limited number of voices re. the resolution. You guys have done and excellent job so far and I don't want to derail anything (not saying anyone else has or is, mind you--this has been an excellent, very instructive thread and all posters have been awesome).

It was a very good catch where you connected the dots that this looked like the soft-brickings related to CWM (i.e., MTD corruption / bad block thing). Jonezy's issue certainly does look very similar, so that does hold-out hope.

Cheers!
 
scary alien said:
Yes, I agree. By the way doogald, kudos and thanks to you and Scotty for staying and working with the Jonezy so dilligently.
Click to expand...

That's why we are here, right?

It was a very good catch where you connected the dots that this looked like the soft-brickings related to CWM (i.e., MTD corruption / bad block thing). Jonezy's issue certainly does look very similar, so that does hold-out hope.
Click to expand...

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.
 
Yeah, I couldn't help but download and analyze bftb0's ErisMTDNuke.zip file after I saw it on the XDA thread way back when. He did an excellent job of making it self-documenting too.

I have a mental image of eu1 in his own "lab" with the Android / Eris equivalent of beakers and bunsen burners, LOL. Crazy smart and helpful and I'm dang glad he picked our little corner of the world to contribute to. I also wonder if he's sitting back, watching us, to see how his padawan's are doing :D ;).

I didn't make the connection when I saw the "Failed-PU" lines that I assume mean "partition update" failing. Excellent catch.

Cheers!
 
You must log in or register to reply here.
Back
Top Bottom