[GUIDE]Unlock Bootloader Easily

[WesTD]

There are some people who can unlock, some can't.

i'll close thread.

Try format data or flash full edl rom to recover your phone.

 

[bibiii79]

Thanks a lot, worked perfectly !!!
:good:
Cheers!

SOME USERS CAN'T MAKE THIS GUIDE. PLEASE READ ALL POST BEFORE DO THIS GUIDE.

[GUIDE]Unlock Bootloader Easily

Hi all. I will present new and easier method to unlock bootloader. This guide works on all models.

Before begin;

- Be sure backed up your stuffs on internal storage.
- Be sure that using x64 Windows.
- Be sure that your battery is over 50%
- Be sure that Disable Driver Signature Verification

Download:

MiFlash 20160401 https://drive.google.com/file/d/0B065LdNGqJLGM2xfSkZMbVYwc3M/view
15 second ADB Installer https://forum.xda-developers.com/showthread.php?t=2588979
ZTE Axon 7 USB Drivers https://androidfilehost.com/?fid=889964283620763004
ZTE Axon 7 Bootloader Unlock Images by TurkDevs https://androidfilehost.com/?fid=817906626617943545

Unlock Bootloader:

1. Install MiFlash. Driver installation will be done automatically.
2. Install ADB Installer. Press Y for all steps on installation.
3. Install Axon 7 Driver.
4. Turn on from developer options "USB Debugging" and "Unlock OEM".
5. Enter; "adb reboot edl"
6. Go Device Manager of Windows and be sure you see your device as "Quallcomm HS-USB QDLoader 9008".
7. Extract ZTE_AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS.zip
8. Go MiFlash and Refresh. Your device will be there. Select from top Unlock Images folder which you've extracted.
9. Flash and wait until it is done.
10. Long press power button and let your device is on.
11. Enter "adb reboot bootloader" after your device is on.
12. Enter "fastboot oem unlock-go" when you are on bootloader interface.
13. Your data will be erased on this step and device will boot with unlock bootloader.

This tool is from forum.turkdevs.com
Orginal thread: https://forum.turkdevs.com/konu/zte-axon-7-bootloader-acma-root-ve-twrp-yukleme.12225

Hit thanks button if I help you.

 

[muzzz33]

Many thanks , worked a charm , installed latest TWRP AND Magisk once unlocked . I thought this would be a night mare but no issues so far. I was on 7.1.1 2017G 1.20B08

 

[sebv_n]

Hi,i followed the steps in the guide to root my Axon 7 A2017, but I forgot to make a backup of the EFS folder before.
Now I have the device without a signal and if I write on the numeric keyboard * # 06 # to see my imei, it says this:
imei1: unknown
imei2: unknown
meid: unknown

But if I go to settings, in the phone information if I see the 2 imei.

I recently tried to go back to the original ROM of the a2017 b13 that I installed on the sd card, I made a wipe data, wipe cache, dalvik cache and a full reset.
After this I made a backup from TWRP of several things like the system, boot, bluetooth and I also had the option to backup the folder efs.
I did that and I just installed the original rom but I still have the device without signal and imei unknown
Can someone help me or give me an idea about what can be done?
Thanks

 

[iitywygms]

Got to this step.

8. Go MiFlash and Refresh. Your device will be there. Select from top Unlock Images folder which you've extracted.
9. Flash and wait until it is done.
10. Long press power button and let your device is on.

Then got the dreaded enter your android password.

Had to do a complete reset.

What did I do wrong?

 

[stinka318]

Hi,i followed the steps in the guide to root my Axon 7 A2017, but I forgot to make a backup of the EFS folder before.
Now I have the device without a signal and if I write on the numeric keyboard * # 06 # to see my imei, it says this:
imei1: unknown
imei2: unknown
meid: unknown

But if I go to settings, in the phone information if I see the 2 imei.

I recently tried to go back to the original ROM of the a2017 b13 that I installed on the sd card, I made a wipe data, wipe cache, dalvik cache and a full reset.
After this I made a backup from TWRP of several things like the system, boot, bluetooth and I also had the option to backup the folder efs.
I did that and I just installed the original rom but I still have the device without signal and imei unknown
Can someone help me or give me an idea about what can be done?
Thanks

Just reflash EDL......

 

[Oki]

I suspect that flashing these weird Turkish files with a green and uncentered ZTE logo, intead of the blue one, in a 2017U removes the capability to enter EDL by pressing VolUp+VolDn while rebooting the device. This behavior persists even after flashing the Oreo B12 or Universal BootStacks.

Are you experiencing this problem? Any clue on how to recover the original behavior of that key combination?

 

[KH_Lionheart]

Does the file included in the OP just flash fastboot functionality back to devices that have had it stripped by OTA?

 

[Kiddles]

12. Enter "fastboot oem unlock-go" when you are on bootloader interface.

Am I missing something here? I have my ADB drivers installed, and am able to get into the bootloader menu just fine, but anytime I use this command, it says the 'fastboot' command is unrecognized. Also, I can not longer use my PIN to get into my phone.

 

[Tekoj]

Does it work on A2017V3.0 B11 (Chinese beta Oreo) ?

 

[Kimmoth]

Am I missing something here? I have my ADB drivers installed, and am able to get into the bootloader menu just fine, but anytime I use this command, it says the 'fastboot' command is unrecognized. Also, I can not longer use my PIN to get into my phone.

It didn't work for me either. I think it should say "fastboot oem unlock /go"

That worked.

 

[bigmarkusch]

I have closely followed the instructions and was able to unlock the bootloader. However since then, I haven't been able to see my device appear again in MiFlash, I can only go in recovery mode or back to the bootloader.

My phone shows up under Device Manager > Android Device but despite trying different drivers (Android ADB Interface, ZTE Handset ADB Interface) I've never been able to see it when typing adb devices in the command line. I've tried adb kill-server without success.

Also the device appears under Ports (COM & LPT) > Qualcomm HS USB when I manually turn ELM on (Vol up + down) but with a broken-driver-yellow-icon "This device cannot start. (Code 10)" and again not in MiFlash.

Any clue how I can move on from here? My goal is to flash this ROM . I'm running Windows 10 on a VirtualBox.

Thanks guys!

 

[bigmarkusch]

I realized my VirtualBox USB Ports was not properly setup (has to be USB 2). So now I can install any driver I want but still, I haven't been able to communicate through adb or while manually running EDL. Have tried different USB ports and different cables and I cannot boot the system, only bootloader / recovery mode.

Anyone?

 

[bigmarkusch]

I have closely followed the instructions and was able to unlock the bootloader. However since then, I haven't been able to see my device appear again in MiFlash, I can only go in recovery mode or back to the bootloader.

My phone shows up under Device Manager > Android Device but despite trying different drivers (Android ADB Interface, ZTE Handset ADB Interface) I've never been able to see it when typing adb devices in the command line. I've tried adb kill-server without success.

Also the device appears under Ports (COM & LPT) > Qualcomm HS USB when I manually turn ELM on (Vol up + down) but with a broken-driver-yellow-icon "This device cannot start. (Code 10)" and again not in MiFlash.

Any clue how I can move on from here? My goal is to flash this ROM . I'm running Windows 10 on a VirtualBox.

Thanks guys!

I solved my issue: I was able to flash TWRP directly using the fastboot command line! Not sure how, why or if EDL mode was even necessary after all… got a fantastic new phone! Yaaay. Advice to beginners like me: keep trying with different versions and approaches, read carefully different threads including comments… good luck!

Thanks guys for all your efforts making these tools for everyone to use!

 

[redhou]

hi
by mistak i flash my A2017G with this file : ZTE_AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS using miflash and now my phone don't start.
i was on oreo b02 , any solution to make it working again

 

[eeyan]

I got the password prompt after doing this, as in, when I power it on normally, it boots up and asks me for a password. I don't seem to have a useful bootloader anymore, when I do volume up + power, the red light turns on briefly then nothing happens. Other people with the password prompt issue have solved it by a factory reset or TWRP functions but I can't get to either. When I do volume up + down + power to get into EDL mode, when I plug it into my computer I get the DFU device in my ports list in device manager and MiFlash can't do anything with that. I got an EDL cable but it doesn't do anything but get me into DFU also, I've tried for hours with combinations of the cable button and device buttons offered online, no luck. When I fire up DFU_MultiDL Tool, I can't flash anything in it because it causes the device to go out of DFU and then shows up as a QDLoader 2008 device. While in that mode I can flash stuff, so I tried flashing the unbrick option in Axon7Toolkit, and now it gives me the password prompt in Russian. There is no fastboot capability. Any stuff I should try?

 

[Choose an username...]

I got the password prompt after doing this, as in, when I power it on normally, it boots up and asks me for a password. I don't seem to have a useful bootloader anymore, when I do volume up + power, the red light turns on briefly then nothing happens. Other people with the password prompt issue have solved it by a factory reset or TWRP functions but I can't get to either. When I do volume up + down + power to get into EDL mode, when I plug it into my computer I get the DFU device in my ports list in device manager and MiFlash can't do anything with that. I got an EDL cable but it doesn't do anything but get me into DFU also, I've tried for hours with combinations of the cable button and device buttons offered online, no luck. When I fire up DFU_MultiDL Tool, I can't flash anything in it because it causes the device to go out of DFU and then shows up as a QDLoader 2008 device. While in that mode I can flash stuff, so I tried flashing the unbrick option in Axon7Toolkit, and now it gives me the password prompt in Russian. There is no fastboot capability. Any stuff I should try?

It shouldn't be that hard to get out of that mess - Just don't use axon7toolkit, you'll bury yourself even more. The unbrick option probably flashed an EDL package, I assume

First of all, you were getting a red light when trying to enter the recovery because the recovery was not compatible. There are some TWRP versions that might start when you get to this state - one of them is 3.0.2-2 Tenfar, which is signed. DO NOT BACKUP with this version as it will erase your EFS partition if you attempt to back it up. But you can format data all right with it.

MultiDL works just like you described it lol, it simply gets you out of DFU. you just have to close it and get to EDL Tool or miflash or whatever. To flash tenfa's TWRP you ca simply use EDL Tool's flash recovery option


Or you can just flash a full EDL package? I can't see why you wouldn't after trying axon7toolkit's unbrick option, whatever it does, it probably already replaced whatever you had before (vendor?)

 

[eeyan]

Thanks for your reply and the info. I got the Tenfar TWRP package but my phone wasn't having it when I tried flashing it. My bootloader didn't get unlocked, not sure why, I had the OEM Unlock option on when I ran this guide. Should the Tenfar TWRP flash even if the bootloader isn't unlocked because it's signed? I've been trying the full EDL packages. One of them gets me the ZTE boot screen with Chinese characters on it and the Russian password prompt and the others give me the regular ZTE boot screen with the Russian password prompt.

It shouldn't be that hard to get out of that mess - Just don't use axon7toolkit, you'll bury yourself even more. The unbrick option probably flashed an EDL package, I assume

First of all, you were getting a red light when trying to enter the recovery because the recovery was not compatible. There are some TWRP versions that might start when you get to this state - one of them is 3.0.2-2 Tenfar, which is signed. DO NOT BACKUP with this version as it will erase your EFS partition if you attempt to back it up. But you can format data all right with it.

MultiDL works just like you described it lol, it simply gets you out of DFU. you just have to close it and get to EDL Tool or miflash or whatever. To flash tenfa's TWRP you ca simply use EDL Tool's flash recovery option


Or you can just flash a full EDL package? I can't see why you wouldn't after trying axon7toolkit's unbrick option, whatever it does, it probably already replaced whatever you had before (vendor?)

 

[Choose an username...]

Thanks for your reply and the info. I got the Tenfar TWRP package but my phone wasn't having it when I tried flashing it. My bootloader didn't get unlocked, not sure why, I had the OEM Unlock option on when I ran this guide. Should the Tenfar TWRP flash even if the bootloader isn't unlocked because it's signed? I've been trying the full EDL packages. One of them gets me the ZTE boot screen with Chinese characters on it and the Russian password prompt and the others give me the regular ZTE boot screen with the Russian password prompt.

How do you know your bootloader is not unlocked? Do you have the warming screen?

Tenfar's TWRP is made for flashing before unlocking the bootloader, so that you can replace the aboot and fbop images and regain Fastboot, and then issue the unlock command from there

You're not bricked anymore though. you just need to format your data partition. Try flashing Tenfar twrp and entering it right away, by holding Volume UP before the ZTE boot logo appears. then format data from inside of it if you manage to get there. if it throws an error about data being encrypted, just reboot - reboot recovery and try formatting data again

 

[adeki]

is this method working 8.0.0 B022 stock ?