• 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

Linux4

Senior Member
changing the display cutout style in the Developer Settings permanently soft-bricks your install

That's a bug in AOSP actually and it seems fixed for me in android-12.0.0_r12 (November securitypatch)
Other than that it doesn't permanently softbrick as you can just use cmd overlay disable <overlay packagename> in adb shell to get rid of it again...
 

slytidar

Senior Member
May 31, 2012
430
53
can anyone provide a guide to dirty flash this ROM on the first build and gain root access?
Phone is solid as it is and don't wanna backup everything again if possible.

Thank You
 
i rebooted back to LOS recovery and the apply from storage option is gone, so I sideloaded the from zip and it flashes successfully but rebooting from there gives loops back to LOS recovery saying data is corrupt and I must factory reset
Aw hell, that's harsh! Well, the only thing I can think of is to install TWRP and pull out all they important files. I basically have no experience curing those "corruptions" =( My excuses
 

Linux4

Senior Member
So honestly, I'm stuck now... I will assume that you know that to install TWRP you need to reboot straight into it after flashing and don't let it auto-reboot into recovery, as then LoS will override it with it's own one, just as stock ROM does. Maybe @Linux4 can help here?
I said it multiple times, TWRP is and will NEVER be supported and eventually you WILL FOR SURE run into issues by using it, that's why I force recovery update in all my unofficial ROMs in the first place
You can't access data from recovery anyway, just as it was always supposed to be.
What makes it get stuck and eventually causes that corrupt data warning is magisk tho, either use Lygisk as suggested in the OP or just reflash magisk now and all should be fine ...
Might as well be some gapps package with broken addon.d if MTG was not used.
 
  • Like
Reactions: sieghartRM

slytidar

Senior Member
May 31, 2012
430
53
I said it multiple times, TWRP is and will NEVER be supported and eventually you WILL FOR SURE run into issues by using it, that's why I force recovery update in all my unofficial ROMs in the first place
You can't access data from recovery anyway, just as it was always supposed to be.
What makes it get stuck and eventually causes that corrupt data warning is magisk tho, either use Lygisk as suggested in the OP or just reflash magisk now and all should be fine ...
Might as well be some gapps package with broken addon.d if MTG was not used.
anyway i can boot into my current rom ? i haven't wiped yet.
 
  • Like
Reactions: Linux4

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
    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...
    3
    Very nice work! The ROM is running smoth so far. Big THX @Linux4
    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.