yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
yeah, none actually. you also against using Magisk?

Some time ago supersu used to work. Maybe if you flash the dm-verity remover zip you might be able to make it work again, idk. But again, it's personal preference but I trust John Wu more than a shady Chinese company that bought SuperSU...

And for the password thing: format data. Go to Wipe and FORMAT (not just wipe) data from there
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] murtaghm:
I couldn't get any root flashing to even boot in Oreo so went Nougat + Magisk and all is working fine. Thanks anyway.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
If you wanted to root stock Oreo, you can use SL1M B03 which is modified to work with latest Magisk 18/19.

https://xdaforums.com/axon-7/development/rom-slm7-dfnr-t3896486
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] murtaghm:
I ended up spending a couple of days trying different stock ROMs and roots with the aim of just rooting stock Oreo, so I wish I'd seen that thread before embarking on the journey. The backup I took, via ZTE, was a complete waste of time and I had to spend another day setting my phone back up after getting the ROM/Root sorted with Nougat/Magisk.

I'm quite loathed to start again unless it's all nice and straight forwards.

Can I:

Axon 7 EDL Tool -> Backup

Install SL1M B03 following https://xdaforums.com/axon-7/development/rom-slm7-dfnr-t3896486

Axon 7 EDL Tool -> Restore

I'm assuming the install of SL1M B03 will wipe my phone again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
If you've already got root, you should use a tool like Titanium Backup to copy over your apps. It'll be easier to do, and you won't need a computer (Make sure to get the Pro version apk).

Just follow the instructions in the SL1M7 B03 thread, and yes you'll need to wipe your phone since you are swapping from Nougat to Oreo.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dunyto:
No Answer from the phone after unlocking the Bootloader

Hi guys,

I needed to have my phone rooted and after many hours in search for the right solution (I have the European <G> version of the Axon 7 with the stock Oreo) I thought this tool should be the right one for me.

As recommended, I first made my backup (the full version with all folders) and then proceeded to unlock the bootloader. I think it worked, because after the reboot it showed me "DEVICE STATE - unlocked". But now I'm stuck at this place and cannot make the Tool to connect to my phone again, so I can reinstall from the backup.

[IMG="error message"]https://imgur.com/v6AcH9X[/IMG]

Do you have an idea how can I reconnect to the tool again?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tenker:
I'm not sure why it's not exiting EDL mode, that's pretty strange. I think it would be best to leave it to the side for 48 hours to ensure a complete drain and then plug in the phone to the power outlet to see if it powers on. If it still seems stuck in EDL Mode after being drained completely, then something is corrupted software-wise. Usually the device gets out of EDL mode after leaving the battery to drain or disconnecting the battery cable from the inside.

Have you tried holding Volume Up + Power for 30s whilst in EDL mode? Sometimes it reboots out.

You could also try to plug it straight into the computer after draining it completely, and then opening Device Manager to see what it shows up as under 'Ports'.[/QUOTE]

I successfully solved the problem with an EDL cable.

Thanks for the tips

:good::fingers-crossed::)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dodo34:
i flash twrp 3.2.1.8 nfound version but the led then blinks 3 times and the phone shuts down. i cannot boot after twrp flash.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] evilKabab:
Finally my time comes to join the club.... Yesterday I shut my A2017G down with intention to do Vol Up + Power, wipe cache and restart... Phone just wont start, not reacting to any button, no light... Seems like I hit Vol Up + Power a bit to early. Phone running (was) Oreo B04.

I'm not in experimenting, rooting or custom ROMs. Just regular Joe Shmoe.

Connected to PC, shows Qualcomm 9008 as a COM port. So it is EDL mode. I tried almost everything - no luck. Your tool gives some Sahara protocol errors and unable to write to COM port.

Discharged it overnight (even put it in fridge overnight, idea was that Lion batteries loose charge in cold).

Now charging... Red light is on, message says 'Battery totally discharged, charge for few mins and power on'. Before it wasnt reacting on charger at all.

About your tool: most recent version wasnt working at all for me, always stuck on 'loading programmer', but your version for Win 10 was able to get past that point...

Quick question what ROM shall I load (try to) now? Nougat or Oreo?

And thank you for that tool, functionality looks impressive and use is hustle-free
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] evilKabab:
So update now. Nothing exciting after full discharge my phone has started as usual. What a relief! Funny thing, those 20 hours was the longest period without cellphone for me since 1999. Feels weird and empty...

Quick question again. My carrier uses AWS bands (Freedom Mobile) and my phone is not fully supporting those. Shall I flash modem firmware from A2017U? Just to make it more compatible...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ficus*:
My phone is an A2017G. After being on Lineage 14.1 for over a year (build May 2018), I decided to install a new Tremble rom. So after reading this post, I downloaded EDL tool and run the unlock procedure (from main menu, options 4 -> 1). after confirming to flash, I got to this screen and I cannot countinue: https://www.dropbox.com/s/6g9dndah7fc8l83/edl.PNG?dl=0

the phone screen is black, and pressing the power button does nothing. if i long press the power button, after a few seconds the red led turns on for a split second, then nothing else happens. before starting the procedure, my battery was around 50%.

1) Anyone knows how to fix this situation?

2) Is my device unlocked now or do i need to run the unlocking procedure again (now that I think about it, I believe I already had the unlocked bootloader.. It said something like that for 5 seconds everytime I turned on the phone, so probably I tried to unlock an already unlocked phone :/)?

edit: after checking previous posts, the A7 is shown as "Qualcomm HS-USB QDLoader 9008 (COM3)" in the Device Manager, so I understand I am in EDL mode. However when I try a full flash of A2017G_B12_NOUGAT_FULL_EDL:

a) the EDL tool stucks (I waited for 20+ minutes) on "loading the programmer: prog_ufs_firehose_8996_ddr.elf >>>" and nothing happens

b) miflash tries to communicate for around 15 seconds, then a timeout error appears and nothing else happens.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
If you were on LineageOS 14.1 beforehand, then your bootloader is already unlocked. You can confirm this by the 5s boot screen you're talking about.

Not being able to flash anything is a bug that happens sometimes when in EDL Mode. You'll have to wait until the phone battery is fully drained to exit it.

I'm guessing you already have TWRP, and if this is the case then you can simply just upgrade your TWRP to a more recent version (3.2.3-0 [Check LOS thread or use Oki Labs]).

After that, continue with the installation as normal by flashing the Universal bootloader, modem, rom zip, etc.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Volumetrik:
Thanks for your useful tool, it saved a lot of time and energy to access to PIE roms :D

---------- Post added at 03:00 PM ---------- Previous post was at 02:31 PM ----------

Just perfomed the same operation on the same model yesterday.

Bricked the phone, EDL available only.

Spent 2 days on it. Realized that MIFlash doesn't help at all, whatever version, driver ou USB ports...

Successfully done with Axon7EDLTool + Oki's EDL Package (to put into Axon7EDLTool/Subfolder Full) + ZTE DFU_MultiDL_A2017X_Tool that can help if issues with ports. Don't forget Qualcomm Drivers.

If stuck at the first command in Axon7EDLTool, try to disconnect and reconnect cable. Wait 10s before retrying, giving time to your computer to reinstall relevant driver.

I experienced this issue before flashing with this tool:

- EDL manual mode gives red LED ON

- connecting cable, LED goes OFF, and computer installs correct driver ( QUALCOMM USB... 9008)

- once above operation done, launched again tool, flash started and passed correctly.

Just for your information:

I had to wipe and re-create vendor partition with Oki's TWRP because of lower size than required.

Then, I just had to reflash B02 Oreo Modem because GSM didn't work at all. Same for Magisk, Manager Playstore install OK, but not zip. Had to flash zip into TWRP

Good luck ;)

---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------

it wasn't necessary in my case
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] schueyisking:
Flashing from Oreo B01 - ERROR

Hi, i am trying to return my phone back to stock, I downloaded the A2017G_B01_OREO_FULL_EDL and put it in the correct folder.

When I ran 1. FLash, I get this error:

