Bricked ASUS ZE552KL (dead Qualcomm HS-USB QDLoader 9008)

Search This thread

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
I'll be that
guinea pig just tell me what I should do with those files. Been a bit busy so sorry for late reply...

The only file I couldn't make/extract was the firehose file, which I have attached from the Mido firmware you mentioned earlier.

Depending on which firmware you are using, you will have to edit the "partition.xml" file and rename the partitions to whatever you have. Example, I have SBL1 listed as "sbl1.img" but it may be "sbl1.bin" or "sbl1.mbn".

Try the guide here and give it a shot.

good luck!
 

Attachments

  • prog_emmc_firehose_8953_ddr.zip
    203.2 KB · Views: 1,290
  • Like
Reactions: garage69s

abatoir

Senior Member
Jun 20, 2012
92
8
The only file I couldn't make/extract was the firehose file, which I have attached from the Mido firmware you mentioned earlier.

Depending on which firmware you are using, you will have to edit the "partition.xml" file and rename the partitions to whatever you have. Example, I have SBL1 listed as "sbl1.img" but it may be "sbl1.bin" or "sbl1.mbn".

Try the guide here and give it a shot.

good luck!
OK great. Will give it a try when I get the devices in my hands, b4 I go further ill explain how I believe my device bricked. It was in bootloop so I decided to update it to the latest firmware OTA zip, but b4 I did so I unlocked the bootloader. Then proceeded with software upgrade through recovery. The process started and stock at 80% for about 1hr. I decided to restart the device and that was it. No longer boot. Just qdloader. Since my bootloader is unlocked it means I should be able to downgrade yes?
 

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
OK great. Will give it a try when I get the devices in my hands, b4 I go further ill explain how I believe my device bricked. It was in bootloop so I decided to update it to the latest firmware OTA zip, but b4 I did so I unlocked the bootloader. Then proceeded with software upgrade through recovery. The process started and stock at 80% for about 1hr. I decided to restart the device and that was it. No longer boot. Just qdloader. Since my bootloader is unlocked it means I should be able to downgrade yes?

yes, you just have to factory reset afterwards and it'll overwrite your custom recovery but it works fine, I just did it to confirm.
 

mr. king

Member
Dec 27, 2016
8
3
I got same problem with my ze520 Kl.

Hi. I have got qdloader 9008 brick on my ze520 Kl. Can't find files to get back my Fastboot. Any help?
 

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
Hi. I have got qdloader 9008 brick on my ze520 Kl. Can't find files to get back my Fastboot. Any help?

can anyone with a ze520kl assist by downloading and running parted and post the partition info?

If it's the same as the ze552kl, you should be able to use the files I uploaded earlier. Although if it's not, I don't suppose it could brick it any worse than it already is, lol.
 

mr. king

Member
Dec 27, 2016
8
3
can anyone with a ze520kl assist by downloading and running parted and post the partition info?

If it's the same as the ze552kl, you should be able to use the files I uploaded earlier. Although if it's not, I don't suppose it could brick it any worse than it already is, lol.

i tried flasing those files but got the same errors as @binarez
any help before i send the brick to service center will be appreciated. thanks.
 
Last edited:
  • Like
Reactions: garage69s

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
i tried flasing those files but got the same errors as @binarez
any help before i send the brick to service center will be appreciated. thanks.

check post 19 and 21 for the updated files.

Depending on the firmware you are trying to flash, the partitions have different names so just open the partition.xml file and edit the partition filename to match to the filename you have, or vice versa.
 

mr. king

Member
Dec 27, 2016
8
3
check post 19 and 21 for the updated files.

Depending on the firmware you are trying to flash, the partitions have different names so just open the partition.xml file and edit the partition filename to match to the filename you have, or vice versa.

Can u please elaborate? Sorry I'm noob in that kind of brick. I just want to get my boot loader back so that I can flash rom. What files do I need exactly for my zenfone 3 ze520kl and where to get them and how will I use them to get my fastboot back? Thanks for helping..
 

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
Can u please elaborate? Sorry I'm noob in that kind of brick. I just want to get my boot loader back so that I can flash rom. What files do I need exactly for my zenfone 3 ze520kl and where to get them and how will I use them to get my fastboot back? Thanks for helping..

