Announcement: Do You have a Soft-Bricked Eris? - Droid Eris Q&A, Help & Troubleshooting

Announcement: Do You have a Soft-Bricked Eris? - Droid Eris Q&A, Help & Troubleshooting

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

I have a friend who is in this exact situation. Any help you can provide would be great.

Yatyas said:
I have a friend who is in this exact situation. Any help you can provide would be great.
Click to expand...
Click to collapse
Take your time, and read and understand this whole post before you begin.
[size=+2]Files Needed:[/size]
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
[size=+2]Installation Method:[/size]
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

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

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

highhacker said:
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
Click to expand...
Click to collapse
Hopefully we can fix them. Do you have any questions to get started?

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????

@obonilla30
obonilla30 said:
Any suggestions????
Click to expand...
Click to collapse
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"?

S###
scotty1223 said:
Hopefully we can fix them. Do you have any questions to get started?
Click to expand...
Click to collapse
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

highhacker said:
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
Click to expand...
Click to collapse
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

defiantely the first step is to get 1.51 onto the phone. in addition to the above,make sure that your sd card is formatted FAT32. i cant remember if this is important for the eris,but it is crucial for other dervices..
what you should see when a properly named PB00IMG file is placed on the root of the sd card,is a quick flash of green writing,then status bars on the upper right corner of the screen as the phone finds and checks the file,followd by a "do you want to update" prompt.
another common error with a PxxxIMG file on any devices,is that the decive must see PxxxIMG.zip. in the case of the eris,the file on the phone must be "PB00IMG.zip". the common error part comes from naming the file with windows. lots of folks will type in the .zip,forgetting that windows naturally adds and hides the file extension. therefore,typing in "PB00IMG.zip" actually names the file to "PB00IMG.zip.zip" in rarer cases,not typing in the ".zip" with windows if configured differently may end up in the file just being "PB00IMG" wish will not be found either.
so to recap
-check sd card for FAT32
-check the name of PB00IMG on the sd card. try adding or removing the ".zip"
-make sure PB00IMG is on the top level of the sd,not hidden inside a folder.
let us know how that goes
once you get the 1.51 hboot onto the phone,the next step is to unlock it. just holler if you have questions on htcdev's directions.

One of the simple mistakes that people make is when they rename the "rom.zip" file, they rename it as
PBOOIMG.zip (PB "oh-oh" IMG.zip)
instead of the correct spelling
PB00IMG.zip (PB "zero-zero" IMG.zip)
As scotty and I both pointed out, if you have a correctly named file on there in the top-level folder, you will see *something* different happen, even if the file is corrupted.
If you don't see something different happen, then the problem is the SD card format, a mis-spelling of the file name (I recall some people transferring files from their PCs, ending up with a file named "PB00IMG.zip.zip"), or the file is not in the top-level folder of the SD card.

bftb0 said:
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
Click to expand...
Click to collapse
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..

have you tried renaming "PB00IMG" without the zip?
you can also try flashing it as an RUU,wich eliminates the sd card,and the name of the file from the equation.
place rom.zip(for 1.51 hboot) into the folder containing fastboot and hboot..
-place the phone in fastboot.
-assuming you leave rom.zip named "rom.zip",open a cmd window and enter the following:
fastboot oem rebootRUU
fastboot flash zip rom.zip
it will do some stuff on the screen,then say "finished". then:
fastboot reboot-bootloader
thaT should boot you back into fastboot,where you should see 1.51.0000 locked hboot.
if you get a "failed" error instead of the above results,let us know what that error is and we can hopefully figure out what to do to make the flash work
if you get the 1.51 hboot,next step is to unlock it

highhacker said:
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..
Click to expand...
Click to collapse
The behavior you describe is EXACTLY how HBOOT mode behaves ... when there is no file named PB00IMG.zip on the root folder of the SD card. When I said "you will see something different happen", what I meant is something in addition to that list of file names rapidly scrolling by.
No doubt you are finding this frustrating.
In the past, there were two other reasons why this occurred:
1) People were using Windows Explorer on the PC. By default, it has an option turned on which is something like "hide file name extensions of known file types". With this (default) behavior, it is possible to rename the file PB00IMG.zip.zip, and yet what would be seen on-screen in Windows Explorer would only be "PB00IMG.zip". Turn that option off, or just use the DIR command from a command prompt to see if that is what happened.
2) Other users reported banging their heads into this without any luck, and then mysteriously solving the problem by formatting the SD card some other way than they previously had done. I don't have any further insight into the details here, other than this: the SD card should NOT be partitioned. If you got a box of phone which were previously rooted, it is possible you have a partitioned card (esp. if the phone had a 2.1 dev ROM on it)
The method scotty details above should allow you to side-step this problem, although you will have to get fastboot communicating with the phone (PC driver installs, etc).
To re-iterate though: if HBOOT discovers a file on the SD card named PB00IMG.zip, you will see something happen in addition to that list of file names rapidly scrolling by and disappearing. If you don't see anything additional - then HBOOT is not finding the file (for some reason or another).
bftb0

I am having an issue getting Amon recovery on my soft-bricked Eris.
I have the 1.51 bootloader unlocked but when I go to run the commands I get the following:
C:\adb>fastboot.exe flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.827s]
writing 'zip'...
FAILED (remote: not allow)
finished. total time: 0.842s
If I try the RUU method it just sits at parsing:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 2.980s]
finished. total time: 2.980s
C:\adb>fastboot flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.842s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
Also running the RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe and replacing the rom.zip did not work or trying to flash Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
The version it says I have it 2.42.0.0
Any ideas?
Thanks!

sorry it took me a couple days to reply to this. i believe the prollem your having is due to the android info document,specifically the hboot pre-update value. i had the same prollem starting in this post.
the android info i was using that was hanging at 'parsing' was:
Code:
ModelID: DESI****
ModelID: PB001****
ModelID: PB00100
CIDNUM: 11111111
CIDNUM: VZW__001
hbootpreupdate: 3
MainVer: 2.42.0.0
i pulled the one from the rom.zip extracted from the 1.51 hboot ruu and it worked fine.heres what it looked like:
Code:
CIDNUM:11111111
modelid: PB0010000
cidnum: VZW__001
cidnum: UTSI_001
mainver: 2.42.0.0
hbootpreupdate:12
try repacking your recovery with that android info,if its not what youre allready using.

zmanzbo,
What were the contents of the "recovery.zip" file you were trying to flash? (specifically, were there any .img files contained in it?)
Even when the 1.51.0000 bootloader is in the unlocked state, the flash will be disallowed if you have certain .img files in there (radio.img or recovery.img iirc - but don't quote me on that, I would need to go and re-read scotty's notes over in the AF thread).
Apologies for the vagueness - I'm afk at this time and am typing this from my phone.
bftb0

Well I got it working. I went to the link Scotty posted and downloaded tiny rescue recovery flashed that and then was able to run the various files listed in the original post bu bftb0. After that I was able to flash Eris_RootROM_v2.19.605.1_PB00IMG.zip. I am back in business now.
What was weird is that the contents of my recovery.zip were just the recovery.img and android-info.txt. The android-info.txt file had the same info as the 2nd one Scotty posted.
Thanks alot for the help here. Really appreciate it!
Cheers!

cool.
I'm glad you put the 1.49.2000 S-OFF bootloader on the phone afterward. It is always a good idea to have that bootloader (rather than the 1.51.0000 "unlockable" bootloader) installed, as the ways in which rescue/repair can be performed are more numerous (in case anything goes wrong in the future).
bftb0

Related

[SOLVED] Anyway to Unbricked a Droid Eris?

All I can see is the HTC logo with 4 ! inside of a triangle on each corner. This is a been bricked for a long time and I cant remember how it happened but just wonder is there is anyway to fix it
Thanks,

The state your phone is in sounds similar to this
http://forum.xda-developers.com/showthread.php?t=824290
but there is no way to be sure of that, based on the zero details you provided.
Read the ENTIRE POST, not just part of it (it is quite long).

WOW, exactly the same problem this phone has!
If I remember right it was a mix up with ClockworkMod recovery.
That was a very nice recovery, I will have to read and learn all that. That's a lot of info and stuff that I will have to learn to try to fix this phone.

I think all that is AWAY over my head... lol
OMG my head hurts now... lol

stick2e said:
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
Click to expand...
Click to collapse
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0

bftb0 said:
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
Click to expand...
Click to collapse
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!

stick2e said:
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
Click to expand...
Click to collapse
Well, first off - you should say what version of the boot loader you have. It is shown on the fastboot screen. If you already have the 1.49.2000 S-OFF bootloader this current step can be skipped, And you can proceed directly to flashing a recovery using fastboot from the pc. If you do not have the S-OFF bootloader the whole point of this current step is to get it on the phone - in which case you should be using the ROOT PB00IMG.ZIP file, not the Leak-V3 PB00IMG.ZIP file.
All Eris RUU and PB00IMG.ZIP files can be found at:
http://forum.xda-developers.com/showthread.php?t=909921
When the RUU program is running, just prior to the moment when you would begin flashing to the phone, you use the search function on your PC in the folder
C:\Documents and Settings\<your_user_name>
(Edit - in Win7, C:\Users\<your_user_name> )
to look for the file named "rom.zip". (You will probably need to twiddle the dumbass Microsoft setting which prevents searching for hidden files and folders.)
Then, you delete the rom.zip file, rename the ROOT PB00IMG.ZIP file to rom.zip, and drop it into the same location.
Before starting this step, make sure your phone is completely charged and also be sure to verify the file size and md5 checksum of the ROOT PB00IMG.ZIP file you downloaded.
As I mentioned above if you already have the S-OFF bootloader present on your phone, this operation is not necessary and we can proceed to flashing a recovery using the fastboot program on the PC.
Lemme know how it goes.

PS - It would be helpful for you to answer a few questions about your current skill set and computer setup:
- have you used either the "fastboot" or "adb" programs in the past on your pc?
- if not, do you know how to verify communication with the phone in fastboot mode?
(Note that running the RUU utility will install drivers on your PC)
The original Amon_RA recovery for the Eris can be found here:
http://forum.xda-developers.com/showthread.php?t=648025

I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.

stick2e said:
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
Click to expand...
Click to collapse
"fastboot devices" when the phone is in fastboot mode.
adb only applies when the normal OS is running with USB debugging turned on, or if the Amon_RA recovery is booted.
What bootloader version do you have?

This is where the phone is right now.
1.49.0000 S-ON bootloader
When I get home today I will look for the proper img file and try the RUU option to see if I can get the S-OFF in there. We will see.

If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot, then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
PS - don't let the phone sit in fastboot mode for extended periods of time - it will discharge rapidly even if it is plugged into the charger

This thread honestly scares me and I hope this never happens to me lol

willwgp said:
This thread honestly scares me and I hope this never happens to me lol
Click to expand...
Click to collapse
All you need to remember is this:
newb + Eris + ClockworkMod = disaster waiting to happen
In almost every bricking that has been reported here on the (XDA) Eris forums, ClockworkMod (or running the battery down to very low charge levels) was involved.
What is also notable is that in almost every case, the folks that got into trouble:
- got their rooting instructions from non-XDA sites (e.g. unrevoked, z4root, unlockr)
- could not clearly explain what they had been doing immediately prior to the event - even after repeatedly being asked to do so,
- were unaware what ROM signing is about (or that ClockworkMod doesn't perform it)
The second observation seems to imply a behavioral trait of innattention or sloppiness.
In the hands of people that are experienced, ClockworkMod seems to behave correctly.
For the moment though, let's stay on topic and see if we can revive stick2e's phone. At the moment, I am guessing that there is about a 30% chance of that. We'll find out more when we hear the result of his/her flashing attempt.
bftb0

I think this is going to work!!!! Thinks are looking better.
I try to flash the RUU but replace the rom.zip (what a pain to find it!!!) with the root rom (PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip) and now I have to load a rom in the sdcard to flash the phone. Fingers crossed we will see.
I'm downloading a ROM now.

RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!

stick2e said:
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
Click to expand...
Click to collapse
DId you rename the new PB00IMG.zip file to rom.zip?

bftb0 said:
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot,
Click to expand...
Click to collapse
Ok, HBOOT-1.49.2000 and S-OFF
bftb0 said:
then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Click to expand...
Click to collapse
C:\sdk\tools>fastboot flash recovery recovery-RA-eris-v1.6.2.img
sending 'recovery' (3834 KB)... OKAY [ 0.826s]
writing 'recovery'... OKAY [ 1.357s]
finished. total time: 2.183s
bftb0 said:
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
Click to expand...
Click to collapse
RUU Utility report ERROR [110]: FILE OPEN ERROR
Parsing... [download ZIP]
[1] User Data - OK
[2] System - Fail-PU
[3] Recovery - OK
[4] Radio_V2 - OK
[5] Boot - Fail-PU
Partition update fail!
Update Fail!

Gimme a minute to fire up a real computer instead of this stupid phone browser.

Well, I fastboot recover revery-RA-eris-v1.6.2.img but nothing happen now :-(
Before used to take me to RA Recovery but now is not.

[SOLVED] Radios will not flash !!!

So in my efforts to update my phone, I downloaded the July 2010 OTA radio. I also tried flashing the sprint radio 2.42.02.10.29
To my surprise, neither of them worked. It's like I am permanently unable to flash a radio. I can flash roms, themes, boot animations and everything else, just not radios. If anyone has any suggestions for this I greatly appreciate it. Here are the radios I've tried to flash and where I got them from.
2.42.01.04.27 from http://forum.xda-developers.com/showthread.php?t=728529
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?

spc_hicks09 said:
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?
Click to expand...
Click to collapse
So you are saying that you followed those instructions exactly and it did not flash?
In other words, you:
- copied that 2.42.02.10.29.zip file to the root of your SD card;
- you checked the MD5 of that file to make sure that it was fully downloaded;
- restarted in recovery and flashed that .zip file;
- you rebooted the phone and a very different screen appeared;
- it went back to Recovery with a message at the bottom saying "formatting cache..."
- you waited about a minute (it says 5 seconds, but I waited longer) and then rebooted the phone
And your radio baseband version did not update?

That's exactly what I'm saying. I flashed both radios and waited 10-15 on both of them and neither one of them did anything !?! So confused
Sent from my Ginger Tazz using XDA App

Well, if it's any consolation I haven't noticed anything different about that radio. People report that they get more "bars", but that's just a display thing - it doesn't mean that they get better performance or signal from the radio version.
You can try unrooting with btfb0's Flashback21 ROM - there is a version that flashes the current Verizon radio - and then re-root after that and see if it updates the radio for you.
http://forum.xda-developers.com/showthread.php?t=792026
Take the version of that with the radio, obviously.

What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img

bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
At work now but I will check it out when I get home. Im not sure how to check some of the stuff you're talking about so I will need your guidance later if possible.
Sent from my Ginger Tazz using XDA App

bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
Recovery Version
RA-eris-v1.6.2
On HBOOT screen I see this:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
FEB 8 2010, 00:08:56
Radio that will not change or anything is:
2.42.00.04.12 which is the pre July 2010 OTA update Radio
Yes you presumed right, I am "rebooting" through the recovery menu as opposed to pulling the battery or anything else.

Executive summary: just get the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash radios using fastboot (being very very careful to verify MD5 signatures). If you are going to be flashing stuff to your phone frequently, you really want the S-OFF bootloader on your phone for disaster recovery reasons anyway.
OK, I ran a fairly long experiment on your behalf, and it went like this:
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
- flashed older radio (2.42.00.04.12) image file back into place using fastboot (not Amon_RA)
- Downgraded my bootloader to 1.49.000 S-ON using fastboot
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.0000 S-ON)
- Upgraded my bootloader using "erisengspl.zip" + Amon_RA **** back to 1.49.2000 S-OFF
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.2000 S-OFF)
- rebooted once (into OS) and then booted into recovery
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
So, I was expecting to see that your trouble had something to do with your bootloader version - especially after seeing the first failure that I observed ... but then I was able to get it to both succeed and fail using the same S-OFF (1.49.2000) bootloader - and the only thing which changed was that I rebooted once between the trial that succeeded, and the trial which failed.
At that point, I did not go back and re-run any trials with the 1.49.0000 S-ON bootloader to see if I could get it to suceed - because it was evident that something else was going on.
Some of this is not entirely unexpected. When you flash either of the firmware images (either the radio or the bootloader image files), it is actually the bootloader that does the flashing, not the recovery boot: that's why the recovery tells you to "reboot .... to complete the installation". What the recovery does is to "stage" the image file (in /cache, I suspect), and then write some instructions into the "misc" partition that tell the bootloader what to do the next time the phone resets.
That's why - when things work correctly - the phone momentarily goes dark, you see a graphic image on the screen (that suggests that flashing is taking place), and then the phone reboots again ... and ends up back in the recovery boot !! (You will have to take my word for it, if you don't remember what it looks like). That "flashing" graphic image is put up on the screen by the bootloader; when it finishes up, it chains back to the recovery boot ... and communicates to the recovery (via the either the misc partition or the cache partition), "hey, wipe the /cache partition as soon as you start up". (Note the implications - the next OS reboot will need to rebuild the dalvik-cache(s))
The thing is, "misc" gets written to every time the phone shuts down or boots up - whether we are talking about starting from the OS, from the recovery boot, from fastboot mode, or from RUU mode - and how many different ways are there to reboot?
- battery pull
- fastboot reboot-recovery
- fastboot reboot
- adb shell reboot bootloader
- adb shell reboot recovery
- reboot Amon_RA from menu
- (cold start) -> fastboot mode -> hboot mode -> recovery
- (cold start) -> hboot mode -> recovery
- (cold start) -> recovery
In any event, if you want to tease this all out, with some experimenting around with the way that you get into the recovery boot, you can probably get the flashing method to work. ( For instance, you could probably use an adb shell session with Amon_RA running to "flash_image misc misc.img", where "misc.img" is the image file from jcase's "Flash Any RUU post" - and then use the flashable radio .zip file from within Amon_RA. )
But, as I mentioned above, it is a lot easier to just punt and install radios using fastboot and the S-OFF bootloader. Just be sure you have triple-checked everything before you hit the Enter key.
bftb0
**** EXTREMELY DANGEROUS UNLESS THE EXISTING BOOTLOADER IS 1.49.0000 - "erisengspl.zip" has hard-bricked phones that had 1.46.0000 bootloaders!

I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?

spc_hicks09 said:
I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?
Click to expand...
Click to collapse
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.46.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0

Here you go...
Introducing...
ErisMiscReset_v0.9.zip :
Size: 53,784 bytes
MD5: aeb8f3d9b2ab39379b8ee563c76efee0
Credits: jcase (for the misc.img file); Amon_RA (for the flash_image binary - from his v1.6.2 Eris recovery)
This doesn't do anything special - it just flashes the embedded "misc.img" file (jcase) to the "misc" partition. It could be done the hard way (with adb and the command line), but this makes life a little easier.
bftb0

bftb0 said:
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.47.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Ok quick question. After doing some digging, I found a post where jcase was working on a flashable zip that would give 1.49.2000 S-OFF. Someone noted that he no longer had an Eris and abandoned the project after pulling it. Well someone else "drewrobinso" picked up where jcase left off and finished the zip and in the post, starting at post 32 he posted that he fixed jcase's file and people after that say it "works perfectly." So I was wondering what your opinion is on this method. It can be found here.
http://forum.xda-developers.com/showthread.php?t=742735&highlight=engineering+bootloader&page=4
Here are the instructions they give for the hboot1492.zip
1) Download hbootupdate.zip
2) Placed it on root of sdcard
3) booted Recovery
4) nand backup
5) flashed hbootupdate.zip
6) rebooted (with menu) after the install of the hboot.zip
7) waited untill it came back to the recovery screen with " formatting cache..." at the bottom.
8) Waited for a few min then pressed reboot from the menu again.
9) waited for it to boot up and rebooted in to hboot as S-OFF was there
10) enjoyed it

spc_hicks09 said:
So I was wondering what your opinion is on this method. It can be found here.
Click to expand...
Click to collapse
Probably equivalent to the "erisengspl.zip" file (I haven't used it or looked at it) - you can find both, unpack them, and compare the differences. They should be extremely similar. I think the reason that jcase pulled his effort is because someone ended up with a brick - but I can't be 100% certain of that.
The thing you should be aware of is the lack of testing that goes into stuff on XDA. That "erisengspl.zip" floated around on XDA for months, and a few people in fact used it successfully. Those few people happened to be "Leakers" (with 1.49.0000 S-ON) on their phones.
The first person to try it with the 1.46.0000 S-ON bootloader on his phone hard-bricked his phone.
I suppose that it will work for you - but, flashing the bootloader is the most dangerous thing you can do to your phone. I prefer to be conservative about it.
LOL, I just realized that I said that after flashing it three times today.

PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip

bftb0 said:
PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip
Click to expand...
Click to collapse
Oh lol, sorry about that. Ok so if I use the misc flashable zip, which PB00IMG.ZIP would I want for the S-OFF, Leak 3 or the Root one ? I'll just use the method you're suggesting but I have no idea which PB00IMG.ZIP to use.
Nevermind lol obviously it would be the Root one since it's the only one with the Engineering Bootloader. Ok so if I downloaded the misc reset file and the PB00IMG.ZIP, do I flash the misc reset zip then the PB00IMG or what ?

bftb0 said:
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Flashed the zip and got the PB00IMG loading now. So far so good !
Now saying 1.49.2000 S-OFF !!!! Now it's going through and loading the system, recovery, radio_v2. Everything says -OK so far !
Rebooting now.......on the Verizon splash screen.............now it's not going anywhere just stuck on the Verizon logo !
Nevermind it booted ! Just took a while to load up !!!! Soon as everything is done loading I will check and see what the HBOOT screen says now.
Software Info:
Firmware - 2.1
Baseband - 2.40.00.01.22
Kernel - 2.6.29-5898f66b [email protected] #1
Build Number - 2.19.605.1 CL123435 test keys
Software Number - 2.19.605.1
Browser Version - WebKit 3.1
PRI Version - 2.11_002
PRL Version - 52219
ERI Version - 5
Rooting now with Eris 1 Click and will post HBOOT info in a few minutes.

spc_hicks09 said:
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Click to expand...
Click to collapse
- Get the Root PB00IMG.ZIP file from this XDA post
- Verify it's size and MD5 signature on the copy you transferred to the root folder on your SD card.
- Put your phone on a charger.
- While it is charging, read through this post on AF (lots of pictures)
- Wait until fully charged, and
- Boot into recovery and make a Nandroid backup.
- (Optional: wipe data/factory reset)
- Flash the ErisMiscReset_v0.9.zip
- Power the phone off
- Boot the phone into HBOOT mode (Vol-Down+End)
- Follow the instructions in that Android Forums thread (PB00IMG.ZIP install)
Note that if you do not do the battery-pull trick, you will be overwriting everything on the phone. (That's OK because you have a backup, right?). If you did the "battery pull trick", you are done.
You can re-root the "root ROM" at that point, or, just skip that and use fastboot on your PC to directly flash the recovery to your phone. Put the phone in fastboot mode (cold-start with Send+End), and then test connectivity to the PC with:
Code:
fastboot devices
You should see your phone ID number if you are communicating correctly. Then,
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Then, boot into Amon_RA directly by cold-starting the phone with Vol-Up+End, and "wipe data/factory reset" and restore your Nandroid backup.
Finally, you can flash a radio image directly at this point. (Note that we are not talking about a zip file, but the individual "radio.img" file that you would dig out of the 2.42.blahblahblah.zip file). Restart the phone in Fastboot Mode (Send+End) and
Code:
fastboot flash radio radio.img
Don't forget to remove the PB00IMG.ZIP file from the root folder of your SD card - otherwise you will forget about it and the next time you boot into HBOOT mode, the bootloader will start loading it up again.
HTH
bftb0

This explains a lot... Thanks.
I've not been able to figure out why my radio won't update until now.

And it allllllllll WORKED !!!!
HBOOT Info:
PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.40.00.01.22
Jan 24 2010, 22:35:57
Dude you are a frickin genius !!!!! LOL
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
You should make a main topic in Developement about your new method to get S-OFF. That was so much more simple than ANYTHING else I found !
Where do I need to have the Radio.img file because I have it in the ADB folder right now, trying to flash through fastboot but it keeps saying "error cannot load radio.img"

spc_hicks09 said:
And it allllllllll WORKED !!!!
Click to expand...
Click to collapse
You've now experienced "old school Eris root".
spc_hicks09 said:
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
Click to expand...
Click to collapse
You certainly should be able to do it with fastboot. As I said before, I'm not precisely sure what was causing your Amon_RA installs to fail.
Just make sure you always, always, always verify file MD5 sigs of image files before flashing them with fastboot.
bftb0

bootloader 1.49 and S-on NEED HELP!

[[[[[[[[[[[[[[[[PROBLEM SOLVED]]]]]]]]]]]]]]]]]]
hi can someone please help me? the phone is able to boot into HBOOT. a normal boot brings up the skateboard droids and stays on it for good. This is what is shown when i go into hboot.
PB00100 XC SHIP S-ON
HBOOT- 1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
FEB 8 2010, 00:08:56
HBOOT
<SEND> FastBoot Mode
<VOL UP> Recovery
there is no recovery on this phone, pressing the VOL UP button just takes the phone to the 3 skateboard screen and gets stuck there.
Can someone please advise me on what to do? Thank you in advance.