12:56:01: DEBUG: XML FILE (79 bytes): CharsInBuffer=4001-79=3922

-------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" ?>

<data>

<response value="NAK" />

</data>

-------------------------------------------------------------------------------------------

12:56:01: DEBUG: Response was 'NAK'

_____

| ___|

| |__ _ __ _ __ ___ _ __

| __| '__| '__/ _ \| '__|

| |__| | | | | (_) | |

\____/_| |_| \___/|_|

12:56:01: {ERROR: handleProgram:8866 program FAILED - Please see log

Any ideas? FFS ANd now my phone is bricked. It won't even start after holding down the power button.

What the hell have i done?

I plug it into the PC and i hear the USB sound as it recognises, but nothing showing on screen.,

The EDL tool says the Phone is connected.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
Hello,

I am with A2017G stock Nougat B09, no root, just bootloader unlocked and encrypted phone. I would like to relock the bootloader.

I do not use Unlock option of the toolkit since it will unlock my phone whidh is already unlocked, and the unlock would cause erased data.

So I flash only fastboot.img and emmc_appsboot.mbn (taken from unlock.xml) to regain access to fastboot. It works (fastboot now available), but upon system reboot, Andoid asks for password that I provide OK, Android starts with default lock screen. When I want to login, a password is also asked, but my previous password is invalid, and it is also impossible to login with fingerprint ! So I cannot do anything ! I have to restore a full EDL backup to get in, losing of course the fastboot enabling.

I expect that only after "fastboot oem lock" that I will have to wipe data/factory reset to get rid of password question, and not after fastboot enabling. Do you have any thought about it? Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Using TWRP you can remove the lock screen password easily.

Go to File Manager in TWRP, and navigate to /Data/System and delete the locksettings.db file.

You don't have to wipe the phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
Thank you for your answer.

My phone is not rooted, and with stock Nougat B09 on A2017G. So I assume I have to EDL flash a TWRP in recovery,

delete the locksettings.db file with TWRP file manager, then EDL reflash stock recovery to keep stock ?

How about dm-verity afterwards? Since I assume TWRP will set system to read-write ?

What are the effect of deleting locksettings.db? Is my phone still encrypted, and same valid password asked at Android start?

And then no more invalid password raised on lock screen?

In fact I do not want to wipe the phone, I would like to re-lock the bootloader, but as far as I know

the relock will cause data lost. So with encrypted phone I will be forced to wipe data.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Yes, you'll have to flash TWRP via EDL. You can use the Axon 7 EDL Tool from djkuz to do so.

Deleting the file will only remove the lock screen password, but keep encryption.

Relocking can be done without data loss, but in this case TWRP is needed to remove the lock screen password, and TWRP can't be run with a locked bootloader. You'll have to flash stock EDL again to overwrite the recovery.img.

If you can find a way to flash stock recovery, then you can try it, but I've never tried it so I can't say if it works or not.

Easiest way to go about this is to backup all your data, and flash Chinese B19 EDL. Chinese B19 has fastboot working without needing to flash fastboot.img.

After flashing B19, you can lock the bootloader using fastboot oem lock and then flash whichever version of stock you would like to use.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
> Deleting the file will only remove the lock screen password, but keep encryption.

I understand (maybe wrongly) that normally the password for encryption is unique and is used to unlock screen (which is what I does).

From your answer can I deduce that I can have one password for encryption, and one new password (to be defined) to lock/unlock screen ?

What are the menu/steps to define those two ?

> Relocking can be done without data loss, but in this case TWRP is needed to remove the lock screen password, and TWRP can't be run with a locked bootloader.

> You'll have to flash stock EDL again to overwrite the recovery.img.

> If you can find a way to flash stock recovery, then you can try it, but I've never tried it so I can't say if it works or not.

OK so I understand with locked bootloader, I can only EDL flash stock recovery. Question : does EDL tool or phone EDL code prevent to flash recovery other than stock, or because after flashing such non-stock recovery, the phone will be bricked ? This would be the latter, since I assume we can EDL flash anything regardless of locked bootloader, the phone is not executing code (passive state).

How about using signed recovery such as tenfar's signed TWRP (18,347,298 bytes) mentioned in other topics? If such signed recovery is accepted by locked

bootloader (should be, since it seems that is used as method to unlock bootloader in the early life Axon 7 xda forum), then we can use it after bootloader relock to delete /data/system/locksettings.db. So the relock would not require wipe data and phone remained encrypted ! Other condition is that tenfar's signed recovery have a built-in filemanager. Or maybe we can get a shell to type in the 'rm' command to delete mentioned file?

> Easiest way to go about this is to backup all your data, and flash Chinese B19 EDL. Chinese B19 has fastboot working without needing to flash fastboot.img.

> After flashing B19, you can lock the bootloader using fastboot oem lock and then flash whichever version of stock you would like to use.

Wow this could be a good solution, but is it tested? My phone is A2017G (Europe), so I am very afraid of problem like no IMEI, modem, build.prop etc... or even brick after EDL flashing firmware not suited to phone model. Have you experiences about such flashings different firmwares on different models?

A bootloader relock solution without wiping data would be the best solution for me, since I use some banking applications, and a wipe data (factory reset) would require a reinitialization af first boot, and so the phone Device Id will be changed. And I am afraid that these banking applications still use the old device id and other tokens, and so they will no longer run after factory reset.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
The password for encryption is the same as your lock screen password, so once the lock screen password is removed, the ecryption password on phone boot should be gone too. I don't use encryption, so I can't confirm this, but that should be the case.

EDL can flash anything regardless of unlocked or locked. Trying to flash TWRP to a locked bootloader will result in the phone not booting to recovery at all, and requiring you to flash your rom again.

I have never seen this signed TWRP from tenfar, so I have no idea what/how it works. I 100% doubt that it works with a locked bootloader, as the recovery is usually locked down on stock rom.

You can in fact use ADB to remove the locksettings file too, but you need to be rooted to allow the phone access to the file.

As for the Chinese B19 solution, I have tested it myself. I relocked my bootloader using the same method, and once locked I simply flashed Oreo to use on the phone, but you can use any version you'd like.

As for the banking apps, you can use the app Swift Backup to backup those apps. There is an option in the app to backup Device ID for each individual app, and then once you are ready to restore the apps, there's an option you can tick to allow Swift Backup to restore each app's Device ID.

The full version of the app does cost money, so go about it in whichever way you'd like.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
> The password for encryption is the same as your lock screen password, so once the lock screen password is removed, the ecryption password on phone boot should be gone too. I don't use encryption, so I can't confirm this, but that should be the case.

So the deletion of the file would not be a solution for my encrypted phone, since Android will not be able to decrypt the data without the password (now deleted with tne file).

> EDL can flash anything regardless of unlocked or locked. Trying to flash TWRP to a locked bootloader will result in the phone not booting to recovery at all, and requiring you to flash your rom again.

OK I understand now.

> I have never seen this signed TWRP from tenfar, so I have no idea what/how it works. I 100% doubt that it works with a locked bootloader, as the recovery is usually locked down on stock rom.

You can in fact use ADB to remove the locksettings file too, but you need to be rooted to allow the phone access to the file.

OK.

> As for the Chinese B19 solution, I have tested it myself. I relocked my bootloader using the same method, and once locked I simply flashed Oreo to use on the phone, but you can use any version you'd like.

I am very interested. Could you confirm that you have a A201G (Europe), then flash A2017 (Chinese) B19 to it, then flash Oreo for A2017G with no problem so far?

> As for the banking apps, you can use the app Swift Backup to backup those apps. There is an option in the app to backup Device ID for each individual app, and then once you are ready to restore the apps, there's an option you can tick to allow Swift Backup to restore each app's Device ID.

The full version of the app does cost money, so go about it in whichever way you'd like.

I will look at this app, but as other apps, it seems to require root to get apps data. For me, root is not possible since root or unlocked bootloader would prevent running some of my banking applications.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
I have done the exact same procedure on my A2017G, I can confirm it does work.

As for the app, yeah it does use root. It seems it's going to be impossible to restore your banking apps without breaking them. I'm not sure what else you could do.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
Some updates of my problem enabling fastboot on A2017G Nougat B09 with encrypted phone, bootloader unlocked.

I used Axon 7 EDL Toolkit unlock part to enable fastboot but got problem of password asked at lock screen

(no valid password accepted, nor stored fingerprints), however same valid encryption password asked at Android start is well accepted.

By using Axon 7 Toolkit unlock part, it works: I can got through both Android start and lockscreen.

After comparison I found that Axon 7 EDL Toolkit uses (in unlock\ directory) the same emmc_appsboot.mbn (aka aboot.img)

taken from Marshmallow, regardless that the the phone is at Marshmallow (MM) or Nougat (N) version.

Axon 7 Toolkit however uses different emmc_appsboot.mbn in separate dỉrectories:

FASTBOOT_UNLOCK_EDL_MM\

FASTBOOT_UNLOCK_EDL_N\
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
I am trying to find (if possible) a way to relock bootloader without loosing data caused by bootloader relock.

I could of course backup data before lock then restore after relock, but there is device id/Android id that will be changed,

causing problems to some applications,.

Proposed scenario:

0) Status: stock A2017G Nougat B09, unlocked bootloader, encrypted phone (so recovery, boot, system are stock).

