[ROM][G920/5-F-I-S-K-L-T-W8][9.0] UNOFFICIAL LineageOS 16.0

Search This thread

schlombie

Senior Member
Dec 28, 2010
81
7
Frankfurt

ADB100

Senior Member
Nov 3, 2006
1,489
115
Could be https://github.com/enesuzun2002/lineageos-ota/releases/tag/lineage-16.0-20200121
It was the build I answered.

Sorry, currently I not on LOS on my S6, because I had problems with encyption and switched to e foundation rom for testing. :eek:

Looking at Enes's sources it doesn't look like they are:

https://github.com/Exynos7420/android_device_samsung_zero-common/blob/nx-10.0/BoardConfigCommon.mk

However I have flashed that build you posted a link to and it says SELinux Enforcing so I am guessing there are some other sources he's using...
It has the default build fingerprint though so CTS profile check fails and its built with the public keys. I have manually changed the fingerprint in the build.prop in /system & /system/vendor and CTS profile passes and it says device is certified in the Play Store app, however the public keys is an issue. If I had the sources this was built from it would really help me out.

Cheers
Andy
 
Last edited:

ADB100

Senior Member
Nov 3, 2006
1,489
115
How to re-enable SELinux?

Looking through the history of the 'BoardConfigCommon.mk' file it looks like SELinux has been enabled and disabled a few times with it last being enabled in September 2019:

https://github.com/Exynos7420/andro...c275420#diff-581794583e89a660d8f68651b78d17f9

And then disabled again in February this year:

https://github.com/Exynos7420/andro...be536f0#diff-581794583e89a660d8f68651b78d17f9

I need SELinux enabled and enforcing. How can I use the sources to achieve this?

Cheers
Andy
 

Lunarixus

Senior Member
Dec 24, 2018
65
221
London
Looking through the history of the 'BoardConfigCommon.mk' file it looks like SELinux has been enabled and disabled a few times with it last being enabled in September 2019:

https://github.com/Exynos7420/andro...c275420#diff-581794583e89a660d8f68651b78d17f9

And then disabled again in February this year:

https://github.com/Exynos7420/andro...be536f0#diff-581794583e89a660d8f68651b78d17f9

I need SELinux enabled and enforcing. How can I use the sources to achieve this?

Cheers
Andy

I'm gonna jump in here and point out that the S6 has never had enforcing SELinux.

The reason you see it enabled is because it uses a kernel edit called "fake enforce" which spoofs an enforcing SELinux but ignores all denials.

The current SEPolicy found in both Enes and TeamNexus' trees is from the Exynos 7580 series which is NOT compatible with our phone.

Proof: https://github.com/Exynos7420/andro...360cba00a4b90d627f5efe2/sepolicy/device.te#L6

Unless you're going to rewrite SEPolicy yourself there is no way to make it enforcing by just enabling something.

- Nathan.
 
  • Like
Reactions: enesuzun2002

ADB100

Senior Member
Nov 3, 2006
1,489
115
I'm gonna jump in here and point out that the S6 has never had enforcing SELinux.

The reason you see it enabled is because it uses a kernel edit called "fake enforce" which spoofs an enforcing SELinux but ignores all denials.

The current SEPolicy found in both Enes and TeamNexus' trees is from the Exynos 7580 series which is NOT compatible with our phone.

Proof: https://github.com/Exynos7420/andro...360cba00a4b90d627f5efe2/sepolicy/device.te#L6

Unless you're going to rewrite SEPolicy yourself there is no way to make it enforcing by just enabling something.

- Nathan.

I am not going to pretend I fully understand what you have written.... However in the file 'BoardConfigCommon.mk' there is a section that I am guessing triggers whether the ROM is built with SELinux enabled (enforcing?) or disabled. In Enes sources this is now commented out and this coincides with a commit to disable SELinux.

https://github.com/Exynos7420/andro...7360cba00a4b90d627f5efe2/BoardConfigCommon.mk

If this is a 'trick' to make Android think SELinux is enforcing then I'm fine with that. My issue is ensuring apps that check the security will run - Banking Apps, Google Pay, NetFlix etc. I know SafetyNet needs to pass and the device appear 'Certified' in the Play Store app, however some other apps (certainly the Sky Go and Santander apps) check other things as well - SELinux being one of them (I think?).

