[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread

bertino

Senior Member
Oct 17, 2014
270
96
Great,

Thank you! Question: How do you include vendor files from android_vendor_samsung_exynos9820-common? I dont want to pull those files from the phone but from the repository instead. Any idea on that?

Just add add the vendor repos for the devices you need to the roomservice.xml like this:
XML:
    <project name="exynos9820-dev/android_vendor_samsung_beyond1lte" path="vendor/samsung/beyond1lte" remote="github" revision="lineage-18.1" />
    <project name="exynos9820-dev/android_vendor_samsung_exynos9820-common" path="vendor/samsung/exynos9820-common" remote="github" revision="lineage-18.1" />
 
  • Like
Reactions: wora92

WalterCool

Senior Member
Jan 15, 2012
144
30
Code:
<project name="LineageOS/android_device_samsung_slsi_sepolicy" path="device/samsung_slsi/sepolicy" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_samsung_nfc" path="hardware/samsung/nfc" remote="github" revision="lineage-18.1" />

<project name="exynos9820-dev/android_device_samsung_beyond1lte" path="device/samsung/beyond1lte"  remote="github" revision="lineage-18.1" />
<project name="exynos9820-dev/android_device_samsung_exynos9820-common" path="device/samsung/exynos9820-common" remote="github" revision="lineage-18.1" />
<project name="exynos9820-dev/android_kernel_samsung_exynos9820" path="kernel/samsung/exynos9820" remote="github" revision="lineage-18.1" />
Just added the NFC repo, latest changes require that.
 
  • Like
Reactions: wora92

WalterCool

Senior Member
Jan 15, 2012
144
30
Great,

Thank you! Question: How do you include vendor files from android_vendor_samsung_exynos9820-common? I dont want to pull those files from the phone but from the repository instead. Any idea on that?
You don't need to do that.

If you are at Linux and you have the original ROM file from Samsung (sammobile.com), then:
- Extract AP_ .tar.md5 file
- Extract system + vendor images
- Convert SIMG to IMG the images (https://github.com/anestisb/android-simg2img)
- Mount system img at some place, and vendor img at system/vendor
- Inside system mount point, run chmod o+r init.*.rc
- Go to LineageOS project, then device/samsung/beyond1lte/ folder
- Run ./extract-files.sh <path-to-your-mounted-system>

I personally disagree the idea of using blobs from "some version" as they could create incompatibilities with your current phone ones, but up to you. You can always use the repositories mentioned above.

Sadly blobs are what they are, just mere files no one in hell knows what they do, it should be a good practice to match your phone vendor.img version with system/vendor blobs version.
 
  • Like
Reactions: wora92

wora92

Senior Member
Sep 19, 2019
76
29
You don't need to do that.

If you are at Linux and you have the original ROM file from Samsung (sammobile.com), then:
- Extract AP_ .tar.md5 file
- Extract system + vendor images
- Convert SIMG to IMG the images (https://github.com/anestisb/android-simg2img)
- Mount system img at some place, and vendor img at system/vendor
- Inside system mount point, run chmod o+r init.*.rc
- Go to LineageOS project, then device/samsung/beyond1lte/ folder
- Run ./extract-files.sh <path-to-your-mounted-system>

I personally disagree the idea of using blobs from "some version" as they could create incompatibilities with your current phone ones, but up to you. You can always use the repositories mentioned above.

Sadly blobs are what they are, just mere files no one in hell knows what they do, it should be a good practice to match your phone vendor.img version with system/vendor blobs version.
Thanks for this little tutorial. I agree - it sounds most reasonable to pull those files from the original ROM. However, this seems like a lot of effort every month. I dont want to put so much time into my phone. Too bad nobody takes over S10 maintenance, I'd love to see an official build.
 
  • Like
Reactions: WalterCool

Spyop3

Member
Jun 29, 2010
26
8
Samsung Galaxy S10e
I managed to patch the system in order to enable signature spoofing for MicroG by following this guide. Here is a zip file I created for my s10e with a patched services.jar one must flash via Magisk.

With the latest update of the ROM I get stuck on loading lineage screen with this module activated in Magisk maybe need an update

@flortsch Do you have the same problem ?

If you have same problem you can try this version I just made based on @flortsch linked tuto

And it works fine for me :)
 

Attachments

  • spoof_s10e_120621.zip
    7.4 MB · Views: 23
Last edited:

wora92

Senior Member
Sep 19, 2019
76
29
@Linux4

I just pulled your sources and tried to build the ROM. It fails with this error, any idea what that means?

Code:
[  0% 8/63977] build out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy
FAILED: out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c         30 -o out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp out/t
arget/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_
intermediates/sepolicy.tmp permissive > out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s out/target/
product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ]; then         echo \"==========\" 1>&2;         echo \"ERROR: permissive domains not allowed i
n user builds\" 1>&2;         echo \"List of invalid domains:\" 1>&2;         cat out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains 1
>&2;         exit 1;         fi ) && (mv out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp out/target/product/beyond0lte/obj/ETC/sepolicy.recovery
_intermediates/sepolicy )"
device/samsung_slsi/sepolicy/common/vendor/genfs_contexts:43:ERROR 'duplicate entry for genfs entry (sysfs, /devices/virtual/sec/tsp/input/enabled)' at token 'genfscon' on line 67240:
genfscon sysfs /devices/virtual/sensor_event                              u:object_r:sysfs_sensors:s0
genfscon sysfs /devices/virtual/sec/tsp/input/enabled                     u:object_r:sysfs_touchscreen_writable:s0
checkpolicy:  error(s) encountered while parsing configuration
[  0% 15/63977] build out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c         30 -o out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_never
allows.tmp out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/beyond0lte/obj/FAKE/sepolicy
_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/policy_2.conf ||       ( echo \"\" 1>&2;     
   echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2;         echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2;         echo \"the policy.
\" 1>&2;         exit 1 ) ) && (touch out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/beyond0lte/obj/FAKE/se
policy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/samsung_slsi/sepolicy/common/vendor/genfs_contexts:43:ERROR 'duplicate entry for genfs entry (sysfs, /devices/virtual/sec/tsp/input/enabled)' at token 'genfscon' on line 63255:
genfscon sysfs /devices/virtual/sensor_event                              u:object_r:sysfs_sensors:s0
genfscon sysfs /devices/virtual/sec/tsp/input/enabled                     u:object_r:sysfs_touchscreen_writable:s0
checkpolicy:  error(s) encountered while parsing configuration
[  0% 19/63977] Building Kernel Config
make: Entering directory '/build/Downloads/build/lineageos/repo/kernel/samsung/exynos9820'
make[1]: Entering directory '/build/lineageos/repo/out/target/product/beyond0lte/obj/KERNEL_OBJ'
  GEN     ./Makefile
 

Linux4

Senior Member
@Linux4

I just pulled your sources and tried to build the ROM. It fails with this error, any idea what that means?

Code:
[  0% 8/63977] build out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy
FAILED: out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c         30 -o out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp out/t
arget/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_
intermediates/sepolicy.tmp permissive > out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s out/target/
product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ]; then         echo \"==========\" 1>&2;         echo \"ERROR: permissive domains not allowed i
n user builds\" 1>&2;         echo \"List of invalid domains:\" 1>&2;         cat out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains 1
>&2;         exit 1;         fi ) && (mv out/target/product/beyond0lte/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp out/target/product/beyond0lte/obj/ETC/sepolicy.recovery
_intermediates/sepolicy )"
device/samsung_slsi/sepolicy/common/vendor/genfs_contexts:43:ERROR 'duplicate entry for genfs entry (sysfs, /devices/virtual/sec/tsp/input/enabled)' at token 'genfscon' on line 67240:
genfscon sysfs /devices/virtual/sensor_event                              u:object_r:sysfs_sensors:s0
genfscon sysfs /devices/virtual/sec/tsp/input/enabled                     u:object_r:sysfs_touchscreen_writable:s0
checkpolicy:  error(s) encountered while parsing configuration
[  0% 15/63977] build out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c         30 -o out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_never
allows.tmp out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/beyond0lte/obj/FAKE/sepolicy
_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/policy_2.conf ||       ( echo \"\" 1>&2;    
   echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2;         echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2;         echo \"the policy.
\" 1>&2;         exit 1 ) ) && (touch out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/beyond0lte/obj/FAKE/se
policy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/beyond0lte/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/samsung_slsi/sepolicy/common/vendor/genfs_contexts:43:ERROR 'duplicate entry for genfs entry (sysfs, /devices/virtual/sec/tsp/input/enabled)' at token 'genfscon' on line 63255:
genfscon sysfs /devices/virtual/sensor_event                              u:object_r:sysfs_sensors:s0
genfscon sysfs /devices/virtual/sec/tsp/input/enabled                     u:object_r:sysfs_touchscreen_writable:s0
checkpolicy:  error(s) encountered while parsing configuration
[  0% 19/63977] Building Kernel Config
make: Entering directory '/build/Downloads/build/lineageos/repo/kernel/samsung/exynos9820'
make[1]: Entering directory '/build/lineageos/repo/out/target/product/beyond0lte/obj/KERNEL_OBJ'
  GEN     ./Makefile
You need https://review.lineageos.org/c/LineageOS/android_device_samsung_gta4xl-common/+/312245

Sorry, didn't yet pick it to 9820, will do it later today
 
  • Like
Reactions: wora92

flortsch

Member
Sep 10, 2014
34
30
Linz
florian-latifi.at
With the latest update of the ROM I get stuck on loading lineage screen with this module activated in Magisk maybe need an update

@flortsch Do you have the same problem ?

If you have same problem you can try this version I just made based on @flortsch linked tuto

And it works fine for me :)
I did not update yet, but you warned me, so I think I will disable mine and install yours after updating :p

How did you deactivate the bad module when you got stuck in the boot loop?
 

starbright_

Senior Member
Apr 11, 2010
1,313
217
Hi @flortsch and @Spyop3:
I am in same situation, have this ROM (May), spoofed to work with microG and with Magisk(23.0). So what are the steps to do?
At the moment I have 3 Magisk modules:
- Dolby Atmos
- microG installer
- spoof_AVDapi30

So what to do?
- disable Modules ?
- update OVT (both ROM and Recovery?)
and how to get Magisk and its modules running again?
 

flortsch

Member
Sep 10, 2014
34
30
Linz
florian-latifi.at
Hi @flortsch and @Spyop3:
I am in same situation, have this ROM (May), spoofed to work with microG and with Magisk(23.0). So what are the steps to do?
At the moment I have 3 Magisk modules:
- Dolby Atmos
- microG installer
- spoof_AVDapi30

So what to do?
- disable Modules ?
- update OVT (both ROM and Recovery?)
and how to get Magisk and its modules running again?
Remove the old spoof module in Magisk app, update the rom, reboot into recovery, sideload the Magisk apk, reboot into system, install the new spoof module via Magisk app, reboot again.
 
Last edited:
  • Like
Reactions: starbright_

starbright_

Senior Member
Apr 11, 2010
1,313
217
Remove the old spoof module in Magisk app, update the rom, reboot into recovery, sideloaded the Magisk apk, reboot into system, install the new spoof module via Magisk app, reboot again.
Did this but update hangs in the around 95% :(

I need to do a force reboot (Volume- & power). After that it seems to finish installation.
Installation of spoof app wasn't enough, also the microG installer. And I added Atmos again.

So far it looks good. Many thanks to the dev(s) and helpers.
 
Last edited:

Spyop3

Member
Jun 29, 2010
26
8
Samsung Galaxy S10e
I did not update yet, but you warned me, so I think I will disable mine and install yours after updating :p

How did you deactivate the bad module when you got stuck in the boot loop?
Since couple of version magisk disable all modules when you boot in safe mode (hold volume down while booting), that's what got me thinking it was the spoof

After, just sideload magisk again in recovery to disable all the modules for normal boot cause in safe mode you can not interact with apps :)
 

Gigantkiller

Member
Jan 22, 2019
9
0
Hello,
i was using S10+ stock with root and magisk and twrp for the last years. Today i flashed Lineago OS recorvery like descripted, but i can't access recovery with Volume up, power and bixby. it just shows the red message. So i flashed https://androidfilehost.com/?w=files&flid=315865 in the hope to make it work, and reflashed LineageOS recorvery like descripted here. Now it's just staring over and over again Black Screen, vibrating, Boot Screen with Warning message, Device Name and green android logo., black screen, every 5 seconds or so) Any help possible?

Edit: in the top left corner there is writen in a text box:
Rev. Check Fail. Device: 8, Binary:2 (DTBO)
 

Linux4

Senior Member
Hello,
i was using S10+ stock with root and magisk and twrp for the last years. Today i flashed Lineago OS recorvery like descripted, but i can't access recovery with Volume up, power and bixby. it just shows the red message. So i flashed https://androidfilehost.com/?w=files&flid=315865 in the hope to make it work, and reflashed LineageOS recorvery like descripted here. Now it's just staring over and over again. Any help possible?

Edit: in the top left corner there is writen in a text box:
Rev. Check Fail. Device: 8, Binary:2 (DTBO)
You were on Pie firmware before by any chance?
Also on download page there's a link "Firmware update" you could try with this
 
  • Like
Reactions: Gigantkiller

Gigantkiller

Member
Jan 22, 2019
9
0
You were on Pie firmware before by any chance?
Also on download page there's a link "Firmware update" you could try with this
Hello, thanks for the reply. I was on stock firmware of new phone (bought august 2019 or so)

Where to mean "download page/ firmware update?"
Thank you very much.

Forgot to mention: Bootloader is unlocked, as i used Magisk and TWRP the last years

PS: i'm just downloading https://www.sammobile.com/samsung/g.../SM-G9758/CHM/download/G9758ZMS5FUE4/1550225/, hope that brings any help
 
Last edited:

Linux4

Senior Member
Hello, thanks for the reply. I was on stock firmware of new phone (bought august 2019 or so)

Where to mean "download page/ firmware update?"
Thank you very much.

Forgot to mention: Bootloader is unlocked, as i used Magisk and TWRP the last years

PS: i'm just downloading https://www.sammobile.com/samsung/g.../SM-G9758/CHM/download/G9758ZMS5FUE4/1550225/, hope that brings any help

This is what I meant
But actually noticed your model is SM-G9758 and not SM-G975F, is that even exynos? And I don't think it has been tested before
I actually don't know if it would be a good idea to flash SM-G975F firmware I linked to above
 

Gigantkiller

Member
Jan 22, 2019
9
0

This is what I meant
But actually noticed your model is SM-G9758 and not SM-G975F, is that even exynos? And I don't think it has been tested before
I actually don't know if it would be a good idea to flash SM-G975F firmware I linked to above
Hello,

i think i downloaded the wrong firmware. My model is exynos s10+ dual sim card. SO probably, your link is right and my download wrong.

I flashed the firmware you linked, still boot-loop. Then i flashed the lineageos recovery, still bootloop. Both times in the odin ap slot. ( I build the recovery.tar like the description says at the beginning of this thread)

Message changed: Check Fail. Device: 11, Binary:8 (DTB)
 
Last edited:

Linux4

Senior Member
Hello,

i think i downloaded the wrong firmware. My model is exynos s10+ dual sim card. SO probably, your link is right and my download wrong.

I flashed the firmware you linked, still boot-loop. Then i flashed the lineageos recovery, still bootloop. Both times in the odin ap slot. ( I build the recovery.tar like the description says at the beginning of this thread)

