Database Users

How can I change SELinux from Enforcing to Permissive on Samsung Galaxy Note 3

Hi to all
I want to found a simple solution(other a kernel) to change SELinux from Enforcing to Permissive on Samsung Galaxy Note SM-N9005 on MJ7 firmware.
Because I want to install LBE SECURITY and it don't work with statu Enforcing.
Thanks for all way Friends

Why not change kernel?
Sent from my SM-N9005 using xda app-developers app

Kernel was not stable and make some error with last firmware(camera ,spen ...)

as things look right now a custom kernel is the only way to get selinux = permissive.
But if you looking for privacy stuff use xposed with xprivacy module.
Beats LBE and all the other crap

Thanks for idea xprivacy module Zroice but Not a modification with edit the build existing ?
Envoyé de mon SM-N9005 en utilisant Tapatalk

On S4 Mini I9195 now whit Knox and stock kernel...
To turn SELinux from Enforcing to Permissive I make this on Terminal Emulator:
su
pm disable com.sec.knox.seandroid
-- wait for killed...
setenforce 0
But here on Note 3 not work.
Can someone study this way on N9005?
Thanks

Fast click 3-4x on "SELinux Status" in "About Tablet" (or "About Phone") should work too to switch between permissive and enforceing.

Lol not.
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

Wanam xposed can change it, it worked for me, stock mk2 stock kernel
Sent from my SM-N900 using xda app-developers app

*GalaxyDev* said:
Wanam xposed can change it, it worked for me, stock mk2 stock kernel
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
I did wonder if Wanam done it as it was deemed "Experimental" -- interesting to know it works though.. I keep mine enforced on custom kernel, no real need for me to have Permissive atm.

SELinux enforcing mode Galaxy S5
I have Galaxy S5 SM-G900F, the problem is I cant use Chainfire Stickmount or Paragon exFAT, NTFS, HFS+. These are the only SU apps that I want to use but will not work without SELinux being set to permissive mode. I have sent the logs for Paragon to the developers in the hope they can make some changes to bypass the MAC my SELinux is imposing.
When I installed ChainFireAutoRoot and ran SuperSU it warned about KNOX and disabled KNOX. KNOX counter at 0x1 after root.
I have tried adb shell su 0 -c "setenforce 0"
rebooted
still enforcing mode
Can someone explain to me, is it actually the boot loader setting SElinux mode?

I have this problem also

One possible way is downloading wanam xposed.
Then go to security hacks
then change selinux from enforcing to permissive
good luck!:fingers-crossed:

Thanks. But that did not work.

boogieb4 said:
Thanks. But that did not work.
Click to expand...
Click to collapse
flash lean kernel, any civz kernel, xnote kernel ...
selinux is set by the kernel

Is it possible to flash any rooms while status is enforcing.

boogieb4 said:
Is it possible to flash any rooms while status is enforcing.
Click to expand...
Click to collapse
Try the Ultimate Kernel v64.. it fix many problems i had with lean kernel and permissive forced on wanamite.
Chooo

boogieb4 said:
Is it possible to flash any rooms while status is enforcing.
Click to expand...
Click to collapse
My experience with Note 3 (SM-N9005) is that any rom can be flashed while selinux status is enforcing
Sent from my SM-N9005 using XDA Free mobile app

How to change enforcing to permissive in My SM-G532F

Bhadran said:
How to change enforcing to permissive in My SM-G532F
Click to expand...
Click to collapse
This is not your phones forum its NOTE 3 forum.

[KNOX]

KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
How do I stop this from showing when I boot my phone?

synthecypher said:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
How do I stop this from showing when I boot my phone?
Click to expand...
Click to collapse
You can't its triggerd

KingOfDope said:
You can't its triggerd
Click to expand...
Click to collapse
So frustrating it was triggered by ROM Manager.
It asked me if I wanted to disable KNOX as it could cause problems. I didn't realise our want reversible.
Surely if I revert to a ROM using stock kernel if should go away?

synthecypher said:
So frustrating it was triggered by ROM Manager.
It asked me if I wanted to disable KNOX as it could cause problems. I didn't realise our want reversible.
Surely if I revert to a ROM using stock kernel if should go away?
Click to expand...
Click to collapse
unfortunately no KNOX is a hardware (eFuses) thing. Maybe in the future somebody can disable it Look in this thread : LINK they said that Samsung has a tool that can reset it but nobody from the outside got a hand on it

