• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v5.4.0

Search This thread

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,718
12,690
Gothenburg
Google Nexus 4
Nexus 6
Yeah I'm a bit wary of letting it ever boot up with attestation module disabled right now because:
- The moment that happens, Google Pay notices and saves something in the Google Play Services data that makes it distrust the phone
- Last time to fix that I had to clear Google Play Services data
- Doing so also wiped the device's COVID tracing data (for Canadian COVID Alert app) and I don't want that to happen again for public health reasons

(for next time, any idea how I might selectively clear only the part of GP Services data that matters, without clearing the COVID data?)
(also any idea how to browse for the downloaded OTA and inspect it?)

I've never used Google Pay, so that's not something I can help with.

Sounds like downloading the OTA file and sideloading it is the safest and easiest option.
 

dimm0k

Senior Member
Jan 25, 2014
1,535
593
Google Pixel 4 XL
---------- Post added at 01:36 AM ---------- Previous post was at 01:06 AM ----------

[/COLOR]
Disable the hardware off module.
You may need to reboot after disabling the module before setting it in MHPC.
I am not sure if needed.


Use the Force BASIC key attestation option in this module.
Follow the prompts and select Pixel 4 as the device to use.
Not the 4 XL. It has to be a different device, not the same as you are using.

Reboot and check SafetyNet.
If it passes then see if it fixes your fingerprint sensor issues.

Good luck.

Cheers. :cowboy:

This worked like a charm! Luckily I had the hardware off module already disabled so I only had to force BASIC key like you said to a Pixel 4. Now both SafetyNet and biometrics work again! Thank you! also thank you to @Didgeridoohan for this module to simplify all of this!
 

pndwal

Senior Member
Sorry, missed 'same OEM' test bit...
So yes.
I can use a Pixel 4 (4XL) and I get BASIC test on my Pixel 4a.
The only way to get HARDWARE test back on my 4a was to use the prop setting for 4a. (actual device)
Fantallytastic! (For many reasons).
@ zgfg
Good point and yes I do.
I reset MHPC in between testing and make sure I get HARDWARE test and fail SafetyNet.
Just to make sure I am not dragging any change along for the ride....
So Controlled Experiment. :good:
I can get HARDWARE test on my Pixel 3aXL if I use full device simulation and choose Pixel 4 or 4XL
This obviously fails SafetyNet since it uses hardware.
That's the interesting part... And blows my last theory...
Not sure where this is taking me but, using full device simulation changes enough to get HARDWARE test.
So bootloader version and board name do not seem to affect it because they are still bonito (3a XL) values. ?
Yep. Still seems to me SN is checking model prop(s) against something, but now it seems to be other props!

Unless I'm wrong again, SN is checking for (at least) two matching Hardware TEE device props on a device to use Hardware Attestation.

Seems Force Basic using different Hardware TEE device model selected works because SafetyNet returns mismatched values and defaults to Basic Attestation.

Also, now seems Force Basic using ANY incorrect value actually works for the same reason: the model prop value does not now MATCH other Hardware TEE device prop(s), causing default to Basic Attestation.

Conversely on a device [at least, one with Hardware TEE] not yet flagged by Google to use Hardware Backed Attestation, Full Device Simulation of a Flagged Hardware TEE device 'forces' Hardware Backed Attestation because SafetyNet is now returning matching props for Hardware TEE device.
Running full simulation using Pixel 4a on my OnePlus 5T was still BASIC test.
So there must be another part in the chain. :confused:
Agree must be another element here, and there could be several explanations.

[Most obvious is that Hardware TEE implementation is OEM specific. The device props SN looks for may include OEM specific code / values that need to match hardware. (In Pixel 3aXL w/ Pixel 4 test, these WOULD match.) So this failure to launch could be due to a MISMATCH also. You could confirm by simulating Hardware TEE OnePlus device on OnePlus 5T.

Another thing, it was reported when Google initially switched on Hardware Attestation, and switched it off again in short order, that this was due to bad Hardware TEE implementation on devices, specifically OnePlus! Apparently the respite for Hardware Attestation is to allow time for these devices to be 'Fixed'. So could be Hardware Attestation is simply bypassed for OnePlus / your model at the moment.]#

This is all only deduction, so on the question of 'which props', I'd have to have time to study it. PW

#Edit: HaHa, I think @Didgeridoohan
put his finger on this! (Most likely reason; guess the Pixel 3a XL actually has the hardware.):
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/post83656075

---------- Post added at 04:03 PM ---------- Previous post was at 03:32 PM ----------

@ipdev Full on experimental mode... :D Thanks for sharing and really interesting. I just wish I could join in the experimental fun times.

I'm gonna leave the module as it is though. Most users just want to force basic attestation and be done with it. Google is probably changing things in the backend all the time, and the option works as advertised. Power users and tinkerers can set whatever value they find works best.
So can I take that as official? - 'f' stands for 'Full on experimental mode' / 'Fun times for Power Users'! ... Happy with that. :good: :D PW
 
Last edited:

geekopa

Member
Jan 25, 2011
5
1
That print /date combination doesn't pass CTS, so no need for logs.

I tried again and this time it passed. I added these props:

Code:
ro.system.build.fingerprint=Redmi/begonia/begonia:9/PPR1.180610.011/V10.4.1.0.PGGMIXM:user/release-keys
ro.system.build.fingerprint_real=xiaomi/ginkgo/ginkgo:10/QKQ1.200114.002/20.6.17:user/release-keys/1592537410
ro.build.version.security_patch=2019-09-01
ro.build.version.security_patch_real=2020-05-01
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,718
12,690
Gothenburg
Google Nexus 4
Nexus 6
I tried again and this time it passed. I added these props:

Code:
ro.system.build.fingerprint=Redmi/begonia/begonia:9/PPR1.180610.011/V10.4.1.0.PGGMIXM:user/release-keys
ro.system.build.fingerprint_real=xiaomi/ginkgo/ginkgo:10/QKQ1.200114.002/20.6.17:user/release-keys/1592537410
ro.build.version.security_patch=2019-09-01
ro.build.version.security_patch_real=2020-05-01

Could you elaborate on what those "_real" props are? Never seen those before...
 

bartleby999

Senior Member
Jan 5, 2015
329
132
So, I'm experiencing a weird issue - When module is active I can pass CTS but some YouTube videos only show in 480p - Disabling the module allows me to stream 1080p, enabling again only allows 480p.

Anyone else had this issue or know any reason it could be going wrong?
 

pndwal

Senior Member
So, I'm experiencing a weird issue - When module is active I can pass CTS but some YouTube videos only show in 480p - Disabling the module allows me to stream 1080p, enabling again only allows 480p.

Anyone else had this issue or know any reason it could be going wrong?
What settings used in MHPC? What device? What ROM? PW
 

bartleby999

Senior Member
Jan 5, 2015
329
132
What settings used in MHPC? What device? What ROM? PW

My bad.
Stock rom on Galaxy Tab S6 (SMT860). I only used the Force Basic Key Attestation option and even then, selected my own device model.

::Edit:: No, I'm an idiot - I didn't use my own device (because of course I couldn't I'm failing so it why would spoofing my own device work) I used SM-A300FU which I'm guessing is a lower spec device. That'll teach me for not paying attention.

Still, it's weird that it's only some YouTube videos that are effected. I'm guessing because HDR is not available on SM-A300FU so youtube doesn't show that option? I'll try a newer Samsung witha spec closer to mine.

::Edit 2:: So, yeah - Using a device much closer to mine (TabS5e) returns HDR support in YouTube.

So it's been an annoying 12 hours (which I thoroughly deserve for not reading prompts correctly), but CTS is passed & I've finally restored HDR support.
 
Last edited:

pndwal

Senior Member
My bad.
Stock rom on Galaxy Tab S6 (SMT860). I only used the Force Basic Key Attestation option and even then, selected my own device model.

::Edit:: No, I'm an idiot - I didn't use my own device (because of course I couldn't I'm failing so it why would spoofing my own device work) I used SM-A300FU which I'm guessing is a lower spec device. That'll teach me for not paying attention.

Still, it's weird that it's only some YouTube videos that are effected. I'm guessing because HDR is not available on SM-A300FU so youtube doesn't show that option? I'll try a newer Samsung witha spec closer to mine.

::Edit 2:: So, yeah - Using a device much closer to mine (TabS5e) returns HDR support in YouTube.

So it's been an annoying 12 hours (which I thoroughly deserve for not reading prompts correctly), but CTS is passed & I've finally restored HDR support.
Well done, and that explains it.

I'm not sure how YouTube streaming works, but It appears from this that some options offered (HD video, etc) depend on device capability (ie. CPU, GPU specs) which are determined using model prop(s).

@ipdevs recent discovery that it's not only models using Basic Attestation (usually older, with more limited functionality) that will cause a default to Basic, as we had assumed, may interest you. You can actually choose ANY value not matching actual model because, as is now clear, it's simply the mismatch that makes Force Basic function in MHPC work.
Tested on my Pixel 4a and Poco F2 Pro since they are Hardware attest.
Sure enough, I could select anything besides the actual device.

So yes.
I can use a Pixel 4 (4XL) and I get BASIC test on my Pixel 4a.
The only way to get HARDWARE test back on my 4a was to use the prop setting for 4a. (actual device)
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/post83654739

