yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
You;d hope by now

As an alternative, i swapped to this terminal and never looked back...has a nice row of special keys right there on the keyboard :)

NetHunter Terminal | Kali NetHunter App Store - Android App Repository for Penetraton Testing and Forensics

© 2010-2019 Kali Linux, F-Droid, and Contributors

store.nethunter.com
[Magisk] Madhanvic:
I want Motorola Moto one power fingerprint sir
[Magisk] kazo391:
Great Job , but my phone not on the list (Samsung M31) :'(

When i can see it ?
[Magisk] ipdev:
When someone has time to submit a valid print and 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

Cheers. :cowboy:
[Magisk] Provee:
works perfectly on the 2017 samsung galaxy a5 running lineage os 17.1. Thank you so much for making this!
[Magisk] Kapiljhajhria:
Here is latest Android 11 stable fingerprint details for oneplus7t India - hotdogb

# autogenerated by build/make/tools/buildinfo_common.sh
ro.vendor.build.date=Thu May 20 00:28:08 CST 2021
ro.vendor.build.date.utc=1621441688
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:11/RKQ1.201022.002/2105071638:user/release-keys
ro.vendor.build.id=RKQ1.201022.002
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=2105071638
ro.vendor.build.version.release=11
ro.vendor.build.version.release_or_codename=11
ro.vendor.build.version.sdk=30
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T

ro.product.first_api_level=29
ro.vendor.build.security_patch=2021-05-01
ro.telephony.default_network=22,22
vendor.product.device=hotdogb

# Do not try to parse thumbprint
ro.vendor.product.manufacturer.db=OP_PHONE
ro.vendor.product.device.db=OP_DEVICE
# end build properties

ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=11
ro.build.version.release_or_codename=11
ro.build.version.security_patch=2021-05-01
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Thu May 20 00:28:08 CST 2021

# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Thu May 20 00:28:08 CST 2021
ro.system.build.date.utc=1621441688
ro.system.build.id=RKQ1.201022.002
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=2105071638
ro.system.build.version.release=11
ro.system.build.version.release_or_codename=11
ro.system.build.version.sdk=30
# end common build properties
[Magisk] mario0318:
Hey @Didgeridoohan

I seem to encounter a lil glitch when selecting multiple options to run in the device simulation menu, it may occur elsewhere but I haven't really tried and there aren't that many other menus that allow for multiple items to be set at once. So far it appears to be purely visual and doesn't cause any actual errors. Here's a pic:

View attachment 5331963

Notice the beginning and the end of the items list I selected to be set, preceded by "\e" and sorta looks like a timer.

I'm not sure if anyone else has gotten this or if it's just on my end.

=======

Besides that, here's a fingerprint you may add to the list

LG K20 V

lge/lv517_vzw/lv517:7.0/NRD90U/1906714433ce5:user/release-keys__2019-03-01

Happy days.
[Magisk] Didgeridoohan:
Thanks. It's not just you, I can confirm this visual bug.

Those "\e" codes you're seeing are the colour codes.

https://github.com/Magisk-Modules-R...9dab34a81a60530281d2/system/binpath/props#L58

That text was supposed to have been cyan...

Has no influence on the function of the module, but looks kinda janky. I'll fix.
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 3a=google/sargo/sargo:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 3a XL=google/bonito/bonito:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 4=google/flame/flame:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 4 XL=google/coral/coral:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 4a=google/sunfish/sunfish:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
Pixel 5=google/redfin/redfin:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05
[Magisk] game5413:
Redmi Note 9 Pro ID (10)
[Magisk] Vethy:
Trying to get screen mirroring to work with this on a Sony Xperia, any ideas?
[Magisk] Vethy:
To quote this, I found I'm meant to add these lines instead.

net.tethering.noprovisioning=true

ro.hdmi.enable=true

ro.hdmi.mirror.enable=true

persist.debug.wfd.enable=1

persist.adb.notify=0

So I did. But I'm not sure what I'm meant to set the values to, I just set the same same as the prop. Am I dumb?
[Magisk] Vethy:
Yeah I'm dumb, from what I can gather you need to set the values to 1.

Edit: sorted! Thanks @Didgeridoohan
[Magisk] Didgeridoohan:
@Vethy it sounds like you're figuring things out, but just to be sure...

Take net.tethering.noprovisioning=true as an example. When asked for the prop to set you enter net.tethering.noprovisioning, and when asked for the value you enter true.
[Magisk] Vethy:
Oh wow! That makes sense, thankyou!
[Magisk] Vethy:
Hi, sorry to bother you one more time. Just to clarify, these will automatically be added to build.prop when I add the lines and set new values?
[Magisk] Didgeridoohan:
Not quite... The new value you set well be used(once you've rebooted), but the build.prop file is never touched. Details:

https://github.com/Magisk-Modules-R...uildprop-doesnt-change-after-using-the-module
[Magisk] Vethy:
Understood. Thankyou :)
[Magisk] Dhaval Bhramkhatri:
Hey what happens if I send device fingerprint from an rooted and unlocked boot loader From an Realme XT can it will still be considered or I have to send from an unrooted and locked bootloader device.
[Magisk] ipdev:
Root access and an unlocked bootloader will not modify the fingerprint.

If it is a certified device, the fingerprint and matching security date are still valid. ;)

Cheers. :cowboy:
[Magisk] sirakuma:
Here's the fingerprint of sony xperia 1 mk2 dual with latest android 11 firmware

# Sony Xperia 1 II XQ-AT52 XQ-AT52
#
# ro.bootimage.build.fingerprint=Sony/XQ-AT52/XQ-AT52:11/58.1.A.5.222A/058001A0050222A2046423728:user/release-keys
# ro.build.version.security_patch=2021-05-01
#
# ro.build.version.release=11
# ro.build.version.release_or_codename=11
# ro.build.version.sdk=30
# ro.product.device=XQ-AT52
# ro.product.brand=Sony
# ro.product.manufacturer=Sony
# ro.product.model=XQ-AT52
# ro.product.name=XQ-AT52
[Magisk] Didgeridoohan:
Some might be wondering why there hasn't been an update to the fingerprints list even though a whole bunch of prints have been submitted in the past couple of weeks.

Long story short: very busy and mainly been mobile (no fun to do these updates on a phone).

I'm hoping to get an opportunity to get an update out this weekend.
[Magisk] Didgeridoohan:
Fingerprints list updated to v129

So, there it is... June is almost over and I finally had an opportunity to test and update all the provided prints.

Thank you @CHT45, @Displax, @NOS_bzone, @Kapiljhajhria, @mario0318, @nomeyamo and @game5413 for your help and contributions.

New

LG K20 V

Redmi Note 9 Pro India

Samsung Galaxy S21

Xiaomi Mi Mix 3 5G Europe

Updated

Google Pixel 3-5 (all variants)

OnePlus 7T (1901 & 1905)

Xiaomi Mi A2
[Magisk] TheKerevas:
How can I help? I want to update the Fingerprint of the POCO F2 Pro from Android 10 to Android 11. The data you need is extracted from the ROM, is there a guide?
[Magisk] Creative_Ingenuity:
I'm on a OP9 pro LE2125 and I just updated the module in Magisk. Rebooted and now Google store and Google play services keep crashing. I unhid them and rehid them and I rebooted and they are still crashing. I run safety net and it just keeps me waiting for a response. I'm pretty sure I'm doing something wrong as this update is my first one since installing it. I also went to terminal got SU permission and went to props to see if OP9 had been listed under certified fingerprints and still don't see it. Again this is all probably do to something I'm doing wrong or not doing at all. Any help would be much appreciated
[Magisk] Creative_Ingenuity:
I created a log but I want to make sure I post the correct one. If this is not it please let me know. I was using one plus 8T pro fingerprint before updating module. Again hope what I attached was thr correct log

Fixed it had to rerun safetynet zip again
[Magisk] ipdev:
Hi. :)

From the OP.

Notice the color difference, that is a link. ;)

MHPC Documentation - GitHub - Link

These sections might be of interest to you.

- Please add support for device X - GitHub - Link

- Finding a certified fingerprint - GitHub - Link

- Matching the Android security patch date - GitHub - Link

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

Cheers. :cowboy:​
[Magisk] Some_Random_Username:
Hi folks, it's been a long time since I posted in this thread, I took some time for myself.

Below are latest fingerprints currently available for OnePlus devices, hopefully I got everything right.

As always, OnePlus/OnePlus7/ fingerprint is for GM1901 and GM1905 / OnePlus/OnePlus7Pro/ fingerprint is for GM1911 and GM1917 / OnePlus/OnePlus7TPro/ fingerprint is for HD1911 and HD1917.

Updated fingerprints:

Spoiler content hidden.

New fingerprints for devices already in list:

Spoiler content hidden.

New fingerprints for devices not already in list:

