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/

Found a fix for when Magisk Hide settings do not stick on reboot

I'm on a Moto G5 Plus stock systemlessly rooted with custom kernel.
I noticed in the Magisk logs that the app was unable to write to /magisk/.core/hidelist -- That's because the subfolder simply wasn't there. The exact error was pretty obvious in the logs: fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory
So I created a new folder and set the permissions on it to rwxr-xr-x
Now when I set my list of apps to hide, it sticks on reboot.
I'm not sure why it doesn't get created in the first place. Other modules seem to be downloaded and written to /magisk just fine. Oh well. Hope this helps out some other people.

Thanks. Guess this works.

Can you please elaborate?
dunderball said:
I'm on a Moto G5 Plus stock systemlessly rooted with custom kernel.
I noticed in the Magisk logs that the app was unable to write to /magisk/.core/hidelist -- That's because the subfolder simply wasn't there. The exact error was pretty obvious in the logs: fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory
So I created a new folder and set the permissions on it to rwxr-xr-x
Now when I set my list of apps to hide, it sticks on reboot.
I'm not sure why it doesn't get created in the first place. Other modules seem to be downloaded and written to /magisk just fine. Oh well. Hope this helps out some other people.
Click to expand...
Click to collapse
Hi,
Can you please elaborate the steps. Sorry, I'm a noob. Where to create a new folder? How to set the permissions on it? to rwxr-xr-x ?
Thanks.

Clarification: "hidelist" is not a folder but a file (under /sbin/.core/img/.core) containing the apps and processes added to the MagiskHide list. The default permissions for the file is rw-rw-rw (666).
Not sure why a folder worked for the OP...
@sghegde87 If you can't get MagiskHide to work and you see the above mentioned errors, use a root capable file explorer and navigate to /sbin/.core/img/.core (make sure the setting to view hidden files and folders is enabled, or you won't see the .core directories). Create an empty file named hidelist (no extension) and then give it the above mentioned permission (666). In most file explorers you can do this by long-pressing the file and go to "details" or similar. Depends on the file explorer... I always recommend FX File Explorer.

Thanks for the quick response but..
Didgeridoohan said:
Clarification: "hidelist" is not a folder but a file (under /sbin/.core/img/.core) containing the apps and processes added to the MagiskHide list. The default permissions for the file is rw-rw-rw (666).
Not sure why a folder worked for the OP...
@sghegde87 If you can't get MagiskHide to work and you see the above mentioned errors, use a root capable file explorer and navigate to /sbin/.core/img/.core (make sure the setting to view hidden files and folders is enabled, or you won't see the .core directories). Create an empty file named hidelist (no extension) and then give it the above mentioned permission (666). In most file explorers you can do this by long-pressing the file and go to "details" or similar. Depends on the file explorer... I always recommend FX File Explorer.
Click to expand...
Click to collapse
@Didgeridoohan:- Thank you for the quick reply and detailed description. Here is what happened:- There is already a file name 'hidelist' in /sbin/.core/img/.core directory. So, I deleted it and created a new one and set the permission to 666.
I added all the apps that has to be magiskhide. I checked this hidelist file and it is updated accordingly after I tick the apps in Magisk manager.
However, after reboot, again, the apps preference is reset.. All hide settings are reset. Below is the Log file from Magisk after reboot if that helps.
Any idea what might be causing this issue?
Device:- Lenovo P2 with Stock rom_S251 - Rooted via Magisk.
Code:
02-14 15:51:58.289 437 437 I Magisk : Magisk v16.0(1600) daemon started
02-14 15:51:58.298 437 442 I Magisk : ** post-fs mode running
02-14 15:52:01.565 437 682 I Magisk : ** post-fs-data mode running
02-14 21:22:01.571 437 682 I Magisk : * Creating /sbin overlay
02-14 21:22:01.572 437 682 I Magisk : * Mounting mirrors
02-14 21:22:01.573 437 682 I Magisk : mount: /sbin/.core/mirror/system
02-14 21:22:01.573 437 682 I Magisk : link: /sbin/.core/mirror/vendor
02-14 21:22:01.574 437 682 I Magisk : bind_mount: /sbin/.core/mirror/bin
02-14 21:22:01.574 437 682 I Magisk : * Setting up internal busybox
02-14 21:22:01.586 437 682 I Magisk : * Mounting /data/adb/magisk.img
02-14 21:22:01.598 437 682 E Magisk : mount /dev/block/loop0->/sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.598 437 682 E Magisk : umount /sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.608 437 682 I Magisk : Resize /data/adb/magisk.img to -1854921600M
02-14 21:22:01.637 437 682 I Magisk : Create /data/adb/tmp.img with size -1854921600M
02-14 21:22:01.660 437 682 E Magisk : mount /dev/block/loop0->/dev/source failed with 22: Invalid argument
02-14 21:22:01.670 437 682 E Magisk : mount /dev/block/loop1->/sbin/.core/img failed with 22: Invalid argument
02-14 21:22:01.670 437 682 I Magisk : * Running post-fs-data.d scripts
02-14 21:22:01.671 437 682 I Magisk : * Running module post-fs-data scripts
02-14 21:22:01.671 437 682 I Magisk : * Loading modules
02-14 21:22:01.671 437 695 I Magisk : * Starting MagiskHide
02-14 21:22:01.671 437 695 I Magisk : hide_utils: Hiding sensitive props
02-14 21:22:01.671 437 695 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
02-14 21:22:01.671 437 695 I Magisk : hide_list add: [com.google.android.gms.unstable]
02-14 21:22:01.691 437 695 I Magisk : proc_monitor: init ns=mnt:[4026531840]
02-14 21:22:01.813 437 755 I Magisk : ** late_start service mode running
02-14 21:22:01.814 437 755 I Magisk : * Running service.d scripts
02-14 21:22:01.814 437 755 I Magisk : * Running module service scripts
02-14 21:22:03.538 437 695 I Magisk : proc_monitor: zygote ns=mnt:[4026533676] zygote64 ns=mnt:[4026533675]
03-06 12:56:00.383 437 695 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=4625 ns=mnt:[4026533848])
03-06 12:56:24.289 437 695 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=6244 ns=mnt:[4026533862])

