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

[ipdev]

Thanks so much for your detailed reply. Unfortunately, my device never passed safetynet after I rooted it, so the props method is not an option. I'm not really familiar with how to extract the fingerprint from a firmware download. I see what you mean about 1.1.1 failing. However, i'm using a rooted firmware with 1.1.0 which seems to download from their website just fine. If you are to find it without too much trouble I'd be grateful. Thanks in advance!

http://fiio-file.fiio.net/M11-ota-1.1.0.zip

EDIT: I'm making progress. I figured out how to identify the fingerprint. Now, I'm stuck because it fails. Based on the documentation, i'm guessing this is because the security patch date is incorrect. I tried to change it to the release date of 12/30/20, but this didn't work. Is there a way to tell this from the package what date to use? Thanks!

Did it pass before you rooted it?

If the only modification you did was to root a stock rom, then the fingerprint and security date will still be correct.

Make sure to enable MagiskHide in the Magisk app.
Settings-> Toggle MagiskHide on.

If the device is not Google certified, the stock fingerprint and security date will not be certified.

Using this module to set the fingerprint and security date to the same will give the same result.
You will have to pick a certified fingerprint with the matching security date.
The fingerprints included in this module have the matching security dates if necessary.

--

I downloaded an took a look at the M11 v1.1.0 OTA.
Used the recovery image from the OTA to pull the props.

It failed SafetyNet for me but.. ¯\_(ツ)_/¯
If you want to try, rename the attached file to printslist and copy it to /sdcard/
Custom fingerprints list GitHub - Link

--

A bit OT for this thread but, it would help me narrow something down.

Could you revert the changes you made, no need to unroot, and then reboot.
Then using a terminal app or an adb shell session.

getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g' >/sdcard/Download/m11-getprop.props;

Then attach the m11-getprop.props file to a post or send me a link to it.
The generated file should be in your Download directory.

It will help me fix an issue in my mHideGP script.
Even though this device is not on the certified.list, it triggered the certified.list MHIDE print configuration for some reason??

Interesting device for sure.

Cheers.

 

[Didgeridoohan]

@gfrank227 Like @ipdev already have told you, that device is not on Google's list of certified devices, and considering that both you and @ipdev have tested the print without success it's quite clear to me that there's no use for further testing... That devices print won't pass CTS. Another big hint is that it's using test-keys. Certified devices use release-keys.

And it's got nothing to do with the security patch date. That print is from a build that is old enough for that not to matter at all.

To pass CTS you need to pick a different device's fingerprint, one that is certified by Google. The included list has 500+ prints to choose from, so take your pick. Usually it's best to pick a device that's as close to yours as possible, but in not quite sure what that would be in this case. Look around and test a print the you think looks good.

Caveat: it's also perfectly possible that just changing the device fingerprint isn't enough to pass SafetyNet. There are many things that can trigger both basic integrity and the CTS profile. If you're still failing after picking a print from the included list, take a look here for more guidance:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

 

[gfrank227]

@gfrank227 Like @ipdev already have told you, that device is not on Google's list of certified devices, and considering that both you and @ipdev have tested the print without success it's quite clear to me that there's no use for further testing... That devices print won't pass CTS. Another big hint is that it's using test-keys. Certified devices use release-keys.

And it's got nothing to do with the security patch date. That print is from a build that is old enough for that not to matter at all.

To pass CTS you need to pick a different device's fingerprint, one that is certified by Google. The included list has 500+ prints to choose from, so take your pick. Usually it's best to pick a device that's as close to yours as possible, but in not quite sure what that would be in this case. Look around and test a print the you think looks good.

Caveat: it's also perfectly possible that just changing the device fingerprint isn't enough to pass SafetyNet. There are many things that can trigger both basic integrity and the CTS profile. If you're still failing after picking a print from the included list, take a look here for more guidance:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