download a copy of the latest firmware for your phone from the ASUS site http://dlcdnet.asus.com/pub/ASUS/Ze...424.245841030.1500277529-605644017.1500277529

---------- Post added at 10:46 PM ---------- Previous post was at 10:45 PM ----------

Open the above file with your preferred zip or rar archive manager, navigate to the "firmware-update" folder, select both sbl1 files (one is the backup) and extract them to the same directory where you saved the files I uploaded in post 19 and 21 of this thread. Open the partition.xml file and change sbl1.img and sbl1bak.img to whatever the two files you extracted are. Delete everything lines 19-83 and save. Open the rawprogram0.xml file and do the same (I think I named them sbl1.bin and sbl1bak.bin, oops), except delete lines 8-72 plus line 5 and save.

Rename both files by removing the "ze552kl" prefix and the "-v2" suffix.

Finally, follow the guide here

You may need the GUID partition table which I don't have for your phone. We need a ze520kl user to extract it and upload it.
 
Last edited:

mr. king

Member
Dec 27, 2016
8
3
download a copy of the latest firmware for your phone from the ASUS site http://dlcdnet.asus.com/pub/ASUS/Ze...424.245841030.1500277529-605644017.1500277529

---------- Post added at 10:46 PM ---------- Previous post was at 10:45 PM ----------

Open the above file with your preferred zip or rar archive manager, navigate to the "firmware-update" folder, select both sbl1 files (one is the backup) and extract them to the same directory where you saved the files I uploaded in post 19 and 21 of this thread. Open the partition.xml file and change sbl1.img and sbl1bak.img to whatever the two files you extracted are. Delete everything lines 19-83 and save. Open the rawprogram0.xml file and do the same (I think I named them sbl1.bin and sbl1bak.bin, oops), except delete lines 8-72 plus line 5 and save.

Rename both files by removing the "ze552kl" prefix and the "-v2" suffix.

Finally, follow the guide here

You may need the GUID partition table which I don't have for your phone. We need a ze520kl user to extract it and upload it.

So I have to use the 8953 programmer file from Mido firmware from post 21?
 
  • Like
Reactions: Voylonhg

ExperienceTesla

Senior Member
Jan 7, 2016
88
21
every time i press "download" in qfil it show this:
v00WL6l.png

i'm in panic. i tried to rename/unpack all files but not work
SaRsp01.png

anyone can help me please? thanks
 

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
every time i press "download" in qfil it show this: 
i'm in panic. i tried to rename/unpack all files but not work
i'm in panic. i tried to rename/unpack all files but not work 
anyone can help me please? thanks

That Sahara error is a common issue with many different fixes. Some people fix it by trying different USB ports, or a different computer/os (windows 10 sometimes causes issues). Some people say having everything in the same root directory makes a difference too. One person wrote "The trick is to click "Download Content" as sooooooon as you hit enter on "adb reboot edl", so maybe mess around with the timing of turning on the phone and clicking download, even plug it in and continually click download while you turn it on.
 
  • Like
Reactions: ExperienceTesla

ExperienceTesla

Senior Member
Jan 7, 2016
88
21
That Sahara error is a common issue with many different fixes. Some people fix it by trying different USB ports, or a different computer/os (windows 10 sometimes causes issues). Some people say having everything in the same root directory makes a difference too. One person wrote "The trick is to click "Download Content" as sooooooon as you hit enter on "adb reboot edl", so maybe mess around with the timing of turning on the phone and clicking download, even plug it in and continually click download while you turn it on.

thanks for the help. i try :)
 

ExperienceTesla

Senior Member
Jan 7, 2016
88
21
i'm doing this:
download prog_emmc_firehose_8953_ddr.zip, ze552kl-partition-v2.xml, ze552kl-rawprogram0-v2.xml, ze552kl-gpt_backup0.zip, ze552kl-gpt_main0.zip, patch0.xml.
rename ze552kl-partition-v2.xml in to partition.xml, ze552kl-rawprogram0-v2.xml in to rawprogram0.xml, ze552kl-gpt_backup0.zip in to gpt_backup0.zip, ze552kl-gpt_main0.zip in to gpt_main0.zip. open the firmware zip, go to the firmware-update folder, copy sbl1.mbr and sbl1(with other numbers here).mbr in the same folder. rename both in sbl1.bin and sbl1bak.bin. open partition.xml, delete lines 19 -> 83 and rename sbl1.img and sbl1bak.img into sbl1.bin and sbl1bak.bin and save. open rawprogram0.xml delete lines 5 - 8 -> 72 and rename sbl1.img and sbl1bak.img into sbl1.bin and sbl1bak.bin and save. install adb and bootloader asus drivers, install qfil, open qfil, select flat build, in programmer path put prog_emmc_firehose_8953_ddr.zip, in load xml put rawprogram0.xml and patch0.xml, connect the phone and clic download.
i tried on a laptop on 3 different usb ports and 2 os: windows 10 and windows 7 and on a personal pc with 6 usb port and windows 7 and windows 10. same sahara error on all. i'm doing the correct procedure?
 

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
i'm doing this:
download prog_emmc_firehose_8953_ddr.zip, ze552kl-partition-v2.xml, ze552kl-rawprogram0-v2.xml, ze552kl-gpt_backup0.zip, ze552kl-gpt_main0.zip, patch0.xml.
rename ze552kl-partition-v2.xml in to partition.xml, ze552kl-rawprogram0-v2.xml in to rawprogram0.xml, ze552kl-gpt_backup0.zip in to gpt_backup0.zip, ze552kl-gpt_main0.zip in to gpt_main0.zip. open the firmware zip, go to the firmware-update folder, copy sbl1.mbr and sbl1(with other numbers here).mbr in the same folder. rename both in sbl1.bin and sbl1bak.bin. open partition.xml, delete lines 19 -> 83 and rename sbl1.img and sbl1bak.img into sbl1.bin and sbl1bak.bin and save. open rawprogram0.xml delete lines 5 - 8 -> 72 and rename sbl1.img and sbl1bak.img into sbl1.bin and sbl1bak.bin and save. install adb and bootloader asus drivers, install qfil, open qfil, select flat build, in programmer path put prog_emmc_firehose_8953_ddr.zip, in load xml put rawprogram0.xml and patch0.xml, connect the phone and clic download.
i tried on a laptop on 3 different usb ports and 2 os: windows 10 and windows 7 and on a personal pc with 6 usb port and windows 7 and windows 10. same sahara error on all. i'm doing the correct procedure?

I think the firehose file needs to be extracted before adding into QFIL, but aside from that everything looks right.

I think there was one other app we could try, I'll take a look for that tonight. Otherwise, I'm sorry ExperiencedTesla, if it still doesn't work, you'll have to send it back to ASUS. Maybe someone more experienced will be able to assist.
 

wang1chung

Senior Member
Aug 9, 2010
616
121
toronto
I think tool studio emmc is the only way then to get this to work.

I have been messing around with qpst's emmcwsdownload, as per this guide, and have attached an 8953_msimage.mbn it created.

I'll take a look at the MPRG file tomorrow.

edit: added second version of 8953_msimage
 