sghegde87 said:
@Didgeridoohan:- Thank you for the quick reply and detailed description. Here is what happened:- There is already a file name 'hidelist' in /sbin/.core/img/.core directory. So, I deleted it and created a new one and set the permission to 666.
I added all the apps that has to be magiskhide. I checked this hidelist file and it is updated accordingly after I tick the apps in Magisk manager.
However, after reboot, again, the apps preference is reset.. All hide settings are reset. Below is the Log file from Magisk after reboot if that helps.
Any idea what might be causing this issue?
Device:- Lenovo P2 with Stock rom_S251 - Rooted via Magisk
Click to expand...
Click to collapse
All I can say is that you've got some kind of loop mount issue...
What's the output when you run the mount command in a terminal emulator?

Yes you are right.
Didgeridoohan said:
All I can say is that you've got some kind of loop mount issue...
What's the output when you run the mount command in a terminal emulator?
Click to expand...
Click to collapse
Yep. It's a mount issue. The problem was F2FS data partition. I formatted it to EXT4 and everything is working just fine. Magisk works as expected only on EXT4 format type in Lenovo P2 stock ROM.
Thanks for the comment though!

I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks

hidelist deleted
It's not working on my Nexus 7 2013 deb tablet. Rebooting deletes hidelist. Please help. Thanks

jhford said:
It's not working on my Nexus 7 2013 deb tablet. Rebooting deletes hidelist. Please help. Thanks
Click to expand...
Click to collapse
This workaround was for devices with f2fs issues, in late 2017. Your device don't use f2fs (normally) and much use happened with Magisk since (the hidelist file is no longer used, as an example).
100% sure you've got something else going on (unless you're on a really old Magisk release).

Didgeridoohan said:
This workaround was for devices with f2fs issues, in late 2017. Your device don't use f2fs (normally) and much use happened with Magisk since (the hidelist file is no longer used, as an example).
100% sure you've got something else going on (unless you're on a really old Magisk release).
Click to expand...
Click to collapse
My problem is that the Spectrum TV app will not run on a rooted device. So, I use Magisk Hide, but Safetynet fails on each reboot. So, the temporary fix is to untick Hide in Settings, reboot, retick hide, rerun Safetynet, which always passes, and Spectrum TV app also works. PITA. Do you know of a permanent solution?
Thanks

jhford said:
My problem is that the Spectrum TV app will not run on a rooted device. So, I use Magisk Hide, but Safetynet fails on each reboot. So, the temporary fix is to untick Hide in Settings, reboot, retick hide, rerun Safetynet, which always passes, and Spectrum TV app also works. PITA. Do you know of a permanent solution?
Thanks
Click to expand...
Click to collapse
That just means things aren't working as intended on your device. More info is needed:
https://www.didgeridoohan.com/magisk/MagiskHideHelp

Didgeridoohan said:
That just means things aren't working as intended on your device. More info is needed:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
Click to expand...
Click to collapse
My Magisk log is attached.

jhford said:
My Magisk log is attached.
Click to expand...
Click to collapse
Update. I uninstalled Magisk manager and installed the Canary version, but the problem remains. Neither Safetynet nor Magisk Hide work unless I do the following: disable Magisk Hide, reboot, and enable Magisk Hide. I'm glad it works, at least, but the rebooting is a PITA.

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

[Help] Magisk 18.0 is not working. No Root prompts from rooted apps.

I updated magisk 15.1 to magisk 18.0 but now the root is not detected as there is no prompt dialog in any apps that tries to access root privilege.
I updated using magisk manager 6.1.0(recommended method). Root didn't work.Then I tried uninstalling and flashing from TWRP.Nothing happens.
So I completely uninstalled and rolled back to magisk 15.1.
That works but I want to use a module that requires magisk >15.3 . So I need that update.
When app tries to access root log reports error
Magisk : write failed with 32: Broken pipe
Complete Log:
02-03 23:08:23.891 2032 2032 I Magisk : * Creating /sbin overlay
02-03 23:08:23.957 2034 2034 I Magisk : Magisk v18.0(18000) daemon started
02-03 23:08:23.968 2034 2035 I Magisk : ** post-fs-data mode running
02-03 23:08:23.968 2034 2035 I Magisk : * Initializing Magisk environment
02-03 23:08:24.018 2034 2035 I Magisk : * Mounting mirrors
02-03 23:08:24.020 2034 2035 I Magisk : mount: /sbin/.magisk/mirror/system
02-03 23:08:24.020 2034 2035 I Magisk : link: /sbin/.magisk/mirror/vendor
02-03 23:08:24.020 2034 2035 I Magisk : bind_mount: /sbin/.magisk/mirror/bin
02-03 23:08:24.021 2034 2035 I Magisk : * Setting up internal busybox
02-03 23:08:24.265 2040 2040 I Magisk : Magisk v18.0(18000) logger started
02-03 23:08:24.416 2034 2035 I Magisk : * Mounting /data/adb/magisk.img
02-03 23:08:24.469 2034 2035 I Magisk : * Running post-fs-data.d scripts
02-03 23:08:24.469 2034 2035 I Magisk : * Running module post-fs-data scripts
02-03 23:08:24.469 2034 2035 I Magisk : * Loading modules
02-03 23:08:24.547 2034 2055 I Magisk : * Starting MagiskHide
02-03 23:08:24.547 2034 2055 I Magisk : hide_utils: Hiding sensitive props
02-03 23:08:24.547 2034 2055 I Magisk : hide_list add: [com.google.android.gms.unstable]
02-03 23:08:24.644 2034 2055 I Magisk : hide_list rm: [com.google.android.gms.unstable]
02-03 23:08:24.700 2034 2055 I Magisk : hide_list add: [com.google.android.gms/.droidguard.DroidGuardService]
02-03 23:08:25.421 2034 2222 I Magisk : ** late_start service mode running
02-03 23:08:25.422 2034 2222 I Magisk : * Running service.d scripts
02-03 23:08:25.426 2034 2222 I Magisk : * Running module service scripts
02-03 23:09:13.944 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[5087] ns=[4026533771]
02-03 23:09:45.854 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[6240] ns=[4026533760]
02-03 23:10:09.865 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[8455] ns=[4026533737]
02-03 23:12:59.931 2034 2055 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[12427] ns=[4026533693]
02-03 23:13:10.484 12566 12566 E Magisk : write failed with 32: Broken pipe
02-03 23:13:34.599 12704 12704 E Magisk : write failed with 32: Broken pipe
02-03 23:13:47.188 13294 13294 W Magisk : su: request rejected (10160->0)

