Database Develop

Snapchat won't sign in, how to fix?

Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks

JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
The reason I'm having this issue is because Snapchat randomly signed me out today and my restore point in titanium backup was too old

I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.

JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
vonDubenshire said:
I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.
Click to expand...
Click to collapse
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it

JayTheKid said:
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it
Click to expand...
Click to collapse
The phone permissions allows the app to see the phone's IMEI code. I think maybe that detected you are on a rooted phone using that information.

How to use Snapchat with magisk (After Ban)
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX

No such item in xbin
I tried that too but i dont find any item such as busybox my Snapchat account can't be locked because its has been open in different phones
So give a solution what should i do i uninstall edxposed tried everything root switch root clock hut none of them really works its say oh on your temporarily login fails please try again later help needed seriously its been days
Running
Magisk 20.4 stable
Ed xposed 0.4.5.6 justins forks snadhook
Android 10

What is the go-to replacement for MagiskHide & the central module repo?

I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!

KaoDome said:
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
Click to expand...
Click to collapse
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Here. First 5 post and you should know all you need

So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?

Quantumrabbit said:
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Click to expand...
Click to collapse
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
Click to expand...
Click to collapse

Porpet said:
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
Click to expand...
Click to collapse
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you

Quantumrabbit said:
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Click to expand...
Click to collapse
And where did you find the deny list?

fusk said:
And where did you find the deny list?
Click to expand...
Click to collapse
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist

H
toolhas4degrees said:
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
Click to expand...
Click to collapse
How to add modules shamiko & how to more hide features

Spartacus500 said:
H
How to add modules shamiko & how to more hide features
Click to expand...
Click to collapse
Shamiko is a flashable only need to slash magisk module. You can find it in the magisk alpha thread on telegram. You need to configure denylist first and reboot then turn off the enforce denylist toggle and flash the shamiko module.
If you are using lsposed download hide my applist xposed module and search how to use it if you want more coverage
Pm me if you want links

I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.

Drakinite said:
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
This is quite weird and definitely shows how different devices handle root detection. I a Samsung S10+ and just installed Magisk 24 with enforce DenyList earlier this week. Today I just installed Duo Mobile and it works fine. I do not have it in the DenyList, and Magisk is not hidden. I use a custom SafetyNet fix that was installed when I originally installed an AIO TWRP/Magisk/SafetyNet fix after unlocking my bootloader. I also fail SafetyNet checks.
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?

Drakinite said:
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.

danbest82 said:
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Click to expand...
Click to collapse
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
anonymous-bot said:
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
Click to expand...
Click to collapse
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.

Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
Get VD Infos and use it to scan your files. You can find it on XDA.

Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
Click to expand...
Click to collapse
Hmm ok. Like I said shimako didn't work for me either. I'm not sure why Duo is still detecting root. For reference this is what is on my DenyList:
Drakinite said:
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
YASNAC is the replacement for Momo it looks like since Momo is Riru based (https://github.com/canyie/Riru-MomoHider)

simplydat said:
Get VD Infos and use use to scan your files. You can find it in XDA
Click to expand...
Click to collapse
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?

Drakinite said:
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Click to expand...
Click to collapse
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.

Drakinite said:
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Click to expand...
Click to collapse
Awesome. Hope it stays that way!

Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!

antivirtel said:
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
Click to expand...
Click to collapse
Version 24102 would be v24.102. So your Magisk 24.300 is newer.

How to hide my custom rom or simulate the stock rom for bank apps?

Well, a month ago I installed ArrowOS12 in my A30, but something I don't knew about custom roms is bank apps blocking cuz'... "SECURITY" (funny AF), At first it just was blocked cuz' i have magisk root, but i activated many things to hide magisk and I realize that was not my root, but the custom OS.
I can't use my UNIQUE bank account by a STUPID SECURITY POLICY, How i solve this? I tried magiskhide props config for change my fingerprint prop or whatever.
If i can emulate a fake device in my own device only for this i will, ciz that's anoying

Hi, try download this two magisk modules
Shmaiko - Direct Link | Link
Universal SafetyFix - Direct Link | Link
Hide you Magisk APP in Magisk Settings and Turn On ZYGISK install this two modules.
Open Magisk Settings and in Enforce Settings Apps, mark your Bank Apps.
It worked for me (Galaxy A40)

I already tried both, didn't worked

AysllanHiro said:
I already tried both, didn't worked
Click to expand...
Click to collapse
Pass safety before

SirKosichka said:
Pass safety before
Click to expand...
Click to collapse
i found a way to pass the app checker, but thx for your help, i already passed safetynet too

TELL US HOW!

AysllanHiro said:
i found a way to pass the app checker, but thx for your help, i already passed safetynet too
Click to expand...
Click to collapse
How?

acerfreak said:
TELL US HOW!
Click to expand...
Click to collapse
I think people are good asking questions but not sharing the solution when they get it.

for me it was:
downloading "Universal SafetyFix" (and reboot)
hidding Magisk with MagiskHide in Magisk settings
Enable Zygisk, enable"Enforce DenyList" (again in Magisk settings) and selecting banking app in it (don't forget to reboot).
Also check if you passed SafetyNet with app like YASNAC for example. And clear storage, cache of banking app.
This was working on my phone with original google services like gapps (custom ROM of course).
On my secondary phone with MicroG implementation it's not working (play store required and something more i guess).

darukutsu said:
On my secondary phone with MicroG implementation it's not working (play store required and something more i guess).
Click to expand...
Click to collapse
Were you passing safetynet on it?

ShaDisNX255 said:
Were you passing safetynet on it?
Click to expand...
Click to collapse
Of course there's the problem...I had microG installed with fakestore (passing safetynet) but I had to install playstore (to install bank app from it) and now i'm not passing safetynet even with magisk module installed.

Question MEETS_DEVICE_INTEGRITY fails after Feb update

For anybody with unlocked bootloaders and root no longer passing the usual 2 out of 3 Play Integrity checks, maybe this helps.
After flashing yesterday's TQ1A.230205.002 update, MEETS_DEVICE_INTEGRITY consistently failed which was something new. Sometimes it would pass after repeated attempts and/or clearing the app's storage, but mostly it failed. Long story short, it's now passing after 1) switching from safetynet-fix 2.40 back to Displax's modified 2.3.1; and 2) uninstalled and reinstalled the Integrity Check app. Either one, the other or both seems to have helped. Occasionally I'll get a fail but it's mostly passing now instead of the other way around.

manjaroid said:
For anybody with unlocked bootloaders and root no longer passing the usual 2 out of 3 Play Integrity checks, maybe this helps.
After flashing yesterday's TQ1A.230205.002 update, MEETS_DEVICE_INTEGRITY consistently failed which was something new. Sometimes it would pass after repeated attempts and/or clearing the app's storage, but mostly it failed. Long story short, it's now passing after 1) switching from safetynet-fix 2.40 back to Displax's modified 2.3.1; and 2) uninstalled and reinstalled the Integrity Check app. Either one, the other or both seems to have helped. Occasionally I'll get a fail but it's mostly passing now instead of the other way around.
Click to expand...
Click to collapse
Yeah, a lot of people are having issues with USNF 2.4.0.

manjaroid said:
For anybody with unlocked bootloaders and root no longer passing the usual 2 out of 3 Play Integrity checks, maybe this helps.
After flashing yesterday's TQ1A.230205.002 update, MEETS_DEVICE_INTEGRITY consistently failed which was something new. Sometimes it would pass after repeated attempts and/or clearing the app's storage, but mostly it failed. Long story short, it's now passing after 1) switching from safetynet-fix 2.40 back to Displax's modified 2.3.1; and 2) uninstalled and reinstalled the Integrity Check app. Either one, the other or both seems to have helped. Occasionally I'll get a fail but it's mostly passing now instead of the other way around.
Click to expand...
Click to collapse
Hi,
may I ask exactly which version you went back to:
- v2.3.1-MOD_2.1
- v2.3.1-MOD_2.0 or
- v2.3.1-MOD
Greetings

jofa news said:
Hi,
may I ask exactly which version you went back to:
- v2.3.1-MOD_2.1
- v2.3.1-MOD_2.0 or
- v2.3.1-MOD
Greetings
Click to expand...
Click to collapse
I went back to 2.3.1-MOD_2.0 since it was already on the phone. I didn't even know about MOD_2.1 until you mentioned it, so that's what I'll do next. I didn't know about 2.4.0 problems either. I guess I need to get out more often, subscribe to an extra forum or two.

i had the same proplem
buy aftel clear data and cash memory about 3 times for google service and google play store and last google wallet , evrey think get bake norml

manjaroid said:
I went back to 2.3.1-MOD_2.0 since it was already on the phone. I didn't even know about MOD_2.1 until you mentioned it, so that's what I'll do next. I didn't know about 2.4.0 problems either. I guess I need to get out more often, subscribe to an extra forum or two.
Click to expand...
Click to collapse
I have read about the problems with USNF 2.4 here
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0

salamdiab said:
i had the same proplem
buy aftel clear data and cash memory about 3 times for google service and google play store and last google wallet , evrey think get bake norml
Click to expand...
Click to collapse
Did you reboot the phone after clearing it? I've been wiping it a few time but it still not seemed to work.

seanho12345 said:
Did you reboot the phone after clearing it? I've been wiping it a few time but it still not seemed to work.
Click to expand...
Click to collapse
this morrning evrey thing not work
i try a lot of thing but no help

All seemed fine yesterday after installing safetynet-fix-v2.3.1-MOD_2.1 but it's a bigger mess today. Unlike yesterday, Safetynet CTS profile fails and Play Protect shows device not certified. I even managed to get an API throttle error from the Integrity Check app, which presumably means I'm SOL for a while.
More gory details...
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

Hiding the Magisk app solves the issue. Just hide then reboot phone. Profit.

Thanks to @Displax everything passes with safetynet-fix 2.3.1-MOD_3.0.
Release v2.3.1-MOD_3.0 · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Release v2.3.1-MOD_3.0 · Displax/safetynet-fix
github.com

manjaroid said:
Thanks to @Displax everything passes with safetynet-fix 2.3.1-MOD_3.0.
Release v2.3.1-MOD_3.0 · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Release v2.3.1-MOD_3.0 · Displax/safetynet-fix
github.com
Click to expand...
Click to collapse
Thanks, its working

Magisk hidden, Zygisk enabled, safetynet-fix 2.3.1-MOD_3.0 installed
Force stop, clear cache and storage for Google Play Services, Play Store and Wallet, reboot.
Repeat 4 times
Still Play Integrity API Checker shows red cross for MEETS_DEVICE_INTEGRITY
EDIT:
Uninstall USNF, reboot, check with Integrity API Checker - got 3 red crosses, predictable.
Reinstall USNF, reboot - MEETS_DEVICE_INTEGRITY is red

BesoC said:
Magisk hidden, Zygisk enabled, safetynet-fix 2.3.1-MOD_3.0 installed
Click to expand...
Click to collapse
Is Enforce DenyList enabled and DenyList configured?

manjaroid said:
Is Enforce DenyList enabled and DenyList configured?
Click to expand...
Click to collapse
DenyList is enforced, There are Google Play Store and Wallet in DenyList

BesoC said:
DenyList is enforced, There are Google Play Store and Wallet in DenyList
Click to expand...
Click to collapse
Try clearing storage for the Integrity Check app or uninstall and reinstall it. Avoid checking too often also, the app gave me an error about limits and throttling when problems were ongoing a couple days ago. Sorry, I don't have any other ideas.

manjaroid said:
Try clearing storage for the Integrity Check app or uninstall and reinstall it. Avoid checking too often also, the app gave me an error about limits and throttling when problems were ongoing a couple days ago. Sorry, I don't have any other ideas.
Click to expand...
Click to collapse
Still not working, but thanks for your efforts

BesoC said:
Still not working, but thanks for your efforts
Click to expand...
Click to collapse
Whats working on pixel 7 pro for me
SafetyNet displax mod 3.0
Shamiko module
Magisk hide
All Google apps hidden in deny list
Deny list enforced disabled
Clear cache from wallet and playstore
Reboot

Bxperiaz3 said:
Whats working on pixel 7 pro for me
SafetyNet displax mod 3.0
Shamiko module
Magisk hide
All Google apps hidden in deny list
Deny list enforced disabled
Clear cache from wallet and playstore
Reboot
Click to expand...
Click to collapse
Thank you for your advise. Did exactly as you wrote, still MEETS_DEVICE_INTEGRITY is red

BesoC said:
Thank you for your advise. Did exactly as you wrote, still MEETS_DEVICE_INTEGRITY is red
Click to expand...
Click to collapse
Maybe try the new USNF mod Displax just put out...
v2.4.0-MOD_1.0

Question Not passing safetynet(Play Integrity API) on pixel 7

I made a big mistake yesterday. I saw threads about the new Play Integrity API thing and download the Integrity API checker. At that time, the integrity API checker cannot pass MEETS_DEVICE_INTEGRITY but my YASNAC can pass CTS profile. So I installed the Displex mod of the universal safetynet fix. I saw that my DEVICE_INTEGRITY passed but after testing a bit I found that it's not very consistent. Then after checking out the original repo knowing that there will be a release about this fix soon, I Installed back v2.4.0. This is when everything goes wrong. My device can no longer pass CTS profile. I tried wiping storage of the GAPPS, install back the modded module, remove Magiskhide props config. It is still not working. I cannot use my GPay now. Please help me get my GPAY back. Thanks for all the help.

To clarify my current setup, I have the modded v2.3.1_MOD2.1 installed now and props config removed.
Also a small question, do I need to wait for the device to get certified to get the CTS profile match or it should immediately work if everything is right.

seanho12345 said:
To clarify my current setup, I have the modded v2.3.1_MOD2.1 installed now and props config removed.
Also a small question, do I need to wait for the device to get certified to get the CTS profile match or it should immediately work if everything is right.
Click to expand...
Click to collapse
safetynet-fix 2.3.1-MOD_2.1 should get you back on track. It's a popular topic today for those of us caught off guard.
Waiting for Play Protect certification should work but clearing storage for Play Store and Play Services will speed it up.

manjaroid said:
safetynet-fix 2.3.1-MOD_2.1 should get you back on track. It's a popular topic today for those of us caught off guard.
Waiting for Play Protect certification should work but clearing storage for Play Store and Play Services will speed it up.
Click to expand...
Click to collapse
Yeah I already have USNF 2.3.1_MOD2.1 installed. However, my question is that is the CTS profile a prerequisite for the device to get certified or it should first get certified then the CTS profile match will work.

Hi
Im having sort of same problem, untill today my phone passed everything, gpay worked and all good..
from nothing it started to fail, not passing CTS profile match, gpay doesnt work.
tried everything, reinstalled magisk, reinstalled the modules, tried 2.3.1 mod, tried 2.4.0. Nothing works.
best i've achieved, is passing safetynet once, but after 2-3 min, it doesnt pass anymore.
any ideas what to do now?

manjaroid said:
safetynet-fix 2.3.1-MOD_2.1 should get you back on track. It's a popular topic today for those of us caught off guard.
Waiting for Play Protect certification should work but clearing storage for Play Store and Play Services will speed it up.
Click to expand...
Click to collapse
I'm Play Store certified but I don't pass CTS profile match

I am not sure if anyone has the same problem as mine. I configured magisk denylist as picture attached which included "play store service". The restarted the phone, went back to the denylist "play store service" gone

tinhsoftware said:
I am not sure if anyone has the same problem as mine. I configured magisk denylist as picture attached which included "play store service". The restarted the phone, went back to the denylist "play store service" gone
Click to expand...
Click to collapse
If you mean Google Play Services, that's normal and intended behavior if using a USNF mod. It's "denied" in the background.

Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip

seanho12345 said:
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
Click to expand...
Click to collapse
I you still have issues with Banking / Wallet app (even passing SN checks) then install Shamiko Module, disable Enforce Deny List and try. This module takes charge of DenyList hidding Zygisk itself and Zygisk modules.

good morning
after maby 20 hours of hiding the magic by Shamiko moldes
itis ok
and fine

I have a Google Pixel 7 with Magisk V25.2, Universal SafetyNetFix V2.4.0 and I still can't install some apps and some other are not even visible in the results.
I've tried with and without the deny list (clearing cache and storage of Google Play service/store/protect), but nothing.
I've spent the last 2 days banging my head on the wall looking for solution, but...nothing.
Do you guys know something that works?

andrea_x said:
Do you guys know something that works?
Click to expand...
Click to collapse
Yes, Canary builds 25206 (831a398b) or 25209 (2717feac) and patch accordingly. Plus the modified safetynet-fix module.

manjaroid said:
Yes, Canary builds 25206 (831a398b) or 25209 (2717feac) and patch accordingly. Plus the modified safetynet-fix module.
Click to expand...
Click to collapse
Wait wait, I'm not familiar with that, how do I get the APK or if it's a Magisk module where do I get the .ZIP?
And what do you mean with "patch accordingly"?
Thanks a lot!

andrea_x said:
Wait wait, I'm not familiar with that, how do I get the APK or if it's a Magisk module where do I get the .ZIP?
And what do you mean with "patch accordingly"?
Thanks a lot!
Click to expand...
Click to collapse
Browse the repo and download app-release.apk. On a PC click the <> symbol to the right. If you're navigating from a phone tap the Browse files button to locate the file. I suggest caution and go with 25206. Anything after it has problems except maybe 25209, which worked ok for me but not for everybody. Once Canary is installed avoid the update button.
First, uninstall your current Magisk and restore init_boot.img back to stock. The phone is unrooted at this point.
Whichever Magisk release you install next, patch init_boot.img with that release. The phone should be rooted at this point.
Then your modules and Magisk configuration.
The safetynet-fix module you want is named safetynet-fix-v2.4.0-MOD_1.2.zip.

andrea_x said:
Wait wait, I'm not familiar with that, how do I get the APK or if it's a Magisk module where do I get the .ZIP?
And what do you mean with "patch accordingly"?
Thanks a lot!
Click to expand...
Click to collapse
magisk-files/canary.json at master · topjohnwu/magisk-files
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com

ziddey said:
magisk-files/canary.json at master · topjohnwu/magisk-files
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks for your help, but I've installed and the "CTS profile match" test stil fails. and I still can't install some apps.

manjaroid said:
Once Canary is installed avoid the update button.
Click to expand...
Click to collapse
Thanks a lot fr your detailed explanation, you're very kind!
Buuut...the update button is exactly where the install button is, how can I patch the init_boot.img?
Should I really go back to the original init_boot.img first?

andrea_x said:
Thanks a lot fr your detailed explanation, you're very kind!
Buuut...the update button is exactly where the install button is, how can I patch the init_boot.img?
Should I really go back to the original init_boot.img first?
Click to expand...
Click to collapse
I don't know what's up with the buttons. Install is needed to select your file to patch. And yes, when starting over it's usually best to clean patch the boot image with the Magisk release that's running, although not always. If you don't mind posting a screen shot of Magisk it might help get a better perspective.

manjaroid said:
I don't know what's up with the buttons. Install is needed to select your file to patch. And yes, when starting over it's usually best to clean patch the boot image with the Magisk release that's running, although not always. If you don't mind posting a screen shot of Magisk it might help get a better perspective.
Click to expand...
Click to collapse
Here it is the screenshot