Many thanks for your help. Props Config is just installed so I haven't changed anything. I'll have a read of the attachment to see what to do unless you have any tips? Thanks again
For ROMs that don't include certified fingerprint or spoof one (many Custom ROMs, China region stock etc) you need only MHPC module option to set certified fingerprint configured in addition to USNF module... PW
Again (handful of similar posts earlier) - old Magisk 23 and new USNF 2.2 for Zygisk?!
Thanks for the reply.
Yes you are right. I have seen that now the problem is I got confused with reading so many posts. That said 2.1.2 did not work for me.
Oh I didn't even see what your problem is, if you're failing basic integrity this can't help you. That means your system partition has been altered or there is evidence of tampering going on. As for eval type basic, that is what you want. If I had to guess a Xposed module altered /system or it's doing something obvious and easy to detect.
Beyond Rom is custom?
Lite on detail.just got the notification my device isn't ok to use NFC but Google pay still loads the cards. checked and failed safety net, I have no idea when that started. I haven't updated anything in a while and avoided updating magisk because it was going to lose magiskhide. no idea why this suddenly changed but I decided to update magisk after anyway just to see. still no good. I have riru and lsposed so maybe I have to tweak that. what changed? should I upgrade to Android 12 and then try fixing this after? pixel 4a here.
edit: seems like I don't have lsposed now. probably because of the update to magisk
so I got 23015 the alpha apk and uninstalled the other magisk apk. I got 2.2.0 usnf and flashed that. I enabled zygisk and denylist. I can pass safetynet and use biometrics on my banking app. the legacy Google pay app still warns me about my device but the newer gpay app doesn't and the NFC payments still work. Lsposed and privacylua don't load now so I guess I can remove them?Lite on detail.
Assume you have public (stable) Magisk 23.0. MagiskHide changes have only hit debug (Canary) TJW builds as yet, but this fix addresses new builds W/ Zygisk / denylist also.
So current stable Magisk should be no different; Google made new server end changes in September however, and many devices now need 2.1+ USNF to pass.
You need 2.1.2 for current stable Magisk & Riru is required also. 2.2.0 is for current canary + builds with Zygisk going forward... PW
Did you clear cache/data from google play store, gpay and google play services? Sometimes if you don't pass safetynet it'll remember that until you do, check play store settings then about and at the bottom see if your device says it's certified or not. Clearing cache/data once safetynet passes should fix it.so I got 23015 the alpha apk and uninstalled the other magisk apk. I got 2.2.0 usnf and flashed that. I enabled zygisk and denylist. I can pass safetynet and use biometrics on my banking app. the legacy Google pay app still warns me about my device but the newer gpay app doesn't and the NFC payments still work. Lsposed and privacylua don't load now so I guess I can remove them?
I'm a little concerned about the legacy Google pay app warning and I don't think I need it so I just uninstalled it. YASNAC app says I pass safetynet (integrity, cts pass, basic eval).
Instead of Riru-LSPosed, you need to use Zygisk-LSPosed because Riru is not compatible with Zygisk.
I'm on the regular lsposed tg I don't know where that archive is. last post says they won't release the zygisk lsposed yetInstead of Riru-LSPosed, you need to use Zygisk-LSPosed because Riru is not compatible with Zygisk.
Go to the Modules tab in Magisk app and Riru itself should dynamically show there some error (when working ok it says that it is loaded and displays how many Riru modules are loaded, like Riru-LSPosed)
Not sure can you download:
from Github, but you can from LSPosed-Arcives TG channel (however, posting URLs to TG channels are not allowed here on XDA).
With Zygisk-LSPosed you should be able to continue using LSPosed modules like XPrivacyLua, etc
Just updated my previous post. Read the PS there to solve the TG labyrinth - actually see the screenshot below
thanks I was able to find and flash it. only thing is I didn't place the shortcut on reboot, where can I find the APK? (ok so on reboot I got another chance to place the shortcut, but I don't know where else to find it)
Interesting - you needed LSPosed/XLua for AdAway?
Hiding Magisk app is irrelevant for Google apps (it may help only to some banking apps - those apps try to explore various methods to find or even guess about the root, eg, you may have locked Bootloader with stock firmware but if you just install Magisk APK they will falsely guess that your phone is rooted bcs why otherwise would one install Magisk APK)
We usually rather call Google Play Services as GMS, due to it's package name (you see that package name when you add to DenyList):
# Remove Play Services from DenyList, otherwise the Zygisk module won't load magisk --denylist rm com.google.android.gms
Had the same problem - all of a sudden yesterday - with Google Pay on my OnePlus 9 Pro. Did everything you did and more, even installing older versions, no luck for 3 hours.Hello
i have a LG G4 with A11 Havoc..
Magisk app 24.3(24300) (27)
Added to the list
google play services for AR
google play store
google play services
universal safety fix module 2.2.1 active
removed data of google play services, google play store and google pay
but no luck with google pay
something that i saw... every restart google play services go out of denied list.
Any suggestion or help?