yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
Flashing the Bootstack from here fixed that for me.

It also fixed cellular signal issues mentioned in this thread.

GPS lock is also much faster.

Not sure what the difference is between that bootstack and the official one on this thread.

Maybe Devs can look into that for us when they get some time to spear.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Soyunamortz:
Where it's the link to get that cable ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
The GPS issues are not related to bootstack and the have been fixed by udev in an unofficial build 2 days ago.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
When do those changes make it into an official build? How can I find out?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
https://xdaforums.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413

He will link 2 different ones in the op
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
You can check the Gerrit for lineage.

It's not there yet, though.

[MENTION=4911249]Unjustified Dev[/MENTION] the GPS is working great so far. I guess you can push the changes so they can be merged.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
So, after dirty-flashing the 0925 official zip over my 0711 unofficial, most (but not all) apps are not working. And wiping cache doesn't fix it. I'm able to get them to work by uninstalling/reinstalling manually, but just wondering whether there's a better approach to it. I didn't have to remove packages.xml to get official to flash, but maybe I should have anyway? Also, I didn't flash gapps - should I have had to?

In any case, I wouldn't mind having Google restore all of my apps like it would after a factory reset - but is there a way to trigger that without wiping /data?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
I've been running the 20180925 nightly for nearly a week now, and most things seem to be running great, except for playing music from the SD card mounted as external storage. Back on 14.1 official I could play mp3 320 kpbs files without issues from the SD card (with BlackPlayer if it matters) but since updating to 15.1 I get small stuttering and audio cutting for a fraction of a second, every 5-10 minutes. I did some tests, disabling AudioFX, and removing it completely, but the issue is still there.

The stuttering doesn't seem to happen when playing from internal storage though, but it shouldn't be a solution as it never happened before updating. I'll wait for the next commits to be merged to see if the issue is still there, but I wanted to point it out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Try installing/using another player to see if the issues persists. I had this happen when trying PowerAmp on my phone. Each & every song would have dropouts. Drove me crazy, since I'd paid for it.

Switched to Rocket Player, problem went away.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
I do have PowerAmp installed too, I haven't tried uninstalling it to see if it interfered with BlackPlayer. I will try that, thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BigMatza:
UPDATE for anyone who cares: I restored back to stock B35 (with factory reset), and even locked the bootloader. Still, the cellular radio would not turn on. Time to send my replacement back for another replacement :-/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcian135:
Thanks guys! Will definitely try flashing the module to see how much it improves the battery. Now all I need is for instagram to start working again!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Waancho:
Did the users with the malfunctioning speakers check if their /data was f2fs formatted? I had same issue with other rom. Formatting /data to ext4 solved it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CobraKolibry:
I can assure that my data is ext4, and have the speaker issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Martinxyzko:
In this rom everything works great except sd card - i got message that i need format my card ( sdcard is in exfat format). I had super weird problems after installation. I could not get it in twrp and before booting i had error message and i had to wait 30 seconds. It was only possible from system through (reboot into recovery). When i got into twrp i found out that i hadnt my twrp 3.2.1-0 but some other version.(i only installed rom,bootloader and modem, from first post). I decided to return to AEX and during installation suddenly half of my screen was grey(with pxiels), after reboot everything was ok but i lost twrp. Thankfully now i have everything back in original state before installation.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
How did you make the GCAM work ? I downloaded latest apk from apk mirror -> 5.2.022 and application crashes on load after successful install. Did you use any zip for TWRP or another version ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mllora81:
TWRP>Backup Data partition 0 MB

Yes. Anyone have a suggestion on how to resolve this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
I had to do the terminal command three times. First time I was an idiot and I forgot the quotations, and the second I just have misspelled something. It worked the third time through.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
https://xdaforums.com/axon-7/how-to/extras-add-ons-lineageos-15-1-t3800443
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
Thanks, I remembered that the oficial GCAM works only on pixels with HDR+, and that there is a ported apk.

Installed the one from extras and HDR+ does appear but it takes some time to process the picture, is it normal ? Is it because Zero Shutter Lag is not yet implemented / ported ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Thanks team to bring this to us. Some feedbacks:

I came from Stock unrooted/unlocked Nougat rom.

I flashed all the things, universal bootloader, modem, rom, gapps arm64 and magisk 16.4 in that order.

First boot led me to "enter a password to start android". Rebooted in recovery wiped everything, reflashed everything, and formatted /data (was ext4; kept ext4). Then it worked fine. This might be due to the fact i left a PIN before flashing everything.

I did not need to do the 'reboot dm-verity' thing.

Problems I had:

- I had 2 freezes probably may be due to privacy guard? phone becomes frozen, have to restart it.

- on one restart, the sim card was not detected anymore after boot; had to restart the phone to fix it. I only use SIM 1 slot.

- when I reboot, i have this annoying message saying the bootloader is unlocked and i should lock it that stays for 5s. I haven't made any research on how to remove it but if anyone already has a procedure; I am interested :)

is it safe to use twrp to enable camera2 api + support and flash a camera app? if yes, wondering which one has been tested?

Thanks again LineageOS team!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CobraKolibry:
I don't think you need to enable Camera2 API from TWRP, even GCam worked for me without doing so. As far as I know, there is no safe method for Oreo yet to remove the warning about unlocked bootloaders, but happy to be proven wrong about that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
I know that when I look into my /data folder using ES File Explorer, it appears empty (because for some reason, magisk denied it root). I can see the /data folder contents just fine now. I never chose to format any partition to f2fs, I don't see why this would have happened overnight. I checked TWRP and see it was ext4.

---------- Post added at 10:58 AM ---------- Previous post was at 10:54 AM ----------

For me, not yet. I have been using my bluetooth earphones for the entire day and then my car set via bluetooth. The 3.5 jack works as well. Just not through the speakers. The mic does work though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] m4tz3m4tz3:
It could be connected to the previous mic issue during calls. Maybe those who were affected by this bug, have the speaker bug now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
I don't know about that. It's more than likely something pretty simple though.

If someone has a very clean install where they wiped the internal storage as well and still has this bug, then it could be handset model related or a step or two that the person took. The point here is to narrow it down. Why do people who have audio, have audio when we do not?

I can start by saying that I have two sim cards installed.

I have the "U" grey model.

I came from stock B32.

My internal storage was not wiped.

My partitions are ext4.

I am using magisk over supersu.

I didn't opt in to share any data with lineage.

I did not opt in to share any data with Google.

I am not using privacy guard.

I am using the fresh install from the Android wizard.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xoroi:
I was about to install the unofficial ZTE Oreo ROM but then Lineage 15.1 appeared and I decided to give it a try. Everything seems to be working fine, except Android Pay. I get a message that my phone uses a custom rom and this is not allowed, blah blah blah (something like this, the original message is in Spanish). How can I solve this?

Does this have to do with the Google Certified in Playstore? Do I need to encrypt the phone to get Android Pay working?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CobraKolibry:
I have one sim card installed

Have G model in gray

I came from LOS 14.1 -- full wipe --> B01 -- full wipe --> B12 -- full wipe --> LOS 15.1

By full wipe I mean everything but internal Storage

My partitions are ext4, never were anything else

Using Magisk root

Did not opt to any data sharing

Not touched privacy guard

I did a backup from the cloud via the wizard

I also never was aware of having a mic bug. We pretty much already ruled out almost everything, didn't we?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] phiversen:
Has anybody found a workaround for the sound bug?

I only have sound through headphones - wired or bluetooth. (I changed the ringtone, as someone mentioned...)

Also when I start Poweramp it says:

Poweramp detected problems with app native libraries

(please consult log for detail):

libpampffmpeg.so: text relocations

Is this related??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
-UPDATE-​

Changelog

:

Add sdfat support

Roll back acdb blobs/ids to B15 (this should fix audio issues)

LineageOS repo sync

DOWNLOAD
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
There can now also be found a clean TWRP build in the OP, which should work without any issues.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
You should flash that TWRP even before installing anything.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Can't say for sure that PowerAmp is causing this, but if after you remove it & it still happens, find another player , install & test it.

You might also consider pulling your music off the SD card (yeah I know bit of a PITA) wipe and reformat it in the phone, then readd your tunes back on it & try.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
I did that already, it still happened. But uninstalling PowerAmp so far seems to have fixed it, but it is still very early to tell.

Nope, it still cuts every once in a while. Next thing I haven't done yet is trying to mount the SD card as adoptable storage.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KH_Lionheart:
I had the same issue as you after a month or two of running the old B32+10 bootstack version of RR from Oki's guide thread. One day I woke up and my phone was exactly the same no signal but could read the sim and number on it. Only thing I was able to do was restore the backup I had made with the EDL tool from [MENTION=6330152]djkuz[/MENTION] right before I unlocked the bootloader and started flashing. Once I restored the back up it started working like normal but I do notice the signal loss every now and then when I turn on the screen. It was solid no signal until I restored the EDL backup and now it is consistently working for the most part. I have until the end of the month for the two year warranty so I need to send it back in. What was your process for returning to stock and relocking the bootloader as well as your previous RMA experience like?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BigMatza:
To return to stock, I simply EDL'd the stock B35 package. Relocking the bootloader was tricky because I couldn't understand why fastboot wouldn't work. Then I remembered that I had to flash the fastboot EDL package before relocking the bootloader.

