[GUIDE/TOOL]the ultimate DFU UNBRICK TOOL

BKHaines

New member
Nov 6, 2017
1
0
1
Bout t test it out on my ZTE blade sparks z971. I have tried dang near everything possible... And that's a lot of crap. But since it's frp locked I had nothing but trouble. I was able to bypass and use as a 'wifi' phone. Just nothing google related or actually using data, and cruicial system things that are needed to root like debugging, etc. But hoping this will work. Unless u say otherwise. But thanks again. ✌
 

kinho066

New member
Dec 17, 2018
1
1
3
Man, what magic is this
I was already thinking about how I would open the phone
3 days trying everything, and finally i found your guide. thanks so much
When i get married the wife is your
 
Last edited:
  • Like
Reactions: raystef66

dcwbis

New member
Dec 24, 2018
4
1
0
Add me to the list of folks who say "THIS IS AMAZING". Four days ago I began trying to unlock my bootloader, install TWRP, and Lineage 15.1. After a lot of fiddling around I accomplished the first two tasks. The attempt to install lineage gave an Error 7. Trying many workarounds I eventually got the phone so it wouldn't boot at all. The power button would cause ZTE to flash for about 2 seconds, then go blank. The led would blink about 3 times - then nothing (volume up or down with power did the same thing). The only thing I could do was get it into EDL mode with the blank screen. Device manager saw it as: ZTE Handset diagnostic interface (DFU). I thought I was fully bricked.
I was reading so many different threads and the only one that looked like it may work was with using an EDL cable. Many pages into that thread it had a link to this one. Yesterday afternoon I had a DFU special. After connecting the phone with a USB cable, running this program and MIFlash I once again have a fully functioning phone. Thank you so much to all who contributed to this masterpiece.
 
  • Like
Reactions: raystef66

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
I had previously gotten this tool to work, but not now, it seems my phone decided to ring in the new year with a hard brick just after midnight. The situation:

I EDL-flashed @djkuz''s B20 Oreo EDL for the A2017U. It seemed to work, so I booted into stock recovery and did a factory reset. Afterwards I tried to reboot, but the ZTE logo quickly flashes and powers off. Battery was at 90ish at the time, so low battery wasn't the issue. Now I don't even get the bootloader unlocked screen. I can't enter recovery, FTM, or EDL. Now I get a black screen with a solid red, not blinking light, which indicates DFU.

But when I plug the phone into laptop (running Windows 10 Enterprise Insider Preview 1809), it is not detected as DFU in Device Management. With all categories unhidden, there is nothing listed under Ports. I do get 3 QUSB 9008 entries, 2 of which have a "device not connected" description. The 3rd says connected, but also says no driver is installed.

I installed the latest DFU Multi tool as instructed by @raystef66 in post # 35. When checking in the Ports category in the tool, I get a message saying no USB ports detected. I have a Sager 2017 gaming laptop with 5 USB 3.1 ports and 2 Thunderbolt/USB C ports. I have tried connecting to PC with all ports, as well as with the stock cable and an Anker PowerLine fiber braided cable. Same message. Next I will try the EDL cable I bought from Amazon months ago (which never worked then). But I keep it away from home in a long term storage unit with other not essential items, so it will be hours before I can report again.

I'm currently draining the battery to 0% until the light turns off, then I will repeat the process until the battery is completely exhausted and no light comes on, since most phones keep a small reserve charge even when they say they're at 0%. After that I will trickle charge via USB to laptop for up to 15 mins. The battery charging screen doesn't appear either, so I have no way of knowing for sure what the % is.

I'm trying to avoid RMAing the device to ZTE a 2nd time, so I may also try the 4th category brick guide to short circuit the pin if all else fails. I have a set of precision screwdrivers and electronic's repair tools for phones for that purpose, and a bit of practice on my really old junk phones that I no longer use regularly.

Really appreciate suggestions, thanks!
 
Last edited:

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
I had previously gotten this tool to work, but not now, it seems my phone decided to ring in the new year with a hard brick just after midnight. The situation:

I EDL-flashed @djkuz''s B20 Oreo EDL for the A2017U. It seemed to work, so I booted into stock recovery and did a factory reset. Afterwards I tried to reboot, but the ZTE logo quickly flashes and powers off. Battery was at 90ish at the time, so low battery wasn't the issue. Now I don't even get the bootloader unlocked screen. I can't enter recovery, FTM, or EDL. Now I get a black screen with a solid red, not blinking light, which indicates DFU.

