yashsingh1/xdaforums huggingface dataset:
[Magisk] Some_Random_Username:
Huawei P20 EML-L09 Android 10 fingerprint (it was about time Huawei update that device): HUAWEI/EML-L09/HWEML:10/HUAWEIEML-L09/10.0.0.161C109:user/release-keys__2020-04-01
[Magisk] Displax:
Pixel`s update

Pixel 2=google/walleye/walleye:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
Pixel 2 XL=google/taimen/taimen:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
Pixel 3=google/blueline/blueline:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
Pixel 3 XL=google/crosshatch/crosshatch:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
Pixel 3a=google/sargo/sargo:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
Pixel 3a XL=google/bonito/bonito:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
Pixel 4=google/flame/flame:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
Pixel 4 XL=google/coral/coral:10/QQ3A.200705.002/6506677:user/release-keys__2020-07-05
[Magisk] zfk110:
I'm looking fingerprint for Asus ROG Phone II i001da I tried Zenfone 6 but it didn't work
[Magisk] Didgeridoohan:
Covered in the docs:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x

And:

https://xdaforums.com/showpost.php?p=82987927&postcount=3665

(I really need to add this to the docs and Magisk troubleshooting guide...)
[Magisk] etavav:
Thank you. As result I found all build.prop's thru shell and made patch script for TWRP for all build.props in my system. System load normal. And now Tags is release-keys and the app work.
[Magisk] tazcan:
If my safety checking is hardware currently, will changing the fingerprint or spoofing another device help to pass Cts or there is nothing I can do right now?
[Magisk] Didgeridoohan:
It will not and for now (and likely forever) there's nothing you can do (short of going stock and locking your bootloader).

Edit: of course, there's always the chance someone will come up with something creative. But that's a very slim chance...
[Magisk] iamelton:
just downloaded the module from the first post.. though its labelled the latest v5.2.6 version, it seemed to be the previous v5.2.5..

i installed it and it asked for external busybox installation..
[Magisk] Didgeridoohan:
That is hilarious... Not the first time I mess up the zip in the OP either. And 3000+ downloads before anyone mentions anything. :laugh:

Download from the Manager and you should get the real deal. I'll fix the OP later.
[Magisk] LBA97:
New submission:

Realme X2 Pro, RealmeUI C28

ro.build.version.security_patch: 2020-06-05

ro.build.fingerprint: realme/RMX1931EEA/RMX1931L1:10/QKQ1.191021.002/1590460856:user/release-keys

ro.product.manufacturer: realme

ro.product.model: RMX1931

Thanks!
[Magisk] KubTreeps:
My device RN8Pro tested successfully in v92 Global (MI)

My device RN8Pro tested successfully in v92, but now it’s not possible. прошу вернуть в версию 93 глобальную версию (mi) RN8Pro.

I was very happy with your application, until the last firmware and update .. (I put the key from 9 andrid)

but my gsi are at 10(Q). this did not stop using the nfs.

I really hope for your support. you are my only chance. I have linage os 17.1
[Magisk] Didgeridoohan:
I'm assuming you no longer can pass CTS. Which is expected now that Google are rolling out hardware key attestation... Details:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unlocked_bootloader_3

As a side note, I never had a Redmi Note 8 Pro global fingerprint included in the module list. As you see in the post you quoted:
[Magisk] Qi Xuan:
Hi, New submission:

Redmi 6 Pro, Android 9

ro.build.version.security_patch: I can't find this

ro.build.fingerprint=xiaomi/sakura/sakura:9/PKQ1.180917.001/20.1.9:user/release-keys

ro.product.model=Redmi 6 Pro

ro.product.manufacturer=Xiaomi

Thanks!
[Magisk] Didgeridoohan:
Thanks, but the security patch date is kind of important... It is necessary to have the right one or CTS won't pass (and guessing the date is not a feasible solution).

Although, I guess that's a bit of a moot point now that hardware key attestation seems to be rolling out for real.
[Magisk] GtrCraft:
Update for Poco X2:

fingerprint: POCO/phoenixin/phoenixin:10/QKQ1.190825.002/V11.0.11.0.QGHINXM:user/release-keys

security patch: 2020-06-01
[Magisk] Didgeridoohan:
Module updated to v5.2.7-v94

A couple of mileposts being reached recently, so I thought I'd celebrate with a small update to the module and the fingerprints list.

First milepost is kinda cool (to me at least): the module has reached 100k downloads here in the thread on XDA. The real number of downloads are gonna be much higher though (I can't track the number of downloads from the Magisk Manager and I assume that's the main source, and I know the zips get hosted at a number of other locations as well), but seeing that big 6 digit number is pretty neat. Thanks everyone!

Second milepost isn't that cool. It was a good run, but the fun might finally be over... If you haven't heard about it already, Google have started rolling out the SafetyNet update using hardware backed key attestation for checking the bootloader state. This means that the main feature that has made this module kind of popular is not gonna work anymore for a whole lot of users: helping to pass CTS on a custom ROMs or otherwise uncertified devices. Bummer... But expected.

The module isn't entirely dead though, you'll still be able to pass CTS on older devices (those that shipped with an Android version lower than 8, until Google bans those from passing SN) and devices where the manufacturer messed up the implementation and you'll still be able to set custom props with it. I'll even keep the fingerprints list updated if there are any submissions, but it's kind of a futile exercise... But hey, who knows. Maybe someone will come up with that golden hack to stick it to the man once more (I doubt it).

Huge thanks to [MENTION=6345368]Displax[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=9098612]Filo1995[/MENTION], [MENTION=4519796]rdis[/MENTION], [MENTION=6003981]LBA97[/MENTION] and [MENTION=5293805]GtrCraft[/MENTION] for providing the fingerprints for this update. As always, it just wouldn't be the same without all your help. :highfive:

Changelog

Added a new run option to set custom props directly from the command prompt. See the documentation for details. Shoutout to [MENTION=4262053]ps000000[/MENTION] @ XDA Developers for putting the idea in my head.

Added fingerprints for OnePlus 8 IN2019, Realme X2 Pro, Samsung Galaxy A90 5G and Tab A 8.0 LTE 2019. Updated fingerprints for Google Pixel 2-4 (all variants), Huawei P20, OnePlus 8 IN2017, POCO X2 and Xiaomi Mi A1, Mi A2, Mi A2 Lite and Mi A3. Fingerprints list updated to v94.
[Magisk] cybermaus:
Small question:

If the Samsung A30s A307FN/DS is not on the list, is that because of no-one submitting a fingerprint yet, or because it is one of the mentioned hardware checking unlucked bootloaders, so not possible anyway? I have (access to) two of them, one rooted, one not, so if someone tells me what to do, I may be able to get a fingerprint from a clean one.
[Magisk] Didgeridoohan:
That'll mean nobody has submitted a working print for the device.

Details on submitting a print can be found here:

https://github.com/Magisk-Modules-R...aster/README.md#how-do-i-submit-a-fingerprint
[Magisk] Riski3Run:
I can confirm this helps me to fix ctsProfile:true so both are green now with basicIntegrity:true

Device: OnePlus7T OOS 10.0.9.HD65BA
[Magisk] Didgeridoohan:
The hardware based key attestation hasn't rolled out to all devices yet, so there are many that can pass CTS still.

There was even a rumour the first time Google showed us this new check that OnePlus had messed up their implementation of the attestation, so maybe you're good...
[Magisk] Riski3Run:
Of course I am good haha. View attachment 5057769View attachment 5057771

Wysłane z mojego HD1903 przy użyciu Tapatalka
[Magisk] Didgeridoohan:
Yes, you already told us that you are passing both CTS and basic integrity, no need to reiterate...

What I meant was that maybe OnePlus have messed up their devices so that hardware key attestation doesn't work properly. Although that guess is based on an old rumor and might have no merit whatsoever (I'm 100% sure it has no merit).

Heck, might even be the Google is just testing things again and we'll all go back to passing CTS once again. Until they see fit to change that, that is...
[Magisk] mrjuniork:
Unless OP did that on purpose, who knows?

Since they are so dev-friendly ;)
[Magisk] naotefalo:
got my Mi A3 stuck on logo after changing Props. How I can restore it?
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] pndwal:
Refined silver hack now available, reportedly working for many for now:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83035285

Original:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83028387

Golden hack still extant. :(

And congratulations on those impressive milestones Didg... Hope temp. fix from Displax may get your elegant module a bit more mileage too! :D PW
[Magisk] Didgeridoohan:
I've seen it. Since they're not making a universal rollout yet it makes some kind of sense that they're using some way of identifying the device and that we can interrupt the with a prop change.

A fix, it seems, but temporary.

Thanks. And you had to go there, huh? :D
[Magisk] pndwal:
Of course you saw it! - that was for the less aware. :D

...And definitely temporary; not the elusive Golden hack. :(

Only because you like us to keep thread on topic but. - Have to get a bit creative at times, eh?

But you are too modest.

Keep up the helpful efforts mate. Thanks or not, most appreciate it. :good: PW
[Magisk] xuxu1:
Update for Redmi 8:

$ getprop ro.build.fingerprint

Xiaomi/olive/olive:10/QKQ1.191014.001/V11.0.1.0.QCNCNXM:user/release-keys

$ getprop ro.product.manufacturer

Xiaomi

$ getprop ro.product.model

Redmi 8

$ getprop ro.build.version.security_patch

2020-06-01
[Magisk] __Michael__:
Hi,

I am still getting bootloop after using the module .

Sent you pm with all the logs .

Thanks mate!
[Magisk] Some_Random_Username:
Fingerprints update for OnePlus 8-series:

OP8

IN2011 OnePlus/OnePlus8_IND/OnePlus8:10/QKQ1.191222.002/2006300108:user/release-keys__2020-06-01

IN2013 OnePlus/OnePlus8_EEA/OnePlus8:10/QKQ1.191222.002/2006300106:user/release-keys__2020-06-01

IN2015 OnePlus/OnePlus8/OnePlus8:10/QKQ1.191222.002/2006300109:user/release-keys__2020-06-01

OP8PRO

IN2021 OnePlus/OnePlus8Pro_IND/OnePlus8Pro:10/QKQ1.191222.002/2007021926:user/release-keys__2020-06-01

IN2023 OnePlus/OnePlus8Pro_EEA/OnePlus8Pro:10/QKQ1.191222.002/2007021926:user/release-keys__2020-06-01

IN2025 OnePlus/OnePlus8Pro/OnePlus8Pro:10/QKQ1.191222.002/2007021926:user/release-keys__2020-06-01
[Magisk] Qi Xuan:
Hi, I found it!

ro.build.version.security_patch=2019-12-01

Thanks a lot! :D
[Magisk] Displax:
Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.17.0.QFQMIXM:user/release-keys__2020-06-05
[Magisk] ronlkh:
Hi, I have a xiaomi mi9pro 5g crux. May I know will there be a finger print fit this device? Thanks
[Magisk] mohitanchalia:
Update for K20 Pro (raphaelin)

$ getprop ro.build.fingerprint

Xiaomi/raphaelin/raphaelin:10/QKQ1.190825.002/V12.0.1.0.QFKINXM:user/release-keys

$ getprop ro.build.version.security_patch

2020-06-01
[Magisk] amrithaathmaram:
Update for Honor 6X

ro.build.fingerprint

HONOR/BLN-L22/HWBLN-H:8.0.0/HONORBLN-L22/520(C675):user/release-keys

Security patch

2018-11-05
[Magisk] Displax:
Xiaomi Mi A1

xiaomi/tissot/tissot_sprout:9/PKQ1.180917.001/V10.0.23.0.PDHMIXM:user/release-keys__2020-07-01
[Magisk] Some_Random_Username:
Fingerprint update for OnePlus 7 Pro NR Spr GM1925: OnePlus/OP7ProNRSpr/OP7ProNRSpr:10/QKQ1.190716.003/2006051914:user/release-keys__2020-06-01

Another update for OnePlus 8 IN2017: OnePlus/OnePlus8TMO/OnePlus8TMO:10/QKQ1.191222.002/2006102149:user/release-keys__2020-06-01
[Magisk] Gymcode:
I accidentally screwed up my MagiskHide Props Config by not resetting fingerprint to default before I changed device fingerprint and restarted device.

Upon phone restart, all the device settings reverted to default, and I lost access to MagiskHide Props when I tried to su>props in terminal.

It says inaccessible or not found 127

I uninstall it from Magisk, rebooted, and tried to reinstall, but encountered the error of: Installation failed!

Below is the log file. Can I still recover from this? :(

- Copying zip to temp directory

- Installing MagiskHide_Props_Config-v5.2.7-v94(60).zip

- Device is system-as-root

Archive: /data/user/0/com.nKO3B0.TnxsbRJay/cache/flash/install.zip

inflating: module.prop

*************************

MagiskHide Props Config

*************************

*******************

Powered by Magisk

*******************

Archive: /data/user/0/com.nKO3B0.TnxsbRJay/cache/flash/install.zip

inflating: customize.sh

- Extracting module files

Archive: /data/user/0/com.nKO3B0.TnxsbRJay/cache/flash/install.zip

inflating: .gitattributes

creating: .github/

inflating: .github/FUNDING.yml

inflating: LICENSE

inflating: README.md

creating: common/

inflating: common/bootlog.sh

inflating: common/prints.sh

inflating: common/propsconf_conf

inflating: common/propsconf_late

inflating: common/util_functions.sh

inflating: customize.sh

inflating: module.prop

inflating: post-fs-data.sh

inflating: service.sh

creating: system/

creating: system/binpath/

inflating: system/binpath/props

inflating: uninstall.sh

************************

Installing v5.2.7

************************

update-binary: /data/adb/mhpc/propsconf_late: line 1: syntax error: unexpected "("

! Installation failed
[Magisk] Didgeridoohan:
[MENTION=9694089]Gymcode[/MENTION] That's a weird error, because there's no "(" in the propsconf_late file, unless something happened along the way and one of the edit attempts failed horribly...

If you could send me the contents of the /data/adb/mhpc folder (zipped) I might figure out why things went wrong. After that you can try by deleting the very same folder and install the module again.
[Magisk] Gymcode:
I have uploaded the contents in a zip file :fingers-crossed:

I can proceed to delete the "mphc" folder and retry?
[Magisk] Didgeridoohan:
XDA seems to be grumpy today, I only get a 404 error when trying to download that...

But yeah, go ahead.
[Magisk] mohitanchalia:
Update for Redmi K20 Pro (raphaelin)

Xiaomi/raphaelin/raphaelin:10/QKQ1.190825.002/V12.0.2.0.QFKINXM:user/release-keys__2020-06-01
[Magisk] mapagm:
I have Xiaomi MI 9T with Android 9 and i need to choose fingerprint exactly for this model or just watever I want? For example Google Pixel?
[Magisk] mikko3024:
Request to add: Lenovo Tab 4 8 Plus TB-8704F

Lenovo Tab 4 8 Plus TB-8704F (8.1.0):Lenovo:Lenovo TB-8704F=Lenovo/TB-8704F/TB-8704F:8.1.0/OPM1.171019.019/8704F_S001018_191009_ROW:user/release-keys__2019-08-05

Thank you.
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint
[Magisk] sirioo:
you can add op8 IN2010 pls
[Magisk] Didgeridoohan:
If I remember correctly, that's the Chinese version so it won't be Google certified and can never pass CTS.
[Magisk] sirioo:
it always worked with Oos 10.5.8 BA (EU)
[Magisk] Didgeridoohan:
​

If you used an EU ROM it would probably have had the IN2013 fingerprint and would therefore have passed CTS with flying colours.

I'm just guessing here, since I don't have a OP8 or have looked closer at its different versions, but I'm fairly sure that I've collected some knowledge on this to be able to make that guess.

Luckily we have [MENTION=8234677]Some_Random_Username[/MENTION] who can correct me if I'm spouting nonsense.
[Magisk] sirioo:
It has always worked with eu roms ... now it doesn't work because I installed EdXposed to activate VolTE support.
[Magisk] DreamFlasher:
Fingerprint for Fxtec Pro1, build number 20200707225313,
[Magisk] Didgeridoohan:
In that case you are in the wrong thread. This module can't help you pass SafetyNet with EdXposed installed (take a look at the section of red text in the OP). This is only for devices that for whatever reason doesn't have a certified fingerprint.

You'll likely need to find the Canary releases for EdXposed (probably on their Github, but I don't use EdXposed so I wouldn't know) since I've heard that they can pass SafetyNet (but please keep any further queries or discussions about that in another thread).
[Magisk] Didgeridoohan:
Thank you, but there are a few other props that I would also need/want for the print to be included in the list. Take a look in the docs:

https://github.com/Magisk-Modules-R...aster/README.md#how-do-i-submit-a-fingerprint
[Magisk] sirioo:
I read OP and realized that EdXposed caused me the problem. But I repeat with rom eu IN2010 safetynet works
[Magisk] Didgeridoohan:
Yes, and if you look at my reply to you I said the same thing.

The EU ROM will be using the IN2013 fingerprint, not the IN2010. That's why it passes.
[Magisk] sirioo:
Perfect I do tests for the VoLTE and I uninstall EdXposed Without EdXposed could I use IN2013 with eu roms?
[Magisk] DreamFlasher:
Wow, thank you for your quick response!

getprop ro.build.fingerprint: Fxtec/QX1000_EEA/QX1000:9/PKQ1.190723.001/05500.20Q202:user/release-keys
getprop ro.product.manufacturer: Fxtec
getprop ro.product.model: QX1000
getprop ro.build.version.security_patch: 2020-04-05
[Magisk] Didgeridoohan:
As long as you're using a stock, certified ROM you won't need to use any other fingerprint to pass CTS. You'll just have to make sure that you don't have any other mods that trigger SN or that your device isn't using hardware backed key attestation to check your bootloader state and you should be good to go.

I've got a while bunch of tips and info regarding Magisk and SafetyNet, for further details on the above. You'll find it here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] Didgeridoohan:
No worries. I was already viewing the thread, so...

I've verified the print and it's passing CTS. I'll include it in the next update (should be fairly soon, I've received a lot of prints over the past few days).
[Magisk] mohitanchalia:
Request you to include the following print of the Indian 'Xiaomi Redmi K20 Pro' (raphaelin) if possible in your next update:

getprop ro.build.fingerprint: Xiaomi/raphaelin/raphaelin:10/QKQ1.190825.002/V12.0.2.0.QFKINXM:user/release-keys

getprop ro.product.manufacturer: Xiaomi

getprop ro.product.model: Redmi K20 Pro

getprop ro.build.version.security_patch: 2020-06-01
[Magisk] Didgeridoohan:
Isn't that the same one you've already posted?
[Magisk] mohitanchalia:
Yes, sorry I forgot to include the manufacturer and model props earlier, and wasn't sure if editing the post would be noticed.
[Magisk] arjunjangir:
Request for add new device fingerprint for props config in termux .for samsung m30s

hello sir .. i big admire of your page and service given by you .thanks ... but sir i have SAMSUNG M30S . and i already root my device by magisk manager .. its CTSPROFILE FALSE problem show ..when i use in termux ..magisk hide props config .by..SU-PROPS-DEVICE FINGERPRINT.. then i dont found my device fingerprint on that list on device model number that provide by Didgeridoohan . so please add a new fingerprint for SAMSUNG-M30s model .so i Heartly Request to you and your company. please as soon as possible add a fingerprint for .Samsung device . Model number .SAMSUNG M30S... thanks sir
[Magisk] Didgeridoohan:
I would love to. But I'd need your help for that:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] oslo83:
Since Google's CTS checks got enhanced and my devices use hardware evaltype I'm now failing CTS at safetynet.

But my Playstore, which is still with previous cache and data from a time where CTS checks were still succeeding, is still certified ! -And behave like that, it's not only cosmetic.

I'll add playstore has been automatically updated since CTS is now failing and so far playstore certification is still OK.

OOT: I wonder how/if these Playstore/GMS tokens could be backup'ed then restored fine keeping safetynet certified state while CTS checks are still failing.
[Magisk] Didgeridoohan:
If it's possible, maybe something similar to the GPay fix would do the trick. Having the Play Store remain certified even if CTS fails would be very useful.
[Magisk] Didgeridoohan:
[MENTION=8234677]Some_Random_Username[/MENTION] That is amazingly useful. Thank you for testing. I'll go through that little list of yours and update accordingly...
[Magisk] SbAgOoTs:
Dear all, I'm in a boot loop as well... :crying:

Please, help me: is there any way to reset props to their previous state through ADB and TWRP?
[Magisk] SbAgOoTs:
Sorry to seem stupid, but the document mentions: "Place the required file in the root of your internal storage (/sdcard), in /data or in /cache (or /data/cache if you're using an A/B device) and reboot. If you want to reset the module, name the file reset_mhpc, or if you want to disable the module name it disable_mhpc"...

Which required file???:rolleyes:

Maybe the propsconf_conf?
[Magisk] Didgeridoohan:
The last sentence of your quote:
[Magisk] SbAgOoTs:
My doubt was about the file to be used, everything else was clear.

Anyway, thanks: it worked!

:good:
[Magisk] pndwal:
Sorry, I'm stupid too. Which file gets renamed? Is there a 'reset' file in the module zip, as with configuration file? (Glad one of us got smart! :) ) PW
[Magisk] Didgeridoohan:
[MENTION=2722599]SbAgOoTs[/MENTION] and [MENTION=7550078]pndwal[/MENTION]

Whenever someone needs to ask for clarification about an instruction, the instruction usually needs improvements. I altered the paragraph in question to hopefully be easier to understand. :good:
[Magisk] pndwal:
Thanks, got it in one now!

"The greatest lesson in life is to know that even fools are right... sometimes." - Winston Churchill. :D PW
[Magisk] kayamokid:
how to add fingerprints? can someone add fingerprint for asus Zenfone max pro M2 (X01BD)?
[Magisk] ipdev:
Hi.

It's been awhile (OnePlus 5T open beta) but..

I might be completely wrong on all of this. ;)

It might make sense that H2OS would include some of Google's (core) framework, since OOS is based on H2OS.

As for certification, (If I remember correctly) the build were certified during the closed beta. In-turn the open beta and (if stable enough) the official release, were certified since they used the same build number (and security date).

Since 5T is no longer in the beta program, they probably wait until they update official OOS to certify the build.

Where as the devices still in the beta program, should get certified some time in the closed beta build.

If the OOS and H2OS builds are different (names), it is only a few lines in a make file to change the fingerprint before building.

If this is the case, it may bend the rules slightly but, I doubt it breaks them. No reputable manufacture would risk their Google license agreement.

After the initial (Third-Party) device certification, I thought Google's licensed manufactures could self verify (certify) updates to the device.

GMS License, GMS Certification, CTS, VTS. It's been even longer since I looked into all of it and somethings probably changed.

Cheers. :cowboy:
[Magisk] Didgeridoohan:
It's all in the docs:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] kayamokid:
idk but i'm getting false cts with this fingerprint:

asus/WW_X01BD/:9/PKQ1/16.2007.094-20200705:user/release-keys

this one is what i get in my stock rom. it seems not certified. i wanna know what is the certified fingerprint for our device. can someone help me?
[Magisk] Didgeridoohan:
Are you using a stock or custom ROM?

If custom you'll also have to match the security patch date.

If your system is stock and you fail you likely have something that is triggering CTS. You'll find lots of tips and info on that here (hardware based key attestation for the bootloader check is common nowadays):

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet