• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7

Search This thread

runninghamster

Senior Member
Dec 30, 2017
409
340
Melbourne
ZTE Axon 7
Once I do that do I just drop them in my Lineage OS 16 repo and build? Or is there something else that I need to do? Thanks for your help.
If you're wanting to build LineageOS, then make a folder in your ~ directory, and sync the Los 16 repo into it, and git clone each one of the Axon's repos into the folder.
ex:
Kernel sources cloned into kernel/zte/msm8996
Device sources cloned into device/zte/axon7
Vendor sources cloned into vendor/zte
Then you can start building.
 
  • Like
Reactions: Zobat and TheZaxor

SugnaB

Member
Jun 16, 2016
23
0
-UPDATE-

Changelog:
DOWNLOAD
lineage-16.0-20190728-UNOFFICIAL-axon7.zip

So this might be a stupid question, but. I have a ZTE axon 7 with the official lineage OS 15.1 on it (last updated 17th of May 2019). Am i able to just download this unofficial build and flash it, and everything will be okay?
 

dutchbird

Member
Jul 14, 2019
16
9

Vielen dank!
I am already on unofficial 15.1. Any idea whether the script will then also work?

---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------

Vielen dank!
I am already on unofficial 15.1. Any idea whether the script will then also work?

Disregard. Found the answer already! It should work.
 

captainhase

Senior Member
May 22, 2007
99
21
In this thread I posted in a link in post 2491 and 2500 which brings you to the original post with the link for the script and a description how to use it.

Gesendet von meinem GM1903 mit Tapatalk
 
  • Like
Reactions: SugnaB

SugnaB

Member
Jun 16, 2016
23
0
In this thread I posted in a link in post 2491 and 2500 which brings you to the original post with the link for the script and a description how to use it.

Gesendet von meinem GM1903 mit Tapatalk

Thanks lol. Your link wasn't taking me to that post which was weird.
Also i think i have ran into a problem... so at the step

"5. At the prompt, type:
cd /sdcard/Download
chmod +x migration.sh
./migration.sh unofficial"

I typed in ./migration.sh unofficial wrong.. i wrote it "unoffical". So it didn't go through, then i continued the steps and installed the ROM and everything. The booting of my phone was taking too long, waited about 20mins and didnt boot. Then i went back and found out i typed it int wrong. So i typed it in right and reflashed the ROM only again and wiped the cache... Did i ruin the flash? Do i have to flash a 15.1 rom and then follow the steps or have i bricked my phone? It's currently been booting for 5mins (stuck on the lineage boot logo)

Edit: Fixed it by going back and forth.. god Android 9 is hideous lmao
Edit 2: Just found out it was magisk causing me boot loops. Anyone know any fixes? I tried uninstalling it with a script but the script said magisk wasn't installed after i just flashed it
Edit 3: tried reflashing unofficial build again and now im stuck in a boot loop again...
 
Last edited:

carpeta

Member
Mar 13, 2011
10
1
I have a problem with the last ROM version 20190729.
I don't know if anyone noticed it at all, but with every reboot my Wifi adapter gets a new virtual MAC address. For many this may not be a problem, but with my home network an additional MAC address filtering is stored as security, so that I had to enter the new address after each restart of the device (otherwise I would probably never have noticed the bug).
The Version 20190728 doesn't have the problem and works as it should.
 

apoha

Member
Jul 18, 2019
15
15
I have a problem with the last ROM version 20190729.
I don't know if anyone noticed it at all, but with every reboot my Wifi adapter gets a new virtual MAC address. For many this may not be a problem, but with my home network an additional MAC address filtering is stored as security, so that I had to enter the new address after each restart of the device (otherwise I would probably never have noticed the bug).
The Version 20190728 doesn't have the problem and works as it should.

Android P will be featuring an additional security feature known as “MAC address randomization,” which will randomize your device's MAC address every time it connects to a network.[/QUOTE]

It is not a bug it is a feature. (I always wanted to say this phrase :) )
 

king1990

Senior Member
Oct 13, 2012
428
786
I have a problem with the last ROM version 20190729.
I don't know if anyone noticed it at all, but with every reboot my Wifi adapter gets a new virtual MAC address. For many this may not be a problem, but with my home network an additional MAC address filtering is stored as security, so that I had to enter the new address after each restart of the device (otherwise I would probably never have noticed the bug).
The Version 20190728 doesn't have the problem and works as it should.
That is a bug because of sepolicy denials because the latest build enforce SElinux while previous one didn't, its already fixed in other custom pie ROMs but if using los16 is must then use permissive patch

Android P will be featuring an additional security feature known as “MAC address randomization,” which will randomize your device's MAC address every time it connects to a network.[/QUOTE]

It is not a bug it is a feature. (I always wanted to say this phrase :) )
In this case it's a bug not a feature, MAC address randomization is not available in los16
 
  • Like
Reactions: olus

[armitage]

Senior Member
Nov 26, 2010
522
461
The thing is we already had that same problem in 15.1 but I think it was Udev who fixed back then. Now it seems to be back in Lineage 16.
 

king1990

Senior Member
Oct 13, 2012
428
786
The thing is we already had that same problem in 15.1 but I think it was Udev who fixed back then. Now it seems to be back in Lineage 16.
the fix udev did is still working in los16 but oreden in his latest build did not fix a wifi hal denial that prevent reading the correct mac address see this commit , this commit will fix the issue and has been tested on all other pie ROMs
you can also check these post for more information
1
2
3
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    I have seen that runninghamster0 has rebased the kernel. In the new kernel source the patches until ASB 2020-08 seem to be included. Therefore I have compled the most recent build using his kernel.

    I also swapped the soft buttons that no 3rd party app is needed to have the soft keys as
    If you don't like, you could just use the patch from @raystef66.

    img2.png

    2
    Thank you so much for keeping this alive, and patched. I've just come from RR and couldn't be happier. Cheers
    Exactly the same. Recently migrated over from RR a few days ago and it's been running nicely.
    1
    You're an absolute champ, keeping this thing up to date on patches!
    1
    Thank you so much for keeping this alive, and patched. I've just come from RR and couldn't be happier. Cheers
  • 80
    http%3A%2F%2Fi.imgur.com%2F2okPze5.png


    About Lineage OS:

    Lin·e·age
    /ˈlinēij/
    noun
    lineal descent from an ancestor; ancestry or pedigree.
    a sequence of species each of which is considered to have evolved from its predecessor.


    Disclaimer:
    LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.


    Warning:
    This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Also does any build from now on require a vendor partition, by doing this you will lose the ability to flash official builds provided by ZTE. Any failure in this process of flashing or repartitioning could lead to an unrecoverable bricked device.

    What's not working:
    SELinux is permissive

    Instructions:
    Attention! The bootloader needs to be unlocked!
    Attention! You'll need a vendor partition!
    1. Install the Universal bootloader and your model specific modem. Download
    2. Flash vendor creation tool. Download (unnecessary, if done already)
    * On first flash the device will reboot, just reboot to recovery and reflash the zip.
    3. Update your version of TWRP. Download
    4. Perform a backup of your current ROM. (optional)
    5. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
    6. Install the ROM. Download
    7. Install GApps. (optional) [Recommended -> Open GApps (arm64) (9.0)]
    8. Reboot.

    What is CAF?
    Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.

    Sources, Changes, & Wiki:
    Source | Changes | Axon 7 Wiki | Lineage OS

    Credits:
    @Unjustified Dev
    @DrakenFX

    XDA:DevDB Information
    [UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7, ROM for the ZTE Axon 7

    Contributors
    OrdenKrieger, Unjustified Dev
    Source Code: https://github.com/OrdenKrieger/android_kernel_zte_msm8996

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.x
    ROM Firmware Required: O bootloader + region modem
    Based On: LineageOS

    Version Information
    Status: Testing

    Created 2018-08-19
    Last Updated 2019-07-28
    52
    -UPDATE-

    Changelog:
    • 2018-09-05 Security Patch (android-9.0.0_r6)
    • Kernel based on newest P CAF tag release (LA.UM.7.6.r1-02000-89xx.0)
    • CNE, DPM, IMS, and RIL blobs updated from Axon M (fujisan) thx to @Unjustified Dev
    • Wlan based on newest P CAF tag release
    • Bluetooth based on newest P CAF tag release
    • RIL based on newest P CAF tag release
    • Fix API1 compatible camera ids, if HAL3 is enabled LineageOS Gerrit
    • Use thermal engine configuration from marlin (Google Pixel XL)
    • Some useful repopicks (e.g. APN updates, icons etc.)
    • LineageOS repo sync
    DOWNLOAD
    lineage-16.0-20180907-UNOFFICIAL-axon7.zip
    51
    Sorry for the inconvenience, didn't notes that LineageOS pushed the new CAF display,media and audio HALs to github. Since our display/media blobs are still based on an Oreo CAF tag, these cause issues with newer P CAF HALs. Next build scheduled for today.
    44
    -UPDATE-

    Changelog:
    • 2018-11-05 Security Patch (9.0.0_r16)
    • Kernel and qcacld-2.0 to LA.UM.7.5.r1-03100-8x96.0
    • Update DRM from Pixel XL (marlin)
    • Update GPS to LA.UM.7.5.r1-03100-8x96.0
    • Update SDM, Vulkan blobs
    • Update CNE, DPM, IMS, and RIL blobs from Axon M (fujisan)
    • Changes from B20 stock build imported
    • Smaller misc fixes
    • Repo sync LineageOS
    DOWNLOAD
    lineage-16.0-20181114-UNOFFICIAL-axon7.zip
    44
    -UPDATE-

    Changelog:
    • SD cards not being detected fixed
    • Snap and Qcom Gallery2 are back
    • ANT+ enabled again and blobs updated for P
    • IPACM enabled again and updated for P
    • Marlins (Pixel XL) brightness curve is used now
    • Smaller misc fixes
    • Repo sync LineageOS
    DOWNLOAD
    lineage-16.0-20180918-UNOFFICIAL-axon7.zip