• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

Search This thread

gandoo

Member
Aug 9, 2021
28
14
@Linux4

LineageOS version: lineage-18.1-20211102-microG-beyond0lte https://download.lineage.microg.org/beyond0lte/
LineageOS Download url: https://download.lineage.microg.org/beyond0lte/lineage-18.1-20211102-microG-beyond0lte.zip
Gapps version: n/a

Did you
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes

Are you using
a task killer: no
a non-stock kernel: no
other modifications: no

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: Am on microG. While trying to cast to a Miracast device. The miracast device screen blanks briefly for a second, like it was about to mirror but then does not. After sometime it disconnects. I have enabled "Enable Wireless Display" as in the screenshot below. logcat - https://pastebin.com/raw/vvqEvQvQ

JXQjcCi.png
 
Last edited:

Virgile59

New member
Nov 16, 2021
1
0
Hello, thank you for your work.
After updating the phone with :
lineage-18.1-20211112-nightly-beyond1lte-signed

I have a problem with the volume when calling with the earpiece. The volume is much lower than before. Do you know how I can boost this volume? I don't know the corresponding configuration files.

Another thing, the fingerprint reader does not work anymore.

Thanks for your help.
 

gandoo

Member
Aug 9, 2021
28
14
@Linux4

LineageOS version: lineage-18.1-20211102-microG-beyond0lte https://download.lineage.microg.org/beyond0lte/
LineageOS Download url: https://download.lineage.microg.org/beyond0lte/lineage-18.1-20211102-microG-beyond0lte.zip
Gapps version: n/a

Did you
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes

Are you using
a task killer: no
a non-stock kernel: no
other modifications: no

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: Am on microG. While trying to cast to a Miracast device. The miracast device screen blanks briefly for a second, like it was about to mirror but then does not. After sometime it disconnects. I have enabled "Enable Wireless Display" as in the screenshot below. logcat - https://pastebin.com/raw/vvqEvQvQ

JXQjcCi.png
I think the cause of this issue is the AnyCast device mirrors over http and the s10e is trying to mirror with a https stream ... so its a insecure connection and gets rejected.

Luckily, I found an option to mirror+stream on the AnyCast device. So I'm using the F-Droid app plainUpnp to stream video to the TV. Would be awesome if miracast worked though :) ... would be no need for transcoding ... and no need for the Anycast to connect to my WiFi/internet and send god-knows-what data :))
 

stts44444

Member
Apr 8, 2016
17
6
I love LineageOS but I dont see the point any more. All networks other than Volte and 5g are being shut down. Lineage cant do Volte. So it cant run all these great 4g only phones. So what is the point of Lineage here? In the USA, Snapdragon is cheapest to get, so may as well settle for factory ROM Snapdragon at better prices than Exynos non Volte that will soon stop working. Do I have it figured out, or am I missing something?
 

kybsmds

Member
Mar 20, 2021
11
2
Hi guys,

i'm preparing to install this official version and i'm wondering which vbmeta file should i use, if any? There is no mention of a vbmeta file in the instructions but i remember needing one when installing the unofficial version of this rom.

I'm currently running the unofficial version of this exact same rom on S10 so i believe i need to do a complete clean install to get this official rom into use, meaning installing the latest custom recovery including a vbmeta file, doing a complete factory reset and data wipe and then installing the official rom. Please correct me if i have misunderstood something.
 

mikk150

Member
Oct 29, 2008
33
6
Tartu
Hi guys,

i'm preparing to install this official version and i'm wondering which vbmeta file should i use, if any? There is no mention of a vbmeta file in the instructions but i remember needing one when installing the unofficial version of this rom.

I'm currently running the unofficial version of this exact same rom on S10 so i believe i need to do a complete clean install to get this official rom into use, meaning installing the latest custom recovery including a vbmeta file, doing a complete factory reset and data wipe and then installing the official rom. Please correct me if i have misunderstood something.
It's because you do not need vbmeta
 
  • Like
Reactions: kybsmds and Linux4

haponib669

