[ROM][SM-G920F][zerofltexx] LineageOS 15.1 UNOFFICIAL for the Galaxy S6

Search This thread

Sub_Zero2

Senior Member
Jun 28, 2010
478
505
Sørreisa
Samsung Galaxy S9
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.

Code:
#include <std_disclaimer.h>

/*
 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

This is an unofficial LineageOS 15.1 build for the international Galaxy S6 (SM-G920F).
It is a signed build that is Selinux Enforcing.
Please test and post about what's not working, and please provide logs (logcat and last_kmsg).

These builds are based on work for the SM-G920F done by (but not limited to): enesuzun2002, lukasb06, u99dev, TeamNexus, Sub_Zero2 and the rest of the (Galaxy S6) LineageOS team.

Latest update

* July 2019 Security patches
* Synced with LineageOS Sources 12th of July 2019

Latest security patch

* July 2019

Additional changes/Repopicks:

* None in particular

What's currently Not working:

* Power performance profiles
* You tell me! (Please provide logs)

Instructions

1. Flash TWRP recovery via Odin.
2. Boot to TWRP recovery (Vol UP + Home + Power).
3. Optional: Wipe data / Factory Reset (If you are coming from another ROM, then you should atleast wipe data + cache).
4. Install the ROM (Lineage zip).
5. Optional: Install LineageOS su addon (Choose addonsu-15.1-arm64-signed.zip) or Magisk to get root.
6. Install the google apps (OpenGapps). Choose ARM64 Android 8.1
7. Reboot

Downloads

LineageOS 15.1: lineage-15.1-20190712-UNOFFICIAL-zerofltexx.zip
Twrp 3.3.1-0: https://eu.dl.twrp.me/zeroflte/
LineageOS AddonSU: addonsu-15.1-arm64-signed.zip
OpenGapps: OpenGapps

Sources

https://github.com/SubZero7748/android_kernel_samsung_exynos7420
https://github.com/SubZero7748/android_device_samsung_zerofltexx
https://github.com/SubZero7748/android_vendor_samsung_zerofltexx
https://github.com/SubZero7748/android_device_samsung_zero-common
https://github.com/SubZero7748/android_vendor_samsung_zero-common

Credits
LineageOS Galaxy S6 Team
Team Nexus

XDA:DevDB Information
[ROM][SM-G920F][zerofltexx] LineageOS 15.1 UNOFFICIAL for the Galaxy S6, ROM for the Samsung Galaxy S6

Contributors
Sub_Zero2, enesuzun2002, lukasb06, u99dev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS

Version Information
Status: Beta

Created 2019-03-10
Last Updated 2019-07-13
 
Last edited:

Sub_Zero2

Senior Member
Jun 28, 2010
478
505
Sørreisa
Samsung Galaxy S9
Never.

---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------

Why another unofficial LineageOS 15.1?
Where is the other one(s)?
Except for the unified projects ofcourse..
As for why: I just wanted a updated signed build with the latest security patches for my device (got it a couple of days ago).
 
Last edited:

ADB100

Senior Member
Nov 3, 2006
1,495
119
Kernel

Hi, I haven't tried your ROM, however have you got around the initial boot message 'KERNEL IS NOT SEANDROID ENFORCING' ?
I have been building unofficial LineageOS 15.1 for zerofltexx and zeroltexx for a while using the official LineageOS repos and Ennes zero.xml but have always had this error on boot. I am using my own keys to get around an issue with the Sky-Q app, but the error was there when using the public keys as well.

recovery-is-not-seandroid-enforcing.png


I know this isn't an image from a S6 - however its the same message....

If I wipe and flash Ennes ROM I don't get this error - although being built with the public keys causes other issues so I prefer to build it myself.

My ROM works perfectly other than this and it seems to have no ill effect, however I'd rather it didn't happen.

Cheers
Andy
 
Last edited:

Sub_Zero2

Senior Member
Jun 28, 2010
478
505
Sørreisa
Samsung Galaxy S9
Hi, I haven't tried your ROM, however have you got around the initial boot message 'KERNEL IS NOT SEANDROID ENFORCING' ?
I have been building unofficial LineageOS 15.1 for zerofltexx and zeroltexx for a while using the official LineageOS repos and Ennes zero.xml but have always had this error on boot. I am using my own keys to get around an issue with the Sky-Q app, but the error was there when using the public keys as well.

recovery-is-not-seandroid-enforcing.png


I know this isn't an image from a S6 - however its the same message....

If I wipe and flash Ennes ROM I don't get this error - although being built with the public keys causes other issues so I prefer to build it myself.

My ROM works perfectly other than this and it seems to have no ill effect, however I'd rather it didn't happen.

Cheers
Andy
It happens on my build as well... It 's there for a second or two before the lineage logo appears.
Both trust and device info says enforcing, so it seems good.
I'll let you know if i stumble into the solution to this
 

ADB100

Senior Member
Nov 3, 2006
1,495
119
It happens on my build as well... It 's there for a second or two before the lineage logo appears.
Both trust and device info says enforcing, so it seems good.
I'll let you know if i stumble into the solution to this

OK, thanks. Let me know if you find the fix.
It looks like we are both building the same ROM - although you are braver than me and releasing it :eek:
I have access to both a zerofltexx and a zeroltexx so I have been building for both. Are you cooking in the build fingerprint workaround to pass the CTS profile check of SafetyNet?

Cheers
Andy
 
  • Like
Reactions: duttyend

kuk218

New member
Mar 13, 2019
1
1
OK, thanks. Let me know if you find the fix.
It looks like we are both building the same ROM - although you are braver than me and releasing it :eek:
I have access to both a zerofltexx and a zeroltexx so I have been building for both. Are you cooking in the build fingerprint workaround to pass the CTS profile check of SafetyNet?

Cheers
Andy

https://xdaforums.com/galaxy-s6/sam...ified-development/oreo-xerium-kernel-t3882244
You can flash fstab patcher from this thread.
 
  • Like
Reactions: duttyend

ADB100

Senior Member
Nov 3, 2006
1,495
119

I had a look at the scripts in that patch and found references to 'Append SEANDROIDENFORCE to boot / recovery image'. I found this for different hardware but it might help
https://review.lineageos.org/c/LineageOS/android_device_samsung_msm8976-common/+/159742

Been through the files for Exynos7420 and can't find the line 'TARGET_IMAGE_APPEND_STRING := SEANDROIDENFORCE' in the kernel section. I might try a build on my spare S6 Edge with this added and see what happens..

Andy

---------- Post added at 09:12 AM ---------- Previous post was at 08:42 AM ----------

I had a look at the scripts in that patch and found references to 'Append SEANDROIDENFORCE to boot / recovery image'. I found this for different hardware but it might help
https://review.lineageos.org/c/LineageOS/android_device_samsung_msm8976-common/+/159742

Been through the files for Exynos7420 and can't find the line 'TARGET_IMAGE_APPEND_STRING := SEANDROIDENFORCE' in the kernel section. I might try a build on my spare S6 Edge with this added and see what happens..

Andy

I think this should already be set from here: https://github.com/LineageOS/android_hardware_samsung/blob/lineage-15.1/mkbootimg.mk

So maybe something else? Ennes has obviously solved this as this message doesn't appear with his ROMs.
 
  • Like
Reactions: duttyend

ADB100

Senior Member
Nov 3, 2006
1,495
119
I had a look at the scripts in that patch and found references to 'Append SEANDROIDENFORCE to boot / recovery image'. I found this for different hardware but it might help
https://review.lineageos.org/c/LineageOS/android_device_samsung_msm8976-common/+/159742

Been through the files for Exynos7420 and can't find the line 'TARGET_IMAGE_APPEND_STRING := SEANDROIDENFORCE' in the kernel section. I might try a build on my spare S6 Edge with this added and see what happens..

Andy

---------- Post added at 09:12 AM ---------- Previous post was at 08:42 AM ----------



I think this should already be set from here: https://github.com/LineageOS/android_hardware_samsung/blob/lineage-15.1/mkbootimg.mk

So maybe something else? Ennes has obviously solved this as this message doesn't appear with his ROMs.


Tried adding TARGET_IMAGE_APPEND_STRING := SEANDROIDENFORCE' to the BoardConfigCommon.mk in the zero-common folder and compiling and it doesn't make any difference...
 
Last edited:
  • Like
Reactions: duttyend

Sub_Zero2

Senior Member
Jun 28, 2010
478
505
Sørreisa
Samsung Galaxy S9
OK, thanks. Let me know if you find the fix.
It looks like we are both building the same ROM - although you are braver than me and releasing it :eek:
I have access to both a zerofltexx and a zeroltexx so I have been building for both. Are you cooking in the build fingerprint workaround to pass the CTS profile check of SafetyNet?

Cheers
Andy
I have not unless it's in the sources i forked allready
 
  • Like
Reactions: duttyend

Sub_Zero2

Senior Member
Jun 28, 2010
478
505
Sørreisa
Samsung Galaxy S9
Tried adding TARGET_IMAGE_APPEND_STRING := SEANDROIDENFORCE' to the BoardConfigCommon.mk in the zero-common folder and compiling and it doesn't make any difference...
I came to think about something, at the beginning of the build, there is a warning:
Code:
warning BOARD_SEPOLICY_VERS not specified, assuming current platform version
I'm not sure if this is causing it, but i don't have time to test it until later on...
 
  • Like
Reactions: duttyend

Top Liked Posts