[Google Pixel 7 Pro] pndwal:
Yup... Aside from the trigger to cause fallback to Basic attestation evaluation type (fake keystore provider registered, causes exception that triggers fallback), we now need 3 separate mismatches to also disable enforcement of a hardware based verdict. See this:

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

The second is @Displax's first addition, needed for many (especially A11+) devices to pass PI deviceIntegrity, and targets the GMS attestation process (com.google.android.gms.unstable) only with (Huawei) angler (Nexus 6P) fingerprint prop, (ro.build.fingerprint), using a very low API level (Android 6.0) print to ensure no device using the fix has a matching API level... Also, using old prints negates the need to match print with security patch date in order to pass CTS Profile match... See:

Drop fingerprint to lowest possible …

To ensure that no one use same Android version

- Original commit set Marlin (Android 7) print:

Import low "marlin" fingerprint

Nb. Since module uses zygisk to target only attestation process rather than set props globally, I'm assuming Google gets your device model from this process via their Play Services back end...

Incidentally, the third bypass trigger is the latest, and of course needed for P7 series+ and other devices launched w/ A13+... See

Bypassing forced STRONG integrity …

* SafetyNet/Play Integrity (bypassing forced STRONG integrity for devices that shipped with 13+) by drop "first_api_level" to <33

* Some cosmetics/fixes

and

service: Set shipping level to 32 for devices >=33 …

If ro.product.first_api_level is 33, its forced to use HW attestation even though the safteynet checker app shows BASIC

setting it to 32 allows for software attestation and passing CTS

- Signed-off-by: Anirudh Gupta <anirudhgupta109@aosip.dev>

It can be seen from the various mismatch types needed that Google's system of whitelisting modern devices compatible with hardware based attestation is becoming more complex, more strictly enforced and also more difficult to bypass with time...

... Stil strikes me as a bit ironic that w/ all that's gone on, we need to pretend to Google to have a Huawei device to pass their Play Integrity requirements!... 🤪

Possibly, but not highly likely...

Such an old print, and even a differing API level are not needed for all devices that need the fingerprint prop mismatch to disable hardware evaluation type enforcement for Play Integrity... Just using an earlier certified print with the same Android version can work w/ some stock A11 (and A12?) OSs, but I haven't heard yet of this being achieved w/ A13...

@Displax's solution is designed to be as universal as possible however, so a print for a very old device that simply works across the board was chosen...

I guess you could experiment using official USNF and older P7 Pro fingerprint props from beta builds etc set using MagiskHide Props Config module... Of course you'd also need to use MHPC to set ro.build.version.security_patch date to match that of any newer fingerprint prop used as well as to set first_api_level to 32 as mentioned above...

Next, if you succeed with a proper P7 Pro print you'd want to consider forking @Displax's USNF mod to adjust the corresponding props and build yourself in case there are issues setting props incl. first_api_level to mismatched values globally. (Of course USNF will set these for GMS attestation (Google Play) process only, unlike MHPC.)

👀 PW