Database Develop

SafetyNet - Do I need to? What for?

Hey Guys,
what is SafetyNet for? And does my MagiskHide doesnt work, cause I dont pass the SafetyNet-Check properly.
My Rooted-Satus is confirmed and I checked all Trouble-Shooting-Tips for passing SafetyNet-Check. No difference after Update Magisk to v14.0.
I have an Honor 8 FRD-L09 on B389 and Android 7.0. Maybe someone can help me. That would be awesome!
My log-file before Update:
Code:
--------- beginning of main
I( 339: 339) Magisk v13.6(1360) daemon started
I( 339: 342) ** post-fs mode running
I( 339: 519) ** post-fs-data mode running
I( 339: 519) * Mounting mirrors
I( 339: 519) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system
I( 339: 519) mount: /dev/block/bootdevice/by-name/vendor -> /dev/magisk/mirror/vendor
I( 339: 519) * Mounting /data/magisk.img
I( 339: 519) * Running post-fs-data.d scripts
I( 339: 519) * Running module post-fs-data scripts
I( 339: 519) * Loading modules
I( 339: 534) * Starting MagiskHide
I( 339: 534) hide_utils: Hiding sensitive props
I( 339: 534) hide_list add: [com.google.android.gms.unstable]
I( 339: 534) proc_monitor: init ns=mnt:[4026531840]
I( 339: 569) ** late_start service mode running
I( 339: 569) * Running service.d scripts
I( 339: 569) * Running module service scripts
I( 339: 534) proc_monitor: zygote ns=mnt:[4026532963] zygote64 ns=mnt:[4026532955]

Safetynet is Google's "root detection system" that blocks the ability to use certain apps if it detects you have root access. It is incorporated into apps like Android Pay, Mario Run by Nintendo, Pokemon Go, a few banking apps, etc.

paed808 said:
Safetynet is Google's "root detection system" that blocks the ability to use certain apps if it detects you have root access. It is incorporated into apps like Android Pay, Mario Run by Nintendo, Pokemon Go, a few banking apps, etc.
Click to expand...
Click to collapse
So I have to pass thatcheck to use MaskHide. I have some banking apps, that doesnt work with my root. Even woithout root just unlocked bootloader they dont work.

Yes, you need to pass safetynet. You could try this module. "Universal Safetynet Fix". Maybe it'll help.
Also, don't install xposed if you want to pass safetynet.

paed808 said:
Yes, you need to pass safetynet. You could try this module. "Universal Safetynet Fix". Maybe it'll help.
Also, don't install xposed if you want to pass safetynet.
Click to expand...
Click to collapse
Universal Safetynet Fix didnt work. And I dont have installed xposed. That sucks.

Blenderhead69 said:
Universal Safetynet Fix didnt work. And I dont have installed xposed. That sucks.
Click to expand...
Click to collapse
Use beta version, stable is oudated
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431

used that one. didnt work.

SchweGELBin said:
If in Safety Net stands like me:
basicIntegrity Passed
ctsProfile Failed
evalrype basic
Check this post.
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
Download Zip (Direct dowoad)
Add Zip as module in Magisk
Reboot
Finish
Maybe another thing is, if u fail is EdXposed.
There just download the Canary Version in the App.
Click to expand...
Click to collapse
Or better yet, how about visiting the actual XDA thread instead of websites that just try to generate traffic off of other peoples work:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/

Problem with Module Install & sometimes lost Root @galaxy s7 on 6.0.1

Hi.
I have several problems with magisk. until yesterday worked all fine (except occasional rubberbanding in Pokemon & sometimes lost Root) - there my mobile shutdown and stopped at reboot with error Message: CUSTOM BINARY LOCKED BY FRP.
So i read a lot of solutions in www but nothing realy works for me.
The only way i can do to unlock was a fullwipe inkl all database lost forever.*
Now i 'repaired' my mobile since yesterday 10am -> install all my apks and Backups and make a backup in SamsungCloud and to my Laptop.
Then i tried to get my systemless root back.
1. Flash twrp 3.1.1.0 Image*
2. Boot in Recovery and install magisk 5.4
3. Boot in regular System and install Modul magisk14.0 via magisk and reboot.
4. After rebooting i feel that my mobile is a little bit lazy/laggy/slow or whatever but it works (i think)
5. Now i want install some extra-module: App_Systemizer-14.0.0, TheSoundMod_S7_Dual_Lv3_6.0.1-v18_Systemless, Enable_Doze_for_GMS_Magisk_Module-v5, App_Systemizer-14.00, VoEnabler-v1.1.
6. Then i get a Log after install Busybox:
Magisk-Log:
*Magisk v14.0(1400) daemon started
*Magisk* : ** post-fs mode running
*Magisk* : ** post-fs-data mode running
*Magisk* : * Mounting mirrors
*Magisk* : mount: /dev/block/platform/155a0000.ufs/by-name/SYSTEM -> /dev/magisk/mirror/system
*Magisk* : link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
Magisk* : bind_mount: /dev/magisk/mirror/bin
*Magisk* : Upgrade module: busybox-ndk
*Magisk* : * Mounting /data/magisk.img
*Magisk* : * Running post-fs-data.d scripts
*Magisk* : * Running module post-fs-data scripts
*Magisk* : * Loading modules
*Magisk* : busybox-ndk: constructing magic mount structure
*Magisk* : bind_mount: /system/xbin
*Magisk* : bind_mount: /system/xbin/busybox
*: bind_mount: /system/xbin/cpustats
*Magisk* : bind_mount: /system/xbin/dexdump
*Magisk* : bind_mount: /system/xbin/jack_connect
*Magisk* : bind_mount: /system/xbin/jack_disconnect
*Magisk* : bind_mount: /system/xbin/jack_lsp
*Magisk* : bind_mount: /system/xbin/jack_showtime Magisk* : bind_mount: /system/xbin/jack_simple_client
*Magisk* : bind_mount: /system/xbin/jack_transport
Magisk* : ** late_start service mode running
*Magisk* : * Running service.d scripts
*Magisk* : * Running module service scripts
*Magisk* : Create /data/magisk_merge.img with size 64M
*Magisk* : * Starting MagiskHide
*Magisk* : hide_utils: Hiding sensitive props
*Magisk* : hide_list: [com.google.android.gms.unstable]
*Magisk* : proc_monitor: init ns=mnt:[4026531840]
*Magisk* : proc_monitor: zygote ns=mnt:[4026535658] zygote64 ns=mnt:[4026535657]
One Modul tell me i have to reboot for working. I reboot sometimes but tell me again and again i have to reboot.
And if i try to install any other Module i get the Message that i cant install via recovery, only in Magisk.
That confused me because i tried to install with magisk and not at recovery..
It mount the merge.img and then stops and tell me that merge.img not been mountet.
So now i need some help for any solutions because i need the App_Systemizer.
My System is Android 6.0.1 without any upgrades on a Samsung Galaxy S7 flat.
I hope anybody knows what there happend and what i have to do for fixing this...
Greetz...
:

Nobody who can help ??

I don't quite follow your installation steps, number 2 and 3... You install the Manager in TWRP and then Magisk v14.0 after booting up?
Sounds like something's fishy with your installation though... I'd flash the uninstaller script in TWRP, reboot to make sure everything works, boot back to TWRP and flash the Magisk installation zip (give the v14.3 beta a try). That should be all you need...

Yeah i See it - i wrote it wrong - i install sure the zip first via twrp and then after that i install the apk file ....
I tried to uninstall several times but there always files in the root partition that not delete via Uninstaller so i delete then with Flash a clean stockrom and reinstall magisk- now i have root again but I cant install the modules !
Magisk teils that Modul install after next boot but nothing installs.
And some other Module that working fine until last week wont install - they ever breaks installing with : */data/magisk_merge.img could not mount to */dev/
Then the script stops...

Test a Step backward.... 5.0/13.1
Hi... today i tried again - i first make complete clean install and then i used the magisk 13.1 Version with 5.0 Manager.
After finished i am install some module - now the most installed without an error_message... (look the attachment) but they wont Start.
After every boot there the same Message that this module Start after the next boot ...
Then I try the actualized Manager 5.4 but there still the same Message!
With magisk 14 are some installers bring back the error_message that magisk can't mount the magisk_merge.img to */dev .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I test to extract the modules and push by Explorer to magisk but get the same effect.
All other functions from Magisk working perfekt only the install of modules are incompatible for me and I dont know what i can do ...

Headache and wasted time - now it is repaired...
Since 4 hours my mobile is repaired!
I had a lot of random shutdowns following by bootloops.. that wasted a lot of time and that makes me really pissed off about my mobile !!
Then i read some hours in xda and found the TGP Kernel for my mobile - it have SU + Busybox + Magisk + a lot of Tweaks!
And is easier or timesaver (fully automatic) to install as the other crapshi.. i had before...
And all the plugins ich need are 100% compatible and I get no more bug- & break- messages!!
But this is interessting -> it is the same Magisk that i used - the Developers from TGP KERNEL do something different on install!
Direct at the first try to install all works fine ! No bugmesssges and no mountingerrors.
That was lucky for me after so long headache!!
@all Samsung Galaxy S7 / S7edge &<+ Users : Take a look to TGP KERNEL - ALL WE NEED IS IN THERE !!
Greetz !!
Link to TGP KERNEL : https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897

Magisk 17.1 Stable not detecting Google Play Services

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

Hide Magisk Failed. Or am I failing magisk somehow :/

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.

Why my Magisk Hide does not save selection in Magisk Hide specific app list

Hello,
it seems like my Magisk Hide option for some reason cannot be saved, if I enable Magisk Hide and go to custom Magisk Hide app list if I select an app and refresh, the app is unselected again. Also, it seems like the Magisk Hide option in the settings menu is also not being saved. I am using Magisk 19.1 and Magisk Manager 7.1.2 because with those versions I have been the most succesful, newest version does not even show Magisk Hide specific app list menu option. Android version is 5.0.1 and I am using Samsung Galaxy S4.
What could be wrong here? I can provide any additional information needed.

That was a bug a while back, but it's since been fixed. Likely after v19.1/v7.1.2 from the sound it it. Nothing to do unless you update...

Didgeridoohan said:
That was a bug a while back, but it's since been fixed. Likely after v19.1/v7.1.2 from the sound it it. Nothing to do unless you update...
Click to expand...
Click to collapse
Thanks so much I've been looking for answer for 2 full days I hope this works!

I have installed v20.0, but now when I select Magisk Hide it does not even show Magisk Hide menu option to select specific apps. What could be the problem?

No need to open another thread... We can continue the discussion here.
If you post your Magisk log it might be easier to help.

Didgeridoohan said:
If you post your Magisk log it might be easier to help.
Click to expand...
Click to collapse
How to get Magisk log?

Here is the log:
--------- beginning of system
--------- beginning of main
I/Magisk ( 280): Magisk v20.0(20000) daemon started
I/Magisk ( 280): * Device API level: 21
I/Magisk ( 280): ** post-fs-data mode running
I/Magisk ( 280): * Initializing Magisk environment
I/Magisk ( 280): * Mounting mirrors
I/Magisk ( 280): mount: /sbin/.magisk/mirror/system
I/Magisk ( 280): mount: /sbin/.magisk/mirror/data
I/Magisk ( 280): link: /sbin/.magisk/mirror/vendor
I/Magisk ( 280): * Setting up internal busybox
I/Magisk ( 280): * Running post-fs-data.d scripts
I/Magisk ( 280): ** late_start service mode running
I/Magisk ( 280): * Running service.d scripts
I/Magisk ( 280): ** boot_complete triggered

If you could install the current Canary debug build and provide that log it would be great. First, there's really no support for old releases and the Canary debug logs are much more verbose.
Canary builds can be found here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

I am using Canary build now, but when I go to logs, it says that the log is empty.