yashsingh1/xdaforums huggingface dataset:
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
kd,

The procedure you used (wipe data/factory reset using the stock recovery) should have worked with a non-rooted phone... assuming that all the hardware was still OK.

You should not have experienced a verification failure applying a valid OTA file as an update.zip, but it is not obvious to me that you should be trying to fix the problem that way in any event.

If the phone is under warranty, I think that the right thing to do is contact VZW or whomever sold you the phone about warranty return. Only if there is NOT a warranty available would I consider further "repair" experimentation on your part.

Let me ask a single question before I give any other advise: what bootloader version is on your phone? (You should see this in the HBOOT or FASTBOOT screen); probably it will be one of these three:

1.47.0000 S-ON

1.49.0000 S-ON

1.49.2000 S-OFF

I would advise you to avoid trying PB00IMG.zip or "RUU" rom reflashes at the moment. I can provide "cautious" instructions about how to proceed; but first- what bootloader do you have?

bftb0
[Droid Eris Q&A, Help & Troubleshooting] kdcroswell:
I have contacted VZW and the phone is not under warranty so she is pretty much stuck with this phone.

Here is what I see on the bootloader screen:

PB00100 XC SHIP S-ON

HBOOT-1.46.0000 (PB0010000)

MICROP-0111

TOUCH PANEL-MELFAS_45_17

RADIO-2.42.01.04.27

Oct 5 2009, 19:21:56

Any instructions would be GREATLY GREATLY appreciated!!

Thanks

kdcroswell
[Droid Eris Q&A, Help & Troubleshooting] malakai1911:
Don't want to threadjack, but for easy MD5 checking on Windows or Mac, you can use HashTab (which is awesome). I can't direct link yet, but: www [dot] implbits [dot] com/Products/HashTab.aspx
[Droid Eris Q&A, Help & Troubleshooting] kdcroswell:
I have downloaded the RUU utility and ran it to install all of the needed drivers. I have also downloaded the fastboot utility and verified that the phone and PC are talking by using the code you provided.

I have also downloaded the Amon_RA custom revovery and the ROOT PB00IMG.zip file and verified the MD5 signature for both files.

I read the link on how to do the PB00IMG.zip install including the battery pull trick and the link to how to make a nandroid backup.

I didnt do anything else but verify that the phone and PC are talking and downloaded the files that I will be needing.

I am not real familiar with rooting phones but the instructions you have given me so far are easy to follow.

Now that we verified that the phone and PC are talking, what should I do next?

Thanks again for all your help!!
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
OK.

(1)

The first step is to charge the phone fully, and attempt the HBOOT+PB00IMG.zip install, using the "battery pull trick":

- charge the phone completely.

- move the "PB*.zip" file to the SD card top-level folder, making sure it is renamed to "PB00IMG.zip".

- Make sure to verify the MD5 of the PB00IMG.zip file on the SD card - not the copy on your computer.

- Turn your phone off.

- Take the back cover of the phone off.

- With the phone off, pull the battery a couple of times and re-insert it to get familiar with how long it takes to pull the battery. You should try to do this within one second of the screen going dark (please re-review the instruction post on AF). The timing is not super-critical, but when you press the button to start the flashing, the "bootloader" flashes very rapidly - something like 1/4 of a second, and then the screen goes dark. Practicing the battery pull will get you used to it.

- Re-review the instructions in that "Visual Example" post over on Android Forums

- Start the phone in HBOOT mode (Hold Vol-Down+End key).

Hopefully, you will not get a "Main Version is Older!" message after HBOOT unpacks and inspects the PB00IMG.zip file. If you do, proceed no further and report that result.

- Accept the flash (start it), and then pull the battery as soon as the screen goes dark. Do NOT pull the battery before the screen goes black - do it as soon as possible after it goes black.

If this all goes well, you should be able to re-start the phone to see if the bootloader flashing occurred.

DO NOT start the phone in HBOOT mode, because the PB00IMG.zip will repeat again., Instead, after you re-insert the battery, start the phone in FASTBOOT mode: Send+End.

