[UNBRICK] HTC Unbricking Project

• 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

1. Boot the linux box and download the appropriate package for the device.
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 35  |...@........1.45|
   00000030  2e 31 33 31 33 00 00 00  38 32 36 30 20 53 50 4c  |.1313...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  38 63 61 38 33 62 37 31  |60.... .8ca83b71|

   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.45
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.44, 1.45) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
    
    Code:

    sudo ./emmc_recover --flash dshotV.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.

• 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. We recommend getting rid of both
• 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

xmc wildchild22 said:

nice....i see this over on the sensation a lot.....so is it done or a wip

Click to expand...

Click to collapse

nickmatine said:

hi
no experience on linux

ubuntu@ubuntu:~$ ./brickdetect.sh
Searching for bricked device...
The bricked device is on
Use the above node to perform operations using the emmc_recover tool

it\s not find something sdX

after i paste next command sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12


Searching for bricked device...
The bricked device is on
Use the above node to perform operations using the emmc_recover tool
ubuntu@ubuntu:~$ sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
=== emmc_recover 0.2, written by Fuses =====
Messing up with device /dev/sdX12, ARE YOU SURE?
CTRL+C if not, ENTER to continue

Waiting device /dev/sdX12.......

Click to expand...

Click to collapse

mrbubs3 said:

Is there an IRC channel for this? My device is not being detected on the Ubuntu live CD but is on my windows 7 machine.

Click to expand...

Click to collapse

12manytimes said:

i have the mt4g glacier...

im running ubuntu (12.10)

i installed the files in the home directory in linux..

after i plug the phone up with no battery, etc...

and type ./brickdetect.sh

it says the device is not detected...

what am im doing wrong?

Click to expand...

Click to collapse

GoPadge said:

I have a MT4GS that's showing in Windows as qhsusb_dload.

I tried to follow the direction in post 1, but I can't get any of my HTC phones to show in my Ubuntu VM.

Click to expand...

Click to collapse