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

[grujea]

I just installed LOS with TWRP and Magisk on my S10 and everything seems to be working fine.

Excellent guide! I have been looking for something like this a couple of days ago, eventually I managed to do the same steps you described (from various sources, same as you). Have been planning also to make a similar post as yours, but unfortunately I haven't managed to succeed with the flashing, I softbricked twice my S10...
Everything seems right on, until I flash the custom OS (indeed I tried Pixel Experience Plus, but from my understanding it should've mattered, even the patched boot.img from lineageOS is referenced on the PE thread).

Could you please tell me, what was the version of the stock firmware that you have used? which security update? I tried with DTI8... (second time I also tried, but couldn't flash the previous version of the stock firmware through Odin, it kept returning an error mentioning "kernel, binary" something (sorry, noob, not familiar with the terms, can't remember exactly)

Thanks!

 

[acefan]

Excellent guide!

Thank you!

Could you please tell me, what was the version of the stock firmware that you have used? which security update?

In Frija, I just entered the model SM-G973F and the CSC DBT.
I had a look on sammobile before, this is the firmware I wanted (and got via Frija):
sammobile.com/samsung/galaxy-s10/firmware/SM-G973F/DBT/download/G973FXXU8DTH7/363864/

 

[grujea]

Thank you!



In Frija, I just entered the model SM-G973F and the CSC DBT.
I had a look on sammobile before, this is the firmware I wanted (and got via Frija):
sammobile.com/samsung/galaxy-s10/firmware/SM-G973F/DBT/download/G973FXXU8DTH7/363864/

Ok, so you installed the september release (DTH7). Unfortunatelly (I think), I installed the october one (DTI8). Could be a word of caution for somebody who is trying to do the same thing.

Thanks for the reply!

Later edit:
I've noticed that actually the Pixel Experience OS is based on the september release as well. Will try again with the october release based Lineage OS. Hopefully I will return with good news!

Later edit2:
Good news! (for me at least ) I managed to get it working with Lineage OS october build. Thanks!

 

[grujea]

. . .
(0. Enable bootloader using John Wus guide.)
. . .

Also, I would suggest adding this guide in your post/guide. In my searches, I found it easier to understand (same steps but more detailed, useful for noobs - like myself) than the one by John Wus. (It also has a video showing the tricky button combos etc).
https://www.androidexplained.com/galaxy-s10-root-tutorial/

 

[FreeRunner2017]

Hi Ivan

Been using this rom for a very long time but as of the most recent release I am unable to use the front camera with snapchat. Only snapchat other apps work fine. I'm having issues with bluetooth calling in my car aswell.

Hi @revolution48 I'm experiencing the same thing anyone? Any solutions?

 

[flunkyball]

I am using this great rom since May and Iam currently running the release from the 21st of May.
The reason why I did not upgrade ever since are the repeatedly reported issues with bluetooth calls which work just fine with my current version.

So I got 2 questions:

1. Are bluetooth calls working in the current release ?
2. Are there any major improvements since May 2020 despite the kernel upgrades and security patches ?

Cheers

 

[DerSteppo]

I am using this great rom since May and Iam currently running the release from the 21st of May.
The reason why I did not upgrade ever since are the repeatedly reported issues with bluetooth calls which work just fine with my current version.

So I got 2 questions:

1. Are bluetooth calls working in the current release ?
2. Are there any major improvements since May 2020 despite the kernel upgrades and security patches ?

Cheers

I am running v1.2 since 2-3 days and I am really happy with it. I have successfully made phone calls with my bluetooth headset (Plantronics Backbeat Fit) and also GPay worked fine when I made a payment via Paypal in the supermarket. I have not tried other cards yet. Magisk is working fine, Play Store shows that the device is official, all good. I just find that the sound from the speakers are not as good as on stock, but that might be a configuration thing and I have not changed anything yet. Then again, bluetooth sound is excellent also for music (Spotify) ! :good: thanks a lot to @modpunk and @derf elot !

Official TWRP (waiting for modpunk's release)
Modpunk's LOS 1.2
Pico GAPPS (opengapps.org)
Modpunk's Magisk

That's all.

 

[DreckSoft]

With the latest update I'm stuck at the lineage boot logo forever.

Update: The issue seems to be with the magisk boot image. If I just install the Update without the Magisk image everything is fine. As soon as I install the patched boot image - stuck at boot logo.

Magisk has always been problematic with this phone. Manual install always failed. I don't know what's wrong now with the boot image. For now it seems I have to use it without root

Update 2: Deleting the Magisk modules helped. Now the provided boot image works.

Update 3: 2 reboots later I'm stuck at the LOS logo again. All I tried was to enable ADB. Unfortunatly the connection to the PC didn't work and now the phone isn't either. Reapplying the update and going back to non-magisk boot won't help.

 

[ZockerFloh7]

Hey ivan, first of all thank you for your great work!

I am having a little trouble, when I try using my drone (I own a Fimi X8 SE).
Usually when I connect the remote control of the drone to the android phone via USB, the drone app automatically opens.
I tested with other phones and it works, so there must be an issue with the rom I think.

When I plug the cable in, my phone gets charged, and the usb notification appears.
But just for a few seconds, then it disappears.
If I keep it plugged, this happens again and again (appears, disappears...).

I am using the latest version of the ROM.
I also attatched logcat, kmsg and tombstones.

*PUSH*
Anyone an idea?

 

[flunkyball]

I am running v1.2 since 2-3 days and I am really happy with it. I have successfully made phone calls with my bluetooth headset (Plantronics Backbeat Fit) and also GPay worked fine when I made a payment via Paypal in the supermarket. I have not tried other cards yet. Magisk is working fine, Play Store shows that the device is official, all good. I just find that the sound from the speakers are not as good as on stock, but that might be a configuration thing and I have not changed anything yet. Then again, bluetooth sound is excellent also for music (Spotify) ! :good: thanks a lot to @modpunk and @derf elot !

Official TWRP (waiting for modpunk's release)
Modpunk's LOS 1.2
Pico GAPPS (opengapps.org)
Modpunk's Magisk

That's all.

Thx for the heads up regarding modpunks release. The only problem I have here is that it only supports FBE which is no option for me. I want the phone to be completely encrypted via FDE. Everything else gives you always access to meta data around your information on the phone.

 

[wora92]

Thx for the heads up regarding modpunks release. The only problem I have here is that it only supports FBE which is no option for me. I want the phone to be completely encrypted via FDE. Everything else gives you always access to meta data around your information on the phone.

An interesting question would be: Which is the thread model you're thinking about? I see two aspects, security wise, that speak against your choice. A) While FDE has some advantages over FBE, I would be more concerned about SELinux being permissive in Ivan Melers build. B) Also, he does not release his sources.

 

[flunkyball]

An interesting question would be: Which is the thread model you're thinking about? I see two aspects, security wise, that speak against your choice. A) While FDE has some advantages over FBE, I would be more concerned about SELinux being permissive in Ivan Melers build. B) Also, he does not release his sources.

Well, the usual thread level - constantly staying secure from various secret services and running from oppressive governments just kidding.

The thread model that Iam thinking about is the following:
If you run a custom rom you always run TWRP as well. Booting into TWRP requires no authentication and enables you to browse all files with FBE (however not to read them) giving information away what you are using. He is using whatsapp, well good to know I can attack him from there as well. He is using app XY, oh well it has a known issue/backdoor I can use. Furthermore it gives you access to all unencrypted data on the phone just like that.

I agree that this thread model means physical access to the phone and is less probable compared to an app containing malware scanning all files while the phone is in use.

In my perspective FBE had comfort in mind when it was designed as it enables services for basic functionalities to run at startup without decryption and therefore also increases performance. However this comes with a loss of security and as we all know, security never is "comfortable".

Anyway, you are right about SELinux being permissive and the fact that no sources are released - moreover, I saw that modpunk integrated Seedvault ! So I will give it a try

 

[chrizbee]

SafetyNet and Google Pay

I've successfully flashed LineageOS 17.1-20201008 for beyond0lte (coming from Samsung's stock android 10).
I've installed everything in the following order:
- TWRP from here
- Multidisabler from here
- lineage-17.1-20201008-UNOFFICIAL-beyond0lte.zip
- OpenGapps Nano
- beyond0lte-boot-magisk.img

After first boot I installed Magisk Manager but SafetyNet always fails with:
- basicIntegrity: true
- ctsProfile: false
- evalType: HARDWARE

I'v also tried to change the fingerprint to the official Samsung Galaxy S10 with MagiskHide Props Config.
Still no success even tho @vomad suggests to do so:

Use "attest" method or simply add the magisk module named Gpay.Sqlite.fix. To initial pass safetynet you need another magisk module (MagiskHideProps). That's all you need on LOS 17.

My problems are that I can't find Netflix in Google Play Store (apk workaround tho) and more importantly I can't use Google Pay.
Did anyone here get Google Pay to work as it should?

 

[sm4rk0]

Please use search

(...snip...)

Did anyone here get Google Pay to work as it should?

That question has already been answered to here, and in posts after that one:

Use "attest" method or simply add the magisk module named Gpay.Sqlite.fix. To initial pass safetynet you need another magisk module (MagiskHideProps). That's all you need on LOS 17.

 

[chrizbee]

That question has already been answered to here, and in posts after that one:

I've read all of the posts regarding these topics... The one you (and I) quoted is the one I followed.
Unfortunately I'm still not able to pass SafetyCheck (ctsProfile) even after editing the devices fingerprint (see my post).

 

[vomad]

I've read all of the posts regarding these topics... The one you (and I) quoted is the one I followed.
Unfortunately I'm still not able to pass SafetyCheck (ctsProfile) even after editing the devices fingerprint (see my post).

With the latest changes in Google framework you need to switch your device from "hardware" attestation to "basic". Just use hardware-off magisk module below

 

[chrizbee]

With the latest changes in Google framework you need to switch your device from "hardware" attestation to "basic". Just use hardware-off magisk module below

Thanks a ton! I'm now able to pass SafetyNet and can add my credit card to Google Pay.
Affter adding my card it still says "not set up" and links me to a Google support page.
Are you able to pay via NFC?

 

[sm4rk0]

I'm sorry, I didn't read to the end of your post.
I'm glad you solved the issue and probably helped the others in similar situation.

I've read all of the posts regarding these topics... The one you (and I) quoted is the one I followed.
Unfortunately I'm still not able to pass SafetyCheck (ctsProfile) even after editing the devices fingerprint (see my post).

 

[Ivan_Meler]

New builds are up with november security update and few other changes
- Updated vendor to XXU9DTJA
- Switched to more calibrated sensor for Adaptive Brightness
- Merged November 2020. Security update
- Synced with LOS source

Updated 18.0 builds should also be out this week, Big thanks to everyone who supported this project as it wouldnt be possible to keep it up without them, Donations help offset build server cost and sometimes get me coffee

 

[Schuft69]

short question here (may be answered in may, but long time ago - so ask again):
Is encryption possible (out of the box) with this image?