yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] StoneTrapper:
I can't say I have any particular experience with DFU tools.

This morning I've been taking a look at the QPST suite to see if there's anything in there to help. It see's the phone in "Download" mode, though as a result of this it seems unable to access anything.

Potentially we could use ZTE Firmware Flasher but there's no partition map supplied in any of the available images and I wouldn't know where to begin in modifying another devices.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
So what causes the phone to flash the ZTE logo briefly, go black, and flash the red LED once or twice before shutting down?

And how does one install SuperSU 2.65? Via zip in TWRP?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] krafter_2k:
DFU issue is the result of following command executed on an Axon 7 a2017g with B03:

axon7root.exe -p X -b -r (where X is your port number)

My advice: do not use both options -b, -r simultaneously, at leas not for now
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
I'm talking about the A2017U, which users EDL.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] diablo900t:
So does this work with US Axon 7's on B27? I'm confused about TWRP asking for passwords and have been hesitant to try this on my phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
My guess is the bootloader (aboot) gets hosed somehow or bootloader can't find boot or recovery. But so far this is only a problem happening to G models. The code there seems to go to different emergency mode (there is a dload mode code in their aboot which is not present in U version, also theirs is missing the fastboot(BL) keypress detection). I don't know if EDL/DFU are selected in aboot or in PBL/SBL. I think i asked someone who flashed the U aboot on the G version if the keys press would take them to EDL of DFU and it would still do the DFU mode. So keypress detection is done before aboot loads, which leaves only PBL/SBL. Looks like both EDL and DFU modes exist on G, so far no one has seen the DFU mode on U version

As far as SU goes, flashing it would be via TWRP but it will mod the boot image i think so you will get boot loop if your BL is locked. You can manually update the su binary though, saw someone do it earlier in this thread.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
Does this method still work on B27?

I tried it last night with the steps provided in OP using the Backup and B27root packages. After flashing TWRP everything is fine but it asks for a decrypt password.

After wiping data all seems good but after reboot and setting up the phone again, the decrypt password prompt is back again.

Has anyone been able to get this working on B27 or able to bypass the password prompt?

If not can B27 be unlocked or do I have to go back to B20 for that?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
You need to just pass that screen that asks for a password, then after format data and then reboot to twrp and that screen doesn't come up anymore
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
Thanks. I did what you mentioned above but after rebooting I had to setup my phone again,which is fine. But when I go back to twrp to flash SU or xposed, the password is there again.

Do you have it working on yours ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
Yes, it worked as in the password screen went away, but I was not able to flash super SU. I am on the U variant and locked bootloader. Many have not been able to flash superSU via twrp with locked bootloader. But [MENTION=3044858]DrakenFX[/MENTION] is experimenting with a few things to remedy this. I currently went back to full stock. But yes it rehashed the credentials twrp was looking for after the reset for me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nickcaper:
I just bough this phone... I have a feeling Im gonna screw it up playing with it and not beable to restore it. It dont seem like there is a straight answer in regards to HOW to root this thing.

Is there any way to restore the phone to factory by using some program and a copy of the factory rom?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
I just received my china version 6gb/128gb... Rooted + TWRP successfully installed.

EDIT: Ran into same problem as a bunch of others with that stupid TWRP password prompt :/

I did the following in exactly this order:

1) Flash boot.img for root

2) Reboot to stock recovery

3) Factory reset, then power off from here

4) Flash TWRP, reboot into TWRP

5) Format Data, reboot into TWRP

6) Reboot into phone for the first time ever, go thru initial setup, install Google Framework etc by sideloading apk's, enable Google Services to autostart, install Play Store

7) Download phh Superuser, test root via rootchecker.... root works.... SO FAR SO GOOD!

8) Enable Developer options, enable OEM Unlocking, enable USB Debugging... disable write protect w/ 'adb shell reboot disemmcwp'

9) Install latest BusyBox after reboot.... notice that BusyBox actually installs, so Step 8 actually worked...

10) Install Xposed Installer apk, copy xposed framework zip file onto storage

11) Reboot to TWRP to install Xposed..... NO U, PASSWORD PRRRRRRRZ HUEHUEHEUHEUHUE!

....Where did I go wrong? Once again this is on the chinese A2017 6gb/128gb model...

Oh, and TWRP is the 3.0.2-2 version... so unless there's a newer one....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
Well, I've got a U model that's running into the black screen / blink-once LED issue. It's easy enough to fix, I was just curious.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
Can you post your TWRP recovery.log if you can save it to SDCard, let's see what it says. BTW, have you setup lockscreen or FP during your phone setup?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
How do I get this log written? Or where is it by default?

No, no lockscreen or FP setup, its all left on just 'swipe'.

After the initial Format Data, if I DIDN'T reboot to system and rebooted into TWRP again, it could mount the partition just fine. But after the first initial System reboot, the partition gets reencrypted when the phone sets itself up it seems like.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
There is an option is TWRP to copy log to SD card. Also you can pull it via ADB like this

adb pull /tmp/recovery.log

it might also end up in /cache/recovery/log or /cache/recovery/last_log depending

You can copy using TWRP file manager as well to SD card

As far as the encryption, yes the phone will auto-encrypt of first OS run since it's forced encryption by default. And if you do not setup any lockscreen protection it should use "default_password" as password so that it can decrypt on reboot by itself. TWRP also tries this when it accesses the /data. Maybe the log will show us what is going on. OTOH i have ran into opposite problem, where TWRP decrypts the /data with default password even though I have lockscreen protection setup. In this case it should prompt for it, but it does not. This was with stock boot and locked just tenfar signed TWRP. Seem that once boot is changed, this stops working in most cases. Either the crypto footer is missing or has stale data or keymaster cannot be accessed, which the log should show hopefully
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
Heads up. Update B11 just popped up for China A2017 devices.

Don't update yet, obviously...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] krishelnino:
How did you go back to stock? Could you please elaborate?

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
I followed this from what I remember. Or the other thread with img files..

http://xdaforums.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484/page1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] krishelnino:
I am on rooted B27 with LOCKED bootloader. So can I follow that guide and get back to stock? Please let me know
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
Read that linked thread. Tenfars method of installing twrp does not require unlocked bootloader. The info is there and in tenfars thread
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gaby_64:
I cant get my device A2017UV1.0.0B27 to go into edl

adb reboot edl just sends it to a black screen

no qualcomm device appears
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Do it manually,

- Unplug you device from PC

- Completely Turn off your device

- press and hold Volume Up and Down.

- plug your device wait just 5 secs. And check your Device Manager for COM number.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
This was the bit that initially got me too. Do not expect anything on screen, it will simply stay at a black screen.

Just plug it in and check device manager for a Qualcomm device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gaby_64:
it was not working on usb 3.0, switched to 2.0 port and it showed up in the device manager
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] apd:
Silly question - how do we get around this (I'm about to root)? Do we run -b first and then -r?

Other than that, are there any other cautions we need to root the euro one on B03?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] weep22:
Bro i try but show DFU port not qualcomm device is OK?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
Did you install the drivers?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] StoneTrapper:
I don't know how to get around it, though doing both at once has left my phone bricked and stuck in DFU mode. When I attempted one without the other there was no effect.

Considering there's supposedly an official bootloader unlock coming soon to the G model I would try and hold off for now or at the very least look for other methods.

I understand not having root can be a dealbreaker (it would be for me) but take it from me, there's little worse than bricking your brand new phone and finding out ZTE's support couldn't care less if you bought your phone internationally.

Which model do you have? The issue that can happen with the A2017G has been mentioned before and AFAIK there's no fix.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
Just as a note for anyone who cares about the Chinese A2017 ver (6gb/128gb). After rooting and installing TWRP, no matter what you do you will get the password prompt in TWRP.

But you can ignore it, swipe to modify and flash Xposed and it will work for some silly reason (dunno why...). Just don't try to flash SuperSU... THAT won't work.

So now I have root+TWRP+xposed.... probably as good as its going to get for now on this variant/model (A2017) until there's a bootloader unlock since DrakeFX took his down.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
I didn't took it down just hide it you still can see it by clicking , but won't recommend using it yet , till i get some info and redo some steps.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Haz3:
Patiently waiting!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
All good, happy to wait if it means more stability/checks across variants.

You're doing great work mate :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DaCashFlow:
One more question for the A2017G:

I flashed recovery and boot, went to TWRP and set it to write access. After that did a restart, but got a password prompt. Do I need to do a Factory Reset to fix that?

Thanks a lot!

Sent from my ZTE A2017G
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xpakage:
Cancel the request. You should not see it again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Wizpop:
Nevermind,,got it back and going. THanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DaCashFlow:
Unfortunately it doesn't :(

I already tried following steps:

1. Boot in edl mode via adb

2. flash new boot.img (I already have TWRP running, so no need for that)

3. reboot to TWRP & do factory reset & reboot