Spoiler content hidden.
[Magisk] Dhaval Bhramkhatri:
How to check if devices is certified do we check in play store in certificate tab or any other method to check.
[Magisk] illusiveairforce:
So I got a question. If your a gamer or know anything about it you might be able to help.

So PuBG Mobile has some devices that are eligible to run 90FPS(Frames Per Second)

Im on a OnePlus 9 5G

Will these props be able to trick the app to think im a OnePlus 8 or 7T Pro in order to have the 90fps button in the settings on PuBG Mobile visible?
[Magisk] f2bacon:
Hi! I think you saw my forum post trying to get my build.prop edited. I just wanna change my build.prop to have info as if it were a galaxy s8.

I've tried using 2 build.prop apps and it either says I'm not rooted, or if it does let me edit, the phone stops being able to boot past the bootloader unlocked screen. I tried editing the file using file managers and it usually tells me it has read/write permission issues, or file permission issues.

Lastly I tried magiskhide props and it seemed promising because I could use the galaxy s8 fingerprint, but if I check my build.prop it didn't change (because that's not what it does, duh). So I went for broke and tried to enable device simulation and individually enabled all the options, but now it won't boot past the bootlogo. Did android 11 completely kill build.prop editing?

EDIT: new problem. so i typically just reflash everything in rominstaller and just skip factory reset, so i can get right back to where i was. then i flash my magisk modified boot.img so i can have root again. but now if i'm rooted and magisk can work, it won't boot past the boot logo. if i don't have root i can't temporarily remove the props config module. looks like i gotta factory reset this time
[Magisk] Didgeridoohan:
@f2bacon You have a few of options to try before doing a factory reset:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] Didgeridoohan:
It's possible, but I can't say for sure... Give it a shot. If you encounter issues you should be able to revert the changes, even if you can't boot properly (see the link in the list above).
[Magisk] f2bacon:
Thank you. That should save me the time of a factory reset but what should I be doing to get this working correctly? Is build.prop editing just done for?
[Magisk] f2bacon:
is there a way to remove this module without root? ive been struggling for the past hour and a half. it wouldve been faster just to reset. if i flash the magisk boot.img it enables magisk and therefor the phone wont boot past the bootlogo. i cant put the disabler files in the root directory cause i cant access the root directory
[Magisk] ipdev:
If the stock/factory rom includes Google Services, the device should be certified.

If PlayStore shows Certified, it is a certified build.

If SafetyNet is broken, PlayStore will not be certified even if it is a valid print and date.​

---

You can also check Google's list.

Public Supported Devices - WebSite - Link

It is a big webpage, 32,935 devices as of this post, so loading will depend on you hardware and connection speed.​

Keep in mind, the device might be certified but the build might not be.

Manufacture have to register each certified build with Google.

- If they have regional builds, some might not be certified while the others are.

- Test/Beta builds are often not registered.​

Cheers. :cowboy:
[Magisk] game5413:
Sorry, I made a mistake naming on my post which caused a misunderstanding, my device is Redmi Note 9 Pro in Indonesia 😅
[Magisk] Didgeridoohan:
Not the root directory, the "root of your internal storage (/sdcard)". That's perfectly accessible without root...

Prop editing is in many cases restricted to the systemless kind on later Android versions. In your case I would just not edit all the props you enabled in the device simulation menu, only the ones you need.
[Magisk] Didgeridoohan:
Now that you mention it, that makes sense.India is "IN", not "ID"... Haven't had any Indonesia prints before.

I've renamed the print, but I won't make another "release" just now since the actual print is still the same. Just run another list update is you want the menu to reflect the correct location.
[Magisk] f2bacon:
putting the reset and disable files in the root of my storage didnt do anything. i was trying all night.

and that's exactly what i was scared of. i thought it was the custom roms fault but every step i go it's not anyones fault so i sorta figured android killed support for it. idk how it worked on android 10 with my 7 pro that was systemlessly rooted. i guess the changed happened between 10 and 11
[Magisk] Didgeridoohan:
Have you tried booting to Safe Mode or using the Magisk adb command to remove modules, as described in the Magisk troubleshooting guide (linked in the module docs)?
[Magisk] TheKerevas:
I have read but I don't understand how to do it, see if I can :(
[Magisk] sdeft:
Are all Pixel 4x using same fingerprint with Pixel 5 model now or is this a typo ?

I am asking as before I was using coral fingeprint on my Xiaomi and now device is recognized as Pixel 5 device.
[Magisk] Didgeridoohan:
If there's something about the instructions you find unclear or anything you wonder about, please do not hesitate to ask.
[Magisk] Didgeridoohan:
Not sure what you mean by typo... All those fingerprints in the post you quoted are different.
[Magisk] Dhaval Bhramkhatri:
Fingerprint for Realme XT RMX1921

Kindly check if this passes safety net and if yes then update in the list

[ro.system.build.date]: [Tue May 18 21:14:41 CST 2021]

[ro.system.build.date.utc]: [1621343681]

[ro.system.build.fingerprint]: [realme/RMX1921/RMX1921:10/QKQ1.190918.001/1619577165:user/release-keys]

[ro.system.build.id]: [QKQ1.190918.001]

[ro.system.build.tags]: [release-keys]

[ro.system.build.type]: [user]

[ro.system.build.version.incremental]: [1619577165]

[ro.system.build.version.release]: [10]

[ro.system.build.version.sdk]: [29]

[ro.telephony.call_ring.multiple]: [false]

[ro.telephony.default_network]: [9,0]

[ro.telephony.iwlan_operation_mode]: [legacy]

[ro.test0]: [0]

[ro.treble.enabled]: [true]

[ro.vendor.build.date]: [Tue May 18 21:14:41 CST 2021]

[ro.vendor.build.date.utc]: [1621343681]

[ro.vendor.build.fingerprint]: [realme/RMX1921/RMX1921:10/QKQ1.190918.001/1619577165:user/release-keys]

[ro.vendor.build.security_patch]: [2021-05-05]

[ro.vendor.oppo.fingerprint]: [realme/RMX1921/RMX1921:10/QKQ1.190918.001/1619577165:user/release-keys]

[ro.vendor.oppo.product.brand]: [realme]

[ro.vendor.oppo.product.device]: [RMX1921]

[ro.vendor.oppo.product.incremental]: [1619577165]

[ro.vendor.oppo.product.manufacturer]: [realme]

[ro.vendor.oppo.product.model]: [RMX1921]

[ro.vendor.oppo.product.name]: [RMX1921]
[Magisk] ipdev:
You picked a good one to try first. 🙃

Xiaomi is confusing by itself.​

Let alone a combined build also. ;)​

Poco F2 Pro is a shared/combined build of Redmi K30 Pro.

The build is defaulted to Redmi.

Somewhere in the install process, it is changed to Poco.

They are both registered/certified as "lmi"

POCO POCO F2 Pro lmi POCO F2 Pro
Redmi K30 PRO lmi Redmi K30 Pro

This is how I would go about it for most Xiaomi devices.

Xiaomi releases the recovery (OTA) updates first.

Fastboot updates follow (some times weeks) later.

For most Xiaomi devices, I would unpack the recovery image file.

The fastboot update will include recovery.img, the recovery update will not.

I use osm0sis's AIK for unpacking boot and recovery image files.

[TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac] - xda Thread - Link

In the ramdisk directory of the unpacked image, there will be a default.prop or prop.default file.

This file will have the props that you are looking for. ;)

If the fastboot update is not available, and you are not running the update, you should be able to grab the fingerprint and date from the recovery update.

Unzip META-INF/com/android/metadata from the recovery update and look for "post" print and security patch.

The metadata file is a text file, you should see something like this.

post-build=Redmi/lmi/lmi:10/QKQ1.191117.002/V12.0.4.0.QJKMIXM:user/release-keys
post-security-patch-level=2020-09-01

---

To modify/correct the fingerprint:

Change

Redmi/lmi/lmi:

To

POCO/lmi_global/lmi:

Hopefully that works. ;)

Now that I think of it, I do not think the default Redmi print worked.?

Maybe we need to change that to global also ??

Redmi/lmi_global/lmi:

I will have time this weekend to test and update my Poco F2 Pro. ;)

Hope it helps more than confuse. :)

Cheers. :cowboy:

PS.

I have not looked into ASUS lately but, they did something similar.

They used a combined/generic build on some (mostly older) devices.

The fingerprint had to be modified for the device.
[Magisk] sdeft:
Pixel 4 XL=google/coral/coral:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05

Pixel 4a=google/sunfish/sunfish:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05

Pixel 4a (5G)=google/bramble/bramble:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05

Pixel 5=google/redfin/redfin:11/RQ3A.210605.005/7349499:user/release-keys__2021-06-05

If you see all above use the same RQ3A.210605.005/7349499. Only difference is the device name. So maybe something changed from Google side. As I wrote earlier I used the coral entry but device was detected as Pixel 5 (redfin).
[Magisk] Didgeridoohan:
That's just the build info, and since the build is basically the same for all those devices it'll be the same...

I can't say anything about why your device was detected as a redfin without seeing the module logs from when you applied that print.
[Magisk] Stremon:
Hey guys,

After updating the fingerprint of my phone with props in su (and rebooting), I still get a ctsProfile failure in Magisk.

My phone is a Pixel 3, on the latest lineageos 18.1.

I'm not sure, but maybe if I'm missing something here?
[Magisk] Stremon:
Thanks a lot for your fast answer!

Indeed the universal safetynet fix module was what I was missing, now it does work!

That's amazing stuff, outstanding work here (y)
[Magisk] sdeft:
ok clear. One more thing. When changing fingerpint with MagiskHide (+reboot) do I also need to clear GooglePlay ?
[Magisk] handy1977:
My s9 plus shows the device is not certified. Android 10 stock from sammy site. I am also struggling to get cts to pass it has failed. Anyway to fix this. My phone is rooted and had stock rom from sammobile website
[Magisk] b0l5:
same here with my OnePlus 8 pro Eu.

MagiskHide install and setup + Universal Seftynet Fix
[Magisk] Didgeridoohan:
https://xdaforums.com/t/module-magi...p-edits-and-more-v5-4-0.3789228/post-85227937
[Magisk] Didgeridoohan:
Both of those modules deal with the CTS profile. You're also failing basic integrity...

My first two guesses would be that MagiskHide needs to be enabled or possibly toggled off and on again, or you've got EdXposed or similar installed that's triggering SafetyNet.
[Magisk] b0l5:
you have right. I turn off Edxposed and works grat! Thanks
[Magisk] Lord Sithek:
EdXposed latest reportedly breaking SafetyNet, plus it's not actively developing. Try LSPosed, SafetyNet passes fine for me
[Magisk] Last_SiN:
Mi8 Explorer Edition, manualy tested and working props.

Xiaomi Mi 8 Explorer (10):Xiaomi:Mi 8 Explorer=Xiaomi/ursa/ursa:10/QKQ1.190828.002/V12.0.5.0.QEHCNXM:user/release-keys__2020-12-01
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 3a=google/sargo/sargo:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 3a XL=google/bonito/bonito:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 4=google/flame/flame:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 4 XL=google/coral/coral:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 4a=google/sunfish/sunfish:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05
Pixel 5=google/redfin/redfin:11/RQ3A.210705.001/7380771:user/release-keys__2021-07-05

Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.11.0.RFQMIXM:user/release-keys__2021-06-05

Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.27.0.QDIMIXM:user/release-keys__2021-06-01

Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.20.0.QDLMIXM:user/release-keys__2021-06-01
[Magisk] rahmanjunior:
I hope someone can help me, I tried device simulation with MagiskHideProps and now it's on a bootloop

How do I reset Props values from TWRP?
[Magisk] rodken:
Try the Magisk Module Disabler.
[Magisk] Didgeridoohan:
There are built-in features in the module to help with that kind of situation, and it's also quite easy to fix from TWRP.

It's all described in the docs:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] Displax:
Nvidia update:

NVIDIA/foster_e/foster:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05
NVIDIA/foster_e_hdd/foster:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05
NVIDIA/darcy/darcy:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05
NVIDIA/sif/sif:9/PPR1.180610.011/4079180_2740.7538:user/release-keys__2021-04-05
NVIDIA/mdarcy/mdarcy:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05
[Magisk] GtrCraft:
Time for some POCO's to be updated:

POCO X3 (NFC) Global:

POCO/surya_global/surya:11/RKQ1.200826.002/V12.0.1.0.RJGMIXM:user/release-keys

2021-05-01

POCO F3 Global:

POCO/alioth_global/alioth:11/RKQ1.200826.002/V12.5.1.0.RKHMIXM:user/release-keys

2021-03-01

POCO X3 NFC Europe can be removed. I will only follow global releases
[Magisk] BlackSoulxxx:
Some Redmi/Poco update:

+Poco F2 Pro Global:

POCO/lmi_global/lmi:11/RKQ1.200826.002/V12.5.1.0.RJKMIXM:user/release-keys__2021-06-01

Source: https://dumps.tadiphone.dev/dumps/r...826.002-V12.5.1.0.RJKMIXM-release-keys/vendor