New member
Nov 24, 2021
3
1
I love LineageOS but I dont see the point any more. All networks other than Volte and 5g are being shut down. Lineage cant do Volte. So it cant run all these great 4g only phones. So what is the point of Lineage here? In the USA, Snapdragon is cheapest to get, so may as well settle for factory ROM Snapdragon at better prices than Exynos non Volte that will soon stop working. Do I have it figured out, or am I missing something?
Goodluck unlocking the bootloader from qcom Samsung phones lol
 

fil3s

Senior Member
Aug 30, 2014
1,391
236
43
bendigo
mobiledevices11.blogspot.com
Hi @Linux4 :)

I want to move to this rom but everytime I flash it ;

1. Flash lineage recovery
2. Format data
3. Flash rom.zip , gapps.zip and lygisk.zip

I have a lot of trouble with my Microsoft account. Like I'll go to sign into outlook etc but the screen just goes blank. Also 2FA doesn't work for me.

I'm currently using evolution x that also uses lineage recovery

However, I accidentally installed lygisk on it and the phone obviously wouldn't work properly, until I flashed magisk after a clean wipe, I Couldn't sign into Microsoft, XDA etc

It now works ok after flashing magisk

Am I missing something?

Best regards
 
Last edited:

Linux4

Senior Member
Hi @Linux4 :)

I want to move to this rom but everytime I flash it ;

1. Flash lineage recovery
2. Format data
3. Flash rom.zip , gapps.zip and lygisk.zip

I have a lot of trouble with my Microsoft account. Like I'll go to sign into outlook etc but the screen just goes blank. Also 2FA doesn't work for me.

I'm currently using evolution x that also uses lineage recovery

However, I accidentally installed lygisk on it and the phone obviously wouldn't work properly, until I flashed magisk after a clean wipe, I Couldn't sign into Microsoft, XDA etc

It now works ok after flashing magisk

Am I missing something?

Best regards

This has nothing to do with the ROM at all.
Note this thread is not a support thread for Lygisk ... however the issues you're having are most likely caused by using Lygisk stable and having Zygisk enabled.
 

kampungc

New member
Nov 22, 2021
3
4
Hello everyone,

First, thank you @Linux4 for bringing this amazing ROM to the S10 lineup :)

I own a S10e and as far as I understand, it comes in two versions:
  • SM-G970U with a Snapdragon that is not supported by LineageOS
  • SM-G970F with an Exynos that is supported as per the list of devices page

Unfortunately, I have a SM-G970F/DS version of that phone. There isn't much information about this one on internet apart from the fact that DS stands for Dual SIM.

So here comes my question: are SM-G970F and SM-G970F/DS totally different versions or the DS is just an insignificant variation that will run LineageOS perfectly fine?

I remember that years ago when I was flashing CyanogenMod to my Galaxy SII, I had to be extra careful with the model I had.

Thank you,
Best
 
  • Like
Reactions: Linux4

Linux4

Senior Member
Hello everyone,

First, thank you @Linux4 for bringing this amazing ROM to the S10 lineup :)

I own a S10e and as far as I understand, it comes in two versions:
  • SM-G970U with a Snapdragon that is not supported by LineageOS
  • SM-G970F with an Exynos that is supported as per the list of devices page

Unfortunately, I have a SM-G970F/DS version of that phone. There isn't much information about this one on internet apart from the fact that DS stands for Dual SIM.

So here comes my question: are SM-G970F and SM-G970F/DS totally different versions or the DS is just an insignificant variation that will run LineageOS perfectly fine?

I remember that years ago when I was flashing CyanogenMod to my Galaxy SII, I had to be extra careful with the model I had.

Thank you,
Best

Hi,

In fact except for S10 5G and Note10+ 5G all Exynos 9820 devices don't even have a single SIM variant anyway (and as you said DS means Dual SIM - that's all about it already).
So yes it will work just fine.
 
  • Like
Reactions: sieghartRM

FluxDeluxe

New member
Nov 30, 2021
4
2
Im new to here (but not so new with installing roms for androids) and readed many pages about this topic, interessing! And appreciated the work!

Well, had S5 for long time with lineageos and its such antic thing (many thanks to Lineageos, that why using for long time). So time for a new phone and bought an second hand S10 exynos. Shocked again about such Samsung and Google bloatware, immediatly went into this topic and Lineageos wiki to install this rom into.

