yashsingh1/xdaforums huggingface dataset:
[Android Software Development] pndwal:
Ok...

First, I'm assuming you have main (com.google.android.gms) and attestation (com.google.android.gms.unstable) Google Play Services processes in denylist (to hide 'root' from these)...

Many custom ROMs integrate @kdrag0ns Safety net Fix and passing device fingerprint, but this doesn't apply..

OnePlus has notoriously produced devices with broken keymaster implementation (processes keystore values in TEE OS) incl. the 8T, so Attestation falls back to Basic Evaluation type (trigger is exception caused by broken keymaster) and Hardware attestation is not enforced (based on device model prop in S/N API and both model and fingerprint props and possibly security patch level in PI API ) without the need for USNF fallbacks / bypasses...

Passing CTS Profile match still requires a passing device fingerprint (you have this on non China region stock ROM; custom ROMs may need to adjust props), and as long as no sensitive props are detected (NB. MHPC adjusts such detected props w/o any configuration if active so this is an alternative to running USNF, which also does this, where sensitive props are an issue), and it seems none are affecting your device - I believe it's more of a problem for legacy devices/older ROMs anyway -, and no other mods break device integrity, device security attestations will just pass!... 😋 PW
[Android Software Development] Vision:
Very strange, today Google play store show me again the Netflix and some other apps which had been missing since July, I don't have changed anything in my phone, I have Xiaomi Poco X3 NFC android 10, magisk 23 with magisk hide com.google.android.gms.unstable and module riru 26.1.3 and Universal SafetyNet Fix 2.1.1 by kdrag0n
[Android Software Development] dimm0k:
having some really weird issues where GPay and my Pixel 6 Pro tells me that it doesn't meet the right requirements for pay, yet I can still make payments by tapping... this was using the unmodded USNF 2.2.0. if i remove that and install the modded version, I still get the same quirk except in Magisk I see this update icon for this module even after rebooting. anyone know how to fix the update issue, as well as the requirements message?
[Android Software Development] 73sydney:
weird issues have been noted in the current times (even using the modded version), best is to not wonder why but bathe in the ability to still use thy contactless functions

ignore the Update icon.....
[Android Software Development] pndwal:
There's no issue... Icon is greyed out so there's no update... That'll change when there is...

Check you now have deviceIntegrity passing in Play Integrity API Checker.

This had probably failed prior to installing @Displax USNF mod/fork but Google has been turning new Play Integrity hardware attestation evaluation type enforcement on and off spasmodically for different devices and at different times lately...

If passing now G Pay/Wallet error message may just go away after some days...

For immediate fixes:

Clear Google Play Services data.

Clear G Pay/Wallet data and reboot before starting app again (important to avoid issues like Activity list failing to populate)... Take any updates and set up cards again as needed...

If you can't see G Pay/Wallet in Play Store, clear Play Store data then check Play Protect says Device is certified in Play Store settings...

🤠 PW
[Android Software Development] pndwal:
Play Store now relies on Play Integrity API since SafetyNet is deprecated and will hide many apps in store if deviceIntegrity verdict fails...

As mentioned above, Google has been turning new Play Integrity hardware attestation evaluation type enforcement on and off spasmodically for different devices and at different times lately...

It seems Google has simply reverted this enforcement for your device recently, but you should probably apply a bypass fix as it's likely they'll restore enforcement when they've sorted out any regression issues for your device...

Clearly you cannot use @Displax modded USNF version with Play Integrity fix with pre-Zygisk magisk. You can try @huskydg's Riru compatible mod here however:

https://github.com/HuskyDG/safetynet-integrity-fix

👀 PW
[Android Software Development] Vision:
Oh, understand, I have read about this, until now I'm little lucky until broke again and not see the apps, so now I see again the apps who hide it in Google Play from the July until post this
[Android Software Development] Vision:
I jinxed, now disappear again the apps from Google Play 🤣😂
[Android Software Development] YMatrix:
Hey

So I have been using the moded safetynet fix by Displax without trouble... Till now.

I had a Google wallet update and suddenly it has stopped working.

Tried tinkering with all options, using shamiko, but without success.

I am using this on my s20fe 5g on a custom oneui rom

Any advice?

Change device fingerprint?
[Android Software Development] pndwal:
Probably only need some resets...

As mentioned above, Google has been turning new Play Integrity hardware attestation evaluation type enforcement on and off spasmodically for different devices and at different times lately...

Check deviceIntegrity first; see here:

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

... Re. resets, scroll down and see 'Related Issues'... 👍 PW
[Android Software Development] matfcb:
Where can I download GPay-SQLite-Fix 2.8? It's not on Github anymore.
[Android Software Development] pndwal:
This:

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

😬 😝 PW
[Android Software Development] Exokan:
Hi, probably a dumb question... Pixel 6 on A13. Used USNF mod to get cards to work (works great!). However, I was previously also using MHPC to add a notethering prop. Can USNF and MHPC not work together because they're essentially both trying to modify the props and would conflict?
[Android Software Development] zgfg:
USNF is Zygisk module and targets only GMS service - thus avoiding potential conflicts with the other system apps (like fingerprint reader, etc)

Besides, USNF 2.3.1-nod is newer, adapted for the latest Wallet changes

It's been elsewhere recommended and countless times, to use USNF 2.3.1.-mod, without MHCP - unless you specifically need MHCP for something else
[Android Software Development] m0han:
I'm not sure, but maybe @Exokan still wants to know if USNF and MHPC can work together so he can get something else done ('add a notethering prop').
[Android Software Development] YMatrix:
So, like you said, I did some more tinkering - I Uninstalled Google wallet and they magisk safetynet module, reset Google play services and store and then did the process all over - success!

Google wallet working again... Till next time
[Android Software Development] Exokan:
So that was my confusion. I assumed that there may be some sort of conflict with USNF and what I was doing with MHPC (the notethering prop). I guess this would only relate to altering a fingerprint? I sorta was wondering why the two modules can't (shouldn't?) be used together. But regardless, I am now using both modules with no issue so far. Thanks for all of the input so far!
[Android Software Development] cheesepuff:
Okay, so safetynet passed, Google play is saying I'm certified, magisk is on hide,

But when I try to search some games in play they don't show up. I can still sideload them.

What am I doing wrong?

Sony Xperia 1 Mkiii stock rom
[Android Software Development] pndwal:
Play Store now uses Play Integrity API's deviceIntegrity and hides such apps if verdict fails... But Play Protect routine is still using old (deprecated) SafetyNet API...

Fix PI deviceIntegrity... PW
[Android Software Development] pndwal:
@kdrag0n recommends using MHPC in addition to USNF where ROMs fail CTS Profile check in his GitHub...

However @Displax recommends to disable/ reset MHPC w/ his USNF mod... Guess MHPC global fingerprint application may interfere, cause issues, isn't needed now etc...

There's no fundamental conflict between the two modules however... PW
[Android Software Development] 73sydney:
sheesh even i get confused and head hurty at that question, like which fingerprint wins if you have them both installed, the one from @diosplaxs USNF MOD or MPHC....

anyone?
[Android Software Development] ipdev:
I am not that familiar with the process (I might be wrong) but, I believe 'USNF-MOD' still only targets Play.

When attestation is called, it will return the Nexus 6P fingerprint instead of what is active on the device.

google/angler/angler:6.0/MDB08L/2343525:user/release-keys

With the USNF-MOD active, no fingerprints are altered.

- Pixel 6 July A12L -

oriole:/ # getprop | grep 'fingerprint'
[init.svc.vendor.fingerprint-goodix]: [running]
[init.svc_debug_pid.vendor.fingerprint-goodix]: [1056]
[persist.vendor.fingerprint.disable.fake.override]: [none]
[ro.bootimage.build.fingerprint]: [Android/gsi_arm64/generic_arm64:12/SGR1.220318.002.A9/8544043:user/release-keys]
[ro.boottime.vendor.fingerprint-goodix]: [4285834514]
[ro.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.odm.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
[ro.product.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
[ro.system.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
[ro.system_ext.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
[ro.vendor.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
[ro.vendor_dlkm.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
oriole:/ #

MHPC applies the fingerprint globally.

- Pixel 6 July A12L - Using May A12L fingerprint -

oriole:/ # getprop | grep 'fingerprint'
[init.svc.vendor.fingerprint-goodix]: [running]
[init.svc_debug_pid.vendor.fingerprint-goodix]: [1027]
[persist.vendor.fingerprint.disable.fake.override]: [none]
[ro.bootimage.build.fingerprint]: [google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys]
[ro.boottime.vendor.fingerprint-goodix]: [4329877198]
[ro.build.fingerprint]: [google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.odm.build.fingerprint]: [google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys]
[ro.product.build.fingerprint]: [google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys]
[ro.system.build.fingerprint]: [google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys]
[ro.system_ext.build.fingerprint]: [google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys]
[ro.vendor.build.fingerprint]: [google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys]
[ro.vendor_dlkm.build.fingerprint]: [google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys]
oriole:/ #

Save for 'ro.vendor_dlkm.build.fingerprint' for now.

If you set the fingerprint using MHPC and are using USNF-MOD, when attestation is called it will return the Nexus 6P print.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Android Software Development] Zibri:
On Redmi Note 10 pro, MIUI 12.5.9, with magisk and safetynet fix 2.3.1

I get the green only in MEETS_BASIC INTEGRITY...

YASNAC passes both tests but also says BASIC as evaluation type.
[Android Software Development] Zibri:
I think we should change approach...

Magisk has the footprint of an elephant.

Unlocking bootloader is easy to detect.

IMHO the best approach is to obtain a temporary root when needed.

That's because the situation will only get worse.

What if the play integrity will be checked by EVERY single app or the system itself?

We are soon going to have only two options: use the system as google and the phone oem wants or use it as we want but kiss goodbye to any relevant app.

Any thoughts?
[Android Software Development] pndwal:
What test is that?

Expected...

Nb. SafetyNet API is now depreciated and many apps have already migrated to Play Integrity API... If you don't pass deciceIntegrity API in Play Integrity API Checker you may need this Play Integrity fix:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

Some here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87548785

😝 PW
[Android Software Development] ScottIsMyName:
So the new Pixel 7 (and P7 pro) is failing Basic Integrity with the @Displax mod installed. Just putting it out there. Device Integrity is passing.

They both pass if the bootloader is locked.

Hopefully the smart people can get this figured out for us early adopters :)

let me know if I can provide any details or info that might help out.
[Android Software Development] Humpie:
Actually with the Displax mod (https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/page-91#post-87198517) it seems to work for me! While the safetynet check apps fail, Google Wallet somehow does work. Plus while before I couldn't even install Netflix, Mario Kart, Disney+ etc from the play store, I now can!

Make sure after installing that module to add everything to the denylist in magisk (Play protect service, play store, wallet/gpay, mario kart (or other games that check the safetynet), netflix, banking apps). Then wipe all the data of the play store and google play services. Opening the play store after this allowed me to download all apps again :)
[Android Software Development] ScottIsMyName:
I forgot to clear the cache of play protect services and I can confirm that I can now use Google Wallet and also install apps (netflix doesn't show up for some reason though? Disney plus does). I also don't see any message in google play store about the device not being certified
[Android Software Development] stroke55:
I can confirm this - it seems to be really depending on the denylist. I'm using USNF 2.3.1-MOD and Shamiko 0.5.2. Device integrity and CTS profile match are failing. I then cleared the data of Play Services and Playstore and rebooted but neither Netflix could be found on the Playstore nor the security-message in Wallet disappeared. I then added Playstore and Play protect to the denylist and Netflix showed up in the store while also the security warning in wallet disappeared. However, device integrity and CTS profile match are still failing and device is not certified in the playstore...
[Android Software Development] wugga3:
Fix issues with your Play Protect certification status - Android Help

If your device isn't Play Protect certified, Google doesn’t have a record of the Android compatibility test results. Keep in mind that: Devices that aren't Play Protect certified may no

support.google.com

Device ID - Apps on Google Play

Obtain Device/Android ID ,Google Services Framework ID, IMEI,IMSI,IP,MAC Address

play.google.com

Not sure how fast/quick this takes to be effective but it's how I became certified again... Then may also; once certified, take a few more moments for Netflix to be available again (can't remember...) Or it just might be immediately...

Hope that's resolves that

Edits: misread so may be this will help others or delete for off topic thx
[Android Software Development] Tokic:
Guys, is there a way I can make Revolut and similar apps work on my rooted Google Pixel 6?

After I unlocked bootloader, I cannot find Revolut in my Play store. After I somehow managed to find it, it says that I cannot install it on that device.

Later I rooted it, enabled Zygiys, enforced DenyList, configured it. I hidden Magisk, installed Univesral SafetyNet Fix and nothing helped.
[Android Software Development] stroke55:
Could you please check if your Wallet quicktile is "greyed out" showing "not available"? I can add cards but I doubt that I can pay with it.
[Android Software Development] aer0zer0:
View attachment 5733991
[Android Software Development] JakeDHS07:
Can confirm with proper denylist and fix wallet works on P7P despite checks failing in checker. Very odd. Not complaining though. I'll take it working for some reason than not 😅
[Android Software Development] Sasy969:
Hi guys!

I'm on CrDroid 8.10 for Op9 based on A12, i'm not able to add my credit card to wallet. I have already installed magisk, flashed the USF mod 2.3.1 and all the think suggested, but nothing seems to work. I pass the safetynet and Only the base integrety.

what can i do?
[Android Software Development] manueltimz:
there is a conflict this creates for users who use Lsposed.

Lsposed requres Riru

Riru doesnt work with Zygisk.

This tweak requires Zygisk

So its either have Riru or have this safetynet fix
[Android Software Development] Ryola:
Or install the Lsposed Zygisk module?
[Android Software Development] manueltimz:
cool
[Android Software Development] Ryola:
I Dm'd the link, if you need any help just ask
[Android Software Development] teddc:
This one claims to be a fork that support both Riru and Zygisk:

GitHub - HuskyDG/safetynet-integrity-fix: A workarround to pass SafetyNet / Play Integrity API on rooted devices with unlocked bootloader

A workarround to pass SafetyNet / Play Integrity API on rooted devices with unlocked bootloader - GitHub - HuskyDG/safetynet-integrity-fix: A workarround to pass SafetyNet / Play Integrity API on r...

github.com
[Android Software Development] Displax:
Hello again!

New Pixel`s 7 (Pro) have problems with CTS/DEVICE_INTEGRITY? - Not now! :p

Original post was updated. Now rebased on more correct @anirudhgupta109 commit.

Details: Commits

This update needed for all devices that shipped with Android 13+ in future, not only Pixel`s.
[Android Software Development] osm0sis:
Is_ever_orange needed to be set later in my testing, hence my placement in the script.

Would still be nice to specify which OEM ROMs the various hacks are needed for, so we're not losing documentation.

Wouldn't it be better to only change that new prop for SafetyNet/Integrity, not system-wide?
[Android Software Development] Displax:
Ok. Reverted.

As I know it shouldn't affect anything in system. Used almost only on CTS/VTS tests.
[Android Software Development] JakeDHS07:
The test zip you posted earlier works but the github mod2 zip results in pixel is starting loop. Not sure what the differences are but there is a problem with the second version. Had to put into safe mode and run adb command to remove modules to recover into system.
[Android Software Development] pndwal:
So another mismatch needed to bypass H evaluation type verdict enforcement identified. 👏

See we've gone fromAPI level 33 (A13) to 26 (A8, first version with requisite keymaster 3 for HKA) to level 32 (A12L) in first_api_level prop...

Just to keep track, we're now adjusting:

ro.product.model for S/N and PI (not all devices required this at least for S/N) [official USNF]

ro.build.fingerprint for PI (mostly A11+ devices initially required this) [@Displax mod fork], and now

first_api_level for PI (A13 launch version devices require this) [@Displax mod fork]

in order to bypass Hardware evaluation type verdict enforcement. (Nb. The enforcement bypass as well as triggers needed are different from fallback to Basic evaluation type itself and it's trigger method...)

Thanks! (May be refined further per issues above I guess...) PW
[Android Software Development] pndwal:
Wot's base integrety'? PW
[Android Software Development] pndwal:
Fixed per @Displax's post above? PW
[Android Software Development] pndwal:
Check passing PI deviceIntegrity, clear Play Services and Play store data... This should resolve Play Store restrictions... If not passing, have you installed @Displax's mod fork of USNF module?

To use app, put App in denylist and clear it's data...

If more hiding is needed you can substitute denylist for Shamiko (read Zygisk hiding(not perfect) + MagiskHide restorer (enhanced)).

You'll need to do this also before trying other strong hiding methods that rely on injection into zygote... In thinking particularly of Hide My Applist LSPosed module. (It won't have desired effect w/ denylist active as that reverses / blocks all modifications to apps in list whereas Shamiko allows these like old MagiskHide.)

For basic hiding, wipes needed etc however, principles here:

https://xdaforums.com/t/...agisk-discussion-thread.3906703/post-87481637

🤠 PW
[Android Software Development] 73sydney:
i couldnt even break anything because he pulled the download :)

whats this world coming to....when someone pulls a zip file denying users from borking their devices...
[Android Software Development] pndwal:
Yup, pulled original mod w/ first_api_level fix due to @osm0sis' testing per his comments...

Seems Main post was updated w/ same fix but w/ Is_ever_orange change reverted, so link there still works fine...

I think you may still be able to break something with this if that's your aim; you just may need to try harder! 😝🤪 PW
[Android Software Development] zgfg:
'New' versions of LSPosed (since the time when Magisk v24 with Zygisk was released - hence over a year ago) are Zygisk-LSPosed.

Hence nothing to break but go up-to-date

See the screenshot

Download link:

Releases · LSPosed/LSPosed

LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.

github.com
[Android Software Development] manan001:
Recently oneplus 7T got android 12.1 stable build. After the upgrade fingure print unlocking was broken. Later after doing some finding i came to know need to diable

Universal SafetyNet Fix 2.3.1. Doing that restarting phone i was able to use fingure print scanner unlocking.​

But now app have started detecting root. I request if this can be fixed quickly in new release or any workaround please suggest.
[Android Software Development] zgfg:
You didn't say which app. But if related to Wallet (or any other app that uses the Google's new Play Integrity API - successor of SafetyNet), you should install safetynet-fix-v2.3.1-MOD.zip

It was released in this thread several months ago, but from a different developer, Displax - sorry you will need to search yourself for his post, but the same has been mentioned in many other posts, and some of them may have a link to his post with his attached zip
[Android Software Development] osm0sis:
Just double-checked my notes, and it was actually fine having is_ever_orange in system.prop. My bad. That's where I had it originally in my PR. 🤦‍♂️🙃

Should be fine to put it back. Not sure why it was moved in the first place. 👍

magisk: Add circumvention of OnePlus' oem unlock counter · Displax/safetynet-fix@d2676e1

- 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...

github.com
[Android Software Development] Displax:
Moved out again 🙃👍
[Android Software Development] Annil:
@Displax : whem using the "original" 2.3.1 by kdrag0n in YasNac everything passes (Basic integrity and CTS Profile match).

WIth the latest MOD 2.0 from you the CTS Profile match fails (and root is getting detected). Where am I missing a step? (background is, several banking apps stopped working in the past few weeks without any update from their side, but google stuff got updated....).

Play Integrity Check now also fails with the latest version. Basic is fine, but device integrity is not.
[Android Software Development] roirraW "edor" ehT:
@Displax Thanks again for your work. I've had 4+ 6/8/10 (who knows now) users so far in my Pixel 7 Pro thread starting here, and additionally including myself, which don't have success passing with 2.3.1 Mod 2.0, but do have complete success with the 2.3.1-test. For this reason, another user has re-posted your test version in my thread here. I hope that's okay with you. If not, please let me know and I'll get the attachment taken down.

And please advise, otherwise. Cheers!
[Android Software Development] justDave:
@Displax Looks like you were the victim of DOS line endings (and probably rushing out a quick fix). I stripped the CRs from service.sh and MOD_2 is working for me. Thanks for doing the heavy lifting!
[Android Software Development] Displax:
Oh God... Thanks man. Reuploaded now... 😵‍💫