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
+20-14Lines changed: 20 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,8 @@ The current release is always attached to the OP of the [module support thread](
12
12
13
13
14
14
## Usage
15
-
After installing the module and rebooting, run the command `props` (as su) in a terminal emulator (you can find a one on [F-Droid](https://f-droid.org/) or in the [Play Store](https://play.google.com/store/apps)), and follow the instructions to set your desired options.
16
-
```
17
-
su
18
-
props
19
-
```
15
+
After installing the module and rebooting, run the command `props` in a terminal emulator (you can find a one on [F-Droid](https://f-droid.org/) or in the [Play Store](https://play.google.com/store/apps)), and follow the instructions to set your desired options. If you use Termux, you'll have to call su before running the command.
16
+
20
17
You can also run the command with options. Use -h for details.
21
18
22
19
@@ -48,27 +45,28 @@ You can find the file to download in your device's forum on XDA Developers (eith
48
45
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.
49
46
50
47
- Sometimes there'll be a build.prop file directly in the zip/package. You'll likely find the fingerprint in there.
51
-
- For some devices you'll have to unpackage the system.img to get to the build.prop file. On Windows, you can use something like [this tool](https://forum.xda-developers.com/showpost.php?p
48
+
- For some devices you'll have to unpackage the system.img to get to the build.prop file. 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).
52
49
- 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.
53
50
- Etc... Experiment, the fingerprint will be in there somewhere.
54
51
55
52
Take a look below for an example of what a device fingerprint looks like.
56
53
57
54
### Custom fingerprints list
58
-
You can add your own fingerprint to the list by placing a file, named `printslist`, in the root of your internal storage with the fingerprint. It needs to be formated as follows:`device name
55
+
You can add your own fingerprint to the list by placing a file, named `printslist`, in the root of your internal storage with the fingerprint. It needs to be formated as follows:`device name=fingerprint`.
59
56
Here's an example:
60
57
```
61
-
Google Nexus 6
58
+
Google Nexus 6=google/shamu/shamu:7.1.1/N8I11B/4171878:user/release-keys
62
59
```
63
60
61
+
64
62
### I still can't pass the ctsProfile check
65
63
If you've picked a certified fingerprint from the provided list, or you're using a fingerprint that you know is certified but still can't pass the ctsProfile check, try one or more of the following:
66
64
- First, do you pass basicIntegrity? If you don't, there's something else going on that this module can't help you with. Take a look under ["Miscellaneous MagiskHide issues"](https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#miscellaneous-magiskhide-issues) below.
67
65
- Go into the script options and move the execution of the boot script to post-fs-data. See ["Boot stage"](https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config#boot-stage) below.
68
66
- Try a different fingerprint (pick one from the provided list).
69
67
- Some ROMs will just not be able to pass the ctsProfile check, if they contain signs of a rooted/modified device that Magisk can't hide. Check in your ROM thread or with the creator/developer.
70
68
- You might have remnants of previous modifications that trigger SafetyNet on your device. A clean install of your system may be required.
71
-
- If you can't get things working, and want help, make sure to provide logs and details. See ["Logs, etc"](https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config#logs-etc) below.
69
+
- If you can't get things working, and want help, make sure to provide logs and details. See ["Logs"](https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config#logs) below.
72
70
73
71
74
72
## Keeping your device "certified"
@@ -86,7 +84,7 @@ The fingerprints list will update without the need to update the entire module.
86
84
87
85
Just run the `props` command and the list will be updated automatically. Use the -nw option to disable or disable it completely in the script settings (see ["Prop script settings"](https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config#prop-script-settings) below). If you've disabled the this setting you can update the list manually in the `Edit device fingerprint` menu.
88
86
89
-
**_Current fingerprints list version - v22_**
87
+
**_Current fingerprints list version - v23_**
90
88
91
89
92
90
## Improved root hiding - Editing build.prop and default.prop
@@ -113,7 +111,7 @@ If you would like to delete a certain prop value from your system, that can be d
113
111
114
112
115
113
## Prop script settings
116
-
There are a couple of persistent options that you can set for the props script. These are currently "Boot stage", "Script colours" and "Fingerprints list check". The options are found under "Script settings" when running the props script. The settings menu can also be opened by using the -s option when running the props script (use -h for details).
114
+
There are a couple of persistent options that you can set for the `props` script. These are currently "Boot stage", "Script colours" and "Fingerprints list check". The options are found under "Script settings" when running the `props` script. The settings menu can also be opened by using the -s option (use -h for details).
117
115
118
116
### Boot stage
119
117
It's possible to move the execution of the boot script from the default late_start service to post-fs-data.d. This is required for the SafetyNet fix and custom props to work on some ROM/device combinations (known: LineageOS 15.1). The reason late_start service is default is that it's best to try to keep the number of scripts running during post-fs-data mode as low as possible, but if late_start service doesn't work, it needs to run in post-fs-data instead.
@@ -122,7 +120,7 @@ It's possible to move the execution of the boot script from the default late_sta
122
120
This option will disable or enable colours for the `props` script.
123
121
124
122
### Fingerprints list check
125
-
This option will disable or enable the automatic updating of the fingerprints list when the `props` script starts. If the fingerprints list check is disabled, the list can be manually updated from within the script, under the `Edit device fingerprint` menu, or with the -f option when running the props script (use -h for details).
123
+
This option will disable or enable the automatic updating of the fingerprints list when the `props` script starts. If the fingerprints list check is disabled, the list can be manually updated from within the script, under the `Edit device fingerprint` menu, or with the -f option (use -h for details).
126
124
127
125
128
126
## Configuration file
@@ -167,7 +165,7 @@ Place a file named `reset_mhpc` in /cache (or /data/cache on A/B devices) and re
167
165
It is possible to use this in combination with the configuration file described above to keep device fingerprint or any other settings intact past the reset. Just make sure to remove any custom props that might have been causing issues from the configuration file.
168
166
169
167
## Logs
170
-
In case of issues, please provide the logs by running the `props` script and selecting the "Collect logs" option (or running the `props` script with the -l command, use -h for details). All the relevant logs, together with the Magisk logs, the stock build.prop file and current prop values will be packaged into a file that'll be stored in the root of the device's internal storage, ready for attaching to a post in the [module support thread](https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228), together with a detailed description of your problem.
168
+
In case of issues, please provide the logs by running the `props` script and selecting the "Collect logs" option (or running the `props` script with the -l option, use -h for details). All the relevant logs and module files, together with the Magisk log, the stock build.prop file and current prop values will be packaged into a file that'll be stored in the root of the device's internal storage, ready for attaching to a post in the [module support thread](https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228), together with a detailed description of your problem.
171
169
172
170
The logs will also automatically be saved to the root of the device's internal storage if there's an issue with the module scripts.
173
171
@@ -186,6 +184,13 @@ If you can't run the `props` script for some reason, the logs are also stored in
186
184
187
185
188
186
## Changelog
187
+
### v2.3.5
188
+
- Fixed issue with busybox version detection.
189
+
- Fixed the documentation. Some parts had been accidentally deleted. Oops...
190
+
- Improved log collecting.
191
+
- Added and updated fingerprints for the Xiaomi Mi Note 2 and Redmi Note 5A Lite, list v23.
192
+
- Minor improvements here and there. Hopefully I haven't broken something this time...
193
+
189
194
### v2.3.4
190
195
- Updated for Busybox v1.29.1. Thank you @osm0sis.
191
196
- Bugfixes. Because I'm blind.
@@ -301,7 +306,7 @@ If you can't run the `props` script for some reason, the logs are also stored in
301
306
302
307
303
308
## Current fingerprints list
304
-
### List v22
309
+
### List v23
305
310
- Asus Zenfone 2 Laser (6.0.1)
306
311
- Asus ZenPad S 8.0 (6.0.1)
307
312
- Google Nexus 4 (5.1.1)
@@ -405,6 +410,7 @@ If you can't run the `props` script for some reason, the logs are also stored in
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.
@@ -1822,6 +1821,7 @@ if [ "$ISSUECHK" == 1 ]; then
1822
1821
collect_logs "issue"
1823
1822
reboot_fn "${ISSUETXT}\n\n If the issue persists after a reboot,\n please report the issue, ${R}with logs!${C}\n\n Logs have automatically been saved\n to your internal storage\n ${R}(propslogs.tar.gz)${C}.\n\n If the automatic collection failed,\n please collect the logs manually.\n\n ${G}See the documentation for details.${N}""reset-script"
0 commit comments