yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] The Great B:
Thank you for your answer! I uninstalled every driver and installed the winUSB and while zadig lists the device and QUSB now, the device manager does not and the axon7tool fails. What else can I try?

----edit: After trying it again and again it finally worked... However, I was unable to find out why

----edit2: Having got a permission denied issue at step B) 8), I tried part B while my device in TWRP but it can't connect to adb. Should I do the dd commands from the TWRP's terminal? Which driver do I have to install for TWRP to work with adb if it is possible?
[ZTE Axon 7 Guides, News, & Discussion] neverthemore:
So any help help from now on would be awesome!

I am stuck on fastboot oem unlock. Right now it reads waiting for any device.

I tried uninstalling the Android from Device Manager and reinstalling the WinUSB drivers from Zadig with no luck.

I tried killing the adb.exe from Task Manager with same zero luck.

I also tried changing to another USB port - no, nothing, zero!

Any idea?
[ZTE Axon 7 Guides, News, & Discussion] bacomino:
Hello everybody... Can anyone help me ?

I uninstalled any drivers, re-flashed B10 [A2017G], used "zadig_2.2.exe" and here is what I get at this step (nothing's successfull :confused:) by sending "axon7tool -w recovery" command :

Connecting to programmer...

log: Supported Functions: program configure nop firmwarewrite patch setbootables toragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors

log: Supported Functions: program configure nop firmwarewrite patch setbootables toragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors

Writing recovery ...

log: Supported Functions: program configure nop firmwarewrite patch setbootables

toragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors

Success!

Reset in 5 seconds ...

Reset in 4 seconds ...

Reset in 3 seconds ...

Reset in 2 seconds ...

Reset in 1 seconds ...

Thanks a lot :o
[ZTE Axon 7 Guides, News, & Discussion] Controllerboy:
You say nothing "works". What do you mean? What happens when you reboot your phone after the process? Are you presented with a black screen when trying to enter recovery? If so, try the recovery.img found in this file (don't use anything else from the file!)
[ZTE Axon 7 Guides, News, & Discussion] neverthemore:
So basically until I am in TWRP it reads ADB Interface in Device Manager and as soon as I execute Adb reboot bootloader the phone enters Bootloader and now it reads Android in Device Manager.

At this point if I execute Fastboot oem unlock it stays on waiting for any device and nothing happens.
[ZTE Axon 7 Guides, News, & Discussion] bacomino:
Well, nothing change : I'm still on stock recovery exactly like if I haven't done anything...

I see the file is named B03, can you confirm me that I can use it (I'm on B10) ?
[ZTE Axon 7 Guides, News, & Discussion] Controllerboy:
Do you posess another win64 computer or have a friend with a win64 PC? If so, retry on that PC. Some users have reported success after trying the process on a different PC.

The A2017G MiFavour version shouldn't matter as long it's not Nougat. The signed recovery is accepted by all Marshmallow versions.
[ZTE Axon 7 Guides, News, & Discussion] bacomino:
I'll try it ASAP ;)

Thanks a lot...
[ZTE Axon 7 Guides, News, & Discussion] ileikpi:
Try using a different computer. I had the exact same problem when using my computer and no matter which usb port I tried I kept getting stuck at fastboot oem unlock. Doing it on a friend's computer solved the issue for me.
[ZTE Axon 7 Guides, News, & Discussion] neverthemore:
Really?! I already tried another laptop but encouraged by you I tried a desktop PC and voila - I am on RR now. Thanks to you, Controllerboy and all the Devs.
[ZTE Axon 7 Guides, News, & Discussion] ileikpi:
Nice!!
[ZTE Axon 7 Guides, News, & Discussion] bacomino:
Hello... I tried an other x64, an other OS and the 2nd file.

I've got the same problem :(

PS : I had this file on my computer but it was impossible for me to DL it from your link...
[ZTE Axon 7 Guides, News, & Discussion] yunowork:
I did follow the guide to the point where i reboot into recovery after having flashed twrp, all i get is a black screen which leads to me having to flash back to stock recovery. How do you proceed at this point? This really bothers me because to me it still appears that the axon7 is a pain in the ass to flash. Isn't there a more comfortable solution?
[ZTE Axon 7 Guides, News, & Discussion] dnlilas:
Hello,

I am also newbie on Axon 7 (not owner yet), but by reading somewhere this information :

"DO NOT use TWRP version other than tenfar signed TWRP 3.0.2, otherwise blackscreen on recovery. You can upgrade TWRP after you unlock bootlader".

So maybe you use a wrong TWRP version?

---------- Post added at 05:53 PM ---------- Previous post was at 05:44 PM ----------

Hello,

In section A) (flash only TWRP on stock phone), I do not see warning (step 24 of section A) about problem rebooting phone if one allows TWRP to modify system at it's first start screen.

Because I read some scareful warnings:

From search: "WARNING: The ZTE Axon 7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!".

From TWRP site: "This device uses dm-verity!

This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."

Please advise, thanks.
[ZTE Axon 7 Guides, News, & Discussion] zdravke:
I'm stuck at this point:

C:\adb>axon7tool -r gpt boot recovery

Failed to connect

I tried shutting down and plugging usb in while holding both volume buttons. At first, I was able to see QUSB_BULK device and driver started installing. It completed without errors, but then QUSB device disappeared from device manager and is not coming back no matter what I try. Rebooting into edl with adb does not seem to work either.

Neither method is now producing QUSB device in device manager, and axon7tool fails to connect.
[ZTE Axon 7 Guides, News, & Discussion] ChrisFFM:
No "adb devices" found

Wow great! My old post was killing after submit, grrrrr... Ok, then try again ;)

I've a ZTE Axon 7 (A2017G - for german guys like me). Currently, i use the b10 Original ROM, but now, i've some trouble with fastboot and/or adb.

At first, the b09 custom ROM from tron1 was installed with twrp. At this time, i hadn't the unlocked bootloader. After long nights, i've removed the lock for the bootloader, so by now, it's unlocked. So far, so good. After unlocking, i've installed the b09 again, cause i had some trouble with the data-partition. It's ok, cause i've backed up my system completely before with twrp (3.0.2-2) and restored successful. After restoring, i was living in a nearly perfect world, buuuuut..... now i've installed the b10 Stock-Rom (without root) and the problem was, that twrp was replaced by original MiFavor recovery. Ok, not so good. But in this case, i can install the original nougat ROM (7.0). This was the next step. Nougat wasn't fine for me, cause i have no root and a lot of information were missing (passwords, websites, todo's, contacts). The result for me was, that i will go back to the old version b09 with all my backed up data. But now, i cannot connect via adb.

If i start Windows 10 Pro x64 i found the device via adb if i enter "adb devices". But if i enter "adb reboot edl", the phone restarts to the black screen (it looks like shutted down). If i enter "adb devices" again, adb didn't found anything. With fastboot, i've the same problem. So now, i haven't any chance to re-install twrp to restore my backup.

I know, that here, there exist a lot of android-experts and i hope, anyone can help me in this case.

Many thanks in advance.

Chris
[ZTE Axon 7 Guides, News, & Discussion] tron1:
You can try to install the old B03 stock image from ZTE. The old bootloader is able to do the edl stuff, also fastboot is in a more usefull state.
[ZTE Axon 7 Guides, News, & Discussion] ChrisFFM:
Succesful !

Hy tron1. Many thanks for your feedback. I selected a different way to solve this problem. I remembered, that in 2016, i've used the axon7root to replace the original recovery image with twrp and now, i do the same and voilá ! Perfect! After then, i restored my "old" ROM (YOUR ROM ;) b09_stockrom_tron1.img) and now, nearly all is perfect.

The once problem i have is, that the display lock needs any unknown pattern. The Finger Print Sensor works regular, so i don't have a problem. I cannot change the display pattern. In Android Device Manager, a change isn't possible, cause the pattern is active. Changing with regular password entry isn't possible. I don't know. I hope, i will find a solution. This is the last bad case i have. The rest is fine (again) for me.
[ZTE Axon 7 Guides, News, & Discussion] Controllerboy:
Delete /data/system/locksettings.db.
[ZTE Axon 7 Guides, News, & Discussion] Dust2Dust:
I got the recovery done whilest on B08, no fuss ;)

But whatabout unlocking bootloader on B08, should that work as well or is this were I start thinking to go back to B06 or B03?

I have all the bits backed up, but the bootloader is a bit tricky. I prefer the way Xiaomi is providing a official unlock :)

Besides, without unlocking BL, would I be able to flash super su ?
[ZTE Axon 7 Guides, News, & Discussion] Tebor:
[MENTION=4464865]Controllerboy[/MENTION]

Thanks for your guide. With the backups the tool makes, how do we restore these?
[ZTE Axon 7 Guides, News, & Discussion] Controllerboy:
I think you'd just need to use axon7tool again to write the backups back to the phone. E.g. rename the backupfiles to "boot.bin", "recovery.bin" and "gpt.bin" and execute "axon7tool -w recovery", "axon7tool -w gpt", "axon7tool -w boot". If you want to be 100% sure ask the maker of the tool [MENTION=7890973]tennear[/MENTION]
[ZTE Axon 7 Guides, News, & Discussion] DeJe63:
One exception, you can't write back gpt. That's a bad idea anyway. ;)
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
[MENTION=4464865]Controllerboy[/MENTION]

i had this file for a while and seems like is been use in different sites, so why just added here to your guide, file is TWRP flashable zip with all necessary files for unlock bootloader on the G. similar to the one posted just with a extra file.

TWRP_UnlockBootloaderPackage_by_DrakenFX.zip
[ZTE Axon 7 Guides, News, & Discussion] nonamesl:
Hi.

I have the same problem but it's slightly different and I have no idea how to solve it.

When I use adb reboot edl it shuts down my phone, and I don't see it in device manager, or at least I can't find it because I don't really know where to look there. And, it's without the LED and axon7tool says "Failed to connect" when I try to run it using axon7tool -r gpt. Have tried this multiple times, always same result.

When I disconnect the phone from the USB, shut down the phone normally, and plug it in while clicking both volume buttons simultaneously, the phone is still off with the black screen but it's with the red LED.

BUT,

the adl devices shows no devices, and axon7tool -r gpt shows both "Device not detected" and "Failed to connect".

What do I do? I tried both the ways multiple times and no success so far.
[ZTE Axon 7 Guides, News, & Discussion] ilinirwan:
I just wanted to install TWRP, unlock BL and root my phone. So I just need to do all the step till before the custom rom part right. Unlock BL and flash TWRP? After that do I need to flash supersu zip?
[ZTE Axon 7 Guides, News, & Discussion] No Kit:
I get the problem with "QUSB_BULK" not showing up.

As soon as I go into edl mode, the axon disappears from the device manager, and command window says "Device not found".

I have tried two computers, one with Windows 10 and one with 8.1, so I'm now kinda stuck.

I'm on B08 so maybe that's where the problem lies?
[ZTE Axon 7 Guides, News, & Discussion] keessonnema:
I want to make sure this works on b08 before I do anything. Could anyone confirm?
[ZTE Axon 7 Guides, News, & Discussion] Dust2Dust:
Confirmed for TWRP only on B08, also still waiting for a confirmation from the dudes.
[ZTE Axon 7 Guides, News, & Discussion] Controllerboy:
Updated the main post to reflect changes noticed by users. Changed link to TWRP to the official version to avoid people bricking their devices by restoring EFS backup using crappy TWRP version.

I am not 100% sure this will work with B08 firmware, but I don't see why it shouldn't. It worked with all other firmwares. I think only Nougat will bring deep changes which might make this tool redundant. Also, having B08 shouldn't exclude you from booting to EDL and connecting as QUSB_BULK. It surprises me some people don't seem to be able to get it to connect as "QUSB_BULK". Uninstalling Qualcomm drivers and reconnecting should be enough, don't know why it behaves so different on different Windows machines...
[ZTE Axon 7 Guides, News, & Discussion] BIGWORM:
Did you need any confirmation on this guide working for b27? I used this guide on b27 as my phone came stock with it.
[ZTE Axon 7 Guides, News, & Discussion] MahathirMohamad_:
Tried to reboot to EDL, but my phone just shut off and the red LED light didnt came on. On my Device Manager, it doesn't detect my phone as QUSB_BULK but as Qualcomm HS-USB QDLoader 90008(COM3). Any help? Tried so many times but it didn't work.

Edit : Manage to install TWRP after downloading Zadig, but when following the steps to unlock bootloader, some parts of it I get " Permission Denied ". I wonder why no one has ever make a video tutorial. I think its easier for people to do it visually looking on how it is done.

Edit #2 : Manage to unlock Bootloader. I've manage to find another thread on how to unlock the bootloader, and it states that you need to be in TWRP while doing so which in this thread, it didnt mentioned here and I guess thats the reason why I've been getting errors on CMD. Now the problem is whenever I tried to flash CM13, I would get failed or any red letterings.

Edit #3 : Manage to Install CM13. Didn't know what I did differently but it manage to flash. Now its time to test it :)
[ZTE Axon 7 Guides, News, & Discussion] Diplodocus123:
Will try the BL unlock on my b08 later. Fingers crossed.
[ZTE Axon 7 Guides, News, & Discussion] keessonnema:
Keep us posted :)
[ZTE Axon 7 Guides, News, & Discussion] Diplodocus123:
Well, I cannot enter edl mode. The screen is black and nothing happens.

---------- Post added at 11:58 AM ---------- Previous post was at 11:44 AM ----------

Okay, I have installed TWRP with Zadig. But if I try to boot into it, it only shows a black screen...any idea what I should do now?
[ZTE Axon 7 Guides, News, & Discussion] Xadro:
So i tried to get TWRP on my A2017G with B08 firmware, everything went well until after flashing recovery. Neither the official nor the unofficial TWRP will boot for me. Whenever i try to boot to recovery, the screen is remaining black. If I roll back the backup made with axon7tool, i can boot to stock recovery again. So having no access through TWRP i can't go ahead to BL unlock or root. I'm a little out of ideas here. Any help much aprechiated.
[ZTE Axon 7 Guides, News, & Discussion] keessonnema:
Ok so both of you have the same problem with recovery. strange.
[ZTE Axon 7 Guides, News, & Discussion] Xadro:
So i poked around a little more. The recovery in this thread is working for me. Not too sure, but i think this is the infamous recovery with the EFS issues. So no tinkering with EFS with this one guys. :)

So i'll go ahead make a backup and try to unlock bl and root.
[ZTE Axon 7 Guides, News, & Discussion] Diplodocus123:
Its not working for me. Or Ive downloaded the wrong one...not sure.
[ZTE Axon 7 Guides, News, & Discussion] Perhogan:
error while flashing Lineage OS

Similar to other users in the thread i got the error:

TZ version TZ.BF.4.0.1-00315 assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1"

I am sure i installed the A2017G but then I got lost in the conversation and not sure what to do now :confused:

:( :crying: Additionally While trying different "wipe" i accidentally wiped the old System. so i am now stuck with a just bought phone with TWRP only ... can you help?

Thanks in Advance

Andrea
[ZTE Axon 7 Guides, News, & Discussion] Mr.Sack:
Thanks alot, this works to unbrick the A2017G version. Now I didn't waste 450 euros...
[ZTE Axon 7 Guides, News, & Discussion] Perhogan:
Same here many thanks!
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
lol i wasn't expecting that

[MENTION=4464865]Controllerboy[/MENTION] Not wanting to bother too much, but it would be nice if you could add what I wrote before on your post. People are having the problems I described there
[ZTE Axon 7 Guides, News, & Discussion] Controllerboy:
Woops, I had missed that. I edited in your reccomendations. Thanks!
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
uuhh flash B03 from the official ZTE website?

You could try to flash N modem and then lineageOS too
[ZTE Axon 7 Guides, News, & Discussion] Perhogan:
Solved thanks!
[ZTE Axon 7 Guides, News, & Discussion] senny22:
20) In command, type "axon7tool -w recovery"

This is were things stop working for me. I get the following error along with "axon7tool.exe" crashing:

C:\adb>axon7tool -w recovery

Connecting to device...

Sending programmer...

Connecting to programmer...

log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors

log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors

Writing recovery ...

F: failed to open recovery.bin

terminate called after throwing an instance of 'std::runtime_error'

what(): error: No error

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

What could be wrong here? I am on A2017G and B06.
[ZTE Axon 7 Guides, News, & Discussion] dnlilas:
[MENTION=8175513]senny22[/MENTION]

You were missing step 7):

"7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img""

You must rename the twrp_rec_tenfar.img to recovery.bin, since the command "axon7tool -w recovery" expects to find recovery.bin file in the same directory.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Did you read the bottom of the OP before asking? I had the same problem, you simply have to uninstall

the drivers, then reboot a couple times or whatever. Just read the part where the error is mentioned
[ZTE Axon 7 Guides, News, & Discussion] senny22:
I did put the following files in the adb folder: "recovery.img" and recovery.bin." see: "https://gyazo.com/5f5cf1b87ff4e325a05f5d0591b07cbe"

Is there something i'm missing here?

---------- Post added at 07:12 PM ---------- Previous post was at 07:03 PM ----------

i've read through this whole thread without succes. I assume you were talking about this part?: If axon7tool fails with a what() and STD-exception and whatnot - if you installed the Zadig driver

Go to Device Manager, right click QUSB__BULK and Uninstall, then use the "adb reboot edl" command. Install the winUSB driver via Zadig. Reboot the phone by holding the power button about 10 seconds. Enter the command adb reboot edl again. Enter "axon7tool -r gpt boot recovery" in command.

In that case then i've tried reinstalling the drivers and rebooting as stated above and yet the problem persists.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
[MENTION=8175513]senny22[/MENTION] What Android version are you running? The thread was written for Marshmallow, so it might not work with Nougat and the missing fastboot mode abd stuff. Try another computer if you can. Maybe try axon7toolkit from bkores (google it)
[ZTE Axon 7 Guides, News, & Discussion] senny22:
I'm running android 6.0.1. A.k.a marshmallow.

---------- Post added at 10:28 PM ---------- Previous post was at 10:05 PM ----------

16) In command, type "axon7tool -r gpt boot recovery" and hit enter

This is where my error occurs. The following is shown in command prompt:

F: failed to open recovery.bin

terminate called after throwing an instance of 'std::runtime_error'

what(): error: No error

The fix in the OP did not resolve my issue with this error. What could be the problem?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Hmm. I don't know. Again, try another computer
[ZTE Axon 7 Guides, News, & Discussion] senny22:
I have tried it on my laptop with the same problem.

---------- Post added at 10:43 AM ---------- Previous post was at 09:59 AM ----------
[ZTE Axon 7 Guides, News, & Discussion] chironfr:
good afternoon.

I have an A2017G

Everything went fine.

TWRP is installed

I've flashed the proper modem A2017G_N_Modem.zip

I can't install lineage-14.1-20170327-nightly-axon7-signed

I have an error

checking for tz version TZ.BF.4.0.1-00315
assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00315") =="1"
update process ended with error 7

I'm puzzled...

I've tried first to install unofficial, same problem.

I've downloaded again the files, same problem.

What is wrong? Help...
[ZTE Axon 7 Guides, News, & Discussion] chironfr:
Replying to myself.

I finally sorted it out

First I had to flash A2017X_B15_Universal_Bootloader.zip then I could flash Lineage

The next problem has been the request by lineage of a password I didn't have

Fixed in TWRP by formatting /data in ext4

FINALLY! IT WORKS! YESSSSSSS!!!! :D:D:D (sorry for the capital letters but I'm really very happy)
[ZTE Axon 7 Guides, News, & Discussion] |Furō|:
Stuck unlocking the bootloader

Hey everyone!

First of all thank you all for this guide! If I manage to get through all of this, it`s definitely thanks to you!

Well to get to the topic:

I managed to complete Step A) and flashed TWRP on my ZTE Axon 7 G, which is currently running Android 6 (B10) found on ZTEs Website (I downgraded from 7.1.1) I`m able to boot into TWRP and as far as I can tell, everything seems okay :) (kinda proud so far ^^)

So I started Step B) with my device still connected to the PC (as MTP) and everything went fine until I got to Step 8. There I would get the "permission denied" post. So I scrolled down, noticed the little "NOTE" and tried doing Step B) while in TWRP. But when doing so, I get stuck at point 6 with the following issue:

adb: error: connect failed: no devices/emulators found

I noticed that, when connecting my phone to the pc, while in TWRP it shows up as ZTE A2017U and is using Google Nexus ADB Interface.

Basically I don`t know what to do now. Since I get the "permission denied" issue when booted normally to stock and I get the "connect failed" issue when booted to TWRP.

Any help is greatly appreciated!! Sorry I really am a noob, but the guide seemed so detailed I decided to dare it :`) Hopefully we can get this to a good end. If you need more infomation, ask away!
[ZTE Axon 7 Guides, News, & Discussion] dnlilas:
@ |Furō|

Maybe you can try this toolkit which should be easier for beginner :

https://xdaforums.com/axon-7/development/tool-axon7toolkit-t3573108
[ZTE Axon 7 Guides, News, & Discussion] |Furō|:
Hey, just found this as well :D seems like the way to go for me honestly!

But I have to questions:

1. Can I just proceed using this method, or do I have to go back a little (since I already have installed TWRP)

Or what is the exact required state to use it.

2. Is there a kind of tutorial/guide out ther on how to use this toolkit? Or is it rather self explanatory?

Thank you very much for your reply! I really do appreciate it!