[GUIDE] EASY Axon 7 UNIVERSAL UNBRICK / FACTORY RESTORE

[raystef66]

Hmm, it sounds weird but I think this guide wrecked my Axon 7 now. I may be wrong but here is what happened:

I tried to return to stock from LOS 15.1 with vendor partition. So I removed the vendor partition with @Oki party tool, wiped data, system, cache and dalvik and finally tried to go back to stock with @raystef66 s files. Firstly I flashed the bootstack of B10 for A2017G and rigth after that the corresponding stocksystem. When I rebooted the device, a red warning message appeared saying my device is corrupt. It wouldn't boot to the OS or to recovery, I was just able to access fastboot mode. After switching drivers, the device was recognized as a fastboot device and I could flash TWRP. After that, the devices successfully booted into TWRP again and was recognized as an adb device. From there I was able to boot into EDL mode in which the device was recognized as Qualcomm HSB. I did steps 1 and 3 of this guide and Miflash flashed the files (B12 Nougat files from here) successfully.

After the flash, the device didn't reboot straight away, so I had to reboot it manually. But now, the device shows the ZTE powered by Android logo but after that, it shows a "dead" android with the text "no command" at the bottom. Then the screen stays black and doesn't do a thing. I neither can boot to recovery, nor fastboot mode. I can hit the EDL mode button combination but it's recognized as a DFU device. Interestingly though, when I hit that combination earlier when the device was "corrupt", I got the same message, but I was able to recover the device.

But now, I can't do anything with it. It just stays black. I can reboot it and reboot it to said "EDL Mode" but thats about it.

I'd be thankful for any advice other then disassemble the devices or return it to ZTE.

Try this - doesnt harm a thing - power off phone if possible, hold vol-&power for a 5 sec and it could show FTM mode (like it once did on my device). If so - and drivers are all installed ok - you should be able to 'adb reboot edl' . After that EDL the B12-G etc...

 

[OberstGrausam]

Try this - doesnt harm a thing - power off phone if possible, hold vol-&power for a 5 sec and it could show FTM mode (like it once did on my device). If so - and drivers are all installed ok - you should be able to 'adb reboot edl' . After that EDL the B12-G etc...

I appreciate your help, unfortunately I doesn't seem to work. The issue is, I can't really power off the device anymore. After the screen goes black, I can only force reboot by pressing the power button for a certain amount of time. Even when I try to enter recovery or FTM/Fastboot mode with the respective button combination, the phone boots up "normally", shows the ZTE logo and then the "dead" android for a splitsecond.

 

[raystef66]

I appreciate your help, unfortunately I doesn't seem to work. The issue is, I can't really power off the device anymore. After the screen goes black, I can only force reboot by pressing the power button for a certain amount of time. Even when I try to enter recovery or FTM/Fastboot mode with the respective button combination, the phone boots up "normally", shows the ZTE logo and then the "dead" android for a splitsecond.

Have you done the FTM mode procedure when hooked on PC ?
Have you tried to drain the battery first and do the steps again ?
Did you check - just a small chance though - if adb isnt just working by default ?
Also take a look in here : https://forum.xda-developers.com/showpost.php?p=77724019&postcount=5
What's your hardwareID showing when connected ?
Did you try playing with the vol+, vol- when 'rebooting' - triple button combo ?

Good advice : try everything and not only once

 

[joaste]

Hello oki,

So I followed the video to make a cable myself (so just shorting one of the connectors). MiFlash now sees my A2017G, but only when it is in fastboot mode. However, I'm unable to flash anything. I always get the same message: "can not found file_flashall.bat"

Some background info:
I was on AEX treble
I removed the vendor partition, wiped system, cache, data,etc.
Flashed the recent B12 slim files (bootstack, system)
Rebooted to system
The ROM booted, but I got a screen saying that decryption failed (NOTE: My phone was not encrypted) and asked for a password. I enter my usual PIN, and it says that the PIN is correct, but that decryption failed, and asks to do a reset.
I click the button to do a reset
The phone reboots to the famous "your phone cannot be verified" screen, where you can use the volume buttons to select reboot, recovery, fastboot, etc...
Selecting recovery just makes the phone reboot to the same screen.

When in the fastboot menu, if I select "Boot to FFBM", the phone boots into the ROM (so I get the stock boot images), but ends up on the same screen saying that decryption failed and asking for a reset.

Any ideas on how I can get out of this?

Pressing the vol-, vol+, power buttons brings to a constant red LED and the phone is recognized as being in DFU mode.

Thanks in advance for any help you can provide.

PS: it's a good thing I kept my LG G3 around lol

EDIT: adb does not list the device when executing adb devices, even when MiFlash sees the phone (whih it only does when it is in fastboot mode, as mentioned above)
EDIT 2: since I was never able to get into the system, USB Debugging is not on.

 

[OberstGrausam]

Have you done the FTM mode procedure when hooked on PC ?
Have you tried to drain the battery first and do the steps again ?
Did you check - just a small chance though - if adb isnt just working by default ?
Also take a look in here : https://forum.xda-developers.com/showpost.php?p=77724019&postcount=5
What's your hardwareID showing when connected ?
Did you try playing with the vol+, vol- when 'rebooting' - triple button combo ?

Good advice : try everything and not only once

Yes, I tried to enter FTM mode while the device was hooked to my pc, multiple times. But no luck. It is only recognized when in this "kinda" EDL mode i.e. I press both volume buttons + power button until the red light flashes. It is recognized as either DFU (USB\VID_19D2&PID_0112) or due to the drivers I've installed QUSB-BULK (under USB devices). No matter which driver I choose, neither adb nor fastboot would see the device, thus the list of devices stays empty. When I reboot the device regularly, it's not detected and thus neither adb nor fastboot works.

As for draining the battery, I haven't done that yet but it's definitly on my to do list.

What do you mean exactly with "Did you try playing with the vol+, vol- when 'rebooting' - triple button combo"? By holding down both volume buttons + power button, I'm able to enter this "kinda" EDL mode with the permanently flashing red light. As mentioned above, the device is recognzied by my pc but I can't do anything with it.

---------- Post added at 06:28 PM ---------- Previous post was at 06:19 PM ----------

Hello oki,

So I followed the video to make a cable myself (so just shorting one of the connectors). MiFlash now sees my A2017G, but only when it is in fastboot mode. However, I'm unable to flash anything. I always get the same message: "can not found file_flashall.bat"

Some background info:
I was on AEX treble
I removed the vendor partition, wiped system, cache, data,etc.
Flashed the recent B12 slim files (bootstack, system)
Rebooted to system
The ROM booted, but I got a screen saying that decryption failed (NOTE: My phone was not encrypted) and asked for a password. I enter my usual PIN, and it says that the PIN is correct, but that decryption failed, and asks to do a reset.
I click the button to do a reset
The phone reboots to the famous "your phone cannot be verified" screen, where you can use the volume buttons to select reboot, recovery, fastboot, etc...
Selecting recovery just makes the phone reboot to the same screen.

When in the fastboot menu, if I select "Boot to FFBM", the phone boots into the ROM (so I get the stock boot images), but ends up on the same screen saying that decryption failed and asking for a reset.

Any ideas on how I can get out of this?

Pressing the vol-, vol+, power buttons brings to a constant red LED and the phone is recognized as being in DFU mode.

Thanks in advance for any help you can provide.

PS: it's a good thing I kept my LG G3 around lol

EDIT: adb does not list the device when executing adb devices, even when MiFlash sees the phone (whih it only does when it is in fastboot mode, as mentioned above)
EDIT 2: since I was never able to get into the system, USB Debugging is not on.

I was in the same situation as you are now, just some hours ago. I got out of it by booting the phone into fastboot mode and then connecting it to my pc. I played around with the drivers until the device was found via cmd.exe and fastboot devices. From there I flashed the most recent recovery again (one without the vendor partition ofc(fastboot flash recovery recovery.img (I renamed the TWRP image to recovery.img))). Then I was able to fastboot reboot recovery and enter TWRP normally again. In case it doesn't work and the "your device is corrupt" screen pops up, press the power button once. That worked for me as well. While in TWRP the device was found by adb and I was able to reboot it to edl mode with adb reboot edl. HOWEVER, flashing the latest B12 FULL EDL package via miflash (I applied the steps of this guide) wrecked my device, eventhough the flash process was successful.

 

[joaste]

I was in the same situation as you are now, just some hours ago. I got out of it by booting the phone into fastboot mode and then connecting it to my pc. I played around with the drivers until the device was found via cmd.exe and fastboot devices. From there I flashed the most recent recovery again (one without the vendor partition ofc(fastboot flash recovery recovery.img (I renamed the TWRP image to recovery.img))). Then I was able to fastboot reboot recovery and enter TWRP normally again. In case it doesn't work and the "your device is corrupt" screen pops up, press the power button once. That worked for me as well. While in TWRP the device was found by adb and I was able to reboot it to edl mode with adb reboot edl. HOWEVER, flashing the latest B12 FULL EDL package via miflash (I applied the steps of this guide) wrecked my device, eventhough the flash process was successful.

Thank you so much!!
MiFlash is currently flashing the full B10 EDL file.

I hope you find a solution to your current situation.

 

[janthe6th]

Hi @Oki. I was on latest DU and wanted to try out LOS 15.1 and used your guide but couldn't get it to work. Got google framework stopped working error at initial google set up. I tried to go back to DU but got same error.
I then tried your guide on this to go back to stock but after I flash the zip, tried to go to recovery mode by volup + power but the zte logo showed up and miui flashed for a split second then phone go back to black. Now holding power button alone will not turn on phone.
I can't enter DFU mode by holding volup+voldown+power (screen stay black, led light red but when I connect to computer miflash doesn't recognize the phone. Ever since before I tried all this flashing, I have only been able to enter EDL by a terminal app or your twrp edl reboot)
volup+power & voldown+power only have zte logo then miui flashed for a split second

What should I do from here?

 

[Voenix]

Hmm, it sounds weird but I think this guide wrecked my Axon 7 now. I may be wrong but here is what happened:

I tried to return to stock from LOS 15.1 with vendor partition. So I removed the vendor partition with @Oki party tool, wiped data, system, cache and dalvik and finally tried to go back to stock with @raystef66 s files. Firstly I flashed the bootstack of B10 for A2017G and rigth after that the corresponding stocksystem. When I rebooted the device, a red warning message appeared saying my device is corrupt. It wouldn't boot to the OS or to recovery, I was just able to access fastboot mode. After switching drivers, the device was recognized as a fastboot device and I could flash TWRP. After that, the devices successfully booted into TWRP again and was recognized as an adb device. From there I was able to boot into EDL mode in which the device was recognized as Qualcomm HSB. I did steps 1 and 3 of this guide and Miflash flashed the files (B12 Nougat files from here) successfully.

After the flash, the device didn't reboot straight away, so I had to reboot it manually. But now, the device shows the ZTE powered by Android logo but after that, it shows a "dead" android with the text "no command" at the bottom. Then the screen stays black and doesn't do a thing. I neither can boot to recovery, nor fastboot mode. I can hit the EDL mode button combination but it's recognized as a DFU device. Interestingly though, when I hit that combination earlier when the device was "corrupt", I got the same message, but I was able to recover the device.

But now, I can't do anything with it. It just stays black. I can reboot it and reboot it to said "EDL Mode" but thats about it.

I'd be thankful for any advice other then disassemble the devices or return it to ZTE.

I bricked my phone too with the party tool. It did corrupt the system partition. You need to install twrp and see if the system and the data partition has storage.

Unfortunaly I cant flash anything because the EDL mode hangs keeps flashing without progress and I just have access to a recovery without usb debugging enabled.
Maybe I need to send it to ZTE too

 

[EBeatFLA]

I bricked my phone too with the party tool. It did corrupt the system partition. You need to install twrp and see if the system and the data partition has storage.

Unfortunaly I cant flash anything because the EDL mode hangs keeps flashing without progress and I just have access to a recovery without usb debugging enabled.
Maybe I need to send it to ZTE too

The disassembly is quite easy. If you have had any experience working on computers, or taking apart any small electronic device, you'll be fine.
I was afraid of opening it up too. I've only ever opened one phone before and it didn't go well, leaving visible marks on the outside and a bent battery on the inside. The Axon 7 was way easier, by far.
You will need to use a razor and a guitar pick, as shown in the disassembly video. Then once those speaker covers are lifted the rest is cake. Just be careful not to smear the pink thermal paste, it's very soft and will move easy. Also be very patient and gentle when removing the battery (which i also recommend doing, just like the guide).

 

[OberstGrausam]

I bricked my phone too with the party tool. It did corrupt the system partition. You need to install twrp and see if the system and the data partition has storage.

Unfortunaly I cant flash anything because the EDL mode hangs keeps flashing without progress and I just have access to a recovery without usb debugging enabled.
Maybe I need to send it to ZTE too

I wouldn't necessarily say, that the party tool is to blame here. It may have been another file in the mix, since @joaste apparently managed to return to stock with the B10 EDL package, while using B12 EDL bricked my phone. I was lucky that I switched phones before I bricked it. The options you mentioned wouldn't have worked anyway, because I wasn't able to access neither EDL nor fastboot or recovery. I ended up sending it in for repair, which may turn out well, since the flash of stock B12 EDL removed any signs of custom firmware on my device.

 

[whatsupgamboys]

Used Party v0.5 prior to installation of LOS from stock and bricked my A2017U. I had unlocked the bootloader and installed TWRP with the toolkit, installed Oreo bootstack and modem as recommended by the LOS thread, flashed Party with latest TWRP and then my phone went to hell. Loads to bootloader and can only get to fastboot now.

Tried installing TWRP via fastboot but when I choose recovery, it restarts the phone. When I go into EDL mode and connect to my computer, device manager lists the phone as "Handset Diagnostic Interface(DFU)" so I think I'm screwed. Would going the EDL cable route as listed in OP even be an option or would I have to go straight into 4th category brick repair?

Much appreciated.

EDIT: Fixed with this method.

 

[emeres]

Would this work if my device works but all I want to do is get rid off TWRP and lock the bootloader?

 

[KennyKusanagi]

I need help. I've purchased the EDL cable like the instructions say but It's not putting the phone in edl mode

 

[lilbluemirage]

I need help. I've purchased the EDL cable like the instructions say but It's not putting the phone in edl mode

Have you tried this: https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

This method doesn't require a EDL cable.

 

[KennyKusanagi]

Have you tried this: https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

This method doesn't require a EDL cable.

I just did, it worked...I just wasted money on a EDL cable

 

[wroclawiak]

i, m losing hope....

i tried to flash lineage 15.1 and something goes wrong...
I got no os, can not go to TWRP and EDL
i tried 4 USB cables, 4 PC (win7.32, win.8.1.64, win10.64)
I bought deep flash cable and I made other DFC by a hand
and nothing helps

my PC can not see axon7...drivers wrong? or what?

my phone boot to info
tell me what I do wrong....please

my phone boot to screen
"If no keys detected Your device will boot i 5 seconds"

i can choose
Power off
restart
recovery
fastboot
back to previous page


When i choose RECOVERY it stucks with black screen

when choose FASTBOOT
I have options:
start
restart bootloader
recovery mode
power off
boot to FFBM

bootloader unlocked

Whatever I choose - my PC can't see axon7...

PC can't see DFU nor EDL...

fastboot devices - nothing...
ADB devices - nothing...

 

[vahid-749]

i, m losing hope....

i tried to flash lineage 15.1 and something goes wrong...
I got no os, can not go to TWRP and EDL
i tried 4 USB cables, 4 PC (win7.32, win.8.1.64, win10.64)
I bought dee...
ADB devices - nothing...

my situation is exactly the same, please someone help

 

[juniorD]

DO NOT BUY A CABLE OR OPEN YOUR DEVICE!!!

Go here https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

TOTALLY WORKED AND I DIDNT HAVE TO OPEN MY PHONE OR BUY AN EDL CABLE!! Follow the setup carefully as the instructions arent perfect but I managed and BOOM! Phone booted from DFU to Qualcomm and MiFlash flashed with ease and my phone is totally working. Before I could only get it to boot to fastboot mode and thats it.

The DFU Tool totally works!! Im so happy!! I had ordered an EDL cable and had to wait a week for it to reach. Found this tool and followed all the steps and my phone is back!!

 

[samo_lego]

Hi guys! I have succesfully bricked my Axon 7 ... just joking, it's really bricked. It was a normal day, I tried to update the GSI via Oki's recovery and when I tried to erase vendor recovery rebooted. It was strange but I didn't pay attention. But then it happened again. So I have reflashed the recovery, everything was normal. I flashed vendor and GSI, then Gapps and rebooted. System didn't boot, I should have flashed it without gapps first time I guess. So I have reflashed everything again. This time without gapps. System booted up, I rebooted recovery and made a backup. Thenn flashed gapps and Magisk. System didn't boot up so I thought I would just restore the backup and flash just the gapps without magisk. System started booting and ... it bootlooped. I thought I would flash everything from the beginning. Tried to reboot recovery, the logo of recovery showed and then it shut down. No problem I thought and I rebooted the recovery again. The logo then just blinked and the phone turned off (I had 60% of battery). I did it for the third tiime. Recovery didn't boot. Phone was black ... I am able to boot in EDL - the miFlash recognizes it and under the device manager it shows up as qualcomm qdloader. I tried to flash the stock file (I have A2017G,, downloaded that file) and it flashed. But phone was just as before. I have done it again. Same. Any ideas?

BTW, some strange things werre happening after the mi flash, phone has showed the splash screen but then turned off ...

EDIT: now, after third try, if I press volup and pwr for ~10 seconds, phone shows ZTE logo and then starts recovery (I just assume), because I can see the mini android laying on ground, however, it tuns of again - as with previous TWRP.

 

[EBeatFLA]

Hi guys! I have succesfully bricked my Axon 7 ... just joking, it's really bricked. It was a normal day, I tried to update the GSI via Oki's recovery and when I tried to erase vendor recovery rebooted. It was strange but I didn't pay attention. But then it happened again. So I have reflashed the recovery, everything was normal. I flashed vendor and GSI, then Gapps and rebooted. System didn't boot, I should have flashed it without gapps first time I guess. So I have reflashed everything again. This time without gapps. System booted up, I rebooted recovery and made a backup. Thenn flashed gapps and Magisk. System didn't boot up so I thought I would just restore the backup and flash just the gapps without magisk. System started booting and ... it bootlooped. I thought I would flash everything from the beginning. Tried to reboot recovery, the logo of recovery showed and then it shut down. No problem I thought and I rebooted the recovery again. The logo then just blinked and the phone turned off (I had 60% of battery). I did it for the third tiime. Recovery didn't boot. Phone was black ... I am able to boot in EDL - the miFlash recognizes it and under the device manager it shows up as qualcomm qdloader. I tried to flash the stock file (I have A2017G,, downloaded that file) and it flashed. But phone was just as before. I have done it again. Same. Any ideas?

BTW, some strange things werre happening after the mi flash, phone has showed the splash screen but then turned off ...

EDIT: now, after third try, if I press volup and pwr for ~10 seconds, phone shows ZTE logo and then starts recovery (I just assume), because I can see the mini android laying on ground, however, it tuns of again - as with previous TWRP.

I've had similar issue trying to EDL back to stock. Just EDL Okis LOS 15.1 EDL package, and you should be able to use his TWRP to get back to a normal state.
You might have to fool around with formatting Data, as your phone will probably think it needs encryption, but I got through it after a few tries.