yashsingh1/xdaforums huggingface dataset:
[Magisk] BADA 187:
Sony Xperia Z [C6603] (Android Lollipop, December Security Patch 2015..? not to sure)

[ro.bootimage.build.fingerprint]: [Sony/C6603/C6603:5.1.1/10.7.A.0.228/58103698:user/release-keys]

[ro.build.fingerprint]: [Sony/C6603/C6603:5.1.1/10.7.A.0.228/58103698:user/release-keys]

[ro.vendor.build.fingerprint]: [Sony/C6603/C6603:5.1.1/10.7.A.0.228/58103698:user/release-keys]

Sony Xperia Tab Z [SGP3210 (Android Lollipop, December Security Patch 2015..? not to sure)

[ro.bootimage.build.fingerprint]: [Sony/SGP321/SGP321:5.1.1/10.7.A.0.228/2020576680:user/release-keys]

[ro.build.fingerprint]: [Sony/SGP321/SGP321:5.1.1/10.7.A.0.228/2020576680:user/release-keys]

[ro.vendor.build.fingerprint]: [Sony/SGP321/SGP321:5.1.1/10.7.A.0.228/2020576680:user/release-keys]

Sony Xperia Z3 Compact [D5803] (Android Marshmallow, May Security Patch 2016)

[ro.bootimage.build.fingerprint]: [Sony/D5803/D5803:6.0.1/23.5.A.1.291/2769308465:user/release-keys]

[ro.build.fingerprint]: [Sony/D5803/D5803:6.0.1/23.5.A.1.291/2769308465:user/release-keys]

[ro.vendor.build.fingerprint]: [Sony/D5803/D5803:6.0.1/23.5.A.1.291/2769308465:user/release-keys]

Samsung Galaxy Tap A 2016 [gtaxllte] (Android Nougat, August Security Patch 2017)

[ro.bootimage.build.fingerprint]: [samsung/lineage_gtaxllte/gtaxllte:7.1.2/NJH47F/5a75e0a895:userdebug/release-keys]

[ro.build.fingerprint]: [samsung/gtaxlltexx/gtaxllte:7.0/NRD90M/T585XXU2BQI9:user/release-keys]

Sony Xperia XZ2 Compact [H8324] (Android Pie, November Security Patch 2018)

[ro.bootimage.build.fingerprint]: [Sony/H8324/H8324:9/52.0.A.3.84/2936176301:user/release-keys]

[ro.build.fingerprint]: [Sony/H8324/H8324:9/52.0.A.3.84/2936176301:user/release-keys]

[ro.vendor.build.fingerprint]: [Sony/H8324/H8324:9/52.0.A.3.84/2936176301:user/release-keys]

[vendor.fingerprint.hwid]: [0711]

[vendor.fingerprint.ready]: [true]

Huawei G8 [RIO] (Android Lollipop, December Security Patch 2015)

[init.svc.fingerprint_log]: [stopped]

[persist.rt.fingerprint.switch]: [true]

[ro.build.fingerprint.replace]: [unknown/Rock-L01/unknown:5.1/unknown/C150B130:user/release-keys]

[ro.build.fingerprint]: [HUAWEI/RIO-L01/hwRIO-L01:5.1/HuaweiRIO-L01/C150B130:user/release-keys]

[ro.mmi.fingerprint_test]: [true]

[ro.product.fingerprintName]: [HUAWEI-RI100]

[sys.fingerprint.deviceId]: [0]

HTC One M8 Will post this soon, gotta replace the charging port..:rolleyes: sry
[Magisk] sszz:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

could you please include this:

Xiaomi Mi 8 (8.1.0)=Xiaomi/dipper/dipper:8.1.0/OPM1.171019.026/V10.0.3.0.OEAMIFH:user/release-keys__2018-10-01

in the next release? Tested, works only with the correct security patch date.

Thank you
[Magisk] jenslody:
And what's the date ?

getprop | grep security_patch
[Magisk] Didgeridoohan:
He's actually included it in the fingerprint according to the module syntax...
[Magisk] jenslody:
Thanks for clarification. I don't need it, so I did not notice the new syntax.
[Magisk] SPyxOff:
Hey guys, does it matter what fingerprint I use for a device?

I use OnePlus 6T with some Magisk mods and I think thats the reason my device is Uncertified.

Will it break anything in the long run if I use OnePlus 6 fingerprint?

Thanks
[Magisk] Desdaemon:
Works wonder, thanks. The Galaxy J7 Prime's print had been posted here before, but neither it nor the default one worked on my phone (SM-G610F) so here's a working replacement.

Samsung Galaxy J7 Prime (6.0.1)=samsung/on7xeltedd/on7xelte:6.0.1/MMB29K/G610FDDU1AQG2:user/release-keys

Patch date is 2017-07-01
[Magisk] ipdev:
[MENTION=1428758]SPyxOff[/MENTION] I believe this is the current 6T fingerprint

ro.bootimage.build.fingerprint=OnePlus/OnePlus6T/OnePlus6T:9/PKQ1.180716.001/1811170214:user/release-keys

ro.build.version.security_patch=2018-11-01

[MENTION=4667597]Didgeridoohan[/MENTION]

Attached is a list of the missing Nexus fingerprints.

Pixel C also, even though Google kicked it under the rug.

Cheers. :)
[Magisk] Notonlyeyes:
Hi [MENTION=4667597]Didgeridoohan[/MENTION] ,

Updating list Fingerprint for Huawei P8 Lite 2017:

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/395(C432):user/release-keys

Security Patch Date: 2018-12-05

I tried the test it's working

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/395(C432):user/release-keys__2018-12-05
[Magisk] Didgeridoohan:
Update to v2.7.0-v38

Pushing an update making it a requirement to have Busybox installed (makes the scripts slightly more reliable). [MENTION=4544860]osm0sis[/MENTION]' Busybox is of course recommended...

There are also a whole bunch of new and updated fingerprints in this release. Huge thank you to [MENTION=8802276]Ramzir1[/MENTION], [MENTION=8931427]skullkid383[/MENTION], [MENTION=1655768]aza361[/MENTION], [MENTION=5976801]BADA 187[/MENTION], [MENTION=330977]sszz[/MENTION], [MENTION=9573517]Desdaemon[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=4553005]Notonlyeyes[/MENTION] and michaelmaverick over at GitHub. It's you guys that make this module what it is...

Changelog

v2.7.0

Updated Busybox logic (again). It is now required to install Busybox alongside the module, to ensure proper functionality. I recommend [MENTION=4544860]osm0sis[/MENTION]' Busybox, installable as a Magisk module from the Magisk repo.

Added fingerprints for Google Nexus 7 (2012 & 2013, WiFi & LTE), Nexus 9 (WiFi & LTE) and Pixel C, LG V30, Motorola Moto E5 Plus, OnePlus 6T, Samsung Galaxy J7 Prime and S5, and Xiaomi Mi 8. Updated the fingerprint for Huawei P8 Lite and Xiaomi Mi Mix 2s. List updated to v38.

Probably some other small fixes as well. Can't remember...
[Magisk] Johnn78:
This module is to pass the ctsprofile or basicIntegrity of safetynet ?
[Magisk] Didgeridoohan:
It makes me sad when I go through all that effort to write proper documentation, and then noone reads it... :crying:

Oh well... Just for you I made a bit clearer in both the OP and the module documentation.
[Magisk] Yurienu:
Thank you very much for your work!

Some updated fingerprints for XZ1 Compact (G8441/lilac/yoshino):

XZ1 Compact Pie=Sony/G8441/G8441:9/47.2.A.2.33/3676206253:user/release-keys__2018-11-01

XZ1 Compact Oreo=Sony/G8441/G8441:8.0.0/47.1.A.16.20/623594567:user/release-keys__2018-09-01 (I believe there won't be any more recent fingerprint for Oreo)

Both are valid, HOWEVER I noticed (what I believe is) a bug when you put both lines into a printslist file in a file saved using Carriage Return characters (CR) by Windows. I believe that your module is keeping the (hidden) CR character that is at the end of the security patchlevel because the first line will result in a failed SafetyNet but not the second. If you revert the two lines, the first is still failing. If you save the file using simple return lines from Unix systems, both are valid.
[Magisk] Didgeridoohan:
Thank you for the updated fingerprints. I'll make sure to check them out when I have the opportunity.

But, about your bugreport: When working with Magisk and it's script (and shell scripts in general) you should always use Unix line endings... I guess I could specify that in the documentation, or even add a function in the module to simply sed replace any trailing CR characters found in the printslist and configuration files (the only ones that should have any user input).
[Magisk] Yurienu:
You're right, I'm always on Linux unless I'm at work, where I don't have much choice, which was the case at that moment.

The most userfriendly option would be to strip CR characters indeed, but in the meantime, adding a short warning in the documentation is enough to save some headscratches.
[Magisk] torben5247:
fingerprints for z4 tablet lte karin :

xperia z4 tablet lte=Sony/SGP771/SGP771:7.1.1/32.4.A.1.54/219395100:user/release-keys__2017-09-01
[Magisk] :
Redmi Y1 fingerprint

Redmi Y1=xiaomi/ugg/ugg:7.1.2/N2G47H/V9.6.2.0.NDKMIFD:user/release-keys__2018-07-01
[Magisk] allrockedout:
[MENTION=4667597]Didgeridoohan[/MENTION] any support for Xiaomi Mi A2? Would Mi A1 work?
[Magisk] ipdev:
[MENTION=4667597]Didgeridoohan[/MENTION]

Thank you for maintaining MagiskHide Props Config as diligently as you do. :)

Great work, I am using it more and more. My humble opinion, a must have for treble GSI's ;)

Small contribution to the project.

(Some more December fingerprints.)

Note:

Pulled from official release boot and recovery images.

PH1 Link

Google Link

Second Note:

[MENTION=3885843]allrockedout[/MENTION]

Added Mi A2 to the attached list.

Mi A2 Link

Gave me something to do while I was waiting when wiping and flashing a Nexus 7.

[/I]

Cheers :)
[Magisk] allrockedout:
[MENTION=7280276]ipdev[/MENTION] thanks man that was really quick.
[Magisk] Didgeridoohan:
Update to v2.7.1-v39

I was given a whole bunch of new and updated fingerprints over the past few days, by several friendly users. Huge thank you to [MENTION=8030733]Yurienu[/MENTION], [MENTION=5219494]torben5247[/MENTION], [MENTION=8944774]Sanish Patil[/MENTION] and last but definitely not least [MENTION=7280276]ipdev[/MENTION]. Decided to also make a small update to the module at the same time, thank you to [MENTION=8030733]Yurienu[/MENTION] for the heads-up on the issue with Windows file endings.

Changelog

v2.7.1

Fixed an issue when users create custom prints list and configuration files with Windows file endings.

Fixed an issue where the currently picked device wouldn't show for the custom prints list.

Added fingerprints for Sony Xperia Z4 Tablet LTE and Xiaomi Mi A2 & Redmi Y1. Updated fingerprints for Essential PH-1, Google Nexus 5X & 6P, Pixel 1-3 (both regular and XL) & C and Sony Xperia XZ1 Compact. List updated to v39.
[Magisk] AxiomGarden:
For Sony Xperia XA2 Single Sim

Sony Xperia XA2 (8.0.0)=Sony/H3113/H3113:8.0.0/50.1.A.13.83/2475295922:user/release-keys__2018-09-01
[Magisk] adelpozoman:
I cant believe this is happening. I am on G4 (H815 7.0) and I did props - h812 6.0. And now I am watching netflix. Thanks! Great work!!
[Magisk] By.TRabZonLu™:
MI 8 Android 9

:/ # getprop ro.build.fingerprint

Xiaomi/dipper/dipper:9/PKQ1.180729.001/8.11.15:user/release-key

When do you add to the list? android You have added version 8.1.

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=PKQ1.180729.001

ro.build.display.id=PKQ1.180729.001

ro.build.version.incremental=8.11.15

ro.build.version.sdk=28

ro.build.version.preview_sdk=0

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=9

ro.build.version.security_patch=2018-10-01

ro.build.version.base_os=

ro.build.version.min_supported_target_sdk=17

ro.build.date=Thu Nov 15 17:06:14 CST 2018

ro.build.date.utc=1542272774

ro.build.type=user

ro.build.user=builder

ro.build.host=c4-miui-ota-bd41.bj

ro.build.tags=release-keys

ro.build.flavor=dipper-user

ro.product.model=MI 8

ro.product.brand=Xiaomi

ro.product.name=dipper

ro.product.device=dipper

ro.product.mod_device=dipper_global

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,

# use ro.product.cpu.abilist instead.

ro.product.cpu.abi=arm64-v8a

ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi

ro.product.cpu.abilist32=armeabi-v7a,armeabi

ro.product.cpu.abilist64=arm64-v8a

ro.product.locale=en-GB

ro.wifi.channels=

# ro.build.product is obsolete; use ro.product.device

ro.build.product=dipper

# Do not try to parse description, fingerprint, or thumbprint

ro.build.description=dipper-user 9 PKQ1.180729.001 8.11.15 release-keys

ro.build.fingerprint=Xiaomi/dipper/dipper:9/PKQ1.180729.001/8.11.15:user/release-keys
[Magisk] kucingbaik2:
i iwas change fihgerprint

but i want to know is same funtion with device fake

??

cause i cheked still same with my phone device

my phone xiaomi redmi note 3 pro
[Magisk] Didgeridoohan:
I add new and updated fingerprints to the list whenever someone posts them and I have time to test and update the module. There hasn't previously been posted any working Android Pie fingerprint for the Mi 8, so Android 8.1.0 it is...

I'll make sure to check this one out when I have some time to kill. Thank you.

Changing the fingerprint of the device is not enough to make your device completely appear as a different device. You would also have to change a whole bunch other props to match whatever device you are trying to simulate.

If you know which device and what props you need to change (ro.build.description, ro.build.name, ro.build.flavor, ro.product.name, ro.product.device are some that come to mind but there are going to be a whole host of other ones as well/instead), you can easily accomplish what you want with the Custom props function of this module. And since we're likely talkning about a rather large amount of props, it'd be a good idea to use the configuration file when setting everything up.

Finally, I have no idea if it is enough to change prop values to fake a different device. I'd be happy to hear your results if you get it working.

Good luck.
[Magisk] Didgeridoohan:
Wait a minute... Now I recognise you. You've posted that fingerprint before in a different thread. I did test it but it would not let CTS pass on my device. I'll take a look at it again...
[Magisk] kucingbaik2:
thank you sir, for explanations

:highfive::good::good:
[Magisk] By.TRabZonLu™:
This is the situation now. The phone is getting update every week. I can share the last week's information if you want.

Xiaomi mi 8 android 9, stock global beta
[Magisk] Didgeridoohan:
That's why the fingerprint doesn't pass... Some manufacturers don't bother to certify a beta release, especially if they release that frequently. Wait for the stable release and the fingerprint will probably pass CTS just fine.
[Magisk] By.TRabZonLu™:
No problem in stable release. Xiaomi company is committed to offering us two options and beta. Beta rom is getting updates every week. Android version does not change. Only number that changed. For example, this week's rom code is 8.12.7 ... 2018.12.7
[Magisk] By.TRabZonLu™:
New problem
[Magisk] By.TRabZonLu™:
I downloaded and installed the program gave Busybox error. Then I installed the Xiaomi Mi 8 version. I re-started. It works smoothly. But the android version says 8.1. Is it a problem?
[Magisk] Didgeridoohan:
Well... Do you have Busybox installed?

Edit: never mind...
[Magisk] Didgeridoohan:
Shouldn't be a problem.
[Magisk] X4K7:
Bug on Mix 2s

Hi, I'm using Xiaomi Mix 2s on MIUI 8.12.7 Global Beta on Android 9, Magisk 18.0

the ctsProfile status is false when i update the OS and update magisk also from MIUI 8.11.23 to 8.12.7, and from magisk 17.1 to 18.0

when i try to run the 'props' command on terminal, it says that the late_start service boot script can't be found.

I already installed busybox using magisk module and restart the device several time but still no luck.

You can find the logs here

Thanks
[Magisk] Didgeridoohan:
Try uninstalling the module and installing it again.
[Magisk] olivercervera:
[MENTION=4667597]Didgeridoohan[/MENTION]

Some Samsung apps don't work because of root on Samsung devices.

S-Health in particular can work by simply editing a line in build.prop:

change

ro.config.tima=1

to

ro.config.tima=0

I am wondering if this change is relevant to your module, I have checked your source and it isn't there. Since I don't like editing build.prop manually would be great to have it added to your module (if relevant).

I am also looking for other potential props that could help to use other Sammy apps.

