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

Search This thread

OneCCART

New member
Dec 9, 2019
3
0
Magisk guide has been posted here make sure you read it and understand what you are doing before installing it, also do not post any bug reports if you are running any magisk modules that might have caused them

Thanks to Ivan, I'm glad that ios17 can run on my S10. I really like it. I'm looking forward to adding more customizations, such as double clicking to light up the screen. In addition, the battery icon on S10 is too far to the left, and it will be more perfect if it can be closer to the camera. When I try to install some Google Apps, I get stuck, and bitapps is too thin. Can I install opengapps in twrp?
 

kevkid

Senior Member
Sep 22, 2010
313
53
I know that. It is just to make an illusion to myself that I'm not being listened. More over I understand that real people might not even heard or listened my conversations and some AI heard the key words and made the suggestions but as long as I see don't see things/topics that I only said and never searched I feel safer.
Good point!
 

cher81

Member
May 31, 2008
31
7
OnePlus 7T
yesterday i finally got it working on my s10e, im afraid there wont be any "mature" feedback since it hasnt even been 3 weeks since the release of los 17 for galaxy s10 series. so far its been working just fine for me, no crashes at all (the only thing crashing is the digital wellbeing app if you update it, the version that comes preinstalled works). there are no google apps at all if you dont install them (bitgapps only contains the play store, no other google apps). bixby is gone aswell of course, you can reassign the button just how you like it, there are several options. you cant swipe down the powerbutton to pull down the status bar (yet?) and i havent found an option to increase the touch sensitivity (problematic if you use a glass screen protector). and the camera app that comes with los 17 is crap, i still have to look for a better one. also, if you never had los you might be disappointed in the looks and capabilities of customization, i think one ui does a better job there (maybe watch a youtube video or something to get an idea). overall i still prefer it to the stock rom because of its simplicity. if you just want to get rid of bixby and google apps you can manage that by uninstalling them via an adb terminal, that might be the better option for you since you lose warranty unlocking the bootloader and its kinda tricky to get los to work. hope i could help a little

Awesome response. Thanks twisted161. I've tried uninstalling bixby with adb and then phone was rebooting every 5 minutes on its own. (maybe deleted too many things). I couldn't find solution and preformed factory reset. I've been using LOS and even CynogenMod in the past. I've actually installed Google Camera on my phone and not using Samsung built-in camera app at all.
 

twisted161

Member
Dec 9, 2019
7
7
Awesome response. Thanks twisted161. I've tried uninstalling bixby with adb and then phone was rebooting every 5 minutes on its own. (maybe deleted too many things). I couldn't find solution and preformed factory reset. I've been using LOS and even CynogenMod in the past. I've actually installed Google Camera on my phone and not using Samsung built-in camera app at all.

Youre welcome. You must have uninstalled too many packages, i got my rid of bixby and the google trash with adb before i installed los and it worked (i used a list of all the apps and services that are "safe to remove", cant find it anymore though, sorry). If you are fine with using third party camera apps i can recommend you open camera once you flashed los, its the only camera ive found so far that detects the wide angle sensor (photo quality and setting options are very good too). If you dont use a glass screen protector and wont miss the "slide down powerbutton to pull down status bar thingy" you are ready for los17 i guess! I still havent had any crashes, let me know if you have any other questions
 

gorgo80

Senior Member
Aug 1, 2010
332
54
Helsingborg
Youre welcome. You must have uninstalled too many packages, i got my rid of bixby and the google trash with adb before i installed los and it worked (i used a list of all the apps and services that are "safe to remove", cant find it anymore though, sorry). If you are fine with using third party camera apps i can recommend you open camera once you flashed los, its the only camera ive found so far that detects the wide angle sensor (photo quality and setting options are very good too). If you dont use a glass screen protector and wont miss the "slide down powerbutton to pull down status bar thingy" you are ready for los17 i guess! I still havent had any crashes, let me know if you have any other questions

How is the gcam app? And how much is that I loose and win on installing Los 17?
What I understand it's only NFC with gpay that's not working.
And I win that I don't need to have all the Google apps installed and gets a more clean Android.

My phone is very important to me. Use it every day and don't have afford to buy a new one if in case it got broken during flash.

Today I ran Android 10 latest stock from Samsung.
 

twisted161

Member
Dec 9, 2019
7
7
How is the gcam app? And how much is that I loose and win on installing Los 17?
What I understand it's only NFC with gpay that's not working.
And I win that I don't need to have all the Google apps installed and gets a more clean Android.

My phone is very important to me. Use it every day and don't have afford to buy a new one if in case it got broken during flash.

Today I ran Android 10 latest stock from Samsung.

I havent tested the gcam app since it doesnt recognize the second sensor (for some reason not even the patched gcam apk by ivan, i checked that). I use open cam instead, i dont see a huge difference to the stock cam so its pretty good. To be honest you dont get a lot of wins by installing los, all you have is a clean android thats not really optimized for the s10 yet. You can get rid of all gapps and almost all samsung apps by disabling them via adb shell, no root needed and no void warranty so if thats all you want you might wanna take a look at how to do that (from my understanding they are not "really uninstalled", they are gone and unusable but still installed for the root user (which you dont have access to without rooting your phone)). The one big advantage is the battery performance. With stock rom i had about 4-5 hours of on screen time, now its about 10 hours which is awesome and the main reason i installed lineage os. If you like experimenting with roms and dont mind missing the fancy stuff like nfc gpay or wifi calling i can absolutely recommend it, its already pretty stable. And btw, you cant really permanently break your phone with flashing, from my experience theres always some way to fix it (you lose warranty though so you have to fix it yourself). It literally took me like 30 times flashing different stock roms and twrp recoveries (including bootloops and being stuck in download mode etc.) til i figured out which versions and key combos i need to get lineage os to work
 

