yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
I don't know why it's failing, unless there's some kind of weird filesystem UUID encoding in the key.

If it does fail, you can just delete locksettings.db in TWRP and you should be good to go.

This is why we should be allowed to encrypt our devices. ZTE is really failing here. (can't set encryption password on stock rom)

Has anyone with the A2017G tested official TWRP build yet? I'd prefer someone let me know sooner rather than later if it works or not. I still have some time where I can rename it from a2017u to ailsa_ii :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jabeth407:
Stuck on drivers

Please help my dumbass get my computer to talk to the phone. I've tried everything I can think of. I've worked at it for five hours going through; driver updater software, the device manager, ZTE's driver installer(s), I've manually tried to set the driver for the "ZTE A2017U" under other devices, nothing is working.

I cannot get the device manager to install ZTE's because after it finds them, it says it can't find them to install them.

I also got stuck on getting the Virtual Box to run the Debian OS. I don't understand which image software I'm supposed to use on my system to get the damn phone to talk to the computer.

I had very similar problems with Motorola's phones. Eventually, I got the driver installed and didn't worry about it again. This time, I can't even get Google's USB driver to install.

Any thing you can suggest that will save my process. I'm stuck on the B20 unlocked, "fastboot oem unlock" step. I cannot for the life of me get that damn phone under fastboot to talk to the computer. I did eventually get it hooked up through ADB, but I wasn't in whatever mode the phone needed to get ADB to talk to it. All it would do is display the device without its name and tell me I didn't have authority to make changes through it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jabeth407:
Update on stuck

I finally got the phone to talk to the mothership and finished the unlocking procedure.

However, it keeps failing on the B20-B27 update zip file. It tells me the build id numbers are different than what it expects to see.

What do you suggest? Is there another signed zip update on step 3 you're using other than the one in your package? I can't imagine that's the case, what the hell did I do wrong?

Should I start over with rolling back to your step 1, B20... or what the hell did I do?

---------- Post added at 01:42 PM ---------- Previous post was at 01:19 PM ----------

Well, rolling back didn't do anything to change the aborted updates from B20 to B27.

I'll find one here somewhere and try another update.zip. Load that up and see what happens.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
you just didn't follow instructions!!!! you need to flash B20 full after unlocking BL then reboot to recovery again and flash B20-B27, then reboot recovery and flash B27-B29

B20-B27 can't be flashed on the unlock BL zip, you have to go back to B20 full

for people who continue to have adb/fastboot driver issues (as I do on windows, grr) I am uploading a 600 MB VirtualBox VM.

You can install VirtualBox 5.1.10 or newer, along with the Extension pack (for USB 2.0/3.0), then download my VM and use the Import Appliance option.

VirtualBox should set it up with the ZTE and Google USB filters already set up for you and automatically mount your phone to it when the VM runs.

It's a very minimal environment of just Debian/LXDE with MTP, gedit, terminal, adb, fastboot, gcc, git, build-essential running on a custom VM kernel (Linux 4.9) with exFAT/f2fs built in in case you want to use mass storage modes.

You should modify the Shared Folder options once the VM is installed and point "shared" to a new directory on your PC. This folder's contents will be accessible in both the VM and your PC as a way to share files between them. Guest additions are preinstalled, and the folder is already automounted RW for all users on the VM. (it needs to be named "shared")

It's only the root user on first install.

Username: root

Password: xda

From root I recommend opening a terminal and typing "adduser yourname" and creating your own account.

Once you create an account, type "visudo" and add this line to it:

yourname ALL=(root) NOPASSWD: /bin/su

(use ctrl+x to exit visudo/nano, you will need to hit Y to save)

This will allow your new user to simply type "su" to become root when needed. (actually sudo su, but I added su as an alias to it in skel)

New user and root desktop environments are set up the exact same way my own PC is.

It's also just a few small commands away from being able to build Android/TWRP. :)

Here it is!

https://build.nethunter.com/possibly-the-coolest-things/Debian.ova

https://build.nethunter.com/possibly-the-coolest-things/Debian.ova.sha1 (sha1sum in case you want to verify, virtualbox should verify it though already)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
so is it safe to flash the Official TWRP over the UnjustifiedDev TWRP?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pointro:
Yes, I've personally done it. Just flash the img file into recovery as if you're updating TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
worked like a charm
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jabeth407:
My mommy told me...

It was my fault all along of course. I'm used to Motorola's fastboot which is (almost) exactly like ZTE's recovery. Obviously that led to confusing my computer (and me). After about five hours, I realized you had two different power-on(s), and that is when I 'found' Axon7's fastboot. POOF! After all that work on my system's drivers, Sony (through Windows, and I have never liked Microsoft's products; Symantec on the other hand... always tight, portable & fast) recognized ZTE immediately, and the rest was me figuring out to reset the developer options after... it did a hiccup between B27 & 29, but it even cleared that up after it was hooked up to its mothership. All is well for this recently freed Axon7 slave-device. This is a great phone. I hope ZTE keeps up their high pursuits.

On another note: I always record conversations with people I've never met. As a result, I required a rooted device just to get most aftermarket call recorders to work without speaker-phone / background recorder combinations. Axon7 is the first one I've used with (most of the paid ones under my belt) Call Recorder and no root, that worked flawlessly. I still needed root but for different reasons. Why don't people wonder why they cannot get a device (it can be done with multiple devices and a little headache) that records calls with the press of a button. Not even home answering / phone combos have a button to record a call. No, silly rabbits; it's not against the law, "your" police record everything you say... Want to delve further into the rabbit's hole?

Our 'money' is paper (technically; 'currency' is paper notes & coin on one hand & demand deposit accounts from commercial [licensed] banks on the other) printed by someone for the rest of us to (exclusively?) use, and that makes "our" laws pretty much fake too.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
[MENTION=5672995]jcadduono[/MENTION]

i was curious and was looking at your fstab for your TWRP.

I have noticed you didn't include the keymaster partition.

/keymaster emmc /dev/block/bootdevice/by-name/keymaster

Any specific reason not to?

Could you elaborate?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bafangul:
I followed the instructions and was successful at unlocking bootloader and installing TWRP. I chose to root with Chainfire and it appears to have installed properly. I checked root with root checker app and it confirms root. I have SuperSu on the device. I for some reason cannot get r/w access for system. I just want to change the Lock.ogg and Unlock.ogg. Does anyone know what I can try to get r/w access?

I have tried:

Es file explorer

Root Explorer

unchecked 'Mount namespace separation' in SuperSu

adb mount commands with su.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
What's the point of adding a partition to it if you're not going to be modifying it/backing it up? It would just add more load time to TWRP detecting all the partition infos.

I suppose it would be interesting to see if replacing the keymaster with another device's could fix the password mismatch problem with anything other than default_password though :P

reboot disemmcwp

when the bootloader does system boot it tells the kernel to enable write protection on most partitions.

reboot disemmcwp tells kernel to tell bootloader to reboot into system with write protection disabled.

dis(able)emmcw(rite)p(rotection)

they should have aliased it to disufswp hehehe since we're not using emmc!

so yeah, need to reboot into write protection disabled mode. you can install a kernel that always has write protection disabled if you want.

i'm still working on trying to add external storage support to custom kernels on stock OS though: https://community.zteusa.com/message/75044#comment-75044
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] -Duir-:
Hello [MENTION=5672995]jcadduono[/MENTION] and all,

I may have found one potentially great difference between the official and unofficial versions of TWRP offered for our device.

As many know who have followed the guides on rooting our device the only version of SuperSU we could install was version 2.65. Any newer version would result in the recovery crashing and the device rebooting. I decided to "tempt fate" as it were upon hearing of our device having official TWRP and its differences from unofficial and a new version of SuperSU being released. To my surprise, I was able to flash the new 2.79 version of SuperSU in TWRP without any issue.

I didn't try any of the previously unsuccessful versions of SuperSU nor have I done any type of comparison between 2.79 and previous versions to know for certain that something hasn't changed in the SuperSU ZIP to make it compatible with our device. I just wanted to point out that with this recovery I was able to flash the latest SuperSU not the 2.65 version we've been limited to.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Great to hear!

I also hear that TWRP is actually working perfectly fine for A2017 and A2017G users, so I have a new update coming very soon.

Changes in TWRP 3.0.2-1 will be:

CodeAurora base updated to LA.HB.1.3.1.c1-19500-8x96.0

Device renamed from a2017u to ailsa_ii (to show it's not just for the US edition)

Firmware partition no longer mounted during decryption - apparently unnecessary on this device :)

System image backup/flash option added

Force touch drivers removed (they seemed to be causing touchscreen to stop working on failed firmware updates)

Various bug fixes and filesystem fixes included in CAF updates

I have a bit of time to add to this list, so let me know if you guys wanted something in particular.

Unfortunately I haven't been able to find any way to distinguish the devices apart, so A2017G and A2017 will show up as A2017U.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
If the ROM's still on stock, you could pull it from build prop as the model models are different (the manufacturing model numbers, not the marketing models names). And if someone is on CM or whatever, then it could just pull that model from the same spot and it would be whatever generic version is used.

Minor issue though. Thanks for the work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
I can confirm this. I was able to successfully flash latest supersu while the unofficial recovery hanged. Great, using your custom kernel I was able to pass SafetyNet :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
I flashed this now I don't have a recovery. Just a blank screen. How the can I fix this?

---------- Post added at 11:24 PM ---------- Previous post was at 11:14 PM ----------

I tried this now I don't have any recovery.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
What phone model do you have, what software version, for example b29 etc... You do have unlocked bootloader?

Did you have the unofficial TWRP before flashing this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pointro:
Did you flash it as if you were installing a dirty flashing a rom, or actually go select image>official TWRP>flash to recovery. It sounds like you did the former.

Flash it through adb as per jcadduono's instructions. It should work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
A2017U. I am on Zadmix B29 and yes bootloader is unlocked.

Yes in had the unofficial TWRP installed. Now when i try to get into recovery. Phone boots up then red light flashes and phone shuts off.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
As the other user just asked, did you flash the image through the unofficial TWRP? If so your did make sure to select recovery as the area to flash to?

So if you power up and hold volume button up you can't get into recovery? If you didn't try that yet, try it. Hit the power button then hold the vol button up. If you can get into TWRP then wipe cache / dalvik and then in TWRP select reboot to system.

If you aren't 100% sure you flashed the .IMG file to the right partition then you will most likely have to use ADB and redo installing recovery and system (zad or stock) that way. Luckily on the u model it's not too hard to get your phone back to life
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
I tried holding down the button. Still did not work. Yes I chose recovery when i flashed the image. The phone boots up fine to my zad ROM. Just can't get into recovery.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
OK when in the ROM download advanced power menu (root) by noxx from play store and meefik's busybox. Install busybox then open the APM and set it up so it shows recovery as a boot option. Then hold the power button, you should have the reboot menu pop up with recovery as an option. Hit it. If that still gives you a blank screen, flash the recovery via ADB. I have the same set up as you, didn't have problems...odd
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
How do i flash the recovery through ADB. What command do i use?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
i recommend you to flashed via fastboot instead.

* Make sure and i assume OEM Enable is already check.

* USB Debugging is enable

* adb reboot bootloader

* fasboot flash recovery TWRP_NAME_HERE.img

* then reboot to recovery and see if work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] *mj13*:
The first post has all that info and/or it points to text files that describe how. Open a bottle of wine, read through it, it's not that hard. You'll be able to save your phone though, as long as you have a computer or another phone that is USB OTG friendly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
Now I can't get adb to see my device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
If you are still rooted and can boot to System, get Terminal Emulator then

1. Type " su "

2. Type " reboot bootloader "

From there just flash TWRP using g fastboot command
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
whats the fastboot command to flash just recovery

---------- Post added at 08:32 PM ---------- Previous post was at 08:16 PM ----------

Ok I am in fastboot and I figured out the command to flash recovery. But I pc still shows no listed devices in fastboot. When I type fastboot devices. It just stays on waiting for device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Yeah probably the phone installed the new drivers which is bad,

Go to device manager while in bootloader and revert to the old drivers and you'll be good to go.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
OK I got the recovery installed again. Had to add these drivers. Thanks for the help guys.

http://xdaforums.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165/post69624854
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Glad you got it working again, but you really didn't have to reinstall drivers hehehe.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xtermmin:
I had the same issue as [MENTION=2793689]borijess[/MENTION] when I tried flashing this a couple of days after it was posted. Tried to use Udev's unofficial TWRP 3.0.2-2 to flash official TWRP directly, made sure to specify Flash Image > Recovery, but upon rebooting into recovery, the phone just turned off. OS booted fine, bootloader booted fine, so I booted into bootloader and flashed via "fastboot flash recovery", and it worked fine. Bootloader unlocked, running CM13.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
That was my exact situation. Glad we got it working.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
[MENTION=5672995]jcadduono[/MENTION]

this is more like request so here we go :

1- REMOVE EFS from " Restore "

* This seems to be causing so many issues across devices, no matter which TWRP is been use. beside is there a really need to restore EFS?

I have never restore EFS since i started use it Android and probably never going to use it.

2- Add " System_Image " in Backup section. (please this one here if is the only request)

* This here have help a lot of user updating to new software update without having full official zips or if there been system modifications.

3- can you re-arrange " Advanced Wipe " order of partitions :

* Dalvik / ART Cache
* Cache
* Data
* System
* Persist (calibration data)
* Internal Storage
* Micro SDCard
* USB OTG

thanks in advance man,
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
1. As long as there is a way to wipe it, there should be a way to restore. I do agree it should not be checked as default restore option. Maybe add a warning? G users seem to be having the most trouble they may need a different build of twrp.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
[MENTION=3130027]jimbo77[/MENTION] where to find the custom kernel you mentioned
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] twilighttony:
Hey guys this is probably very off topic but does anyone know if the bootloader lock image that we backup before the oem unlock command is device specific? My computer crashed yesterday and I lost the file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Znuf:
Work great on my A2017G
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
This one :)

http://xdaforums.com/axon-7/development/kernel-kali-nethunter-zte-axon-7-t3520280

Regards,
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
[MENTION=2379516]jacdduono[/MENTION]

I ended up successfully flashing the "official" 3.0.2.0 as linked in the OP over the "unofficial" 3.0.2.2 flashed when I rooted last month, without incident. But in the process I saw that Flashify recommended a version 3.0.3--ailisa_ii. That version was NOT on the official TWRP page. Is there a difference/improvement?

Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
welcome 2 the future bro

one of the first devices on 3.0.3 the rest will come eventually

i renamed it from a2017u because it apparently works on all the variants just fine

here's the things I changed:

Removed persist from wipe/backup menu, merged it with EFS

EFS = modemst1, modemst2, fsc, fsg, persist (which are all on the same ufsd block dev)

Kernel updated to CAF tag LA.HB.1.3.1.c1-19500-8x96.0 & Linux 3.18.45 in the interest of filesystem & encryption stability on backup/restore

Add BTFM (Bluetooth) and System Image to Flash Image and Backup/Restore page

Remove Modem (NON-HLOS) from mounted partitions since it is apparently unnecessary for encryption on this device, can still be backed up

a2017u -> ailsa_ii

TWRP 3.0.3 just added the option to install the new official TWRP app when you reboot (can be turned off)

Last build was on 3.0.3 sources already, it just wasn't called 3.0.3 until the TWRP app was added.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
Just flashed 3.0.3 from within twrp on the global model with B08 bootloader, worked perfectly.

Thanks a lot!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] vibrantliker:
I just heard you and Freeza switched to this phone. How do you compare?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] peramikic:
From all i read, the keymaster is bound to the hardware, so technically even restoring a partition encrypted with "default_password" to another device should not let it decrypt the DEK since KEK will be wrong based on the keymaster
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Thank you for adding System_Image to Backup page and for the rest of the goodies.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] projectseahorse:
I have one major noob question, I'm still trying very hard to learn. How do I install zip from SD drive for this version of the recovery? I'm trying to follow the instructions in the zte axon 7 unlock kit. I'm confused because I tried to flash the zip files via install => select storage = external SD then I navigated to the folder where all the zips were and selected the first zip. I swiped to confirm flashing and it always have an error. Please help! thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
What error do you get
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
You posted this in three threads so far.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Erahgon:
Flashed 3.0.3 and got a new system up and running. Works like a charm! Thank you devs!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] projectseahorse:
Sorry, I wasn't sure where I should post this question and I panicked.

---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------

Hi Nupi,

When I try to install directly from the root folder of the zip files, it shows the following error:

Checking for Md5 file . . .

skipping MD5 check: no MD5 file found

assert failed: getprop("ro.product.name") == "p996a01

updater process ended with ERROR: 8

Error installing zip file "/external_sd/STEP-1-3-B20-FULL-OTA.zip

updating partition details . . .

. . . done

I tried to do a google search but was unable to find any answers. Any tips and suggestions will greatly be appreciated! Thank you very much for your help!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
You can't flash stock image with twrp
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
Looks like whatever recovery you have installed right now has incorrect case for ro.product.name? Flash Official TWRP 3.0.3 or stock recovery and boot into that before flashing.

You should be able to install full OTAs on the official TWRP.

In unrelated Axon 7 news, I've managed to fully rebase & fix up most important changes from B27 source on top of LA.UM.5.5.c1 (Nougat) CAF msm-3.18 kernel sources.

It *does* boot on stock and functionally it works just as well. The main challenge to get past at the moment is figuring out why some of the camera sensor initialization is happening at the wrong time causing NULL pointer derefs. I'll have it solved pretty soon though. (just using null checks to get past that and reinit later in boot sequence)

I guess this is another small step towards CM14.1 if any of the devs are interested in using it for such a thing.

I'm also still cleaning it up more and trying to make sure new changes aren't breaking any of the drivers, as well as fixing some of the small code bugs present in the original OEM kernel.

My goal is to bring it as close to CAF as possible without disturbing OEM stock ROM support.