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

[rpiquet]

Fingerprints list updated to v110

Got a bunch of prints submitted over the past couple of weeks. So here goes... Lot's of thanks, as usual, to those whom help me keep the list somewhat updated and relevant. This time around those awesome people are (in no particular order) @red_lnn, @Johnny Eng, @dron39, @Some_Random_Username, @GtrCraft and @Kovacs-.

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

New
OnePlus 8T China
OnePlus N100 Europe
OnePlus N10 5G Europe
Samsung Galaxy A70
Samsung Galaxy Note 20 Ultra 5G
Samsung Galaxy S20 FE 5G

Updated
OnePlus 5
OnePlus 5T
OnePlus 7 (several variants)
OnePlus 7 Pro (several variants)
OnePlus 7T (several variants)
OnePlus 7T Pro (several variants)
OnePlus 8 (several variants)
OnePlus 8 Pro (several variants)
OnePlus 8T (several variants)
OnePlus Nord (several variants)
POCO X3 NFC
Xiaomi Mi 10 China

Hi Didgeridoohan, Any chance to add y device Samsung Galaxy M31 (SM-315F) into fingerprint list?
I tested it with Samsung M21 (SM-215F) and it didn't work.

 

[Didgeridoohan]

Hi Didgeridoohan, Any chance to add y device Samsung Galaxy M31 (SM-315F) into fingerprint list?
I tested it with Samsung M21 (SM-215F) and it didn't work.

First, there's always a chance a new device will be added to the list. But:

Magisk-Modules-Repo/MagiskHidePropsConf

MagiskHidePropsConf. Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

Second, if you tried one of the certified prints included in the module and still couldn't pass CTS there's a really good chance that there is something else going on. Take a look here for more tips:

Magisk-Modules-Repo/MagiskHidePropsConf

MagiskHidePropsConf. Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

 

[Displax]

Pixel`s update:

Pixel 2=google/walleye/walleye:11/RP1A.201005.004.A1/6934943:user/release-keys__2020-10-05
Pixel 2 XL= google/taimen/taimen:11/RP1A.201005.004.A1/6934943:user/release-keys__2020-10-05 
Pixel 3=google/blueline/blueline:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 3a=google/sargo/sargo:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 3a XL=google/bonito/bonito:11/RQ1A.201205.003/6906706:user/release-keys__2020-12-05
Pixel 4=google/flame/flame:11/RQ1A.201205.008/6943376:user/release-keys__2020-12-05
Pixel 4 XL=google/coral/coral:11/RQ1A.201205.008/6943376:user/release-keys__2020-12-05
Pixel 4a=google/sunfish/sunfish:11/RQ1A.201205.008/6943376:user/release-keys__2020-12-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ1A.201205.011/6966805:user/release-keys__2020-12-05
Pixel 5=google/redfin/redfin:11/RQ1A.201205.011/6966805:user/release-keys__2020-12-05

 

[ultradj83]

Hello there.

On Galaxy S10+ (SM-G975F/DS), setting fingerprint from Galaxy A3 2015 (SM-A300FU) to revert to basic key attestation (other Samsungs don't work), there's no more chance to call Google Assistant by "Hey Google" voice match when screen is off.
The option is not available in the settings, maybe because it's not supported on SM-A300FU.

Any workarounds?

Regards

 

[Didgeridoohan]

Hello there.

On Galaxy S10+ (SM-G975F/DS), setting fingerprint from Galaxy A3 2015 (SM-A300FU) to revert to basic key attestation (other Samsungs don't work), there's no more chance to call Google Assistant by "Hey Google" voice match when screen is off.
The option is not available in the settings, maybe because it's not supported on SM-A300FU.

Any workarounds?

Regards

Pick a device manually from the included list that does have that feature...

 

[ultradj83]

Unfortunately any other devices I tried fails in reverting to basic key attestation.
I don't know if this is normal, maybe all other Samsung models, not only the latest, support hardware key attestation...

 

[Didgeridoohan]

Unfortunately any other devices I tried fails in reverting to basic key attestation.
I don't know if this is normal, maybe all other Samsung models, not only the latest, support hardware key attestation...

Any device that shipped with Android 8+ should in theory have hardware backed key attestation (that's when Google started enforcing it), but there'll also be earlier models that have it.

For a while now, from what we've seen, it hasn't mattered what device you pick as long as it is different from the actual device you're using.

I can't say what's going on with your device, but it's possible that Google has changed something again. That's not something I can test or verify though, since none of my devices uses hardware backed key attestation.

There's also a possibility that something went wrong with they module, of course, so a set of logs from when you have another model set and SafetyNet fails could be useful.

 

[bartleby999]

Unfortunately any other devices I tried fails in reverting to basic key attestation.
I don't know if this is normal, maybe all other Samsung models, not only the latest, support hardware key attestation...

Have you tried a custom setting - Change ro.product.model to a Galaxy S10 (SM-G973F) that is the closest device to yours so should maintain all functions.

That's all I needed to do on my Galaxy Tab S6 to force Basic.

 

[Didgeridoohan]

Fingerprintslist updated to v111

Here's a bunch of updated and a couple of new fingerprints, provided by these awesome individuals: @GtrCraft, @carlos974, @IanWorthington, @garylawwd and @Displax. Thank you!

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

New
ASUS ZENFONE 7 Pro Europe
POCO X3 NFC Europe
Samsung Galaxy Tab E 9.6

Updated
Google Pixel 2-5 (all variants)
Xiaomi Mi A3 Global

 

[isoladisegnata]

How edit for my app banking? Dont hide for me

 

[Didgeridoohan]

How edit for my app banking? Dont hide for me

I think you've ended up in the wrong thread... General app hiding questions are better suited for the Magisk general support thread or one of the many "bank app detects root" threads.

Start by taking a look here, and then try to find a more suitable thread if you need further help:

Basics:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

 

[limuc]

Hi Didgeridoohan,

thank you for your great work. I also use the program to be able to use Gpay under root, unfortunately I can no longer do this under Android 11 from December (Pixel 4a) with MagiskHide 110, so I removed root and closed the bootloader to use Gpay.
Now my question: Do you think that the new 111 variant enables me to get Root AND GPay again?
A second question: Although my device is no longer rooted and the bootloader is closed and I have reflashed the stock ROM (with -w), is the phone shown in the Win Explorer as Nexus 5?

Thanks for any help!

limuc

 

[Didgeridoohan]

Hi Didgeridoohan,

thank you for your great work. I also use the program to be able to use Gpay under root, unfortunately I can no longer do this under Android 11 from December (Pixel 4a) with MagiskHide 110, so I removed root and closed the bootloader to use Gpay.
Now my question: Do you think that the new 111 variant enables me to get Root AND GPay again?
A second question: Although my device is no longer rooted and the bootloader is closed and I have reflashed the stock ROM (with -w), is the phone shown in the Win Explorer as Nexus 5?

Thanks for any help!

limuc

Even though GPay was failing, were you still passing SafetyNet? If so, the module was working just as intended and GPay was failing for other reasons (here's a collection of resources for GPay: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Google_Pay). The v111 fingerprints list update would make no difference really, since it just adds the latest device fingerprints. The older prints used in v110 are still certified and would work just fine as well...

And about showing as a Nexus 5 in Windows Explorer, that's likely just a cached value on your PC.

 

[limuc]

Thanks, SafetyNet is passing but 'Play Protect Certification' is negativ.

The showing Nexus 5 is little mysterious, deleting all caches on two win-machines there is no effect, but on my Linux-mint there is showing Pixel 4a. Tomorrow I will test on an other win-machine.

 

[Didgeridoohan]

Thanks, SafetyNet is passing but 'Play Protect Certification' is negativ.

The showing Nexus 5 is little mysterious, deleting all caches on two win-machines there is no effect, but on my Linux-mint there is showing Pixel 4a. Tomorrow I will test on an other win-machine.

I didn't mean if SafetyNet is passing now, but before you wiped everything. GPay can fail even when a fully passing SafetyNet, and this module only helps with SN.

Play Store certification can usually be fixed by clearing data for the Play Store.

 

[pndwal]

Thanks, SafetyNet is passing but 'Play Protect Certification' is negativ.

The showing Nexus 5 is little mysterious, deleting all caches on two win-machines there is no effect, but on my Linux-mint there is showing Pixel 4a. Tomorrow I will test on an other win-machine.

Guess you're meaning before restoring stock/ locking bootloader Play Protect showed Not Certified? As stated, clearing Play Store data would likely have fixed this...

Re Nexus 5, likely you set up windows connection while MHPC was configured for Force BASIC key Attestation using default setting, which spoofs Nexus 5 in Model prop(s) on Google devices. I imagine windows just retains original model associated with device ID... Uninstalling and reinstalling the drivers may have more effect than clearing caches... PW

 

[limuc]

Good news: I tried again to bring Root and Gpay together on Pixel 4a. It worked.
However, it only worked if I approved my device (Pixel 4a) as 'Nexus 5' (as suggested by your system), if I took the correct name, it didn't work.
Now with 'Nexus 5', 'SaftyNet' and 'Play Protect Certificate' are positive. The setup of PayPal in Gpay worked, tomorrow I'll see if it works in real life.
Thanks again!

 

[limuc]

I imagine windows just retains original model associated with device ID... Uninstalling and reinstalling the drivers may have more effect than clearing caches...

Thanks, I will try it!

 

[pndwal]

Good news: I tried again to bring Root and Gpay together on Pixel 4a. It worked.
However, it only worked if I approved my device (Pixel 4a) as 'Nexus 5' (as suggested by your system), if I took the correct name, it didn't work.
Now with 'Nexus 5', 'SaftyNet' and 'Play Protect Certificate' are positive. The setup of PayPal in Gpay worked, tomorrow I'll see if it works in real life.
Thanks again!

Good result.

Nb. You must NOT select the actual model for Force BASIC key Attestation option as it's a simple MISMATCH with actual model that causes fallback to BASIC Attestation. (Using actual model will do nothing.)

It's therefore best to manually select a close/similar model to spoof from same Manufacturer for compatibility with model/OEM specific functionality.

For Pixel 4a, I'd be choosing Pixel 4XL etc, even though default Nexus 5 value works. It's not about passing only; that's the easy part. Using anything other than actual model (even 'creamcheese') will cause mismatch and therefore fallback to BASIC, but this will do nothing for OEM's special features/functions. PW

 

[41rw4lk]

I can't get props to run. I've uninstalled busybox ndk and propshide modules, deleted the folder from data and uninstalled magisk manager. I did a clean install of magisk manager, and both modules (rebooting in between both installs), but nothing. I have root in terminal, but when I run the props command it just says 'inaccessible or not found". I've attached the propshide logs and magisk logs.

I'm running a Pixel 3a XL (bonito) btw.