yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
[MENTION=4911249]Unjustified Dev[/MENTION]

just tried your latest version, but gps stills shows me about 2 kilometers away from my actual location. I can fix this by using the gps fixer app, but as soon as I uninstall it and reboot it's back to the wrong location again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
[MENTION=4911249]Unjustified Dev[/MENTION]

- while on 20181029-UNOFFICIAL I can't disable location permission for google play services. It's allowed on the official builds with the same Gapps. It's imperative to me, as I do use only hardware GPS on my smartphones.

- searching the settings works on unofficial but it doesn't work on official
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hille2001:
Why is the unofficial Version better then the actual official one?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
I'm on official now.

Do I flash the zip attached first then flash unofficial. Or unofficial then the attached zip?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] levp:
1. Extract the file migration.sh from the Zip that has "TWRP" in the name into your Download folder.

2. Download the latest unofficial ROM Zip, GApps package (such as Opengapps for 8.1 64bit; I use nano version) and Magisk installation Zip.

3. Reboot into recovery and create a backup.

4. While still in recovery, choose Terminal.

5. At the prompt, type:

cd /sdcard/Download

chmod +x migration.sh

./migration.sh unofficial

6. Escape out of Terminal and flash ROM, GApps and Magisk as normal.

7. Wipe cache, reboot and profit ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
Thank you, much appreciated I will try that!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rx149:
Does anybody have a guide on how to downgrade back to 14.1 from 15.1?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CobraKolibry:
Probably the best way to go indeed, wiped everything, phone is decrypted now. Speakers are working as expected, I could change ringtones aswell. Good call!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mllora81:
Anyone having an issue using "Ok Google" or "Hey Google"?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Some1 with audio issues on an encrypted device pls send logs, in order to fix that issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Soyunamortz:
I'm saying because I don't have any ... To me the first build still running great 0 issues ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TPMJB:
Yeah, I wasn't sure if it was just people who encrypted within Oreo or all people who encrypted. I *thought* it was just those who encrypted with Oreo since there was also a problem with TWRP decrypting Oreo (but not Nougat.)

Basically what happens:

-Speakers do not work (I hear sound on the PIN entry screen on bootup, though.)

-Headphone jack works

-Bluetooth audio works

-Microphone works.

Weirdest issue ever.

A guy in another forum postulated that it had something to do with this: "Maybe theres some kind of audio config on data which cant be read on audio hal init because data is not avail at this time."
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Waancho:
Is this the same one as on the twrp website?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tvm76:
I would like to know this too. WiFi calling is essential for me. If it doesn't work on Lineage, does anybody know if it works on B12?

Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jbruff232:
I think I have created an "unrecoverable bricked device". I followed the instructions but it restarted mid-flash and now I can't boot into fastboot but can no longer get to recovery mode.

FML:crying:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
There is an option to enable it but it is disabled by default. When I enable it I don't see any icon or notification showing up like in stock nougat. I did not try to call yet but I'm wondering if I'll see any difference since I have good 4g coverage wherever I go.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
My best advice is to keep trying. Step away and let it charge.

If all else fails try the tool in the sticky thread

https://xdaforums.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514

The author of that thread is/was the original maintainer of the first official TWRP recovery for the Axon 7. Like, his method is the only "oh crap" one I trust.

I've had to do it once. Sometimes it took just the right drivers on my computer to recognize my device, the right key combination at the right time, and clicking buttons at the right time but eventually I stepped through the process to return to stock and then got back to Lineage.

Unless you relocked your bootloader while on a custom ROM you should be fine. If you did then maybe you can buy DrakenFX some beer to help you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cyrus D.:
Same issue. The command from the TWRP terminal says not found, and doing it through ADB does nothing.

I used the bootstack on the beta Oreo B12 ROM to be able to write to system and it appears partially working; I can't seem to permanently uninstall the ZTE apps like ZTE backup or the browser. Are those located somewhere else now, or is it actually a system writing issue? That and I have some odd issues now like Google Opinion Rewards, Skype, and VR Theatre crashing on startup whenever I try to run them.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Strange issue but every so often I get a message "Google has stopped ".

I am guessing it's related to gapps.

Other strange thing, but not major was the setup wizard kept looping for me on initial boot and it tried to get me to set up security twice. Luckily I could skip the second time and my fingerprint and pattern still worked. I'm sure this is also a gapps related issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
I get force closes when disabling WiFi for random system apps.

Example: disable WiFi for gallery
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
I get force closes when disabling WiFi for random system apps.

Example: disable WiFi for gallery or music.

Looks like the toggle tries to change iptables but throws an error about invalid argument and not understanding OWNER.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
Is there anything that we can do to help reduce the echo during voice calls? It seems like the other end hears echoing from their end for themselves and for myself.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AceNovel:
[MENTION=5027381]OrdenKrieger[/MENTION] how about adding CAD Project?

And please give sources to other developers. Perhaps [MENTION=5492451]NFound[/MENTION] [MENTION=7790189]Kranoner[/MENTION] [MENTION=6977124]Skrem339[/MENTION] [MENTION=4492089]kdp162[/MENTION] or someone else, will be able to add something interesting or useful which would accelerate the overall progress on our device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
I was experiencing this issue so thought i would reboot my phone. Now i have no sound out of the speakers at all. There is sound via the headphone jack however. Any suggestions for getting the speakers working again?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
Saw someone posted some while back:

1. The sound on call (using phone earpiece not bluetooth or headset) is too loud even on lowest volume (sound gets distorted / membrane vibrating due to volume too high), could this be somehow lowered ? Is there any config we can lower this volume ? I think this is the root cause also for the so called echo, the person you are talking to hears, due to earpiece being too loud, it is being captured by the microphone, creating an echo loop.

2. Sound is very slim sort of speaking on the speakers (also in call comparing with stock). Why is there such a big difference between the stock rom and lineage as both using same blobs / sound drivers right ? Could it be the missing Dolby Atmos audio DSP ? (actually never used the phone without Dolby enabled on stock rom, so possibly this would be the difference)

My device was not encrypted before installing Lineage 15.1 and seems never experienced the issue with missing sound on speakers after trying to change ringtone. Now on latest release from 07 June and still issue not seen. Seems indeed to be related to encryption.

Other than the two points, up until now device is fast and smooth, thanks to [MENTION=5027381]OrdenKrieger[/MENTION], UDev and others who worked to bring Lineage 15.1 to Axon 7. Battery could be better (but we have the battery mods I can try).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h3ndrik:
i'm also having troubles with (probably) the encryption option:

1. no sound at all via the speakers

2. twrp can't decrypt and access the storage. (both version from op and twrp.me)

is there any version of twrp that'll work with current encryption?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
[MENTION=249608]h3ndric[/MENTION]k: can you or anyone else please post logcat of the speaker problem when encrypted.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
confirm
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jrotaetxe:
Used the migration script, and so far, sogood.

I find it way more power friendly (the boots in official were melting my phone) and not any problem. Everything smooth, and considering my phone is heavy tweaked, I would say this uDev development is a clear go. Will check the GPS tthis afternoon with my sport app.

Thank you very much, sir

(Obs. Build 20181029)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
You will have to remove the vendor partition, either by using PARTY or by flashing a stock nougat rom. Then you need to flash the correct bootloader, modem and TWRP version, and then the rom with gapps. Check lineage 14.1 for those files.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
i have installed the offline chargin zip,but it doesnt show on how many percentage(%) the battery is

---------- Post added at 11:09 AM ---------- Previous post was at 11:07 AM ----------

are you sure,flashing stock rom with vendor partitions etc,will be safe? I recommend you not to do this.Delete vendor part first
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
I did this many times. Flashing a stock rom will repartition the device to factory settings. It's safe.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rx149:
Okay, so that's what I have been doing but I keep running into an issue where after I remove the vendor partition, flashing the correct bootloader, modem, and TWRP, and then the ROM I try booting up LOS and it gets to the boot animation, freezes, and then goes into EDL mode. I've tried multiple 14.1 ROMs at different build dates but all of them yield the same result.

This whole thing is ridiculous, I just want a working battery indicator.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sumade:
Does battery indicator not work at all in 15.1 for Axon 7? Are there any other bugs that someone has a summary of?

I am looking forward to using Lineage on Axon 7, but I am not sure at all what version to choose that is fully functional.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
uDev's unofficial build has fixes that aren't tested enough to go into the official build yet. Think of it more as a beta for the official build. There may be more bugs occasionally in a specific build but also more bug fixes overall.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tprfd:
The battery bug does not affect everyone.

There's 3 models of the phone, 3 modems, multiple bootstacks, multiple versions of TWRP, different file systems supported, multiple instructions on how to install, so I guess it's possible that if you pick a combo of the above that will cause the bug, you are unlucky.

I personally used oki's install method on page 126 and do not have any bugs except for maybe slightly worse battery life than stock.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sumade:
OK thanks, very much appreciated - will try that method and see how I get on!

There's a few comments regarding possible battery drain, i.e. really bad battery drain, but if it's possible to get only slightly worse battery life then that is good to know.

However, is it true that the method from Oki will result in no support for encryption? In post #1240 it was suggested that "the only TWRP version with working decryption is nfounds "3.2.1-8-TREBLE for android 8.x-9.x (new bootstacks)" "
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
Oki has two TWRP versions -- the normal one he ships as part of his EDL file, but also a separate one that works with encryption but loses adb support (which is based on nfound's TWRP version).

AFAIK, the official TWRP for our phone doesn't work with /vendor so it's kind of moot and the LOS "official" TWRP from this thread works with /vendor but not encryption.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tprfd:
The default TWRP supplied by Oki lacks support for decrypting an encrypted phone. So it won't be able to see your data and won't be able to do ota updates (because I think TWRP won't be able to see the downloaded update file). You can still encrypt, everything within lineage will still work and you can update the to the latest weekly lineage official build with ADB sideload. At least, this is what I have done. TWRP can't decrypt though. You can likely flash another TWRP version afterwards, though I never bothered yet so don't take my word for that... 'likely' is a big part of that sentence.

Regarding the battery drain, my experience is that I can make it through the full day still. However my phone is only 1 year old and I don't run games or run anything intensive. Compared to stock, it's about 80%-90% of the battery life, so not substantial but just enough to notice. There is possibly some good news with this as I believe the wonderful devs we have for this phone are testing fixes at this time in the unofficial version so hopefully the battery situation will be better shortly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sauerkraut17:
I don't 100% agree with that, I'll explain below.

[MENTION=3044858]DrakenFX[/MENTION]

[MENTION=4911249]Unjustified Dev[/MENTION]

[MENTION=5027381]OrdenKrieger[/MENTION]

Is there anything about these bootstacks which causes a permanent change?

As short as I can make this, I now have software navigation regardless of what I do trying to go back to stock (I do not have a development version of the phone and never had software navigation). I could jump between LOS 14.1 and stock (even re-locking the bootloader) multiple times via EDL, never had soft nav.

- Direct EDL to Nougat B15 from LOS 15.1 using B20 bootstack, results in soft nav appearing

- Direct EDL to Nougat B19 from LOS 15.1 using regular LOS 15.1 bootstack = software nav keys

- On LOS 15.1 either bootstack, wiping everything in TWRP and using party to remove vendor partition; rebooting to EDL and flashing B15, B19 or B35 = software nav keys

- EDL'ing from one stock to the other = software nav keys

- Reverting to LOS 14.1 and flashing the official B35 or B20 zips from ZTE in TWRP = still equals soft navbar

- I even tried this tool, NAVIGATION BAR Enabler/Disabler as a last resort, no dice

Basically, I am now stuck using LOS unless I want to have software navbar plus hardware nav. This wouldn't be such a problem if the hardware buttons were disabled, but having both them and soft navbar is a nightmare... Don't get me wrong, I love LOS and plan on staying on it, but would like to revert back to factory for whenever I decide to sell or give to someone as a replacement.

P.S. I am using the TWRP linked in the OP when on LOS 15.1, but I dont think that matters since I tried others during this whole adventure of mine.

Device ZTEA2017U
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
You re lucky ( I guess), in my case coming from stock nougat to lineage 15.1, I had no navigation bar and had to flash a magisk module and now they disappear when the screen is off for too long. I have no hardware navigation bar... I'm wondering if it's not an issue with the keylayout provided in vendor somehow conflicting with system's. Wiping cache and dalvik fixes the issue for couple of hours....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Hopefully the devs can help you with this. I just wanted to say that there are ROMs out there that allow you to disable the hardware buttons.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BJHiltbrand:
So, Something went very bad for me when trying to install this. I flashed the files as required and rebooted. The phone seemed like it was fine, and then I rebooted the phone again. Now, it just hangs on the warning screen for the unlocked bootloader. I can reboot to fastboot and to recovery, but twrp complains about not being able to mount /system and I can't get into EDL mode (It only shows up as DFU mode on my computer). Any thoughts as to how I should proceed to recover? Thanks.

EDIT: I figured it out. I had to re-format the system partition to get it to work again in TWRP, but then I was able to re-flash everything and it seems to have worked. Does anyone know if there might be any unintended fallout from having to re-format the system partition? Should I do anything special to make sure my phone is as clean as it can be? Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blackpac:
Generally speaking, most of the information on this device is all over the different Axon 7 threads in this forum. In order to try to understand what’s going on, one must gather all of the many scattered bits and pieces around and only than he might get a general idea of what most likely the issues are, what probably needs to be done and what is the less risky way to do so.

Highly respected members of the Axon 7 community members as [MENTION=5334294]raystef66[/MENTION] and [MENTION=319057]Oki[/MENTION] did most of the work for us with their very informative threads but unfortunately, a lot of information is still missing.

For instance, a number of modded bootstacks are available but still, not much is known with regards to the advantage/disadvantage of any one of then and their different versions.

I still remember the long struggle I had to have system r/w, tried all kind of tools and commands to get this thing to work, but only after the universal Oreo bootstack was released I was able to achieve that, it was all because of the bootstack. The fact it was a bootstack related issue was not publicly known prior to the release.

Bootstacks were and still remains a mystery…
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h321b:
Two days ago I switched from 20181008-Official to 20181029-Unofficial and very happy with that! It gives me 10 to 20% more Battery life at the end of the day. GPS works fine, no GPS fixer app needed. No FC's, no reboots. Hotspot and NFC working ok. I have not been able to test NFC beam, however. Imo Rom is stable and snappy.

Thanks for your excellent work, [MENTION=4911249]Unjustified Dev[/MENTION] :o I still love my Axon 7!

Model: A2017 Chinese,

Bootstack: UniversalBootstack_v2_by_DrakenFX
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lilbluemirage:
Are you rooted? If so, have you tried checking/editing the build.props for qemu.hw.mainkeys=0?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
You have to use TWRP 3.2.1-8-TREBLE (https://androidfilehost.com/?fid=5862345805528058637)from the thread I linked, then it should work fine. But I have removed encryption from my device because it es easier to handle bootstack change etc. So I can not check if the fresh builds of LOS 15.1 also work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wroclawiak:
penguin...

when i get "scary screen" i pushed power button once

and I get a penguin...

then I push power button once again - but penguin i still there and watchibg me...

nothing happend - penguin is still there

my computer can not connect to pc - pc can not see axon...

so adb not working, edl , fastboot etc...nothing works
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
When on the bootloader warning screen, if you hit volume down button do you see option for recovery? Press volume down until it highlights recovery then hit power. Should at least get you into TWRP to flash things, as well as connect to PC.

If this isn't working for you, try powering off, then power on while holding the volume up key. Don't let go of volume up until you see TWRP recovery boot.

I know these are simple options you may have tried already, but I didn't see them mentioned in your attempts.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wroclawiak:
problem is that I can not go to TWRP - i have black screen when i try to go to TWRP...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Yikes... Yeah you're going to need to EDL somehow. Check your drivers are up to date. Plug into PC while holding down all three buttons. Look in device manager, does it show DFU or Qualcomm?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
Anyone experiencing the out of sync flash when taking a photo? I'm currently on the latest unofficial build but this issue has continually existed for me in past official and unofficial builds.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wroclawiak:
My pc can not recognize AXON7...

I have drivers...but pc can not see ogólne

do i can not flash anything

---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------

3 buttons not working...AXON7 restarts and restarts and....when i try this

Nothing shows in device manager...

---------- Post added at 09:59 PM ---------- Previous post was at 09:56 PM ----------

I tried this...nothing appears im device manager..

---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------

Nothing appears in device manager...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
Does anyone know if currently battery life on Lineage 15.1 (with all the additions from official B20 and newer drivers) is better than on Lineage 16, as the 16 thread seems abandoned and thinking of switching back to 15.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] roisuke:
No, not really. With moderate YouTube videos and browsing with WiFi and 4g lte when out and about I barely get more than 4 hours. Don't expect a massive improvement.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
If this is the case there is no point in opening your phone. Just send it back to ZTE.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Change pc, cables, USB port etc

But it seems you are doing it wrong and your phone is just turned off
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wroclawiak:
I have done it...

3 pc - Win7 32b, win 8.1 64b, win10 64b...

3 USB. cables, + 1 bought deep flash cable + 1 hand made deep flash cable

Still nothing on device manager...

I'm loosing hope...

Tel me how to do it right way, please
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
Have you been able to patch system with nanodroid?

On unofficial build of 29.october it did not work for me. (takes long time without success)

Gesendet von meinem Redmi Note 4 mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
make sure phone is off and turn it on and connect to a pc

check if at least windows makes a sound, it should, even if the phone is bootlooping
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wroclawiak:
I do that's way:

In boot menu i choose POWER OFF

then connect to PC using USB cable

then

-power on or

-3 buttons

- or every cmbinations of buttons...

still ...no sound, nothing new in device manager...