Database Users

[GUIDE] [UNBRICK] Unbrick Oneplus One

*** I've been receiving many requests and PMs from members asking to help them unbrick their device. Please note that I no longer own this device (and even if I did I would not purposely brick it just to reproduce your problem), therefore I am unable to help out beyond this tutorial. ***
Hello,
First some background and credits:
There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.
This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.
Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.
***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.
If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...
1:
Download Color.zip from (mirror needed).
After downloading, unzip the archive on your computer.
2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.
So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then:
2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: (mirror needed).
Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.
3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.
Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?

mysterio619 said:
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
Click to expand...
Click to collapse
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.

netbuzz said:
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.
Click to expand...
Click to collapse
Tried it......still no imei

mysterio619 said:
Tried it......still no imei
Click to expand...
Click to collapse
Just to give one last try, flash color os modded zip from relic, i used 2.0.43 purezip and it gave me back my imei. Had the same issue as you last week. Be sure to flash TWRP 2.8.4.1 first and then flash color os.

Legit method.
Worked for me 2 weeks ago!

unbrick oneplus one, oppo 7
Hi there my friend, i had many works about unbricking solutions, a few of you know that, i have much easier and faster ways now, tested many times before i decided to share with you, it will be a long topic ( and my brain is messed up to sum them up clearly), as soon i can think clearly again, i start to write them, till then,
greetings from Istanbul to all geeks around thw world.
Ps: including restoring imei's if they got lost during this process.
Ps2: just a quick info abou imei, if your imei is "invalid" , this means your modem.bin (NON-HLOS.bin, baseband) is not inadaptable with your rom, just try flashing the right modem ( from fastboot), your imei will be back.
Ps3 : This will lead us to unbrick many Snapdragon's out there , not only oneplus one's or oppo's.

I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.

michaeldepotter said:
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
Click to expand...
Click to collapse
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!

nag4pl said:
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
Click to expand...
Click to collapse
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app

michaeldepotter said:
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you.. Troubleshooting my phone now..

may i ?
http://www.androidbrick.com/?wpdmdl=2599

Back from Brick!!
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!

nag4pl said:
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
Click to expand...
Click to collapse
Thanks for this Win7/8 workaround. I'll be adding your info to the OP.

Finally Unbricked mine...Drivers resolved on Win 7
netbuzz said:
Second note about drivers is that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations by default. I've tried overwriting these settings in Windows and spent half a day messing with it, and I never got things to work properly. At first all looked good to go, but then latter steps were failing. You might have a better luck getting drivers to work on Windows 7 or 8 (I've heard some people did it), but if you have access to a Windows XP or 2003 machine, try it first, it should save you some major headache.
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Click to expand...
Click to collapse
I have used the override tool for certificates: DSEO - Driver signature enforcement overrider
to allow the unsigned drivers to be used and it worked like charm on windows 7 64 bit.
Also, I used the additional Qualcomm 2012 drivers and not sure which one might got picked in that mess :cyclops::cyclops:
Thanks!!
:good::good::angel::angel:

nevermind!

Well I managed to hardbrick my phone. I am download the ColorOS file from Mega at the moment. It's downloading at 30KB/s and will take around 6.5 hours. Is there any other source to download it from ? Thanks !
Also, about the driver ...
While I wait on the colorOS to download I want to clarify one more thing about the driver.
According to the screenshot of @nag4pl the driver should show as Qualcomm USB diagnostic 9006, while for me it shows as Qualcomm HS-USB QDloader 9008. Is this going to be an issue ?
This is what I did. I uninstalled the default driver that came with windows 7. After that it failed to install the driver provided in this forum because it kept saying that device descriptor failed. I rebooted the phone several times and changed the USB ports and eventually windows detected it but AGAIN with the windows driver even though I had checked the option to delete the original driver while uninstalling it. Through the update driver option I managed to force it to install the unsigned driver.
Now I can see both the drivers under the update drivers option. Interestingly the default driver is a version ahead of the unsigned driver provided in this forum.
My only concern is that I see a different driver name compared to the one posted by @nag4pl

Thanks! Very useful for me!

That shouldn't be a problem. Not sure if that is specific to region, mine is India version phone.. Can some one clarify on this?

[Solved] A2017G totally Bricked

First of all, i live in Bangladesh. I asked a relative of mine who lives in Sweden to buy me this phone. So, there is no way for me to send this phone back to ZTE.
Now let me explain how i got into this huge mess. I installed twrp successfully using this post - https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
i only followed part A of this post. Then i needed to root. so i tried to flash supersu 2.79 first but failed. Then i tried to flash supersu 2.65 as someone commented that they failed with 2.79 but succeeded with 2.65. However, after flashing supersu 2.65 i soft bricked my phone. i could still access twrp 3.0.2. After a while, i downloaded b08 update.zip and tried to flash it through twrp but failed. then i saw this post - https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
and this post - https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And tried to update twrp to 3.03. which then hard bricked my phone. now i cannot access anything. when i try to start my phone it shows the zte logo for a second and the whole screen goes blank with the red led.
same thing happens with volume up+power and volume down+power. And there is no way to turn the phone off. So, i waited a whole day for the phone to empty it's battery and tried to boot to edl mode using volume up+down but Qualcomm HS-USB QDLoader does not appear. The only thing i can get to connecting to my computer is handset diagnostic interface.
Now only a brilliant dev can help me. So can someone PLEASE Help me.
Also i've found this post is very similar to my problem https://forum.xda-developers.com/axon-7/help/bricked-a2017g-b03-help-please-t3487635
Update: Fixed using this post >> https://forum.xda-developers.com/ax...ory-brick-repair-manual-t3585898#post71764940
& this >> http://4pda.ru/forum/index.php?showtopic=814221&st=0#entry60102671

Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...

Abiram26 said:
Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...
Click to expand...
Click to collapse
yes i have. but in the device manager, instead of Qualcomm HS-USB QDLoader, Handset Diagnostic Interface appears.
Furthermore, computers does not recognize any adb device when i connect my axon 7
what do i do???
Edit: when i uninstall Handset Diagnostic Interface from device manager and then connect my phone with both volume keys pressed, at first qusb_bulk appears but after automatic installation of hardware software it's Handset Diagnostic Interface all over again

Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7

Abiram26 said:
Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7
Click to expand...
Click to collapse
:crying::crying::crying::crying:
if only i could boot into edl mode

I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?

Send me a PM with your Hangouts, let's see if I can help.

Controllerboy said:
I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?
Click to expand...
Click to collapse
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help

nsabir said:
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help
Click to expand...
Click to collapse
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.

Oki said:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Click to expand...
Click to collapse
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??

Oki said:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Click to expand...
Click to collapse
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??

nsabir said:
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
Click to expand...
Click to collapse
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.

Oki said:
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.
Click to expand...
Click to collapse
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only old ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.

nsabir said:
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.
Click to expand...
Click to collapse
Can you boot into the bootloader by pressing the button combination?

Oki said:
Can you boot into the bootloader by pressing the button combination?
Click to expand...
Click to collapse
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G

nsabir said:
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G
Click to expand...
Click to collapse
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/

Altomugriento said:
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/
Click to expand...
Click to collapse
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.

nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
Do you find something useful? I think I find someone in that forum, exactly in your position, all the answers pointing to RMA for the fix, sorry, maybe later can take another look and search for a solution.
Enviado desde mi ZTE A2017U mediante Tapatalk

nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk

Altomugriento said:
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
Thank you for the link. But i tried this miflash tools weeks ago.
Here is the full guide in my opinion for the mi flash tool.
http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Unfortunately, the A2017G does not have 9008 port. It has ZTE's own Handset Diagnostic Interface (DFU) (ComX) for which i need the latest version of ZTE firmware flasher. At the moment only ZTE have this. So, my bricked phone is a lost cause.

[UNBRICK] Xiaomi Mi Max 64/128 GB a.k.a Helium - %100 Tested Recover From Hard Brick

Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.

Different reactions
Hi,
My device could still boot on fastboot mode, and flashes successfully through it on MiFlash Beta. However, the device remains stuck on Mi logo. I've already tested flashing on EDL mode apparently successfully, with the same results. I've flashed TWRP, but the device don't enter recovery mode. What can I do? Any suggestion will be welcome.

benzersizadam said:
Many thanks for this thread, I stuck on my mi max with no reaction at anything, I read more than 100 threads, I tried testpoint, DFC (deep flash cable), click inside usb terminal to pc, windows 8, 7 10, 32 bits, 64 bits, programms like qfil (qpst), flasher tools for other phones and nothing, before with other apps at first second gives me error "can not read from port COM...", and now at least advance to 5 seconds with same error, I need to know it is neccesary too disconnect, remove two plastic cables down where places the battery
Click to expand...
Click to collapse

Working also with Hydrogen. Thanks.

@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!

coffee-turtle said:
@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!
Click to expand...
Click to collapse
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance

SubwayChamp said:
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance
Click to expand...
Click to collapse
Hi @SubwayChamp Everything I did was in the post and video from above in the first post by benz....
His instructions were perfect along with the youtube video. It's tricky, true, but with patience you can go through the steps and get your device running again. I was so glad that @Qulox gave me this link to this thread.
As you go through the steps, if you get stuck, we can try to give you advice.

This works for Hydrogen as well.
Many thanks

I have two dead mi max. One 128gb helium and one 32gb hydrogen.
128gb helium is completely lifeless. No charging led, no vibrations, no fastboot mode. Though i could bring it up to edl mode showing right qualcomm device in device manager. I tried flashing stock rom as mentioned in this guide which rather went successful without giving any error, even while battery connector was removed.
But mobile is still in same lifeless condition. Other than flashing process going through, it didnt make any difference. Dont know whats wrong. Also i didnt have to use two miflash versions as mentioned in steps as flashing process didnt give any error.
32gb hydrogen, boots up in flashboot mode, shows charging led, mi logo even edl model worked without any issue. It even boots up, but gives error of encryption unsuccessful asking me to reset device. I tried factory reseting it. Tried flashing twrp and wiping, formatting data, changing file system to all formats like fat, f2fs, ext1, ext2, ext3, ext4. Tried flashing crdoid and RR based on orea. Nothing working.
With twrp it keeps bootlooping showing mi logo. And with stock rom, recovery shows up encryption error. Followed procedure mentioned in this guide as well.
Is there anything am i missing or can do? Btw, bootloader is locked for both the devices. I could flash twrp referring another guide which suggested to replace stock recovery in rom files/ folder and flashing it like stock rom through miflash tool.

Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .

cobben said:
Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .
Click to expand...
Click to collapse
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....

Hello,
trying with both Helium & Hydrogen. Still on error like say these logs.
log#1
Code:
[0,02 COM7]:[COM7]:start flash.
[0,02 COM7]:received hello packet
[0,02 COM7]:can not found programmer file.
log#2
Code:
[0,00 COM7]:[COM7]:start flash.
[2,03 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[4,56 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,11 COM7]:try to reset status.
[7,13 COM7]:Switch mode back
[7,13 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,14 COM7]:Riferimento a un oggetto non impostato su un'istanza di oggetto.
Hope anyone can help me. What's my wrong following the guide.
Thanks

harpy.eagle said:
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....
Click to expand...
Click to collapse
Hi there.. The link of video & image of test points is not working. Can anybody please share working links

Hi there.. The link of video & image of test points is not working. Can anybody please share working links

rizkhan77 said:
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
Click to expand...
Click to collapse
This is the video of Test Point https://youtu.be/SqcVY8IWkZI

benzersizadam said:
Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.
Click to expand...
Click to collapse
hi, could someone share with me the miflash beta? I can download the rest but I cannot download the beta one.
thanks

Wanted to say thank you was able to recover my mi max 64gb unit.

Softbricked axon 7, need help !

Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !

Dr_Raider said:
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Click to expand...
Click to collapse
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode

Choose an username... said:
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Click to expand...
Click to collapse
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.

Kantastisch said:
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Click to expand...
Click to collapse
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)

Choose an username... said:
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Click to expand...
Click to collapse
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.

Kantastisch said:
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Click to expand...
Click to collapse
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?

I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps

Choose an username... said:
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
Click to expand...
Click to collapse
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps

Kantastisch said:
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Click to expand...
Click to collapse
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash

Choose an username... said:
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Click to expand...
Click to collapse
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...

Kantastisch said:
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Click to expand...
Click to collapse
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).

Choose an username... said:
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Click to expand...
Click to collapse
THANKS SO MUCH , you saved my ass, it flashed without a problem and sorry for bothering you. Bootloader is locked now and it works fine. Thanks again!

Bricked Mi A1 - Qualcom HS-USB Diagnostics 900E

Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?

Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,

To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screwdriver.
I did NOT have success with deep flash cable myself, I had to use testpoint method (and sadly broke my LCD in the process). The deep flash issue might of been because I was in Windows 10 x64 or on a USB3 port. If you do go that route and can't get it working, try with a Windows 7 x86 VM and USB2 passthrough mode before last resort of taking device apart.

Hold power button for 20 sec then volume down and fastboot will apear

1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol

udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)

CosmicDan said:
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
Click to expand...
Click to collapse
Actually I think I got scammed. It is Mi5x sold as MiA1. ****ing chinks! Anyway, I managed to install (Tiffany) on it and now it is booting to boot logo and bootlooping. I can get to fastboot and default (MIUI's) recovery by pressing button combos. But OEM is locked now so I cannot flash TWRP or other ROMs in it. I will have to EDL flash back to that MIA1 ROM to get it unlocked from fastboot. Otherwise MIUI unlocker asks me to link my miui account to this phone by going to settings, which I can't do because it is not booting up.
funny situation.

Bruce666 said:
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Click to expand...
Click to collapse
Facing The same Issue
---------- Post added at 10:42 AM ---------- Previous post was at 10:35 AM ----------
Phone Showing Charging Only
Can't Even Transfer Data
Not Detected on Pc

udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Im sorry, exactly with which ROM did you get to the fastboot?

Press power button for 15 sec
If you feel vibration then you are so lucky

boshell said:
Im sorry, exactly with which ROM did you get to the fastboot?
Click to expand...
Click to collapse
Fastboot rom for Mi5x because the phone is Mi5x.