yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
1. Works without issue.

2. You'll be lucky on a custom rom. Maybe LOS supports it on some providers. Expect nothing.

3. Blur and Judder reduction doesn't work, performance is awful. Its unusable. Stick to stock Nougat for Daydream.

4. You can get around this with magisk spoofing another device which is play store certified but you'll have problems with Netflix only being lower quality because our phone lacks wildvine support. Btw on stock you may also have these problems since the phone doesn't seem to be play store certified any more.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Volte works on Verizon in the US no problems.

WiFi calling does not however.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h078:
Dual sim data swap seems not working. I have T-Mobile and AT&T; It sees both SIMs , I can call and SMS on both SIMs , however I cant swap data SIM. It locks to one sim and regardless what I tried, it does not switch data sim.

All APNs are set correctly. For Example, it is currently locked to TMobile for data and even after I turn off TMobile SIM, Second sim (ATT) does not pick up data connection.

Any Help here?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
try this

https://xdaforums.com/showpost.php?p=80079279&postcount=5
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kaplah:
Huh. I usually keep my phones for 4 years prior to an upgrade, but issues with the ZTE Axon 7 seem to be cropping up quickly. The two year warranty was great (I used it a few times) however if this is the support we can expect when a device becomes out of date perhaps I need to not consider ZTE for a replacement device. Especially when they fixed Daydream in Oreo, but only in the German rom...

Thank you Dodgexander for your feedback!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
[MENTION=8432117]jiggumbob[/MENTION], no, LOS 16 doesn't have signature spoofing. You would have to patch the ROM first. Could probably try NanoDroid Patcher or some other tool like SmaliPatcher.

Check here...

[MODULE/SYSTEM] NanoDroid 22.3.20190805 (microG, pseudo-debloat, F-Droid + apps) - https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928

and/or this post...

https://xdaforums.com/showpost.php?p=80089645&postcount=7029

ZTE Axon 7 A2017U, Candy7 v5.2 ROM, Google free - no microG, MultiROM, XDA Legacy
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h078:
Thanks for a suggestion, but I have unlimited data on both cards.

So for me it does not matter which one goes in slot 1 as long as I can switch between them when I need to (due to coverage) as I was able to do in Stock rom.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Yeah, they fixed daydream for the g variant but they fixed it in the kernel and haven't shared how.. So basically on custom or even stock Oreo on the U it won't work well.

It's been clear with this phone that there's always been software problems, you could I guess blame a lot of that on recent politics.

In ZTEs defence there's manufacturers who are a lot worse in this respect!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] davidroid1:
please update the vendor, no gsi starts with the current vendor [MENTION=5027381]OrdenKrieger[/MENTION]

Enviado desde mi ZTE A2017X mediante Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
This has nothing to do with that. I'm just not building a fake treble build since we can't enable proper linker isolation.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Giustiniman:
will you continue to update los16? :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Yea sure, I'll push updates from time to time. When I got time, I'll try to get Q working.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Normally I would say they should fix their app themselves. HAL1 is dead and it's not my problem, if they are to lazy to update their stuff. But I think I know a way to fix this.

About vibration idk, no one is happy about the vibration on this device, I might just the Pixel vibration pattern.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Encryption is broken right now for all FDE devices on P. This goes to the bug list and will be fixed in the future, thanks for the report.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
Vibration is okay on stock beta Oreo or treble Pie. But it is broken on this rom
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blu3wh0:
GCam works again after using the above P fix for the settings. I can't tell if the flash timing has the improvements that Unjustified Dev was talking about previously, but I'll try to do some testing later. I'm fine with the vibration, probably because I do use a case for the phone, and I would prefer a strong vibration vs weak because it is my primary source for calls and notifications. I'm still fighting with Adaptive brightness as it won't always maintain my desired brightness level relative to light, but turning it off causes other pains when I use my phone in bright light.

I did have some random glitches after restarting the phone (different issue on the occasional restart), like SIM card not being found, System UI constantly restarting, BT crashing, and restart power option ending up crashing the phone with a red notification light. But I'll probably blame these on me as a power cycle resolves them.

Thank you for letting us know about encryption, I was planning on trying it this weekend so it's good to know beforehand that it doesn't work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Have any of the people (was it just me and the other fellow?) who had data APNs not set and unsettable in the previous build tried this one? Does it work in this one?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ibphantom:
If you want to try and fix the ?, by all means go for it. But you've already done your job if HAL1 is the issue and Snapchat isn't keeping up.

I'm not sure there's a problem with the vibration pattern. I think it just needs to be turned down a notch or two cause it sounds like it's spinning so quickly that its zapping the insides.

I'm all for beta/bug testing this.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] paketjabbe:
I have download party en run it but is reconice a vendor partition. Must i remove the old one and install a new one? TWRP don't list de vendor. I am a little confused.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
You need to have the latest twrp 3.2.3 I believe or NFounds -8-TREBLE one. Which TWRP do you have?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] paketjabbe:
I use twrp 3.2.1.8 treble from Nfound. I was at first on aex extended treble but had a in comming call problem. Then I flasht aex non treble. Now i did flash Los 16 over it and Los 16 works great. Only no vendor anymore in twrp.

Btw thanks for the fast anser.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
Did battery life improve in last build or is same as first one? Afaik currently battery life is worse than on 15.1 right?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] eaponte23:
If you want better battery life go with stock rom. LOS for the Axon isn't going to be better than stock, at least on my phone it never was.

If you're expecting better stats then it's time to change your battery. It is a 2 year old phone...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
Chill dud, was just looking for a comparison of battery between latest los 15.1 and latest los 16 (and of first and second los 16). I'm on custom roms for some time now and know the shortcomings. Appreciate all the work devs ar putting into having our devices updated to latest and greatest, was not even expecting for treble.

Shortcommings come from mainly having the beta modem and bootstack from b12 rom, should get better when / if official Oreo will be released.

Ps: already changed battery once, have the phone since release.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] eaponte23:
Okay then it that case, I saw close to 5 hours of SoT. But thats dependent on various factors. All of which you know by now :o
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Vendor partition

Is the contents of the vendor partition on 16.0 the same as 15.1?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KevinX8:
No, also to all the people reporting vibration broken, be more descriptive! The actual issue is vibration is stuck at 100%, changing it in kernel settings still keeps it at 100%. This is what is causing the horribly loud vibration when an app tries to use max vibration.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RedWave31:
I've got the exact opposite : Vibration is at minimum when using hardware keys. Hope it'll change, it wasn't the same on AEX 5.8 Oreo.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Thank you for your reply. I am confused about compatibility between vendor and rom. For example, would the 16.0 vendor partition work with AEX 5.8 (Oreo)?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] trevor68:
Device Theme = Dark doesn't seem to do anything?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
actually it works. it just changes to statusbar, not settings
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RedWave31:
By the way [MENTION=5027381]OrdenKrieger[/MENTION], it works perfectly fine on an A2017G, aside of the Wifi Code that must be tweaked a bit (2.4Ghz wifi only at startup). Thanks a lot for putting on the ROM!

However, since we're on Treble, could you tell what has to be put in the ROM, instead of using a GSI image? I know there are some HAL problems, but can't remember which ones. Thanks ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] llamanirvana:
SmaliPatcher worked like a charm to patch for signature spoofing on ROM 20190729.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
[MENTION=5027381]OrdenKrieger[/MENTION] is there any advice you can give a few of us?

After you kindly published your sources we have been seeing lots of new device specific roms for the axon 7.

Each release though seems to include undefeatable thermal throttling.

It is normally possible to disable the the throttling by editing config files but for some reason it's not working for us.

Can you think of anything in your sources that may be causing it? When we have been running the GSI releases with the vendor from los15 we didn't have the problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
[MENTION=5027381]OrdenKrieger[/MENTION] in pie .Treble Checker apps say we dont have treble.How it could be ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
[MENTION=5027381]OrdenKrieger[/MENTION] This forced low thermal throttling is occurring in both your latest July builds. Editing thermal-engine-8996.conf is not yielding any difference. I tried the earlier March build and it is able to be modified by the thermal conf normally.

I saw this in build.prop ro.treble.enabled=false not sure if that's the exact cause. Why should the report matter in any case?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Louisthefirst:
hey!

i am comming from lineageos 16.0 2019.march.12.

can i simply update the newest version of lineageos by using twrp without instaling modem again?

thx

bytheway why cant i simly update the rom through updater ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RobMahn:
I could not turn on "Access with Voice Match". Upon your note that you use Aroma, I looked into the Open GAPPS, as I had started with PICO. I noted that the fly over for NANO said that it "includes the extra functionality that is not available from the play store".

So, I downloaded NANO and installed it over my existing system. That fixed the problem. (Note that I am now running ViperOS, but had the same problem.)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
To update, you can simply flash the new zip in TWRP over your existing system, and then flash gapps/magisk again.

You don't need to flash modem or bootstack again.

Updating via OTA through the updater isn't available because LineageOS 16 for the Axon 7 isn't Official.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Beeperz:
Phone can't establish EDGE connection in "2G only" mode. 3G and LTE works well. (lineage-16.0-20190729-UNOFFICIAL-axon7.zip).

It worked on some of early build, can't remember which exactly, may be even not from topic-starter.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RobMahn:
VoLTE not working on T-Mobile

I am on T-Mobile. I was running lineage-16.0-20190729-UNOFFICIAL-axon7.zip and having trouble with no inbound audio on some calls. I switched to Viper-axon7-20190924-v6.7-OFFICIAL.zip and was having the same problem, but then isolated the situation.

I only lose inbound audio on an inbound call from another T-Mobile phone. Inbound from land line is OK. Calling out to a T-Mobile phone is OK. Turning off VoLTE resolves the problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Giustiniman:
Hi, any news about los16 or Android q?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Voenix:
Android Q works on our device if that is what you mean
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Giustiniman:
Yeah but I was asking to orden since he told that he was working on it
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Jahcopo:
Stock Music Player Problem

i was listening to music from the stock lineage os (16) player when my axon7 died due to dead battery.

the day after I load it 100%, turn it on and enter the music player and surprise ... the player no longer recognizes the songs on the sd card. I have already tried: to clear the cache and data and disable the app and restart, to remove the micro sd from the phone and restart, but nothing ... I also have other alternative music players that obviously works well, solutions for the stock music player?

many thx!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mohamedkam000:
Single swiping Music Player out of recents & reopening could've fixed your problem.

Now, try clearing "Media Storage" app's data & cache, reboot, use your phone normally till Media Storage finishes recognizing your media files.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Jahcopo:
ok, i will try it in a few days :) oh yes put out and in the data's SD is a good way i think, thx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tiesemans:
I am scared ****less

ok,

From this point on I am scared ****less.

What happened?!

Well in my case I had a brand new sealed in storebox Axon 7 lying around for the past 2 years.

My OnePlus One was still going strong on Lineage 16 so I felt no need to start using the Axon.

Until a couple of weeks ago when my OPO screen broke.

Thus I took out the EU model Axon 7 and assuming it was still running the factory installed OS version so I immediately ran the Axon7 EDL Tool and used it as a total noob.

BIG mistake. Hard bricked the damn thing on first try.

Send it back to the store feeling sick to my gut.

I bought it from them 2 years and 4 months ago and they have been very generous ... even do It was 4 months past EU 2 years factory warranty they send a brand new replacement Axon 7.

Thus my title .. Now I am scared ****less to repeat myself.

Unlike the samsungs and Opo's I have no idea how to root, install TWRP and sideload Lineage on a phone like this.

Which of the hardcore veterans is willing to guide me step by step via PM to a successful install of Lineage 16 on this brand new stock Axon 7?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Sorry for the dumb question but how can I apply this commit? Is there a way I can do it manually without having to make my own rom build? I don't have the resources to do it unfortunately.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
I'm surprised to managed to hard brick the Axon 7, it's basically unbrickable. If you managed to brick it again, just post here for help and describe the situation. Anyhow, going from stock to LineageOS 16.0 is pretty simple. It's going to be a lot of text, but I've simplified as much as I could.

• Firstly, make sure you've enabled OEM Unlocking and USB Debugging from Developer Settings on the phone, standard procedure.

• On your computer, install Qualcomm USB drivers. You can Google for these, easy to find.

• Download the very same 'Axon 7 EDL Tool' you used before. It won't brick the phone lol.

• Make sure you extract the folder of the tool to the base of your C:\ drive. It should be C:\ Axon7EDLTool (example).

• Plug your phone into the computer via a USB 2.0 port, and launch the EDL Tool.

• Agree with the confirmation it gives, and it'll automatically reboot the phone into EDL mode.

• Once rebooted, it should appear on the tool 'Connected' as Qualcomm QLoader 9008 etc.

• On the tool, select 'Unlock' and then 'Unlock bootloader'.

• Let it run, and once complete it will reboot the device.

• You can confirm the bootloader is unlocked if it shows a red/yellow text warning everytime you boot the phone saying 'Your device is corrupt / Your device is unlocked'.

• Download TWRP version 3.2.1-0 from here

https://eu.dl.twrp.me/ailsa_ii/

• Rename the downloaded TWRP image to recovery.img and place it in C:\EDL_Tool\flash\recovery

• Unplug/replug your phone back into the computer and relaunch the EDL Tool. It should reboot the phone into EDL mode.

• Back on the tool, confirm the phone shows as connected, and select 'Flash' and then 'Recovery'.

• This will flash TWRP on your device.

• It should reboot the device, or give you a prompt to reboot it. Hit yes, and then confirm TWRP works by powering off the phone, and then turning it on by holding the Power + Volume Up buttons simultaneously until the ZTE logo shows.

• If for some reason it flashes a red led instead of going to TWRP, just try booting to it again.

• Now you can simply follow the instructions given in the first post of this thread. Flash Los15.1 Universal v2 bootloader, flash your device's modem, and then flash LOS 16 + Gapps + Magisk (if needed).

