yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lilbluemirage:
I have a 2017U locked bootloader and I'm on B29. I have the same black screen issue... I'm not sure I got lost along the way as well...

After backing up the GPT, Boot, and Recovery:

Downloaded TWRP (tried the lastest 3.0.4), renamed it to recovery.bin, and used command axon7tool -w recovery. The write shows successful, but i'm unable to boot into twrp... Am I missing something..?

Maybe I need tenfars twrp 3.0.2-2? I'm having a difficult time trying to download that.... anyone got a mirror?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
https://we.tl/dv78KwQZCY
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shia786:
Yeah download twrp 3.0.2.2 from the bellow link, that should fix twrp issyez but to get unlocked bootloader you need to downgrade to b20 and then follow procedures in the post under guides

The issue here is the official twrp requires unlocked bootloader which is why you get the black screen
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
EDIT: disregard
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shia786:
No because tennar tool requires .Bin file, to be honest i would recommend tenfar tool, i think it's a bit better and simple to be honest
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
I'm trying to run this and I get:

C:\Program Files (x86)\Minimal ADB and Fastboot>tool -r boot
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
Reading boot ...
F: failed to open boot-backup.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.

EDIT: Nevermind, ran the tool as admin in w10 and it worked. Managed to backup gpt recovery and boot with no problems.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] `SBR`:
you shouldnot use it from the ADB Commnad.

Download the axon 7 root file from the OP and extract to a directory, Shift + right click on the folder will have open in command window, then use the syntax as used in the OP.

first try to take backup and see it connects correctly, then flash the file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
yeah it worked just fine after running it as admin

Now I gotta know if I can flash the signed TWRP to a B15 (Nougat) A2017U with locked bootloader.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] `SBR`:
there are mixed reviews with TWRP booting up in Noughot, you should wait for sometime, as you're in locked boot loader there are less chances to revert if something screw-up
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
I took the risk... twrp boots fine but Nougat wont boot. It's stuck in the ZTE screen.

Should I unlock the bootloader? Or flash B29 from ZTE?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cyberwolf2:
I entered EDL mode on my axon 7 G , but when i try to do read command axon7tool -r gpt ist says failed to connect...what i did wrong?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Make sure you have the drivers installed.

Check device manager and see if your phone is there.

If not:

Setup instructions for Win64:

1. Download zadig from http://zadig.akeo.ie/

2. Put device in EDL mode.

3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.

4. All done!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cyberwolf2:
What exactly do I need to Edit?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sgarrand:
Did you get it installed and working?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Not the official one, no. Just lineage os. I didn't try stock after the bootloader unlock.

But I found out that the reason it wasn't booting was because I allowed system modifications via TWRP. That creates a boot loop with stock nougat.

It booted fine a couple of times and then a boot loop because of that.

You should be fine if you don't enable that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] z45123qqq:
Will this work With b15

I just want to make sure this will work with b15. Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
Read the last page of posts.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] george241312:
So.... wheres the recovery link ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
I think there are a few links in the thread.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tupurl:
Hi tennear, I'm a newbie to this, but when you say the tool writes raw partitions to the PC, does this mean that I can use it to write the raw partitions to a PC then run a recovery software such as Recuva, Testdisk, or Photorec to recover data from the image?

Thanks in advance.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jabeth407:
system based programs

You can only use it for boot & recovery as it indicates at the beginning of his thread. Sorry dude, you'll have to get a nice recovery image, set up your favorite system with your goodies, make a backup with your nice recovery image onto a separate drive then mess it (system) up and have the ability to recover it from the recovery software using offsite storage.

Hope that helps, it seems people like to think information sould either be self-evident or kept hidden, never explained or exposed. Using someone else's property for benefits is a form of enslavement if one depends upon the use of said property for one's benefits, even a paperbased monetary system which presupposes someone is on top of the[ir] paper pile printing what all the rest of us call "money". I'm just saying, not everything is as it meets the eye; there are corporations (governments & their(?) banks... who exactly?) doing things they don't want exposed, or they just want to keep hidden under the guise of protecting you. These various creators of current operating systems and their structured "devices" they're (OS) running on are of the same mentality; keep some stuff hidden, provide enough information to you to get you hooked in.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MacLaughlin:
I have a problem. I just flashed the new Nougat Update for 2017G. My bootloader was already unlocked and I had root access. Sadly my TWRP got overwritten and now I'm stuck at EDL Mode with this error message: C:\Program Files (x86)\Minimal ADB and Fastboot>axon7tool -r gpt boot recovery

Connecting to device...

S: failed to read command

S: Failed to receive hello

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

what(): error: Unknown error

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

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

Hope somebody could help. I can't live without my TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MacLaughlin:
My device is recognized like the picture depicts in the attachement. I'm not quite sure what happened. Is it a simple driver problem?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Drackyen:
Having Trouble

EDIT: I fixed my problem, and I am posting the solution.

If you have a locked bootloader and are trying to install TWRP, this tool will ONLY work if you flash tenfar's signed version. All other versions of TWRP will give you a black screen when you try to boot into recovery.

The dev-host link posted in his guide doesn't work - the green download button downloads malware, the blue one times out.

To get this TWRP, you need to use a mirror. Here is a link that currently works (which I found in this guide).

PLEASE ALSO NOTE that this specific TWRP version has issues wiping IMEIs when restoring EFS (see earlier posts in this thread). You will want to unlock your bootloader then replace it with a different TWRP version ASAP, but you need to use this one to unlock in the first place.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Can someone please tell me what the device has to be listed as under device manager in order for the tool to work correctly? Is it QUSB__BULK or something else?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcus.linkenbach:
Good morning ?

I need some help. Updated win7 to win10 and reinstalled Qualcomm drivers an everything. But now everytime I try to flash recovery it connects and crashes after 3 seconds. What is this? Do I have to downgrade to win7 again?

Send from ZTE A2017G using Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcus.linkenbach:
Send from ZTE A2017G using Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcus.linkenbach:
solved

solved: was my fault. It wasn't an admin shell. :eek:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gaijin1%:
Now there is a new bootloader unlock listed at the Axon7tool thread. https://xdaforums.com/axon-7/development/tool-axon7toolkit-t3573108

I could unlock the bootloader with the Axon7tool on my A2017G with Android 7.1.1 b02.

After that I installed the LineageOS 14.1 (Android 7.1.1 closer to Android stock than the mess ZTE threw at us)

With it I have everything I wanted.

★Daydream (not available on lower than Android 7.1)

★Ability to turn off the lock screen (Security - Screen lock - None)

★Live wallpaper

★Root

▪ Multiple user support

That is the order to do it. With the Axon7tool you can unlock your bootloader and it will install the Recovery (TWRP for Axon 7) used to flash LineageOS. Thread here:

https://xdaforums.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Failure to connect on Ubuntu 16.04

Hi, thank you for the tool and for the instructions on how to use.

I am on Ubuntu 16.04 and have the A2017G model (A2017GV1.0.0B08) on Android 6.0.1 (just got it yesterday) where I am trying to unlock the bootloader and install TWRP.

I have followed your instructions at the start of the thread, and specifically:

- adb devices works and lists my device.

- I am listed in the group plugdev.

- lsusb also lists my device and I have added the device id etc... to qcom.rules, 51-android.rules and 69-mtp.rules (/etc/udev/rules.d)

- my device boots into edl

- running the linux version of the tool then gives a failure to connect.

- lsusb no longer lists the phone., although there is now a Qualcomm device with a different id.

Any ideas? Any help is warmly welcomed.

Thank you,

Piet
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] perrin4869:
Error in linux

I have the exact same issue on Slackware... Anybody found a fix for this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jdlark:
Trying not to add to the noise here, but maybe this is useful info: I'm getting the same behaviour on Debian testing, however on a different machine with Debian unstable it works with no issues whatsoever.

I couldn't figure out why this is so, since they have the same kernel version, and all libraries open()-ed by the tool are the same version as well. Dmesg shows:

## adb reboot edl
[ 2243.539320] usb 2-1.3: USB disconnect, device number 12
[ 2243.762025] usb 2-1.3: new high-speed USB device number 13 using ehci-pci
[ 2243.873804] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9008
[ 2243.873808] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2243.873811] usb 2-1.3: Product: QUSB__BULK
[ 2243.873813] usb 2-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 2243.875504] qcserial 2-1.3:1.0: Qualcomm USB modem converter detected
[ 2243.875657] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB0

