Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,786,517 Members 37,125 Now Online
XDA Developers Android and Mobile Development Forum

Announcement: Do You have a Soft-Bricked Eris?

Tip us?
 
bftb0
Old
(Last edited by bftb0; 20th February 2012 at 12:35 AM.)
#1  
Senior Member - OP
Thanks Meter 796
Posts: 2,122
Join Date: Feb 2010
Smile Announcement: Do You have a Soft-Bricked Eris?

The release by HTC of an unlockable bootloader (v 1.51.0000) for the Droid Eris has created a potential opportunity for rescue of some soft-bricked Eris handsets.

Are you an owner of one of these units? There is a decent chance of recovery back to a working state!

(Props go to Android Forums user "scotty85" for figuring this out.)

This (v 1.51.0000) bootloader is rather quirky - it does not allow direct flashing of individual partitions using fastboot - but it does allow flashing of zip files containing recovery, boot, and system partitions via fastboot with the phone in "RUU mode" once the bootloader is unlocked with a procedure from HTC.


If your phone can be booted into its' bootloader (HBOOT, FASTBOOT, or RUU mode), but can not successfully boot all the way up - or it gets stuck in a bootloop during booting, and you only have a stock recovery on the phone, this might be the approach for you.

Rather than write up the whole method to begin with, I'll just ask for responses to see if anyone is interested. And then take it from there if I get some nibbles.

If you think you have a phone you want to try to rescue, speak up - and say a few words about whether the phone can get into different bootloader modes, which bootloader version you have on the phone, and so forth.

Note: at the moment, getting this to work requires getting the fastboot program running on your PC - it is not a phone-only method. The amount of effort at the command line is minimal, but you will need to be able to get your PC talking to your phone to do this.



bftb0
The Following 4 Users Say Thank You to bftb0 For This Useful Post: [ Click to Expand ]
 
Yatyas
Old
#2  
Senior Member
Thanks Meter 10
Posts: 104
Join Date: Dec 2003
Location: Houston
I have a friend who is in this exact situation. Any help you can provide would be great.
 
bftb0
Old
(Last edited by bftb0; 28th February 2012 at 03:03 AM.)
#3  
Senior Member - OP
Thanks Meter 796
Posts: 2,122
Join Date: Feb 2010
Quote:
Originally Posted by Yatyas View Post
I have a friend who is in this exact situation. Any help you can provide would be great.
Take your time, and read and understand this whole post before you begin.

Files Needed:

Collect all the files you will need, get them on to the root folder of your SD card, and verify their MD5 signatures (the copy that makes it to your SD card, not the copy on your computer) :

"rom.zip" - the 1.51.0000 bootloader install payload - here **
MD5: daab6bcbe78c41938a95c4963c5c44e8

custom recovery - either Amon_RA's ("recovery-RA-eris-v1.6.2.img"), or scary alien's trackball-free derivatives here (e.g. the New 1.7.1 version)

"ErisMiscReset_v0.9.zip" here

"MTD_Inspect_v0.9.zip" here

"ErisMTDNuke_v0.9.zip" here (also, please see disclaimer here)

"Eris_RootROM_v2.19.605.1_PB00IMG.zip" from shipped-roms.com. Note that this (also) is renamed to PB00IMG.zip at the appropriate time. **

A custom (dev) ROM, or even a fully stock ROM such as the HTC Eris March 2011 OTA Stock ROM - v2.41.605.6


Installation Method:

Note:

A less thorough method than what is described here, but shorter, is reported here. Even though I built the "ErisMTDNuke_v0.9.zip" repair tool, I do not advocate using it unless it is confirmed to be absolutely necessary. Moreover, in almost every case, having the Eris S-OFF bootloader on a rooted phone is an advantage, and (also) having the "misc" partition "MainVer" value reset back to a low value after fooling with RUUs or PB00IMG.zip installs is a good idea to prevent future disasters. The short method does not document either of these two steps.

Note #2: In any of these procedures, it is important to do so with A FULLY CHARGED PHONE. Do not let the phone sit idle for long periods of time in HBOOT, FASTBOOT, or RUU modes - even with the Eris plugged in to a USB port, in those modes it will discharge very rapidly - about two hours or so. That little green light is your friend.


- get fastboot on a PC working and communicating with the phone in its' current state (with the phone in fastboot mode or RUU mode). Doubtful if I will reply to inquiries about Windows and driver installs - it's covered in gory detail all over the place. Same goes with getting a copy of "fastboot.exe" for windows. (Google is your friend).

- Install the "rom.zip" file for the 1.51.0000 bootloader, (Rename to PB00IMG.zip and install it by booting the phone into HBOOT mode**)

- register with htcdev.com for unlocking this new Eris bootloader & follow the bootloader unlocking instructions (you can skip downloading & running the RUU, as you have installed the bootloader already)

- create a zip file with a custom recovery image in it (named "recovery.img"), and an "android-info.txt" file with MainVer set to 2.42.0000 (see step #3 of this XDA post).

- using fastboot and the phone in RUU mode, flash this zip file ("fastboot flash zip zipfilename.zip") Again, see step #3 of the link above.

- power off the phone and boot into the custom recovery and flash the ErisMiscReset_v0.9.zip file (watch for any errors - stop if you see errors!).

- in the same recovery session flash the MTD_Inspect_v0.9.zip file and determine if you have massive (bad block) corruption in any of /boot, /system, or /data. (See instructions here)

- If the above mentioned partitions only have one or two bad blocks, skip the next step.

- Flash (in recovery) ErisMTDNuke_v0.9.zip

- Re-lock the 1.51.0000 bootloader (phone in fastboot mode) with "fastboot oem lock"

- Flash the Eris Root ROM (from shipped-roms.com), using the HBOOT+PB00IMG.zip install method. The objective of this step is primarily to get rid of the 1.51.0000 bootloader, and install the 1.49.2000 S-OFF bootloader. Note this will stomp on your custom recovery (unless you use the battery pull trick), but that's OK.**

- get the custom recovery back onto the phone - using either the standard Eris rooting tools (Dummies or One-Click), or simply flash it using fastboot (e.g. "fastboot flash recovery recovery-RA-eris-v1.6.2.img")

- one last time: in the custom recovery, flash the ErisMiscReset_v0.9.zip file

- Install a ROM and be happy.


** after using any PB00IMG.zip file, it is a really good idea to rename it ASAP, so that you don't accidentally re-install it by inadvertently powering up the phone in HBOOT mode.


bftb0
The Following 2 Users Say Thank You to bftb0 For This Useful Post: [ Click to Expand ]
 
scotty1223
Old
#4  
scotty1223's Avatar
Senior Member
Thanks Meter 2,261
Posts: 2,237
Join Date: Jan 2011
not much to add. if the notion of downloading the sdk,installing fastboot,adb,etc. is a bit overwhelming you can use this file: http://www.mediafire.com/?hzf1u4bowjewhdq it contains adb and fastboot,and a utility called md5sums,and the needed files to make them work.

simply download,extract(unzip),and place the extracted folder onto the root of the C drive on your PC.

open a command window in windows 7 by clicking the start bubble,and type "command" in the search box. i believe xp is the same,or similar.

once you have a small,black command window open,you can change to the "mini-adb" directory by typing this command:
Code:
cd c:\mini-adb
you can call that folder anything you want,but when you "cd" to it,you must type the exact name the folder is called.

for drivers to get the eris recognized by the PC,you can install htc sync,or use these modified htc drivers from revolutionary public wiki

just holler if you have any questions with any of the above
 
highhacker
Old
#5  
highhacker's Avatar
Senior Member
Thanks Meter 15
Posts: 161
Join Date: May 2008
Location: in the country

 
DONATE TO ME
i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot
devices
Kyocera ECHO -root- new toy
5 lg optimus v -root
5 Droid Eris's on Virgin Mobile
2 android hero's
2 Htc Vouges
Alltel Vogue mp6900 Rooted cynogenMod rls5a
Alltel Vogue WM6.1/Ion Donut 1.6 Duel Boot
12 dozen other smartphones
CDMA 3.8 regged
FCC qualified Cell phone Tech-retired
 
scotty1223
Old
#6  
scotty1223's Avatar
Senior Member
Thanks Meter 2,261
Posts: 2,237
Join Date: Jan 2011
Quote:
Originally Posted by highhacker View Post
i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot
Hopefully we can fix them. Do you have any questions to get started?
 
obonilla30
Old
#7  
Junior Member
Thanks Meter 3
Posts: 21
Join Date: Jul 2010
Location: Chicago
Default wrong nv items wont boot or boot into recovery

Hey guys this phone is on an endless bootloop. I installed the 1.51. hboot unlock the bootloader, flash aman recovery 1.6.2 via Ruu successfully but when I try to boot into recover it continues to bootloop. I already install recovery via hboot but no success. I am willing to try anything with this phone for educational purposes for I dont need the phone but is something that I started over a year ago when I did the mistake with the wrong NV items. I can successfully follow all the step until step 4 but when is time to boot recovery it simply wont or any other file. Tried via regular FASTBOOT recovery.img but no luck. I Still have the S-ON on hboot 1.51. Any suggestions????
 
bftb0
Old
(Last edited by bftb0; 9th March 2012 at 07:26 AM.)
#8  
Senior Member - OP
Thanks Meter 796
Posts: 2,122
Join Date: Feb 2010
@obonilla30

Quote:
Originally Posted by obonilla30 View Post
Any suggestions????
I started a reply and then saw that you were communicating with the right folks over on Android Forums. I was going to send you to exactly the same thread that you found.

If I may make a suggestion - both your posts here and also over there at AF leave quite a bit open to interpretation. For instance, when you mention "bootlooping", you didn't say whether this was for entering recovery from a coldstart (Vol-Up+End/Power), or via navigating from either Fastboot mode (Send+End/Power) or HBOOT mode (Vol-Down+End/Power), and then traversing the menus there to boot the recovery partition. It might be that you tried all three - but you didn't say so. Slow down a little bit and fill in as much detail as you can.

There are TWO methods suggested over in that AF thread - one is to flash (w/ unlocked 1.51 bootloader in RUU mode) a custom recovery to the recovery partition, and the other is to flash a stripped-down version of the (custom) recovery to the boot partition. (You could actually do both in the same flashing operation if you wanted - but note that you can't just rename one of the custom recovery images to "boot.img", because they are too big. But scary alien and scotty85 over there on AF put together something that will fit into the boot partition). That gives you two different ways to get a privileged execution environment running.

cheers

bftb0


PS Not to rehash old painful memories, but do you recall what exactly it was you did when you "did the mistake with the wrong NV items"?
The Following User Says Thank You to bftb0 For This Useful Post: [ Click to Expand ]
 
highhacker
Old
#9  
highhacker's Avatar
Senior Member
Thanks Meter 15
Posts: 161
Join Date: May 2008
Location: in the country

 
DONATE TO ME
Default S###

Quote:
Originally Posted by scotty1223 View Post
Hopefully we can fix them. Do you have any questions to get started?
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide
devices
Kyocera ECHO -root- new toy
5 lg optimus v -root
5 Droid Eris's on Virgin Mobile
2 android hero's
2 Htc Vouges
Alltel Vogue mp6900 Rooted cynogenMod rls5a
Alltel Vogue WM6.1/Ion Donut 1.6 Duel Boot
12 dozen other smartphones
CDMA 3.8 regged
FCC qualified Cell phone Tech-retired
 
bftb0
Old
(Last edited by bftb0; 28th March 2012 at 07:42 AM.)
#10  
Senior Member - OP
Thanks Meter 796
Posts: 2,122
Join Date: Feb 2010
Quote:
Originally Posted by highhacker View Post
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide
You will always get "remote not allowed" with a S-ON bootloader, or with the 1.51.000 bootloader in the locked state. And you will probably also get that error even with a 1.51.0000 bootloader in an unlocked state if you try putting a "boot.img" or "recovery.img" file in the zip. Don't bother using fastboot with a 1.4x.00 S-ON bootloader - it doesn't ever work for anything useful.

Note also that the steps given above need to be performed in sequence and each step needs to succeed. There is no point in doing a 2nd or 3rd step if the first step fails.

As for the PB00IMG.zip install of the 1.51.0000 bootloader, when you boot the phone into HBOOT mode, you should see SOMETHING different happen - even if it is a failure of some sort - than how HBOOT behaves when there is no PB00IMG.zip file on the SD card. If the phone behaves identically whether or not you have the SD card in place, then that means you mis-spelled the name of the PB00IMG.zip file, or didn't put it in the top-level folder of the SD card. Even in the case where it is there on the card, but corrupted, you will see a different behavior of the HBOOT from when there is no PB00IMG.zip file present.

Unfortunately, your post above gives no details about this. That means that anybody that is willing to try and help you is forced to guess about what you are seeing your phone do.

bftb0

The Following 2 Users Say Thank You to bftb0 For This Useful Post: [ Click to Expand ]
Tags
1.51, bootloader, eris, rescue, unlocked
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes