yashsingh1/xdaforums huggingface dataset:
[Android Software Development] minimal35:
I do not need to hide the module, my application is in denylist, but as long as it is there the substitution module will not work for an application that is in denylist. If I remove an application from the denylist, the module will work for that application, but the application will detect the root:(
[Android Software Development] minimal35:
Simply put I need a tool that will hide the root for a specific application without using denylist
[Android Software Development] pndwal:
Ah; could be an issue the module forum may address?...

You could try Shamiko module; uses denylist (app must be in list) as list only (hijacks it) for convenience, but denylist must not be enforced... Shamiko uses its own hiding (alternative methods)... PW
[Android Software Development] drasterlx:
what app use to unistall the new version?

what happend if the Google Play Services will update ?

Thanks
[Android Software Development] Fishawy:
No app, just go to Google Play Services, three dots, uninstall updates.
[Android Software Development] Chrisch_91:
I can't use my banking app. I pass safetynet, i have the app in denylist, magisk hide and universal safetynet fix active. Also shamino module. With my old smartphone i had to disable magisk app temporary, but this also doesn't work for me. What coud be the problem?
[Android Software Development] lyrebird:
I recently update my Oneplus 8 Pro to OOS 12 C.16. Factory reset. Everything was running ok. I then tried this module, and found out it breaks my fingerprint login. Have to disable this module and restart my phone to bring my fingerprint login back.

Anything else I should do in addition to installing this module?
[Android Software Development] firozpatel:
I'm the same, was working before the security patch update, but now finger print don't work and I don't pass safety net, can't find a fix, unless someone can help
[Android Software Development] ipdev:
Start at Post - #1,691

---

The fix will be in the next release.

You can see all the commits added since the v2.2.1 release here.

safetynet-fix - [github] - Comparing changes

Cheers. :cowboy:
[Android Software Development] firozpatel:
There is a fix now, if you head over to the link

SafetyNet fails on C.20 update for OnePlus 8 Pro · Issue #188 · kdrag0n/safetynet-fix

The "C.20" update for OnePlus 8 Pro based on Android 12 and the OxygenOS 12.1 overlay in correlation with "SafetyNet-Fix v2.2.1" completely blocks the fingerprint scanner. Uninstalling this module ...

github.com
[Android Software Development] MaciekZ123:
Doesnt work for moto g7 power with flashed pixel experience
[Android Software Development] parpagnas:
Same for me: i have this fix + props (ootb config) on a Pixel Experience, it passes all checks, including cts but Revolut still détectés the root. I also hid Magisk from its settings.

I triés with Magisk and Shamiko but it doesn't work better :(
[Android Software Development] parpagnas:
Nevermind, after having installed lspod + Shamiko + having added Revolut to the Deny list i was able to use the Revolut app.
[Android Software Development] zgfg:
Of course, that's must be the first thing to add the banking apps to DenyList (otherwise there is no use of DenyList)
[Android Software Development] parpagnas:
Yeah but that's not enough. I just made the test and without shamiko enabled, but this module still enabled, ans Revolut detected the root again.
[Android Software Development] zgfg:
Yeah, just putting the banking app to DenyList is not enough but that that must be the first thing to test

If that banking app tries to find Zygisk, then you have to use Shamiko as well (IDK if Unmount DenyList that some use instead of Shamiko also hides Zygisk)

For some banking apps you have to go even further (hiding Magisk app, using HideMyApps etc). It all depends how 'smart' in detection is that particular banking app (there is no one single developer who develops all banking apps, games, etc and puts the same detection mechanism to all of them to make our lives easier - that one and single method for hiding the root would apply for all those apps)

And unfortunately, things ever change with the new versions of those banking apps, new versions of Magisk...
[Android Software Development] parpagnas:
Thanks for the explanation. I hadn't root a primary phone for a long time, and wasn't aware of all these tools yet.
[Android Software Development] kouzelnik3:
I've found USNF 2.3.0 forked from kdrag0n in addition to frnode that should fix some FOD issues etc.

Releases · frnode/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - frnode/safetynet-fix

github.com
[Android Software Development] Fif_:
GitHub says there are no differences between these versions except for the addition of docker infrastructure in fmode's fork.
[Android Software Development] pndwal:
How does GitHub say that?...

I count 18 built commits and various fixes / changes since official 2.2.1, including commits from osm0sis, kdrag0n, benjibobs and ipdev99 from official project as well as several from frnode in this fork... 👀 PW
[Android Software Development] osm0sis:
I informed @kdrag0n of the new active fork and he said he'd try to get an official release out soon; he's had a busy few months and hadn't been able to get to it.
[Android Software Development] Fif_:
Looked at https://github.com/kdrag0n/safetynet-fix/compare/master...frnode:master

Nevertheless, I was wrong, 4 commits were about renaming, adding docker builld, but there is a small change in the code at https://github.com/kdrag0n/safetynet-fix/commit/dc3ec64eff578bc88aa6bb2970c026d71f9799e0
[Android Software Development] ipdev:
Hi all. 🙂

I am looking to resurrect PR #158.

It has been awhile and I do not remember what properties are actually needed to pass SafetyNet. 🙃

This is my current WIP.

GitHub - testing

I am not sure how far to go setting props with USNF.

I would prefer to not go overboard since that might cause problems.

Then again, I would also like to add extra sensitive props for completeness. 🙂​

Since USNF now supports Android 7.x and older..

Should I include the Magisk version check?

Should I include adding PlayServices (GMS) to the denylist for SDK25 and older?​

Suggestions and opinions are appreciated. 🙂

Cheers all. :cowboy:
[Android Software Development] pndwal:
Further re. this comment:

Since you answer kouzelnik3's post about fixes for Fingerprint on Display (FoD) etc and his reference to versions available from kdrag0n & frnode, please note that comparing frnode fork with kdrag0n master is not enough to determine differences between versions... The frnode fork does in fact make the fix for Oppo fingerprint scanner available before any official (kdrag0n) release...

Some 13 commits in kdrag0n master branch are downstream of current official releases (ie. are not available / have not been built by him yet). Since frnode fork builds on kdrag0n master, pending kdrag0n fixes are available in this version in addition to the 5 unofficial commits you mention.

Diffs between official version and frnode release therefore encompasses some 18 commits (some are documentation / GitHub site changes only however) including these changes he notes:

Changes​

Fixed fingerprint scanner*

Fixed SafetyNet Pass (now "pass" all verifications)

Add Docker container for build Magisk module (only Zygisk tested)

*magisk: fix Oppo fingerprint reader issues …

- move ro.boot.vbmeta.device_state to late props since any earlier appears to break Oppo (ColorOS/OOS12) fingerprint readers

Thanks @MlgmXyysd

Fixes #157

osm0sis authored and kdrag0n committed on 11 Mar

- Nb. Earlier FoD fixes (already available in official releases) included:

• Fixed under-display fingerprint sensor on Realme devices

• Fixed under-display fingerprint on OnePlus devices

and these new unmentioned ones:

magisk: Add circumvention of OnePlus' oem unlock counter …

- I recently discovered `ro.is_ever_orange` on OOS 11, which gets set roughly 32 seconds after boot completed and is equal to the number of times a device has ever been `fastboot oem unlock`ed

- a fresh MSM (i.e. factory locked device) has it set to 0, and using system.prop to set it to 0 earlier in the boot seems to keep it set to 0 instead of the real unlock count

- I haven't seen this exploited anywhere, though I presume it exists for a reason, so probably good to manage it as well

osm0sis authored and kdrag0n committed on 25 Dec 2021

magisk: Allow limited installation on Android 7 and older …

- Key attestation was introduced in Android 7.0, but Android 7.x doesn't have InMemoryDexClassLoader so our Zygisk module is incompatible.

- In general, users on such old versions of Android don't need to bypass hardware-backed attestation (which isn't even applicable on Android 6 and older), so allow them to install the module without the Zygisk part.

Closes #156.

kdrag0n committed on 13 Mar

The three commits detailed above are those that improve compatibility for various devices, and will especially interest Oppo, OnePlus and pre-Android 8 users...

It's worth noting that while this fork makes these enhancements available early, they will eventually be built in official Universal SafetyNet Fix releases ... 🤠 PW
[Android Software Development] Feduz:
Hi to all

I have OP8T KB2003_11_C.20 with USNF V2.2.1-ob1-bg by kdrag0n

I cannot use Gpay, it tells me because rooted device, in safety net I have CTS profile match "fail"

Any suggestion for this?
[Android Software Development] pndwal:
Please say what Android version, all 3 results in YASNAC, does Magisk App home screen say Zygisk-Yes, is ROM stock, custom, developer/beta or China stock, have you tried disabling all modules except USNF (and check it is toggled enabled in Modules list) and rebooting before checking Zygisk and YASNAC...

And what is V2.2.1-ob1-bg?... PW
[Android Software Development] Feduz:
Basic Integrity: Pass

CTS: Fail

Evaluation Type: Basic

Magisk Zygisk: Yes

Stock ROM, eu version.

In magisk i've only Systemless Host and USNF (I think it's a """custom""" version, with a fix to fingerprint)
[Android Software Development] pndwal:
Please try with official USNF 2.2.1 from OP here... BTW, do you mean custom device fingerprint prop fix or fix for physical fingerprint reader/scanner... PW
[Android Software Development] Feduz:
same error in YASNAC.

