yashsingh1/xdaforums huggingface dataset:
[Android Software Development] kudichode:
Well hey there ya go, glad it worked out for you. Does safetynet/gwallet work out of the box? Haven't ran a custom rom since the days of Cyanogen 😅
[Android Software Development] xSnowLeopardx:
Got my OP11 bricked (no idea where my luck is...)

Currently in the process of unbricking it.
[Android Software Development] swieder711:
I have two devices, Pixel 7 Pro and Pixel tablet. Both are running stock A13 with root, USFN_1.3, Zygisk and Shamiko. Both devices pass Safetynet. Starting today, my corporate Outlook (and Slack, Onedrive, Teams) are detecting ROOT. I tried clearing cache and memory, but that didnt help. My P7P still lets me run corporate Outlook.

I plan to do a full wipe next week with the next Android drop. In the meantime, are there any suggestions?
[Android Software Development] Nergal di Cuthah:
Update your usnf to the latest displax version (2.4.0 mod 2.0 i believe)
[Android Software Development] swieder711:
I thought the current recommendation was to run USNF_1.3 due to a recent change by Google.

I am going to try rolling back Intune for an earlier release. Anyone seeing corp apps now detecting root?
[Android Software Development] Nergal di Cuthah:
Only change i know is pasing strong was possible with it but google fixed a serverside problem which stopped strong from passing, there are still fixes in mod 2 that make it preferable imho
[Android Software Development] pndwal:
Passing strongIntegrity with the Pixel 2 fingerprint anomaly also required that shipping level wasn't set to 32, so this prop adjustment (usually needed to bypass server end hardware-backed verdict enforcement for A13 launch version devices) was charged since the P2 crock was faking the pass as a hardware-backed evaluationType one anyway...

That's why the 2.4.0 mod 2.0 fix broke for all devices launched with Android 13, but still works for others...

Nb. 2.4.0 mod 1.3 still sets shipping level globally so VoWiFi (and other functions?) is broken for many P7 series users, but @Displax said he will produce a fix (with the spoof targeting GMS) eventually(?!)

👀 PW
[Android Software Development] swieder711:
EDIT: Rolling back Intune Company portal to 5.0.5926 allows me to prevent corporate apps from detecting ROOT.
[Android Software Development] arkzok:
Samsung Galaxy Tab A7 Lite SM-T220 Android 13 not working. Zygisk enabled, denylist enforced, Magisk app hidden, MagiskHidePropsConf installed, still not working. Testing with YASNAC.
[Android Software Development] chiteroman:
Uninstall safetynet-fix and MagiskHidePropsConfig and then install my module: https://xdaforums.com/t/module-play-integrity-fix.4607985/
[Android Software Development] Iridule:
I'm using USNF mod 2.4.0 1.3

moto edge (2020) all seems ok yet Androidacy shows update though Magisk does not. All seems to still be working well on Android 11. Should I still update?
[Android Software Development] zgfg:
Usually, if things work for you, don't change. But if you scroll back, you will see that this module is not up-to-date with what Google did in the meantime and ppl left for Displax USNF fork (another thread) or alternative module Play Integrity Fix (separated thread). Links can be found in the posts or by searching on XDA or by googling
[Android Software Development] Iridule:
My usnf is mod by displax.

View attachment 6005045
[Android Software Development] pndwal:
For you either @Displax Mod 1.3 or latest 2.0 should be fine, but 2.0 was experimental, does use a different (Pixel 2) fingerprint prop and it's Shipping level prop setting breaks the fix for devices launched with A13 like Pixel 7... The props set by either of these affecting your device are set to target GMS properly however...

@chiteroman's newer PIF module (based on USNF but renamed) presumably sets shipping level for LV A13 devices to target GMS so should be better for Pixel 7 and other A13 launch version devices... @Displax Mod 1.3 sets it correctly to 32 but globally which breaks WiFi calling and possibly other features...

Others reading this; Note that the official module (this thread) has been largely broken for some time...

👀 PW
[Android Software Development] R0298:
I don't pass the CTS profile match test. How can I fix?

Motorola edge 30 fusion with Android 13
[Android Software Development] zgfg:
First of all, if you are still on the old KDragon's USNF module - better please read just like two or three last pages and you will see that you had to move to the USNF fork from Displax or Play Integrity midule - they have their own threads with downloads

If it won't help, then which Magisk version you have, which modules, and if you have LSPosed, which LSPosed modules you have installed- some modules may collide (like MHCP, XPrivacyLua, Lucky patcher and so)

If you have custom ROM and if that ROM runs SELinux in Permissive mode - you're in troubles again

Etc - just the question "not passing CTS" cannot be decisively answered

Btw, SafetyNet is deprecated and you should download from Playstore and test Play Integrity API (Checker).

There, you need to pass Device and Basic Integrity - don't ask or expect to pass Strong Integrity (for that, phone must run stock/official firmware with the locked Bootloader)
[Android Software Development] Wip_:
Hello, after rooting a nexus 6P, using magisk and twrp i still dont pass the cts profile match on YASNAC, after downloading and activating safetynet fix and rebooting my phone the google play services crashes again and again with the message "google play services has stopped working" & "google play services keeps stopping". I have not been able to find much. is there a known fix for that ? running 8.1oreo, magisk 26.3 and latest safetynet fix from github.
[Android Software Development] casouzaj:
I recall having experienced Google services crashing for no reason in my wife's Xperia XZ2, running LineageOS 20.0. Don't know why, but after I installed Shamiko, such nasty behavior stopped. Just my 2 cents.
[Android Software Development] Nergal di Cuthah:
Yasnac checks are outdated and have been replaced by play integrity (pi). However i think you won't pass both needed in PI either.

Instead of the latest from this thread try displax's mod or Play integrity fix. Either may fix your issue

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699//unread

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix-updated-fork.4607985/
[Android Software Development] klemi71:
Answer was already given, sorry
[Android Software Development] pndwal:
You can use modded USNF (as suggested above) but don't really need it for Angler... Clue: 6P launched with 6.0 Marshmallow...

For you, (Angler on stock A8.1?) just adding Google Play Services Droidguard/attestation (com.google.android.gms.unstable) process to denylist and installing MHPC module to reset any 'sensitive' props to non-suspicious values (no need to configure it; does this by default) should get both S/N ctsProfileMatch and PI deviceIntegrity passing.

🤠 PW
[Android Software Development] Wip_:
Hey, so turns out it was that easy, i saw USNF from displax but thought it was basically the same thing.

Thanks a lot.
[Android Software Development] pndwal:
Woops... I meant "and installing MHPC module to reset any 'sensitive' props to non-suspicious values..." above... Corrected... Alternative to using USNF at all... 🙃

Also, Official @kdrag0n USNF has been broken/unmaintained for some time... The newer forks including PIF come with needed fixes. 👀 PW
[Android Software Development] Wip_:
So, i do pass yasnac test and i can access apps that are blocked of you dont pass safetynet even tho the play integrity api checker tells me device integrity fails.

I've also been running into another issue about making my root /system rw but ig its not the right place to ask.

Ill look into mhpc as well, thanks again
[Android Software Development] ZerkerEOD:
I just installed this from the old v2.0 mod 1.2 and it broke my CTS profile and I can't figure out how to get it back. I confirmed google apps like play services, play store, and framework are still on the deny list, I went back and removed storage from those apps but it still failed integrity. Any ideas why? Also this is on a Pixel 7 Pro.

Even though, I keep deleting my storage for play store it keeps me logged in, not sure about that.
[Android Software Development] Wip_:
Hey, you could try these two mods as replacement.

As said above by another member, this safetynet fix has been unmaintained and has serious issues.

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699//unread

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix-updated-fork.4607985/
[Android Software Development] ZerkerEOD:
After a few reboots I got the CTS profile back but still can't hide root from Intune.
[Android Software Development] eXtremeDevil:
Hi, I recently had to reset my device. I'm using and old Android 10 xiaomi.eu ROM (MIUI 12). I've always been able to pass SafetyNet CTS on BASIC mode with USNF 2.4.0 (official, not MOD), but, since the flash, no matter what I do or try, YASNAC always report fail, and the CTS in on hardware_backed mode. How can I change from "hardware_backed" to "basic"? Anything I can manually check to confirm the module is working properly?

Thanks!
[Android Software Development] zgfg:
No wonder if you're using this outdated module

Please scroll back to read about the up -to-date forked modules and test with them
[Android Software Development] eXtremeDevil:
@zgfg I know it's outdated, but yet it was working for me. In any case, forgot to mention, I've also tried MOD 1.3, MOD 2.0 and PlayIntegrityFix 8.8. Still hardware_backed.
[Android Software Development] zgfg:
Try PlayIntegrity Fix v8.7 - for me , for Xiaomi.eu 12.5 that one works but v8.8 does not (I have reported to developer)

When his PIF module does not work then catch the logcat from Terminal Emulator by:

su -c logcat | grep SNFix

Or from ADB by pretending to that command:

adb shell

Start the logcat before you test PlayIntegrity and/or SafetyNet

Send that log to developer to his thread or to GitHub, describing the phone and ROM

AFAIK, that is described on his GitHub project and in his OP post #1 in the XDA theead
[Android Software Development] eXtremeDevil:
HOLY ****, that works! I still can't understand how it worked before and not now with the exact same conf, but if 8.7 doesn't break anything, I won't complain xD
[Android Software Development] zgfg:
See the post:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix-updated-fork.4607985/post-89083419
[Android Software Development] eXtremeDevil:
I see, seems we're stuck with 8.7 from the meantime. In any case, I can't get it out of my head the fact that I used to be able to pass BASIC verification with the USNF 2.4.0 original module. What could have changed, just by reflashing the same ROM?

EDIT

Could it be the play services update from yesterday, October 3?
[Android Software Development] zgfg:
You can easily check when your Play Services updated last time

But please read the discussions in the other threads, particularly about the architecture of PI API

Google does not need to update your local Google Play Services (GMS) - GMS is just a 'postman' or man in the middle

GMS downloads the latest droidGuard (the.apk - read there how and where you will find it)

droidGuard contacts Google servers and downloads the bytecode that actually does inspect on your phone

droidGuard then signs the data and sends to Google server that delivers back its signed JSon verdict

As you see, relevants updates happen on the Google's servers, not in your GMS

Btw, if you read back, you could see that most users migrated from this outdated module long ago, and/or, they continually do, forr many of them this module (or even the newer, forked ones) suddenly stop working and they must upgrade

Google developers work 24/7
[Android Software Development] pndwal:
May have simply been some change related to timing...

The issues with official USNF relate to new part-time hiding (only when GMS, specifically it's DroidGuard process, is called, ie "spoofing dynamically at runtime only when necessary") and related timing issues in 2.4.0. It worked partially, but generally with a small delay (would get failed result) after booting device and with intermittent failures after that... Worse on some devices than others... @Displax builds added several fixes for this issue... @chiteroman builds include these fixes also... I see he now has a cut down fix to use in tandem with @Displax fork builds. (I'd use with 2.4.0 mod 1.3)...

Official 2.4.0 was enough for some (many?) banks on some devices, but generally GPay/Wallet would always fail since that app accesses cached changes in 'security' configuration that is polled constantly in the background, (ie when app isn't running)... On opening GPay/Wallet, security requirements for contactless payments will show 'failed' as deviceIntegrity on startup was failing... (Other configuration changes, eg if device password/pattern lock was removed, contactless security check may fail even if it was only removed briefly and restored before opening the app.)

Other apps call deviceIntegrity verdict at runtime only rather than checking a cached result...

🤠 PW
[Android Software Development] eXtremeDevil:
Thanks both! In any case now we xiaomi.eu users have PlayIntegrity Fix 9.0 + USNF Mod 2.0 :)
[Android Software Development] Tianhe:
Confirming that installation of this zip fails. The original version (1.1.0) doesn't enable CTS pass on Android 9 (Zenfone Max Pro M1)

Temporary solution : Using a combo of MHPC + Safety Net Fix seems to be working.
[Android Software Development] fkofilee:
Works for me after updating to the new versions.

Installed over Magisk - Running Pixel 5 - Rebooted - Killed Google Pay and its now working again.

Using Basic Attestation to convert to Pixel 3a
[Android Software Development] zygorf:
Sorry, please ignore. I can't seem to delete my post but realised I overlooked the heavy OEM skin may not work part which MIUI clearly is.

Not working on Mix 3 5G Andromeda on Android 9 using stock ROM with V 12.0.2.0.PEMEUXM

changes attestation from hardware to basic but still fails unfortunately. I've tried toggling magisk hide and have no other modules installed.
[Android Software Development] pndwal:
Please say exactly what is configured in MHPC. 👍 PW
[Android Software Development] tylerdurden:
Still don't work, with or without using "MagiskHide Progs Config", forcing basic key attestation to Pixel 3a.
[Android Software Development] Tianhe:
MHPC Configs:

1) Forced BASIC key attestation.

2) Changed fingerprint to same device but later build.
[Android Software Development] zygorf:
Also works for Mi Mix 3 5g with Android 9 MIUI stock ROM for me using the following steps:

1. Install safetynet fix 1.1.0 in magisk

2. Install MagiskHide Props Config in magisk

3. Reboot

4. Run "props" in adb shell and chose option 1 to change device fingerprint. Changes to Mix 3 (non 5g) version. Android 9

5. Reboot

Now passes safetynet and Google pay works although not tested making a payment
[Android Software Development] pndwal:
@kdrag0n Many thanks for well implemented fix, and for your insights too.

Working beautifully on my Xiaomi Redmi Note 8T incl. G Pay.

For some devices (many custom ROMs, Chinese and other uncertified ROMs) users have flashed MagiskHide Props Config Magisk module to set a Certified fingerprint in props for some time now. My device above does not require this, but could you please say whether you module should work fine with such props applied systemlessly?

Also, when clearing data I noticed that Google Play Services and Google Services Framework are duplicated (one of the pair showing lock symbol over icon like Dual Apps) in Manage Apps. Please could you explain how this duplication relates to this fix (I'm assuming it does)?

Many thanks for such a useful mod(ule). PW
[Android Software Development] pndwal:
Thanks!

I'm curious if this will still work for you with fingerprint prop only...

This would both be better for you (new SafetyNet Fix doesn't spoof other model / alter props, so all device / OEM specific functionality should keep working), and it would also indicate that the 2 modules will play nicely together also for those with custom ROMs, Chinese and other uncertified ROMs that require spoofed fingerprint for ctsProfile and Play Protect certification.

Please let us know if you try. 👍 PW
[Android Software Development] Tianhe:
As far as I remember, I first tried only with forcing BASIC key attestation + safetynet fix combo which didn't work. I then changed the fingerprint and achieved success so your theory might hold true. Since this device is my daily driver, I will require some time to test out your theory.

Curiously, the fingerprint specimen which I used also belongs to the same device - just that it was a later build. Probably also the reason why I am not bothered about spoofing devices and breaking functionality.

N.B. - I also use Edxposed + SELinux permissive.
[Android Software Development] GROOVYJOSHCLARK:
Worked for me on pixel 4XL running AOSiP.

View attachment 5187031View attachment 5187033First thing I did was backup my SD (just in case), then I FULLY removed magisk (uninstalled), rebooted, installed the latest magisk app, redid my boot.img and enabled root. Rebooted then enabled magisk hide, and installed "safetynet-fix-v1.1.0.zip" along with props (only the two modules in my second pic).

I used the new safetynet fix with magiskhide and props config (using pixel 4XL with 11 fingerprint) with basic forced on my 10 ROM and it's back to normal. Screenshot shows the date and time (right now) with safetynet passed in the background.

You may not need to FULLY remove magisk but I did so because I was testing many modules so I didn't want to confuse things. I was also afraid of using a module that wasn't needed OR isn't confirmed safe (I tried a lot at first and all found on random internet searches). I felt it safest to wipe magisk data, delete all downloaded modules, remove magisk FULLY and start over safe and freshly.

Thanks for fixing this for us Android enthusiasts!
[Android Software Development] Seehank:
Guys I am sorry for asking a stupid question. But how do I get to the .zip file that I can install in Magisc? I know its in github and you all know what to do, but I am no programmer, so I really don't know if I have to pull and make or whatever... to get to the damn .zip file, or I am blind and there is link there that I don't see. Would someone please be so king and educate me on this?

Never mind I am stupid and blind... ITs here: https://github.com/kdrag0n/safetynet-fix/releases
[Android Software Development] pndwal:
Thanks for this info, and I quite understand.

Having said that, I'm fairly confident fingerprint is all you need, as 1) nothing changed w/ 'force basic', 2) it did w/ new fingerprint, 3) while ctsProfile changes introduced by Google apparently include 'under the hood' Hardware Key Attestation that functions irrespective of evalType reported and require a fallback method DIFFERENT from simple model prop mismatch, the new means cause both this 'under the hood' Attestation, as well as the H K Attestation affected by evalType to fall back to Basic in any case.

You are correct that you won't be spoofing a different device in fingerprint props (as it's same device but newer print), and fingerprint prop apparently won't often affect device functionality anyway.

Model prop(s) however definitely do, and since Force BASIC changes these you will necessarily be spoofing a different device here, even if you chose 'Default' setting for this. (Requisite mismatch won't occur w/ actual model selected!) Also, Default setting in MHPC usually causes more problems than one you might select as it is usually an older model without the latest added functions (eg proprietary code for high end camera functions, etc)

If you forgot which model you chose, or simply used 'Default', you can check what device you are spoofing simply by checking 'About Phone/Device' in Settings. (Nb. while model is selected from MHPC's fingerprint database, it does NOT simply use device for fingerprint selected as this wouldn't work unless using a fingerprint for a DIFFERENT device, as explained.) PW
[Android Software Development] dkryder:
I have a pixel 3a that has been failing since a google play services update earlier this week. I'm running stock Android 11 and magisk. I tried the 1.0.2 fix today and it worked. Thank you for your work.
[Android Software Development] abdominazer:
Worked like a charm.

Realme 6 device.

Thanks to the developer!
[Android Software Development] redymedan:
@kdrag0n Thanks it works on A50 SM-A505F with Unlocked Bootloader and Rooted. A cup of coffee from me :) This Tutorial is Clearly, I hope it will help you
[Android Software Development] jekyll86:
Not working on moto g6 plus with Android 9. Cts is still failing
[Android Software Development] GROOVYJOSHCLARK:
Did you do everything required (I.E. configure MagiskHide + safetynet-fix-v1.1.0.zip module + props module)? I then needed to change my fingerprint to my same device (its a pixel 4 XL so I chose Pixel 4 XL with 11) so I chose 11 fingerprint of the same device (but not 10 which my OS truly is), but I would start with the 3 things first. If that fails, then force basic with a fingerprint that works for your model/device. Make sure to reboot after setting it all up.
[Android Software Development] trisimix:
Working on pixel 4a android 10. Had MagiskHide Props Config with basic attestation forced (nexus 5) and gms dg.db set to read only (chmod 440) prior. Not sure if combination or just your module was the key but I am passing all checks and can go back to pentesting :P.
[Android Software Development] Tianhe:
That took me some time to process ! But of course, I agree with you on the points that I understand.

My device is Asus_X00TD running on Build WW-16.2017.1908.058.

The device fingerprint selected in the module is ASUS_X00TD WW-16.2017.2009.087

Since Force BASIC key attestation doesn't affect the final result, all I should have to do is upgrade to v87 firmware. Then I can ditch the MHPC module while retaining only the safety net fix module to pass CTS ?

BUT there's apparently a catch. Although I have selected ASUS_X00TD (Zenfone Max Pro M1) as fingerprint my "about phone" shows the device as ASUS_Z00LD (Asus Zenfone 2 Laser ZE550KL).

Final twist, when I delve deeper into "about phone" it changes from ASUS_X00LD to ASUS_X00TD !
[Android Software Development] zgfg:
Then, if you take Download latest, you must follow with Factory reset since you are going from custom ROM (LOS) back to stock
[Android Software Development] DJBhardwaj:
Have you enabled MagiskHide in Magisk Manager settings?
[Android Software Development] shortye:
Redmi Note 8 global (ginkgo) with Miui V12.0.3 (android 10) , used V 1.1.1 works :)

Thank you!
[Android Software Development] arifn82:
redmi k30 4g , crDroid rom, android 10 , version 1.1.1 works ! basic integrity and cts profile success.. thankyou sir!
[Android Software Development] Dante63:
Try this:

https://play.google.com/store/apps/details?id=com.chornerman.easycachewiper

And you need to flash data, not system because /data/system/ but that will erase your apps, how about dirty flash ROM?
[Android Software Development] BrimoFan123:
Thanks for pointing to this app but I have already did factory reset in Recovery and completed whole nasty procedure of making back my phone configured the way I need.

It took me few hours and this time I made a self-promise I will not touch anything that could lead to the similar disaster :-)
[Android Software Development] ASRock86Cro:
Works on my galaxy note 9 with stock android 10
[Android Software Development] Neverendingxsin:
GPay is finally working again on my Pixel 2XL running stock (December 2020 update) and Magisk 21.4 w/ Manager 8.0.7 thanks to this! :)
[Android Software Development] PaulPizz:
Works on the stock pixel 5. Nice work. Thank you! 👌👌👌