[Guide] [A2017(G)] - Unlock, TWRP, Flash with Toolkit - ZTE Axon 7 Guides, News, & Discussion

About
Hi there,
I created this guide not so much as a substitute for the other guides or because this would be the best way to do it.
When I looked into rooting my new Axon 7 (international) I studied all the other guides first, but then did it very differently, mainly
because
- I am on Win 7 32-bit and some of the tools used in the other guides don't work for that
- since the other guides were created the Axon7Toolkit came along - that simplified a lot of steps.
The guide is actually very similar to this one for the 2017U:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Only now with the toolkit it pretty much works for the 2017G as well without the need for tenfar's TWRP (see comments). In case I left out anything, this guide will be of help, too.
So this guide is for you if
- You want to root or flash a custom rom and don't mind unlocking the bootloader OR
- You are on Win32 and cannot use the axon7tool command line tool OR
- You want to use the Axon 7 Toolkit for the job to keep things simple
Please read all the notes below before attempting anything...
Disclaimer
- This worked well for me - no claims it does for anyone else. For the record: I was on Stock 6.0 MM B08 A2017G, no fingerprint/lock etc and went straight to RR.
- Use at your own risk, if you are unsure what you are doing stay stock - I'm not responsible for bricked devices, dead SD cards, Donald Trump, or you getting fired because the alarm app failed...
Regarding Drivers
- Qualcomm ones for MiFlash (link below)
- QUSB_BULK if going with eg the axon7tool commandline version (edl mode)
- You can use the Toolkit to install (some of) the needed drivers
- ZTE drivers - phone is set up to install them upon connect to the PC. Don't.
- Uninstall incorrect drivers, just installing the correct ones won't necessarily do the trick.
MiFlash
- right click & 'run as admin' (flashing didn't work for me without this)
- Correct driver: Qualcomm HS-USB QDLoader 9008 when in edl (check with device manager open)
Boot modes
- power phone down and boot into
- EDL by holding Volume UP/DOWN & POWER simultaneously
- recovery/TWRP (once installed) by holding Volume UP & POWER simultaneously
- fastboot: Not enabled in A2017G Stock
Windows
- 32-bit: MiFlash needed, commandline axon7tool not working
- The toolkit seems to run on Mac/Linux using a Windows emulator/virtual machine (not tested, Wine helps I guess)
TWRP
- versions: Signed tenfar TWRP 3.0.2 that is used in a lot of other guides is buggy and can do a lot of harm - not needed if you unlock
the bootloader first. You can (and should) use the latest official TWRP version.
- dm-verity: https://twrp.me/devices/zteaxon7.html
- USB OTG: Axon 7 supports this, so does TWRP - no need for SD cards. Simply use a thumbdrive with a OTG cable (with included Adapter if needed), boot into TWRP (thumbdrive needs to be connected beforehand) and click 'Mount' in TWRP, then select USB storage
Bootloader
- Afaik DO NOT lock again with custom rom installed or rooted (brick)
Root/Unlock
- Can create problems with Android Pay, playstore etc - see https://www.xda-developers.com/tag/safetynet/
- Root disabled by default in Lineage, needs flashing Magisk or SU - see other guides
- Some features root provides on Android 6.0 MM won't work in Nougat (so far anyway, eg xposed)
Links
- Axon7Toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
- TWRP: https://twrp.me/devices/zteaxon7.html
- Zadig (if needed): http://zadig.akeo.ie/
- Qualcomm driver: https://build.nethunter.com/misc/axon7/Qualcomm_QUSB_BULK_Drivers.zip (link from https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514)
- Lineage Os thread: https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
- Modem & bootloader from Lineage Os thread: https://www.androidfilehost.com/?w=files&flid=148464
- OpenGApps: http://opengapps.org/?arch=arm64&api=7.1 (arm64 version for OS version to flash, e.g. 7.1 Nougat)
Thanks
bkores (for the tool), dnlilas (help in the forum), DrakenFX, Unjustified Dev, Controllerboy & all the guide/rom creators etc in this forum. (And the poor souls who came first and discovered all the ways not to do it, preventing my fall)
1) Prep
- Note down IMEI(s) from your settings/about phone/status/... just in case
- Unlock developer options (Phone settings > "About Phone" > Click "Build Number" 7 times...)
- Check "Allow OEM unlock" and "USB Debugging" there
- Connect your Axon 7 to your PC with the original USB cable - do not disconnect with MiFlash/Toolkit running.
- Open device manager to check your drivers (will show up differently depending on the boot mode)
- Run Axon7Toolkit
- Select Option 1 - Install/Test Drivers
2) Unlock
- This will RESET your device, did you save your data? (using Toolkit etc)
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
- The unlock files the Axon7Toolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' - works for A2017G
(- Axon7Toolkit preview version offers different folder content to flash - have not checked that)
- One can restart MiFlash (e.g. to 'run as Admin') anytime and try again, but after the flash was succesful, do not disconnect the phone but
- Finish off with the Toolkit 'press a key to continue' (or one will have only fastboot enabled)
- A message will appear on the phone: Confirm that you want to unlock the bootloader (using volume & power buttons to navigate)
- Done. From now on you will get an annoying message on booting the phone about your device being unlocked. Just ignore and wait for a re-boot...
3) TWRP
- Unlock developer options - AGAIN etc as device was reset. And - again - enable debugging...
- In the toolkit (main screen) go to '11 Advanced Options', select <Flash boot/bootloader/modem/recovery<choose recovery partition
- In 'Open' dialog select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img (or newer version)
- Flash as 'recovery'
- Reboot, check system boots up fine
4) Flash Custom Rom etc.
- Generally: Follow instructions provided with the custom rom you are going to flash (as they might differ)
- Boot into recovery/TWRP (Volume UP + Power after shutdown)
- No need to swipe to 'Allow system modification' - this can actually brick things...see https://forum.xda-developers.com/axon-7/help/a2017u-stuck-zte-screen-boot-factory-t3584062
- Mount/Select storage (for OTG USB)
- Backup boot, recovery, data(if needed), HLOS, System image or System (image was recommended but that did not work in my case, so I backed up system)
- Wipe/Format
- ***If you like to avoid your data partition to be encrypted, follow that thread: ( format your data partition to ext4 instead of f2fs (wipe -> advanced)????)
- Install Bootloader & then modem (or Nougat won't install if coming from MM) - A2017X_B15_Universal_Bootloader.zip & A2017G_N_Modem.zip
- Rom & Magisk/SuperSU
- GAPPS (version)
- Re-boot: Unlocked message, long first time boot - After RR, my phone show up as 2017U... well, who cares...
Any comments to correct errors in this guide or fill out any blanks are highly appreciated...

---

I dunno why now one has thanked this yet, it is a well written guide imo and useful for those not yet unlocked.

---

THANKS SOO MUCH FOR THIS!! The timing could not have been any better. I literally just bought this phone from a guy on craigslist for $270 (Couldn't pass that up coming from an LG G4) less than a hour ago. Quick question. It's a 2017u with build B25. Will the toolkit work with it. I don't see an option for this build

---

Hi Senny,
thanks a lot - I hope the guide is helpful, as mentioned it worked for me. Hopefully I included at least most of the pitfalls one could encounter...
Hi raphi809,
The toolkit should work fine with the 2017U (it should detect your version).
To be sure, also have a look at the toolkit thread (https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108) and the thread linked above (https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128), as it is more specific for the 2017U.
The main thing I am not 100% sure with the 2017U is (as I am on a 2017G and started from Android 6.0 MM), if you have to downgrade from Nougat/certain versions before unlocking etc.
If someone could shed some light on this, that would be great!

---

Whoooo? said:
About
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
Click to expand...
Click to collapse
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?

---

Volumetrik said:
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Click to expand...
Click to collapse
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps

---

Whoooo? said:
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Click to expand...
Click to collapse
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:

---

It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?

---

marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi there,
Obviously I have not tried this myself, so I only can refer to these two posts from the Toolkit thread:
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71673370#post71673370
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71861250#post71861250
...stating that 'Bootloader mode is disabled in G variant with Nougat update' and one has to either
- revert to MM or
- flash a different Unlock package with MiFlash (linked in the second post)
(There is also a note in the instructions saying that the toolkit's Bootloader unlock with MiFlashdoes not work on A2017U B25)

---

marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi Marcus,
I tried to find some time to reply and explain how I used this guide and two others to get my device unlocked, twrp'ed and LineageOS. It's running like a charm.
I started with a A2017G device basis with MM B03. My device was updated to the latest official update available via MyFavor network. I didn't try to update OTA.
I Used Axon7ToolKit v1.1.1 + Update_Install.bat / Qualcomm Drivers / A2017U_Bootloader_EDL. I worked under windows x64, because I experienced too many troubles to get Axon7toolkit working properly under 32bits. The only one differences I experienced and not written in the threads:
- I saw a FTM mode (Factory Test Mode) displayed in a white square centered on the device screen after unlocking bootloader. In my memory, it disappeared after TWRP flash.
- I got a problem with Flashlight, didn't work, associated with a problem to call (sms working). I flashed the modem firmware once again, it solved the problem after reboot.
- At the end, LineageOS installed, LineageOS updater strangely saw the same update version installed on the device. The only difference was the"signed" at the end of the update name I launched the update and installed it succesfully, without issue. No more update after that (until a new one of course)
Hope this will help someones

---

Volumetrik said:
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
Click to expand...
Click to collapse
Hi, when are you planning to release your complete guide? This would really help me.

---

I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...

---

Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?

---

still_living said:
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
Click to expand...
Click to collapse
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).

---

Apocalypse12345 said:
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Click to expand...
Click to collapse
Hi there,
I think (memory blanks setting in) that's the error I got when MiFlash was not running as admin.

---

Whoooo? said:
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Click to expand...
Click to collapse
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).

---

Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
still_living said:
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Click to expand...
Click to collapse
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.

---

djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
Only stock recovery for me. No twrp unfortunately. Really want to change from miflavour

---

djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
HURRAY! ! !
Well no it didn't work until today I tried the option to restore from bricked device to b10. Out took me to miflash and asked me to unlock bootloader? Dunno why, it's already unlocked, anyway , after that was successful I went back to the option page of the toolkit and selected 'install twrp', and this time it flashed! It didn't stop on the 'failed to flash twrp' message but still gave me a 'flash to boot into twrp' then I followed your advise to go to twrp directly from there and it had installed. I'm so happy thanks loads dude. :laugh:

---

Worked like a charm! Thanks for posting the guide
Edit: Went from locked Nougat to Unlocked Lineage.
Whole process took me about 2 hours, but if you are better at following the steps than me you'll probably be able to do it in 1 hour.