OK good to know. I had tried a different fingerprint which passed SN but was causing other problems with Netflix. I tried another device which uses the same Android version, 7.0. In theory, this should be OK, and it did pass the SN. Thanks for the info regarding the test-keys.

 

[Displax]

Those two I had some interesting issues with... They broke the resetprop tool on my test device and the prints didn't get set at all. I got the Android 10 print to pass on a different device, but the 9 print didn't.

Is there still issues with it?
Anyway, actual print for Mi A3 Europe:
Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.3.0.RFQEUXM:user/release-keys__2021-01-05

P.S. Discussion question about old prints from different android versions for one device... Does it really exists any practical or other sense to store them? I don't see any reason (exclude historical) for this, whatever i think.
Printlist could be much cleaner (and less "heavy") when it has only latest prints for latest rom build.
Yes, I remember my "bomb" with old prints, but is was only side effect

 

[Didgeridoohan]

Is there still issues with it?
Anyway, actual print for Mi A3 Europe:
Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.3.0.RFQEUXM:user/release-keys__2021-01-05

P.S. Discussion question about old prints from different android versions for one device... Does it really exists any practical or other sense to store them? I don't see any reason (exclude historical) for this, whatever i think.
Printlist could be much cleaner (and less "heavy") when it has only latest prints for latest rom build.
Yes, I remember my "bomb" with old prints, but is was only side effect

I had forgotten about that, but now that you mentioned it I remember why that particular print is causing issues and breaking the resetprop tool.

There's a character limit on prop values that you set with the setprop command, and thus also resetprop. 91 characters to be more precise, and the print for that device is 93 characters long (all three variants). I've brought that up with John previously, and I don't think there was any reason why the character limit for resetprop couldn't be lifted (this is a bit outside my area and I can't give any details on why the limit is there and so on, but if someone wants to go looking they can surely find something on this in the AOSP and Magisk code). Seems like it was forgotten about at some point though (not really high priority). I'll bring it up again...

Regarding historical prints, I have been playing with an idea to keep two prints lists. One with only the latest, and one with previous prints (just for completeness and giving whomever want it the possibility to use an old print). That would, as you say, keep the prints list a lot cleaner. I might revisit that idea...

 

[ineedroot69]

So i was reading this thread back from 2018 and they recommend this module and also said if i pass safetynet test i would most likely be "play protect certified" too?? i want to fixed this play protect not certified issue so i just need my previous valid release-keys is that correct??

 

[Didgeridoohan]

So i was reading this thread back from 2018 and they recommend this module and also said if i pass safetynet test i would most likely be "play protect certified" too?? i want to fixed this play protect not certified issue so i just need my previous valid release-keys is that correct??

If you pass the CTS profile you can get your Play Store to be certified (might have to clear data for it first though).

If you're using a custom ROM you need to use a certified fingerprint (there are loads of them included in the module, and in the docs you can find info on how to get one if there isn't one for your particular device). And, if your device uses hardware backed key attestation you need the new Universal SafetyNet Fix.
Some reading about that:
https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1

And some further reading on what's needed to pass SafetyNet:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

 

[ineedroot69]

holy fvk ahaha let's go would recommend this module 10/10

 

[FivEawE]

Xiaomi Redmi Note 8 Pro (begonia) Europe A10 - Update

[ro.product.manufacturer]: [Xiaomi]
[ro.product.model]: [Redmi Note 8 Pro]
[ro.build.fingerprint]: [Redmi/begonia_eea/begonia:10/QP1A.190711.020/V12.0.4.0.QGGEUXM:user/release-keys]
[ro.build.version.security_patch]: [2021-02-01]

 

[Didgeridoohan]

Fingerprints list updated to v119

Another batch of prints submitted, tested and added to the list. Thank you @Displax, @marat2509 and @FivEawE.

The list will update when you run the props command, or if you have disabled automatic updates by using the -f option or from the "Edit device fingerprint" menu.

New
Xiaomi Redmi 9

Updated
Nvidia Shield TV 2015
Nvidia Shield TV 2015 Pro
Nvidia Shield TV 2017
Nvidia Shield TV 2019
Nvidia Shield TV 2019 Pro
Redmi Note 8 Pro Europe

 

[Displax]

Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 3a=google/sargo/sargo:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 3a XL=google/bonito/bonito:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4=google/flame/flame:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4 XL=google/coral/coral:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4a=google/sunfish/sunfish:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 5=google/redfin/redfin:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05

 

[Didgeridoohan]

Fingerprints list updated to v120

@Displax is back with this month's Pixel prints. Yay!

The list will update when you run the props command, or if you have disabled automatic updates by using the -f option or from the "Edit device fingerprint" menu.

Updated
Google Pixel 3 - 5, all variants

 

[73sydney]

Fingerprints list updated to v120

@Displax is back with this month's Pixel prints. Yay!

The list will update when you run the props command, or if you have disabled automatic updates by using the -f option or from the "Edit device fingerprint" menu.

Updated
Google Pixel 3 - 5, all variants

At least you didnt Squee....

 

[Displax]

Razer Phone 2
razer/cheryl2/aura:9/P-SMR6-RC001-RZR-201022/3201:user/release-keys_2020-11-05

 

[Displax]

Fixes:
Rename: "Xiaomi MI 10 Europe" >>> "Xiaomi Mi 10 Europe"
Rename: "Nvidia Shield K1" >>> "Nvidia Shield Tablet K1"
Rename: "Nvidia Shield Tablet" >>> "Nvidia Shield Tablet WiFi"

Add:

Nvidia Shield Tablet LTE (7.0):NVIDIA:SHIELD Tablet=nvidia/wx_un_do/shieldtablet:7.0/NRD90M/1928188_1065.2559:user/release-keys

Update:

Nvidia Shield Tablet WiFi (7.0):NVIDIA:SHIELD Tablet=nvidia/wx_na_wf/shieldtablet:7.0/NRD90M/1928188_1065.2559:user/release-keys

 

[glothatik]

Hi all,

That device had not fingerprint yet:

Samsung [SM-A510F] (7.0):samsung:SM-A510F=samsung/a5xeltexx/a5xelte:7.0/NRD90M/A510FXXS8CSF3:user/release-keys__2019-07-01

# Samsung SM-A510F [Build Date - Jun 26 2019]
# ro.bootimage.build.fingerprint=samsung/a5xeltexx/a5xelte:7.0/NRD90M/A510FXXS8CSF3:user/release-keys
# ro.build.version.security_patch=2019-07-01
#
# ro.build.version.release=7.0
# ro.build.version.sdk=24
# ro.product.device=a5xelte
# ro.product.brand=samsung
# ro.product.manufacturer=samsung
# ro.product.model=SM-A510F
# ro.product.name=a5xeltexx
# ro.build.product=a5xelte

 

[Didgeridoohan]

Razer Phone 2
razer/cheryl2/aura:9/P-SMR6-RC001-RZR-201022/3201:user/release-keys_2020-11-05

Quick heads-up on this one. I had a couple of minutes to test the last few submitted prints and they all passed except for this one. I even checked against Android Dumps and it matches the data there so I guess it isn't certified...

 

[Displax]

I even checked against Android Dumps and it matches the data there so I guess it isn't certified...

Strange. Because it's official ROM. Maybe certification recall.

Can you, please, test this one?
razer/cheryl2/aura:9/P-SMR7-RC003-RZR-210107/3225:user/release-keys__2021-02-05

 

[Didgeridoohan]

Strange. Because it's official ROM. Maybe certification recall.

Can you, please, test this one?
razer/cheryl2/aura:9/P-SMR7-RC003-RZR-210107/3225:user/release-keys__2021-02-05

Yup, that one works.

 

[T1tino]

Please add
LG k20 Plus
MP260
lv517
MetroPCS/lv517_mpcs_us/lv517:7.0/NRD90U/1833409570571:user/release-keys__2018-12-01