yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Yup, that's been known for a few weeks now. It's even covered in both the latest changelog and the regular docs.
[Magisk] M1ster1:
Indeed, I probably missed it until a Bank app started to behave strangely.

In fact I thought that it was just one or two custom prop to edit to do the trick.

But no, I had to install the additional module "Universal SafetyNet Fix".

In my case (Xiaomi Note 10) just activating the latter made it pass.

Thanks for the links Didgeridoohan (y)
[Magisk] 73sydney:
Its OK, he lives for updates :)
[Magisk] c3k:
I was wrong. GPay went ok by itself.

Activating the (very old and different) A3 fingerprint still triggers the basicIntegrity, but not a problem anymore.

Thanks for all the support and patience.
[Magisk] jarton:
FINGERPRINT : Galaxy S9, Android 10

Official Stock Rom G960FXXSDFTL1

Samsung SM-G960F [Build Date - Dec 17 2020] Security Patch 01/01/2021

Samsung Galaxy S9 [SM-G960F] (10):samsung:SM-G960F=samsung/starltexx/starlte:10/QP1A.190711.020/G960FXXSDFTL1:user/release-keys__2021-01-01

"

######

## The above " was added to close custom printslist list early.

## Just to clean it up a little. Lines below will not display on screen.

## Due to updates in Magisk and/or mHide module.

## The rest of the file is now block commented to hide/clean it up further.

######

#

#

# Samsung SM-G960F [Build Date - Dec 17 2020]

#

# Device is on certified list

# Samsung Galaxy S9 starlte SM-G960F

#

# ro.system.build.fingerprint=samsung/starltexx/starlte:10/QP1A.190711.020/G960FXXSDFTL1:user/release-keys

# ro.build.version.security_patch=2021-01-01

#

# ro.build.version.release=10

# ro.build.version.sdk=29

# # ro.product.name/ro.product.device should use PRODUCT_MODEL in case of jpn model

# # ro.product.name/ro.product.device should use PRODUCT_MODEL in case of jpn model

# ro.system.build.fingerprint=samsung/starltexx/starlte:10/QP1A.190711.020/G960FXXSDFTL1:user/release-keys

# ro.product.system.brand=samsung

# ro.product.system.manufacturer=samsung

# ro.product.system.model=SM-G960F

# ro.product.system.name=starltexx

# ro.product.system.device=starlte

# ro.build.product=starlte

#

# # Pulled from build.prop
[Magisk] Kung-Foo-Kamel:
Does anyone have a FIngerprint for a Xiaomi Black Shark 3?
[Magisk] Alucard:
Hello can someone advise so i can find the root of this issue,i have the device Gome U9 on android 8.1.0 overseas,lately in pokemon go i got the message unable to authnticate,so i believe its cause of safetynet and latest updates,so is the solution to patch the fingerprint via props or other way,i understand its a very rare device.
[Magisk] Didgeridoohan:
Maybe... You likely need to pass CTS, and since that device isn't on Google's list of supported devices you can probably fix that by applying one of the fingerprints from this module. If that still doesn't work you might need to use the new Universal SafeyNet Fix as well. It's all described in the docs:

https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1
[Magisk] Alucard:
Thanks for the reply,the phone has a MEID number so i guess its on gogle?

I realised the problem its the only device i cant log in to pokemon go account,also google contacts are not able to sync,for example adding a new contact doesnt appear to the account after,any ideas on what it might happened cause it used to work,i will look at your guides also!
[Magisk] Didgeridoohan:
What I meant was that I couldn't find that device in Google's list of Google Play supported devices:

https://support.google.com/googleplay/answer/1727131?hl=en
[Magisk] Alucard:
Thanks for the interest wish i could borrow you my phone for 5 minutes ,you would find the solution and more!Haha,mainly i have issue logging in pokemon go account so i guessed its cause of safetynet pass.
[Magisk] Didgeridoohan:
That could very well be the case. If you do not pass SafetyNet (CTS profile) you might need to use a certified fingerprint from this module and/or the Universal SafetyNet Fix module linked in the docs I linked you previously.
[Magisk] Xanth0k1d:
Sony Xperia 10

Sony/I4193/I4193:10/53.1.A.3.85/053001A003008502135191194:user/release-keys

For Sony kirin, the l4193 model, which cant be flashed with the sony emma...

I downloaded the firmware with Xperifirm and used UnSIN by @IgorEisberg (thanks!) to get a .ext4 file from which I took the build.prop. (Attached the build.prop too)

Havent test the stimulation stuff though...

Oops can't seem to attach so this is the google drive link if anyone wants it: https://drive.google.com/file/d/1Fz5PThgVu1uLbcARVtr0oYvKs7DrSyXB/view?usp=sharing
[Magisk] HalfACalf:
Hi,

First post here.Just flashed a Samsung Galxy S6 with LineageOs 17.1

Worked flawlessy, except that netflix did not show up in Play Store.

After googling a bit I end up here.

Have been trying to get this to work since yesterday.

Installed Magisk Manager, then I downloaded Magisk installation package through that app.

I then run the installation in TWRP.

Rebooted, and installed MagiskhideProps Config through the Magisk Manager app.

Enabled a terminal and went

su

props

Then selected 1 to alter the device fingerprint, then f.

Selected samsung in the list, located the galaxy S6 and selected that.

It then asks if I want to reboot and so I did.

When rebooted if I go into props again and select to update the fingreprint, it says that it has the old fingreprint and nothing is changed.

I have tried different boot phases but there is no effect when I try to overwrite thefingerprint prop

It is just ignored.

Anyone have any suggestions on what is wrong here?
[Magisk] Didgeridoohan:
@HalfACalf I can't say anything without seeing the module logs. Take a look here:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] lukjod:
Guys any advice how to use on s20 ultra exynos dub5 android 11. Which option to use on termux to made google pay to work and make my bank apps to use fingerprint. universal fix works ok with google pay but makes bank apps not to use fingerprint so not good enough. Any advice?
[Magisk] Didgeridoohan:
You won't be helped by this module. The only thing that can possibly help you with fingerprint authentication is the test version of the new Universal SafetyNet Fix module that you'll find on it's GitHub.

Edit: If you ever start using a custom ROM you might need this module to set a certified device fingerprint to pass CTS, but that's about it...
[Magisk] lukjod:
Can't find it last is 1.1.1, can You please share link to try?
[Magisk] zgfg:
You nean SafetyNet-fix?

Simply search to find its thread on XDA and in the OP posts there find the link to GitHub for its official download
[Magisk] Didgeridoohan:
Apart from that was said above you'll find the test version in a pull request on the modules Github repo.
[Magisk] Lord Sithek:
Shim the keystore service instead of replacing it by kdrag0n · Pull Request #13 · kdrag0n/safetynet-fix

This method is more portable, does not require a different executable for each Android version, and avoids breaking ROMs with heavy keystore customizations. It works by injecting a shared library i...

github.com

I think this is what you are looking for
[Magisk] lukjod:
I have installed last beta version but unfortunately Google pay doesn't work, it senses phone is rooted, fingerprints works Ok on bank apps
[Magisk] Didgeridoohan:
If you've got problems with that particular module you're much better off posting in its thread...
[Magisk] lukjod:
One more question, will it work if it says uncofigured?
[Magisk] Didgeridoohan:
I wouldn't know, never used GPay... But there are a couple it GPay discussion threads here in the Magisk forum where it might have been discussed. I'm sure someone will chime in here eventually though.
[Magisk] lukjod:
Ok had to clear data and cache of play services and Google pay then use gpay sqlite fix magisk module found on xda, add cards again and it works well
[Magisk] Alucard:
Tried both,is the empty serial number causing this?
[Magisk] Didgeridoohan:
No idea... I don't even know what you mean by that.

I'm going to assume that you do not pass CTS after setting a certified device fingerprint with this module and installing the Universal SafetyNet Fix module. If so, I'm not sure what it could be... You can find a bunch of resources on how to pass SafetyNet in my Magisk troubleshooting guide, maybe you'll find something there:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] Alucard:
Thank u,im really confused myself,i meant the serial number if the device is empty but i dont think it should cause any issues,will try every step again when i find the time,im just curious on where is the problem located!!
[Magisk] Displax:
Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.6.0.RFQMIXM:user/release-keys__2021-02-05
[Magisk] Didgeridoohan:
Fingerprints list updated to v118

Have had a few of these prints laying around for a couple of weeks now. To be honest, I almost forgot about them...

Anyway, thanks to @Displax, @jarton, @Marocco2 on GitHub and @Xanth0k1d for providing the prints. I'm always so grateful for the contributions everyone brings to this module.

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 list updates.

New

Sony Xperia 10

Updated

Samsung Galaxy S9

Xiaomi Mi 9T Pro China

Xiaomi Mi 9T Pro Europe

Xiaomi Mi A2

Xiaomi Mi A2 Lite

Xiaomi Mi A3

Xiaomi Redmi K20 Pro Europe
[Magisk] Lord Sithek:
And we are grateful to you that you keep maintaining this module for our benefit!
[Magisk] Displax:
NVIDIA update

NVIDIA/foster_e/foster:9/PPR1.180610.011/4079208_2513.0256:user/release-keys__2020-12-05
NVIDIA/foster_e_hdd/foster:9/PPR1.180610.011/4079208_2513.0256:user/release-keys__2020-12-05
NVIDIA/darcy/darcy:9/PPR1.180610.011/4079208_2513.0256:user/release-keys__2020-12-05
NVIDIA/mdarcy/mdarcy:9/PPR1.180610.011/4079208_2513.0256:user/release-keys__2020-12-05
NVIDIA/sif/sif:9/PPR1.180610.011/4079180_2513.0256:user/release-keys__2020-12-05
[Magisk] crazyriz:
After installed Magisk 22.0 ,safety net won't pass with this module, but it will pass without the module
[Magisk] Didgeridoohan:
I can't replicate... You need to provide more info than that, and the module logs.
[Magisk] gfrank227:
Hi all. Does anybody know of any valid fingerprints for a Fiii M11? It's not on the list but I would really appreciate if there was some way to add it. Thanks so much. Note there's also M11 Pro and M15 which I'm sure would be helpful to many people. Thanks
[Magisk] ipdev:
Hi.

The MagiskHide Props Config documentation explains the process.

Finding a certified fingerprint GitHub - Link

How do I submit a fingerprint? GitHub - Link

New and updated prints are always welcome. :D

Keep in mind, you can normally use a different device if yours is not in the list.

Best to pick a device closest to yours.

Can I use any fingerprint? GitHub - Link

--

I did a quick check, FiiO shows a M11, M11 Pro and M15 models.

No FiiO on Google's public certified list.

While looking about the device, I tried to download M11 FW 1.1.1 but, the download failed.

Cheers. :cowboy:
[Magisk] gfrank227:
Thanks so much for your detailed reply. Unfortunately, my device never passed safetynet after I rooted it, so the props method is not an option. I'm not really familiar with how to extract the fingerprint from a firmware download. I see what you mean about 1.1.1 failing. However, i'm using a rooted firmware with 1.1.0 which seems to download from their website just fine. If you are to find it without too much trouble I'd be grateful. Thanks in advance!

http://fiio-file.fiio.net/M11-ota-1.1.0.zip

EDIT: I'm making progress. I figured out how to identify the fingerprint. Now, I'm stuck because it fails. Based on the documentation, i'm guessing this is because the security patch date is incorrect. I tried to change it to the release date of 12/30/20, but this didn't work. Is there a way to tell this from the package what date to use? Thanks!
[Magisk] ipdev:
Did it pass before you rooted it?

If the only modification you did was to root a stock rom, then the fingerprint and security date will still be correct.

Make sure to enable MagiskHide in the Magisk app.

Settings-> Toggle MagiskHide on.

If the device is not Google certified, the stock fingerprint and security date will not be certified.

Using this module to set the fingerprint and security date to the same will give the same result.

You will have to pick a certified fingerprint with the matching security date.

The fingerprints included in this module have the matching security dates if necessary.

--

I downloaded an took a look at the M11 v1.1.0 OTA.

Used the recovery image from the OTA to pull the props.

It failed SafetyNet for me but.. ¯\_(ツ)_/¯

If you want to try, rename the attached file to printslist and copy it to /sdcard/

Custom fingerprints list GitHub - Link

--

A bit OT for this thread but, it would help me narrow something down.

Could you revert the changes you made, no need to unroot, and then reboot.

Then using a terminal app or an adb shell session.

getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g' >/sdcard/Download/m11-getprop.props;

Then attach the m11-getprop.props file to a post or send me a link to it.

The generated file should be in your Download directory.

It will help me fix an issue in my mHideGP script.

Even though this device is not on the certified.list, it triggered the certified.list MHIDE print configuration for some reason??

Interesting device for sure. ;)

Cheers. :cowboy:
[Magisk] Didgeridoohan:
@gfrank227 Like @ipdev already have told you, that device is not on Google's list of certified devices, and considering that both you and @ipdev have tested the print without success it's quite clear to me that there's no use for further testing... That devices print won't pass CTS. Another big hint is that it's using test-keys. Certified devices use release-keys.

And it's got nothing to do with the security patch date. That print is from a build that is old enough for that not to matter at all.

To pass CTS you need to pick a different device's fingerprint, one that is certified by Google. The included list has 500+ prints to choose from, so take your pick. Usually it's best to pick a device that's as close to yours as possible, but in not quite sure what that would be in this case. Look around and test a print the you think looks good.

Caveat: it's also perfectly possible that just changing the device fingerprint isn't enough to pass SafetyNet. There are many things that can trigger both basic integrity and the CTS profile. If you're still failing after picking a print from the included list, take a look here for more guidance:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] gfrank227:
OK good to know. I had tried a different fingerprint which passed SN but was causing other problems with Netflix. I tried another device which uses the same Android version, 7.0. In theory, this should be OK, and it did pass the SN. Thanks for the info regarding the test-keys.
[Magisk] Displax:
Is there still issues with it?

Anyway, actual print for Mi A3 Europe:

Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.3.0.RFQEUXM:user/release-keys__2021-01-05

P.S. Discussion question about old prints from different android versions for one device... Does it really exists any practical or other sense to store them? I don't see any reason (exclude historical) for this, whatever i think.

Printlist could be much cleaner (and less "heavy") when it has only latest prints for latest rom build.

Yes, I remember my "bomb" with old prints, but is was only side effect :)
[Magisk] Didgeridoohan:
I had forgotten about that, but now that you mentioned it I remember why that particular print is causing issues and breaking the resetprop tool.

There's a character limit on prop values that you set with the setprop command, and thus also resetprop. 91 characters to be more precise, and the print for that device is 93 characters long (all three variants). I've brought that up with John previously, and I don't think there was any reason why the character limit for resetprop couldn't be lifted (this is a bit outside my area and I can't give any details on why the limit is there and so on, but if someone wants to go looking they can surely find something on this in the AOSP and Magisk code). Seems like it was forgotten about at some point though (not really high priority). I'll bring it up again...

Regarding historical prints, I have been playing with an idea to keep two prints lists. One with only the latest, and one with previous prints (just for completeness and giving whomever want it the possibility to use an old print). That would, as you say, keep the prints list a lot cleaner. I might revisit that idea...
[Magisk] ineedroot69:
So i was reading this thread back from 2018 and they recommend this module and also said if i pass safetynet test i would most likely be "play protect certified" too?? i want to fixed this play protect not certified issue so i just need my previous valid release-keys is that correct??
[Magisk] Didgeridoohan:
Does that contain the FrankeNDK Busybox though? I didn't think he'd done that yet...

[MENTION=8126387]martyfender[/MENTION] Could you test the attached test module? I simply added a check for a 0 byte file and re-run wget with -q if that's the case. If you could uninstall the previously installed module and install this one clean, and then supply the logs after you've rebooted, I'd be grateful.

Edit: Removed the zip. It no longer serves any purpose.
[Magisk] martyfender:
Yes they are. I would like to find a newer, even more expensive 7-8" tablet that has TWRP built for it and is confirmed to work with Magisk. These were ~$70. If anyone has any ideas please let me know. I know, OT here, maybe I should ask in the general forum.

Thanks
[Magisk] martyfender:
Here are the logs. I am on [MENTION=3306843]kantjer[/MENTION] 's build from today. Your module appears to be working correctly.
[Magisk] kantjer:
FYI, my build is done with NDKr10e, no FrankeNDK yet.
[Magisk] Didgeridoohan:
W! T! F!

Now everything is working exactly as it should. No gettime error or anything! Is that the device that previously had issues? Could you test on a different device? And maybe also do a clean install of the repo version, just to see what happens...
[Magisk] martyfender:
Here are the logs for the second device on [MENTION=7187684]ianmacd[/MENTION] 's build from today.

I will do the clean install from the repo on the device I had problems on.
[Magisk] martyfender:
Here are logs of a clean install from the repo. Busybox downloaded this time. I disabled and un-installed the module, then rebooted before installing the repo module.
[Magisk] Didgeridoohan:
Everything looks and works fine... And the only thing that's changed since yesterday is that you've flashed a new Magisk build?

Could you run the wget command again (without -q) and see if there's any difference this time around?
[Magisk] martyfender:
At work now, but tonight after 11 Eastern daylight time.

I do have the newest tablet of the 4 with me without Magisk Hide Props Config, but a fresh install of the rom I could run the command on at dinner break.
[Magisk] Incrovantilist:
I'm trying to improve magisk hide with this module. I'm using Lenovo Zuk Z2 plus and have no issues with regard to Safetynet passing. Just that magiskhide fails with Google Tez app alone. It's a pain in the ass to get Tez working with root & magiskhide failing because with each update to Tez, google is updating its security policies. I read in module description that it is possible to improve magisk hide with prop editing. Can someone guide me through the process of doing so? If anyone has a particular solution for hiding root from Tez (other than Disabling play services telephone permissions or using Tez hider app - - Both aren't working now), please let me know.

Update - Tried to keep improve hiding Active but nothing changes with Tez.
[Magisk] martyfender:
i get the same results as previously with those commands on this newer tablet.
[Magisk] Didgeridoohan:
Ok... I've got a FrankeNDK built Busybox for you to test. Download the attachment and then unzip it and drop it in /sbin/.core/img/busybox-ndk/system/xbin/, replacing the one that's already there. You can confirm that it's working by running busybox in terminal, and it should have a header showing it's by topjohnwu. If not, a reboot might be necessary.

After that, run the wget commands again. Let's hope...
[Magisk] martyfender:
Here is the output of the 2 commands, from this post:

https://xdaforums.com/showpost.php?p=77288353&postcount=493

You had a third command with -d in it that you did not ask me to run.

u0_a90@NX16A8116K:/ $ su
usercontent.com/Didgeridoohan/MHPCBB/master/busybox-x86 <
Connecting to raw.githubusercontent.com (151.101.184.133:443)
wget: note: TLS certificate validation not implemented
busybox 100% |***************************| 1370k 0:00:00 ETA
u0_a90@NX16A8116K:/ #
usercontent.com/Didgeridoohan/MHPCBB/master/busybox-x86 <
wget: note: TLS certificate validation not implemented
u0_a90@NX16A8116K:/ #

The first command shows it downloading, the second, does not even though files were created:

Unlike the last time, the first command creates a file of 1.3 M and like the last time with the -q, it also creates a 1.3M file, despite no indication with percentages that it is downloading?

I copied and pasted the commands a second time to confirm since the selection process to copy is so, very very touchy.

Man, it is to hard to select text and copy it in these code boxes reliably. That is how I do the commands versus typing them out each time. On Linux, with the mouse, it is easy, versus Android. It is hard if the code box is small and much easier without the code box. That was all on the tablet I had problems with, in the first place.

EDIT:

u0_a90@NX16A8116K:/ $ su

han/MHPCBB/master/busybox-x86; md5sum /sdcard/busybox-d; <

Connecting to raw.githubusercontent.com (151.101.184.133:443)

wget: note: TLS certificate validation not implemented

busybox-d 100% |***************************| 1370k 0:00:00 ETA

170133693c4af03a6f311179793569ec /sdcard/busybox-d

u0_a90@NX16A8116K:/ #

u0_a90@NX16A8116K:/ $ su

u0_a90@NX16A8116K:/ # md5sum /sdcard/busybox

170133693c4af03a6f311179793569ec /sdcard/busybox

u0_a90@NX16A8116K:/ # md5sum /sdcard/busybox-q

170133693c4af03a6f311179793569ec /sdcard/busybox-q

u0_a90@NX16A8116K:/ #

u0_a90@NX16A8116K:/ $ su

u0_a90@NX16A8116K:/ # md5sum /sdcard/busybox-d

170133693c4af03a6f311179793569ec /sdcard/busybox-d

u0_a90@NX16A8116K:/ #

If I'm not mistaken, I believe all three files have the same md5 checksum. Is this the results you hoped for?

Thanks
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] [MENTION=4544860]osm0sis[/MENTION] That's a bingo!

Thank you for testing. That means everything is working as it should. The reason you don't see any download progress bar with the second command is the -q option (means quiet). It was likely failing earlier because it couldn't calculate the ETA, and disabling the progress bar fixed that.

Now I'm curious as to which of [MENTION=3306843]kantjer[/MENTION]'s builds you were using the first time around, and which one you used when you installed the martyfender-test.zip. Something changed between those two build which made the Magisk internal Busybox work, without FrankeNDK.