yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
Something is messing with your device when it comes to the architecture (arm 32/64 bit).

Disable the hardware off module and reset MagiskHidePropsConfig module.

Reboot and then check that your device shows as arm64.

You can check using the getprop command in a terminal app or adb shell.

getprop | grep abi or adb shell getprop | grep abi

Example of output from arm64 device(s).

Pixel 4a and Poco F1 running Lineage 18.1

[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]

Example of output from arm device.

Nexus 7 (2013) running Lineage 18.1

[ro.odm.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.odm.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.odm.product.cpu.abilist64]: []
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: []
[ro.vendor.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist64]: []

If you show v8a, then try the Universal SafetyNet Fix module again.

If you are on a stock rom, the build fingerprint and security dates should be correct, and you should pass SafetyNet.

If you are on a custom rom, you might need to use MagiskHidePropsConfig and select a certified fingerprint (includes the corresponding security date).

It should not matter what fingerprint device you pick. The closest one available is ideal but, not a requirement.

--

If you are on a custom rom, and still only showing v7a.

Check with the rom dev, for some reason the rom/kernel is built on arm (arm32) not arm64.

Cheers. :cowboy:
[Magisk] Jorge_8:
Thanks! it works on a Pocophone F1 with the MSM-Xtended rom Android 11, installing Magisk Canary, and the modules safetynet-fix-v1.1.1.zip and MagiskHidePropsConf-v5.4.0.zip, with the magisk hide option activated, changing the version of device fingerprint for the Pocophone F1 to Android 10 from the terminal, and deleting the data of these applications.

Google Play Store

Google Play Services

Google Services Framework

Greetings!!!
[Magisk] zfk110:
I couldn't get that info

gta3xlwifi:/ # adb shell getprop | grep abi

/system/bin/sh: adb: inaccessible or not found

so I install this app to find this info for you, I don't know if they make any sense to you?

Which security dates should I use with this?
[Magisk] Kurt Krummbein:
ROFL, if you run it directly on the device, you don't need the "adb shell"!

Kurt
[Magisk] Anertz0153:
Hi.

I'm having a problem with this module, can someone please help me? Or tips?

I am using Mi9TPro PixelExperience, I was using this module due to L1. The recent update didn't do it well, so I used one previous version of the Magisk Module to fix it.

But the list of fingerprints? has changed to 30 and 31 for Xiaomi, right? Oddly enough, the fix I was able to do before is no longer possible and I am now on L3.

How can I get it to work?

If there's any info I'm missing, I'll get back to you!
[Magisk] zgfg:
Widewine L1 requires paid cerificte for your device.