For the fingerprint, it's showed the icon, but if you tap on it, nothing happens (like in this case, I have to use the "fixed" module of USNF)
[Android Software Development] pndwal:
Van you link that fork?... And what is Android version?... PW
[Android Software Development] Feduz:
https://xdaforums.com/attachments/safetynet-fix-v2-2-1-ob1-zip.5613133/

On Android 12
[Android Software Development] pndwal:
Ah... Seems fingerprint reader is broken in OnePlus A12 builds, no fault of USNF... Also users report need for fingerprint prop manually set as OnePlus seem to have messed up ROM certification.... (Some reports GPay broken due to this on bootloader locked devices)...

Solution seems to be to set a working/passing device fingerprint in MagiskHide Props Config as you would for a non-certified custom ROM or China stock etc...

Users report success spoofing OnePlus 8T Europe KB2003 or OnePlus 8 Pro IN2023 fingerprints for Android 11 (seems instead of Android 12)...

Edit: Some users report that taking full C20 zip OTA results in these bugs (ie. update is flawed), but bugs are avoided (no issues) if take full C16 zip OTA, then incremental C20 OTA (which seems fine)... ie. don't use full C20 ROM updater!!... You may be best to try this first...

Link to full C16 EU version here:

https://xdaforums.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/post-87009051

(Also, can you link a thread/forum/post for that modded USNF file?...)

Hope it helps... PW
[Android Software Development] Feduz:
Thanks!

I've found it here: https://xdaforums.com/t/guide-root-and-keeping-root-options.4387977/
[Android Software Development] amn1987:
I can't add any new Google account after flashing this module! Is this a known issue or it's something unique to my setup? Poco F1 running Awaken A12.1 with Magisk 24.3 and Zygisk enabled with Shamiko and Custom Fonts Installer the only other modules. If I disable USNF, Google accounts can again be added.

Edit: The issue persisted with v2.3.1.

Edit2: Issue resolved after clean flashing crDroid.
[Android Software Development] osm0sis:
Official 2.3.1 is now out!

Release v2.3.1 · kdrag0n/safetynet-fix

Changes Highlights Fixed fingerprint on OxygenOS/ColorOS 12 (@osm0sis) Support for Magisk 24+ module updates (@benjibobs) Restored support for Android 7 Other changes Spoofed OnePlus OEM unlock ...

github.com
[Android Software Development] ruszok:
2.3.1 installed but still in C20 (OP 8T) I must change device fingerprint to A11 - because CTS fail.
[Android Software Development] pndwal:
Many OP8T users are upset w/ OnePlus about this... The full zip OTA is broken... I put this (fix) here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-87047883

and more here:

Post in thread '[GUIDE] Root and keeping root options' https://xdaforums.com/t/guide-root-and-keeping-root-options.4387977/post-87051521

👀 PW
[Android Software Development] otimmy:
I'm haviong trouble to get Google Pay to work on my phone.

I have a Poco F3 with Lineage 19.1.

Yasnac still says the following:

Basic Pass

CTS profile Match Fail

Evaluation Type Basic

Timestamp... today's date

Installed Magisk,

Zygisk+list activated, google play services gms and gms.unstable selected

Universal Safetynet Fix activated

Magiskhide props config installed and pro values adjusted + certified fingerprint as per https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/#post-86320349

Any ideas what I could do next?
[Android Software Development] pndwal:
You need pass here...

Don't add these to denylist; USNF does proper hiding for these and will remove these from list on next boot anyway...

Revert all changes here except selecting a late certified fingerprint per instructions...

Nb. Sensitive props are handled by USNF anyway, and MHPC function is only needed for those wanting SafetyNet pass on old (pre Oreo) devices w/o USNF...

Nb. 2. certified fingerprint is certainly needed for all official LOS releases due to their anti-spoofing policy, but may not be needed for unofficial LOS as many devs add fingerprint spoofing (ie. spoof a certified stock ROM) along with integrated USNF...

The above...

Once CTS profile match passes you may need to clear data in Google Play Store and/or Google Play Services to obtain Play Protect Device is certified result in Play Store settings...

