• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM] LineageOS 17.1 for S10E/S10/S10+ Exynos

Search This thread

Mustermann_1

New member
Jun 13, 2021
2
0
Hej everybody,

I am still a beginner with custom ROMs and hope that you can help me. I read already the first 540 posts in that topic but couldn't find anybody with the same "problem" as me yet....I will continue reading but I hope to get a quicker answer by this post ;-).
It seems that everybody has installed Magisk and rooted the phone before he installed LOS (at least all instructions are written like that). I have a Samsung Galaxy S10e and installed first LOS 17.1 and everything works fine so far but I can't get the phone rooted properly.... I have installed TWRP and I have the Magisk app installed BUT Magisk itself is not installed and I don't know how to do it now to get the phone rooted :-(.
Can anybody please help me and tell me step by step what I have to do?
 

leaves-fly

New member
Jun 15, 2021
2
0
Hej everybody,

I am still a beginner with custom ROMs and hope that you can help me. I read already the first 540 posts in that topic but couldn't find anybody with the same "problem" as me yet....I will continue reading but I hope to get a quicker answer by this post ;-).
It seems that everybody has installed Magisk and rooted the phone before he installed LOS (at least all instructions are written like that). I have a Samsung Galaxy S10e and installed first LOS 17.1 and everything works fine so far but I can't get the phone rooted properly.... I have installed TWRP and I have the Magisk app installed BUT Magisk itself is not installed and I don't know how to do it now to get the phone rooted :-(.
Can anybody please help me and tell me step by step what I have to do?
Magisk boot images are provided in this google drive folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine
 

Mustermann_1

New member
Jun 13, 2021
2
0
@leaves-fly : Thank you for your quick answer :) but I have already TWRP installed. I did that totally at the beginning before I flashed LOS 17.1. And it seems that I am the only one who did the "wrong" order here because everyone here have flashed magisk first and rooted the phone and then flashed LOS 17.1 and at the end TWRP.....
Is now the only option to go totally back to stock (never did that before.....) and start in the right order again or is there another option from my point?
 

phaze3131

Senior Member
Feb 11, 2010
304
33
When I try to install this on my stock rooted s10 I get errors in my TWRP. Any help is greatly appreciated.
 

Attachments

  • 20210710_120518.jpg
    20210710_120518.jpg
    1.3 MB · Views: 14

phaze3131

Senior Member
Feb 11, 2010
304
33
is this thread full of bots saying this rom actually works? I'm so confused whats going on here.

Clearly the rom does not function with the rolled back twrp:
twrp-3.5.0_9-2-beyond1lte.img.tar . it will boot once and then that's it because if try to reboot recovery because your twrp is magisk flashed then you are out of luck and you wont get passed the samsung splash screen.

trying this twrp here just gets the phone booting to Downloading and you cannot do anything, you can't even enter TWRP


Its probably best to remove this spam bot filled thread because nothing works here
 
  • Haha
Reactions: cgirerd

Keule-Tm

Senior Member
Oct 3, 2016
353
136
Berlin
Samsung Galaxy S10
is this thread full of bots saying this rom actually works? I'm so confused whats going on here.

Clearly the rom does not function with the rolled back twrp:
twrp-3.5.0_9-2-beyond1lte.img.tar . it will boot once and then that's it because if try to reboot recovery because your twrp is magisk flashed then you are out of luck and you wont get passed the samsung splash screen.

trying this twrp here just gets the phone booting to Downloading and you cannot do anything, you can't even enter TWRP


Its probably best to remove this spam bot filled thread because nothing works here
Maybe you could stop whining. You show up here, claim to have followed the "directions absolutely perfectly" (which is obviously not the case*) and start to call names when not everybody jumps to your aid.

*) If you had read the OP thoroughly you would have noticed that there is no need to patch Magisk into TWRP, because a Magisk image is provided.
 

Keule-Tm

Senior Member
Oct 3, 2016
353
136
Berlin
Samsung Galaxy S10
is this thread full of bots saying this rom actually works? I'm so confused whats going on here.

Clearly the rom does not function with the rolled back twrp:
twrp-3.5.0_9-2-beyond1lte.img.tar . it will boot once and then that's it because if try to reboot recovery because your twrp is magisk flashed then you are out of luck and you wont get passed the samsung splash screen.

trying this twrp here just gets the phone booting to Downloading and you cannot do anything, you can't even enter TWRP


Its probably best to remove this spam bot filled thread because nothing works here
It's in the third post:
[…] Magisk boot images are provided within each device folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine […] Do note that you will have to reflash magisk boot image when updating rom.
(emphasis is mine).
 

phaze3131

Senior Member
Feb 11, 2010
304
33
It's in the third post:

(emphasis is mine).
Ok so a few things to know for people when they locate this thread and want to get going,

First, Ignore the idiot above me @Keule-Tm who claims I did not follow directions.

Secondly, The directions written out in the OP were meant to trick you and waste your time, maybe it was an april fools joke, I'm not sure. but honestly maybe at the time they might have possibly worked.

Lastly, follow these directions here and remember that the latest twrp to work with lineage 17.1 is this one:




1- Download BSL4 and patch AP file only with Magisk
2- Open patched AP file via 7zip and delete recovery.img file
3- Rename Compatible version of TWRP (Don't patch that file) to recovery.img and put that file into patched AP file with the help of 7zip
4- Open odin and put BL, AP (Patched File), CP and CSC or Home_CSC file
5- Uncheck Auto Reboot and Flash
6- Once done the go to TWRP recovery
7- Install multi-disabler 2.2
8- Format by time YES
9- Wipe Cache, Dalvink, Data and System
10- Flash ROM (if you want GApp then flash this after ROM flash without rebooting on first boot)
11- Once done reboot to SYSTEM not recovery
12- Do the setup without signing Google Account
13- Once complete then reboot to TWRP (With combo buttons)
14- Flash / install image file i.e beyond*lte-boot-magisk.img in TWRP by selecting ****Boot image*****
15- Reboot to system
16- Install magisk manager apk
17- Open and let it finish the first setup. It will reboot itself
18- Its done :p
 

Keule-Tm

Senior Member
Oct 3, 2016
353
136
Berlin
Samsung Galaxy S10
Ok so a few things to know for people when they locate this thread and want to get going,

First, Ignore the idiot above me @Keule-Tm who claims I did not follow directions.

Secondly, The directions written out in the OP were meant to trick you and waste your time, maybe it was an april fools joke, I'm not sure. but honestly maybe at the time they might have possibly worked.

Lastly, follow these directions here and remember that the latest twrp to work with lineage 17.1 is this one:




1- Download BSL4 and patch AP file only with Magisk
2- Open patched AP file via 7zip and delete recovery.img file
3- Rename Compatible version of TWRP (Don't patch that file) to recovery.img and put that file into patched AP file with the help of 7zip
4- Open odin and put BL, AP (Patched File), CP and CSC or Home_CSC file
5- Uncheck Auto Reboot and Flash
6- Once done the go to TWRP recovery
7- Install multi-disabler 2.2
8- Format by time YES
9- Wipe Cache, Dalvink, Data and System
10- Flash ROM (if you want GApp then flash this after ROM flash without rebooting on first boot)
11- Once done reboot to SYSTEM not recovery
12- Do the setup without signing Google Account
13- Once complete then reboot to TWRP (With combo buttons)
14- Flash / install image file i.e beyond*lte-boot-magisk.img in TWRP by selecting ****Boot image*****
15- Reboot to system
16- Install magisk manager apk
17- Open and let it finish the first setup. It will reboot itself
18- Its done :p
There you go! Disregarding your ad hominem you actually contributed something. Most of it was already in this thread (or the TWRP one), but nice write up.
Regarding directions: you yourself wrote about having a patched TWRP image.
You're welcome.
 

phaze3131

Senior Member
Feb 11, 2010
304
33
yes exactly it was in this thread just no where near the OP like it should have been but hopefully if idiots like you can stop posting nonsense then people can actually find the correct steps they must do to get this to work properly.

Yes I wrote about a patched rom image just like I should have and just like in the directions I posted which I will post here if you can refrain from tricking people by typing nonsense and deleting your posts.


1- Download BSL4 and patch AP file only with Magisk
2- Open patched AP file via 7zip and delete recovery.img file
3- Rename Compatible version of TWRP (Don't patch that file) to recovery.img and put that file into patched AP file with the help of 7zip
4- Open odin and put BL, AP (Patched File), CP and CSC or Home_CSC file
5- Uncheck Auto Reboot and Flash
6- Once done the go to TWRP recovery
7- Install multi-disabler 2.2
8- Format by time YES
9- Wipe Cache, Dalvink, Data and System
10- Flash ROM (if you want GApp then flash this after ROM flash without rebooting on first boot)
11- Once done reboot to SYSTEM not recovery
12- Do the setup without signing Google Account
13- Once complete then reboot to TWRP (With combo buttons)
14- Flash / install image file i.e beyond*lte-boot-magisk.img in TWRP by selecting ****Boot image*****
15- Reboot to system
16- Install magisk manager apk
17- Open and let it finish the first setup. It will reboot itself
18- Its done :p
 
  • Like
Reactions: sgtchocky

sgtchocky

Member
Mar 2, 2017
5
0
yes exactly it was in this thread just no where near the OP like it should have been but hopefully if idiots like you can stop posting nonsense then people can actually find the correct steps they must do to get this to work properly.

Yes I wrote about a patched rom image just like I should have and just like in the directions I posted which I will post here if you can refrain from tricking people by typing nonsense and deleting your posts.


1- Download BSL4 and patch AP file only with Magisk
2- Open patched AP file via 7zip and delete recovery.img file
3- Rename Compatible version of TWRP (Don't patch that file) to recovery.img and put that file into patched AP file with the help of 7zip
4- Open odin and put BL, AP (Patched File), CP and CSC or Home_CSC file
5- Uncheck Auto Reboot and Flash
6- Once done the go to TWRP recovery
7- Install multi-disabler 2.2
8- Format by time YES
9- Wipe Cache, Dalvink, Data and System
10- Flash ROM (if you want GApp then flash this after ROM flash without rebooting on first boot)
11- Once done reboot to SYSTEM not recovery
12- Do the setup without signing Google Account
13- Once complete then reboot to TWRP (With combo buttons)
14- Flash / install image file i.e beyond*lte-boot-magisk.img in TWRP by selecting ****Boot image*****
15- Reboot to system
16- Install magisk manager apk
17- Open and let it finish the first setup. It will reboot itself
18- Its done :p
If that is an answer for me, thank you!

I have tried many stock firmwares to patch (AP), but always getting the same message on device screen, that the device bootloader is 11 and cannot flash lower version things. Honestly, I did not tried with BSL4. Will do that.

One more question:
Step 3, you mention "compatible version" of twrp. Do you mean to compatible with BSL4? Because it is the 3.5.0_9, right?
 

sgtchocky

Member
Mar 2, 2017
5
0
yes please use this twrp here because the lastest ones do not work with android 10 :
twrp-3.5.0_9-2-beyond1lte.img.tar
Okay. Now, I have tried with BSL4 without luck.

Facts:
I have G975F/DS
I am on Android 11, FUE. Latest stock rom. XEH.
Bootloader unlocked (greyed out in developer options)

I did the AP patch with Magisk and used the 3.5.0_9-2 twrp, both beyond2lte and beyond1lte.
Those twrp's was not patched with Magisk. Just dropped them into the AP with 7zip.

I have used Odin 3.14.1 and 3.14.4.

None of them worked.

Error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE 11, BINARY: 3
pit_flash_binary - Unsupported Version.

I think the problem is that I am already on Android 11. (Edit: I think the downgrade is not supported by samsung)
Any clue?
 
Last edited:

phaze3131

Senior Member
Feb 11, 2010
304
33

Okay. Now, I have tried with BSL4 without luck.

Facts:
I have G975F/DS
I am on Android 11, FUE. Latest stock rom. XEH.
Bootloader unlocked (greyed out in developer options)

I did the AP patch with Magisk and used the 3.5.0_9-2 twrp, both beyond2lte and beyond1lte.
Those twrp's was not patched with Magisk. Just dropped them into the AP with 7zip.

I have used Odin 3.14.1 and 3.14.4.

None of them worked.

Error:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE 11, BINARY: 3
pit_flash_binary - Unsupported Version.

I think the problem is that I am already on Android 11. (Edit: I think the downgrade is not supported by samsung)
Any clue?
I can't be sure because I know nothing about it but I know once you go to a certain level android 10 bootloader you cannot go back to android 9 bootloader. Maybe it's the same with android 11 and android 10. You might be stuck going to the next lineage os that is made for android 11. Also I was not aware our related devices received ota update to android 11, that's cool

also disregard me telling you to use beyond1lte if you do not have the s10 g973f because that is what it is for. Please read the twrp thread to figure out which twrp you should be using and ask there if you are not sure. Often times it is not the "latest" one depending on what bootloader you have

 
Last edited:
  • Like
Reactions: sgtchocky

sgtchocky

Member
Mar 2, 2017
5
0
I can't be sure because I know nothing about it but I know once you go to a certain level android 10 bootloader you cannot go back to android 9 bootloader. Maybe it's the same with android 11 and android 10. You might be stuck going to the next lineage os that is made for android 11. Also I was not aware our related devices received ota update to android 11, that's cool

also disregard me telling you to use beyond1lte if you do not have the s10 g973f because that is what it is for. Please read the twrp thread to figure out which twrp you should be using and ask there if you are not sure. Often times it is not the "latest" one depending on what bootloader you have

Np man. I really appreciate your effort to helping me.

As I see now, no chance to put any kind of twrp to S10+ if you are on latest Android 11.
Official twrp images only support the ETL stock ROMs, but if you are on latest, no chance as Samsung deny the downgrade.

The picture shows the stock ROMs after ETL.
It is for my country code XEH.

Capture.PNG
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    is this thread full of bots saying this rom actually works? I'm so confused whats going on here.

    Clearly the rom does not function with the rolled back twrp:
    twrp-3.5.0_9-2-beyond1lte.img.tar . it will boot once and then that's it because if try to reboot recovery because your twrp is magisk flashed then you are out of luck and you wont get passed the samsung splash screen.

    trying this twrp here just gets the phone booting to Downloading and you cannot do anything, you can't even enter TWRP


    Its probably best to remove this spam bot filled thread because nothing works here
    1
    yes exactly it was in this thread just no where near the OP like it should have been but hopefully if idiots like you can stop posting nonsense then people can actually find the correct steps they must do to get this to work properly.

    Yes I wrote about a patched rom image just like I should have and just like in the directions I posted which I will post here if you can refrain from tricking people by typing nonsense and deleting your posts.


    1- Download BSL4 and patch AP file only with Magisk
    2- Open patched AP file via 7zip and delete recovery.img file
    3- Rename Compatible version of TWRP (Don't patch that file) to recovery.img and put that file into patched AP file with the help of 7zip
    4- Open odin and put BL, AP (Patched File), CP and CSC or Home_CSC file
    5- Uncheck Auto Reboot and Flash
    6- Once done the go to TWRP recovery
    7- Install multi-disabler 2.2
    8- Format by time YES
    9- Wipe Cache, Dalvink, Data and System
    10- Flash ROM (if you want GApp then flash this after ROM flash without rebooting on first boot)
    11- Once done reboot to SYSTEM not recovery
    12- Do the setup without signing Google Account
    13- Once complete then reboot to TWRP (With combo buttons)
    14- Flash / install image file i.e beyond*lte-boot-magisk.img in TWRP by selecting ****Boot image*****
    15- Reboot to system
    16- Install magisk manager apk
    17- Open and let it finish the first setup. It will reboot itself
    18- Its done :p
    1
    yes please use this twrp here because the lastest ones do not work with android 10 :
    twrp-3.5.0_9-2-beyond1lte.img.tar
    1

    Okay. Now, I have tried with BSL4 without luck.

    Facts:
    I have G975F/DS
    I am on Android 11, FUE. Latest stock rom. XEH.
    Bootloader unlocked (greyed out in developer options)

    I did the AP patch with Magisk and used the 3.5.0_9-2 twrp, both beyond2lte and beyond1lte.
    Those twrp's was not patched with Magisk. Just dropped them into the AP with 7zip.

    I have used Odin 3.14.1 and 3.14.4.

    None of them worked.

    Error:
    SW REV. CHECK FAIL(BOOTLOADER) DEVICE 11, BINARY: 3
    pit_flash_binary - Unsupported Version.

    I think the problem is that I am already on Android 11. (Edit: I think the downgrade is not supported by samsung)
    Any clue?
    I can't be sure because I know nothing about it but I know once you go to a certain level android 10 bootloader you cannot go back to android 9 bootloader. Maybe it's the same with android 11 and android 10. You might be stuck going to the next lineage os that is made for android 11. Also I was not aware our related devices received ota update to android 11, that's cool

    also disregard me telling you to use beyond1lte if you do not have the s10 g973f because that is what it is for. Please read the twrp thread to figure out which twrp you should be using and ask there if you are not sure. Often times it is not the "latest" one depending on what bootloader you have

  • 109
    k5tUT1V.png

    LineageOS 17.1 for Galaxy S10 Series

    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */


    Working:
    - Wifi
    - Sound
    - mali drivers
    - USB tethering
    - Video Playback
    - Fingerprint Sensor
    - Ril (Mobile data,calls, sms and stuff)
    - Sensors
    - Bluetooth
    - Wifi HotSpot
    - MTP
    - 2D and 3D gpu acceleration
    - HW encoding/decoding
    - GPS
    - Cameras (All of them)
    - HWcomposer (HWC)
    - Signal indicator
    - Double tap to wake
    - Wireless PowerShare

    Not Working
    - VoLTE and VoWiFi will not be implemented (for now) as they heavily depand on samsungs framework


    To properly report a bug (Please dont report things already on the Not Working list)
    a) Logcat
    b) /proc/last_kmsg (or /proc/kmsg)
    c) /data/tombstones
    d) dmesg

    Please do not report bugs if you have performed any system modifications excluding gapps installation



    Installation instructions


    Make sure you are on Q stock firmware (All of the Q firmwares are tested and confirmed to be working, This should be the case with new fws too as long as Samsung doesnt significantly change bootloader trustzone bits)
    Download Q twrp from this thread
    flash twrp as per given instructions
    if you are coming from stock and have encryption enabled format data (Note i said format, Wiping it in twrp is not the same as formating it)
    wipe cache, dalvik cache and system
    flash LineageOS
    If you want to have gapps flash them right after flashing the rom before first booting
    Reboot the device

    Downloads:
    Google drive
    Mega.nz
    (Select build coresponding to your devices codename, S10e = beyond0lte | s10 = beyond1lte | s10+ = beyond2lte)
    sha256 checksums

    Code:
    93ca94478bd8fa8e95fd513d8aae82b8e3aa0d21484e31ba2098c1e5e6693990  lineage-17.1-20210112-UNOFFICIAL-beyond2lte.zip
    afb505986373bbeb10ade91f67765d800f504a933c6b94d88c4013382ab32270  lineage-17.1-20210112-UNOFFICIAL-beyond1lte.zip
    06a334e091bdaac91f6c64559b5c9746559178facc7364b5676c39ddaa826a18  lineage-17.1-20210112-UNOFFICIAL-beyond0lte.zip
    
    4668a9cc55f6135403120370e668548a  beyond2lte-boot-magisk.img
    4954c5f2cbedbc2bbd90362745d93a1d  beyond1lte-boot-magisk.img
    84ec49e64560477e1df87417dbc4890e  beyond0lte-boot-magisk.img


    If you need general help or questions feel free to join Telegram group

    Gapps
    READ BEFORE INSTALLING MAGISK

    I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
    if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler





    Based On Android Q
    Changelog

    01.12.2021.
    - Merged january security update
    - Updated magisk boot image to magisk 21.2
    - Misc performance and security updates

    12.12.2020.
    -Merged december security update
    - Merged december vendor security update
    - Updated magisk images to 21.1
    - Synced with los source

    11.09.2020.
    - Updated vendor to XXU9DTJA
    - Switched to more calibrated sensor for Adaptive Brightness
    - Merged November 2020. Security update
    - Synced with LOS source

    10.08.2020.
    - Updated vendor to FXXS9DTI8
    - Fixed camera and bt issues present in previous build
    - Merged october 2020 security update
    - Synced with LOS source
    - Updates magisk images to latest canary build (turns out it was more stable than beta version)

    09.10.2020.
    - Merged OneUI 2.5 Kernel and vendor (DTH7)
    - Enabled 5GHz tethering
    - Updated Magisk images
    - Merged September 2020 Security update
    - Tuned little core optimizations
    - Enabled vibrator intensity control (under accesibility)
    - Misc performance and stability improvements
    - Synced with LOS source

    08.05.2020.
    - Imported G97*FXXU8CTG4 vendor changes
    - Merged August 2020 system and vendor security updates
    - Improved system security and stability
    - Synced with LOS source (Check out new extended volume panel)


    07.08.2020.
    - Imported G97*FXXS7CTF3 vendor changes
    - Merged July 2020 security update for both system and vendor
    - Misc performance and stability improvements

    06.11.2020.
    - Merged G97*FXXU7CTF1 kernel source
    - Imported G97*FXXU7CTF1 vendor changes
    - Removed proximity from always on display (again)
    - Updated magisk images to G97*FXXU7CTF1
    - Camera and wifi stability and performance improvements
    - HWC stability and performance improvements
    - Fixed issue where USB tethering under linux would cause kernel panic
    - Synced with LOS source

    06.03.2020.
    - Merged June 2020 System security patch
    - Merged June 2020 Vendor security patch (G97*FXXU3ASJD)
    - Improved completely back theme
    - Misc performance improvements
    - Synced with LOS source

    05.21.2020.
    - Fixed DT2W on AOD
    - Added completely black theme (You can access it thru styles settings entry)
    - Removed blinking proximity sensor from AOD
    - Added usb trust hal that can prevent usb devices from being used if plugged in while device is locked
    - Exposed mdnie screen tuning modes
    - Moved pin entry area above fingerprint on s10 and s10+ so they dont overlap with sensor
    - Cleaned up DT2W implementation
    - Added high touch sensitivity mode (Glove mode) (This can also help when using screen protectors)
    - Implemented mDNIe powered color calibration (Settings>Display>LiveDisplay)
    - Implemented color profiles so you can use natural colors if you wish to do so (Settings>Display>LiveDisplay)
    - Next update should add even more color modes powered by mDNIe like negative and greyscale
    - Updated magisk kernel images
    - Synced with LOS source

    05.15.2020
    - Fixed boot on latest CTD1 firmware
    - added ctd1 dtbo
    - exposed all camera instances to external apps
    - started working on HRM sensor
    - merged CTD1 kernel source
    - updated magisk images
    - misc performance and stability improvements

    05.05.2020.
    - Merged G97*FXXS5CTD1 blobs with may 2020 security update
    - Merged may 2020 system security update
    - Fixed usb tethering issues

    04.14.2020.
    - Fixed significant motion sensor detection
    - merged April system security update
    - Added vbmeta into the zip
    - Removed unused radio(ril) interfaces
    - Merged Note and s10 5g kernels into same tree for easier maintanance
    - Switched to source built dtbo
    - Updated magisk kernel images

    03.31.2020.
    - April vendor security update (System is still march as april tags havent been released on aosp yet)
    - Rebased kernel on top of G97*FXXU4CTC9
    - Added dt and dtbo images to rom
    - merged G97*FXXU4CTC9 vendor binaries
    - Removed simstat service as samsung fixed dual sim device detection
    - Updated boot images to Magisk 20.4
    - Misc performance and stability improvements

    03.03.2020.
    - Merged march system security update
    - Merged latest feature drop
    - Synced with los source
    - merged G97*FXXS4BTB3 vendor binaries

    02.27.2020.
    - Fixed camera cutout on S10
    - Enabled proximity sensor in all apps with proper permissions
    - Rewrote sensor impl
    - Removed unused parts of lights hal
    - Added vendor to the build (This is why rom is larger now)
    - Cleaned up lights overlays and power hal handling
    (This means vendor partition also gets built from source and can be more customized per aosp needs
    instead of relaying on bind mounting over existing drivers)

    02.19.2020.
    - Fixed BT calls on some devices that had issues with WBS
    - Fixed issue where on clean install or after factory reset there were no default notification sounds and ringtones set
    - Synced with LOS source

    02.11.2020
    - Merged 4BTA8 kernel source
    - Merged February security update
    - Fixed MTP/USB tethering while ADB is enabled
    - Synced with LOS source

    02.05.2020.
    - Rebased kernel on top of samsungs G975FXXU3BSKO source
    - Fixed kernel not properly reporting deep sleep state to userspace
    - Reimplemented sensor reporting to allow access to proximity sensor to more apps
    - Updated build fingerprint to Q one
    - Updated TARGET_BOARD_PLATFORM flag to reflect samsungs changes to same
    - Removed releasetools which was failing on new-ish twrp releases anyway
    - Removed P vndk libs
    - Fixed power hal race condition
    - Fixed manual network selection
    - Performance and stability improvements

    26.11.2019.
    - Added FOD icons for S10 and S10+
    (This will show up any time system or app needs to use fp sensor and will help users locate the sensor)
    - Fixed detection of dual sim devices
    - Misc performance and stability improvements

    20.11.2019.
    - Initial public release



    XDA:DevDB Information
    [ROM] LineageOS 17.1 for S10E/S10/S10+ Exynos , ROM for the Samsung Galaxy S10

    Contributors
    Ivan_Meler
    Source Code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/tree/lineage-17.1

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Any stock Q firmware, Latest is recommended

    Version Information
    Status:
    Stable
    Current Stable Version: 1.7.5
    Stable Release Date: 2020-11-09

    Created 2019-11-20
    Last Updated 2020-11-09
    41
    Reserved

    Magisk boot images are provided within each device folder named beyond*lte-boot-magisk.img you can flash them on boot slot and install magisk manager, No need to worry about rebooting to recovery or not having TWRP and magisk at the same time, Just make sure you dont try to boot to system with magisk patched TWRP as that might cause issues but as long as you have stock twrp and have flashed beyond*lte-boot-magisk.img image to boot slot you are fine, Source for given kernel is available at GitHub if you want to compile kernel yourself just run source build.sh devicename e.g. source build.sh beyond2lte, It will produce new boot image in build/ folder, To update magisk you can follow instructions given at this commit enjoy

    Do note that you will have to reflash magisk boot image when updating rom
    37
    New build is up sorry for delays on this one but there was weird bug caused by samsungs power hal which took way longer than it should to be fixed, Magisk is independent of recovery as promised you can read more info about it in 3rd post on main page, There are a lot of other smaller improvements all around, Rest of the source for developers to compile other roms will be up soon (Just doing some final cleanup of proprietary bits and pieces)

    Also big thanks to anyone who supported this project by covering build server cost and stuff and I'm really sorry for delays with this build but things should be pretty straightforward from this point
    30
    Reserved

    Reserved
    28
    New update is almost ready for release from extensive testing i only noticed 1 small issue that needs to be fixed before release(that being sec power hal)

    And more great news is that you won't need any custom recovery for magisk root anymore as it will reside within boot images for those that want to use it, that also means there won't be need to reboot to recovery/hold key combo to boot rooted with magisk