With my own current builds of 15.1 everything I need works - SafetyNet passes, SELinux is (or appears to be) enforcing and I am using my own certificates to sign the build. With the 16.0 builds I have tried so far I have had issues with apps that check security and then fail to run, therefore I am looking for 16.0 sources that I can use that work as well as my own 15.1 sources.

Cheers
Andy
 

Lunarixus

Senior Member
Dec 24, 2018
65
221
London
I am not going to pretend I fully understand what you have written.... However in the file 'BoardConfigCommon.mk' there is a section that I am guessing triggers whether the ROM is built with SELinux enabled (enforcing?) or disabled. In Enes sources this is now commented out and this coincides with a commit to disable SELinux.

https://github.com/Exynos7420/andro...7360cba00a4b90d627f5efe2/BoardConfigCommon.mk

If this is a 'trick' to make Android think SELinux is enforcing then I'm fine with that. My issue is ensuring apps that check the security will run - Banking Apps, Google Pay, NetFlix etc. I know SafetyNet needs to pass and the device appear 'Certified' in the Play Store app, however some other apps (certainly the Sky Go and Santander apps) check other things as well - SELinux being one of them (I think?).

With my own current builds of 15.1 everything I need works - SafetyNet passes, SELinux is (or appears to be) enforcing and I am using my own certificates to sign the build. With the 16.0 builds I have tried so far I have had issues with apps that check security and then fail to run, therefore I am looking for 16.0 sources that I can use that work as well as my own 15.1 sources.

Cheers
Andy

Safetynet doesn't require SELinux enforcement to pass, I can confirm this for all of my Pixels, my Xiaomi devices and many others.
You most likely just need to spoof props correctly.
 

marcelo007

New member
Jul 14, 2020
1
0
Working for me

I downloaded the ROM and the Gapps. Actually This lineage OS is android 10! It surprised me but i loved it! I recommend, fixed the bugs i was having with my old firmware nugget 7.

Steps:
1 - download ROM and Gapps Android 10
2- go to the recovery TWRP
3 - wipe dalvik, data, system, cache
4 - install ROM
5 - install Gapps
6- reboot and have fun
 

ADB100

Senior Member
Nov 3, 2006
1,489
115
Safetynet doesn't require SELinux enforcement to pass, I can confirm this for all of my Pixels, my Xiaomi devices and many others.
You most likely just need to spoof props correctly.

Hmm... I thought I had. With my 15.1 builds its the 'BUILD_FINGERPRINT' value in build.prop that needed changing to a stock fingerprint one to get it to pass the CTS Profile check. I have this in my sources and can confirm its in the build.prop in the resulting ROM. I'll have to do some more playing.
 

Johannesdavidsen

Senior Member
Jan 22, 2020
75
15
32
Upernavik
Hmm... I thought I had. With my 15.1 builds its the 'BUILD_FINGERPRINT' value in build.prop that needed changing to a stock fingerprint one to get it to pass the CTS Profile check. I have this in my sources and can confirm its in the build.prop in the resulting ROM. I'll have to do some more playing.

