Displax / safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG] Pixel 7 Pro seen as Pixel XL

warmoans opened this issue · comments

Describe the bug & To reproduce
Open Google One and phone is shown as Pixel XL. Ask a Google assistant device to find your phone and it says Pixel XL

Expected behavior
Phone should be seen as Pixel 7 Pro.

Device info
Device model: Pixel 7 Pro
Android version: 13
ROM name/version: June 2023

Screenshot_20230624-091638
Screenshot_20230624-091613
Screenshot_20230624-091557
EDIT: Removed log due to personal info on it.

Here are magisk modules I'm using. I don't think they would cause this.
Screenshot_20230624-091842

Let me know if you need anything else.

You can rename devices using the Find Device app from Google. This fixed naming in Google One. I'm going to close bug report.

@Displax can you check this? Is not exaclty a bug, this phone Google Pixel XL (marlin) is use it to spoof for pass safetynet, but the strange is the programmer say this (This doesn't break other features because key attestation is only blocked for Play Services, and even within Play Services, it's only blocked for SafetyNet code. As a result, other attestation-based features (such as using the device as a security key) continue to work.) for that im little confused how your google one and Google assistant in your phone read the fake device who is only for spoof in safetynet, my question is, so what other apps read the fake device? only google or and other etc. and can break features