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

[ROM][LineageOS 14.1][substratum] for Moto G [falcon]

Search This thread

zuaumlinds

Member
Apr 15, 2017
7
1
Did I do something wrong? After install the ROM and gApps, i got stuck in 'checking for updates' after the restart. Is there something that I can do to by pass it?
 

Guttergorm

Member
Jun 9, 2016
39
5
I've got a question while preparing good old Moto G for my son with this superb ROM.
I gave encryption a try, but I am not able to mount data partition in latest TWRP. Does it work if I use a password before encryption instead of a PIN? I slightly remember that this procedure was a workaround for TWRP not 'knowing about the encryption key'. Or do I have to use a different TWRP version (currently 3.5.0_9 from twrp.me)?
 

Tiki Thorsen

Senior Member
Jan 27, 2017
219
44
38
Argentina
Moto G
Moto G 2015
I've got a question while preparing good old Moto G for my son with this superb ROM.
I gave encryption a try, but I am not able to mount data partition in latest TWRP. Does it work if I use a password before encryption instead of a PIN? I slightly remember that this procedure was a workaround for TWRP not 'knowing about the encryption key'. Or do I have to use a different TWRP version (currently 3.5.0_9 from twrp.me)?
MSe1969 recommends using this version of TWRP to avoid issues.
 
Next build...
This month, I have been somewhat quite busy work-wise, so I think I will only be able to take care about next builds towards the weekend.

Update: Sorry, work has taken up all my time and energy. I think I'll skip October and deliver November (incl. October) on time
 
Last edited:

Scranalot

Senior Member
Mar 28, 2019
70
40
Next build...
This month, I have been somewhat quite busy work-wise, so I think I will only be able to take care about next builds towards the weekend.

Update: Sorry, work has taken up all my time and energy. I think I'll skip October and deliver November (incl. October) on time
Good Afternoon
No need to apologise on my account @MSe1969 anything you do to keep these venerable old devices 'up to snuff' is very much appreciated by myself & doubtless everyone else here in this thread :)

Anyway I must continue with somewhat of a tale of woe - I had been having the not uncommon issue with the 'Hotspot' access point with my XT1033 whereby sometimes the connection would drop out or the phone would unilaterally reboot.

This appeared to happen after about an hour or two in use resulting in afwall+ repeatedly try to reset itself. Getting it back to 'normal' would involve turning 'Hotspot' off in the settings - this would allow afwall+ to settle down to normal operation.

I have no special rule set scripts for afwall+ - just make my requisite selections through the standard interface. Obviously the phone is rooted, with just the official lineage addonsu, for afwall+, which is the only app granted root access through the developer options.

Although these drop outs were an inconvenience, I just regarded it as that & nothing more, however I've now got a big problem. Yesterday I was using the phone as a Hotspot when it rebooted - but when it did so it remained stuck at the boot screen. I left it for about 15 mins then tried to reboot it & went straight to the boot screen again.

I cannot access this phone via adb from the computer as adb is not enabled in the developer options on the phone, but I can boot into TWRP recovery via the power + vol buttons.


In TWRP on the log screen it states:

Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/system' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present
E:TWFunc::Copy_Log -- Can't open destination log
file: 'cache/recovery/log'
E:failed to write /dev/block/mmcblk0p30: I/O error
Unable to mount /data/media/TWRP/.twrps
Error opening '/cache/recovery/.version' (Read-
only file system)
MTP Enabled
Failed to mount '/data' (I/O error)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/system' (Invalid argument)


I cannot repair partitions or reinstall ROM & most directories (apart from /sys, /proc & /cache) appear to be empty! (maybe because they are unmounted?)


I have accessed the file system in TWRP. Using the Busybox terminal I did a list out of the /cache directory:

Code:
/cache # ls -lah
ls: ./lost+found: I/O error
ls: ./backup_stage: I/O error
ls: ./backup: I/O error
ls: ./trace: I/O error
__bionic_open_tzdata: couldn't find any tzdata when looking
for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking
for posixrules!
drwxrwx---   7 system  cache       4.0k Apr 13 15:37
.
drwxr-xr-x  23 root    root          0 Apr 29 22.03
..
-rwx------   1 root    cache      3.0M Oct 24  2021
pds-dump.img
drwxrwx---   2 system  cache       4.0k Oct 15  2021
recovery

Note: There is nothing in the /cache/recovery directory


has anyone got any suggestions?
Cheers
 
  • Like
Reactions: phoenixmet

Scranalot

Senior Member
Mar 28, 2019
70
40
Good Evening

Further to my earlier post above #788. I have bitten the bullet so to speak & decided to format Data:

Code:
Formatting Data using mkfs.f2fs...
Done.
Failed to mount '/data' (I/O error)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use
/data again
Updating partition details...
Failed to mount '/data' (I/O error)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/system' (Invalid argument)
...done
Unable to mount storage


Upon rebooting the same failure to mount partitions, including /data still prevails - plus I don't really know if indeed the formatting has occured.
I've also done a Factory Reset - again it is stated:

Code:
Formatting Cache using make_ext4fs...
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (I/O error)
Updating partition details...
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (I/O error)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/system' (Invalid argument)
...done
Unable to mount storage


So again I suspect nothing has happened

I have found that I can access the phone with Fastboot via USB from my computer so I could restore stock image
 
New builds available

Hi all,
new builds with back-ported November and October ASB patches is available for download and via the Updater app.

A comment on the security-string:
Up to now, I have usually picked the ASB topics from the LineageOS Gerrit, when the test feedbacks and my own testing looked good, before the topic got officially merged. As a matter of fact (but no complaints), the merge has often happened late on the LineageOS side, but the topics were always merged as uploaded.
However, CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing! That is, why the security string has not been merged from July onwards in the official LineageOS repositories, because of those missing CVEs.
Therefore, I have decided to show again the "official" LineageOS security string 2021-06-05 and show in addition a "Custom build release" to indicate the status of ASB backports - as usual, on a "best effort basis".

A. Default LineageOS 14.1 with substratum and microG patch
  • November 2021 custom build release
  • System Webview 95.0.4638.50
B. Hardened build with pre-installed microG and F-Droid, patched for substratum
  • November 2021 custom build release
  • Bromite Webview 94.0.4606.109
Happy flashing
Regards, M.
 
Well that's jolly interesting. I've faithfully installed your updates up to now and they've all worked just fine, no problems, thank you very much. However, the latest, lineage-14.1-20211108-UNOFFICIAL-oms-falcon.zip, for some reason, upset Signal and the NHS app. Signal kept crashing, I assume it was trying to phone home, and the NHS app just once. I tried running Signal and it crashed immediately, the NHS app seemed to run OK. I have reverted to the previous release, lineage-14.1-20210917-UNOFFICIAL-oms-falcon.zip, and everything is just fine again. I don't know if a crash dump from Signal would be very useful, I could try it again and get one, but I'm quite happy as it is, I'm planning on replacing the phone soon anyway.
 
Well that's jolly interesting. I've faithfully installed your updates up to now and they've all worked just fine, no problems, thank you very much. However, the latest, lineage-14.1-20211108-UNOFFICIAL-oms-falcon.zip, for some reason, upset Signal and the NHS app. Signal kept crashing, I assume it was trying to phone home, and the NHS app just once. I tried running Signal and it crashed immediately, the NHS app seemed to run OK. I have reverted to the previous release, lineage-14.1-20210917-UNOFFICIAL-oms-falcon.zip, and everything is just fine again. I don't know if a crash dump from Signal would be very useful, I could try it again and get one, but I'm quite happy as it is, I'm planning on replacing the phone soon anyway.
Thanks for the hint - I'll try to install Signal and see, whether I can reproduce the issue.
 

phoenixmet

Member
Jun 26, 2011
18
4
38
Caracas
I have a similar error but with a google play mod , in the previous compilation I did not get to pass :(
 
Last edited:

Xazu

New member
May 1, 2021
3
1
New builds available

Hi all,
new builds with back-ported November and October ASB patches is available for download and via the Updater app.

A comment on the security-string:
Up to now, I have usually picked the ASB topics from the LineageOS Gerrit, when the test feedbacks and my own testing looked good, before the topic got officially merged. As a matter of fact (but no complaints), the merge has often happened late on the LineageOS side, but the topics were always merged as uploaded.
However, CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing! That is, why the security string has not been merged from July onwards in the official LineageOS repositories, because of those missing CVEs.
Therefore, I have decided to show again the "official" LineageOS security string 2021-06-05 and show in addition a "Custom build release" to indicate the status of ASB backports - as usual, on a "best effort basis".

A. Default LineageOS 14.1 with substratum and microG patch
  • November 2021 custom build release
  • System Webview 95.0.4638.50
B. Hardened build with pre-installed microG and F-Droid, patched for substratum
  • November 2021 custom build release
  • Bromite Webview 94.0.4606.109
Happy flashing
Regards, M.
I want to thank you deeply for your work. It's really important to me and to my family
 

Bludwurst

Senior Member
Mar 26, 2016
536
472
Moto G
Redmi 9A
Thank you for your work.
I'll report that ProtonVPN crashes and won't run since updating to latest hardebed build; clearing the app's data solved it.

Again, thank you.
 

peelie

Senior Member
Nov 8, 2010
127
39
hi i am getting fails on Signal and French Covid app

edit/ clearing all data for apps solves problem
 
Last edited:
  • Like
Reactions: MSe1969
hi i am getting fails on Signal and French Covid app

edit/ clearing all data for apps solves problem
Thanks for the update - I have installed Signal on my peregrine (same device family, same kernel and only diff is LTE module) and experienced no issue. What I got from last posts is that clearing app cache or data solved issues.
No idea, what was causing this - to all:
Are there still apps with issues?
 
  • Like
Reactions: phoenixmet

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    New builds available

    Hi all,
    new builds with back-ported November and October ASB patches is available for download and via the Updater app.

    A comment on the security-string:
    Up to now, I have usually picked the ASB topics from the LineageOS Gerrit, when the test feedbacks and my own testing looked good, before the topic got officially merged. As a matter of fact (but no complaints), the merge has often happened late on the LineageOS side, but the topics were always merged as uploaded.
    However, CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing! That is, why the security string has not been merged from July onwards in the official LineageOS repositories, because of those missing CVEs.
    Therefore, I have decided to show again the "official" LineageOS security string 2021-06-05 and show in addition a "Custom build release" to indicate the status of ASB backports - as usual, on a "best effort basis".

    A. Default LineageOS 14.1 with substratum and microG patch
    • November 2021 custom build release
    • System Webview 95.0.4638.50
    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    • November 2021 custom build release
    • Bromite Webview 94.0.4606.109
    Happy flashing
    Regards, M.
    1
    hi i am getting fails on Signal and French Covid app

    edit/ clearing all data for apps solves problem
    1
    hi i am getting fails on Signal and French Covid app

    edit/ clearing all data for apps solves problem
    Thanks for the update - I have installed Signal on my peregrine (same device family, same kernel and only diff is LTE module) and experienced no issue. What I got from last posts is that clearing app cache or data solved issues.
    No idea, what was causing this - to all:
    Are there still apps with issues?
    1
    Thanks for the update - I have installed Signal on my peregrine (same device family, same kernel and only diff is LTE module) and experienced no issue. What I got from last posts is that clearing app cache or data solved issues.
    No idea, what was causing this - to all:
    Are there still apps with issues?
    if a clean installation is done there is no failure but if an update is performed from another compilation some applications fail until the cache or data of the applications is cleared
    1

    Hardware AEC (Acoustic Echo Cancellation) doesn't work​

    The other side hears an echo when talking on the speakerphone and quiet echo in a normal conversation. Hands-free echo makes video calls impossible with apps, that uses hardware AEC. Use Conversations and call a friend with videocall - loud speaker + mic, they hear themselves. Same with audio call in Conversations and Speaker mode. Same with Jitsi Meet

    Possible Solution​

    Adapted from https://gitlab.com/LineageOS/issues/android/-/issues/2194#note_739468172

    On Moto G4 (athene), running Lineage OS 14.1 (Android 7.1.2 Nougat), Acoustic Echo Cancellation (AEC) was fixed by editing /system/build.prop, set persist.audio.fluence.voicecall=false and ro.qc.sdk.audio.fluencetype=fluence. Other true/flase combinations involving persist.audio.fluence.speaker and persist.audio.fluence.voicecall did not work for me.

    On phone/device settings, developer options, enable USB debugging and ADB root access. Then connect phone to a pc host with ADB installed, and in terminal type:
    adb root && adb remount
    When prompted on the device to select "Always allow".
    adb shell nano /system/build.prop
    Change the following values to shown here:
    persist.audio.fluence.voicecall=false
    If fluence.voicecall is true , change it to false.
    ro.qc.sdk.audio.fluencetype=fluence
    If audio.fluencetype is none, change it to fluence.

    In nano, hit CTRL-X and then Y to save your changes.

    Peelie, if this problem persists in your next Moto G4 ROM update, please pull/merge/test this solution.
  • 57
    Hi,

    this is my unofficial LineageOS 14.1 build for the Moto G (falcon) device with current security patches, microG patch and substratum support.
    (This thread is for the falcon device, I have also a thread for preregrine using the same sources)

    As announced here, LineageOS has discontinued to deliver official 14.1 builds in the course of providing LineageOS 16.0 builds, but the 14.1 tree will continue to be maintained for security patches by the community (I am one of these contibutors, btw). So this build will continue.

    The build has got the following features:
    • LineageOS 14.1 with current security patches (from official LineageOS repositories)
    • Security string 2021-06-05, AOSP tag 7.2.1_r36
    • Additional custom build release November 2021 (to indicate ASB backport status)
    • Adapted LineageOS Jelly Browser (additionally having Startpage and Qwant as search engines)
    • Root is not included and would need to be flashed separately
    • Patched for the use of the substratum theme engine (the substratum app and the themes need to be downloaded separately)
    • System certificates taken from AOSP Oreo branch
    • Kernel forked from LineageOS and updated with many security patches
    • OTA Support
    • Enforcing SELinux

    There are two build variants available:

    A. Default LineageOS 14.1 with substratum and microG patch
    • Patched for the use of microG - you can either flash Gapps or manually install microG as apps (or use neither of those)
    • Android System Webview M95
    Download here

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    For the security/privacy focused. It has to be said that microG seems to run better if it is pre-installed.
    • Pre-installed microG same as the LineageOS for microG project
    • Pre-installed AuroraStore / AuroraServices
    • Additional security hardening features listed below
    • SQLite 'secure delete' feature enabled
    • Access to /proc/net blocked for user apps
    • Bundled netmonitor app to allow network monitoring
    • Enhanced Privacy Guard: Switches for motion sensors and other sensors available
    • Oreo backport: SET_TIME_ZONE permission restricted to system apps
    • Oreo backport: Access to timers in /proc restricted
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • No submission of IMSI/phone number to Google when GPS is in use
    • Bromite System Webview M94
    Download here

    Source Code links
    LineageOS: https://github.com/LineageOS
    Kernel: https://github.com/lin14-mGoms/android_kernel_motorola_msm8226/tree/mse_v1
    microG patches:
    (1) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
    (2) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
    Patches for Substratum: https://github.com/LineageOMS
    local manifest: https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms

    Installation Instructions

    YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
    Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.

    Pre-Requisites
    • Get familiar with the hardware keys of the Motorola Moto G (falcon) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume down key to the reboot recovery option and select with volume up key)
    • Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
    • Download the most current .ZIP file of this ROM and place it to your phone's internal memory
    • An unlocked bootloader (read the warnings carefully and backup your data!
    • Your bootloader must at least be on version 41.18 (find out via fastboot getvar version-bootloader) - if your bootloader is below that version, the ROM will refuse to install. In that case, you need to upgrade the BL first. See e.g. here for more info. (I currently do not find the link, which I have used some years back, but the provided link should be helpful, too)

    Install TWRP recovery
    If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it.
    However - I recommend to use the TWRP recovery. The following instructions are based on TWRP.
    NOTE: There have been reports of encryption issues in this thread, when using TWRP 3.3.x, which disappear, when TWRP 3.2.1 is used - I myself use the TWRP 3.2.1, as higher versions have mainly been developed for higher Android versions. I can't technically confirm or prove the situation, but based on the reports and the fact, that I myself did not encounter ANY issues for my own device with TWRP 3.2.1, I recommend this version
    To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
    Code:
    fastboot flash recovery TWRP.img
    Afterwards, directly boot into 'recovery mode' (see above) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.

    Advanced Wipe
    ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!

    Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped.
    Make sure NOT to wipe "Internal memory" (or "SD Card", if shown). Swipe to confirm the deletion and get back into the main menu.

    GApps (only for build variant A - do not flash on build variant B!)
    You have the choice: a. Use microG - b. Flash GApps - c. Neither of those (obviously, you cannot combine those options!)
    'microG' is installed simply by installing the respective apps, no flashing necessary. If you wish to have GApps, they need to be flashed together with the ROM. Download GApps in that case only from opengapps.org and put the .ZIP also to the Internal memory of your device. Choose ARM as platform, Android 7.1 and the flavor of your choice. I strongly recommend "pico" for two reasons:
    1. The Moto G has not much internal memory (8 or 16GB) and no SD card and GApps are notoriously known to waste a lot of space
    2. It leaves you the most freedom to only install, what you really need; you can later download and still install all the Google products you want from the play store, so you do not need to live with pre-installed Google stuff you have no use for.
    The 'microG patch' in this ROM has no negative impact on installing Gapps.

    Install the ROM
    In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard).
    Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe. If in that case, you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process.
    If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you want to install GApps, flash them directly after the ROM, do not reboot in between. (Note: If you wish to get rid of previously installed GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
    When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 14.1 - be patient, the first boot after flashing a new ROM takes quite long!


    Current / reported issues
    • WiFi hotspot needs to be toggled on/off/on after a reboot to work
    • WiFi hotspot enabled longer than 2 hours may cause a sudden reboot
    • Sometimes (root cause not clear), WiFi switches itself off after a couple of hours (fix by enabling/disabling flight mode)
    • It has been reported by some forum participants, that after messing with some Android-10 test builds for this device, WiFi wouldn't work any more: In this case, the solution can be found here:
      or here (scroll down and use the manual unpack option):

    Why still on Android 7.1 (Nougat) and not a higher Android version (like 10 or 11)?
    The falcon device is low on memory (RAM and storage flash memory), each newer Android release increases the resource demand and thus decreases performance and available memory - so higher versions won't really make sense for this device.
    Further, I haven't seen any ROM for this device on a higher Android version than Nougat with enforcing SELinux (yes, coming there indeed is "slave work"; none of the devs, including me for above stated reasons, is willing to invest this time...) - which is a No-Go for any daily-driver use (in that case, your device simply is fully open many vulnerabilities and applying monthly ASB patches on a permissive SELinux is close to a complete waste of time).


    Credits
    Android Open Source project (AOSP)
    LineageOS project
    microG project
    Substratum team
    SkewedZeppelin (Kernel patches)


    XDA:DevDB Information
    [ROM][LineageOS 14.1][substratum] for Moto G [falcon], ROM for the Moto G

    Contributors
    MSe1969
    Source Code: https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    Based On: LineageOS 14.1

    Version Information
    Status:
    Stable
    Current Stable Version: cm-14.1
    Stable Release Date: 2021-11-09

    Created 2018-06-24
    Last Updated 2021-11-09
    20
    Change Log

    November 9th, 2021

    • Show again "official" Sec. string same as LineageOS (2021-06-05)
    • Additional Custom build release property to indicate backport status
    • Standard flavor only: System Webview updated to 95.0.4638.50
    • microG flavor only: Bromite Webview 94.0.4606.109

    September 17th, 2021
    • UNOFFICIAL Security string 2021-09-05 *
    • Standard flavor only: System Webview updated to 92.0.4515.159
    • microG flavor only: microG upstreamed to 0.2.22.212658-2
    ___________________________
    * CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!

    August 10th, 2021
    • UNOFFICIAL Security string 2021-08-05 *
    • Standard flavor only: System Webview updated to 91.0.4472.164
    • microG flavor only: Bromite System Webview updated to 92.0.4515.134
    • microG flavor only: F-Droid 1.13
    ___________________________
    * CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!

    July 14th, 2021
    • UNOFFICIAL Security string 2021-07-05 *
    • Kernel: Many sec. patches applied (taken from Divest-OS)
    • microG flavor only: Bromite System Webview updated to 91.0.4472.146
    • microG flavor only: microG upstreamed to 0.2.21.212158-2
    • microG flavor only: AuroraStore 4.0.7
    ___________________________
    * CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!

    June 16th, 2021
    • Security string 2021-06-05
    • Standard flavor only: System Webview updated to 91.0.4472.101
    • microG flavor only: Bromite System Webview updated to 91.0.4472.102
    • microG flavor only: microG upstreamed to 0.2.19211515-9

    May 09th, 2021
    • Security string 2021-05-05
    • Standard flavor only: System Webview on 90.0.4430.82
    • microG flavor only: Bromite System Webview on 90.0.4430.204
    • microG flavor only: microG upstreamed (no version upgrade)
    • microG flavor only: AuroraServices updated 1.1.1

    April 11th, 2021
    • Security string 2021-04-05
    • Standard flavor only: System Webview on 89.0.4389.105
    • microG flavor only: Bromite System Webview on 90.0.4430.59
    • microG flavor only: F-Droid updated to 1.12
    • microG flavor only: AuroraStore updated to 4.0.4 with AuroraService 1.1.0

    March 08th, 2021
    • Security string 2021-03-05
    • microG flavor only: Bromite System Webview on 88.0.4324.207
    • microG flavor only: F-Droid 1.11
    • microG flavor only: microG 0.2.18.204714

    February 07th, 2021
    • ASB Security string 2021-02-05
    • microG flavor only: Bromite Webview on 88.0.4324.141
    • microG flavor only: Updated microG from upstream to 0.2.17.204714-5
    • microG flavor only: F-Droid updated to 1.10-alpha-234

    January 17th, 2021
    • ASB Security string 2021-01-05
    • Standard flavor only: System Webview on 87.0.4280.101 & fix of persistent histograms eating disk space
    • microG flavor only: Bromite Webview on 87.0.4280.131
    • microG flavor only: Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
    • microG flavor only: F-Droid updated to 1.10-alpha1-212

    December 18th, 2020
    • ASB Security string 2020-12-05
    • Standard flavor only: System Webview on 86.0.4240.198
    • microG flavor only: Bromite Webview on 87.0.4280.68
    • microG flavor only: Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)
    • microG flavor only: F-Droid updated to 1.10-alpha1-114

    November 08th, 2020
    • ASB Security string 2020-11-05
    • Fix of AOSP E-Mail widget
    • Fix for CVE-2020-15999
    • Standard flavor only: System Webview 86.0.4240.185
    • microG flavor only: Bromite Webview on 86.0.4240.181
    • microG flavor only: Updated microG with fixes in GCM and EN API
    • microG flavor only: Replaced weak F-Droid signatures with ROM's V2 signatures

    October 12th, 2020
    • ASB Security string 2020-10-05
    • Updated TimeService.apk
    • microG flavor only: Bromite Webview on 86.0.4240.73
    • microG flavor only: updated microG with included Exposure notification API (for Covid tracing apps)

    September 14th, 2020
    • ASB Security string 2020-09-05
    • Standard flavor only: System Webview on 85.0.4183.101
    • microG flavor only: Bromite Webview on 85.0.4183.86

    August 9th, 2020
    • ASB Security string 2020-08-05
    • Standard flavor only: System Webview on 84.0.4147.89
    • microG flavor only: Bromite Webview on 84.0.4147.113

    July 12th, 2020
    • ASB Security string 2020-07-05
    • microG flavor only: updated prebuilt microG GmsCore fom /e/ project to fix FCM registration issues
    • microG flavor only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
    • microG flavor only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

    June 09th, 2020
    • ASB Security string 2020-06-05
    • Standard flavor only: System Webview on 81.0.4044.138
    • microG flavor only: Bromite Webview on 83.0.4103.76

    May 07th, 2020
    • ASB Security string 2020-05-05
    • Standard flavor only: System Webview on 81.0.4044.117
    • microG flavor only: Bromite Webview on 81.0.4044.127
    • microG flavor only: AuroraStore updated to 3.2.8

    April 10th, 2020
    • ASB Security string 2020-04-05
    • Fix for CVE-2020-8597 (external/ppp)
    • Kernel: CVE-2019-10638 siphash 128bit for IP generation
    • Standard flavor only: System Webview on 80.0.3987.132
    • microG flavor only: Bromite Webview on 81.0.4044.76
    • microG flavor only: AuroraStore updated to 3.2.4

    March 07th, 2020
    • ASB Security string 2020-03-05
    • Standard flavor only: System Webview on 80.0.3987.117
    • microG flavor only: Bromite Webview on 80.0.3987.118
    • microG flavor only: AuroraStore updated to 3.2.0
    • microG flavor only: Added Netguard app (F-Droid version) to SELinux domain allowing to access /proc/net

    February 07th, 2020
    • ASB Security string 2020-02-01
    • Standard flavor only: System Webview on 79.0.3945.136
    • microG flavor only: Bromite Webview on 79.0.3945.139
    • microG flavor only: AuroraStore updated to 3.1.8

    January 13th, 2020
    • ASB Security string 2020-01-05
    • Standard flavor only: System Webview on 79.0.3945.116
    • microG flavor only: Bromite Webview on 79.0.3945.107
    • microG flavor only: AuroraStore updated to 3.1.7
    • microG flavor only: AuroraServices updated to 1.0.5

    December 7th, 2019
    • ASB Security string 2019-12-05
    • Standard flavor only: System Webview on 78.0.3904.96
    • microG flavor only: AuroraStore updated to 3.1.5

    November 10th, 2019
    • ASB Security string 2019-11-05
    • microG flavor only: Bromite Webview on 78.0.3904.72
    • microG flavor only: microG GMS core updated to 0.2.9

    October 15th, 2019
    • ASB Security string 2019-10-05
    • Standard flavor only: System Webview on 77.0.3865.92
    • microG flavor only: Bromite Webview on 77.0.3865.104
    • microG flavor only: AuroraStore updated to 3.1.3

    September 10th, 2019
    • ASB Security string 2019-09-05
    • Standard flavor only: System Webview on 76.0.3809.111
    • microG flavor only: AuroraServices updated to 1.0.4

    August 11th, 2019
    • ASB Security string 2019-08-05
    • Additional patches from AOSP branch 'nougat-mr2-security-release'
    • OTA Support
    • microG flavor only: Bromite Webview on 76.0.3809.100
    • microG flavor only: Aurorastore 3.0.9 with AuroraServices install method

    July 5th, 2019
    • ASB Security string 2019-07-05
    • System Webview updated to 75.0.3770.101 (non-microG flavor)
    • microG flavor only: Bromite Webview on 75.0.3770.109

    June 12th, 2019
    • ASB Security string 2019-06-05
    • System Webview updated to 74.0.3729.157 (non-microG flavor)
    • microG flavor only: Bromite Webview on 75.0.3770.86
    • microG flavor only: Replaced Yalpstore with Aurorastore
    • microG flavor only: Updated F-Droid & priv. extension
    • microG flavor only: Updated microG GMS core 0.2.7.x

    May 8th, 2019
    • Security string 2019-05-05
    • System Webview M74
    • 2nd build variant: "hardened microG build"

    April 8th, 2019
    • Security string 2019-04-05

    March 12th, 2019
    • Security string 2019-03-05
    • Android System Webview updated to M72 (includes CVE-2019-5786)

    February 8th, 2019
    • Security string 2019-02-05
    • Android System Webview M71
    • Kernel updated with many security patches
    • Additional Spectre V1 mitigations for the kernel

    January 12th, 2019
    • Security string 2019-01-05

    December 8th, 2018
    • Security string 2018-12-05
    • Fix of 'adb root' bug

    November 8th, 2018
    • Security string 2018-11-05

    October 20th, 2018
    • Security string 2018-10-05
    • Android System Webview M69

    September 9th, 2018
    • Security string 2018-09-05

    August 10th, 2018
    • Security string 2018-08-05

    July 24th, 2018
    • Security string 2018-07-05
    • System certificates from Oreo AOSP branch

    June 24th, 2018
    Initial creation
    • Security string 2018-06-05
    • AOSP tag 7.2.1_r36
    • Android System Webview M67
    • microG N patches
    • Patched repositories according to LineageOMS project to support substratum
    18
    New builds with April 2020 ASB

    Hi all,
    new builds are ready and are already offered through the updater app as OTA update:

    A. Default LineageOS 14.1 with substratum and microG patch
    https://sourceforge.net/projects/li...1-20200410-UNOFFICIAL-oms-falcon.zip/download
    • ASB Security string 2020-04-05
    • Fix for CVE-2020-8597 (external/ppp)
    • Kernel: CVE-2019-10638 siphash 128bit for IP generation *
    • System Webview on 80.0.3987.132

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    https://sourceforge.net/projects/li...0200409-UNOFFICIAL-mG-oms-falcon.zip/download
    • ASB Security string 2020-04-05
    • Fix for CVE-2020-8597 (external/ppp)
    • Kernel: CVE-2019-10638 siphash 128bit for IP generation *
    • Bromite Webview on 81.0.4044.76
    • AuroraStore updated to 3.2.4

    Cheers, M.
    ________________________________________
    * Kernel is frequently updated every month, but this one I found worth mentioning
    16
    New builds with June 2020 ASB

    Hi all,

    new builds are ready for download and also already offered for OTA update through the updater app:

    A. Default LineageOS 14.1 with substratum and microG patch
    https://sourceforge.net/projects/li...1-20200607-UNOFFICIAL-oms-falcon.zip/download
    • Sec. string 2020-06-05
    • System Webview on 81.0.4044.138

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    https://sourceforge.net/projects/li...0200605-UNOFFICIAL-mG-oms-falcon.zip/download
    • Sec. string 2020-06-05
    • Bromite Webview on 83.0.4103.76

    Note:
    This time, there haven't been any platform patches, as all published patches were already pushed by Google in a previous tag upstream and already back ported.
    15
    New builds with May 2020 ASB

    Hi all,
    new builds are ready and are already offered through the updater app as OTA update:

    A. Default LineageOS 14.1 with substratum and microG patch
    https://sourceforge.net/projects/li...1-20200507-UNOFFICIAL-oms-falcon.zip/download
    • ASB Security string 2020-05-05
    • System Webview on 81.0.4044.117

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    https://sourceforge.net/projects/li...0200507-UNOFFICIAL-mG-oms-falcon.zip/download
    • ASB Security string 2020-05-05
    • Bromite Webview on 81.0.4044.127
    • AuroraStore updated to 3.2.8

    Cheers, M.