Hi i`m not supposed to respond here but i`m very excited of your Work.
Did you add all knox files and folders? In the system.
And E Foundation has SE Linux Enforcing i think.
And i have been experimented long time ago, with Stock / Nano Rom Marshmallow and added back, knox folders and files in the system and then
if i remember right SE become enforcing i might have did something more before that and maybe i might have edited prop file too
And maybe add some data from twrp backup data
maybe edit some 0 to 1 in stock build.prop i can`t remember what but i was searching it on google to enable enforcing mode and to-
enable those needed to use stock apps like Health app and private mode and other stuff but tested private mode and it not worth to have files there, i might done bad somewhere
it cool.. i hope you get there to get it Work and i hope for your Work to be released here..

Noob from Greenland.. :p

Edit: I have edited something like 1 to 0 on build.prop i guess
Just try to get some 1's to 0 somewhere on build.prop in ur work and place those files with ur tools and with ur works
Good Luck I'm not so good to English words sometimes sorry about that..
 
Last edited:

Azhar.iq

Member
Jul 25, 2017
20
0
Recently installed this ROM, falling back from 17.1

I wiped and clean installed everything. I didn't installed openGapps, but did install microG. All of the apps are working (the ones i need).

My question is, if almost everything can be done without openGapps, even the pico version, then why is it recommended to install it???? What am i missing??
 

chelsea_21

Member
Apr 4, 2019
33
8
Sharjah
Recently installed this ROM, falling back from 17.1

I wiped and clean installed everything. I didn't installed openGapps, but did install microG. All of the apps are working (the ones i need).

My question is, if almost everything can be done without openGapps, even the pico version, then why is it recommended to install it???? What am i missing??

IS THE ROM GOOD, THINKING OF TESTING IT out again
 

Johannesdavidsen

Senior Member
Jan 22, 2020
75
15
32
Upernavik
Had some problems with it. It felt slower, and wouldn't respond as fast as the 17.1, so i moved to Resurrection Rom 7.0.1. So far its stable and responsive.

Hi recognise me?
Is Resurrection Rom 7.0.1 good? Give update. . .
And I tested his build 21 Jan LOS 16. It almost the same as build 28 Feb LOS 17.1 I think it good enough very much more better with Battery charge changeble on current so it can be lower amps lower charging so it can charge slower and not warm
And default is fast charge I think.. So thumbs up for that :good:
Lol I downloaded it because 21 Jan is my birthday :p
 

Johannes89

Senior Member
Aug 12, 2020
116
5
New build is released check that out

Beautiful work didn't find any problem.
I didn't test for other apps yet:good:

Edit: I think now i know what causes 'Video screen mess up' problem.
I'm thinking it may be when phone is on battery saver or on 'rooted and tweaked CPU' caused some video screen messed up problems when it can't follow what going on apps... So I will test on 17.1 again without changing anything thanks for reading.
No problem on Tiktok app for now. Lol
 
Last edited:
Sep 26, 2014
6
1
Cant get PC to recognize USB

I cannot get any PC to recognize the phone on the USB cable.

Phone: SM-G920W8
Build: zerofltexx-userdebug 9 PQ3A.190801.002 eng.enesuz.20200418.174126 test-keys

Tried setting USB configuration to File transfer, USB tethering, PTP and no data transfer - no worky

Set developer mode. Tried setting USB default configuration to File transfer, USB tethering, PTP and no data transfer - no worky

No MTP listed anywhere.

Read the thread and nothing helped.

Suggestions?
 

Johannesdavidsen

Senior Member
Jan 22, 2020
75
15
32
Upernavik
I cannot get any PC to recognize the phone on the USB cable.

Phone: SM-G920W8
Build: zerofltexx-userdebug 9 PQ3A.190801.002 eng.enesuz.20200418.174126 test-keys

Tried setting USB configuration to File transfer, USB tethering, PTP and no data transfer - no worky

Set developer mode. Tried setting USB default configuration to File transfer, USB tethering, PTP and no data transfer - no worky

No MTP listed anywhere.

Read the thread and nothing helped.

Suggestions?

Maybe you need Samsung drivers?
What distro do you use?
Windows? Or Linux
It could be your phones USB port try other Usb's
If not it is damaged this phone is very annoying when USB port is old I transfer files only while holding phone and micro USB together lol
 
Last edited:

Johannes89

Senior Member
Aug 12, 2020
116
5
How do i increase call volume??
On a normal call, sound is too low to understand clearly what other person is saying.
Please guide.
Hey so I have edited system volume values.
Please check my comments on 17.1 section just search my other account name Johannes Davidsen on comment sections. I have forgotten my password so I have created new account
I use that other account only on my laptop..
There are 3 steps for that 1 text file
I couldn't post a file attachment here lol
If you will use my edits make sure to edit it by yourself
Because it is very LOW VOLUME lol
Have fun editing..?

---------- Post added at 07:53 AM ---------- Previous post was at 07:25 AM ----------

I build LOS 15.1 for S6, S6 Edge and HTC One M8 once a month when the security patches are merged. Everything I use is available online to everyone. I include a few tweaks so that it passes SafetyNet (Build Fingerprint), RIL fix so it doesn't crash when viewing the call forwarding settings, the supposed fix for the call echo and I use my own keys so that apps that check for it being built with public keys and then either moan or won't work will work (Sky Q/Go for example).
Anyone can replicate this. I am not doing anything special. I don't tweak anything with the HTC One M8 builds.
Apparently my builds for S6/S6 Edge still have the call echo bug, however I don't experience this myself - or at least the callers I speak to don't complain about it.

I am reluctant to share my builds as I simply don't want the grief of trying to please people when they say something doesn't work. I am not a programmer, nor do I have the time to debug things. I simply have access to some compute and storage that allows me to kick off some scripts to build this once a month for myself. I have a S6, a S6 Edge and a HTC One M8.
That why your builds are not visible.
I could be your tester I don't care about brick
Or softbrick I could test only software related apps not banking I don't have credit card yet..
It could be so cool to use S6 as paying with Lineage Os..
You can see me crying lol

---------- Post added at 08:00 AM ---------- Previous post was at 07:53 AM ----------

I cannot get any PC to recognize the phone on the USB cable.

Phone: SM-G920W8
Build: zerofltexx-userdebug 9 PQ3A.190801.002 eng.enesuz.20200418.174126 test-keys

Tried setting USB configuration to File transfer, USB tethering, PTP and no data transfer - no worky

Set developer mode. Tried setting USB default configuration to File transfer, USB tethering, PTP and no data transfer - no worky

No MTP listed anywhere.

Read the thread and noth
ing helped.

Suggestions?
Yo did you check TWRP ?
It could be there
On Mount section
Edit: If it Linux sometimes it doesn't recognise Android USB
(Use Windows to try-to connect)
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 65
    https%3A%2F%2Fimg.xda-cdn.com%2Fy-LtXHGCDBH0KxFw9MxWAPF3guk%3D%2Fhttp%253A%252F%252Fi.imgur.com%252F2okPze5.png

    Note: This is not a ROM based on the ROM shipped with your device.

    LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.

    Custom Features Overview:
    • Hyper - Kernel
    • Custom Power Hal by TeamNexus
    • Many More

    What's working:
    • Telephony (Calls, SMS, Mobile Data)
    • WiFi
    • Bluetooth
    • NFC
    • GPS (Plain Device Mode Works)
    • Fingerprint
    • Camera (Needs Improvements)
    • HWC

    What's not working:
    • Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. We may have our own implementation to similar functions, though.
    • IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.

    Instructions:
    • Make sure TWRP has been installed and functional.
    • Download the latest build (and optionally gapps).
    • Reboot to recovery
    • Wipe data and cache (required if you switch from other ROMs)
    • Flash the latest build (and gapps)
    • Reboot

    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)

    Telegram Group:

    Samsung Galaxy S6 LineageOS Development: https://t.me/joinchat/GhF7_U8IaarGQ2Y08NWilg

    Donate:

    I do this in my free time and currently i work on this alone. If you want to support the project feel free to donate

    XDA:DevDB Information
    LineageOS, ROM for the Samsung Galaxy S6

    Contributors
    enesuzun2002, lukasb06, u99dev, TeamNexus
    Source Code: https://github.com/Exynos7420

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x

    Version Information
    Status: Beta
    Current Beta Version: 20181219
    Beta Release Date: 2018-12-19

    Created 2018-12-19
    Last Updated 2020-04-18
    26
    Changelog:

    ---------------
    2019-08-16
    ---------------

    ---------------
    2019-06-14
    ---------------

    • Changelog on download link upcoming builds will be too


    ---------------
    2019-04-01
    ---------------

    • Improved Camera Quality
    • Disabled Input Booster (battery life should increase)
    • Updated Blobs to ESA1 firmware with January Security Patch
    • Synced LineageOS Source

    ---------------
    2019-03-21
    ---------------

    • Rom isn't prerooted anymore
    • Removed FDroid
    • Readded Jelly
    • PowerProfiles optimized for better battery life
    • Fixed the Cpu freq perms for non-root apps
    • LineageOS Sources Synced

    ---------------
    2019-03-09
    ---------------

    • March Security Patch
    • LineageOS Sources Synced
    • Improved GPS Performance
    • Fixed robotic sound issues with some apps
    • StatusBar Icon Padding Removed
    • Wi-Fi configuration is updated to match stock one (better Wi-Fi stability)
    • Trust Hal (Some new security stuff check Trust from Settings)
    • Switched back to G920F-EQL7 source based kernel (new one had graphic glitches while playing youtube videos i don't have time to fix it)

    ---------------
    2019-02-11
    ---------------

    • Swap is enabled
    • GPS performance is improved
    • Switch to LineageOS Samsung Audio Hal
    • February Security Patch
    • Synced LineageOS Source

    ---------------
    2019-01-25
    ---------------

    • Uprev Hals and Improve Performance
    • Improved Battery Life (Now you won't lose battery on reboot or the last %15 won't drain fast)
    • Booting time significantly descreased
    • Updated Hyper-Kernel to A810F CHR7 Oreo Source
    • Vendor Security Patch Date is 2017-12-01 (i know it is old, i will update blobs soon)
    • Synced LineageOS Source

    ---------------
    2019-01-21
    ---------------

    • NFC is fully stable now
    • Updated PowerProfiles (Battery Life and smoothness Improved)
    • Improved Overall stability
    • AOD is enabled now
    • Hyper-Kernel Updated
    • Wi-Fi Hotspot is Fixed
    • FDroid updated
    • Phone Boots Much Faster Now
    • Fixed MMS sending for carriers that use separate mms apn
    • Fixed LineageHW java overlays (many more features in rom now)
    • Synced LineageOS Sources

    ---------------
    2018-12-19
    ---------------

    • Initial Release
    16
    F.A.Q.

    It is a good idea to read here before asking same question


    1- Q: How can i report a bug?
    A: Download Syslog app from Google Play Store and send me all log types and explain the bug clearly please.

    2- Q: I have a tmobile device and can't connect LTE what should i do?
    A: Try this workaround (till i find a real fix for that) by @bohica888: https://forum.xda-developers.com/showpost.php?p=81732753&postcount=602
    8
    Hi everyone! I took the liberty of fixing the build errors in the hardware samsung_slsi official repos to be able to build zerofltecan, zerofltexx, zeroltecan, and zeroltexx, with the standard lineage codebase.

    With enusuzun2002's permission, here are my roomservices:

    zerofltecan
    zerofltexx
    zeroltecan
    zeroltexx

    and my builds:

    zerofltecan
    zerofltexx
    zeroltecan
    zeroltexx
    7
    Changelog

    Build 0716 for all 4 variants (link in my signature)
    * Partial HWC fix that I had mistakenly overlooked in my previous builds, but I am familiar with these changes because I use them in my S7 builds, from Ivan_Meler's sources. PLEASE NOTE: This is NOT something new! enesuzun2002 had included these changes in his own builds.

    surfaceflinger: check for unreliable retire-fences before invalidating
    [TEMP] graphics: libhwc2on1adapter: fix up layer handles

    Once Ivan_Meler pushes his finalized HWC fix, I will be sure to cherry-pick it into my forks of enesuzun2002's S6 sources.

    * Synced with LineageOS sources.

    You should be able to dirty flash my builds overtop of enesuzun2002's lineage-16.0 builds. However, if in doubt, do a clean flash.

    Q: Why don't you make use of the Lineage OTA Updater in your builds?
    A: Because I upload to Google Drive, it is impossible to use Lineage's OTA updater because the download URL of the build would have to be predicted prior to building and merged into the OTA updater's settings. Because Google Drive only assigns a file ID once a file is finished uploading, it is impossible to predict the file ID ahead of time to insert it into the OTA updater. I use Google Drive because of virtually zero downtime and generally fast download speeds. I have used Android File Host and BasketBuild in the past, as well as Mega, and all these services had let me down at one point or another. Not that Google Drive is perfect, but it has been the most reliable for me. However, for those unfamiliar, the easiest way to be able to download my updated builds straight to your phone is to add your variant's folder from my account to your account as a shared folder.