What this means for you is that, if you wish (eg in the event you find other device specific functions broken), manually choosing a later device should 'Force Basic'. You could try Tab S7, and is should work (likely giving even better / more up-to-the-minute device specific functionality, apps etc) as even a later model won't match.

Hope it helps, PW
 
Last edited:

bartleby999

Senior Member
Jan 5, 2015
329
132
I'm not sure how YouTube streaming works, but It appears from this that some options offered (HD video, etc) depend on device capability (ie. CPU, GPU specs) which are determined using model prop(s).

I though it was blocking anything over 480p on some videos, some videos were showing up as 1080p - it turns out that it was actually blocking were all HDR videos. That was certainly the confusing aspect as I didn't know they were HDR, just that they should be 1080p.

So yeah I'm guessing at very least YouTube uses your props to check your model is capable of HDR.

Anyway, what you've added certainly does help, I'll keep that in mind for the future - So Thanks.
 

zgfg

Senior Member
Oct 10, 2016
5,493
2,835
I though it was blocking anything over 480p on some videos, some videos were showing up as 1080p - it turns out that it was actually blocking were all HDR videos. That was certainly the confusing aspect as I didn't know they were HDR, just that they should be 1080p.

So yeah I'm guessing at very least YouTube uses your props to check your model is capable of HDR.

Anyway, what you've added certainly does help, I'll keep that in mind for the future - So Thanks.
On Xiaomi Mi 9T, MIUI 12 eea, Android 10, even with a gibberish like ro.product.model = "undefined", YT Vanced root 15.38.35, playing 8K HDR 10+ videos, by default in 1060p
 

Attachments

  • IMG_20201008_225548.jpg
    IMG_20201008_225548.jpg
    174.1 KB · Views: 175
  • Screenshot_2020-10-08-23-04-38-297_com.vanced.manager.jpg
    Screenshot_2020-10-08-23-04-38-297_com.vanced.manager.jpg
    249.2 KB · Views: 173
  • YT_8K_HDR-1060p.jpg
    YT_8K_HDR-1060p.jpg
    155.9 KB · Views: 165
  • YT_8K_HDR10plus-1060p.jpg
    YT_8K_HDR10plus-1060p.jpg
    108.9 KB · Views: 168
Last edited:

bartleby999

Senior Member
Jan 5, 2015
329
132
On Xiaomi Mi 9T, MIUI 12 eea, Android 10, even with a gibberish like ro.product.model = "undefined", YT Vanced root 15.38.35, playing 8K HDR 10+ videos, by default in 1060p

I don't know what to say man. I'm running Vanced too, Android 9, TabS6 - Having the Props set to SM-A300FU meant no HDR. HDR was available without it and available with S5e. Come up with your own conclusion? :confused:
 

pndwal

Senior Member
On Xiaomi Mi 9T, MIUI 12 eea, Android 10, even with a gibberish like ro.product.model = "undefined", YT Vanced root 15.38.35, playing 8K HDR 10+ videos, by default in 1060p
You are changing only that one prop only, right? Whereas MHPC Force Basic changes all model props.

I don't know what to say man. I'm running Vanced too, Android 9, TabS6 - Having the Props set to SM-A300FU meant no HDR. HDR was available without it and available with S5e. Come up with your own conclusion? :confused:
This may be another way to get back HD YouTube, etc.

I think it doesn't work on all devices, but you could use MagiskHide Props Config to change just ro.product.model prop (to anything, "unidentified_flying_object if you like") instead of using Force Basic function (which changes several model props), to see if this is all you need to 'force' Basic Attestation.

If it does, likely you will also have HD in YouTube as this seems to be looking at a DIFFERENT model prop to determine device capability, and this being unchanged, YouTube will be seeing your actual model.

Also, if that works, I'd still be using a real model for the changed prop, not just 'unidentified' etc, and I'd now be making that a newer device from the same OEM and series (as discussed already) in order for apps that look at this prop to have the best chance to work. PW
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,718
12,690
Gothenburg
Google Nexus 4
Nexus 6
This may be another way to get back HD YouTube, etc.

I think it doesn't work on all devices, but you could use MagiskHide Props Config to change just ro.product.model prop (to anything, "unidentified_flying_object if you like") instead of using Force Basic function (which changes several model props), to see if this is all you need to 'force' Basic Attestation.

If it does, likely you will also have HD in YouTube as this seems to be looking at a DIFFERENT model prop to determine device capability, and this being unchanged, YouTube will be seeing your actual model.

Also, if that works, I'd still be using a real model for the changed prop, not just 'unidentified' etc, and I'd now be making that a newer device from the same OEM and series (as discussed already) in order for apps that look at this prop to have the best chance to work. PW

@bartleby999 If you're going to be testing this, I would also be curious what happens if you use the "Custom value" option for the "Force BASIC key attestation" feature and add a nonsense value.
 

Mirardt

Senior Member
Sep 21, 2020
59
3
The GApps with our phone should be installed by using the preinstalled GetApps app. Like in this video https://www.youtube.com/watch?v=Tz7Vi68kbuU
MIUI is just a skin for Android, it's not a separate OS. It's like OneUI for Samsung. Everything has the capability to work, e.g. I just got my country's COVID-19 Exposure Notifications app working.

What you need is a fingerprint that will let CTS Profile pass. Once that passes then you should be able to use Google Pay. Make sure you've chosen the HCE Wallet option in the NFC settings and given all the permissions required for Google Pay, Play Services Framework, and Google Services Framework.

Ok so I wiped my device completely and tried to use that video of yours to install google services, but still SafetyNet fails. After that, I wiped again and installed every single apk. seperately from apkmirrors and it still failed SafetyNet. So it has nothing to do with my sellers preinstalled apps.

Its very hopeful to read that everything has the capability to work!

Something about those fingerprints and passing CTS Profile doesn't work with my device so I hope maybe @Didgeridoohan can find something out!

@Mirardt I've taken a quick look at your logs and haven't seen anything obvious that might be causing you issues.

I did test your device's fingerprint and it passes CTS, so it's certified. Which is funny, since your device doesn't come when GApps preinstalled... Why bother certifying it, if you're not gonna use it? I guess they might be reusing the fingerprint.

I have a faint memory of a similar situation, and I did search around a bit but couldn't find anything. Once I'm not busy like hell I'll try to look closer...

@zgfg

But if you are not using any app that complains about SafetyNet, why should you bother, have the GApps, Magisk, enjoy

Ofc, you would not be able to use GPay, but I doubt that even if you trick the SafetyNet to pass, that your Chinese firmware is not ready for GPay by NFC, and that you could never make it work

Wait what? That could happen? I always thought that the second I pass SafetyNet I can use it for sure.


Let's do it quick and dirty. Use some root file explorer - advising you to install MiXPlorer. Grant it root and go to Root, then navigate to /data/adb/modules/MagiskHidePropsConf

Find the system prop file in that folder.
Make it there a backup copy system.bak, and don't touch the rest

Open system.prop as a text file - MiXPlorer can do everything for you.
Lines starting with # are comments, they don't count.
Over the rest of the lines, paste the following stuff:

ro.product.model=davinci
ro.build.fingerprint=Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002
ro.build.version.security_patch=2020-07-01

Reboot and getprop those three props (they have to return those values you pasted to the file), and check your SafetyNet

Once you are done, revert system.bak to system.prop, reboot and erase from your memory any reminisce about that back-door to MHPC?

Ok that was easy enough. Memory erased!

Props show what they should but Safety Net still doesn't pass. .

With that new Magisk Manager, SafetyNet test will show you visually if CTS Profile attestation used Basic or Hardware mode (so no need for analyzing the logcat anymorey).
If it uses Basic (passing CTS or not), then further playing with Forcing CTS to Basic makes no sense - then something else brakes your CTS

Brw, @Didgeridoohan and me independently tested with your stock fingerprint and got it passing the SafetyNet.
Hence there must be something else causing you to fail, like that GApps you had to install to that Chinese firmware

Ok yeah it uses Basic. Thats all super weird, because like I wrote above, I wiped the system and installed google apks. from apkmirror and over an installer.

If its the firmware, is there no way to hide that to google?

Could that also be the reason that Wifi Calling isn't working?

Also, I found a ROM, could it be able to help? It uses EdXposed though and as I understand it, that cannot be hidden so my banking apps will never work with that, correct?

Thanks :)

link: http://bbs.ydss.cn/thread-1500533-1-1.html

translation:
HTML:
Redmi K30 Ultra_V12.0.12.0-MIUI12-Stable Version-Advanced Settings-Improve Smoothness-Desktop Clock-V4 Dolby-Holidays






Some machines have built-in Magisk and cannot flash magisk, please download and flash by yourself: https://cloud.189.cn/t/nueeIn2mYRVf



Reminder: A small part of the advanced settings can only be used with the corresponding model, such as refresh rate (mind not to brush)
Modified with a new mounting method, without destroying any permissions of the official package, and more stable



EdXposed frame download address: https://loud.189.cn/t/Njuqy2vEvea2 (the dynamic partition machine is flashed with Magisk)



Based on the latest MIUI12 stable version production, pure and no promotion
Update Magisk 21.0 (the mask will only appear after rebooting after flashing)
Update Magisk 21.0 more complete removal verification and better support for EdXposed
A more comprehensive cracking framework
The new version of advanced settings is more smooth
Add double-row status bar mode selection
Add time size customization of status bar
Add drop-down tiles left or right or change
Add desktop search customization
Add a small white bar to show and hide custom
Add charging animation selection (original version, Mi 10, Alpha)
Add boot fingerprint unlock customization
Add one-click blocking ads
System push customization
Hide ROOT
Repair excessive animation is invalid (thanks to the machine friend for reminding)
Fix the list animation is invalid (thanks to the reminder)
Repair list interpolation is invalid (thanks to the machine friend for reminding)
Remove official Kami verificationRemove dm, avb verification
Add core crack
Remove the upper display
Kernel tolerance
Built-in 21.0 version mask
Update advanced settings
Advanced settings update content
Add custom status bar clock size
Customize the height, thickness and length of small white bars
The notification panel shows the weather
Add the function of freely modifying the number of steps on a negative screen of Xiaomi
Hidden HD function moved and classified into the status bar icon function
Status bar icons add hidden no sim card, permission reminder, do not disturb mode, push notification and other icons
Add a variety of transition animation effects,
Add advanced power to support official, extended and secondary extended switching (default official)
Added enable and disable official system update switch
Add multiple fingerprint effects switching
The status bar layout switch does not need to restart the ui, it takes effect immediately, and adds the time centered signal to the right layout
Add the status bar clock always display function
Add native notification icon and color switch in status bar
Added status bar battery square and capsule icon switch
Add desktop search box switch, desktop icon shadow switch, auto close folder, desktop navigation bottom bar font display switch, desktop multiple quick layout switching
Add the fingerprint unlock function and switch directly after restart
Add list animation list interpolation function
Add linear battery and custom width color
Add functions such as a custom interface
Add network type in status bar, support default 4G 4G+ 5G 5G+ LTE LTE+ hidden switch
Add call flashing, application notification flashing can customize the frequency of flashing times,
Add camera advanced settings switch
Add Google Camera, Dolby Viper dual sound effects
Added status bar time year, month, day and second display
Double row network speed, double row signal switching
Status bar style layout switch (support official and time centered network speed left and right switch),
Single and dual card switching in status bar (dual card and hidden card one card two)
Drop down the weather, drop down the lunar calendar, custom DPI, self
Define the resolution, customize the status bar,
Customize the desktop layout, double-click and hold the status bar desktop shortcut actions, gestures and other functions
Added invisible button function in status bar,
One-key flashing function
For more functions, please see the picture, or brush into the experience by yourself
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,718
12,690
Gothenburg
Google Nexus 4
Nexus 6
@Mirardt It is perfectly possible that you can't pass CTS on that particular firmware, no matter what you do. Getting help from someone that has the device and know more about it would be ideal though...

If you really do need to pass CTS I guess you have nothing to loose by trying different ROMs (if available). If the ROM you've linked comes with EdXposed preinstalled that would be unfortunate (why would they do that?). You sure it is though, since in that translation I only see a (broken) download link to EdXposed.
 

zgfg

Senior Member
Oct 10, 2016
5,493
2,835
You are changing only that one prop only, right? Whereas MHPC Force Basic changes all model props.
Yes, only that one and from the beginning (from the time of the fist HardawareOff and experimenting with its system.prop file)
For my Mi 9T it was enough and before MHPC was extended with, couple of other Xiaomi stock firmware users confirmed for other Mi 9 line models that it was enough

However, since MHCP was extended, it was easier to advice people to read about and use there

Also, now when G relaxed with Hardware attest, it passes without forcing Basic on some phones, hence it's hard to make conclusions
 

Mirardt

Senior Member
Sep 21, 2020
59
3
@Mirardt It is perfectly possible that you can't pass CTS on that particular firmware, no matter what you do. Getting help from someone that has the device and know more about it would be ideal though...

If you really do need to pass CTS I guess you have nothing to loose by trying different ROMs (if available). If the ROM you've linked comes with EdXposed preinstalled that would be unfortunate (why would they do that?). You sure it is though, since in that translation I only see a (broken) download link to EdXposed.

Oh ok ... I don't think there is anybody in the english speaking community that has the device and tried out a bunch of stuff with it.

I'm not sure. I think I'm just gonna try it out because their seems to not be another out.