1) Enable fastboot (use Axon 7 toolkit or Axon 7 EDL toolkit)

2) Load latest TWRP with fastboot: "fastboot boot twrp-3.3.1-0-ailsa_ii.img"

Backup all system, including user data.

3) Relock bootloader with fastboot: "fastboot oem lock"

This will induce user data erased/factory reset.

4) Load latest TWRP with fastboot: "fastboot boot twrp-3.3.1-0-ailsa_ii.img"

Restore user data from backup.

5) Reboot the phone. I should get phone as at step 0 but with bootloader locked: no user data erased, all apps working.

The problem would be at step 4):

With bootloader locked, does the fastboot booting external image work although System, boot and recovery remain stock?

Edit: I have answer to step 4) from this article:

Cannot flash or boot custom recovery with boot loader locked:

https://android.stackexchange.com/q...into-custom-recovery-with-a-locked-bootloader

So the only remaining option is to use tenfar's signed TWRP, but unfortunately it cannot be used to backup/restore

due to bugs. Refer to https://xdaforums.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379

"Tenfar's signed TWRP version is the only one that will be accepted by a locked phone, so you need to flash that version first to unlock your bootloader. You should however not use it for backing up and restoring, since it contains fatal flaws that can lead to bricking your phone."

But how about using it and run a shell to 'dd if=source of='target for backup and restore the userdata partition ?

