I've been experiencing losing SafetyNet pass with Magisk after the phone has been on for awhile. Has anyone seen this issue before?
I'm on Magisk v14.5 with Magisk Manager v5.4.0, on Android 8.1 (happened on 8.0 too). I already tried flashing a different kernel, but this issues still happens.
SafetyNet passes again after restarting my phone.
Any help will be appreciated. Thanks!
Try updating magisk to 5.4.3 that's the newest one. I'm also on the beta channel you can change it in the setting. And you should be good.
Edit
Link to the newest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I was on the new magisk 5.4.3, and the failure still happens. I only downgraded to 5.4.0 to avoid the dtbo.img failure right now.
I have a OnePlus 5T that passes fully the SafetyNet test, but after a few hours it gives false in ctsProfile and BasicIntegrity, I am with Android 8.1 OxygenOS 5.1.5 (I already tried with 5.1.4 doing a thorough cleanup between rom exchange and also unsuccessful ), I unlocked Bootloader and installed TWRP 3.2.3 Blu spark v9.85, then i flash Root Magisk 17.1 by twrp, Installed from a clean ROM and I've already tried with 17.2 and It's the same thing at the end, I have also tried to install Magisk 16.0 from a clean rom and then upgrade to 17.1 directly via Magisk Manager but it was the same, already activated the Magisk Hide in all necessary applications, I hid the Magisk Manager, I've tried flashing Petnoire's SafetyNet Spoofer and me too changed the device fingerprint by MagiskHide Props Config but nothing solved my initial problem, every time I restart the device it passes on the SafetyNet again but after a few hours it fails again, Now i tried to flash the module Universal SafetyNet Fix v3 beta1(MG v17 fix) by Magisk Manager, but Magisk Manager stopped opening even uninstalling the application and installing other versions, I tried more than once and the installation of this module always presents this problem even flashing by TWRP, and after a few hours too SafetyNet failed, Can inform me the latest version of OxygenOS for OnePlus 5T that passes on SafetyNet without any problem? Even though OxygenOS is perfect for me, I'm willing to change rom in the last case, because the most important thing for me is to go through SafetyNet to use the applications I need.
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
anatoly1983 said:
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Click to expand...
Click to collapse
I tried to do this yesterday but the initial problem persisted, every time I restart the device it passes on the SafetyNet again but after a few hours or minutes it fails again.
yoye_cros said:
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
Click to expand...
Click to collapse
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Mega_Monster_X said:
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Click to expand...
Click to collapse
Honestly, I didn't have found any bug. I tried crDroid but I wasn't really happy, and CNP is for my use very stable without bug. I don't know if Volte or VoWifi is working because I don't use this. Also, it's very easy to install compared to other Pie Roms. I just can advise you to try it.
Try a different play services apk. This was the case with me previously.
Seagorilla2 said:
Try a different play services apk. This was the case with me previously.
Click to expand...
Click to collapse
I've tried this but to no avail
With Magisk 16.0 everything went fine, the problem is the Magisk modules I used that are not compatible, but I'll search here to see if I find the modules I want for Magisk 16.0.
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
floborg said:
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
Click to expand...
Click to collapse
I have not found a solution yet, when I fail on SafetyNet I reboot the device and pass SafetyNet a few times for a short time and sometimes lasts several hours but then fails again , I'm using Magisk 18 in OOS Open Beta 20 Android 9.0
So i sometimes ago i discovered Xposed, it never get updates anymore so it didn't came to Android 10. Luckily some people people succesfully ported it with magisk. I tried TaiChi, and it was all in chinese, so i move to EDXposed YAHFA. After succesfully installing it i wanted to install modules since Xposed have much more modules than magisk and therefore there are more interesting modules. The thing is, EDXposed can't pass the SafetyNet check, with that it would be a long process of uninstalling EDxposed and reinstalling it. Fortunately, there's a enable/disable toggle feature for every module on magisk. The question is, would it be safe to disable EDXposed while an Xposed module is installed?
Thx
My phone keeps soft booting a lot after I flashed custom ROMs.. I tried infinity os and now fresh ROM no frills.. but this sof booting issue persists.. I think this is happening due to some magisk module but the only modules I have are riru core, riru exposed, systemless host, safetynet fix, magiskhide props...
lumpygiraffe said:
My phone keeps soft booting a lot after I flashed custom ROMs.. I tried infinity os and now fresh ROM no frills.. but this sof booting issue persists.. I think this is happening due to some magisk module but the only modules I have are riru core, riru exposed, systemless host, safetynet fix, magiskhide props...
Click to expand...
Click to collapse
Check with all modules disabled. If the issue persists, please check buttons and USB slot (if it's clean and dry). Just to be sure.
x
SafetyNet Attestation fails once the pre-installed Stock ROM got tampered ( e.g. bootloader unlocked, Android rooted, Custom ROM installed, etc.pp ).
xurbh said:
I flashed a custom rom to check its features but when I shifted back to my usual custom rom that I was using before, it was showing "safety net test failed" but before then it successfully passes that every time, now I cannot find apps like NETFLIX on play store and unable to use banking apps. What went wrong? any fix? Also after re-flashing (the usual rom), just after booting into the rom it was showing storage full when I was trying to install some apps ( No apps were installed as it was showing storage full)
Also file manager was only showing SD Card storage.
Now the same is happening with other custom roms too.
Click to expand...
Click to collapse
Do you have magisk ? , You can flash universal safety net magisk module .
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
priyansh94 said:
Do you have magisk ? , You can flash universal safety net magisk module .
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
Regarding the storage, maybe a complete wipe including system followed by new rom will fix it.
<Moderator Note>: Closed at OP's request.