But when I plug the phone into laptop (running Windows 10 Enterprise Insider Preview 1809), it is not detected as DFU in Device Management. With all categories unhidden, there is nothing listed under Ports. I do get 3 QUSB 9008 entries, 2 of which have a "device not connected" description. The 3rd says connected, but also says no driver is installed.

I installed the latest DFU Multi tool as instructed by @raystef66 in post # 35. When checking in the Ports category in the tool, I get a message saying no USB ports detected. I have a Sager 2017 gaming laptop with 5 USB 3.1 ports and 2 Thunderbolt/USB C ports. I have tried connecting to PC with all ports, as well as with the stock cable and an Anker PowerLine fiber braided cable. Same message. Next I will try the EDL cable I bought from Amazon months ago (which never worked then). But I keep it away from home in a long term storage unit with other not essential items, so it will be hours before I can report again.

I'm currently draining the battery to 0% until the light turns off, then I will repeat the process until the battery is completely exhausted and no light comes on, since most phones keep a small reserve charge even when they say they're at 0%. After that I will trickle charge via USB to laptop for up to 15 mins. The battery charging screen doesn't appear either, so I have no way of knowing for sure what the % is.

I'm trying to avoid RMAing the device to ZTE a 2nd time, so I may also try the 4th category brick guide to short circuit the pin if all else fails. I have a set of precision screwdrivers and electronic's repair tools for phones for that purpose, and a bit of practice on my really old junk phones that I no longer use regularly.

Really appreciate suggestions, thanks!
Latest times I do see more members having trouble after flashing an EDL.
These posts are somewhat similar : https://forum.xda-developers.com/showpost.php?p=78543622&postcount=218
https://forum.xda-developers.com/showpost.php?p=78549031&postcount=219
I too ran into some problems after flashing. When tapping button combo's my device didn't even do anything anymore, no leds, nothing. In usb ports, all faulty description...
Had to drain battery overnight.
Once you tap power and you'll notice a single blinking light, the phone is drained. By then, hold the 3 buttons and put the phone into EDL again and connect to pc like you did before. It'll work.
Do the procedure right over again and hopefully this time it'll work. For me it was.
I haven't had these problems before but I do sense some latest updates have made it harder to EDL right in W10....don't know for sure but there's something changed....
I also remember I had downloaded the EDL Tool again. Perhaps @djkuz has updated the tool ??
 
Last edited:

Mee68

Member
Jan 14, 2013
15
4
0
My phone does not get into EDL mode. I pressed all three buttons (Vol up + Vol down+ power) and nothing happens. Can anyone help. It can into FTM and recovery but not EDL. Any one can help? Thanks.
I am on stock Oreo :ZTE_A2017V3.0.0B19 (Chinese version).
 

sToRm1nG

Senior Member
Oct 24, 2013
558
354
63
Near Zurich
Latest times I do see more members having trouble after flashing an EDL.
These posts are somewhat similar : https://forum.xda-developers.com/showpost.php?p=78543622&postcount=218
https://forum.xda-developers.com/showpost.php?p=78549031&postcount=219
I too ran into some problems after flashing. When tapping button combo's my device didn't even do anything anymore, no leds, nothing. In usb ports, all faulty description...
Had to drain battery overnight.
Once you tap power and you'll notice a single blinking light, the phone is drained. By then, hold the 3 buttons and put the phone into EDL again and connect to pc like you did before. It'll work.
Do the procedure right over again and hopefully this time it'll work. For me it was.
I haven't had these problems before but I do sense some latest updates have made it harder to EDL right in W10....don't know for sure but there's something changed....
I also remember I had downloaded the EDL Tool again. Perhaps @djkuz has updated the tool ??
Same happened to me yesterday. There was no way to exit EDL. After emptying the battery over night I was able to use MiFlash to fix my phone.

I guess my EDL session expired and for some reason EDL itself did no longer react to any pushed buttons on the phone.

It then came into my mind that I used an USB3.0 instead of an USB2.0 port which lead to issues in the past last time when I tried to fix the buttons to access EDL.

My phone does not get into EDL mode. I pressed all three buttons (Vol up + Vol down+ power) and nothing happens. Can anyone help. It can into FTM and recovery but not EDL. Any one can help? Thanks.
I am on stock Oreo :ZTE_A2017V3.0.0B19 (Chinese version).
Take a look at this: https://forum.xda-developers.com/axon-7/help/restore-edl-functionality-a2017g-t3850458
For as long as you have access to adb you should be able to "adb reboot edl" from either TWRP or your current ROM.

After that try to fix EDL (to be able to use the buttons again) using @djkruz's Axon 7 Tool: https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
 
Last edited:

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
Same happened to me yesterday. There was no way to exit EDL. After emptying the battery over night I was able to use MiFlash to fix my phone.

I guess my EDL session expired and for some reason EDL itself did no longer react to any pushed buttons on the phone.

It then came into my mind that I used an USB3.0 instead of an USB2.0 port which lead to issues in the past last time when I tried to fix the buttons to access EDL.
Yeah I think the 3.0 has/can caused me some troubles too....I'm on a fully new machine and having some troubles (not all the time) when connecting my phones.
It might be even the cause why the EDL mode is stuck after an EDL flash, because on previous EDL flashes I only used 2.0 and never had that issue before. So definitely something to remember to use usb2.0 as a safe way to flash and avoid more trouble.
Anyway, like you said, the only solution afaik, is to drain the battery and when drained, use the button combo to start EDL again.
 

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
@raystef66: This tool detects my phone as a COM modem port instead of COM diag. I have selected the correct port in Ports Manager but the phone still doesnt switch from DFU to EDL. I was previously running LOS15.1 bootstack on a Treble ROM, could that be playing a factor? Any idea what I'm doing wrong? Suggestions?

I currently have Windows 10 and Linux installed, but I am going to try tri-booting with a clean install of Windows 7, since it has been stated that this tool sometimes doesnt work correctly with 10. I am trying to avoid RMAing my phone a 3rd time.

Thanks!
 

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
@raystef66: This tool detects my phone as a COM modem port instead of COM diag. I have selected the correct port in Ports Manager but the phone still doesnt switch from DFU to EDL. I was previously running LOS15.1 bootstack on a Treble ROM, could that be playing a factor? Any idea what I'm doing wrong? Suggestions?

I currently have Windows 10 and Linux installed, but I am going to try tri-booting with a clean install of Windows 7, since it has been stated that this tool sometimes doesnt work correctly with 10. I am trying to avoid RMAing my phone a 3rd time.

Thanks!
I've tested the tool under W7 and W10 and it's doing the job correctly.
The only thing I encountered once on W10 was the EDL Tool not working properly to flash the EDL roms. And I got stuck in EDL mode. Only way was to drain the battery and doing the job over with the EDL Tool and all went ok.
But as said I never had problems with the DFU tool under W7 or W10. And shown as COM(diag). Never on modem....and no experience with that to be honest.

Btw, when you power off phone and hold the 3 buttons and connect to phone, what do you see in ports/lpt ? Is it just displayed as modem ? Remove drivers and let it reinstall automaticly. Have you installed the proper Qualcomm drivers ?
Main thing is to have those Qualcomm drivers displayed under COM&LPT, otherwise it won't work flashing EDL's.
 

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
@raystef66: Which Qualcomm drivers do you recommend? Im using the driver from @jcadduono's EDL thread in the dev section. i am going to try for most of the night to fix this, if not done by noon then I am going to ship the phone. ZTE already emailed me a FedEx shipping label but if i can get it unbricked then great.

Thanks!

I had previously been using your crDroid Treble ROM with Schwifty kernel for a day, but battery drain is too high. Great job anyway, but I guess Treble just isnt for me. I was trying to EDL back to B15 N.
 
Last edited:

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
@raystef66: Which Qualcomm drivers do you recommend? Im using the driver from @jcadduono's EDL thread in the dev section. i am going to try for most of the night to fix this, if not done by noon then I am going to ship the phone. ZTE already emailed me a FedEx shipping label but if i can get it unbricked then great.

Thanks!

I had previously been using your crDroid Treble ROM with Schwifty kernel for a day, but battery drain is too high. Great job anyway, but I guess Treble just isnt for me. I was trying to EDL back to B15 N.
Those Qualcomm driver you mentioned are ok. Or use this one : https://www.androidbrick.com/downlo...mm-diag-qd-loader-windows-10-drivers-signed/#
Or : https://androidfilehost.com/?fid=745425885120754986

I uploaded the onces I use : A2017 Drivers
Just extract - there are 2 files in there

The crDroid has a fairly good battery stat. I'm running on it as my DD. Thnx for mentioning it !
 
Last edited:

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
@raystef66: The drivers you personally are exactly identical to what @jcadduono provided. So it's not a driver issue, maybe.

I was able to install 7 into a partition and it booted, but no luck. I have a 2017 Sager gaming laptop thst has 5 USB 3.0 ports, and 2 usb c ports, but no 2.0 ports at all. In short, 7 couldnt detect any USB devices I plugged in, I guess my PC is just too new.