Ideally, I'd like to remove fastboot to have it completely stock, but I won't lose sleep over that. I was also surprised to find out that the phone still retains some data, even after flashing the stock B35 EDL. Instead of letting me into the launcher, I was being prompted for the credentials of the user I'd previously set up in the phone. This is what made me realize I had to do a full factory reset, even after restoring the stock EDL. Now I'm wondering if it even repartitioned the device to get rid of the new vendor partition. Anyone know?

RMA experience was pretty easy actually. Go for the advance replacement, so you'll have both phones at the same time for a few weeks. It kinda takes the edge off of needing to get it done right away, and it doesn't cost any extra.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
T-Mobile Wifi calling would seem to be working on my phone - though I can't be sure. The option is enabled, and when I make a call, the Wifi connection to the router seems to drop and reconnect at the end of the call. Don't know what that's about, but it implies that Wifi is involved in the call, no? I tried going into airplane mode and then re-enabling wifi, but with wifi up in that mode, I get a 'no network' message when I try to make a call - and the wifi calling options are under the Mobile Network setting, which is greyed out in airplne mode. So, how can I tell if wifi is actually being used to make calls? The icon on the notification bar is the normal phone icon - not the wifi one, so maybe it's just wishful thinking that calls are made over wifi.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] extremetempz:
i had this issue also took it to ZTE and the RF chip had completely died, and he had never seen anything like it but he just replaced it on the spot even though i had unlocked the bootloader ect.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BigMatza:
Well that solves that mystery. I got your refurbished RF chip!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Had to use MagiskHide Props Config to pass safetynet, just like I've been doing on Pie GSIs. Is everyone here having to do the same?

Using the Google Nexus 6 sig and the Google apps transform to the Material 2.0 look. So even if you don't need to use Props Config, if you want Material 2.0 Google apps this is a way.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Yes. You cant pass anymore without a certified device.. Even when one of the spoof certified device signatures is from a stock axon rom lol
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] voetbalremco:
Yes. On AEX it was fine (Spoofing signatures was enabled by default?) but now the Magisk module is required.

I had it set to the original Axon7 strings, but using Nexus for Material 2 is a plus.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kg3:
To avoid bricking, are these steps correct for a stock A2017G 7.1.1 B09:

1. Tick OEM unlocking and USB debugging

2. Run Axon7Toolkit 'install drivers' and 'test ADB'

3. Run 'app and data backup'

4. Run 'Unlock bootloader'

5. Run 'Flash TWRP' and then close Axon7Toolkit

6. Boot to TWRP and install O bootloader (or nfound B12 bootloader) and A2017G modem per OP

7. In TWRP, Update TWRP per OP via install image files

8. Wipe system/data

9. Install LOS and gapps

10. Done

Is it ok to save all the files and run them via internal storage or external SD?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BigMatza:
I would definitely also get a backup of the EFS partitions before you start, and store those somewhere safe. I believe you can use the Axon 7 EDL Tool to do this. Although my recent issue was hardware related, you can never be too careful with these EFS partitions. They are unique for each individual device, and you don't want to lose your own!

The Axon7Toolkit may have an option to back up EFS too, but I'm not sure about that.

Can anyone confirm?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
Little update: I bit the bullet and made a full backup of my phone, and then wiped everything (system, data, cache) and started fresh. The audio doesn't cut anymore, so it would seem it fixed it. Since I did a full reset, I'm not 100% sure what solved it. Good thing is that now it works fine I suppose :p
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] serpfra:
Hi there marvellous people!

Hi! How are you today?

I upgraded from LOS 14 to LOS 15.1.

All looks fine :o

Before the upgrade I checked "About phone" and was an ZTE A2017U. That confused me (I live in Europe).

I flashed ZTE_A7LOSv1_UniversalBootStack.zip

A2017U_OreoModem.zip

Updated the TWRP

Installed ROM GApps

booted and all was fine.

Then I found the original box and on a sticker is write ZTE A2017G :eek:

I restart all the process again with the A2017G_OreoModem.zip this time and all looks fine again.

Is there a way to change what "About phone" is reporting (A2017U ->A2017G) or should I leave it as it is.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
It is fine, your phone is still a A2017G but the string that shows it as A2017U is universal for most custom ROMs, there is no need to worry if you flashed the right modem file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
I'm not sure if there's a way to change it, but I remember the dev saying that keeping it that way helped with making the process easier for naming. Having to put a signature in to have it detect which model you have might be a bit unnecessary or tedious.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
Hi, so i got this device few months ago, i had heat issues since first day, device temp go to 42c easily in few mins on stock rom (even if I'm opening a single app) i doubted that those heat problem is related to the bad design by zte.. i left it in box since then so i wonder if anyone else have those heat problems and if installing los 15.1 solves it..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mark1003:
Hi, which Bootstack is the right one?

The newer A2017x_LineageOS15.1_UniversalBootstack_v1_by_DrakenFX.zip

or

the ZTE_A7LOSv1_UniversalBootStack.zip

Thanks a lot
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mb0:
i did something wrong.

everything was fine, then i tried Encrypt the phone and after 50 min it was done.

problem is that TWRP is asking for password for dencrypt and i didn't put any password at the OS/ROM.

recovery is TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod and i used alternative/safe installation guide

i tried with 3.2.1-8-TREBLE for android 8.x-9.x (new bootstacks) and is not asking for password.

what are my options, beside format DATA, if i want reflash TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod?

or maybe i should stay on 3.2.1-8-TREBLE for android 8.x-9.x (new bootstacks)?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
[MENTION=319057]Oki[/MENTION] thanks for your package flash went fine. I just recently received my replacement phone from warranty and install went fine.

However my phone is now the a7g332 which does not have the capacitive buttons at the bottom but normally a pull up action shows them. In a 15.1 fresh install, they re gone and I can't find a way to show them. Meaning I can't press home, see recent apps or anything.... :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheWaterBug:
Yeah, I was wondering why 15.1 doesn't have nav buttons like 14.1 did. There is a fix if you have Magisk: MI A2 nav buttons module.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
You mean MI A1 navigation bar...?

I'll give it a try if I can find a way to open magisk manager.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheWaterBug:
Yeah, that's it. I'm using it because the capacitive buttons aren't visible in the dark. Good luck!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Raystef soft key reverse module worked for me

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

Only thing missing for me now is Dolby. I'll probably try v4a like everyone else
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Flashed a1 in twrp and it now shows the nav keys. Thanks. No way to auto hide them though...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kg3:
Dolby - https://xdaforums.com/axon-7/themes/info-n-dolby-port-v4a-setup-custom-8-1-t3824475
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jrotaetxe:
Hello, Master.

I have tried to "check" HAVOC in my LOS 15.1 treble based rom, flashing the arm64aonly GSI image from the Treble thread, but I enter in bootloop. Prior to flash, wiped System, data cache and Dalvik, then flashed system, but I enter in an eternal "android" letters welcome.

My boot is this "A2017x_LineageOS15.1_UniversalBootstack_v1_by_DrakenFX.zip". Perhaps you can shed some light with this....

Regards
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AnonVendetta:
Does Substratum work in OMS mode with LineageOS?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chilewille:
I have a similar problem. It was also noticed that the program "Cool Tool - system stats "- does not show the discharge current of the battery and the percentage of CPU usage.

I stayed and tried everything that Bootstack found, it didn’t help me.

My phone is A2017, the battery was replaced with a new one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] giliev:
I am getting some battery issues after updating from 14.1.

With the same apps and usage my battery is lasting about 2-3 times less - around half a day.

There is also the issue that it doesn't sleep some times and I wake up in the morning to find out my phone went from 60% to zero during the night.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
First of all. Wrong thread to post in if you're trying GSIs. Second, I'll bet you are not waiting long enough on the boot screen. It really does take a long time, be patient. Also, not sure if wiping is necessary. I just flash the GSI image after a clean flash of LOS, no wiping.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Here is another problem I did not have with the unofficial 15.1... Everytime I quick charge the phone, the led turns red as expected but I can't wake the screen up. The phone seems to answer (it vibrates, the red light becomes green) but only a long press on power to reboot the phone works... Anything known or anything can help to troubleshoot the issue? It s a fresh install using Oki kit and the latest lineage is from October...

Edit: i have a pattern as lockscreen. Doing the pattern wakes up the screen so for some reason the pattern grid is not showing up
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Is there a way to get rid of bootloader unlocked warning on boot for a faster restart? I read about it for nfound's twrp before but now I'm on official latest
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chironfr:
I had the same problem see here

read to the end! ;)

After that I upgraded to team win recovery project 3.2.3-0L by oki that's ok.