yashsingh1/xdaforums huggingface dataset:
[Android Software Development] aaanonymous:
Works on Motorola Moto G Power XT2041-4 (sofia) running latest stock Android 10 rooted with Magisk 21.4 . Passes SafetyNet and Magisk Hide works perfectly. (y) (y):) Cheers to the developer and this forum 👌

UPDATE: Seems to work well with either "safetynet-fix-v1.1.1.zip" or "safetynet-fix-v2.0.0-test2.zip" Magisk module installed. Passes SafetyNet with either module without the need for the "MagiskHide Props Config" module.

For Root to be blocked from detection by all my selected financial apps, "MagiskHide" and "Hide Magisk Manager" must be enabled, with either Magisk module installed. Currently using the "safetynet-fix-v2.0.0-test2.zip" module.
[Android Software Development] flyl0:
It does not work even with MagiskHide Props on stock xperia 5II A10..

But that's not a surprise, usually all magisk modules that claim to pass the safetynet test never work.
[Android Software Development] PrussianWolf:
Xiaomi Mi Note 10 (pro) TUCANA, MIUI 12.0.4.0 QFDMIXM, Android 10, Security Patch 2021-01-01

Working! You did a great job, thank you! (y)
[Android Software Development] pndwal:
Never say never... this fix is pleasing most of the people most of the time... Of course, you just cannot please all of the people all of the time... neither @kdrag0n nor @topjohnwu. PW
[Android Software Development] PrussianWolf:
Xiaomi Mi 10 Lite 5G, Global, MIUI 12.1.2.0 RJIMIXM, Android 11, Security Patch 2021-01-01

Also working! You did a great job, thank you again! (y)(y)
[Android Software Development] jelbo:
I passed SafetyNet, but it messed up my biometrics. After adding another fingerprint, I could not re-enable biometric unlock in any app that asks for it after you add another fingerprint.

Disabled the module and it works again.
[Android Software Development] wyt18:
if you're on a samsung stock rom, use the modded zip from earlier in this thread
[Android Software Development] jelbo:
I found safetynet-fix-v2.0.0-test2.zip on https://github.com/kdrag0n/safetynet-fix/pull/13
[Android Software Development] BChamp:
Thanks for the module, great work on this one!!

Working on a S20 5G Ultra SM-G988N Korean Stock Rom with a Flashed U1 HOME_CSC on a T-Mobile network.

Unlocked bootloader running Magisk 21.4 (Stable) and Xposed (Canary) 5.2.0

Safetynet Passed

Google Play says device is certified

Thanks again!!💪🏾
[Android Software Development] BChamp:
Thanks for the module, great work on this one!!

Working on a S20 5G Ultra SM-G988N with a Flashed U1 HOME_CSC on a T-Mobile network.

Unlocked bootloader running Magisk 21.4 (Stable) and Xposed (Canary) 5.2.0

Safetynet Passed

Google Play says device is certified

Thanks again!!💪🏾
[Android Software Development] cosmicslice:
This is partially working for me. One banking app that was detecting root and refusing to stay open, after installing this fix is now working fine.

BUT, the safety check in Magisk is still failing on ctsProfile, and another banking app is still detecting root / safety-check failure (because it is still preventing fingerprint unlock).

Before mid-January these apps worked fine, so I must be affected by this Google change.

Details:

LG H850, LineageOS 16.0 (Android 9)

Root software: Magisk + MagiskManger + Busybox + MagiskHide Props Config + this fix. MagiskHide enabled, and these banking apps explicitly hidden.

EDIT: Uninstalling Magisk solved biometric issues, so issue is with MagiskHide.
[Android Software Development] cubandanger05:
Pixel 7a, android 14 rooted, V2.4.0 1.1 mod, passing both device and basic integrity
[Android Software Development] pndwal:
Try USNF 2.4.0 mod 1.3 + PIF 9.0+ to fix DEVICEINTEGRITY... (Nb. That USNF will work on its own, but that PIF should fix VoWiFi etc on devices launched with A13+)... 👍 PW
[Android Software Development] cubandanger05:
Apologies, I meant everything is working thus far.
[Android Software Development] pndwal:
Oh... you said passing BASICINTEGRITY which is only first of 3 levels and not enough for banks... Guess you meant DEVICEINTEGRITY which is enough for all I know of... BTW, you can edit posts! (May benefit/prevent confusion for P7 series users.)

Also, might want to check VoWiFi and note what I said about it...

... Did you mean "Pixel 7a, android 14 rooted, V2.4.0 1.1 mod + PIF 9.0 passing DEVICEINTEGRITY"? 🙂 PW
[Android Software Development] cubandanger05:
Yes, passing both. I edited my post.

Also, calls over wifi works
[Android Software Development] Sandbird:
I have an old Xiaomi Redmi Note 5 Pro still running Android 8.1.0 (spoofed as a Pixel XL using MagiskHidePropsConfig, to allow AR services). Yesterday i noticed that i am not passing SafetyNet anymore (used to run safetynet-fix-v2.2.1). I tried the latest 2.4.0, but it didnt work. On top of that i keep getting crashes on Google Play Services now.

Is there any hope for my little device?

Thanks
[Android Software Development] biTToe:
PIXEL 6 PRO

after the upgrade to A14 (rooted 26300-Stable), USF v2.4.0-MOD_1.2 (kdragon) no longer allows my Barclay banking app to function.

Basic intetgrity & CTS all pass

There are no other issues.

Google pay still functions

BofA banking still functions

I use the deny list, but I think i read somewhere that it was no longer necessary?

I have not tried hiding Magisk yet. Is there an updated, or better, version of USF?
[Android Software Development] Nergal di Cuthah:
Go up to at least mod 1.3. I'm using mod 2.0 with no problem on my p6p android 14 but don't use vowifi so not sure if it's bugged (as it is for some 2.0 users)
[Android Software Development] CSX321:
Yes, I'd also recommend using mod 1.3, and definitely hide the Magisk app.

I updated Magisk to 26300 and SNF to mod 1.3 while still running Android 13, then re-hid the app and did my usual update process to install Android 14 just this morning on my P6:

Extract boot.img from the update ZIP

Push it to my phone

Patch it with Magisk

Pull the patched image back to my computer

Rename it to boot.img and replace the original in the update ZIP

Remove -w from flash-all.bat

Reboot to bootloader

Run flash-all.bat

Everything went perfectly smoothly.
[Android Software Development] inzaghi89:
Updated few minutes ago my wife phone, and all works well. Displax mod 2.0, latest Magisk. But I'm using magisk hide and changing app name. Without that some app doesn't work.
[Android Software Development] arkzok:
Thank you very much, it works!
[Android Software Development] Exbadboy:
Hi.

Excuse my ignorance but what is PIF 9.0+ as i need my "VoWIFI - Wifi calling" back if possible.

Any help would be appreciated.
[Android Software Development] Nergal di Cuthah:
🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Android Software Development] Exbadboy:
Thank you for the quick response. Will that help bring back wif calling on android 13?
[Android Software Development] Nergal di Cuthah:
In combination with mod 1.3 yes. I believe, though don't know because i don't use vowifi, that mod 2.0 is what breaks wifi calling. I use mod 2.0 with no issue (on android 14 but pixel 6p so didn't ship with 13+) but do not, as i stated, use wifi calling.
[Android Software Development] pndwal:
For devices launched with A13+, in addition to mismatched prop requirements for earlier devices, ie model and fingerprint props, shipping API level must be charged from 33+ in order to bypass server end hardware-backed verdict enforcement, and a setting of 32 generally works fine...

@Displax 2.4.0 mod 1.3 sets this correctly but globally which is what breaks VoWiFi on some P7 series (+ other?) LV A13+/API 33+ devices...

His 2.4.0 mod 2.0 (experimental STRONGINTEGRITY fix using P2 fake STRONGINTEGRITY pass exploit) sets value to 'nul' which simply doesn't work anymore despite targeting GMS Droidguard process...

Solutions like PIF (also a USNF fork) that set all 3 required prop mismatches (spoofs), ie model, fingerprint and shipping level props, to target the GMS Droidguard/attestation process avoid breaking device specific functions like VoWiFi...

🤠 PW
[Android Software Development] Toast555:
hello everyone, can you help me, my phone can pass the safetynet with you module, but if i select google play services at lsposed module make safetynet fail, how to resolve that, help....
[Android Software Development] Homeboy76:
Use Diplax's Safety Net Fix v2.4.0-MOD_1.3
[Android Software Development] Dj Telo:
Hi everyone,

I upgraded my P6 to A14 (UP1A.231005.007) last week and I was able to configure Wallet with all my cards using Safetynet fix 2.4.0 MOD 2.0. However, this morning something changed in my phone and Wallet has started complaining that I cannot use it anymore due to my software being blablabla, you know.

I tried clearing data of Play Services, Play Store and Wallet, plus reinstalling the Safetynet module, but Wallet keeps complaining.

Any suggestions to fix this?

Thanks in advance, have a nice day!
[Android Software Development] Lada333:
Same thing happened to me, hopefully the community is going to be able to figure out what Google has changed so we can get around it.
[Android Software Development] chiteroman:
🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Android Software Development] crok.bic:
Systems are failing to pass checks (even with your module) from today morning.
[Android Software Development] chiteroman:
For me it's working.
[Android Software Development] crok.bic:
For lots of us it is not. Out of ~20..30 PI API checks perhaps only one goes through OK (Device && Basic) thus device is remaining non-certified and Wallet and related services are all failing, too. Check your own thread, people are complainig since this morning.
[Android Software Development] Homeboy76:
<< Deleted >>
[Android Software Development] Lada333:
And, as per usual, the community is already at least 17 steps ahead of me. Thank you for your quick help!

I remembered reading in a Telegram group somewhere that there's a "new" safetynet fix, but obviously simply Googling "xda safetynet fix" only brought this old large thread up.

What did Google change this time around that requires an updated safetynet fix?
[Android Software Development] Homeboy76:
Use Play Integrity Fix Latest version
[Android Software Development] Lada333:
Have you cleared cache of all relevant apps & made sure that everything is on the DenyList that needs to be? I had set up my phone about 3-4 months ago, have not touched Magisk since -- I checked the DenyList now, and there are tons of new switches within Play Services & Wallet (at least for me, maybe it's all irrelevant though)
[Android Software Development] crok.bic:
Like I mentioned in #4,004 it doesn't work for lots of us.

If I delete the data and updates of Google Play Services and Google Play Store completely then the first PI API check always tell me that there was an error with the test, the next one goes through with Device and Basic integrity OK and from the third checks it is behaving like out of around 20..30 PI API checks maybe one is okay, all the rest fails, even Basic.. (for testing I'm using the Play Store integrated check).

I used Magisk v26.4 && only the chiteroman PlayIntegrityFix v12 (the latest at the moment, released 17 hrs ago).

This is not only for me but I can confirm at least 2 of my own devices and other users, too.
[Android Software Development] Dj Telo:
Thank you very much. Working again for me.
[Android Software Development] pndwal:
Read post before yours...

...You too! PW

Edit: HaHa.. I didn't read posts after... See you got it from the horses mouth now... 😜 PW
[Android Software Development] matrix200200:
I have Lygisk 25.200 and safetynet displax mod 2.0.

Should I uninstall it, install Magisk 26.3 and then the playintegrity module?

Phone is Galaxy S10E with Lineageos 19

EDIT:

Nevermind, I installed the playintegrity module and wallet is working again.
[Android Software Development] old_fart:
Thank you, sir !

Please be advised there is a minor update / fix so it is now 12.1

Releases · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Android Software Development] Homeboy76:
Thanks, I edited most of my post and changed the version to

Latest version

.
[Android Software Development] gentano:
thats why you should never link to a specific version except your post is related to an older specific version for certain reason
[Android Software Development] rombad:
Thanks, my wallet is working again:)
[Android Software Development] xvcf:
The PlayIntegrityFix isn't working for me either, I know why tho. It's because of LSPosed for me, if I enable it, YASNAC (yes, I do know, that it's deprecated) and PlayIngegrity fail. If you dont need LSPosed, try turning it off, until someone finds a fix.

The module works fine then.
[Android Software Development] Nergal di Cuthah:
Did you try yesterday's pif 13 (google flipped another switch and broke 12.x). But yes lsposed can cause great issues. I never moved to it when i got my p6p (i had xposed on my 2xl but was still rocking android 8 i think)
[Android Software Development] xvcf:
Thank you, this worked. Didn't see, that there was a new version. YASNAC passed, ChatGPT login for example (which somehow doesn't work without play integrity / safetynet) works as well. Thank you.
[Android Software Development] xvcf:
Well, this is quite weird. The first test passes, PlayIngegrity works, as soon as I run the second test, it fails. Same with YASNAC. I ran both of these tests with maybe 5s delay. I've read that this can be related to LSPosed as well, I dont wanna uninstall it tho.

First test:

View attachment 6034308

Second test (not even 5s later)

View attachment 6034310

Edit: if I reboot, one test passes again, then it fails.
[Android Software Development] crok.bic:
I experience the same phenomenon on Xiaomi.EU ROM (w/o LSPosed).
[Android Software Development] xvcf:
Hmmm, quite weird. Im on a Nothing Phone (1), EU as well and everything works fine without LSPosed for me.
[Android Software Development] Lada333:
I suggest you read some of this thread and try to find answers there. This current thread (USNF) seems to be dead/abandoned.
[Android Software Development] Jeetu:
Hello

I have installed Universal Safetynet Fix v2.4.0 MOD and in YASNAC both Basic and CTS profile bypass.

The real problem is my google account is showing aa login in Google Pixel 2 but my phone is Oneplus 9 Pro.

Anyone know what’s this?
[Android Software Development] xvcf:
If you use Pixelify GPhotos (what may be the case since you installed LSPosed and its a well-known module), make sure you turned on "Only spoof in Google Photos":

View attachment 6034422
[Android Software Development] Jeetu:
No, I have never installed or used this Pixelify GPhotos.

This happened only after flashing this Universal safetney fix.

Android 11.
[Android Software Development] Lada333:
Stop using USFN, use PIF instead.

Why is it a problem that Google thinks your device is a Pixel instead of a OnePlus?
[Android Software Development] Chris_Kaos79:
Safety.net is in January 2024 obsolete. All Apps will use Play Integrity in two Months as the Security-Check. Google set the last Date and Safety.net will get deactivated then.
[Android Software Development] xvcf:
Read that its January 2025 somewhere 🤔
[Android Software Development] Chris_Kaos79:
Only if you don't Update the concerning Apps.

January 2024 is the Deadline: https://developer.android.com/privacy-and-security/safetynet/deprecation-timeline
[Android Software Development] crok.bic:
Here: SafetyNet Attestation deprecation timeline

End of January 2024

Migration deadline (timeline extended)

If you have migrated to the Play Integrity API, SafetyNet Attestation will continue to work on the former versions of your app. You can still detect risky interactions with the previous versions of your app. If you have not migrated, SafetyNet Attestation will no longer work for your app (including the previous versions) and return an error. We will consider that you have migrated if your app calls the Play Integrity API in production.
[Android Software Development] VFL:
Anyone know or maybe know that browser app for connected app..I don't remember wiche Browser app for smstan,

My insurance app "Barmer app" is working with Xiaomi with mi browser and it passed, but when use aosp it have root detect with chrome, I only know that one browser passed don't remember wiche one. That same way for other banking app who use smsTan like for N26 banking app need to connected with browser without root
[Android Software Development] Jeetu:
I have removed USFN and installed PIF.

Now if I login gmail account or any other app login it detects my device as LG Nexus 5X with PIF.

same issue in USFN the device was detect as Pixel 2.
[Android Software Development] zgfg:
Modules spoof you phone model as shown to /com/google/android/gms

As needed to downgrade Play Integration attestation from Strong to Basic
[Android Software Development] Lada333:
I don't see why that is an issue at all. Did installing PIF solve your issue or not?
[Android Software Development] Jeetu:
NO,

Earlier in USFN the devices was detected as Pixel 2 XL but i have removed USFN and installed PIF now the device is detected as LG NEXUS 5X.
[Android Software Development] schmeggy929:
That's not what he is talking about. Are you passing Basic and Device Integrity?
[Android Software Development] Nergal di Cuthah:
Google flipped another switch today/yesterday. basically only a few are passing device any more. See the play integrity fix thread. . If you dare.
[Android Software Development] Mowca:
When I add it to the Google Play service deny list in Magisk, after a while it deselects itself. Why is this happening?
[Android Software Development] Lada333:
USNF is outdated, use Play Integrity Fix.
[Android Software Development] Lughnasadh:
It's designed to do that so not to interfere with the mod.

safetynet-fix/magisk/post-fs-data.sh at master · kdrag0n/safetynet-fix

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

github.com
[Android Software Development] Mowca:
I installed it. It's better, but Play services are still deselects itself. But the McDonald app is already working. It didn't work before
[Android Software Development] simplepinoi177:
Just be aware that, most likely after New Years Day, unless you implemented your own custom fingerprint, Play Integrity Fix module (without some "tweaking") will not be enough and you will fail MEETS_DEVICE_INTEGRITY; hence the McDonald's app. Play services sometimes needs to be clear data to get things working right again (this will remove any cards from Wallet; maybe some other undue effects).
[Android Software Development] Nergal di Cuthah:
Yes this is as designed. For the spoof to work play services must not be denied (this is my understanding at least)

As far as the second screenshot. Playstore takes a little while (in day(s) i believe) to recertify.
[Android Software Development] Lughnasadh:
I already answered this in the post directly above yours.
[Android Software Development] osm0sis:
🤔

What do you mean you wonder? It's open source, go look.

I've actually done the code comparison, the Magisk module scripts were taken whole from USNF, which I told you (and which is why I credit USNF for them in my fork's README), but the Java code is all new/rewritten from the USNF Kotlin, and the Zygisk C++ code is new/rewritten as well. The only similarities I noted in the Zygisk code seem to be just basic Zygisk boilerplate initialization/injection/companion code.
[Android Software Development] mortmaru:
I do not see any option of import or even the word blacklist.

If you could give step by step guide?

thx
[Android Software Development] pndwal:
The post above was a attempt to explain properly why GMS processes are removed from denylist at boot and why I personally question the value/need for this function that only serves to protect users from themselves (their own lack of understanding) anyway, and more so now since users should not be in the habit (since Riru based USNF) of adding GMS processes anymore (unless attempting to pass PI verdicts without PIF)...

I didn't mean to contact what you told me; I fully concur with your reasoning re. why this is not a fork any longer (and thanked your post) and credited you for the pains you took to point this out recently...

The reason I said "but I wonder if much of it is still identical" was because of the identical behaviours... Perhaps I should have said the code may be "similar"...

For the purpose of GMS process removal from denylist (which behaviour I explained goes back to the beginning of Zygisk based USNF and has been inherited by PIF), some "similar" code found in post-fs-data.sh (used by both solutions) is of course:

USNF:

# Remove Play Services from the Magisk Denylist when set to enforcing.
if magisk --denylist status; then
magisk --denylist rm com.google.android.gms
fi

PIF

# Remove Play Services from Magisk Denylist when set to enforcing
if magisk --denylist status; then
magisk --denylist rm com.google.android.gms
fi

... Sure it's not identical, but I had to look hard! 😜 PW
[Android Software Development] osm0sis:
Again, as I told you before and told you above, those scripts are literally cut and paste from USNF. They were identical before I rewrote them for resetprop_if_diff and resetprop_if_match.

See here:

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com
[Android Software Development] pndwal:
I think you're missing my point; I have no issue with yours...

Perhaps if I rephrased it just a little it'd be better?:

🤔 PW
[Android Software Development] osm0sis:
But don't wonder, go look. There's no need to have any uninformed supposition with open source. 🤷‍♂️

And the scripts aren't the code, and I told you the scripts were the same, so it should be literally no surprise that they're "virtually" the same.
[Android Software Development] pndwal:
Fair enough... But I meant I know functionality is s the same... I shouldn't have equated that will identical/similar code, sure...

Of course it shouldn't!... And I did say "portions of script"...

Ok, this then:

🤷‍♂️ PW
[Android Software Development] osm0sis:
For accuracy, and to avoid further misinformation:

chiteroman's PIF module was originally a fork of USNF so its behaviour at that point was almost exactly the same... Now, its older commit history has been removed (several times), but osm0sis confirmed that the current Java and C++ Zygisk code was completely rewritten from scratch (to target only DroidGuard for the device spoofing), so it's no longer a USNF fork. However, osm0sis also confirmed that the Magisk module scripts for during installation, and that run at each boot to change properties which are safe globally, including doing GMS denylist-removal (for user protection) were taken directly from USNF and have only had minor changes since.