Message changed: Check Fail. Device: 11, Binary:8 (DTB)
Extract dtb.img from my latest LineageOS build, pack it into a .tar flash that (I think for making Odin flash it you will need to rename it to dt.img and then pack it into a tar archive), should resolve that issue.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6

    Official support for the s10 and note 10 family is coming soon! thanks linux4
    3
    Some note about OTA update of this ROM. This is fairly easy (only italic steps below).
    But I am using Magisk/microg - with that some additional steps are required - all is listed below. Don't be afraid, it is done in less than 5 minutes.

    * Make sure your firewall allows the "Updater"
    * If you uses Magisk, download the apk and rename it to zip and put it to SDcard (otherwise a PC is needed for sideload - see below)
    * Go to Settings/System/Extended/Updater
    * Search for update and download

    * I recommend disable data traffic now until the FW-update is completed and microG/firewall is operational again, otherwise your system might be open for some time.
    * start update

    Device will boot into recovery and does the upgrade. It seems that the update is not completely finished in case of Magisk is installed. In this case force a restart by "Vol- + Power" for a few seconds if update hangs at around 95% (can bee roughly seen in the timeline)

    * After update has finished: boot again to recovery
    * Now Either
    a) just do the update with already downloaded Magisk.zip (Apply Update/Update from SD_card) or
    b) Enable ADB sideload by Apply Update/Apply from ADB and do an adb sideload from PC of Magisk.apk or zip (no matter here)
    * boot into system
    * in case of microG check (and give if required) microG give all the required permissions
    * If all is set and done you can enable data connection again

    On thing I was thinking about:
    There are is one module needed for spoofing (spoof_AVDapi30). I found that an update of it is not required. Not sure whether this will be the case for other updates of 18.1 too, but keep an eye on it.
    Enjoy the ROM and thanks to @Linux4
    2
    Hi @Linux4

    Thank you for your work.

    Briefly, for beyond0lte there was a release on LOS Official https://download.lineageos.org/beyond0lte it seems to be pulled down as it;s not available anymore.

    While it was available, I installed successfully. What would I need to do once the Official release is back up again? or will I just need to do a normal update via System > Updater, thanks

    Red.

    Updating via Updater will work.
    1
    Hi folks. It's me again, the one guy who kept complaining about random resets. I finally figured out how to prevent this from happening.

    I primarily use wireless charging for charging the device and let the device "be" for hours on it. Most things I can access through my PC (e-mail, calls, whatsapp, etc). When it is on this charger the device used to randomly reset every now and then.

    After installing ACC:
    And setting a config using ACCA:
    To 5-85-90 (shutdown, start, stop) I no longer got resets.

    It seems that the random resets have to do with the battery being near full and being on a wireless charger.

    Is there anyone else who can test this?

    For me this is an acceptable solution as I wanted to have ACC anyways to improve battery life.
    1
    Ah sorry didn't notice your edit until now
    Maybe try on telegram (group link is in OP) or in pm here on xda?
    Since the OTA I've done yesterday I haven't seen it happen again. Maybe that fixed it?
    I'll send you the kmsg if it happens again.
  • 35
    1607247455067.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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: https://github.com/exynos9820-dev
    13
    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 magisk 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!
    13
    Features

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

    Known issues

    • Miracast not working (Google removed it in AOSP Pie)
    • VoLTE/VoWiFi
    • You tell me
    7
    LOS 18.1 for our S10 device? SELinux enforcing? FBE? Open-source device tree? Where can I donate for this awesome work?
    6
    Update on feedback on the ROM, its been a couple of days, and this is easily my daily driver. Only issue I encountered was through Gapps not having the dialer app set as the default. Bizarrely the dialer was still semi functional. The finger print sensor is now fixed as well.

    This is a an easy successor to ModPunks great work, and I hope that Linux4 finds the time to become a maintainer for our device. Thanks for the great work