Pixel 3=google/blueline/blueline:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 3 XL=google/crosshatch/crosshatch:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 3a=google/sargo/sargo:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 3a XL=google/bonito/bonito:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 4=google/flame/flame:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 4 XL=google/coral/coral:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 4a=google/sunfish/sunfish:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 4a (5G)=google/bramble/bramble:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05 Pixel 5=google/redfin/redfin:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Not sure what you mean by typo... All those fingerprints in the post you quoted are different.
You picked a good one to try first.
POCO POCO F2 Pro lmi POCO F2 Pro Redmi K30 PRO lmi Redmi K30 Pro
recovery.img, the recovery update will not.
ramdiskdirectory of the unpacked image, there will be a default.prop or prop.default file.
META-INF/com/android/metadatafrom the recovery update and look for "post" print and security patch.
That's just the build info, and since the build is basically the same for all those devices it'll be the same...
Thanks a lot for your fast answer!
Both of those modules deal with the CTS profile. You're also failing basic integrity...
Pixel 3=google/blueline/blueline:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 3 XL=google/crosshatch/crosshatch:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 3a=google/sargo/sargo:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 3a XL=google/bonito/bonito:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 4=google/flame/flame:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 4 XL=google/coral/coral:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 4a=google/sunfish/sunfish:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 4a (5G)=google/bramble/bramble:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05 Pixel 5=google/redfin/redfin:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Google is working on things on their end... Check the main Magisk thread and you'll see that it's been discussed a bit already. You can use XprivasyLua or spoof the model prop with MHPC. There's also a small tweak to the USNF module that @Displax posted in there that should do it for you.
Johns working like crazy for the next Magisk release, check the commits on GitHub. The only thing he won't be working on is MagiskHide.So far only 2.0.0 safetynet fix is available unless you are pateron of kdrag0n. I know the 2.0.0 build does not work on anything I have. I haven't checked on devices I haven't updated yet.
I was under the impression we weren't getting anymore releases anytime soon from topjohnwu now that he was working for Google. I thought most people had gone to vvb2060's builds of Magisk?
You went with the default it sounds like... A0001 is the model for the OnePlus One, that will be set if you pick the default value. The recommendation is to pick a device from the list, one that most closely matches your device (but not your actual device). It'll still show the wrong model, but you're less likely to experience weird issues...