Database Users

[Q] Knox-Free Rom and SELinux Question

TL;DR
If I flash a ROM which is "KNOX Free" (such as ExtremeDebloat Rom by elliwigy), will I be able to set SELinux to Permissive?
Details
Ultimately, I am trying to get my appradio 3 to be able to send touch screen input to my S5 (SM-G900V). I believe the reason I cannot get it to work yet is because SELinux is in Enforcing mode. There is an app called SELinux Mode Changer that allows you to toggle from Enforcing to Permissive by just tapping a button, but from what I have been able to find while researching the issue, it will not work on KNOX-enabled devices such as the Galaxy series. If I use SafeStrap on my rooted device (since the SM-G900V has a locked bootloader), flash a rom without KNOX, and install SELinux Mode Changer, will I be able to set SELinux to Permissive?
I apologize if this has been answered somewhere else on XDA. I searched but was unable to find an answer on here. Honestly, I'm a noob with this stuff so I might have even come across an answer and not recognized it haha.

I'm on a knox free ROM and just tried the selinux app and it didn't work.
Edit: there's a setting in the Wanam xposed module to turn off selinux but that doesn't seem to work either, just fyi.
Sent from my SM-G900V using Tapatalk

Thanks for the info. It saved me a lot of time trying to test that out myself haha.
So currently no one has found a way to set SELinux to Permissive on the SM-G900V variant of the S5?

Hmm... I'll try this on mine. I did this on the stock rom with Knox disabled, and SELinux installed fine, set to permissive, said it worked...I was just tinkering with trying to get Airwatch to work with root, and needed it in permissive mode to install Rootcloak. I got rootcloak installed and it seemed to be fine with the permissive setting in SELinux, but I never got Airwatch to work, so I just gave up.
Currently I am on SlimHyde, I'll try SELinux on it and see what it says.
EDIT: Well, it doesn't work now, so either I imagined it working, or...I dont know...sorry.

Thanks. Yeah the app always says it worked but if i exit and go back in it says it is enforcing again and the status under About Phone never changes.
Also, when Super User is first started, it asks if you want it to try to disable KNOX. I said yes and it said it was successful. What exactly did it do?

How to hide: Kernel is not seandroid enforcing set warranty bit: Kernel?

Hi everybody!! I've installed cyanogenmod 11 on galaxy s5 g900f stock with root. Now at boot it show this message: "Kernel is not seandroid enforcing set warranty bit: Kernel". How can I hide it? However the phone works well. The message shows also when I connect it to charger. How can I change the ugly charging battery animation? Thank you in advance

Anyone can help me?

glegoodroid said:
Anyone can help me?
Click to expand...
Click to collapse
i am still currently finding out how to disable the error , by the only way is to flash back Stock ROM into the phone so SnapDragon SECURE BOOT will not have problems will third party kernels . . . , i will update you once i done a research to disable SnapDragon Secure Boot ! :good:
---------- Post added at 09:08 PM ---------- Previous post was at 09:03 PM ----------
When you flashed from MKE the newer locked bootloader JB is already contained 4.3, which now more aggressively responds in conjunction with the eFuse chip if you try a different kernel or recovery on your Galaxy S4 to flash. Not only that you have you now changed in all probability due to the flash the CF-Auto-Root Kernel, the Knox Warranty Void recognition to 0x1, you'll love this regard with the message of life must, because you've made ​​a change in the system by the eFuse- chip and bootloader was detected . If you want to understand it so, the eFuse chip as a kind of guardian because that monitors not only the boot loader, but also the SELinux kernel, and the CWM Recovery . In conjunction with the bootloader, which acts as a kind of BIOS, will now be started for the system normally because of your made ​​flash operations, but detects the change as such, which is out now displayed accordingly. If you have very bad luck now (will most likely also occur), you will get with subsequently installed root apps also some problems that are being monitored by the Knox apps to avoid the additional system modifications you make will. If you do then you bear with the idea that you some Knox Apps example, try the app Titanium Backup to remove it, you'll end up in a subsequent reboot your Galaxy S4 in a bootloop and your Galaxy S4 can not start. This means in turn then for you that you get this error only resolved when you XXUEMKE new flashst the original Samsung firmware build on the PC Odin Flash program on your Galaxy S4. As you will probably notice about my design now, you have almost no more opportunities your Galaxy S4 to manipulate the way you would want it but you yourself to make certain modifications to your usual Galaxy S4, then without problems to get , :good:

SM-G900F CM12.1 ERROR "KERNEL IS NOT SEANDROID ENFORCING SET WARRANTY BIT: KERNEL"

