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

Search This thread
OTA Updated yesterday And now phone is fully dead ,
no Bootloader , no recovery, not charging.

if anyone have solution ,please suggest !!!!!

Thanks in advance !!!!!
I have tested both variants f. OTA - not sure, what caused the hard-brick to your device.

Tbh, I can only recommend you to search on XDA and the search engine of your choice for methods to unbrick a hard-bricked Moto G. A quick search has delivered to me some hits, but I can't give you a recommendation for any approach. Maybe others would like to step in?

In general, the falcon is an aged (almost 10 years now) low budget device, e.g. the "internal flash memory" is only a recrafted SD card. Maybe its time simply has come...? Of course, before giving up, try to unbrick somehow...

Sorry, that I can't give you any better advice, but a true hard-brick as described by you with NO reaction at all does not belong to my experience ...
 

pankajandhale

Member
Oct 13, 2016
17
14
Moto G
Xiaomi Redmi 4X
I have tested both variants f. OTA - not sure, what caused the hard-brick to your device.

Tbh, I can only recommend you to search on XDA and the search engine of your choice for methods to unbrick a hard-bricked Moto G. A quick search has delivered to me some hits, but I can't give you a recommendation for any approach. Maybe others would like to step in?

In general, the falcon is an aged (almost 10 years now) low budget device, e.g. the "internal flash memory" is only a recrafted SD card. Maybe its time simply has come...? Of course, before giving up, try to unbrick somehow...

Sorry, that I can't give you any better advice, but a true hard-brick as described by you with NO reaction at all does not belong to my experience ...
Hey man thanks for reply ,

Tried all the Methods > No Luck .

then at last opened the phone and checked the battery voltage it was 2.8 V , and my fastboot oem-off-mode was set to 0 thats why phone was not charging nor booting .
Jump-charged the battery for 15 minutes and then tried to boot in fasstboot !!!!!!!!!!!!!!!!!!

My Lovely Moto rose from dead !!!!!
thank you very much for your efforts to keep this Device alive .


one last thing Whenever I try to do > fastboot oem-off-mode 1
it gives > slot-count not found .
any suggestion ?
 

Attachments

  • PXL_20220625_191232751.jpg
    PXL_20220625_191232751.jpg
    2.9 MB · Views: 29
Hey man thanks for reply ,

Tried all the Methods > No Luck .

then at last opened the phone and checked the battery voltage it was 2.8 V , and my fastboot oem-off-mode was set to 0 thats why phone was not charging nor booting .
Jump-charged the battery for 15 minutes and then tried to boot in fasstboot !!!!!!!!!!!!!!!!!!
Glad you reanimated your phone :)
Just to understand: So you put charge directly to the battery, right?
one last thing Whenever I try to do > fastboot oem-off-mode 1
it gives > slot-count not found .
any suggestion ?
Unfortunately, I am not familiar with the undocumented oem-specific fastboot commands. If I understood you right, the oem off-mode would cause the battery not being charged??? I am not sure about that - I think there is a setting to leave the screen black during charging, but not to "not load" the battery... However, as said - I am not really familiar with the hidden fastboot commands. But I would expect that the command is 'fastboot oem <special command>', hence 'fastboot oem off-mode ...' - and AFAIK, there is only a command like 'fastboot oem off-mode-charging ...' - Just my thoughts...
 

pankajandhale

Member
Oct 13, 2016
17
14
Moto G
Xiaomi Redmi 4X
Just to understand: So you put charge directly to the battery, right? > YES

Unfortunately, I am not familiar with the undocumented oem-specific fastboot commands. If I understood you right, the oem off-mode would cause the battery not being charged??? I am not sure about that - I think there is a setting to leave the screen black during charging, but not to "not load" the battery... However, as said - I am not really familiar with the hidden fastboot commands. But I would expect that the command is 'fastboot oem <special command>', hence 'fastboot oem off-mode ...' - and AFAIK, there is only a command like 'fastboot oem off-mode-charging ...' - Just my thoughts. >

fastboot oem off-mode-charge (takes "0" and "1" as an argument ).

if I connect charger to switched off phone , following functions can be achieved

"fastboot oem off-mode-charge 0" >>> will keep my phone switched off while charging when usb is connected
"fastboot oem off-mode-charge 1" >>> will power on phone as soon as phone is connected (as power button of my phone is little hard this trick helps me to power on my phone )

anyways thank you and please keep developing for this phone until possible :):):)
 
  • Like
Reactions: GizmoTheGreen
New builds available

Hi all,
new builds with backported July 2022 patches (July 2022 custom build release) are available for download and via the Updater app.


A. Default LineageOS 14.1 with substratum and microG patch

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

Happy flashing
Regards, M.
 

amlethh

New member
Aug 3, 2022
2
0
Thank you so much for keeping the Falcon alive! I have 3 strong units and intend to use them till the dawn of time. Lately I have been facing one issue though: some apps are starting to drop support for Android 7. One example is Slack, the last versions all require Android 8+ and they are sending emails telling this for everyone who has an older version installed:
Our records indicate that you are on a version of the Slack mobile app that Slack will stop supporting on September 1, 2022.
As we all know, our beloved Falcon can't handle Android 8 or up because of hardware constraints. However, is there a way to spoof the Android version so it appears we are on Android 8 or up while still being on the current build?
That is, is there a way to spoof Android version on MSe1969's LineageOS Falcon build?

Regards.
 
As we all know, our beloved Falcon can't handle Android 8 or up because of hardware constraints. However, is there a way to spoof the Android version so it appears we are on Android 8 or up while still being on the current build?
That is, is there a way to spoof Android version on MSe1969's LineageOS Falcon build?
Unfortunately not. This is not about "spoofing". An Android app declares a "minimum SDK" level, which is the lowest Android version supported. By doing so, the developer is limited to those functionalities, which are available in that release. Any attempt of using a method or a class or simply a method parameter, which does not exist in the minimum SDK hence causes a build error, when compiling the app.
So the desire to use new cool features of a newer Android release has to be balanced against the user base. Slack has decided to "move on" it seems...
In addition, there is also the "target SDK" topic adding complexity to this, but let's talk about that another time...
 
  • Like
Reactions: phpbb3

amlethh

New member
Aug 3, 2022
2
0
Unfortunately not. This is not about "spoofing". An Android app declares a "minimum SDK" level, which is the lowest Android version supported. By doing so, the developer is limited to those functionalities, which are available in that release. Any attempt of using a method or a class or simply a method parameter, which does not exist in the minimum SDK hence causes a build error, when compiling the app.
So the desire to use new cool features of a newer Android release has to be balanced against the user base. Slack has decided to "move on" it seems...
In addition, there is also the "target SDK" topic adding complexity to this, but let's talk about that another time...
That is a sad situation but as users we must understand developers reasons. Still, could it be that in some cases the app requiring a higher SDK is unnecessarily doing so? I found this post on another forum from some months ago:
This decision really frustrating! And yeah, I spoofed my Android version as 8 and it works perfectly fine on my Android 7, so it's not a case of technical limitations.
So far this is the only app that's limiting my Falcon experience, so it'd be really good if there were a workaround...

Thanks!
 
That is a sad situation but as users we must understand developers reasons. Still, could it be that in some cases the app requiring a higher SDK is unnecessarily doing so? I found this post on another forum from some months ago . . .
Technically, a developer can of course use code fully suitable for Android version Y, but declare the minimum SDK level to be Y+n - would be not really be the smartest move at all, but that is technically possible. (Further, I know that Google forces app developers to frequently increase the target SDK declaration to the defined minimum for apps in the play store - not sure however about the minimum SDK level declaration...?)

So if you find some "good stuff" helping you to spoof the Android version (like an Xposed module?) or you succeed in modifying the apk manifest to allow Android 7 in the Slack apk file via e.g. apktool and the apk does not crash, there you go. But frankly, that is nothing, I am willing to spend time with in my ROM builds. (e.g. because this is also kind of a security/stability feature to ensure, that the system does not crash and freeze)
 
New builds available

Hi all,
new builds with backported August 2022 patches (August 2022 custom build release) are available for download and via the Updater app.

A. Default LineageOS 14.1 with substratum and microG patch
  • System Webview 103.0.5060.71
B. Hardened build with pre-installed microG and F-Droid, patched for substratum
  • Bromite Webview 103.0.5060.140
Happy flashing
Regards, M.
 

CallMeTom1

New member
Aug 12, 2022
3
2
After updating via the updater app, I stuck in fastboot mode. I can no longer boot the system ("boot up failed"). The recovery/TWRP still works. I have already tried in TWRP to reflash the zip file but without success. Does anyone have an idea?

IMG_6314_cut.jpg
 

Scranalot

Senior Member
Mar 28, 2019
73
45
After updating via the updater app, I stuck in fastboot mode. I can no longer boot the system ("boot up failed"). The recovery/TWRP still works. I have already tried in TWRP to reflash the zip file but without success. Does anyone have an idea?

View attachment 5683775
Hello Tom
Was the phone working satisfactorily before the update?
Your phone isn't full up with data is it?
What ever you do from now though firstly I would try & extract as much data that you would want to keep from the phone as possible.
Got a few of suggestions you may want to try - please read through them all first though:
Please bare in mind Tom these are only my suggestions - I am not telling you to do any of these that is entirely your own choice & responsibility - that being said I have done all the above , with the exception of the 'fall-through from normal boot mode' specific things mentioned in the first link, during my ownership of the these phones.
Someone else will hopefully chime in with a knowledgeable response.
All the best
 
  • Like
Reactions: MSe1969
After updating via the updater app, I stuck in fastboot mode. I can no longer boot the system ("boot up failed"). The recovery/TWRP still works. I have already tried in TWRP to reflash the zip file but without success. Does anyone have an idea?
I think, what @Scranalot replied to you pretty well lists your options here.

Maybe an additional thought, just to be sure - please advise:
You were using this ROM normally before without any issue, correct?
You haven't flashed anything on top recently, which has e.g. put some kind of "survival script" attempting to reflash something?
The phone wasn't already somehow "messed up" before the update (e.g. by flashing bad stuff) and you were hoping to "repair" the mess by applying an update?
 

CallMeTom1

New member
Aug 12, 2022
3
2
@Scranalot @MSe1969
Hi! Thanks for your replies and sorry for my late reply.

The Moto G is my second phone. I use it to control my Bluetooth box and for navigation (since BT and GPS work rather poorly on my main phone). Everything worked fine before the update (it was all a bit slow, but the smartphone is old) and I only did the update/dirty flash.

Meanwhile it works again (more or less). I did a full wipe and reinstalled the ROM (without full wipe it didn't work before).
I can not install Gapps for some reason (Error Code 70), but here I will also find a solution.
 
Meanwhile it works again (more or less). I did a full wipe and reinstalled the ROM (without full wipe it didn't work before).
I can not install Gapps for some reason (Error Code 70), but here I will also find a solution.
Which flavor of Gapps did you try to install? The falcon does not have a lot of space in the system partition, so 'nano' is the largest, you should aim for (I recommend - if you really want Gapps - only the 'pico' flavor)
 
  • Like
Reactions: CallMeTom1

Top Liked Posts

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

    Hi all,
    new builds with backported September 2022 patches (September 2022 custom build release) are available for download and via the Updater app.

    A. Default LineageOS 14.1 with substratum and microG patch
    • Custom build release 2022-09-01
    • System Webview 105.0.5195.79
    • Many kernel patches

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    • Custom build release 2022-09-01
    • Bromite Webview 104.0.5112.91
    • Many kernel patches
    • microG 0.2.24.214816-30

    Happy flashing
    Regards, M.
    2
    Thank you for this contribution and maintenance of this device.
    In turns out falcon got preserved better than my two Nexus 4 by LG and performs like my Nexus 5.
    All thanks to xda contributors. Much better than the future I see for my mich newer devices.
  • 64
    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 August 2022 (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 M105
    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 M104
    Download here

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

    Installation Instructions

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

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

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

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

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

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

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


    Current / reported issues
    • WiFi hotspot needs to be toggled on/off/on after a reboot to work
    • WiFi hotspot enabled longer than 2 hours may cause a sudden reboot
    • Sometimes (root cause not clear), WiFi switches itself off after a couple of hours (fix by enabling/disabling flight mode)
    • It has been reported by some forum participants, that after messing with some Android-10 test builds for this device, WiFi wouldn't work any more: In this case, the solution can be found here:
      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, 11 or 12)?
    The falcon device is low on memory (RAM and storage flash memory), each newer Android release increases the resource demand and thus decreases performance and available memory - so higher versions won't really make sense for this device.
    Further, I haven't seen any ROM for this device on a higher Android version than Nougat with enforcing SELinux (yes, coming there indeed is "slave work"; none of the devs, including me for above stated reasons, is willing to invest this time...) - which is a No-Go for any daily-driver use (in that case, your device simply is fully open many vulnerabilities and applying monthly ASB patches on a permissive SELinux is close to a complete waste of time).


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


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

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

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

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

    Created 2018-06-24
    Last Updated 2022-09-11
    22
    Change Log

    September 11th, 2022

    • September 2022 Custom build release
    • Many kernel patches
    • Standard flavor only: System Webview 105.0.5195.79
    • microG flavor only: Bromite Webview updated to 104.0.5112.91
    • microG flavor only: microG 0.2.24.214816-30

    August 9th, 2022
    • August 2022 custom build release
    • Standard flavor only: System Webview 103.0.5060.71
    • microG flavor only: Bromite Webview 103.0.5060.140

    July 16th, 2022
    • July 2022 custom build release

    June 16th, 2022
    • June 2022 custom build release
    • Standard flavor only: System Webview 102.0.5005.78
    • microG flavor only: Bromite Webview updated to 102.0.5005.96
    • microG flavor only: F-Droid 1.15.2
    • microG flavor only: microG 0.2.24.214816-11
    May 11th, 2022
    • May 2022 custom build release
    • Standard flavor only: System Webview updated to 100.0.4896.127
    • microG flavor only: Bromite Webview updated to 101.0.4951.53
    • microG flavor only: F-Droid 1.15
    • microG flavor only: Mozilla Location provider 1.5.0
    • microG flavor only: microG 0.2.24.214816-10

    April 16th, 2022
    • April 2022 custom build release
    • Standard flavor only: System Webview updated to 100.0.4896.58
    • microG flavor only: Bromite Webview updated to 100.0.4896.57

    February 19th, 2022
    • February 2022 custom build release
    • Standard flavor only: System Webview updated to 98.0.4758.101
    • microG flavor only: F-Droid updated to 1.14, F-Droid privileged extension to 0.2.13
    • microG flavor only: Bromite Webview updated to 97.0.4692.106
    • microG flavor only: microG updated to 0.2.24.214816-2

    December 20th, 2021
    • December 2021 custom build release
    • Standard flavor only: System Webview updated to 96.0.4664.104
    • microG flavor only: Bromite Webview 96.0.4664.54
    • microG flavor only: microG 0.22.214516-21

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    June 24th, 2018
    Initial creation
    • Security string 2018-06-05
    • AOSP tag 7.2.1_r36
    • Android System Webview M67
    • microG N patches
    • Patched repositories according to LineageOMS project to support substratum
    19
    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
    17
    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.