[UNBRICK] HTC Unbricking Project

Search This thread

teshiburu2010

Senior Member
Mar 2, 2010
93
0
Rochester
Dexter - I know this is a long shot but maybe you can help, I believe I bricked my EVO 3D ago, and wasnt greatly fussed as had just got my ONE X but now I want to play 3D games again :p

If i plug my phone into my pc when booted into W7 it recognises it as QHSUSB_DLOAD

But if I boot into an ubuntu live cd, used the one you linked it says "cannot locate bricked device"

I honestly cant remember what I did to cause the brick either :(
 

thabchi

New member
Feb 14, 2010
4
0
Can.t download file

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. 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 GSM VERSION ON A CDMA 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/sdX12
    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  |...............@|
    00000010  d8 fc 0f 00 d8 fb 0f 00  d8 fb 1f 40 00 01 00 00  |...........@....|
    00000020  d8 fc 1f 40 00 00 00 00  12 00 00 ea 31 2e 34 39  |...@........1.49|
    00000030  2e 31 31 30 37 00 00 00  38 32 36 30 20 53 50 4c  |.1107...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  65 64 62 61 38 31 32 66  |60.... .edba812f|
    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.49
  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.49) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
    Code:
    sudo ./emmc_recover --flash shotrUV.VV.nb0 --device /dev/sdX12 --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 SIM, 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 GSM( ShooterU):


Hello,

I'm trying to download the package for my Evo 3D GSM, but no matter which link I click (32 or 64 bit), I get directed to a suspended webpage that says "contact support"

Do you have the files available for me to download directly?

Thanks in advance!
 

titanium_akt

Member
Dec 21, 2008
7
1
FILES

You can have the lost files for "EVO 3D GSM" here (of course till main links get repaired!)
-I'm not as reach as Dexter in No of "Thanks", so please do not forget to press Thanks! if you find it useful :)
gsme.sharif.edu/~tanara/wp-content/uploads/2014/10/Unbrick_ShooterU_32bit.tar.gz
gsme.sharif.edu/~tanara/wp-content/uploads/2014/10/Unbrick_ShooterU_64bit.tar.gz
 
Last edited:
  • Like
Reactions: chrisftlse

gaara22

Member
Jun 2, 2014
37
4
Yesterday my power switch came out and I was seeing this when I plugged my evo 3d into my computer. The phone is now dead and the red LED doesn't come on when I put the phone to charge. Is there any hope for my phone getting back to working normal?
 

edensan

New member
Aug 15, 2010
4
0
connect

If i plug my phone into my pc when booted into W7 it recognises it as QHSUSB_DLOAD no problem at all

But if I boot into an ubuntu live cd, used the one you linked it does nothing.

am i doing something wrong?

i see more ppl have troubles with this issue but no answers..

ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$
 
Last edited:

benny mulya sofyan

New member
Jan 4, 2016
1
0
If i plug my phone into my pc when booted into W7 it recognises it as QHSUSB_DLOAD no problem at all

But if I boot into an ubuntu live cd, used the one you linked it does nothing.

am i doing something wrong?

i see more ppl have troubles with this issue but no answers..

ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
ubuntu@ubuntu:~$
same problem with mine
are you s-off ?

Sent from my Oneplus One using Tapatalk
 

Avo_GH

Member
Apr 7, 2017
13
1
Hi guys,
any of you still has these files that can upload please. or f anyone has shotrU1.53.nb0 file that will also do.

would really appreciate your help
 

I_did_it_just_tmrrow

Senior Member
Feb 27, 2011
405
80
Last edited:
  • Like
Reactions: i_BANDIT

Top Liked Posts

  • There are no posts matching your filters.
  • 38
    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.
    21
    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. 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 GSM VERSION ON A CDMA 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/sdX12
      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  |...............@|
      00000010  d8 fc 0f 00 d8 fb 0f 00  d8 fb 1f 40 00 01 00 00  |...........@....|
      00000020  d8 fc 1f 40 00 00 00 00  12 00 00 ea 31 2e 34 39  |...@........1.49|
      00000030  2e 31 31 30 37 00 00 00  38 32 36 30 20 53 50 4c  |.1107...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  65 64 62 61 38 31 32 66  |60.... .edba812f|
      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.49
    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.49) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
      Code:
      sudo ./emmc_recover --flash shotrUV.VV.nb0 --device /dev/sdX12 --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 SIM, 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 GSM( ShooterU):
    32bit version MD5: 4fa6ddf99acc33f069e3192ee8417aa0
    64bit version MD5: 8acfdfc391de99e864bfd7e6ca34e9b3

    Don't have a linux distro installed on your pc? We highly recommend this livecd
    3
    downloads updated with fixed detection scripts. the output should be more clear now
    2
    evo3d gsm

    uloz.to/!ZzzYAUQ704DF/evo-3d-gsm-shooteru-1-53-zip
    2
    Release bump!
    Everything you'll need is in the first page