CyanogenMod 12.1 ERROR "KERNEL IS NOT SEANDROID ENFORCING SET WARRANTY BIT: KERNEL"
Hi. I am working on a brand new Samsung SM-G900F i.e. a Samsung Galaxy s5.
I shall explain how I have got where I have got below - which ended up with a rooted, working phone running CyanogenMod 12.1, Android 5.1.1 and with the GAPPS (Google Apps) on it, but the question is simply this: -
"How do I get rid of the error message that appears when I boot at the top left of the screen
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
?"
I have set out the following in detail, in case the sequence of steps I undertook will assist other users, or enable them to recognise whereabouts in the sequence they are experiencing errors.
1) I am in the UK. The phone is a brnd new, boxed Samsung SM-G900F which uses LTE (it says so on the box, whatever LTE is).
2) The phone is not network locked: I bought it from MobilePhonesDirect (a big online retailer here in the UK) but I have a Vodafone (UK) SIM card in it, and it has hitherto worked. I am porting a number across to it such port taking effect today.
3) On the new phone I downloaded an upgrade to Android 5.0. I then encrypted the phone which took less than an hour, but quite a long time nonetheless.
4) This wasn't good enough! I wanted Android 5.1 or Android 5.1.1, so ....
5) I connected the phone to my Windows 10 PC via USB, and I attempted to use Kies. This told me to use a newer product called Smart Switch to communicate with the phone. I installed this and was able to communicate.
6) I used ODIN 3.07 to flash things to the phone. I flashed CF-Auto-Root-klte-kltejv-smg900fq and I successfully rooted the phone. Upon boot it was still running Android 5.0 and it was still encrypted.
7) I flashed ClockWorkMod (CWM) to the phone, this version: g900f-cwm-recovery-6.0.4.7
8) I flashed the following zip files to the phone [TN]-VM12.1-20150327-2.0.0-klte and gapps-5.1.x-20150324-minimal-edition-signed.
9) The phone started to boot, but I got the Cyanogenmod 12.1 "Encryption Unsuccessful" message and it would not get past that.
10) I read up. I had used the wrong Cyanogenmod file, I think. I then discovered that as the phone would not boot I was unable to get any files onto it.
11) I then, from CWM, did a factory reset, wiped the cache, and wiped the Dalvik cache
12) I discovered the wonderful, wonderful ADB feature in CMW. I managed to find a piece of software called fastboot.zip. Eventually I worked out the sequence of commands and the syntax (thanks to a YouTube video which I wished to link to but I cannot find what it was I used last night!).
12) I flashed these two slightly different CyanogenMod 12.1 / GAPPS files to the phone: cm-12.1-20150428-UNOFFICIAL-klte.zip and gapps-lpmr1-20150324-signed.zip.
13) It still had errors. I went back to CWM and I "unmounted" and "formatted" this, that and everything, and I eventually got those two zips to work.
13) The phone now functions effectively, BUT ....
14) I still get the error message
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
The above took me about 4 and a half hours in total, watching YouTube tutorial videos etc etc.
I am very grateful for all of those who share their knowledge. I would love it if someone knew how to get rid of that error message. I read something about it being Samsung Knox. I tried to run a command line command from a terminal emulator on the phone, but I got an error message.
BlameTheMachines
(to quote Duran Duran!)

This error is normal because CM12.1 has unsecured kernel. CM12.1 Kernel doesn't support SEAndroid and is not secured so that's why you are getting this error.

Bruce666 said:
This error is normal because CM12.1 has unsecured kernel. CM12.1 Kernel doesn't support SEAndroid and is not secured so that's why you are getting this error.
Click to expand...
Click to collapse
Many thanks. Would you have any idea how I can work around this? When using CM 12.1 and Android 5.1 on my Galaxy SIII up until yesterday there has been no issue (except the fundamental crash issue on power loss reported in my post today elsewhere on this Forum!).
Any tips would be appreciated, and at least I now know it is CM 12.1 not any of the other permutations and combinations of my set-up. I thought of posting on here: http://forum.cyanogenmod.org/
All the best,
BlameTheMachines

Building and running a custom kernel on a stock ROM S10 SM-G973F exynos

Hey all, for some development work I am required to build a custom kernel with some non-standard features on the Samsung S10 SM-G973F Exynos model. Could anyone point me to the best way to get this done? I have a feeling have way over-thought this issue...
I have tried many different kernel configs. Getting the kernel built for my phone's ROM version is not the issue, it's actually getting it to boot. I've disabled a lot of the security features (not all) and either the phone goes into a boot loop, or Heimdall/ODIN cannot finish the boot flash because I get that "You can only run samsung images" error message (paraphrased), and the "OEM unlocking" developer option goes missing until I factory reset and screw around with the phone's date. Also noticed topjohnwu of Magisk posted some details about this as a challenge that had to be overcome for S10 support.
Anyway Im just wondering if maybe I am missing anything really obvious: like can I do this somehow with Magisk (replace the kernel magisk uses? i know magisk does some kind of kernel patching, but not sure if its different for the S10.) or, maybe someone else has gotten a custom kernel going via different meants.
Thanks in advance!

Samsung Galaxy J370f SIM stopped working after custom ROM and Kernel

I wanted to change my phones SELinux status to permissive. I've tried everything, but it just wasn't working. After some deliberation i downloaded this https://forum.xda-developers.com/galaxy-j7-2017/development/rom-godness-one-ui-t3936809 Custom rom. Don't get me wrong, it works great, but SELinux is still Enforcing on paper which doesn't work with the app. After that failed, i flashed this https://forum.xda-developers.com/galaxy-j7-2017/development/kernel-refined-kernel-v2-5-t3731176 Kernel. My phone booted, I opened settings and there it was. Permissive. I was happy for a very short while since I noticed that my SIM card wasn't working. I've removed it, moved it to different slots and nothing is happening, can't access the SIM menu either. I've tried installing a stock Sboot with Odin, but it always says fail (i don't really get this process). Any suggestions?

https://forum.xda-developers.com/galaxy-j7-2017/help/sim-issues-bootloader-t3960740
In short, custom kernels aren't compatible with new bootloaders (SIM issues) and you can't downgrade them. We'll have to wait until someone looks into it.
You need to install the latest stock ROM.