is there something I can do to get rid of the Dangerous App notification ?
on an AT&T LG G4 H810 10o
on an AT&T LG G4 H810 10o
Same hereI've been using this app for a while now on several devices including my Z2 (D6503) which had it installed for over 6 months. Then a few days ago I got this pop-up.
Has anyone else experienced this?
Any ideas?
Thanks in advance!
Its been quite q while since I used this app, but I don't believe it requires a reboot for changes to take effect. After changing the SELinux mode with the app, you should be able to see the SELinux status in the system settings > about phone.The word reboot is used too much to search 37 pages.
If I set SELinux from Permissive back to Enforcing, is a reboot required? I assume yes but want to confirm
Thanks, can anyone confirm? What you posted makes sense but what I am wondering is if the system is only reading the (current) value changed or if it is actually (actively) enforced at the time you ADB it.Its been quite q while since I used this app, but I don't believe it requires a reboot for changes to take effect. After changing the SELinux mode with the app, you should be able to see the SELinux status in the system settings > about phone.
Or you can type the following from an ADB shell or a terminal emulator app:
su
getenforce
Sent from my m8whl using Tapatalk
First post says that the app theoreticly doesn't work on Samsung cuz of KnoxOn Galaxy S7 (6.0.1, no "My KNOX" installed) it says that the app has no SU rights, but I gave it when it asked for...
How do I fix this?
I don't know how Knox works other than being a security feature on Samsung devices.Then, is there a way to disable KNOX or smth?
Thanks!
bumppppssingThanks, can anyone confirm? What you posted makes sense but what I am wondering is if the system is only reading the (current) value changed or if it is actually (actively) enforced at the time you ADB it.
So if this is the case, that means Enforcing does in-fact require a reboot and is not on-the-fly which to me indicates that the state read back by sestatus is only what is in the config, not the actual state.SELinux can transition from Enforcing to Permissive easily using the setenforce command. Providing setenforce with a "0" argument will put the system in Permissive mode, a "1" will set it to Enforcing. To transition to or from Disabled mode, you need to reboot after making the appropriate changes to the sysconfig file.
that will be good toolNow opensourced under gplv3! GITHUB
Also you can get it in f-droid! F-DROID page
There are lots of folks around who already has KitKat on their devices. But kitkat comes with new secutity enhancement, SELinux, put into "enforcing mode". Maybe This thing is good from the point of security, but it breaks some Root Apps, like my Ultimate Dynamic Navbar, so I created this app.
What does it do? This app can change modes of SELinux:
Run app, give root access, select the mode you want SELinux to be in(permissive or enforcing) and that's all. Every time you reboot your device app will execute the script to change SELinux to the mode you've selected. Simple and stupid.
SELinuxModeChanger-v3.2.apk
Google Play Link
My google play account was banned because of selinux stuff ;/
know issues:
- [THEORETICALLY] doesn't work with Samsung KNOX.
XDA:DevDB Information
SELinuxModeChanger, App for the Android General
Contributors
MrBIMC
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2015-04-27
Created 2013-11-13
Last Updated 2015-05-17
Have the same issue with rooted Huawei mate sHi, i have a issue wih Selinus mode changer: "app was unable to gain root access"
My Nexus 5 was rooted and used SU v2.72
Same on Shield TV.Hi, i have a issue wih Selinus mode changer: "app was unable to gain root access"
My Nexus 5 was rooted and used SU v2.72
Hi, i have a issue wih Selinus mode changer: "app was unable to gain root access"
My Nexus 5 was rooted and used SU v2.72
Have the same issue with rooted Huawei mate s
Envoyé de mon PRO 5 en utilisant Tapatalk
Same on Shield TV.
Sent from my XT1575 using Tapatalk
All of you are using SuperSU newer version than 2.68? On my device any other version newer than this give me that issue.
Thanks for the help, but I downgraded SuperSU to 2.65 and still have the same problem.All of you are using SuperSU newer version than 2.68? On my device any other version newer than this give me that issue.
Sent from my Oneplus One
same issue, oneplus one - cm13 sultanHi, i have a issue wih Selinus mode changer: "app was unable to gain root access"
My Nexus 5 was rooted and used SU v2.72
Same here. Nexus 5X 6.0.1 MTC19T, SuperSU 2.7.2same issue, oneplus one - cm13 sultan