While it makes SN pass on a OnePlus 8T running OOS 18.104.22.168, it breaks the fingerprint sensor with "hardware is temporarily unavailable" shown on the lock screen.v2.1.0 is officially released and open sourced now, so everyone can stop being ****ing babies.
Changes Fixed new SafetyNet CTS profile failures as of September 2, 2021 Added MagiskHide features that will be removed in future versions of Magisk Donate If you found this helpful, please consi...github.com
Wow, that was fast.
magisk: fix OnePlus display issues, reorganize props by osm0sis · Pull Request #90 · kdrag0n/safetynet-fixvendor.boot.verifiedbootstate was a "late_prop" in MagiskHide so needs to be set at boot_completed; this works around OnePlus display mode and in-display fingerprint reader breakage when ...github.com
Not sure if you saw this:
Thanks, yes. Does that mean it will work in a later version? I can't tell if that post just mentions the issue or resolves it.
Should do - pull request contains solution but requires reviews etc, however my hunch is OP may push a build with a fix quickly due to issue found... Here's hoping! PW
Were you able to solve the problem? I'm on op8p, crdroid, same problemI purchased 2.1.0 and I'm also not passing safetynet beyond basic.
CrDroid, 1P8Pro, Magisk Canary 23001
I've got AML, V4A, Busybox, Riru 26.1.2 and Systemlesshosts active in Magisk (along with SNfix 2.1.0
Do I need MagiskHide Props Config?
And if that had happened before now, the code review could have happened sooner, and patches &etc could have been tested.
My number one concern here is that Riru is a vector for unwanted payloads, and so it is *vital* that the code is properly audited by many eyes - PRIOR TO ANY RELEASE WHATSOEVER.
There are actually also concerns that the release model being applied here is in direct contravention of the terms of service at Github, before we even get into anything else.
I have no problem with rewarding ingenuity, but this model of "Access to Pre-releases for Patrons" is troubling, to say the least.
Reasonable people would realise that these are legitimate concerns. And if the language is robust, then perhaps it is required, to wake people from their slumber.
Hi, thank you for your answer, I try installing this module via magisk, clear google play all data and google pay all data, but same error., also my banking app A1 Wallet recognize my phone is rootedI would suggest trying Riru-Momohider
A Riru module tries to make Magisk more hidden. Contribute to canyie/Riru-MomoHider development by creating an account on GitHub.github.com
or for even easier automatic setup, my mod of it here (attached to post):
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Threadforum.xda-developers.com
Note: You *may* want/need to clear data of Google Play afterwards (be aware that this will remove cards/loyalty cards)
MomoHide is usually a easy way to try and get around those issue’s and is what i use for both my banking and GPay issues, though sadly it doesnt work for everyone, but requires the least amount of addons and fiddling when it works
magiskhide add com.google.android.gms.unstable
magiskhide add bg.a1.wallet
OnePlus 5T and 6T are old enough that they do not need this module.
My Samsung A71 get passed all safertynet check also showing "BLUE" pass.
But when going into my Local Bank Apps, apps warn & kick me out saying detected device is rooted.
Needless to say , I made all necessary procedures such as TERMUX su -props choose Nexus 6P ..... Magisk Module Riru and others all installed relate to safetynet stuffs...... every steep between restart device...... finally Magisk Hide , give it another name instead of Magisk Manager .... hide all Banking apps.
Appreciate if any member shed some light on solution.
Thank you very much., edmond.
Genius !!!Are you running on the latest SafetyNet fix? And have you tried adding the banking app(s) itself in LSPosed/Xprivacy and block tracking (important). Some banking apps have become smarter in detecting unlocked/rooted device, it's not enough to have a SafetyNet pass.
Also, some apps have started registering the SSAID assigned to the app and banning your device. The good news is, with root access, you can spoof it and "un-ban" yourself easily.
The above has helped me pass all banking apps that were able to detect me.
Already merged, actually: https://github.com/PixelExperience/frameworks_base/commit/993e10547c7329657e48610c5a10cb99943b13c7
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.