PS: I have just discovered I can add custom props with your module, great. However this trick would work out of the box for all Samsung devices.
[Magisk] Didgeridoohan:
[MENTION=3341206]olivercervera[/MENTION] In a way that is slightly outside the scope of this module. I haven't really had any intention of adding any further kind of root detection/hiding stuff to the module than changing the device fingerprint to pass CTS verification.

You can use the module to achieve the desired result though, since you very easily can use the Custom props function of the module to change that particular prop.

Although, thinking about it, if you do find a bunch of props that are useful for getting Sammy apps to work, I could consider adding a function to the module for that... It wouldn't be too much work actually (famous last words).
[Magisk] X4K7:
Well, that fixed it, thanks!
[Magisk] Jos_Hdez22:
A digital banking app is making my device appear as not certified when you set it as the default Touch and pay payment method of the phone. Any idea to solve this? The app is "Super Wallet" of Santander bank
[Magisk] TheUndertaker21:
hope note 9 will be added to the list soon but s9/plus works fine though
[Magisk] Didgeridoohan:
No idea... And it's slightly outside the scope of this thread. Try the Magisk general support thread or open a new one.

I doubt you need Universal SafetyNet fix, and depending on the version you use it messes up Magisk internals... Apart from that it does the same thing this module does, changes the device fingerprint and in that case to a Xiaomi one. And if you have it installed, this module won't work.

After you installed MagiskHide Props Config, did you run the props command and set a certified fingerprint? If you have questions about how things work, start with taking a look in the documentation. Most things are covered there.

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] TheUndertaker21:
Note 9 build

That's Android 9 one. But should work for 8.1 I think
[Magisk] pekkle_hksar:
Xiaomi/dipper/dipper:9/PKQ1.180729.001/V10.1.1.0.PEAMIFI:user/release-keys

Latest fingerprint of xiaomi mi 8 global running Android P
[Magisk] PHiDi:
Xiaomi Redmi Note 5 Global latest fingerprint.

Redmi Note 5 MIUI Global 10.0 Stable 10.0.6.0 OEIMIFH / Android 8.1.0 / Security Patch 2018-11-01

xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V10.0.6.0.OEIMIFH:user/release-keys

Thanks for your work :good:
[Magisk] Nebrassy:
Please update fingerprint for Xiaomi Mi A2

[ro.build.fingerprint]: [xiaomi/jasmine/jasmine_sprout:9/PKQ1.180904.001/V10.0.2.0.PDIMIFJ:user/release-keys]

[ro.build.version.security_patch]: [2018-12-05]
[Magisk] Ramzir1:
You've worked with me on the release 6.0.1

I want you to add the version 7.2.1 Custom Rom

---------- Post added at 05:32 PM ---------- Previous post was at 05:32 PM ----------

You've worked with me on the release 6.0.1

I want you to add the version 7.2.1 Custom Rom :good:
[Magisk] Didgeridoohan:
[MENTION=6948826]Nebrassy[/MENTION] just reminded me of something... Could you guys also please provide the security patch date that corresponds to the fingerprints you've supplied. Thanks.
[Magisk] Didgeridoohan:
A fingerprint from a custom ROM will not be able to pass the CTS check. If you're on a custom ROM you have to use a fingerprint from an official release, even if it isn't the same Android version.
[Magisk] Didgeridoohan:
Not the topic for this thread. Please edit your post to remove...

(I don't particularly like blatant self promotion in other people's threads.)
[Magisk] ninad1234:
Sorry for the wrong post. Please delete my post.
[Magisk] Ramzir1:
I mean to modify the system build.prop And change fingerprint from an official

Do you succeed?:rolleyes:
[Magisk] Didgeridoohan:
I'm guessing we have some kind of language barrier going on here...

You provided a 6.0.1 fingerprint for the Samsung S5, right? But, if you want a newer fingerprint for the S5 I think you'll be disappointed since, if my searching skills aren't failing me completely, there was never any official version of Android past 6.0.1 for the Samsung Galaxy S5.

If you want a newer fingerprint you'll have to use one of those that are included in the list already...
[Magisk] Ramzir1:
thank bro
[Magisk] TheUndertaker21:
View attachment 4665275

Love that you replied to almost everyone here.

Very active thread.
[Magisk] Skulldriver:
Hello! Noob here hoping to get help...

Galaxy note 9 n9600 oreo 8.0.1 rooted with magisks v18... unable to pass safetynet both basic and cts.