So, I'm trying Windows 10 in a virtual machine.
 

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
@raystef66: You are an 11th hour savior! Your last post provided the file I needed to go from DFU to EDL (your link to A2017 Drivers that you use), it seems that the Qualcomm USB driver *and* the ZTE Handset USB driver did the trick. I didnt have this last driver installed, only the EDL drivers, MiFlash, and the MultiDL tool.

However, there is some confusing and unclear info in this thread, later today I will post a concise guide detailing what files are needed, the install order, and how-to. I tested on a clean-installed Windows 10 Enterprise in a virtual machine, because I was sure that my real 10 install must have some conflicting files/drivers/etc that were preventing the MultiDL tool from working. So I believe my steps will be accurate and reproducable for most.

In regards to your crDroid build, it has a system image, vendor image, and boot image, and those happen to be what Treble requires. Your vendor.img/boot.img can also boot GSIs (I tested with Phh Treble 8.x and RR Official Treble 8.x). So I dont understand when you say that your crDroid build is a non-Treble ROM, yet it has all the characteristics of a Treble ROM (except that your system image will only boot on an A7, whereas a GSI is generic and designed for many Treble compatible devices).

I'm not gay but here's a virtual bro hug as thanks!
 
Last edited:

raystef66

Recognized Developer / Recognized Contributor
Jul 2, 2013
2,050
4,975
203
@raystef66: You are an 11th hour savior! Your last post provided the file I needed to go from DFU to EDL (your link to A2017 Drivers that you use), it seems that the Qualcomm USB driver *and* the ZTE Handset USB driver did the trick. I didnt have this last driver installed, only the EDL drivers, MiFlash, and the MultiDL tool.

However, there is some confusing and unclear info in this thread, later today I will post a concise guide detailing what files are needed, the install order, and how-to. I tested on a clean-installed Windows 10 Enterprise in a virtual machine, because I was sure that my real 10 install must have some conflicting files/drivers/etc that were preventing the MultiDL tool from working. So I believe my steps will be accurate and reproducable for most.

In regards to your crDroid build, it has a system image, vendor image, and boot image, and those happen to be what Treble requires. Your vendor.img/boot.img can also boot GSIs (I tested with Phh Treble 8.x and RR Official Treble 8.x). So I dont understand when you say that your crDroid build is a non-Treble ROM, yet it has all the characteristics of a Treble ROM (except that your system image will only boot on an A7, whereas a GSI is generic and designed for many Treble compatible devices).

I'm not gay but here's a virtual bro hug as thanks!
NIce to see you got it working with those 2 driver files.
Regarding crDroid, confused myself as I've been working now on a non-treble one, the B03 SL!M7 ;), ofc crDroid can indeed be flashed on treble phones . And it's indeed fully customed for A7.

Anyway, good to see you've a working phone again ;)
 
Last edited:

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
I didnt have enough time yesterday to post my steps, but here they are anyway:

Download these files before starting:
1. ZTE handset USB driver and Qualcomm EDL 9008/USB driver (https://androidfilehost.com/?fid=11410963190603913612
2. Latest version of the MultiDL Tool (https://androidfilehost.com/?fid=11410932744536984126
3. MiFlash (may not be the latest version but it has always worked for me, https://build.nethunter.com/misc/axon7/MiFlashSetup.msi
4. Axon 7 EDL Tool (optional, but sometimes works better than MiFlash and has more features, refer to the forum thread for details on how to use it, https://forum.xda-developers.com/attachment.php?attachmentid=4682066&d=1546889147

For a clean start, uninstall the DFU MultiDL Tool and MiFlash from Windows Control Panel. Open Device Management (search for devmgmt.msc from start menu, or hit Windows key+R, type it in, press Enter). Enable the viewing of hidden devices, open every category and uninstall every driver that mentions ZTE, Qualcomm 9008 (not exact wording but it will be obvious). Be especially sure to check under the Unknown/Other categories, as well as USB and Ports categories. If a checkbox appears asking to remove the driver, click it, then OK.

I'm not sure if the next step is absolutely necessary, but I sometimes didnt get driver install prompts if DSE is enabled. Modern Windows 64 bit OSes since Vista have Driver Signature Enforcement enabled by default, which can prevent a driver from installing. All provided driver files should be signed but it's better to get this right the first time. So:

Open a command prompt as admin (type cmd in Start menu, right click, run as admin), type the following, reboot again:

bcdedit /set TESTSIGNING ON

Afer you have rebooted you will notice a watermark in the lower left of your desktop. It is insecure to run Windows with DSE always off, so when done with all my steps you should type the above command again, but change ON to OFF and reboot.

Next steps:
1. Extract @raystef66's A2017G_Driver.zip, it says G but it will work on A2017/A2017U models too.

2. In the extracted Windows folder, run Autorun.exe as admin (ZTE Handset driver).

3. In the other extracted folder you will find 3 files ending in inf, right click each of them and click Install. Dont worry about the other subfolders. This is the Qualcomm EDL 9008 EDL/USB driver.

4. Install MiFlash

5. Install ZTE MultiDL Tool.

Do the above steps *IN THE ORDER* I have listed them. And dont plug phone into PC until you have done all the steps.

Now you are ready to use the DFU MultiDL Tool. Use the pics here as a visual reference (https://forum.xda-developers.com/showpost.php?p=77926571&postcount=35

Now, make sure phone is off. Hold volume up, volume down, then power in that order, but keep all buttons held down. You should feel a vibration, maybe not. If you see a solid red light/LED in upper left corner of phone screen, this is DFU mode. Red light that either blinks or turns off is EDL, you can just skip the DFU MultiDL tool and go straight to flashing with MiFlash or A7 EDL Tool. You can also use Device Management as an indicator for which mode the phone is in.

Plug in device to PC, open the DFU tool. Find the Port Config button, then click Port Manager. If your phone isnt listed as a COM diag port then this probably wont work. Under the line where the COM button is listed, remember the USB number. Close Port Manager, click line 1, then select the USB number you saw. Then click OK. You should hear a USB disconnect sound on PC, and the red light should turn off. This means you are in EDL mode (or should be). Close the DFU tool and open either MiFlash or the EDL Tool batch file and flash. Be sure not to have more than one of these programs open at once, since they may be in conflict by trying to access the phone simultaneously. While EDL flashing or or using the EDL tool, open the Task Manager and kill any adb.exe processes. The EDL Tool can use ADB to switch to EDL, but it but it shouldnt be running during the actual flashing process.

Now you can flash with the other tools I listed (preferably a full stock ROM EDL zip of your choice for a fresh start, then you can bootloader unlock, flash TWRP/custom ROM/etc later). If MiFlash gives an error, or the EDL Tool gets stuck on loading the firehose file then you are probably not in EDL. Try disconnecting/reconnecting phone to PC. If that doesnt work then do the steps with the DFU Tool again. If still not working then you can put the phone in DFU mode and let the red light drain the battery completely. Then charge for a few mins (at a minumum, battery charging screen may not appear, just use your judgement). This may take hours depending on how much charge the phone has. Bottom line is you must get to EDL or you're going nowhere fast.

Once you are in EDL then you can flash with the normal tools and unbrick. DFU MultiDL Tool can also EDL flash files to the device, but I have never gotten it to work (didnt try too hard). A user has earlier mentioned that running the tool in Windows 7 compatibility mode may allow EDL flashing to function properly, if you are using Win8/8.1/10. I will test more later but for now just use the other tools.

Another thing, be sure to run all tools/installers as admin. Use a good cable. And use a USB 2.0 port if available (not an option for me since my laptop has only USB3/USB C).

If you still cant get these steps to work in a real Windows install, it is possible there are deeper conflicts somewhere (usually installed drivers/programs) then you can try installing Win10 64 bit in a VMware Workstation (paid software but has 30 day trial)/VirtualBox (free) virtual machine. Then do my steps. Win7 will also work (not recommended if you have USB3 ports and no USB2). In the VM program you can share (pass through) a USB port from the host OS to the guest OS, set config to either USB2 or USB3 in VMware/VirtualBox, depending on your PC. Microsoft hosts free trial downloads of Windows which dont need to be activated immediately, those will suffice, so no need to pay or pirate. I use Linux as my main OS, I find VMs to be useful for flashing phones.

Absolute worst case is that none of this works, then you can either dissassemble the phone and short circuit the test point using @Choose an username...'s DFU unbrick guide (never did this myself, dont want to damage phone). Or you can RMA the phone to ZTE if the warranty is still valid. I have RMAed to them twice in a year and dont want to do it again so I'm posting this guide in the hope that someone will find it useful. And because I feel that the steps listed by others are incomplete, dont list and give links to all required tools, or provide a proper step order to follow.
@raystef66: If you find this post useful then maybe you can link to it in the first post as a starter reference.
 

cercelcremene

Senior Member
May 19, 2014
105
16
18
Kure
Thank you! It worked from the very first moment, then I got some problems because I tried to flash an EDL backup made with OKI's TWRP. I finally managed to get it back to the Nougat system found on the Internet. Now I got again to AEX 5.8. Thank you again!
 
Last edited:
  • Like
Reactions: raystef66