Related
Are there any kernels available that allow Viper4Android to work in Enforcing mode, but also allow T-Mobile WiFi Calling to work? I've been away from the N6 for around 6 weeks, due to a need for WiFi Calling. I'm back now, but would absolutely love to reinstall V4A and not lose WiFi Calling, since I barely get service in my office.
You don't need a kernel for this. A simple terminal command can be scripted via various apps (Tasker, script manager) or get one of those SELinux mode changer apps.
Code is:
setenforce 0
danarama said:
You don't need a kernel for this. A simple terminal command can be scripted via various apps (Tasker, script manager) or get one of those SELinux mode changer apps.
Code is:
setenforce 0
Click to expand...
Click to collapse
Thanks. I know you can shut off Enforcing mode, but I'm not looking to do that. When I was running Chroma, it had changes implemented into the kernel to allow V4A to run in Enforcing, and that is what I'm looking to do again. Just without losing WiFi Calling.
NotATreoFan said:
Thanks. I know you can shut off Enforcing mode, but I'm not looking to do that. When I was running Chroma, it had changes implemented into the kernel to allow V4A to run in Enforcing, and that is what I'm looking to do again. Just without losing WiFi Calling.
Click to expand...
Click to collapse
Hmm. I see what you're saying. You want to be as secure as possible.
Chroma's kernel is compiled from Source. Didn't @Chainfire manage to unpack the stock kernel and make some SELinux changes in his early Lollipop SuperSU releases?
Maybe @zephiK knows if it can be done with a repack.
Perhaps someone can clarify for me...
I use Magisk and I've noticed that it was recently updated and there are mentionings about SELinux/sepolicy and pseudo enforced, etc. in the changelog.
Whenever I run SambaDroid it will fail to start unless I open the SELinuxModeChanger app and change the mode to Permissive first, which of course ruins SafetyNet, so I can't just leave it in that mode all the time.
I have to go back and change it to Enforcing when I am done.
An extra step I'm hoping won't be required in the future. Perhaps on a per-app basis like MagiskHide.
Should the recent changes to Magisk allow me to run SambaDroid without having to manually change the SELinux Mode?
If so, it doesn't work yet, but maybe I am misunderstanding the changelog references.
andrewsfm said:
Perhaps someone can clarify for me...
I use Magisk and I've noticed that it was recently updated and there are mentionings about SELinux/sepolicy and pseudo enforced, etc. in the changelog.
Whenever I run SambaDroid it will fail to start unless I open the SELinuxModeChanger app and change the mode to Permissive first, which of course ruins SafetyNet, so I can't just leave it in that mode all the time.
I have to go back and change it to Enforcing when I am done.
An extra step I'm hoping won't be required in the future. Perhaps on a per-app basis like MagiskHide.
Should the recent changes to Magisk allow me to run SambaDroid without having to manually change the SELinux Mode?
If so, it doesn't work yet, but maybe I am misunderstanding the changelog references.
Click to expand...
Click to collapse
The update in v11 you're talking about should be able to hide permissive SELinux from SafetNet. In other words: you should be able to leave SELinux permissive and still pass SafetyNet with the help of Magisk Hide.
Didgeridoohan said:
The update in v11 you're talking about should be able to hide permissive SELinux from SafetNet. In other words: you should be able to leave SELinux permissive and still pass SafetyNet with the help of Magisk Hide.
Click to expand...
Click to collapse
Ahh okay, I get it. Just tested it now and it works exactly like you described. It wouldn't pass SafetyNet before on the previous version but apparently does now after the upgrade when left in permissive. Thanks!
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
Hmm... Interesting. I think I'll do some tests myself.
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
Ok. I've tested and it seems to work as expected.
What I did was add a file in /magisk/.core/post-fs-data.d named 08setperm (doesn't matter what the file is named). In that file I added:
#!/system/sh
setenforce 0
This way SELinux is set to permissive at boot.
Disabled Magisk Hide, rebooted and verified that SELinux now was set to permissive on boot (typed getenforce in Teminal Emulator).
Enabled Magisk Hide again and voila! Typing getenforce in Terminal emulator now reported Enforcing and SafetyNet passed.
No idea if this will make SambaDroid work though...
I found a way to somewhat replicate what I am experiencing.
You'll need SELinuxModeChanger (SELMC) to see if you get the same results.
Although I'm wondering if it may be the cause of the problem...
Open recent apps and clear everything out.
Open SELMC and change to permissive.
Hit the home button.
Launch Magisk Manager and check SN. Should pass.
Hit the home button.
Clear recent apps.
Open SELMC, and it's back to enforcing.
Change back to permissive.
Hit the home button.
Re-launch MM and check SN, and it comes back CTS fail.
If you stay in MM and wait for a while, occasionally clicking check SN, eventually, it'll pass without changing anything.
If you change tasks over to SELMC, you'll see it's still in permissive as well.
It appears the transition from enforcing to permissive causes SN to fail for a while, and SELMC reverts back to enforcing if cleared from recent tasks, and re-activating it causes SN to fail for a period of time?
andrewsfm said:
I found a way to somewhat replicate what I am experiencing.
You'll need SELinuxModeChanger (SELMC) to see if you get the same results.
Although I'm wondering if it may be the cause of the problem...
Open recent apps and clear everything out.
Open SELMC and change to permissive.
Hit the home button.
Launch Magisk Manager and check SN. Should pass.
Hit the home button.
Clear recent apps.
Open SELMC, and it's back to enforcing.
Change back to permissive.
Hit the home button.
Re-launch MM and check SN, and it comes back CTS fail.
If you stay in MM and wait for a while, occasionally clicking check SN, eventually, it'll pass without changing anything.
If you change tasks over to SELMC, you'll see it's still in permissive as well.
It appears the transition from enforcing to permissive causes SN to fail for a while, and SELMC reverts back to enforcing if cleared from recent tasks, and re-activating it causes SN to fail for a period of time?
Click to expand...
Click to collapse
Sounds like MagiskHide deamon takes a short wile to start up after the change, or something like that. Seems normal to me... If you wan't a more permanent solution than SELMC, try using the script I posted earlier.
Didgeridoohan said:
Sounds like MagiskHide deamon takes a short wile to start up after the change, or something like that. Seems normal to me... If you wan't a more permanent solution than SELMC, try using the script I posted earlier.
Click to expand...
Click to collapse
I gave your script a try, but it didn't work.
I created the file with the same contents/name by copy/paste, and put it in the folder you specified using Root Explorer.
Rebooted the phone, and checked selinux status using "sestatus" and it said enforcing.
Tried manually typing in the commands in your post into terminal emulator...
#!/system/sh (which didn't show a response.)
setenforce 0 (responded "Couldn't set enforcing to 0. Permission denied.")
So I tried...
su
setenforce 0
After that it shows permissive.
Ran SambaDroid, and it works fine, and SN passes.
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
andrewsfm said:
...
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/Shebang_(Unix)
MagiskHide sets pseudo-enforcing since Magisk 11 because enforcing is needed to pass SafetyNet
andrewsfm said:
I gave your script a try, but it didn't work.
I created the file with the same contents/name by copy/paste, and put it in the folder you specified using Root Explorer.
Rebooted the phone, and checked selinux status using "sestatus" and it said enforcing.
Tried manually typing in the commands in your post into terminal emulator...
#!/system/sh (which didn't show a response.)
setenforce 0 (responded "Couldn't set enforcing to 0. Permission denied.")
So I tried...
su
setenforce 0
After that it shows permissive.
Ran SambaDroid, and it works fine, and SN passes.
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
Click to expand...
Click to collapse
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Didgeridoohan said:
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Click to expand...
Click to collapse
Yeah, I used notepad... Should have used UltraEdit I guess?
Just downloaded your script and installed it, and it works fine now.
SambaDroid worked right off the bat without needing to remember to open SELMC every time before and after.
Thanks!
Didgeridoohan said:
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Click to expand...
Click to collapse
Is this a bug in Magisk?
Meowdib said:
Is this a bug in Magisk?
Click to expand...
Click to collapse
No. Why do you think that?
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
I have an S7 and a modified stock kernel with SELinux permissive. I enabled Magisk hide and only enabled SystemUI and SafetyNet passed.
Sent from my S7.
andrewsfm said:
Yeah, I used notepad... Should have used UltraEdit I guess?
Just downloaded your script and installed it, and it works fine now.
SambaDroid worked right off the bat without needing to remember to open SELMC every time before and after.
Thanks!
Click to expand...
Click to collapse
Sorry for reviving a somewhat old thread. I was just curious if with this script, do apps that need SELinux Permissive work, AND SafetyNet still passes? Thanks!
jbw716 said:
Sorry for reviving a somewhat old thread. I was just curious if with this script, do apps that need SELinux Permissive work, AND SafetyNet still passes? Thanks!
Click to expand...
Click to collapse
Magisk Hide have a pseudo-enforcing feature that will make SELinux seem enforcing to hidden apps, even though it's permissive. Including SafetyNet.
So the answer to your question is: yes.
I request a thread regarding this issue. The script is very helpfull and i currently dont know any other way making selinux stay permanently on permissive. Many people are having this issue with soundmods like arise which require permissive selinux. Thnaks!!
nadejo said:
I request a thread regarding this issue. The script is very helpfull and i currently dont know any other way making selinux stay permanently on permissive. Many people are having this issue with soundmods like arise which require permissive selinux. Thnaks!!
Click to expand...
Click to collapse
Are you asking for a module to install the necessary script? Like I've provided here https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549.
AS OF 03/07/2018
Support and development of this module have been discontinued.
A replacement module can be found here : https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
This module has been tested on and is compatible with Magisk v11.6-15.2.
Disclaimer & Recommendations: This module should be used as a last resort only if appropriate SELinux Permissions can not be generated and injected into the SELinux Policy using selinux-inject, supolicy or magiskpolicy. Putting your device into Permissive Mode will essentially disable all of the operating system level security built into Android and allow any app in any context to do whatever it wants. Actions requiring root access will still trigger your SU Manager App, but all apps have elevated privileges due to permissive and may be able to take malicious actions on your device without needing root access. If you find that this module fixes issues you are experiencing with an app I recommend contacting the app developer and trying to work with them to isolate the necessary SELinux Permissions and have them injected into the SELinux Policy at startup.
Here is a discussion of some of concerns to consider when running your device in Permissive Mode : https://forum.xda-developers.com/general/general/discussion-root-selinux-risks-t3607295
Github Repo : https://github.com/Jman420/magisk-permissive-script
Change Log :
v1.0 - Initial Release
v1.1 - Update to Module Template v1400
v1.2 - Update to Module Template v1500
thank you brother!
LeEco LePro 3 Atmos can work finally!
huaiyue said:
thank you brother!
Can you tell me how to install LeEco LePro 3 Atmos ?
I hava supersu systemless.
Click to expand...
Click to collapse
These two things are completely unrelated.
If you want to install something, you install it. There's not much more to that.
huaiyue said:
thank you brother!
Can you tell me how to install LeEco LePro 3 Atmos ?
I hava supersu systemless.
Click to expand...
Click to collapse
In Magisk, go to the Modules section, and select the "+", and select the zip you downloaded.
Jman420 said:
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
Github Repo : https://github.com/Jman420/magisk-permissive-script
Click to expand...
Click to collapse
LeEco LePro 3 Atmos can work
however
xposed systemless failed.
---------- Post added at 01:32 ---------- Previous post was at 01:31 ----------
ahrion said:
These two things are completely unrelated.
If you want to install something, you install it. There's not much more to that.
Click to expand...
Click to collapse
http://imgur.com/a/Sbf9p
dolby fc.
---------- Post added at 01:36 ---------- Previous post was at 01:32 ----------
jhedfors said:
In Magisk, go to the Modules section, and select the "+", and select the zip you downloaded.
Click to expand...
Click to collapse
thank you brother!
Thanks a lot
huaiyue said:
thank you brother!
LeEco LePro 3 Atmos can work finally!
Click to expand...
Click to collapse
Regarding your other post mentioning Xposed (which I'm not quoting cause it's a mess). I'm running on Nougat so I can't use Xposed and haven't tested with it. If you give me more details I can try to determine what the issue is. Logs, error messages, symptoms would all be helpful.
Thor™ said:
Thanks a lot
Click to expand...
Click to collapse
I aim to please
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
its working with s5neo?
I've just flashed this zip. This allows Viper4Android to run in enforcing mode:
https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
I forgot the source. Maybe Google it
matssa said:
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
Click to expand...
Click to collapse
I agree that Magisk hides the actual SELinux Mode in such a way that if Magisk Hide is enabled the 'getenforce' command always returns 'Enforcing'. But if you do not run the 'setenforce 0' command the SELinux mode will still be set to 'Enforcing' rather than 'Permissive'. This script puts the SELinux mode into 'Permissive' at startup. Magisk Hide will still hide the fact that you are in Permissive Mode, which I believe is the 'pseudo permissive' mode that Magisk describes. But I can not find any settings or commands within Magisk that enable Permissive Mode.
htr5 said:
I've just flashed this zip. This allows Viper4Android to run in enforcing mode:
https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
I forgot the source. Maybe Google it
Click to expand...
Click to collapse
It's just a shell script, the source is in the zip file. This is really helpful and is the direction I want to take this project. Permissive Mode is great in that it gets the Apps/Mods that we want to run to work, but I consider it the equivalent of using a sledgehammer to hammer in a finishing nail. I would much rather be able to grant the specific permissions that each App needs rather than enable all permissions for all apps (which is what permissive mode does).
I plan on trying to develop an App which will assist in managing and generating a script which uses 'supolicy' to inject individual SELinux Policy Permissions. I had planned on using the Dolby Atmos LePro3 build as a guinea pig to try to isolate which permissions it needs and put together the supolicy command for them. I've hit a bit of a roadblock in verifying my supolicy command due to the format that the SELinux Policy is stored in on the device. I've found a project called sedump (https://ge0n0sis.github.io/posts/2015/12/exploring-androids-selinux-kernel-policy/) which claims to deserialize the Binary SELinux Policy to a readable format, but I can't seem to get it to work... the process seems to complete, but it generates an empty file... If anyone has experience with SELinux I'd really appreciate any feedback.
cosmin691 said:
its working with s5neo?
Click to expand...
Click to collapse
Dunno, I've only got an HTC 10 for testing. Give it a shot, if it doesn't work just uninstall the Magisk Package. Remember to disable Magisk Hide if you are testing to make sure it actually put your phone into Permissive Mode by using the 'getenforce' command.
It works for oneplus 3t on freedom OS rom.
Jman420 said:
This is a very simple module that installs a post-fs-data.sh script which enables SELinux Permissive Mode. This is useful for certain audio mods and removes the need to understand Magisk's file system & boot logic. No need to create your own scripts, just flash and forget.
I have only tested this on my Verizon HTC 10, but this module is so simple and generic that it should work on any Android device with SELinux.
Github Repo : https://github.com/Jman420/magisk-permissive-script
Click to expand...
Click to collapse
this zip must be flashed using twrp rite ? or stock recovery also will do fine ? because i tried many times to flash recovery for samsung e5 5.1.1 but ended up with boot loop. now running all stock !!
X_GOD said:
this zip must be flashed using twrp rite ? or stock recovery also will do fine ? because i tried many times to flash recovery for samsung e5 5.1.1 but ended up with boot loop. now running all stock !!
Click to expand...
Click to collapse
Should be able to install it through Magisk Manager or TWRP. Let me know if you have problems.
matssa said:
I don't understand why this mod is usefull. In the latest version of magisk, there is a semi enforce/permissive linux bypass. The system thinks it's enforced, but in reality is permissive. Or maybe I didn't fully understand it?
Click to expand...
Click to collapse
Now, I have magisk 11.6 on EMUI marshmallows V4A driver was abnormal because Enforcing selinux. Same happened with SuperSU 2.79. When I changed to permissive mode using terminal emulato/kernerl aduitor init.d script emulator/su.d SuperSU script, V4A driver was normal and it was processing. I like Magisk a lot because of its xposed like modules. Now using jman420's permissive magisk module.
Thor™ said:
Now, I have magisk 11.6 on EMUI marshmallows V4A driver was abnormal because Enforcing selinux. Same happened with SuperSU 2.79. When I changed to permissive mode using terminal emulato/kernerl aduitor init.d script emulator/su.d SuperSU script, V4A driver was normal and it was processing. I like Magisk a lot because of its xposed like modules. Now using jman420's permissive magisk module.
Click to expand...
Click to collapse
Without this module, ARISE is working fine, processing in 48000 on my side, so for V4A I don't think this is necessary, at least on my side.
Sent from my OnePlus3 using XDA Labs
matssa said:
Without this module, ARISE is working fine, processing in 48000 on my side, so for V4A I don't think this is necessary, at least on my side.
Click to expand...
Click to collapse
For ARISE I used to flash permissive script by osm0sis. Otherwise no luck with V4A, AM3D and Dolby.
Thor™ said:
For ARISE I used to flash permissive script by osm0sis. Otherwise no luck with V4A, AM3D and Dolby.
Click to expand...
Click to collapse
Strange... Did you enable magisk hide? If not, that is the reason.
Sent from my OnePlus3 using XDA Labs
matssa said:
Strange... Did you enable magisk hide? If not, that is the reason.
Click to expand...
Click to collapse
No, I was using SuperSU 2.79. Same happened with MagiskSU.
This project has been discontinued. The final state of the module can be found at the GitHub Repo https://github.com/Jman420/magisk_selinux_manager.
Magisk SELinux Manager
A Magisk Module dedicated to the manipulation and analysis of SELinux.
Features
* Select SELinux mode to set at startup
Usage
The SELinux mode to set at startup must be specified during module installation. The SELinux mode can be selected either by specifying the mode (permissive or enforcing) in the install zip's filename (ie. magisk_selinux_manager_v1.0_permissive.zip) or using your phone's volume keys when prompted.
Disclaimer & Recommendations regarding Permissive Mode
This module should be used to enable SELinux Permissive Mode only as a last resort only if appropriate SELinux Permissions can not be generated and injected into the SELinux Policy using selinux-inject, supolicy or magiskpolicy. Putting your device into Permissive Mode will essentially disable all of the operating system level security built into Android and allow any app in any context to do whatever it wants. Actions requiring root access will still trigger your SU Manager App, but all apps have elevated privileges due to permissive mode and may be able to take malicious actions on your device without needing root access. If you find that this module fixes issues you are experiencing with an app I recommend contacting the app developer and trying to work with them to isolate the necessary SELinux Permissions and have them injected into the SELinux Policy at startup.
Here is a discussion of some of concerns to consider when running your device in Permissive Mode : https://forum.xda-developers.com/gen...risks-t3607295
GitHub Repo : https://github.com/Jman420/magisk_selinux_manager
Requirements
* SELinux enabled kernel
* Magisk v15.3+
Change Log
* v1.0.5 - Update Unity Installer Files to v1.5.4
* v1.0.4 - Update Unity Installer Files to v1.5.3
* v1.0.3 - Update Unity Installer Files to v1.5.2
* v1.0.2 - Update Unity Installer Files to v1.4.1
* v1.0.1 - Update Unity Installer Files to v1.4
* v1.0.0 - Initial Release
Special thanks!
* topjohnwu - For providing Magisk and the interesting insights that its source code gave into SELinux
* ahrion & zackptg5 - For providing the Unity Installer and Vol Key Input code
* Everyone who supported the old magisk_permissive_script module and giving me a bit of motivation to keep working on SELinux stuff
Release Distribution Plans
All Releases are available on the Magisk Module Repo. Releases will not be distributed here.
Jman420 said:
Magisk SELinux Manager
A Magisk Module dedicated to the manipulation and analysis of SELinux.
Features
* Select SELinux mode to set at startup
Usage
The SELinux mode to set at startup must be specified during module installation. The SELinux mode can be selected either by specifying the mode (permissive or enforcing) in the install zip's filename (ie. magisk_selinux_manager_v1.0_permissive.zip) or using your phone's volume keys when prompted.
Disclaimer & Recommendations regarding Permissive Mode
This module should be used to enable SELinux Permissive Mode only as a last resort only if appropriate SELinux Permissions can not be generated and injected into the SELinux Policy using selinux-inject, supolicy or magiskpolicy. Putting your device into Permissive Mode will essentially disable all of the operating system level security built into Android and allow any app in any context to do whatever it wants. Actions requiring root access will still trigger your SU Manager App, but all apps have elevated privileges due to permissive mode and may be able to take malicious actions on your device without needing root access. If you find that this module fixes issues you are experiencing with an app I recommend contacting the app developer and trying to work with them to isolate the necessary SELinux Permissions and have them injected into the SELinux Policy at startup.
Here is a discussion of some of concerns to consider when running your device in Permissive Mode : https://forum.xda-developers.com/gen...risks-t3607295
GitHub Repo : https://github.com/Jman420/magisk_selinux_manager
Requirements
* SELinux enabled kernel
* Magisk v15.3+
Change Log
* v1.0 - Initial Release
Special thanks!
* topjohnwu - For providing Magisk and the interesting insights that its source code gave into SELinux
* ahrion & zackptg5 - For providing the Unity Installer and Vol Key Input code
* Everyone who supported the old magisk_permissive_script module and giving me a bit of motivation to keep working on SELinux stuff
Release Distribution Plans
I have submitted a request to include this module in the Magisk Repo List. Once that request has been accepted the Magisk Repo List will be the ONLY source for up to date releases of the module. Until that time I will provide download links through this posting.
Click to expand...
Click to collapse
What are the differences with this zip and the old one?
dredq said:
What are the differences with this zip and the old one?
Click to expand...
Click to collapse
When installing the module you can choose if SELinux should be set to enforcing or permissive (it's written right there in the OP).
Didgeridoohan said:
When installing the module you can choose if SELinux should be set to enforcing or permissive (it's written right there in the OP).
Click to expand...
Click to collapse
Sorry. I saw that. I was wondering if there where any other differences.
dredq said:
Sorry. I saw that. I was wondering if there where any other differences.
Click to expand...
Click to collapse
Nope, if there were I'd have mentioned them.
I installed the module and set it to permissive, but when I restarted my phone now it is stuck in the boot animation. I tried uninstalling using the magisk uninstaller, but still the problem remains. Is there a way to undo the changes from Recovery? Thank you! Running lineage 14.
samplebird said:
I installed the module and set it to permissive, but when I restarted my phone now it is stuck in the boot animation. I tried uninstalling using the magisk uninstaller, but still the problem remains. Is there a way to undo the changes from Recovery? Thank you! Running lineage 14.
Click to expand...
Click to collapse
You can flash the zip again to uninstall, thanks to Unity Installer... but I don't expect that to do anything different than the Magisk Uninstall. You may need to debug your Magisk installation with Magisk Manager for Recovery (https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165).
samplebird said:
I installed the module and set it to permissive, but when I restarted my phone now it is stuck in the boot animation. I tried uninstalling using the magisk uninstaller, but still the problem remains. Is there a way to undo the changes from Recovery? Thank you! Running lineage 14.
Click to expand...
Click to collapse
Did you try installing the module again and choosing enforcing instead of permissive?
Update v1.0.1 has been released on Magisk Repo. No real functionality updates, just updated Unity Installer to latest (v1.4). See change logs for Unity Installer here : https://forum.xda-developers.com/android/software/module-audio-modification-library-t3579612
I've also migrated to using Semantic Versioning for this project (although it's probably not needed). See details here : https://semver.org/
The module doesn't seem to be part of the magisk repo yet. But v1.0.0 us working fine on my side anyway. :good:
PixelChris95 said:
The module doesn't seem to be part of the magisk repo yet. But v1.0.0 us working fine on my side anyway. :good:
Click to expand...
Click to collapse
Clear the repo cache (Manager settings) and reload the Downloads list (pull down).
Didgeridoohan said:
Clear the repo cache (Manager settings) and reload the Downloads list (pull down).
Click to expand...
Click to collapse
That did the trick. Thx!
Not working on Oreo b390 Huawei P10. SeLinunx remains on enforce:
watch this issue:
https://forum.xda-developers.com/p10/help/magisk-16-0-p10-orea-t3765921
mxn2000 said:
Not working on Oreo b390 Huawei P10. SeLinunx remains on enforce:
watch this issue:
https://forum.xda-developers.com/p10/help/magisk-16-0-p10-orea-t3765921
Click to expand...
Click to collapse
"Preserve Forced Encryption" doesn't have anything to do with SELinux. That's /data encryption...
Try running:
Code:
setenforce permissive
And if that still doesn't work, run this and use whatever options are available, or return with the result:
Code:
setenforce --help
Every time I setenforce 1 it always says Permissive after .. Even after reboot or in the Twrp terminal .. Anytime I type grtenforce it always says Permissive. What do I type in terminal emulator to access this mod? Am I missing something here?? Lol sorry - still learning.
Intelli69 said:
Every time I setenforce 1 it always says Permissive after .. Even after reboot or in the Twrp terminal .. Anytime I type grtenforce it always says Permissive. What do I type in terminal emulator to access this mod? Am I missing something here?? Lol sorry - still learning.
Click to expand...
Click to collapse
You don't have to do anything after installing the module. At installation your choose enforcing or permissive, and then that's what the module will set at each boot.
OK I thought that was it! Thanks!
so should use this one or old version?
or it is still the same function?
does this work on samsung?
lawong said:
does this work on samsung?
Click to expand...
Click to collapse
Yup, as long as you have magisk.
I have installed a xposed's module that requires Selinux in permissive mode to work.
How do I know what status Selinux is in on my Note 9?
pupido said:
I have installed a xposed's module that requires Selinux in permissive mode to work.
How do I know what status Selinux is in on my Note 9?
Click to expand...
Click to collapse
Depending on how is kernel see if kernel has seelinux permissive