yashsingh1/xdaforums huggingface dataset:
[Magisk] sergey1977:
after reboot didnt work, in terminal - permission denied. must reboot several times before is safetynet pass. mi 5s+. magisk 16.7
[Magisk] Notonlyeyes:
[MENTION=4667597]Didgeridoohan[/MENTION] thank you

Update Huawei P8 Lite 2017

FW Oreo PRA-LX1 8.0.0.367(C432)

fingerprint=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/367(C432):user/release-keys
[Magisk] Didgeridoohan:
Fingerprints list update, v26

Added and updated fingerprints for Huawei P8 Lite and Xiaomi Mi 5S Plus. Thank you [MENTION=4247344]_Ayhan_[/MENTION] and [MENTION=4553005]Notonlyeyes[/MENTION].

[MENTION=8701255]gingin88[/MENTION] The Mate 9 fingerprint did not pass ctsProfile on my test devices, so I have not added it to the list. Thank you anyway.
[Magisk] probanditz:
[MENTION=4667597]Didgeridoohan[/MENTION]

Here's the fingerprint for P10 Plus: HUAWEI/VKY-L29/HWVKY:8.0.0/HUAWEIVKY-L29/368(C636):user/release-key
[Magisk] iamleeeeeeeeee:
Im having trouble with my cts profile as it is being false. Thought this module would do the trick but will this work for my samsung j7 pro running LOS 15.1? Im sorry im new in here.
[Magisk] Didgeridoohan:
If it's just ctsProfile that fails, you should be able to fix that with this module, or any module that changes the device fingerprint (Universal SafetyNet fix, Device Spoofer Tool, etc). What this module does different from most others is that I maintain a list of certified fingerprints you can use, instead of just hard-coding a set fingerprint.

I don't have one for your particular module, but you should be able to use any certified fingerprint to pass SafetyNet. The vendor mismatch you experienced with USNF might be because it uses a different fingerprint though...

If you can get a hold of a stock fingerprint for your device you can use that, and if you provide it here I can also add it to the list. Take a look here:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] milomak:
Are build.props updated on the go?

So for instance I can boot my phone with Magisk running and my bank app rejects saying it has spotted root

Uninstall Magisk

Run app again and I can access my banking app.

How can i get the state the phone is in at this point?
[Magisk] saulin78:
Will this work for Android TV Boxes? can You add support for the Nvidia Shield Android TV?
[Magisk] Didgeridoohan:
I make that distinction for a reason. The devices found under the Redmi menu are released under the brand Redmi, while the Xiaomi menu contains devices released under the Xiaomi brand.

Xiaomi's different brands and models are confusing (and annoying), but they won't be merged...
[Magisk] zgfg:
Xiaomi Mi 9T MIUI 12, Android 10, EEA latest:

Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V12.0.3.0.QFJEUXM:user/release-keys

2020-10-01
[Magisk] Didgeridoohan:
Module updated to v5.3.6, fingerprints list to v106

This is mainly an update of the fingerprints list (and boy have you guys been submitting a bunch!), but I also figured I'd do some minor updates to the ui for the "Force BASIC key attestation" feature. A small attempt at making things clearer for all the new users that are dropping in as Google updates the Play Services to use hardware backed key attestation for more and more devices (maybe). There's also been some significant additions to the documentation lately (not specifically in this update), especially regarding warnings on what changing prop values might actually do to your device (something that I foolishly took for granted that people now about).

Anyway, before the changelog, here's a huge thank you to everyone contributing with device fingerprints to the list:

[MENTION=3559445]geekopa[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=8970704]Fangshing87[/MENTION], [MENTION=7786725]zgfg[/MENTION], [MENTION=6348248]malowz[/MENTION], [MENTION=6345368]Displax[/MENTION], [MENTION=2038193]dron39[/MENTION], [MENTION=11130029]dynux90[/MENTION] and [MENTION=7786725]zgfg[/MENTION]

Changelog

v5.3.6

Updated the menu item for picking a device manually for the "Force BASIC key attestation" feature to better match the menu option. Press "f" to pay respect.

Minor updates to the "Force BASIC key attestation" menus to be more clear and informative (hopefully).

Added fingerprints for Nvidia Shield TV 2015, 2015 Pro, 2019 and 2019 Pro, OnePlus 8T (several variants), Redmi Note 8 Pro	Global and Xiaomi Mi 10 Lite 5G Global and Mi 10 Ultra. Updated fingerprints for Nvidia Shield TV 2017, OnePlus 6, 6T, 8 (most variants) and 8 Pro (most variants), POCO F2 Pro European, Samsung Galaxy A40 and Note 20 Ultra 5G and Xiaomi Mi 9T Europe and Global, Mi A2, Mi A2 Lite, Pocophone F1 and Redmi Note 8. List updated to v106.
[Magisk] Displax:
Hi. Just little fixes needed:

It`s now double NVIDIA (foster_e_hdd) lines in prints. Just delete "Nvidia Shield TV Pro (8.0.0 & 9)" lines from prints.sh and readme.

And rename "Nvidia Shield K1" to "Nvidia Shield Tablet K1".

Thanks.
[Magisk] zgfg:
First off all thank you for the whole work and always a patient support (no matter how was the question or claim)?

Today I played for a while with MHPC, options 1 and 3 - since so far I never really needed to spoof the fingerprint(S).

Ie, I only needed Basic CTS so far and to add or edit some custom props (and until I started to use my own ad-hoc module and system.prop to manage the needed props)

So I tried (1), selecting my own Xiaomi Mi 9T eea device and (franklx I was little surprised) it didn't note me that I already have exactly the same fingerprint (QFJEUXM 12.0.3.0 I did submit xou) and that there is no need to change anything and reboot.

All observations were the same with option 3 later, when I asked to emulate my own device

I closely inspected the MHPC generated system.prop and found that it wanted to 'change' five props:

ro.build.fingerprint=

ro.bootimage.build.fingerprint=

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

and

ro.build.description=

davinci_eea-user 10 QKQ1.190825.002 V12.0.3.0.QFJEUXM release-keys

I was surprised that you have (and the correct one) algorithm how to derive ro.build.description (since you only ask for submitting ro.build.fingerprint - a little diffrrent one)

But when I compared to my stock props, I found a discrepancy:

- my stock ro.system.build.fingerprint and ro.odm.build.fingerprint are indeed equal to ro.build.fingerprint

- but ro.bootimage.build.fingerprint (stock value) is little bit different, it starts with

Xiaomi/davinci/ not Xiaomi/davinci-eea/ (like the other three) and hence it is a bit shorter:

Xiaomi/davinci/davinci:10/QKQ1.190825.002/V12.0.3.0.QFJEUXM:user/release-key

However, even with that/your wrong ro.bootimage.build.fingerprint it passed SafetyNet, so I wonder are all these others prints you change really important?

Indeed:

- you always ask only for ro.build.fingerprint (and ro.build.version.security_patch), not for the other four

- when I used to test some other fingerprints like Huawei on my Xiaomi phone (I found them elswhere but wanted to verify before submitting for your module), I always changed only ro.build.fingerprint while keeping my other prints on stock Xiaomi values, and it was ok to pass

- to the other side, just missing correct caps in ro.build.fingerprint is enough to immediately fail SN

Btw, I also realized that Moon has changed its phase once again -now if I don't spoof ro.build.model it falls again to CTS Hardware attest, finds that Bootloader is unlocked and fails CTS/SN (the whole thing changed for me three times upside down last months)

It's all pretty chaotical and not properly dependent on the G side: my ro.build.version.release equals to (Android) 10, but with a fingerprint for e.g. Huawei Mate 9 with Pie (fingerprint also 'encodes' the Android version) it still passes SN
[Magisk] Didgeridoohan:
[MENTION=6345368]Displax[/MENTION] That's kind of funny... I didn't realise you were posting the same device. I'll get the duplicates out in the next update.

[MENTION=7786725]zgfg[/MENTION] Most of the time there's actually a method to my madness. I'll try to cover your observations one by one.

I don't do any checks to compare the device you have against the fingerprint the user picks/the device they want to emulate. Never felt that it was necessary...

The ro.build.description is most of the time easy to derive from the information in the fingerprint. There are discrepancies with some OEMs (if I remember correctly), but that's never been much of an issue. I started emulating it a while back (can't even remember when that was) since it was requested by a bunch of users and I wanted to see if I could hack together a method to automatically get the necessary information from the print. Spoiler: I could. Is it necessary to change the description prop? Most likely not, but so far it hasn't hurt and it can be disabled by the user if they wish.

Tangent: that's actually mostly what this module is about. I see a need somewhere, or someone asking about a feature, etc, and then I play around and see if I can get things working. It's just a playground for me to test different kinds of shell script hacks and see if I can get things working in different ways. That there are then some people that finds it useful is just icing on the cake.

Now, about the different fingerprint props...

The one that matters for SafetyNet is ro.build.fingerprint. The other ones, for the different system partitions, are only changed if they are already found on the device. I don't add any print props automatically. Some devices need to have the different fingerprint props matching (at least some of them, but I change all just in case), or the OS might find the mismatching props as a sign of a broken system and pester you with an error message/warning at boot.

And lastly, yes. The pattern matching for the certified prints is very strict and case sensitive. If the print doesn't exactly match that Google has on record it won't pass CTS.

I think that covered most of the stuff you brought up. Hope it made it slightly more clear...
[Magisk] zgfg:
Yeah, it covers...mostly.

I still don't understand why my stock

ro.bootimage.build.fingerprint=

Xiaomi/davinci/davinci:10/QKQ1.190825.002/V12.0.3.0.QFJEUXM:user/release-keys

is different (in three charcters) from

ro.build.fingerprint=

Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V12.0.3.0.QFJEUXM:user/release-keys

but that's probably more of a question to Xiaomi (and I don't know how it goes for the other MIUI firmwares - you put the first to be equal to the second, but as you also say, seems that only the second matters)

Thx
[Magisk] Didgeridoohan:
[MENTION=7786725]zgfg[/MENTION] Yeah, that's down to Xiaomi. Nothing I can answer... They're probably just reusing stuff between the different devices.
[Magisk] mxpower:
FYI: The Redmi Note 8 Pro Global fingerprint always fails and evalType is forced to hardware. With "begonia" or "Redmi Note 8T" the SafetyNet check passes and evalType is set to BASIC.

I think the Xiaomi Redmi Note 8 Pro is set to hardware-backed only and if your bootloader is unlocked it will always fail (unless you fake SafetyNet with EdXposed) so to pass the check you need the BASIC (software) check and use a fingerprint that still works with basic evaluation.
[Magisk] Didgeridoohan:
The evalType has nothing to do with the device fingerprint. SafetyNet uses the device model value to determine if your device should do a hardware backed key attestation, or a basic one. As long as the ro.producy.model prop (or possible one of the variations of the same) reads something other than your actual device's model you should get basic attestation.
[Magisk] BlackVoltage:
Work till a few days ago .. changend nothing but does not pass any longer

Magisk + Props worked fine so far for my samsung S9 with LineageOs 17.1

Since it stopped working a few days ago.

Did Google change anything? Is there still a chance to pass safetynet again?

How to?

Seems without AusweisApp2 does not work (also googlepay, netflix and so on but I could live with that)

Thanks a lot in advance!
[Magisk] Didgeridoohan:
[MENTION=11006415]BlackVoltage[/MENTION] You might want to try enabling "Force BASIC key attestation" (take a look in the docs for details). Most likely suspect at the moment...
[Magisk] BlackVoltage:
Amazing - that helped :) (magisk 21000 / 8.0.2; newest props module)

Thanks a lot!

Edit: It helped to pass safety net; "ausweis app2" still says "your device does not comply technical requirements (extended length) (it did with samsung stock firmware)

Edit2: google pay similar still telling my that my smartphone does not meet needed safety requirements
[Magisk] zgfg:
There is another XDA thread with modules and instructions to pass GPay, you can search and try (no guarantee)

For that app, maybe it remembers now that you 'were' rooted, you can try cleaning its cache, data, uninstallimg.

There are also other tricks to try (hiding Manager, removing some well known root apps, TWRP folder, etc).

Of cource, Magisk Hide must be on and apo must be listed on the Magisk hide list (and must not be present in Superuser list, not even as an app for whom root is not granted)
[Magisk] alvintimothyjr:
I Just re-flashed stock android 11 and I am unable to pass safety net. My previous configuration is the same as my current one. The only thing I saw different in MagiskProps module is that it defaults to a nexus 5 finger print....

I followed the OP instructions. Has anything changed recently?
[Magisk] Didgeridoohan:
There's no "default Nexus 5 print", but by default the "Force BASIC key attestation" feature uses the Nexus 5 as the model to spoof basic attestation (that you can change yourself though).

This would be a good place to start:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] zgfg:
Fingerprints are not really for stock firmwares, but Force CTS Basic - please look in the posts, every second is about ?

Must be allso covered by Instructions, in case when CTS Profile is failing

Google started to test and enforce (per devices) since April, and again since the summer, it's all the time a hot topic here and Magisk general thread. For now, forcing CTS Basic does the trick
[Magisk] alvintimothyjr:
cleared data to google play services....passed safety
[Magisk] BlackVoltage:
Regarding AusweisApp2 it seems that nfc extended length is a technical feature which needs to be supported from hardware and software. Unfortunately lineage did not support that feature which is needed for secure signature transfer or something like that. Too bad government digitalization back step ?
[Magisk] dynux90:
[MENTION=4667597]Didgeridoohan[/MENTION] hi,

unfortunately even with updates fingerprints i cannot pass the safetynet on my Galaxy a40, it fails on the ctsprofile.

using the force basic attestation i can pass the safetynet but it forces the model to the Samsung Galaxy A3 2015 SM-A300FU, breaking the samsung themes (for example).

if i force the basic attestation to the real model SM-A405FN the attestation fails.

Is this a normal behaviour or there is a way to fix this?

Thank you very much.
[Magisk] Didgeridoohan:
That is completely normal.

Your device uses hardware backed key attestation, so just changing the fingerprint won't help (and if you are using a stock ROM it's completely unnecessary). With the "Force BASIC key attestation" feature you'll have to pick a device that is different from your own (because you'll have to trick SafetyNet into using basic attestation, and if you pick your own device that'll just be as if you haven't actually activated the option).

Pick a device as close as possible to your own device and device specific things might start working as expected, but model specific features will of course break (since we spoof the model name to trick SafetyNet).
[Magisk] zgfg:
Fingetprints do not help for CTS Profile.

Already answered for the same today afternoon, use Force CTS Basic option 2 in the new MHCP
[Magisk] Didgeridoohan:
Just to clarify: On custom and otherwise uncertified ROMs they do... And if the device uses hardware backed key attestation you

also

have to spoof the model prop.
[Magisk] zgfg:
Ofc, but it was an answer to the post about stock ROM (and stating that fingerprints did not happen)

I just wonder why CTS Profile / Force CTS Basic is that new to some people, it was discussed here and in Magisk thread for months and in countless posts. And maybe a post or two above when they ask

Some like did not read / pay attention until it hits them or what
[Magisk] slutman:
Hello,

I would love to see S10 SM-G9730 added to the module but I have no idea to where I can find the fingerprints files (and if I can try it first before to send them to OP)

Can someone help me with that please ?

Thanks in advance :)
[Magisk] zgfg:
OP post #1 and MHPC GitHub docs

Anyway, from Terminal execute commands and provide results (assuming you have device with the firmware installed and its passing SafetyNet):

>> getprop ro.build.fingerprint

>> getprop ro.build.version.security_patch
[Magisk] sean222:
For my Pixel 5, changing the authentication to BASIC allowed my Google Pay to work!

Question though, my device now shows "Google BASIC" as the name instead of "Google Pixel 5". Also my car and my watch show "Google BASIC connected"...also on the Play Store...is there any way to cosmetically change the device name while keeping the basic authentication?

Or is this the tradeoff for having SafetyNet pass?
[Magisk] Didgeridoohan:
Forcing basic attestation involves changing the model prop for the device, so it won't be showing the proper name with this kind of hack active. No way around it... You can pick a device model very close to yours though (like the Pixel 4a), and it'll at least look a little bit better.

But, I have to ask: did you use this module to force basic attestation? And if so, did you pick the custom option to manually enter "BASIC" as the used value? Just want to know if there's a possible issue, because from the regular settings of the bottle you won't get "BASIC" as the module prop.
[Magisk] sean222:
Thanks. I used the hardwareoff module floating around to get BASIC. Going through through props manually I also got Basic and choose a device (Pixel 3 XL), but "Google Basic" looked visually better than "Google Pixel 3 XL"...more generic...lol.

But anyways thanks for the reply, makes sense.

Sent from my Nexus 6P
[Magisk] panddah:
Please add props suport to XT1941-4 DEEN reteu
[Magisk] haafizd34:
Samsung Galaxy A70 SM-A705F (10)

samsung/a70qdx/a70q:10/QP1A.190711.020/A705FXXU5BTF1:user/release-keys
[Magisk] ipdev:
[MENTION=5779564]haafizd34[/MENTION]

Need the matching security date also. ;)

Cheers. :cowboy:
[Magisk] zgfg:
Pls scroll up five posts earlier than yours with instructions how to submit device fingerprint for s particular phone and firmware - it cannot be added without somebody reading and submitting the props
[Magisk] zy54917118:
help!!!

[MENTION=4667597]Didgeridoohan[/MENTION]

Thank you so much for your advice but I still have a difficulty in passing the ctsProfile check. and I have followed and tried all the procedures that you provide .

i clollected my logs but i don't know how to give my logs to you because this forum has no function of adding attachments.

PS :I am amateur about this.

Look forward to your response. thank you very much.
[Magisk] Didgeridoohan:
It is possible to attach files, but not for brand new users with no posts... I think the limit is 10 posts or so.

You can upload the logs to a file sharing service (Drive, etc) and send me the link.
[Magisk] zy54917118:
Here is all my relevant logs but I am not sure if the logs are appropriate so I upload some pictures to illustrate the details of my problems.

The four pictures are the version of Magsik,the information of my phone,failed test result .

again,thank you very much.

drive.google.com/file/d/1-YJyjF1_EqR087ka1Z-Ojs7y0cHq1fnc/view?usp=sharing

drive.google.com/file/d/19QRq2ZxElSr9MElhMDEjheHSPwiU2awY/view?usp=sharing

drive.google.com/file/d/1NADZqXXDcpbTVPryYLS_RXcLtT295WV7/view?usp=sharing

drive.google.com/file/d/1nKjdTU24CzIMm6km3TJVSaSqRZYvqz0L/view?usp=sharing

drive.google.com/file/d/1C4QntVfFuGvxbI_O_EYgmac7UDEuxqkq/view?usp=sharing
[Magisk] panddah:
hey man sorry, but how can I force cts?? what is MHCP? im 18yo and new here... sorry
[Magisk] zgfg:
MHCP=Magisk Hide Props Config module. You are right here in the XDA thread

Make sure you use a new MHCP version, use its option 2 to force CTS attest to use Basic mode, that way Magisk can hide that Bootloader is unlocked and if everything else is ok, it passes CTS and SafetyNet
[Magisk] Didgeridoohan:
[MENTION=11210941]zy54917118[/MENTION] Awesome. I'll take a look as soon as possible, but first you have to turn on link sharing so that I can access the files.
[Magisk] zy54917118:
I have uploaded my logs successfully. please check it again. sorry to bother you. My fault.

drive.google.com/file/d/1-YJyjF1_EqR087ka1Z-Ojs7y0cHq1fnc/view?usp=sharing

drive.google.com/file/d/19QRq2ZxElSr9MElhMDEjheHSPwiU2awY/view?usp=sharing

drive.google.com/file/d/1NADZqXXDcpbTVPryYLS_RXcLtT295WV7/view?usp=sharing

drive.google.com/file/d/1nKjdTU24CzIMm6km3TJVSaSqRZYvqz0L/view?usp=sharing

drive.google.com/file/d/1C4QntVfFuGvxbI_O_EYgmac7UDEuxqkq/view?usp=sharing
[Magisk] panddah:
option 2 = systemize installed app (enter label) found this with termux, is that ?
[Magisk] zgfg:
See the screenshot
[Magisk] panddah:
ahh ok, im was using systemize command.. hehe my bad

so, after i use props.. and select option 2, my device don't here in that list (motorola xt1941-4 deen)

my cts is ok, but i cant found netflix on playstore yet ):
[Magisk] Spartacus500:
With Android 9 version, can fingerprint from newer Android 10 or 11 be applied and there will be Safety net pass as well as app updates?
[Magisk] ipdev:
OT for this thread but..

You can install Netflix from another source.

Google will find it installed and Google being Google will take over and Netflix will be available and update via PlayStore.

PlayStore certification does not seem to matter.

You can grab the newest Netflix from here along with instructions on using SAI to install.

[SAI][TWRP][STABLE][BETA] Netflix - Latest Versions xda Thread - Link

Cheers. :cowboy:
[Magisk] Didgeridoohan:
The instructions is to

not

pick your own device... See the docs for details on your to use the option.

You already have one proposed solution for Netflix, but it might also be worth taking a look here:

https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up
[Magisk] zgfg:
If your CTS and SafetyNet are ok now, but Device is not certified in Playstore:

- Airplane on

- Settings, Apps, Show system apps, Clear cache and data for Google play, Google play services, Google services framework

- Reboot and airplane off

- Give some time for Playstore to sync

But it could be also that changing ro.product.model (for CTS Basic) interfere with Netflix. Search in this thread, you can put any custom string/name and maybe if you put a model name from an older device, you could get both CTS/SafetyNet and Netflix (with L1 - if your phone was certified for)

See the other answers you got about Netflix, they know more about (I'm not using Netflix)
[Magisk] Didgeridoohan:
I test all prints on an A10 device (Nexus 6 with custom ROM), and the A11 prints pass just fine. That's not a universal assurance that it will work on every combination of devices and prints, but you should mostly be fine...

Easiest way to find out is to try. :good:
[Magisk] Spartacus500:
Unfortunately, with Android 9.0, you cannot fingerprint newer Android 10 or 11, reason: SafetyNet - CTS profile = false ...
[Magisk] Didgeridoohan:
Thanks for testing, good to know.
[Magisk] Didgeridoohan:
[MENTION=11210941]zy54917118[/MENTION] There's nothing in your logs that suggest that anything is wrong and would cause CTS to fail (that I could spot at a quick glance at least).

But, tell me a little more about your setup.

Are you using stock MIUI, and does it come with GApps preinstalled?