[Android Software Development] pndwal:
I don't think @Displax mods ever did that... @Didgeridoohan's MHPC did however...

... Do you have MHPC with Force BASIC key Attestation option active?... The default setting spoofs Nexus 5 in Model prop(s) on Google devices and it seems it may also use Nexus 5 model prop value for devices unknown to MHPC...

Details:

@Displax actually said:

since w/ USNF only fingerprint prop setting in MHPC might have previously been needed by users, but with his Mod builds even that was now covered by USNF since differing fingerprint must be set for many devices to pass Play Integrity deviceIntegrity verdict...

Most users had reverted MHPC Force BASIC key Attestation well before this as from Jan 2021 it stopped being effective... Actually, Google stopped using this S/N API prop based enforcement of hardware-backed attestation altogether when they introduced opportunistic use of hardware-backed attestation (if valid hardware key based measurements were received by Google Play servers these would always be used but if not basic attestation would) at that time...

The MHPC solution failed at that point and most modders with devices launched with A8+ adopted USNF which initially used the "not implemented" error code from Keymaster "to simulate... an old device lacking support for key attestation" causing SafetyNet to "gracefully" fall back to basic attestation. It now uses Zygisk "to inject code into the Play Services process and register a fake keystore provider" causing gms to throw an exception when attempting to use key attestation that effectively simulates the same failure condition resulting in a fall back to basic attestation...

Since September 2021 Google actually added back the old S/N API model prop based enforcement of hardware-backed attestation on devices they know to support hardware-backed attestation... This simply invalidates exclusively basic attestation based verdicts on these devices for S/N, and the same enforcement plus two using different props (not affecting S/N API) have also been implemented in the new PI API.

MHPC prop spoofing can be used to bypass device integrity API (both PI and S/N) hardware-backed attestation enforcement since September 2021 once again, but of course that will no longer suffice on its own since opportunistic hardware-backed attestation use means hardware key based measurements will still be used without a fallback trigger, so there's really been no point using MHPC prop spoofing since Jan 2021... Only 2 weeks after S/N API model prop based enforcement was reinstated in September 2021, @kdragOn released USNF 2.1.0 with both triggers ('fallback to basic' and 'hardware-backed enforcement bypass) now needed...

Nb. (Many are fooled by this): S/N's Evaluation type response would be BASIC with the spoofed model prop bypass trigger (indicating that S/N API only requires basic attestation signals and measurements) but without the broken keystore fallback trigger hardware-backed signals and measurements are still received by the Play server so the API uses these and CTS Profile Match necessarily fails... Yes, gms may still be sending Google Play servers hardware-backed attestation data when S/N API indicates Evaluation type is BASIC...

Notably, USNF does targeted prop spoofing (ie only affects gms) so device/OEM specific functionality incl. Camera, fingerprint hardware, OEM app stores, backup utilities etc etc will generally not be broken... MHPC prop spoofing was global...

FWIW, some other key (unintended pun!) hardware-backed attestation related dates for modders:

- March 2020 - Google does some intermittent prop based testing of hardware-backed attestation, spooking the modding community while CTS Profile Match attestation was failing randomly...

- May 2020 - Google announced new evaluationType JWS response field.

- June 2020 - Google begins turning on S/N API model prop based enforcement of hardware-backed attestation for devices they know to support hardware-backed attestation (Initial period)... [If S/N evaluationType = BASIC, this is the attestation type used]

- July 2020 - @Displax posts his HardwareOff S/N API model prop based hardware-backed attestation enforcement bypass solution...

- MHPC adds configurable Force BASIC key Attestation option a little later...

- Jan 2021 - Google swaps S/N API model prop based hardware-backed attestation enforcement for opportunistic use of hardware-backed attestation... [If S/N evaluationType = BASIC, this is the attestation type used]

- @kdrag0n introduces USNF the same month with an initial fix / fallback for opportunistic hardware-backed attestation use...

- September 2021 - Google reinstates the S/N API model prop based enforcement of hardware-backed attestation on devices they know to support hardware-backed attestation... [If S/N evaluationType = BASIC it MAY NOT be the attestation type used since working opportunistic use of hardware-backed attestation is not overridden by bypassed prop based enforcement of hardware-backed attestation although the latter's evaluationType takes precedence over the former... From this it is clear that S/N evaluationType simply reflects the minimum level of trust required for attestation signals and measurements used to produce fully passing S/N verdicts]

- @kdrag0n adds fix / bypass for USNF S/N API model prop based enforcement and releases this 2 weeks later...

- June 2022- Google launches new Play Integrity API and SafetyNet Attestation API is deprecated...

- July 2022 - @Displax posts his interim fix / bypass for PI API deviceIntegrity verdict fingerprint prop based enforcement for devices needing this. (Some devices can pass this with only USNF for S/N)... A fix / bypass for shipping level prop based enforcement (affecting all A13+ LV devices) was added since...

- Jan 2023 - @kdrag0n adds fix / bypasses for USNF PI API deviceIntegrity verdict fingerprint prop (with 'temporary' spoofing) and shipping level prop based enforcement and releases this...

Not intended behaviour... Intended behaviour is: Delete/disable/reset MagiskHidePropsConfig if installed... As it was for @Displax USNF fork/Mod. 😜 PW