yashsingh1/xdaforums huggingface dataset:
[Magisk] sagybp:
Hi good people. I hope you can help me with something.

I have a rooted Samsung Galaxy S21 Ultra with Android 11 (One UI 3.1).

I wanted to pass SafetyNet so I can pay with Google Pay, so I followed this tutorial:

How to Pass Magisk SafetyNet on Rooted Android 11

In this tutorial, we will show you how to pass the Magisk SafetyNet test on your rooted Android 11 device with Hardware attestation type.

www.droidwin.com

I spoofed my fingerprint to Pixel 3A, installed SafetyNet Fix 1.1.1 and indeed passed SafteNet and Google Pay is working.

However, now I'm having issues with apps that require fingerprint authentication. Mainly one banking app and one password manager app.

One of them claims I don't have a fingerprint configured in my system (which is not true) and the other one doesn't even let me choose that option.

Other banking apps I have are working perfectly with a fingerprint, so just these specific 2 are problemtaic.

I'm aassuming it has something to do with spoofing my fingerprint to Pixel 3A.

Is there a way to fix this so my apps will work with fingerprints, while keeping everything I did in place (SafetyNet passed, Google Pay is working)?

Thank you!
[Magisk] Didgeridoohan:
That's a silly guide...

Since you're on a stock ROM you don't need to change the device fingerprint (and when you do it's better to pick your own device from the list, or at least one as close as possible). You don't need this module...

And there are known issues like you're describing with the Universal SafetyNet Fix module you're using, so you'd better update to a version that has fixed it:

https://github.com/kdrag0n/safetynet-fix
[Magisk] sagybp:
Wow, thanks for the quick reply!

So after installing the newer USFN you would recommend changing my fingerprint back to my own device?
[Magisk] sagybp:
Thank you so much. It worked like a charm.

I didn't think it would be so easy.
[Magisk] NOS_bzone:
Hi dev,

Help for put fingerprint Xiaomi Mi 11 Lite 4G (codename: courbet)

Rom A11 Global Stable Indonesia:

Xiaomi/courbet_id/courbet:11/RKQ1.200826.002/V12.5.1.0.RKQIDXM:user/release-keys

Security patch: 2021-06-01

Thank you
[Magisk] Didgeridoohan:
Updated module to v6.1.0, fingerprints list to v133

Another day, another release with a bunch of fixes and updates. And a few new and updated fingerprints (thank you @Displax, @pepote666 and @NOS_bzone).

Not much to say really, the changelog speaks for itself...

Changelog

v6.1.0

Added settings file version check.

Added a check for the new Universal SafetyNet Fix and disable sensitive props at install if v2.1.0 or newer is detected.

Changed default boot stage for SELinux fix and triggering props to late_start service.

Fixed update check.

Fixed a few problems with the configuration file import.

Make sure late props are set after boot completed (might break some features otherwise, forgot about that).

Minor UI fixes.

Added fingerprints for Asus Smartphone for Snapdragon Insiders and Xiaomi Mi 11 Lite Indonesia. Updated fingerprint for Xiaomi Mi 10 Lite 5G Global. List updated to v133.
[Magisk] Some_Random_Username:
Hi folks, below are newer fingerprints for OnePlus devices, hopefully I got everything right.

As always, OnePlus/OnePlus7/ fingerprint is for GM1901 and GM1905 / OnePlus/OnePlus7Pro/ fingerprint is for GM1911 and GM1917 / OnePlus/OnePlus7T/ fingerprint is for HD1901 and HD1905 / OnePlus/OnePlus7TPro/ fingerprint is for HD1911 and HD1917.

Updated fingerprints:

Spoiler content hidden.

New fingerprints for devices already in list:

Spoiler content hidden.

New fingerprints for devices not already in list:

Spoiler content hidden.
[Magisk] Displax:
Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.14.0.RFQMIXM:user/release-keys__2021-09-05

Xiaomi Mi A3 EU

Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.11.0.RFQEUXM:user/release-keys__2021-08-05
[Magisk] Didgeridoohan:
Fingerprints list updated to v134

Oh well... Thanks to the impeccable timing of @Some_Random_Username and @Displax, here's another quick update with a whole host of prints.

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

New

OnePlus N200, Global and T-Mobile

Oneplus Nord 2, Europe and India

Update

OnePlus 6 to Nord CE, many variants

Xiaomi Mi A3, Europe and Global
[Magisk] Pandemic:
Can you add more xperias in the fingerprint list like Xperia 1 (j9110) ? Thanks 😊
[Magisk] Didgeridoohan:
I would love to. But:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] swour:
No more errors with v6.1.0, thanks! (y)
[Magisk] Zimbushman:
Hi, is there anyone who would be kind enough to give me Samsung Galaxy A10s Sm-A107F/DS A107FXXS8BUC1 with Android 10 and patch fingerprint Thanx in advance
[Magisk] Some_Random_Username:
Hi gang, OnePlus released their A12 Developer Preview 2 for OnePlus 9 and 9 Pro earlier today, fingerprints seem to pass SafetyNet according to testing I've done on my 5T, I've pasted them below.

