[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2

Search This thread

ipdev

Recognized Contributor
Feb 14, 2016
1,917
1
3,510
Google Nexus 10
Nexus 7 (2013)
I am unable to install this module. Through Lygisk it never finishes and the LineageOS recovery throws an error message.
Just a few days ago it worked just fine, had to reset my phone, don't know what I'm doing wrong this time.
I am not sure if I ever installed this module from recovery.
If I did it was a long time ago and would have been TWRP.

I am not surprised that it does not install from Lineage recovery.
The next time I install Lineage on a device I will try it and see what error it gives. 🙃

The module should install though Magisk's Module installer.
Next time please save and attach the logcat from Magisk when the module install stalls, stops or fails.

--

You say you reset your device for some reason.
For me, this normally is a complete wipe/format and clean install of system (rom) and everything else.

Unless you completely wiped data/formatted data, it is possible that something is left over from the prior install.
Make sure to save what you want to keep and store it off device (Computer, removable storage, cloud storage,...) before wiping/formatting data.

You could could try deleting the /data/adb directory and reboot.
Magisk will recreate the directory and it's database but, you will start from scratch as far as Magisk goes.
- You will have to setup Magisk again, configure root access, install modules, ...

Cheers. :cowboy:
 
Last edited:

damian101

Member
Dec 4, 2017
8
1
I am not sure if I ever installed this module from recovery.
If I did it was a long time ago and would have been TWRP.

I am not surprised that it does not install from Lineage recovery.
The next time I install Lineage on a device I will try it and see what error it gives. 🙃

The module should install though Magisk's Module installer.
Next time please save and attach the logcat from Magisk when the module install stalls, stops or fails.

--

You say you reset your device for some reason.
For me, this normally is a complete wipe/format and clean install of system (rom) and everything else.

Unless you completely wiped data/formatted data, it is possible that something is left over from the prior install.
Make sure to save what you want to keep and store it off device (Computer, removable storage, cloud storage,...) before wiping/formatting data.

You could could try deleting the /data/adb directory and reboot.
Magisk will recreate the directory and it's database but, you will start from scratch as far as Magisk goes.
- You will have to setup Magisk again, configure root access, install modules, ...

Cheers. :cowboy:
thanks, deleting /data/adb worked
 
  • Like
Reactions: ipdev

matt1313

Senior Member
Sep 24, 2010
704
319
California
Google Pixel 5
Could anyone provide some suggestions.

Currently have a P5 running protron 12.4.1 early release. I can't get gpay working.
Magisk 25.2

Tried
Safetynet fix by display
Props changing fingers prints to p5 12, p5 11, p4 5g
Clear caches/data

Google API shows basic is good, play store shows verified. Others don't pass.

Thanks in advance.
 

pndwal

Senior Member
Could anyone provide some suggestions.

Currently have a P5 running protron 12.4.1 early release. I can't get gpay working.
Magisk 25.2

Tried
Safetynet fix by display
Props changing fingers prints to p5 12, p5 11, p4 5g
Clear caches/data

Google API shows basic is good, play store shows verified. Others don't pass.

Thanks in advance.
Proton ROMs generally have SafetyNet Fix integrated AFAIK; after all, SNF was developed by @kdragon for Proton and USNF was/is really SNF made available for other ROMs/devices...

I haven't looked into Proton apart from its SNF implementation; perhaps @kdragon makes ROMs w/o fixes for CTS Profile (fingerprint/security patch level spoofing) available?

Not sure how USNF copes with embedded SNF, but I'm aware others have reported difficulties with ROMs incorporating the fix... Perhaps @Displax may say if this is actually the problem (I think it's likely) or another issue...

If it is, it may be possible to make a module that only spoofs A6 fingerprint for gms attestation process for use with ROMs w/ integrated SNF... (!?)

Also, have you checked Proton forums in case there are user comments about this?... PW
 
  • Like
Reactions: 73sydney and ipdev

ipdev

Recognized Contributor
Feb 14, 2016
1,917
1
3,510
Google Nexus 10
Nexus 7 (2013)
Could anyone provide some suggestions.

Currently have a P5 running protron 12.4.1 early release. I can't get gpay working.
Magisk 25.2

Tried
Safetynet fix by display
Props changing fingers prints to p5 12, p5 11, p4 5g
Clear caches/data

Google API shows basic is good, play store shows verified. Others don't pass.

Thanks in advance.
Without the USNF module, does SafetyNet return Basic or Hardware test?

If it shows basic, then the Proton rom is forcing basic attestation.

With changes to Google's security, SafetyNet is being replaced by Play Integrity.
You device can pass SafetyNet but fail Play Integrity.

xda member @1nikolas made an app to check Play Integrity.
Play Integrity API Checker - PlayStore

For example.
Stock July Google build.
Magisk canary.
The normal USNF module.
MHPC module.

I can pass SafetyNet using any certified fingerprint.
I can only pass Play Integrity with a few.
Play Integrity fails if I use a June/July Pixel fingerprint.
If I use May or older Pixel fingerprint, Play Integrity passes.​

Cheers. :cowboy:
 
  • Like
Reactions: 73sydney

matt1313

Senior Member
Sep 24, 2010
704
319
California
Google Pixel 5
Without the USNF module, does SafetyNet return Basic or Hardware test?

If it shows basic, then the Proton rom is forcing basic attestation.

With changes to Google's security, SafetyNet is being replaced by Play Integrity.
You device can pass SafetyNet but fail Play Integrity.

xda member @1nikolas made an app to check Play Integrity.
Play Integrity API Checker - PlayStore

For example.
Stock July Google build.
Magisk canary.
The normal USNF module.
MHPC module.

I can pass SafetyNet using any certified fingerprint.
I can only pass Play Integrity with a few.
Play Integrity fails if I use a June/July Pixel fingerprint.​
If I use May or older Pixel fingerprint, Play Integrity passes.​

Cheers. :cowboy:
Without USNF it only passes basic. Same as with the module.
 
  • Like
Reactions: ipdev

ipdev

Recognized Contributor
Feb 14, 2016
1,917
1
3,510
Google Nexus 10
Nexus 7 (2013)
Where in props do you see the months of finger prints
This module's fingerprint list does not support multiple same level build fingerprints.
Support for different Android levels per device but, the current print will be replaced by the newest print when supplied.​
MagiskHidePropsConfig - [GitHub] - [fingerprint list] - Link

Before Play Integrity, this was not an issue.
Normally any certified print could be used to pass SafetyNet on any device.

You can generally go by the matching security date.
I thought it showed the security date when you selected a fingerprint but, I see it does not.
The current Pixel 12 prints in the fingerprint list are from the October 2021 release.

--

If you use a custom fingerprint list (printslist), you set the device name shown.

Code:
=====================================
 Edit device fingerprint
 List version - v137
 Select an option below.
=====================================

1 - Pixel 5a -Jan- (12)
2 - Pixel 5a -Feb- (12)
3 - Pixel 5a -Mar- (12L)
4 - Pixel 5a -Apr- (12L)
5 - Pixel 5a -May- (12L)
6 - Pixel 5a -Jun- (12L)
7 - Pixel 5a -Jul- (12L)
b - Go back
e - Exit

/sdcard/printslist
Code:
Pixel 5a -Jan- (12):Google:Pixel 5a=google/barbet/barbet:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 5a -Feb- (12):Google:Pixel 5a=google/barbet/barbet:12/SQ1A.220205.002/8010174:user/release-keys__2022-02-05
Pixel 5a -Mar- (12L):Google:Pixel 5a=google/barbet/barbet:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 5a -Apr- (12L):Google:Pixel 5a=google/barbet/barbet:12/SP2A.220405.003/8210211:user/release-keys__2022-04-05
Pixel 5a -May- (12L):Google:Pixel 5a=google/barbet/barbet:12/SP2A.220505.002/8353555:user/release-keys__2022-05-05
Pixel 5a -Jun- (12L):Google:Pixel 5a=google/barbet/barbet:12/SQ3A.220605.009.A1/8643238:user/release-keys__2022-06-05
Pixel 5a -Jul- (12L):Google:Pixel 5a=google/barbet/barbet:12/SQ3A.220705.003.A1/8672226:user/release-keys__2022-07-05

Attached is a custom prints list for Pixel 5.
January (2022) though July (2022).
- To use, rename it to printslist and place it in the /sdcard/ directory.
The next time you run props it will show up in the finger print list as 3 - Custom.

Cheers. :cowboy:

PS.
Yes. Google generally builds their updates a month before release.
 

Attachments

  • Pixel5-printslist-20220807.txt
    13.4 KB · Views: 21