One thing im stucked with is, succesfully flashed with Heimdall (have to unlock bootloader within download mode, otherwise, not flashable) with lineageos recovery image file. But i cant get into Lineageos Recovery mode after its flashed. So first while at download mode, pressing volume down and power button, when screen goes black, immediatly volume up + bixty + power button while cable is connected to my laptop, but it will pass every time to Samsung stock rom. Looked whole internet and youtubes videos and do it same. When going to recovery mode without flashing (from samsung itself), it works. Probaly new update (wich previous owner installed?) of samsung blocks, to get into Lineageos recovery mode? I mean, it does looks something is blocking me from to get into Lineage recovery mode from download mode.

I am following this guide: https://wiki.lineageos.org/devices/beyond1lte/install

Like this video, i did extactly (only the buttons part, to get into Lineage recovery mode) but it passing and going to Starting samsung stock rom:


Cheers
 
Last edited:

FluxDeluxe

New member
Nov 30, 2021
4
2
Im new to here (but not so new with installing roms for androids) and readed many pages about this topic, interessing! And appreciated the work!

Well, had S5 for long time with lineageos and its such antic thing (many thanks to Lineageos, that why using for long time). So time for a new phone and bought an second hand S10 exynos. Shocked again about such Samsung and Google bloatware, immediatly went into this topic and Lineageos wiki to install this rom into.

One thing im stucked with is, succesfully flashed with Heimdall (have to unlock bootloader within download mode, otherwise, not flashable) with lineageos recovery image file. But i cant get into Lineageos Recovery mode after its flashed. So first while at download mode, pressing volume down and power button, when screen goes black, immediatly volume up + bixty + power button while cable is connected to my laptop, but it will pass every time to Samsung stock rom. Looked whole internet and youtubes videos and do it same. When going to recovery mode without flashing (from samsung itself), it works. Probaly new update (wich previous owner installed?) of samsung blocks, to get into Lineageos recovery mode? I mean, it does looks something is blocking me from to get into Lineage recovery mode from download mode.

I am following this guide: https://wiki.lineageos.org/devices/beyond1lte/install

Like this video, i did extactly (only the buttons part, to get into Lineage recovery mode) but it passing and going to Starting samsung stock rom:


Cheers


Unbelieveable, its working now. Found an solution by myself. At download mode, after flashing lineage recovery with heimdall, press power button + volume DOWN + bixby and with this way phone will be turned off. And then press power button + volume UP + Bixby and got into Lineage recovery. Pfff working whole day about this and no one came with this solution on internet.. Anyways, appreciated can help anybody with my solution if have same problem.

Keep up the good work guys! Cheers Flux
 
  • Like
Reactions: ajislav and zpunout

zpunout

Senior Member
Aug 26, 2015
129
22
Samsung Galaxy S5
Moto G5 Plus
Unbelieveable, its working now. Found an solution by myself. At download mode, after flashing lineage recovery with heimdall, press power button + volume DOWN + bixby and with this way phone will be turned off. And then press power button + volume UP + Bixby and got into Lineage recovery. Pfff working whole day about this and no one came with this solution on internet.. Anyways, appreciated can help anybody with my solution if have same problem.

Keep up the good work guys! Cheers Flux
Yeah, the timing of the button presses between resetting the phone to the combination to boot into recovery has to be precise. I've struggled with this too on some days.
The way I do it to prevent fumbling around with the buttons:
After using Heimdall to flash LOS recovery, I leave the USB plugged in.
Then I hold Vol Down, Bixby and Power until the screen goes black.
At that exact moment when the screen goes black, I move the finger which is on the Vol Down button to the Vol Up button and continue to hold all three buttons until LOS recovery appears.
 

zpunout

Senior Member
Aug 26, 2015
129
22
Samsung Galaxy S5
Moto G5 Plus
Minor bug report:

When playing audio through earphones or through an aux cable to the car radio (In my case, playing YouTube videos in the background in Kiwi Browser), if an alarm or reminder sound goes off, I dismiss the alarm then the audio playback resumes but it switches to the phone speaker.
Sometimes, it will play through the speaker and earphones at the same time.