Prior to v18 I passed both no issues (17.3) with xposed installed systemless.

I tested magiskshide....works fine...tested it on root checker app.. also unticked MagiskHide option, rebooted, checked it back on, rebooted...

Any ideas on where to proceed?
[Magisk] Didgeridoohan:
I don't know what you where doing earlier, but passing SafetyNet with Xposed active isn't possible, not even if it's systemless.
[Magisk] pekkle_hksar:
ro.build.version.security_patch=2018-11-01

ro.build.fingerprint=Xiaomi/dipper/dipper:9/PKQ1.180729.001/V10.1.1.0.PEAMIFI:user/release-keys
[Magisk] microMXL:
Nice, this one worked like a charm on lineageOS 15.1 on google pixel (sailfish)
[Magisk] max2348:
I still have a CTS false with Havoc OS 2.0 on OP5 after flashing the zip
[Magisk] DemonLoader:
Hello. Thanks for this module.

I'm having an issue getting the mod to run after install + reboot in Magisk 18. The terminals are granted su in BusyBox, and the module installs normally, but says to reboot every time I run it. I'm attaching the logs below. Am I missing something?
[Magisk] Nebrassy:
[MENTION=4667597]Didgeridoohan[/MENTION] have you tested this one yet? Some people are reporting that it isn't passing on custom roms, if so we can use the older one

xiaomi/jasmine/jasmine_sprout:9/PKQ1.180904.001/V10.0.1.0.PDIMIFJ:user/release-keys

2018-11-05
[Magisk] Didgeridoohan:
And you've set the module up with a certified fingerprint as well, right? It's not a flash and forget module, there's some setup required...

Your file has gotten corrupted somehow, so no logs... But, ususally that problem is fixed by uninstalling and reinstalling the module.

I have not actually. Too busy between my studies and playing with my baby boy. Hopefully some time this week.
[Magisk] Seagold:
Please add A5 2017
[Magisk] VVAREZ:
I have the not found problem and I dont have any /cache or /data/cache folders.
[Magisk] compgamer89:
Xiaomi MI PAD 4

[MENTION=4667597]Didgeridoohan[/MENTION]

ro.build.fingerprint=Xiaomi/clover/clover:8.1.0/OPM1.171019.019/V10.1.1.0.ODJCNFI:user/release-keys

ro.build.version.security_patch=2018-10-01
[Magisk] ipdev:
Sorry, I have been meaning to post this for a few days.

I have been having some problems with Magisk, so that has been taking the little time I have this week, still trying to narrow it down.

Mi A2 (v10.0.2.0) Worked for me, Passed SafetyNet and Play Certification.

It was a clean install. I setup Magisk, BusyBox for Android NDK and MagiskHide Props Config, prior to logging into my google account.

Note:

Something caught my attention when I switched the fingerprint to OnePlus 5T.

I never noticed it before but, after switching the fingerprint, Play Certification did not show up under PlayStore's Settings page. Regardless of Cache and Data clearing, SafetyNet still passed and had no problem installing or updating from PlayStore.

Only showed Certified, when I went back to the original fingerprint I was using when I first logged into Google.

Note 2:

Still narrowing it down but, besides wiping PlayStore data, it seems I have to actually have to disable PlayStore, reboot and enable PlayStore, reboot and then the new fingerprint will show Certified in PlayStore.

Note 3:

Still working on my Magisk issues, seems to be related to flashing a patched boot image verses flashing Magisk in TWRP.

PS.

Attached my work-in-progress printslist

Cheers. :)
[Magisk] Nebrassy:
Yeah I've tested 10.0.2.0 and it's working for me, after clearing play store data I need to wait s while, exit and open play store again for certification to show up
[Magisk] Didgeridoohan:
There are a few possible reasons for what you're seeing:

The module isn't installed.

The module is installed but the Magisk Core Only Mode is active.

The module is installed but there's something wrong with how Magisk mounts the file.

Something else.

Without at least the Magisk log (and preferably the Canary debug log since it is much more verbose), there's no telling what is going on.

Just as [MENTION=6948826]Nebrassy[/MENTION], I've always had to wait for a while before the Certification appears after clearing data for the Play store. I've never seen it suddenly disappear by just changing the fingerprint. I doubt it's going to cause any issues though...