You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-8Lines changed: 14 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,9 +100,11 @@ When using a Treble GSI ROM with a stock vendor partition, it is possible to use
100
100
For some devices, if the fingerprint is for an Android build after March 16th 2018, it is necessary to use a security patch date that matches the fingerprint used. For the module provided fingerprints this is done automatically, but if you enter a fingerprint manually you will have to update the security patch date yourself (if they don't already match). Use the [Custom props](https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#changeset-custom-prop-values) function of this module to change `ro.build.version.security_patch` to the desired date.
101
101
102
102
### Can I use any fingerprint?
103
-
It's possible to use any fingerprint that's certified for your device. It doesn't have to match, either device or Android version. If you don't use a fingerprint for your device, the device might be percieved as the device that the fingerprint belongs to, in certain situations (Play Store, etc). The Android version doesn't matter much, and if you're using a ROM with an Android version much newer than what is officially available for your device, you are going to have to use an older fingerprint if you want to use the one for your device. But, like already stated, that doesn't really matter.
103
+
It's usually possible to use any fingerprint that's certified for your device. It doesn't have to match, either device or Android version. If you don't use a fingerprint for your device, the device might be percieved as the device that the fingerprint belongs to, in certain situations (Play Store, etc). The Android version doesn't matter much, and if you're using a ROM with an Android version much newer than what is officially available for your device, you are going to have to use an older fingerprint if you want to use the one for your device. But, like already stated, that doesn't really matter (most of the time, there might of course be exceptions).
104
104
105
105
### Finding a certified fingerprint
106
+
If you need a certain fingerprint from a device, here are a few tips on how to find it. Also remember that you might need to get the security patch date that corresponds to the fingerprint you find (see [Matching the Android security patch date](https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf#matching-the-android-security-patch-date) above).
107
+
106
108
#### The getprop method
107
109
If you don't want to use one of the provided fingerprints, you can get one for your device by running the getprop command below on a stock ROM/firmware/factory image that fully passes SafetyNet.
108
110
```
@@ -122,7 +124,7 @@ You can find the file to download in your device's forum on XDA Developers (eith
122
124
Once you have the file downloaded, there are several different ways that the fingerprint can be found. In all cases you'll have to access the file somehow, and in most cases it's just a matter of unpackaging it. After that it depends on how the package is constructed.
123
125
124
126
- Sometimes there'll be a build.prop file directly in the zip/package. You'll likely find the fingerprint in there.
125
-
- For some devices you'll have to unpackage the system.img to get to the build.prop or default.prop file, where you'll find the info you want. On Windows, you can use something like [this tool](https://forum.xda-developers.com/showpost.php?p=57742855&postcount=42). You'll also find more info in the [main thread for that post](https://forum.xda-developers.com/android/software-hacking/how-to-conver-lollipop-dat-files-to-t2978952).
127
+
- For some devices you'll have to unpack the system.img to get to the build.prop or default.prop file, where you'll find the info you want.This can sometimes be done with a simple archive app/program, but sometimes more advanced utilities are needed. On Windows, you can use something like [this tool](https://forum.xda-developers.com/showpost.php?p=57742855&postcount=42). You'll also find more info in the [main thread for that post](https://forum.xda-developers.com/android/software-hacking/how-to-conver-lollipop-dat-files-to-t2978952).
126
128
- Other times you'll find the fingerprint in META-INF\com\google\android\updater-script. Look for "Target:" and you'll likely find the fingerprint there.
127
129
- Etc... Experiment, the fingerprint will be in there somewhere.
128
130
@@ -169,7 +171,7 @@ Just run the `props` command and the list will be updated automatically. Use the
169
171
170
172
If you already have a device fingerprint set by the module, and it has been updated in the current fingerprints list, it will be automatically updated when the prints list gets an update. Just reboot to apply. This function can be turned of in the script settings (see ["Prop script settings"](https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config#prop-script-settings) below)
171
173
172
-
**_Current fingerprints list version - v42_**
174
+
**_Current fingerprints list version - v43_**
173
175
174
176
175
177
## Please add support for device X
@@ -566,7 +568,7 @@ Releases from v2.4.1 are compatible with Magisk v17+.
566
568
567
569
568
570
## Current fingerprints list
569
-
### List v42
571
+
### List v43
570
572
- Asus Zenfone 2 Laser (6.0.1)
571
573
- Asus Zenfone 4 Max (7.1.1)
572
574
- Asus ZenPad S 8.0 (6.0.1)
@@ -580,7 +582,7 @@ Releases from v2.4.1 are compatible with Magisk v17+.
580
582
- Google Nexus 7 2012 LTE (5.1.1)
581
583
- Google Nexus 7 2013 WiFi (6.0.1)
582
584
- Google Nexus 7 2013 LTE (6.0.1)
583
-
- Google Nexus 9 WiFi ()
585
+
- Google Nexus 9 WiFi (7.1.1)
584
586
- Google Nexus 9 LTE (7.1.1)
585
587
- Google Nexus 10 (5.1.1)
586
588
- Google Pixel (9)
@@ -597,15 +599,18 @@ Releases from v2.4.1 are compatible with Magisk v17+.
597
599
- Huawei Honor 9 (8.0.0)
598
600
- Huawei Mate 10 (8.0.0)
599
601
- Huawei Mate 10 Pro (8.0.0)
602
+
- Huawei Mate 20 Pro (9)
600
603
- Huawei P8 Lite (8.0.0)
601
604
- Huawei P9 (7.0)
602
605
- Huawei P9 Lite (7.0)
603
606
- Huawei P9 Plus (7.0)
607
+
- Huawei P20 (9)
604
608
- Huawei P20 Pro (8.1.0)
605
609
- LeEco Le Pro3 (6.0.1)
606
610
- LG G2 BS980 (5.0.2)
607
611
- LG G4 H812 (6.0)
608
612
- LG G5 H850 (8.0.0)
613
+
- LG G6 H870 (7.0)
609
614
- LG V30 H930 (8.0.0)
610
615
- Motorola Moto C Plus (7.0)
611
616
- Motorola Moto E4 (7.1.1)
@@ -628,18 +633,19 @@ Releases from v2.4.1 are compatible with Magisk v17+.
628
633
- OnePlus 3 (8.0.0)
629
634
- OnePlus 3T (8.0.0)
630
635
- OnePlus 5 (8.1.0)
631
-
- OnePlus 5T (8.1.0)
636
+
- OnePlus 5T (9)
632
637
- OnePlus 6 (9)
633
638
- OnePlus 6T (9)
634
639
- Razer Phone (8.1.0)
635
640
- Razer Phone 2 (8.1.0)
641
+
- Samsung Galaxy A5 2015 (6.0.1)
636
642
- Samsung Galaxy A5 2017 (8.0.0)
637
643
- Samsung Galaxy A8 Plus (7.1.1)
638
644
- Samsung Galaxy Grand Prime (5.0.2)
639
645
- Samsung Galaxy J2 (5.1.1)
640
646
- Samsung Galaxy J3 (5.1.1)
641
647
- Samsung Galaxy J5 2015 (6.0.1)
642
-
- Samsung Galaxy J5 (7.1.1)
648
+
- Samsung Galaxy J5 2016 (7.1.1)
643
649
- Samsung Galaxy J5 Prime (7.0)
644
650
- Samsung Galaxy J7 2017 (8.1.0)
645
651
- Samsung Galaxy J7 Prime (6.0.1)
@@ -695,7 +701,7 @@ Releases from v2.4.1 are compatible with Magisk v17+.
Copy file name to clipboardExpand all lines: module.prop
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
id=MagiskHidePropsConf
2
2
name=MagiskHide Props Config
3
-
version=v3.0.2-v42
3
+
version=v3.0.2-v43
4
4
versionCode=39
5
5
author=Didgeridoohan
6
6
description=Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Edit prop files for better root hiding. Set/reset prop values set by MagiskHide. Change any prop values easily, and set your own custom props.
0 commit comments