[GUIDE][A2017G] Reinstall TWRP and Root after update to Nougat

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
Get TWRP and root after updating to Nougat

This method worked for me, but be aware, it might not work for your specific device. in a worst-case scenario, you'll brick your device - proceed at your own risk!


For devices with UNLOCKED BOOTLOADER! This guide does not show you how to unlock the bootloader

BIG thanks to @tamahouse02, @bkores, @S0wL and @tron1 for the help they gave me when trying to do this on my own device. This post is just a compilation of everything we tested over the old questions/answers post.

How To:

Set up axon7tool and download TWRP

  • Download axon7tool from here. Thanks tennear for the awesome tool
  • Download TWRP for ailsa_ii, newest one available. I used 3.1.0.0
  • Download Zadig and throw the exe somewhere
  • I asume that you already have adb installed, if not install it with 15 seconds installer
  • Put axon7tool on your adb folder, rename it to axon7tool.exe
  • Put TWRP image on the same folder, rename it to recovery.img (you NEED TO BE ABLE TO SEE THE FILE EXTENSION! Google how to enable that)
  • Duplicate the recovery.img, rename it recovery.bin, keep it in the same place
  • Connect your phone, enable USB debugging, open CMD and run adb reboot edl
  • Open Device Manager once your phone looks like it's off. You should see a Qualcomm HS-USB QDLoader 9008 under Ports - COM & LPT, uninstall it AND TICK DELETE DRIVER SOFTWARE TOO and hold the three buttons of your phone (vol buttons and power) for quite a lot of time, until you see that the device manager list refreshes. If Windows attempts to install the driver cancel it at once, repeat the process if it did install it (it appears as a Qualcomm thing again). After holding the 3 buttons you should see an unidentified device named QUSB_BULK
  • After you have the QUSB_BULK device fire up Zadig and Install the driver.

Flash TWRP using axon7tool

  • Hold the 3 buttons of your phone again until device manager refreshes
  • Open CMD on your adb folder (go to the folder, SHIFT+right click anywhere, open command window here)
  • run axon7tool -r recovery gpt boot
  • Leave CMD open. Go to the folder where the tool is and make a folder named backups or whatever, put all the backups there (recovery_backup.bin for example)
  • You should have made a recovery.img and recovery.bin there before. Check that you left them there, just to be sure
  • Finally, on the CMD window, run axon7tool -w recovery. If it fails try holding the three buttons, opening cmd again and trying this step again. otherwise post your error here
  • If it succeeds disconnect your usb cable from the phone BEFORE THE COUNTDOWN ENDS, then hold the power button for like an eternity until the phone reboots. If you don't do this your TWRP will be replaced by the stock recovery. you only have to do the previous step again in that case, don't worry.
  • Either while the phone is booting or with adb after it gets to system, get to the recovery and test if it boots. Congrats if it does!

Install SuperSU

You probably know how to do this if you came this far. If you don't:
  • Download SuperSU 2.79 from somewhere on the internet
  • Get to TWRP
  • Flash SuperSU
  • Avoid the inherent nervous breakdown that the initial bootloop causes (in layman's terms, don't freak out, let it do its thing)
  • Done

Get Fastboot

  • Download this ZIP (thanks @sToRm1nG) and put it in the root of your phone's storage
  • Go to TWRP and flash the ZIP
  • Boot system and adb reboot edl
  • Now we need to replace the Zadig driver, sorry :( you'll find QUSB_BULK under USB devices (bottom of the list in English), uninstall and check Delete driver software too
  • Hold the 3 keys
  • Windows might attempt to install the driver. Leave it, hopefully it will. You need to get Qualcomm HS-USB QDLoader 9008. If it appears as an unknown device google for the driver (just google Qualcomm HS-USB QDLoader 9008 driver and you'll get it) and install it, then hold the 3 buttons and check if the QDLoader 9008 appears under Ports COM&LPT
  • Download MiFlash from here, and the fastboot package from here
  • Unpack the fastboot package somewhere, be careful not to unpack it like a folder with another one inside, but rather one folder directly with all the stuff inside
  • Open MiFlash and select the folder that you unpacked
  • Select Refresh, then your device should appear. if it doesn't then you didn't reload EDL or you didn't install the Qualcomm drivers, simply do that again. If it appears go ahead and choose Flash
  • Reboot and try if it worked, by selecting Fastboot from the 5 sec menu or using adb once you're booted


All done. I'm not a developer of any kind, so I'm afraid i won't be able to help with specific errors. But most simple errors you could have are described here, so you should have little trouble doing the procedure.

Hope the best of luck to y'all while doing this
 
Last edited:

logimowl

Member
Jan 4, 2015
31
4
0
Thanks for the Guide!

My Axon 7 (G-Modell - Nougat 7.1.1) is located in the EDL and is under Device Manager as
"Qualcomm HS-USB QDLoader 9008" detected, but MiFlash does not recognize it. The latest drivers from Qualcomm are installed and I use the original cable from ZTE, but it does not want to be recognized ;-(
 

jorgex

Member
Oct 24, 2006
9
0
0
Thank you man!I'm already Rooted in Nougat 7.0 in my A2017G..... But AdAway can't write the host file, do you have the same issue?
 
Last edited:

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
Otherwise try to get to fastboot however you can, then flash TWRP again, or you can try getting to EDL and restoring the backups that you hopefully made. I have no idea how the DFU mode thing is, but I would do some research on that. I'm no dev
 
  • Like
Reactions: nsabir

icaros1530

Member
Jun 9, 2014
37
4
0
Please help, I have the same problem as logimowl:

My Axon 7 (G-Modell - Nougat 7.1.1) is located in the EDL and is under Device Manager as
"Qualcomm HS-USB QDLoader 9008" detected, but MiFlash does not recognize it. The latest drivers from Qualcomm are installed and I use the original cable from ZTE, but it does not want to be recognized
 

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
@icaros1530 Huh I've just installed 7.1.1 official today, so I have to do the process again. I've just opened MiFlash and it detects stuff nicely. The device appears as COM5 on MiFlash and the driver is under Ports (COM & LPT) with the name Qualcomm HS-USB QDLoader 9008 (COM5)
 
Last edited:

icaros1530

Member
Jun 9, 2014
37
4
0
@icaros1530 Huh I've just installed 7.1.1 official today, so I have to do the process again. I've just opened MiFlash and it detects stuff nicely. Look
Thanks for checking and posting the screenie. I've been on the issue since yesterday now and found a suggestion to try on a different computer, so I tried again and it worked on my win10 notebook. So issue is insofar solved as my smartphone is now running 7.1.1 and rooted and all. Why miflash just can't connect on my win10 pc.. I have no clue. I've rebooted device and pc tons of time with different drivers, even trying the old root methods, used zadig whatever. Everything looks the way it should - but some minor thing hiding somewhere just won't let it work.

td;dr: if miflash can't connect try different computer..

---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------

Download any terminal emulator app and execute:
Code:
su
then
Code:
reboot disemmcwp
That doesn't work for me. The command reboots the device, but Adaway keeps saying host files couldn't be copied.

SOLVED: for 7.1.1. we seem to need the systemless version of adaway. I picked up version 3.2 from here and it works perfectly: https://forum.xda-developers.com/showthread.php?t=2190753
 
Last edited:

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
@icaros1530 lol I'm gonna add that to the OP (try different computers if it doesn't work)
All these programs are extremely nitpicky it seems! :eek:


And I uploaded 2 pictures, but only one showed up, so I just deleted them and added some text. That's why i edited, i just wanted to make that clear
 
Last edited: