hey guys since "one-click" rooting is now available i though i might post a few instructions on how to install busybox on the ARC/Play/Neo devices...
DO NOT RUN THIS IF U ALREADY HAVE BUSYBOX INSTALLED
download the attached file... it contains busybox v1.17.2 & adb files & will install busybox to /system/xbin/
extract the package in some temporary folder
[ Step 0 ] Root ur device
Root ur device using GingerBreak app
[ Step 1 ] Verify that ur device is rooted
browse to the "files" folder where u extracted package and launch the command prompt in the folder (holding down SHIFT key on keyboard right click and select "Open command window here")
keep the device screen unlocked (also might help to keep screen timeout to >5 mins so that u dont miss the superuser prompts)
now execute the following command in the command prompt
Code:
adb shell "su"
a popup/prompt will come on ur device asking for Superuser permissions... click allow...
if u get permissions denied that means either u did not allow Superuser prompt OR the device was not rooted
[ Step 2 ] Install busybox
{A}
in the same command window (from Step 1) execute the following:
Code:
runme.bat
popup/prompt will come multiple times on ur device asking for Superuser permissions... click allow...
if u get any error or "permission denied" in any of the steps check part {B}
{B} (only if the Step 2 A fails)
<if any popup/prompt comes on ur device asking for Superuser permissions... click allow...>
in the same command window (from Step 1) execute the following:
(this will copy busybox to /data/local/tmp/)
Code:
adb push busybox /data/local/tmp/.
(launch adb shell)
Code:
adb shell
(the following commands are to be input in the adb shell itself)
Code:
su
(remounting system as rw)
Code:
mount -o remount,rw -t yaffs2 `mount | /data/local/tmp/busybox grep /system | /data/local/tmp/busybox awk '{print $1}'` /system
(copying busybox to /system/xbin/)
Code:
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
(verifying ownership)
Code:
chown root.root /system/xbin/busybox
(verifying permissions)
Code:
chmod 04755 /system/xbin/busybox
(installing busybox in /system/xbin/)
Code:
/system/xbin/busybox --install -s /system/xbin
(removing temporary files)
Code:
rm -r /data/local/tmp/busybox
[ Step 3 ] Verify busybox installation
in the same command window (from Step 1) execute the following:
Code:
which busybox
this should return
PHP:
/system/xbin/busybox
and
Code:
ls -l /system/xbin/
this should return a LOT of files lists (which are basically symlinks to /system/xbin/busybox)
if u see only one file (dexdump) then installation was not successful
Search for "Busybox Installer" in the market, I think it's as simple as that
Here's the link https://market.android.com/details?id=com.jrummy.busybox.installer
itskapil said:
Search for "Busybox Installer" in the market, I think it's as simple as that
Here's the link https://market.android.com/details?id=com.jrummy.busybox.installer
Click to expand...
Click to collapse
Busybox Installer sometimes installs in /system/bin and messes up toolbox symlinks... also its option to install in /system/xbin doesnt always work...
it works for my ARC, without busybox, Titium backup not working, after install busybox from market, it T backup works.
keijames said:
it works for my ARC, with busybox, Titium backup not working, after install busybox from market, it T backup works.
Click to expand...
Click to collapse
did u try the manual way i posted in 1st post of this thread?
cause i tested this yesterday night on my Arc and TB, Root Explorer, SetCPU, ScreenShot, AbsoluteSystem, all work with the manual way i posted here in OP (1st post of this thread)...
It is much simpler to use the busybox installer, it works and takes much less time
All I did is root my phone installed titanium and installed busybox through titanium and everything works perfect for me no problems watsoever
Sent from my LT15i using XDA Premium App
i would agree with installing from the market its much more easier and hasssle free! i could not gain acesss to titanium backup, but after i installed bb from market, everything works fine
SiRIus[X] said:
i would agree with installing from the market its much more easier and hasssle free! i could not gain acesss to titanium backup, but after i installed bb from market, everything works fine
Click to expand...
Click to collapse
+1, the market one is as good as you can get...
Sent from my arc using tapatalk
PollPixx said:
+1, the market one is as good as you can get...
To TS, thanks for your time and input! Its not flaming you, but the job can be done much easier
Sent from my arc using tapatalk
Click to expand...
Click to collapse
Sent from my arc using tapatalk
can any body upload the 1.19 version for us on mediafire
I just downloaded titanium back up, clicked on Problems? Which then installed busybox
Sent from my LT15i using XDA App
Awesome guide.
Instead of ADB, you can do it all in terminal emulator.
Regarding market installers, they usually work fine.
But some people experience bugs with them or have limited version's to choose from.
So this is a sure fire way to get what you want installed without hassles.
mount not prmited
it say mount not permitted on my sony xperia t3 please help me. been looking for years to install busybox on my phone.
Hello,
On my Teclast P90HD running Kitkat 4.4.2, I found a /system/xbin/su binary while connected through adb. However, the su command in Terminal emulator gives :
uid 10107 not allowed to su
I guess it has to do with SELinux. After setenforce = 0 and reboot, getenforce returns 'Disabled', yet no change in Terminal Emulator.
Installing SuperSU apk from Play Store obviously fails, and I can't get it to boot in recovery to try flashing UPDATE-SuperSU-v2.46.zip.
Is there anything I can do to get that su file helpful ?
Thanks.
Hi, did you find any solution here ?
I'm in the same situation, what looks to be a solution is to recompile su.c removing the AID_ROOT / AID_SHELL related part.
I've been trying to get ViPER4Android FX to work, but so far I haven't been able to. Whenever I try to open up Viper, my current song stops playing and an error pops up saying "Unable to play track...". I have the drivers installed, but I've noticed that when I look at driver status, it says "Driver Version: 2.4.0.1, NEON Enabled: No, Enabled: No, Status: Abnormal, Audio Format: Unsupported, Processing: No, Sampling Rate: 0". My device is rooted and I have set_immutable.list deleted, so that can't be the problem.
Does anybody know what might be stopping my device from running ViPER4Android FX properly?
madis121 said:
I've been trying to get ViPER4Android FX to work, but so far I haven't been able to. Whenever I try to open up Viper, my current song stops playing and an error pops up saying "Unable to play track...". I have the drivers installed, but I've noticed that when I look at driver status, it says "Driver Version: 2.4.0.1, NEON Enabled: No, Enabled: No, Status: Abnormal, Audio Format: Unsupported, Processing: No, Sampling Rate: 0". My device is rooted and I have set_immutable.list deleted, so that can't be the problem.
Does anybody know what might be stopping my device from running ViPER4Android FX properly?
Click to expand...
Click to collapse
First of all make sure you have busybox installed. Then
download terminal emulator from the playstore and type in the following commands exactly:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
lsattr
Then download audio_effects.conf file and with a root explorer replace the one in /system/etc
That should fix your problem.
TheSproker said:
First of all make sure you have busybox installed. Then
download terminal emulator from the playstore and type in the following commands exactly:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
lsattr
Then download audio_effects.conf file and with a root explorer replace the one in /system/etc
That should fix your problem.
Click to expand...
Click to collapse
I got it working, thanks!
deleted
library needed
TheSproker said:
First of all make sure you have busybox installed. Then
download terminal emulator from the playstore and type in the following commands exactly:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
lsattr
Then download audio_effects.conf file and with a root explorer replace the one in /system/etc
That should fix your problem.
Click to expand...
Click to collapse
Hello and thanks for your great help.
I ran the command and copied audio_effects.config but I got
Driver version: 2.5.0.4
NEON enabled : Yes
Enabled: Yes
Status: Normal
Audio Format : supported
Processing : No
Sampling rate: 48000
I took a look at your audio_effects.config and I saw a libv4a_fx_ics.so missing.
Do you have it and please share it with us:good:
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Invert The Default Android SELinux Mode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive]).
- One Module To Switch Between Enforcing Mode & Permissive Mode
- This Module Changes The SELinux Mode For The Entirety Of The Device's Uptime Until Next Reboot
- The Default Android SELinux Mode Can Be Either Enforcing Mode Or Permissive Mode Which Depends On The Installed/Flashed Rom/Kernel
- After The Installation & 1st Reboot, The SELinux Mode = The Default Android SELinux Mode
- Disabling The Module = The Default Android SELinux Mode (Next Reboot)
- Enabling The Module = Inverting The Default Android SELinux Mode (Next Reboot)
Current Version: 1.0.3.3
- SELinux Enabled Kernel/SELinux Development Mode Is A Main Point To Use The Module So Check The General Steps
- Disabling Itself Before Getting Stuck On Bootloop For Some Roms/Kernels
- Just Install It & You Don't Need To Do Anything More
- Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of SELinuxModeInverter
- For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Solved By Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]
- For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Wait --> Reboot
- For Activating The Wait Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Delete The File Of Disable From The Folder Of Wait --> Reboot
Created: Apr.09.2018
Updated: May.09.2019
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The General Steps)
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
- Or Using A Flash-Tool (Flasher) Such FlashFire, Flashify Or Rashr --> Flash ZIP File (Flash A Flashable ZIP File) --> Choose The Downloaded File --> Reboot
Recommendation/In-Case Of Failure:
- Check The General Steps From This Post https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271/post76381334
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Core Only Mode - Microsoft Intune Company Portal Hider - Other Modules
----------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------
permissive mode, selinux permissive, selinux permissive mode, enforcing mode, selinux enforcing, selinux enforcing mode, selinux mode changer, selinux changer, selinux switch, selinux selector, selinux toggler, setenforce, getenforce, magisk selinux, sestatus, enforce, permissive, selinux enabled kernel, selinux development mode, selinux manager, magisk module, selinux converter, selinux mode converter
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi,
Saw your module, just wanted to tell you that not all devices have `getenforce`, some have `sestatus` instead. You might need to update accordingly.
MCMotherEffin'
SELinuxModeInverter4Magisk-v1.0.1
MCMotherEffin' said:
Hi,
Saw your module, just wanted to tell you that not all devices have `getenforce`, some have `sestatus` instead. You might need to update accordingly.
MCMotherEffin'
Click to expand...
Click to collapse
MCMotherEffin
Thanks For Your Advice & Your Modules. Kindly see the Attached Modified Module (SELinuxModeInverter4Magisk-v1.0.1(v1500)(3MF).zip) .
I would be Happy If There Is Any Recommendation/Advice.
Thanks Again.
Dreamer(3MF) said:
MCMotherEffin
Thanks For Your Advice & Your Modules. Kindly see the Attached Modified Module (SELinuxModeInverter4Magisk-v1.0.1(v1500)(3MF).zip) .
I would be Happy If There Is Any Recommendation/Advice.
Thanks Again.
Click to expand...
Click to collapse
Hi,
Instead of using `ls`, you could simply put `||` in there, also you could combine exit 1 into the same statement.
Code:
if ! selinux_mode=$(getenforce || sestatus); then exit 1; fi;
The above statement combines setenforce, sestatus and exit all in one. Also you don't need asterisks in the case statement and, setenforce takes only 1 and 0 as arguments, not enforcing or permissive, no matter what getenforce / sestatus shows.
Code:
case $selinux_mode in
enforcing|Enforcing|1 ) setenforce 0; ;;
permissive|Permissive|0) setenforce 1; ;;
esac;
will do the job while saving space.
What would one gain from inverting the status during Magisk's Startup?
MCMotherEffin' said:
Hi,
Instead of using `ls`, you could simply put `||` in there, also you could combine exit 1 into the same statement.
Code:
if ! selinux_mode=$(getenforce || sestatus); then exit 1; fi;
The above statement combines setenforce, sestatus and exit all in one. Also you don't need asterisks in the case statement and, setenforce takes only 1 and 0 as arguments, not enforcing or permissive, no matter what getenforce / sestatus shows.
Code:
case $selinux_mode in
enforcing|Enforcing|1 ) setenforce 0; ;;
permissive|Permissive|0) setenforce 1; ;;
esac;
will do the job while saving space.
Click to expand...
Click to collapse
Concerning
A- (if ! selinux_mode=$(getenforce || sestatus); then exit 1; fi , I tried Something like This But The Module doesnot change the SELinux Mode because 'sestatus' which is not Supported in My Android So The Module will get An Error which force to not Continue. So The Best Solution For Me is Using 'ls'.
B- The Other Points, Will be Reflected/Applied In The Next Version
Thanks For Sharing Your Thoughts & Efforts
SELinuxModeInverter4Magisk-v1.0.2
Dreamer(3MF) said:
Concerning
A- (if ! selinux_mode=$(getenforce || sestatus); then exit 1; fi , I tried Something like This But The Module doesnot change the SELinux Mode because 'sestatus' which is not Supported in My Android So The Module will get An Error which force to not Continue. So The Best Solution For Me is Using 'ls'.
B- The Other Points, Will be Reflected/Applied In The Next Version
Thanks For Sharing Your Thoughts & Efforts
Click to expand...
Click to collapse
I use Your Sytanx [ (if ! selinux_mode=$(getenforce || sestatus); then exit 1; fi] which works Good
oreo27 said:
What would one gain from inverting the status during Magisk's Startup?
Click to expand...
Click to collapse
For Example
- This is Useful for Certain Audio Mods.
- Some Android Versions come with Permissive As The Default SELinux Mode. Enforcing is The Preferred SELinux Mode for Security so You can choose It But It needs SELinux Enabled Kernel.
Kindly check This Link https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
Dreamer(3MF) said:
For Eaxample
- This is Useful for Certain Audio Mods.
- Some Android Versions come with Permissive As The Default SELinux Mode. Enforcing is The Preferred SELinux Mode for Security so You can choose It But It needs SELinux Enabled Kernel.
Kindly check This Link https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
Click to expand...
Click to collapse
Thank you!
Ah yes. I think I've read something similar to what you've mentioned. If mine is already Enforcing, will this change it to Permissive during the boot-up process only or for the entirety of the device's uptime until next reboot?
If the former, what benefits will I actually gain in having it use Permissive during boot-up?
oreo27 said:
Thank you!
Ah yes. I think I've read something similar to what you've mentioned. If mine is already Enforcing, will this change it to Permissive during the boot-up process only or for the entirety of the device's uptime until next reboot?
If the former, what benefits will I actually gain in having it use Permissive during boot-up?
Click to expand...
Click to collapse
This Module will change the SELinux Mode for the entirety of the device's uptime until next reboot
Notes:
- This Module Changes The SELinux Mode (Invert The Default Android SELinux Mode) For The Entirety Of The Device's Uptime Until Next Reboot
- Disabling This Module From Magisk Manager = The Default Android SELinux Mode
- Enabling This Module From Magisk Manager = Inverting The Default Android SELinux Mode
- Enforcing Mode For Security
- Permissive Mode For Mods (Specially Audio Mods)
For Magisk v1400, Download SELinuxModeInverter4Magisk-v1.0.2(v1400)(3MF).zip
Reserved for News/Updates #1
Deleted
Reserved for News/Updates #2
Changelog: More Details Have Been Added In The 1st Post.
Updated SELinuxModeInverter4Magisk To v1.0.3!
Changelog: Disabling Itself Before Getting Stuck On Bootloop For Some Roms/Kernels.
Just Install It & You Don't Need To Do Anything More.
For More Details About Enforcing Mode & Permissive Mode, Check This Link https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
The General Steps:
- SELinux Enabled Kernel/SELinux Development Mode Is Required Which Means The Installed/Flashed Rom/Kernel Has The Ability To Switch Between Enforcing Mode & Permissive Mode
- To Check The Above Mentioned Ability, Install Terminal Emulator From PlayStore --> Open It -->
-----> For Getting The Current Android SELinux Mode, Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter
-----> For Setting The Current Android SELinux Mode, Write su --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter
-----> Check Again The Current Android SELinux Mode
-----> If The Mentioned Steps Worked/Succeeded, Download SELinuxModeInverter4Magisk From This Link https://androidfilehost.com/?w=files&flid=293646 & Flash It Then Reboot
-----> Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
-----> For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager
-----> For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Solved By Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting]
-----> For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Wait --> Reboot
-----> For Activating The Wait Mode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Delete The File Of Disable From The Folder Of Wait --> Reboot
-----> If The Mentioned Steps Didn't Work/Succeed, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Enforcing Mode & Permissive Mode So Flash Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode
- P.S. Maybe The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Can Use Only The Wait Mode (Not The Fast Mode)
- For Magisk Users, If You Want To Get Accurate Feedback From getenforce/sestatus, Disable Magisk Hide (Magisk Manager --> Settings --> Disable Magisk Hide) And After Finishing, Enable Magisk Hide Again [P.S. Magisk Hide Will Hide That Your Device Is In Permissive Mode To Pass The SafetyNet]
In-Case Of Failure: After Doing Successfully The Above Mentioned Steps
- For Magisk Users, Disable All Modules From Magisk Manager (Modules) & Also Disable All Apps Except Terminal Emulator From Magisk Manager (SuperUser) Then Reboot
- For Non-Magisk Users, Disable All Apps Except Terminal Emulator From SuperUser Of The Used Rooting Tool Then Reboot
- For Activating The Functionality Of ClearDalvikCache, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> DalvikCache --> Delete The File Of Disable From The Folder Of Active --> Reboot
- For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To The Folder Of Inactive --> Reboot
- Terminal Emulator --> Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator
- Download The Test Module Of SELinuxModeInverter4Magisk From This Link https://androidfilehost.com/?w=files&flid=274655 & Flash It Then Reboot
- Wait About 30 Min.
- Terminal Emulator --> Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator
- Reboot & Wait About 30 Min.
- Terminal Emulator --> Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator
- Send A Copy Of debug-SELinux.txt & debug-SELinux-BU.txt (Their Paths Are Root --> /data/debug-SELinux.txt, /data/debug-SELinux-BU.txt & For Copying These Files, Use Any Root File Explorer Such As MiXplorer)
- For Magisk Users, Magisk Manager --> Modules --> Send Its Screenshot & Magisk Manager --> SuperUser --> Send Its Screenshot
- For Non-Magisk Users, Send The Screenshot Of SuperUser Of The Used Rooting Tool
- Send Full Logcat (Download Logcat Extreme From PlayStore)
- For Magisk Users, Send Magisk Log (Magisk Manager --> Log --> Magisk & Also The Screenshot Of Magisk Manager --> Log --> SuperUser]
P.S. In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module,
- For Magisk Users, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
- For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module To Uninstall The Module
Updated SELinuxModeInverter4Magisk To v1.0.5!
Changelog: Checking Its Path.
Just Install It & You Don't Need To Do Anything More.
Monitor Magisk Daemon
About Module
Never let magisk crash and lose root again
Those of you who use Magisk, along with aggressive battery saving profiles in your android phone for longer battery backup, it seems that magisk sometimes loses root, which is very annoying. Some people face it several times a day. As a result, they have to restart their phones to gain root access again.
To solve this problem, I made this simple module, which monitors magisk daemon process. Whenever it crashes or gets destroyed, the module tries to restart the daemon. Also, it keeps logs of its activity. Unless your aggressive power profile kills this module, you're never going to lose root again.
Click to expand...
Click to collapse
Download Link
Download Monitor_Magisk_Daemon_1.0.1
How to Use
Extremely Easy
Simply download the module and flash inside magisk. On the next boot, the module will start its' job automatically.
However, if you want to customize it, you can run the script in your terminal for real time update as well. For this, just open your terminal emulator and type:
PHP:
monitor_magisk_daemon.sh --term
# or
monitor_magisk_daemon.sh -t
For no log file mode:
PHP:
monitor_magisk_daemon.sh --no-log --term --single
# or
monitor_magisk_daemon.sh -n -l -s
To kill the module:
PHP:
monitor_magisk_daemon.sh --single
# or
monitor_magisk_daemon.sh -s
For silent operation:
PHP:
monitor_magisk_daemon.sh --no-log
# or
monitor_magisk_daemon.sh -nl
Logs may be found in:
`/data/local/tmp/monitor_magisk_daemon.log`
This is helpful to determine when the magisk gets killed
Click to expand...
Click to collapse
Inspired by
The wonderful guy at XDA named Geofferey :
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Author
sheikhmishar