yashsingh1/xdaforums huggingface dataset:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
I don't see how flashing ZIPs can be harmful to your system, as flashable ZIPs usually just unzip some content into rw-mounted /system and set permissions. Others, like my latest kernel installer, do modify /vendor which makes changes permanent and only can be reverted by restoring a backup or flashing a vendor image from EMUI

The only reason users like Tecalote recommended to stay away form TWRP was because it couldn't handle Huawei's encryption and it couldn't do a proper factory reset on an encrypted device due to some proprietary bits not being present (and will never be) but an unencrypted phone works perfectly with TWRP. This gives the user flexiblity to backup, restore, patch easily and recover from soft bricks very fast thanks to excellent MTP support and the ability to flash images directly.

BTW for users, do not flash anything on top of [MENTION=7929484]MSe1969[/MENTION]'s ROM. All the needed fixes are integrated and the NFC-patching ZIP was recalled due to incompatibility with EVA hardware even though it activated it in software. I advise you to reflash your system and flash the new amend. A newer phh-based ROM should have working NFC out of the box.

Also I;ve looked at some past posts and to avoid confusion when referring to Pie ROM or vendor you should call the firmware EMUI 8.0, or VNDK 26 (Treble O).
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Nightwish1976:
[MENTION=7929484]MSe1969[/MENTION]: I suspected it was a problem affecting only my phone, but I still had to ask.

Let me ask you something, have you done the decryption/installing TWRP to your phone? You said the GSI installation is similar to the one for Open Kyrin's ROMs which specifically forbid any modifications. In my case, after update to EMUI 8, I installed TWRP and decrypted. Decryption was the point when some anomalies appeared.

I mean we have similar phones, it has to be something I've done that caused a different result.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Stock ROMs are tightly integrated, you can expect incompatibilities sometimes when you install custom stuff. Can you tell me the exact problem? I have no problems with decryption on phh-based AOSP ROMs.

---------- Post added at 22:48 ---------- Previous post was at 22:15 ----------

I am going to flash clean B550 EMUI 8.0.0, it was very hard to find but I found a mirror on a Russian website
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
[MENTION=9152969]Wattsensi[/MENTION] : Yes, on the Russian website - but I ended up a really "weird", but at the end effective way to "update" my ROM (I have it encrypted with the Stock recovery):

I have first flashed the b540 system.IMG via fastboot. (There is the Huawei extractor software with an XDA thread allowing you to extract sparse images from Huawei firmware ZIP files)

It then first OTA updated a very small b540 patch and afterwards it pulled the b550 "delta" OTA (600MB). Now comes the weird part: This update failed, and the Stock recovery tried 3 times to apply, reboot, apply again. Then it booted back to the Android and automatically downloaded the full package (3 GB), and this time all worked. At the end, I had to temporarily flash TWRP for the network patch, could then flash the stock recovery again (extracted from b550) and my build. [MENTION=4210118]Nightwish1976[/MENTION] : When I first flashed my build, I had before flashed the Stock recovery and did a factory reset and a cache wipe with it. After flashing my build (or any other, e.g. Openkirin build), encryption is automatically taking place as part of the first boot. So I do not use TWRP - it is definitely needed to get from Stock Nougat to Stock Emui 8 and finally to patch the Network/Modem/... stuff to use our SIM cards, but once that all is set up, I stick with the stock recovery.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Nothing bad with TWRP in general, I like it very much on my other non-treble builds. But as encryption does not work, I use stock recovery. You've explained, what I said before, in different words - so we are in agreement.

Using TWRP and flashing Zips is not "bad" as such, but as said: Dangerous if, other partitions than /system are modified, as you cannot easily revert. And, I suspect this (I mean: something flashed on top, no matter what) being the root cause of reported issues, if those reported things perfectly work on my device with my setup, and we can exclude HW issues.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Nightwish1976:
Hi, guys. Posting to let you know that I wiped everything, went back to EMUI 8 and flashed this ROM on a clean vendor (genuine recovery and encrypted). No big surprise, but my fingerprint problem has disappeared. So it was obviously caused by vendor alterations.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] NervReaper:
Did you delete your fingerprints or did a factory reset before flash the rom? It's a common issue that firgerprint doesn't work on gsi if you didn't delete them on emui.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Vendor is not the problem, it's the AOSP-based ROMs being unable to fully access the fingerprint scanner's secure memory. It forgets about them after a factory reset if they aren't deleted. This allows you to accidentally fill your secure memory with ghost fingerprints.

They waste a fingerprint slot and can become a security backdoor by working even if only other fingerprints are enabled. The only way to delete ghost fingerprints is to return to EMUI and delete them from there, because only EMUI can detect those ghost fingerprints.

So, if you use AOSP GSI ROMs, delete all your fingerprints before factory resetting or you will have to flash EMUI to get rid of them ;)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Nightwish1976:
I'm not 100% sure, but I might have had a fingerprint registered before installing Lineage. 16.

Thanks, it's good to know for the future.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] xaweryp:
Hi, installed on top of 'clean' P9 AL-10 (B550). Looks like majority works fine, but found 2 minor issues as well:

1. wifi is not connecting if AP is not broadcasting it's name (aka 'hidden SSID')

-> no longer valid - was configurational issue

2. booting from offline charging does not work

Steps to reproduce:

1. turn off P9

2. connect charger (used standard 5v charger)

3. wait for the phone to start offline charging

4. try to turn on the phone while charging (mine got stuck at this step, need to hold power to reboot)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Sadly we have no way to debug this currently
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
You can restore B550 firmware via Erecovery
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Not in every case, I have tried that approach with my device (scroll up a little), but eRecovery wanted to restore the last Nougat version B387 (? don't remember the number exactly), so I stopped and ended up a different path...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
For me Erecovery downloaded B550 firmware.

And I also downloaded the B550 firmwar via Huawei Firmware Finder.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
If it worked that way, this is perfect. This is the easiest and straightforward approach - I just wanted to inform, that it did not work on my device and in that case, it can become tricky.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] md sabuj:
After restoring the B550 firmware via Erecovery I just downloaded the entire B550 firmware via Firmware Finder to extract the Ramdisk to patch it via magisk and have root access.

After patching the Ramdisk via Magisk i flashed it to Ramdisk partition and it’s worked for me.

I think other partition will work as well.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
thanks, but I already flashed the full B550 package from TWRP with HuRUpdater, which lets you flash stock ROMs from TWRP.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
New build with October ASB available

Hi all,

a new build is available for download (install instructions, see OP) - this time, with a couple of improvements, besides the sec. fixes:

https://sourceforge.net/projects/li..._a_lineage16_20201007_system.img.zip/download

ASB Security string 2020-10-01

Bromite Webview on 86.0.4240.73

microG upgraded to 0.2.12.203315 - it includes now the "Exposure notification API" for Covid tracing apps

Additional hardening (hardened bionic lib and constified JNI method tables in several system apps)

Fixed: WiFi Hotspot is working now

Fixed: AuroraStore now finds all suitable apps - thanks [MENTION=9152969]Wattsensi[/MENTION] for the hint to the fix

A remark to the upgraded microG:

- If you have location providers configured, you need to re-enable them after flashing the upgrade as a one-time activity.

- The exposure notification API allows you to run Covid tracing apps, which are designed for its use (most apps are)

Happy flashing! Cheers, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
[MENTION=7929484]MSe1969[/MENTION] I managed to build LineageOS 18.0 from a customized manifest, what did you do to make the build smaller than 2.3 GB?

The Huawei P9 cannot accept system images larger than 2080 MB. I tried changing the partition size in BoardConfig.mk already down to 1.6 GB but it still churned out a 2.3 GB image which I cannot flash.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
I have no specific "secret" - my work is based on Phh and AndyYan. But I can simply add some thoughts, which you may find interesting or you can immediately drop, as they won't apply to your situation:

- my build is Android 9 and yours is Android 11 - newer android versions tend to become larger and larger

- do you include Gapps? If so, make sure - similar to what phh does - to ONLY include the bare minimum (that even means less than gapps pico) and not the "full Google sh*tload"

- if you dex-preopt, keep in mind that this significantly increases the needed space, so rather dex-preopt selected apps or even refrain from it (I have no clue about android 11, so maybe you would have to?)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
Thanks for your answer, I have no GApps in the build, it's just a barebones arm64_avS build. I added WITH_DEXPREOPT := false to the BoardConfigGsiCommon.mk, so it may help. I also noticed that there are some .apex files in /system/apex which together are like 300 MB, just enough to bring down the size to something flashable if I also remove some MediaTek and Qualcomm files. However they also work for essential system functions so I will proceed with caution.

Unfortunately future Android versions for this phone will either have to be Android Go, require repartitioning the phone or just won't be possible. If LineageOS is already this heavy then we probably won't see newer Android versions if repartitioning is not possible.

EDIT: Not possible, will release repartitioning script instead
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] dkionline:
Android Go Apps could be enough, but its too early to talk about that.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
I'll try making a repartitioning ZIP in the meantime so it can fit a full build. This device has a really tight system partition not suited for ARM64 and I'll try expanding it to 3 GB just to future proof it.

However it is destructive so it must be done with care
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Wattsensi:
[MENTION=7929484]MSe1969[/MENTION] I repartitioned my phone to have a 3 GB system image, but Fastboot still didn't let me flash. I'll use TWRP's mechanism to flash it instead or as a last resort, dd it into the system partition. Let's see if it is possible via repartitioning, of if it needs to be done other way.

EDIT: ROM doesn't boot, will try phhusson's GSI. It will be investigated, no progress for now. I will try phhusson's AOSP R preview GSI

EDIT: AOSP 11 booted. Doing some tests now. ROM needs to be rebuilt. Will release repartitioning script soon.

EDIT: My source-built GSI doesn't boot, I will have to redo the device tree from scratch, or pick another ROM...will you guys settle for modified AOSP 11 instead? Something in the phh patching stage isn't right for non-pure AOSP ROMs...or maybe it is my usage of Dakkar's script. I will try repo syncing Lineage once more and building it but no promises.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
To #1 - don't have a router allowing me to hide SSID, so can't test - anybody else having that issue?

To #2 - works fine with my device, not able to re-produce. (Also, as mentioned, very difficult to debug this)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
microG interim update

Hi all,

an interim update of microG GmsCore is available for download here:

https://sourceforge.net/projects/li...llaneous/GmsCore_20201017-signed.apk/download

The apk has been built from the microG source and signed with the specific key of this ROM.

(This means, it

cannot

be used on any other ROM, except the signed LineageOS 16.0 ROMs for the various devices provided by

me

)

This update contains the following fixes:

GCM sign-in issues

Mapbox issues

Various improvements of the exposure notification API

There is currently no official new version of microG, but due to some issues, which I have experienced myself in regards to the Covid tracing app and GCM sign-in and which were fully solved after applying the update, I wanted to offer it for those of you, who are interested. To update, simply download the linked apk and install.

Important hint:

The UI has been re-shaped internally. If you start the microG UI and what you see looks "weird" (e.g. Exposure notifications API now shown, or device registration and GCM looking "disabled"), don't panic and DON'T change any settings.

Instead, please go to Settings - apps, pick the microG GMS Core app and purge the app's cache (only the cache,

and not the app data

!) - Afterwards, all will be fine.

Regards, M.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] :
How could I install play store and play services. It is possible to flash open gapps va twrp?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] brookie229:
Hi - I've also just tried this ROM from a clean P9 with AL-10 (B550) as the poster above and I have NO mobile connection. WiFi, BT, all work fine (and everything else I've tested) but my SIM card will only show in Slot 2 and only with emergency use. Maybe I'm missing something?

p.s. question: I'm newby at this but can I try another ROM directly over this (ie OpenKirin for P9, or do I have to revert back to the previous EMUI first?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
IMO, when you were on b550, you had to flash Network zip patch (single or dual SIM, deprnding on your phone). It installs the patch but not to /system, and the patch should stay with the custom ROM.

That was exactly the case when installing OpenKirin custom ROMs over b535, b540, back at those tines

If you just rebranded to Chinese AL-10 with a clean b550, Network patch was not present

I don't know would it be possible to patch when you are alredy on the custom ROM
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
This ROM contains some hardening features, which most probably won't work with the genuine Google play services.

If you'd like to try, it is your device, so you decide what you do with it - yes, technically, it should be possible to use TWRP to flash the Gapps.

But I can't give you any prediction for the result, I personally don't recommend it and whatever the result is, I can't help.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
In addition to what [MENTION=7786725]zgfg[/MENTION] said already:

The

correct

Network patch is necessary and it should be flashed while still on EMUI. You indicated "Slot 2", which means: DUAL-SIM - so you have an EVA-L19 or EVA-L29 (and not an EVA-L09, which is single-SIM, this is what I have).

In regards to your issue: You can't even connect to your carrier to make phone calls, you can only make emergency calls, even with your home carrier, correct? And also only from slot 2?

Then indeed, this somehow feels like the wrong network patch - in that case, it may be most secure to start from scratch and

not

to simply try to flash the correct patch over the wrong one...

In case I misunderstood you and your only issue is mobile data (meaning: you can make regular phone calls), try manually configuring the APN based on the information you find on your carrier's homepage.

About flashing a different ROM over my ROM:

1. You can simply flash a different ROM on the /system partition, but you would then need to do a factory reset - if you flash an update (e.g. you are on my ROM and flash another version of my ROM - or you are on OpenKirin LineageOS and flash an update of OpenKirin LinerageOS), this is not necessary. But flashing Openkirin LineageOS over mine, or flashing OpenKirin LineageOS over OpenKirin Omni, you must do a factory reset.

2. I am pretty sure, that flashing a different treble system.img over your setup will not solve your issue, if you can only use your SIM for emergency calls.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
I think his case was:

- dual SIM P9 rebranded and upgraded to EMUI 8, without Network patch.

Then only slot 2 still recognizes the SIM card, but IMEI is not available and even slot 2 cannot make calls

But that should still be ok for eRecovery to reinstall b550, followed by TWRP (temporarily) and (dual SIM) NW patch , and finally to install the ROM per your OP instructions
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] brookie229:
Thanks again [MENTION=7786725]zgfg[/MENTION] and [MENTION=7929484]MSe1969[/MENTION] for the replies and, I'm sure, correct diagnosis and info. I have an EVA-L29 (2 sim) rebranded to the AL10 and totally did NOT flash the Network.zip. Rookie error. I'm going to have to re-do everything including going back to my stock eva-L29 (B399) OS. I may try from b550 first if I find the courage, lol.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
If you don't plan to stay on Nougat, just go back to b550 by eRecovery and then re-do
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] brookie229:
Yep, I'm back on b550 and am going to stick here for awhile. At least it has a July 2020 security patch (much better than Nougat's of course). I may try again later, hopefully without missing anything.:)

Many thanks again to both of you for the excellent advice!:good:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] _wasted_:
Hello, many thanks for keeping up a recent ROM for the P9. Its working fine on my device.

But I need to replace the battery in my device to make it my daily driver again and since there is no other maintained ROM for this device I have one question:

Is support being dropped in the foreseeable future?

greetings
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
If you look at my other threads, you will notice, that I usually provide support quite long. So this thread won't make an exception.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] ric0shay:
Update

So I'm on a previous version of of this rom (no working hot-spot) Is my understanding correct that I can just flash the latest version over the current one to enable hot-spot?

Thanks again for the support!
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
HI folks, first post here! Big UP to all your work here. Need to be said. :good:

I am running LineageOS 16.0 Build 6 Released October 19, 2020 downloaded from openkiri.net successfull.

Bevor the P9 was updatet to EVA_AL10 (EMUI8) via [MENTION=6870018]Tecalote[/MENTION] step-by-step manual. After installing network patch my provider/carrier named "HOT" showed up correctly in top left corner of the display. Its a discounter running on T-Mobil Austria (now called "Magenta") infrastructure.

After flashing LineageOS 16 it shows only T-Mobil, no more HOT. A friend of mine working there (T-Mobil) checked my IMEI and MISI and my P9 is corrrectly signed in at T-Mobil via HOT. So all runs fine just the names of the network are wrong listed.

As I figured out there are three posibilitys where the phone gets this information from. SIM-Card, via air (network) and branding (firmware).

Its only a little detail but is it possible to update the carriers to the present names?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
It's about virtual providers. They don't have their own infrastructure but users (similarly like in roaming) attach through the host networks

Phone receives both info - indeed, you can see both names, although with different ROMs.

Actually, phone does not receive names but their codes and translates them to the names through its own tables

Official ROM takes the correct code from the two and displays correct info, custom ROM picks the code of the host network- it would be a serious defect for the official ROM if it would not properly deal with network names even for virtual operators

But if other things work fine in LOS, why do you bother with few leters in the corner of thevscreen?

LOS maybe does not distinguish virtual providers from roaming and thinks that host network code/name (in roaming, you would always see the host network name) as the expected info to show
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] P9_User:
Thanks for explaination, that makes sense. Just wanted to be shure there is no issue, for exsample going abroad and figuring out my phone cannot log in at a roaming-partner network.

And no, I dont care too much about what provider is written and yes, I am very curious how nice LOS16 runs my P9. :highfive:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] _wasted_:
Hello, i have an issue.

When i activate either night-mode, read-mode, or calibrate the colors in 'LiveDisplay'-settings, the UI of the trebuchet-launcher becomes quite laggy. Same for color correction in 'Accessibility Settings'.

Reproduction: swipe through the pages of the home-screen, fast and slowly -> activate one of the settings mentioned above -> swipe again fast and slowly through the pages of the home-screen & you should notice the difference.

Build: 20201007

Don't know if this is related to the ROM, and if there is a way to solve this or at least workaround.

greetings

Edith:@ b550 stock kernel

no Xposed or other modifications
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Yes, just flash the system image, that's it.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] ric0shay:
It flashed fine. But hot-spot still isn't working. Turns on the off and says error. Any idea what the issue could be.

Thanks again for the help
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] _wasted_:
same for me. hotspot not working. Did a clean flash yesterday.
[MENTION=7929484]MSe1969[/MENTION] what do you need, logcat and dmseg? can post them in a few hours.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Just tried to reproduce the issue on my P9, I didn't see any issues, no not sure, how I can help...
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
Which build exactly did you flash?

It works w/o issues on my device.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] _wasted_:
kernel/vendor: B550

system: treble_arm64_a_lineage16_20201007_system

no Xposed or other modifications

logcat

tried to get dmesg as well (followed the explenation in the link from OP) but got klogctl permission exception... also tried with root enabled for adb, but couldn't get it to work.

dmesg
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] MSe1969:
I am for a specific reason reluctant to "downgrade" my device to 20201007 to verify. Could you please flash the interim version 20201017, which I have announced some posts back and tell me, whether it works?