Edit add: Open a terminal under tenfar's TWRP, got # (root) prompt. Backup data partition image command could be:

dd if=/dev/block/sda9 of=/external_sd/Axon7/backup_dd/data.img bs=1m
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Great to see you got it working. Good job figuring it out, I didn't even know that was possible.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jp3871:
Hi,

I don't know how to solve it : after flashing recovery, my phone doesn't want to boot on recovery !

I can boot only on fastboot with all options and nothing else...

On Windows 10, I see "ADB android Interface" when connected : never see QUSB_BULK or port COM even when installed driver Qualcomm or ZTE Axon7

With command : "fastboot flash recovery xxx" it shows me FAILED (remote : unknow command)

Any idea ?

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dnlilas:
@ jp3871

"(remote : unknow command" : this means that your fastboot in the phone (fbop partition: fastboot.img) does not support this "flash" command. You have to install the right fastboot enabler (if you are in Marshmallow or Nougat: you can use Axon 7 Toolkit or Axon 7 EDL Tool).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jp3871:
Hi Dnlilas,

As I said : On Windows 10, I see "ADB android Interface" when plug USB : never see QUSB_BULK or port COM even when installed driver Qualcomm or ZTE Axon7

So I cannot use Axon 7 Toolkit or Axon 7 EDL Tool due to driver not recognised...