try removing magisk from battery optimization in android settings, then rebooting??

all the permission are given also updated to latest one STILL NOT WORKING
miura19882 said:
try removing magisk from battery optimization in android settings, then rebooting??
Click to expand...
Click to collapse
updated magisk manager to 7.0 and magisk to 18.1. Same issue
Also app is put in not optimized list in battery optimization
and in performance optimization app is allowed to run in background, allow the system to wake up and allowed to be awakened by other application.

No idea what your device is, so can't say if this is applicable or not, but make sure that the Manager isn't installed to external/adoptable storage. That has been known to cause quite a few issues...

mine wont work either on pixel 2 xl, coming from 18.0
downloads the apk for 7.0.0, says it needs additional setup and then fails. i flashed 18.1 so that is working, its just the manager thats giving me problems.

fixxxer0 said:
mine wont work either on pixel 2 xl, coming from 18.0
downloads the apk for 7.0.0, says it needs additional setup and then fails. i flashed 18.1 so that is working, its just the manager thats giving me problems.
Click to expand...
Click to collapse
same things happened on my oneplus 6t... after install magisk manager 7.0.0, it need addition setup but setup fails, when flashed 18.1 in magisk, it wrote unable to unpack boot

yathomasi said:
updated magisk manager to 7.0 and magisk to 18.1. Same issue
Also app is put in not optimized list in battery optimization
and in performance optimization app is allowed to run in background, allow the system to wake up and allowed to be awakened by other application.
Click to expand...
Click to collapse
Just make sure there is an exception under power saving in the battery settings

ArlenCheng said:
same things happened on my oneplus 6t... after install magisk manager 7.0.0, it need addition setup but setup fails, when flashed 18.1 in magisk, it wrote unable to unpack boot
Click to expand...
Click to collapse
not sure what happened, but it seems to have fixed itself?
i did remove the old manager, and remove all my modules, and several reboots... cant say exactly which one fixed the problem.

miura19882 said:
Just make sure there is an exception under power saving in the battery settings
Click to expand...
Click to collapse
OMG, IT WORKS! AFTER SETTINGS, IT CAN DIRECT BOOT IMAGE!:fingers-crossed:

yathomasi said:
updated magisk manager to 7.0 and magisk to 18.1. Same issue
Also app is put in not optimized list in battery optimization
and in performance optimization app is allowed to run in background, allow the system to wake up and allowed to be awakened by other application.
Click to expand...
Click to collapse
ArlenCheng said:
OMG, IT WORKS! AFTER SETTINGS, IT CAN DIRECT BOOT IMAGE!:fingers-crossed:
Click to expand...
Click to collapse
Sweet happy it worked out for you

Thank you so much !!! it worked for me too !!!! :highfive::victory::laugh::good:

miura19882 said:
Just make sure there is an exception under power saving in the battery settings
Click to expand...
Click to collapse
I don't find options for power saving and to put the app on exception on battery settings in my phone running Android Nougat

It's only for Oreo

hey fellas check this out:
if you have root but magisk is not prompting, under settings choose to hide magisk manager by repacking it with a random package name.
this fixed for me.

x_berzerker said:
hey fellas check this out:
if you have root but magisk is not prompting, under settings choose to hide magisk manager by repacking it with a random package name.
this fixed for me.
Click to expand...
Click to collapse
Did this, disabled the battery optimisation, rebooted a couple of times; still doesn't work (magisk 19.3, magisk manager 7.3.2, htc desire 820, stock android 6.0.1)

miura19882 said:
try removing magisk from battery optimization in android settings, then rebooting??
Click to expand...
Click to collapse
This worked for me as well!

I know its a bit late but I had the same problem and I fixed it by enabling the "Display pop-up windows while running in the background" option in the app settings.
{
"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"
}

im having the same problem but none of the suggested fixed here have worked. any further suggestions????

DarkAndBlue said:
I know its a bit late but I had the same problem and I fixed it by enabling the "Display pop-up windows while running in the background" option in the app settings.
Click to expand...
Click to collapse
That one fixed it for me on Android 9.

Im on 4.2.2 android
Installed it via patched boot img on adb
Facing same issue
I dont see any battery settings on settings app
Trying to uninstall and install app,just same
Help plz

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.