Attachments

  • 8953_msimage.mbn.zip
    307.1 KB · Views: 754
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Cool, I haven't returned mine for a repair yet, still hoping I can fix it myself. Keep me posted on your progress, I'll take a look myself into this toolkit.

    Hey binarez, have you tried the Asus flash tool with the raw firmware? take a look at this and/or this.

    I tried to extract the raw firmware in the hopes of finding the partition and xml files but to no avail.
    1
    Hi, if someone here knows how to use the Qualcomm tools or any tool to unbrick my phone, your input will be highly regarded!

    I bricked my ASUS ZE552KL... and I know how : it was full and I started a memory hungry app and it just froze. The app was probably caching some stuff locally. I hold the Power On button to reboot it and it doesn't boot at all (black screen, all LEDs are off, etc). This is known in some articles online as OLD “Qualcomm HS-USB QDLoader 9008” MODE (the worst kind AFAIK). When I connect the phone to my Win7 machine, I have a PORT that opens as “Qualcomm HS-USB QDLoader 9008”. I do not get the Qualcomm disk drive.

    I found this guide (cannot post URL but dotandroid dot com/android-root-guides/unbrick-qualcomm-mobiles) that offered me some hope. I followed the instructions as best as I could. That means I uninstalled all the Qualcomm device on my system, I installed the proper drivers (QualcommDrv/Allx64, I have a 64 bit Windows installation) and the proper version of QFIL (QPST tools). I cannot remove the battery from this phone so I had to skip the "battery removal for 5 secs" step. I tried all kind of key combinations before/while/after plugging the USB cable.

    I got to the point where I try to flash the files from 8675_W00 but the MBN file provided in it (prog_emmc_firehose_8936.mbn + rawprogram0.xml + patch0.xml) but I just cannot get it to work. I get the following error from QFIL:

    Code:
    Sahara Version:0
    Start Sending Programmer
    Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
       QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
       QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
    Download Fail:Sahara FailSahara Fail
    Finish Download

    Eventually, I realized that 8936 was the cpu model number and that the ZE552KL model is 8953. I have searched pretty much everywhere on the internet for a prog_emmc_firehose_8953.mbn file but I can't find it.

    I found some documentation on how to make your own mbn file using emmcswdownload.exe but it doesn't work because the partition_boot.xml file I'm using doesn't have the right syntax:

    Code:
    C:\Program Files (x86)\Qualcomm\QPST\bin>emmcswdownload.exe -f 8660_msimage.mbn
    -x partition_boot.xml -s 1G -g 4M
    
    C:\Program Files (x86)\Qualcomm\QPST\bin>-f = 8660_msimage.mbn
    -x = partition_boot.xml
    -s = 1073741824
    -t =
    -f : Beginning image build...
    -x : Parsing partition description file...
    CExParsePartition
    -x : error parsing partition description file: Document error on element type "r
    oot" and name/value "<image> tag no longer supported"

    Conclusion: I'm new to this and I have no idea what I'm doing :)

    Two questions:

    1- Can I recover files from the phone before wiping it while it is in this OLD "Qualcomm HS-USB QDLoader 9008” MODE? I have some pictures and movies from my daughter's birthday that I would like to save, if possible.

    2- How can I resurrect this bad boy? It's under warranty and I didn't mess it further yet so I'll get it replaced if I can't get it to boot but I figured that ZE552KL-specific info was not commonly found on the web... maybe we can fix this thing as a community for future reference!

    Thanks for any help with this matter!
    1
    Hey binarez. There are a couple of devices out there that uses our processor. (my device is bricked as well) one of which is Xiaomi Redmi note4 mido. That's the best option to work with cause Xiaomi utilities Qualcomm edl mode to reprogram their devices. So I'm hoping to use some files from the mido softWare to get my ze552kl repaired.

    Cool, I haven't returned mine for a repair yet, still hoping I can fix it myself. Keep me posted on your progress, I'll take a look myself into this toolkit.
    1
    Hey binarez, have you tried the Asus flash tool with the raw firmware? take a look at this and/or this.

    I tried to extract the raw firmware in the hopes of finding the partition and xml files but to no avail.

    i have checked the raw file! its all the raw partition images, i believe there are in correct order! i even tried the sd card boot repair with them but it didnt work.the OTA update zip and the raw file combined both have identical files to xiaomi edl firmware pack but files like xml an others are nowhere to be found. which partitions are needed to get our devices to boot into the bootloader?
    1
    I believe you need sbl1 at the least, but possibly some others like rpm, tz, devcfg, and aboot.

    How did you open the .raw firmware? I renamed to zip but only got 800kb of the 4gig image viewable?

    use 7-zip exe, thats what i used to do the extract the raw file! if my memory serves me right, all the files that you have listed are in the raw file, the extracted files are in my hard drive at work, esle i would have sent screenshoot. is it possible for someone to edit the partition file(xml) of the xiaomi mido to match that of the asus ze552kl?