4. systems starts fine, but stucks again at the encryption password prompt

5. flashed stock boot.img

6. started system, set up system pin (alá 1234)

7. flashed Tenfars boot.img

8. but even then it asks me for a password & 1234 doesnt work :confused:

Anyone running B03 and managed to get root?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xpakage:
I am on B27. Not sure if B03 is why. I also thought you meant TWRP asked for the password instead of the ROM doing it.

Did you format data in TWRP. I would think a factory reset would do that but a data format (if I remember right) removes encryption, which you get back when booting ROM. If all that has happened and it is still asking, I am not sure the next step.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DaCashFlow:
Thank you!

You were entirely right and I made the mistake not to do every step of tenfars instructions. I did not format data, because of that I got the encryption prompt.

At least I needed to invest 2 hrs for research and testing DrakenFX method. So I promise reading properly next time!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DeJe63:
OP should say that you need wipe / format data if you had previously set security above swipe. Just a note why it is needed would save some letters here. ;)

Anyway, thanks for all the work. It worked flawlessly on my A2017G B03.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
It is there.. Look under the last code example in the first post.. Last big paragraph...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DeJe63:
It's there you should do...but the reason is not there. That's what I'm trying to say. ;)

So make it clear why it's needed.

I did not tried. But I can imaging if you clear security settings prior to root this way you don't need to clear all your data...

PS: last not least, disable emmc wp also would be nice to mention.

OK, complained enough for today. ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xpakage:
Just follow the steps in the order written, and how the OP states. Reading the thread will explain why it needs done. If you want to take shortcuts, you will be back asking questions on why something happened.

I will admit I read too fast to be safe sometimes, but there are other times I read 2 or 3 times to be very sure I know what I am supposed to do :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FunkyELF:
source code

Is the source code available for the axon7root.exe?

I'd like to be able to use this from Linux. I'd be willing to compile and test it out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
You're better of using wine for Windows base software.

Source won't be release at all.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FunkyELF:
Unfortunate. Where did axon7root.exe come from? Was it leaked or developed? I see that the files contained in the various zips are different.

Also, I hate the idea of running exe files downloaded from mirror sites where you cannot tell which button is the real download link.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
i recommend you start reading from the following link Page 29 forward, you'll have a better idea why i said " You better off using an alternative way to use Tenfar tools" ...

http://xdaforums.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204/page29
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FunkyELF:
So... I'm getting my phone delivered on Friday and then going out of the country (Germany) on Saturday for 2 weeks.

The question is... when I turn the phone on for the first time and there is a software update should I do it or no? Will doing the update prevent any of these rooting / bootloader unlocking from working?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
If we assume that the error is in the flasher tool, then safest way to do it would be like this

- Flash only TWRP recovery via the -r switch. This so far has not been reported to cause a problem.

- Then from TWRP flash the boot img. This way of writing boot image should be safer if we assume that the DFU mode is due to damage to the bootloader. But if it's because boot image itself is bad...i can't remember if there was confirmed B03 image flash
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] stepw:
It's likely based on emmcdl, see https://github.com/binsys/emmcdl
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] seby1234:
I already unlocked the bootloader and installed the new twrp update on my axon 7 but as soon as I flashed supersu with twrp it froze and restarted my phone. I didn't have bootloop and everything is normal but it didn't flash SuperSU. How should I root my device?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Well, really doesn't matter which Update you get or currently are, Tenfar tool bypass all that.

[MENTION=540283]tenfar[/MENTION]

i was wondering if you are going to Mod the A2017.B11 Boot which is out, not that i have the A2017 but i do have ready the Flashable Zips (Bootstack + Stock System) ready for B10 user to update to B11 and not going thru the while EDL thing. Thanks man
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] StoneTrapper:
The trouble is that is a bit of an assumption. It seems to me some batches of A2017G do not enter EDL via keypress, I certainly had to use adb commands to get there, this could be sign of something as a few that have bricked have reported the same issue.

I was unable to initially flash only TWRP. The app succeeded however it wouldn't boot. I then put too much faith in the tool and thought perhaps it needs the modified boot.img too and everything has been black since.

Wild speculation ahead

Usually when flashing the name of the partition is used as an identifier of what will be overwritten with the new image, that isn't happening here for some people.

My understanding is that while tenfare's tool is only dealing with boot.img and recovery.img, as opposed to also the hidden partitions, it is a massively powerful tool and (please correct me if I'm wrong) may be injecting partitions with predetermined offset locations, considering tenfare's contacts this could be partition numbering via a partition.mbn and/or a zte_partition.mbn, directly into the UFS.

It may be this one batch that is suffering from becoming stuck in DFU has, for whatever reason, a slightly different partition map and with the injected files now in the incorrect location the phone has nothing to boot to.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
My assumption is that tenfar's tool uses partition offsets if it's based on emmcdl code , sort off like cmd based QFIL. While unlikely, it's not impossible that some batches use different offsets om emmc. As far as EDL, i think all G models will have this HW key entering DFU since it's in the bootloader, the keypress detection goes to dload_mode. This does not exist in the aboot of the U model. Also U model aboot has keypress detection for fastboot, which G model seems to be missing, so it can't enter bootloader like that either it would seem. No U model has come up with DFU problem so far but that might be due to same offsets in all phones. So with all this in mind, safest thing to try to flash first is TWRP, although if emmc offsets are different, then there is no guaranty that you wan't be overwriting the aboot instead. My guess is that DFU is triggered when something like bootloader is damaged, but who knows. There is a difference between G and U models here for sure
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] StoneTrapper:
Thanks, I was hesitant to post before my morning coffee but it seems like we're on the same track here, the tool is certainly akin to parts of the QPST suite though you're rather more eloquent and knowledgeable.

Considering some A2017G have no problem with the tool it does seem unlikely it's different offsets however I'm struggling to think of another justification, for what it's worth mine was shipped with B02 and purchased in Asia, though clearly those that bought in Europe are having the same issue. (Though they are likely able to use their warranty - It seems I am not)

For myself the tool reported it had succeeded in writing both times. Attempting TWRP only the app reported success however I could not access TWRP, with the phone entering DFU mode when attempting to enter recovery. Given this I would be hesitant to use it as a litmus test for success since without root or fastboot there is currently no way to fix the lack of recovery using tenfares immediate tool. We need a fulldump (inc partition.mbn) to restore functionality, though I doubt we'll see one too soon because of the implications for things that can not be discussed here.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
You need to use a specific 2.65 version of SuperSU to flash. Can't just flash the latest SuperSU (for whatever odd ass reason....) even with bootloader unlocked.

But once you flash SuperSU, you can download the update from Google Play and install the update normally. DrakeFX has the SuperSU linked in his thread.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] apd:
Now I'm really confused! Does this mean it is always safe, even on a potentially affected 2017G on B03? I'm chomping at the bit to root (this is my first unrooted phone!) but don't want to mess things up permanently
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
If all you want is root, just use tenfar's method in this thread and root w/ phh Superuser. You don't NEED SuperSU. Tenfar's method has proven to be bulletproof so long as you

BACKUP YOUR boot.img AND recovery.img

There's no way to mess anything up permanently, not if you read the warnings and TAKE BACKUPS like everything tells you to....

Don't bother w/ SuperSU if you do not have an unlocked bootloader, its only for those who DO have an unlocked bootloader. Once your bootloader is unlocked, then you're safe by default as having an unlocked bootloader means go flash whatever you want.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ticotexas:
What is the best/easiest way to backup your boot.img and recovery.img, and when do you do it? Is it to apply this root first and then use ADB commands? If I understand you, it sounds like you recommend backing them up prior to doing this. How do you do that with the stock phone and no root? Confused
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
This method is full proof on the U versions, however the G version have a different aboot or even SBL which make is imposible to enter EDL mode with HW buttons (it enters ZTE's DFU mode which will not work with tenfars tool). And quite a few G owners have reported ending up in such state after flashing modified boot and recovery, essentially hard-bricked in absence of ZTE flasher and image. So caution for G users is warranted. Flashing boot image via TWRP would be probably safer way then with axon7root, but a user reported ending up in DFU after just flashing TWRP as well
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shirakani:
You follow tenfar's instructions in the first post.

Yeah admittedly I do not have a G variant... I have the A2017 6gb/128gb china variant. From what I've previously read in this thread though.... you boot to DFU mode, and from there its possible to go to EDL mode.

IF I HAD A G MODEL... What I would do is enable USB debugging and OEM unlocking in Developer options, then go 'adb reboot edl' and that will get you into EDL mode. From there instead of flashing boot.img first, do recovery.img only to give you TWRP. This will not change your stock status. Once you have TWRP, follow this thread for how to unlock your bootloader.

After that, do what you want... No more restrictions or worries.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ticotexas:
That explains how to flash the new boot.img and recovery. But how do you backup the original stock boot.img and recovery? Wouldn't you need to go back to those for any warranty claim?