Database Develop

SafetyNet not passing on Magisk v12 OnePlus3T on 7.1.1

My oxygenOS version is 4.1.6, I installed Magisk with MagiskSU(topjohnwu) today but SafetyNet won't pass. I have MagiskHide enabled.
Any idea why?

Google updated SafetyNet so you're gonna have to use magisk core mode for now to pass safetynet

You can also switch to Magisk 13 which is currently passing for me without issues. I am no longer using any Magisk Modules as having those enabled was causing it to fail.

Or you can switch v13 beta to pass safetynet which is not stable yet

CJ-Wylde said:
You can also switch to Magisk 13 which is currently passing for me without issues. I am no longer using any Magisk Modules as having those enabled was causing it to fail.
Click to expand...
Click to collapse
Same

chazarss said:
Or you can switch v13 beta to pass safetynet which is not stable yet
Click to expand...
Click to collapse
Do I flash the beta directly or must I uninstall Magisk before and then install the beta?
Also, where can I find this beta?

Here is the link
Fredol7 said:
Do I flash the beta directly or must I uninstall Magisk before and then install the beta?
Also, where can I find this beta?
Click to expand...
Click to collapse
You can dirty flash the magisk v13 without uninstall the previous one but don't forget to update magisk manager app to v5.0.2 or the magisk v13 won't work
Here is the link
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

Fredol7 said:
My oxygenOS version is 4.1.6, I installed Magisk with MagiskSU(topjohnwu) today but SafetyNet won't pass. I have MagiskHide enabled.
Any idea why?
Click to expand...
Click to collapse
Enable Magisk core module in only in the magisk settings to pass the safety net check. this is a temporary fix.

The following module works for me: https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Using Magisk v12, with other modules working (not just core mode) and it passes Safetynet.
The Safetynet fix does change the device fingerprint, so I think it will screw up (prevent) OTA updates. But you can simply disable the module when an update rolls out.

redpoint73 said:
The following module works for me: https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Using Magisk v12, with other modules working (not just core mode) and it passes Safetynet.
The Safetynet fix does change the device fingerprint, so I think it will screw up (prevent) OTA updates. But you can simply disable the module when an update rolls out.
Click to expand...
Click to collapse
The actual fix doesn't need the fingerprint change. There's a modified version here that have those prop changing lines commented out.

Can't get Magisk to work on Pixel

I have pixel (sailfish) running lineage 15.1 w/ microG and I've followed the exact steps from the official Magisk install page using Magisk v18.1 with manager 7.0 only to get the same safetynet api error. Ive even tried other suggested installation methods from: https://android.gadgethacks.com/how-to/install-magisk-your-pixel-pixel-xl-0177522/
And it left me in a bootloop whereby I had to wipe and reinstall everything.
Anybody please help!

If you can get Magisk up and running, but get a SafetyNet API error when trying to check SafetyNet in the Manager, the problem lies elsewhere, most likely with your microG setup (or possibly that the Manager snet.apk hasn't downloaded properly, clear data for the Manager to fix that).
Test with a separate SafetyNet checker, and also test MagiskHide by adding a root app to the Hide list (if it can't detect root, MagiskHide works). If you get the same error with the other app we know that the problem likely isn't with Magisk.

Sorry for the newb question, but how do you clear Manager data? Thanks.

conundrew said:
Sorry for the newb question, but how do you clear Manager data? Thanks.
Click to expand...
Click to collapse
By going to the app information in the Android settings.

Still doesn't work. Getting the same message after everything you've suggested.

Even with a separate SafetyNet checker app? In that case it is very likely that it is your microG setup that isn't working. Ask for advice in your ROM thread.

Didgeridoohan said:
If you can get Magisk up and running, but get a SafetyNet API error when trying to check SafetyNet in the Manager, the problem lies elsewhere, most likely with your microG setup (or possibly that the Manager snet.apk hasn't downloaded properly, clear data for the Manager to fix that).
Test with a separate SafetyNet checker, and also test MagiskHide by adding a root app to the Hide list (if it can't detect root, MagiskHide works). If you get the same error with the other app we know that the problem likely isn't with Magisk.
Click to expand...
Click to collapse
Didgeridoohan said:
Even with a separate SafetyNet checker app? In that case it is very likely that it is your microG setup that isn't working. Ask for advice in your ROM thread.
Click to expand...
Click to collapse
Not sure exactly what I did but when I cleared Manager data and changed some microG settings, I was able to finally get SafetyNet Check Success but now it says: ctsProfile: false and basicIntegrity: false. Any advice?

conundrew said:
Not sure exactly what I did but when I cleared Manager data and changed some microG settings, I was able to finally get SafetyNet Check Success but now it says: ctsProfile: false and basicIntegrity: false. Any advice?
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
So I did a clean install of LineageOS 16 only (no microG) and then installed Magisk following installation instructions and when I opened up Magisk Manager I don't see the option to do SafetyNet Check anymore. When I ran SafetyNet Test it said "GooglePlayServices is not available on this device". I was given the impression that microG was the problem which is why I installed LineageOS without microG, but it's still not working. Please help!

If you have neither Gapps or MicroG installed there's no way you can use anything SafetyNet related. It's Google's system, so you're going to have to install one or the other...

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
Didgeridoohan said:
If you have neither Gapps or MicroG installed there's no way you can use anything SafetyNet related. It's Google's system, so you're going to have to install one or the other...
Click to expand...
Click to collapse
Thank you!
Is there any benefit or even necessary to install a custom kernel, like ElementalX, for getting Magisk to work properly? Thanks.

conundrew said:
Thank you!
Is there any benefit or even necessary to install a custom kernel, like ElementalX, for getting Magisk to work properly? Thanks.
Click to expand...
Click to collapse
No.

Device not Certified [SOLVED]

I feel like I am at a loss and i need help,like 2 days ago I reverted back to stock from a custom rom on my pixel 4 xl and google play store keeps saying device not certified, now I have come across this issue before in the past and fixed it with guides posted on the internet but this time they are not working. here is everything I have done:
-registered device as per guides on the internet, cleared play store data and even play services data and rebooted. waited a literal day. rebooted and cleared data of both then rebooted again
- i redownloaded the april image and flashed it to both slots and manually wiped user data in fastboot, tried registering again and waited atleast 10 minutes before trying anything else
- downloaded march image and did everything listed above
- downloaded the android 12 dev beta and did everything listed above.
- tried making safetynet pass with magisk and stuff in between there
- checked safetynet right off the bat on a fresh flash with zero modifications and it failed too.
- as i am posting this i am flashing a fresh download of the april image + platform tools on a different computer and different cable
if anyone has any suggestions please let me know.

Did you flash the Universal SafetyNet Fix module after rooting? If not, try that. Also make sure you enable Magisk Hide in the Manager settings, clear data & cache of Play Store and reboot. Sometimes it takes a while for it to show up as certified.
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

Lughnasadh said:
Did you flash the Universal SafetyNet Fix module after rooting? If not, try that. Also make sure you enable Magisk Hide in the Manager settings, clear data & cache of Play Store and reboot. Sometimes it takes a while for it to show up as certified.
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
i will give that a shot in a little bit here and update

Lughnasadh said:
Did you flash the Universal SafetyNet Fix module after rooting? If not, try that. Also make sure you enable Magisk Hide in the Manager settings, clear data & cache of Play Store and reboot. Sometimes it takes a while for it to show up as certified.
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
Thank you so much that did the trick. I in all honesty did not know that module existed so thank you so very much! <3

Buddyjohn said:
Thank you so much that did the trick. I in all honesty did not know that module existed so thank you so very much! <3
Click to expand...
Click to collapse
No problem. Glad you got it going

Lughnasadh said:
No problem. Glad you got it going
Click to expand...
Click to collapse
I know im kinda late.. But gosh, thank you so much

Question [SOLVED] Anyone with rooted 10s (with or without TWRP) and Google Pay working?

Hi
I succeded in rooting this phone without TWRP following this guide and applied the SafetyNet Fix without success.
I have also a rooted Poco X3 NFC with stock MIUI 12.5 where SafetynetFix is working fine. I have not flashed TWRP on the POCO, but I just use TWRP to boot into recovery, when needed.
Anyone succeded in having the RN 10s rooted with GPay working?
Thanks

no success for me too

Yup google pay is working for me. Make sure safetynet passes. I followed this: Root then install magisk as an app with different name, enabled magisk hide, enable safetynet fix, reboot and then install google pay

abhinavprateek said:
Yup google pay is working for me. Make sure safetynet passes. I followed this: Root then install magisk as an app with different name, enabled magisk hide, enable safetynet fix, reboot and then install google pay
Click to expand...
Click to collapse
Safetynet unfortunately does not pass.
Which version of SafetyNet Fix did you use?
I will check again.
Thanks

This one: https://github.com/kdrag0n/safetynet-fix
You need to install magisk and riru for it to work

abhinavprateek said:
Yup google pay is working for me. Make sure safetynet passes. I followed this: Root then install magisk as an app with different name, enabled magisk hide, enable safetynet fix, reboot and then install google pay
Click to expand...
Click to collapse
When you say "install magisk as an app with different name" you mean that I have to install Magisk normally, then from the Magisk settings, reinstall with different name to hide it from other app.
Is it correct?
Thanks

THANKS @abhinavprateek
Finally it's working!!!
Probably the issue was the correct version of SafetyNet Fix that has to be the Riru one, version 2.1.2 actually (and Riru has to be installed in Magisk previously, as you wrote).
After installing Safetynet fix I cleared all data in those apps:
Google Pay
Play Store
Play Services
and rebooted
Then the safetynet check in Magisk was working ad also Google Pay

Can't get Android 12 + Magisk + SafetyNet, no matter what... All the guides seem outdated

So I'm trying to get Android 12 working with root and SafetyNet passing. I found that all the guides to be wrong or outdated. Problem with the latest Magisk canary is that it does not support MagiskHide. Problem with the latest stable Magisk (v23) is that it doesn't support Android 12. Here are the combinations I've tried:
Canary Magisk APK, Canary Magisk boot image, with Universal SafetyNet Fix v2.2.1 (Zygisk)
Result: No way to test if safety net passes within Magisk, but it doesn't seem to work.
Canary Magisk APK, Stable Magisk v23 boot image, with Universal SafetyNet Fix v2.1.3 (Riru)
Result: Does not work. MagiskHide automatically turns off after every reboot, probably because the canary boot image does not support it.
Stable Magisk v23 APK, Stable Magisk v23 boot image
Result: Device fails to boot. fast food indicates in an invalid signature. presumably happening because stable magisk v23 does not support Android 12.
Based on these test results these are my assumptions:
1. There is no way to run Magisk 23 on Android 12, and this article and its screenshot are fake:
https://www.droidwin.com/how-to-roo...k-on-android-12/#STEP_6_Boot_to_Fastboot_Mode
and this also does not work: https://krispitech.com/how-to-pass-safetynet-on-rooted-android-12/
OR
It was possible and Android 12 September 5th patch level but somehow not the latest December build?
There is no advantage to running mismatched Magisk APK and boot image versions
Both the Zygisk and Riru versions of the SafetyNet Fix do not work on the latest Android 12 builds.
The new DenyList system does nothing in allowing a SafetyNet bypass.
The ONLY working method That can possibly bypass safety net on Android 12 is using either of these 2 Magisk forks:
Custom Magisk by TheHitMan7 (Can’t find download link)
Alpha Magisk by vvb2060 (Can’t find download link)
Are these assumptions correct? Can someone please correct my misunderstandings?

You need Universal Safetynet Fix v2.2.0 or v2.2.1 which was just released 10 days ago.
To be honest, I haven't tried v2.2.1 yet, but I would imagine it will work. I'm on v2.2.0 right now.
Get it from here: https://github.com/kdrag0n/safetynet-fix

I have been using Magisk Canary 23016, USNF 2.2.0, and MagiskHide Props Config 6.1.2 on my Pixel 5 running the December Android 12 release. SafetyNet passes, GPay works.
I have DenyList blocking both GPay and Google Play Store..
Either you have something configured wrong, or you're having a unique issue. Others have been able to pass SafetyNet using a similar configuration.
No, Magisk Stable does not currently support Android 12. You MUST use Canary 23016; none of the previous builds properly handle the vbmeta flags in the boot image header.

I'm using the latest magisk canary, USNF 2.2.1 and no magisk hide props and am passing. I have Zygisk enabled, but that's about it. Install was flawless. Followed V0latyle's thread on going from A11 to A12 when the canary update dropped.

Thank you everyone, I got it working the way you said! I was super close.
-----------------------------------
V0latyle said:
I have been using Magisk Canary 23016, USNF 2.2.0, and MagiskHide Props Config 6.1.2 on my Pixel 5 running the December Android 12 release. SafetyNet passes, GPay works.
I have DenyList blocking both GPay and Google Play Store..
Either you have something configured wrong, or you're having a unique issue. Others have been able to pass SafetyNet using a similar configuration.
No, Magisk Stable does not currently support Android 12. You MUST use Canary 23016; none of the previous builds properly handle the vbmeta flags in the boot image header.
Click to expand...
Click to collapse
I only blocked play services with deny list and it worked.
One of the guides told me to flash stock vbmeta (idk what this is), and this bricked it until I re-flashed the ROM. But I guess that's not needed anymore.

flyoffacliff said:
Thank you everyone, I got it working the way you said! I was super close.
-----------------------------------
I only blocked play services with deny list and it worked.
One of the guides told me to flash stock vbmeta (idk what this is), and this bricked it until I re-flashed the ROM. But I guess that's not needed anymore.
Click to expand...
Click to collapse
Which guide?

V0latyle said:
Which guide?
Click to expand...
Click to collapse
How to Root Pixel Devices via Magisk on Android 12
In this comprehensive tutorial, we will show you detailed steps to root your Pixel device via Magisk running Android 12.
www.droidwin.com
On step 7. It says it's not necessary for some reason on newer devices but pixel 5 and older still require it. What does flashing this file actually do? Like what's the file made of?

flyoffacliff said:
How to Root Pixel Devices via Magisk on Android 12
In this comprehensive tutorial, we will show you detailed steps to root your Pixel device via Magisk running Android 12.
www.droidwin.com
On step 7. It says it's not necessary for some reason on newer devices but pixel 5 and older still require it. What does flashing this file actually do? Like what's the file made of?
Click to expand...
Click to collapse
Nothing needs to be done with vbmeta as long as you're using Magisk 23016.
I'll try to explain what it is and what it does as simply as I can but there isn't really a simple explanation...
Some components of Android system security, such as Verified Boot, incorporate a means by which the data being loaded from critical partitions is checked in real time as it is loaded. This is called "device-mapper verity". The raw data itself is read at the block device level and used to create a hash; this hash is then compared to a reference hash to determine the data has not been modified. The partition that contains this reference hash is vbmeta.
When the Android 12 beta was first released, Magisk had not yet been updated to properly handle Android 12 boot image headers. Verified Boot is disabled for the most part when the bootloader is unlocked; however some elements still remain to ensure you're booting a proper device boot image. Magisk did not preserve necessary information in the boot headers, so the device wouldn't boot; we would get a message in bootloader stating failed to load/verify boot images
We figured out a workaround for this: disable dm-verity and vbmeta verification altogether. This was done by flashing the vbmeta partition with those two options:
Code:
flash vbmeta vbmeta.img --disable-verity --disable-verification
The problem with this is it has some sort of safety interlock that prevents system from loading if verity/verification are disabled and /data isn't clean. So, rooting required wiping data. You probably discovered this during your "brick": you got a screen reading Cannot load Android system. Your data may be corrupt.
We also discovered that the vbmeta workaround had to be performed every time vbmeta was flashed - meaning no OTA updates, because if vbmeta was flashed without the disable options, we wouldn't be able to boot a patched boot image, and even if we re-disabled verity/verification, the device still wouldn't boot unless data was clean. The only way to update AND reroot AND keep data was to ensure that verity and verification were disabled every time the device was updated.
Fortunately, Magisk 23016 fixed all of this. We don't have to mess with vbmeta anymore. Magisk properly preserves the flags in the boot header, meaning that AVB recognizes it as a legitimate boot image, and the device is happy.

has anyone able to pass safety CTSprofile ?
Basic integrity is pass but CTSprofile Check isnt passed...
anybody able to pass in A12 (OnePlus Nord)
tried all effort but dint work, even Universal SafetyNet Fix v2.2.1 (Zygisk) isnt working..
its makes Basic Integrity Fail after Flash ( Universal SafetyNet Fix v2.2.1 (Zygisk).
I roll back to A11 then sadly....

shhahidxda said:
has anyone able to pass safety CTSprofile ?
Basic integrity is pass but CTSprofile Check isnt passed...
anybody able to pass in A12 (OnePlus Nord)
tried all effort but dint work, even Universal SafetyNet Fix v2.2.1 (Zygisk) isnt working..
its makes Basic Integrity Fail after Flash ( Universal SafetyNet Fix v2.2.1 (Zygisk).
I roll back to A11 then sadly....
Click to expand...
Click to collapse
You're doing something wrong. Don't overlook anything. I'm on Android 12.1 and pass safety net, Google pay works, Netflix works.
Have you configured the deny list in magisk?? If not do that then. I'd start fresh, don't connect to anything on first start. Hide everything about those Google apps. Then add your accounts etc etc. This is what worked for me no problem

thatsupnow said:
You're doing something wrong. Don't overlook anything. I'm on Android 12.1 and pass safety net, Google pay works, Netflix works.
Have you configured the deny list in magisk?? If not do that then. I'd start fresh, don't connect to anything on first start. Hide everything about those Google apps. Then add your accounts etc etc. This is what worked for me no problem
Click to expand...
Click to collapse
I would like to know, how you are able to pass? I mean It is passed using Universal safetynet fix by Kdragon?
or without fix?
as you mention in your screenshot that you have put all google services in denylist,
I've already done that..
anything else ? you done it? can you show screenshot of your safetynet pass??

shhahidxda said:
I would like to know, how you are able to pass? I mean It is passed using Universal safetynet fix by Kdragon?
or without fix?
as you mention in your screenshot that you have put all google services in denylist,
I've already done that..
anything else ? you done it? can you show screenshot of your safetynet pass??
Click to expand...
Click to collapse
I'm using the latest safetynet fix v2.2.1 Kdragon

thatsupnow said:
I'm using the latest safetynet fix v2.2.1 Kdragon
Click to expand...
Click to collapse
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal fix..
but as I applied OTA of A12...
I lose safetynet pass.
let me know do you have any workaround?
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
I am still looking for solution to fix this issue..!! if you have any work around.. let me know.. I will do my best.. may be i need to modify device fingerprints with Security patch.? what you say?

shhahidxda said:
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
Click to expand...
Click to collapse
shhahidxda said:
Yes, you are able to pass both .. but i am having issue with OnePlus Nord A12..
On A11 i was able to pass without Universal fix..
but as I applied OTA of A12...
I lose safetynet pass.
let me know do you have any workaround?
I've applied Universal fix by Kdragon.. but before flashing Universal fix of Zygisk I was able to pass Basic Integrity but as soon as I flash Kdragon Universal fix of Zygisk both CTS profile & Basic Integrity gets failed... !!!!
I am still looking for solution to fix this issue..!! if you have any work around.. let me know.. I will do my best.. may be i need to modify device fingerprints with Security patch.? what you say?
Click to expand...
Click to collapse
You do realise that your posting on the pixel 5 forum right?? I'd maybe go checkout what they are doing on the OnePlus side of the tracks

thatsupnow said:
You do realise that your posting on the pixel 5 forum right?? I'd maybe go checkout what they are doing on the OnePlus side of the tracks
Click to expand...
Click to collapse
Yes, I knew i am posting in Pixel 5 and this topic isnt mention on Oneplus section..
I am looking for a solution of this issue.. but nobody has mention it till now.

Android 12.1 + Magisk 25.1 + Zygisk + Google Play services on enforced Denylist > Works charmingly
Note 1: Enforce Denylist for all the Google Play services modules on Magisk.
Note 2: After reboot, clear data of Google Play services and Play Store to make a fresh start.

pseudokawaii said:
Android 12.1 + Magisk 25.1 + Zygisk + Google Play services on enforced Denylist > Works charmingly
Note 1: Enforce Denylist for all the Google Play services modules on Magisk.
Note 2: After reboot, clear data of Google Play services and Play Store to make a fresh start.
Click to expand...
Click to collapse
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?

El3ssar said:
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
Click to expand...
Click to collapse
What do you mean by "it no longer shows there"? Does the Google Play services disappear after putting on denylist? Did you enable the "Enforce Denylist" option? Did you do a retest of SafetyNet after reboot?

El3ssar said:
I have the same running on a Galaxy S10, but every time I put Google Play Services on the enforce Denylist and reboot it no longer shows there. I'm trying to be able to use my banking app, it worked charmingly on magisk 24 but not anymore. Any advice?
Click to expand...
Click to collapse
Yea and it won't stick I've tried that too. You don't need to add Google Play services to the deny list anyway

thatsupnow said:
Yea and it won't stick I've tried that too. You don't need to add Google Play services to the deny list anyway
Click to expand...
Click to collapse
If you're using Universal Safetynet Fix, Play Services is blocked out of the box. I had the same thing happen in one of the newer releases and thought it was an issue. It isn't. Play Services is blocked even though it doesn't show it.