• The bootloader changes the TWRP you've installed currently to a semi-broken one. I'd recommend installing the TWRP linked in the OP, version 3.2.3-0.

• The red 'device is corrupt/bootloader unlocked' screen is normal. Simply press the power button on those screens (will show twice), and then it'll show a tux. Wait 20 seconds, and the LineageOS boot logo will show. Done :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
You need to build the ROM to apply the commit.

You can use permissive patch to fix this bug by flashing it in twrp
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tiesemans:
First off ... let me say> THANK YOU!

I really appreciate your effort in trying to help me!!

Second .. I have no idea why it bricked like it did .. I went from stock to block in one action.

So uhm ... from the get go LOS 16 is a bad idea?! And ADB Sideload is not possible?!

Last Question ... If I were to update the phone via ZTE update (pushed updates) how far would I come ... version Android etc.?

The repair company (Dynafix) couldn't repair it, not even a special branch of their company .. so they replaced my phone with a brand new one. I must say excellent customer service from BelSimpel.nl

I will try exactly what you have written down.

I do however feel pretty insecure after having seen what happened to the first phone.

If I screw it up this time I won't even dare contacting the store I bought it from.

Oh well ... will keep you informed. :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
LineageOS 16 runs fine, I'd say it's pretty stable. You can have a look at the other ROMs found on the A7 forum as well, all can be flashed the same as LOS 16.

ADB works fine. You can sideload apps and files, etc.

Fastboot is mostly broken however.

If you were to stay on stock, the latest you'd be at would be Android 8.0 Oreo with mid 2018 security patches.

If you end up doing something wrong and messing it up, no problems. The Axon 7 is 100% unbrickable via software, and can be recovered from no matter the issue. As long as there's no hardware faults, it's all good.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tiesemans:
[MENTION=1089164]running[/MENTION]

Good point about the stock update and lack of security updates.

Does it matter if I "update" to Lineage right away fresh from factory or first update stock and then go over to Lineage?!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Doesn't matter, you can switch to Lineage whenever.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] reversalx:
I cant seem to boot into the OS, keeps booting back TWRP after the boot animation plays for a while. After using the axon7tool to unlock bootloader and flash twrp(on stock 7.1.1), i followed the instructions on the OP to install LOS16; i flashed A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip, a2017u Oreo modem, flashed the vendor creation tool(flashed it again on reboot as per instruction), and now the latest rom+gapps. This was done on TWRP 3.3.1-0. I may be missing something important, but i cant figure it out. This is on the american a2017u model.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tiesemans:
Done

Done

Done

Done

Done

Done

Where I am at the moment (Nervous as F$$$)

Will attempt in a sec ...

Does it have to be TWRP v3.2.1-0 Or can I used the latest version? 3.3.1-0 for ZTE/Axon7?

Nothing I need to ask ...

After each flash need to reboot? Or can I flash one after another in one go??

Same question ... Is TWRP 3.3.1-0 also ok in stead of 3.2.3-0 ??!

Will keep see when I get there. ;)

Thanks a million!!

*EDIT*

OH for f#ck sakes ...

This time I have green letters in big saying ZTE and below powered by Android but the freaking phone won't power down or reboot :S

I will let the phone battery drain completely but I am scared ****less another RMA is in the makings
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
TWRP 3.2.1-0 was the latest version that worked on stock for me, so that's what I recommend.

TWRP 3.3.1-0 from the official website doesn't have the option to show the Vendor partition in the Wipe/Backup menus, so I wouldn't use it. 3.2.3-0 from the OP has been modified to work with Treble and has a visible Vendor partition in TWRP.

Did you manage to unlock the bootloader? If yes, then try flashing this EDL via MiFlash. You can use any version of MiFlash, it should work.

https://androidfilehost.com/?fid=1322778262904015138

To use MiFlash you'll need your phone to be in EDL mode, which can be done by holding Volume Up + Power buttons together whilst plugging the phone into the computer all at the same time.

If you didn't unlock your bootloader, go into EDL mode via the instructions above ^ and then go back into the EDL Tool and try unlocking the bootloader again. After that, flash the EDL file I've linked.

No RMA is required, calm down. These things happen with the Axon all the time, it's a strange phone. It's damn near impossible to brick.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tiesemans:
Phone is powered on and stuck at ZTE - powered by Android screen for hours now ...

Waiting until battery is drained/empty ..

Hopefully it boots and gets recognized when charged and turned on again.

IF not it goes back to the store.

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

Did not manage to unlock bootloader ... attempt with EDL toolkit failed and resulted in current situation.

Link in OP is not working/file not longer available.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mitchum67:
https://qc2.androidfilehost.com/dl/...55/5862345805528066666/twrp-3.2.3-0-axon7.img

I can download it...

Gesendet von meinem ZTE A2017U mit Tapatalk