Thanks!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Oh man...

    The backlog for submitted fingerprints is just growing and growing. Thank you so much guys for still providing all these prints!

    I've had ridiculous amounts of work in the past few weeks and my testing device has decided to give out on me. I don't test prints on my daily driver, so currently I'm a bit stumped. Hopefully I'll have time to give my old devices some TLC over the next few days and I can get back to business as usual.
    4
    Update S10 series (International, Korea and Europe) to July security patch (sorry for my inactivity in the past months):

    Samsung Galaxy S10e - SM-G970F
    samsung/beyond0ltexx/beyond0:11/RP1A.200720.012/G970FXXSBFUF3:user/release-keys_2021_07_01

    Samsung Galaxy S10e - SM-G970N
    samsung/beyond0lteks/beyond0:11/RP1A.200720.012/G970NKSU6FUF5:user/release-keys_2021_07_01

    Samsung Galaxy S10e - SM-G970F (Europe)
    samsung/beyond0lteeea/beyond0:11/RP1A.200720.012/G970FXXSBFUF3:user/release-keys_2021_07_01


    Samsung Galaxy S10 - SM-G973F
    samsung/beyond1ltexx/beyond1:11/RP1A.200720.012/G973FXXSBFUF3:user/release-keys_2021_07_01

    Samsung Galaxy S10 - SM-G973N
    samsung/beyond1lteks/beyond1:11/RP1A.200720.012/G973NKSU6FUF5:user/release-keys_2021_07_01

    Samsung Galaxy S10 - SM-G973F (Europe)
    samsung/beyond1lteeea/beyond1:11/RP1A.200720.012/G973FXXSBFUF3:user/release-keys_2021_07_01


    Samsung Galaxy S10 Plus - SM-G975F
    samsung/beyond2ltexx/beyond2:11/RP1A.200720.012/G975FXXSBFUF3:user/release-keys_2021_07_01

    Samsung Galaxy S10 Plus - SM-G975N
    samsung/beyond2lteks/beyond2:11/RP1A.200720.012/G975NKSU6FUF5:user/release-keys_2021_07_01

    Samsung Galaxy S10 Plus - SM-G975F (Europe)
    samsung/beyond2lteeea/beyond2:11/RP1A.200720.012/G975FXXSBFUF3:user/release-keys_2021_07_01


    Samsung Galaxy S10 5G - SM-G977B
    samsung/beyondxxx/beyondx:11/RP1A.200720.012/G977BXXS8FUF3:user/release-keys_2021_07_01

    Samsung Galaxy S10 5G - SM-G977N
    samsung/beyondxks/beyondx:11/RP1A.200720.012/G977NKSU5FUF5:user/release-keys_2021_07_01
    4
    I know I should've searched before posting but there are so many pages I couldn't do it. Sorry.
    Just to make sure, to use a custom fingerprint I have to create a file named printslist (without extensions) on the root of internal storage. Then on that file I simply write the device name + fingerprint?

    Code:
    MotorolaOneAction=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys

    Would this be correct for example?
    Looks to be an Android 10 build so you will need to add the matching security date to the end.
    __YYYY-MM-DD

    Code:
    MotorolaOneAction=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys__YYYY-MM-DD

    The part before the = is what is displayed on the screen when you run the props command and select custom prints list.
    You can space it out if you want.

    Example using the Nexus 6 and 6P.
    The last build for 6 was not new enough to require the matching security date.
    The last build for 6P was so it requires the matching security date.

    Code:
    Google Nexus 6 (7.1.1):Motorola:Nexus 6=google/shamu/shamu:7.1.1/N8I11B/4171878:user/release-keys
    Google Nexus 6P (8.1.0):Huawei:Nexus 6P=google/angler/angler:8.1.0/OPM7.181205.001/5080180:user/release-keys__2018-12-05

    The above example is a little different than the basic MHPC printslist, it includes manufacture and model.
    Motorola made the Nexus 6 and Huawei made the Nexus 6P

    Small tweek to your printslist..
    Code:
    Motorola one action (10):Motorola:motorola one action=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys__YYYY-MM-DD

    The part before the first : is what is displayed on the screen when you run the props command and select custom prints list.
    Note: The Android version is added to the end of the MHPC display name in parentheses (10).

    If you put all the above into a printslist file and run props the custom list would show..
    Code:
    MotorolaOneAction
    Google Nexus 6 (7.1.1)
    Google Nexus 6P (8.1.0)
    Motorola one action (10)

    Note:
    The MHPC display name is cosmetic.
    The part before the equal = using the older (basic) printslist layout.
    The part before the first colon : using the current printslist layout.


    The manufacture, model, build fingerprint and (if required) the matching security date, all need to be correct matching values.

    You can find all this and more in the documentation.
    MHPC Documentation - GitHub - Link
    - Custom fingerprints list - GitHub - Link

    To quote Didgeridoohan.
    If there's something about the instructions you find unclear or anything you wonder about, please do not hesitate to ask.

    Cheers. :cowboy:

    PS.

    I did not see troika_m1 on Google's certified list.
    Only troika and troika_sprout.

    Retail BrandingMarketing NameDeviceModel
    Motorolamotorola one actiontroikamotorola one action
    Motorolamotorola one actiontroika_sproutmotorola one action
    Both models are also motorola one action.
    3
    Nvidia update:
    Code:
    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
    3
    Poco M3 Pro 5G
    M2103K19PG
    MIUI Global
    Regional Indonesia
    Security Update June 1, 2021

    POCO/camellian_p_id/camellian:11/RP1A.200720.011/V12.0.3.0.RKSIDXM:user/release-keys
  • 238
    MagiskHide Props Config v5.4.0
    ctsProfilefalse.jpg

    What's this?
    If you are wondering anything about what this module can do and how it works or if you're experiencing issues of some kind, take a look at the documentation on GitHub and see if whatever you wonder about is covered there (most things are). If they're not, look again and then post in the thread.

    If you're wondering about the latest and greatest after an update, take a look at the changelog and accompanying release notes.

    Prerequisites
    • Magisk v20.4+.

    Installation
    Install through the Magisk Manager Downloads section. Or, download the zip (attached below) and install through the Magisk Manager -> Modules, or from recovery. Combine a recovery installation with the use of the module configuration file and you can set up a certified fingerprint and any custom props you want without first booting on a clean flash. Instant settings.

    Usage
    After installing and rebooting, run the command props in terminal (you can find a terminal emulator on F-Droid or in the Play Store), and then follow the instructions to set your desired options (also see the documentation on GitHub). You might have to call su before running the command.

    You can also run the command with options. Use -h for details.

    Source
    GitHub

    Credits and mentions
    @topjohnwu, for Magisk
    @Zackptg5, @veez21 and @jenslody, for help and inspiration
    @Some_Random_Username for all the OnePlus fingerprints
    @Displax, for all the prints and the basic attestation workaround.
    @ipdev, for being always helpful, bringing tons of fingerprints to the module list and the mHideGP script.
    And of course, everyone that provides fingerprints for me to add to the list. The module wouldn't be the same without you guys. Thank you!

    Previous releases
    Any previous releases can be found on GitHub.

    Releases up until v2.4.0 are compatible with Magisk v15 to v16.7.
    Releases from v2.4.1 are compatible with Magisk v17 to 18.1.
    Releases from v4.0.0 are compatible with Magisk v19+.
    Releases from v5.0.0 are recommended for Magisk v19.4+.
    Releases from v5.2.5 will only install on Magisk v20+.
    Releases from v5.4.0 will only install on Magisk v20.4+.

    The current release is attached below:
    58
    Changelog

    v5.4.0
    Release notes

    v5.3.6
    Release notes
    • Updated the menu item for picking a device manually for the "Force BASIC key attestation" feature to better match the menu option. Press "f" to pay respect.
    • Minor updates to the "Force BASIC key attestation" menus to be more clear and informative (hopefully).
    • Added fingerprints for Nvidia Shield TV 2015, 2015 Pro, 2019 and 2019 Pro, OnePlus 8T (several variants), Redmi Note 8 Pro Global and Xiaomi Mi 10 Lite 5G Global and Mi 10 Ultra. Updated fingerprints for Nvidia Shield TV 2017, OnePlus 6, 6T, 8 (most variants) and 8 Pro (most variants), POCO F2 Pro European, Samsung Galaxy A40 and Note 20 Ultra 5G and Xiaomi Mi 9T Europe and Global, Mi A2, Mi A2 Lite, Pocophone F1 and Redmi Note 8. List updated to v106.

    v5.3.5
    Release notes
    • Fixed issue with partition model props not being set correctly.
    • Make sure that simulating ro.product.model is completely disabled when enabling "Force BASIC key attestation".
    • Removed Android versions from the device list when picking a model for "Force BASIC key attestation".

    v5.3.4
    Release notes
    • Added a module update check option. See the documentation for details.
    • Added `system_ext` to the list of partitions used for certain props (thank you @simonsmh).
    • Fixed an edge case where changing settings after updating the module, but not having rebooted yet would cause issues with system.prop being kept from the previous version.
    • Fixed the -nw run option and made sure that some run options can't be picked together. See the documentation for details.
    • Cleaned up some unused variables.
    • Added print for Sony Xperia 10 II Dual XQ-AU52. Updated fingerprints for Google Pixel 2, 2 XL, 4, 4 XL and 4a, OnePlus 8 IN2015 and 8 Pro In2025 and Xiaomi Mi 10 Global, Mi 10 Pro and Pocophone F1. List updated to v102.

    v5.3.3
    Release notes
    • More (very) minor ui tweaks.
    • Added fingerprint for Samsung Galaxy J7 Neo SM-J701M. Updated fingerprints for OnePlus 8 IN2013, 8 Pro IN2023, Nord AC2001, Nord European AC2003 and Nord Global AC2003 and Samsung Galaxy Tab S5e SM-T720. List updated to v5.
    • There are 10 types of people in the world. Those who understand binary numbers and those who don't.

    v5.3.2
    Release notes
    • Some minor fixes/clarifications in the ui.
    • Added PIXELARITY to the list of modules that also edit device fingerprint.
    • Added fingerprint for Google Pixel 4a, Huawei Mate 9 and P9 EVA-AL10, OnePlus Nord Global AC2003, Samsung Galaxy A7 2018 and Xiaomi Mi 10 European. Updated print for Google Pixel 2-4 (all variants), Oneplus 6, 6T, 7 (several variants), 7 Pro (several variants), 7T (several variants), 7T Pro (several variants), 8 (several variants), 8 Pro (several variants) and OnePlus Nord, POCO F2 Pro, Samsung Galaxy A5 2017 and Xiaomi Mi A1, Mi A2 and Mi 9T European. List updated to v99.

    v5.3.1
    Release notes
    • Added a feature to enable a delay for when custom props to be executed (during the late_start service boot stage). See the documentation for details.
    • Fixed a possibly longstanding bug where props couldn't be set using the ui on some devices (would get stuck on "Working. Please wait...").
    • Fixed some of the settings in an exported settings file not being set correctly.
    • Minor adjustments and bugfixes (mainly stupid bugs introduced in the last update).
    • Added fingerprint for Nokia 6.1, Samsung Galaxy S5, S10 and Tab S4 and Xiaomi Mi 10 Lite 5G. Updated fingerprints for Asus ZenFone Max M1, Google Pixel 2-4 (all variants) and Xiaomi Pocofone F1. List updated to v97.

    v5.3.0
    Release notes
    • Added a new feature to force SafteyNet's bootloader check to use basic attestation rather than hardware. See the documentation for details.
    • Added fingerprints for Asus ZenFone Max Pro M2, Fxtec Pro 1, Huawei Honor 6X BLN-L22, Lenovo Tab 4 8 Plus, LG V30, OnePlus 7, 7 Pro, 7T, 7T Pro, 8 and 8 Pro (Chinese variants), OnePlus Nord, Redmi Note 9 Pro, Samsung Galaxy A3 2016 and 2027 and Galaxy Tab 4 7.0, 8.0 and 10.1 and Xiaomi Redmi K20 Pro India. Updated fingerprints for OnePlus 7 Pro NR and 7 Pro NR Spr, 8 (almost all variants) and 8 Pro (all variants), Redmi Note 8 Pro and Xiaomi Mi A1, Mi A3 and Redmi 8. List updated to v95.

    v5.2.7
    Release notes
    • Added a new run option to set custom props directly from the command prompt. See the documentation for details. Shoutout to @ps000000 @ 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.

    v5.2.6
    Release notes
    • Fixed the supposedly "improved" verbose boot logging.
    • Change to using Magisk's internal Busybox for the `props` script (the boot scripts are already using it without issues and have for some time). Separately installed Busybox no longer needed. Thank you @Juzman for the push.
    • Added info about MagiskHide's status in the "Edit device fingeprint" menu.
    • Added fingerprint for Lenovo Tab 4 10 Plus TB-X704F and TB-X704L, Samsung Galaxy Note 4 SM-N910G and Xiaomi Redmi Note 8. Updated fingerprints for Google Pixel 2-4 XL, Motorola Moto G7 Power, OnePlus 5, 5T, 6, 6T, several variants of 7, 7 Pro, several variants of 7T and 7T Pro and several variants of 8 and 8 Pro, Poco X2, Redmi K30 Pro, Samsung Galaxy A5 2017 and Xiaomi Mi A2, Mi A2 Lite and PocoPhone F1. List updated to v92.

    v5.2.5
    Release notes
    • Fixed and improved verbose boot logging.
    • Fixed collecting logs producing a broken 0-byte file.
    • Logging does not need to use nanoseconds. Microseconds is enough.
    • Added ro.bootmode and ro.boot.mode to "Edit MagiskHide props".
    • Don't use ro.build.selinux in "Edit MagiskHide props" if it isn't set.
    • Added fingerprints for POCO F2 Pro, Redmi K30 Pro Zoom Edition and Note 9S, Samsung Galaxy A20 and Xiaomi Redmi 6 and 6A. Updated fingerprint for OnePlus 5, 5T, 7 Pro (GM1911 and GM1917) several variants of 8 and 8 Pro, Redmi K30 Pro and Xiaomi Mi A1, Mi A3, Redmi 7 and Redmi Note 7. Relabeled Xiaomi Redmi K30 Pro and Redmi Note 8 Pro with Redmi as manufacturer. List updated to v91.

    v5.2.4
    Release notes
    • Added a function for disabling the module by placing a specific file in /sdcard, /data or /cache (see the documentation for details). Useful if there are issues with booting the device after installing/setting up the module.
    • Fixed some issues with setting partition props in other boot stages than default.
    • Fixed an issue with boot scripts clashing if post-fs-data.sh script takes too long.
    • Fixed an issue with settings transfer overwriting the file backup at install.
    • Fixed an issue with log writing that came with the change to using getprop for retreiving prop values.
    • Added fingerprints for Xiaomi Redmi 7. Updated fingerprints for Google Pixel 2-4 (all variants), OnePlus 7 Pro NR, Samsung Galaxy A5 2017 and Xiaomi Pocophone F1. Fingerprints list updated to v80.

    v5.2.3
    Release notes
    • Fixed issue with settings transferring between module updates.
    • Use resetprop only to set values and retrieve values with getprop. For whatever reason some devices have issues with resetprop and this might make the module work on those.
    • Updated fingerprints for OnePlus 6, 6T and 7T Pro NR. Fingerprints list updated to v79.

    v5.2.2
    Release notes
    • Another quick fix taking care of a weird copy-pasta error that broke manufacturer and model simulation.
    v5.2.1
    • Quick fix for broken fingerprints list and settings export.
    v5.2.0
    • Added ro.product.manufacturer and ro.product.model to simulation props.
    • Added an option to also use partition specific versions of simulation props (see the documentation for details).
    • Fixed basic device simulation so that it now only sets props that are already found on the device.
    • Fixed changing MagiskHide sensitive props in late_start service boot stage (see the documentation for details).
    • Updated simulation props editing so that several props can be activated at once (see the documentation for details).
    • Updated MagiskHide sensitive prop editing so that several props can be activated at once (see the documentation for details).
    • Added a new feature to export current module settings to a configuratino file (see the documentation for details).
    • Updated the documentation and added AndroidDumps as a resource for finding certified fingerprints (see the documentation for details).
    • Various under the hood changes and improvements.
    • Added fingerprint for Samsung Galaxy Note 9 and Xiaomi Mi Box S. Updated fingerprints for HTC U12 Plus, Nokia 6.1 Plus and several variants of OnePlus 7, 7 Pro and 7T. List updated to v78.

    v5.1.2
    Release notes
    • Reset current fingerprint if disabling fingerprint modification because of a conflicting module.
    • Fixed using the configuration file in /sdcard during boot on FBE encrypted devices.
    • Added fingerprint for Huawei P20 (L09 single SIM), Motorola Moto G7 Power, Samsung Galaxy Core Prime and Xiaomi Mi 9 SE. Updated fingerprint for OnePlus 7 Pro NR and Razer Phone 2. List updated to v73.

    v5.1.1
    Release notes
    • Updated the module to conform with the current module installation setup.
    • Minor updates.
    • Added fingerprint for Samsung Galaxy Note 10 Plus and Xiaomi Mi 9T (Global version). Updated fingerprints for Essential PH-1, Google Pixel 2-4 (all variants), Oneplus 5, 5T and 6T, Xiaomi Mi 9T (European version), Mi Mix 2 and Redmi Note 4/4x. Fingerprints list updated to v72.

    v5.1.0
    Release notes
    • Fixed issue caused by some devices toybox commands not working as expected.
    • Cleaned up the post-fs-data script to remove unnecessary strain from the boot process. Moved as much as possible to the late_start service boot script instead. Among other things, this means that there will be a reboot late in the boot process when using the configuration file during boot (see the documentation for details).
    • Added new script setting to execute the post-fs-data module boot script completely in the background (see the documentation for details).
    • Fixed some typos.
    • Various minor fixes and optimisations (which just means I can't remember exactly what I did and can't be bothered to look it up).
    • Added fingerprints for the Fairphone 2, Google Pixel 4 and 4 XL, OnePlus 7T and Samsung Galaxt Tab A WiFi. Updated fingerprints for the Essential PH-1, Google Pixel 2-3a (both regular and XL), OnePlus 6, 6T, 7 Pro and 7 Pro NR, Samsung Galaxy A5 2017 and Xiaomi Mi 9 Lite and Redmi K20 Pro/Mi 9T Pro. List updated to v66.

    v5.0.1
    Release notes
    • Fixed issue with settings being cleared when updating from earlier module versions. Sorry if anyone got all their custom props removed...
    • Fixed issue with creating a custom prints list.
    • Fixed issue with saving Magisk log.
    • Added fingerprint for Xiaomi Note 7 Pro. Fingerprints list updated to v65.

    v5.0.0
    Release notes
    • Updated possible locations for both the configuration and reset files (can now be placed in the root of internal storage, in /data or in /cache).
    • Updated device simulation so that all props now are disabled by default. Should hopefully make a few less careless users experience issues caused by the feature. NOTE! All simulation prop values will be disabled with this update. If you did have basic simulation enabled prior to the update, you have to manually enable it again.
    • Updated device simulation and added ro.build.display.id.
    • Updated reboot function.
    • Fixed a bug with the reset file (reset_mhpc) where system.prop would not be reset.
    • Fixed the setting of fingerprint props so that props that aren't already present on the device won't be set.
    • Fixed a bug where too similar custom props could not be set.
    • Fixed removal of old settings file on a fresh install.
    • Fixed possible issues with retrieving default file values on some devices/ROMs.
    • Fixed an issue where colours and clearing of the screen between menus don't work on Magisk v19.4+. Credits to @veez21 for the fix.
    • Stopped using /cache for logs and other module files. New location is /data/adb/mhpc. See the documentation for details.
    • Removed the "Improved root hiding" feature. It is most likely just placebo, but more importantly will also mount the system partition as rw on SAR devices. Big no-no... Might make a reworked reapperance in the future.
    • Slight tweaks to the ui and on-screen instructions, for (hopefully) better clarity and understanding.
    • Updated fingerprints for Asus Zenfone 6, Essential PH-1, Google Pixel 1-3a (regular and XL) and Pixel C, Huawei Mate 20 Pro, Motorola Moto G5S, OnePlus 5, 5T, 6T and 7 Pro, Samsung Galaxy A5 2017, Xiaomi Mi A2, Pocophone F1, Redmi 5A, Redmi K20 Pro, Redmi Note 5 Pro and Redmi Note 7. Added prints for Asus Zenfone 3 Max, Nokia 6.1 Plus, OnePlus One, Walmart Onn 8, Xiaomi Mi 9 Lite, Mi 9T, Mi A3, Redmi 4A and Redmi Note 4 Mediatek. Removed fingerprint for the LG G6 H872. List updated to v64.
    54
    Current fingerprints list version
    The fingerprints list will update without the need to update the entire module. Keep an eye on this thread for info about updates.

    When you run the props command it'll be updated automatically, or run the props command with the -f option if you've disabled automatic updates of the fingerprints list (can be done in the script settings). The list can also be updated from the "Edit device fingerprint" menu.

    Current fingerprints list - List v129
    - Asus ROG Phone 3 ZS661KS (10)
    - Asus ROG Phone 5 ZS673KS (10)
    - Asus ZenFone 2 Laser ASUS_Z00LD (6.0.1)
    - Asus ZenFone 3 Max ASUS_X00DD (7.1.1 & 8.1.0)
    - Asus ZenFone 3 Ultra ASUS_A001 (7.0)
    - Asus ZenFone 4 ASUS_Z01KD (8.0.0 & 9)
    - Asus ZenFone 4 Max ASUS_X00HD (7.1.1)
    - Asus ZenFone 5 ASUS_X00QD (9)
    - Asus ZenFone 5Z ASUS_Z01RD (9)
    - Asus ZenFone 6 ASUS_I01WD (9)
    - Asus ZenFone 7/7 Pro Europe ASUS_I002D (10)
    - Asus ZenFone 7/7 Pro Global ASUS_I002D (10)
    - Asus ZenFone Max M1 ASUS_X00PD (8.0.0 & 9 & 10)
    - Asus ZenFone Max Pro M1 ASUS_X00TD (8.1.0 & 9)
    - Asus ZenFone Max Pro M2 ASUS_X01BD (9)
    - Asus ZenPad S 8.0 P01MA (6.0.1)
    - BLU S1 (7.0)
    - BLU Vivo XI (8.1.0)
    - Elephone U Pro (8.0.0)
    - Essential PH-1 (7.1.1 & 8.1.0 & 9 & 10)
    - Fairphone 2 (6.0.1)
    - Fairphone 3/3 Plus (10)
    - Fxtec Pro 1 (9)
    - Google Nexus 4 (5.1.1)
    - Google Nexus 5 (6.0.1)
    - Google Nexus 5X (6.0 & 6.0.1 & 7.0 & 7.1.1 & 7.1.2 & 8.0.0 & 8.1.0)
    - Google Nexus 6 (5.0 & 5.0.1 & 5.1 & 5.1.1 & 6.0 & 6.0.1 & 7.0 & 7.1.1)
    - Google Nexus 6P (6.0 & 6.0.1 & 7.0 & 7.1.1 & 7.1.2 & 8.0.0 & 8.1.0)
    - Google Nexus 7 2012 Mobile (5.1.1)
    - Google Nexus 7 2012 WiFi (5.1.1)
    - Google Nexus 7 2013 Mobile (6.0.1)
    - Google Nexus 7 2013 WiFi (6.0.1)
    - Google Nexus 9 LTE (5.0.1 & 5.0.2 & 5.1.1 & 6.0 & 6.0.1 & 7.0 & 7.1.1)
    - Google Nexus 9 WiFi (5.0 & 5.0.1 & 5.0.2 & 5.1.1 & 6.0 & 6.0.1 & 7.0 & 7.1.1)
    - Google Nexus 10 (5.1.1)
    - Google Nexus Player (5.0 & 5.1 & 5.1.1 & 6.0.1 & 7.0 & 7.1.1 & 7.1.2 & 8.0.0)
    - Google Pixel (7.1 & 7.1.1 & 7.1.2 & 8.0.0 & 8.1.0 & 9 & 10)
    - Google Pixel XL (7.1 & 7.1.1 & 7.1.2 & 8.0.0 & 8.1.0 & 9 & 10)
    - Google Pixel 2 (8.0.0 & 8.1.0 & 9 & 10 & 11)
    - Google Pixel 2 XL (8.0.0 & 8.1.0 & 9 & 10 & 11)
    - Google Pixel 3 (9 & 10 & 11)
    - Google Pixel 3 XL (9 & 10 & 11)
    - Google Pixel 3a (9 & 10 & 11)
    - Google Pixel 3a XL (9 & 10 & 11)
    - Google Pixel 4 (10 & 11)
    - Google Pixel 4 XL (10 & 11)
    - Google Pixel 4a (10 & 11)
    - Google Pixel 4a 5G (11)
    - Google Pixel 5 (11)
    - Google Pixel C (6.0.1 & 7.0 & 7.1.1 & 7.1.2 & 8.0.0 & 8.1.0)
    - HTC 10 (6.0.1)
    - HTC U11 (8.0.0)
    - HTC U12 Plus (8.0.0 & 9)
    - HTC Exodus 1 (9)
    - Huawei Honor 6X BLN-AL10 (8.0.0)
    - Huawei Honor 6X BLN-L22 (8.0.0)
    - Huawei Honor 8X JSN-L21 (8.1.0)
    - Huawei Honor 9 STF-L09 (8.0.0 & 9)
    - Huawei Mate 9 MHA-L29 (9)
    - Huawei Mate 10 ALP-L29 (8.0.0)
    - Huawei Mate 10 Pro BLA-L29 (8.0.0)
    - Huawei Mate 20 Lite SNE-LX1 (9)
    - Huawei Mate 20 Pro LYA-L29 (9)
    - Huawei P8 Lite PRA-LX1 (8.0.0)
    - Huawei P9 EVA-AL10 (8.0.0)
    - Huawei P9 EVA-L09 (7.0)
    - Huawei P9 Lite VNS-L31 (7.0)
    - Huawei P9 Plus VIE-AL10 (8.0.0)
    - Huawei P9 Plus VIE-L09 (7.0)
    - Huawei P10 Lite (8.0.0)
    - Huawei P20 EML-L09 (9 & 10)
    - Huawei P20 Dual SIM EML-L29 (9)
    - Huawei P20 Lite (9)
    - Huawei P20 Lite Dual SIM (8.0.0 & 9)
    - Huawei P20 Pro CLT-L29 (8.1.0 & 9)
    - Infinix Note 5 (9 & 10)
    - Lenovo K6 Note (7.0)
    - Lenovo Tab 4 8 Plus TB-8704F (8.1.0)
    - Lenovo Tab 4 10 Plus TB-X704F (7.1.1)
    - Lenovo Tab 4 10 Plus TB-X704L (7.1.1)
    - LeEco Le Pro3 (6.0.1)
    - LG G2 VS980 (5.0.2)
    - LG G4 H812 (6.0)
    - LG G5 H830 (8.0.0)
    - LG G5 H850 (8.0.0)
    - LG G5 RS988 (7.0)
    - LG G6 H870 (7.0 & 8.0.0)
    - LG G7 ThinQ LM-G710 (9)
    - LG K20 Plus LG-TP260 (7.0)
    - LG K20 Plus LGMP260 (7.0)
    - LG K20 V VS501 (7.0)
    - LG V20 H910 (8.0.0)
    - LG V20 H918 (8.0.0)
    - LG V20 H990DS (7.0)
    - LG V20 LS997 (8.0.0)
    - LG V20 US996 (8.0.0)
    - LG V20 VS995 (8.0.0)
    - LG V30 H930 (8.0.0)
    - LG V30 LS998 (8.0.0)
    - Mecool KM8 (8.0.0 & 9)
    - Meizu 16th (8.1.0)
    - Meizu 17 (10)
    - Meizu X8 (8.1.0)
    - Motorola Moto C Plus (7.0)
    - Motorola Moto E4 (7.1.1)
    - Motorola Moto E4 Plus (7.1.1)
    - Motorola Moto E5 Play (8.0.0)
    - Motorola Moto E5 Plus (8.0.0)
    - Motorola Moto G Stylus (10)
    - Motorola Moto G4 (7.0 & 8.1.0)
    - Motorola Moto G5 (7.0)
    - Motorola Moto G5 Plus (7.0)
    - Motorola Moto G5S (7.1.1 & 8.1.0)
    - Motorola Moto G5S Plus (8.1.0)
    - Motorola Moto G6 (9)
    - Motorola Moto G6 Play (8.0.0 & 9)
    - Motorola Moto G6 Plus (9)
    - Motorola Moto G7 XT1962-1 (9 & 10)
    - Motorola Moto G7 XT1962-5 (10)
    - Motorola Moto G7 Power (9 & 10)
    - Motorola Moto G7 Play (9 & 10)
    - Motorola Moto G7 Play T-Mobile (10)
    - Motorola Moto X Play (7.1.1)
    - Motorola Moto X4 (8.0.0 & 9)
    - Motorola Moto Z2 Force T-Mobile (8.0.0)
    - Motorola Moto Z2 Play (8.0.0)
    - Nextbook Ares 8A (6.0.1)
    - Nokia 6 TA-1021 (9)
    - Nokia 6 TA-1025 (9)
    - Nokia 6 TA-1033 (9)
    - Nokia 6 TA-1039 (9)
    - Nokia 6.1 (10)
    - Nokia 6.1 Plus (9 & 10)
    - Nokia 6.2 (9)
    - Nokia 7 Plus (9 & 10)
    - Nokia 7.1 TA-1095 (10)
    - Nvidia Shield Tablet K1 (7.0)
    - Nvidia Shield Tablet LTE (7.0)
    - Nvidia Shield Tablet WiFi (7.0)
    - Nvidia Shield TV 2015 (8.0.0 & 9)
    - Nvidia Shield TV 2015 Pro (8.0.0 & 9)
    - Nvidia Shield TV 2017 (8.0.0 & 9)
    - Nvidia Shield TV 2019 (9)
    - Nvidia Shield TV 2019 Pro (9)
    - OnePlus One (6.0.1)
    - OnePlus 2 (6.0.1)
    - OnePlus X (6.0.1)
    - OnePlus 3 (8.0.0 & 9)
    - OnePlus 3T (8.0.0 & 9)
    - OnePlus 5 (8.1.0 & 9 & 10)
    - OnePlus 5T (7.1.1 & 8.0.0 & 8.1.0 & 9 & 10)
    - OnePlus 6 (8.1.0 & 9 & 10)
    - OnePlus 6T (9 & 10)
    - OnePlus 6T T-Mobile (9)
    - OnePlus 7 China GM1900 (10)
    - OnePlus 7 GM1901 (9 & 10)
    - OnePlus 7 Europe GM1903 (9 & 10)
    - OnePlus 7 GM1905 (9 & 10)
    - OnePlus 7 Pro China GM1910 (10)
    - OnePlus 7 Pro GM1911 (9 & 10)
    - OnePlus 7 Pro Europe GM1913 (9 & 10)
    - OnePlus 7 Pro T-Mobile GM1915 (9 & 10)
    - OnePlus 7 Pro GM1917 (9 & 10)
    - OnePlus 7 Pro NR Europe GM1920 (9 & 10)
    - OnePlus 7 Pro NR Sprint GM1925 (9 & 10)
    - OnePlus 7T China HD1900 (10)
    - OnePlus 7T HD1901 (10 & 11)
    - OnePlus 7T Europe HD1903 (10)
    - OnePlus 7T HD1905 (10 & 11)
    - OnePlus 7T Pro China HD1910 (10)
    - OnePlus 7T Pro HD1911 (10)
    - OnePlus 7T Pro Europe HD1913 (10)
    - OnePlus 7T Pro HD1917 (10)
    - OnePlus 7T Pro NR HD1925 (10)
    - OnePlus 8 China IN2010 (10)
    - OnePlus 8 India IN2011 (10 & 11)
    - OnePlus 8 Europe IN2013 (10 & 11)
    - OnePlus 8 Global IN2015 (10 & 11)
    - OnePlus 8 Visible IN2015 (10)
    - OnePlus 8 T-Mobile IN2017 (10 & 11)
    - OnePlus 8 Verizon IN2019 (10)
    - OnePlus 8 Pro China IN2020 (10)
    - OnePlus 8 Pro India IN2021 (10 & 11)
    - OnePlus 8 Pro Europe IN2023 (10 & 11)
    - OnePlus 8 Pro Global IN2025 (10 & 11)
    - OnePlus 8T China KB2000 (11)
    - OnePlus 8T India KB2001 (11)
    - OnePlus 8T Europe KB2003 (11)
    - OnePlus 8T Global KB2005 (11)
    - OnePlus 8T T-Mobile KB2007 (11)
    - OnePlus N10 5G Global BE2026 (10)
    - OnePlus N10 5G Europe BE2029 (10)
    - OnePlus N10 5G Metro BE2025 (10)
    - OnePlus N10 5G T-Mobile BE2028 (10)
    - OnePlus N100 Global BE2011 (10)
    - OnePlus N100 Europe BE2013 (10)
    - OnePlus N100 Metro BE2015 (10)
    - OnePlus N100 T-Mobile BE2012 (10)
    - OnePlus Nord India AC2001 (10 & 11)
    - OnePlus Nord Europe AC2003 (10 & 11)
    - OnePlus Nord Global AC2003 (10 & 11)
    - OPPO A53s Europe (10)
    - OPPO Find X2 Neo Europe CPH2009 (10)
    - OPPO Neo 7 A33w (5.1)
    - OPPO Neo 7 A1603 (5.1)
    - POCO F2 Pro Europe (10)
    - POCO F2 Pro Global (10)
    - POCO X2 (10)
    - POCO X3 NFC Europe (10 & 11)
    - POCO X3 NFC Global (10)
    - POCO X3 Pro Global (11)
    - Razer Phone (7.1.1 & 8.1.0 & 9)
    - Razer Phone 2 (8.1.0 & 9)
    - Realme X2 Pro (10)
    - Redmi 9T Global (10)
    - Redmi K30 Pro China (10)
    - Redmi K30 Pro Zoom Edition China (10)
    - Redmi K30 Ultra China (10)
    - Redmi K30S Ultra China (10)
    - Redmi Note 8 Pro Europe (10)
    - Redmi Note 8 Pro Global (9 & 10)
    - Redmi Note 8 Pro India (9 & 10)
    - Redmi Note 8 Pro Russia (9 & 10)
    - Redmi Note 9 Pro Europe (10)
    - Redmi Note 9 Pro Global (10)
    - Redmi Note 9 Pro Indonesia (10)
    - Redmi Note 9 Pro Max India (10)
    - Redmi Note 9S Europe (10)
    - Redmi Note 9S Global (10)
    - Redmi Note 10 Pro Global (11)
    - Samsung Galaxy A01 Core (10)
    - Samsung Galaxy A3 2015 SM-A300FU (6.0.1)
    - Samsung Galaxy A3 2016 SM-A310F (7.0)
    - Samsung Galaxy A3 2017 SM-A320FL (8.0.0)
    - Samsung Galaxy A5 2015 SM-A500FU (6.0.1)
    - Samsung Galaxy A5 2016 SM-A510F (7.0)
    - Samsung Galaxy A5 2017 SM-A520F (8.0.0)
    - Samsung Galaxy A6 SM-A600F (10)
    - Samsung Galaxy A6 Plus SM-A605G (9)
    - Samsung Galaxy A7 2017 SM-A720F (8.0.0)
    - Samsung Galaxy A7 2018 SM-A750GN (9 & 10)
    - Samsung Galaxy A8 Plus SM-A730F (7.1.1)
    - Samsung Galaxy A20 SM-A205W (9)
    - Samsung Galaxy A40 SM-A405FN (10)
    - Samsung Galaxy A50 SM-A505F (9)
    - Samsung Galaxy A50S SM-A507FN (10)
    - Samsung Galaxy A51 SM-A515F (10)
    - Samsung Galaxy A70 SM-A705FN (10)
    - Samsung Galaxy A71 SM-A715F (10)
    - Samsung Galaxy A90 5G SM-A908B (9)
    - Samsung Galaxy Core Prime SM-G361F (5.1.1)
    - Samsung Galaxy Grand Prime SM-G530BT (5.0.2)
    - Samsung Galaxy J2 2015 SM-J200H (5.1.1)
    - Samsung Galaxy J2 Core SM-S260DL (8.1.0)
    - Samsung Galaxy J3 SM-J320FN (5.1.1)
    - Samsung Galaxy J5 2015 SM-J500FN (6.0.1)
    - Samsung Galaxy J5 2016 SM-J510FN (7.1.1)
    - Samsung Galaxy J5 Prime SM-G570F (7.0)
    - Samsung Galaxy J7 2016 SM-J710FQ (8.1.0)
    - Samsung Galaxy J7 2017 SM-J730F (8.1.0)
    - Samsung Galaxy J7 Neo SM-J701M (8.1.0)
    - Samsung Galaxy J7 Prime SM-G610F (6.0.1)
    - Samsung Galaxy M20 SM-M205F (10)
    - Samsung Galaxy M21 SM-M215F (10)
    - Samsung Galaxy Note 3 SM-N9005 (5.0)
    - Samsung Galaxy Note 4 SM-N910F (6.0.1)
    - Samsung Galaxy Note 4 SM-N910G (6.0.1)
    - Samsung Galaxy Note 5 SM-N920C (7.0)
    - Samsung Galaxy Note 8 SM-N950F (8.0.0)
    - Samsung Galaxy Note 9 SM-N960F (10)
    - Samsung Galaxy Note 10 Plus SM-N9750 (10)
    - Samsung Galaxy Note 10 Plus SM-N975F (10)
    - Samsung Galaxy Note 10 Plus SM-N975U (10)
    - Samsung Galaxy Note 10.1 2014 SM-P600 (5.1.1)
    - Samsung Galaxy Note 20 Ultra SM-N986U (10)
    - Samsung Galaxy Note 20 Ultra 5G SM-N9860 (10)
    - Samsung Galaxy Note 20 Ultra 5G SM-N986B/DS (10)
    - Samsung Galaxy S3 Neo GT-I9300I (4.4.4)
    - Samsung Galaxy S4 GT-I9505 (5.0.1)
    - Samsung Galaxy S4 Active GT-I9295 (5.0.1)
    - Samsung Galaxy S5 SM-G900F (6.0.1)
    - Samsung Galaxy S5 SM-G900H (6.0.1)
    - Samsung Galaxy S6 SM-G920F (7.0)
    - Samsung Galaxy S6 Edge SM-G925F (7.0)
    - Samsung Galaxy S7 SM-G930F (8.0.0)
    - Samsung Galaxy S7 Edge SM-G935F (8.0.0)
    - Samsung Galaxy S8 SM-G950F (8.0.0)
    - Samsung Galaxy S8 Plus SM-G955F (8.0.0)
    - Samsung Galaxy S9 SM-G960F (8.0.0 & 10)
    - Samsung Galaxy S9 Plus SM-G965F (8.0.0)
    - Samsung Galaxy S10 SM-G973F (10 & 11)
    - Samsung Galaxy S10 SM-G973F Europe (11)
    - Samsung Galaxy S10 SM-G973N (11)
    - Samsung Galaxy S10 5G SM-G977B (11)
    - Samsung Galaxy S10 5G SM-G977N (11)
    - Samsung Galaxy S10 Plus SM-G975F (10 & 11)
    - Samsung Galaxy S10 Plus SM-G975F Europe (11)
    - Samsung Galaxy S10 Plus SM-G975N (11)
    - Samsung Galaxy S10 Plus SM-G975U (9)
    - Samsung Galaxy S10e SM-G970F (10 & 11)
    - Samsung Galaxy S10e SM-G970F Europe (11)
    - Samsung Galaxy S10e SM-G970N (10 & 11)
    - Samsung Galaxy S20 FE 5G (10)
    - Samsung Galaxy S20 Ultra SM-G988B (10)
    - Samsung Galaxy S21 SM-G991B (11)
    - Samsung Galaxy Tab 2 7.0 GT-P5110 (4.2.2)
    - Samsung Galaxy Tab 4 7.0 SM-T230NU (4.4.2)
    - Samsung Galaxy Tab 4 8.0 SM-T330NU (5.1.1)
    - Samsung Galaxy Tab 4 10.1 SM-T530NU (5.0.2)
    - Samsung Galaxy Tab A 8.0 LTE 2019 SM-T295 (9)
    - Samsung Galaxy tab A 10.1 WiFi 2019 SM-T510 (10)
    - Samsung Galaxt Tab A WiFi SM-T590 (9)
    - Samsung Galaxt Tab A LTE SM-T595 (9)
    - Samsung Galaxt Tab A LTE SM-T597 (9)
    - Samsung Galaxy Tab E 9.6 SM-T560 (4.4.4)
    - Samsung Galaxy Tab S2 SM-T813 (7.0)
    - Samsung Galaxy Tab S3 LTE SM-T825 (8.0.0)
    - Samsung Galaxy Tab S4 WiFi SM-T830 (10)
    - Samsung Galaxy Tab S4 LTE SM-T835 (10)
    - Samsung Galaxy Tab S5e SM-T720 (9 & 10 & 11)
    - Samsung Galaxy Tab S6 Lite SM-P610 (10)
    - Samsung Galaxy Tab S7+ WiFi SM-T970 (11)
    - Sony Xperia 5 DSDS J9210 (10)
    - Sony Xperia 10 (10)
    - Sony Xperia 10 II Dual XQ-AU52 (10)
    - Sony Xperia M (4.3)
    - Sony Xperia X F5121 (8.0.0)
    - Sony Xperia X Compact F5321 (8.0.0)
    - Sony Xperia X Dual F5122 (8.0.0)
    - Sony Xperia X Performance F8131 (8.0.0)
    - Sony Xperia X Performance Dual F8132 (8.0.0)
    - Sony Xperia XA2 Dual H4113 (8.0.0)
    - Sony Xperia XA2 Ultra H3223 (9)
    - Sony Xperia XZ F8331 (8.0.0)
    - Sony Xperia XZ Dual F8332 (8.0.0)
    - Sony Xperia XZ Premium G8141 (8.0.0)
    - Sony Xperia XZ Premium Dual G8142 (8.0.0)
    - Sony Xperia XZ1 G8341 (8.0.0)
    - Sony Xperia XZ1 Compact G8441 (8.0.0 & 9)
    - Sony Xperia XZ1 Dual G8342 (8.0.0)
    - Sony Xperia XZ2 H8216 (8.0.0)
    - Sony Xperia XZ2 Compact H8314 (8.0.0)
    - Sony Xperia XZ2 Compact Dual H8324 (8.0.0)
    - Sony Xperia XZ2 Dual H8266 (8.0.0)
    - Sony Xperia Z C6603 (5.1.1)
    - Sony Xperia Z1 C6903 (5.1.1)
    - Sony Xperia Z2 D6503 (6.0.1)
    - Sony Xperia Z3 D6633 (6.0.1)
    - Sony Xperia Z3 Compact D5803 (6.0.1)
    - Sony Xperia Z3 Tablet Compact SGP621 (6.0.1)
    - Sony Xperia Z4 Tablet LTE SGP771 (7.1.1)
    - Sony Xperia Z5 E6603 (7.1.1)
    - Sony Xperia Z5 E6653 (7.1.1)
    - Sony Xperia Z5 Compact E5823 (7.1.1)
    - Sony Xperia Z5 Dual E6633 (7.1.1)
    - Sony Xperia Z5 Premium E6853 (7.1.1)
    - Sony Xperia Z5 Premium Dual E6883 (7.1.1)
    - Vodafone Smart Ultra 6 (5.1.1)
    - Walmart Onn 8 (9)
    - Xiaomi Mi 3 Global (6.0.1)
    - Xiaomi Mi 4 Global (6.0.1)
    - Xiaomi Mi 4C China (7.0)
    - Xiaomi Mi 5/5 Pro Global (7.0 & 8.0.0)
    - Xiaomi Mi 5S Global (7.0)
    - Xiaomi Mi 5S Plus Global (6.0.1 & 7.0)
    - Xiaomi Mi 6 Global (8.0.0 & 9)
    - Xiaomi Mi 8 Global (8.1.0 & 9 & 10)
    - Xiaomi Mi 8 Pro Global (10)
    - Xiaomi Mi 8 Pro Russia (10)
    - Xiaomi Mi 9 China (10)
    - Xiaomi Mi 9 Europe (9)
    - Xiaomi Mi 9 Lite Global (9)
    - Xiaomi Mi 9 SE Global (9)
    - Xiaomi Mi 9T China (10)
    - Xiaomi Mi 9T Europe (9 & 10)
    - Xiaomi Mi 9T Pro China (9 & 10)
    - Xiaomi Mi 9T Pro Europe (10)
    - Xiaomi Mi 9T Pro Global (10)
    - Xiaomi Mi 10 China (10 & 11)
    - Xiaomi Mi 10 Europe (10)
    - Xiaomi Mi 10 Lite 5G Europe (10)
    - Xiaomi Mi 10 Lite 5G Global (10)
    - Xiaomi Mi 10 Pro China (10 & 11)
    - Xiaomi Mi 10 Ultra China (10 & 11)
    - Xiaomi Mi 10S China (11)
    - Xiaomi Mi 10T Europe (10)
    - Xiaomi Mi 10T Lite Europe (10)
    - Xiaomi Mi 10T Pro Europe (10)
    - Xiaomi Mi 11 China (11)
    - Xiaomi Mi A1 Global (7.1.2 & 8.0.0 & 8.1.0 & 9)
    - Xiaomi Mi A2 Global (8.1.0 & 9 & 10)
    - Xiaomi Mi A2 Lite Global (8.1.0 & 9 & 10)
    - Xiaomi Mi A3 Europe (9 & 10 & 11)
    - Xiaomi Mi A3 Global (9 & 10 & 11)
    - Xiaomi Mi Box S (9)
    - Xiaomi Mi Max Global (6.0.1)
    - Xiaomi Mi Max 2 Global (7.1.1)
    - Xiaomi Mi Max 3 Global (9)
    - Xiaomi Mi Mix 2 Global (8.0.0 & 9)
    - Xiaomi Mi Mix 2S Global (8.0.0 & 9)
    - Xiaomi Mi Mix 2S China (10)
    - Xiaomi Mi Mix 3 Global (9 & 10)
    - Xiaomi Mi Mix 3 5G Europe (9)
    - Xiaomi Mi Note 2 China (8.0.0)
    - Xiaomi Mi Note 2 Global (7.0)
    - Xiaomi Mi Note 3 Global (8.1.0)
    - Xiaomi Mi Note 10 Europe (9)
    - Xiaomi Mi Pad Global (4.4.4)
    - Xiaomi Mi Pad 4 China (8.1.0)
    - Xiaomi Pocophone F1 Global (9 & 10)
    - Xiaomi Redmi 3/3 Pro Global (5.1.1)
    - Xiaomi Redmi 3S/X Prime Global (6.0.1)
    - Xiaomi Redmi 4 Pro Global (6.0.1)
    - Xiaomi Redmi 4A Global (7.1.2)
    - Xiaomi Redmi 4X China (6.0.1)
    - Xiaomi Redmi 5 Plus Global (7.1.2 & 8.1.0)
    - Xiaomi Redmi 5A Global (7.1.2 & 8.1.0)
    - Xiaomi Redmi 6 Global (9)
    - Xiaomi Redmi 6 Pro China (9)
    - Xiaomi Redmi 6 Pro India (9)
    - Xiaomi Redmi 6A Global (9)
    - Xiaomi Redmi 7 Europe (10)
    - Xiaomi Redmi 7 Global (9)
    - Xiaomi Redmi 7A Global (9 & 10)
    - Xiaomi Redmi 8 China (9 & 10)
    - Xiaomi Redmi 9 China (10)
    - Xiaomi Redmi Go Global (8.1.0)
    - Xiaomi Redmi K20 Pro China (9 & 10)
    - Xiaomi Redmi K20 Pro Europe (10)
    - Xiaomi Redmi K20 Pro Global (10)
    - Xiaomi Redmi K20 Pro India (10)
    - Xiaomi Redmi Note 2 Global (5.0.2)
    - Xiaomi Redmi Note 3 Pro China (6.0.1)
    - Xiaomi Redmi Note 3 Pro SE Global (6.0.1)
    - Xiaomi Redmi Note 4 Global (7.0)
    - Xiaomi Redmi Note 4X Global (7.0)
    - Xiaomi Redmi Note 4 Mediatek Global (6.0)
    - Xiaomi Redmi Note 5 Global (7.1.2 & 8.1.0)
    - Xiaomi Redmi Note 5 Pro Global (8.1.0 & 9)
    - Xiaomi Redmi Note 5A Lite Global (7.1.2)
    - Xiaomi Redmi Note 6 Pro Global (8.1.0 & 9)
    - Xiaomi Redmi Note 7 Global (9)
    - Xiaomi Redmi Note 7 Pro India (9)
    - Xiaomi Redmi Note 8 Global (9 & 10)
    - Xiaomi Redmi Note 8T Europe (9 & 10)
    - Xiaomi Redmi Y1 Global (7.1.2)
    - ZTE Axon 7 (7.1.1 & 8.0.0)
    - ZTE Blade (6.0.1)
    - ZTE Nubia Z17 (7.1.1)
    - Zuk Z2 Pro (7.0)
    27
    Nice and shiny new support thread. And while moving everything over I also found what the issue was with the old one and why I couldn't update the OP of that one... :laugh:

    Oh well... It's done now.

    Will be back shortly with some new fingerprints added to the list (well, they've already been posted in the old support thread, but I'll add them to the module). :good:
    27
    Announcement

    Real life happened...

    Yesterday I started University, and that's gonna be a huge priority from now on (and for the next 5 years :eek:). I can no longer sit at work and pretend to be doing something useful while browsing the Magisk forums... :laugh:

    That, combined with some other major upcoming life events, means I will not be anywhere near as active as I've been the past couple of years. I'll keep track of this thread and I'll make sure the Magisk and MagiskHide Installation and Troubleshooting guide is kept alive, but that's about it.

    Have a good one. :good: