kloroformkandi

Okay I just dragged them all onto the SD card.

scotty85

it has been a long time,but i definately remember getting a similar error when trying to make/restore backups with too low a battery cahrge. plugging the phone in usually fixed it,but that may not be the case with recovery booted from the boot partition.

my first thots were that we had to streamline the recovery to the point that the usb toggle didnt work,but without rereading everything i dont remember i had a post typed out to reflect this,but then decided to mention the charge issue first,in efforts to not complicate the matter(i find in alot of complicated situations its easy to overlook the obvious!)

also just thot id point out that after doing the above and flashing amon in the recovery partition,he will have tiny rescue recovery in the boot partition,and regular amon in the recovery partition not a big deal as the boot image will be over written when you flash the rom,after flashing the repair files.

so if he is able to get to "regular recovery",thats great. if not,all he should have to do is power on the phone normally and "tiny rescue recovery" should start.

__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
donate to my device fund

Last edited by scotty85; June 5th, 2012 at 05:40 PM.

doogald

Right, I should have mentioned that I fastboot flashed that recovery image and USB-MS toggle did not work for me. However, flashing my recovery.zip from a couple of posts ago and then restarting in Recovery allowed USB-MS to work.

Kicking myself for not trying that out first...

Yes, I realized that as well. I though about adding a good boot.img to that recovery.zip but realized it's probably not necessary.

kloroformkandi

Just to make it clear so no one gets confused [mainly me lol], I have dragged those three files onto my SD card but have not done anything past that.
Refresh me on what's next?

doogald

Ok, it's this.

First, if you followed those steps a few posts ago to flash recovery.zip, then restart the phone while holding VolUp. If you did not, and just copied using the external card reader, then just restart the phone without holding a volume key. It should start in Recovery.

kloroformkandi

Okay I did those steps.

doogald

The next step was to flash MTD_Inspect_v0.9.zip. But, because it will be cumbersome, I suggest that you skip that step and flash ErisMTDNuke_v0.9.zip.

So, from Recovery,

"Flash a zip from sdcard"

Choose ErisMTDNuke_v0.9.zip

Press trackball to confirm.

Report any error messages.

kloroformkandi

Okay, no errors.

doogald

Ok, the next two steps are:

So, turn off the phone by pulling the battery. Restart in HBOOT by holding down VolDn while starting. Check the top line - does it say "Unlocked" or "Locked" at the top? I am betting that it says locked - if so, you can pull battery.

Otherwise, out the phone in fastboot mode, and run the command

fastboot oem lock

Then pull battery.

Maybe let it charge for a while before we go on to the next step. Meanwhile, we can copy over a couple of files to the SD card.

First, you should have copied a file called "Eris_RootROM_v2.19.605.1_PB00IMG.zip". We need to rename that file to just PB00IMG.zip (those are two zeroes, not two letter O) - when you rename, you can just delete the stuff before the PB00IMG.

Next, you need to copy that file over to the SD card. I assume that you will use the SD card reader for that. Again, do not put the file in a folder - just put it in the root folder.

You can also copy over the "March2011_OTA_ReferenceROM_v1.zip" if you downloaded that as well - to the same place on the SD card.

I think that you should also copy over a file called FlashBack21_v2.zip from here: http://doogald.net/eris/FlashBack21_v2.zip

Copy that file to the SD card as well.

Now, after the files are copied, the battery is charged for a bit, and the SD card is back in the phone, restart the phone to HBOOT by holding VolDn. It should be a little different, checking the file called PB00IMG.zip. It will be in that state for a couple of minutes or so. Finally, it should show a message asking if you want to apply the update? <ACTION> Yes. Press the trackball. The screen will go dark for a second, the it should now start loading PB00IMG.zip with a progress bar that turns blue on the upper right.

Wait for that to complete - a couple of minutes or so. (It should now say HBOOT 1.49.2000 S-OFF on the second line.) There will also be a few different progress bars in different colors as each of Userdata, System, Recovery, Radio_VZ and Boot update.

(There is a thread by erisuser1 that shows and describes what should be happening - see here: Visual Example: The PB00IMG.ZIP update method )

Finally, there will be a message - do you want to reboot the device <ACTION> Yes. Press the trackball. Hopefully, the phone will successfully boot. (It will be stuck on the skating Androids for a minute or so - then on the Verizon Wireless boot image for a few minutes - don't panic.)

When the phone start, awesome - don't do anything else. Pull the battery and let me know that you're ready. Or, of course, if you have an issue, report that as well.

kloroformkandi

Everything has worked just fine. :]
Battery pulled and ready.

