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

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

Search This thread

davidlyerly

Member
Nov 5, 2021
6
3
Why are colors listed as system files in the OS.? lmfao
I successfuly tethered to my oneplus with afwall and a vpn running from my sonim xp5 but it seems like either every time I boot or update the rom or whatever tethering fails. It connects but then my vpn won't, and once that happens even if I remove the vpn it connects but doesn't access the data. I'm gonna switch to mint. Having to call redpocket every time to fix it is lame.

Happy being treated like cattle when the location data is now bought by governments. Good luck.
 
Why are colors listed as system files in the OS.? lmfao

The built-in accent colors used by Styles & Wallpaper are compiled as tiny little system APKs, and consist of nothing more than XMLs that redefine certain color values used throughout the system. That's why they show up as system files.
 
Why are colors listed as system files in the OS.? lmfao
I successfuly tethered to my oneplus with afwall and a vpn running from my sonim xp5 but it seems like either every time I boot or update the rom or whatever tethering fails. It connects but then my vpn won't, and once that happens even if I remove the vpn it connects but doesn't access the data. I'm gonna switch to mint. Having to call redpocket every time to fix it is lame.

Happy being treated like cattle when the location data is now bought by governments. Good luck.
Hi,
the explanation about the overlay apks has already been given by @MJPollard . If interested, here some more information.
Just to understand: You use the OP3T as hotspot and connect with your other device xp5 to it, right?
And under what conditions it stops? Can you produce a log?

Btw, seems you have edited your post? - I saw recently a much longer post by you here, if I remember right, and wanted to take some time now to carefully read and comment, if applicable. You can of course edit your posts as you consider this necessary, however - not receiving an immediate reply does not mean, that people would ignore or dislike, what you say... (just my 2 cents)

Regarding location data, yes, this is an interesting and challenging topic - for sure a reason not to use GApps, and yes, also w/o Gapps crap, there is still enough challenges...
 

borisSweden

Senior Member
May 10, 2021
115
7
Is it a false postive that the phone supports 3xLTE-CA flashing this ROM? NSG sometimes shows. On OOS its 2xCA. The phone doesnt support B28.
 
Is it a false postive that the phone supports 3xLTE-CA flashing this ROM? NSG sometimes shows. On OOS its 2xCA. The phone doesnt support B28.
Honestly, I don't know - as indicated before (maybe in my 17.1 thread and not here), I have mainly taken over the LineageOS device configuration, I am not the Hardware specialist for this device. However, I can't imagine, that LineageOS would be able to activate a hardware feature (like e.g. LTE carrier aggregation), which isn't supported by OOS...
 

borisSweden

Senior Member
May 10, 2021
115
7
Honestly, I don't know - as indicated before (maybe in my 17.1 thread and not here), I have mainly taken over the LineageOS device configuration, I am not the Hardware specialist for this device. However, I can't imagine, that LineageOS would be able to activate a hardware feature (like e.g. LTE carrier aggregation), which isn't supported by OOS...
LOS team doesnt deal with EFS or NV items and them using QXDM would be in breach with Qualcomms Code Aurora Project. Also I only get 3xCA inside but outside I only get 2xCA. Right now Im on OOS again and playing around with Efstool to mask the phone as a "certified" X12 modem phone. I was able to side-load a X9 modem binary from Xiaomi A1 but I didnt get IMS or Band 28(should be interest for you and many as B28 is universal in Europe).

Btw, do you know how to extract .mbn files from ROMS?

Edit: I sideloaded a SD835 mbn file with EFStools and not got bricked.
 
Last edited:

AndrewRnd

New member
Aug 23, 2016
1
0
Hello. Is there a way to disable one of SIM softly? I find a lot of discussions about it for LOS.
1638239084514.png
 

davidlyerly

Member
Nov 5, 2021
6
3
Hi,
the explanation about the overlay apks has already been given by @MJPollard . If interested, here some more information.
Just to understand: You use the OP3T as hotspot and connect with your other device xp5 to it, right?
And under what conditions it stops? Can you produce a log?

Btw, seems you have edited your post? - I saw recently a much longer post by you here, if I remember right, and wanted to take some time now to carefully read and comment, if applicable. You can of course edit your posts as you consider this necessary, however - not receiving an immediate reply does not mean, that people would ignore or dislike, what you say... (just my 2 cents)

Regarding location data, yes, this is an interesting and challenging topic - for sure a reason not to use GApps, and yes, also w/o Gapps crap, there is still enough challenges...
Just as I thought. It's a kind of hack that gives the same overlay, in this case a simple color apparently, to any ap with the resource flag enabled. So Instead of actually having full-screen overlays and their corresponding controls, we're stuck in some simpleton box-like choose your color setup. Imo this is why even though the phone supports overlays such as a transparent background/foreground, it's really not giving you a full and proper overlay feature. Even on a full 4K say 120Hz display, you still aren't utilizing the actual ability of the screen's resources.
I'd like to have a homescreen that is actually 2 screens. One a fullscreen wallpapaper or whatever, and the other as the functioning one, but both just overlays if that even makes sense. I'm guessing it can be done and look waaay better but would take a lot more power too. Some day.

As for tethering with my sonim xp5 to the one+3t ? I figured it out. Turn data on, reboot, turn tether on. Seems to work like a charm. Btw I uninstalled (w/pkg mgr) 2 of the 3 phone files leaving only services enable, the cellbroadcast recevr, service and module, the dialer, everything that I simply don't need on the oneplus anymore I 'uninstalled'.. Gps, bt, wifi, tethering, all good. Package Mgr will let me re-install even if I update the rom. But why?
The xp5 is fun being so simple. T9 ROCKS! lol
 
Last edited:

davidlyerly

Member
Nov 5, 2021
6
3
Switching from 9pie to 10, clipx still worked as a convenient overlay ap, but now in 11 google once again is messing with the overlay and I had to switch to Xclipper which I like mo betta. The network up/down notification completely stopped working and I am back to using Data Stats which is kind of a pita. Plus Volume Styles update fails to wok at all. Just lovin the new google overlay BS. TG it doesn't have a sim.
Dalvik cache seems to be a super place to hang out these days. Or is it hang up?

Does anyone know of a cool network notification other than Data Stats?
I remember there being one but it was on a forum I no longer partake from. NBD
Data Stats is perfect except for having to disable it on certain aps.
I have zero location modules now so the gps can take like 2 minutes to achieve a fix. Funny too 'cause it almost acts like it doesn't work at all lol.

Linux had such potential and still does on phone hardware. Unfortunately the govt has aligned itself with google's "fused" mentality. Mandating a gps chip not only exist on every phone but be "fused" to the radio/modem/bt. Think of a joint being fused and all actual and any flexibility, that which is linux, is gone. Poof.
It'd be cool to build your pwn phone that works on modern systems but has no wifi bt or gps but would really not be easy at all.. That LiePhone2 is nice looking but doesn't act so. There's zero control of the gps. It's just ON, always. Plus they 'discourage' anything but uploading your vcf file just to import it and it's supposed to be based on android 8!

One's only other option is to use a sip acct.. But then the price of service automatically doubles and so it's actually cheaper and therefore easier not to as you are still stuck using android if you want to use osmand or magic earth. All the true dedicated gps devices are rather for hiking and even then are a pita to update and whatnot. Osmand is free and just plain works..

After careful consideration I have decided to never buy a google phone. When you are trying to remove google using a phone made BY google and then pretending you removed it is a farce. Wake me up when 5G no longer exists.
 
Last edited:
  • Like
Reactions: alleykat2561

davidlyerly

Member
Nov 5, 2021
6
3
I think google's modus operandi is to continually force hardware changes which then force software changes essentially forcing we the end user to buy a 'newer' device just to keep an ap going. Ergo they are now forcing 5G down your throat if you want the latest device.
MSe 1969 is a saviour with this device. I am so glad I removed the sim. The ONLY ap I would buy a new rooted non-5g phone for would be gps stuff like Osmand~. Everything else can either never recieve an update or be removed/replaced. My sonim xp5 is like new and the speakers are so good I don't even need BT in the car.
It's almost Xmas. Merry Christmas everyone!
 
  • Like
Reactions: alleykat2561
I'm going to update from a previous version of your ROM, the LineageOS 17.1 build w/microg. I'm also running magisk 2.3, should I uninstall magisk first or install on top of it?

Generally good advice when moving from any major ROM release to the next (i.e. LineageOS 17.1 to 18.1) is to back up your apps and settings, wipe data and caches, do a clean install of the new version (along with Magisk), and restore your apps and settings. If you're using TWRP, I'd also do a full backup of the data, system, and boot partitions before you begin. That way, you can restore it and go back to 17.1 if necessary. (That's good advice no matter how you're updating, even if it's as simple as an OTA update. Backups have saved my bacon more than once!)
 
  • Like
Reactions: alleykat2561

alleykat2561

Senior Member
Aug 30, 2010
65
13
CC, TX
Nexus 7 (2013)
Google Nexus 5
Generally good advice when moving from any major ROM release to the next (i.e. LineageOS 17.1 to 18.1) is to back up your apps and settings, wipe data and caches, do a clean install of the new version (along with Magisk), and restore your apps and settings. If you're using TWRP, I'd also do a full backup of the data, system, and boot partitions before you begin. That way, you can restore it and go back to 17.1 if necessary. (That's good advice no matter how you're updating, even if it's as simple as an OTA update. Backups have saved my bacon more than once!)
Thanks for the input! This is common knowledge for me. Since the OP, MSe1969 stated " If you update from a previous version of my ROM, including my LineageOS 17.1 build, you don't need to perform a wipe. ", Thought I'd give that a shot first (famous last words). I just wondered about magisk. I may have to do the fresh install anyway.
 
Thanks for the input! This is common knowledge for me. Since the OP, MSe1969 stated " If you update from a previous version of my ROM, including my LineageOS 17.1 build, you don't need to perform a wipe. ", Thought I'd give that a shot first (famous last words). I just wondered about magisk. I may have to do the fresh install anyway.
Well, a clean-flash will for sure work, but many folks try to avoid this. I stick to my advice, that you can dirty-flash my 18.1 build over my 17.1 build - but that is without Magisk.
So my advice in your case would be - as per your preference - to either uninstall Magisk, dirty-flash and then install Magisk again, or to do a clean-flash.
 
  • Like
Reactions: alleykat2561

borisSweden

Senior Member
May 10, 2021
115
7
New build with December 2021 ASB patches

Hi all,
a new build for the OP3(T) containing the December 2021 ASB patches has been released:

The Updater app should already indicate to offer an OTA update.
  • Security string 2021-12-05
  • Bromite Webview and Browser on 96.0.4664.54
  • microG 0.22.214516-21
  • Some kernel patches
Happy flashing,
Regards, M.
is the unsupported 3.18 kernel issue fixed? Also is Z-Ram finally enabled?
 

alleykat2561

Senior Member
Aug 30, 2010
65
13
CC, TX
Nexus 7 (2013)
Google Nexus 5
Well, a clean-flash will for sure work, but many folks try to avoid this. I stick to my advice, that you can dirty-flash my 18.1 build over my 17.1 build - but that is without Magisk.
So my advice in your case would be - as per your preference - to either uninstall Magisk, dirty-flash and then install Magisk again, or to do a clean-flash.
Thanks for the reply and for the continued work on these builds!
 
  • Like
Reactions: MSe1969
is the unsupported 3.18 kernel issue fixed? Also is Z-Ram finally enabled?
I am picking kernel patches from the "Divested Mobile" org. on Github for my 18.1 buid since the beginning.
The developer behind DivestOS keeps collecting and backporting available kernel patches from higher releases, so I would assume so. Not "perfect" (as the dev describes his approach himself), but one of the best sources available for older, no longer officially supported kernels.

Regarding Z-RAM:
I have picked this upstream commit from LineageOS, which is now part of the build. Further, see here.
 

borisSweden

Senior Member
May 10, 2021
115
7
I am picking kernel patches from the "Divested Mobile" org. on Github for my 18.1 buid since the beginning.
The developer behind DivestOS keeps collecting and backporting available kernel patches from higher releases, so I would assume so. Not "perfect" (as the dev describes his approach himself), but one of the best sources available for older, no longer officially supported kernels.

Regarding Z-RAM:
I have picked this upstream commit from LineageOS, which is now part of the build. Further, see here.
Great. But is there any big addon in the works in the near future? I check the Github/ gerrit page and Z-RAM was the newest. It wasnt supported before which cause alot of lag.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    New build with January 2022 ASB patches

    Hi all,
    a new build for the OP3(T) containing the January 2022 ASB patches has been released:

    The Updater app should already indicate to offer an OTA update.
    • Security string 2022-01-05
    • Some kernel patches
    • A couple of patches and fixes from LineageOS
    Happy flashing,
    Regards, M.

    EDIT: URL adapted, see next post
    2
    Super excited about this one, gonna try to give my old OP3T a breath of fresh air!

    Thanks for your work, @MSe1969 , keep it up!
    1
    Hi @MSe1969 I notice the wake screen for notification option is missing from Settings | Lock Screen menu, but it's searchable. Could you please take a look?
    Screenshot_20220104-161350_Settings_Suggestions.png

    Screenshot_20220104-161403_Settings.png
    1
    It works great but be prepared as boot times are significantly longer than say stock when new.
    1
    It works great but be prepared as boot times are significantly longer than say stock when new.
    Very true, but this is something, people should be able to live with :)
    But right - don't panic - 1st boot after every update takes loooong...
  • 11
    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
    • 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 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: 2022-01-05
    AOSP tag: 11.0.0_r46
    Bromite System Webview: M96

    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.



    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)
    7
    Change Log

    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
    7
    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:

    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.
    5
    New build with December 2021 ASB patches

    Hi all,
    a new build for the OP3(T) containing the December 2021 ASB patches has been released:

    The Updater app should already indicate to offer an OTA update.
    • Security string 2021-12-05
    • Bromite Webview and Browser on 96.0.4664.54
    • microG 0.22.214516-21
    • Some kernel patches
    Happy flashing,
    Regards, M.
    5
    H

    How long did you wait for A10 and A11?
    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...