If your custom ROM affected your /persist (some custom ROMs do, it's a well known issue for Xiaomi devices), then the cerificate is gone and you drop to default, free, L3

Maybe you can restore your /persist by flashing stock or restoring backup of your /persist if you have, look at your device forum
[Magisk] Anertz0153:
Thank you.

After flashing MIUI, I installed Pixel and fixed this module and it worked fine.
[Magisk] TheTrueJayTwenty:
Kinda a noob when it comes to running commands on android, what would I type in Termux to set my fingerprint to - Samsung Galaxy S20 FE 5G (10)

Thanks
[Magisk] zgfg:
Type props and it will guide you. Read also OP post and the guide (link in the OP)
[Magisk] TheTrueJayTwenty:
So props then just enter? lol I thought I had to type props then something to do with the name of the fingerprint.
[Magisk] zgfg:
It's props not prop (see my post and PLEASE read OP post #1)
[Magisk] TheTrueJayTwenty:
Sorry typo on my part, and I have read it a few times, I just got a bit confused when I read the usage on the GitHub page.

I thought I was supposed to type something after I type props
[Magisk] Didgeridoohan:
That's only if you want to add a custom prop without going through the ui, or to use one of the listed run options.
[Magisk] emaborsa:
Hi guyz,

- I have an SM-A600FN

- installed Magisk without TWRP

- basicIntegrity failed, ctsProfile failed, evalType HARDWARE

- installed MagiskHide Props Config

- set fingerprint using terminal emulator

Now I have basicIntegrity passed, ctsProfile failed, evalType HARDWARE.

I found a guide to edit the device simulation:

- props in teminal emulator

- type 2 for Device simulation

- type s for Device simulation

- enable ro.product.brand, ro.product.name, ro.product.device, ro.product.manufaturer, ro.product.model

After these steps I still have basicIntegrity passed and ctsProfile failed, but evalType BASIC.

I also tryied the Safetynet-fix v1.1.1, but it complies for the CPU architecture.

Any hints what to do?
[Magisk] Didgeridoohan:
Since it seems like your device uses hardware attestation regardless of what evalType reports, you will likely need a fix like Universal SafetyNet Fix (unles you've got other stuff on your device that triggers the CTS check). But you've already found that the module doesn't work on your reported CPU architecture.

There was no need to open a new issue in the module's repo though, since there already was one available:

https://github.com/kdrag0n/safetynet-fix/issues/7

You'll have to wait and see if @kdrag0n decides to add support for armv7-a devices.
[Magisk] emaborsa:
Ops, didn't see the already open Issue...sorry.

Do you know if all SM-A600 have the same architecture? I mean, do all Samsung A6 have the armv7?
[Magisk] Didgeridoohan:
I don't do Samsung, but I would assume so. Sounds like something you could practice your Google-Fu on though...
[Magisk] AndDiSa:
@emaborsa looks to me as if your device is ARM-v8a
[Magisk] Didgeridoohan:
But if the device reports arm7 it doesn't really matter what hardware it actually uses... Blame the OEM.

Further queries and discussions on this is best kept in the Universal SafetyNet fix's thread though (and probably already have been brought up a few times before):

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Magisk] emaborsa:
View attachment 5198459
[Magisk] Darth Bidder:
I just updated to the latest Magisk version 21.4 and now when I installed the latest version of this module and changed the fp, it now fails the SafetyNet test.

Before it used to work as it should when I had installed Magisk 20.4 installed, is this a Magisk issue?

I've already enabled MagiskHide and no effect.

I used the Redmi 7 Global (9) before but it doesn't work atm.

EDIT: Found the fix on the changelog.
[Magisk] Kurt Krummbein:
How? By installing safetynet-fix-v1.1.0? Also working with current safetynet-fix-v1.1.1?

Please tell us :-).

Cheers

Kurt
[Magisk] carabot:
hi

fingerprint for gauguin is present?
[Magisk] Didgeridoohan:
Since they mention the changelog I'm pretty sure they're talking about the new Universal SafetyNet Fix... If you need help with that module, please keep that discussion in the USNF thread.
[Magisk] Didgeridoohan:
Yes, there's a European print on the list. But, since I typoed the name you'll currently find it under "Xiamoi" rather than Xiaomi. I'm gonna fix that with the next release...
[Magisk] zgfg:
Xiaomi Mi 9T, Europe, A10:

ro.build.fingerprint=Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V12.0.4.0.QFJEUXM:user/release-keys

ro.build.version.security_patch=2021-01-01
[Magisk] carabot:
I edited fingerprint, but the safety net check did not pass
[Magisk] Didgeridoohan:
There's a checklist for that in the module docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check

(My guess is that you need the new Universal SafetyNet Fix, also linked in the docs: https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation)
[Magisk] carabot:
with safetynet fix he succeeded, thanks
[Magisk] Dante63:
The module is working, device certified, but it broke fingerprint functionality, all apps that have biometric security can't use fingerprint, please help, I don't want to type the entire password every time...

I have Samsung Galaxy Note 20 Ultra SM-N986B/DS android 10 but android 11 rolled out already so i am not sure if that's the reason...
[Magisk] zgfg:
About which module are you talking, MHPC or safetynet-fix?

The lattet has its own thread to debate about and a biometrics issuees are known for Samsung (many people are reporting there)
[Magisk] DavidLuz2031:
Hello, I would like to update the device fingerprint of redmi 7 (9) to version (10). How can I help you?
[Magisk] Didgeridoohan:
By providing the fingerprint and corresponding security patch date. And since you just did that I can test it and include it in the next update if it passes CTS. Thanks.
[Magisk] Dante63:
I am honestly not sure which module has caused the biometric security issues, problem is, when I disabled both, biometric security still fail to be used in many apps, the only module with options is MHPC, perhaps the fingerprint is still active...?
[Magisk] zgfg:
When you disable a module you must reboot.

To find out which module causes the problem experiment with disabling one by one (and rebooting) - but please take your time, find the safetynet-fix thread and read there about the biometrics issues
[Magisk] Didgeridoohan:
Fingerprints list updated to v115

Small update to the fingerprints list. Thanks to @zgfg and @DavidLuz2031 for your help in keeping the list updated.