doogald

Ok, a few things now.

- pull the SD card, put it in the card reader, and delete the file PB00IMG.zip from the SD card.

- pop the SD card back in the phone. Cable the phone to the PC

- download the file "recovery-RA-eris-v1.6.2-trackball-optional.img" from here: https://sites.google.com/site/scaryalienware/downloads/recovery-RA-eris-v1.6.2-trackball-optional.img?attredirects=0 - copy that file to c:\android

- start the phone in HBOOT by holding VolDn. Press Send to start fastboot

- from the CMD window, enter the command fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img

It shouldn't have an error messages.

- press VolDn to go back to HBOOT mode.

- Now press VolUp to go to Amon_RA Recovery (the screen with the green text and the black background.)

- Go the "Wipe" menu

- Choose "Wipe data/factory reset". Press the trackball to confirm.

- When the menu returns, press VolDn to go back to the Main Menu.

- Go to "Flash a zip file from sdcard"

- Choose "Flashback21_v2.zip" and press the SD card to confirm.

Read this:

So, the phone will eventually restart and start booting normally, with the Verizon Wireless screen and all. When the phone starts up to the normal screen, you can pull battery.

YOU ARE ALMOST DONE!

kloroformkandi

All good here.

scotty85

just making sure... your phone flashed the root rom and the booted into the OS? if so thats great news! the next thing you do will get your custom recovery back and update your phone to the most current software and radio.

excellent job you are doing. youve learned alot of commands and procedures in a very short time

doogald

Ok, that last step actually unrooted the phone, in order to install the latest radio. The root ROM that we used a few steps ago installed an outdated version of the radio - but it also installed the S-OFF bootloader, which is very powerful and makes the fastboot command very useful.

So, you are going to make one more trip into HBOOT.

- start in HBOOT by holding VolDn while powering up.

- press Send to put it in fastboot mode

- we are going to repeat the step from last time: from the cmd window, enter the command fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img

- when that is complete, press VolDn to return to HBOOT mode

- then press VolUp to restart the phone in Amon_RA recovery

- go to the "Wipe" menu

- Choose "Wipe data/factory reset"

- Press VolDn when the menu returns to go back to the main menu

- "Flash a zip file from sdcard"

- Choose the file "March2011_OTA_ReferenceROM_v1.zip"

- when the main menu returns, choose to restart the phone

If all went well, you will now be running a stock, rooted ROM (it should take a few minutes to boot the first time.) When you have your phone all set up, with your Google account set and your apps reinstalled, post back and I'll give you a few more things that you can do.

Sorry that this took so long. It turns out that if your phone had the 1.47.0000 HBOOT, it would have been a lot faster, but at least we got your phone working again! (I hope...)

kloroformkandi

It works!
I cannot thank you both enough, you have been very helpful and saved me from having to spend money I don't have on a new phone.

Thanks so much.

doogald

You're very welcome!

The few things that I promised before:

first, when you have your phone set up the way that you like, you should shut the phone down, and then restart in Recovery by holding VolUp as it starts.

- go to the "Backup/Restore" menu

- Choose "Nand backup" and then press trackball to confirm.

This process creates an exact image of your phone, and there is a restore command that will bring the phone back exactly as it is at the time that you ran the backup. One huge advantage of root. You can press VolDn to go back to the main menu, then Reboot.


second, there are a couple of great root-only backup and restore apps for the phone that can help you restore the phone if you do have to do a factory reset. It becomes an easy and quick way to get your apps *and* data back. The two apps are Titanium Backup Pro and MyBackup Pro - either one is fine, though MyBackup is probably easier to use.

Titanium: https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackupPro&feature =nav_other#?t=W251bGwsMSwxLDYsImNvbS5rZXJhbWlkYXMu VGl0YW5pdW1CYWNrdXBQcm8iXQ..

MyBackup: https://play.google.com/store/apps/details?id=com.rerware.android.MyBackupPro&feature =more_from_developer#?t=W251bGwsMSwxLDEwMiwiY29tLn JlcndhcmUuYW5kcm9pZC5NeUJhY2t1cFBybyJd


