Hello,
I am under OOS 9.0.2 with :
- Standard kernel
- Magisk 18
- 3 Magisk modules : Google Dialer, Digital Wellbeing, Substratum
SafetyNet loops and test never finishes.
If I disable Magisk Hide, test finishes but fails ...
If I add my bank app to MagiskHide, it doesn't launch. Same with Google Pay.
What I have to do to make everything works fine?
Thanks a lot
I have Magisk 18 and no problems.
OK it is due to Google Dialer module.
Mystery solved
Related
I am using corvus 16.7 latest with optumis drunk 11v rooted with magisk 23.0v I installed safteynet universal fix 1.2.0v and did magisk hide installed magisk config prop did all the steps hided google apps everything passed but cts profile is the only thing left any fix?
this worked fine 4 me:
This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders or custom verified boot keys. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021.
Instructions:
1. Make sure Magisk hide is enabled.
2. Download the universal safety net fix from kdrag0n's github repository right here.
3. Install it from Magisk manager.
4. Test if it works, if not then download this version of the module instead.
5. If it works congratulations your device now passes safetynet responses.
Credits
@kdrag0n
Worked for me, thanks!
This version of the safetynet fix only works for Magisk v24+(Zygisk).
If you are on version 23.0 of Magisk this should work. But it requires Riru v24.0.0 or newer installed and Magisk hide enabled.
I've attached my results from a SM-A750FN variant.
Hello people, i have a problem.
I cannot pass safetynet fix. Only CTS profile is with red! i have try almost all methods.
My phone is note 20 ultra. I have android 12, magisk 24. I have install deny list, module safetynet fix 2.2 and still cannot pass cts profiile
Installed Android 12 GM1900_11_H.32
APP Magisk Cannery 25.2 (25200)(33) Installed 831a398b (25206)(D)
TWRP 3.7.0_12-0
Zygisk
Enforce Deny List - Deny list is configured for all google apps
Riru (not enabled, it then allows zygisk to run)
Universal safetynet fix v2.2.1
MagiskHide Props Config v6.2-v137
I cannot hide the Magisk app it creates a new app name but it won't load and magisk is still there and of course, google Wallet won't run
everything else is ok rooted and running.
Is anybody with experience of this problem and any solution? would appreciate feedback
p.s. SafetyNet 'attest' returns "Response signature validation error" other SafetyNet tests run OK.
Aussiewaterdragon said:
Installed Android 12 GM1900_11_H.32
APP Magisk Cannery 25.2 (25200)(33) Installed 831a398b (25206)(D)
TWRP 3.7.0_12-0
Zygisk
Enforce Deny List - Deny list is configured for all google apps
Riru (not enabled, it then allows zygisk to run)
Universal safetynet fix v2.2.1
MagiskHide Props Config v6.2-v137
I cannot hide the Magisk app it creates a new app name but it won't load and magisk is still there and of course, google Wallet won't run
everything else is ok rooted and running.
Is anybody with experience of this problem and any solution? would appreciate feedback
p.s. SafetyNet 'attest' returns "Response signature validation error" other SafetyNet tests run OK.
Click to expand...
Click to collapse
I am facing the same issue.
Android 12 GM1900_11_H.36
Magisk 25.2 (25200)(33)
Package ifk.peqffjnp
Universal SafetyNet Fix 2.2.1 by kdrag0n
The SafetyNet test is passed.
However, I can't pay...
A new version of Safety Net fix mod has been uploaded to GitHub today, and it finally works for me! I've tried everything before and gave up months ago.
Maybe not necessary, but I did the following:
- I turned off Zygisk and rebooted.
- Flashed the Safety Net fix in Magisk and rebooted.
- Turned on Zygisk and rebooted again. It did the trick!
Thanks to Displax for the Mod!
Release v2.4.0-MOD_1.3 · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Release v2.4.0-MOD_1.3 · Displax/safetynet-fix
github.com
Does this work with Gpay? I've been using Safetynet fix v2.3.1-MOD_3.0 for awhile now in order for GPay to work.. The earlier releases of v2.4.0 didn't seem to work with GPay.