The workaround to this minor issue is to simply press pause and resume playback to continue listening through earphones.
I'm happy to generate a logcat if it will help @Linux4 .
 

GantengMania

New member
Jul 22, 2015
3
0
Hello does anyone have a problem using the super version of open gapps? Every time I try to sign in my google account the screen just turn black
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Thank you very much for the quick reply!
    I'll definitely give it a go then ;)
    Hi,

    I have been using this ROM for a couple weeks now and I love it! It feels smoother than stock One UI indeed and battery lasts longer. The experience is very pleasant.

    Huge thanks to the LineageOS team and @Linux4 for their great work! 😃

    Best
    2
    S10 & S10+ /DS Variants Supported?





    So why not add it to the wiki? 🤷‍♂️

    Some user on Reddit was asking if the SM-G975F/DS is supported because the LineageOS wiki page Samsung Galaxy S10+ (beyond2lte) says: "Supported models SM-G975F".

    And the Don't see yours? link just below that leads to the FAQ: "We try to have the list as complete as possible. If yours isn’t there it will either not work or we couldn’t test it."

    BTW thanks for supporting these devices. :cool:👍
    ***

    View attachment 5494251

    Of course it is supported, it's not there because technically the /DS is not part of the model number.
    Considering stock settings app shows it like that though, it might be worth adding it to avoid confusion.

    Edit: https://review.lineageos.org/c/LineageOS/lineage_wiki/+/320958
    2
    I am on https://lineage.microg.org/ (which is based on this version here, right). Even in latest release (12/16) the vendor patch level is 10/1 - seems to me outdated. Is this normal or are some patches missed? What is vendor patch date here?
    Thank you

    2021-11-01 vendor blobs were simply skipped in favor of working on LineageOS 19.0 ...
    2021-12-01 ones are for Android 12 now already so you can't use them on 18.1.
    2
    There are a couple of ways to make complete image backups of the phone. The simplest is to use adb.

    On my phone the following files are the actual partitions:

    a) /dev/block/sda25 - system
    b) /dev/block/sda31 - userdata

    First check your phone to see where your partitions are mapped. i.e.:

    Navigate to: /dev/block/platform

    Open each folder in the platform folder till you find a folder named "by-name" (There may be only one folder)

    On my phone it's "13d60000.ufs". Thus I issue this command from a terminal or adb shell:

    ls -al /dev/block/platform/13d60000.ufs/by-name

    This will give you list of all the partitions and the files they are mapped to. (make sure you use those mappings not mine)

    Thus, to backup my phone:
    a) Boot into recovery
    b) enable adb
    c) I run these commands:

    adb pull -z any /dev/block/sda25 system.img
    adb pull -z any /dev/block/sda31 userdata.img

    This creates two image files on my computer (system.img & userdata.img)

    To restore:
    a) Boot into recovery
    b) enable adb
    c) I run these commands:

    adb push -z any system.img /dev/block/sda25
    adb push -z any userdata.img /dev/block/sda31

    Note: The userdata image backup contains the data on your sdcard (internal storage). So restoring that will delete (overwrite) all your data too. (copy that separately)

    p.s. Make sure you check the partition mapping on your phone or it could be disastrous.
    p.p.s You can obviously backup any of the other partitions too (e.g. recovery, boot, etc.).
    I tried this for testing, as I want to have a quick switch between my daily system and a system I just want to try.
    The steps I usually do are:
    Full system backup (TWRP)
    messing around
    Full system restore (TWRP
    and I'm back where I left.

    As I see the benefits from this ROM (i tried it, ans I'm quite happy) I want to move forward and use it as my daily driver. But I also want to keep the possibility to quickly try another system or a future update before moving to it. Hence I triede to get used to the backup and restore process.

    I did the following steps:

    1. Installing LOS18.1 (as in the instructions given with LOS recovery)
    2. Setting up everything (initial setup, some apps, launcher, fingerprint and pattern/pin/password)

    Backup Process::
    3. Copy all data from storage while booted (MTP) to desktop computer
    4. rebooting to recovery (LOS recovery)
    5. pull the images with mentioned adb pull commands

    Randomly messing around (as i would do to try new/other things)
    6. Re-Installing any OS

    Restore Process:
    7. Re-insytlling LOS18.1 (as in the instructions given)
    8. boot into LOS do the initial setup
    9. reboot to recovery (LOS recovery)
    10. factory reset
    11. pushing the two images back
    12. rebooting
    --> Lock screen looks fine
    but I cannot unlock the phone, with all variants (pin, pattern, password) it reports: wrong ***

    Next Steps:
    13: I would copy back all content to the storage through MTP connected (reverse of step 3).
    14: after a reboot I would expect being back as before step 3.

    Anyone an advice or hint on the unlock problem?
    Or a better procedure to what I do?

    Before I move to like to know now, how to do it properly for once I need it...
    Thanks a lot!
    1
    Does anybody else also have wrong colors when using LiveDisplay (looks over-saturated) or color-calibration in general. I already reported it in the official LineageOS issue tracker (#3813), but no one seems interested looking at it.
    In the picture, you see two phones side-by-side with blue and green values in the color profile set to the lowest value for demonstration purposes such that the UI should be completely red:

    • Left: S10 with 18.1: wrong colors - there are still non-red colors
    • Right: S4 with (unofficial) 17.1: correct colors - everything is red
    View attachment 5487633
    I have also noticed this when using the livedisplay night mode.
  • 37
    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:
    Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
    Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.

    Downloads:

    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • 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/LineageOS
    Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
    7
    my safetynet fails, is there any way to make it pass? s10 exynos

    First you need to install magisk and then:


    1) Enable settings MagiskHide
    2) install MagiskHide Props Config(Magisk module)
    3) Open the terminal
    4) su
    5) Type "props"
    6) Edit 1 fingerprint of the device
    7) Choose a certified fingerprint
    8) 21 Oneplus
    9) Find an Android 11 device (OnePlus 8T global 44)
    10) Follow the instructions
    11) Restart
    12) Clear Google Play Store Data
    13) Check SafetyNet (should pass)
    14) Open MagiskHide (Magisk -> Tap on the Shield symbol)
    15) Check all apps that do not require root privileges
    5
    Any way around it? I like this rom but if updater is gonna get stuck because I'm using magisk I had to change back kraken rom 🥲 not that I prefer aoskp

    You could join the telegram group to find some early access build of some magisk fork that has addon.d working with FBE (topjohnwu is not even willing to merge an already existing fix as seen here: https://github.com/topjohnwu/Magisk/pull/3037)
    Other than that you could install magisk by just patching boot.img in the app instead of sideloading it in recovery (for now) which should make it not install addon.d.
    5
    First of all, I appreciate your work a lot. I've been waiting quite a long time for an official lineageos build for the s10, and you nailed it, you're even fixing the few bugs remained.
    Anyway, why are you saying TWRP would brick a device? I followed your suggestions of installing lineageos recovery and it works great, but I had TWRP in my previous device for about 2 years and I never had a problem

    Hi Linux4,
    Just a bit curious about you thoughts on TWRP. Indeed, it has been around for a while, has many features and is very popular, and your statement looked quite strong for me, but probably for good reasons. Is it simply not adapted to your ROM, or is it not adapted to the s10 phones, or has it gone bad generally? I am still using TWRP for all the added features that the Lineage recovery doesn't have, but will switch based on your advice.
    TWRP is way too bloated for a recovery IMO - it's more likely to break something than help you nowadays
    Especially that it's heavily touching /data isn't good on devices with FBE, like on this ROM, TWRP randomly messes up FBE policy (especially on OTAs it seems) rendering the device unbootable without wiping (which is why OP says using TWRP = data loss) which is what I referred to with (soft)"brick"
    Not to talk about that crap not even properly formatting data on standard "factory reset" which makes it not boot on this ROM.
    Also applies to other devices using FBE encryption including Tab S6 Lite and S20 series.
    Older devices that use legacy FDE instead don't seem to have similar issues afaik.

    PS: TWRP looses most of it's "features" with encrypted userdata.
    4
    I do the same with every OTA: let the system install it, seeing that it does not finish in 2-3 or so minutes, reboot (but not to recovery, just a simple reboot via holding power&vol- for >7s) - and there's the viola! A hack for sure, but it works.

    Being stuck is caused by magisk's broken addon.d just in case you wonder why it happens