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

[ROM][UNOFFICIAL][12][OTA][Material You][Signature Spoofing][Open Source][Encryption] LineageOS 19.0 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread

Raiz

Forum Moderator
Staff member
Guys, please keep it civil and on-topic. I'm going to clean up that thread, and ask you to be respectful and polite even when frustrated, infuriated, and other words in "-ed".
See Rule 2.3 :
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Thanks for your understanding.
 

ThePS4Gamer

Senior Member
Dec 20, 2015
317
106
Samsung Galaxy S10e
Redmi Note 10
This is (upstream) fixed in today's build btw.
It seems like the icon theming feature of the Monet Engine got fixed in Trebuchet by upstream, too.

In just a month, you and the contribution of other Lineage devs made this ROM into daily driver material. You only need to fix the screen regarding giving storage permissions to certain storage devices and the issue of OTA updates getting stuck at 90% with the Lineage Recovery and I would say this is a flash and forget experience now.
 

Linux4

Senior Member
It seems like the icon theming feature of the Monet Engine got fixed in Trebuchet by upstream, too.

In just a month, you and the contribution of other Lineage devs made this ROM into daily driver material. You only need to fix the screen regarding giving storage permissions to certain storage devices and the issue of OTA updates getting stuck at 90% with the Lineage Recovery and I would say this is a flash and forget experience now.

That getting stuck issue isn't caused by the ROM, it's caused by Magisk's addon.d not working with FBE (and topjohnwu isn't willing to fix that even tho it's possible)
I'd recommend you using https://github.com/programminghoch10/Lygisk instead. If you need any help you can join the project's Telegram group.
 

wor52

Member
Aug 8, 2021
6
2

Linux4

Senior Member
Why aren't these problems present in 18.1? I can install OTA updates without any problems, I just have to re-flash magisk from recovery

They are present there too.
Did you maybe just patch bootimage instead of flashing zip/apk in recovery ? If so it didn't install it's addon script, which would explain why it doesn't freeze for you.
Anyway Lygisk also removes the need to reflash after OTA (but only if you flash via recovery ofc!)
 

wor52

Member
Aug 8, 2021
6
2
They are present there too.
Did you maybe just patch bootimage instead of flashing zip/apk in recovery ? If so it didn't install it's addon script, which would explain why it doesn't freeze for you.
Anyway Lygisk also removes the need to reflash after OTA (but only if you flash via recovery ofc!)
No I flashed the magisk zip/apk from recovery (lineage recovery) as you recommended in the installation instructions and every week I can download the lineageos official build and install it. It works perfectly but magisk gets obviously overwritten every time, so I have to reflash it from recovery.
Anyway I know about Lygisk but I haven't reviewd the changes you made from upstream yet, as soon as I find the time to check them I will gladly try it :)
(I still don't understand why topjohnwu isn't implementing them on Magisk tho)
 
Last edited:

wor52

Member
Aug 8, 2021
6
2
Update: I reviewed the Lygisk code and it seems to work just fine. I also looked up issues on Magisk and found this thread in which they talk about the problem. They don't like storing magisk apk on addon.d so they prefer suggesting to install twrp
 

Linux4

Senior Member
Update: I reviewed the Lygisk code and it seems to work just fine. I also looked up issues on Magisk and found this thread in which they talk about the problem. They don't like storing magisk apk on addon.d so they prefer suggesting to install twrp

The recovery isn't the problem, if /data wasn't encrypted it would work even with lineage recovery (just that for some devices other custom recoveries provide decryption of /data in recovery which isn't possible on our devices tho, and it's not meant to exist anyway so...)
Also dependencies of addon.d were never meant to be stored outside of /system....

Edit: Also imo it was just rude of them to completely ignore jesec's attempt to fix it in https://github.com/topjohnwu/Magisk/pull/3037
 
Last edited:
  • Like
Reactions: starbright_

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    So I'm on stock ROM. In Germany OneUI4 released today. I installed it accidentally. My bootloader is already unlocked, can't relock it, the switch is greyed out, because I had LineageOS before. Can I switch to LineageOS now or am I screwed?

    Binary version wasn't increased on initial OneUI 4 update so you should be able to downgrade to OneUI 3 if needed (using Odin and a stock package from e.g samfw.com).
    However it seems that current lineage (which uses OneUI 3 kernel and blobs as base) works fine on OneUI 4 firmware still, but it needs more testing.
    As soon as samsung releases updated kernel sources I can start working on integrating OneUI 4 changes anyway.
    3
    Very nice work! The ROM is running smoth so far. Big THX @Linux4
    3
    Hi guys! The symbols in the first line as seen in the picture are cut off above. Does anyone know the problem? How could it be fixed?
    Thanks!
    If you install today's build it is fixed...
    2
    Sorry, I was just kidding ;-) Many years ago I also asked myself the same questions. Honestly, no one can say exactly what is safe or not. Since a lot happens on the hardware level, even Android keeps one or the other topic hidden. Again and again we come across strange conditions in individual patch levels of renowned manufacturers and their stock roms like this or for example, strange encrypted communications of various preinstalled apps with even stranger preinstalled (root) certificates from foreign countries.

    I'm no longer a security expert, but when a lightweight operating system like Lineage or E-OS https://e.foundation/e-os/ doesn't randomly generate strange traffic on my gateway, I'm really happier.

    Whether that is better then? No, just different ;-) :)

    Because I've seen horses throw up, at least when they went over cellular instead of WIFI. Then the world is again a whole different ;-)
  • 24
    1607247455067.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions:
    • Follow the instructions here

    Downloads:

    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • DO NOT Report bugs if you're using TWRP
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:


    Support
    Telegram group

    Contributors
    Linux4
    Source Code: LineageOS Gerrit
    Kernel source: https://github.com/Linux4/android_kernel_samsung_exynos9820
    16
    Requirements:
    • Any Q or R based firmware installed on your device.

    Pre-Install Instructions

    Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.

    1. Connect the device to a Wi-Fi network.
    2. Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
      • From within the Developer options menu, enable OEM unlock.
    3. Power off the device, and boot it into download mode:
      • With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
      • Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
    4. Your device will reboot, you may now unplug the USB cable from your device.
    5. The device will demand you format userdata, please follow the onscreen instructions to do so.
    6. Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
    7. Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.

    Installing LineageOS for the first time
    1. Flash lineage recovery
      Only the provided lineage recovery will be supported,
      using TWRP might result in a possible data loss!!

      If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
      If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
    2. Boot lineage recovery
      IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
      If using Odin untick auto-reboot before flashing.
      After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
      immediately hold Volume Up, Bixby and Power to boot recovery
      IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
      boot recovery via Volume Up, Bixby and Power.
    3. Factory reset using Factory reset -> Format data/factory reset
      Warning: Unlike TWRP this will also erase internal storage!
    4. Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
      Then run adb sideload <path to your lineage.zip> on your PC
      Optional:
    5. Sideload GApps and Lygisk by repeating above step
      with their zip/apk

    Magisk
    As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
    on every other device, no bootimage with magisk included or installing to recovery is needed!
    I also strongly recommend to use Lygisk instead,
    which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
    this will also fix OTAs getting stuck while having installed Magisk.
    13
    Features

    • SELinux enforcing
    • AES-256-XTS FBE encryption
    • Latest Linux 4.14.x kernel
    • All cameras are working
    • Ramdisk is working

    Known issues

    • VoLTE/VoWiFi
    • LineageOS specific features like livedisplay (for now)
    • You tell me
    7
    HI Linux4,
    Just a "little"question, when are we going to become official, do you have an idea?
    Thank you in advance for your answer and especially for all your work !

    19.0 is in general not even close to an official release at this point, all I can tell you is, if we're not running into bigger issues (and currently we don't seem to) S10/N10 Series might be in the first batch of devices to get official 19.x once it's ready.
    Please don't ask for a more specific ETA because I can't give one.