[UNBRICK] HTC Unbricking Project

Search This thread

dexter93

Inactive Recognized Developer
Jul 1, 2010
11,612
2,342
We are proud to announce that the Evo 3D is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.

Unbrick-proj-EVO.jpg


Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it

The "core" of the unbricking project dev team:
MOVZX
RussianBear
Fuses
Dexter93

Testing stuff and irc support:
globatron
Deceptivechaos
dburgd84
Snake_skw

Other stuff:
dmcb123
xIndirect
Hawke84

Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.
 
Last edited:

dexter93

Inactive Recognized Developer
Jul 1, 2010
11,612
2,342
Prerequisites
  • a linux box/live cd with automount disabled and without unity
  • the appropriate package for the device
  • the latest RUU for your device
  • a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
  • a usb cable
  • some basic linux experience
  • patience

DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.

Instructions

NEW: Detailed video on the process. Its displaying the process on a Sensation, but its pretty much the same thing. Watch out for partition differences. Thanks to kgs1992 :)

  1. Boot the linux box and download the appropriate package for the device.
    WARNING: IT IS DEVICE SPECIFIC. DO NOT USE THE CDMA VERSION ON A GSM EVO AND VICE VERSA. SAME GOES FOR THE INSTRUCTIONS
  2. Extract the package in the home directory
  3. Open up a terminal
  4. Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery
  5. Detect the device using the script provided. Type this in the terminal
    Code:
    ./brickdetect.sh
    You should get something like sdX. We are interested on that "X"
  6. Unplug the usb cable from the device
  7. Backup the hboot currently in the phone by using this command. Plug the device in ONLY when asked to
    Code:
    sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX13
    Replace the "X" with the letter the script gave you
  8. Follow the on-screen instructions from emmc_recover
  9. Hexdump the b_hboot to check the hboot version
    Code:
    hexdump -C b_hboot.img |less
    The output should be like this:
    Code:
    00000000  05 00 00 00 03 00 00 00  00 00 00 00 00 00 10 40  |[email protected]|
    00000010  d8 fc 0f 00 d8 fb 0f 00  d8 fb 1f 40 00 01 00 00  |[email protected]|
    00000020  d8 fc 1f 40 00 00 00 00  1a 00 00 ea 31 2e 34 30  |[email protected]|
    00000030  2e 30 30 30 30 00 00 00  38 32 36 30 20 53 50 4c  |.1100...8260 SPL|
    00000040  00 00 00 00 00 f0 20 e3  53 48 49 50 00 00 00 00  |...... .SHIP....|
    00000050  00 f0 20 e3 00 f0 20 e3  48 42 4f 4f 54 2d 38 32  |.. ... .HBOOT-82|
    00000060  36 30 00 00 00 f0 20 e3  62 62 35 35 33 39 32 62  |60.... .bb55392b|
    This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.40
  10. If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again
  11. Unplug the device
  12. Check again it is the right version, because if you do a mistake here, you won't be able to go back
    You can only flash the same version as the one in the device.


    !!!!!DO NOT ATTEMPT TO FLASH ANOTHER VERSION OR DOWNGRADE!!!IT HAS BEEN PROVEN FATAL!!!!
  13. Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.30, 1.40, 1.50) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
    Code:
    sudo ./emmc_recover --flash shooterV.VV.nb0 --device /dev/sdX13 --backupafter hboot_f.nb0
  14. Follow the on-screen instructions from emmc_recover. A successful flash should have this output:
    Code:
    511+1 records in
    511+1 records out
    1047808 bytes(1.0 MB) copied
  15. Unplug the device, put microSD card and battery in and power on
  16. Congratulations, the device is unbricked.
  17. FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.

Notes on the procedure:

  • If the device doesn't power on, get a copy of the hboot_f.nb0 and b_hboot.img (should be located in the home directory) and contact us
  • The connection between the device and the pc will be unstable, and will time out. You have to be quick when doing the above, specially while flashing. If the connection times out don't panic, just unplug and replug the device
  • Unity and automount are known to cause issues in ubuntu 11.04 and 11.10. We recommend getting rid of both, or use a 12.04, or 10.04/.10 liveCD
  • USB3 ports do not work properly. Please plug the device in a USB2 port
  • How to disable automount on ubuntu
    Code:
    gsettings set org.gnome.desktop.media-handling automount false


Downloads

For EVO 3D CDMA( Shooter):
32bit version MD5: 5f49aff0347b7b839f666f590bfb3f76
64bit version MD5: e9087359552b622cf07cb5d67adb991b

Don't have a linux distro installed on your pc? We highly recommend this livecd
 
Last edited:

patrao_n

Senior Member
Dec 17, 2010
2,278
971
san diego
If you follow their instructions you can make your 3d unbrickable. Meaning you can flash whatever including a gsm rom in your cdma and be able to recover from it. Definitely excited dexter thanks :)

Sent from my SPH-D710 using Tapatalk 2
 

powduh09

Senior Member
Feb 17, 2011
1,270
704
Dallas, NC
This sounds awesome... Will make it safer to follow the downgrade guide for hboot 1.5 users, meaning if they true brick, they can recover...

sent from my downgraded hboot 1.50 3vo running ZR3D injected with anthrax... s-off HTC, thanks to the real developers, I now have control of my device again ;)
 

myn

Retired Senior Recognized Developer
Nov 15, 2007
2,679
3,985
I <3 anticipation threads..
 

laie1472

Senior Member
Feb 18, 2010
4,549
820
Astronomical dev work. Hats off truly to all involved. I'll be picking up another 3d as well and this just gives me more incentive.

#Root-Hack_Mod*Always\
 

leerage

Senior Member
Nov 9, 2009
412
134
Amazing work with all parties involved. Thanks again for all the hard work and dedication.

Sent from my PG86100 using xda premium
 

Astrikz

Senior Member
Mar 27, 2012
1,282
566
Funny how they have disclaimers. The phones already bircked is it possiable to have an ultra bricked device?

Sent from my PG86100 using Tapatalk
 
We are proud to announce that the Evo 3D is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.

Unbrick-proj-EVO.jpg


Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it

The "core" of the unbricking project dev team:
MOVZX
RussianBear
Fuses
Dexter93

Testing stuff and irc support:
globatron
Deceptivechaos
dburgd84
Snake_skw

Other stuff:
dmcb123
xIndirect
Hawke84

Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.

Nice to Finally see the goings ons of unbricking, however any chance of this at some point becoming an unbrickable mod
 

dfskevinohyeah

Senior Member
Jul 6, 2010
1,400
751
sweeeeeeeet thanks guys will bookmark this. Though I am a very paranoid tester so I doubt I will ever brick my device :)
 

dexter93

Inactive Recognized Developer
Jul 1, 2010
11,612
2,342
ok, I've had some pms about this. Maybe I didnt stress it enough in my sig, but I cannot give support by pm. I simply can't respond to all of them. Please post here so that if someone faces the same issue , will have the answer

Thanks guys :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 33
    We are proud to announce that the Evo 3D is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.

    Unbrick-proj-EVO.jpg


    Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it

    The "core" of the unbricking project dev team:
    MOVZX
    RussianBear
    Fuses
    Dexter93

    Testing stuff and irc support:
    globatron
    Deceptivechaos
    dburgd84
    Snake_skw

    Other stuff:
    dmcb123
    xIndirect
    Hawke84

    Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.
    15
    Prerequisites
    • a linux box/live cd with automount disabled and without unity
    • the appropriate package for the device
    • the latest RUU for your device
    • a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
    • a usb cable
    • some basic linux experience
    • patience

    DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.

    Instructions

    NEW: Detailed video on the process. Its displaying the process on a Sensation, but its pretty much the same thing. Watch out for partition differences. Thanks to kgs1992 :)

    1. Boot the linux box and download the appropriate package for the device.
      WARNING: IT IS DEVICE SPECIFIC. DO NOT USE THE CDMA VERSION ON A GSM EVO AND VICE VERSA. SAME GOES FOR THE INSTRUCTIONS
    2. Extract the package in the home directory
    3. Open up a terminal
    4. Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery
    5. Detect the device using the script provided. Type this in the terminal
      Code:
      ./brickdetect.sh
      You should get something like sdX. We are interested on that "X"
    6. Unplug the usb cable from the device
    7. Backup the hboot currently in the phone by using this command. Plug the device in ONLY when asked to
      Code:
      sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX13
      Replace the "X" with the letter the script gave you
    8. Follow the on-screen instructions from emmc_recover
    9. Hexdump the b_hboot to check the hboot version
      Code:
      hexdump -C b_hboot.img |less
      The output should be like this:
      Code:
      00000000  05 00 00 00 03 00 00 00  00 00 00 00 00 00 10 40  |[email protected]|
      00000010  d8 fc 0f 00 d8 fb 0f 00  d8 fb 1f 40 00 01 00 00  |[email protected]|
      00000020  d8 fc 1f 40 00 00 00 00  1a 00 00 ea 31 2e 34 30  |[email protected]|
      00000030  2e 30 30 30 30 00 00 00  38 32 36 30 20 53 50 4c  |.1100...8260 SPL|
      00000040  00 00 00 00 00 f0 20 e3  53 48 49 50 00 00 00 00  |...... .SHIP....|
      00000050  00 f0 20 e3 00 f0 20 e3  48 42 4f 4f 54 2d 38 32  |.. ... .HBOOT-82|
      00000060  36 30 00 00 00 f0 20 e3  62 62 35 35 33 39 32 62  |60.... .bb55392b|
      This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.40
    10. If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again
    11. Unplug the device
    12. Check again it is the right version, because if you do a mistake here, you won't be able to go back
      You can only flash the same version as the one in the device.


      !!!!!DO NOT ATTEMPT TO FLASH ANOTHER VERSION OR DOWNGRADE!!!IT HAS BEEN PROVEN FATAL!!!!
    13. Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.30, 1.40, 1.50) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
      Code:
      sudo ./emmc_recover --flash shooterV.VV.nb0 --device /dev/sdX13 --backupafter hboot_f.nb0
    14. Follow the on-screen instructions from emmc_recover. A successful flash should have this output:
      Code:
      511+1 records in
      511+1 records out
      1047808 bytes(1.0 MB) copied
    15. Unplug the device, put microSD card and battery in and power on
    16. Congratulations, the device is unbricked.
    17. FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.

    Notes on the procedure:

    • If the device doesn't power on, get a copy of the hboot_f.nb0 and b_hboot.img (should be located in the home directory) and contact us
    • The connection between the device and the pc will be unstable, and will time out. You have to be quick when doing the above, specially while flashing. If the connection times out don't panic, just unplug and replug the device
    • Unity and automount are known to cause issues in ubuntu 11.04 and 11.10. We recommend getting rid of both, or use a 12.04, or 10.04/.10 liveCD
    • USB3 ports do not work properly. Please plug the device in a USB2 port
    • How to disable automount on ubuntu
      Code:
      gsettings set org.gnome.desktop.media-handling automount false


    Downloads

    For EVO 3D CDMA( Shooter):
    32bit version MD5: 5f49aff0347b7b839f666f590bfb3f76
    64bit version MD5: e9087359552b622cf07cb5d67adb991b

    Don't have a linux distro installed on your pc? We highly recommend this livecd
    2
    !Luke

    Sent from my Galaxy Nexus using Tapatalk 2
    2
    Well if your device is actually bricked, try downgrading your hboot to 1.4 using closeone's live cd. It's super easy...
    1
    Can anyone direct me to the 1.58.nb0. I have searched with no luck.
    If that's the 1.58 stock bootloader you can find it here.

    ramjet73