[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - Forked and ready to go live again!

[vithuselservices]

Hi All,

This is a revival of the original MagiskHide Props Config module.

I've been working on this all day and its finally ready to start taking fingerprint submissions so i thought id open a new thread here to reach more people.

Disclaimers -

• I have copied and pasted from the original thread with a few changes where relevant.
• I fully intend on handing this back over to @Didgeridoohan if they ever decide to take the reign again. Im simply just stepping in to fill a much needed void in the custom rom space.
• As with any Magisk Module. This comes with risk. You can very easily break your device. I myself have a Samsung Note 10 Plus so i will be testing on my own device prior to making any releases.
• I have no intention of collecting donations at all. This project depends upon the community more then myself.

What's this?
If you are wondering anything about what this module can do and how it works or if you're experiencing issues of some kind, take a look at the documentation on GitHub and see if whatever you wonder about is covered there (most things are). If they're not, look again and then post in the thread.

If you're wondering about the latest and greatest after an update, take a look at the changelog and accompanying release notes.

Prerequisites

• Magisk v20.4+.

Installation
Install through the Magisk Manager Downloads section. Or, download the zip (attached below) and install through the Magisk Manager -> Modules, or from recovery. Combine a recovery installation with the use of the module configuration file and you can set up a certified fingerprint and any custom props you want without first booting on a clean flash. Instant settings.

Usage
After installing and rebooting, run the command props in terminal (you can find a terminal emulator on F-Droid or in the Play Store), and then follow the instructions to set your desired options (also see the documentation on GitHub). You might have to call su before running the command.

You can also run the command with options. Use -h for details.

Submitting Fingerprints
Now this is where you lovely people come in. There is no way ill be able to spend all my time gathering fingerprints and i have absolutely no intention of doing so. However i've made it very easy to submit your fingerprints in a way that i can process them with very little effort.
How to find your fingerprint
Submit your Fingerprint

Source
GitLab - All scripts are completely opensource and your free to download it yourself directly from source

Download Repository
MHPC Releases & Archive

Support
Discord Invite Link - For the time being i will only be able to support users either on here and Discord.

Credits and mentions
There are lots of people to thank for this project. I've included the main two below
@topjohnwu, for Magisk
@Didgeridoohan, for creating MHPC and maintaining it for so long

Original Module Thread
Link to Original Thread

 

[devnoname120]

@vithuselservices You forgot to attach the module in your post.

 

[vithuselservices]

@vithuselservices You forgot to attach the module in your post.

Hi. There haven't been any official releases just yet. ETA for the first beta releases are the end of this week but that's only if everything goes well and I see no issues on my tests. So far there are only Experimental releases that i have stopped uploading to the release fileshare.

Once the new build is ready I can begin working on integrating new Fingerprints from the submissions that have been given to me.

 

[devnoname120]

@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.

Any ideas how to fix this issue?

Edit: typing `su` before solves the issue..

 

[rocketda7331]

@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.

Any ideas how to fix this issue?

type su first

 

[dickta]

I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.

Is it something that I missed from the prop values? I cannot understand this behavior.

Any advice?

 

[neelchauhan]

Is this project still alive? I haven't seen any updates for a few weeks. Did OP just ghost us?

 

[vithuselservices]

Post has been removed by a Moderator

Hi.

This is not the case. Can you please remove this post as its highly inaccurate?

Im still here. Apologies for the lack of updates.

Ive had a lot of work come in so its delayed things somewhat but the final version is indeed ready.

Theres a final bit of testing to be conducted prior to making a official release as the last thing i want is bricked phones or settings being dropped.

The first beta release will be out by sunday.

In future can you please give more then 2 hours prior to making such a claim? Its considered rude to make such a claim without reaching out to a dev with sufficient time to reply. Your welcome to fork it yourself. Thats your right. But be more thoughtful when you spread messages like this

 

[vithuselservices]

I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.

Is it something that I missed from the prop values? I cannot understand this behavior.

Any advice?

Hi.

I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.

 

[dickta]

Hi.

I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.

I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.

I'm not a dev but if I can help, I'm sure I will.

 

[vithuselservices]

I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.

I'm not a dev but if I can help, I'm sure I will.

How odd.

Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?

 

[dickta]

How odd.

Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?

Absolutely! I own all the 3 phones , I also did a full stock rom recovery on all to run the getprop command to make sure the fingerprint and the patch date is correct.

Ohh and almost forgot: thank you!

 

[vithuselservices]

Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.

Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.

 

[dickta]

Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.

Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.

I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.

After that it seems the module can't access for some files and it not really working after that.

I attached a log to help.

 

[vithuselservices]

I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
View attachment 5759567
After that it seems the module can't access for some files and it not really working after that.
View attachment 5759575
View attachment 5759571
I attached a log to help.

How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!

 

[chewy74]

How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!

Same for me. After assigning a fingerprint, reboot will clear it and it reverts back to original

 

[vithuselservices]

This is still being looked into.

Its coming to the end of the year so im having to process a lot of projects to completion in my day job. Sorry for the delay!

 

[vithuselservices]

New Beta Build is up. This should fix the install issues users have been having.
Ill be uploading a load of fingerprints very soon. Just finishing off testing the ones i have to hand.
For the moment. Android 13 support is very hit or miss. I'm working to find a solution to this.

A future update will need the deletion of the existing module so it can properly overwrite the new install files. This will also be completed with the next update.

 

[dickta]

The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work

 

[vithuselservices]

The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work

Can you try uninstalling the original module and do a clean install of this one?

Im afraid i am not able to recreate the issue at all on my device which is quite infuriating