Database Info

[CLOSED][EOL] LineageOS 12.1 for Z1c with current Sec.Patches - Xperia Z1 Compact Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all,
this thread is discontinued
this thread is dedicated to keep the LineageOS (former Cyanogen Mod) version 12.1 (Android 5.1.1) alive for the Sony Xperia Z1 compact with current security patches.
Features
Enforcing SELinux (unfortunately, many ROMs for this device don't have it, but we do!)
Based on LineageOS sources (former CyanogenMod), branch 'cm-12.1'
Rebranded to LineageOS
Current Android security fixes included
Kernel 3.4.113 including Android Security Bulletin patches (frequently maintained and updated)
Privacy Browser as replacement of outdated AOSP Browser
Removed Cyngn-Tracking and Google-dependencies (same as LineageOS)
Support for microG available under development options
Current Android System Webview (M86 stable)
Enhanced Privacy Guard: Own switches for Wi-Fi scan, clipboard, notifications and vibrate
Renewed CA certificates from AOSP master branch
Use Cloudflare DNS 1.1.1.1 as default fallback (instead of Google)
Download latest version with November 2020 security patches:
release:
https://sourceforge.net/projects/cm...e-12.1-20201112-UNOFFICIAL-amami.zip/download
TWRP 3.2.3-1 for Z1c (amami)
https://www.androidfilehost.com/?fid=6006931924117909119
(Please note, that this TWRP does only support full-disk encryption (FDE) in all android releases; it does not support file-based encryption as of Nougat/Oreo)
Older TWRP versions: https://androidfilehost.com/?w=files&flid=174382
List of available Downloads:
https://androidfilehost.com/?w=files&flid=155737
https://www.androidfilehost.com/?w=files&flid=199304
https://sourceforge.net/projects/cm12-amami/files/
Source code and build instructions:
Kernel: https://github.com/cm12-amami/android_kernel_sony_msm8974
Build manifest: https://github.com/cm12-amami/android & https://github.com/cm12-amami/local_manifests
microG-patch: Until July 2017 official microG patch, since August 2017 base and Settings patch for unified build (equivalent implementation as in OmniROM)
Bug reports:
If you have a problem please create a post with these information:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
A comment about Custom CM12.1 Themes:
CM 12.1 (Android 5.1) is meanwhile quite "aged", and maintaining it with security patches also involves back-porting stuff from newer Android versions, as well as keeping the Android Webview engine up to date. The majority of available CM 12.1 Custom Themes however is not really maintained any more. We have had one reported and one suspected case, where an active CM12.1 Custom theme which hasn't been maintained since more than two years, has caused an issue. Hence, if things crash and you use a custom theme, please try first to activate the shipped default theme. We cannot and will not put any effort to solve compatibility issues with old custom themes.
Magisk
It is reported that Magisk in general works up to version 19. From version 19.1 onwards, the recovery boot is broken, so do not use Magisk 19.1 and above with this ROM!
We cannot, hence we will not, provide any support related to issues with Magisk.
Installation instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - we 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 information available.
Pre-Requisites
Get familiar with the hardware keys of the Xperia Z1 compact device, especially how to enter fastboot mode and recovery mode
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
Download the most current .ZIP file of our ROM and place it to your phone's internal memory or SD card
If you wish to install Google apps (GApps), please refer to the GApps section further below
An unlocked bootloader (read the warnings carefully and backup your data!)
In case your device is still with the pre-delivered Sony Stock ROM: It is recommended that you have updated the Stock ROM to the latest version offered by Sony to make sure that the bootloader has the needed capabilities (see also 'trouble-shooting' below)
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it. However - we recommend to use the TWRP recovery linked in this thread. The following instructions are based on TWRP.
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash FOTAKernel TWRP.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and use the right hardware keys to get into recovery mode) - we recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Trouble-shooting:
Depending on the Stock ROM you are on, you may face some difficulties to get the phone into recovery after flashing TWRP. If you are facing such difficulties (i.e. phone always boots into Stock ROM), get into fastboot mode, and manually boot into TWRP by entereing the below command:
Code:
fastboot boot TWRP.img
If that also does not help you, it could be that your Stock ROM has got a too old bootloader. In that case, use the Sony flash tool (Windows only) or Androxyde's Open source flshtool to flash a more current Sony firmware image. Both approaches can also help to "unbrick" your device.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and spefify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
GApps
You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device. Choose ARM as platform, Android 5.1 and the flavor of your choice. We recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications you have no use for.
Install our ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd). Choose the .ZIP file of our ROM and swipe to flash.
If you update from a previous version of our ROM, you don't need to perform a wipe. If you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process. (Note: If you wish to get rid of GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps.
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into our Lineage OS 12.1 - be patient, the first boot after flashing a new ROM takes quite long!
This has been a joint effort of hahnjo, Micha_Btz and Mse1969, based on the LineageOS sources on GitHub (https://github.com/LineageOS). Meanwhile, hahnjo and Micha_Btz aren't active any longer in this project. Special thanks also to derf elot, who is not active any longer in this project, but he has laid the solid foundation for it.
You can view the progress and discussion about this initiative by looking at the issues in our discussion repository https://github.com/cm12-amami/discussion - contributions and pull requests are welcome, since applying backports of the actual android security bulletins is a lot of work.
XDA:DevDB Information
LineageOS 12.1 for Xperia Z1 compact , ROM for the Sony Xperia Z1 Compact
Contributors
MSe1969, derf elot, Micha_Btz, hahnjo
Source Code: https://github.com/cm12-amami
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: cm-12.1
Stable Release Date: 2020-11-12
Created 2017-05-31
Last Updated 2020-11-29

Change Log
Applies to both versions, 'standard' and 'microG-patched' until July 2017 release
Since August 2017, there is a unified build
November 12th, 2020 - FINAL build
- ASB November 2020 patches (sec. string 2020-11-05)
- Addl. fix of CVE-2019-2306
- Addl. fix of CVE-2020-15999
- System Webview on 86.0.4240.185
October 15th, 2020
- ASB October 2020 patches (sec. string 2020-10-05)
- Fix of E-Mail widget
September 15th, 2020
- ASB September 2020 patches (sec. string 2020-09-05)
- Webview updated to 85.0.4183.101
- Privacy Browser updated to version 3.5.1
August 12th, 2020
- ASB August 2020 patches (sec. string 2020-08-05)
- Kernel: Upstream fixes and PR merges from @fowof
- Webview updated to 84.0.4147.89
June 09th, 2020
- ASB June 2020 patches (sec. string 2020-06-05)
- Ported missing CVE-2020-0096 ("Strandhogg") from May ASB
- Webview updated to 81.0.4044.138
May 13th, 2020
- ASB May 2020 patches (sec. string 2020-05-05)
- Webview updated to 81.0.4044.117
April 15th, 2020
- ASB April 2020 patches (sec. string 2020-04-05)
- Privacy Browser updated to version 3.4.1
- Fix for CVE-2020-8597 (external/ppp)
- Kernel: CVE-2019-10638 siphash 128bit for IP generation
March 15th, 2020
- ASB March 2020 patches (sec. string 2020-03-05)
- Webview updated to 80.0.3987.132
February 16th, 2020
- ASB February 2020 patches (sec. string 2020-02-01)
- Webview updated to 79.0.3945.136
January 14th, 2020
- ASB January 2020 patches (sec. string 2020-01-05)
- Privacy Browser updated to version 3.3
- Webview updated to 79.0.3945.116
December 09th, 2019
- ASB December 2019 patches (sec. string 2019-12-05)
- Webview updated to 78.0.3904.108
- Kernel: Amongst several patches, backported CVE-2019-2215 from October 2019 ASB
- Skipped CVE-2019-2212 from ASB 2019.11 included
- Skipped CVE-2019-2196/CVE-2019-2198 from ASB 2019.11 included
- Skipped CVE-2019-2117 from ASB 2019.07 included
- DownloadProvider part of CVE-2018-9493 from ASB 2018.10 now also included
November 17th, 2019
- ASB November 2019 patches (sec. string 2019-11-05)
- Webview updated to 78.0.3904.96
October 16th, 2019
- ASB October 2019 patches (sec. string 2019-10-05)
- Webview updated to 77.0.3865.116
September 10th, 2019
- ASB September 2019 patches (sec. string 2019-09-05)
- Implemented CVE-2018-20346 (aka "Magellan"), which was outstanding from March 2019 ASB
- Implemented CVE-2019-2031 outstanding from April 2019 ASB
- Webview updated to 76.0.3809.111
August 11th, 2019
- ASB August 2019 patches (sec. string 2019-08-05)
- Additional (backported) security patches from AOSP branch 'nougat-mr2-security-release'
- Privacy Browser updated to version 3.2
- SetupWizard rebranded to LineageOS
July 4th, 2019
- ASB July 2019 patches (sec. string 2019-07-05)
- System Webview M75 - updated to 75.0.3770.101
June 16th, 2019
- ASB June 2019 patches (sec. string 2019-06-05)
- Privacy Browser updated to version 3.1
- System Webview M74 - updated to 74.0.3729.157
- Included CVE-2017-0554 and CVE-2017-0840
May 9th, 2019
- ASB May 2019 patches (sec. string 2019-05-05)
- Privacy Browser updated to version 3.0.1
- System Webview M74
April 8th, 2019
- ASB April 2019 patches (sec. string 2019-04-05)
- Privacy Browser updated to version 2.17.1
March 13th, 2019
- ASB March 2019 patches (sec. string 2019-03-01)
- Privacy Browser updated to version 2.17
- Android System Webview updated to M72 (includes CVE-2019-5786)
February 9th, 2019
- ASB February 2019 patches (sec. string 2019-02-05)
- Privacy Browser updated to version 2.16
- Fix of carrier display of Telefonica Germany, part 2 (thanks to @awl14 )
- Kernel: Additional 'spectre' mitigations
January 13th, 2019
- ASB January 2019 patches (sec. string 2019-01-05)
- System Webview M71
- Privacy Browser updated to version 2.15.1
- Fix of carrier display of Telefonica Germany
- App usage stats disabled by default
December 7th, 2018
- ASB December 2018 patches (sec. string 2018-12-05)
- Fix of 'adb root' bug (see LineageOS announcements)
- Addl. fix of CVE-2018-9531, CVE-2018-9536 and CVE-2018-9537 from November ASB, which are flagged Android 9 only, but also apply
- Backport of CVE-2017-15835 (skipped in November ASB)
November 7th, 2018
- ASB November 2018 patches (sec. string 2018-11-05)
October 20th, 2018
- ASB October 2018 patches (sec. string 2018-10-01)
- Android System Webview updated to M69
- Indication in Settings that Security patch level is unofficial
September 9th, 2018
- ASB September 2018 patches (sec. string 2018-09-05)
August 13th, 2018
- ASB August 2018 patches (sec. string 2018-08-05)
- Privacy Browser updated to version 2.12
July 16th, 2018
- ASB July 2018 patches (sec. string 2018-07-05)
- Privacy Browser updated to version 2.11
- Android System Webview updated to M67
- Additional kernel fixes CVE-2018-1092 / CVE-2018-1093
June 10th, 2018
- ASB June 2018 patches (sec. string 2018-06-05)
- Privacy Browser updated to version 2.10
- Privacy-default setting (at clean install): Sensitive information is hidden on the lock screen
May 16th, 2018
- ASB May 2018 patches (sec. string 2018-05-05)
- Android System Webview updated to M66
- Privacy Browser updated to version 2.9
- Use Cloudflare DNS 1.1.1.1 as default fallback (instead of Google's 8.8.8.8)
- Further fix for the "Ask" topic in Privacy Guard to mimic the defined behavior
April 20th, 2018
- ASB April 2018 patches (sec. string 2018-04-05)
- Android System Webview updated to M65
- GPS https-fix (CVE-2016-5341)
March 13, 2018
- ASB March 2018 patches (sec. string 2018-03-05)
- Android System Webview updated to M64
- Privacy Browser updated to version 2.8.1
- Renewed CA certificates from AOSP master branch
February 11, 2018
- ASB February 2018 patches (sec. string 2018-02-05)
- Applied many past ASB patches flagged as "not publicly available"
- Privacy Guard enhancements: Own switches for Wi-Fi scan, clipboard, notifications and vibrate
January 16, 2018
- ASB January 2018 patches (sec. string 2018-01-05)
- Webview switched to stable M63
- SQLite 'secure delete' feature enabled
December 14, 2017
- ASB December 2017 patches (sec. string 2017-12-05)
- Privacy Browser updated to version 2.7.2
- Backported patches for su (root app) from LineageOS 13
November 19, 2017
- ASB November 2017 patches (sec. string 2017-11-06)
- Privacy Browser updated to version 2.7.1
October 28, 2017 (interim release)
- Fix WPA-TKIP issue after applying "krack" fix
October 20, 2017 (interim release)
- Fix for KRACK attack (see https://www.krackattacks.com/)
- Android System Webview updated to M64
October 06, 2017
- ASB October 2017 patches (sec. string 2017-10-05)
- Fixed 'Hardware Overlay' bug
- Addl. kernel fix for the 'Blueborne' vulnerability
September 26, 2017
- ASB September 2017 patches (sec. string 2017-09-05)
September 21, 2017 (interim release)
- Security patch level 2017-09-01 (yet w/o September ASB kernel patches), but fixed 'Blueborne'
- Privacy Browser updated to version 2.6
September 2, 2017 (interim release)
- Privacy Browser updated to version 2.5
August 23, 2017
- ASB August 2017 patches (sec. string 2017-08-05)
- Unified build: microG patch included, needs to be enabled in the developer settings
- Android System Webview updated to most current M60
July 16, 2017
- ASB July 2017 patches (sec. string 2017-07-05)
- Kernel rebased and merged to release 3.4.113
- Privacy Browser updated to version 2.4
- Lock Clock: Removed built-in Google lib (Back port from LineageOS)
- Settings (1): Rebranding to LineageOS, link to LineageOS privacy policy (Backport from LineageOS)
- Settings (2): Elimination of Stats tracking (Backports from LineageOS: (1), (2), (3), (4))
- SetupWizard (1): Removed built-in Google lib (Back port from LineageOS)
- SetupWizard (2): Removed 'opt-out' for stats tracking (will simply be switched off by default)
- SetupWizard (3): Added option to switch on Privacy Guard
- Trebuchet Launcher (1): Removed 'Cyngn'-tracking (Back port from LineageOS)
- Trebuchet Launcher (2): Show 'Privacy Browser' as default Browser on new installs
June 11, 2017
- ASB June 2017 patches (sec. string 2017-06-05)
- Android System Webview updated to most current M59
- Replaced old (and insecure) Browser app with Privacy Browser
May 25, 2017
- ASB May 2017 patches (sec. string 2017-05-05)
- Lineage OS 'su hide' patch applied
- Lineage OS Boot animation (instead of old CM)
May 14, 2017
- ASB April 2017 patches (sec. string 2017-04-05)
- Removed CMUpdater from build

Open issues
Our open issues can be found here.
Our closed issues before moving to our new organization can be found in our issues archive.
Currently open:
open CVE's from the ASB - Here we will list all patches, which we could not (yet) apply

Hello!
Good luck in development!
In the cm12 firmware.1 there is a joint in the lower right corner does not respond to touch
Only a Reboot helps

Viktor245 said:
Hello!
Good luck in development!
In the cm12 firmware.1 there is a joint in the lower right corner does not respond to touch
Only a Reboot helps
Click to expand...
Click to collapse
Hi,
I could not reproduce the described behavior; I did not experience such a behavior on my own device - could you please provide more details or a screen-shot?
Thanks - M.

MSe1969 said:
Hi,
I could not reproduce the described behavior; I did not experience such a behavior on my own device - could you please provide more details or a screen-shot?
Thanks - M.
Click to expand...
Click to collapse
This behavior is not immediate,official firmware is also a school there,does not react to tap in the lower right corner,have to do the screen calibration

Awesome rom, using it regularly now. No problems so far. Thank you for your work helping us to use this nice phone longer
Looking forward to the next security update!

can i flash this from AICP12.1 ?

nhicko95 said:
can i flash this from AICP12.1 ?
Click to expand...
Click to collapse
No, downgrades aren't supported by android. You should make a clean install to avoid a lots of problems.

Micha_Btz said:
No, downgrades aren't supported by android. You should make a clean install to avoid a lots of problems.
Click to expand...
Click to collapse
i know that what i means is no need for flash stock rom then flash this rom ? and can you share a picture taken by z1c with this rom ?

Is this essentially the old cm build with current security patches? So camera is intact and everything works? This is my girlfriend's phone, so I'm trying to make sure I don't mess it up

nhicko95 said:
i know that what i means is no need for flash stock rom then flash this rom ? and can you share a picture taken by z1c with this rom ?
Click to expand...
Click to collapse
You don't need to flash a stock rom in between. just wipe and install this rom.
diemadedrei said:
Is this essentially the old cm build with current security patches? So camera is intact and everything works? This is my girlfriend's phone, so I'm trying to make sure I don't mess it up
Click to expand...
Click to collapse
exactly

Micha_Btz said:
You don't need to flash a stock rom in between. just wipe and install this rom.
exactly
Click to expand...
Click to collapse
can i use custom kenel for this rom?

nhicko95 said:
can i use custom kenel for this rom?
Click to expand...
Click to collapse
Try m5 if you want - https://forum.xda-developers.com/sony-xperia-z1-compact/development/kernel-m5-kernel-t3154470
Might be chancy, since this rom is very much updated, and m5 is not...

diemadedrei said:
Is this essentially the old cm build with current security patches? So camera is intact and everything works? This is my girlfriend's phone, so I'm trying to make sure I don't mess it up
Click to expand...
Click to collapse
Yes, that's right

what about battery drain...i switched from CM to jaguar because of this.
With stock Rom, my device runs 2-4day, with CM 1-2 and jaguar 2-3days

Many thanks, I'm running this since one week, it's stable and fast (I was using stock rom, this is x3 faster lol)
Had only one problem, when I had to open the camera in WhatsApp after 1 second the screen went black, this was happening also for Netflix.
Solved enabling 2D gpu rendering and disabling Hw overlay.
BTW, many thanks

Update - Z1c LOS 12.1 June build is out
Hi all,
the June build for the Z1c is available for download now:
Regular Release
Build with microG-patch
Besides the Android June 2017 security bulletin patches, the build also contains the most current release M59 of System Webview and we have replaced the old (and meanwhile insecure) AOSP Browser, which isn't being further developed since a long time, with 'Privacy Browser' (XDA thread see here - thanks @sorenstoutner)
Further, @hahnjo has joined our team as contributor to support this project.
We will soon merge the test branches into the 'cm-12.1' stable branch for those folks who would like to build themselves.
Regards, M.

WhB/K said:
what about battery drain...i switched from CM to jaguar because of this.
With stock Rom, my device runs 2-4day, with CM 1-2 and jaguar 2-3days
Click to expand...
Click to collapse
We haven't really noticed bad battery behavior, that's all I can answer. You may want to give it a try and decide accordingly...

Music is not working for me, my music files are on sd card and when trying to play the app just goes trough all of my music files and announce that it can't be played. Tried another music app and it reports I/O error.

Related

Hi,
this is my unofficial LineageOS 14.1 build for the Moto G (falcon) device with current security patches, microG patch and substratum support.
(This thread is for the falcon device, I have also a thread for preregrine using the same sources)
As announced here, LineageOS has discontinued to deliver official 14.1 builds in the course of providing LineageOS 16.0 builds, but the 14.1 tree will continue to be maintained for security patches by the community (I am one of these contibutors, btw). So this build will continue.
The build has got the following features:
LineageOS 14.1 with current security patches (from official LineageOS repositories)
Security string 2021-06-05, AOSP tag 7.2.1_r36
Additional custom build release May 2023 (to indicate ASB backport status)
Adapted LineageOS Jelly Browser (additionally having Startpage and Qwant as search engines)
Root is not included and would need to be flashed separately
Patched for the use of the substratum theme engine (the substratum app and the themes need to be downloaded separately)
System certificates taken from AOSP Oreo branch
Kernel forked from LineageOS and updated with many security patches
OTA Support
Enforcing SELinux
There are two build variants available:
A. Default LineageOS 14.1 with substratum and microG patch
Patched for the use of microG - you can either flash Gapps or manually install microG as apps (or use neither of those)
Android System Webview M114
Download here
B. Hardened build with pre-installed microG and F-Droid, patched for substratum
For the security/privacy focused. It has to be said that microG seems to run better if it is pre-installed.
Pre-installed microG same as the LineageOS for microG project
Pre-installed AuroraStore / AuroraServices
Additional security hardening features listed below
SQLite 'secure delete' feature enabled
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 available
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
No submission of IMSI/phone number to Google when GPS is in use
Mulch System Webview M114
Download here
Source Code links
LineageOS: https://github.com/LineageOS
Kernel: https://github.com/lin14-mGoms/android_kernel_motorola_msm8226/tree/mse_v1
microG patches:
(1) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
(2) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
Patches for Substratum: https://github.com/LineageOMS
local manifests: https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms and https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-mG-oms
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 information available.
Pre-Requisites
Get familiar with the hardware keys of the Motorola Moto G (falcon) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume down key to the reboot recovery option and select with volume up key)
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
Download the most current .ZIP file of this ROM and place it to your phone's internal memory
An unlocked bootloader (read the warnings carefully and backup your data!
Your bootloader must at least be on version 41.18 (find out via fastboot getvar version-bootloader) - if your bootloader is below that version, the ROM will refuse to install. In that case, you need to upgrade the BL first. See e.g. here for more info. (I currently do not find the link, which I have used some years back, but the provided link should be helpful, too)
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it.
However - I recommend to use the TWRP recovery. The following instructions are based on TWRP.
NOTE: There have been reports of encryption issues in this thread, when using TWRP 3.3.x, which disappear, when TWRP 3.2.1 is used - I myself use the TWRP 3.2.1, as higher versions have mainly been developed for higher Android versions. I can't technically confirm or prove the situation, but based on the reports and the fact, that I myself did not encounter ANY issues for my own device with TWRP 3.2.1, I recommend this version
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (see above) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped.
Make sure NOT to wipe "Internal memory" (or "SD Card", if shown). Swipe to confirm the deletion and get back into the main menu.
GApps (only for build variant A - do not flash on build variant B!)
You have the choice: a. Use microG - b. Flash GApps - c. Neither of those (obviously, you cannot combine those options!)
'microG' is installed simply by installing the respective apps, no flashing necessary. If you wish to have GApps, they need to be flashed together with the ROM. Download GApps in that case only from opengapps.org and put the .ZIP also to the Internal memory of your device. Choose ARM as platform, Android 7.1 and the flavor of your choice. I strongly recommend "pico" for two reasons:
1. The Moto G has not much internal memory (8 or 16GB) and no SD card and GApps are notoriously known to waste a lot of space
2. It leaves you the most freedom to only install, what you really need; you can later download and still install all the Google products you want from the play store, so you do not need to live with pre-installed Google stuff you have no use for.
The 'microG patch' in this ROM has no negative impact on installing Gapps.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard).
Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe. If in that case, you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process.
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you want to install GApps, flash them directly after the ROM, do not reboot in between. (Note: If you wish to get rid of previously installed GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 14.1 - be patient, the first boot after flashing a new ROM takes quite long!
Current / reported issues
WiFi hotspot needs to be toggled on/off/on after a reboot to work
WiFi hotspot enabled longer than 2 hours may cause a sudden reboot
Sometimes (root cause not clear), WiFi switches itself off after a couple of hours (fix by enabling/disabling flight mode)
It has been reported by some forum participants, that after messing with some Android-10 test builds for this device, WiFi wouldn't work any more: In this case, the solution can be found here:
[FIX] Cant turn WIFI on? You are missing this file
So after lots of flashing of different roms on my Moto G 2nd gen (XT1068) I ended up unable to turn WIFI on in any rom, including stock! Thing is, after days of breaking my head with this, I figured out I was missing the...
forum.xda-developers.com
or here (scroll down and use the manual unpack option):
[TUTORIAL] Fix " wi-fi can't on " problem without PC
Hiiiiii frnds...... I know u r in big trouble right now bcz u can't on your wi-fi (i was in trouble so) If u install some bad rom in your moto g then sometime u can't on your wifi It only stay at "turning on wi-fi" bt can't on... If u have...
forum.xda-developers.com
Why still on Android 7.1 (Nougat) and not a higher Android version (like 10, 11 or 12)?
The falcon device is low on memory (RAM and storage flash memory), each newer Android release increases the resource demand and thus decreases performance and available memory - so higher versions won't really make sense for this device.
Further, I haven't seen any ROM for this device on a higher Android version than Nougat with enforcing SELinux (yes, coming there indeed is "slave work"; none of the devs, including me for above stated reasons, is willing to invest this time...) - which is a No-Go for any daily-driver use (in that case, your device simply is fully open many vulnerabilities and applying monthly ASB patches on a permissive SELinux is close to a complete waste of time).
Credits
Android Open Source project (AOSP)
LineageOS project
microG project
Substratum team
SkewedZeppelin (Kernel patches)
XDA:DevDB Information
[ROM][LineageOS 14.1][substratum] for Moto G [falcon], ROM for the Moto G
Contributors
MSe1969
Source Code: https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS 14.1
Version Information
Status: Stable
Current Stable Version: cm-14.1
Stable Release Date: 2023-06-20
Created 2018-06-24
Last Updated 2023-06-20

Change Log
June 2023
Custom build release 2023-06-01
Standard and Mulch Webview 114.0.5735.131
microG flavor only: microG 0.2.28.231657
microG flavor only: AuroraStore 4.2.3
May 2023
Custom build release 2023-05-01
Standard flavor only: System Webview 113.0.5672.77
microG flavor only: Mulch Webview 113.0.5672.77
April 2023
April 2023 Custom build release
Standard flavor only: System Webview 112.0.5615.136
microG flavor only: Mulch Webview 112.0.5615.136
March 2023
March 2023 Custom build release
Standard flavor only: System Webview 111.0.5563.58
microG flavor only: Mulch Webview 111.0.5563.58
February 2023
February 2023 Custom build release
Standard flavor only: System Webview 109.0.5414.118
microG flavor only: 0.2.27.223616-3
January 8th, 2023
January 2023 Custom build release
Standard flavor only: System Webview 108.0.5359.128
microG flavor only: 0.2.26.223616-16
December 14th, 2022
December 2022 Custom build release
Standard flavor only: System Webview 108.0.5359.79
microG flavor only: Bromite Webview updated to 108.0.5359.106
microG flavor only: 0.2.26.223616-2
November 14th, 2022
November 2022 Custom build release
Timezone DB 2022 updates
Standard flavor only: System Webview 107.0.5304.105
microG flavor only: Bromite Webview updated to 106.0.5249.163
microG flavor only: microG 0.2.25.223616-10
microG flavor only: F-Droid 1.15.3
October 17th, 2022
October 2022 Custom build release
Kernel: Some WiFi patches
Standard flavor only: System Webview 106.0.5249.79
microG flavor only: Bromite Webview updated to 105.0.5195.147
microG flavor only: microG 0.2.24.223616-61
September 11th, 2022
September 2022 Custom build release
Many kernel patches
Standard flavor only: System Webview 105.0.5195.79
microG flavor only: Bromite Webview updated to 104.0.5112.91
microG flavor only: microG 0.2.24.214816-30
August 9th, 2022
August 2022 custom build release
Standard flavor only: System Webview 103.0.5060.71
microG flavor only: Bromite Webview 103.0.5060.140
July 16th, 2022
July 2022 custom build release
June 16th, 2022
June 2022 custom build release
Standard flavor only: System Webview 102.0.5005.78
microG flavor only: Bromite Webview updated to 102.0.5005.96
microG flavor only: F-Droid 1.15.2
microG flavor only: microG 0.2.24.214816-11
May 11th, 2022
May 2022 custom build release
Standard flavor only: System Webview updated to 100.0.4896.127
microG flavor only: Bromite Webview updated to 101.0.4951.53
microG flavor only: F-Droid 1.15
microG flavor only: Mozilla Location provider 1.5.0
microG flavor only: microG 0.2.24.214816-10
April 16th, 2022
April 2022 custom build release
Standard flavor only: System Webview updated to 100.0.4896.58
microG flavor only: Bromite Webview updated to 100.0.4896.57
February 19th, 2022
February 2022 custom build release
Standard flavor only: System Webview updated to 98.0.4758.101
microG flavor only: F-Droid updated to 1.14, F-Droid privileged extension to 0.2.13
microG flavor only: Bromite Webview updated to 97.0.4692.106
microG flavor only: microG updated to 0.2.24.214816-2
December 20th, 2021
December 2021 custom build release
Standard flavor only: System Webview updated to 96.0.4664.104
microG flavor only: Bromite Webview 96.0.4664.54
microG flavor only: microG 0.22.214516-21
November 9th, 2021
Show again "official" Sec. string same as LineageOS (2021-06-05)
Additional Custom build release property to indicate backport status
Standard flavor only: System Webview updated to 95.0.4638.50
microG flavor only: Bromite Webview 94.0.4606.109
September 17th, 2021
UNOFFICIAL Security string 2021-09-05 *
Standard flavor only: System Webview updated to 92.0.4515.159
microG flavor only: microG upstreamed to 0.2.22.212658-2
___________________________
* CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!
August 10th, 2021
UNOFFICIAL Security string 2021-08-05 *
Standard flavor only: System Webview updated to 91.0.4472.164
microG flavor only: Bromite System Webview updated to 92.0.4515.134
microG flavor only: F-Droid 1.13
___________________________
* CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!
July 14th, 2021
UNOFFICIAL Security string 2021-07-05 *
Kernel: Many sec. patches applied (taken from Divest-OS)
microG flavor only: Bromite System Webview updated to 91.0.4472.146
microG flavor only: microG upstreamed to 0.2.21.212158-2
microG flavor only: AuroraStore 4.0.7
___________________________
* CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!
June 16th, 2021
Security string 2021-06-05
Standard flavor only: System Webview updated to 91.0.4472.101
microG flavor only: Bromite System Webview updated to 91.0.4472.102
microG flavor only: microG upstreamed to 0.2.19211515-9
May 09th, 2021
Security string 2021-05-05
Standard flavor only: System Webview on 90.0.4430.82
microG flavor only: Bromite System Webview on 90.0.4430.204
microG flavor only: microG upstreamed (no version upgrade)
microG flavor only: AuroraServices updated 1.1.1
April 11th, 2021
Security string 2021-04-05
Standard flavor only: System Webview on 89.0.4389.105
microG flavor only: Bromite System Webview on 90.0.4430.59
microG flavor only: F-Droid updated to 1.12
microG flavor only: AuroraStore updated to 4.0.4 with AuroraService 1.1.0
March 08th, 2021
Security string 2021-03-05
microG flavor only: Bromite System Webview on 88.0.4324.207
microG flavor only: F-Droid 1.11
microG flavor only: microG 0.2.18.204714
February 07th, 2021
ASB Security string 2021-02-05
microG flavor only: Bromite Webview on 88.0.4324.141
microG flavor only: Updated microG from upstream to 0.2.17.204714-5
microG flavor only: F-Droid updated to 1.10-alpha-234
January 17th, 2021
ASB Security string 2021-01-05
Standard flavor only: System Webview on 87.0.4280.101 & fix of persistent histograms eating disk space
microG flavor only: Bromite Webview on 87.0.4280.131
microG flavor only: Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
microG flavor only: F-Droid updated to 1.10-alpha1-212
December 18th, 2020
ASB Security string 2020-12-05
Standard flavor only: System Webview on 86.0.4240.198
microG flavor only: Bromite Webview on 87.0.4280.68
microG flavor only: Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)
microG flavor only: F-Droid updated to 1.10-alpha1-114
November 08th, 2020
ASB Security string 2020-11-05
Fix of AOSP E-Mail widget
Fix for CVE-2020-15999
Standard flavor only: System Webview 86.0.4240.185
microG flavor only: Bromite Webview on 86.0.4240.181
microG flavor only: Updated microG with fixes in GCM and EN API
microG flavor only: Replaced weak F-Droid signatures with ROM's V2 signatures
October 12th, 2020
ASB Security string 2020-10-05
Updated TimeService.apk
microG flavor only: Bromite Webview on 86.0.4240.73
microG flavor only: updated microG with included Exposure notification API (for Covid tracing apps)
September 14th, 2020
ASB Security string 2020-09-05
Standard flavor only: System Webview on 85.0.4183.101
microG flavor only: Bromite Webview on 85.0.4183.86
August 9th, 2020
ASB Security string 2020-08-05
Standard flavor only: System Webview on 84.0.4147.89
microG flavor only: Bromite Webview on 84.0.4147.113
July 12th, 2020
ASB Security string 2020-07-05
microG flavor only: updated prebuilt microG GmsCore fom /e/ project to fix FCM registration issues
microG flavor only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
microG flavor only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
June 09th, 2020
ASB Security string 2020-06-05
Standard flavor only: System Webview on 81.0.4044.138
microG flavor only: Bromite Webview on 83.0.4103.76
May 07th, 2020
ASB Security string 2020-05-05
Standard flavor only: System Webview on 81.0.4044.117
microG flavor only: Bromite Webview on 81.0.4044.127
microG flavor only: AuroraStore updated to 3.2.8
April 10th, 2020
ASB Security string 2020-04-05
Fix for CVE-2020-8597 (external/ppp)
Kernel: CVE-2019-10638 siphash 128bit for IP generation
Standard flavor only: System Webview on 80.0.3987.132
microG flavor only: Bromite Webview on 81.0.4044.76
microG flavor only: AuroraStore updated to 3.2.4
March 07th, 2020
ASB Security string 2020-03-05
Standard flavor only: System Webview on 80.0.3987.117
microG flavor only: Bromite Webview on 80.0.3987.118
microG flavor only: AuroraStore updated to 3.2.0
microG flavor only: Added Netguard app (F-Droid version) to SELinux domain allowing to access /proc/net
February 07th, 2020
ASB Security string 2020-02-01
Standard flavor only: System Webview on 79.0.3945.136
microG flavor only: Bromite Webview on 79.0.3945.139
microG flavor only: AuroraStore updated to 3.1.8
January 13th, 2020
ASB Security string 2020-01-05
Standard flavor only: System Webview on 79.0.3945.116
microG flavor only: Bromite Webview on 79.0.3945.107
microG flavor only: AuroraStore updated to 3.1.7
microG flavor only: AuroraServices updated to 1.0.5
December 7th, 2019
ASB Security string 2019-12-05
Standard flavor only: System Webview on 78.0.3904.96
microG flavor only: AuroraStore updated to 3.1.5
November 10th, 2019
ASB Security string 2019-11-05
microG flavor only: Bromite Webview on 78.0.3904.72
microG flavor only: microG GMS core updated to 0.2.9
October 15th, 2019
ASB Security string 2019-10-05
Standard flavor only: System Webview on 77.0.3865.92
microG flavor only: Bromite Webview on 77.0.3865.104
microG flavor only: AuroraStore updated to 3.1.3
September 10th, 2019
ASB Security string 2019-09-05
Standard flavor only: System Webview on 76.0.3809.111
microG flavor only: AuroraServices updated to 1.0.4
August 11th, 2019
ASB Security string 2019-08-05
Additional patches from AOSP branch 'nougat-mr2-security-release'
OTA Support
microG flavor only: Bromite Webview on 76.0.3809.100
microG flavor only: Aurorastore 3.0.9 with AuroraServices install method
July 5th, 2019
ASB Security string 2019-07-05
System Webview updated to 75.0.3770.101 (non-microG flavor)
microG flavor only: Bromite Webview on 75.0.3770.109
June 12th, 2019
ASB Security string 2019-06-05
System Webview updated to 74.0.3729.157 (non-microG flavor)
microG flavor only: Bromite Webview on 75.0.3770.86
microG flavor only: Replaced Yalpstore with Aurorastore
microG flavor only: Updated F-Droid & priv. extension
microG flavor only: Updated microG GMS core 0.2.7.x
May 8th, 2019
Security string 2019-05-05
System Webview M74
2nd build variant: "hardened microG build"
April 8th, 2019
Security string 2019-04-05
March 12th, 2019
Security string 2019-03-05
Android System Webview updated to M72 (includes CVE-2019-5786)
February 8th, 2019
Security string 2019-02-05
Android System Webview M71
Kernel updated with many security patches
Additional Spectre V1 mitigations for the kernel
January 12th, 2019
Security string 2019-01-05
December 8th, 2018
Security string 2018-12-05
Fix of 'adb root' bug
November 8th, 2018
Security string 2018-11-05
October 20th, 2018
Security string 2018-10-05
Android System Webview M69
September 9th, 2018
Security string 2018-09-05
August 10th, 2018
Security string 2018-08-05
July 24th, 2018
Security string 2018-07-05
System certificates from Oreo AOSP branch
June 24th, 2018
Initial creation
Security string 2018-06-05
AOSP tag 7.2.1_r36
Android System Webview M67
microG N patches
Patched repositories according to LineageOMS project to support substratum

Tips and tricks
microG installation on build variant A
The ROM (build variant A) is patched for the use of microG, but it does not contain the microG system components.
The best way to obtain them is to install the F-Droid store as app store and to include the microG repository as described on the microG Download page, where you will also find links for the direct download of the .apk files.
Please refer to the official installation instructions. However, there are three pieces of information, which are explained on the microG pages, but unfortunately not directly in the installation instructions, so I would like to point them out here:
Download the latest 'unstable' Gms Core version to avoid "outdated play services" warnings
The Location Provider functionality is included in Gms Core, but also available as separate application. I recommend Gms Core - however, the explanation is not included in Gms Core, but only here
To grant the signature spoofing permission, go to Settings - Apps - Advanced (the 'gear' icon) - App Permissions - Spoof package signature; it is not possible when you enter the individual app's permissions menu
Make sure to grant all permissions to the location and microG apps (best via running the self-test)
Install substratum
This ROM is patched to support the substratum theme engine, so no root required because of substratum (different from unpatched ROMs). Simply download and install the substratum theme engine from the play store (or look further down, if you don't use GApps) and also the theme(s), you wish to use. For any support with regards to substratum itself and the themes, please search on XDA in the respective forums. You may of course also ask here in this thread and I hope people participating here will answer, but I am no substratum expert, so please do not expect too much support from my side, when it comes to substratum details.
Btw, the ROM also works without substratum, so you can simply use it without, e.g. because of the microG patch.
Getting the substratum app without GApps
Without GApps, no official Play store . . . - but: When you search in XDA / the internet or simply install F-Droid (and for example search for "play store" in F-Droid), you will find a suitable alternative . . .
Root
Although not needed for substratum, there are many further valid reasons why root is needed (I myself also use it). The most popular options are:
Official LineageOS su addon (use 'addonsu-14.1-arm-signed.zip')
Magisk (please search XDA on your own)
SuperSU
Note that I cannot and will not support any issues related to Magisk and/or SuperSU
Details about the build variant B (hardened microG build)
The security hardening features of the 2nd build variant are described here

If you come from an official LineageOS 14.1 build and you would like to "dirty-flash" this OMS build - i.e. no wipe to keep your stuff (my recommendation is to do a clean install, see OP) - these instructions on the LineageOS Wiki are helpful. I will however not further explain this, you need to know, what you are doing (if you don't understand these instructions, it really is better and in your own interest, if you don't do it)

Excellent, I clean flashed this build, thank you so much! @MSe1969
For anyone who wants to know which is better - just clean flash.

Hi all, just an interim info:
New build with July ASB will be available mid of next week - Google has only published the AOSP links end of last week and I didn't have any time this week to make a new build...

MSe1969 said:
Hi all, just an interim info:
New build with July ASB will be available mid of next week - Google has only published the AOSP links end of last week and I didn't have any time this week to make a new build...
Click to expand...
Click to collapse
:good:

Hi all, a new build is up:
Sec. string 2018-07-05 (July patch level)
System certificates taken from Oreo AOSP branch
Download here

New build with August ASB patches
Hi all,
new build with August Sec. patches available for download here
Regards, M.

MSe1969 said:
Hi all,
new build with August Sec. patches available
Regards, M.
Click to expand...
Click to collapse
Thank you for the updated build!
Clean flashed the latest build just to be on the safe side, but can these updates be dirty flashed in the future?

legendavey said:
Thank you for the updated build!
Clean flashed the latest build just to be on the safe side, but can these updates be dirty flashed in the future?
Click to expand...
Click to collapse
Sure, if you update "my" build, you can dirty-flash - the recommendation for the clean-flash was/is when you come from a different ROM, like e.g. an official LineageOS build

New build with September ASB patches
Hi all,
new build with September ASB available here:
https://www.androidfilehost.com/?fid=1322778262904001677
Regards, M.

Hi,
although the Oktober ASB are out already, I won't be able to take care before mid of this month. So be patient...

MSe1969 said:
Hi,
although the Oktober ASB are out already, I won't be able to take care before mid of this month. So be patient...
Click to expand...
Click to collapse
That's alright. We're really grateful that you're building for falcon - we can wait!

New build with October Security patches
Hi all,
new build is up and ready for download:
https://www.androidfilehost.com/?fid=11410932744536984306
It contains the October security patches, as well as an update of Android System Webview to version 69.0.3497.109
(All details can be found in the OP)
Regards, M.

November build
New build with November ASB patches (sec. string 2018-11-05) is up:
https://www.androidfilehost.com/?fid=11410963190603843469

December ASB, new build available
Hi all,
a new build with the December ASB patches (Security string 2018-12-05) is available for download:
https://www.androidfilehost.com/?fid=11410963190603869922
It also contains the fix for the 'adb root' bug announced here.
Regards, M.

MSe1969 said:
Hi all,
a new build with the December ASB patches (Security string 2018-12-05) is available for download:
https://www.androidfilehost.com/?fid=11410963190603869922
It also contains the fix for the 'adb root' bug announced here.
Regards, M.
Click to expand...
Click to collapse
Thanks alot. Really appreciate it. God bless you.

January 2019 build
New build is up with January 2019 ASB patches:
https://www.androidfilehost.com/?fid=11410963190603897973

hi thx for the latest update; nice rom; my first time trying it; undortunatley i can't seem to get the location working?
i installed microg core from f-droid which comes with default location package no?
edit/
forgot to mention when i try to configure backend in nlp settings i get message "error initializing backend".
edit2/
okay doh it was a permissions issue! location working now

This thread is dedicated to provide hardened Lineage-OS 18.1 builds with microG included for the OnePlus 3/3T with current security patches.
It is the successor of my Lineage 17.1 thread.
It may be worth to also look there, if you are looking for information.
Download here
Features of this ROM​
Pre-installed microG like LineageOS for microG project (own fork)
Pre-installed AuroraStore, AuroraDroid and AuroraServices
OTA Support
eSpeakTTS engine
Additional security hardening features listed below:
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Mulch System Webview
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Kernel kept up to date with ASB patches of Google kernel/common 'android-4.14-q-release' branch
Debloated from Oneplus blobs for Soter and IFAA
Hardened bionic lib and constified JNI method tables
Option to only use fingerprint unlock for apps and not for the device
Optional timeout for Bluetooth and WLAN connections
Per connection WiFi randomization option
Current release levels​Security string: 2023-06-05
AOSP tag: 11.0.0_r46
Mulch System Webview: M114
Source-code and build instructions​Kernel: https://github.com/lin18-microg/android_kernel_oneplus_msm8996/tree/lin-18.1-mse3
Build manifest: https://github.com/lin18-microg/local_manifests/tree/lin-18.1-hmalloc
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​
If you come from OxygenOS Stock ROM, make sure to update to the latest offered software version (if not, no issue).
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 (see e.g. LineageOS install instructions)
OxygenOS 9.0.6 firmware, which is needed for LineageOS 18.1 - see next section
Download the most current .ZIP file of the ROM and place it to your phone's internal memory
OxygenOS 9.0.6 Firmware​If you come from my LineageOS 17.1 build - or any Android 10 based ROM, you most probably have already the proper firmware.
And yes, LineageOS 18.1 is Android 11, but the latest firmware for this device has been published by Oneplus for Android 9.
How to find out about your current firmware, if you use a Custom ROM:
Connect as root via adb to your phone and enter the command adb shell cat /system/vendor/firmware_mnt/verinfo | grep Time_Stamp
If the result is "Time_Stamp": "2019-11-04 21:25:29", you are on the latest firmware, if the date/time is earlier, you need to update the firmware. THIS THREAD has got more information for you.
If you come from an Oreo (Android 8.x) Custom ROM, READ THE OP OF THIS THREAD CAREFULLY !
I can't explain it better and I am not going to repeat or summarize this. It really is in your interest to carefully read it - you have been notified and warned. Please also pay attention to the last section named "Alipay, WeChatpay, Soter and IFAA" - I strongly recommend to use the debloated firmware.
Install TWRP recovery​If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. I recommend to use the TWRP recovery for the OnePlus 3/3T. The following instructions are based on TWRP.
To install TWRP, download the twrp-x.x.x-x-oneplus3.img file (Note: replace "x.x.x-x" in the following instructions with the respective values from the real file name) to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash recovery twrp-x.x.x-x-oneplus3.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and hold Power and vol.down) - DO NOT boot into the phone's Android system after having flashed TWRP! Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP must be TWRP in recovery mode.
Advanced Wipe​ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM![/B]
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory". Swipe to confirm the deletion and get back into the main menu.
DO NOT flash Gapps!
This ROM comes with pre-installed microG. So don't attempt to flash Gapps.
Install ROM​In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard). Choose the .ZIP file of our ROM and swipe to flash.
If you update from a previous version of my ROM, including my LineageOS 17.1 build, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 18.1 - be patient, the first boot after flashing a new ROM takes quite long!
Dealing with signed builds​Please note, that this builds is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash" (recommended), or - you do this on your own risk - you may try the below steps.
This happens at your own risk - make a backup with TWRP before!
Download and extract the file migration.sh from this archive
This file helps you to migrate from a build signed with the publicly available test keys (i.e. all builds around, which do not state that they are signed). If you come from another signed build (e.g. official LineageOS), you have to adapt the file accordingly (see below links).
boot into TWRP
push the migration.sh file to the directory /data/local on your device and mount the /system partition in TWRP (you can do so using the dedicated TWRP's menu entry)
launch the built-in terminal in TWRP, cd into /data/local, make migration.sh executable (chmod +x) and execute the command ./migration.sh official
(In case you receive an error, try sh ./migration.sh official instead)
flash the ROM .zip
wipe Cache and Dalvik/ART Cache
reboot system
More background information and the "theory behind" can be found in the LineageOS wiki and AOSP reference.
Why no Android 12 / LineageOS 19 build ?​The answer can be found here: https://lineageos.org/Changelog-26/ (section "Let’s talk about legacy devices…").
Bug reports:​If you have a problem, please create a post with these informations:
Original Kernel shipped with this rom:
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
microG project
Graphene OS project
csagan5 (Bromite)
WhyOrean (Aurora)
nvertigo67 (for the modded 9.x firmware and for collaboration)
SkewedZeppelin (Kernel patches)

Change Log
June 2023
ASB Security string 2023-06-05
Some kernel patches
Mulch Webview 114.0.5735.61
microG on 0.2.28.231657-5
FakeStore 0.2.0
AuroraStore 4.2.3
May 2023
Security string 2023-05-05
Some kernel patches
Mulch Webview 113.0.5672.77
April 2023
Security string 2023-04-05
Some kernel patches
Removed Bromite browser and shipped LineageOS' Jelly instead
Mulch Webview 112.0.5615.48
March 2023
Security string 2023-03-05
Some kernel patches
Bromite Webview replaced by Mulch Webview 111.0.5563.58
February 2023
ASB Security string 2023-02-05
microG on 0.2.27.223616-3
Some kernel patches
Spoof apps installed by G*PlayStore
January 2023
Security string 2023-01-05
Bromite Browser and Webview updated to 108.0.5359.156
Some kernel patches
microG 0.2.26.223616-16
December 2022
Security string 2022-12-05
Bromite Browser and Webview updated to 108.0.5359.106
Some kernel patches
microG 0.2.26.223616-2
November 2022
Security string 2022-11-05
Bromite Browser and Webview updated to 106.0.5249.163
Some kernel patches
microG 0.2.25.223616-10
October 2022
Security string 2022-10-05
Bromite Browser and Webview updated to 105.0.5195.147
Some kernel patches
microG 0.2.24.223616-61
September 9th, 2022
Security string 2022-09-05
Bromite Browser and Webview updated to 104.0.5112.91
Kernel: Some patches and also hardening (GrpaheneOS patches)
microG 0.2.24.214816-30
Contacts app slightly 'de-Googled'
August 6th, 2022
Security string 2022-08-05
Bromite Browser and Webview updated to 103.0.5060.140
Some kernel patches
July 14th, 2022
Security string 2022-07-05
Some kernel patches
June 15th, 2022
Security string 2022-06-05
Some kernel patches
Bromite Browser and Webview on 102.0.5005.96
microG updated to 0.2.24.214816-11
May 9th, 2022
Security string 2022-05-05
Some kernel patches
Bromite Browser and Webview on 101.0.4951.53
microG updated to 0.2.24.214816-10
Mozilla Location provider on 1.5.0
April 15th, 2022
Security string 2022-04-05
Some kernel patches
Bromite Browser and Webview on 100.0.4896.57
March 15th, 2022
Bromite Browser and Webview on 99.0.4844.58 (bugfix build)
March 12th, 2022
Security string 2022-03-05
Some kernel patches
Bromite Browser and Webview on 99.0.4844.55
microG 0.2.24.214816-2
AuroraStore 4.1.1
Janaury 20th, 2020
Security string 2022-01-05
Some kernel patches
A couple of patches and fixes from LineageOS
December 19th, 2021
Security string 2021-12-05
Bromite Webview and Browser on 96.0.4664.54
microG 0.22.214516-21
November 13th, 2021
Security string 2021-11-05
Bromite Webview and Browser on 94.0.4606.109
October 15th, 2021
Initial build:
Security string 2021-10-01
AOSP tag 11.0.0_r46
Pre-installed microG (0.2.22.212658-2) like LineageOS for microG project (own fork)
Pre-installed AuroraStore (4.0.7), AuroraDroid (1.0.8) and AuroraServices (1.1.1)
OTA Support
eSpeakTTS engine
Bromite (93.0.4577.83) as default browser
Additional security hardening features listed below:
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView (93.0.4577.83)
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Debloated from Oneplus blobs for Soter and IFAA
Hardened bionic lib and constified JNI method tables
Option to only use fingerprint unlock for apps and not for the device
Optional timeout for Bluetooth and WLAN connections
Per connection WiFi randomization option

Tips & tricks
Please refer to the FAQ section here

Hi
Thanks for this amazing rom! Have not had any major issues that I can report. I think you forgot to add the download link? Could not find it here but got it from your Los 17 thread.
lin18-microG - Browse /oneplus3 at SourceForge.net
sourceforge.net
This is a solid build until we see A12 betas/alpha coming soon, hope you'll fork the same flavor for those roms

rudolf895 said:
Hi
Thanks for this amazing rom! Have not had any major issues that I can report. I think you forgot to add the download link? Could not find it here but got it from your Los 17 thread.
lin18-microG - Browse /oneplus3 at SourceForge.net
sourceforge.net
This is a solid build until we see A12 betas/alpha coming soon, hope you'll fork the same flavor for those roms
Click to expand...
Click to collapse
Oops, thanks for the hint! Must have gone lost, when I edited the thread, adding it again.
Edit:
I am a little bit "conservative", when it comes to providing new versions. That means: Eventually yes (assuming my device continues to work smoothly), but definitely not before LineageOS officially releases 12 for the OP3(T) and not before microG is supported for 12.
And even if those prerequisites are met, it may take several weeks, so expect at least another 6-7 months from now, before we can seriously talk about a 12 flavor for this build.

MSe1969 said:
Oops, thanks for the hint! Must have gone lost, when I edited the thread, adding it again.
Edit:
I am a little bit "conservative", when it comes to providing new versions. That means: Eventually yes (assuming my device continues to work smoothly), but definitely not before LineageOS officially releases 12 for the OP3(T) and not before microG is supported for 12.
And even if those prerequisites are met, it may take several weeks, so expect at least another 6-7 months from now, before we can seriously talk about a 12 flavor for this build.
Click to expand...
Click to collapse
fair assessment of the timeline. I have AOSP build (A12) running on my Op5 and it is so good.

H
MSe1969 said:
Oops, thanks for the hint! Must have gone lost, when I edited the thread, adding it again.
Edit:
I am a little bit "conservative", when it comes to providing new versions. That means: Eventually yes (assuming my device continues to work smoothly), but definitely not before LineageOS officially releases 12 for the OP3(T) and not before microG is supported for 12.
And even if those prerequisites are met, it may take several weeks, so expect at least another 6-7 months from now, before we can seriously talk about a 12 flavor for this build.
Click to expand...
Click to collapse
How long did you wait for A10 and A11?

borisSweden said:
H
How long did you wait for A10 and A11?
Click to expand...
Click to collapse
To bring up the build flavor to a new version, I first start with emulator builds to bring all the features up (if still possible and applicable) and to look for features from other ROMs, which I consider meaningful in regards to hardening/data privacy. Next, I try to build for the devices, I support. For the OP3T, the kernel was a bigger issue, as I wanted to keep the entirely upstreamed one (which I didn't succeed with, so I came up with plan B). Depending on personal time and motivation, you can assume ~2 months before the start of the thread as point in time, where I started developing...

I might as well update but I want to fix my mbn auto select problem (I live in Sweden, have a Swedish SIM and EU phone), Bluetooth needs to repair after some time and slwo WiFi. My base is Debloated OOS but should I do a wipe before installing 18.1? As always I use 17.1 hardened edition.
edit: Im a novice but why does the ROM replace Twrp with LOS native recovery. If its installed from twrp it should stay put. And yeah I know, flash Magisk or TWRP app after flashing the ROM.

borisSweden said:
I might as well update but I want to fix my mbn auto select problem (I live in Sweden, have a Swedish SIM and EU phone), Bluetooth needs to repair after some time and slwo WiFi. My base is Debloated OOS but should I do a wipe before installing 18.1? As always I use 17.1 hardened edition.
Click to expand...
Click to collapse
What do you mean exactly with "Debloated OOS"? You mean the debloated firmware linked in the OP?
You can " dirty-flash" my 18.1 build over 17.1.
As indicated already in my 17.1 thread, I haven't experienced your described issue. I am right now using my OP3T as a hotspot in PL using a PL SIM card without any issues...
borisSweden said:
edit: Im a novice but why does the ROM replace Twrp with LOS native recovery. If its installed from twrp it should stay put. And yeah I know, flash Magisk or TWRP app after flashing the ROM.
Click to expand...
Click to collapse
There is a setting in the Updater app, which you need to switch off to keep TWRP untouched.

MSe1969 said:
And yes, LineageOS 18.1 is Android 11, but the latest firmware for this device has been published by Oneplus for Android 9.
Click to expand...
Click to collapse
Cant you salvage something from the MSM8996plus OG Pixel 1? Last update was Android Q. Let me guess, signed drivers?
MSe1969 said:
What do you mean exactly with "Debloated OOS"? You mean the debloated firmware linked in the OP?
You can " dirty-flash" my 18.1 build over 17.1.
As indicated already in my 17.1 thread, I haven't experienced your described issue. I am right now using my OP3T as a hotspot in PL using a PL SIM card without any issues...
Click to expand...
Click to collapse
Lets see if Gabeldorsche fixes Bluetooth. Nvertigo said that the region selecter works as intended but on PDC I got mostly Chinese and US carriers. I had to do a wipe install so its to late do a "dirty install". i forgot Seedvault was a thing.
MSe1969 said:
There is a setting in the Updater app, which you need to switch off to keep TWRP untouched.
Click to expand...
Click to collapse
Doh! Cant you remove that option because TWRP is more useful. I was able to change recovery after installing your ROM thankfully didnt brick or wipe my install.

borisSweden said:
Cant you salvage something from the MSM8996plus OG Pixel 1? Last update was Android Q. Let me guess, signed drivers?
Click to expand...
Click to collapse
No. Firmware is device - not only soc - dependent. For details on what exactly firmware contaims see my thread on (patched) firmware in the general forum.
I.g. the bootloader and the modem partitions are part of the firmware. Overwriting these with otjer devives versions will brick your device, and youu will need to use the msm tool to bring it back to life.
Please read the general forum and all los threafs in the dev forum to get the basics to start messing with firmware.
I don't mean to offend you, but some of your questions seem to me that your current questions are three steps ahead of your current knowledge.

Might as well write stuff I found wrong in the ROM as Im returning to OOS. Aurora F-droid lags to much and the F-droid privilege module doesn't work with it. Manually accepting every install and update isnt that fun so I would recommend going back to the OG app.
Also in the update app for LOS, the timestamp is wrong. It says last update 1970 January 1. Should say 10 October.
Idk what my cellular network bug is but on the to right corner the icon is just wrong. Its 4G then the triangle with a X. In preferred network type settings NR/5G is still present. Doesn't make sense that you can chose 5G.
Bluetooth works as intended but in dev settings Enable Gabeldorsche doesnt do anything. Does it even work?

borisSweden said:
Might as well write stuff I found wrong in the ROM as Im returning to OOS. Aurora F-droid lags to much and the F-droid privilege module doesn't work with it. Manually accepting every install and update isnt that fun so I would recommend going back to the OG app.
Click to expand...
Click to collapse
The ROM comes with AuroraServices, but you have to enable that in the app's setings, then it'll work.
If you try flashing the F-Droid privileged extension, that won't work for sure!
borisSweden said:
Also in the update app for LOS, the timestamp is wrong. It says last update 1970 January 1. Should say 10 October.
Click to expand...
Click to collapse
This normally should only happen, if you haven't fetched any update before (or deleted the app cache). Btw, I took over the LineageOS Updater app "as is" and only overlaid the updater URI.
borisSweden said:
Idk what my cellular network bug is but on the to right corner the icon is just wrong. Its 4G then the triangle with a X. In preferred network type settings NR/5G is still present. Doesn't make sense that you can chose 5G.
Click to expand...
Click to collapse
Tend to agree - will have a look, but I did not change/alter anything here. Will get back...
borisSweden said:
Bluetooth works as intended but in dev settings Enable Gabeldorsche doesnt do anything. Does it even work?
Click to expand...
Click to collapse
No idea, haven't changed anything in that area - this seems original Android code.

MSe1969 said:
No idea, haven't changed anything in that area - this seems original Android code.
Click to expand...
Click to collapse
In theory less battery usage but it could be Fushsia snakeoil. It written in cleaner code. But everyone knows that a higher BT version is more efficient in battery usage. To bad SBC HD isnt working as intended , APTX take to many resources.
MSe1969 said:
The ROM comes with AuroraServices, but you have to enable that in the app's setings, then it'll work.
If you try flashing the F-Droid privileged extension, that won't work for sure!
Click to expand...
Click to collapse
Did I make a mistake? Yes I did.
>Tend to agree - will have a look, but I did not change/alter anything here. Will get back...
I would like to have a carrier volte profile selector or enable Diag mode for PDC button but that is LOS team job.

Hello my favorite "kernel-upstreamer" ,
android-3.18 has been gone and deprecated/android-3.18 has shown up:
Code:
[email protected] /usr/local/src/los16/kernel/oneplus/msm8996 $ LANG=C.UTF-8 git fetch https://android.googlesource.com/kernel/common android-3.18
fatal: couldn't find remote ref android-3.18
[email protected] /usr/local/src/los16/kernel/oneplus/msm8996 $ LANG=C.UTF-8 git fetch https://android.googlesource.com/kernel/common deprecated/android-3.18
From https://android.googlesource.com/kernel/common
* branch deprecated/android-3.18 -> FETCH_HEAD
My educated guess is that support for 3.18 has been finally droped.
As far as I can see caf for 3.18 for 8x96 hasn't seen any updates for at least 14 months.
I've merged 380bbf94c0fc..839523fca2ef from the deprecated branch on top of your lin-17-mse3 - works great. I've also tried to merge the commits from the 4.x.y branches mentioned here: https://source.android.com/security/bulletin/2021-11-01#kernel-components (but to no advance).
Do you have more information? What are your thoughts?
Take care.

nvertigo67 said:
android-3.18 has been gone and deprecated/android-3.18 has shown up:
Click to expand...
Click to collapse
My question about "how long will 3.18 be supported" was way close to this decision. Did I jinx it?

nvertigo67 said:
Hello my favorite "kernel-upstreamer" ,
android-3.18 has been gone and deprecated/android-3.18 has shown up: [...] My educated guess is that support for 3.18 has been finally droped.
Click to expand...
Click to collapse
Well, that is also my conclusion. Pitty, but expectable one day...
nvertigo67 said:
As far as I can see caf for 3.18 for 8x96 hasn't seen any updates for at least 14 months.
Click to expand...
Click to collapse
Hmmm... not really good news either...
nvertigo67 said:
I've merged 380bbf94c0fc..839523fca2ef from the deprecated branch on top of your lin-17-mse3 - works great. I've also tried to merge the commits from the 4.x.y branches mentioned here: https://source.android.com/security/bulletin/2021-11-01#kernel-components (but to no advance).
Do you have more information? What are your thoughts?
Click to expand...
Click to collapse
The source, where I get the few patches for this 18.1 ROM's kernel is the divested-mobile org. on GH (but the guy in fact was also making use of the kernel/common 3.18 repo...), so no real good idea. We may from time to time see some back ports of certain 4.4 commits, but I'm afraid the good times of getting patches f. 3.18 are over...

MSe1969 said:
The source, where I get the few patches for this 18.1 ROM's kernel is the divested-mobile org. on GH (but the guy in fact was also making use of the kernel/common 3.18 repo...), so no real good idea. We may from time to time see some back ports of certain 4.4 commits, but I'm afraid the good times of getting patches f. 3.18 are over...
Click to expand...
Click to collapse
Ironic as it been 5 years since the 3T was released. Do all SoC specific kernels only have 5 years of patches?
Well there is still 4.4 commits or going full 4.4 but then you would only get 1 extra year of commits when the OP5 turns 5 years old.
On the issue of the USB port and Dash not working with 4.4, finding a New old Stock Dash charger is hard and nobody wants to fork out 50 Euros for a Warp 65 charger. Supporting proprietary charging tech is verbose for now.
Only supporting USB-PD is enough also is the phone USB2.0 because of physical limitations?
That's my 2 cents.

New build with November 2021 ASB patches
Hi all, a new build for the OP3(T) containing the November 2021 ASB patches has been released:
https://sourceforge.net/projects/lin18-microg/files/oneplus3/lineage-18.1-20211113-UNOFFICIAL-microG-signed-oneplus3.zip/download
The Updater app should soon indicate it to offer an OTA update.
Security string 2021-11-05
Bromite Webview and Browser on 94.0.4606.109
Some kernel patches
Happy flashing,
Regards, M.

Non-Official Lineage 18.1 for Huawei (anne) - LeaOS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LeaOS is a project which based on LineageOS 18.1 with Andy Yan's and phhusson's Treble GSI patches. I have added my personnals patches for Huawei devices : Signal Strengh, Assisted GPS, NFC, CAST/Miracast, Default Sound etc..) and some eremitein patch
Changelog :
LeaOS March 2023 version
March 2023 SPL
Synchronize with last Lineage Source
Fix dynamic root functionnality
Include AGPS patch
LeaOS February 2023 version
Synchronize with last Lineage Source
LeaOS January 2023 version
January 2023 SPL
Synchronize with last Lineage Source
Add more resolution for offline charging
Spoiler: Old Changelog
LeaOS December 2022 version
December 22 SPL
Synchronize with last Lineage Source
Fix selinux display status bug
Add EMUI 9.1 offline charging
Leaos November 2022 version
November 2022 SPL
Synchronize with last Lineage Source
Fix NFC
Leaos October 2022 version
October 2022 SPL
Synchronize with last Lineage Source
Add patch to fix offline charger (permissif kernel only)
LeaOS September 2022 version
September 2022 SPL
Synchronize with last Lineage Source
Add /splash2 and /modem_log support
Add kirin and huawei properties
Support permissive (non crypt data) or enforce kernel
Fix vndk detect bug
LeaOS August 2022 version
August 2022 SPL
Synchronize with last Lineage Source
Fix minor SE denied ioctl
Update Lite Google Apps to 2.6
LeaOS July 2022 version
July 2022 SPL
Synchronize with last Lineage Source
LeaOS Jun 2022 version
Jun 2022 SPL
Synchronize with last Lineage Source
Fix MediaScanner crash and no default sound (ringtone, alarms..)
Add support of EMUI 9.1.0.405 (preav partition)
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download file : "LeaOS-20230407-iceows-ane.7z" and extract img file
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage,
Wipe data
install DRM patch for EMUI 9.1 : 8-Huawei-FixPreav-AB-v1.1-signed.zip
(optional) install now Google Apps Lite : 1-Huawei-DataPrep-DeCrypt-AB-v1.0-signed.zip and [RECOVERY]LiteGapps_arm64_11.0_v2.6_official.zip
reboot to System and set up the phone with Lineage first start assistant. You can also add most user
Enjoy !!!
More informations to install here : https://forum.xda-developers.com/t/guide-emui9-p20-lite-basics.4341373/
Source Code:
https://github.com/Iceows
ROM OS Version: Android 11
ROM Kernel: Linux Huawei 4.9.148 or Phenix 4.9.319
ROM Firmware Required: EMUI 9
Based On: Lineage 18.1
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group

AltairFR said:
Non-Official Lineage 18.1 for Huawei (anne) - LeaOS
Click to expand...
Click to collapse
AltairFR said:
my personnals patches for Huawei devices : Encryption.... NFC...
Click to expand...
Click to collapse

which twrp do you recommend to install?

I am using the official version twrp 3.6.1 for anne. But I think older versions work too.
Huawei P20 Lite
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me

AltairFR said:
I am using the official version twrp 3.6.1 for anne. But I think older versions work too.
Huawei P20 Lite
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Click to expand...
Click to collapse
Hi
Is boot override finally solved?
Cheers

Is anyone experiencing phone call/receive bug? This is the only bug I've found till now. If I start a call it suddenly stops, and if I try to receive a call, I don't see any incoming call popping up.

The August build didn't work for me, it got stuck on a boot loop. I had to install the July build and that one did work. I really appreciate this effort to bring the latest versions of LineageOS to ANNE.

Hi
I will verify in my ANE, perhaps i have not upload the right version. I have also compile yesterday lineage 19.1 , but for the moment not upload it
Thanks for the report

I have not the bootloop. What version of emui do you have? What patch did you install?

Hi there! Cool guide!
Just before trying it I want to double check one thing, does the DRM-patch for EMUI mean I can install safely without first downgrading? Also for some reason I don't have 9.1.0.405 but rather 9.1.0.401 installed. If you would have a guess do you think the DRM-patch may work with that version too? How hard do you think I would brick my phone if it would not work?

Hi.
I have french orange version of ane-lx1 (C109) so my max emui is 405. For 401 version you can install LeaOS without patch , install app drm info from playstore, check if the app show correct info of drm. If the app show nothing, reboot in twrp and install the patch

AltairFR said:
Non-Official Lineage 18.1 for Huawei (anne) - LeaOS
LeaOS is a project which based on LineageOS 18.1 with Andy Yan's and phhusson's Treble GSI patches. I have added my personnals patches for Huawei devices : Signal Strengh, Assisted GPS, NFC, CAST/Miracast, Default Sound etc..) and some eremitein patch
Changelog :
LeaOS August 2022 version
August 2022 SPL
Synchronize with last Lineage Source
Fix minor SE denied ioctl
Update Lite Google Apps to 2.6
LeaOS July 2022 version
July 2022 SPL
Synchronize with last Lineage Source
LeaOS Jun 2022 version
Jun 2022 SPL
Synchronize with last Lineage Source
Fix MediaScanner crash and no default sound (ringtone, alarms..)
Add support of EMUI 9.1.0.405 (preav partition)
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download file : “LeaOS-20220813-iceows-ane.7z" and extract img file
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage, data
(optional) install AGPS patch : 4-Huawei-AGPS-AB-v1.1-signed.zip
(optional) install DRM patch for EMUI 9.1.0.405 : 8-Huawei-FixPreav-AB-v1.0-signed.zip
(optional) install now Google Apps Lite : [RECOVERY]LiteGapps_arm64_11.0_v2.6_official.zip
reboot to System and set up the phone with Lineage first start assistant. You can also add most user
Enjoy !!!
More informations to install here : https://forum.xda-developers.com/t/guide-emui9-p20-lite-basics.4341373/
Source Code:
https://github.com/Iceows
ROM OS Version: Android 11
ROM Kernel: Linux 4.19.x
ROM Firmware Required: EMUI 9
Based On: Lineage 18.1
Credits:
Frax3r
PHH
eremitein
And all the others who tested my patches and helped me improve this ROM
Support Group
Click to expand...
Click to collapse
When was last update for this Rom??
Dose all pached and fixes applied to it??
How stable is it??
Dose this links /post and Rom gets updates and renew as new updates or patches comes out??

AltairFR said:
Hi.
I have french orange version of ane-lx1 (C109) so my max emui is 405. For 401 version you can install LeaOS without patch , install app drm info from playstore, check if the app show correct info of drm. If the app show nothing, reboot in twrp and install the patch
Click to expand...
Click to collapse
Okay, cool!
Regarding downgrading, is that still a thing that is needed for flashing or is it a thing of the past?

brugne92 said:
Is anyone experiencing phone call/receive bug? This is the only bug I've found till now. If I start a call it suddenly stops, and if I try to receive a call, I don't see any incoming call popping up.
Click to expand...
Click to collapse
This is a very old problem on android 11 (all GSI and ROM) and Huawei. After 6 months of research, I finalized this weekend a patch for all hi6250 phones (and even all Huawei). It has been successfully tested on a PRA-LX1. I am looking for someone to test it on ANE-LX1. Would you be ok to take the test?

AltairFR said:
This is a very old problem on android 11 (all GSI and ROM)
Click to expand...
Click to collapse
On GSI (I mean normal GSI, not yours) it's not a problem at all .
AltairFR said:
After 6 months of research, I finalized this weekend a patch for all hi6250 phones
Click to expand...
Click to collapse
. Bravo!

Alf. Do you want test it ?

AltairFR said:
I have not the bootloop. What version of emui do you have? What patch did you install?
Click to expand...
Click to collapse
How do I check the EMUI version? I can't find it anywhere. Also, let's say I want to upgrade to the latest build to test it again: is it possible to do it without losing data? And then return to the previous build if it doesn't work, also without losing data.
Edit: also, is it possible to apply builds with the FRP enabled?
Edit: I would also appreciate if no Google software was installed by default in the ROM. I'd rather have the stock LineageOS camera app than the proprietary Gcam Lite (or whatever it is called).

I'm sorry but it looks like i'm totally lost.
I managed to make almost everything work and i'm really happy this device is still so well supported by the community. But i cannot, for the life of me, bring magisk to work with this ROM.
I suppose this doesn't technically concern you, but i really hope you'll be able to help me nonetheless.
Cheers
Edit: Some details i've missed the first time:
I have TWRP (3.6.2_9-0) running
I already tried flashing a few magisk apk's turned .zip (namely: "Magisk-v24.3" and "v23-canary-phh") using TWRP
TWRP logs mostly "flashed successfully", but in the magisk manager app, magisk isn't being detected
I know about the recovery patch method but
1) i recall magisk natively supporting treble GSI's
2) i had magisk working before but on lineageOS 16/Android 9 (still based on EMUI 9 firmware though) and i think it ran without a modified recovery
3) i could very well be wrong here but: since i've flashed a TWRP recovery_ramdisk, wouldn't that mean i had to patch and then flash the TWRP recovery .img? I don't know why but this seems... Weird?

It have not test in emui9 but in emui8 magisk version canary works natively on LeaOS. You just have to download it from the official site of magisk, rename it to .zip and install it with twrp

aavalos said:
How do I check the EMUI version? I can't find it anywhere. Also, let's say I want to upgrade to the latest build to test it again: is it possible to do it without losing data? And then return to the previous build if it doesn't work, also without losing data.
Edit: also, is it possible to apply builds with the FRP enabled?
Edit: I would also appreciate if no Google software was installed by default in the ROM. I'd rather have the stock LineageOS camera app than the proprietary Gcam Lite (or whatever it is called).
Click to expand...
Click to collapse
It is not gcam from Google in leaos , but Gcam mod. The stock LineageOS cam have some bugs with the flash on huawei

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LeaOS is a project which based on AOSP with trebledroid patches.
This build includes settings parameters for Huawei ANE-LX1 (P20 Lite) as well as several evolutions:
Offline charging
AGPS Supl20
SafetyNet
GCam for kirin
Changelog :
LeaOS-AOSP May 2023 version
Move to android13-r44 (May SPL)
All variant are now mono-modem to avoid LTE/data disconnection
Safetynet pass with dynamic spoof pixel model
LeaOS-AOSP April 2023 version
Move to android13-r41 (April SPL)
Fix audio bug
LeaOS-AOSP March 2023 version
Move to android13-r35 (April SPL)
LeaOS-AOSP Feb 2023 version (24/02)
Move to android13-r29 (Feb SPL)
Add AGPS supl20 features
Add securize and pass safetynet (option in TrebleApp Setting)
Reduce lag UI
LeaOS-AOSP Jan 2023 version (05/01)
Move to android13-r24 (Jan SPL)
LeaOS-AOSP Dec 2022 version (08/12)
Move to android13-r16 (Dec SPL)
Support data encryption (stock huawei kernel only)
Remove Seedvault backup
Add Magisk support (need securize phone before)
LeaOS-AOSP Nov 2022 version (09/11)
Add Android Beam NFC and HCE NFC
Move to android13-r14 (Nov SPL)
Fix offline charging (no need patch now)
Reduce img size by remove apex files in system_ext
LeaOS-AOSP Oct 2022
Add Google Apps version
Fix NFC
Move to android13-r11
Add offline charging patch
LeaOS-AOSP Oct 2022 version (05/10)
Fix screen-recorder crash
Enable adb root
Move to android13-r8
First release with android13-r4
Wireless Display
Pre-requisite :
You must have TWRP installed, see this post to install it : https://forum.xda-developers.com/t/guide-emui9-p20-lite-basics.4341373/
Installation
Download system file : "LeaOS-A13-20230503-iceows-ane.img.xz" (without google apps) or "LeaOS-A13-20230503-iceows-google-ane.img.xz" (google apps version)
Extract img file
Flash system image : fastboot flash system <drag system.img here>
Boot into twrp: power + vol+ while NOT connected to pc
Wipe cache, dalvik/art cache, internal storage
Wipe data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
Reboot to System and setup with android assistant
Enjoy !!!
More informations to install here : https://forum.xda-developers.com/t/guide-emui9-p20-lite-basics.4341373/
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13.0
ROM Kernel: Stock kernel or Phenix 4.9.302 and sup
ROM Firmware Required: EMUI 9
Based On: Google AOSP + TrebleDroid patches
Credits:
@Frax3r (Testing)
@PHH (manifest)
@eremitein (patches)
@RakinTheGreat (GCam)
@TureX (Kernel)
@Sooti777 (patches)
@Haridhayal (patches)
@harvey186 (patches)
@DarkJoker360 (patches)
@chondoe (patches)
@ponces (patches)
@Adbdelhay.ali (kernel perm)
And all the others who tested my patches and helped me improve this ROM
Kernel :
Android 13 for P20 lite (Tested GSIs)
Here are recent A13 GSIs that booted and worked on my P20 lite Hi6250 Requirements: You can flash SHRP recovery that have all the requirements to make Android 13 boot normally (including permissive kernel, decrypt data, selinux fix, AIO fix and...
forum.xda-developers.com
Support Group
Channel update

reserved

Worked baseband thanks iceows
- issue aosp screen record not working LeaOS 13

I have honor play with kirin 970 chaps with emui 9.1 this GSI boot in my phone fine but camera not work in my phone , it is show Image but it is freezing and stop camera app after that

cvenal said:
I have honor play with kirin 970 chaps with emui 9.1 this GSI boot in my phone fine but camera not work in my phone , it is show Image but it is freezing and stop camera app after that
Click to expand...
Click to collapse
Ok thank you. Can you give me more details about your phone model, your emui version with minor version and your kernel version. I already see that the screen record works

AltairFR said:
Ok thank you. Can you give me more details about your phone model, your emui version with minor version and your kernel version. I already see that the screen record works
Click to expand...
Click to collapse
My phone model COR-AL00 and I am use EMUI 9.1.0.312 I can use the harmony os but The system partition can not resize it give 2.8 Gbit when emui 9.1.0.312 I can resize system partition to 4 Gbit
and I am use this kernel

technodeha said:
Worked baseband thanks iceows
- issue aosp screen record not working LeaOS 13
View attachment 5729269
Click to expand...
Click to collapse
Ok i have fix the pb in yhe next release

I can't get NFC to work. I tried your patch as well as "universal" one. The universal one does not work, yours does not install in TWRP. I tried same approach as with the rest of the patches in your description.

Ok i have not test but fix is easy

Thank you for this great ROM
The speaker volume low during calls. I have tried volume booster goodev.apk, but not worked

Awesome rom, everything works fine Only NFC to fix

My phone is p20 lite ANE-LX2J 9.1.0.324(C111E37R1P6). the ringtone and notification stuck on zero
could you put the following Patch in the next build
"Make volume steps and defaults adjustable for all audio streams"
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/226009
to allow using "ro.config.ring_vol_steps" in build.prop
Edit
Problem solved
I have restored vendor partition. I think vendor partition was corrupted

Abdelhay.ali said:
My phone is p20 lite ANE-LX2J 9.1.0.324(C111E37R1P6). the ringtone and notification stuck on zero
could you put the following Patch in the next build
"Make volume steps and defaults adjustable for all audio streams"
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/226009
to allow using "ro.config.ring_vol_steps" in build.prop
Thanks
Click to expand...
Click to collapse
Yes of course. I'm compiling new patches, I need to adapt this one for android 13 and include it immediately

luka_bubi said:
I can't get NFC to work. I tried your patch as well as "universal" one. The universal one does not work, yours does not install in TWRP. I tried same approach as with the rest of the patches in your description.
Click to expand...
Click to collapse
Fix in the 18/10 release

technodeha said:
Worked baseband thanks iceows
- issue aosp screen record not working LeaOS 13
View attachment 5729269
Click to expand...
Click to collapse
Fix in the 18/10 release

Bro I couldn't find the wallpaper and styles feature in setting. I could only see the wallpaper option

AltairFR said:
View attachment 5728215​
LeaOS is a project which based on AOSP with trebledroid patches.
Changelog :
LeaOS-AOSP Oct 2022 version (18/10)
Add Google Apps version
Fix NFC
Move to android13-r11
LeaOS-AOSP Oct 2022 version (05/10)
Fix screen-recorder crash
Enable adb root
Move to android13-r8
First release with android13-r4
Pre-requisite :
You must have TWRP installed, see this post to install it : https://forum.xda-developers.com/t/guide-emui9-p20-lite-basics.4341373/
Installation
Download system file : "LeaOS-A13-20221018-iceows-ane.7z" (without google apps) or LeaOS-A13-20221018-iceows-google-ane.7z" (google apps version)
Extract img file
Download kernel file here https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/ and extract img file
Flash system image : fastboot flash system <drag system.img here>
Flash kernel image : fastboot flash kernel <drag phenix.img here>
Boot into twrp: power + vol+ while NOT connected to pc
Wipe cache, dalvik/art cache, internal storage, data
Install decrypt patch :1-Huawei-DataPrep-DeCrypt-AB-v1.0-signed.zip
(optional) install DRM patch for EMUI 9.1.0.401 and sup : 8-Huawei-FixPreav-AB-v1.0-signed.zip
reboot to System and set up the phone with Lineage first start assistant. You can also add most user
Enjoy !!!
More informations to install here : https://forum.xda-developers.com/t/guide-emui9-p20-lite-basics.4341373/
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13.0
ROM Kernel: Only Phenix Linux 4.9.302 and sup
ROM Firmware Required: EMUI 9
Based On: PHH AOSP + TrebleDroid patches
Credits:
@Frax3r (Testing)
@PHH (manifest)
@eremitein (patches)
@RakinTheGreat (GCam)
@TureX (Kernel)
@Sooti777 (patches)
@Haridhayal (patches)
@harvey186 (patches)
@DarkJoker360 (patches)
@chondoe (patches)
@ponces (patches)
And all the others who tested my patches and helped me improve this ROM
Support Group
Click to expand...
Click to collapse
hi, what is the patch for?

I do not understand your question. I made more than 10 patches on huawei

@AltairFR i tried to install this rom but at reboot, the screen remains frozen in initial logo HUAWEI

Do you have install phenix kernel ? Do you have uncrypt data partition ?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INTRODUCTION
LineageOS is a free, community built, aftermarket firmware distribution of Android , which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
What's working
All Features are working and tested from last 3 months.
Known issues:
-None -
SELinux Status Enforcing.
CTS Passes without Root.
Encrypted By Default.
OTA works.
Note : All development of these amazing ROMs is done by Zeelog. The OP anandsvm is tester ,provide assistance and collect and submit bug reports.
DOWNLOAD
Telegram Channel
****************************************************************************************
How to Install(Follow All Instruction)
(Dont Report Bugs if you dont follow below Instructions)
Android 13 Release Notes/Installation Guide
1. Clean Flash
• Clean flash is mandatory: you are required to backup all of your existing data to your computer or your preferred cloud service and avoid using nandroid backup.
2.Flash TWRP
• Flash the new TWRP Recovery made by Zeelog : ( Mandatory)due to various changes in fstab file and encryption implementation, you are required to flash the new TWRP of which the link is undermentioned
Link
3. Wipe and format Device ( Both are different)
• After you flash and boot into the new TWRP recovery, format data and reboot to the recovery again.
Now, wipe all the partitions (i.e. system, vendor, data, internal storage). Wiping Internal might throw an error because of missing /data/media/ which is okay, reboot to recovery again.
This format data and wiping of other partitions is required only once every clean flash.
NB : encryption is now enabled by default and that is why a clean flash would cost you a data format.
4.Flash ROM and Gapps
*To use internal storage for transferring files from PC
From TWRP > tap Advanced > Terminal > run command: mkdir -p /data/media/0/
• Copy the latest releases LineageOS 20.0 Android 13 rom and latest NikGapps (optional) (basic edition is preferred) to your internal storage/otg media/sd card etc.
Flash the rom + gapps (if you need) using the usual method.
Nik Gapps Download : Link
Nik Gapps Addon : Link
****************************************************************************************
GitHub/OTA Release : Link
Dev Profile : Link
Support my efforts: Donate to Zeelog
Contributors
Zeelog
ROM OS Version: Android 13
ROM Kernel: Linux 4.9
ROM Firmware Required: Latest Firmware V11.0.2.0.NCFMIXM
Version Information
Status: Stable
Stable Release Date: 2022-10-06

Changelog for Android 13:
Release 1 : Oct 6
- Initial Build - Android 13
- October security patch
- Synced latest LineageOS sources as of 06 October 2022
- Synced kernel with latest Google's android-4.9 as of 06 October 2022
- Merged latest CLO tags as of 06 October 2022
- FBE (File based encryption) enabled by default *
Release 2 : Oct 7
*Fixed sdcard detection
Release 3 : Oct 21
Synced latest LineageOS sources as of 21 October 2022
- Android 13 release 11
- Synced kernel with latest Google's android-4.9 as of 21 October 2022
- Merged latest CLO tags as of 21 October 2022
- Revamped default launcher - added more features
- Update Dialer, Messaging & Contacts apps
- Added smart charging feature
- Added more custom button actions
- Add more fonts
- Memory & cache optimizations
- Updated Aperture camera app
- Add flashlight blink notification feature
Release 4: Nov 10
- November security patch
- Synced latest LineageOS sources as of 09 November 2022
- Synced kernel with latest Google's android-4.9 as of 09 November 2022
- WiFi: Add WPA3 security support
- Hotspot: Add WPA3 security support
- Hotspot: Add hidden SSID feature
- Wifi/BT: Add WiFi/BT timeout options
- Launcher updates
- Add more private DNS providers
Release 5: Dec 24
- December SP
- Synced latest LineageOS sources as of 24 Dec 2022
- Synced Kernel with latest Google android-4.9.336
- Fixed reboot issues related to Wi-Fi SSID length
- Fixed reboot issues related to charging
- Add lockscreen weather
- Add weather tile
- Integrated hotspot in Internet tile
- Add more screen recorder options
- Add firewall status bar icon
- Add notification sound panel in volume panel (when unlinked)
- Add compass tile
- Launcher: Add memory info bar
- Add support for Micro-G
- Add screenshot tile
- Add GameSpace feature
- Fixed L2TP/PSK VPN
- Fixed jelly browser download dialogue
- Fixed crash with Clock analogue widget
Release 6 Jan 14 2023
-January security patch
-Synced latest LineageOS sources as of 14th January 2023
-Synced Kernel with latest Google android-4.9 [4.9.337]
-Add full support for F2FS
-Launcher: Add option to enable/disable search bar in app drawer
-Dirac: Update lottie and dirac tile
-FM: Switched to Revamped FM radio (credit: iusmac)
-Fix notification light text
-Translation updates

Reserved:

Screenshots

Best ROM for mido currently. Even on 3GB version this ROM is very fast and doesn't lag over time.

I can't get the alarm to sound.
I have tried with the sound enabled, with vibration, with do not disturb, in no case if the screen is off the alarm sounds.
It happens to someone else?
Thank you

I've been using it since it was first published. I haven't noticed any problem so far. Thank you to those who contributed.

Robe7 said:
I can't get the alarm to sound.
I have tried with the sound enabled, with vibration, with do not disturb, in no case if the screen is off the alarm sounds.
It happens to someone else?
Thank you
Click to expand...
Click to collapse
The Clock app works with no problem for me. You should give it all necessary permissions if you haven't done it.

Huge thanks for your work

It worked very well on October version but new November causes Pixel Luncher stop working and Recent button acting strange. I use other launcher with November version. I tried few different fixes founded on few websites but any of them don't work. I have to reflash October update and everything works very well. I haven't tried only clean flash with November version yet. I'm not sure what else I can do.

It worked very well on my device，but battery charges slowly，just 5V 1A.

Screen recorder does not record sound.,but thanks anyway,probably the best room for Mido

dxzelda said:
It worked very well on my device，but battery charges slowly，just 5V 1A.
Click to expand...
Click to collapse
same problem , slow charge <500mah show in the lock screen, I have to turn it off to chargue fast

Thx for the rom <3

thanks for continuing to support this superb phone.

I followed the instructions in detail and my device boots into TWRP. I have done the process 5 or 6 times installing the gapps as without and it does the same, I have downloaded the ROM again and nothing. Help!!!

dxzelda said:
It worked very well on my device，but battery charges slowly，just 5V 1A.
Click to expand...
Click to collapse
Here I get around 1750 mA of current and 4.1V . around 7W .
You have to buy new original cable.

sxnii13 said:
I followed the instructions in detail and my device boots into TWRP. I have done the process 5 or 6 times installing the gapps as without and it does the same, I have downloaded the ROM again and nothing. Help!!!
Click to expand...
Click to collapse
Follow all steps correctly.

sxnii13 said:
I followed the instructions in detail and my device boots into TWRP. I have done the process 5 or 6 times installing the gapps as without and it does the same, I have downloaded the ROM again and nothing. Help!!!
Click to expand...
Click to collapse
Have you tried using NikGapps instead of gapps?
NikGapps - Browse /Releases/NikGapps-T/08-Sep-2022 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net

yerbakili said:
Have you tried using NikGapps instead of gapps?
NikGapps - Browse /Releases/NikGapps-T/08-Sep-2022 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
Click to expand...
Click to collapse
Yes, I am using Nikgapps, specifically the basic ones. I even flashed the rom without Gapps and I have the same result.