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

Search This thread
ginger scanner

i have problem with finger scanner
 

Attachments

  • Screenshot_20200206-143522_Settings.png
    Screenshot_20200206-143522_Settings.png
    129.9 KB · Views: 529

gantzzz

Senior Member
May 18, 2016
51
12
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

Dear Ivan_Meler, could you please help to find out what is wrong with my procedure:
1) I've flashed stock (unpatched TWRP) onto RECOVERY partition: "sudo heimdall flash --RECOVERY twrp-stock.img"
2) I've flashed provided with the LOS beyond2lte-boot-magisk.img into BOOT partition: ""sudo heimdall flash --BOOT twrp-stock.img"

And the phone has come into bootloop. no matter how long I press recovery combo.
 

Ivan_Meler

Recognized Developer
Dear Ivan_Meler, could you please help to find out what is wrong with my procedure:
1) I've flashed stock (unpatched TWRP) onto RECOVERY partition: "sudo heimdall flash --RECOVERY twrp-stock.img"
2) I've flashed provided with the LOS beyond2lte-boot-magisk.img into BOOT partition: ""sudo heimdall flash --BOOT twrp-stock.img"

And the phone has come into bootloop. no matter how long I press recovery combo.

did you flash full Q stock rom before, Because samsung has made changes to tee that are also in bootloader and older bootloader will not work,
 
  • Like
Reactions: 3f1f37

gantzzz

Senior Member
May 18, 2016
51
12
did you flash full Q stock rom before, Because samsung has made changes to tee that are also in bootloader and older bootloader will not work,

Yes I've done everything from scratch according to the instructions:

1) At first I've Installed the latest official firmware (BSL4) with ODIN, as stated in the 1st post.
2) then I've magisk-rooted the "AP" archieve and reinstalled it with ODIN <- this gave me root
3) then I've installed Magisk-patched TWRP: "f=/storage/emulated/0/Download/magisk_patched.img; dd if=$f of=/dev/block/sda15 bs=$(stat -c%s $f)", with reservations under spoiler.
I have to say that this method did not work for me so I've just downloaded unofficial prepatched TWRP from this link. File name is twrp-beyond2lte-3.3.1-101_ianmacd.img after which I've uploaded it with heimdall to Recovery partition.

4) with TWRP available, I've wiped data, cache, dalvik and flashed LOS + opengapps
At this point the LOS was up and running with GAPPS okay...

Then I've tried to root with magisk according to the given instructions:

1) I've flashed stock (unpatched) TWRP onto RECOVERY partition: "sudo heimdall flash --RECOVERY twrp-stock.img"
2) I've flashed provided with the LOS beyond2lte-boot-magisk.img into BOOT partition: ""sudo heimdall flash --BOOT twrp-stock.img"

And got as bootloop...

After this point, to recover to LOS without doing it from scratch is the following:
1) Unpack boot.img from the LOS archieve;
2) flash Magisk-patched TWRP + LOS boot.img from download mode via: heimdall flash --RECOVERY twrp-beyond2lte-3.3.1-101_ianmacd.img --BOOT boot.img
 

Kirillos98

Member
Feb 6, 2020
6
1
Thanks Ivan for the new update!!! I was waiting for it all the time for beeing part of the los17 (S10) family.
Just got a queestion People:

1. Is it possible to wipe the System Partition as well?
Did this at every flash on my older devices and thougt it would be good here too, though i don't know the new partition system of Samsung, so i am in worry to delete some necessary files and end up in a bootloop.

Thanks for advise :)
 
Last edited:

flunkyball

Senior Member
May 20, 2019
80
65
did you flash full Q stock rom before, Because samsung has made changes to tee that are also in bootloader and older bootloader will not work,

Same for me over here.

I flashed latest samsung stock, even booted it up once.
Afterwards flashed a blank vbmeta.img followed by the TWRP recovery image.
Booted into TWRP, flashed multi disabler, wiped cache dalvink and system.
Flashed LOS 17.1 and rebooted normally.

My phone hangs on the samsung warning screen for about 3min and then reboots.

Any ideas ?
 

Kirillos98

Member
Feb 6, 2020
6
1
Make sure you update to Q first if you're coming from Pie, boot loader plus many other important changes.

Yeah i am of course on Q, Maybe i didn't ask precise. My concern is that i don't want to wipe just Data, Cache and Dalvik, i want to wipe System too, but because of the new Partition structure of Samsung i'm not sure if i can do this without ending up with a bricked device.
 

flunkyball

Senior Member
May 20, 2019
80
65
did you flash full Q stock rom before, Because samsung has made changes to tee that are also in bootloader and older bootloader will not work,

Same for me over here.

I flashed latest samsung stock, even booted it up once.
Afterwards flashed a blank vbmeta.img followed by the TWRP recovery image.
Booted into TWRP, flashed multi disabler, wiped cache dalvink and system.
Flashed LOS 17.1 and rebooted normally.

My phone hangs on the samsung warning screen for about 3min and then reboots.

Any ideas ?

Well, ... I went the long way round. After starting again from the beginning, incl. the setup of root on the stock rom everything now works perfectly. LOS17.1 + your lovely Magisk boot image.

However, I really do not understand how patching the stock rom with magisk support did help me out of that issue since it basically only patches the boot.img, recovery.img and introduces an emtpy vbmeta.img. The last one I replaced my self and the first ones are replaced by twrp / LOS17.1 boot image or even your magisk boot image.:eek:
 

Bene11660

Member
Oct 21, 2011
7
0
Well, ... I went the long way round. After starting again from the beginning, incl. the setup of root on the stock rom everything now works perfectly. LOS17.1 + your lovely Magisk boot image.

However, I really do not understand how patching the stock rom with magisk support did help me out of that issue since it basically only patches the boot.img, recovery.img and introduces an emtpy vbmeta.img. The last one I replaced my self and the first ones are replaced by twrp / LOS17.1 boot image or even your magisk boot image.:eek:

Great to hear, in which order did you flash the files?
I always end up with a bootloop. :/

1. Stock BSL4 Rom
2. beyond0lte-boot-magisk
3. vbmeta.img
4. twrp
5. multidisabler
6. wipe
7. LineageOS
8. opengapps pico
 
Last edited:

flunkyball

Senior Member
May 20, 2019
80
65
Great to hear, in which order did you flash the files?
I always end up with a bootloop. :/

1. Stock BSL4 Rom
2. beyond0lte-boot-magisk
3. vbmeta.img
4. twrp
5. multidisabler
6. wipe
7. LineageOS
8. opengapps pico


1. I followed that guide in order to create a magisk patched BSL4 stock rom: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
2. I flashed (via Odin) that patched version (AP file) together with the rest of the stock firmware.
3. After I verified that Magisk and root is available in stock I flashed twrp via heimdall.
4. Multidisabler
5. Wipe
6. LOS
7. Reboot to system check if everything boots up as expected.
8. Back to recovery, flashing Ivans boot image for magisk.
9. Boot to system.

The rest for setting up signature spoofing, microg and encryption was straight forward as before.

---------- Post added at 12:09 AM ---------- Previous post was at 12:05 AM ----------

i have problem with finger scanner

You tried to read in your finger print to early. If the setup wizard asks you to locate your finger print reader, just hit the "next" button on the right lower corner and go directly to the actual process which works fine. Do not tip your finger on the reader, otherwise you end up with the message you showed.
 

dexn

Member
Oct 22, 2008
7
0
Brisbane
Hi, I'm having a couple of issues.

1. On the previous release bluetooth calling didn't work, I couldn't hear the other person yet they could here me sounding like a monster coming from the deep. This release I can barely hear the other person, they are very soft even with the volume set at max and them yelling into their mic. They are able to hear me without any problem.

2. The second problem I'm having is enabling Google Voice Match. When I enable it, I go through the prompts and everything looks good until after the setup process finishes. After it returns me to the settings page, the option is still disabled and OK Google won't work.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Updated Magisk boot images are up in the same folder you can find rom in (Magisk 22.1) you can flash them from within twrp or with dd to get latest magisk Do not try to update boot image from app itself instead just flash provided image
  • 108
    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
    
    f8e3c8398929946b5959b7f8cbc990220d37419ac9de5be23c2dbffdc5455afd  beyond2lte-boot-magisk.img
    2380893c018ab44fa5f38f20d13d7e32fe98156724f047a07bc314a3e800c05f  beyond1lte-boot-magisk.img
    a382706e94f2c5eb334fafde485d2aae7f03881e4a9d52ee48776e4dd53b892b  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
    40
    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
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone