Database Info

[CLOSED][EOL] LineageOS 12.1 for Z1c with current Sec.Patches

{
"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.

[ROM][UNOFFICIAL]LineageOS15.1+MICROG

UNOFFICIAL LineageOS fork with built-in microG gapps implementation.​LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
While the core operating system is still released as part of the Android Open Source Project, the majority of core apps are not. It gets worse: More and more libraries and APIs are only available on phones that run various Google apps pre-installed, effectively locking third-party apps to the Google ecosystem. Several popular open-source applications already require some of Google’s proprietary libraries to be installed. Increasing demand in the free software community in addition to severe problems in Google’s proprietary software discovered by the Android modding community, have led to the development of a free software clone of Google’s proprietary core libraries and applications - the microG Project was born.
This image uses the restricted microG patch meaning only system packages embedded in the build can use FAKE_SIGNATURE permission.
I have also replaced the default chromium system webview with the bromite system webview (20190519 build) which includes extra ad-blocking and privacy patches on top of chromium.
Code:
DISCLAIMER: THERE IS NO WARRANTY OF ANY KIND APPLICABLE TO THE CONTENT BELOW
What's working:
Boots
Wifi
NFC
Bluetooth
Camera
Video Playback
Audio
Sensors
GPS
SafetyNet Check passes both Basic Integrity and CTS profile match!
Known Bugs:
Phone is not detected by adb while booted in recovery mode (TWRP). I don't know if that's a bug in TWRP or on my laptop's USB drivers. If the phone has an OS installed (checked on various ROM's) (ie booted in system mode) it is detected, but not when in it is booted in recovery mode and running the latest TWRP. Place the image in an sdcard, put it in the phone and install it from there as a workaround. (Adb sideload can also work.)
Battery consumption appears to have improved on later builds, probably because of this change.
Instructions:
Download and install the latest twrp - dl-link (Steps on how to do it not covered here.)
Reboot to recovery
Wipe Data+Cache+Dalvik+System
Install ZIP file.
Reboot
Downloads:
Latest Build: lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip - lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip.md5sum
20190319 Build: lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Notes:
Many thanks to Stricted for pointing me out to the patch needed to fix a phone reboot whenever the phone connected to Wi-Fi
This is an amateur hobby project. I recommend against using this image as a daily driver, and I am quite likely to be unable to help you with any problems you experience (because I don't know enough about building a ROM).
Source Code:
Complete instructions on how to build this image on your own here !
Team Exynos7580 sources
LineageOS4microG CI/CD docker image code
FAQ:
Q: What is microG?
A: The projects webpage will do a better job than me.
TLDR version: A free software implementation of some proprietary Google Play services API's.
XDA:DevDB Information
LineageOS4microG, ROM for the Samsung Galaxy S5 Neo
Contributors
Iolaum, Stricted
Source Code: https://github.com/Iolaum/s5neoltexx-lineageos-microg
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Testing
Created 2018-11-18
Last Updated 2018-11-19

It seems interesting the ROM who has installed the details please as it runs the ROM

Rovar22 said:
It seems interesting the ROM who has installed the details please as it runs the ROM
Click to expand...
Click to collapse
Hello, I am not sure what you ask. Can you please elaborate?

Iolaum said:
Hello, I am not sure what you ask. Can you please elaborate?
Click to expand...
Click to collapse
Hey there, I'm guessing that he wants a log of someone who has already installed the system, to find out whether he wants to install it or not.
I'm going to flash it today and maybe post a log from a clean install, if it is helpful to anyone.
Btw thank you lolalum for the build and the instructions!
It's awesome that there's still someone left, who's trying to save us from google

Thank you for your answers, the installation is very good, what I need is the installation of "play store". Thanks for the Rom.

Sure, no problem.
Ok, now I understand: I guess you didn't know that you can't install the Playstore with microG.
The reason is, that it has been replaced by the "Fakestore" (you can find it in Settings>Apps*show system processes) It is just a fake or a placeholder to make apps "think" there is an official Playstore, when there really isn't one. So even if you tried to install it, (through Xda Labs for example) it would only be seen as an update of the Fakestore, and wouldn't work.
You can still get every app in the Playstore though, with "Aurora Store" or "Yalp Store". They both allow you to log in to your Google account and to buy apps and items. If that isn't needed "apkmirror.com" works as well.

Thank you

Rovar22 said:
Thank you
Click to expand...
Click to collapse
Glad I could help, but there is a "thank you button" for this

I've been using this rom for the past 2 days, and it worked ok, but I had issues with some calls with root and vibration settings and pretty much every time I tried to reboot to recovery the phone didn't respond at all until I removed the battery. (going to switch over to AospExtended rom now, because it supports microg as well.)

New build
New Build:
lineage-15.1-20190204-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190204-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Added custom microG apks built with PRs that allow to pass SafetyNet check.
Added Gsam Battery monitor and Matlog libre as system apps. They require permissions that need to be given by adb or root, it's easier to use their functionality if they are built in.

New Build:
lineage-15.1-20190214-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190214-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Updated microg apk from Nanodroid. (If Nandodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuilt so soon to include the lastest 5 Feb 2019 security update that patches a critical security vulnerability in Framework that could allow a remote attacker using a specially crafted PNG file to execute arbitrary code within the context of a privileged process.

New build
New Build:
lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip - lineage-15.1-20190319-CUSTOM_LINEAGE_MICROG-s5neoltexx.zip.md5sum
Changelog:
Updated microg gmscore apk from Nanodroid. (If Nanodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuild includes android security patch level march 2019. (Vendor security patch level is still March 2017 as in all earlier builds.
I installed this ROM on top of the previous one with no problems. Process is:
Reboot into recovery
Wipe Cache, Dalvik/ART Cache and System
Install new system image (zip file) and reboot.

New build features
New Build
lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip - lineage-15.1-20190519-CUSTOM_LINEAGE_MICROG-s5neolte.zip.md5sum
Changelog:
Moved to new Team Exynos7580 sources.
Updated microg gmscore apk from Nanodroid. (If Nanodroid releases newer versions before I release a new image you can download them from his repository and install them since I am using the pre-built apks signed by him instead of building them from source.)
Rebuild includes android security patch level May 2019. (Vendor security patch level is still March 2017 as in all earlier builds.
Replaced android's chromium system webview with the bromite system webview. Bromite is Chromium plus ad blocking and privacy enhancements.
Installation Instructions:
Because this build is built from a slightly different source than the previous ones and the default system webview was changed, I suggest a clean install wiping data, cache, dalvik and system.
Known Issues
- Nanolx and Bromite repositories are not added in Fdroid repositories by default as intended. They need to be added manually after installation. After you do so, ignoring updates for the Play store package is recommended if you don't plan to use it. The fakestore package included by default is only intended to be there for apps that want it to be there in order to function. Nanolx's playstore app allows in-app purchaces and other functionality which may or may not work properly - I 've never tested it not intend to do so.
Source code if you want to build it yourselves.

[CLOSED][ROM][Unofficial][10.0][microG][signed]hardened LineageOS 17.1 Oneplus 3/3T

This thread is deprecated - please refer to its LineageOS 18.1 successor thread
This thread is dedicated to provide hardened Lineage-OS 17.1 builds with microG included for the OnePlus 3/3T with current security patches.
It is the successor of my Lineage 16.0 thread.
It may be worth to also look there, if you are looking for information.
Features of this ROM
Download here
Pre-installed microG and F-Droid like LineageOS for microG project (own fork)
Pre-installed AuroraStore
OTA Support
eSpeakTTS engine
Bromite 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
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Kernel kept up to date with ASB patches and Google kernel/common 'android-3.18' branch
Debloated from Oneplus blobs for Alipay, WeChatpay, Soter and IFAA
Hardened bionic lib and constified JNI method tables
Current release levels
Security string: 2021-10-05
AOSP tag: 10.0.0_r41
Bromite System Webview: M93
Source-code and build instructions
Kernel: https://github.com/lin17-microg/android_kernel_oneplus_msm8996/tree/lin-17.1-mse3
Build manifest: https://github.com/lin17-microg/local_manifests/tree/lin-17.1-microG
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 17.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 16.0 build - or any Android 9 or 10 based ROM, you most probably have already the proper firmware.
And yes, LineageOS 17.1 is Android 10, 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!
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 16.0 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 17.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.
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)

Change log
2021-10-14 - FINAL
ASB Security string 2021-10-05
Bromite System Webview and Browser updated to 93.0.4577.83
Kernel upstreamed (note: tag equals last months tag)
2021-09-12
ASB Security string 2021-09-05
Kernel upstreamed to tag ASB-2021-09-05_3.18
microG microG 0.2.22.212658-2
2021-08-08
ASB Security string 2021-08-05
Kernel upstreamed to tag ASB-2021-08-05_3.18
Bromite System Webview and Browser updated to 92.0.4515.134
F-Droid updated to 1.13
Fix in WiFi randomization
2021-07-10
ASB Security string 2021-07-05
Kernel upstreamed to tag ASB-2021-07-05_3.18
Bromite System Webview and Browser updated to 91.0.4472.146
microG 0.2.21.212158-2
AuroraStore 4.0.7
2021-06-13
ASB Security string 2021-06-05
Kernel upstreamed to tag ASB-2021-06-05_3.18
Kernel WLAN driver (qcacld-2.0) patched to include mitigations against "Frag" vuln.
Bromite System Webview and Browser updated to 91.0.4472.102
microG 0.2.19211515-9
2021-05-09
ASB Security string 2021-05-01
Kernel upstreamed to tag ASB-2021-05-05_3.18
Bromite System Webview and Browser updated to 90.0.4430.204
microG upstreamed (no version change)
Update: AuroraServices 1.1.1
2021-04-10
ASB Security string 2021-04-01
Kernel upstreamed to tag ASB-2021-04-05_3.18
Bromite System Webview and Browser updated to 90.0.4430.59
F-Droid updated to 1.12
Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
2021-03-08
Security string 2021-03-05
Kernel upstreamed to tag ASB-2021-03-05_3.18
Bromite System webview updated to 88.0.4324.207
Bromite Browser updated to 88.0.4324.207
F-Droid 1.11
microG 0.2.18.204714
2021-02-04
Security string 2021-02-05
Kernel upstreamed to tag ASB-2021-02-05_3.18
Bromite System webview updated to 88.0.4324.141
Bromite Browser updated to 88.0.4324.141
F-Droid 1.10-alpha-234
microG 0.2.17.204714-5
2021-01-15 - Initial build
Pre-installed microG (0.2.16.204713-10) and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Bromite as default browser (87.0.4280.106)
eSpeak TTS engine (FOSS TTS solution)
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 (87.0.4280.131)
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Constified JNI method tables and hardened bionic lib

Security Hardening Features - Details
1. Pre-installed microG and F-Droid
same as the LineageOS for microG project
2. Pre-installed AuroraStore
works w/o having to enable the "unknown sources feature"
3. Extra control of sensor access for additionally installed user apps
Special access under app permissions
4. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
5. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 17.1 (all settings can be changed at any time later):
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sensitive information is hidden on the lock screen
Camera app: Location tagging disabled by default
Further, when a lock screen protection is set (PIN, pattern, password), the Nfc, Hotspot and airplane mode tiles require authentication and cannot be set without
6. Optional blocking of Facebook- and Google-Tracking
Settings => Network & Internet (scroll down)
When activated, all outgoing connection attempts to Facebook servers will be suppressed.
Same applies to Google, but certain apps on an internal exception list will still be able to connect (AuroraStore, microG, or e.g. NewPipe, if installed)
7. Optional disable captive portal detection and to select Captive portal server URL provider
Settings => Network & Internet (scroll down)
When deactivated, the system will not ping a specific Google server any longer when establishing a WiFi connection to determine, whether a captive portal is being used. Further, the captive portal URL provider can be set (default is GrapheneOS and not Google; Settings - Network & Internet)
8. No submission of IMSI or phone number to Google when GPS is in use
GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties ) to provide this data . . .
9. Default hosts file with many blocked ad/tracking sites
The system's hosts file redirects a comprehensive list of URLs known to be adware, tracking, etc. to 127.0.0.1 (ipv4) and ::1 (ipv6)
10. Privacy-enhanced Bromite SystemWebView
Instead of the default Chromium System Webview component, the Bromite SystemWebView is used offering more privacy, more ad blocking and less Google tracking.
11. Bromite as shipped Browser
A chromium based browser with many privacy features.
12. Firewall UI
Settings => Privacy - Firewall
Lists all apps and allows to restrict Internet access per app in regards to WiFi, mobile network or VPN
This per-app feature is a standard feature in LineageOS, but the UI to show all apps is an Extra (taken from a topic in LineageOS's Gerrit - it may, or may not, become part of the official LineageOS one day)
13. Maximum password length increased to 64

Thanks a lot!! Will flash and report tomorrow!!

Hello!
Does this ROM allow to lock a bootloader?

Clean flashed this morning. So far so good!

zhenev said:
Hello!
Does this ROM allow to lock a bootloader?
Click to expand...
Click to collapse
I would like to refer you to the below post from the 16.0 predecessor thread:
[CLOSED] EOL [ROM][Unofficial][9.0.0][microG][signed]hardened LineageOS 16.0 for Oneplus 3/3T
Thread is discontinued: Please visit the my LineageOS 17.1 successor thread This thread is dedicated to provide hardened Lineage-OS 16.0 builds with microG included for the OnePlus 3/3T with current security patches. It is the successor of my...
forum.xda-developers.com

Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.

WM-Sef said:
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
Click to expand...
Click to collapse
What phone and firmware? Works like a charm for me on OP3 and OOS 9.0.6 firmware.

WM-Sef said:
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
Click to expand...
Click to collapse
USB works fine on my own device. As suggested by @Anghirrim - what firmware are you on?

MSe1969 said:
USB works fine on my own device. As suggested by @Anghirrim - what firmware are you on?
Click to expand...
Click to collapse
How do I check for the firmware version? It's not under Settings -> Build Number, only the Android Version.
Solved the problem by switching the default USB action to 'MTP'. After that, it suddenly started working.
Still no clue about the Termux issue.

WM-Sef said:
How do I check for the firmware version? It's not under Settings -> Build Number, only the Android Version.
Click to expand...
Click to collapse
The OP of this OP3(T) firmware thread indicates to look at the file /system/vendor/firmware_mnt/verinfo/ver_info.txt

WM-Sef said:
Still no clue about the Termux issue.
Click to expand...
Click to collapse
Their docu indicates issues with Android 10.

WM-Sef said:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
Click to expand...
Click to collapse
I had the same issue but just enabling USB-Debugging from the developer options fixed it. I was a bit surprised too and that shouldn't be normal I guess.

SenseSei said:
I had the same issue but just enabling USB-Debugging from the developer options fixed it. I was a bit surprised too and that shouldn't be normal I guess.
Click to expand...
Click to collapse
As indicated before, I do not experience such an issue with my own device, so I can't reproduce this issue.

This is actually fascinating, thank you!

How is the exact steps to install? I'm coming from another rom.. Please help.
1) Advanced Wipe >> flash fw >> flash rom
or
2) Flash fw >> Advanced wipe >> flash rom
Confused after see this thread and fw installation's thread linked above.

vkey.ptr said:
How is the exact steps to install? I'm coming from another rom.. Please help.
1) Advanced Wipe >> flash fw >> flash rom
or
2) Flash fw >> Advanced wipe >> flash rom
Confused after see this thread and fw installation's thread linked above.
Click to expand...
Click to collapse
The above order does not matter, as the firmware is flashed to different partitions than those to be wiped.
EDIT:
If you have already 9.0.6 firmware, there is no need to flash it again.

