[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9

Search This thread
New build with May 2021 ASB patches available

Hi all,
a new build is available for download:
  • ASB Security String 2021-05-01
  • Replaced LineageOS/AOSP Camera with Huawei Stock Camera *
  • Fixed image size of system.img, so flash issues with some devices should be fixed
  • Fixed Firmware display info in case of B552 (was still showing as B550 before)
  • AuroraServices updated to version 1.1.1
  • Bromite Webview updated to 90.0.4430.204
_________________
* Although not all features (e.g. slow motion) work, the offered and working functionality by far exceeds, what the shipped LineageOS Camera is able to do

Happy flashing!
Regards, M.
 

Nezus3301

Member
  • Aug 14, 2020
    26
    4
    28
    Samsung Galaxy S3 Neo
    Huawei P9
    New build with May 2021 ASB patches available

    Hi all,
    a new build is available for download:
    • ASB Security String 2021-05-01
    • Replaced LineageOS/AOSP Camera with Huawei Stock Camera *
    • Fixed image size of system.img, so flash issues with some devices should be fixed
    • Fixed Firmware display info in case of B552 (was still showing as B550 before)
    • AuroraServices updated to version 1.1.1
    • Bromite Webview updated to 90.0.4430.204
    _________________
    * Although not all features (e.g. slow motion) work, the offered and working functionality by far exceeds, what the shipped LineageOS Camera is able to do

    Happy flashing!
    Regards, M.
    hi there, I've just flashed the rom update and everything root related that I edited on the last update, got resetted.
    Infact I can't use Magisk anymore, the fix that i made on the old rom, was deleting su on bin and xbin, but now I can't do it anymore and dk why.

    step that I made:

    I use as root explorer Amaze, I tried to delete su from there but an error displays: Can't delete this file 1. su

    i tried to delete su from adb (adb rm -f /system/xbin/su) but nothing happens because i can't reach the root (adb root , adb remount)
     
    hi there, I've just flashed the rom update and everything root related that I edited on the last update, got resetted.
    Infact I can't use Magisk anymore, the fix that i made on the old rom, was deleting su on bin and xbin, but now I can't do it anymore and dk why.

    step that I made:

    I use as root explorer Amaze, I tried to delete su from there but an error displays: Can't delete this file 1. su

    i tried to delete su from adb (adb rm -f /system/xbin/su) but nothing happens because i can't reach the root (adb root , adb remount)
    Normally, if you enable root for ADB and apps in the developer options, you should be able to work with 'adb root' & 'adb remount'.
    Independently, if you simply flashed the system.ing via fastboot, your patched ramdisk.img for Magisk hasn't been touched, so I don't see any reason, why there should be an issue.
    However, based on the previous discussions we had, I am still not sure, what exactly you have done with your device. I only got the feedback from you, that you were able to fix the problem...

    EDIT:
    For the most recent Magisk version, the Huawei instructions have been removed from the official Magisk install instructions.
    Quote: "P.S.2: Huawei devices are not supported, and the instructions are removed from this page."
    Not sure, whether you have upgraded Magisk, so I'd stick with the last working version of Magisk.
     
    Last edited:

    Nezus3301

    Member
  • Aug 14, 2020
    26
    4
    28
    Samsung Galaxy S3 Neo
    Huawei P9
    "Normally, if you enable root for ADB and apps in the developer options, you should be able to work with 'adb root' & 'adb remount'."
    in developer options, this section doesn't exist anymore, unless it changed its name while translating everything in italian (but i don't think so)
    Is there a way to enable root adb?

    However, based on the previous discussions we had, I am still not sure, what exactly you have done with your device. I only got the feedback from you, that you were able to fix the problem...
    on the older rom you have pubblished, when i installed magisk, the only thing i did to make work magisk and fix the "an abnomal su is in your device, please delete it and then reinstall magisk" error, i was searching the file in the root but nothing, when i tried to make the root work, i tried to open an app that requires root to see if i did something: it was titanium backup, and on the error window, he said actually where the su file, that i had to delete, are.

    /system/bin/su
    /system/xbin/su

    i delete them with a root explorer from my device, Amaze, i reinstalled magisk and everything worked just fine.

    i don't know if i did something bad when flashing your latest rom two/three days ago, but that error on magisk popped out again when i flashed the rom and i did again that deleting thing, on bin i did it succesfully, but not on xbin, so there i am.
    i opened just now xda, waiting for your reply, so i didn't touch anything from the day i sended the message
     
    Last edited:
    in developer options, this section doesn't exist anymore, unless it changed its name while translating everything in italian (but i don't think so)
    Is there a way to enable root adb?
    Okay - that means, that Magisk as such is already active, as the "redirection" of /system is already in place...

    on the older rom you have pubblished, when i installed magisk, the only thing i did to make work magisk and fix the "an abnomal su is in your device, please delete it and then reinstall magisk" error, i was searching the file in the root but nothing, when i tried to make the root work, i tried to open an app that requires root to see if i did something: it was titanium backup, and on the error window, he said actually where the su file, that i had to delete, are.

    /system/bin/su
    /system/xbin/su

    i delete them with a root explorer from my device, Amaze, i reinstalled magisk and everything worked just fine.
    ... I am no Magisk expert - I also don't use it myself, but I have an idea:

    You seem to be in a "catch 22" situation:
    - Magisk is already active and thus you can't use the shipped root solution any longer
    - Magisk however is not happy and does not let you use its own root option
    - So you have no root, but you need root to make Magisk "happy"

    If my assumption is correct, then this would be the way forward:
    - Get an unpatched RAMDISK.img from Huawei Stock firmware and flash it via fastboot
    - Now, Magisk isn't active any longer and you can make use of the shipped root solution
    - Via 'adb root' & 'adb remount', purge the files you want/need to purge
    - Re-flash the patched RAMDISK.img, if you still have it somewhere; otherwise, start installing Magisk from scratch

    Needless to say, this happens on your own risk. It's an idea of mine, and I can't give you any assurance.
     

    Nezus3301

    Member
  • Aug 14, 2020
    26
    4
    28
    Samsung Galaxy S3 Neo
    Huawei P9
    Okay - that means, that Magisk as such is already active, as the "redirection" of /system is already in place...


    ... I am no Magisk expert - I also don't use it myself, but I have an idea:

    You seem to be in a "catch 22" situation:
    - Magisk is already active and thus you can't use the shipped root solution any longer
    - Magisk however is not happy and does not let you use its own root option
    - So you have no root, but you need root to make Magisk "happy"

    If my assumption is correct, then this would be the way forward:
    - Get an unpatched RAMDISK.img from Huawei Stock firmware and flash it via fastboot
    - Now, Magisk isn't active any longer and you can make use of the shipped root solution
    - Via 'adb root' & 'adb remount', purge the files you want/need to purge
    - Re-flash the patched RAMDISK.img, if you still have it somewhere; otherwise, start installing Magisk from scratch

    Needless to say, this happens on your own risk. It's an idea of mine, and I can't give you any assurance.
    so, where should I take the un-patched Ramdisk.img?
    no clue that somehow I ****ed up the files just to make work magisk, in that case, if I flash the RAMDISK.img, can this affect my data? should I take a backup?
     
    so, where should I take the un-patched Ramdisk.img?
    From the same place you took it when you installed Magisk the 1st time. Normally, you were in need of it already at that time...?
    (I had offered you a while back to provide it to you, but you said you didn't need it. As I am not at home right now and I have the Huwei firmware files and extractor software plus VM to run Windows only on my home PC, I could earliest do so in about 10 days from now. If you still need it by then, just let me know.)
    Important: Don't grab any "random" RAMDISK.img, you may find when looking around in the internet! You are on a specific firmware version, most probably either B540, B550 or B552 - and the RAMDISK.img must be from the same firmware version.

    no clue that somehow I ****ed up the files just to make work magisk, in that case, if I flash the RAMDISK.img, can this affect my data? should I take a backup?
    Normally, flashing RAMDISK.img won't harm your data. But taking a backup is always a good practice.
     

    zgfg

    Senior Member
  • Oct 10, 2016
    5,315
    2,623
    so, where should I take the un-patched Ramdisk.img?
    no clue that somehow I ****ed up the files just to make work magisk, in that case, if I flash the RAMDISK.img, can this affect my data? should I take a backup?
    What was your last b5xx installation?
    E.g., if it was b550, you need to download its update.zip and unzip to extract update.app.
    Then use Huawei Update Extractor (find its thread on XDA) to extract Ramdisk.img from update.apk and then patch it.

    Procedure is the same as if you stayed on b55x (without going to LOS) or if you went to OpenKirin ROMs, hence Magisk installation has been described in those threads and so (although maybe for b540 and some older Magisk versions - but procedure is still same)

    Nevertheless, if somebody has the same b5xx as you do, he can give you his ramdisk.img he already extracted or even his
    patched ramdisk ing (then you just flash and you will have the same Magisk version as he patched by).
    But it's crucial that ramdisk.img is from the same b5xx

    Edit:
    Ramdisk is different partition from System or Data, hence it will not wipe or whatever your apps, settings and data.

    If anything goes wrong, you just flash back the original ramdisk.img

    When you install Magisk apk, it has link to Magisk Github, find Wiki there with detailed instructiions for Magisk Installation (with special section for Huawei)

    PS: With TWRP, you can backup (to SD card!!!) ramdisk.emmc.win (assuming you didn't tamper yet with Ramdisk) and then patch by Magisk that file instead of the ramdisk.img
     
    Last edited:

    Nezus3301

    Member
  • Aug 14, 2020
    26
    4
    28
    Samsung Galaxy S3 Neo
    Huawei P9
    What was your last b5xx installation?
    E.g., if it was b550, you need to download its update.zip,unzip to extract update.app.
    Then use Huawei Update Extractor (find its thread on XDA) to extract Ramdisk.img and to patch it.

    Procedure is the same as if you stayed on b55x (without going to LOS) or for OpenKirin ROMs, hence Magisk installation has been described in those threads and so (although maybe for b540 and some older Magisk versions - but the procedure is same)

    Nevertheless, if somebody has the same b5xx as you do, he can give you the ramdisk.img he already extracted or even the patched ramdisk ing (then you just flash and you will have the same Magisk version as he patched by).
    But it's crucial that ramdisk.img is from the same b5xx

    Edit:
    Ramdisk is different partition from System or Data, hence it will not wipe or whatever your apps, settings and data.

    If anything goes wrong, you just flash back the original ramdisk.img

    When you install Magisk apk, it has link to Magisk Github, find Wiki there with detailed instructiions for Magisk Installation (with special section for Huawei)

    PS: With TWRP, you can backup (to SD card!!!)armdisk.emmc.win (assuming you didn't tamper yet with Ramdisk) and then patch by Magisk that file instead of the ramdisk.img
    wait, this sounds familiar, i remember that to make everything work (also the step from android 7 to 8) i had to rebrand my phone, i have in a folder where i store all my phones data in, there's a System folder that leads me to this:
    Screenshot (106).png

    and that remembered me the rebrand software where should be the last update zip i flashed with that: b540

    in magisk folder:
    Screenshot (107).png


    there's a file named AL10c00b540_Patch02-Magisk_20400-Encrypt_AVB-Ramdisk.img
    is it the right ramdisk?
     
    Last edited:

    Nezus3301

    Member
  • Aug 14, 2020
    26
    4
    28
    Samsung Galaxy S3 Neo
    Huawei P9
    From the same place you took it when you installed Magisk the 1st time. Normally, you were in need of it already at that time...?
    (I had offered you a while back to provide it to you, but you said you didn't need it. As I am not at home right now and I have the Huwei firmware files and extractor software plus VM to run Windows only on my home PC, I could earliest do so in about 10 days from now. If you still need it by then, just let me know.)
    Important: Don't grab any "random" RAMDISK.img, you may find when looking around in the internet! You are on a specific firmware version, most probably either B540, B550 or B552 - and the RAMDISK.img must be from the same firmware version.


    Normally, flashing RAMDISK.img won't harm your data. But taking a backup is always a good practice.
    also that's ok, i have to use the phone normally (aka without using root stuff) it's my main phone so i always do the things carefoully even if i spend too much time, i can wait for you, nntw :)
     
    Last edited:

    zgfg

    Senior Member
  • Oct 10, 2016
    5,315
    2,623
    Huawei section has been removed, it now says "no support for Huawei devices"
    Bad luck for those who stayed on Huawei

    Btw, do you have Magisk installed and which vdrsion?

    Bcs, I've seen a report in XDA General Magisk thread that only Magisk v20.4 (the latest is now v23) or older work for P10 with EMUI 8 (same case, patching to its ramdisk.img) - if so, that's the reason Huawei was removed from Magisk Wiki

    (I don't have P9 anymore or any Huawei). When I did have, it was b540 and Magisk v20 4 and the Magisk procedure I commented above perfectly worked.
    I can still find on my PC the ramdisk.img from b540 and its patched by Magisk b540 counterpart, and I can share - but only for those who did not upgrade from b540 to b55x (and who are willing to stay on old Magisk)
     
    • Like
    Reactions: MSe1969

    Nezus3301

    Member
  • Aug 14, 2020
    26
    4
    28
    Samsung Galaxy S3 Neo
    Huawei P9
    Bad luck for those who stayed on Huawei
    also yeah, i'm waiting summer so hard, so i can get a job and buy a oneplus, it's my dream-phone
    Btw, do you have Magisk installed and which vdrsion?

    Bcs, I've seen a report in XDA General Magisk thread that only Magisk v20.4 (the latest is now v23) or older work for P10 with EMUI 8 (same case, patching to its ramdisk.img) - if so, that's the reason Huawei was removed from Magisk Wiki

    (I don't have P9 anymore or any Huawei). When I did have, it was b540 and Magisk v20 4 and the Magisk procedure I commented above perfectly worked.
    I can still find on my PC the ramdisk.img from b540 and its patched by Magisk b540 counterpart, and I can share - but only for those who did not upgrade from b540 to b55x (and who are willing to stay on old Magisk)
    btw I have b540 with magisk v22.1
    there's an update but just because that happened, i still didn't update magisk
     

    zgfg

    Senior Member
  • Oct 10, 2016
    5,315
    2,623
    wait, this sounds familiar, i remember that to make everything work (also the step from android 7 to 8) i had to rebrand my phone, i have in a folder where i store all my phones data in, there's a System folder that leads me to this:View attachment 5308135
    and that remembered me the rebrand software where should be the last update zip i flashed with that: b540

    in magisk folder:
    View attachment 5308137

    there's a file named AL10c00b540_Patch02-Magisk_20400-Encrypt_AVB-Ramdisk.img
    is it the right ramdisk?
    The (long) file name is the same as I have on my Mega - you probably downloaded from my Mega (link was in the HWOTA7 thread, even in the OP posts). You can compare your file with:

    There you can find also my original ramdisk.img and Magisk Manager v7.5.1 (companion to that old Magisk v20.4)

    See my another post here, before this one, about Huawei instructiions been removed from Magisk Wiki

    PS: As my name says, it was ramdisk.img taken from b540 Patch02 (at that time there was OTA Patch02 but later Huawei added direct OTA to b55x).
    As far as I can recall (I see I have removed ramdisk.img corresponding to b540 without Patch02), b540 and b540 Patch02 had the same Ramdisk (I did compare checksums)

    Therfore, this will be good for b540 (but not b55x if you upgraded to) and you will have to use that Magisk Manager v5 7.1 and turn off Check for Magisk update in Magisk Manager)

    But better take the ramdisk.img (and Magisk patched one) from @MSe1969, since he has it working for Magisk v22, and use the same Magisk mngr/apk as him
     
    Last edited:

    zgfg

    Senior Member
  • Oct 10, 2016
    5,315
    2,623
    so, as you said, the file i said before is the right one, but it's the patched one from magisk manager 7.1, once i flashed the ramdisk Patch02 img, i can update magisk without any problems, am i right?
    Not sure. As I wrote above in one of the answers, somebody with P10 (I think) and also EMUI 8 complained that he could not update Magisk anymore.
    You can always try, and if not working flash back the old working patched ramdisk img
     

    Nezus3301

    Member
  • Aug 14, 2020
    26
    4
    28
    Samsung Galaxy S3 Neo
    Huawei P9
    (I had offered you a while back to provide it to you, but you said you didn't need it. As I am not at home right now and I have the Huwei firmware files and extractor software plus VM to run Windows only on my home PC, I could earliest do so in about 10 days from now. If you still need it by then, just let me know.)
    also, when you can reach your pc and use it, can you send me the unpatched ramdisk? so whenever something goes wrong i can reflash it :)
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 2
      New build with June 2021 ASB patches available

      Hi all,
      a new build is available for download (install instructions in OP):

      • ASB Security String 2021-06-01
      • Bromite Webview updated to 91.0.4472.102
      • microG 0.2.19211515-9
      Happy flashing!
      Regards, M.
      1
      let me explain, I remember that when on emui 5, if you long press the vol - button when display's off, it does a sound, you say a name from your contacts and it calls it for you if the vocal search understood what you said,
      EMUI in general is a whole proprietary software on system level with UI and many features provided - seems that the feature you have described is or was part of it - however, not an AOSP / LineageOS feature. So I can't do anything about it.

      another thing if you can put the stock music app, because it was very cooler than the music app on lineage.
      There are many good music apps out there, (e.g. I use VLC) - I don't see the benefit of trying to get the Huawei Stock Music app running, which is most probably deeply integrated into EMUI (which does not exist on the /system partition). . .
      I know that the LineageOS Eleven app has some issues in LineageOS 16.0, but e.g. VLC really works flawlessly for me.

      Here's a problem with the songs of every type I have in my phone: when the phone restarts, my clock alarms set the song on the default alarm, overwriting the songs i set as alarm. Another strange thing is the ringtone, when someone calls me, even this if I set a song as my phone ringtone, it always plays the default one.
      I can't observe this behavior on my device. Can you produce some logs?

      The strangest and the most annoying one is the music app, I don't know if it's a bad flash that does this thing but when I play some music with bluetooth earphones, everything works just fine, when I try with the speakers, it's a 75% that the song doesn't even play, the minute counter goes forward but I can't hear it, the other 25% works or it does work but it suddently stops and refuses to skip to the next song
      Whilst I was a happy user of the LineageOS Eleven app in LineageOS 15.1, I have stopped using it in LineageOS 16.0 due to various reasons, I could solve some by backporting commits from LineageOS 17.1, but eventually, I have started to use VLC and I really recommend it. One annoying thing I have recently detected is, that it won't play songs downloaded from NewPipe (maybe because of new codecs?); maybe a similar thing as you observed - VLC works fine for me, as mentioned already.
      1
      EMUI in general is a whole proprietary software on system level with UI and many features provided - seems that the feature you have described is or was part of it - however, not an AOSP / LineageOS feature. So I can't do anything about it.


      There are many good music apps out there, (e.g. I use VLC) - I don't see the benefit of trying to get the Huawei Stock Music app running, which is most probably deeply integrated into EMUI (which does not exist on the /system partition). . .
      I know that the LineageOS Eleven app has some issues in LineageOS 16.0, but e.g. VLC really works flawlessly for me.


      I can't observe this behavior on my device. Can you produce some logs?


      Whilst I was a happy user of the LineageOS Eleven app in LineageOS 15.1, I have stopped using it in LineageOS 16.0 due to various reasons, I could solve some by backporting commits from LineageOS 17.1, but eventually, I have started to use VLC and I really recommend it. One annoying thing I have recently detected is, that it won't play songs downloaded from NewPipe (maybe because of new codecs?); maybe a similar thing as you observed - VLC works fine for me, as mentioned already.
      infact it was Music Eleven the problem, VLC apparently fixed the problem, and i used that app to set my ringtone so... problem kinda solved, if anything else happens I'll let you know
    • 14
      This thread is dedicated to provide Lineage-OS 16.0 builds with microG included for the HUAWEI P9 with current security patches.

      It is a treble build, therefore it could also work on other devices, but I haven't tested. And yes, the camera works!

      Features of this ROM
      Download here
      • Pre-installed microG and F-Droid like the LineageOS for microG project (own fork)
      • Pre-installed AuroraStore
      • Root included (switch on in dev. settings)
      • eSpeakTTS (FOSS TTS engine)
      • Additional security hardening features listed below
      • Access to /proc/net blocked for user apps
      • Bundled netmonitor app to allow network monitoring
      • Enhanced Privacy Guard: Switches for motion sensors and other sensors
      • Cloudflare as default DNS (instead of Google)
      • Privacy-preferred default settings
      • Optional blocking of Facebook- and Google-Tracking
      • Optional disabling of captive portal detection
      • Firewall UI
      • No submission of IMSI/phone number to Google/Sony when GPS is in use
      • Default hosts file with many blocked ad/tracking sites
      • Privacy-enhanced Bromite SystemWebView
      • Additional restrictions for secondary users
      • Increased password length
      • Hardened bionic lib and constified JNI method tables
      • Huawei Stock Camera

      Current release levels
      Security string: 2021-06-01
      AOSP tag: 9.0.0_r46
      Bromite System Webview: M91


      Source-code and build instructions
      Device config.: https://github.com/lin16-microg/device_phh_treble/tree/lin-16.0-eva-p9
      Build manifest: https://github.com/lin16-microg/local_manifests/tree/lin-16.0-treble


      Installation Instructions

      YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!

      Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty of information available.

      Pre-Requisites
      • Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
      • An unlocked bootloader
      • EMUI 8.0 firmware

      ONLY, If the above pre-requisites are met, download and unpack the linked ZIP file, and flash the .img file via fastboot.
      The OpenKirin installation instructions describe this in a very good way, I could not really explain it better (please note, that I have no relation to them, but they are really doing an amazing job!)
      Some hints:
      • If you come from an EMUI 8.0 stock ROM or a different treble build (which means, you are already on EMUI 8.0), don't forget the factory reset as described.
      • If you update one of my builds from this thread, you don't need to wipe anything
      • On some (but not all) PCs, you may have to run fastboot as Admin (Windows) or root/sudo (Linux)

      If the above pre-requisites are NOT met, you will have some extra-rounds to perform, until you get there:
      Unlocked Bootloader
      Huawei has stopped providing unlock keys, so if you haven't got one, this thread and of course the search-engine of your choice may be helpful. I was lucky enough to obtain an official unlock key on the last day of HUAWEI's unlock page, so I have no experience with the unofficial unlock methods - good luck!

      EMUI 8.0 firmware
      Get back to Stock ROM, if you use a Custom ROM. On Stock, if not yet done, apply all updates offered to you by the Stock ROM updater, until you are on the latest officially offered Android 7 (Nougat) EMUI 5.x release.
      Once you are on Android 7 (aka Nougat), please visit this thread, which really explains step-by-step, what needs to be done. Really carefully ready everything and follow ALL the steps, especially, don't forget at the very end to flash the Stock EMUI recovery!
      IMPORTANT UPDATE:
      The linked thread, as well as the Openkirin documentation point - via a Russian firmware site - to the domain 'hicloud.com' for the firmware download, which seems to be down. As suggested by @zgfg you can try either
      his Mega link or e.g. https://androidhost.ru/search.html
      Update: See this post to obtain the firmware!

      You need your unlock key handy: During this process, the bootloader will be automatically locked several times, so you need the key a couple of times to unlock again!
      A hint for Linux users: The HWOTA tool is in fact a windows wrapper around Linux shell scripts, so there is no real need to use Windows, if you have a working Linux installation (however, make sure to replace the 'mkdir' commands in hwota_eng.sh with 'mkdir -p').



      Bug reports:
      If you have a problem, please create a post with these informations:
      Build Date:
      And try to get log as described here
      Please note that I can't and won't support issues with builds using a different kernel or Xposed.
      In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.

      Credits
      AOSP project
      LineageOS project
      openkirin.net
      phhusson
      AndyYan
      Tecalote
      microG project
      Graphene OS project
      csagan5 (Bromite)
      WhyOrean (Aurora)


      XDA:DevDB Information
      [ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9, ROM for the Huawei P9

      Contributors
      MSe1969
      Source Code: https://github.com/lin16-microg/device_phh_treble/tree/lin-16.0-eva-p9

      ROM OS Version: 9.x Pie
      ROM Kernel: Linux 4.x
      ROM Firmware Required: EMUI 8 firmware
      Based On: LineageOS

      Version Information
      Status:
      Stable
      Stable Release Date: 2021-06-12

      Created 2020-04-06
      Last Updated 2021-06-13
      5
      New build with May 2020 ASB

      Hi all, a new build is available for download:
      https://sourceforge.net/projects/li..._a_lineage16_20200508_system.img.zip/download

      To install, download, unzip and follow instructions as outlined in OP.
      The build has the following features:
      • Sec. string 2020-05-01
      • Bromite Webview on 81.0.4044.127
      • AuroraStore updated to 3.2.8
      • Fix of bundled 'netmonitor' app not starting

      Regards, M.
      4
      New build with July ASB patches

      Hi all,
      a new build is available for download (install instructions, see OP):
      https://sourceforge.net/projects/li..._a_lineage16_20200708_system.img.zip/download

      • ASB Security string 2020-07-01
      • microG: updated prebuilt GmsCore fom /e/ project (fixed FCM registration issues)
      • F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
      • Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
      • Bromite Webview on 83.0.4103.101
      • Sepolicy: Netmonitor exception f. "Tracker Control" app

      Happy flashing - regards, M.
      3
      Kernel

      Just gave a try to the ECO Kernel, which seems to run really fine on the P9.
      Instructions in the linked thread (I flashed the "04.05.20 build with Linaro").

      Advantages:
      - Up to date with current patches (Stock kernel is from December 2018)
      - Hopefully better battery behavior

      I'll report my impressions soon, after using the device for some time.
      3
      Do you plan to provide regular updates with the latest security patches in the future?
      Yes, I do - April ASB is "already in the pipeline"...