Next, add Google Pay (only) to denylist and clear its data... You will need to set up cards again, but should be happy now...

Also,

Tip: read USNF GitHub page linked in OP as well as read back thru changelogs... Most (all?) you need to know is covered there (but OP hasn't updated OP in this thread)...

👀 PW
[Android Software Development] otimmy:
Thank you for your answer.

I started by removing the items from denylist, went to check YASNAC, and now Google Pay is working. :)
[Android Software Development] smo69:
Hey, newbie question here, but I'm reading a lot of issues in particular with fingerprint readers and apps on One Plus, OPPO, Poco, etc., but what's the failure rate for Safteynet Fix on Pixel devices? I stopped rooting my phone 2 years ago because I couldn't put up with the constant maintenance of Safteynet and apps randomly failing on me, so I'm wondering if rooting is still even worth the hassle. Yes, using a Pixel 6.
[Android Software Development] Gyration3046:
Poco x3 pro with LOS 19.1 MicroG , Magisk 25.1 and with the lastest USNF 2.3.1 Yasnac safetynet check says Google Play Services API error 13: error . What does that mean ?

edit: i found the fix i should have enabled device registration but now doesnt pass cts match
[Android Software Development] Sneakdovi:
I'm unable to pay with GPay.

I'm on Oneplus 8pro C20 with root.

I have done everything suggested in the Github post for the USNF and MagiskHideProps:

Basic Integrity: Pass

CTS: Pass

But the payment is rejected.

Is anyone experiencing this?
[Android Software Development] astralmaster:
Has anyone tried to make this work on an Android emulator? To pass the Safetynet? Is it even doable on standard AOSP images? How would one achieve that?
[Android Software Development] shoey63:
I would suggest hardly anyone. Most people use it on an actual Android device.

Why do you feel it is important to have it running on an emulator?
[Android Software Development] astralmaster:
There is an app I want to run on an emulator that streams videos but has this safety net check - Google Play store app doesn't even show it when running from an emulator (it is not searchable/downloadable in the app). I could just get an apk and install it manually but this app constantly releases new versions and having Google Play store would mean easier updating. If there is another method apart from Play Store app that could do the same thing, I would settle for it, but I do not know of any, unfortunately.
[Android Software Development] TioCareca:
try aurora store 😉
[Android Software Development] rodken:
Google Play Services became unstable [Google Play Services keeps stopping] after updating from v. 2.2.0 to v. 2.3.1.

-- Force stopped Play Services, cleared cache, cleared data and restarted [to no avail].

-- Uninstalled GPay and reinstalled GPay [to no avail].

-- Force stopped Play Store, cleared cache, cleared data and restarted [to no avail].

-- Uninstalled USNF v. 2.3.1 > restarted > reflashed USNF v. 2.2.0 [hit pay-dirt].

N.B.: These are just my findings considering that there are other avenues that I could've visited.
[Android Software Development] Makishima:
Google Pay has updated to Google Wallet and now it says that my device is insecure for contactless payments, whereas right before it worked just fine. Google Pixel 4a Stock + Magisk latest + Zygisk denied everything to do with Google wallet. Also USNF 2.2.1
[Android Software Development] zgfg:
Not using GPay/Wallet but do you have:

- Zygisk enabled

--Denylist not enforced

- latest Shamiko module installed

And try to add Wallet to DenyList
[Android Software Development] AndDiSa:
@Makishima I had the same message and I added Google Wallet to the deny list ... now at least the message is gone though I didn't try a payment yet.
[Android Software Development] Nova_Max:
Something in the root detection changed when Google Pay updated to Wallet.

Previously I used Magisk Hide and the sqlite fix but that stopped working yesterday.

Now I updated to the latest Magisk and I am using:

-Shamiko (with Wallet in denylist)

-Universal SafetyNet

-GPay Sqlite fix

-Magisk app hidden

Wallet is still not working even though SafetyNet and Play Certification passes.

I also tested with Oprek which shows everything as passed.

Momo only mentions TEE but isn't able to detect root.

So I think they are using a new way to detect root.
[Android Software Development] zgfg:
Probably they improved detections

Btw, did you Clear Cache and Data for Wallet before retesting?

There is a Magisk Delta Fork (you can find on GitHub and there is also the XDA thread)

It's based on latest Magisk v25.2 but you can have Zygisk (optionally) and the old MagiskHide (seems stronger for hiding than DenyList) - you could try

If going for Delta I'd suggest to disable Zygisk and DenyList while still on the official Magisk and all modules relying to Zygisk.

Then you change Magisk app for Magisk Delta app (I use his Delta Canary version on my second phone), patch img from Delta app, flash the patched img - then reboot and start configuring MagiskHide, and re-enable Zygisk and it's modules (optionally)
[Android Software Development] AndDiSa:
@Makishima I was too optimistic, just now I received another message that contactless payment is no longer possible :-(
[Android Software Development] ai024:
@AndDiSa You can check the Google Wallet contactless payment status by tapping on your avatar in top right corner, then "Tap to pay setup".

Mine says "Phone doesn't meet security requirements" :(
[Android Software Development] AndDiSa:
Same for me ... :-(
[Android Software Development] pndwal:
Google Pay / Wallet issues; see last page in this thread (I posted fixes for related issues here also):

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87179213

And yes, Google Wallet should be selected in denylist... 👀 PW
[Android Software Development] 73sydney:
fwiw, i had zero issue after doing the wallet update last night

Its important to note that while the app name has changed to Wallet, the packagename seems to remain the same, as i discovered when i checked my Deny List afterwards....

quite why its causing issues for some is a bit of a puzzle...
[Android Software Development] Uzephi:
You're on a heavily OEM skinned OS. OneUI has the most modifications away from AOSP compared to almost all other OEMs. Heavily modified OEM skins like OneUI don't have full support as said in the readme and OP. Ymmv with those. Now if you ran LOS or another custom rom for your device, you might have better luck.

Edit: from OP: Heavy OEM skins are not officially supported, but they may work depending on your luck and the particular ROM in question. Please do not report problems on such ROMs.
[Android Software Development] Essentrix:
Appreciate the quick reply mate and the great work you guys do. Also understood re LOS and support for OneUI. Just that I am so close to working fully... 😁

It was even stable for a while with 1.1.1 until reboot...
[Android Software Development] Uzephi:
You could try what others have and use the MagiskHide Props module and try a different fingerprint in tandem with this module.
[Android Software Development] Jimmy Stat:
To be clear will this work on pixel 5 w/ stock room w/ new January ota? I figured I'd ask before I attempted to try and then waste anyone's time lol. Thanks
[Android Software Development] Jimmy Stat:
which version of safetynet fix are you using and on which device? i'm on stock s9 snapdragon oneui 2.5, magisk 21.2 and xposed (tried both taichi and edxposed/riru). haven't been able to get fingerprint in banking apps to work

[/QUOTE]

Hey this is a little off topic but, I thought you couldn't root a Samsung s9+ Snapdragon, did I read correctly or did you find something I'm very unaware of? Thanks
[Android Software Development] wyt18:
Hey this is a little off topic but, I thought you couldn't root a Samsung s9+ Snapdragon, did I read correctly or did you find something I'm very unaware of? Thanks

[/QUOTE]

i have an s9 not s9+, but it should be just as straightforward to root:

https://xdaforums.com/t/official-twrp-sm-g9650-star2qlte-chn.3802933/
[Android Software Development] Uzephi:
It works fine on a Pixel 3a Jan 2021 update. Should work on the Pixel 5 as well.
[Android Software Development] Jimmy Stat:
Thank u sir, I will let you know how it goes...
[Android Software Development] VD171:
Fails with Miui V12.0.6 Xiaomi Redmi Note 9
[Android Software Development] Essentrix:
Thanks for the thought... Will give it a try...
[Android Software Development] R00tFreak:
Thank you!

Works fine with latest universal safety net fix 1.1.1 and latest xiaomi.eu Miui V12.0.1.0 Redmi Note 9 Pro (Joyeuse)
[Android Software Development] eustachy:
Hi, I am on miui xiaomi.eu 12.0.6 (Mi9), installed fix 1.1.1 and ... the system won't start, after a few minutes of MIUI logo it goes to TWRP. Unfortunately I haven't done a backup. Is there a way to remove the fix from the system?
[Android Software Development] Philnicolls89:
Through twrp navigate to /data/adb and delete the module then you should be able to reboot like normal.
[Android Software Development] eustachy:
@Philnicolls89 - many, many thanks. You saved my day :)!!!
[Android Software Development] darkinside01:
Hi, im using (Mi9) rooted, installed fix 1.1.1 . but its not passed safetynet. how can i pas? thank u
[Android Software Development] alfred vierra:
Hi,

I have sm-a600n, installation failed cause ro.product.cpu.abi=armeabi-v7a on a10.

Do you have a plan to build for armv7?

Anyway, thank you for your great efforts.