yashsingh1/xdaforums huggingface dataset:
[Magisk] Displax:
Pixel`s Android 12L update

We need to separate this prints because of new API level 32. But the problem is that this builds showing as common "12" instead as 12L or 12.1.

Spoiler content hidden.

So from official docs we need call it as "12L": https://source.android.com/setup/st...de-names-versions-api-levels-and-ndk-releases

Also, from this moment we need to ask API level when someone post updated or new fingerprint from Android 12 "family platform".

Pixel 3a=google/sargo/sargo:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 3a XL=google/bonito/bonito:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 4=google/flame/flame:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 4 XL=google/coral/coral:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 4a=google/sunfish/sunfish:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 4a (5G)=google/bramble/bramble:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 5=google/redfin/redfin:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 5a=google/barbet/barbet:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05

Xiaomi Mi A3 EU

Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.17.0.RFQEUXM:user/release-keys__2022-02-01

Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.20.0.RFQMIXM:user/release-keys__2022-02-01
[Magisk] Displax:
Another change, that we should done - add new pack of supported partition that used for different props:

"system_dlkm",

"vendor_dlkm",

"odm_dlkm".
[Magisk] :
Redmi Note 9 Pro (joyeuse)

MIUI Global Rom (V12.5.4.0.RJZMIXM) Android 11

Fingerprint: Redmi/joyeuse_global/joyeuse:11/RKQ1.200826.002/V12.5.4.0.RJZMIXM:user/release-keys

Security Patch: 2022-01-01
[Magisk] Namekinek0:
I've got Redmi Note 9 (merlin, M2003J15SC) Miui 12.5.4I've enabled MagiskHide, I've tried to install:

- this module

- the gpay-gms-patch script

- Universal Safety Net Fix install

Nothing works. The safety net test says:

Safety Net Request: success

Response signature validation: fail(Response payload validation failed)

is there something that I'm missing? Maybe DenyList? I think it's the first time I see this option and I've no idea how it works

EDIT: apparently I was missing something:

I wasn't aware that simply installing MHPC doesn't do much...I forced the basic attestation method and then I installed the zygisk version of the Universal Safety Net Fix

Now it works! *Cr1TiKal screaming meme*
[Magisk] Filo1995:
Xiaomi Redmi K30Pro (Android 12) Update

ro.build.fingerprint

Redmi/lmi/lmi:12/SKQ1.211006.001/V13.0.1.0.SJKCNXM:user/release-keys

ro.product.manufacturer

Xiaomi

ro.product.model

Redmi K30 Pro

ro.build.version.security_patch

2022-02-01
[Magisk] 0LDST4R:
Sony Xperia XZ2 Dual H8296, latest Stock FW, Android 10 with proper security patch date 20-07-01, ready for users with LOS 18.1, no additional modules required.

Remove file extention and use as custom fingerprint file.
[Magisk] Filo1995:
Xiaomi Redmi K30Pro (Android 12) Update

Rom updated today.Here is the new fingerprint.

ro.build.fingerprint

Redmi/lmi/lmi:12/SKQ1.211006.001/V13.0.2.0.SJKCNXM:user/release-keys

ro.product.manufacturer

Xiaomi

ro.product.model

Redmi K30 Pro

ro.build.version.security_patch

2022-02-01
[Magisk] Jexboxer:
Realme Narzo 20 Pro

ro.build.fingerprint

realme/RMX2161/RMX2161L1:10/QP1A.190711.020/1623904874:user/release-keys

ro.product.manufacturer

Realme

Security patch June, 2021
[Magisk] m0han:
@Didgeridoohan and others, I ran into an issue with CTS Profile Match failing on Poco X3 (Karna) device running crDroid A12 rom of 14-Mar-2022 (Android Security Patch date 5-Feb-2022). It all could have started after I tried to update Magisk Canary to 24304 soon after it was released. I did not change any settings anywhere (surely nothing w.r..t. Magisk). After trying a lot of things with several users trying to help, nothing has worked till now. I then flashed MagiskHidePropsConf v6.1.2 (tbh, I hadn't needed this in a long time), but my device didn't boot. I booted into recovery & renamed the folder and thus was able to boot into the system. Almost everything except YASNAC is as before. btw, I was on AOSPeXtended A12 rom earlier. now i'm on crDroid A12 - if that matters.

I have a few questions:

i) Could my issue be rom-related?

ii) Could MagiskHidePropsConf get CTS to pass?

iii) How can I use it without getting into further bootloops?

Screenshot showing the modules I'm using is attached. I hope you/someone can help. Thanks.
[Magisk] cash1220:
I had a lot of problems passing CTS Profile Match after upgrading to a custom Android 12 ROM on an old HTC U12+ device and I will share how I was able to pass.

1) Choose custom fingerprint

2) Set custom prop ro.build.version.security_patch to the correct date (the date should be shown if you don't know it)

3) Set prop boot stage to late_start service

That's it. No Universal SafetyNet Fix needed. The key for me was setting the prop boot stage to late_start. This also fixed another issue with Zygisk not initiating after enabling it.

Edit: I also had to change the kernel I was using to get CTS Profile Match to pass.
[Magisk] m0han:
can i take it to mean that - even after using mhpc - you had to flash a different kernel to get cts profile match to pass? if so, maybe my issue lies therein and i should let the dev of my rom know this. thanks for your tips.
[Magisk] cash1220:
After I got CTS Profile Match to pass using the steps stated above I changed my kernel and noticed CTS Profile Match failed so I had to revert back to the other kernel I was using. So in my experience certain kernels as well as any prop boot stage other than late_start cause the CTS Profile Match to fail.
[Magisk] Camisa:
berlna:/ $ getprop ro.build.fingerprint
motorola/berlna_global/berlna:11/RRMS31.Q3-23-77-1-3/faee2:user/release-keys

berlna:/ $ getprop ro.build.version.security_patch
2022-03-01

berlna:/ $ getprop ro.product.manufacturer
motorola

berlna:/ $ getprop ro.product.model
motorola edge (2021)
[Magisk] :
Have anyone successfully tried this module to enable unlimited google photos storage with original quality?
[Magisk] m0han:
Replying to myself: Turns out my 'CTS Profile Match failing' issue could have been ROM-related. After I updated my ROM, it is passing. MHPC not needed.
[Magisk] rodken:
OnePlus8VZW

Android Version: 11

ROM: Stock - OxygenOS 11.7.IN67CD

Root Method: Alpha-Magisk 24.1

Device Fingerprint: OnePlus/OnePlus8VZW/OnePlus8VZW:10/QKQ1.191222.002/2011031214:user/release-keys

Security Patch: M02 1,2022

Manufacturer: OnePlus

Model Number: IN2020
[Magisk] livinabsurdism:
Does anyone have any insight into if there is a way to:

- use this module without having to reboot the device?

- send one single command to handle any changes you want to make to the device?

Thanks in advance.
[Magisk] KelleyCook:
Thanks, worked perfectly. Until now, CTS profile has been wrong at least since Lineage 18, but it didn't seem to matter with MagiskHide. But yesterday at the store without a wallet, I realized that I haven't had GPay since the Magisk 2.4 came out. This restored that functionality.
[Magisk] rener78:
Still need that?

$ getprop ro.build.fingerprint

google/crosshatch/crosshatch:12/SP1A.210812.016.C1/8029091:user/release-keys

$ getprop ro.build.version.security_patch

2021-10-05

$ getprop ro.product.manufacturer

Google

$ getprop ro.product.model

Pixel 3 XLp

If not oh well
[Magisk] jesrani:
I have OnePlus 7T India version HD1901 rooted with OOs 11.0.3.1.

I am rooted with Magisk Canary and all banking apps were working with Magisk Hide enabled. Only BhimUPI was detecting root so I was not using that.

Now suddenly iMobile Pay app (ICICI Bank) is also detecting root after it's latest update.

I updated Magisk Manager to 24.3 version I think and also updated Magisk. Now there was no MagiskHide option but there is a Zygisk option under settings. I enabled this, enabled deny list and selected all banking apps as well as all Google Apps. I also downloaded the MagiskHide Props Config module and Universal SafetyNet Fix. Using the option su -c props in Termux I activated basic key activation with HD1901 option. Now it is showing "Force BASIC key attestion" and "Edit MagiskHide props" as active. In spite of this iMobile Pay is detecting root.

Safetynet is passing.

Currently I have reverted to old version of the iMobile app and it is working.

Is there some other setting I need to do to get this app also working. Otherwise I may have to use without root as I need that banking app.

Is there any way to get Widevine L3, currently it is on L1?
[Magisk] asripath:
Post in thread '[Discussion] Magisk - The Age of Zygisk.' https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86686897
[Magisk] ipdev:
Hi all. :)

Quick update for the fingerprint list.

OnePlus Nord N200 5G Global OOS v11.0.6.0

OnePlus Nord N200 5G [DE2117] (11):OnePlus:DE2117=OnePlus/OnePlusN200/OnePlusN200:11/RKQ1.201217.002/2203021418:user/release-keys__2022-03-01

Cheers all. :cowboy:
[Magisk] Event_Horizon:
I'm using OOS 12.1 aka Android 12 in OnePlus 10 Pro, Using magisk 24.3, Kdrag0n universal safety net fix module, zygisk enabled, magisk hidden, SafetyNet is passing checked in YASNAC, Cleared data for Google Play Store & Services, as Netflix wasn't visible in Play Store, after data clear, Netflix is visible to download & Device is certified in Play Store. TWRP isn't available for OnePlus 10 Pro yet hence I patched the boot.img through Magisk 24.3 as Magisk 23 cannot patch OOS 12 boot.img, getting error while patching.

But Netflix showing error on launch of the app - Sorry, cannot reach Netflix Service, please try again -93

So don't know how & what actually making the cause, other bank apps are working, I feels bootloader is unlocked that's what the issue is? and universal safety net module doesn't help in bypass some verification which the earlier build of magisk 23 was passing with its own safety net bypass, because in S7 Edge & OP7p I'm using Lineage OS 12.1 unofficial with Magisk 23, there Netflix is working.

1 - So is it because of TWRP isn't available for OP10p and I used magisk patching method hence I'm getting error in Netflix??

2 - Bootloader is unlocked hence Netflix not working?

3 - Universal Safety Net doesn't provide bypass in such a level that Netflix catches the system is modified or magisk/root is active or bootloader is unlocked ?

4 - Do we have any module to hide bootloader unlock status?

Any further solution anyone can suggest, I'm 😢

Note*

- several times install uninstall clear data done.

- Magisk hide on, zygisk enabled, Netflix, Google Play & service hidden in configure list, denylist enabled.

- Enclosed screenshots for various stuffs

- Wanted to get the Netflix work, unroot isn't a option as there are 7 different things I use that required root privilege.View attachment 5584611
[Magisk] EetsGeets:
Any chance I could get a fingerprint for SM-N976B (Samsung Galaxy Note 10+ 5G (UK))?

Would I be able to pass CTS profile match with any other Galaxy Note 10+ fingerprint? Would I risk softbricking my phone by doing so? Never messed with fingerprints before.

Running Lineage OS 18.1.
[Magisk] ipdev:
When someone has time to find and submit a valid print with matching date to test. ;)

MHPC Documentation - Please add support for device X - GitHub - Link

MHPC Documentation - Finding a certified fingerprint - GitHub - Link

MHPC Documentation - Matching the Android security patch date - GitHub - Link

MHPC Documentation - How do I submit a fingerprint? - GitHub - Link

--

In the meantime, you should be able to use any of the certified prints.

Normally recommended to stay as close as you can to your own device.

MHPC Documentation - Can I use any fingerprint? - GitHub - Link

---

Quick look on AndroidDumps, I found this one.

This was a quick manual copy and paste of some props from the prop files. 🙃

ro.bootimage.build.fingerprint=samsung/d2xxx/d2x:10/QP1A.190711.020/N976BXXU1BTA1:user/release-keys
ro.system.build.fingerprint=samsung/d2xxx/d2x:10/QP1A.190711.020/N976BXXU1BTA1:user/release-keys
ro.vendor.build.fingerprint=samsung/d2xxx/d2x:10/QP1A.190711.020/N976BXXU1BTA1:user/release-keys

ro.build.version.security_patch=2020-01-01
ro.vendor.build.security_patch=

ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=samsung
ro.product.vendor.manufacturer=samsung
ro.product.vendor.model=SM-N976B
ro.product.vendor.name=d2xxx
ro.product.vendor.device=d2x

ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=samsung
ro.product.system.manufacturer=samsung
ro.product.system.model=SM-N976B
ro.product.system.name=d2xxx
ro.product.system.device=d2x

Quick check of the certified list.

[ip@lost mHideGP]$ cat certified.list | grep 'SM-N976B'
Samsung	Galaxy Note10+ 5G	d2x	SM-N976B

Samsung Galaxy Note10+ 5G [SM-N976B] (10):samsung:SM-N976B=samsung/d2xxx/d2x:10/QP1A.190711.020/N976BXXU1BTA1:user/release-keys__2020-01-01

I did not test it so I am not sure if it works. :unsure:

Cheers. :cowboy:
[Magisk] EetsGeets:
Thank you very much for your help!
[Magisk] ipdev:
Hi all. :D

A new (to me) device ran across my desk. 🙃

Quick check and it was not in the list yet.

So here it is. ;)

Samsung Galaxy Tab A (2016) WiFi [SM-T580]

It was on Android 7.0

I updated from 7.0- > 8.1 -> 8.1 (the final build for the device).

The 7.0 and final 8.1 fingerprints.

Samsung Galaxy Tab A (2016) [SM-T580] (7.0):samsung:SM-T580=samsung/gtaxlwifixx/gtaxlwifi:7.0/NRD90M/T580XXU3BRF1:user/release-keys__2018-06-01
Samsung Galaxy Tab A (2016) [SM-T580] (8.1.0):samsung:SM-T580=samsung/gtaxlwifixx/gtaxlwifi:8.1.0/M1AJQ/T580XXS5CTK1:user/release-keys__2020-04-01

Cheers all. :cowboy:
[Magisk] wkn000:
I would need the properties for a Moto X4 XT1900-7 payton RETEU. The properties in this tool device list doesn't work, also giving CTS profile mismatch.

Here the build information of last stock rom:

BUILD REQUEST INFO:

SW Version: payton-user 9 PPWS29.69-37-5 63ca8 release-keysM660_7045.36.01.100R

MBM Version: MBM-3.0-payton_retail-fe5d8a9-190829

Modem Version: M660_7045.36.01.100R

FSG Version: FSG-660-01.102

Build Fingerprint: motorola/payton/payton:9/PPWS29.69-37-5/63ca8:user/release-keys

CQATest App Version: 6.0.4

VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:

System Version: 29.381.29.payton.retail.en.US

Model Number: moto x4

Android Version: 9

Baseband Version: M660_7045.36.01.100R

Build Id: PPWS29.69-37-5

SW Display Build ID: PPWS29.69-37-5

Build Date: Thu Aug 29 11:02:40 CDT 2019

OTHER MISC VERSION INFO:

Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm

Regulatory Info (eLabel): regulatory_info_default.png

Blur Version: Blur_Version.29.381.29.payton.retail.en.US

Version when read from CPV: payton-user 9 PPWS29.69-37-5 63ca8 release-keys

AB Update Enabled: True

Full Treble Enabled: False
[Magisk] rodken:
OnePlus8VZW

Android Version: 11

ROM: Stock - OxygenOS 11.7.IN67CD

Root Method: Alpha-Magisk 24.3

Device Fingerprint: OnePlus/OnePlus8VZW/OnePlus8VZW:11/RP1A.201005.001/2202091620:user/release-keys

Security Patch: February 1, 2022

Manufacturer: OnePlus

Model Number: IN2020

Code Name: instantnoodlev
[Magisk] ipdev:
@wkn000

Need the matching security date for motorola/payton/payton:9/PPWS29.69-37-5/63ca8:user/release-keys

ro.build.version.security_patch=

Cheers. :cowboy:
[Magisk] wkn000:
@ipdev

Phone is on LineageOS 18.1 with Magisk 24.3, LSPosed Zygisk 1.8.2, FakeGapps 3.0, USNF and MHPC.

ro.build.version.security_patch=2022-04-05 when running getprop

In About phone there is

Android security update = 2022-04-05

Vendor security patch level = 2021-02-01
[Magisk] FloFloFlow:
Hello ! When I run "su props" on Termux I see "props : inacessible or not found", I'm the only one with this issue ?

It's both with 23 and 24.3 Magisk.

Thank you.
[Magisk] casouzaj:
su is one command. And props, another one. Apply su, then props.
[Magisk] FloFloFlow:
Su then props, su -c props, all the same result...
[Magisk] zgfg:
Seems something is wrong with the path in your Termux

props should usually be in /system/xbin

Check my screenshots

Btw, I usually just run props, no need for su (it will take the root privileges anyway)
[Magisk] tejljr:
LG G4​

Android version: 6.0

ROM: LG UX (Stock)

Codename: p1

Device Fingerprint:

lge/p1_bell_ca/p1:6.0/MRA58K/16327114014c4:user/release-keys

Security Patch Date: 2016-11-01

Manufacturer: LGE

Model: LG-H812
[Magisk] ipdev:
@FloFloFlow

If you have not yet, read the props not found and the The boot scripts did not run sections.

MHPC Documentation - props not found - GitHub - Link

Make sure the module is enabled and reboot.

You can try also to install the module again to make sure it installed properly.

- Uninstall the module and reboot.

- Install the module and reboot.

It is possible your Magisk installation is partially broken.

The log files will help figure out what is wrong.

MHPC Documentation - Logs - GitHub - Link

---

@zgfg

The xbin directory was depreciated in Android 10 or 11 so every thing was moved back into the bin directory.

Some devices and/or manufactures will still use xbin for awhile but, it will eventually disappear.

MHPC will check for xbin and use it if it exists.

If not it will use bin.

oriole:/ # which props
/system/bin/props

Some terminal apps and/or devices will not allow props to switch user by itself.

You need to su before running the props command.

Termux is one that you need to switch user before running the props command.

Cheers all. :cowboy:
[Magisk] FloFloFlow:
Thank you very much for your help.

Here are the logs.
[Magisk] zgfg:
Based on bin vs xbin path as described by @ipdev, please simply check the following:

Use ls command in Terminal (first run su) or use root explorer like MiXplorer (root must be granted to)

Go to: /data/adb/modules/MagiskHidePropsConf/system

and check do you have

a) bin/props

or

b) xbin/props

In the first case props is installed to /system/bin,

in the second case to /system/xbin

Indeed, then again use ls or root explorer and check do you see props in your /system/bin or /system/xbin

It must be in accordance to (a) or (b)

And then the same directory must be in the path in your Termux - if not in path, then props will be 'innaccassible or not found'

Hence, in Termux, run:

echo $PATH

and

su

echo $PATH

Termux will display the configured path - be aware with and without su the path might be different

Generally, Termux is powerful but highly configurable (eg, it's path) - hence might not be friendly to newbies

I personally use a different Terminal emulator (a lightweight one from the Net Hunter store) and I never had a problem with the path, it includes all the system executable directories from my phone (screenshot)
[Magisk] FloFloFlow:
Indeed props is not in system/xbin as it should be. Do you have an idea about the origin of the issue?
[Magisk] zgfg:
Hmm, it's in:

/data/adb/modules/MagiskHidePropsConf/system/xbin

but not in:

/system/xbin

It means that Magisk did not properly mount

Did you reboot upon installing MHPC (try rebooting again)

---

You could try the following (dirty), rename xbin folder to bin inside the:

/data/adb/modules/MagiskHidePropsConf/system

and reboot - then it should be mounted to /system/bin
[Magisk] FloFloFlow:
The dirty fix is working. Thank you so much !

edit : I had a message "unmount vendor" error during Magisk installation, maybe it's the problem ? Otherwise root access is working fine.
[Magisk] zgfg:
It depends how your SAR looks like. You might have /vendor or /system/vendor

but eventually one must be mounted to another, that both show the same content

You could check in your case if eg /vendor is empty and /system/vendor not or vice versa, or they show different content

But for MHCP it seems that you don't have /system/xbin (or it is empty) in which case MHCP should have been chosen bin, not xbin

Or regarding to both mounts, something is wrong with the mounting in Magisk

But ok, for now you have MHCP working - be aware that updating of the module might install it again to xbin
[Magisk] Cyndaquissshhh:
Samsung Galaxy A03 (SM-A035F)​

Build fingerprint:​

samsung/a03nnxx/a03:11/RP1A.200720.012/A035FXXU1AVD3:user/release-keys

Security patch:​

2022-03-01

Manufacturer:​

samsung

Model:​

SM-A035F

Samsung Galaxy A03:samsung:SM-A035F=samsung/a03nnxx/a03:11/RP1A.200720.012/A035FXXU1AVD3:user/release-keys__2022-03-01
[Magisk] mikage_kun:
Has anyone had any luck using this module to install Samsung-specific apps on a non-Samsung device? (Galaxy Store, Secure Folder, etc.)?

I was able to do so a while back with a Pixel 2XL, but that was several Android versions ago. I'm currently experimenting with a Pixel 4XL I've designated as a "sandbox" device, which I may have already soft-bricked...he he.
[Magisk] ramzidz15:
Please can you add Added fingerprints for realme c25y
[Magisk] rogers11:
Hello. I've updated (dirty) a Pixel 3a and 4a from LOS 18.1 to 19 this week.

On both devices I reinstalled Magisk after ROM and GApps. I did not reinstall MHCP and Universal SafetyNet Fix. Everything was working and SafetyNet passed.

However, on both machines I could not run props anymore because it wasn't in system/bin.

After reading your post I renamed data/adb/.../xbin/props to .../bin/props on one device and rebooted. props was availabe again.

On the other device I reinstalled MHCP and after reboot props was in system/bin and working.

Don't know what caused the error but renaming data/adb/.../xbin manually or reinstalling MHCP will fix it.

BTW: At the moment SafetyNet passes without MHCP enabled on my devices.
[Magisk] TemporarilyAwake:
Hello all,

Is there any information on fingerprint support for lineageOS 19 on the OnePlus 6T?

My upgrade went awry and I lost the device fingerprint, is there anyone else that was able to solve it?

I'm getting lost in the manual on github, so any help (even pointers to do it myself) would be greatly appreciated!
[Magisk] sloambbr11:
Having some issues getting Device Simulation to work and also passing the CTS Profile Match and hoping someone can help. I'm running [ROM][12.0][STARLTE/STAR2LTE] Project Elixir [OSS][OFFICIAL][TWELVE][AOSP] on my S9+ and trying to get samsung apps to work (ie Smart Things, Samsung Galaxy Wear) and also Google Pay. Currently I can only get one or the other to work.. If I use Device Simulation with a Android 12 fingerprint (currently using Pixel 6) Samsung apps work but CTS profile fails. Changing MHPC to late-boot gets the CTS profile to work, but in YASNAC my device returns to SM-G965F and samsung apps start complaining again my OS has been modified.

Magisk 24.3

Zygisk with DenyList - denying everything samsung and everything Google Play

Un. Safety Net Fix v2.2.1

Have also installed HideMyApplist, Zygistk - LSPOsed and YouTube vanced to decouble youtubevanced from google play.. don't think this part is relevant

Any help would be appreciated to get both working..

edit: should say i've asked on ROM forum and didn't get any love

edit2: did end up getting this to work switched to LineageOS a12, still used Pixel6 fingerprint and only enabled 1,2,3,4,5,9,10 in device sim
[Magisk] alex_nikkou:
OnePlus 10 pro, Android 12. Somehow when I install the module and reboot, my fingerprint scanner immediately stops working (can't use it to unlock the screen, can't send new fingerprints in security settings, etc). When I disable and reboot, it starts working again. Other magisk modules (e g. Universal safetyfix) are working fine and haven't been causing such issues.
[Magisk] Umi max fun:
Please add support for Redmi Note 11 pro (pissarro)
[Magisk] GokberkTunc:
Hi, i flashed android 12L to my note 8. this one.

it has built-in Signature Spoofing. Still i need this module for using Galaxy Wearable app.

Before 12L i was picking some google device that match with my android version. For fingerprint, force basic key attestation and device simulation(all options enabled). And it was working like a charm.

Now i am picking Google Pixel 6 Pro (12) and even if device pass safetynet, galaxy wearable app saying your device not compatibile with this version.

any solution for this?

Thank your precious works.