## ./axon7tool-1.5-linux -r gpt
[ 2303.662581] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 2303.662673] qcserial 2-1.3:1.0: device disconnected

P.S.: thanks for the tool [MENTION=7890973]tennear[/MENTION].

Later edit: I have compared the straces from the two machines, and I couldn't find any obvious difference. Just...

< write(1, "Connecting to device...\n", 24) = 24
< read(6, "\1", 1) = 1
< poll([{fd=6, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLOUT}], 3, 500) = 0 (Timeout)

> write(1, "Connecting to device...\n", 24) = 24
> read(6, "\1", 1) = 1
> poll([{fd=6, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLOUT}], 3, 500) = 1 ([{fd=9, revents=POLLOUT}])

Maybe it really is just a simple timeout? The machine where it works is indeed more capable than the failing one (Core i7 5th-gen vs 1st-gen I think, plus USB3).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Flapjack:
I'm getting pretty much the exact same thing, only in Windows.

c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] fbusarello:
GPT header parse fail

I've done backups of gpt, boot and recovery with this tool and after a lot of mess i've got a brick. Now I try to write the boot or recovery images and the tool returns:

Writing boot...

bad gpt header

GPT header parse fail

Cannot read GPT

Is there a solution?

Thanks guys
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheBigJ:
Hi tennear,

somewhere in the thread you mentioned a Mac Version of the tool. Would you be able to upload this?

Today I tried unlocking the bootloader of my new Axon using a Windows VM but was already failing at getting the phone to show up as a usb device. Hence no adb communication :(

However under the mac os, I can at least see the device in the adb device list.

Thank you!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BigCountry907:
I need a backup of the GPT partition Table.

This tool creates a backup of the backup gpt which is different than the primary gpt.

Anyone of you that have root access can accomplish backing up the GPT very easily with ADB.

Start an adb shell.

Type commands as follows.

adb shell

su

dd if=/dev/block/mmcblk0 of=/sdcard/GPT.bin bs=1 count=17408

This copies the first 17408 bytes of the emmc which is the GPT Partition Table.

You may need to adjust "sdcard" to be the name of either the internal or external sdcard.

I appreciate the help from you guys.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] faxme:
A2017 ZTE_A2017V2.0.0B08 >>>>Convert to A2017U

I have a A2017 with rom update at the moment "A2017 ZTE_A2017V2.0.0B08" I need good help how I can convert to A2017U.

I spent the whole night using below steps but does not come further than STEP 8 :

Step 1: Enable Developer options in phone by tapping the build number

Step 2: Enable OEM Unlock in phone (is this needed?)

Step 3: Enable debugging (for adb)

Step 4: Connect phone to PC

Step 5: Download Zadig

Step 6: Install Zadig

Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)

******Step 8: Enter the command “Adb Devices” to reassure your device is detected******

I do receive certain number when check with above last commando. I assume contact is lost thereafter because as soon as I try to use Axon7tool to create backup of gpt (1st) then I see the below (of course still in EDL mode):

No Device found

Anybody know the best step to get this done looking at my Rom version (A2017 ZTE_A2017V2.0.0B08).

Could it be that it has been blocked to make CONVERTION A2017 >>>>>>>>>A2017U impossible?????
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kantastisch:
I really need help!

I rooted my phone longer ago and the BL was unlocked, but I wanted to relock it because I wanted to sell the phone.

I just bootet into bootloader and typed in "fastboot oem lock" and then everything stopped working. I can't boot into the recovery or bootloader anymore. It only shows the ZTE logo for 1-2 secs and then it disappears.

I use the A2017G model and my PC is recognized the Phone as QUSB BULK, even when the screen turn off again.

EDIT: After I installed Miflash I get recognized as com10 and in the device manager I get recognized as QDLOADER 9008
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alien0101:
I am also facing the same issue . Can someone post me link to tenfars twrp 3.0.2-2

---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------

Can u please mention me link to tenfar tool?

---------- Post added at 01:01 PM ---------- Previous post was at 01:00 PM ----------

This link is not working ,Can someong plz post new link to this file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alien0101:
I am able to flash twrp but when I try to go in recovery it shows ZTE logo and then black screen.I have tried different Twrp versions