Apart from the two prints, there was also a small typo for the Xiaomi Mi 10T Lite Europe which has now been fixed (not in the print, but in the name shown in the prints list). Thank you @Micdu70.

The list will update when you run the props command, or if you have disabled automatic updates by using the -f flag (use -h for details) or from the "Edit device fingerprint" menu.

New

Xiaomi Redmi 7 Europe

Updated

Xiaomi Mi 9T Europe
[Magisk] Displax:
Xiaomi Mi A3 | NEW Android 11 Print Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.4.0.RFQMIXM:user/release-keys__2021-01-05

Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.20.0.QDIMIXM:user/release-keys__2021-01-01

Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.17.0.QDLMIXM:user/release-keys__2021-01-01
[Magisk] mozila:
Edit device fingerprint (disabled),need help.
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...ter/README.md#an-option-is-marked-as-disabled
[Magisk] _tuniol:
Hello, how to pass safety.net on poco x3 ? I can't use NFC. because every tutorial what i found (like this) telling about "Press option 2 - "Force BASIC key attestation" ", but I dont have that option. Im using newest global miui.
[Magisk] Didgeridoohan:
Unfortunately, guides and tutorials not written by the original creator of whatever tool they reference often become obsolete after a while... I'd suggest you look at the module documentation instead:

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
[Magisk] olivercervera:
Fingerprint update for Xiaomi Redmi Note 8T Europe.

The device already exist with Android 9, here's Android 10:

xiaomi/willow_eea/willow:10/QKQ1.200114.002/V12.0.1.0.QCXEUXM:user/release-keys
patch date: 2020-10-01
[Magisk] :
Samsung Galaxy A7 2018 (SM-A750GN) - Android 10: samsung/a7y18ltedx/a7y18lte:10/QP1A.190711.020/A750GNDXU6CTK1:user/release-keys

Patch day: 2020-12-01
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 3a=google/sargo/sargo:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 3a XL=google/bonito/bonito:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 4=google/flame/flame:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 4 XL=google/coral/coral:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 4a=google/sunfish/sunfish:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
Pixel 5=google/redfin/redfin:11/RQ1A.210205.004/7038034:user/release-keys__2021-02-05
[Magisk] YamazakiRobert:
hey guys I'm using lineageos 17.1 for z3 play and cant pass the ctsprofile, i have created the fingerprint with

Motorola Z3 Play=motorola/beckham/beckham:9/PPWS29.131-27-1-27/34b6d:user/release-keys__2018-08-05

but still no luck, the is anything extra i can try to resolve may issue:

tks in advance
[Magisk] ipdev:
Maybe something in the docs. ?

I still can't pass the ctsProfile check GitHub - Link

Cheers. :cowboy:
[Magisk] Didgeridoohan:
Fingerprints list updated to v116

Beginning of the month and as usual a bunch of Pixel prints dropped in the thread. Together with a few others. Thank you @Displax, @olivercervera and @K-218 for the prints for this update.

The list will update automatically when you run the props comman, or if you have disabled automatic updates by using the -f flag or from the "Edit device fingerprint" menu.

Updated

Google Pixel 3-5 (all variants).

Samsung Galaxy A7 2018 SM-A750GN

Xiaomi Mi A2

Xiaomi Mi A2 Lite

Xiaomi Mi A3

Xiaomi Redmi Note 8T Europe
[Magisk] Didgeridoohan:
Apart from the link to the docs you were given above, I tested that print for the updated list I just released and it did not pass CTS. Perhaps the security patch date is wrong?
[Magisk] Bradford1040:
Edit, nevermind! Soon as I posted I found my answer, the new version just adds new fingerprints, so if my phone is working then I'm good

I guess call this question a noob question,

If everything is working and passing is there any need to update the module? I'm sure it's been asked, but I couldn't find it searching through on my phone

Apologies if it was in the thread
[Magisk] isoladisegnata:
On pixenOS 11 ..oneplus 6t everything pass CTS but my bank app still not pass..
[Magisk] Didgeridoohan:
Since you pass CTS you've gotten as far as you can with this module (if you're actually using it). There are many, many, many other things besides SafetyNet that apps can use to check for root...

Take a look here for tips, and if you need further assistance there are many "bank app is detecting root"-threads in the Magisk forum where you can try to get more help:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] gallgamer:
Mi 8 Pro (UD) Global

Xiaomi/equuleus/equuleus:10/QKQ1.190828.002/V11.0.5.0.QECMIXM:user/release-keys

