[Q] Unbrick Telus Desire HD (QHSUSB_DLOAD after flash boot.img to S-ON DHD)

Search This thread

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
UPDATE:
I downloaded some xxxx.HEX files and tried flashing them. Only two of them flashed.
After flashing the first one, windows detected the phone as Fastboot XT626 NS
Picture 1

Second one was detected as USB STORAGE but it was also showing as an Unknown device under the mass storage devices
Picture 2
1. Can you confirm you used the emmcswdownload (from QPST) to flash the HEX file.
2. Did you use any MBN file, if yes, which
3. Which HEX/MBN combination resulted in the fastboot xt626 mode
4. which hex/mbn combination resulted in the storage mode
5. if you take the battery out and re-install it then plugin your phone to the pc again, what is its current mode? QHSUSB_DLOAD, fastboot xt626 or storage?
 

mickeyasamoah

Senior Member
Jan 11, 2013
979
230
Accra
1. Can you confirm you used the emmcswdownload (from QPST) to flash the HEX file.
2. Did you use any MBN file, if yes, which
3. Which HEX/MBN combination resulted in the fastboot xt626 mode
4. which hex/mbn combination resulted in the storage mode
5. if you take the battery out and re-install it then plugin your phone to the pc again, what is its current mode? QHSUSB_DLOAD, fastboot xt626 or storage?

1. I used software download.
2.I used the 7x30_msimage.mbn
3. I Used the 7x30prg.hex for fastboot ....
4.The ARMPRG.HEX
5.Everything resets to QHSUSB_DLOAD when you take out the battery.

So how is it going with the qd.pl file?
Were u able to load the .HEX file with it?
 

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
So far I can load the MPRG7x30.bin (original file MPRG7x30.hex) to phone, but failed to load the MBN file after that.

Before loading hex file:
Code:
: new high speed USB device using ehci_hcd and address 2
: New USB device found, idVendor=05c6, idProduct=9008
: New USB device strings: Mfr=1, Product=2, SerialNumber=0
: Product: QHSUSB_DLOAD
: Manufacturer: Qualcomm CDMA Technologies MSM

After loading hex file:
Code:
: new high speed USB device using ehci_hcd and address 9
: New USB device found, idVendor=22b8, idProduct=2df1
: New USB device strings: Mfr=4, Product=3, SerialNumber=5
: Product: Fastboot XT626 NS
: Manufacturer: Motorola Inc.
: SerialNumber: 0000000000000000

So it becomes a Motorola device. 'fastboot devices' gives all zeros sn device. 'adb devices' gives nothing.

I will try other HEX file next. Thanks.
 

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
I got the following error after loading ARMPRG.hex:
Code:
$ perl ./fixdhd.pl --fixdhd
fixdhd.pl version 20140212.
This function is for HTC Desire HD which is in QDLoader mode only. 
!! You are running it on your own risk!!
Please plugin your DHD and press enter...
Qualcomm device is (05c6:9008/9025): Bus 001 Device 026: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Please input lower case 'y' if you confirm to move forward.
Device found, load ARMPRG.bin? y
Opening ttyUSB port...
Loading ARMPRG.bin at 2147483648...
....................................................................................................................................................................................................................................................................................................Executing file...
..So far so good, load 7x30_msimage.mbn? y
Opening ttyUSB port...
Sending MAGIC...
..Good magic response from DHD
Sending secureMode...
SENDING: 7e 17 01 57 c6 7e
RECEIVED: 18 b1 6c
Sending openMulti ...
SENDING: 7e 1b 21 f5 4e 7e
RECEIVED: 0e 4e 6f 20 70 61 72 74 69 74 69 6f 6e 20 74 61 62 6c 65 20 72 65 63 65 69 76 65 64 20 62 65 66 6f 72 65 20 6f 70 65 6e 20 6d 75 6c 74 69 0a f5 8f
MSG: No partition table received before open multi 
RECEIVED: 0d 0f 00 00 00 4e 6f 20 70 61 72 74 69 74 69 6f 6e 20 74 61 62 6c 65 20 72 65 63 65 69 76 65 64 20 62 65 66 6f 72 65 20 6f 70 65 6e 20 6d 75 6c 74 69 a4 c3
ERROR: No partition table received before open multi
Invalid openMulti response.
In the protocol doc I have for now, there is no secureMode, openMulti, or Magic command, but the code runs well with both magic and secureMode, but fails at openMulti.
 

Attachments

  • fixdhd20140212.zip
    640.9 KB · Views: 498
  • 80-39912-1_Rev_A_DMSS_Download_Protocol.pdf
    239 KB · Views: 280
  • Like
Reactions: adfree

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
The phone will reply 'Write unsuccessful' (hex 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c) error if I skip the multiOpen.

Code:
If skip both securemode and multiopen:

Sending MAGIC...
..Good magic response from DHD
Loading 7x30_msimage.mbn ...
Writing 1024 bytes to 0x00000000; 1981480 bytes left.
SENDING: 7e 07 00 00 00 00 0a 00 00 ...
...
RECEIVED: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a 65 ac
Invalid Response: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a

If skip the multiopen only:

Sending MAGIC...
..Good magic response from DHD
Sending secureMode...
SENDING: 7e 17 01 57 c6 7e
RECEIVED: 18 b1 6c
Loading 7x30_msimage.mbn ...
Writing 1024 bytes to 0x00000000; 1981480 bytes left.
SENDING: 7e 07 00 00 00 00 0a 00...
...
RECEIVED: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a 65 ac
Invalid Response: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a
 

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
As my understanding, the MBN file for the first stage should have partition table in the beginning at offset 0x1fe, so the two bytes should be '55AA' (as the attached file from http://xdaforums.com/showthread.php?t=2136738). None of our current MBN files has that so we need go ahead and find the right mbn file. Don't know if this is the reason you got the 'cookie error' with QPST.
 

Attachments

  • 8660_msimage.zip
    407 KB · Views: 179
Last edited:

mickeyasamoah

Senior Member
Jan 11, 2013
979
230
Accra
With QPST, after selecting Program Download, and selecting the Multi-Image Tab, i select Sec Boot 2.0, and select start, it loads and then ask for the partition table.mbn.
So i am thinking, We need partition.mbn file.
I think thats our only chance.

I am thinking if we put up a thread on the DHD forum for people to upload thier partition table through this procedure,We can ask the author of this thread so that he can create a partition.mbn for us.
What do you think??
 

mickeyasamoah

Senior Member
Jan 11, 2013
979
230
Accra
@fairsimple I have found these partition.mbn and a HEX editor which is used for editing such files.

I havent tried them yet.
 

Attachments

  • HxDSetupEN.zip
    851.6 KB · Views: 300
  • partition.zip
    296 bytes · Views: 320
Last edited:

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
@fairsimple I have found these partition.mbn and a HEX editor which is used for editing such files.

I havent tried them yet.

As my understanding, the first step should be loading the HEX file (which I think we found) and the MBN file (which I think we still miss). After that the phone will become SD device. The 2nd step is to load partition table and SBL1/2/3, TZ, RPM, etc.

Anyway, I will check those files to see if you can load. Thanks.
 

tjnapster555

Member
Feb 3, 2014
32
6
my DHD problem is exactly as yoyrs

i install a app in stock ROM didn't root my device and it was installing then did installing for long
then i pulled the battery then on it show htc logo then off then never on
its not charging but when connect to PC show as QHSUSB_DLOAD) :(
 
  • Like
Reactions: Branded badmash

mickeyasamoah

Senior Member
Jan 11, 2013
979
230
Accra
i install a app in stock ROM didn't root my device and it was installing then did installing for long
then i pulled the battery then on it show htc logo then off then never on
its not charging but when connect to PC show as QHSUSB_DLOAD) :(

You are welcome brother. We still working on a fix. You are welcome to help.

---------- Post added at 09:01 PM ---------- Previous post was at 08:49 PM ----------

As my understanding, the first step should be loading the HEX file (which I think we found) and the MBN file (which I think we still miss). After that the phone will become SD device. The 2nd step is to load partition table and SBL1/2/3, TZ, RPM, etc.

Anyway, I will check those files to see if you can load. Thanks.

I taught we the SD device part done, reason is because when i open software programmer (QPST),and select Multi-Image Tab, i select Sec Boot 2.0, and select advanced,it shows the files needed to get the device into hboot or bootloader mode. You can check it out if am wrong.

So as i was saying, when i click start after selecting Multi-Image tab and Sec Boot2.0, it loads the HEX file and then gets stuck at partition.
But after adding the partition file i uploaded, it now gets stuck on the file next to partition advance.

Maybe the SBL1/2/3,tz,RPM is for the samsung devices as i saw those files in the brixfix files.
Fromthe advanced option in Multi-Image tab, we need partition,fsbl,amss,osbl(which i think is the bootloader{or hboot}).

Or i could be wrong.
 
  • Like
Reactions: tjnapster555

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
You are welcome brother. We still working on a fix. You are welcome to help.
Welcome on board @tjnapster555. If you have Linux experience, can you try to run the Perl script as post #19 and check if you get same result. http://xdaforums.com/showpost.php?p=49675637&postcount=19

I taught we the SD device part done, reason is because when i open software programmer (QPST),and select Multi-Image Tab, i select Sec Boot 2.0, and select advanced,it shows the files needed to get the device into hboot or bootloader mode. You can check it out if am wrong.

So as i was saying, when i click start after selecting Multi-Image tab and Sec Boot2.0, it loads the HEX file and then gets stuck at partition.
But after adding the partition file i uploaded, it now gets stuck on the file next to partition advance.

Maybe the SBL1/2/3,tz,RPM is for the samsung devices as i saw those files in the brixfix files.
Fromthe advanced option in Multi-Image tab, we need partition,fsbl,amss,osbl(which i think is the bootloader{or hboot}).

Or i could be wrong.
FYI: as @darkspr1te post here (http://xdaforums.com/showpost.php?p=33082185&postcount=29), the HEX and first step MBN files should be loaded by EMMCSWDOWNLOAD. However, I keep getting 'cookie error' with that (screen attached).

When I try the 'multi-image' tab as you did, I got error too.

I agree with you regarding that DHD has different partitions than samsung, and the osbl should be the bootloader/hboot, but I still don't think we have move the phone to SD mode. If the DHD is in SD mode, after you plugin the cable, the pc should have some new drives (like you plugin a usb drive or sd to the memory slot).
 

Attachments

  • emmsdl-err1.png
    emmsdl-err1.png
    78.3 KB · Views: 177
  • mulit-image-err1.png
    mulit-image-err1.png
    62.6 KB · Views: 150
  • Like
Reactions: tjnapster555

mickeyasamoah

Senior Member
Jan 11, 2013
979
230
Accra
Welcome on board @tjnapster555. If you have Linux experience, can you try to run the Perl script as post #19 and check if you get same result. http://xdaforums.com/showpost.php?p=49675637&postcount=19


FYI: as @darkspr1te post here (http://xdaforums.com/showpost.php?p=33082185&postcount=29), the HEX and first step MBN files should be loaded by EMMCSWDOWNLOAD. However, I keep getting 'cookie error' with that (screen attached).

When I try the 'multi-image' tab as you did, I got error too.

I agree with you regarding that DHD has different partitions than samsung, and the osbl should be the bootloader/hboot, but I still don't think we have move the phone to SD mode. If the DHD is in SD mode, after you plugin the cable, the pc should have some new drives (like you plugin a usb drive or sd to the memory slot).

For the multi-image tab, select multi-sec.2.0, that's why you keep getting that error.
So try that and see.

Sent from my GT-I9100 using xda app-developers app
 
  • Like
Reactions: tjnapster555

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
  • Like
Reactions: tjnapster555

tjnapster555

Member
Feb 3, 2014
32
6
Welcome on board @tjnapster555. If you have Linux experience, can you try to run the Perl script as post #19 and check if you get same result. http://xdaforums.com/showpost.php?p=49675637&postcount=19


FYI: as @darkspr1te post here (http://xdaforums.com/showpost.php?p=33082185&postcount=29), the HEX and first step MBN files should be loaded by EMMCSWDOWNLOAD. However, I keep getting 'cookie error' with that (screen attached).

When I try the 'multi-image' tab as you did, I got error too.

I agree with you regarding that DHD has different partitions than samsung, and the osbl should be the bootloader/hboot, but I still don't think we have move the phone to SD mode. If the DHD is in SD mode, after you plugin the cable, the pc should have some new drives (like you plugin a usb drive or sd to the memory slot).

sorry never use linux
 

mickeyasamoah

Senior Member
Jan 11, 2013
979
230
Accra
I can't find the 'multi-sec 2.0'. I have QPST v2.7 b378.

Also if you have access to a working DHD (I think we need it as rooted), we need backup the whole internal memory as #2 of this post, then we may can get the partition table from the backup file.

http://xdaforums.com/showthread.php?t=1188510

Its there check the image below.

And i was thinking of backing up another DHD so that we can get all the files for unbricking the device.
But i dont have another DHD. So then, how about we put up a thread in the DHD forum giving the guidelines on how to backup the DHD for unbricking purpose.
What do you think?

Also do you have any idea on how to backup the DHDs mbn files?
 

Attachments

  • Capture.PNG
    Capture.PNG
    69.1 KB · Views: 193

fairsimple

Senior Member
Aug 23, 2013
83
35
Toronto
i will wait for you guys and hoping someone will unbrirk his device :)
Thanks to be patient ;)

Its there check the image below.

And i was thinking of backing up another DHD so that we can get all the files for unbricking the device.
But i dont have another DHD. So then, how about we put up a thread in the DHD forum giving the guidelines on how to backup the DHD for unbricking purpose.
What do you think?

Also do you have any idea on how to backup the DHDs mbn files?

Agree. We should discover lots of info from the working DHD.

As my understanding, to get a full emmc backup, the phone has to be rooted, and has a SD inserted with at lease 2G free space (since DHD has 1.5G internal flash), asthis post (by TrevE) , user can use command 'dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img' to copy whole internal emmc to a file on microSD. I think the command can either run from a terminal app on the phone or use 'adb shell ..' command from a PC when phone has usb development on. Please note the generated file should not be posted publicly since the backup file has the phone's IMEI number and other phone data.

This post(by E:V:A) shows how to get the partition info from a working phone. I also find a tools folder which has the fdisk/gdisk/ect apps from the zip of Brixfix V2 (by darkspr1te) but don't know if them work on DHD or not.

However I don't think either of above method will provide us with MBN file directly, even we may can build MBN from the whole emmc backup.

Also I still don't think we have put the phone to SD mode for loading partition table and other xbl partitions. As the 2nd picture from this post, we need the right MBN file (which is a mini file system to run the phone as SD).

FYI: with QPST software download app - multi-image tab, if I only select partition.mbn and uncheck all others, I got 'Could not Communicate in Diagnostic Mode' error.
 
  • Like
Reactions: tjnapster555

mickeyasamoah

Senior Member
Jan 11, 2013
979
230
Accra
Thanks to be patient ;)



Agree. We should discover lots of info from the working DHD.

As my understanding, to get a full emmc backup, the phone has to be rooted, and has a SD inserted with at lease 2G free space (since DHD has 1.5G internal flash), asthis post (by TrevE) , user can use command 'dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img' to copy whole internal emmc to a file on microSD. I think the command can either run from a terminal app on the phone or use 'adb shell ..' command from a PC when phone has usb development on. Please note the generated file should not be posted publicly since the backup file has the phone's IMEI number and other phone data.

This post(by E:V:A) shows how to get the partition info from a working phone. I also find a tools folder which has the fdisk/gdisk/ect apps from the zip of Brixfix V2 (by darkspr1te) but don't know if them work on DHD or not.

However I don't think either of above method will provide us with MBN file directly, even we may can build MBN from the whole emmc backup.

Also I still don't think we have put the phone to SD mode for loading partition table and other xbl partitions. As the 2nd picture from this post, we need the right MBN file (which is a mini file system to run the phone as SD).

FYI: with QPST software download app - multi-image tab, if I only select partition.mbn and uncheck all others, I got 'Could not Communicate in Diagnostic Mode' error.

Wow!!! We have to ask @darkspr1te how he got/made his mbn files. Also, If we get a volunteer to backup his device, it would be saved into a .img file. Then the person could delete his/her personal info from the backup by opening it with a .img software like Power Iso or something.

FYI: with QPST software download app - multi-image tab, if I only select partition.mbn and uncheck all others, I got 'Could not Communicate in Diagnostic Mode' error.

I dont know why you get that error but with mine, it flashes the partition file and gets stuck since i dont have the next file. But when i leave all the mbn files selected, it flashes the partition file then stops the flash due to the next file being incorrect.

Anyway did you try removing the battery and re-inserting it?
Maybe you flashed a HEX file and its kind of blocking the communication.

---------- Post added at 07:33 PM ---------- Previous post was at 06:34 PM ----------

I just found these. It appears to be able to do a full emmc backup.

This(Documentation on the software) and That(download link to the file)
 
  • Like
Reactions: tjnapster555

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Hi Everyone. By opening this thread, I hope I can 1) log my work, 2) get input from the wonderful people here, 3) benefit others who has the same type of brick. I have been reading/following/searching stuffs here for a while, and this is my first dirty-work-to-do. Please help me as much as you can. Thank you all!

    How I bricked my Telus HTC Desire HD:
    1. Phone has stock Android 2.3 and one day it keeps rebooting
    2. Unlock bootloader by HTCDev
    3. Didn't turn S-OFF
    4. Flash _TOUCHRECOVERY__CWM_5.8.0.0_Touch_Recovery_for_DesireHD successfully
    5. Flash cm-11-20131203-UNOFFICIAL-ace.zip successfully (after one failure) but phone is in boot loop
    6. Unzip boot.img from the CM11 zip and 'fastboot flash boot boot.img' (as in [1]). The command didn't return anything, and I disconnect the cable after about 1m

    Now the phone bricks, it doesn't boot to fastboot/hboot, charging LED never on. Connecting to PC shows a QHSUSB_DLOAD device.

    The first thing I'd like to know is the root cause of my brick. Is it because the phone has S-ON, or because I disconnected the USB cable before getting the fastboot fully done. As [2] (which is for One X), the S-ON may not be an issue, then why the fastboot command didn't return anything?

    What I got to work so far:
    1. Install driver to my PC (QHSUSB_Drivers_(x64).zip from [4], thanks JSLEnterprises)
    2. Enable the driver as test driver since it doesn't have signature (as [6])
    3. Install QPST (QPST_2.7_378.zip, from [5], thanks darkspr1te)
    4. QPST connects to phone and lists as type 'Q/QCP-XXX' which is in '*Download*' mode

    As there is an 'HTC Unbricking Project' which doesn't have DHD in its supported phones list [3], I see the hope to unbrick my DHD without JTAG. I am not expecting to have a one-click solution like the unbrick project, and I am open to do some coding if needed, but I think I should be able to restore my boot partition (or multiple partitions) with QPST. And here I need your help:

    1. What cause the brick? S-ON of the phone, or failure of fastboot
    2. Do you think I can unbrick it just with QPST
    3. If someone has a working Desire HD and uses QPST to backup its partitions to files, will I have its IMEI/CID/etc after download those files to my phone
    4. Do you think I can manully build the QPST QCN download file from a stock ROM/RUU

    Thank you!

    [1] http://xdaforums.com/showthread.php?t=2533007 (HTC Desire HD > Desire HD Android Development > [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies)
    [2] http://xdaforums.com/showthread.php?t=1603791 (HTC One X > One X Android Development > [WARNING] Flashing boot.img on S-ON devices)
    [3] http://xdaforums.com/showthread.php?t=1522351 ( HTC Sensation > Sensation Android Development > [UNBRICK] HTC Unbricking Project)
    [4] http://xdaforums.com/showthread.php?t=1041153&page=2 ( HTC Desire HD > Desire HD Q&A, Help & Troubleshooting > [Q]HTC Desire HD QHSUSB_DLOAD driver[brick caused by rom manager sdcard repartition])
    [5] http://xdaforums.com/showpost.php?p=33545892 (AT&T Samsung Galaxy Note I717 > AT&T Galaxy Note I717 General > [SOLVED]-[BRICKED]SHV-E160L Korean model)
    How to calculate partition info in post #13, 15, 16 thanks darkspr1te
    [6] http://windows7themes.net/windows-requires-a-digitally-signed-driver-windows-7.html
    [7] http://xdaforums.com/showthread.php?t=2086142 (Hardware Hacking > Hardware Hacking General > [R&D][QUALCOMM] Using QDL, EHostDL and DIAG interfaces & features)
    [8] http://xdaforums.com/showthread.php?t=905003
    (HTC Desire HD > Desire HD Android Development > [GUIDE] How to downgrade 1.7x/1.8x/2.x to 1.32.405.6, with download of stock PD98IMG.ZIP)
    [9] 7x30 HEX and MBN files in post#39 and partition.mbn and HxD HEX editor in post #48 (thanks mickeyasamoah)
    [10] Qualcomm docs in post #87 and post #88 on page 9 (thanks darkspr1te)
    [11] QFIT (flash image creation tool) in post #90 (thank darkspr1te)
    [12] fixdhd.pl v20140228 in post #98 (based on qdloader.pl thanks JCSullins(Rootz Wiki)) v20140410 in post #161 on page 17
    [13] MBN files from HP Pre 3 device in post #126 (thanks mickeyasamoah)
    [14] Qualcomm development doc in Chinese and English. Need download file from https://support.cdmatech.com/login/, https://silver.arm.com/browse or https://developer.qualcomm.com/.
    [15] Related post: Request for DHD backup and Qualcomm docs
    [16] (thanks Gussta) Qualcomm processors and Snapdragon SoCs (post #139 on page 14), and Dual boot DHD with SD
    3
    Hi darkspr1te, I think we make a big progress as getting you the QHSUSB_DLOAD exporter involved:) Thank you to spend time on this thread!

    I did read your brixfix thread (v1 mostly since it has your working history) and after we got some HEX and MBN files (thinks mickeyasamoah found them), mickeyasamoah and I tried them with both QPST and qdload.pl. With QPST, I got mostly same rsult as mickeyasamoah replys above (I didn't get partition.mbn loaded successfully as him). With my modifed qdload.pl, I confirmed the HEX/BIN file works since after that the phone reboots and reply to some streaming download message. However, I can't go ahead to loading MBN file. You can see the result from post #44 (http://xdaforums.com/showpost.php?p=50274440&postcount=44 ). Personally I don't think we get into the SD mode yet.
    I checked DMSS manual you provided on that thread, thats the limited instruction set, also thats a very old document and as E:V:A pointed out to me once, often the qualcomm docs are far behind the actual reality , please find attached a revised copy of the same document, if you compare section 3.3 between the two you will see what i mean.
    3
    Files for 8x25(karbonn a9+) from this post: http://forum.gsmhosting.com/vbb/f824/karbonn-a9-dead-qualcomm-hs-usb-qdloader-9008-how-fix-1740061/#post9962431

    Code:
    12-19-2013, 10:00	   #12 (permalink)
    umesh gaba
    Product Manager
    
     
    
     
    Join Date: Aug 2012
    Location: jalandhar,india
    Posts: 4,034 
    Member: 1792140 
    Status: Online
    Sonork: 100.1618782;gaba
    Thanks Meter: 4,644
    QPST 2.7 build 399QPST-2.7.399
    
    
    BP Firmware BP_JB_Firmware
    
    drivers ICS_pcdrivers
    
    drivers JB_pcdrivers
    
    
    
    Install QPST
    1. Extract QPST-2.7.399.rar. Run SETUP.EXE
    2. Run SETUP.EXE, press INSTALL when it prmpt to insall additional Visual C++ runtime libraries. Follow the defaults, press NEXT until it is finished with the install.
    
    Install drivers
    1. Connect deadboot flare to PC / Laptop.
    2. Go to device manager, expand PORTS (COM & LPT). Check if there is an item called Qualcomm HSUSB QDLOADER 9008. If the item is there, you are done with driver install. If it does not exist, proceed to step3.
    3. If there is no item under PORTS (COM & LPT), check device manager under OTHER DEVICES > Unknown Device
    4. Double click UNKNOWN DEVICE > UPDATE DRIVER > BROWSE MY COMPUTER > browse to the folder where you saved extracted the ICS / JB drivers. It will install the driver, if it prompts for unsigned drivers, press INSTALL ANYWAY.
    5. It should now be listed under COM PORTS > Qualcomm HSUSB QDLOADER 9008.
    
    Run QPST and reprogram EMMC (this is where the magic begins)
    If you are on Win7, make sure you run it under compatibility XP Sp3 and RUN AS ADMINISTRATOR
    
    1. Run EMMC SOFTWARE DOWNLOAD.
    2. Press BROWSE, it will detect your phone. Look for the PHONE TAB that says DOWNLOAD. Press OK.
    3. Put check mark on PROGRAM BOOTLOADERS, PROGRAM MMC DEVICE, TRUSTED.
    4. Under FLASH PROGRAMMER FILENAME, enter MPRG8X25.hex
    5. Under BOOT IMAGE, enter 8X25_msimage.mbn
    6. Press LOAD XML DEF > navigate to your extracted JB firmware > select rawprogram0 > press OPEN.
    7. Press LOAD PATCH DEF > navigate to your extracted JB firmware > select patch0 > press OPEN
    8. PRESS DOWNLOAD
    9. An warning message may appear, TIME OUT WAITING etc etc or COOKIE NOT RECEIVED. If the error is TIME OUT WAITING, press OK and then press SWITCH DEVICE TO DLOAD. Check the flare, it will show RESET FOR ENTRY QPST.
    10. Exit EMMC SOFTWARE DOWNLOAD. Proceed to flash Jelly Bean BP Firmware and then flash Jelly Bean img dump.
    11. IF ERROR IS COOKIE NOT RECEIVED, sorry it is still bricked.
    3
    Can you zip and attach the files you have, or post the link where you download them. Again I will try to use qd.pl (which should use the same MDSS protocol as QPST, but for this program we have better control:) Please also zip those files which doesn't work for you, I may also try them then.

    I was beginning to think you have had your DHD fixed by RiffBox or JTAG thats why you werent commenting.
    Any way, i have uploaded the files.

    MPRG7x30.hex and ARMPRG.HEX are the working files
    The rest arent working.
    2
    I can't find the 'multi-sec 2.0'. I have QPST v2.7 b378.

    Also if you have access to a working DHD (I think we need it as rooted), we need backup the whole internal memory as #2 of this post, then we may can get the partition table from the backup file.

    http://xdaforums.com/showthread.php?t=1188510

    Its there check the image below.

    And i was thinking of backing up another DHD so that we can get all the files for unbricking the device.
    But i dont have another DHD. So then, how about we put up a thread in the DHD forum giving the guidelines on how to backup the DHD for unbricking purpose.
    What do you think?

    Also do you have any idea on how to backup the DHDs mbn files?