Spoiler content hidden.
[Magisk] CarbonGTR:
Nokia 6.1 Plus's last official update's build fingerprint.

Build security patch is dated August 2021

Nokia/Dragon_00WW/DRG_sprout:10/QKQ1.190828.002/00WW_4_15T:user/release-keys
[Magisk] Timmmmaaahh!:
Ugh, I should probably create a dedicated thread for this (should I?) but here goes.. I have a OnePlus 6T and my banking app seems to detect root no matter what I do. This is the one: Keytrade Bank

It used to be enough to just MagiskHide it and scramble Magisk's package name but it seems to have found a way around that. This is its crash log:

Spoiler content hidden.

Why is it even riddled with all this com.facebook.soloader.a and other FB stuff? I don't even have Facebook.

Anyway, stuff I tried:

Unhiding Magisk and hiding it again

Adding a ridiculous amount of entries to MagiskHide like all G-related items, Play Store services, etc.

Using other certified keys from MagiskHide Props Config, both same brand/type and others

Following this tutorial (Riru + LSPosed + XPrivacyLua)

Disabling debugging

At any point, SafetyNet always passed

I just don't get how it can still "know". Even my NFC payments and government authentication tools are working fine! The banking app keeps sending me to this page, which basically states my device is either rooted, I'm using an untrusted keyboard or an untrusted screen reader. I doubt SwiftKey is an untrusted keyboard but I tried switching to Gboard anyway, without any success. Any help would be much appreciated!
[Magisk] crok.bic:
Yes, you should open a separate thread for this since SafetyNet is already passing for you - thus this is not related to Magisk directly. Your app is detecting traces of having an unlocked bootloader and probably doesn't even care about SafetyNet at all (like the banking app I'm using..). I would try to delete / rename TWRP / FOX / PBRP directory on your internal storage (here's the logic behind: why would you have a custom recovery's dir in your internal storage if your bootloader is locked, huh'?) or try to use AirFrozen for example (I wrote about it here) or Storage isolation Riru module.. Just Google it.

Edit: just tested it for you: if I freeze the hidden Magisk app then your banking app just starts fine without any warning or issue, asking for logging in.
[Magisk] danilo_scala:
Improved hiding disable, How enable?
[Magisk] Didgeridoohan:
It's documented:

https://github.com/Magisk-Modules-R...ter/README.md#an-option-is-marked-as-disabled
[Magisk] arddy1:
Does magisk 1674 build fix resetprop tool that not working on android p?

Somebody said it's just for google pixel, but i wonder if it means for the android p devices. I need to find a method to fix broken ctsprofile on my Mi Mix 2s running android p.
[Magisk] Didgeridoohan:
No, it doesn't. You currently have two options:

Live with it until there's an update.

Revert to Oreo.

Edit: Of course, you could also manually edit your build.prop, but that wouldn't be very systemless, would it?

Sidenote:

The 1674 build that's floating around can be used on any device, but it contains some fixes that were designed to fix device boot issues, something that was seen relatively often on Pixel devices (and others).
[Magisk] arddy1:
Will editing anything on /system partitition break safety net sir?

I wouldnt mind if it breaks ota. My purpose of using systemless thing is just to make mods easier. I only need to install magisk zip once every updating rom to install all mods. Additional task of editing props is just little thing if it doesnt break safetynet. :D
[Magisk] Didgeridoohan:
It shouldn't. SafetyNet could check the integrity of /system and fail if it's discovered to be tampered with, but so far I haven't seen that happening. I've edited different parts of /system on many occasions and so far haven't failed SN as a result. Of course, that doesn't mean that it can't happen, just that I haven't experienced it...
[Magisk] arddy1:
Damn it works! Thank you for your suggestion sir :good:
[Magisk] Seagold:
Which app did you use to run the test?
[Magisk] Didgeridoohan:
That's SafetyNet Helper Sample. Very good app to check SafetyNet and it's updated to the new API.
[Magisk] Seagold:
SafetyNet Test App
[Magisk] Seagold:
SafetyNet Attest App
[Magisk] Seagold:
This SafetyNet thing is not working ? on my phone ?
[Magisk] Didgeridoohan:
Looks like MagiskHide isn't working at all on your device (or at least Basic Integrity would pass).

First thing you do is to toggle MagiskHide off and on, and if it still doesn't pass, start reading:

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] Seagold:
Not passing anything. I will wait till I get a better phone. GOD WILLING.

Thanks for your effort.
[Magisk] Samrat Sengupta:
config props not working for asus zoot ze601kl

Hi Dev, I flashed the config prop as well as ran the props but could find only the zool version for asus and not the zoot for fingerprint. Need assistance please to know if there is any other certified fingerprint that does run it successfully.:rolleyes:
[Magisk] Didgeridoohan:
The zool fingerprint didn't work? If you can provide a functioning zoot fingerprint I'll happily add it to the list.

Fingerprint acquisition:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] Felix Siahaan:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

Please help to update the latest fingerprint for Xiaomi Redmi Note 5 Pro (8.1.0):

xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.6.3.0.OEIMIFD:user/release-keys

Thank you
[Magisk] jcmm11:
Fingerprint acquisition: couldn't they just look in /vendor/build.prop (assuming they have a vendor partition)?

ro.vendor.build.fingerprint

Vendor folders tend to remain stock even in custom ROMs. (I don't have fingerprint problems myself)
[Magisk] Didgeridoohan:
I wouldn't know. I don't have any device with a vendor partition... Is the build fingerprint stored there though? If so, and if it's kept stock like you say, they wouldn't need this module would they? Running getprop will load the correct value no matter where it's stored...

Some custom ROMs simply do the same thing I do and spoof a certified fingerprint when building.
[Magisk] Samrat Sengupta:
Sure I will get back once I get any..:good:
[Magisk] Didgeridoohan:
@Timmmmaaahh! From a quick test I can tell you that it's detecting the Magisk app, even if it's repackaged (that's a very common detection method now, and almost impossible to completely circumvent without additional tools).

Solution is to freeze or uninstall the Magisk app when you want to use the bank app or use a Riru/LSPosed module to prevent apps from seeing other apps.

@crok.bic If SafetyNet passes the unlocked bootloader should be fully hidden already. But stuff like the TWRP directory and the like is very common to use as a root litmus test (which I guess you could call traces of unlocking the booloader).
[Magisk] crok.bic:
That's what I mean / tried to say - yes.
[Magisk] zgfg:
Enabling MagiskHide for G Play app and so would not help you - unfortunately it can even cause problems by slowing down Magisk and MagiskHide.

Only Google Play Services must be enabled for MagiskHide, the way how it does it by default (one or two processes, depending on your phone/ROM - if you screwed it up by enabling all proccess, details were discussed in Magisk General thread, if I remember correctly, look for one of the recent posts by @ipdev)

Of course, that banking app itself must be enabled for MagiskHide

More tips can be found in the @Didgeridoohan's Wiki (link to Magisk Github in the Magisk app)
[Magisk] MoL_82:
@Timmmmaaahh! and @Didgeridoohan: I recommend SudoHide by @Mikanoshi, which also runs in LSPosed. It can hide any app from seeing other apps. I use it to hide YTVanced from the Play Store and it works perfect.
[Magisk] Timmmmaaahh!:
That was fast!

Indeed! Same result here, freezing 'MagicalUnicorn' allows the banking app to run! That's awesome, thanks!

Odd to learn from this that much more sensitive apps (eg. verifying my identity with my government) is not utilizing the same method! I'm just glad freezing works, it was driving me nuts. I'll see what I can do with LSPosed, I don't have much experience with it.

that is wildly interesting! I have some research to do...

Thank you for adding this, will check that out! I've been using TeMeFi to detach YTV so far with much success.

You people are amazing! Cheers!
[Magisk] Stunntn:
Can I request a Device FingerPrint .

I was Hoping you could Actually add iPhones. To the list. Maybe start with the Newer ones?
[Magisk] zgfg:
Are you kidding?

MHPC is a module for Magisk, Magisk is only for Android - hence this module cannot be installed to iPhones

On the other side, on Android you cannot fake an iPhone (and btw who knows how that goes on iPhones - probably they have something different than ro props), hence adding iPhone 'fingerprints' would make no sense, neither simulating an iPhone, etc.

Or what would be MagiskHide props or Force Basic key attestaion for iPhones?!
[Magisk] Stunntn:
Yeah I didn't know if it was possible or not. But it would be a great feat if could be done.
[Magisk] zgfg:
You have to check these things on iPhone forums - first of all to understand what do you want, what is appropriate for iPhone architecture and what is available there

I don't know what would be an 'equivalent' of 'passing Safetynet' on the iPhone - once you will know and understand that, you could search on iPhone forums what kind of mods are available there
[Magisk] Didgeridoohan:
I'm guessing you'd like to make your phone look like it's an iPhone...

That's not quite how this works.

This module takes properties from various Android devices, properties that are used to identify them in different situations and let's you change those properties around on your device. IOS works quite differently, so your request unfortunately doesn't make any sense.
[Magisk] ipdev:
@Timmmmaaahh!

Happy to see the freeze (disable) method works for you.

I love your hidden Magisk name. :love:

---

To answer your question about the log file.

It is licensed under Apache 2.0

facebook SoLoader - GitHub - Link

That is why you see it in reference to library .so files.

Pointing back into the app directory so, it is unpacking and loading the lib files from be.keytradebank.phone.

Side note:

Looks like the app was also denied background location services.

It got rejected by SELinux, the avc: lines.

Cheers. :cowboy:
[Magisk] zgfg:
Updates for Xiaomi Redmi K20/Mi 9T, EEA, A12 fingerprints:

ro.build.fingerprint=Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys
ro.build.version.security_patch=2021-08-01

Thanks to @Wolfcity who getprop-ed them from his stock V12.1.1.0.RFJEUXM ROM (I tested by spoofing on my Mi 9T with Xiaomi.eu that's based on CN and everything was ok, SafetyNet passing)

---

Also, you can shorten your list/options for Certified fingerprints for Xiaomi by putting together Mi 9T and Redmi K20, as well as Mi 9T Pro and Redmi K20 Pro

They differ in ro.product.model being Mi 9T for one vs Redmi K20 for the other (and also Mi 9T Pro vs Redmi K20 Pro)

---

And a little digression - the attached schema describes the nomenclature for Xiaomi stock ROMs names/fingerprints.

Described also here:

What the letters in the MIUI version designation mean

MIUI V12.0.5.0. QFJMIXM - Android version M - Android 6.x (Marshmallow) N - Android 7.x (nugát) O - Android 8.x (Oreo) P - Android 9.x (Pie) Q - Android 10.x R - Android 11.x S - Android 12.x - device code (phone model) JA - Xiaomi Mi 10 Pro JB - Xiaomi Mi 10 JC - Redmi 9 JO - Redmi Note 9 JZ...

xiaomi.eu

Schema provides only four Xiaomi models (second and third letters in the ROM name), but for example for Mi 9T and/or Redmi K20 (davinci), those two letters will be FJ, while for Redmi K20 Pro and/or Mi 9T Pro (Raphael) the two letters will be FK, etc.

Thus the above ROM name V12.1.1.0.RFJEUXM means:

12.1.1 = MIUI version
R = A11
FJ = Redmi K20 / Mi 9T (davinci)
EU = EEA region (European Economic Area)
XM = Not locked for any particular SIM/carrier (Mobile provider)

PS: More pairs like Redmi K30 vs Poco X2 (phoenix) can be found from the app (screenshot):

MIUI Downloader - Apps on Google Play

MIUI upgrade app for Mi users.

play.google.com
[Magisk] dey18:
How to do what this module does without using Magisk because I have issues with using magisk on my phone?
[Magisk] Didgeridoohan:
Manually edit the prop files (build.prop, default.prop, etc). You'll need access to system though, so that means superuser access in some way (Magisk/other root management software or custom recovery). Plenty of guides about this all over the interweb.

Very easy to mess up, so make sure to keep a copy of the original files. It's also possible that the system partitions on your device cannot be set to rw, in which case you might be out of luck (this depends on what type of device you have, but many modern devices are starting to use read only system partitions that cannot be set to read-write). There are some ways to repartition a device like this though, so if you need to you can find this info here in XDA (there are a couple of tools available for this, but I currently do not have the links to those threads).
[Magisk] Didgeridoohan:
This is the key reason why they're in the list as separate devices.
[Magisk] dey18:
I am OK with extracting build.prop, device.prop files then changing them to the preffered fingerprint and replacing them with default ones.

I hope these are all the locations to get those

(I'm on lineage os 18.1 on a-only device)

/default.prop
/system/build.prop
/system-ext/build.prop
/vendor/default.prop
/vendor/build.prop
/product/build.prop
[Magisk] dey18:
Please specify if I missed any other files.

And I am stunned at your response speed.

Thank you.
[Magisk] Didgeridoohan:
That looks like it should be all, but it's hard to say for sure since it varies from device to device...
[Magisk] dey18:
So can I know how the module does this?

I can share the logs if you can check where all are my .prop files located.
[Magisk] Didgeridoohan:
The module just uses the resetprop tool, so it doesn't deal with prop files. A lot of it is described in the module docs.

Easiest way to find files would probably be to run something like this from a command line:

find / -name *.prop
[Magisk] zgfg:
If your system is not read-only, you can use apps like SetEdit to edit the props.

You could also edit the props file through TWRP, if you have the appropriate TWRP for your device and if TWRP has write access to system

However, most new devices (particularly all those originally deployed to market with A11) have READ-ONLY System As Root and systemless approach, through Magisk is the only way to make changes to the system - i.e., in that case you cannot do it without Magisk and its systemless mechanism (used also by this module)

EDIT: Reading now your further posts, seems that you have no read-only SAR and you will manually edit the prop files
[Magisk] zgfg:
Ok for Device simulation but if Edit device fingerprint changes only the fingerprint and security patch date, then they could be paired together

Or at least you can have then symmetric options for Mi 9T (Pro) and Redmi K20 (Pro) - currently one has four fingerprints for A10, the other only 3 and so
[Magisk] Dalbas123:
Can you please add a fingerprint for the Xiaomi mi 10t lite 5g android 11
[Magisk] Didgeridoohan:
As always:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] russel5:
@Didgeridoohan since v6.0 i'm can't add two same custom props. can you disable this like v5.4

on color os i'm need two same props with different start (post and late)
[Magisk] Didgeridoohan:
No need to set the prop twice in that case, just pick the "Both boot stages" option for the prop in question.
[Magisk] russel5:
but prop have different arguments with post 0 with late 1
[Magisk] Didgeridoohan:
Ah, that was pertinent info missing from the initial post...

Hadn't considered that use case, but it's obvious that it could be useful now that you mention it. It's an easy fix, so I'll look at getting that done during the coming week.
[Magisk] ipdev:
Not sure if it will work but, in the meantime you could try using a Configuration file.

MHPC Documentation - Configuration file - GitHub - Link

Cheers. :cowboy:
[Magisk] Helmasaur:
Hey,

After updating the ROM I am using (and Magisk at the same time), I realized that I could not buy an application on the Play Store. The error which is returned is: OR-PMSA-03.

I am not sure that I understand what is the use of this module. So I wanted to know if it could be the solution to my problem.

Thanks!
[Magisk] 73sydney:
1) Have you checked you pass SafetyNet? If youre using Magisk, the test is available on the opening screen or alternately, use this: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

An answer to this may tell you whether you need this module or not

2) If that passes, have you checked if your Google Play Store is Certified?

Open Google Play, go to Settings, then About and check the last line

If not "Certified", continue on...

Toggle Airplane mode on

Wipe data for Google Play Store, Google Play Services & (optionally) Google Pay (WARNING/DISCLAIMER: Any cards present will be removed and will need to be re-added)

Reboot

Toggle Airplane mode off

Wait 5 minutes

Check Google Play Store status again - as long as it doesnt say Not Certified you should be fine (It will change to Certified after some time)

The first result of a Google search for OR-PMSA-03 takes you to :

Fix payment issues on your account - Computer - Google Play Help

If you try to buy something on Google Play but your payment is declined or won't process, try the steps below. Troubleshoot payment and order issues If you've bought someth

support.google.com

But if you pass SafetyNet AND Google Play Store Certification, your next step will be to run through that Google error page as your payment issues may be unrelated to the above tests
[Magisk] Didgeridoohan:
@expressluke You ok there?
[Magisk] totyax:
Hi!

Safetynet pass doesn't really big problem for me, via this magisk module on custom roms (when magisk ramdisk=yes). For example su/props, and I choose Lenovo Note fingerprint.

Device unlock works via fingerprint, but my problem is, I can't use fingerprint in applications really. Fingerprint mismatch, or other messages come in. My question is, this module (or other) can help for me anyhow? Thank you.

My phone is K33a48 (Lenovo K6)