security_patch=2020-04-01

Mi 8 Pro (UD) Russia

Xiaomi/equuleus_ru/equuleus:10/QKQ1.190828.002/V11.0.3.0.QECRUXM:user/release-keys

security_patch=2020-04-01
[Magisk] c3k:
My device isn't passing basicIntegrity:

MagiskHide Props disabeld: basicIntegrity passed

MagiskHide Props enabled: basicIntegrity fail

No problem for months with the same device fingerprint, yesterday I try the test version of Universal SafetyNet Fix (maybe only a coincidence) and MagiskHide Props stops working, for the first time I can't pass basicIntegrity, (Universal SafetyNet Fix downgraded and removed).

Configuration:

S10 exynos

stock rom - one ui 2.5 - android 10

MagiskHide Props 5.4.0 (116), Samsung A3 2015 SM-A300FU device fingerprint

No other modules

Any hint?
[Magisk] Didgeridoohan:
You're using the stock Samsung ROM, so you do not need to change the device fingerprint. Your device is already certified so this module cannot do anything for you anymore, since Google blocked the trick to force basic attestation by changing the model prop. You now need the new Universal SafetyNet Fix to pass CTS.

But your basic integrity failing is interesting, since you say it only happens when you have MHPC enabled. By the way, why have you changed the device fingerprint to an A3? Does basic integrity pass if you change back to the default fingerprint?
[Magisk] arik100:
there is no fingerprint for POCO M3

i tried using POCO X3 NFC GLOBAL but i dont pass cts test.

any ideas?
[Magisk] Didgeridoohan:
If you can't pass CTS when using a certified device fingerprint you likely also need to force basic attestation. Take a look here for a hint as to what options of this module you need (if you even need the module at all):

https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1
[Magisk] Thoiareg:
Hi, thanks for your work.

With the lastest version , 5.4.0 v116 , my phone don't boot and stay on logo before rom logo.

Android 11 ( Havoc 4.0) on Xiaomi Mi max 3.