matt1313

Senior Member
Sep 24, 2010
704
319
California
Google Pixel 5
This module's fingerprint list does not support multiple same level build fingerprints.
Support for different Android levels per device but, the current print will be replaced by the newest print when supplied.​
MagiskHidePropsConfig - [GitHub] - [fingerprint list] - Link

Before Play Integrity, this was not an issue.
Normally any certified print could be used to pass SafetyNet on any device.

You can generally go by the matching security date.
I thought it showed the security date when you selected a fingerprint but, I see it does not.
The current Pixel 12 prints in the fingerprint list are from the October 2021 release.

--

If you use a custom fingerprint list (printslist), you set the device name shown.

Code:
=====================================
 Edit device fingerprint
 List version - v137
 Select an option below.
=====================================

1 - Pixel 5a -Jan- (12)
2 - Pixel 5a -Feb- (12)
3 - Pixel 5a -Mar- (12L)
4 - Pixel 5a -Apr- (12L)
5 - Pixel 5a -May- (12L)
6 - Pixel 5a -Jun- (12L)
7 - Pixel 5a -Jul- (12L)
b - Go back
e - Exit

/sdcard/printslist
Code:
Pixel 5a -Jan- (12):Google:Pixel 5a=google/barbet/barbet:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 5a -Feb- (12):Google:Pixel 5a=google/barbet/barbet:12/SQ1A.220205.002/8010174:user/release-keys__2022-02-05
Pixel 5a -Mar- (12L):Google:Pixel 5a=google/barbet/barbet:12/SP2A.220305.012/8177914:user/release-keys__2022-03-05
Pixel 5a -Apr- (12L):Google:Pixel 5a=google/barbet/barbet:12/SP2A.220405.003/8210211:user/release-keys__2022-04-05
Pixel 5a -May- (12L):Google:Pixel 5a=google/barbet/barbet:12/SP2A.220505.002/8353555:user/release-keys__2022-05-05
Pixel 5a -Jun- (12L):Google:Pixel 5a=google/barbet/barbet:12/SQ3A.220605.009.A1/8643238:user/release-keys__2022-06-05
Pixel 5a -Jul- (12L):Google:Pixel 5a=google/barbet/barbet:12/SQ3A.220705.003.A1/8672226:user/release-keys__2022-07-05

Attached is a custom prints list for Pixel 5.
January (2022) though July (2022).
- To use, rename it to printslist and place it in the /sdcard/ directory.
The next time you run props it will show up in the finger print list as 3 - Custom.

Cheers. :cowboy:

PS.
Yes. Google generally builds their updates a month before release.
Thank you for the detailed help and support. Unfortunately I still cant get it to pass. Going back to stock for now.

Thanks again!!
 
  • Like
Reactions: 73sydney and ipdev

nasrrafiq

New member
Nov 8, 2016
2
0
How can i upload my own signature?
Code:
Redmi/secret_id/secret:11/RP1A.200720.011/V12.5.8.0.RKLIDXM:user/release-keys
 

73sydney

Senior Member
How can i upload my own signature?
Code:
Redmi/secret_id/secret:11/RP1A.200720.011/V12.5.8.0.RKLIDXM:user/release-keys

The dev is very busy outside of XDA in real life as of a while ago and probably currently.

If youre just posting here to submit, you have done all thats required and can do

If however youre looking to use that fingerprint in the module itself, then you should create a printslist file as per these instructions:


Once created and on internal memory (sdcard), you can access it via the Custom menu in the module

There are examples of the correct formatting for such a file through this thread, and i referenced some for my device here last week in correct printslist format, as below:


Samsung Galaxy S20+ 5G SM-G986B (11):Samsung:SM-G986B=samsung/y2sxxx/y2s:11/RP1A.200720.012/G986BXXSCDUJ5:user/release-keys_2021-11-01


So basically:

<Manufacturer> <Model> <Model Number> (Android Version):<Manufacturer>:<Model Number>=<fingerprint>
 
  • Like
Reactions: ipdev and rodken

Finnzz

Senior Member
Sep 26, 2017
222
131
Is there any way possible with Magisk, to change a build.prop value and have it take effect without a reboot? It doesn't seem possible with MagiskHide Props, but it's there a way to pull it off in combination with some other module, or another module all together?
 

zgfg

Senior Member
Oct 10, 2016
7,799
5,201
Is there any way possible with Magisk, to change a build.prop value and have it take effect without a reboot? It doesn't seem possible with MagiskHide Props, but it's there a way to pull it off in combination with some other module, or another module all together?
Magisk makes Systemless changes only while (re) booting

Modules do not write over the System but define their changes at /data/adb/modules, Magisk reads and mounts the changes while initializing

If you have and old phone white writeble System, you could make then manually changes directly to System, by using root but not through MHCP
 
  • Like
Reactions: Finnzz

73sydney

Senior Member
Guys do we install and forget or are we supposed to tweak things? The Github guide seems bit outdated in options
Thanks

Read the documentation, we refer to it all the time, so not sure where its "outdated" as its core functions havent changed in eons

If you feel its outdated, please show an example and someone will comment further.

Users are expected to read at least the opening sections especially:


If after reading this you are stuck by all means post back and ask for help/clarification if you dont understand, but no ones going to regurgitate the extremely detailed info from the dev every time someone posts here...you can appreciate how messy the thread would be

The documentation is set out in case usage sections, so only you know which case you fit....
 
  • Haha
Reactions: pndwal

pndwal

Senior Member
Guys do we install and forget or are we supposed to tweak things? The Github guide seems bit outdated in options
Thanks
@2B (or Not 2B) -

You can, but will profit only if you require the following limited-use function:
Set/reset MagiskHide Sensitive props

Up to and including Magisk v23 MagiskHide changes some sensitive props to "safe" values that won't trigger apps that might be looking for them as a sign of your device being tampered with (root).

This feature is enabled by default and will automatically change any triggering values it finds to "safe" values.

The props in question are:
...
https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props

To be clear (doc is not very), this means that this module replaces (restores) the MagiskHide 'Set/reset MagiskHide Sensitive props' function for Zygisk-age (24.0+) Magisk builds and is enabled by default.

Nb. This is already being done by Universal SafetyNet Fix module, so many users will not notice any changes applied. Users who haven't installed USNF (eg users of pre Android 7 (Nb. USNF now supports 7) and devices w/ broken keymaster implementation) may benefit/need this.

AFAIK, these are the only prop changes applied by default; Prior to this function being added, installing MHPC did nothing until configured using a terminal emulator...

So, for all other use scenarios including the commonly-used Spoofing device's fingerprint to pass the ctsProfile check function, you need to configure MHPC using a terminal emulator...

This may be a (good) reminder (for some) that unconfigured MHPC is actually active, setting/resetting any sensitive props formerly adjusted by MagiskHide found...

... no ones going to regurgitate...
You make me sic (sic)... Fully sic erat scriptum... 😛 PW

regurgitate /rɪˈɡəːdʒɪteɪt/
verb
1. bring (swallowed food) up again to the mouth.
"gulls regurgitate food for the chicks"
Similar: vomit, bring up, disgorge, regorge
2. repeat (information) without analysing or comprehending it.
"facts which can then be regurgitated at examinations"
Similar: repeat, say again, restate, recapitulate, iterate reiterate, recite, rehearse, parrot, trot out
 
Last edited:

73sydney

Senior Member
@2B (or Not 2B) -

You can, but will profit only if you require the following limited-use function:

https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props

To be clear (doc is not very), this means that this module replaces (restores) the MagiskHide 'Set/reset MagiskHide Sensitive props' function for Zygisk-age (24.0+) Magisk builds and is enabled by default.

Nb. This is already being done by Universal SafetyNet Fix module, so many users will not notice any changes applied. Users who haven't installed USNF (eg users of pre Android 7 (Nb. USNF now supports 7) and devices w/ broken keymaster implementation) may benefit/need this.

AFAIK, these are the only prop changes applied by default; Prior to this function being added, installing MHPC did nothing until configured using a terminal emulator...

So, for all other use scenarios including the commonly-used Spoofing device's fingerprint to pass the ctsProfile check function, you need to configure MHPC using a terminal emulator...

This may be a (good) reminder (for some) that unconfigured MHPC is actually active, setting/resetting any sensitive props formerly adjusted by MagiskHide found...


You make me sic (sic)... Fully sic erat scriptum... 😛 PW

regurgitate /rɪˈɡəːdʒɪteɪt/
verb
1. bring (swallowed food) up again to the mouth.
"gulls regurgitate food for the chicks"
Similar: vomit, bring up, disgorge, regorge
2. repeat (information) without analysing or comprehending it.
"facts which can then be regurgitated at examinations"
Similar: repeat, say again, restate, recapitulate, iterate reiterate, recite, rehearse, parrot, trot out

Stop enabling spoonfeeding you horrible person :) :)

Food for the chicks.....that dictionary reference needs to adopt the great Aussie "chunder"
 
  • Haha
Reactions: pndwal

ipdev

Recognized Contributor
Feb 14, 2016
1,917
1
3,510
Google Nexus 10
Nexus 7 (2013)
<SNIP>
https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props

To be clear (doc is not very), this means that this module replaces (restores) the MagiskHide 'Set/reset MagiskHide Sensitive props' function for Zygisk-age (24.0+) Magisk builds and is enabled by default.
<SNIP>
One of the hardest parts of creating and maintaining a project (even a simple script), is writing the documentation.
At least it is for me. 🙃
  • Not too technical.
  • Not too general.
  • Does it make sense to someone who is not familiar with the project?
  • Make sense out-of-context (stand-alone) from the rest of the instructions?

Cheers. :cowboy:
PS.
Two scripts I use semi-often.
- dump_image_files script to unpack a rom.
- mount_image_files script to mount the images.

It would take at least a few paragraphs (and a few rewrites) to properly document how to use them.
I could not get away with just "Use the dump_image_files script to unpack the rom. Use the mount_image_files script to mount it."
 

pndwal

Senior Member
One of the hardest parts of creating and maintaining a project (even a simple script), is writing the documentation.
At least it is for me. 🙃
  • Not too technical.
  • Not too general.
  • Does it make sense to someone who is not familiar with the project?
  • Make sense out-of-context (stand-alone) from the rest of the instructions?

Cheers. :cowboy:
PS.
Two scripts I use semi-often.
- dump_image_files script to unpack a rom.
- mount_image_files script to mount the images.

It would take at least a few paragraphs (and a few rewrites) to properly document how to use them.
I could not get away with just "Use the dump_image_files script to unpack the rom. Use the mount_image_files script to mount it."
Hadn't meant to be critical although it is a criticism I guess...

Rather, it's an acknowledgement that a user could be excused for not understanding, and the kind of flag for improvement any dev will need and any modest one will appreciate... And the didgeridoo-man from Sweden is one such contradiction... 😬 ... I trust the boomerang won't fall far from the didgeridoo...

Also, this might serve till he can extricate himself from RL to do maintenance...

FWIW, the difficulty relates to your point no. 4, "Makes sense out-of-context (stand-alone) from the rest of the instructions"... And it will be the exceptional dev who can always disregard everything he knows to think like a noob when writing docs... Sometimes it's gonna take a noob like me to plead for clarity!...

Further, Didge knows what I think of his project. (For inside joke, search-term = elegant)...
@pndwal Elegant? Have you seen my code!? :silly:
Elegant not manly enough? Not PC? No offense meant. - How about more 'robust' then? More 'universal'? More 'powerful'?

Man, if I could code it'd look like yours... Hats off to @hackintosh5 too however - great stand-alone solution for some time (no need for terminal or even root, and worked on stock ROMs too)! Just wish I could code like him...

Rogue bind mount eh? - I had a hunch! ;) PW
Click to collapse
:D My code could be called many things, but "elegant" is not one of them. I wish... It's gotten better over the years, but some of it is downright ugly.
And congratulations on those impressive milestones Didg... Hope temp. fix from Displax may get your elegant module a bit more mileage too! :D PW
Thanks. And you had to go there, huh? :D
Nicely implemented! - especially option f, 'Pick from fingerprints list', which provides for dead easy setting / trialing alternative prop values where device specific features may not work with default forced prop value as expected.
Yeah, I thought you'd like that one. The inspiration for that came from your suggestion...
In any case, this is the difinitive all-in-one systemless solution for custom props, and your new option has got to be the most elegant solution for forcing BASIC (non hardware backed) SafetyNet attestation to date! ;) Ta, PW
Thank you. Somehow I knew you'd say that... :p
(the excellent, exhaustive & - dare I say it - elegant) Magisk Troubleshoot Wiki by @Didgeridoohan.
giphy.gif

You forgot: in need of a major update... Once Magisk v24 is released I've got a lot of work to do.
🤪 PW
 
  • Like
Reactions: ipdev

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Does this module still receive updates? I am using it to pass basic attestation against the new Play Integrity API, and it works great, but I noticed that the module's development seems to have slowed?

    Real life happened. 🙃
    Post #6,033
    Just popping in and letting everyone know I'm still alive.

    There are simply too many things going on outside the world of Android tinkering for me to be able to give XDA much attention at all. Once things settle down, and if I'm not entirely burnt out by then, I've got quite a lot of catching up to do. Can't give any kind of ETA, but I'm hoping for things clearing up before the end of February.

    Huge thanks to everyone answering questions and helping out, and to everyone still providing device fingerprints. I will get to them eventually...

    I am sure he will be back as soon as he can. 🙂

    The module seems to still work fine.
    I was going to gather up all the new fingerprints, test them and share a custom printslist with all the new prints but....
    Real life kicked my butt and I have not had time to do it yet. 🙃

    Cheers. :cowboy:
    5
    Real life happened. 🙃
    Post #6,033
    Got it. That's totally understandable. Thanks for sharing! Sometimes these XDA threads are so dense that it's very easy to miss noteworthy posts such as that one.
    4

    Maybe chainfire and su will make a comeback :)

    Someone start that rumour, maybe it will offset all the conspiracy theories about topjohnwu and his work at big G :)

    Meanwhile the mystery train keeps rolling and now in my wonky brain my focus is set to wonder which of the Strays @pndwal looks like most
    3
    <SNIP>
    Tried JackPals Term.apk also... Can't install on my device for some reason:
    <SNIP>
    ... If it won't work it won't work. 😕 🤷 PW
    Bummer. 😥

    Just checked on my Pixel 6. (Android 12L).
    Looks like jackpal does not work properly as user.
    Works fine as root. 🙃

    So it looks like (after about 10 years) I will have to find a different terminal app. 😥

    Cheers. :cowboy:

    Edit:
    Since jackpal works fine with root privilege, the props command runs fine.
    3
    Hello can I have a little help, cause I might be blind but can't seem to find the link to download busybox from osmosis github...

    bookmark this


    Or/also

    try this for alternatives

  • 310
    MagiskHide Props Config v6.1.2
    ctsProfilefalse.jpg

    Note: For some time I have been extremely busy IRL. I simply have to prioritise things outside the Android modding world... I will get back to updating the fingerprints list and providing support as soon as I can. There is no ETA for this, but hopefully by the end of March 2022.

    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:
    77
    Changelog
    v6.1.2
    Release notes
    • Added rudimentary tampering check.
    • Added fingerprints for OnePlus 9RT, Samsung Galaxy A52 4G and Xiaomi Mi 6X and Redmi K30 Pro. Updated fingerprints for OnePlus 6 to Nord CE, many variants. List updated to v137.
    v6.1.1
    Release notes
    • Updated custom props so that it's possible to set the same prop with different values during different boot stages.
    • Updated some module checks to match the new state of Magisk (MagiskHide is dead, long live MagiskHide).
    • Added fingerprints for LG G8 ThinQ, Samsung Galaxy S20 FE SM-G780F and Xiaomi Redmi K20 Europe. Updated fingerprints for Google Pixel 3 to 5a (all variants), Nokia 6.1 Plus, Oneplus 6T, 9 and 9 Pro (several variants), Xiaomi Mi 9T Europe, Mi 9T Pro Global and Redmi K20 Pro China. List updated to v135.
    v6.1.0
    Release notes
    • Added settings file version check.
    • Added a check for the new Universal SafetyNet Fix and disable sensitive props at install if v2.1.0 or newer is detected.
    • Changed default boot stage for SELinux fix and triggering props to late_start service.
    • Fixed update check.
    • Fixed a few problems with the configuration file import.
    • Make sure late props are set after boot completed (might break some features otherwise, forgot about that).
    • Minor UI fixes.
    • Added fingerprints for Asus Smartphone for Snapdragon Insiders and Xiaomi Mi 11 Lite Indonesia. Updated fingerprint for Xiaomi Mi 10 Lite 5G Global. List updated to v133.
    v6.0.2
    Release notes
    • Fix problems when trying to disable/enable sensitive props.
    • Fix typo when checking for triggering prop values (meant that props wouldn't set properly during boot).
    • Fix UI info for if a sensitive prop has been set by the module or not.
    • More optimisations of the new code (but it's by no means optimised).
    v6.0.1
    • Quickfix update to make the soft reboot when setting props in the late_start service boot stage an option. It has the potential for causing issues it seems (mainly on Samsung devices apparently). See the documentation for details.
    • Minor UI fixes and optimisations.
    v6.0.0
    • Updated the "Edit MagiskHide props" feature to include all the sensitive prop values that MagiskHide changed, up to and including Magisk v23. All props will now be set by default. See the documentation for details.
    • Alter the permissions for SELinux files if SELinux is permissive (was included in MagiskHide up to Magisk v23).
    • Reenabled "Force BASIC key attestation", since Google seems to have changed things around again. See the documentation for details.
    • Fix reboot function in post-fs-data.sh.
    • Various small fixes.
    • Added fingerprints for Google Pixel 5a and Motorola Moto Z3 Play. List updated to v132.
    v5.4.1
    Release notes
    • Changed internet connection test to use Github rather than Google, for users that do not have access to Google in their countries.
    • Fixed a bug where prop values containing equal signs would be truncated.
    • Fix error message in log regarding copying system.prop during module installation.
    • Added fingerprints for the POCO F3 (Europe, Global, Indonesia, Russia, Taiwan and Turkey) and Redmi K40 China and updated the fingerprint for the Xiaomi Mi 8 Explorer. Fingerprints list updated to v131.

    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.
    62
    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 v137
    - Asus ROG Phone 3 ZS661KS (10)
    - Asus ROG Phone 5 ZS673KS (10)
    - Asus Smartphone for Snapdragon Insiders ASUS_I007D (11)
    - 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 Zenfone 8 Mini Europe ASUS_I006D (11)
    - Asus Zenfone 8 Mini Global ASUS_I006D (11)
    - 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 & 12)
    - Google Pixel 3 XL (9 & 10 & 11 & 12)
    - Google Pixel 3a (9 & 10 & 11 & 12)
    - Google Pixel 3a XL (9 & 10 & 11 & 12)
    - Google Pixel 4 (10 & 11 & 12)
    - Google Pixel 4 XL (10 & 11 & 12)
    - Google Pixel 4a (10 & 11 & 12)
    - Google Pixel 4a 5G (11 & 12)
    - Google Pixel 5 (11 & 12)
    - Google Pixel 5a (11 & 12)
    - Google Pixel 6 (12)
    - Google Pixel 6 Pro (12)
    - 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 G8 ThinQ LM G850l (11)
    - 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 Edge (10 & 11)
    - Motorola Moto G Stylus (10)
    - Motorola Moto G 5g (10)
    - Motorola Moto G 5g Plus (10 & 11)
    - Motorola Moto G Pro (11)
    - 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 Razr 2020 (10 & 11)
    - 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)
    - Motorola Moto Z3 Play (9)
    - 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 & 11)
    - OnePlus 6T (9 & 10 & 11)
    - OnePlus 6T T-Mobile (9 & 10)
    - OnePlus 7 China GM1900 (10 & 11)
    - OnePlus 7 GM1901 (9 & 10 & 11)
    - OnePlus 7 Europe GM1903 (9 & 10 & 11)
    - OnePlus 7 GM1905 (9 & 10 & 11)
    - OnePlus 7 Pro China GM1910 (10 & 11)
    - OnePlus 7 Pro GM1911 (9 & 10 & 11)
    - OnePlus 7 Pro Europe GM1913 (9 & 10 & 11)
    - OnePlus 7 Pro T-Mobile GM1915 (9 & 10 & 11)
    - OnePlus 7 Pro GM1917 (9 & 10 & 11)
    - OnePlus 7 Pro NR Europe GM1920 (9 & 10)
    - OnePlus 7 Pro NR Sprint GM1925 (9 & 10)
    - OnePlus 7T China HD1900 (10 & 11)
    - OnePlus 7T HD1901 (10 & 11)
    - OnePlus 7T Europe HD1903 (10 & 11)
    - OnePlus 7T HD1905 (10 & 11)
    - OnePlus 7T T-Mobile HD1907 (11)
    - OnePlus 7T Pro China HD1910 (10 & 11)
    - OnePlus 7T Pro HD1911 (10 & 11)
    - OnePlus 7T Pro Europe HD1913 (10 & 11)
    - OnePlus 7T Pro HD1917 (10 & 11)
    - OnePlus 7T Pro NR HD1925 (10 & 11)
    - OnePlus 8 China IN2010 (10 & 11)
    - OnePlus 8 India IN2011 (10 & 11)
    - OnePlus 8 Europe IN2013 (10 & 11)
    - OnePlus 8 Global IN2015 (10 & 11)
    - OnePlus 8 Visible IN2015 (10 & 11)
    - OnePlus 8 T-Mobile IN2017 (10 & 11)
    - OnePlus 8 Verizon IN2019 (10)
    - OnePlus 8 Pro China IN2020 (10 & 11)
    - 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 9 India LE2111 (11 & 12)
    - OnePlus 9 Europe LE2113 (11)
    - OnePlus 9 LE2115 (11 & 12)
    - OnePlus 9 TMO LE2117 (11)
    - OnePlus 9 Pro India LE2121 (11 & 12)
    - OnePlus 9 Pro Europe LE2123 (11)
    - OnePlus 9 Pro LE2125 (11 & 12)
    - OnePlus 9 Pro TMO LE2127 (11)
    - OnePlus 9R India LE2101 (11)
    - OnePlus 9RT China MT2110 (11)
    - OnePlus N10 5G Global BE2026 (10 & 11)
    - OnePlus N10 5G Europe BE2029 (10 & 11)
    - OnePlus N10 5G Metro BE2025 (10 & 11)
    - OnePlus N10 5G T-Mobile BE2028 (10 & 11)
    - OnePlus N100 Global BE2011 (10 & 11)
    - OnePlus N100 Europe BE2013 (10 & 11)
    - OnePlus N100 Metro BE2015 (10 & 11)
    - OnePlus N100 T-Mobile BE2012 (10 & 11)
    - OnePlus N200 Global DE2117 (11)
    - OnePlus N200 T-Mobile DE2118 (11)
    - OnePlus Nord India AC2001 (10 & 11)
    - OnePlus Nord Europe AC2003 (10 & 11)
    - OnePlus Nord Global AC2003 (10 & 11)
    - OnePlus Nord 2 India DN2101 (11)
    - OnePlus Nord 2 Europe DN2103 (11)
    - OnePlus Nord CE EB13AA (11)
    - OnePlus Nord CE India EB2101 (11)
    - OnePlus Nord CE Europe EB2103 (11)
    - OPPO A53s Europe (10)
    - OPPO Find X2 Neo Europe CPH2009 (10 & 11)
    - OPPO Neo 7 A33w (5.1)
    - OPPO Neo 7 A1603 (5.1)
    - POCO F2 Pro Europe (10)
    - POCO F2 Pro Global (10 & 11)
    - POCO F3 Europe (11)
    - POCO F3 Global (11)
    - POCO F3 Indoniesia (11)
    - POCO F3 Russia (11)
    - POCO F3 Taiwan (11)
    - POCO F3 Turkey (11)
    - POCO M3 Pro 5G Indonesia (11)
    - POCO X2 (10)
    - POCO X3 NFC Europe (10 & 11)
    - POCO X3 NFC Global (10 & 11)
    - 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)
    - Realme XT RMX1921 (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 K40 China (11)
    - Redmi Note 8 Pro Europe (10 & 11)
    - 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 & 11)
    - 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 A52 4G (11)
    - 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 Lite SM-G770F (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 SM-G780F (11)
    - Samsung Galaxy S20 FE 5G SM-G781B (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 S4 LTE SM-T837A (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 6X China (9)
    - Xiaomi Mi 8 Global (8.1.0 & 9 & 10)
    - Xiaomi Mi 8 Explorer (10)
    - Xiaomi Mi 8 Pro Global (10)
    - Xiaomi Mi 8 Pro Russia (10)
    - Xiaomi Mi 9 China (10 & 11)
    - 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 & 11)
    - Xiaomi Mi 9T Pro China (9 & 10)
    - Xiaomi Mi 9T Pro Europe (10)
    - Xiaomi Mi 9T Pro Global (10 & 11)
    - 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 & 11)
    - 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 11 Lite Indonesia (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 Europe (11)
    - Xiaomi Redmi K20 Pro China (9 & 10 & 11)
    - Xiaomi Redmi K20 Pro Europe (10)
    - Xiaomi Redmi K20 Pro Global (10)
    - Xiaomi Redmi K20 Pro India (10)
    - Xiaomi Redmi K30 Pro China (11)
    - 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)
    31
    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: