Added BDO in magiskhide. Renamed magisk app into something else. Rebooted. No dice.
BDO app refuses to work. What's different with your setup comapared to mine that you're able to make it run?
The title page of the safetynet module on github says:
Android versions 7–12 are supported, including OEM skins such as Samsung One UI and MIUI. This is a Riru module, so Riru must be installed in order for it to work.
Well, I guess that Android 7 is no longer supported since Riru works on Android 8 and later.
https://github.com/RikkaApps/Riru PW
Ah, sure, but could help others reading / trying / thinking it does nothing when it does...Never fear, i did link the kiddie to my automatic modded version of Momo-Hider, here: https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-85630515
As well as linking to the HP of Momo-Hider (containing the manual method of adding those files) back a page in response to his original post
Yours,
Nigel
Still says "Universal SafetyNet Fix 1.1.0" too... Clearly OP doesn't update on XDA much and hasn't even announced later releases here.pndwal:
Sorry, I have it somehow connected mainly with edXposed and LSPosed (which are only on Android 8 and later)
But anyway, in the first post of this forum is Android versions 8–11 are supported which is a bit confusing.
Disclaimer: I'm not (yet) using this module but interested in its development.To those who are bored, can you try if you can prevent this banking app from detecting root? This banking app is the only one that's refusing to work on my device. Other banking apps work with just "magiskhiding" it. Some of my apps work if put them inside Island. Just this one app that refuses to work no matter what.
If you ever want to try "breaking" it to not detect root, the name of the app is BDO Digital Banking (by BDO Unibank, Inc.)
Thank you. I tried AirFrozen and it was able to freeze my renamed magisk app, but I get the same error, unfortunately.I used to "freeze" the hidden Magisk app, too.. works for me (you app does indirect discovery I guess). I "freeze" the hidden Magisk app with AirFrozen after I set up everything I wanted to be set up in Magisk and my banking app (myRaiffeisen Hungary) works. Here's my "method" I wrote on Xiaomi.EU forum.. I got the idea from Didgeridoohan's Magisk help page.
Thank you for this suggestion. I tried AirFrozen, but it didn't work. But I love how AirFrozen freezes (makes renamed magisk app disappear from system tray). Maybe this will work with other apps so I'll definitely try this in the future.I used to "freeze" the hidden Magisk app, too.. works for me (you app does indirect discovery I guess). I "freeze" the hidden Magisk app with AirFrozen after I set up everything I wanted to be set up in Magisk and my banking app (myRaiffeisen Hungary) works. Here's my "method" I wrote on Xiaomi.EU forum.. I got the idea from Didgeridoohan's Magisk help page.
Finally, this solved the issue for me!Disclaimer: I'm not (yet) using this module but interested in its development.
What works for me (until login screen) is using MagiskHide and (renaming TWRP folder in /sdcard OR using Storage Isolation on the app)
Confirming it fixes all issues with display and fingerprint reader on OP8T.
Only to try LSPosed / PrivacyLua solution, or petition ROM dev to merge commit linked here:
That frameworks_base repo and commit are missing now, perhaps @Displax can repost somewhere using gist for just the example diff/patch? Then @kdrag0n might be interested in adding it to the USNF README as another "out of scope" example.Only to try LSPosed / PrivacyLua solution, or petition ROM dev to merge commit linked here:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85580011
Not sure this is actually referring to ROMs like PixelExperience (with "prebuilded utils, which manipulate the props values. Need to fix inside there").That frameworks_base repo and commit are missing now, perhaps @Displax can repost somewhere using gist for just the example diff/patch? Then @kdrag0n might be interested in adding it to the USNF README as another "out of scope" example.
Edit: Actually, scratch that, looks like @kdrag0n will make a patch himself when he has time for ROM stuff next: https://github.com/kdrag0n/safetynet-fix/issues/88#issuecomment-917729677
Agree. PWShould still probably be linked in the README though, since there seem to be a lot of confused custom ROM users always asking for help...
That is on you not the module. Everything works fine on my Pixel 4a 5G.The latest version caused my Pixel 4a 5g to lose network calling as well as have issues with laggy UI responsiveness. The problems went away when I uninstalled the module.
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.