yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Well... Looks like the logging works, but it doesn't seem like you tried setting the custom prop before saving the logs. Or? I need you to do that first for it to show up in the new logs...
[Magisk] th3legend:
Anyone know how to extract the a20 fingerprint ? Could I extract it from the stock firmware via a file or would I have to load the device on stock again and grab it via getprops or something?
[Magisk] Didgeridoohan:
Some methods are covered in the docs:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] pilger:
I can't really try setting the prop before saving the logs cause setting the props kinda hangs the script. I have to abort it with crtrl+c.

Or maybe I didn't get what you need me to do. :o
[Magisk] Didgeridoohan:
Try setting the prop, abort the script and then run it again and save the log. That should get my the info I need...
[Magisk] pilger:
My bad. Haha.

There you go.
[Magisk] Didgeridoohan:
Hmm... You might have been a little too quick with the ctrl+c. It looks like things got interrupted midway. Could you try again and let it sit frozen a moment or two before interrupting the script?

And by the way, just so I have the reference, you're attempting to change the ro.build.csca.version prop from "BORETS ROM" to Foobar, correct?
[Magisk] th3legend:
Derp looked at that Mobi site and there it is. Thanks didgeridoohan!

Opp on second thought...I'll extract the stock and see what I get...I have 205w and the fingerprint on the site is 205g
[Magisk] pilger:
Oops. Here is a new one. I hope I gave it enough time.

Yeah. That's what I'm trying to do. "Foobar" is just a testing value. I intend to change that to the original build name.

There's an app I'm trying to run that detects I'm on a custom ROM somehow.
[Magisk] Didgeridoohan:
Thanks. I'll look closer at this tomorrow (technically today). It is well past midnight here, and my little one is sure to wake up way earlier than I would like. And if the little one doesn't sleep, neither do the big ones. :D
[Magisk] G U C C I:
I'm running both EdXposed and this module simultaneously and haven't had any issues. Even with my EdXposed modules. This is on Lineage 9.0...
[Magisk] th3legend:
ro.build.version.security_patch=2019-08-01

ro.build.version.base_os=samsung/a20cs/a20:9/PPR1.180610.011/A205WVLU1ASE7:user/release-keys

got it - for the 205w a20
[Magisk] th3legend:
Confirmed working for a20
[Magisk] TigerKing:
Fingerprints -

Poco F1

C:\>adb shell getprop ro.build.fingerprint

Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V11.0.5.0.PEJMIXM:user/release-keys

C:\>adb shell getprop ro.build.version.security_patch

2019-10-01

Motorola G5s Plus

C:\>adb shell getprop ro.build.fingerprint

motorola/sanders_n/sanders_n:8.1.0/OPS28.65-36-14/63857:user/release-keys

C:\>adb shell getprop ro.build.version.security_patch

2019-08-01
[Magisk] Some_Random_Username:
OnePlus 7T Pro NR HD1925 (Android Q, security patch level 2019/12/01)

OnePlus/OnePlus7TProNR/OnePlus7TProNR:10/QKQ1.190716.003/2001101147:user/release-keys
[Magisk] Didgeridoohan:
I'm actually not seeing why things would be failing right there... I'm sorry. I might take a closer look in a week or so, with more fresh eyes, but right now I'm stumped. Uninstalling and then reinstalling might do something, but since it wasn't fixed by installing the test zip I doubt it. If you want to set the prop you can always use the configuration file to set things up instead: https://github.com/Magisk-Modules-R...nfig/blob/master/README.md#configuration-file

But, I was also looking at your Magisk log and saw that you've got Xposed installed. That might be why your app is complaining, since Xposed cannot be hidden even when it is installed systemlessly as a Magisk module. You might have better luck with EdXposed and it's blacklist feature, but I can't help with that (I know very little about it).
[Magisk] pilger:
It might have something to do with my device being x86. That's not very common. I've tried again on a different ROM now and got the same result.

But you were absolutely right! Despite the app error message saying I had a "non original software", it was, in fact, detecting Xposed.

Anyways, about the issue, no biggie, man. I appreciate the effort. I guess there's not much need to get further into the issue since it appears to be affecting just this device.

If you want/need me to do further testing, though, just mark me and I'd be happy to help.

Have a great week!
[Magisk] Some_Random_Username:
[MENTION=4667597]Didgeridoohan[/MENTION]

OnePlus 6 updated fingerprint

Android 10: OnePlus/OnePlus6/OnePlus6:10/QKQ1.190716.003/1912142009:user/release-keys__2019-11-01

OnePlus 6T T-Mobile USA new fingerprint

Android 9: OnePlus/OnePlus6TSingle/OnePlus6TSingle:9/PKQ1.180716.001/1810291147:user/release-keys__2018-11-01 (not latest fingerprint, but rather one I was able to find easily)

OnePlus7 GM1901/GM1905 updated fingerprint

Android 10: OnePlus/OnePlus7/OnePlus7:10/QKQ1.190716.003/1912141900:user/release-keys__2019-11-01

OnePlus 7 GM1903 updated fingerprint

Android 10: OnePlus/OnePlus7_EEA/OnePlus7:10/QKQ1.190716.003/1912061900:user/release-keys__2019-11-01

OnePlus 7 Pro GM1911/GM1917 updated fingerprint

Android 10: OnePlus/OnePlus7Pro/OnePlus7Pro:10/QKQ1.190716.003/1912141900:user/release-keys__2019-11-01

OnePlus 7 Pro GM1913 updated fingerprint

Android 10: OnePlus/OnePlus7Pro_EEA/OnePlus7Pro:10/QKQ1.190716.003/1912061900:user/release-keys__2019-11-01

OnePlus 7 Pro GM1915 new fingerprint

Android 9: OnePlus/OnePlus7ProTMO/OnePlus7ProTMO:9/PKQ1.190110.001/1905021004:user/release-keys__2019-03-01 (not latest fingerprint, but rather one I was able to find easily)

OnePlus 7 Pro NR Spr GM1925 new fingerprint

Android 9: OnePlus/OP7ProNRSpr/OP7ProNRSpr:9/PKQ1.190223.001/1908201041:user/release-keys__2019-08-01 (not latest fingerprint, but rather one I was able to find easily)

OnePlus 7T HD1901 and HD1905 (updated version of current 7T fingerprint )

Android 10: OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1912060025:user/release-keys__2019-11-01

OnePlus 7T HD1903 new fingerprint

Android 10: OnePlus/OnePlus7T_EEA/OnePlus7T:10/QKQ1.190716.003/1912060025:user/release-keys__2019-11-01

OnePlus 7T Pro HD1911 and 1917 new fingerprint

Android 10: OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys__2019-11-01

OnePlus 7T Pro HD1913 new fingerprint

Android 10: OnePlus/OnePlus7TPro_EEA/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys__2019-11-01

Additionaly, I have a question: are you interested by Android 7.1 and 8 fingerprints for OnePlus 5T for instance (current prints present for it are 8.1 and 9)?
[Magisk] Didgeridoohan:
[MENTION=8234677]Some_Random_Username[/MENTION] That's insane! Thank you so much, I'll try to get an updated list out tonight... :good:

For completeness sake, why not?
[Magisk] Didgeridoohan:
[MENTION=8234677]Some_Random_Username[/MENTION] All prints double-checked and working. Great work!

I also looked back in the old commits for the prints list and found the 7.1.1 and 8.0.0 prints for the OnePlus 5T, so no need to look for those.

As soon as I've put the little one in bed (2-3 hours) I'll get the list updated. Thanks again.
[Magisk] shi-no_tenshi:
Hello, thank you for your module.

I'd like to submit a device fingerprint for the Samsung Galaxy A7 (2017) [A720FXXU9CKS3] with the December 1 patch running Android 8.0.0, it passes both ctsProfile and basicIntegrity checks.

Please let me know how I can submit so I can help other users out there!

Regards,

shi-no_tenshi

Edit: Here's the fingerprint extracted from a TWRP backup of my Stock ROM.

ro.build.fingerprint=samsung/a7y17ltexx/a7y17lte:8.0.0/R16NW/A720FXXU9CSK3:user/release-keys

This is for the Dual Sim variant. Openline (XTC)
[Magisk] Some_Random_Username:
My pleasure :)

Additionally I obtained one Huawei Mate 20 Lite SNE-LX1 Android Pie fingerprint from someone at my university:

HUAWEI/SNE-LX1EEA/HWSNE:9/HUAWEISNE-L01/245EEAC782:user/release-keys__2019-09-01
[Magisk] Didgeridoohan:
Fingerprints list updated to v74