twrp-3.0.2-0-a2017u

twrp-3.0.4-1-ailsa_ii

twrp-3.2.1-0-ailsa_ii

twrp-3.1.0-0-ailsa_ii

I have 2017U model and I am using it in India, so it means its bootloaded is already unlocked? Do I need to unlock it before flashing twrp?

C:\adb>axon7tool.exe -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 ...

log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive 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 ...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
You have to disconnect the USB cable before the countdown ends. After that just hold the power button until it reboots and then use volume down to enter TWRP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alien0101:
Do I need to unlock before flashing twrp. or unlocking is mandatory for rooting device?

Also if I unlock, will it erase all my data?

What is best tutorial for unlocking?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alphie:
Same issue with recovery not sticking

I'm getting exactly the same symptoms. Everything appears to work, but not matter what I do after the countdown, I can't get into TWRP. If i hold vol up I get into EDL mode again. If I hold vol down I get into the factory mode. If I do nothing, I get the Axon boot logo followed by normal boot. Could it be that this tool no longer works with the latest stock ROM?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Of course, you'll DFU brick your phone otherwise!

Some guides actually point you to flash TWRP first, then flash some files to get fastboot, then unlock. That is fine, but ALWAYS UNLOCK BEFORE DOING ANYTHING OR YOU'LL HAVE A DFU BRICKED PHONE

---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------

Did you read my post above and try? I've used this thing a bunch of times and that's the way to make it work.

Just after disconnecting the cable your phone will still be in EDL mode. Hold Power for a lot of time (easily a minute or two), if it doesn't reboot on its own release the button, wait 5 secs, then hold it again. It should get out. Right when you see the red LED you have to hold Volume up before the ZTE screen appears, and then you'll get to TWRP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alphie:
The recovery flashing is successfully wiping out the stock recovery. Any attempt to get into recovery will lead to EDL mode. My guess is that this is the failure mode when the phone tries to load a recovery then finds that it's invalid. Could it be that I need to try a different recovery image? I'm using one called twrp-3.0.2-2-a2017u.img which someone on this thread said was signed, but who knows.

I can recover my backup recovery to get back to stock, but that's it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] alien0101:
what is the easiest tutorial for unlocking it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BaamAlex:
With the Axon7Toolkit
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
CMD Errors

[IMG="screenshot"]https://imgur.com/xJ8zqzw[/IMG]

Hello! SO I followed the instructions to the letter but am still having an issue with the tool. (I already enabled OEM Unlocking and USB Debugging) I installed the universal adb drivers and set up the adb/fastboot tools. After restarting my pc, I downloaded and placed the newest twrp image (renamed it to recovery.img and recovery.bin) in the tools folder. As well as the axon 7 tool (renamed to axon7tool.exe). I then added the file path to the environmental variables as shown in the picture. I then opened the command prompt from the file location and proceeded with "adb devices" followed by "adb reboot edl" which I then used zadig to install the windows drivers. The pc recognizes the device as ....BULK but then I enter "axon7tool -r gpt" into the command prompt, I get the "not recognized as an internal or external command" error. Any ideas?

imgur.com slash xJ8zqzw
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
After entering CMD you have to go to the location where axon7tool is. Say that you have it in C:/adb, you have to do this:

input 'cd..' (with 2 dots) until you get to C:/

then 'cd adb' (adb being the name of the folder that axon7tool is on)

then try axon7tool

Or you can shift+right click on the folder where axon7tool is, then use 'Open command prompt here' or 'powershell'
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Sorry if I wasn't clear, but in my post I said I opened the cmd from the file location.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
try writing axon and hitting tab. if the name is autofilled it's right.

maybe you might need to write it as axon7tool.exe
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
That fixed it! Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
SO I have encountered another issue. I have lineageOS installed, but upon first boot it asks for a password to start android. I never set a password. Any ideas?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Figured it out. Turned out this tool doesn't work on my Axon 7 so I had to us the MiFlash tool. I re-flashed stock android B19 onto my phone, then reinstalled TWRP and then installed Lineage with no issues!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
No, it was because your data was encrypted. Just formatting data fixes it lol, it was much simpler
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Tried formatting the data in twrp multiple times using other forums advice, but to no avail. Thus my solution.