SafetyNet Suddenly Fails - Android Q&A, Help & Troubleshooting

Hi all, I noticed today that safetynet is suddenly failing. I don't think I made any changes to the system today that would have an affect on SafetyNet. I was playing around yesterday with an exposed module and while doing so, was switching between xposed frameworks to compare them (Edxposed was NOT one of them, because that always trips SN for me).
So I am wondering...did Google make any recent changes to SN that would affect the CTS profile passing?
Is it possible that the experimenting with different xposed frameworks changed the system in such a way that the only way to get SN back is to start from scratch?
Thanks for any insights you might have.

---

Yes, SafetyNet API got changed: it no longer looks for a phone's CTS profile locally stored on phone but externally stored on Google server - uploaded there by phone's manufacturer.
{
"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"
}

---

The cat-and-mouse game has ended.

---

jwoegerbauer said:
Yes, SafetyNet API got changed: it no longer looks for a phone's CTS profile locally stored on phone but externally stored on Google server - uploaded there by phone's manufacturer.
Click to expand...
Click to collapse
Where did you get this info from?
Pls send link

---

devaponnadsm said:
Where did you get this info from?
Pls send link
Click to expand...
Click to collapse
SafetyNet Attestation API | Android Developers
The SafetyNet Attestation API provides services for determining whether a device running your app satisfies Android compatibility tests.
developer.android.com

---

jwoegerbauer said:
The cat-and-mouse game has ended.
Click to expand...
Click to collapse
People have said that before.....i said just two days ago that if google suddenly finds a way to bypass magiskhide for good, then i'd be inclined to blame topjohnwu.
Is there absolutely no way around this?

---

Magisk no longer can't prevent this, because it can't intercept this server-side query.
Take note that the developer of Magisk has already adnitted that!
MagiskHide became obsolete.

---

jwoegerbauer said:
Magisk no longer can't prevent this, because it can't intercept this server-side query.
Take note that the developer of Magisk has already adnitted that!
MagiskHide became obsolete.
Click to expand...
Click to collapse
And all this happened yesterday?

---

Depends on when Google Play Services Framework got updated on your phone: SafetyNet is integral part of Google Play Services Framework.

---

OK. I set up the XPrivacyLua with the assistance of this youtube video.
I only watched the video once and set it up using the google play store app. but after reading your response, I set it up using the "google play services" process, and now my phone passes safetynet again.
Hope this helps someone.

---

gfrank227 said:
OK. I set up the XPrivacyLua with the assistance of this youtube video.
I only watched the video once and set it up using the google play store app. but after reading your response, I set it up using the "google play services" process, and now my phone passes safetynet again.
Hope this helps someone.
Click to expand...
Click to collapse
Its work for me is poco x3 pro , thanks

---

Hi @gfrank227 et all.
My Safetynet was working due to the instructions in the video you posted above. This could be a classic case of 'If it ain't broke don't try and fix it'.
I got a Magisk update message, and 'perhaps stupidly' I installed it in Magisk. I then lost my 'Check SafetyNet' option in the main screen of Magisk, and in Magisk Settings I lost the 'MagiskHide' option.
I also got a message to update LSposed, so I downloaded the zip, and decided to re-follow the youtube video above again this time installing the new LSposed zip.
Nothing's changed, I still have those missing options in Magisk, and also now in Google Play Store my device is now showing as 'Not Certified'.
SafetyNet Test App states 'Failed'.
However, LSposed & XPrivacyLua are actually set up correctly as per the youtube video.
Not sure how to proceed to fix this. Could really do with my Google Pay back.

---

jaccydan said:
Hi @gfrank227 et all.
My Safetynet was working due to the instructions in the video you posted above. This could be a classic case of 'If it ain't broke don't try and fix it'.
I got a Magisk update message, and 'perhaps stupidly' I installed it in Magisk. I then lost my 'Check SafetyNet' option in the main screen of Magisk, and in Magisk Settings I lost the 'MagiskHide' option.
I also got a message to update LSposed, so I downloaded the zip, and decided to re-follow the youtube video above again this time installing the new LSposed zip.
Nothing's changed, I still have those missing options in Magisk, and also now in Google Play Store my device is now showing as 'Not Certified'.
SafetyNet Test App states 'Failed'.
However, LSposed & XPrivacyLua are actually set up correctly as per the youtube video.
Not sure how to proceed to fix this. Could really do with my Google Pay back.
Click to expand...
Click to collapse
You must have installed the latest magisk canary. Have you tried the magisk module universal safety net fix?

---

Thanks for the reply, sorry it took so long to get back to you - (for some reason I didn't get an email notification, but never mind).
Anyway, yes I was looking at those very 2 things. I actually went into Magisk and 'installed from storage' the latest safety net fix, but nothing's changed.
With Canary, I have gone into the Magisk App tab in settings, and clicked on 'Update Channel', then clicked on Canary, but nothing happens. What am I doing wrong here?
I think this Canary build thing could be the answer.
I am also unsure if I need to download a latest canary apk and install it via Odin or something. Not sure how to proceed.
Thanks in advance.
Here's my Magisk Home Screen:
Some additional information:

---

Also install magiskhide props config. they added some props to the default module that magisk is removing.
If this also doesn't work, then go back to 23.0 and don't update until someone fully replaces magiskhide with an working module.

---

jaccydan said:
Thanks for the reply, sorry it took so long to get back to you - (for some reason I didn't get an email notification, but never mind).
Anyway, yes I was looking at those very 2 things. I actually went into Magisk and 'installed from storage' the latest safety net fix, but nothing's changed.
With Canary, I have gone into the Magisk App tab in settings, and clicked on 'Update Channel', then clicked on Canary, but nothing happens. What am I doing wrong here?
I think this Canary build thing could be the answer.
I am also unsure if I need to download a latest canary apk and install it via Odin or something. Not sure how to proceed.
Thanks in advance.
Here's my Magisk Home Screen:
View attachment 5441241
Some additional information:
View attachment 5441249
Click to expand...
Click to collapse
Also install magiskhide props config. they added some props to the default module that magisk is removing.
If this also doesn't work, then go back to 23.0 and don't update until someone fully replaces magiskhide with an working module.

---

gfrank227 said:
Also install magiskhide props config. they added some props to the default module that magisk is removing.
If this also doesn't work, then go back to 23.0 and don't update until someone fully replaces magiskhide with an working module.
Click to expand...
Click to collapse
This might sound stupid but when I go into modules there seems to be no way now of searching for modules online through Magisk - it only seems to be an option to install from storage, so I can see if I need to update magiskhide props config.
Btw, I already have a version of magiskhide props config activated, so I probably don't need to do anything with that.
This page states ( I think) that yesterday this v.23.0 build of Magisk has been updated with a new Canary build:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I think therefore I need to install this Magisk version and then activate Canary in it.
I'm a newbie, so if you could advise me which method to install this, it would be much appreciated. Am i going back to Twrp or Odin or can I do it more easily via the Magisk app? I came across this page explaining various installation methods, but I'm not sure which one to follow in my circumstance:
Installation
The Magic Mask for Android
topjohnwu.github.io
Thanks.

---

jaccydan said:
This might sound stupid but when I go into modules there seems to be no way now of searching for modules online through Magisk - it only seems to be an option to install from storage, so I can see if I need to update magiskhide props config.
Btw, I already have a version of magiskhide props config activated, so I probably don't need to do anything with that.
This page states ( I think) that yesterday this v.23.0 build of Magisk has been updated with a new Canary build:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I think therefore I need to install this Magisk version and then activate Canary in it.
I'm a newbie, so if you could advise me which method to install this, it would be much appreciated. Am i going back to Twrp or Odin or can I do it more easily via the Magisk app? I came across this page explaining various installation methods, but I'm not sure which one to follow in my circumstance:
Installation
The Magic Mask for Android
topjohnwu.github.io
Thanks.
Click to expand...
Click to collapse
Yeah, so it's not stupid. You're right. Topjohnwu, the developer of magisk recently joined the Google security team. As a result, magisk development was put on hold pending approval. Due to conflicts of interest, it was determined that he would not be creating software intended to get around Google's security checks. This is the reason why Magiskhide is gone in the newest canary build.
The other change he made was to remove the built-in modules. You will have to therefore download the zip file for magiskhide props config from github. The props in magiskhide props config were only added in the past couple of months. so you should make sure you are downloading the latest version, or at least the one right before the latest.
If you have both modules I reference and are still failing, then this is because these modules were not intended to fully replace magiskhide. I am confident that eventually they will be able to fully replace it; but until then, you should simply uninstall the magisk manager and then install the apk from the github site that you reference above. That's the correct latest stable version. Then, forget about the canary version.
After the canary version goes as a full update, I recommend that you don't update magisk right away but wait until there's a suitable replacement module that works.
Additionally, if you patched boot.img with the latest canary version, simply repatch using the magisk app after replacing the manager. In theory, you should then have magiskhide back and pass safety-net.
Eventually, of course, google will find a way to bypass this so eventually, we will certainly need to hope for a fix. But this is the best solution for the short term.

---

If you look at the change-log from the three or four most recent releases, you'll be able to see if magiskhide props config you are running has the magiskhide props.
GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com

---

gfrank227 said:
simply repatch using the magisk app
Click to expand...
Click to collapse
Thanks for that info @gfrank227 that is very helpful.
When you said the above (see quote), do I need to rename that Magisk .apk to .img before using Magisk Install to 'Select and Patch a File' from out of my downloads folder?
It's the 2nd part of your reply that I'm stuck on:
"Additionally, if you patched boot.img with the latest canary version, simply repatch using the magisk app after replacing the manager."
Can you run me through this process, I'm not familiar with patching images?