byteXpression

Senior Member
Aug 31, 2017
66
128
Frankfurt
Did anyone already test with BSKO Firmware?

I tested it today and no, it did not work. It ended up in boot loops.
I tested the new TWRP for BSKO (twrp-beyond1lte-3.3.1-100_ianmacd) and the TWRP installed and works fine. But could not test further, because I could not get LOS17 to boot (even without Magisk) on the BSKO firmware.

@Ivan_Meler: Are there any plans to make LOS17 compatible with the new BSKO firmware (and TWRP)?

---------- Post added at 10:37 AM ---------- Previous post was at 10:29 AM ----------

Thanks to Ivan, I'm glad that ios17 can run on my S10. I really like it. I'm looking forward to adding more customizations, such as double clicking to light up the screen. In addition, the battery icon on S10 is too far to the left, and it will be more perfect if it can be closer to the camera. When I try to install some Google Apps, I get stuck, and bitapps is too thin. Can I install opengapps in twrp?
Hello OnceCCART... Open Gapps for Android 10 is not released yet. And the 9er package won't work. ;)
 
Last edited:

flunkyball

Senior Member
May 20, 2019
113
75
Also to boot to magisk patched recovery use reboot recovery option in system (that can be unlocked from developer options) instead of holding a key combo as its more reliable and wont lead to issues that might be caused by holding recovery combo for too long

As it happens I just rebooted from android not to recovery but system.... No matter what I try, I am stuck at the samsung splash screen with the warning about non official software.
How long exactly do I need to hold the key combo ? I tried everything from a few seconds until the continue screen dissapeared till 1min... No change and the phone does not boot up in system at all.
 

culjonito

Member
Oct 4, 2019
36
29
Hi culjonito... did you test the latest beta version already?
When I tested the OpenGapps beta versions which were a couple of weeks old, they did not work properly.
Would be nice if progress was made recently and maybe they will be released to stable soon?

Hi byteXpression
I haven't tested the OpenGApps yet, because I haven't had the time yet.
I just sent the link to show that BETA versions already exist.
Maybe I will test the OpenGApps BETA this weekend with LOS17. I'll keep you up to date :good:
 

twisted161

Member
Dec 9, 2019
7
7
As it happens I just rebooted from android not to recovery but system.... No matter what I try, I am stuck at the samsung splash screen with the warning about non official software.
How long exactly do I need to hold the key combo ? I tried everything from a few seconds until the continue screen dissapeared till 1min... No change and the phone does not boot up in system at all.
You have to hold power+bixby+volume up until you see the "splash screen" (when you boot there will be that yellow warning text after a few seconds that you have to skip via pressing the power button. You turn your phone off and hold power+bixby+volume up to turn it on (keep the buttons pressed). When that screen with the yellow warning text comes up you keep the buttons pressed for a bit (all of them including the power button)! That way the warning ("splash") screen will disappear right away and as soon as it does you release the buttons). Thats how you boot into magisk enabled rom. If you want to boot into recovery, you turn off your phone, hold power+bixby+volume up until the splash screen comes up and disappears again and release power+bixby (keep volume up pressed!). If you do exactly as i told you and it doesnt work im afraid you have to reflash everything. Ive made the experience that you have to do it right on the first time booting, let me know if it worked
 
Last edited:

Ivan_Meler

Forum Moderator / Recognized Developer
Staff member
I will rebase everything on top of current Q kernel soon(week or so probably), I will also include dtbo and vendor inside of rom itself so you won't have to be on specific firmware except when samsung does significant bl. upgrades which block older tee and trustzone elements in kernels from booting (that is not really often, It happened 2 times total so far)
 
Last edited:

vantjnh1991

Member
Jan 29, 2012
7
0
I will rebase everything on top of current Q kernel soon(week or so probably), I will also include dtbo and vendor inside of rom itself so you won't have to be on specific firmware expect when samsung does significant bl. upgrades which block older tee and trustzone elements in kernels from booting (that is not really often, It happened 2 times total so far)
Hello Ivan.
You can support s10 5G G977*
Thanks U very much!!!
 

Valentino911

Senior Member
Oct 4, 2014
93
34
In my case after installation of Los and first boot, I install magisk by flashing the .img as recovery and installing manager apk.
Then reboot to recovery from the system.

Issue: if I turn off the phone, when I try to turn it on, it stucks on the boot screen. Tried 3 times and to fix it, I always had to start los installation from scratch.

How to fix it? Where am I wrong?
 
Last edited:

kevkid

Senior Member
Sep 22, 2010
313
53
If the battery dies and I keep getting the Galaxy s10 secured by knox screen. How can I bring it back (without a computer). I know I can flash recovery etc, but this is insane, no matter what button combo I could not get it out of that boot loop. Any ideas?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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