A whole host of OnePlus fingerprints where dropped in my lap earlier today. Awesome! And I also went back through some old commits and found a couple of old prints for the OnePlus 5T that I also added back (just for completeness sake).

Anyway, fingerprints list has been updated to v74 and will automatically update in the module when you run the props script (with the -f option if you've turned off automatic updates) or from the "Edit device fingerprint" menu.

Thank you to [MENTION=6827524]amit.tiger12[/MENTION], [MENTION=9776809]shi-no_tenshi[/MENTION] and a huge shoutout to [MENTION=8234677]Some_Random_Username[/MENTION] for providing the prints.

New

Huawei Mate 20 Lite

Motorola Moto G5S Plus

OnePlus 6T T-Mobile

OnePlus 7 Pro GM1915

OnePlus 7 Pro NR Spr GM1925

OnePlus 7T HD1903

OnePlus 7T Pro HD1911/HD1917

OnePlus 7T Pro HD1913

OnePlus 7T Pro NR HD1925

Samsung Galaxy A7

Updated

OnePlus 5T

OnePlus 6

OnePlus 7 GM1901/GM1905

OnePlus 7 GM1903

OnePlus 7 Pro GM1911/GM1917

OnePlus 7 Pro GM1913

OnePlus 7T HD1901/HD1905
[Magisk] bagdas:
Hello,

Fingerprint for Xiaomi Mi Note 10 (EEA European) / Android 9 / MIUI 11

getprop ro.build.fingerprint

Xiaomi/tucana_eea/tucana:9/PKQ1.190302.001/V11.0.11.0.PFDEUXM:user/release-keys

getprop ro.build.version.security_patch

2019-11-01
[Magisk] zbysogi:
I have 2 issues:

1. My phone randomly loses root. One time it passes cts profile and basic integrity, the other time cts profile is false.

Reboot sometimes helps (not every time) but only for several minutes.

2. When uning the phone it freezes. The app I am using at that time shuts down, screen turns off and phone is frozen but seems on with the screen off. I.e. if I connect to whatsapp web and the phone freezes, whatsapp web still works, so the internet connection is there but the screen is off, if Im charging it the LED light is on but there is no access to the phone and I have to hard boot it.

I tried to unroot it but its not booting to system when I do that. I have to manually enter TWRP and flash magisk again. Yesterday I unrooted it and waited over an hour and it didnt boot to system :/

I do not have any conflicting modules installed in magisk but I cant find the culprit of those issues and its driving me crazy.

I read somewhere that losing root issue was known in 2013... apparently nothing changed since then?
[Magisk] Didgeridoohan:
You've other issues than what the scope of this thread is...

#1 could be caused by a number of reasons, usually device/OEM specific, but has been greatly reduced with later versions of Magisk.

#2 doesn't sound like something that has to do with Magisk, more like a dying device... You should probably do a full wipe and reflash of your ROM. A nice cleanup to get rid of the cobwebs.

I'd advice doing some (early) spring cleaning and then, if you continue to have issues, ask for help in the Magisk general support thread.
[Magisk] shi-no_tenshi:
THANK YOU SO MUCH

Confirmed fingerprint is certified when I edited it with your module!

Used it in a custom ROM I was hoping to use a few apps on.

I hope you know how much you've helped me!

Edit: Can you please edit the name of the device to indicate that it's from 2017? I just want to avoid people getting confused. Thank you!

Regards,

shi-no_tenshi
[Magisk] Sid220:
New Fingerprint for Xiaomi Poco F1

MIUI 11.0.4.0

Android version 10

Security Patches 2020-01-01

Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V11.0.4.0.QEJMIXM:user/release-keys

Tested and working [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] TigerKing:
friend clean flash your rom again.. and set up everything again..

and try this Xposed module, if this magisk module didn't help.

https://repo.xposed.info/module/com.cofface.ivader

(this app have AOD issue)
[Magisk] Jayram2000:
Can the current version of signatures be used on Android 10 with the latest Magisk? I am using a OnePlus 5
[Magisk] Didgeridoohan:
Yes, there are no restrictions on Android version. I'm currently using an Android 7.1.1 fingerprint on an Android 10 ROM for my Nexus 6 without issues.
[Magisk] Jayram2000:
Great thanks
[Magisk] Didgeridoohan:
Fingerprints list updated to v75

Small update to the fingerprints list. Thank you [MENTION=4770208]Sid220[/MENTION] and [MENTION=601351]bagdas[/MENTION].

New

Xiaomi Mi Note 10

Updated

Xiaomi Pocophone F1
[Magisk] Max1Truc:
Nokia 7.1 fingerprint

Here is a fingerprint for the Nokia 7.1 (TA-1095):

Nokia/Crystal_00WW/CTL_sprout:10/QKQ1.190828.002/00WW_4_08B:user/release-keys

Security patch date : 2019-11-01
[Magisk] manjaroid:
Fingerprints for custom 64-bit Pie ROMs

The ARM64 release of Arrow OS Pie [for Moto G4 athene] with January 2020 security patch is built with a Pixel 2 fingerprint that isn't passing SafetyNet checks. Is this just a matter of Play Protect catching up with the newer date for the security patch?

ctsProfile false:

google/walleye/walleye:9/PPP3.180510.008/4811556:user/release-keys

​

Meanwhile, SafetyNet passes using a different fingerprint from another Pixel 2 in Props Config.

ctsProfile true:

google/walleye/walleye:9/PQ3A.190801.002/5670241:user/release-keys​
[Magisk] Didgeridoohan:
It's all about the security patch date. I've no idea what the date would be for the first print, but I'm fairly sure you won't find a Pie print for the Pixel 2 that corresponds to a January 2020 security patch. Prints for an Android build after march 2018 have to match the security patch date or CTS will fail.

If you use the module to set a print (from the included list) the patch date is set correspondingly.

It's got nothing to do with Play Protect.
[Magisk] manjaroid:
I was just reading about that in previous posts and those 7 words are now on my forehead in reverse. Thanks!
[Magisk] Some_Random_Username:
OnePlus 6 updated Android 10 fingerprint:

OnePlus/OnePlus6/OnePlus6:10/QKQ1.190716.003/2001151848:user/release-keys__2019-12-01

OnePlus 6T updated Android 10 fingerprint:

OnePlus/OnePlus6T/OnePlus6T:10/QKQ1.190716.003/2001151848:user/release-keys__2019-12-01

Nokia 6.2 (unfortunately don't know for which specific model as there are several) new fingerprint (Android 9): Nokia/Starlord_00WW/SLD_sprout:9/PKQ1.190118.001/00WW_1_170:user/release-keys__2020-01-05

Nokia 6 new fingerprints (for four of the six models ) (Android Pie)

TA-1039 model: Nokia/TA-1039_00WW/PLE:9/PKQ1.181105.001/00WW_6_19C:user/release-keys__2020-01-01

TA-1033: Nokia/TA-1033_00WW/PLE:9/PKQ1.181105.001/00WW_6_19C:user/release-keys__2020-01-01

TA-1021: Nokia/TA-1021_00WW/PLE:9/PKQ1.181105.001/00WW_6_19C:user/release-keys__2020-01-01

TA-1025: Nokia/TA-1025_00WW/PLE:9/PKQ1.181105.001/00WW_6_19C:user/release-keys__2020-01-01
[Magisk] ipdev:
So, this one may be a little dirty.

I started working on a script to take some of the manual intervention (aka copy and past) out. ;)

I believe Poco F1, OnePlus 5T and 6T have been given already.

February Pixel(s) 2, 3, 3a, 4.

Cheers all. :cowboy:
[Magisk] wingbat:
Moto g7, US, Google Fi variant, XT1962-1, Android 9.0:

motorola/river/river:9/PPOS29.114-134-7/b6963:user/release-keys__2019-12-01
[Magisk] ArkBlitz:
Xiaomi Redmi 8 (olive), Latin America, Android 9.0, patched up to Nov. 25, 2019:

Xiaomi/olive/olive:9/PKQ1.190319.001/V11.0.7.0.PCNCNXM:user/release-keys
[Magisk] Didgeridoohan:
Thank you, but that print does not pass CTS with the posted security patch date. And I suspected as much already before testing, since the dates are always either the 1st or 5th of the month. I tested both Nov. 1 and Nov. 5 though, unfortunately with negative results. If you could provide an alternative date (run getprop ro.build.version.security_patch in a terminal window) I can give it another go.
[Magisk] oslo83:
Huawei Mate 20 Pro 9.1

HUAWEI/LYA-L29/HWLYA:9/HUAWEILYA-L29/346C432:user/release-keys__2019-10-06

(Yes 6 and not 1 nor 5 as habitually.)

Huawei Mate 20 Pro 9.1

HUAWEI/LYA-L29/HWLYA:9/HUAWEILYA-L29/358C432:user/release-keys__2019-11-01
[Magisk] ArkBlitz:
I currently can't run getprop directly as I already installed a custom ROM (via GSI), but I do have the update file for the original ROM, which is where I got the value of the fingerprint from. The files are stated to be generated in December 18, 2019 - I'll test with 2019-12-01 and 2019-12-05 then
[Magisk] gmnabeel:
Magisk hide not working 20.3.. Is everyone getting this error
[Magisk] Didgeridoohan:
MagiskHide works fine. Start by taking a look here if there's anything that could help you troubleshooting:

https://didgeridoohan.com/magisk/MagiskHide

If you can't get things working as expected after that, post all relevant details in the general support thread:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[Magisk] ArkBlitz:
Alright, I already verified that

Xiaomi/olive/olive:9/PKQ1.190319.001/V11.0.7.0.PCNCNXM:user/release-keys

works with a date of

2019-12-01
[Magisk] Didgeridoohan:
Fingerprints list updated to v76

New month, new security updates, new and updated prints added to the module.

Thank you [MENTION=10494415]Max1Truc[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=4892097]ArkBlitz[/MENTION] and [MENTION=7530018]oslo83[/MENTION] for providing fingerprints.

There are now 308(!) certified device fingerprints included in the module. Awesome work everyone who contributes! There are (as of writing this) 27035 devices on Google's official list of Supported devices, so we're lagging behind a little (but catching up :D).

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

New

Motorola Moto G7 XT1962-1

Nokia 6 TA-1021

Nokia 6 TA-1025

Nokia 6 TA-1033

Nokia 6 TA-1039

Nokia 6.2

Nokia 7.1 TA-1095

Xiaomi Redmi 8

Updated

Essential PH-1

Google Pixel 2

Google Pixel 2 XL

Google Pixel 3

Google Pixel 3 XL

Google Pixel 3a

Google Pixel 3a XL

Google Pixel 4

Google Pixel 4 XL

Huawei Mate 20 Pro

OnePlus 5T

OnePlus 6

OnePlus 6T
[Magisk] Gianluk99:
Thanks for making this module, and making it so simple to use :D
[Magisk] PoccoF1:
It didn't work to trick Netflix on POCO F1. Just detected my real phone.
[Magisk] Didgeridoohan:
What have you tried and what is your expected result? You'll have to give more details if I'm going to be able to help...
[Magisk] PoccoF1:
I'm trying to change my phone fingerprint so Netflix could see it as another one. As you should know Pocophone is not available in HD, so I thought that if I change fingerprint to another I might be able to trick netflix but it didn't work. Netflix is still able to see that I'm using a POCO.
[Magisk] Didgeridoohan:
That's not quite how things work... To mask your device as another you need to do more than just change the device fingerprint. There is a rudimentary feature for this in the module, but beware that on some devices you may get issues if enabling every simulation prop (see the docs for more details).

But, HD Netflix doesn't rely on this at all so you can't fix that "issue" with this module. It is unlikely you can fix it at all actually, since (if I remember correctly) it relies on things like your Widevine level and other drm mechanisms.
[Magisk] Some_Random_Username:
OnePlus 7T Pro NR HD1925 updated fingerprint: OnePlus/OnePlus7TProNR/OnePlus7TProNR:10/QKQ1.190716.003/2002051152:user/release-keys__2019-12-01
[Magisk] PoccoF1:
People made it work by editing props. :confused:

https://xdaforums.com/poco-f1/how-to/root-guide-to-netflix-hd-official-t4035219
[Magisk] Didgeridoohan:
Ok, I see... The Poco Widevine is level 1 (which is what I was talking about), but Netflix is still blocking it from HD content somehow. Is that correct?

Looking at that guide, changing the device fingerprint isn't what's needed but a few other props. You can do that with this module as well, you'll just need to know the prop names. Brand and device can be changed automatically from the picked fingerprint with the "Device simulation" feature (but it isn't quite complete). Manufacturer (possibly ro.product.manufacturer) and model (ro.product.model?) you'd have to set yourself. Although, I believe the guide is wrong on the device prop and that it should read "sargo" rather than "Pixel 3a" (so since it seems to work anyway that particular prop likely isn't needed).

