yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Factory reset

Thank you for your reply. Maybe I was not clear in my post: I have no problem to wipe my phone as I had just received it and there are no data on it. However, I am stuck in that I can boot to edl, but then I cannot flash anything. So, my question is: how do I get it back to stock recovery and ROM so that I can boot back to the OS?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gaijin1%:
Use the Axon7tool (or just MiFlash) to flash TWRP back on your phone. Then start the phone holding the volume button up to get to TWRP and be able to flash.

If you want to return to stock, use the earlier Stock ROM (and Kernel if you changed that) then just upgrade from there using MiFavor system update with the updates on your SD card one by one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Axon7tool

But the thing is that when I am in edl mode, the axon7tool does not see my phone. When not in edl mode, Adb shows the device but offline. So, how to get Axon7tool to see my device again?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gaijin1%:
Choose to unlock the bootloader and that will launch MiFlash. Use MiFlash to flash TWRP instead. Other way is to adb sideload. That works in edl mode.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
MiFlash

Thank you for your answers and your patience. This is the problem with MiFlash: when I try to use it to unlock the bootloader again, it says "Receiving hello packet" and then "Missed hello packet, try to recover" and then nothing happens. Upon reboot, I still get the question re. the password.

Now, I am afraid my situation has deteriorated: I had left my phone last night in edl mode and now that I wanted to try and sideload tenfar's twrp, I find it is in DFU mode. So, I will start posting in the DFU mode thread to see if I can get out of it or not.

OK, I kept the start button and volume pressed long enough and managed to get it back to factory diagnostic mode and then with adb reboot edl to edl. But then, when I try to do adb sideload with tenfar' s signed twrp (the .img), adb give me an error: device not found. I am using a windows 10 PC and the device manager shows a Qualcomm HS-USB QDLoader 9008 on a com port. Can I miflash tenfar's signed twrp .img file now?

The saga continues: I miflashed unlock which this time completed in 2s. But then the device went back into DFU mode and I have not been able to get it out of that again.

OK, final update: I found a solution:

I was able to get my phone from DFU to factory test mode (FTM) by unplugging the USB connection and running down the battery. When I then start up with power and volume down, I get the blue ZTE sign. Then power + volume up -> FTM mode. adb devices then gives me a reply of '? device' . 'adb sideload ...img' gives me 'error: closed'. However, once I have FTM, I finally was able to unbrick my device by using the windows 1.1.1 tool to unlock my bootloader again while in FTM mode. That was the key: just stay in FTM and use the tool.!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
I am happy to announce a preview(test version) of Axon7Toolkit 1.2.0 is available for download. As I said it is for TESTING PURPOSES ONLY so please only download if you are going to test. This is a major update and simplifies and fixes many many things.

Here is the changelog(subject to change):

-Fixed NUMEROUS minor bugs

-Minor enhancements

-Fixed bug in which in extremely rare instances the toolkit would hang when checking ADB or fastboot connectivity

-New UI

-New popup design

-Increased wait time before checking ADB recovery or fastboot connectivity

-EDL driver installations now handled by the toolkit, no need to do it manually with Zadig or Device Manager

-Bootloader Lock option now flashes aboot and fastboot unlock image before locking to guarantee success

-MiFlash updated to latest version(fixes unable to launch setup on 32-bit PCs)

-Wget updated to latest version

-Option to utilize axon7tool instead of miflash for bootloader unlock on 64-bit PCs

-Added A2017U B19 restore stock option thanks to [MENTION=6930800]jcau[/MENTION]danno

-Added A2017G B10 restore stock option thanks to [MENTION=6330152]djkuz[/MENTION]

-Modified bootloader unlock miflash package(added aboot) to support unlocking on A2017G B02 Nougat

-Fixed ADB restore not working

-2nd attempt to fix hashcheck mismatch issue when importing

-Dropped support for any Windows version below 7

-Fixed bugs in uninstaller

-Code cleanup

-No longer required to set build, just variant

-Simplified downloader

-New simplified toolkit: removed Driver Installation/Test and Advanced Utilities

-All drivers now installed during setup

-NEW OPTIONS! ADB+Fastboot Test & Flash TWRP

-Fixed toolkit not finding A2017 B13 restore package even if downloaded

-Fixed indefinite loop for wipe data and system prompt for flash zip option if yes is inputted

Known Issues:

On Windows 8.1 and up QUSB__BULK driver for axon7tool install fails

Downloader progress stuck at 0%

Variant gets set to A2017 if choosing A2017U making restore stock option useless(workaround: change variant to A2017U in Settings

Toolkit hang bug still remains(although I have a strong suspicion why)

minor cosmetic bugs such as some popups

Restore stock option will not download ANY package
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
HI, I have installed it but when i open, i can only see 4 to 5 notifications near notification area but tool never opens. Tried multiple times, can you please help. I am using windows 10 64 bit.

---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------

HI, I have installed it but when i open, i can only see 4 to 5 notifications near notification area but tool never opens. Tried multiple times, can you please help. I am using windows 10 64 bit.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
You have to wait for the toolkit to finish setting up. And please do not quote the entire post, it's useless clutter.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
Thanks for the reply :) N Sorry for quoting the entire post. I have waited for almost 10 minutes but nothing opened. Does it really take that much time ?

I dont even see anything running in the background, already disabled Anti Virus.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Ok no it's not supposed to take that long and it should have opened. Maybe try reinstalling???
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
Yeah, I have tried multiple times! Is there any issue with Windows 10 :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Shouldn't be I'm on Windows 10 and it opens for me...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
If you dont mind, can you please uninstall and install post downloading fresh file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Are you using 1.1.1 or 1.2.0-P1?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
I am using 1.1.1. Where is that 1.2.0 ? :eek:

---------- Post added at 11:45 PM ---------- Previous post was at 11:37 PM ----------

Its the same with both these versions. I am following some other tutorial and my phone is bricked now. Can you please help exact tutorial or link please?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Ok I think I know what the problem is. Open an elevated command prompt window(search "cmd", right click, run as administrator) and execute

taskkill /F /IM adb.exe
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
ADB was killed successfully but no use. Still cant open the tool
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
Your Tool is really great :) I have transformed to A2017U but wifi didnt work so installing FW again. I have lost TWRP in this process and now i am unable to install. Bootloader is UN locked and whenever i try to boot into fastboot mode, the device not going rather booting to OS. I am going crazy as i am missing something. Please help.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
You are not going crazy, ZTE blocked the bootloader partition on Nougat. Use the unlock option in the toolkit which will fix this. By the way how did the toolkit finally open for you?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] satish.yarramsetti:
I See, are you referring bootloader unlock in toolkit ? I am facing dll issue while running MiFlash, even i faced it first time but not sure how i flashed TWRP.

Its opened for me when i try in another computer.

Can you guide step by step to flash TWRP Now? i am on B11 & Boot Loader Unlock.

---------- Post added at 12:33 PM ---------- Previous post was at 12:22 PM ----------

I tried to flash manually from MiFLash but Hello Packet not receiving.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Bucatino:
No new update incoming? ^^
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
I'll release it when its ready. Don't ask for ETAs. And in case you didn't see I uploaded a test version for anyone who is willing to test.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Fuilares:
It is possible to unlock A2017 bootloader on V1.1.0B13 (Nougat) with this tool?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Seriously?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Can I unlock the bootloader of my Nokia 3310?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TopWargamer:
MiFlash doesn't seem to be working for me. I made sure all of the Windows drivers were installed. My device is not being shown. Whenever I click "Refresh" it says "There was a problem starting qcCoInstaller.dll. The specified module could not be found." I tried Googling around for the dll, but I couldn't find it. Any ideas what's up?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] antpaige:
How bout you take a chill pill bruh, Everybody here is appreciative of your work and just anticipating future updates. No need to get testy. Be happy you have the following you do. Nice work, will be trying it soon
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aljarreaud:
Im getting this error when trying to unlockbootloader. ZTE_A2017V1.1.0B13
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Well that's because you're trying to flash the wrong package. You need to flash the unlock, not B13
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Dude relax. I wasn't being testy at all just stating the facts.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Agent_no1:
First i want to thank you for your tool and support for the Axon device.

Today i wanted to catch a first glimpse at unlocking/rooting my phone, which currently is running B02 Nougat (ADB enabled, OEM unlock enabled). I've browsed the whole 24 pages trying to get everything right.

On Axontool 1.1.1 I'll started with testing the driver packages with the menu-entry 1-> 3. Except from missing the fastboot package, the connection seemed to be working properly.

I'll then installed the Miflash-Software from the AxonDevelopment Folder and flashed the EDL-Fastboot-File from that mega-link which were mentioned here. It worked instantly and my device were rebooting. Fastboot-connection then seemed to be fine accordingly to the tests of the Axontool.

But (!) since then i'm not able to enter my PIN anymore for unlocking my device. I am able to enter the SIM-PIN sucessfully, but after that my current PIN for unlocking my device won't be accepted anymore.

As i wanted to backup my mobilephone before going for the next step unlocking the bootloader, i now won't be able to do this anymore, as it seems.

Is this state the one, which were mentioned before (sudden android password-query when using the phone)? :-/

Is there somehow a way gaining access to the phone again? I can see my mobile background and still got the ADB-connection running.

Any help is appreciated

Thanks in advance

PS: Google Device Manager is able to connect and locate the device, as well "locking" it with a self defined password, but unfortunately it won't change anything.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] VoidrayX:
Hi, could you elaborate abit on the detailed steps for doing this step? Sorry for being such a nub.

I assume if when I did the driver test and i get no fastboot device detected i need to do this. Still locked on stock b02 Nougat
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Grogros4:
[MENTION=3849138]Agent_no1[/MENTION] If you have access to TWRP you can delete in /data/system all the files with the .key extension and all the files named locksettings. I had the same issue after restoring a nandroid backup and it worked for me
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] igbee:
Thanks for creating this! It makes it much easier for me to figure things out.

I'm trying to follow the instructions to get rid of MiCrapper but I get stuck when flashing zips. The zips get imported ok and then when device reboots to TWRP I lose the connection and the toolkit says "ADB Recovery Device not connected"

I used the toolkit to Unlock the bootloader already.

---------- Post added at 05:38 PM ---------- Previous post was at 05:00 PM ----------

Got this going again by reinstalling the drivers while connected to TWRP!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aljarreaud:
Im on A2017 nougat B13, so i clicked flash on the unlock\A2017\A2017U_FASTBOOT_UNLOCK_EDL folder. what do i do next?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] VoidrayX:
[MENTION=7658623]bkores[/MENTION]

I noticed the included instructions for bootloader unlock is shown for A2017U, despite selecting build to be AnyA2017G, is it still okay to use? also im assuming we flash the A2017G EDL unlock instead on post 2 instead of the one mentioned in the instructions
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Yes and if you are on B02 Nougat yes
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] toxicOne:
Axon7Toolkit

hey guys, question my phone A2017G Variant. ( ZTE Axon 7 A2017G / Build: ZTE A2017GV1.0.0B06 ) bkores mate you mean in changelog from stable Axon7Toolkit-v1.1.1-setup

can i use your Win10x64 Axon7Toolkit-v1.1.1-setup to flash TWRP, unloock bootloader and root my device!? Iám not sure but i have only plug in my ZTE to pc connect and install Smartphone driver on my Pc. Problem or not?

thank you very much for your answers
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
V1.2.0 Preview I Feedback

Hi, thank you for the tool. It has been crucial for me to stick with my A7.

I just managed to upgrade my A2017G to 7.1.1. I have an unlocked bootloader but have put everything else back to stock in order to get my upgrade. Now, I want to go put fastboot back and TWRP. With version 1, I got missing hello packet in miflash, so decided to give V1.2.0 Preview I a test run. Here is my feedback:

a. I installed it without uninstalling v1.0. Hope that is OK. Maybe tell in the instructions what to do.

b. Like the selection of the 3 hardware variants at the start.

c. I used to use option 6 (bootloader unlock) to flash fastboot when the phone is in edl. As I mentioned before, miflash did not work any more. With version 1.2, I get a choice to do it via axon7tool or miflash and it recommends doing it via axon7tool. Small nitpick: you have to choose 1 or 2 but you do not indicate in the question that axon7tool is 1 and miflash is 2.

d. I picked 1 and then it reboots to edl on its own. Great. It started to look for QUSB_BULK device. That is great! No more having to do so manually. It then lloked for Qualcomm HS-USB QDLoader 9008 , which it found. Then it decided to replace the driver. That gives an error message: C:\Axon7Development\Axon7Toolkit\axon7tool\devices.txt not found..

e. Then I get a message Driver replaced successfully!. Then it seems to hang, because I did not notice some other window where it told me to hold the power button and use the option again.

f. So, I restarted the process. Again option 6. Replacing driver. Now I get a popup with title Error and text Replacing. Now the popup to hold the power button is on top. So, I hold the power button, phone reboots, asks for my pin, and my pin no longer works!!! Maybe the miflash works better?

Let me sweat this one and I will provide more feedback. Hope this is what you are looking for.

EDIT 1: additional steps - I am still sweating this!

1. Now chose miflash for option 6 and installed the Chinese language software 2016.12.22.0 (Release).

2. Interface looks nice. I selected the package to flash as per the instructions.txt. I got a script not found error pop up but proceeded with the flash. It says - start flash, read hello package, cannot receive hello, trying to reset - finally, I get a message - Object reference not set to an instance of an object - in the status field and a result which says error on a red background.

So, now I am stuck, apparently in the same situation as Agent_no1.

EDIT 2: was able to get to stock recovery and do a factory reset. No more PIN. Back in business.

EDIT 3: amazingly enough, upon reboot from the OS, I now have fastboot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Thanks for the feedback! For the axon7tool the QUSB__BULK driver install actually fails due to an invalid catalog file so the driver replaced successfully message is false. As for the popup its a typo. I'm aware of everything else. Thanks again for testing!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chrisrodsa210:
I'm on 2017U B19, Windows 10 laptop, completely stock, locked bootloader, and haven't gotten anything to work with it except ADB commands. I'm specifically trying to unlock my bootloader and running into issues with Fastboot. FASTBOOT device is not detected. I've tried uninstalling and reinstalling drivers and programs, and using the original and other usb C cords. And same issue. Miflash successfully flashes the file but after the reboot into bootloader I get the Fastboot error message. Help anyone, or any idea what's up?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Which version of Axon7Toolkit and of miflash do you use?

Which one is "the Fastboot error message"?

Notes:

a) I have sometimes had to do miflash (from v1.1. of the Axon7Tookit) a couple of times for it to succeed. On 1.2.0, it seems to work better.

b) I have a A2017G so not sure - if I am not mistaken, B19 is 7.1.1. There is a reference to a different set of files to flash for Nougat on this page a bit higher in the thread. Have you used that set of files?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chrisrodsa210:
It's ok, IDK for me it was a huge mess, I was able to recover through EDL mode. But thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
I have now used the Preview version more and have not run into problems. It works really well through the new MiFlash to get fastboot back (using option 6). Thank you very much.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] z45123qqq:
I have a quick question when the new updates are available is there a quick instruction on how to install the new updates when you have used the tool to root. Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
You cannot. If you're rooted you have to restore to stock first to apply OTAs.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] z45123qqq:
Thank You I heard people are having issues rooting the new update is that true.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] fuzz_33594:
I have been in ZTE beta testing with an unlocked bootloader. Downgraded from B25 to B19 because of problems noted in the OP. Preview failed to download TWRP & SU, stable version downloaded & installed items without issue. ADB connects fine, but fastboot fails because ZTE removed it in Nougat. Tried unlock bootloader to see if MIFlash had boot image with fastboot, but had no luck. I can go back to MM, but wanted to know if there is a method in the tool that I am missing to get fastboot. Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
It should have worked. The unlock package that comes with the preview has both the aboot and fastboot. All you had to do was flash it and the toolkit does the rest.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] fuzz_33594:
Thanks for the quick response. I'll try again later today.

Edit - After restarting both laptop and phone, ran again and gained fastboot. Root worked after I disabled write protection. Thanks for your support - I'll buy you a coke.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] thefiqs:
Hi,

[MENTION=7658623]bkores[/MENTION]

First of all, would like to thank you for this awesome tool.

On the other hand, I would like to ask how locking bootloader works. I understand I need to be on completely stock. But you mean stock ROM and stock recovery? I have a 2017G and want to relock but don't want to brick it of course and now I'm confused what stock do I need. B03 stock MM or B01/B02 stock N? Regarding stock recovery, is the stock recovery same or is it different with different ROM versions? I have a stock system B01 N if I flash it is replacing TWRP with stock recovery but in that case, I will have the annoying message my device isn't safe and I have no fastboot.

I have a backed up stock recovery but backed up on B02 N, is it safe to flash it on B03 MM? Or what steps would you suggest to go back to stock to use the fastboot lock option safely?

edit: flashed B01 N complete, this restored stock recovery, then I flashed "fastboot unlocked mod" with MiFlash, than Locked with your tool. All good. Cheers

Regards,

me
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KoTiX2:
To use this tool is it mandatory to use a windows64 os??

I still have not understand it..

Tnx ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Torske:
turn off volume buttons?

Hey can you teach me how to turn off the volume buttons using this rootkit? I have no idea how to use it and my volume button is jammed so i can only boot into safe mode at the moment, therefore i need to turn off volume buttons. Thanks in advance!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
No it works on 32-bit as well
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Sorry the toolkit can't do that for you that's not the purpose of it :(

If the volume buttons are jammed your only option is RMA
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Whoooo?:
Command line use?

Hi there,

Could anyone please give me some information regarding flashing TWRP Recovery to my device.

My problems at the moment is, I am using Controllerboy's '[GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM' and it uses the toolkit from the command line - this doesn't seem to work for me anymore (new, no links, sorry).

Now I am kind of stuck right at the beginning where I'd like to create backup files for gpt, recovery and boot & install TWRP (A -#16-22, also tried the shortcut on page 2 for these steps).

In the guide this is done before unlocking the bootloader - I am aware there might be an easier way from the toolkit menu, but not sure about what that would be and is backup files are created/an unlocked bootloader is needed beforehand.

(I'd like to unlock the bootloader as late as possible, even would be happy with root only - in regards to warranty)

For info, I am on a ZTE A2017GV1.0.0B08 Android 6.0.1 (Stock, Australian version).

Thanks a lot for your help! :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KoTiX2:
Well I can't unlock the bootloader because miphone.exe cannot run on my win7 32 bit. What am I missing?

Whsre can I find the correct miflash version to install?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Torske:
how to root?

Okay thanks but how do i root the phone tho? I have heard rooted androids can disable the effects of the volume button alltogheter by entering a # before the code in the rooted system.