Well, I think your best bet may be to try do a factory reset. From http://www.shipped-roms.com/index.php?category=android&model=Desire :
1. With the phone turned off, press and hold the Volume Down, Send (green phone) and Power buttons. The device will turn on. Keep holding down the keys unto you see a screen to clear storage.
2. Press the track ball.
3. Follow the instructions to complete the hard reset.
Click to expand...
Click to collapse
If that does not work, you may be able to install the Leak V3 PB00IMG.zip. You can download it from here: http://www.shipped-roms.com/downloa...sire&file=Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
Rename that file to PB00IMG.zip (that's letter P, letter B, zero, zero, letter i, letter M, letter G period letter Z, letter i, letter P. Of course you can just delete the starting portion of the name and leave the PB00IMG.zip.)
Copy it to your SD card (you will probably need a USB SD card reader for your computer to copy the file over)
This post walks you through the steps to install the image file: http://androidforums.com/eris-all-things-root/75384-visual-example-pb00img-zip-update-method.html
Alos, whether it works or not (it may not), make sure to delete the PB00IMG.zip file from the SD card as soon as you can. Let us know whether it worked or not.

Hi thanks for the reply
i tried the hard reset, it went through that process without any problems. it rebooted and went straight back to the 3 skateboards. So i did your second suggestion. I downloaded the leak v3 pb00img.zip and renamed it to PB00IMG.ZIP as you said i should and copied it to my Sd card. I started the phone in hboot again. I tried to upload a picture of what it did, but forum rules wont let me till 10 posts.
Anyway it ran through the whole "SD checking" and said no image! for everything and just disappeared and i was left at the same hboot menu as before. What to try and do now ?

god_damn_eris said:
Hi thanks for the reply
i tried the hard reset, it went through that process without any problems. it rebooted and went straight back to the 3 skateboards. So i did your second suggestion. I downloaded the leak v3 pb00img.zip and renamed it to PB00IMG.ZIP as you said i should and copied it to my Sd card. I started the phone in hboot again. I tried to upload a picture of what it did, but forum rules wont let me till 10 posts.
Anyway it ran through the whole "SD checking" and said no image! for everything and just disappeared and i was left at the same hboot menu as before. What to try and do now ?
Click to expand...
Click to collapse
If you renamed it in Windows, are you sure that you didn't have the file extensions turned off, so that the file name is actually PB00IMG.ZIP.ZIP? I'm on a Mac, and can't recall on Windows how to turn on display of file extensions by default, but that is always a possibility.
I'd see if that's the case first. Make sure that the file name is exactly PB00IMG.ZIP

i doubled checked, its correct the way i renamed it. in windows we don't put the .zip extension, we would just rename it as PB00IMG. Anyway i tried it both ways, i did it as PB00IMG.ZIP just in case and it did the same thing. It goes through the "Sd checking" and gives the No image! right under, then goes back to the hboot with the <send> and <vol up> menu.
stumped

god_damn_eris said:
i doubled checked, its correct the way i renamed it. in windows we don't put the .zip extension, we would just rename it as PB00IMG. Anyway i tried it both ways, i did it as PB00IMG.ZIP just in case and it did the same thing. It goes through the "Sd checking" and gives the No image! right under, then goes back to the hboot with the <send> and <vol up> menu.
stumped
Click to expand...
Click to collapse
Did you put the file into a folder on the SD card or at the root of the SD card? Are you sure that there are no spaces in the file name, either at the start (before the P) or at the end (before the period) - it has to be exactly PB00IMG.ZIP. Also, what is the file size? Is it 104.8 MB (or 109,946,224 bytes)?
Also, see this: http://forum.xda-developers.com/showpost.php?p=24186683&postcount=15
I'm going to be traveling tomorrow - hopefully somebody else will see this.
If that still doesn't work, you can try installing the RUU: http://www.shipped-roms.com/downloa...WWE_2.36.605.1_release_signed_with_driver.exe
Connect the Eris to your computer and run that file - hopefully it can update the phone.
By the way, if you can, take some time to charge the battery with the phone turned off - running in HBOOT kills the battery fast, and the last thing you want is for the phone to be in the middle of a PB00IMG flash and fail because the battery ran out.
If that does not work, your problem is not exactly the same, but this procedure may work: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html - well, starting at post 15: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html#post4475687
It's a lot of steps, but it's worked a few times before.

I placed the PB00IMG.ZIP (i've looked at it several times to make sure im doing what you said and spelling it the way you want me to.) in the Root of my SD card, i dont have any other files on the sd card, just that zip file.
I right clicked it and went to properties via windows explorer (I've also checked to see using the DIR command in command prompt.) It shows no spaces before or after and no .zip.zip.
The file is size: 104 MB (109,946,224 bytes)
Size on disk: 104 MB (109,948,928 bytes)
I read the first link you supplied to me in the last post by bftb0, im not sure if the sd card is partitioned or not, he says it SHOULD NOT BE, so i'll try and reformat the sd card first before trying anything else. Will let you know how it goes. Thanks for helping again, greatly appreciated.:good:

Okay so i formatted the sd card by putting it in my brothers phone and mounting it to my laptop. Right clicked it and hit format. I kept it at the default format setting FAT. Reloaded the PB00IMG onto the sd card and put it into the eris. Started up in HBOOT, it did the same thing as before, gave me the No image, and went back to the <send> and <vol up> menu.
I let the phone charge over night, it had the orange led, and it had the green led when i woke up, so full battery charged. i downloaded the RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe and followed the instructions step by step to run the RUU. the update image version had a from "blank" to 2.36.605.1,the phone went into the bootloader, it showed a black picture with the words HTC on it, It said it was clearing data, then it started sending the rom image to the phone. About 3 or 4 mins later it said updating signature and then gave me an error [131]: customer ID Error. The RUU cannot update your android phone. Please get the correct RUU and try again. I hit exit and its reboots to the 3 skateboard droids with the letters "fastboot usb" highlighted in red.
Im gonna start reading the last link you gave me, crossing my fingers something will work.

I tried something different, i formatted the sd card as FAT32 and placed the PB00IMG on the card. I wasnt sure if this was gna do anything but i did it. i put it into the eris and fired up HBOOT, this time it actually picked up the PB00IMG file, it even brought up the progress bar on the top right, it did its thing and processed all the way but gave me this error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
im assuming this is the same error related to that Error [131]: customer ID i got from the RUU.
i think i'll wait and get some feedback from anyone who can help me out with this till Doogald gets back.

god_damn_eris said:
I tried something different, i formatted the sd card as FAT32 and placed the PB00IMG on the card. I wasnt sure if this was gna do anything but i did it. i put it into the eris and fired up HBOOT, this time it actually picked up the PB00IMG file, it even brought up the progress bar on the top right, it did its thing and processed all the way but gave me this error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
im assuming this is the same error related to that Error [131]: customer ID i got from the RUU.
i think i'll wait and get some feedback from anyone who can help me out with this till Doogald gets back.
Click to expand...
Click to collapse
I think that you need to do what I suggested here:
doogald said:
If that does not work, your problem is not exactly the same, but this procedure may work: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html - well, starting at post 15: http://androidforums.com/eris-all-things-root/556826-stuck-boot-up-screen.html#post4475687
It's a lot of steps, but it's worked a few times before.
Click to expand...
Click to collapse
My guess is that there is some sort of error with the flash storage on the phone and that procedure will walk you through the steps. Unfortunately you cannot root the phone at this point without a running OS on the phone (that I am aware of). That procedure above (it's a lot of steps) is about the only thing that I can think of that will work with 1.49.0000 S-ON.

doogald said:
I think that you need to do what I suggested here:
My guess is that there is some sort of error with the flash storage on the phone and that procedure will walk you through the steps. Unfortunately you cannot root the phone at this point without a running OS on the phone (that I am aware of). That procedure above (it's a lot of steps) is about the only thing that I can think of that will work with 1.49.0000 S-ON.
Click to expand...
Click to collapse
okay so i was able to get all the files, the htc drivers and also abd and fastboot. I got to the step where it said for me to put the rom.zip (hboot 1.51) in the same folder as the fastboot and adb. iit gave me an error though :
sending 'zip' (180 KB)...
OKAY [ 0.327s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.660s

Try the PB00IMG.ZIP method. Rename the rom.zip file to that name, place that file on the SD card, and restart the phone in HBOOT mode.

doogald said:
Try the PB00IMG.ZIP method. Rename the rom.zip file to that name, place that file on the SD card, and restart the phone in HBOOT mode.
Click to expand...
Click to collapse
I renamed the rom.zip to PB00IMG and placed it in the sd card. Fired up hboot but still getting this error:
CID incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes

Is there any way to get around this error? Seems like its the only thing thats blocking me from from being able to do anything to my phone. Is there anyone else out there that has had this problem before, if so, please advice on how you solved it.

I got a friend who has the Riff JTAG box, i asked him to fix the IMEI and CID and also if he could downgrade the hboot to either 1.46 or 1.47 with S-OFF. Im sending him the phone to look at. I should have it back in a couple of days. I'll report back when i get it back. Thanks Doogald for all your help.

god_damn_eris said:
I got a friend who has the Riff JTAG box, i asked him to fix the IMEI and CID and also if he could downgrade the hboot to either 1.46 or 1.47 with S-OFF. Im sending him the phone to look at. I should have it back in a couple of days. I'll report back when i get it back. Thanks Doogald for all your help.
Click to expand...
Click to collapse
You're welcome. Sorry it didn't work out this way.

doogald said:
You're welcome. Sorry it didn't work out this way.
Click to expand...
Click to collapse
Dont be sorry, you have been more than helpful and i really appreciate your effort to help me :good:, i hope my friend is able to do something with the riff box.

full memory dump needed?
Hi Doogald,
my friend is trying to repair that CID error, his asking me if i can get the full memory dump from a working phone. Im not sure what he means. But he says he needs to copy the boot memory from a working phone to my phone in order to fix that CID error. Would you know where i can find the dump file?

god_damn_eris said:
Hi Doogald,
my friend is trying to repair that CID error, his asking me if i can get the full memory dump from a working phone. Im not sure what he means. But he says he needs to copy the boot memory from a working phone to my phone in order to fix that CID error. Would you know where i can find the dump file?
Click to expand...
Click to collapse
Not sure. Ask him *exactly* in details what he needs. I'm not sure what "boot memory from a working phone" means.

doogald said:
Not sure. Ask him *exactly* in details what he needs. I'm not sure what "boot memory from a working phone" means.
Click to expand...
Click to collapse
The guy is russian so his english is broken, i'll quote what he said:
so I connected it back to get the resurrector report - unfortunately it has no choice except 49 Hboot, so will try to make s-off, as an alternative - there is a possibility to flash the full memory dump from the working phone (just have to find it), and plus I've received on Saturday the ORT jtag Tool in addition to Riff - so give me some time. Riff Box can repair CID - if you remember the default one - I can reflash it. Other then that I should flash the whole mem dump - I ment first I have to find the same but working phone to copy its boot memory or to find on internet - sometimes it is possible to download it. Without the proper CID we are finished - no way to replace the Hboot or flash a recovery
Click to expand...
Click to collapse
.
He says its a .bin file and that its about 500MB in size. Im wondering if its a file we get when we do a nandroid backup?

[Q] Rezound - bricked or worse - looking for guidance (noob)

So while trying to update to ICS my fingers were working faster than my brain (yes, it happens) and I selected a menu option while using Clockwork and, while I'm not sure, I think the option said something like, "format .. OS...something..." before I could fully read it (and stop my finger from pressing the power button), I pressed the power button.
The phone rebooted, got to the white HTC screen and stopped - stuck on the white HTC screen. I pulled the battery.
I Held down power and up-volume and got to the bootloader menu, selected recovery and Clockwork came up.
Couldn't "Recover" because it couldn't mount the SD card.
Couldn't mount the external SD card either.
Ok - tried a factory reset - Rebooted - up came the white HTC screen where it stays until I pull the battery.
I'm new at this (probably didn't need to say that, but...).
How Do I get past this point?
Is this phone agonner?
How do I load (anything) to the phone at this point?
Thanks in advance! I appreciate it.

MilesTHD said:
So while trying to update to ICS my fingers were working faster than my brain (yes, it happens) and I selected a menu option while using Clockwork and, while I'm not sure, I think the option said something like, "format .. OS...something..." before I could fully read it (and stop my finger from pressing the power button), I pressed the power button.
The phone rebooted, got to the white HTC screen and stopped - stuck on the white HTC screen. I pulled the batter.
I Held down power and up-volume and got to the bootloader menu, selected recovery and Clockwork came up.
Couldn't "Recover" because it couldn't mound the SD card.
Couldn't mound the external SD card either.
Ok - tried a factory reset - Rebooted - up came the white HTC screen where it stays until I pull the battery.
I'm new at this (probably didn't need to say that, but...).
How Do I get past this point?
Is this phone agonner?
How do I load (anything) to the phone at this point?
Thanks in advance! I appreciate it.
Click to expand...
Click to collapse
Try using adb commands from your computer to push a recovery to your phone and go from there
Sent from my ADR6425LVW using xda app-developers app

If it powers on, you're not bricked.
Are s-on or s-off?
Make sure you have a card reader for the following.
The best thing for you to do would probably to flash an RUU.
First, download the latest RUU.
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
If you are s-on with unlocked boot loader, relock it:
Make sure there is no PH98IMG.ZIP on your sdcard. Delete if there is one.
Power off phone completely with battery pull.
Plug in phone to computer with USB.
Go to the bootloader menu with vol down + power.
Select fastboot.
On your computer, run the following fastboot command (do whatever you needed to do to use fastboot):
fastboot oem lock
After that is done, time to install the RUU.
Find the RUU you downloaded and put it on your sdcard, then rename to PH98IMG.ZIP
Put sdcard back, then power on to bootloader.
It should now scan for the PH98IMG and then ask you to install it.
Follow all the instructions to install it.
After you finish this, you will be back to the stock ROM with a locked boot loader.
If either s-off or s-on locked bootloader
Sent from my HTC Rezound using Tapatalk 2

Rezound still major messed up
THANK YOU for your help, I really appreciate your response. I followed your instructions and once the PH98IMG.zip file was on the SD card I loaded bootloader and it did scan for the file, but said "no file or wrong file!" Well, the file is there so I know its not "no" file. I've tried a couple of different PH98IMG files that I found on XDA but I guess the specific file wasn't the problem.
After it gives the error message it simple goes back to the bootloader and waits.
Unlocking the bootloader and then following your instructions did result in the file being seen and, what appeared to be, the installation process beginning - however when the phone reboots for the first time it just goes quiet and never comes back up. I waited for at least 20 minutes before I decided it wasn't just a long boot process.
I"m pretty sure there is NOTHING on this phone. I've verified there's nothing on the SD card besides the PH98IMG.zip file. Assuming I've completely wiped out the OS (and it is not on the phone) is the method you've outlined the right starting point?
Thanks again, and Merry Christmas
Miles
wlmeng11 said:
If it powers on, you're not bricked.
Are s-on or s-off?
Make sure you have a card reader for the following.
The best thing for you to do would probably to flash an RUU.
First, download the latest RUU.
If you are s-on with unlocked boot loader, relock it:
Make sure there is no PH98IMG.ZIP on your sdcard. Delete if there is one.
Power off phone completely with battery pull.
Plug in phone to computer with USB.
Go to the bootloader menu with vol down + power.
Select fastboot.
On your computer, run the following fastboot command (do whatever you needed to do to use fastboot):
fastboot oem lock
After that is done, time to install the RUU.
Find the RUU you downloaded and put it on your sdcard, then rename to PH98IMG.ZIP
Put sdcard back, then power on to bootloader.
It should now scan for the PH98IMG and then ask you to install it.
Follow all the instructions to install it.
After you finish this, you will be back to the stock ROM with a locked boot loader.
If either s-off or s-on locked bootloader
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse

MilesTHD said:
THANK YOU for your help, I really appreciate your response. I followed your instructions and once the PH98IMG.zip file was on the SD card I loaded bootloader and it did scan for the file, but said "no file or wrong file!" Well, the file is there so I know its not "no" file. I've tried a couple of different PH98IMG files that I found on XDA but I guess the specific file wasn't the problem.
After it gives the error message it simple goes back to the bootloader and waits.
Unlocking the bootloader and then following your instructions did result in the file being seen and, what appeared to be, the installation process beginning - however when the phone reboots for the first time it just goes quiet and never comes back up. I waited for at least 20 minutes before I decided it wasn't just a long boot process.
I"m pretty sure there is NOTHING on this phone. I've verified there's nothing on the SD card besides the PH98IMG.zip file. Assuming I've completely wiped out the OS (and it is not on the phone) is the method you've outlined the right starting point?
Thanks again, and Merry Christmas
Miles
Click to expand...
Click to collapse
If you are S-on and have an unlocked bootloader, you will need to relock it before attempting to flash an ruu. Once re-locked, ensure that the PH98IMG is not a zip file within a zip file which is how they are usually uploaded. Attempt to unzip the files until it will not unzip anymore. That file that won't unzip needs to be the one you rename as PH98IMG and placed on the root of your SD card. Reboot to bootloader and allow it to scan. It will ask you if you wish to proceed and you will allow it. After some time it will reboot back to bootloader to flash radios and the rest of firmware. After that process and a 2nd reboot you should he back to stock, locked, and unrooted.
Sent from my Rezound using xda premium

Also, it could be possible that your phone can't recognize the sd card so it needs to be formatted.
Sent from my HTC Rezound using Tapatalk 2

zip file contents?
Maybe I should ask what the contents of the .zip file should be? I did check the zip to make sure it wasn't a double-zip. There were two versions of the PH98IMG file i tried. One had the file (imagemate-3.60.exe) the other had the file(s) (boot.img and android-info.txt).
I did "relock" the bootloader prior to trying and it would not recognize the file. When it was unlocked it would see it, start the install process, then go quiet. So that at least tells us that the file is there and likely workable.
I can't seem to get past the "No image or wrong image" message. I've tried on 3 different cards (the original and two fresh cards) and I've checked to ensure the zip is not a zip within a zip.
IAmTheOneTheyCallNeo said:
If you are S-on and have an unlocked bootloader, you will need to relock it before attempting to flash an ruu. Once re-locked, ensure that the PH98IMG is not a zip file within a zip file which is how they are usually uploaded. Attempt to unzip the files until it will not unzip anymore. That file that won't unzip needs to be the one you rename as PH98IMG and placed on the root of your SD card. Reboot to bootloader and allow it to scan. It will ask you if you wish to proceed and you will allow it. After some time it will reboot back to bootloader to flash radios and the rest of firmware. After that process and a 2nd reboot you should he back to stock, locked, and unrooted.
Sent from my Rezound using xda premium
Click to expand...
Click to collapse

MilesTHD said:
Maybe I should ask what the contents of the .zip file should be? I did check the zip to make sure it wasn't a double-zip. There were two versions of the PH98IMG file i tried. One had the file (imagemate-3.60.exe) the other had the file(s) (boot.img and android-info.txt).
I did "relock" the bootloader prior to trying and it would not recognize the file. When it was unlocked it would see it, start the install process, then go quiet. So that at least tells us that the file is there and likely workable.
I can't seem to get past the "No image or wrong image" message. I've tried on 3 different cards (the original and two fresh cards) and I've checked to ensure the zip is not a zip within a zip.
Click to expand...
Click to collapse
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots.
So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly. In your examples above one is a kernel (boot.img) and I have no idea what imagemate-3.60.exe is. It sounds like you have not had the correct file.
Here is the global RUU you should run to get you back to stock with all the latest radios and firmware:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
You need to be locked to run it so if you are S-ON, which it sounds like you are (don't remember if you mentioned that before), you need to use fastboot from your pc to do that, just like you did when you unlocked it with this command:
fastboot oem lock
***If you are S-OFF you should be locked again from that process already. But if you are S-OFF then confirm with someone to be sure it's safe to run the RUU, there's something about not relocking if you are on a certain hboot or you can brick it or something...***
Then put the RUU on your SD card and reboot the phone. Let it run through the RUU a few times because apparently it needs to do it a few times to get all the system files. Afterwards, if you want to root again and flash a custom ROM you will need to unlock again and flash a custom recovery and reroot.

It Works!
Not that I'm going to give you all the credit, because everyone kinda chipped in - however you DID provide the ONLY correct link to exactly what I needed! LORDY there are a lot of bad links being passed around. THANK YOU Ms. Feralicious, I totally appreciate your help.
... Everyone else as well - very generous with your knowledge and time and I will always love you.
Merry Christmas! Have a safe new year as well!
Miles
feralicious said:
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots.
So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly. In your examples above one is a kernel (boot.img) and I have no idea what imagemate-3.60.exe is. It sounds like you have not had the correct file.
Here is the global RUU you should run to get you back to stock with all the latest radios and firmware:
You need to be locked to run it so if you are S-ON, which it sounds like you are (don't remember if you mentioned that before), you need to use fastboot from your pc to do that, just like you did when you unlocked it with this command:
fastboot oem lock
***If you are S-OFF you should be locked again from that process already. But if you are S-OFF then confirm with someone to be sure it's safe to run the RUU, there's something about not relocking if you are on a certain hboot or you can brick it or something...***
Then put the RUU on your SD card and reboot the phone. Let it run through the RUU a few times because apparently it needs to do it a few times to get all the system files. Afterwards, if you want to root again and flash a custom ROM you will need to unlock again and flash a custom recovery and reroot.
Click to expand...
Click to collapse

Followed these directions & update fails...Please help.
Have PH98IMG.zip on sd card.
Gets this far...
*** LOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
HBOOT
Parsing...[SD ZIP]
[1]...
...[18]
...start update?
<VOL UP>
Next to "[1] BOOTLOADER" "- Fail-PU"
And below [18]..., "Partition update fail!"
"Update Fail!"
"Press <POWER> to reboot."
It's an HTC Rezound I'm trying to get back to stock, Verizon.
Any ideas?

It's locked which means it's never been unlocked and it's s-on. A simple factory reset within the rom itself will suffice
Sent from my Rezound using xda premium

rut-row...running rezound reset from rom repeatedly ravaging me :-O
IAmTheOneTheyCallNeo said:
It's locked which means it's never been unlocked and it's s-on. A simple factory reset within the rom itself will suffice
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
When running rom, ...
"RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9
K_release_270509_signed.exe" ...
ends in usb error 170...
Anyone having any pointers for me will be worshiped indefinately!
Thank-You and I'm-not-worthy, in advance,
Tom

screen shots
TommyJames said:
When running rom, ...
"RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9
K_release_270509_signed.exe" ...
ends in usb error 170...
Anyone having any pointers for me will be worshiped indefinately!
Thank-You and I'm-not-worthy, in advance,
Tom
Click to expand...
Click to collapse
attached error window pic.

TommyJames said:
attached error window pic.
Click to expand...
Click to collapse
Try putting the PH98IMG.ZIP on your sdcard manually.
Sent from my HTC Rezound using Tapatalk 2

TommyJames said:
When running rom, ...
"RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9
K_release_270509_signed.exe" ...
ends in usb error 170...
Anyone having any pointers for me will be worshiped indefinately!
Thank-You and I'm-not-worthy, in advance,
Tom
Click to expand...
Click to collapse
Not sure what you're trying to do there, run an RUU?
Did you try a factory reset from the settings of the phone as Neo suggested?
Settings > Storage > Factory data reset
But back up anything you want to save such as pics, settings, etc... it will wipe everything.

same thing happens...
TommyJames said:
Have PH98IMG.zip on sd card.
Gets this far...
*** LOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
HBOOT
Parsing...[SD ZIP]
[1]...
...[18]
...start update?
<VOL UP>
Next to "[1] BOOTLOADER" "- Fail-PU"
And below [18]..., "Partition update fail!"
"Update Fail!"
"Press <POWER> to reboot."
It's an HTC Rezound I'm trying to get back to stock, Verizon.
Any ideas?
Click to expand...
Click to collapse
same thing happens...

TommyJames said:
same thing happens...
Click to expand...
Click to collapse
You still needing help?
Where did you get the PH...img file you are using? Are you sure it's an RUU?
Did you ever try resetting to factory settings within the phone? You don't need to RUU for that, check a few posts up on where to find the setting.

Solved CDMA Sprint Hboot 1.58 Total noob guide for S-off[ROOT]

Hey, I am trying to root my HTC evo 3d phone with hboot 1.58. I followed all 12 steps on htcdev.com, except on the final step I punch in: fastboot flash unlocktoken Unlock_code.bin and enter, then noting happens. The phone is supposed to reboot with the unlock option..but nothing happens
Also, the phone is Sprint CDMA if that makes any difference, so no sim card
....................................................................................................................................................................
THREAD SUMMARY
K finally got th phone rooted so here is what you have to do. The following applied to my ***locked*** S-ON Sprint HTC Evo3d with hboot 1.58 but should work with any other version higher than hboot 1.40.
The purpose is to get S-OFF(ROOT the phone) and also continue to use your factory HbOOT 1.58 and main version in the end.
1. Brick the phone carefully following steps outlined in unknownforce's [TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset). Scroll down to the "Downgrade/Unbrick" section and begin the bricking process with the PG86IMG.zip he mentions in "things you'll need".(place the zip on SD card in the main directory and name it PG86IMG)
2. Once phone is bricked(indicated by SOLID and very dimly lit charge light with the AC charger connected. Also the phone will not turn on or boot), download latest version of URT 3.1(first link in [TOOL] thread), continue to the second step 2 which involves booting up with Linux live boot CD on your PC, OR you can use URTLiveCD 1.0 and you will not need Linux
I did it the hard way an used latest version of URT with Ubuntu v12.04 LiveCD. I would recommend URTLiveCD 1.0 as you will boot straight to the tool and will not need the Ubuntu terminal.
3. After successfully completing downgrade with URT 3.1 downgrade, boot up to your new HBOOT 1.40 bootloader screen and enter fastboot USB mode. CHECK THAT THE MAIN VERSION HAS BEEN LOWERED ALONG WITH THE HBOOT.
Log back into windows
3.(A) If you haven't done this yet, get a fastboot PC command directory to retrieve all phone identification info from the bootloader. I used ROOTEVO3DNEW to check my phone's identity info at this point(though there are many programs that do the same thing). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder.
Now open the command prompt with the phone connected to PC in fastboot USB. Type cd \rootevo3dnew and enter. Now type the following: "fastboot getvar all" (without quotations) and enter. A list should appear. Check that you have: (bootloader) version-main: 0.01.651.1. If this number is still 2.95.XXX.XXX or something close to it, then YOU MUST BRICK THE PHONE AGAIN. See posts starting at #35 of this thread for a more detailed guide through the second brick. It may be very tricky but very much the same process!!!!!
4. After successfully lowering HBoot to 1.40 and the main-version to 0.01.651.1 you can run the 1.13 RUU.exe found HERE: http://d-h.st/h1p . Connect the phone to fastboot USB and RUN the .exe....after the 1.13 .exe successfully runs, your main version should now be 1.13.651.7...again, checking using your rootevo3dnew tool from 3.(A) above....
5. REVOLUTIONARY S-OFF. Very simple, download for windows(or Linux) and fill in your info and retrieve you BETA key. Run REVOLUTIONARY application (which will run in the command prompt) and after successfully completely revolutionary S-off, YOU ARE ROOTED...continue to step 6
6. RESTORE your main version to 2.95(from 1.13) by running the 2.89 zip (HERE . Place this .zip in your main directory(RENAME IT PG86IMG) on the SD card and let it unzip and install it from the bootloader.
After that, you are pretty much finished!! boot up to android(main version 2.89) and let system updates detect and bring you back to 2.95.xxx.xxx..
....
Download and Install a custom recovery. Rename that .zip PG86IMG and install from bootloader as you did with the 2.89 zip. Now you have a custom recovery where you can backup and restore, install ROMS or other software without having to rename it PG86IMG every time, wipe partitions and lots of other stuff...
Now, download this and place it on your SD main directory. Then, using your new recovery(by selecting "recovery" in bootloader menu), select "install from sdcard" and "choose zip from sdcard", select the SuperSU zip and let it install. Reboot, get to homepage, and install SuperSU from the play store. You now hae an administrative super APP that will let you choose which apps are given root access.
Custom ROMS can be installed the same way from the custom recovery. I am currently using Negalite BluRom and loving it
...
THE 6 STEPS OUTLINED HERE PRETTY MUCH COVER EVERYTHING FROM THIS THREAD
HUGE THANKS TO USERS MPGRIMM2 AND BRIAN706 FOR NEARLY 3 DAYS OF HARD WORK !!

Did you get your motherboard replaced at some point of time?
Can't think of a good sig

donkeykong1 said:
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
Click to expand...
Click to collapse
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?

otto325 said:
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
Click to expand...
Click to collapse
On the phone?
Can't think of a good sig

donkeykong1 said:
On the phone?
Can't think of a good sig
Click to expand...
Click to collapse
Oh ok, what the hell..No, I just got the phone on ebay for $30, currently locked and I am trying to root it. Some Brittney girl owned according to phone identity info left on the phone

Do I need to downgrade the hboot from 1.58 to 1.4? Sorry I'm really new to smartphones, any help is really appreciated

Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.

Brian706 said:
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Click to expand...
Click to collapse
THANKS
main version 2.95.651.5. If I factory reset the phone and discard updates, will the main version reset to 2.89 making the RUU possible?
EDIT: factory reset and no updates did not bring main version down to 2.89
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
Also check most recent post (#508) in the guide thread.
http://forum.xda-developers.com/showthread.php?t=1889438&page=51

Factory reset won't affect your main version

As DK mentioned, a factory reset only resets your current build. It would only take you back to the point of the last OTA update.
Unfortunately, you can't lower the mainversion without the bootloader unlocked, so it's a catch 22 there.
As a long shot, you might look into the new towelroot, thought I really don't think it will work for this phone because HTC locks down the /system partition. It would at least be worth looking in to.
As far as the hboot downgrade method (I assume you mean THIS) it was intended to downgrade from 1.50 Gingerbread to 1.40 Gingerbread. I have no idea if it will work to downgrade from 1.58 ICS?? You might want to ask around a little about that.
Okay... I just saw your posts in the other thread, have you actually received the unlock token from HTC?
IE, you received a file via email named Unlock_Code.bin that you placed in your fastboot directory and then typed the command: fastboot flash unlocktoken Unlock_code.bin ??
Also, when you say nothing happens after running the command, something must happen whether it's the intended results or not. Can you tell us what the command prompt returns after running the command? Maybe just copy/paste it here.
There will either be an error or a confirmation after running the command.

Comes up as successful on the command prompt. But the phone does not reboot or direct to the unlock screen. I just remains on the fastboot USB screen and does nothing.
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.163s

Thanks for that... That's a bummer. Looks to me like you have the motherboard swap issue. It really sucks that you can't RUU.
It looks like someone answered the question in the other thread though about the hboot downgrade method.

So I got the HBOOT downgrade(0.8.2) boot for a disk but it says the phone needs to be bricked before the downgrade..
That's where I'm at now basically, I'm going to do a little more reading on bricking...
Also would be good to have confirmed that this downgrade will work starting with hboot 1.58, so I don't mess anything up
mpgrimm2 may have found found his way over here from from the [Guide] thread
Also I hope I am downloading the correct RUU's. I had to fish them from various searches because the link supplied in Unknownforce's thread is invalid:
2.17 RUU:
http://d-h.st/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
1.13 RUU:
http://d-h.st/Xrp

mpgrimm2 said:
Well. Post that in Unknownforce's Ultimate Recovery Tool thread so you are not "off topic" here.
I haven't used the Evo3d in a while but you should probably look over my ...
Post 781 in Unknownforce's thread and the follow up posts right after.
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)
Click to expand...
Click to collapse
Fyi, I think Unknownforce indicated in one of his first 3 posts that u can brick with the last 2.95 PG86IMG.zip file he linked and then downgrade to 1.13 for s-off. Have to go check...
Keep in mind that you may want to considering posting any issues with the URT/Downgrade tool in Unknownforce's thread if you want any chance of assistance from him.
Bad link in his op but this post has it...
Unknownforce said:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.
I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.
Here's the PG86IMG file -> http://d-h.st/3p8
Click to expand...
Click to collapse
And just as a reference for you later I will quote myself from Ramjet73's 2.95 ota update thread
mpgrimm2 said:
ramjet73 and others. I see we still don't have any source for the 2.95.651.6 RUU's. Since I just went ahead and reset my 2 Evo3d's back to stock/S-off as a backup here are the files I had to step through if you want to add or host them directly:
- PG86IMG 2.89.651.2.zip - 449.18 MB
Full RUU.zip for use in bootloader (rename to PG86IMG.zip & place on /sdcard)
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.5-2.89.651.2_release_307948lagg6bmccb9c63ip.zip - 51.11 MB
2.89.651.2 update to 2.95.651.5 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
This is the last official update that just downloaded to my phone after the other Ruu's/updates that were posted previously
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z.zip - 10.59 MB
2.95.651.5 update to 2.95.651.6 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
Wish someone with HTC/Sprint access would post up the latest full RUU. It was a bit of a pain stepping through the updates, but definitely easier being s-Off. Seems that if someone is S-On with the 2.95.651.6 update and can't get past step 13 of the HTC Unlock or needs to RUU back, their only option is Unknownforce's Hboot Downgrade Ultimate Toolkit and "Brick it Twice" to get back to an earlier version for Revolutionary S-Off and then go through the updates from 2.89 on up.
Hope this helps others.
EDIT:
I may be too tired at the moment to figure this out, but for some darn reason both the official OTA Updates would not flash from the bootloader on a stock 2.89.651.2 phone with S-Off (both phones actually). Didn't matter if it was renamed PG86IMG.zip or left as officially downloaded to sdcard/download and booting into the stock recovery. The MD5 of my 651.5 update file matches Ramjet73's as well. But If I connect to wifi, do a system update, let it download (how I got the files) and reboot automatically, it works fine and updates without issue.
Click to expand...
Click to collapse

Forgive me for being such a noob with this stuff.
I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.
So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?
The stock
(OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z)
Click to expand...
Click to collapse
is there, so do I remove that one and replace it?
I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?
*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader
I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.
Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that

What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?

This one:
http://forum.xda-developers.com/showthread.php?t=1563342

Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.
see here
Sent from my "Up All Night Sleep All Day" Nexus 5!

THANKS
Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Just a matter of getting a new data sync cable now and I can do this...
Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..
Will report back in a couple days, hopefully with a newly rooted phone
--------
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?

otto325 said:
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
Click to expand...
Click to collapse
Yep. Previously...
mpgrimm2 said:
....
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself) <<<--- HERE
Click to expand...
Click to collapse
Sent from my "Up All Night Sleep All Day" Nexus 5!

Better Mobile App

welcome