• 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

Linux4

Senior Member
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
 
Last edited:

starbright_

Senior Member
Apr 11, 2010
1,340
223
To update the device (from your previous unofficial ROM) - are that the same steps as described here?

----

Some note about OTA update of this ROM. This is fairly easy (only italic steps below).
But I am using Magisk/microg - with that some additional steps are required - all is listed below. Don't be afraid, it is done in less than 5 minutes.

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

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

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

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

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

J4son82

Member
Jun 2, 2021
9
10
MUC
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
 

KiddoIce

Member
Mar 26, 2013
16
3
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
thanks man ill give this a shot

edit;; can confirm that this is working. thanks alot man!

linux4, its a great looking rom btw thanks for the hard work. During the first time i ran recovery, i saw there was an option to run an update through internal storage. but the second time i went to recovery it was gone. Does the update through internal storage work? and why did it disappear when i entered recovery for the second time.
 
Last edited:

FUNKYBAT

New member
Aug 7, 2021
2
0
Recife, Pernambuco, Brazil
Hello
What exactly is working and what does not work or do not act at highest quality? Can the camera be performed on maximum quality? I bought this cell phone (S10e) a short time ago, I'm waiting to arrive. The installation of the LineageOS can break his system? Well, as is my first Custom Room, I have some doubts.
 

Linux4

Senior Member
thanks man ill give this a shot

edit;; can confirm that this is working. thanks alot man!

linux4, its a great looking rom btw thanks for the hard work. During the first time i ran recovery, i saw there was an option to run an update through internal storage. but the second time i went to recovery it was gone. Does the update through internal storage work? and why did it disappear when i entered recovery for the second time.

/data is encrypted so no there's no way to install something from internal storage, either update via sideload, from external sdcard or OTG (If you're just talking about OS update you'll get them via OTA anyways, so what I said only applies to e.g magisk)
 
  • Like
Reactions: FUNKYBAT

kugel.

Senior Member
Jul 11, 2010
139
21
Works great so far. Seems I can even use bankings apps, after unrooting again. I initially rooted to restore backups using TitaniumBackup but then removed magisk using the internal uninstaller (checked "remove completely"). DKB, comdirekt and TK work so far.

EDIT: hotspot works on s10e
 
Last edited:
  • Like
Reactions: DerSteppo

kubis111

Member
Oct 2, 2016
32
4
Hi, is there a camera app in this rom that works wide, ultrawide, slowmo and portrait mode("all in one")? And a remap of the bixby button is possible? THX
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
    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
    3
    First off, thank you for making this.
    Been using the microg fork for a couple of days, so I thought I'd share a list of things that I had/have issues with or that don't work.
    Most of these issues should also be present on this official ROM, as it's just the google services backend that's different.
    I'm also new to modern smartphone ROMs, so please don't bash me if I say something dumb.

    Using on an S10+ Exynos. SM-G975F
    Installation went just fine on Arch Linux.

    Lockscreen/locked related:
    Always on Display doesn't shift the clock every minute, so there's a chance of burn-in.
    Always on Display has a clump of maybe 5 pixels next to the front cameras that constantly blink green.
    Wave to wake up doesn't work.

    Microg related, had to install DroidGuard Helper from FDroid to get the fingerprint sensor working. Works well and much quicker than on the stock Samsung ROM.

    Random issues:
    Status bar doesn't change to a dark font with a light wallpaper. Works just fine in apps.
    Adaptive brightness seems to be having issues actually doing anything, very often.
    There are no built-in torch intensity settings.
    Most likely microg related, doesn't automatically pick up auth codes from SMS as there's no daemon for it.

    Frequently asked about features:
    Wireless hotspot working just fine.
    5GHz wifi working just fine.
    Bluetooth working just fine. No issues with wireless earbuds, paired instantly.
    LTE working as expected, signal is fine. Central EU. TMobile network.

    Camera:
    Stock camera app doesn't let you change lenses or video framerate to 60 fps.

    Using the GCam fork mentioned somewhere above "MGC_8.1.101_A9_GV1r_MGC"
    Wide angle lens working, normal lens working, no telephoto.
    Both front cameras working
    Takes some time to switch between any of these.
    You can force [email protected] video with stabilization and all the nice things in the settings.
    No 4K video for the front cameras, it caps at [email protected]

    Not tested:
    NFC/Contactless Payments.
    Dual sim
    SD card slot
    USB hotspot.
    Sensor that checks for liquid in the charging port.
    Samsung's pointless oxygen levels in blood / heartbeat sensor.
    "Pedometer".
    Gyro/etc. for VR.
    3
    ok, thanks, I guess no countermeasure can be adopted... (?)
    Try installing this as a system app, by making a folder /system/app/SamsungDAP and putting the APK inside
    2
    Hi

    I softbricked my beyond1 trying to use updater. It was my fault, I interupted the system update but it was taking approx 2 hours and still wouldn't finish, so I force rebooted and tried to go to download mode upon reboot I got the error



    I stopped and thought about what I should do for a minute, since I could not get into recovery or download mode.

    I did a quick Google search of the error and fixed it by ignoring the error and kept holding bixby and volume down to get into download mode and luckily it worked

    That is all. Just thought I'd report it here for reference sake.

    Cheers
    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.
  • 30
    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
    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.
    5
    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
    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