If changing those props is what's needed, then the above should be what you need.
[Magisk] Some_Random_Username:
OnePlus 7Pro GM1911/1917 updated fingerprint: OnePlus/OnePlus7Pro/OnePlus7Pro:10/QKQ1.190716.003/2002021900:user/release-keys__2020-01-01

OnePlus 7T Pro HD1913 updated fingerprint: OnePlus/OnePlus7TPro_EEA/OnePlus7TPro:10/QKQ1.190716.003/2002022020:user/release-keys__2020-01-01

OnePlus 7T Pro HD1911/1917 updated fingerprint: OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/2002022020:user/release-keys__2020-01-01
[Magisk] Some_Random_Username:
OnePlus 7 GM1901/GM1905 updated fingerprint: OnePlus/OnePlus7/OnePlus7:10/QKQ1.190716.003/2002021900:user/release-keys__2020-01-01
[Magisk] Zachary_Foxx:
The fingerprint to Xiaomi Mi Pad 7.9' directly from the last OTA firmware (miui_MIPADGlobal_V7.5.2.0.KXFMIDE_c4f7d5f70d_4.4.zip):

ro.build.fingerprint=Xiaomi/mocha/mocha:4.4.4/KTU84P/V7.5.2.0.KXFMIDE:user/release-keys

ro.build.version.security_patch=2016-06-01

Xiaomi Mi Pad (4.4.4.)=Xiaomi/mocha/mocha:4.4.4/KTU84P/V7.5.2.0.KXFMIDE:user/release-keys

I tested here and it works!!
[Magisk] Didgeridoohan:
Fingerprints list updated to v77

OnePlus rolled out some updates to the OP7 line and a few hours later the fingerprints from those updates start showing up in this thread. Thank you [MENTION=8234677]Some_Random_Username[/MENTION].

There's also an oldie but goldie in this update, a fingerprint for the Xiaomi Mi Pad provided by [MENTION=9576460]Zachary_Foxx[/MENTION]. Thank you.

The fingerprints list will update when the props command is run, or by using the -f option or from the "Edit device fingerprint" menu if the automatic update has been disabled in settings.

New

Xiaomi Mi Pad

Updated

OnePlus 7 GM1901/GM1905

OnePlus 7 Pro GM1911/1917

OnePlus 7T Pro HD1911/1917

OnePlus 7T Pro HD1913

OnePlus 7T Pro NR HD1925
[Magisk] ncc1977d:
I need the fingerprint for PRA-LX1 (P8 Lite 2017).
[Magisk] Didgeridoohan:
It's available in the fingerprints list included with the module. So you can either use the module to set the print, or if you want to work with your own scripts (or similar) you can find it in the module files (prints.sh) on GitHub (links in 1st post).
[Magisk] ncc1977d:
In my list was the P8 Lite profile but not the P8 Lite 2017 profile.

So i took the P8 Lite profile, but it does not work. :(

Maybe it is in the TopJohnWu magisk version available when installing Exposed.
[Magisk] Sid127:
Latest Fingerprint from Nokia 6.1 Plus (DRG) Android 10

Nokia/Dragon_00WW/DRG_sprout:10/QKQ1.190828.002/00WW_4_10D:user/release-keys

Security patch date - January 1, 2020
[Magisk] Didgeridoohan:
The fingerprint included in the module is the PRA-LX1, so you're good on that front (the name is just a name I've put there, look at the print).

But you're going to have to be more detailed then just saying "it doesn't work" if you need help... What's your setup, etc?

Sounds like you might have Xposed installed, and that would be your issue in that case. You might have better luck with EdXposed.

Instead of me listing possible things that could trigger SafetyNet (because I'm assuming that's what you're trying to fix), take a look here (where I've already listed a bunch of tips):

https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] jaroulz:
can't get this mod to work, it says inaccessible or not found, please help
[Magisk] ncc1977d:
Same on my side. :(
[Magisk] Didgeridoohan:
Details guys... Do you get the message in terminal (which terminal app?), when installing, or where?

If nothing else, install logs and Magisk logs are always useful, but before anything else: do you have Core Only Mode (Safe Mode in the latest Canary builds) enabled? If so, disable that and try again.

If you can't get things working I need more info, or I won't be able to help...