System status suddenly showing custom

I have rooted my phone using towel root when it came out and the system status was still official, nothing has change on my phone since then not even a firmware update and just today I noticed that my system status is already custom, I saw this a few days back and it was still official. Is there anyway to revert this back to official aside from a wipe and a stock reflash ? Would greenifying some system apps cause this because that was the change I made yesterday..

EarlZ said:
I have rooted my phone using towel root when it came out and the system status was still official, nothing has change on my phone since then not even a firmware update and just today I noticed that my system status is already custom, I saw this a few days back and it was still official. Is there anyway to revert this back to official aside from a wipe and a stock reflash ? Would greenifying some system apps cause this because that was the change I made yesterday..
Click to expand...
Click to collapse
Read about stuff like Wanam xposed.

xclub_101 said:
Read about stuff like Wanam xposed.
Click to expand...
Click to collapse
I already had wanam installed on the same day and it did not trigger the status. Is there a specific change in Wanam that triggers it ?

EarlZ said:
I already had wanam installed on the same day and it did not trigger the status. Is there a specific change in Wanam that triggers it ?
Click to expand...
Click to collapse
Security hacks -> fake system status.

xclub_101 said:
Security hacks -> fake system status.
Click to expand...
Click to collapse
That doesnt seem to fix the one displayed in download mode.
Im more interested on what triggered it and how to fix it with out a wipe.

EarlZ said:
That doesnt seem to fix the one displayed in download mode.
Im more interested on what triggered it and how to fix it with out a wipe.
Click to expand...
Click to collapse
Why does a custom binary tick you off so much you would want a wipe? Who would go into Download mode and take a look at your custom binary and say "OooOoOOOooOoOooooo this guy has Custom in System Status!!!!!!!!!!!11111oneone"
KNOX is what should tick you off, I could care less whether my System Status shows Official or Custom, because it's not permanent, just flash back to stock if any and it will return back to Official.

Because of OC. Sorry if this post offends you.

@EarlZ system status is always custom when your rooted, isnt it? Correct me if iam wrong.
I used cf auto root
Sent from Galaxy Note 3 SM-N9005

EarlZ said:
Because of OC. Sorry if this post offends you.
Click to expand...
Click to collapse
Not offended... Regardless OC means a lot of things. Like overclocking.... What do you mean by OC?

thahim said:
@EarlZ system status is always custom when your rooted, isnt it? Correct me if iam wrong.
I used cf auto root
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
I can guarantee that with 4.3 rooted with URDLV and Wanam xposed I have knox 0 and (fake) status official in download mode. I do not know first-hand with knox 0x1 (as after cf auto root) or 4.4.
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
EarlZ said:
That doesnt seem to fix the one displayed in download mode.
Im more interested on what triggered it and how to fix it with out a wipe.
Click to expand...
Click to collapse
See above.

thahim said:
@EarlZ system status is always custom when your rooted, isnt it? Correct me if iam wrong.
I used cf auto root
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
xclub_101 said:
I can guarantee that with 4.3 rooted with URDLV and Wanam xposed I have knox 0 and (fake) status official in download mode. I do not know first-hand with knox 0x1 (as after cf auto root) or 4.4.
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
See above.
Click to expand...
Click to collapse
Like what I posted, I used towel root and both Knox and System status was untouched. A few days ago I checked up on both and it was still official and 0x0, but yesterday it changed to custom. I understand that I can fix this by reflashing to all stock but what I am trying to also understand is what suddenly triggered it and if possible how to revert it with out wipe.

EarlZ said:
Like what I posted, I used towel root and both Knox and System status was untouched. A few days ago I checked up on both and it was still official and 0x0, but yesterday it changed to custom. I understand that I can fix this by reflashing to all stock but what I am trying to also understand is what suddenly triggered it and if possible how to revert it with out wipe.
Click to expand...
Click to collapse
I have same situation like you. Use wanam and you will be official in a download meny

Okay, you're not the only ones who got this situation.
For me, custom is better than official, since there is no possibility to accidentally update OTA, if I'm right.
But if you want your status back to official, try wiping cache from recovery. If that does not help, uninstall Wanam Xposed and then wipe again
If you use SEARCH you might found that You are NOT the only one with the problem you have, and the answer most likely is out there, just search, search and then search again
http://forum.xda-developers.com/showthread.php?t=2783954&page=14

Rooted 5.1.1 Private Mode Failed

Whenever i flash custom kernel for root 5.1.1, private mode always fail. Is there a solution ?

get a custom kernel with enforcing status , i guess then it will work

Er. Aditya said:
get a custom kernel with enforcing status , i guess then it will work
Click to expand...
Click to collapse
than you so much I am using N910g can you avice any kernel

I'm using the stock kernel with NTFS support and SEenforcing and i'm also having the same problem!

I tried many kernel one of them enforcing but still private mode failed
@Er. Aditya

any-way said:
Whenever i flash custom kernel for root 5.1.1, private mode always fail. Is there a solution ?
Click to expand...
Click to collapse
Tripped KNOX counter = No Private mode forever

d4rkkn16ht said:
Tripped KNOX counter = No Private mode forever
Click to expand...
Click to collapse
But With stock rom and stock kernel it is working

any-way said:
But With stock rom and stock kernel it is working
Click to expand...
Click to collapse
Try again, I was using stock ROM & kernel (Rooted) = KNOX Counter tripped = no Private Mode

Update: I've factory reset my phone and still can't get Private Mode to work. Used to work perfectly fine prior to 5.1.1?

thecrater said:
Update: I've factory reset my phone and still can't get Private Mode to work. Used to work perfectly fine prior to 5.1.1?
Click to expand...
Click to collapse
It doesn't work anymore because KNOX Counter is tripped. You can't revert it.

sorry, double post

you could try with this: Original Samsung SE enforced kernel.
This is ONLY for N910F.

OyyoDams said:
It doesn't work anymore because KNOX Counter is tripped. You can't revert it.
Click to expand...
Click to collapse
d4rkkn16ht said:
Tripped KNOX counter = No Private mode forever
Click to expand...
Click to collapse
Bull****
You can have knox tripped, custom kernel and private mode fully functional
as you can see in the screenshot below

zamcum said:
Bull****
You can have knox tripped, custom kernel and private mode fully functional
as you can see in the screenshot below
Click to expand...
Click to collapse
I don't know if such attitude is necessary or even allowed in this forum.
I'm talking based on my experience & others.
I was using rooted stock ROM & kernel but Private mode is disabled forever right after KNOX counter tripped.
If you can enable Private Mode while using custom kernel + tripped KNOX why don't you help OP instead?

I had mine rooted and Private Mode worked on 5.0 and without Xposed. I had the original Kernel rooted by chainfire so nothing fancy! Not sure what's changed in 5.1.1

thecrater said:
I had mine rooted and Private Mode worked on 5.0 and without Xposed. I had the original Kernel rooted by chainfire so nothing fancy! Not sure what's changed in 5.1.1
Click to expand...
Click to collapse
A butt load of security was added...

Private Mode works after rooting, just try This and see the magic.

ultramag69 said:
A butt load of security was added...
Click to expand...
Click to collapse
once 5.1.1 flashed...rooted on stock rom.....i was not able to make any change by the build.prop anymore!! downgraded to 5.0.1 and "bang" everything was back...

zxaz said:
once 5.1.1 flashed...rooted on stock rom.....i was not able to make any change by the build.prop anymore!! downgraded to 5.0.1 and "bang" everything was back...
Click to expand...
Click to collapse
Lollipop 5.1.1 can't be rooted ordinary way.
You need to use custom Permissive Kernel to be able to ROOT it.
It seems that your root attempt was failed (but no error message).

i succesfully rooted...even checked with "root checker" but was not able to make any change with the build.prop....

G900f Permissive mode

Hi, is there any way to change SElinux to permissive mode on BPA2 without flashing custom kernel ? My phone is rooted, deknoxed, knox 0x1.
Thanks for help.

prostozsadu said:
Hi, is there any way to change SElinux to permissive mode on BPA2 without flashing custom kernel ? My phone is rooted, deknoxed, knox 0x1.
Thanks for help.
Click to expand...
Click to collapse
I dont think there is, not 100% sure on that though.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Thats bad, now im on Boeffla kernek but i noticed worse performance than on stock and i want to enable reactivation lock.

prostozsadu said:
Thats bad, now im on Boeffla kernek but i noticed worse performance than on stock and i want to enable reactivation lock.
Click to expand...
Click to collapse
As with before, not 100% as I'm not on a model that allows me to get too deep in custom stuff, but the general consensus ive seen is custom anything+reactivation lock on=bad news bear.
Sent from my SAMSUNG-SM-G900A using Tapatalk

That's why i want permissive mode on stock kernel