Related
From time to time, Xposed cant load at start. Reason unknown, Error -2147483646
Code:
02-17 15:46:52.154: I/Xposed(4661): Starting Xposed binary version 60, compiled for SDK 21
02-17 15:46:52.154: I/Xposed(4661): Phone: Nexus 7 (asus), Android version 5.0.2 (SDK 21)
02-17 15:46:52.154: I/Xposed(4661): ROM: LRX22G
02-17 15:46:52.154: I/Xposed(4661): Build fingerprint: google/razor/flo:5.0.2/LRX22G/1649326:user/release-keys
02-17 15:46:52.154: I/Xposed(4661): Platform: armeabi-v7a, 32-bit binary, system server: yes
02-17 15:46:52.154: I/Xposed(4661): SELinux enabled: yes, enforcing: no
02-17 15:46:52.158: E/Xposed(4697): Error -2147483646 while adding app service user.xposed.app
02-17 15:46:57.161: E/Xposed(4661): Zygote service is not running, Xposed cannot work without it
After another reboot it work 99%
Did you fix this? I got the same error today
Did I read that first line correctly? Version 60?
You need to give more info. What ROM (stock Nexus?). What version of Xposed.
The last line tells you why Xposed isn't running. You might want to search for that.
EDIT: LOL, I just noticed the original post is from way back in February. @atrix4nag, maybe you should post your output instead.
LG G3 D851, Fusion ROM, Tapatalk 4.9.5
I got same error on nexus 6p.
It will randomly soft rebooted and this error show.
Xposed will work again after I hard reboot myself
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.
As the title says, Play Services doesn't show up on MagiskHide for some reason. I'm on Android 5.0 in a quite old Lenovo A7000 Plus, and lately I just kept trying to pass SafetyNet to no avail.
(Still on the manufacturer stock ROM)
Some of the things I have tried are:
enabling Magisk Core Only mode
testing out MagiskHide again as on this guide
toggling MagiskHide on and off and rebooting in between
uninstalling Play Services updates and reinstalling new ones (2 times)
clearing Play services' cache and data
uninstalling Play Store updates and reinstalling new ones
clearing Play Store's cache and data
uninstalling other root apps (Lucky Patcher) and clearing AdAway's hosts file
toggling SELinux to Enforcing and uninstalling the app I've used to do so
signing my phone out of my Google account and back again
disabling USB debugging
wiping dalvik and cache in TWRP 3.0
reinstalling Magisk 17.1 Stable
uninstalling Magisk 17.1 Stable and installing 17.3 Beta
reinstalling Magisk 17.1 again.
adding Play Services to MagiskHide through terminal commands:
HTML:
su
magiskhide --add com.google.android.gms
Also, whenever I click on any app in the Store i get an FC. I can only install apps, but only through the three-dot menu. I can install Netflix and even run Pokemon Go without issues, but the Store says my device is not certified.
My Play Store version is 12.3.30 and my Play Services is 14.3.66.
I still need Google Pay but I'm completely lost.
If anyone can help me out I'd greatly appreciate it.
Play services are added to the Hide list by default, they don't need to show up in the Hide list...
Have you made sure that MagiskHide works at all?
Where's that Magisk log?
Didgeridoohan said:
Play services are added to the Hide list by default, they don't need to show up in the Hide list...
Have you made sure that MagiskHide works at all?
Where's that Magisk log?
Click to expand...
Click to collapse
Hello, thanks for the reply.
Oh. I didn't know that... quite odd that my first Magisk 17.1 stable installation made it show up.
I did; I toggled it on other root apps e.g. Titanium Backup, Kernel Adiutor, etc.
Here's the log after I updated to 17.3 Beta:
HTML:
11-11 17:22:51.836 237 237 I Magisk : Magisk v17.3(17302) daemon started
11-11 17:22:51.851 241 241 I Magisk : Magisk v17.3(17302) logger started
11-11 17:22:51.852 237 238 I Magisk : ** post-fs-data mode running
11-11 17:22:51.852 237 238 I Magisk : * Mounting /data/adb/magisk.img
11-11 17:22:51.893 237 238 I Magisk : * Running post-fs-data.d scripts
11-11 17:22:51.893 237 238 I Magisk : * Running module post-fs-data scripts
11-11 17:22:51.893 237 238 I Magisk : * Loading modules
11-11 17:22:51.893 237 238 I Magisk : * Enabling systemless hosts file support
11-11 17:22:51.899 237 238 I Magisk : bind_mount: /system/etc/hosts
11-11 17:22:51.900 237 253 I Magisk : * Starting MagiskHide
11-11 17:22:51.900 237 253 I Magisk : hide_utils: Hiding sensitive props
11-11 17:22:51.900 237 253 I Magisk : hide_list: [com.google.android.gms.unstable]
11-11 17:22:51.913 237 253 I Magisk : hide_list: [com.google.android.instantapps.supervisor]
11-11 17:22:51.926 237 253 I Magisk : hide_list: [com.google.android.play.games]
11-11 17:22:51.940 237 253 I Magisk : hide_list: [com.google.android.gsf.login]
11-11 17:22:51.953 237 253 I Magisk : hide_list: [com.google.android.googlequicksearchbox]
11-11 17:22:51.968 237 253 I Magisk : hide_list: [com.landbank.mobilebanking]
11-11 17:22:51.982 237 253 I Magisk : hide_list: [com.google.android.partnersetup]
11-11 17:22:51.993 237 253 I Magisk : hide_list: [com.google.android.apps.plus]
11-11 17:22:52.004 237 253 I Magisk : hide_list: [com.grabtaxi.passenger]
11-11 17:22:52.015 237 253 I Magisk : hide_list: [com.lazada.android]
11-11 17:22:52.030 237 253 I Magisk : hide_list: [com.android.vending]
11-11 17:22:52.041 237 253 I Magisk : hide_list: [com.google.android.gms]
11-11 17:22:52.056 237 253 I Magisk : hide_list: [com.paymaya]
11-11 17:22:52.446 237 335 I Magisk : ** late_start service mode running
11-11 17:22:52.447 237 335 I Magisk : * Running service.d scripts
11-11 17:22:52.447 237 335 I Magisk : * Running module service scripts
11-11 17:23:35.494 237 253 I Magisk : proc_monitor: com.google.android.googlequicksearchbox:interactor
11-11 17:23:36.173 237 253 I Magisk : proc_monitor: com.google.android.gms
11-11 17:23:37.744 237 253 I Magisk : proc_monitor: com.google.android.googlequicksearchbox:search
11-11 17:23:39.082 237 253 I Magisk : proc_monitor: com.google.android.partnersetup
11-11 17:23:41.504 237 253 I Magisk : proc_monitor: com.android.vending
11-11 17:23:43.809 237 253 I Magisk : proc_monitor: com.google.android.gms:car
11-11 17:23:55.475 237 253 I Magisk : proc_monitor: com.google.android.partnersetup
11-11 17:23:56.637 237 253 I Magisk : proc_monitor: com.android.vending
11-11 17:23:57.028 237 253 I Magisk : proc_monitor: com.google.android.gms:car
11-11 17:24:03.877 237 253 I Magisk : proc_monitor: com.google.android.googlequicksearchbox:search
11-11 17:24:07.349 237 253 I Magisk : proc_monitor: com.google.android.gms.unstable
11-11 17:24:29.773 237 253 I Magisk : proc_monitor: com.google.android.apps.plus
11-11 17:24:30.676 237 253 I Magisk : proc_monitor: com.google.android.googlequicksearchbox:search
11-11 17:24:43.117 237 253 I Magisk : proc_monitor: com.android.vending
11-11 17:24:45.439 237 253 I Magisk : proc_monitor: com.google.android.gms:car
11-11 17:24:46.106 237 253 I Magisk : proc_monitor: com.google.android.apps.plus
11-11 17:24:46.769 237 253 I Magisk : proc_monitor: com.google.android.googlequicksearchbox:search
11-11 17:24:53.757 237 6821 I Magisk : hide_list add: [com.google.android.gsf]
11-11 17:24:54.021 237 253 I Magisk : proc_monitor: com.google.android.gms
11-11 17:28:56.531 237 253 I Magisk : proc_monitor: com.google.android.gms.unstable
11-11 17:29:08.148 237 253 I Magisk : proc_monitor: com.grabtaxi.passenger
11-11 17:33:05.230 237 253 I Magisk : proc_monitor: com.android.vending
11-11 17:33:05.779 237 253 I Magisk : proc_monitor: com.google.android.gms:car
11-11 19:24:06.905 237 253 I Magisk : proc_monitor: com.grabtaxi.passenger
11-11 19:25:43.491 237 253 I Magisk : proc_monitor: com.google.android.gms.unstable
I also don't have any modules installed, and AdAway seems to still modify the system partition despite of the systemless hosts setting in Magisk Manager. I currently have no idea why.
Let's continue then...
Only add the apps that absolutely need to be on the Hide list. Every addition comes with a price... To pass SafetyNet you don't need to add anything.
Do you at least pass Basic integrity? If that passes, but the CTS profile check fails, try using my MagiskHide Props Config module to set a certified fingerprint. That might help.
If you fail both CTS and Basic integrity, but you've verified that MagiskHide works (hiding root from a root app), that likely means you've got something else on your device causing SN to fail. You don't happen to have Xposed installed?
Got it.
Nope, just "response is invalid".
I don't have Xposed... I do have a non-systemless iYTBP (Youtube Vanced). I installed it a few months ago before I completely switched from SuperSU to Magisk. My first installation was fine though, i used the unSU script from osm0sis and then installed Magisk in TWRP. Could the non-systemless YouTube Vanced have tripped SN? Cause it didn't at the first time I installed Magisk...
Also i kept Play Store at the "factory version" cause it's the only state that it can install/update my apps successfully. Don't know why it FCs on the latest version.
"Response is invalid" is not a failed SafetyNet test. That just means that you don't have a proper answer from the servers. Usually caused by using an app that's not been updated to the latest Google APIs (use the Magisk Manager to check SN), or there's something wrong with your Play Services. Since you're keeping them at a "factory version" on an Android 5.0 system, that's likely your issue. You need to have the latest updates...
Didgeridoohan said:
"Response is invalid" is not a failed SafetyNet test. That just means that you don't have a proper answer from the servers. Usually caused by using an app that's not been updated to the latest Google APIs (use the Magisk Manager to check SN), or there's something wrong with your Play Services. Since you're keeping them at a "factory version" on an Android 5.0 system, that's likely your issue. You need to have the latest updates...
Click to expand...
Click to collapse
Do I have to keep both Play Services and the Store at the latest version? I have Play Services at the latest version but not the Play Store because of the reasons I've said... Also I've checked with another SN test app and both basic integrity and CTS are failed.
Anyone?
(I have Play Services at the latest version available for my phone, but I kept the Play Store at the default version that came with my phone.)
HootenannyMagic said:
Also I've checked with another SN test app and both basic integrity and CTS are failed.
Click to expand...
Click to collapse
What app are you using to check SafetyNet? I've seen several of the apps that haven't been updated for the new API to wrongly report an invalid response as a failed check (when I haven't been able to use the Magisk Manager, I've always turned to SafetyNet Helper Sample)... And I'm assuming that the "invalid response" result is from the Magisk Manager, or?
You hint at having been able to pass SafetyNet previously on your device (with Magisk installed). If so, what changed between passing and failing? What did you do to your device?
You've already seen my troubleshooting guide, so you have everything there at your disposal... I can add that if you have confirmed that MagiskHide actually works (hiding root from a root app) and you still see a failed SafetyNet check (both CTS and Basic integrity), that likely means there's something about your device that triggers SafetyNet. You'll have to find out what...
Lastly, it's usually a good idea to use the latest Canary build when troubleshooting. There might be bugs in the stable and beta releases that have been fixed in the Canary build. And if you're going to be providing logs, make sure to use the debug channel. I don't think that it'll have any impact on your case, but it's generally a good practise.
Didgeridoohan said:
What app are you using to check SafetyNet? I've seen several of the apps that haven't been updated for the new API to wrongly report an invalid response as a failed check (when I haven't been able to use the Magisk Manager, I've always turned to SafetyNet Helper Sample)... And I'm assuming that the "invalid response" result is from the Magisk Manager, or?
You hint at having been able to pass SafetyNet previously on your device (with Magisk installed). If so, what changed between passing and failing? What did you do to your device?
You've already seen my troubleshooting guide, so you have everything there at your disposal... I can add that if you have confirmed that MagiskHide actually works (hiding root from a root app) and you still see a failed SafetyNet check (both CTS and Basic integrity), that likely means there's something about your device that triggers SafetyNet. You'll have to find out what...
Lastly, it's usually a good idea to use the latest Canary build when troubleshooting. There might be bugs in the stable and beta releases that have been fixed in the Canary build. And if you're going to be providing logs, make sure to use the debug channel. I don't think that it'll have any impact on your case, but it's generally a good practise.
Click to expand...
Click to collapse
I've also used the same app to check SN. It reported failed in both basicintegrity and ctsprofilematch.
However I've tried reverting all my non-systemless modifications on the /system partition, and sometimes Magisk Manager would report that my phone passed SN, but then hours later it's back to failed.
I've also noticed that my SELinux permissive mode seems to not get hidden by Magisk. Was it supposed to hide permissive, or to set it back to default enforcing? I've read an outdated part on your guide that Magisk Hide uses a pseudo-enforcing SELinux state to mask a permissive kernel. I've just toggled it from permissive to enforcing in a terminal emulator, and now Magisk says I'm passing SN again. I'm not really sure if it's the SELinux mode that trips my SN...
Also i'm getting rather confused that I can install Netflix even when i'm not certified on the Play Store.
It very much sounds like it's SELinux. There have been a couple of reports that Magisk can have trouble hiding a permissive SELinux on some devices...
Just keep it at enforcing and you should be good.
Didgeridoohan said:
It very much sounds like it's SELinux. There have been a couple of reports that Magisk can have trouble hiding a permissive SELinux on some devices...
Just keep it at enforcing and you should be good.
Click to expand...
Click to collapse
Okay now i've kept it at Enforcing and SN passed, but just half an hour later it's back to failed. I've reverted all the non-systemless modifications I've possibly made but nothing seems to work. Im back to being clueless.
HootenannyMagic said:
Okay now i've kept it at Enforcing and SN passed, but just half an hour later it's back to failed. I've reverted all the non-systemless modifications I've possibly made but nothing seems to work. Im back to being clueless.
Click to expand...
Click to collapse
If you can repeat that same process with the Canary debug build and afterwards provide the Magisk log, it might show what's going on.
Didgeridoohan said:
If you can repeat that same process with the Canary debug build and afterwards provide the Magisk log, it might show what's going on.
Click to expand...
Click to collapse
Okay I've installed the canary debug build and here are the logs.
Thank you for putting up with me.
At any time during the timeframe the log was saved, did SafetyNet first work and then fail (like you described earlier)?
And right now I seem to be passing SN, but minutes ago I wasn't. I think SN would fail again minutes from now.
Didgeridoohan said:
At any time during the timeframe the log was saved, did SafetyNet first work and then fail (like you described earlier)?
Click to expand...
Click to collapse
I saved the log when SN didn't work since it's originally like that, and then I toggled SELinux again. Right now i seem to pass SN.
And now it's back to failed.
HootenannyMagic said:
And now it's back to failed.
Click to expand...
Click to collapse
And I'm assuming you don't have a Canary debug log showing the transition from passing to failing?
Without any kind of detailed info as to what's actually happening, there's not much anyone can do...
Didgeridoohan said:
And I'm assuming you don't have a Canary debug log showing the transition from passing to failing?
Without any kind of detailed info as to what's actually happening, there's not much anyone can do...
Click to expand...
Click to collapse
I do have the debug log
Hi everyone, looking for some guidance on magisk hide. I've searched for days but nothing yet, I'll try my best to explain my problem then I'll list my device and ROM etc after. So I've rooted my phone, installed magisk, updated everything within magisk, magisk hide works and hides my root from banking Netflix etc, modules install without a hitch and work fine BUT... When ever I try to hide magisk manager itself (different name etc) I get the error message "hide magisk failed." My logs show nothing related to it so no error codes or reasons it could be being blocked. I checked out John wus Twitter he had a post a while back explaining that Google play protect is blocking the installation and to disable it then enable it after magisk repacks. Most people there said it worked for them, but it isn't working for me. Things I've tried:
Uninstall magisk through the app and reinstall (twrp)
Unroot phone and reroot through twrp
Update OS
Wipe phone, downgrade OS reroot
Disable Google play through play store
Disable all Google services using service disabler app
Disable all Google services and miui security
Updated magisk to canary
Downgraded magisk to 19.4 (now back on latest build)
Deleted the magisk files in root browser
Renamed magisk files through twrp and through root browser
There may be a couple of other things I've tried Ive been at it for days lol. I'm hoping I'm just being really stupid and missing something and it's an easy fix, but googling it brings up mainly older posts, the fixes I find don't work for me, or people assume I'm asking about 'magisk hide' rather than 'hide magisk'. I would really appreciate any help people could give. Thank you
Phone details:
Redmi note 8 pro Global
Miui global 10.4.1 (pggmixm)
Android version 9
Security patch 2019-9-1
Magisk
20.2
Manager
7.4.1
(Canary)
You're mixing up the terminology a bit, which might explain why some have a hard time understanding what you're asking for. You're trying to hide the Manager, not Magisk.
Another thing you could try is if it's SELinux causing issues. Set it to permissive and try again (and don't forget to set it back to enforcing again afterwards). If it still fails, you'll need to provide at least a logcat showing when things go wrong.
Ah brilliant thanks I'll try that now n let u know yeah I thought I might be getting something wrong, it usually just works firs time so I've never actually had to actually look into how it works etc lol
Solved!
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
m4rkj4y said:
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
Click to expand...
Click to collapse
We're always learning on XDA [emoji4]
I'm always happy to learn, I usually get so mad with getting something wrong I overlook the simple things lol
m4rkj4y said:
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
Click to expand...
Click to collapse
I have the same problem in note 8 pro. Could you provide the details how to solve the problem? Many thx
m4rkj4y said:
Your an absolute legend. Worked a charm!! I really can't thank you enough, I feel really stupid, but I'm also very happy now lol. Thanks so much
Click to expand...
Click to collapse
Have you solved the problem?
Teach me please
log:
--------- beginning of main
--------- beginning of system
03-19 18:48:48.508 456 456 I Magisk : Magisk v20.3(20300) daemon started
03-19 18:48:48.508 456 456 I Magisk : * Device API level: 28
03-19 18:48:58.498 456 457 I Magisk : ** post-fs-data mode running
03-19 18:48:58.500 456 457 I Magisk : * Initializing Magisk environment
03-19 18:48:58.515 456 457 E Magisk : su: cannot find manager
03-19 18:48:58.516 456 457 I Magisk : * Mounting mirrors
03-19 18:48:58.518 456 457 I Magisk : mount: /sbin/.magisk/mirror/vendor
03-19 18:48:58.518 456 457 I Magisk : mount: /sbin/.magisk/mirror/data
03-19 18:48:58.518 456 457 I Magisk : link: /sbin/.magisk/mirror/system
03-19 18:48:58.518 456 457 I Magisk : link: /sbin/.magisk/mirror/product
03-19 18:48:58.518 456 457 I Magisk : * Setting up internal busybox
03-19 18:48:58.528 456 457 I Magisk : * Running post-fs-data.d scripts
03-19 18:48:58.530 456 457 I Magisk : * Running module post-fs-data scripts
03-19 18:48:58.530 456 457 I Magisk : * Loading modules
03-19 18:48:58.535 456 466 I Magisk : * Starting MagiskHide
03-19 18:48:58.535 456 466 I Magisk : hide_policy: Hiding sensitive props
03-19 18:48:58.535 456 466 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
03-19 18:48:58.538 456 466 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
03-19 18:48:59.178 456 738 I Magisk : ** late_start service mode running
03-19 18:48:59.179 456 738 I Magisk : * Running service.d scripts
03-19 18:48:59.186 456 738 I Magisk : * Running module service scripts
03-19 18:49:07.765 456 2144 I Magisk : ** boot_complete triggered
03-19 18:49:07.816 2159 2159 I Magisk : apk_install: /data/magisk.apk
03-19 18:49:26.698 456 466 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[5699] UID=[10010]
03-19 18:49:30.324 6360 6360 I Magisk : apk_install: Success
03-19 18:49:44.754 456 466 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[8515] UID=[10010]
Work
Hide magisk manager App
1.Set Selinux permissive.
Open terminal type
su
setenforce 0
2.Force close magisk manager from settings
3.Open magisk manager and go to settings click on hide magisk manager and put any name then ok ..and wait
Spiderlll said:
Hide magisk manager App
1.Set Selinux permissive.
Open terminal type
su
setenforce 0
2.Force close magisk manager from settings
3.Open magisk manager and go to settings click on hide magisk manager and put any name then ok ..and wait
Click to expand...
Click to collapse
Great! Works for me! :good:
How to Change SeLinux Mod
I have the same problem.Can't Hide Magisk manager.
I don't know how to change the SeLinux Mod.Can you help me ?
Download app Terminal from play store and follow the previous steps
Hi sir
Same problem the magisk manager hiding package name process is not working evenif the device selinux setted to permissive
How to fix.
dlnraja said:
Hi sir
Same problem the magisk manager hiding package name process is not working evenif the device selinux setted to permissive
How to fix.
Click to expand...
Click to collapse
Did you check whether your Google play protect feature is turned off? That was my issue. Apparently it stops Magisk Manager from repackaging itself. Once in sorted that out, it works! Golden!
Not working in Mi 8 Lite, Android 10, Ver: 20.4
Changing Selinux didn't help for me it was still giving error though i find a way you can disable play protect and try , it worked for me afterwards you can enable it again.
shackled said:
Did you check whether your Google play protect feature is turned off? That was my issue. Apparently it stops Magisk Manager from repackaging itself. Once in sorted that out, it works! Golden!
Click to expand...
Click to collapse
This one works for me
shackled said:
Did you check whether your Google play protect feature is turned off? That was my issue. Apparently it stops Magisk Manager from repackaging itself. Once in sorted that out, it works! Golden!
Click to expand...
Click to collapse
That's it! That point should be included in the basic install procedure.
Thanks
I have changed selinux to permissive , Disabled play protect, but still getting the error. I am using realme 3 pro. Please help.
ExFAT thumb drives do not work on OxygenOS, upon insertion you're asked to reformat the drive.
It turns out that ExFAT support is built in (at least since OOS 9), but a bug in the OOS SELinux policies shipped with the device prevents ExFAT from working.
This module patches the SELinux policy with Magisk and allows ExFAT-formatted drives to work.
It does the equivalent of running this root command:
supolicy --live 'allow fsck_untrusted system_file file { entrypoint }
Tested on:
- OnePlus 8T running OOS 11.0.8.13
- OnePlus 7Pro running OOS 9.5.13