Skip to content

Commit 79aed5f

Browse files
Update README.md
1 parent 1ba97eb commit 79aed5f

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,11 @@ It's usually possible to use any fingerprint that's certified for your device. I
105105
### Finding a certified fingerprint
106106
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).
107107

108+
Also make sure that you get the actual device fingerprint, since there might be props that look similar to what you need. Here's an example, taken from a Google Nexus 6 (named Shamu):
109+
```
110+
google/shamu/shamu:7.1.1/N8I11B/4171878:user/release-keys
111+
```
112+
108113
#### The getprop method
109114
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.
110115
```
@@ -128,8 +133,6 @@ Once you have the file downloaded, there are several different ways that the fin
128133
- 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.
129134
- Etc... Experiment, the fingerprint will be in there somewhere.
130135

131-
Take a look below for an example of what a device fingerprint looks like.
132-
133136
#### The firmware.mobi method
134137
Sometimes you can also find up to date and certified fingerprints at [firmware.mobi](https://desktop.firmware.mobi/).
135138

0 commit comments

Comments
 (0)