[APP][TOOL][2.0+][OFFICIAL]The SELinux Switch

[jrkruse]

several of the android 10 roms i'd like to run on my device(s) have selinux enforcing by default. it's not that i have anything against enforcing roms, but, i'm able to restore my data from recovery (after a clean flash) only on permissive roms. i'm yet to find a way i can change selinux state to permissive that enables me to restore data from recovery and boot up without issues. so, i ask you and other learned devs/users: is there a not-too-complex way i can achieve what i seek? thanks in advance for any help on this.


i too could find the app in the drawer only after the traditional installation.

Your problem could be that android 10 is system as root system so some deviices require the zip to mount the system as root and not just system and some systems require you to extract the files to system root not just system. You may find most older zips will not flash properly. It really depends on how your twrp handles the system as root.


Sent from my iPhone using Tapatalk

 

[m0han]

..You may find most older zips will not flash properly. It really depends on how your twrp handles the system as root.

thanks for the response. so, is there something a simple user can do on his/her own to get around this?

 

[Ibuprophen]

thanks for the response. so, is there something a simple user can do on his/her own to get around this?

When it comes to Android 9 & 10 (and likely future versions)...

I've found that there's really 3 precursors (I plan to outline) that's needed before installing The SELinux Switch App.

1) You can't switch the SELinux to/from Permissive & Enforcing unless the Android OS has a SEAndroid Capable Kernel to enable this feature.

Especially when it comes to New/Beta/Alpha versions of a Custom OS, the developers will typically have the SEAndroid set to a Permanent Permissive state (that restricts switching) solely for developers to perform the required fixes necessary for an eventual Stable OS to be released. Once a Stable OS is released, the OS will then have its SEAndroid set (by default) to Enforcing and will typically (meaning, unless otherwise outlined by the developers) be SEAndroid Capable.

2) Root... Root... Root... Is "really needed" before you install The SELinux Switch App.

3) Importantly... The Google Play Protect feature "needs" to be disabled before installing The SELinux Switch. If it isn't disabled and you install the App (either via Apk or Flashed using the Zip file), the Google Play Protect "will" prevent the installation of the App OR remove/disable the App's installation.

I hope I was able to explain this okay via text...


~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX2 Forum App on my Sanyo Juno device.

 

[m0han]

...1) You can't switch the SELinux to/from Permissive & Enforcing unless the Android OS has a SEAndroid Capable Kernel...

2) ...Root... Is "really needed" before you install The SELinux Switch App.

3) ...Google Play Protect feature "needs" to be disabled before installing The SELinux Switch...

i can't be sure about 1). most rom devs don't bother answering queries about it. but, 2) and 3) are in place/done always. thanks.

 

[Ibuprophen]

i can't be sure about 1). most rom devs don't bother answering queries about it. but, 2) and 3) are in place/done always. thanks.

I know what you mean. SEAndroid question are not typically a topic the Custom Firmware Developer(s) like to address only because it's really something that they discourage from changing it to a Permissive Mode.

It's completely understandable to me because, if the individual doesn't understand about the SEAndroid and what it means to be in Permissive Mode, I would then discourage it as well.

Without getting into a confusing geek like explanation...

If someone doesn't understand what it means to the device when it is in a Permissive Mode, it can potentially open up certain areas of your device to a handful of attacks.

Also, too many individuals confuse the SEAndroid being tied specifically to Root and they're two completely separate worlds. The only tie to them is that one of the requirements for changing to a Permissive Mode is the device having root ONLY because accessing the directory where the kernel is located is within a Root Directory.

I found that a majority of "Stable" Custom Firmware (ie. LineageOS to name 1) does have the ability for its SEAndroid State to be changed back and forth.

To be honest, I personally "Rarely" enter into a Permissive Mode on my device and only do so when necessary for one reason or another.

Anyways, I hope I had explained this okay via text...


~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX2 Forum App on my Sanyo Juno device.

 

[ZHIWA-XM]

If selinux is disabled selinuxswitch app can enabled it
Device:j5lte
ROM: cr droid

 

[Ibuprophen]

If selinux is disabled selinuxswitch app can enabled it
Device:j5lte
ROM: cr droid

Only if the Firmware has SEAndroid Capable Kernel to allow it. Having Root is only one of the prerequisites.

You'll be able to locate this information outlined in a few ways throughout this thread (and even the last few pages as well).


~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX2 Forum App on my Sanyo Juno device.

 

[dariomtk]

Moto G4 plus AOSIP 9 rom one gapps , root, it crashes when I set Enforcing. what I'm doing wrong ?

 

[m0han]

...crashes when I set Enforcing...

see post above yours. maybe your device Firmware does not have SEAndroid Capable Kernel.

 

[jrkruse]

The days of flipping a switch from enforcing to permissive are probably a thing of the past. There is no ram disk in boot images no more and phones now have dynamic partitions making selinux very complicated now. You have lots of things that now need changed for a permissive system.


Sent from my iPad using Tapatalk

 

[ecompton59]

This still works on OnePlus 8t on android 11 great work I've used this forever thanks bro

 

[kelumsd]

deleted

 

[kelumsd]

deleted

 

[immi803]

i'm new user of this app and wanted obviously permissive mode , there's no glitch in APP itself and working absolutely fine, only problem i encounter when there's an upgrade to my rom, flashing an update over my rom triggers enforcing mode and force stops viper4Andriod legacy driver installation, so all i've to repeat is boot rom for first time after upgrade and change mode to permissive using this great app, reflash V4A legacy again and reboot again, is there a work around for this procedure? my kernel fully supports permissive , A11, Dynamic system, Arrow OS custom rom

Surely needing some help, i think magisk module for this might solve this issue, do i simply need zip to be flashed in magisk? and turning on Busybox within magisk will solve this problem? i'm previusly using apk version , i preferred to ask before testing at my own, my data partition is encrypted so better to ask

@Ibuprophen

 

[immi803]

repeat
deleted

 

[YamiYukiSenpai]

Primary Download Links

The SELinux Switch - Apk & Flashable Zip Installers via this DevDB Thread (Downloads)

Just want to inform you that this doesn't work.

 

[fobtob387]

Just want to inform you that this doesn't work.

The alternative mirrors in the OP work fine, this is to be expected from a 4 year old OP.

 

[victorsv]

Is this application still developed?
I own a Moto G7 Plus (XT1965-3) with TWRP (3.5.2_9-0-lake), LineageOS 18.1 and MagiskHide (23.0).
I wanted to use the system as permissive in order to use "Viper4Andriod"!

 

[m0han]

.... wanted to use the system as permissive in order to use "Viper4Andriod"

you might like to read this post and try the attached ViperFX_Android11 file: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85163825

 

[Ibuprophen]

A long awaited update to the The SeLinux Switch v7.1.4 b714 was just pushed.

Changes reflected on the OP & Changelog.

Never perfect and always a work in progress.

Please Enjoy!

~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. [Sent from the room next door.]