With the version v113 , i have no issue.
[Magisk] Didgeridoohan:
The second part of the version string refers to the fingerprints list. The first half is for the actual module. There has been no change to the module between v5.4.0-v113 and v5.4.0-v116, apart from adding/updating a few device fingerprints and the Mi Max 3 was not among them (that print hasn't been updated since it was added in prints list v54).

In other words: it is very unlikely that updating the fingerprints list from v113 to v116 would cause the problem you're describing.
[Magisk] amplatfus:
Dear devs,

First of all thankk you for the module.

Second: please consider my below submission and help me with the addition into module.

OPPO A53s submit it for inclusion in the list of certified fingerprints.

OPPO/ CPH2135EEA

security_patch=2020-11-05

sdk=29

getprop ro.build.fingerprint

OPPO/CPH2135EEA/OP4EFDL1:10/QKQ1.200614.002/1605790610:user/release-keys

Terminal, history:

:/ $ getprop ro.build.fingerprint
OPPO/CPH2135EEA/OP4EFDL1:10/QKQ1.200614.002/1605790610:user/release-keys
:/ $
:/ $ getprop ro.build.version.security_patch
2020-11-05
:/ $
:/ $ getprop ro.product.manufacturer
OPPO
:/ $
:/ $ getprop ro.oem_unlock_supported
1
:/ $
:/ $ getprop ro.build.version.sdk
29

Much appreciated,

amplatfus
[Magisk] Didgeridoohan:
@amplatfus Print tested and confirmed passing CTS. I'll add it to the next prints list update.

Cheers!
[Magisk] c3k:
I believed that I need to change the fingerprint to get the basic evalType AND Universal SafetyNet Fix to pass.

This was my working setup until 2 days ago when I try the test version of SafetyNet Fix (I had in-app fingerprint authentication problem).

Now I try to remove MHPC, leave SafetyNet Fix and happen what I expected: failing because of hardware evalType.

I think I'm missing something (big?)

Otherwise I have no idea but try a previous version of MHCP.

Yes, installing the module without changing the fingerprint didn't break basic integrity.

But, I repeat, I was using A3 fingerprint and passing SafetyNet for months.
[Magisk] Didgeridoohan:
That has about no chance of working (but there might of course be exceptions, knowing how Android works) after Google patched out the model prop trick for forcing basic integrity. Currently the only proper way to pass CTS with a device that has the hardware for the unstoppable bootloader check is with the new USNF. That's where you need to focus your attention...

Just to make sure, I tested the A3 print and there's nothing wrong with it.
[Magisk] c3k:
You're right.

Simply USNF2-test2 isn't working on my device.

With 1.1.1 I'm passing again SafetyNet.

I know very very little about basic integrity check... It's 100% fingerprint related? If you want any other test just ask.
[Magisk] Didgeridoohan:
The basic integrity check has nothing to do with the device fingerprint. It checks the system integrity and triggers by things like root and Xposed. If basic integrity suddenly fails it's most likely caused by MagiskHide conking out.
[Magisk] c3k:
Could MagiskHide be deceived by the fake fingerprint for your experience?
[Magisk] Didgeridoohan:
It's nothing I've seen so far (not for a working certified print at least).

Recently I've been seeing it fail a few times on a reboot (fixed by rebooting again), something that might be connected to a libsu bug that John fixed yesterday (not in any releases yet). That's just a wild guess though and nothing that I've had the time to investigate or verify.
[Magisk] c3k:
I've found the reason I need the A3 fingerprint (Google Pay / Play protect certification).

I have to confirm that activating device fingerprint in MHCP triggers basicIntegrity, even after additional reboots.

I think something is changed (with an update) in SafetyNet OR in Magisk OR in MHCP.

Or something USNF2-test2 did, since the story starts after installing this module.
[Magisk] Didgeridoohan:
Your device is using the stock Samsung ROM, you should not need to apply another device fingerprint to be Play Store certified... Let me explain:

Play Store certification is tied to the SafetyNet CTS profile, so if you fail the latter, the former will become uncertified. Once you pass CTS again you won't have the Play Store certified until you clear the Play Store data (and possibly done a reboot).

Is this with any fingerprint or just the A3? That's a rather old device, and it's always preferable to use a device as close to your own as possible when applying a new fingerprint (and the same was true for the now deprecated "Force BASIC key attestation" feature of this module). Changing props

always

has the possibly to mess up your device...
[Magisk] c3k:
Sorry, I wasn't accurate: Play Store certification and SafetyNet are ok, but not Google Pay. This is the reason I had the A3 fingerprint.

I'm my mind Google Pay did an additional check, and it know which device could be hardware verified, so I need to appear as A3 to use pay with a BASIC SafetyNet evalType.
[Magisk] Didgeridoohan:
But still... The device fingerprint doesn't have anything to do with the bootloader check (from what we've seen so far). So that will not help you get a basic evalType. That was accomplished with a change of the model prop (and had nothing to do with the fingerprint).

GPay does use additional checks yes, that is known and quite easy to work around:

https://xdaforums.com/t/working-mag...s-17-1-22-on-pie.3929950/page-9#post-79643248

It's a bit of a wall of text, but there's a module there that can help you in getting GPay working (as long as you have SafetyNet fully passing, but as you see that's also described in there).

That reminds me though: @73sydney You might want to update the instructions since MHPC no longer have the possibility (or even the option anymore) to force basic attestation. The new USNF is needed for that.
[Magisk] c3k:
Thanks, again.

I don't want a basic evalType only, I want a basic evalType on a device (fingerprint) that *can't* be hardware verified.

This is what I did in the last months (year?) to use Google Pay.

Don't know if that's the simplest solution, but it worked and now something breaks it.

This trick is part of my mods, I don't use the module but I did the db changes and make it read only. Seems not enough with the S10 fingerprint.
[Magisk] Didgeridoohan:
Fingerprints list update to v117

Got a small update with a few new fingerprints. Thanks you @gallgamer and @amplatfus for providing these.

The list will update when the props command is run, or (if you've disabled automatic updates) by using the -f run option or from the "Edit device fingerprint" menu.

New

OPPO A53s

Xiaomi Mi 8 Pro Global & Russia
[Magisk] Displax:
Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.18.0.QDLMIXM:user/release-keys__2021-02-01

Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.21.0.QDIMIXM:user/release-keys__2021-02-01

Oops, a little late :)
[Magisk] Didgeridoohan:
Gorramit... Funny timing @Displax. :ROFLMAO:
[Magisk] M1ster1:
Hey there, It lasted one month :LOL:

So, apparently Google has modified some stuff and using only a custom "ro.product.model" does not seem to work anymore.

I am back to:

basicIntegrity OK

ctsProfile Not OK

evalType BASIC

So, do you have any advice on how to pass SafetyNet this time?