[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

[exaveal]

This is the right order:

1. Flash lineage-18.1-20210415-recovery-beyond0lte.img and vbmeta.img
2. Boot Recovery
3. Factory reset using Factory reset in Recovery -> Format data/factory reset
4. adb sideload lineage-18.1-20210415-UNOFFICIAL-beyond0lte
5. adb sideload Magisk-v22.0.apk
6. Boot to LineageOS and finish Installation of Magisk
7. Boot Recovery
8. adb sideload spoof_s10e.zip to enable signature spoofing (or install via Magisk)
9. adb sideload Nanodroid for MicroG
10. Boot to LineageOS

 

[tillaz]

Do it with some app like https://f-droid.org/en/packages/dk.jens.backup/ ?
Or disable FBE encryption if you are fine with that and use TWRP ...
As long as FBE is enabled you'll eventually corrupt your /data partition by using TWRP.

How do I disable FBE encryption?

 

[minilandl]

whats the best way to backup because lineage recovery dosen't allow this would adb backup work ?

 

[Spyop3]

whats the best way to backup because lineage recovery dosen't allow this would adb backup work ?

Yes it should

 

[tillaz]

Hoe do I get SELinux enforcing mine says permissive

 

[minilandl]

Thank you for making this amazing rom for our device lineage support is the reason I purchased this phone without it I wouldn't have so I may donate some money your way. Thanks and its much more stable than other roms available. Stock android on samsung hardware is something I've been interested to try for ages and it fixes most of my issue with the galaxy S series the ****ty bloated software.

 

[minilandl]

One problem I'm having whenever I try and charge my phone on lineage it turns itself off and needs to be manually restarted

 

[flortsch]

Hoe do I get SELinux enforcing mine says permissive

Did you flash any Magisk module? Maybe you flashed one that messed around with SELinux.

 

[flortsch]

How do I disable FBE encryption?

I know from modpunk's 17.1 rom that one has to modify the /etc/fstab file where mounts are defined to disable FBE. But I can't tell exactly how it works.

 

[flortsch]

whats the best way to backup because lineage recovery dosen't allow this would adb backup work ?

There are multiple ways to backup (adb, Seedvault, OAndBackupX), but you have to try them out if they work for your use-case, because these user-land backup solutions don't perform as well as raw disk backups via TWRP. For example, some banking apps force reconfiguration even after user data has been restored.

For me personally, OAndBackupX worked best from all the options. Note that it requires root, i.e., Magisk. But also here, some apps (like Fennec browser from F-Droid) just crashed after restore, so test it for your use-case.

 

[gaglia83]

Thank you @Linux4 for this great work, I just installed and works like a charm.

One problem though: disk encryption.

I'm entering a rabbit hole of encryption on Android now. I was not aware that Android 10+ enforces FBE (File-Based Encryption) as opposite as FDE (Full-Disk Encryption). I never realized it because this is not the case on older devices, even if on Android 11, that probably do not have storage and power to support FBE and therefore fallback to FDE, and I was using an older phone before. From what I read, I think FBE looks like a really bad idea that sacrifices user's control on data privacy in exchange for silly amenities such as being able to use the phone as an alarm or for emergency calls even if powered off and rebooted by an unauthorized person.

The build in this thread adopts FBE natively, in fact my beyond0lte came out already encrypted just by installing the ROM (I found no way of disabling it). And this is, I'm sure, also the core reason why you cannot use TWRP with this build. But, most critically, the problem is that native FBE does not seem to allow to have two different passwords, one to insert only one time when the phone boots up, and one (like a PIN or fingerprint) to unlock the screen. This is a very desirable security feature that, I suspect, is not in the best interest of Google&friends to let you have.

Now, I have questions:

1) would it be possible to have this build without FBE enabled? So that if you want it you need to go in Settings -> Security and enable it yourself?

2) Is it possible to undo FDE on this build? Clearly not from the UI, but maybe with a rooted terminal, e.g., Magisk + Termux?

3) A bit off-topic but... If necessary to use FBE, is it at least possible to disable Direct Boot and have two different passwords, one to insert only one time when the phone boots up, and one (like a PIN or fingerprint) to unlock the screen? See this for refrence: http://www.gagliardoni.net/#android_dual_cryptfs_dec_2020

 

[Linux4]

Thank you @Linux4 for this great work, I just installed and works like a charm.

One problem though: disk encryption.

I'm entering a rabbit hole of encryption on Android now. I was not aware that Android 10+ enforces FBE (File-Based Encryption) as opposite as FDE (Full-Disk Encryption). I never realized it because this is not the case on older devices, even if on Android 11, that probably do not have storage and power to support FBE and therefore fallback to FDE, and I was using an older phone before. From what I read, I think FBE looks like a really bad idea that sacrifices user's control on data privacy in exchange for silly amenities such as being able to use the phone as an alarm or for emergency calls even if powered off and rebooted by an unauthorized person.

The build in this thread adopts FBE natively, in fact my beyond0lte came out already encrypted just by installing the ROM (I found no way of disabling it). And this is, I'm sure, also the core reason why you cannot use TWRP with this build. But, most critically, the problem is that native FBE does not seem to allow to have two different passwords, one to insert only one time when the phone boots up, and one (like a PIN or fingerprint) to unlock the screen. This is a very desirable security feature that, I suspect, is not in the best interest of Google&friends to let you have.

Now, I have questions:

1) would it be possible to have this build without FBE enabled? So that if you want it you need to go in Settings -> Security and enable it yourself?

2) Is it possible to undo FDE on this build? Clearly not from the UI, but maybe with a rooted terminal, e.g., Magisk + Termux?

3) A bit off-topic but... If necessary to use FBE, is it at least possible to disable Direct Boot and have two different passwords, one to insert only one time when the phone boots up, and one (like a PIN or fingerprint) to unlock the screen? See this for refrence: http://www.gagliardoni.net/#android_dual_cryptfs_dec_2020

1) No, due to how FBE works it needs to be enabled by default and cannot be enabled by the user later
2) Very unlikely, even if you'd disable FBE and encrypt via settings (which is for FDE) it will probably fail.
3) Not that I know of, sorry

 

[gaglia83]

1) No, due to how FBE works it needs to be enabled by default and cannot be enabled by the user later

Thank you for the reply. I know of another LOS 18 build for beyondXlte devices on this community that does come with FBE *not* enabled. That is not really good though, because for some reason also the FDE doesn't work, so it leaves the phone completely unencrypted.

This leads me to think that it is in theory possible to build the ROM *without* FBE enabled by default. The question is whether the alternative is no encryption at all, or the lack of FDE in the other build is fixable.

 

[Linux4]

Thank you for the reply. I know of another LOS 18 build for beyondXlte devices on this community that does come with FBE *not* enabled. That is not really good though, because for some reason also the FDE doesn't work, so it leaves the phone completely unencrypted.

This leads me to think that it is in theory possible to build the ROM *without* FBE enabled by default. The question is whether the alternative is no encryption at all, or the lack of FDE in the other build is fixable.

You can build without, but good luck getting FDE to work on this ...
It's deprecated and not meant to be used on new devices so I won't support it

 

[gaglia83]

You can build without, but good luck getting FDE to work on this ...
It's deprecated and not meant to be used on new devices so I won't support it

Understood, no problem, it was more of a curiosity thanks again for the great job!

 

[starbright_]

I managed to patch the system in order to enable signature spoofing for MicroG by following this guide. Here is a zip file I created for my s10e with a patched services.jar one must flash via Magisk.

This service.jar: Is is under change - so need to be recreated with each update? Or only if major version is changing? How individually is this (s10, s10e, ...?)

 

[hornedfiend]

I'm having problems with phone app. For some reason receiving calls it not showing any UI, even after installing and switching to other phone apps like Aurora or Koler. Looks like it's a deep sleep issue.
Anyone else having this issue?

 

[El Dun]

Hi, I have a question about this ROM and sadly at current no time to try this out on my own.
Does this ROM support High-Res over USB-C and do (DJI) drones work with it?
I'm asking because I have this problem with Ivans Lineage OS version:

Hi, thanks for maintaining this ROM.
after I saw in changelog you fixed USB-C audio I tried it out, but for me, High-Res audio over USB-C is still not working, basically I have the same problem I posted last year:

https://xdaforums.com/t/rom-exynos-...-v1-4-update-2020-12-17.4076585/post-83209835

I've also tested using my DJI drone with this ROM and did not get it working, while the usual warning message appears if the app is allowed to access USB, after that nothing happens. It's 100% working on stock and I did the same procedure with this ROM, also I've tried troubleshooting but couldn't get any further.
It is quite interesting that I only found this problems with AOSP ROMs, but not with stock ones, so do other (Qualcomm-based) devices have those problems with AOSP ROMs too?

 

[hajkan]

Would this work with G770F or G973F?

 

[flortsch]

This service.jar: Is is under change - so need to be recreated with each update? Or only if major version is changing? How individually is this (s10, s10e, ...?)

Not an expert here and someone correct me if I am wrong, but as I can see, the services.jar is part of Android and therefore not device specific. So it should be sufficient to update it only when bigger changes happen to underlying Android/LOS.