this is just what I need for my old OP3. Running a degoogled 6T as daily and still need occasional apps that do not work w/o google. flashing without hesitation and reporting back.
EDIT: a question. can I flash twrp right back after flashing the rom? I know im giving up over the air updates, but im fine with that.

I am on LineageOS 17.1 for microG, unlocked bootloader, rooted with Magisk, 9.0.6 official firmware, but I would love to try this ROM.
Few questions, please:
- can I install modded firmware, because this sounds good: "The modem firmware contains some alipay* and soter* files used for Alipay and WeChatpay. Since these are suspect to be a privacy hazard, I've modified NON-HALOS.bin to not contain any of these files any more"
- this ROM can be rooted with Magisk 20.4 or newer?
- do I have to do "clean install", and finally
- is wiping internal sd card (pics, videos etc.) obligatory?
Thanks in advance

[ROM][Unofficial][11.0][microG][signed]hardened LineageOS 18.1 Oneplus 3/3T

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.

General GSI thread - April 12, 2023 UPB1.230309.014 available for the Pixel 7 Pro [Cheetah]- Android 14 GSI binaries and release notes

GSIs​
I won't be using these, either, but feel free to use this thread for everything GSI related for the Pixel 7 Pro. I'll update the information in the OP when necessary. See Post #2 in my main thread for general information (Unlocking Bootloader / Rooting / Updating | SafetyNet working again | ADB/Fastboot & Windows USB Drivers) but ask questions or make observations about all GSI-related items in this thread, please.
April 12, 2023:
Generic System Image releases | Platform | Android Developers
developer.android.com
Android 14 GSIs (Preview)​
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-UPB1.230309.014-9890577-febd421e.zipfebd421e2fa182fa7a3e30ff64417f0da342b825535fc0eef90028679f72380fARM64aosp_arm64-exp-UPB1.230309.014-9890577-2c116021.zip2c11602154a507b8bd50d0e8a0e3b631ef24e1af70e1bc5e6932700f649cf95ax86_64+GMSgsi_gms_x86_64-exp-UPB1.230309.014-9890577-0aef912d.zip0aef912d0bbab412fe4bc6d7fc9408579197af936ee84d17be10eb1117edae76x86_64aosp_x86_64-exp-UPB1.230309.014-9890577-d25c18bc.zipd25c18bc77d5ff6eea176c399fc6411c66d20a5a796cb691929c1012298e82e8
Known issues with Android 14 GSIs​Android 14 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.

Spoiler: Old News/Releases
March 15, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR3 as well as discover and report OS and framework issues until Android 13 QPR3 is officially released.
GSI binaries for Android 13 QPR3 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: March 15, 2023
Build: T3B1.230224.005
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T3B1.230224.005-9723149-85eb7259.zip85eb725917e4b05e7e66c0898e94fd78e5f4ce1b530d09b10627e67c2c4bf190ARM64aosp_arm64-exp-T3B1.230224.005-9723149-6f182cba.zip6f182cbad4fc1c9c92e01538346c16771da641caa7499efc92b5b9b2d02f00c0x86_64+GMSgsi_gms_x86_64-exp-T3B1.230224.005-9723149-1773dc5c.zip1773dc5c80bee4b127e9fd491a7215dfebeedea9f2de7e5ff4b00b6b38791d2ex86_64aosp_x86_64-exp-T3B1.230224.005-9723149-78e6bc0f.zip78e6bc0f94b8fd33c77701948098b3732af6618f24ddf68f379ac4945e7d3549
February 1, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR2 as well as discover and report OS and framework issues until Android 13 QPR2 is officially released.
GSI binaries for Android 13 QPR2 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: February 1, 2023
Build: T2B3.230109.002
Build type: experimental
Security patch level: January 2023
Google Play Services: 22.46.17
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T2B3.230109.002-9523436-539488e0.zip539488e0638b879b9212567d57049c8178d173f8d0b90ce627fbb763ddbc1fd6ARM64aosp_arm64-exp-T2B3.230109.002-9523436-98a648ca.zip98a648ca2edb2ac1719998eab31e0de4901ab6ef974ab91257f3e25f36c2317ax86_64+GMSgsi_gms_x86_64-exp-T2B3.230109.002-9523436-cd37ecd0.zipcd37ecd060add9d1d5aca20fcea7af5ad9776dbd81a464933efa3d4d9e3b4525x86_64aosp_x86_64-exp-T2B3.230109.002-9523436-22691864.zip22691864640bcfa2b215c6548df45e37ba49a8898923d412ca5d29471a6a0313
October 20, 2022:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Downloads​Date: October 20, 2022
Build: T1B3.221003.003
Build type: experimental
Security patch level: October 2022
Google Play Services: 22.33.16
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T1B3.221003.003-9173718-1aa73579.zip1aa735796e13eae7d49e622345fc1dd35cb4a1ea2edb569e627a8b6e7c4dd8b6ARM64aosp_arm64-exp-T1B3.221003.003-9173718-7eba5aba.zip7eba5abadf9c09aa56a907e121030828d9239e2f4441fc231188a9fae274701bx86_64+GMSgsi_gms_x86_64-exp-T1B3.221003.003-9173718-990f7aa5.zip990f7aa5f83c7ba607749646dbec2b7075ce9cf8f43d1c2ab0dd79d45444542ax86_64aosp_x86_64-exp-T1B3.221003.003-9173718-c631df22.zipc631df2236c6f95cc862ab41f6b98870f0917e6cd1cc8c1dcd83d9d5f3262036

