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

Search This thread

UstoBF

New member
Hi, I have installed the ROM, it is fantastic the work done, it works very well and fluid, however, I have found a problem, I can not use voice match, it does not let me activate it. Can you help me with this?

Installed versions:
lineage-18.1-20211216-nightly-beyond0lte-signed
MindTheGapps-11.0.0-arm64-20210920_084011

I have looked for information on the web and here on the forum, but it is not clear to me what the solution is, if any.

Thanks !!!
 

Attachments

  • WhatsApp Image 2021-12-27 at 23.39.28.jpeg
    WhatsApp Image 2021-12-27 at 23.39.28.jpeg
    37.2 KB · Views: 60
S10 & S10+ /DS Variants Supported?

is lineage 18 possible for sm-g975f/ds or only for sm-g975f,
the same problem i have with trwp
i know its a real smal problem, but i didnt find any information about this.
And i dont want buy the wrong phone

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.

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:👍
***

S10+_Model_Supported.png
 
Last edited:
  • Like
Reactions: Linux4

Linux4

Recognized Developer
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
 
Last edited:

nicovell3

Member
Nov 14, 2014
8
5
Samsung Galaxy S8
Hello,
I'm about to buy this phone. I've seen all cameras are working in Lineage 19 so... Can I expect the only bug with this rom is VoLte and VoWifi too? How are cameras working in this version comparing to stock?
Thanks for your help!
 

heni63

Senior Member
Dec 26, 2017
107
28
Does anybody know why Gravity Screen is not working on this Phone? I also tried CrDroid before and didn't work there either.

But I probably should also ask the Dev of the app. But afaik he's not the most responsive one

Cheers
 

starbright_

Senior Member
Apr 11, 2010
1,370
231
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
 

Linux4

Recognized Developer
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.
 

starbright_

Senior Member
Apr 11, 2010
1,370
231
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.
Mh, I understand that 19.0 is more fancy and a challenge. :)
But please don't drop further support of LOS18.1. Finally I go for LOS to have a secure (as good as possible) system. That would be great.
 

zpunout

Senior Member
Aug 26, 2015
225
39
Samsung Galaxy S5
Moto G5 Plus
Are you sure you are using this ROM?
I have the same issue with no USB data connectivity. Phone wasn't updated since about November 2021 as a friend was using it. I updated OTA to a January build but the issue persists. I also can't enter download mode anymore which leads me to suspect a hardware fault. Thought I'd post here just in case it's relevant to anyone else with the same issue.
 
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!
 
Last edited:

zpunout

Senior Member
Aug 26, 2015
225
39
Samsung Galaxy S5
Moto G5 Plus
So, I bought another S10e G970F today. I updated the stock firmware which now is up to Android 12. Can anyone confirm that LOS18.1 works on top of this? If not, I'll try myself and report back here.
[Edit: confirmed working]
 
Last edited:

starbright_

Senior Member
Apr 11, 2010
1,370
231
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.
...

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?

I am interested in this topic too. To handle that topic properly would (imho) reduce the pain of missing TWRP, which is not supported here.
So maybe @Linux4 can help us with that. I can't imagine he doesn't have a solution for that (backup/restore).
 
Last edited:

illiadin

New member
Dec 17, 2011
4
0
OnePlus 3
Samsung Galaxy S10
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!
@willy_666 I had this unlock problem with an old phone i used to have, try deleting /data/system/locksettings.db
 

illiadin

New member
Dec 17, 2011
4
0
OnePlus 3
Samsung Galaxy S10
Thanks for the hint. I think I tried to find that file, but somehow I was not able to identify it. I'll double check in the backups.
Did you solve your problem with FBE enabled?
No i actually don't use FBE for the same exact reason that you are doing this for, TWRP backups saved me multiple times before, I can't just give TWRP up without an alternative.
So far the best alternative i could come up with is use an app called migrate it takes care of most of the stuff i need to backup but i want to somehow find a way to backup the ROM settings too, that way it is almost as if i made a complete backup of the ROM data, I'm interested to how know things will go for you as i want to use FBE too.

Oh and regarding accessing the locksettings.db file, i assume you have ADB access enabled, if so i think you can simply just adb shell into your phone after boot and remove the file.
 
No i actually don't use FBE for the same exact reason that you are doing this for, TWRP backups saved me multiple times before, I can't just give TWRP up without an alternative.
So far the best alternative i could come up with is use an app called migrate it takes care of most of the stuff i need to backup but i want to somehow find a way to backup the ROM settings too, that way it is almost as if i made a complete backup of the ROM data, I'm interested to how know things will go for you as i want to use FBE too.

Oh and regarding accessing the locksettings.db file, i assume you have ADB access enabled, if so i think you can simply just adb shell into your phone after boot and remove the file.
I actually have my setup for backup and restore for emergency reasons. I'm looking for something to quickly switch the OS e.g. to try out a new rom for testing, but than restore everything completely back to where I was before.

Regarding the adb access after restoring: somehow the system lost the fingerprint of the machines allowed to access the phone through adb. The pop-up to confirm the allowance again, only shows after unlocking... where I'm back at square one...

Maybe the solution is to pull more partition block to images?
 

Top Liked Posts

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