i am using cm12.1 rom. i installed busybox. i am using viper lollipop . i searched several methods on internet. but i couldn't solve . how to fix this problem?
is your selinux set to permissive?
if its not (if its enforcing) download an app called selinuxmodechanger
Related
Hi
Xposed is here. if you are wondering it does not work for you its because the SELinux status is set as Enforcing which doesnt allow xposed framework to modify at system level. though some modules are not compatible yet
Bonus : Also if you are using Viper4Android it wont work unless the SELinux is Permissive
there is a workaround for this. 3rd being the easiest and permanent fix
1. Terminal method
Code:
Su
Setenforce permissive
soft reboot to make xposed to work
OR
2. Using SELinux Mode Changer APP
Use this app SELinux Mode Changer
change it to Permissive and soft reboot to make xposed to work
Else
3. With a modified Kernel(CM12 only) easiest method
Here is the modified Kernel which is set to permissive by default.
it is a boot.img not flashable.zip
How to flash
1. Flash this using TWRP(TWRP can flash img files now ) or apps like RASHR can be used to flash boot.img
for more info check this https://source.android.com/devices/tech/security/selinux/validate.html#switching_to_permissive
Tested with BlissPop 13th release works as intended
i have used BlissPop kernel. it is as good as CM12 Kernel
Better to have a backup(Not mandatory its upto you)
All credits to original developers
reversegear said:
Hi
Xposed is here. if you are wondering it does not work for you its because the SELinux status is set as Enforcing which doesnt allow xposed framework to modify at system level. though some modules are not compatible yet
Bonus : Also if you are using Viper4Android it wont work unless the SELinux is Permissive
there is a workaround for this. 3rd being the easiest and permanent fix
1. Terminal method
Code:
Su
Setenforce permissive
soft reboot to make xposed to work
OR
2. Using SELinux Mode Changer APP
Use this app SELinux Mode Changer
change it to Permissive and soft reboot to make xposed to work
Else
3. With a modified Kernel(CM12 only) easiest method
Here is the modified Kernel which is set to permissive by default.
it is a boot.img not flashable.zip
How to flash
1. Flash this using TWRP(TWRP can flash img files now ) or apps like RASHR can be used to flash boot.img
for more info check this https://source.android.com/devices/tech/security/selinux/validate.html#switching_to_permissive
Tested with BlissPop 13th release works as intended
i have used BlissPop kernel. it is as good as CM12 Kernel
Better to have a backup(Not mandatory its upto you)
All credits to original developers
Click to expand...
Click to collapse
Hi,
great post, thanks!
I have two questions:
- Can you provide more information about this kernel please?. Is stock cm12 kernel, only with SeLinux changed?
I don´t use cm12 because SeLinux is set to enforcing and have problems restoring nandroid backup with TWRP (no problems with philz recovery).
- I don´t have tested, but i think that if you make init.d script that change SeLinux, you would´t have to make soft reboot.
Regards.
SergioSanchezR said:
Hi,
great post, thanks!
I have two questions:
- Can you provide more information about this kernel please?. Is stock cm12 kernel, only with SeLinux changed?
I don´t use cm12 because SeLinux is set to enforcing and have problems restoring nandroid backup with TWRP (no problems with philz recovery).
- I don´t have tested, but i think that if you make init.d script that change SeLinux, you would´t have to make soft reboot.
Regards.
Click to expand...
Click to collapse
1. as i said kernel i used is from BLISSPOP rom from 13th experimental build. i dont think Bliss Team made any changes to the kernel. i guess you can flash custom kernel like optimus / Attacked on top of the modded kernel because both provide only Zimage. so that SELinux status is retained to Permissive
2. i Tried init.d script unfortunately it wont work on CM based rom so i thought of modifying in boot.img itself
Hope this helps
Cool !!
wow!, the terminal method is vv easy method. Works perfectly!!
SELinux-Status: Moderat
Hi!
I used the Terminal method.
However, the SELinux-Status is now: Moderat (see screenshot).
Can you please instruct?
THX
Fantastic place thanks in advance for any and all help ,
Running nvidia shield console 16gb version 3.2 marshmallow , custom rom twrp 201602222 unofficial foster. TWRP manager paid version installed , #super su paid version installed from google play over su beta flash , SELinuxModeChanger also installed from download link in xda also installed xposed framework from xda big thanks to the devs
my issue is , that i need to find a way to switch selinux to permissive as TWRP manager cannot fully function with it set to enforced , i have downloaded and run SELinuxModeChanger however i keep getting a toast message which reads
App was unable to gain root access
superuser manager doesnt allow app to access SU or you dont have root at all. Fix this to use this SELinuxModeChanger
I have tried escalating apps permissions via SU but nothing seems to work and i am now stumped as to what to do next ??
I have been able to create a manual backup via adb fastboot but would really like to be using twrp on line back up if i can switch selinux mode
I have searched on here as well as google and nvidia forums to no avail please help a newb many thanks in advance
SOLVED
Managed to solve the problem by flashing update-superSU-v2.76-SYSTEMMODE over currant version now SELinuxModeChanger has su access
Hi
I got J510F (2016) stock rom (andrroid 6) , stock kernel is rooted already but I can't get SELinux permissive its always stay in enforcement and can't change Any idea ???
thanks for help
Try using selinuxmodechanger.apk install it as system app
Kcjbj
Firstly u have to install busy box in system/bin then install selinux mode changer apk
Did somebody manage to properly run ViperFX? I found a thread over at en.miui.com, with a flashable zip but no instructions. On my old smartphone I had to remove AudioFX and cmaudio befor flashing ViperFX, and also set selinux to permissive. I tried the same with my redmi but it didn't work. Also setting selinux to permissive causes problems with my password recognition, oddly.
Also there is a thread at 4pda with an attachment, which however I cant donwload or which is removed.
So, anybody got ViperFX running and can give a propper instruction, would be very welcome!
I use ViperFX as Magisk Module, it works fine with LOS13 by jacoghi 05.06 ROM build, just flash it after you've flash Magisk v12. It works good as well with xiaomi.eu(as i've used it on xiaomi.eu 8.1.3.0 ROM build before). And yes, i think you have to set SELinux to Permissive for it to work properly. You can download it from this link.
Hello.
I run V4A in stock 8.2.4.0 with no problem, downloaded from official site http://vipersaudio.com/blog/
I put a simple script to set selinux to permissive in tasker at device boot, and everything work´s OK.
No problem here with password or anything else.
Sorry for my english.
jmsonicbox said:
Hello.
I run V4A in stock 8.2.4.0 with no problem, downloaded from official site http://vipersaudio.com/blog/
I put a simple script to set selinux to permissive in tasker at device boot, and everything work´s OK.
No problem here with password or anything else.
Sorry for my english.
Click to expand...
Click to collapse
Upload your script to use it and others users
Thanks
Hi, I am using Viper4android Fx for Magisk (created by ShadySquirrel) on Xiaomi Mi A1 which was rooted systemlessly by Magisk "patched_boot.img" method. I have installed Magisk SELinux permissive script and Busybox through Magisk Manager. Now whenever I am installing V4A Magisk module, it works for some time and then it stops working with a pop up like "Update/install driver". But when I am trying to update or install the driver, it fails with an I/O error. Reboot doesn't solve the problem. I read on Xda that SELinux permissive script needs to be enabled and storage permission needs to be given to V4A. I have both active. But still, the problem persists. If I uninstall V4A module and reinstall it, then it works, but for a few days. Then the problem starts again. Is there any workaround?
Note that, I have stock android 8.0.0 with no custom recovery and no custom kernel.
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
I'm not using viper actually, I stay with Dolby on Oreo with my a1.
But I guess you will find working viper and answers on the link.
I guess I have the same problem here. When I try to install Viper4Android or Viper4Arise modules, phone starts crashing with "Dirac Control Services Stopped Working" showing up every few seconds. I really love Viper and I don't want to move from Stock ROM or install any kernel. Any clue on that?
Maybe Try selinux switcher and viper4android by viper520, zhuhang and others (i Click Three Times Volume Up)