Reserved #3

Reserved #4

Reserved #5

Reserved #6

Reserved #7

Great stuff as always
Thanks

this google gsi is android 13 qpr1 or stable?

victortitan said:
this google gsi is android 13 qpr1 or stable?
Click to expand...
Click to collapse
I have no idea if it's either, or if it would be considered its own thing:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Date: October 20, 2022
Build: T1B3.221003.003
Build type: experimental
Security patch level: October 2022
Google Play Services: 22.33.16
Click to expand...
Click to collapse
I would expect that it's an "Experimental" GSI build of Stable, since the page makes no mention of QPR.

roirraW edor ehT said:
I have no idea if it's either, or if it would be considered its own thing:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
I would expect that it's an "Experimental" GSI build of Stable, since the page makes no mention of QPR.
Click to expand...
Click to collapse
{
"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"
}
thank you, i will try

victortitan said:
View attachment 5742581
thank you, i will try
Click to expand...
Click to collapse
Good eye. My mistake. I would've expected it to say down in the Build information.

GSIs
February 1, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​bookmark_border
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR2 as well as discover and report OS and framework issues until Android 13 QPR2 is officially released.
GSI binaries for Android 13 QPR2 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: February 1, 2023
Build: T2B3.230109.002
Build type: experimental
Security patch level: January 2023
Google Play Services: 22.46.17
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T2B3.230109.002-9523436-539488e0.zip539488e0638b879b9212567d57049c8178d173f8d0b90ce627fbb763ddbc1fd6ARM64aosp_arm64-exp-T2B3.230109.002-9523436-98a648ca.zip98a648ca2edb2ac1719998eab31e0de4901ab6ef974ab91257f3e25f36c2317ax86_64+GMSgsi_gms_x86_64-exp-T2B3.230109.002-9523436-cd37ecd0.zipcd37ecd060add9d1d5aca20fcea7af5ad9776dbd81a464933efa3d4d9e3b4525x86_64aosp_x86_64-exp-T2B3.230109.002-9523436-22691864.zip22691864640bcfa2b215c6548df45e37ba49a8898923d412ca5d29471a6a0313

March 15, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR3 as well as discover and report OS and framework issues until Android 13 QPR3 is officially released.
GSI binaries for Android 13 QPR3 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: March 15, 2023
Build: T3B1.230224.005
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T3B1.230224.005-9723149-85eb7259.zip85eb725917e4b05e7e66c0898e94fd78e5f4ce1b530d09b10627e67c2c4bf190ARM64aosp_arm64-exp-T3B1.230224.005-9723149-6f182cba.zip6f182cbad4fc1c9c92e01538346c16771da641caa7499efc92b5b9b2d02f00c0x86_64+GMSgsi_gms_x86_64-exp-T3B1.230224.005-9723149-1773dc5c.zip1773dc5c80bee4b127e9fd491a7215dfebeedea9f2de7e5ff4b00b6b38791d2ex86_64aosp_x86_64-exp-T3B1.230224.005-9723149-78e6bc0f.zip78e6bc0f94b8fd33c77701948098b3732af6618f24ddf68f379ac4945e7d3549

March 29, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​bookmark_border
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR3 as well as discover and report OS and framework issues until Android 13 QPR3 is officially released.
GSI binaries for Android 13 QPR3 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: March 29, 2023
Build: T3B2.230316.003
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T3B2.230316.003-9794841-bf9fb488.zipbf9fb488bcdabcb4dbf4cf381ddd28858af96ab50ad6c53298c55cbe25835dbbARM64aosp_arm64-exp-T3B2.230316.003-9794841-5c9b2ecf.zip5c9b2ecf5dea44680b442ead3a14f97b7ddb5d3893bfc7e018ce701bb3736168x86_64+GMSgsi_gms_x86_64-exp-T3B2.230316.003-9794841-77ebefd1.zip77ebefd182f985bfb0e85359eba2b088f480f9a149a21ac20ef338f53f44ef63x86_64aosp_x86_64-exp-T3B2.230316.003-9794841-5d809315.zip5d809315ebf1015733cdcb93aad058f1d130be48e9dbcb0cc8bb1c6b9456b116

Generic System Image releases | Platform | Android Developers
developer.android.com
Android 14 GSIs (Preview)​
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-UPB1.230309.014-9890577-febd421e.zipfebd421e2fa182fa7a3e30ff64417f0da342b825535fc0eef90028679f72380fARM64aosp_arm64-exp-UPB1.230309.014-9890577-2c116021.zip2c11602154a507b8bd50d0e8a0e3b631ef24e1af70e1bc5e6932700f649cf95ax86_64+GMSgsi_gms_x86_64-exp-UPB1.230309.014-9890577-0aef912d.zip0aef912d0bbab412fe4bc6d7fc9408579197af936ee84d17be10eb1117edae76x86_64aosp_x86_64-exp-UPB1.230309.014-9890577-d25c18bc.zipd25c18bc77d5ff6eea176c399fc6411c66d20a5a796cb691929c1012298e82e8
Known issues with Android 14 GSIs​Android 14 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.