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.
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://forum.xda-developers.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
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.
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!
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:
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
OnePlus 5T and 6T are old enough that they do not need this module.
https://github.com/kdrag0n/safetynet-fix#universal-safetynet-fixThe only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels. MagiskHide is required as a result.
Passing basic attestation is out-of-scope for this module; this module is meant to defy hardware attestation, as well as reported "basic" attestation that actually uses hardware under-the-hood. Use MagiskHide Props Config to spoof your CTS profile if you have trouble passing basic attestation. This is a common issue on old devices and custom ROMs.
kdrag0n released this 18 days ago
Fixed under-display fingerprint on OnePlus devices (@osm0sis)
kdrag0n released this 20 days ago
Fixed new SafetyNet CTS profile failures as of September 2, 2021
Added MagiskHide features that will be removed in future versions of Magisk
kdrag0n released this 27 days ago
Added support for heavy OEM skins (One UI, MIUI, etc.)
Added support for Android 12 Beta 4 and future versions
Android 12: Fixed face unlock on Pixel 4 series
Added support for Android 7.0 and 7.1
Rewritten as a Riru module
kdrag0n released this on 14 Jan
Added support for Android 8.0, 8.1, 9, and 10
Increased chances of passing SafetyNet on older devices
You should submit a Pull Request on GitHub to update the README.https://github.com/kdrag0n/safetynet-fix#universal-safetynet-fix
@kdrag0n, others -
Just a heads up. - GitHub README.md is a bit misleading.
Devices passing basicIntegrity often lack a passing (certified) fingerprint (eg. my Mi Pad 4 w/ unofficial LOS 18.1), therefore 'basic attestation' (basicIntegrity) pass is NOT the only requirement to allow USNF to fix failed ctsProfile (work).
Actually, 'basic attestation' (basicIntegrity) often does NOT require a valid combination including build fingerprints and security patch levels (but apparently such may be required for some devices), but this IS an additional requirement for passing ctsProfile / SafetyNet.
While passing 'basic attestation' (basicIntegrity) is out-of-scope for this module, passing ctsProfile is ALSO out-of-scope when a valid combination including build fingerprints and security patch levels is lacking.
And contrary to the last suggestion above, @Didgeridoohan's MHPC GitHub home page states:
The last statement should therefore read:
"Use MagiskHide Props Config to spoof a certified (passing) fingerprint if you have trouble passing ctsProfile after enabling Riru, this module (USNF) and MagiskHide (in Magisk settings), and have passing basicIntegrity. This is a common issue on custom and uncertified stock (China etc) ROMs."
Hope this helps / README.md can be made clearer. PW
You're way off, and have cited no proof!Anyone who installs Riru, deserves everything that happens to them.
Anyone who pays a clown for broken amateur hour nonsense, also deserves everything that happens to them.
This project has dramatically veered into a wall, and the torrent of mockery that is sure to follow, is well deserved.