You should see "S-OFF" and "1.49.2000" if the flash succeeded.

(Note: some people have reported that occasionally, the "flashing" process will continue after powering up the phone, even though this is not the desired outcome. I have done the "battery pull" trick with the HBOOT+(Root) PB00IMG.zip install perhaps 50 times, and I think it happened to me twice. If this occurs, don't panic - just let it go to completion.)

(2)

If the flash succeeded, put the phone into FASTBOOT mode (Send+End), and perform a soft-boot of the Amon_RA image:

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

The easiest way to make this work is to have the "recovery-RA-eris-v1.6.2.img" file in the same folder that you have the "fastboot.exe" program in (unless you have changed your PATH environment variable to include that location; in that case you can run the program from any "current directory").

This is one of the features of the S-OFF bootloader: using the "fastboot" program, you can shove a bootable image across the USB connection, and tell the phone to boot it up; doing this does not alter any of the flash memory on the phone. You should be able to use Amon_RA to make an initial Nandroid backup at this point.

I'll add another post to this in a couple minutes.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
OK.

Now, normally - if the phone in question had not been acting up when it was "stock", we would be proceeding much more rapidly. But, in the past, we have observed cases where just "flashing" a ROM, especially using the RUU utility or HBOOT+PB00IMG.zip method can cause the phone to become a hard brick if there are problems with the flash memory partitions.

So, download the attached "flashable .zip" file: MTD_Inspect_v0.9.zip

File: MTD_Inspect_v0.9.zip

Size: 2,786,881 bytes

MD5: 17a39da9d554bef76930ea0499fc8851

You can transfer files to your SD card when it is in Amon_RA recovery - that is the menu item "MS-USB" toggle. Use that mode to transfer this file ("MTD_Inspect_v0.9.zip") to the root folder of your SD card.

(BTW, since you are using the "MS-USB" toggle feature, now is a good time to rename or delete the PB00IMG.zip file on the SD card - you don't wan't the install to re-start automatically should you accidentally start the phone in HBOOT mode)

(BTW #2, I should mention that your phone will charge when it is running Amon_RA - so it is safe to leave the phone in Amon_RA recovery for extended periods of time - so long as you eventually plug it in either via USB, or on a charger)

You can "flash" this above package after you have transferred it to your phone. It actually doesn't "flash" anything - it runs a diagnostic program to look at the health of your phone's flash memory.

When it finishes, it will create a report file on the SD card named "MTD_Inspect.txt". It will have some lines of text at the top of the file which look like this. Post the top of that report (as shown below).

(I just ran this on my phone - this shows you what the first several lines of that file look like)

Eris MTD Partition Status Report Generated on Wed Mar 16 05:20:45 UTC 2011

PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS

misc /dev/mtd/mtd0 655360 0 5 0 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 0 20 0 0 0
system /dev/mtd/mtd3 178257920 1 1360 0 0 0
cache /dev/mtd/mtd4 136314880 1 1040 0 0 0
userdata /dev/mtd/mtd5 167247872 0 1276 0 0 0

What I am most interested to look at are the "bad block" counts. Some phones have none; as you can see my phone has 1 bad block in each of the system and cache partitions. (Zero or low numbers are OK - we are just checking here to see if there is anything horribly wrong).

Also, BTW - please report if you saw any errors reported when you make the Nandroid backup. You will see an "E:" and a message on-screen if an error occurs.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Hi kd,

It occurred to me that - because you had already performed a "factory reset" procedure using the stock recovery boot - that there is little value in performing a Nandroid backup. (Although, if errors occur during the backup, that information could be useful for diagnostic purposes).

I had been thinking something along the lines of "wouldn't it be great to get hand the phone back to the wife just as she had last used it" - but that is clearly impossible if the /data partition got cleaned up.

So... what you probably want to do is download a ROM file to load onto the phone after we review the results of the "MTD_Inspect.txt" report.

The one that will be most familiar to your wife, and 100% stock, is this one:

[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6

It's not even rooted - it literally is identical to the most recent "stock" HTC/VZW code for the Eris. Putting a rooted ROM on the phone is also possible, and there are versions that are extremely close to stock, such as "xtrSense 5.0", if you want to put that on the phone as an alternative. (The phone will be a little snappier in it's behavior.)

Anyway, you might want to download a ROM file, transfer it to the root folder of your SD card, and verify it's "MD5" signature (the copy on the SD card, not the one on the computer).

Assuming that no problems occurred with the Nandroid backup and the "MTD_Inspect.txt" report doesn't indicate huge problems with any of the "boot", "system", "userdata", or "cache" partitions, the next step you will be taking is to flash the ROM file using the Amon_RA menu.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] kdcroswell:
Hey bftb0,

I have followed the steps you listed and successfully flashed the bootloader to 1.492000 and performed a soft-boot of the Amon_RA image. I created a nandroid backup without any errors.

I downloaded the attached MTD_Inspect_v0.9.zip file and transfered it to the sd card using Amon_RA custom recovery tool and flashed it. I attached the report it left on the sd card.
[Droid Eris Q&A, Help & Troubleshooting] kdcroswell:
I think the wife will be happy with a working android phone. She is currently using an old windows phone (HTC ozone). I think she would be very happy with xtr sense.50 rom if it makes the phone a little snappier. She had complaints about the stock rom lagging between making calls and what not.

After you take a look at the inspect report and don't see anything out of the ordinary, I can give it a shot.

I will wait for your reply.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
OK, everything looks normal. (1 bad block in /cache, but I don't know why that would cause a problem)

Go ahead and flash a ROM file after performing a

wipe -> wipe data/factory reset

in Amon_RA.

Watch the screen carefully for any errors (indicated with an "E:")

If flashing of the ROM succeeds, power the phone off with the menu, start it up in fastboot mode (Send+End), and then perform a flashing operation of the recovery partition:

fastboot flash recovery recovery-RA-eris-v1.6.2.img

Then, after waiting for all visible activity to cease on the screen, pull the battery, re-insert it, and power the phone up normally. It will take quite a bit longer to get to the initial screen than normal, but that is typical for a first boot.

Let me know if you see any errors anywhere - watch the phone closely through all these steps.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
kd

I just remembered that - because you did a factory reset with the stock recovery on your phone - you will need to "activate" the phone.

The phone may request to do activation during the initial start up of the phone. I think that any other phone which is registered on that line needs to be switched off for this to work correctly (but am not completely sure, since I don't flop back and forth between phones). I guess that means that the Ozone should be off when you start up the phone.

If you've already gone past that point and need to do it manually, dial *228, and then enter option 1.

Whether this works or not depends on what Verizon did for you when you visited them. (It won't work if they removed the phone from the account) If it doesn't activate, give Verizon a call on another line and tell them "your phone came back from the dead".

bftb0
[Droid Eris Q&A, Help & Troubleshooting] kdcroswell:
No errors!!!!

She now has xtrSense 5.0 running on her phone and it booted up!!!!!!

Thank you for all the help you provided!!
[Droid Eris Q&A, Help & Troubleshooting] kdcroswell:
We activated the ozone when we got home from Chicago by dialing *228 opt 1.

So after I got the new rom loaded on her eris, I followed the prompts and activated the phone again.

Everything seems to be working normal again!!

I can't thank you enough for all the help you gave me!!

So far, running the xtrSense rom, the only thing that she has noticed different was the internet icon in the apps list. I got her facebook set up without any issues. (thats all she really cares about)

Thanks again for everything!!!
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
OK, you're welcome.

Sorry we went through a lot of extra effort (I was afraid of a scenario that didn't exist on your phone), but it sounds like your wife had a phone to use in the meantime.

Make sure to get rid of the PB00IMG.zip file (either delete it or rename it or move it out of the top-level folder) so it doesn't cause any disruption should the phone get booted into HBOOT mode.

A couple of other points are worthwhile to make, too.

1) You are an Eris rooter now, whether you wanted it or not :)

2) If you flashed the recovery ("fastboot flash recovery recov..."), you can now boot directly in to it (the custom recovery) by holding the Vol-Up and End/Power buttons when the phone is turned off.

3) You have means to make complete backups on your wife's phone with Nandroid. Once she has her phone fully configured, you might want to do that once as a insurance policy against further disasters.

Cheers and safe travels,

bftb0

PS It didn't escape me that you had absolutely no troubles with any of this stuff, including the command line, which usually eludes younger windows users. Compute much?
[Droid Eris Q&A, Help & Troubleshooting] kdcroswell:
That was no big deal going through the extra effort! I am just relieved that we dont have to puchurse a different eris thru craiglist or ebay.

I deleted the PB00IMG.zip file when you mentioned it in a previous step.

I am going to have to look into rooting my phone now!! It was kind of fun!

I wouldn't say that I compute much. When I was a child and first introduced to computers, there was no such thing as windows. It was all dos. My father is a software engineer so I picked up alot from him back in the dos days.

My wife can't thank you enough for all the information you provided!

Cheers to you!!

kdcroswell
[Droid Eris Q&A, Help & Troubleshooting] crazymacleod:
Hello,

I want to send out a Heavy thanks for this thread. I too was able to restore my wife's phone and flashed xtrsense 5.0. All other forums I visited for this topic ended with a verizon exchange and that wasn't possible for me. But right on! this was a tremendous help. Thanks again! :)
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
bftb0, I am having the same issue but it seems the process may be a little different for me do to my boot loader.

Mine shows 1.49.0000 S-ON

I did all of the same steps up to the point that I received the error as follows.

"Main Version is Older!" message after HBOOT unpacks and inspects the PB00IMG.zip file.

You advised to Stop and ask for further guidance so I am doing that now.

In advance I appreciate the help. This thread has been more helpful than any other resource I have found so far.
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
I have a droid eris that I was given by my sister in law. She went on a trip to California and the phone died on her way home. She charged over night and turns it on the next morning and it sticks on the three skateboarding androids.

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

is the boot loader if I under stand correctly. When I go to the recovery screen (phone with ! triangle) and hit the Vol up and End simultaneously I get the blue menu. At the top it says Android System Recovery <2e> and at the bottom in yellow it says E:can't open /cache/recovery/comand

I did a little more digging around and found this thread

http://xdaforums.com/showthread.php?t=968216

I started following the directions in this post

http://xdaforums.com/showpost.php?p=11635866&postcount=7

I replaced the rom.zip file with the renamed PB00IMG.zip from this thread and I received this error after running the RUU program

ERROR [140]: BOOTLOADER VERSION ERROR

The ROM Update Utility cannot update your android phone.

Please get the correct ROM Update Utility and try again.

I am new to Android and all of this rooting and flashing business but I am not a stranger to technology and I use terminal and cmd prmt at work so I am familiar with the tools.

Any additional help would be great thanks.

Also I can open a new thread I just am not sure if that is necessary yet.

EDIT:

I just noticed in this post that he used the Root Rom to "inject" into the RUU I used the V3 rom so I am going to try again with the root rom.

http://xdaforums.com/showpost.php?p=8943332&postcount=5

Also yes I know I am talking to my self but it seems to help me work through this plus someone may stumble upon this at some point :)

EDIT:

Using the Root Rom

the RUU gives me the error

ERROR[140] BOOTLOADER VERSION ERROR

The ROM Update Utility cannot update your android phone.

Please get the correct ROM Update Utility and try again.

When I boot holding the send + end I still get

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

Not really sure where to go next so I will probably stand by at this point.
[Droid Eris Q&A, Help & Troubleshooting] roirraW "edor" ehT:
I wish I knew what to tell you. bftb0 doesn't appear to have made any posts on XDA since March 30th. Hope he's alright, probably just busy. He probably already has a post somewhere that addresses this. Might have more luck searching XDA using Google. Maybe Google search for

XDA Main Version is Older

I know I've seen that before, so I'm sure it's come across bftb0's desk, but I don't know what the solution was off the top of my head.

Good luck!
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
Thanks for the reply. I will have to poke around with it some more. I am sure I can figure it out or brick it even more either way it was free.
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
Well I think I am at the point of saying....

bftb0, please come back!!!! I cannot do this without you!
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
If I understand your situation correctly, you have only two recourses:

1) Go into the stock recovery menu ("Android System Recovery <2e>"), and perform a factory reset. See if the phone will boot. This is not a rooting method - just an attempt to see if the phone is somehow hung during initial boot up (e.g. a "boot loop"). After the reset, if you can boot it, then root it.

2) The "tereg" SD-card eject race condition exploit. Search the archives circa late June/early July 2010. It works for a small fraction of the people that have tried it. It is an exploit against the stock recovery. No clues whether it will work for the stock recovery on your phone; as it was only successfully used against the "Leak-V3" recovery (presumably your recovery is somewhat later). This is truly a "method of last resort for the desperate" - low odds that you will get it to work.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
Thanks for showing up! I really appreciate it.

I tried the stock recovery and reset the phone but it still did not boot after doing that.

When I boot the phone with it connected via usb I do hear the two tones in windows and can see the SD card as an accessible device.

I can use the command "fastboot devices" and see the device id if I do the boot holding the send + end.

I saw the "tereg" SD-card eject race condition exploit and was really hoping their was an alternative. I guess I will head back to that thread and start reading.
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
I found the thread again and went to download the needed files and the megauploads have been deleted due to inactivity. I will have to see if anyone has them.
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
Also one more issue. on this step how am I supposed to enable debugging if I cannot access the phone as it is?

5. Make sure USB Debugging is turned on on the phone

From the Home screen, press the Menu button -> Settings. Tap Applications -> Tap Development -> Make sure that USB Debugging is CHECKED.

Open a command prompt by going to Start -> Run. Type cmd in the text box, click OK.

If using Linux, open a terminal prompt and change your working directory to the android SDK tools folder and execute the "adb devices" command.

Execute these commands
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
It is my personal opinion that that particular instruction was nothing more than voodoo nonsense.

Here's why: both race conditions exploits are attacks on the recovery boot, NOT the main OS.

The persistent settings which control whether or not the "adbd" daemon runs immediately after bootup are stored in a file in the /data partition, and it is my belief that the recovery boot does not mount the /data partition by default - which means that there is no possible way that such a setting (performed when the normal OS is booted) would affect the recovery boot.

Not that I am confident that the "tereg race condition" exploit was ever very successful - many people did get it to work (upwards of 30 folks or so), but probably hundreds of people tried it and never got it to work.

Good Luck!

bftb0
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
Alright I will give it a go.

I cannot believe the have no way to recover these devices. (I came from the Palm Pre to Android, and their WebOS Doctor could restore ANYTHING so I guess I was spoiled)

Thanks, Bean
[Droid Eris Q&A, Help & Troubleshooting] beantastic:
Well i have tried the race method with pretty much no luck it seems that I have a paper weight with 3 skateboarding androids on it. Very frustrating that a stock phone would go down like this because the battery drained to 0, and there is no way to recover.

I think my best option at this point is to buy an Eris with a cracked screen and do a swap.

http://cgi.ebay.com/HTC-DROID-ERIS-...Cell_Phones&hash=item3f096f0746#ht_4139wt_906

Anyone see a problem with this plan?
[Droid Eris Q&A, Help & Troubleshooting] Skruffy Jew:
Totally of the topic BUT I'm Selling a fully rooted Droid Eris running CM7 port ROM for $90...interested PM me.

"Proudly running Skyraider 4.0 w/CleDinc red theme"
[Droid Eris Q&A, Help & Troubleshooting] phone_cell:
bftb0 Could You Help?

cjslugbug is having the same symptoms that the OP had.

http://xdaforums.com/showthread.php?t=1155453

I hope I was not too presumptuous when I recommended that he should get your help.

Thanks.