yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Fingerprints list updated to v110

Got a bunch of prints submitted over the past couple of weeks. So here goes... Lot's of thanks, as usual, to those whom help me keep the list somewhat updated and relevant. This time around those awesome people are (in no particular order) [MENTION=11244869]red_lnn[/MENTION], [MENTION=4612862]Johnny Eng[/MENTION], [MENTION=2038193]dron39[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=5293805]GtrCraft[/MENTION] and [MENTION=11210555]Kovacs-[/MENTION].

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 8T China

OnePlus N100 Europe

OnePlus N10 5G Europe

Samsung Galaxy A70

Samsung Galaxy Note 20 Ultra 5G

Samsung Galaxy S20 FE 5G

Updated

OnePlus 5

OnePlus 5T

OnePlus 7 (several variants)

OnePlus 7 Pro (several variants)

OnePlus 7T (several variants)

OnePlus 7T Pro (several variants)

OnePlus 8 (several variants)

OnePlus 8 Pro (several variants)

OnePlus 8T (several variants)

OnePlus Nord (several variants)

POCO X3 NFC

Xiaomi Mi 10 China
[Magisk] Johnny Eng:
Thank you so much savior!! ?

Now I can use banking apps.
[Magisk] zuelber:
Sorry for the newbie question but how could I set permission 440 for dg.bd and where can I found this file?

Thanks.
[Magisk] Didgeridoohan:
Perhaps it would be simpler to just use [MENTION=9317193]73sydney[/MENTION]'s module:

https://xdaforums.com/apps/magisk/m...7-1-22-pie-t3929950/post79643248#post79643248
[Magisk] GtrCraft:
POCO X3 NFC (Europe):

fingerprint: POCO/surya_eea/surya:10/QKQ1.200512.002/V12.0.4.0.QJGEUXM:user/release-keys

security patch: 2020-10-01
[Magisk] zuelber:
Looks like it's working now.

Gpay is now accepting my card and GPS says my phone is certified.

So this is whats I have done:

Installed Hardware off 1.1 by Displax module

enabled Magiskhide Props. I am not using any FP since there´s no FP for Android 10 (I am afraid of using Android 9 FP) so not sure if it's somehow helping.

Did all caches cleaning and here I believe is the trick. It only worked after toggling airplane on.

Will test it when I have a chance.

Just want to thank you all and Didgeridoohan for his patience with newbie users like me hehe.
[Magisk] Didgeridoohan:
Glad to hear that things are working now, but if you haven't set anything up in this module it's not doing anything and you don't need it at all.

From the sound of it the only thing you could benefit from is to use "Force BASIC key attestation" in this module rather than Hardware off to get an actual device's model as the prop value (but of course you could also just edit the files for that module and enter whatever model value you'd like). But if things are working, there's no need to change anything....
[Magisk] kryshnakishore:
Oneplus 6, OOS 10.3.7, Rooted with magisk 20.4 & using blue spark TWRP.

https://play.google.com/store/apps/details?id=com.leadsquared.nextgen

Root is not working for this app, can some one install & tell me if it is working for you.

It worked with OOS 10.3.6 Perfectly
[Magisk] Didgeridoohan:
That's not quite the topic for this thread...

Take a look at my guide here, and if you can't figure things out from there try the general support thread or see if one of the many "this or that app detects root" threads is suited for your app.
[Magisk] kryshnakishore:
Sorry, sure thanks for the link.
[Magisk] :
Hey there,

After submitting the SM-A705FN fingerprint to be added, I'm now facing some eval type HARDWARE issue, I did try using force basic attestation, device simulation, nothing seems to work, I am wondering if it's becuase I am doing something wrong or simply the device is doomed.

Note: I did check the documentation and did some research about the topic, I am just posting to see if it's me that I am doing something wrong or the device is doomed.

Thanks!
[Magisk] Didgeridoohan:
The key to fixing evalType=HARDWARE is to change your model to one that is

different

from your actual device. Did you try that? Pick a device that's as close to your own as possible.
[Magisk] carlos974:
Attached is the fingerprint of the Samsung Galaxy Tab E 9.6 SM-T560:

Samsung Galaxy Tab E 9.6 SM-T560 (4.4.4):Samsung:SM-T560=samsung/gtelwifixx/gtelwifi:4.4.4/KTU84P/T560XXU0APL1:user/release-keys

I tested it, Play Protect certification: the device is certified!

SafetyNet: Certificate granted!
[Magisk] IanWorthington:
Is it worth reporting fingerprint updates here? If so, here's the latest for the ASUS ZENFONE 7 PRO:

>adb shell getprop ro.build.fingerprint

asus/EU_I002D/ASUS_I002D:10/QKQ1.200127.002/29.14.53.5_20201111:user/release-keys

>adb shell getprop ro.build.version.security_patch

2020-10-05

>adb shell getprop ro.product.manufacturer

asus

>adb shell getprop ro.product.model

ASUS_I002D
[Magisk] garylawwd:
Xiaomi Mi A3 Latest Global V11.0.23.0

Fingerprint:

Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.23.0.QFQMIXM:user/release-keys

Security Patch Date:

5th November 2020

Manufacturer:

Xiaomi

Model:

Mi A3
[Magisk] rpiquet:
Hi Didgeridoohan, Any chance to add y device Samsung Galaxy M31 (SM-315F) into fingerprint list?

I tested it with Samsung M21 (SM-215F) and it didn't work.
[Magisk] Didgeridoohan:
First, there's always a chance a new device will be added to the list. But:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

Second, if you tried one of the certified prints included in the module and still couldn't pass CTS there's a really good chance that there is something else going on. Take a look here for more tips:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Magisk] Displax:
Pixel`s update:

Pixel 2=google/walleye/walleye:11/RP1A.201005.004.A1/6934943:user/release-keys__2020-10-05
Pixel 2 XL= google/taimen/taimen:11/RP1A.201005.004.A1/6934943:user/release-keys__2020-10-05
Pixel 3=google/blueline/blueline:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 3a=google/sargo/sargo:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 3a XL=google/bonito/bonito:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 4=google/flame/flame:11/RQ1A.201205.008/6943376:user/release-keys__2020-12-05
Pixel 4 XL=google/coral/coral:11/RQ1A.201205.008/6943376:user/release-keys__2020-12-05
Pixel 4a=google/sunfish/sunfish:11/RQ1A.201205.008/6943376:user/release-keys__2020-12-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ1A.201205.011/6966805:user/release-keys__2020-12-05
Pixel 5=google/redfin/redfin:11/RQ1A.201205.011/6966805:user/release-keys__2020-12-05
[Magisk] ultradj83:
Hello there.

On Galaxy S10+ (SM-G975F/DS), setting fingerprint from Galaxy A3 2015 (SM-A300FU) to revert to basic key attestation (other Samsungs don't work), there's no more chance to call Google Assistant by "Hey Google" voice match when screen is off.

The option is not available in the settings, maybe because it's not supported on SM-A300FU.

Any workarounds?

Regards
[Magisk] Didgeridoohan:
Pick a device manually from the included list that does have that feature...
[Magisk] ultradj83:
Unfortunately any other devices I tried fails in reverting to basic key attestation.

I don't know if this is normal, maybe all other Samsung models, not only the latest, support hardware key attestation...
[Magisk] Didgeridoohan:
Any device that shipped with Android 8+ should in theory have hardware backed key attestation (that's when Google started enforcing it), but there'll also be earlier models that have it.

For a while now, from what we've seen, it hasn't mattered what device you pick as long as it is different from the actual device you're using.

I can't say what's going on with your device, but it's possible that Google has changed something again. That's not something I can test or verify though, since none of my devices uses hardware backed key attestation.

There's also a possibility that something went wrong with they module, of course, so a set of logs from when you have another model set and SafetyNet fails could be useful.
[Magisk] bartleby999:
Have you tried a custom setting - Change ro.product.model to a Galaxy S10 (SM-G973F) that is the closest device to yours so should maintain all functions.

That's all I needed to do on my Galaxy Tab S6 to force Basic.
[Magisk] Didgeridoohan:
Fingerprintslist updated to v111

Here's a bunch of updated and a couple of new fingerprints, provided by these awesome individuals: @GtrCraft, @carlos974, @IanWorthington, @garylawwd and @Displax. Thank you!

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

New

ASUS ZENFONE 7 Pro Europe

POCO X3 NFC Europe

Samsung Galaxy Tab E 9.6

Updated

Google Pixel 2-5 (all variants)

Xiaomi Mi A3 Global
[Magisk] isoladisegnata:
How edit for my app banking? Dont hide for me
[Magisk] Didgeridoohan:
I think you've ended up in the wrong thread... General app hiding questions are better suited for the Magisk general support thread or one of the many "bank app detects root" threads.

Start by taking a look here, and then try to find a more suitable thread if you need further help:

Hiding root and passing Safety Net:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com
[Magisk] limuc:
Hi Didgeridoohan,

thank you for your great work. I also use the program to be able to use Gpay under root, unfortunately I can no longer do this under Android 11 from December (Pixel 4a) with MagiskHide 110, so I removed root and closed the bootloader to use Gpay.

Now my question: Do you think that the new 111 variant enables me to get Root AND GPay again?

A second question: Although my device is no longer rooted and the bootloader is closed and I have reflashed the stock ROM (with -w), is the phone shown in the Win Explorer as Nexus 5?

Thanks for any help!

limuc
[Magisk] Didgeridoohan:
Even though GPay was failing, were you still passing SafetyNet? If so, the module was working just as intended and GPay was failing for other reasons (here's a collection of resources for GPay: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Google_Pay). The v111 fingerprints list update would make no difference really, since it just adds the latest device fingerprints. The older prints used in v110 are still certified and would work just fine as well...

And about showing as a Nexus 5 in Windows Explorer, that's likely just a cached value on your PC.
[Magisk] limuc:
Thanks, SafetyNet is passing but 'Play Protect Certification' is negativ.

The showing Nexus 5 is little mysterious, deleting all caches on two win-machines there is no effect, but on my Linux-mint there is showing Pixel 4a. Tomorrow I will test on an other win-machine.
[Magisk] Didgeridoohan:
I didn't mean if SafetyNet is passing now, but before you wiped everything. GPay can fail even when a fully passing SafetyNet, and this module only helps with SN.

Play Store certification can usually be fixed by clearing data for the Play Store.
[Magisk] pndwal:
Guess you're meaning before restoring stock/ locking bootloader Play Protect showed Not Certified? As stated, clearing Play Store data would likely have fixed this...

Re Nexus 5, likely you set up windows connection while MHPC was configured for Force BASIC key Attestation using default setting, which spoofs Nexus 5 in Model prop(s) on Google devices. I imagine windows just retains original model associated with device ID... Uninstalling and reinstalling the drivers may have more effect than clearing caches... PW
[Magisk] limuc:
Good news: I tried again to bring Root and Gpay together on Pixel 4a. It worked.

However, it only worked if I approved my device (Pixel 4a) as 'Nexus 5' (as suggested by your system), if I took the correct name, it didn't work.

Now with 'Nexus 5', 'SaftyNet' and 'Play Protect Certificate' are positive. The setup of PayPal in Gpay worked, tomorrow I'll see if it works in real life.

Thanks again!
[Magisk] limuc:
Thanks, I will try it!
[Magisk] pndwal:
Good result.

Nb. You must NOT select the actual model for Force BASIC key Attestation option as it's a simple MISMATCH with actual model that causes fallback to BASIC Attestation. (Using actual model will do nothing.)

It's therefore best to manually select a close/similar model to spoof from same Manufacturer for compatibility with model/OEM specific functionality.

For Pixel 4a, I'd be choosing Pixel 4XL etc, even though default Nexus 5 value works. It's not about passing only; that's the easy part. Using anything other than actual model (even 'creamcheese') will cause mismatch and therefore fallback to BASIC, but this will do nothing for OEM's special features/functions. PW
[Magisk] 41rw4lk:
I can't get props to run. I've uninstalled busybox ndk and propshide modules, deleted the folder from data and uninstalled magisk manager. I did a clean install of magisk manager, and both modules (rebooting in between both installs), but nothing. I have root in terminal, but when I run the props command it just says 'inaccessible or not found". I've attached the propshide logs and magisk logs.

I'm running a Pixel 3a XL (bonito) btw.
[Magisk] Didgeridoohan:
@41rw4lk Looks like you have Magisk's Core Only Mode active. Delete /cache/.disable_magisk, reboot and you should be good to go.
[Magisk] 41rw4lk:
Brilliant, that was it. All sorted.Thanks
[Magisk] der_Kief:
@Didgeridoohan

is Mi 10T Lite gauguin supported ?

Cannot find it in fingerprint list.
[Magisk] Didgeridoohan:
It's not on the list, no. And the only variant available on Android Dumps seems to be the Redmi Note 9 Pro. If you've got the print I'd love to add it.
[Magisk] der_Kief:
@Didgeridoohan

i already switched to Xiaomi.eu ROM so i think its not possible as i believe you need the one from Original vendor ROM ?

And the corresponding counterpart is the Redmi Note 9 Pro 5G i think.

Is it mandatory to use the matching device fingerprint or is it possible to use anyone ? If yes any disadvantage ?
[Magisk] Didgeridoohan:
It is not necessary to use the exact fingerprint. As long as you have a certified print SafetyNet should pass (as long as all other prerequisites are fulfilled). There are of course some possible disadvantages, mainly with your device being perceived by different apps and services as the print you're using rather than your actual device. Picking a print from a device as close as your own as possible is preferable if you can't use the correct one.
[Magisk] paolocorpo:
Dear Developer I am back now to ask your relevant support

I have recently used a fingerprint for my XIAOMI Mi A1 that is using last update of SO (Android 9)

I discovered to achive the certification of Play Protect only choosing Mi A1 with android 8 but this is not a problem to me

Now I have a new task

I have to use an app MINIMED that manage a insulin pump

Unfortunately this app is certified to run only with few devices (some Samsung and some Google Pixel)

Of course my Xiaomi Mi A1 is not accepted

I have tried to use your Magisk module to fix my issue

I am in front of a strange situation

If I use fingerprint of Pixel 3 and 4 (any model and any android version) my device is recognized as Nexus 5 !!

DO you know the reason why ?

Thanks

Paolo
[Magisk] Didgeridoohan:
I don't know the reason why, but I could make a guess (would have to look at the logs for anything more than that)... And that guess would be that you have are simulating a Pixel device while having "Force BASIC key attestation" enabled and set to the default value (Nexus 5 for Google devices).

But, like I said, that's a complete shot in the dark so logs would be nice...
[Magisk] princedede:
So guys, I can't get newer Netflix app to launch even after using this module and having passed all my cts profile on los 18. Only old Netflix app works. Version 4.15 downwards...
[Magisk] Didgeridoohan:
CTS and Play Store certification only affects the availability of the app in the Play Store (as far as I know, and even that's not entirely reliable judging from different reports). If the app doesn't start there's something else going on.
[Magisk] paolocorpo:
You are the boss of this module and not only ...

Your hypothesys is CORRECT

The setting was wrong

NOW i have a fake Pixel 3 (really a Mi A1) but I am now able to use my app Minimed !!!!

Thank you so much

Paolo
[Magisk] Wafggy:
Hi there.

I have a Redmi Note 9s running stock MIUI 12 with android 10. My phone is failing to pass cts profile with evalType HARDWARE. To fix that is better using the

“Force BASIC key attestatioin”

from the

MagiskHide Props Config Module

OR install the

Module hardwareoff_1.1.zip

that I found linked in your documentacion on github?

And if the better is using the first one, I must pick one from fingerprints list (I don't know if this is the most suitable option) and maybe choose for Redmi Note 9 Pro, that is closest to my device? Or you suggest another better option here for my case?

Thanks in advance!
[Magisk] Didgeridoohan:
Hardwareoff will simply change your model to BASIC (IIRC), so if you're fine with that you can use that module (it's more flash and forget than MagiskHide Props Config). The reason I'm linking the relevant post in the docs is to give proper credits...

If you want more customisation without manually editing the script files you can use "Force BASIC key attestation". And, like it says in the manual, pick the device closest to your own for the best compatibility. The Note 9 Pro sounds like a good pick for you...
[Magisk] pratik8989:
Need help, not enable to change device fp, it changed once but now not working now, no error as well everything goes fine on terminal
[Magisk] Didgeridoohan:
If you need help with that you're going to have to provide more details. And preferably the module logs: https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] pratik8989:
Sorry using first time so, I want to change/spoof device

So what I'm doing is, Changing device fingerprint which changed successfully but device model and brand not changing ( changed first time don't know how )
[Magisk] Didgeridoohan:
Did you enable "Device simulation"?

Edit: And, again, if you're experiencing issues it's a good idea to include the logs.
[Magisk] pratik8989:
Yes device simulation is active

Sorry don't know how to take logs because I'm not getting any error during operation/in terminal, just Manufacturer and device model not changing, is there any other way to change it manually?

I'm on Android 11 custom ROM
[Magisk] Didgeridoohan:
I linked you the documentation on how to grab the logs. And there's an entry in the main menu named "Collect logs".
[Magisk] emanresu2:
Xiaomi Redmi Note 8 (ginkgo) Global ROM MIUI V12.0.1.0.QCOMIXM fingerprint

getprop returns:

[ro.build.fingerprint]: [xiaomi/ginkgo/ginkgo:10/QKQ1.200114.002/V12.0.1.0.QCOMIXM:user/release-keys]
[ro.build.version.security_patch]: [2020-09-01]
[ro.product.manufacturer]: [Xiaomi]
[ro.product.model]: [Redmi Note 8]
[Magisk] BlueMan_86:
New ROM, new Update :)

Device: Mi 10T / Mi 10T Pro EEA

Codename: apollo

Version: V12.0.13.0.QJDEUXM

Branch: Stable

Release Date: 2020-11-27

Android Security Patch: 2020-11-01 (1st NOV)

PS.. There is also for K30 Ultra... inside :)

You will see...

Thanks for your great module :)
[Magisk] Dreamchoco:
I have a Realme 6 with android 10, is it possible to choose the fingerprint edit of Realme X2 Pro that android 10 too? And what will happen if i try it??
[Magisk] Didgeridoohan:
That should be covered in the docs, here:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

and here:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Magisk] yasars:
Can you add for mi 10 europe android 11 V12.2.1.0.RJBEUXM...thx. I have not the rom...
[Magisk] Didgeridoohan:
Neither do I...

Take a look in the docs:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Magisk] carabot:
hello

is there a version for Mi 10 T Lite ( gauguin)?
[Magisk] pndwal:
Deleted.. wrong thread 🙄
[Magisk] Didgeridoohan:
That's been requested before, but so far nobody has submitted it:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Magisk] LuCeiFeR:
Worked fine on Samsung note 9 running Dr.Ketan ROM with android 10. Now, on lineage OS android 11 gives an error message for vendor partition .. Is the module supporting android 11?
[Magisk] Didgeridoohan:
Had no issues on my old Nexus 6 with A11 (ArrowOS), and there should be no general A11 incompatibilities...

That looks very weird and shouldn't have anything to do with the module. I'd guess it's the terminal emulator you're using that is having issues. Try a different one.

That's just a guess though, so if that's not the case I need to see the module logs.

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Magisk] Asma12:
It's possible to set a custom prop active only for a specific app? Or active for all system except for a specific app?

I need that an app doesn't see the changes to ro.product.name and ro.product.manufacturer
[Magisk] Didgeridoohan:
Not with this module.

The best you could do with Magisk, I guess, would be to use something like Tasker and some scripting that uses the resetprop tool to change the props back to the original value and then starts the app in question. Then once you close the app it could change them back again.
[Magisk] Asma12:
Thank you!

I'll try 😉
[Magisk] chowceal:
im just not understanding if this is what i need. i have an lg-v10 on android 7, and i dont believe there are updates anymore. my banking app requires at least android 8. will this module work? and how do i set it up? i have looked at it, and just dont know what to do.
[Magisk] zgfg:
For how to use the module - please read instructions in the OP post here, you can also find there the link to the GitHub with more detailed instructions

Module will work but nobody can guarantee you that it would trick your banking app to think that you have Oreo

You have to experiment - you can simply disable your changes if it won't eork and go back to your original prop values (or try another combination)

E.g., you can change device fingerprint, you can emulate another phone, or you can just change the props declaring the Android and SDK versions
[Magisk] salmanghiyas:
hello all,

i've rooted from magisk on my note 20 ultra sm-n985f/ds

i'm trying to edit build.prop from build prop editor

i just need to add

fw.max_users=3

fw.show_multiuserui=1

to enable multiple users on my phone

and I am unable to get the method from this thread, can someone please help me?
[Magisk] Didgeridoohan:
This is not a build.prop editor... The actual prop files will stay untouched.

What you want is the "Add/edit custom props" option (currently option #5 in the main menu after running the props command). Just pick that and follow the on screen instructions...
[Magisk] salmanghiyas:
would that be able to activate the multiple users options in sm-n985f/ds?
[Magisk] Didgeridoohan:
If all you need is to change those two props, yes.