third, there is a great custom ROM for the Eris called xtrSENSE. It s a stock rooted ROM, but it has some advantages over the ROM that you just installed. First, it is overclocked, meaning that the phone runs a little faster than stock. Second, it uses some functionality called cache2cache, which creates a lot more room for your apps and data. You can download it from my dropbox here: https://dl.dropbox.com/u/220420/Eris/xtrSENSE/xtrSENSE5.0.1.zip

One thing that is great about this is that you can flash it over the ROM that you are running now, without having to do a factory reset first. So, you can copy the xtrSENSE5.0.1.zip file over to your SD card, just as you did with the other files, and the do the following procedure:

- shut down the phone
- restart in Recovery by holding VolUp
- Backup/Restore menu
- Nand backup (just in case...)
- VolDn to go back to the main menu
- Wipe menu
- Wipe Dalvik cache
- VolDn to go back to the main menu
- Flash a zip file from sdcard
- Choose xtrSENSE5.0.1.zip
- when complete, reboot the phone

Anyway, good luck going forward, and, (not that I wish this on you), with the 1.49.2000 S-OFF bootloader and the fastboot command, it will be *a lot* easier to recover if anything goes wrong in the future.

kloroformkandi

Alright. I'll make sure to do a backup and check those things out.
Thank you again!

scotty85

excellent job! im glad you are up and running.

doogald

Since this thread evolved into rooting the Eris, I've moved it to the "All Things Root" subforum. I was a bit reluctant, as it may help somebody with a stuck, stock Eris (and it's very possible to use rooting tools but get the phone back into a stock state), but we can just point people to this thread going forward.

TheMortallyWounded

Wow. Reading this thread was just pure shock-and-awe. You don't get this kind of customer service ANYWHERE. Two guys working hard with an inexperienced user to restore a three-year-old phone... free of charge. Faith in humanity restored. Hats off to googald and scotty... that was amazing.

THIS is why I love Android. It isn't about which OS is better, or which hardware package is better... it's about community. Open-source is the way to go, and if this thread doesn't prove it then you're just plain blind.

I had the same problem on my Eris when I first bought it. I took it back and conned Verizon into giving me a new one. But that isn't an option now and most people would have said that this wasn't worth fixing.

__________________
Good afternoon, gentlemen. I am a HAL9000 computer. I became operational at the H.A.L. Lab in Urbana, Illinois on the 12th of January, 1992.

scotty85

thanks for the kind words,and im sure i speak for doogald as well,when i say "my sentiments exactly!" it is all about the community,and helping one another.

my lil buddy was the first phone i ever rooted and rom'ed,so it has sentimental values. i definately want to save as many of them from the trash as we can!

bugmenot2

Let me just say.. "doogald" is my favorite person in the world right now.

Someone gave me there bricked phone with the same exact issue as the OP here.. and I became obsessed with it and "wasted" hours trying everything and nearly gave up on bringing it back to life.. when I eventually came across this thread.

Followed all the steps in the provided by the incredibly helpful doogald, and everything is working flawlessly. I couldn't find a working solution anywhere else on the internet. I saw countless people who gave up on the same issue along the way, and I began to think the phone was dead for good.

Anyway, just wanted to say: THANKS!!

(and sorry for using a bugmenot account.. i'll make a new account soon)

doogald

Awesome - glad to hear it. Most of the credit goes to Scotty and Erisuser1. These guys are superstars.

afonz

This thread saved my bacon - thanks for all the good info! +1000 to the superstars!

kloroformkandi

Hey guys, me again o_O

I recently dropped my phone and it ended up doing the same thing, being stuck on the droid load-up screen.
I did VolDn>Recovery>Reboot System now [It won't let me scroll down to anything else] but that didn't do anything.

I wasn't sure if I should repeat any of these steps or what suggestions you had.
You were so great at helping me before it would be great again to have your help again.

doogald

I believe that we installed the trackball-optional recovery, right? If so, you *should* be able to scroll down the recovery menu with the green (call) key, and select an option with the red (end call) key.

If you can scroll, and you created a backup using "Backup/Restore", you can try restoring an old backup. Otherwise, you can try a "Wipe data/factory reset" and reset the phone from scratch.

But I'd be shocked that dropping the phone caused some problem that would be fixed by wipe data. Anyway, report back if you can or cannot get one of those things to work.

kloroformkandi

Ahh I didn't think to use the green/call key to scroll! >_>

I was able to scroll to backup/restore. Restore was 'completed', but sadly my phone still won't turn on properly.

I have no idea if dropping it actually had anything to do with this problem reoccurring [I have dropped it so many times >.<], but I figured if it was once fixed it could be fixed again? o.O

doogald

I wonder if you are having bad sectors in flash memory again? (It's also possible that the phone is bad...)

Remembering that well-charged battery is important for this (i.e., try to get the battery charged up, if it is not already), perhaps it's time to go back and try to flash the MTD_Inspect_v0.9.zip file that you downloaded before. If it's still on the SD card, that's great; flash that file from recovery (remembering the hardware key scrolling method). You actually skipped that step the last time, as I think I was pretty sure that you had bad sectors anyway.

When you flash that zip file, it will create a file on the sdcard called "MTDInspect.txt". If you don't have an external SD card reader, you can connect the phone to your computer using the USB cable and select the option in recovery called "MS-USB toggle", it will mount the SD card as an external drive on your computer, where you can look for that file. Open that text file and see if there are any bad blocks in any of the partitions. The report will look something like this:

[From this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9]

kloroformkandi

Seems there are two bad blocks.

Last edited by kloroformkandi; December 3rd, 2012 at 09:25 PM.

doogald

It may be a bad block in a critical area.

I'd say the next thing to do is to try the ErisMTDNuke_v0.9.zip

Actually, if you get no error messages, you may want to try to do a Nandroid restore right away, then see if the phone works after a restart.

Just the standard warning that the phone may still be unusable after this... though of course it is now anyway.

kloroformkandi

Yay It works! ^_^
Except when I went to restore there were two choices?
I wasn't sure if it mattered which one I chose.

Last edited by kloroformkandi; December 4th, 2012 at 12:46 PM.

doogald

The backup files have a date code - they should look something like BCDS-yyyymmdd-hhmm IIRC, where the yyyy, mm, and dd mean what you think they do

Good thing on it working, too.

kloroformkandi

Thank you once again~

CapnO

This thread fixed my soft bricked Eris (1.49 S-ON, stock recovery, stuck on 3 skateboards).

Agree with post above; this thread is why I love Android...the community. Best step-by-step guide I've EVER seen ...no contest (I root my Samsung Vibrant as well).

Bob Cat

Welcome to the forums CapnO! We're glad you got it going.

BC

__________________
The Plumber^®

vladrytskiy

Hi, maybe someone can help me.
I faced the following trouble stuck on 3 droids on skates.
Device info:





This is aproblem when i'm trying to push recovery.img




As you see i also can't push recovery.zip
What's the trouble ?
P.S. The size of recovery files differ, cause i tried to flash different recoveries, from different threads

Last edited by vladrytskiy; March 5th, 2013 at 11:42 AM.

doogald

vladrytskiy, try the instructions and recovery in this post (post 40 in this thread): Stuck in boot-up screen.

Show the results when you try to fastboot flash zip recovery.zip

vladrytskiy

Today I tried at least 5 times, the first result is one of shown above .
Ok, I'll try one more ..
in 10 minutes ill post new result ...

vladrytskiy

hre it is.
C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.062s]
finished. total time: 0.063s

C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot oem rebootRUU
... INFOmsm_nand_dm_read_oob 0x1FF60000 2048 0 fai
led (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF80000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0800 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF60000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FF80000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0000 2048 0 failed (-74), correct
INFO 0 bits
INFOmsm_nand_dm_read_oob 0x1FFA0800 2048 0 failed (-74), correct
INFO 0 bits
OKAY [ 0.065s]
finished. total time: 0.065s

C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot erase cache
erasing 'cache'... OKAY [ 3.807s]
finished. total time: 3.807s

C:\One_X_All-In-One_Kit_v1.2.2\Data>fastboot flash zip recovery.zip
sending 'zip' (2463 KB)... FAILED (status read failed (Too many links))
finished. total time: 282.770s
Here is a screen before flashing

it's after faild status


it's me disconected usb

it refuses to boot at all


the only way to boot is to flah the hboot again...but it's some kind of loop

Last edited by vladrytskiy; March 5th, 2013 at 02:55 PM.

doogald

It looks to me as if the flash memory on the phone has failed in a way that prevents the recovery partition from being flashed. Does the phone restart in HBOOT if you power up while holding down VolDn? If yes, is it still 1.51.0000 *UNLOCKED*?

The recovery.zip in the post that I linked above is 2523 KB, while the two results you showed were 3834 KB and 3818 KB, so the recovery.zip were two different files. That's why I wanted to see the result of fastboot flash zip recovery.zip.

vladrytskiy

no it doesn't boot in hboot, it starts with black screen with no signs, the only way to boot it now in hboot is to reflash it and then i can unlock it.
the last image shows the screen after connecting via usb.

is it dead with no hope on recoveryng at all?

Last edited by vladrytskiy; March 5th, 2013 at 03:34 PM. Reason: added a question

scotty85

i wouldnt write him off just yet. if we can get a recovery image to boot,even if we cant get it to permantly flash,there is hope. give us a few minutes

scary alien

Hey vladrytskiy,

Scotty sent me some things for you to try, but it would also help if you could let us know what the recoveries were that you flashed (i.e., description, file sizes and MD5 checksums if you can).

Anyway, there's also a special "rescue recovery" that we built that might help you in this situation (no guarantees, though ). It's smaller and doesn't have all of the bells and whistles (options/features) as the full-blown Amon_RA recovery.

Here's a link to it: PB00IMG-rescue-recovery.zip

It's file size is 2,583,818 bytes and it's MD5 sum is a2f3b8007df147bed7247efa2920a513.

Try to flash this tiny/rescue recovery:

fastboot flash zip PB00IMG-rescue-recovery.zip

Then do a "fastboot reboot" to see if that will take you into that special recovery.

By the way, Scotty wanted to note:

Let us know what you find/see from the above.

Thanks!

__________________
androidforums Site Rules/Guidelines

[App] AFV (Android File Verifier) - file checksum (MD5, SHA1, etc.), signed jar / .zip verifier, and Nandroid backup verification
[App] OTA Verifier (beta) - verify an over-the-air (OTA) update.zip or other flashable .zip file
[App] Android Root Toolkit - useful root functions / utilities

scotty85

Thanks mister scary.

Hopefully that will get a recovery boooted. Holler if you have questions

vladrytskiy

It's rather hard to find all info about that recoveries that I tried to flash , cause there were lots of them .. after the multiple tries I deleted them
I'll try flash rescue recovery in two hours , then I'll send feedback...

vladrytskiy

So i tried to send command fastboot oem reset RUUflag an got

C:\Users\Vlad\Desktop\mini>fastboot oem reset RUUflag
... FAILED (status read failed (Too many links))
finished. total time: 0.004s

then i disconnected usb relocked bootloader and flashed PB00IMG-eris-1.51.0000-hboot.zip


then i unlocked bootloader


the md5 A2F3B8007DF147BED7247EFA2920A513 is correct for the file ofrecovery so i tried to flash it.
the first attempt was faild so i tied the second wit command fastboot oem rebootRUU and it send me OK.



after sending fastboot reboot


what i'll have to do next?
should i do this:


but i don't understand if i'll see some erors in the first flashing (flash the ErisMiscReset_v0.9.zip) what does it mean stop it means that next 2 flashing i have to miss and try to flash ?

Last edited by vladrytskiy; March 6th, 2013 at 03:36 AM.

scotty85

Yes! That is exactly what you should do,only flash the misc reset last.

Flash:
-inspect
-nuke
-misc reset

Im fairly certain inspect will reveal a large number of bad blocks,so likey plan on flashing them all

After that,you will flash the "root rom" to get the real s off hboot,and put a bootable os back on the phone.

Don't want to get your hopes up too much,but I think you are well on your way to possible recovery!

vladrytskiy

Good news is that i cold restore the phone and flashed HTC Eris March 2011 OTA Stock ROM - v2.41.605.6 which boots and works.
Yhank you guys.
The bad news is i can't reach recovery and can't flash nither anoter recovery nither any ROM.

Any ideas?

scotty85

Awesome! That is great news. What troubles are you having flashing recovery? You should be able to install it just as you did before, with the fastboot flash recovery command. This time, you can use 1 of the normal images, and not the special rescue recovery. Another option if you could find it, would be to run the heiress 1 click root app

doogald

Ugh, it's been so long since I have done this...

If you restart the phone while holding VolDn, do you see the HBOOT start screen? Or do you see Amon_RA Recovery?

If HBOOT, my thinking is that the *best* thing to do is to run the root ROM PB00IMG.zip from HBOOT to get the 1.49.2000 S-OFF bootloader, so you can now more reliably fastboot flash from now on. After that, you would need to either flashing the latest radio (the root ROM has an older one) or flash a good Amon_RA recovery, then the Flashback_21v2 (to get the latest radio), fastboot flash Amon_RA recovery again, and then flash the ROM of you choice.

Scotty, what do you think?