[Q] EVO 3D Unbricking Help - HTC EVO 3D

I've got a Sprint EVO 3D I am trying to unbrick for a friend. What happens is that the phone powers on and the only thing that happens is that I get a black screen with the HTC logo and four exclamation points on the four corners of the screen. I can't get into hboot. Holding the power button and the volume down button don't do anything unless the phone is completely off, in which case, I get the previously mentioned HTC screen.
I can use fastboot commands though. The command "fastboot reboot-recovery" restarts the phone but I get exactly the same result, the black HTC screen with four exclamation points.
"fastboot getvar mainver" returns "2.17.651.5"
"fastboot getvar cid" returns "SPCS_001"
Based on that information, I consulted the Google and found "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed." That ran for a while until the RUU program on my computer then said it couldn't complete the update and returned error code 155. Googling that error produced several threads that spoke of making sure the bootloader was locked prior to running the RUU. That step was mentioned in the forum that led me to the RUU in the first place and I verified that the bootloader was locked prior to running the RUU by running "fastboot oem lock." That command returned "(bootloader) Device was already locked!" To be sure, I ran the whole process again. Verified the bootloader was locked, and received error 155 again.
When you disconnect the USB after running the RUU, the screen changes to the familiar white hboot screen and says the following
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Hboot Version is older
Update Fail!
After more searching and more Googling, I found an RUU named "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed" which is supposed to work with hboot 1.58. That one ran for much longer and a green status bar showed up on the EVO's screen. The RUU program errors out with error 132: Signature Error but the green bar on the EVO's screen keeps moving until it gets to just before the "C" in the HTC logo and stops there. I let the phone sit for nearly an hour with no change. At that point, I disconnected the USB to see if I could get the HBoot screen again and this is what it showed:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Parsing ...[download ZIP]
[1] BOOTLOADER - Bypassed
[2] BOOT - OK
[3] SBL1 - OK
[4] USERDATA - OK
[5] WIMAX - OK
[6] RECOVERY - OK
[7] SBL2 - OK
[8] SPLASH1 - OK
[9] SYSTEM - Fail-UZ
[10] SBL3 - Fail-PU
[11] TRUST_ZONE - OK
[12] ADSP - OK
[13] RPM - OK
[14] PG2FS_SPCUSTOM - Fail-UZ
[15] RADIO_V2 - Fail-UZ
Image uzipping fail!
Update Fail!
I have also tried placing a PG86IMG.zip file from another thread onto an SDCard. This doesn't do anything that I can see. At this point, I've spent two days trying to fix this phone and I am out of ideas. The rest of the fixes for a bricked EVO all start with "enter hboot" which I can't do with any method I am aware of or can find.
Any suggestions or am I just out of luck?

---

firesyde424 said:
I've got a Sprint EVO 3D I am trying to unbrick for a friend. What happens is that the phone powers on and the only thing that happens is that I get a black screen with the HTC logo and four exclamation points on the four corners of the screen. I can't get into hboot. Holding the power button and the volume down button don't do anything unless the phone is completely off, in which case, I get the previously mentioned HTC screen.
I can use fastboot commands though. The command "fastboot reboot-recovery" restarts the phone but I get exactly the same result, the black HTC screen with four exclamation points.
"fastboot getvar mainver" returns "2.17.651.5"
"fastboot getvar cid" returns "SPCS_001"
Based on that information, I consulted the Google and found "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed." That ran for a while until the RUU program on my computer then said it couldn't complete the update and returned error code 155. Googling that error produced several threads that spoke of making sure the bootloader was locked prior to running the RUU. That step was mentioned in the forum that led me to the RUU in the first place and I verified that the bootloader was locked prior to running the RUU by running "fastboot oem lock." That command returned "(bootloader) Device was already locked!" To be sure, I ran the whole process again. Verified the bootloader was locked, and received error 155 again.
When you disconnect the USB after running the RUU, the screen changes to the familiar white hboot screen and says the following
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Hboot Version is older
Update Fail!
After more searching and more Googling, I found an RUU named "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed" which is supposed to work with hboot 1.58. That one ran for much longer and a green status bar showed up on the EVO's screen. The RUU program errors out with error 132: Signature Error but the green bar on the EVO's screen keeps moving until it gets to just before the "C" in the HTC logo and stops there. I let the phone sit for nearly an hour with no change. At that point, I disconnected the USB to see if I could get the HBoot screen again and this is what it showed:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Parsing ...[download ZIP]
[1] BOOTLOADER - Bypassed
[2] BOOT - OK
[3] SBL1 - OK
[4] USERDATA - OK
[5] WIMAX - OK
[6] RECOVERY - OK
[7] SBL2 - OK
[8] SPLASH1 - OK
[9] SYSTEM - Fail-UZ
[10] SBL3 - Fail-PU
[11] TRUST_ZONE - OK
[12] ADSP - OK
[13] RPM - OK
[14] PG2FS_SPCUSTOM - Fail-UZ
[15] RADIO_V2 - Fail-UZ
Image uzipping fail!
Update Fail!
I have also tried placing a PG86IMG.zip file from another thread onto an SDCard. This doesn't do anything that I can see. At this point, I've spent two days trying to fix this phone and I am out of ideas. The rest of the fixes for a bricked EVO all start with "enter hboot" which I can't do with any method I am aware of or can find.
Any suggestions or am I just out of luck?
Click to expand...
Click to collapse
in order to write a new bootloader youll need to be unlocked andsOFF...your phone says youre relocked
plus the version youre trying to install is for hboot 1.5 not 1.58...
http://goo.im/stock/shooter/ruu
go there and try to runn that RUU...its for the ICS version of android with hboot 1.58 which is what you have...and until you unlock your bootloader again and then root then gain s-off THEN you can install a different bootloader versio like 1.5 which is what is suppoed to run with version 2.17