Thanks! Now safety net passes but Google Pay keeps saying my phone is rooted. I already added Google Pay in Magisk Hide but no luck.You'll need to install the MagiscHide Props Config and to set a recognised fingerprint then. My Huawei tablet now has a P40 fingerprint, and google is happy with it...
I was using 1.1.0 version and worked just fine, but after intensive testing I found some strange issues with my banking app and Amazon App (Safety Net pass and Gpay contactless OK).Everyone having issues passing basic attestation after installing the module, please try the attached versions.
There have been quite a few reports of fingerprint unlocking in apps breaking on One UI. This is not something that is planned to be fixed, because One UI is a heavy OEM skin that is not officially supported. It's surprising that it works on One UI to begin with.
probably v31 armed with root beerOdd, something else in your setup is tripping it then. Magisk hide works for me. Pixel 3a, Jan 2021 security patch. Modules: AccA, USNF. ElementalX kernel. Not ticking revolut in Magisk hide: root detected, flipped magisk hide for revolut, clear app data, bam, works.
Do you get any strage issues with banking apps or lastpass etc.works on S20 FE 5G (SM-G781B) ROM OneUi 3 Android 11.
no configuration required here is how I proceeded:
• activate Magisk Hide
• install MagiskHide props config
• install UniversalSafety fix v.1.1.1 test1.zip (see Page 4)
• restart and erase playstore data
(I specify that I have EdXposed installed)
thank you very much to the dev
So far no luck and also gonna give up. Rather not use google pay but have my fingerprint actually workinghave the same problem with oneui2.5 ... let me know if you find a solution to this; the lack of third party biometrics access is a deal breaker as I use it to login to my pc ...
Are you able to have third party app access to biometrics?works on S20 FE 5G (SM-G781B) ROM OneUi 3 Android 11.
no configuration required here is how I proceeded:
• activate Magisk Hide
• install MagiskHide props config
• install UniversalSafety fix v.1.1.1 test1.zip (see Page 4)
• restart and erase playstore data
(I specify that I have EdXposed installed)
thank you very much to the dev
I don't use banking apps to be honest I never register a card because I am wary of data theft.Do you get any strage issues with banking apps or lastpass etc.
Give me an example of applications that use biometrics that I can test ...
Everyone having issues passing basic attestation after installing the module, please try the attached versions.
There have been quite a few reports of fingerprint unlocking in apps breaking on One UI. This is not something that is planned to be fixed, because One UI is a heavy OEM skin that is not officially supported. It's surprising that it works on One UI to begin with.
Try this: https://github.com/sdex/AndroidIDeditor/releasesThanks kdrag0n for your hard work ;-)
Feedback: With your fix, Magisk shows success when checking safetynet, but until now, the fix doesn't work for GPay in my case, neither with V1.1.0 nor with V1.1.1-test2 on Xiaomi Mi 9 with MIUI 12.
What I have done: I have cleared GPay's and PlayStore's cache and user data, uninstalled GPay, rebooted. Checked that PlayStore is checked in Magisk Hide and that Play Store indicates no problems in Play protect. Then I re-installed GPay, added it to MagiskHide and cleard GPlay's and GPay's cache and user data again. After this procedure, GPay did still know my credit card, but reported that the phone doesn't meet the security requirements. I have deleted the credit card, cleared cache and data, rebooted and added the card again, but GPay is still not working.
Lastpass or Remote fingerprint unlock? Both are on play store. Google Pay works for me too, but third party access to biometrics does not ...Give me an example of applications that use biometrics that I can test ...
No it does not work it may be related to the Samsung pass frameworkLastpass or Remote fingerprint unlock? Both are on play store. Google Pay works for me too, but third party access to biometrics does not ...
You can find all oficial releases here. I have never encountered any security issues with files from that website but it's up to you if you trust them or not.i am facing the same problem my friend.
please can you answer 2 questions? first, where did you download the previous version from? is it safe?
second, do you believe this can be fixed with a future magisk update, or are we screwed forever?
thanks for trying. i tried to disable samsung pass but it didn't work eitherNo it does not work it may be related to the Samsung pass framework
I took some time to compare last working version 7.30.3 to the two newest ones 7.31/7.32. After taking some logs I noticed that:Ok, thank you very much, that did the trick... for now. I wonder what kind of additional checks they are doing compared to others and if there is or will be a way to circumvent this in the future.
One crazy idea would be if it was possible to run apps in their own isolated containers chroot or vm style. Possibly unrealistic thought but who knows what the future will bring
Again, big thanks! Very much appreciated.
I did the same as you on my S20+ exynos Android 11 and it workedworks on S20 FE 5G (SM-G781B) ROM OneUi 3 Android 11.
no configuration required here is how I proceeded:
• activate Magisk Hide
• install MagiskHide props config
• install UniversalSafety fix v.1.1.1 test1.zip (see Page 4)
• restart and erase playstore data
(I specify that I have EdXposed installed)
thank you very much to the dev
Please make 'Universal Play Integrity Fix' ... #204
Fixes to expand 'Universal SafetyNet Fix' to become a 'Universal Play Integrity Fix' are needed.
The SafetyNet Attestation API is deprecated and has been replaced by the Play Integrity API.
https://developer.android.com/training/safetynet/deprecation-timeline
New Play Integrity API is rolling out from June 2022, and evidently Google Play Store and Google Pay/Wallet are already using its verdict.
June 2023 is the Migration Deadline for app developers. This will also allow their older app versions to continue working with SafetyNet API for a limited time.
June 2024 is the End of life for SafetyNet API; its attestation will no longer work for any app version, and apps will receive an error.
The new Integrity API has more strict requirements for passing attestation, and this seems to be enforced in Android 11+ particularly.
Currently (evidently due to this), device security issues are detected by
I'm guessing that the 'passing' messages based on the old SafetyNet API are likely to realigned soon.
- Google Pay/Wallet, which may state "You can't pay contactless with this device...(Your phone doesn't meet software standards)" on updating or attempting to add a card despite in-app Contactless setup stating "You're ready to pay contactless with your phone (Your phone meets security requirements)", and
- Google Play Store, which may no longer show apps like Netflix w/ Android 11+ (developers can 'exclude devices from their app's distribution based on their device integrity . Device exclusion is based on the latest device integrity verdict that the Play Store app receives from the Play Integrity API') despite in-app settings showing Play Protect 'Device is certified' result.
A workaround that evidently allows Play Integrity API attestation to pass (and solve Wallet / Play Store issues also) has been discovered. It involves spoofing an earlier certified ROM, generally by using MagiskHide Props Config module to change fingerprint prop to one for Android 10 or earlier.
Undoubtedly other apps will begin to detect broken TEE etc / fail as they migrate or begin integrating the Play Integrity API.
A 'Universal Play Integrity Fix' will evidently require more understanding / research into how the fingerprint prop is used, and possibly other new behaviours.