yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
Something is not quite right..

Did you use this module to set a different fingerprint?

If so, then something went wrong and props got set improperly.

Under option number 1.

1 - Edit device fingerprint (active)

It should display

Currently set to (by this module):

Your's displays only Currently set to: which leads me to believe that it is being adjusted (set) by a different app, Magisk module or device modification.

Secondly.

It is showing the original fingerprint value with the security date added to the end.

__2020-11-05

That is not how a fingerprint is supposed to be configured in Android.

That is the format that is used by this module for the fingerprint list.

The fingerprint and date get separated and the both set separately when installed by this module.​

Thirdly.

You are missing the option to reset the fingerprint.

r - Reset fingerprint

This is the option to restore the original fingerprint.

- This module can not restore it since it is not the one setting it. 🙃

---

I see you are using an OPPO fingerprint and the current version of this module.

What is your device and setup?

- What Magisk version are you running?

- Stock OS or a custom OS (rom)?

- What other modules or modifications?

Cheers. :cowboy:
[Magisk] venusloop29:
i did command r - Reset fingerprint and it worked

my device realme c2 stock os rui android 10

I only use magisk lsposed and safetynet, I have never modified this device like a custom rom

I'm using the magiskhide props option 1,3,2 module but safetynet fails, I want to change the device model without using the magisk safetynet module, is it possible?

how to change it step by ste p

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.
[Magisk] pndwal:
... Bit confusing; r = Reset fingerprint option was and is still missing in Edit Device Fingerprint menu in your screenshots... Did you take r = 'reset all' option in main screen?

So things still look a bit strange... Should be like this:

Spoiler content hidden.

This is not clear either... What do you mean?

Yes (if you only mean to create the mismatch needed to trigger enforced hardware based attestation bypass)...

Assuming you just want to pass SafetyNet and now the new Play Integrity API:

Just uninstall MHPC (this) module.

Install @Displax modded Universal SafetyNet Fix module. I put details and a link to his file upload post here:

https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-149#post-87481637

Some technical detail here:

https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-149#post-87480375

Reboot and ensure Zygisk is active (= Yes on Magisk App home screen) and test S/N and PI verdicts...

Please report success... 🙂 PW
[Magisk] venusloop29:
the problem is that i want to change the device model not with the safetynet module in magisk apparently it can't safetynet still fails

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.
[Magisk] pndwal:
So S/N & PI are passing!...

Please say what you're trying to achieve / why you want to change device model... It's not clear what your goal is...

By 'safeynet module' I guess you mean USNF... I think you should he able to change ro.product.model prop globally using either MHPC Force BASIC key attestation or Custom props function and still pass S/N and still pass S/N even if the targeted USNF change is overridden by MHPC; after all it's a mismatch that allow S/N to pass!...

But I don't know why you want to change the model beyond USNF's appended space character in GM's... PW
[Magisk] ipdev:
You failed SafetyNet due to Hardware attestation.

The 2 - Force BASIC key attestation option in this module is currently not enough.

You need to use kdrag0n's method to force basic attestation.​

Use the USNF module to force basic, and you should pass SafetyNet.

The rest of the prop changes (if needed) can be set with this module.

To pass PlayIntegrity, you might need a mis-match of the build fingerprint and active fingerprint.

This is what Displax's mod version of USNF does.​

As PW has already mentioned. 🙃

Actually it is closer to what it should look like when the fingerprint is not adjusted.

1 - Edit device fingerprint

Note: It does not show as (active)​

🙃

You are correct though. 👍

When the fingerprint is not set (adjusted) it should only show.

Currently set to:

Example.

MagiskHide Props Config v6.1.2
by Didgeridoohan @ XDA Developers

=====================================
Select an option below.
=====================================

1 - Edit device fingerprint
2 - Force BASIC key attestation
3 - Device simulation (disabled)
4 - Edit MagiskHide props (active)
5 - Add/edit custom props
6 - Delete prop values
7 - Script settings
8 - Collect logs
u - Perform module update check
r - Reset all options/settings
b - Reboot device
e - Exit

See the module readme or the
support thread @ XDA for details.

Enter your desired option: 1

MagiskHide Props Config v6.1.2
by Didgeridoohan @ XDA Developers

=====================================
Edit device fingerprint
=====================================

Edit the device fingerprint to
pass SafetyNet's CTS profile.

Currently set to:

google/barbet/barbet:13/TP1A.220624.014/8819323:user/release-keys

Enter the new fingerprint or
pick from the options below.

Denylist is not enforced

f - Pick a certified fingerprint
v - Use vendor fingerprint (for Treble GSI ROMs)
s - Boot stages (default/late_start service).
b - Go back.
e - Exit

Note: No r - Reset fingerprint option since the fingerprint is not being adjusted (set).​

--

@pndwal @venusloop29

I have not looked into PlayIntegrity lately but..

The last time I checked it seemed to work with a lower build branch.

It did not need to be a device or API(SDK) level mis-match.

Pixel aOS 12L - (SDK 32)..

I was able to use the May 12L (SP2A) and older fingerprint to pass PlayIntegrity on a 12L June/July (SQ3A) builds.

OnePlus - aOS 12 (SDK31)..

I was able to use any of the Pixel 12 fingerprints to pass PlayIntegrity.

SafetyNet passed but, PlayIntegrity failed when I used a 12L fingerprint.​

Cheers. :cowboy:
[Magisk] pndwal:
Well explained... Seems member successfully passes both S/N and PI now... Guessing with modded USNF suggested, so not sure why member prefers "to change the device model" with MHPC and "not with the safetynet module"...

Yup...

But to be clear, the mismatch to thwart what Google server expects is not with build print (but it may need to be changed); it's presumably with a list of prints (or an extrapolated match) the server expects. (ie. Even building a ROM with a working print still causes the needed mismatch.) ... And such a list / extrapolation method could be altered at any time... More below...

Sure... User made changes since that post...

... Yup. But I was simply pointing out persisting anomalies, eg no 'current value', no 'set by this module' note, no 'r' option, and in view of this (and previous lack of 'r' option), how was this achieved: "i did command r - Reset fingerprint and it worked"?

Seems no common rule; many devices need no change at all (esp w/ A10 and earlier)... Initial observations were that earlier level prints worked in many cases...

Also, are you testing on stock ROMs/devices?... Nb. @Displax's comment:

- He says only "some ROM(s)", narrowed down to "mainly some customs with build in prints manipulations"...

Of course PI API fix requires all of the previous S/N API fix components. A fake keystore provider is still used to cause exception which in turn causes both API's to fall back to basic attestation, and so is a model prop mismatch to bypass the separate hardware check and enforcement of hardware-backed attestation (@Displax tested/confirmed PI also uses this)...

In PI, while the fallback method hasn't changed, an additional mismatch to bypass separate hardware check and enforcement of hardware-backed attestation is now needed in many devices for deviceIntegrity verdict.

This is a fingerprint mismatch, and it's clearly trickier to produce (needs to be valid/passing to satisfy CTS Profile match at the same time as mismatched for instance) than the simple model mismatch (which can range from actual model + space character to creamcheese and still work), and, as mentioned, Google's server end list of prints or method used to extrapolate expected prints may change at any time...

😛 PW
[Magisk] ipdev:
In venusloop29's second post, it shows not active and is back to the defualt fingerprint.

That was the one I was referring to but, it still had some anomalies though. 🙃

Last time testing was a few months ago.

Stock OS on Pixel (4a, 5a, 6) and OnePlus (5T, 6T, 7T, N200).

Pixel 5 with LineageOS 19.1.

Do not remember if I tested on Moto or Poco.

Used the normal USNF module to force basic on Pixel(s) and N200.

Used MHPC to adjust the fingerprint.

Note: OnePlus 5T, 6T and 7T do not support hardware attestation.

So it was just fingerprint changes.​

As I previously commented in one of the threads.

Note: It does not need to be a different SDK level but..

I still have not figured out the rhyme or reason for adjusting the build fingerprint.

Every time I seem to find a pattern that works, the pattern is destroyed by a different device.😜

Some notes from my last testing..

Pixel 6 stock July (12L) build.

ro.system.build.fingerprint=google/oriole/oriole:12/SQ3A.220705.003.A1/8672226:user/release-keys
ro.build.version.security_patch=2022-07-05

Set it to the June build.. Pass SafetyNet. Failed PlayIntegrity.

ro.system.build.fingerprint=google/oriole/oriole:12/SQ3A.220605.009.B1/8650216:user/release-keys
ro.build.version.security_patch=2022-06-05

Set it to the May build.. Pass SafetyNet. Pass PlayIntegrity.

ro.system.build.fingerprint=google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys
ro.build.version.security_patch=2022-05-05

Same if I use the April and March 12L builds or any of the 12 builds.

So the May Pixel 6 12L print should be safe... Nope.

OnePlus Nord N200 5G stock June (12) build.

ro.build.fingerprint=OnePlus/OnePlusN200/OnePlusN200:12/SKQ1.210216.001/R.202206201650:user/release-keys
ro.build.version.security_patch=2022-05-05

Set to the Pixel 6 (12L) May build.. Pass SafetyNet. Fail PlayIntegrity.

ro.system.build.fingerprint=google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys
ro.build.version.security_patch=2022-05-05

Set to the Pixel 6 (12) February build.. Pass SafetyNet. Pass PlayIntegrity.

ro.system.build.fingerprint=google/oriole/oriole:12/SQ1D.220205.003/8069835:user/release-keys
ro.build.version.security_patch=2022-02-05

So..

- Does not need to be a device mis-match.

- Does not need to be a SDK level mis-match.

- Needs to be equal to or less than the device SDK level.

So back to the build branch? :unsure:​

I gave up trying to figure it out and just started doing what worked per device. 🙃

Cheers. :cowboy:
[Magisk] pndwal:
Good stuff doc!

Nb. My comments on need for model mismatch were in relation to original model prop mismatch... @Displax confirmed here it's still needed for PI:

https://github.com/kdrag0n/safetynet-fix/pull/207#issuecomment-1208704294

Fingerprint clearly doesn't need to be from mismatched device however...

Re SDK level, your example results still seem to be for stock devices...

Again, @Displax said his testing indicated only "some ROM(s)" need differing SDK level, and then only "some customs with build in prints manipulations"...

I'm not saying I believe his testing any more than yours, however I'm just not taking anything for granted and I simply don't have enough data to say he's wrong to state "if some ROM uses the same SDK level as specified in the mod's print - this hack won't work"...

I'm also not aware of which affected custom ROMs w/ 'build in print manipulations' he's referring to, but guess he may have tested some... 🙂 PW
[Magisk] ipdev:
MHPC Documentation - GitHub

- Custom fingerprints list - Link

Attached is a custom prints list for Pixel 6a (bluejay).

June (2022) though September (2022).

- To use, rename it to printslist and place it in the /sdcard/ directory.

Cheers. :cowboy:
[Magisk] Layns:
Any of you have Samsung A51 android 12 fingerprint?
[Magisk] Captain_cookie_200:
i am using sooti's a13 gsi. i used this module to pass safety net and i select pixel 4 fingerprint after a reboot it worked! although after a few reboots cts profile check fails again. running the command again setting the fingerprint fixes it. (after a reboot) any idea on whats causing this?
[Magisk] pndwal:
Samsung Galaxy Tab A7 LTE?

No idea, but @Displax-modded USNF with Play Integrity deviceIntegrity fix may work better for you... Swap out MHPC... PW
[Magisk] Captain_cookie_200:
no its galaxy a32 4G. i switched to sooti's aosp since i felt it was actually smoother. it doesnt have the fix for safety net already implemented and i have to flash modules on my own. i havent rebooted since i enabled the prop but if i reboot its gonna go away and my cts profile check will fail. i am using pixel 4 fingerprint from the menu.
[Magisk] pndwal:
... still you'll likely find @Displax-modded USNF with Play Integrity deviceIntegrity fix will work better for you (and persist)... (Swap out MHPC)... PW
[Magisk] Captain_cookie_200:
yep it worked. thanks
[Magisk] milanbey:
Hello guys, my device is samsung s10e (sm-g970f), running lineage 19 (android 12) and magisk 25.2 with zygisk enabled. Props module version is 6.1.2 and safetynet fix version is 2.3.1. Android security update is dated 22/09/05.

YASNAC shows eval. type BASIC, basic integrity PASS, cts profile match FAIL.

What can I do to pass cts profile match as well? No available guide seems to provide a workable solution.

Thx.
[Magisk] pndwal:
Sounds like you haven't read the guide for this module! If you do you'll learn much...

However, for most this is a better solution (old S/N API CTS Profile match is fixed for custom ROMs lacking working fingerprint/security patch level props as a side benefit):

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

... Bye-bye 😝 PW
[Magisk] milanbey:
I knew there would be someone with this incredible knowledge :-)

It worked like a charm! Thx m8
[Magisk] cmonty14:
Hello,

running 'Test SafetyNet attestation' completes w/o error.

Therefore I installed MagiskHide Props Config.

After running props in terminal and 1 I get this (see attached screenshot).

Can you please advise what must be entered next?

THX
[Magisk] 73sydney:
One does not turn up in the thread expecting this level of spoonfeeding for one will be very disappointed....

1) If you install a module, youre expected to at least read the OP of the module to know how to use it

for instance, reading this OP:

https://xdaforums.com/t/module-magiskhide-props-config-safetynet-prop-edits-and-more-v6-1-2.3789228/

would lead you to:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

2) It is a good policy to, before creating a new post in any thread to read the last half dozen or so posts in a thread to see if the issue youre haivng is one thats been addressed already, as if youre experiencing something, logic dictates that it may be a current issue that others will also be experiencing, and most likely resolved

Having said that, you probably want to uninstall MPHC, and then read this:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637

Please do ther basics before creating a new post. Members arent here to cater to you whims like servants, youre expected to do some work yourself, especially when theres an extensive amount of info available, some specifically written to avoid repeated (and often needy) questions

Thanks
[Magisk] cmonty14:
Thanks for your reply.

I don't know how much time you spent on writing it, but I guess it would be faster to reply to my question.

Anyway, 2 of the links you shared are known to me, otherwise I wouldn't manage to install to module.

The 3rd link is irrelevant because my posting is not related to Google Pay.
[Magisk] 73sydney:
And again, id advise you to read (again) because the link i posted is actually exactly directed to and relevant your original message

In particular SafetyNet is now not the only mechanism to make a ROM certify for play store and or payment systems

and youre welcome for me taking the time to help you

and again, no one is here to "work for you", please dont treat members in such a fashion
[Magisk] pndwal:
If there are no errors, please say what you are trying to achieve...

This may or may not even be needed depending on your answer to q. above. 😉 PW
[Magisk] Rajarshi Khatua:
Plese add the support for Samsung Galaxy M31( SM-M315F/DS)

device Fingerprint is - samsung/m31nnxx/m31:12/SP1A.210812.016/M315FXXU3CVH1:user/release-keys

android security patch level - 1 August, 2022
[Magisk] 73sydney:
Please see this post:

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-2.3789228/post-87269699
[Magisk] Captain_cookie_200:
i am really not sure where to post this. i am using superior os 13 GSI by chondoe. i am passing safety net after use shamiko to hide root from gplay services. although play integrity fails and only passes basic integrity. i tried flashing @Displax's modded USNF that still didnt fix it. what could be the source? i have also flashed dolby atmos mod port from Razer phone 2 that seemed to make every app believe that is my phone. could that be the source of the problem? but the modded USNF spoofs the fingerprint already doesnt it? hope someone can help me with this.
[Magisk] Captain_cookie_200:
i have also tried running securize but nothing happens magisk just says its not installed and comes back after an reboot
[Magisk] Leecox626:
For mi 11 lite 5g(Renoir) please.
[Magisk] FireRattus:
Probable fingerprint for Google Pixel 6 Pro

Pixel 6 Pro (13):Google:Pixel 6 Pro=google/raven/raven:13/TP1A.221005.002/9012097:user/release-keys__2022-10-05

Extracted from raven-tp1a.221005.002-factory-d61dff29
[Magisk] mvincent2k:
Backup of OEM Fingerprint Questions:

I have a One Plus 10Pro 5G and performed a backup of the fingerprint successfully using the method per the documentation (i.e. getprop ro.build.fingerprint). It shows my fingerprint is "OnePlus/NE2215/OP516FL1:12/SKQ1.211019.002/S.202209131402:user/release-keys " which is great.

...My questions are:

1) Where is this backup fingerprint located so I can EXPORT & upload it to share for others to use on the public fingerprint DB (since it is not an option currently) and also keep a copy in the event I want to return back to it on my device?

2) Is this all I need to backup?

3) What is the procedure to transfer and restore it on another device?

Thanks

-MV
[Magisk] rocketda7331:
if you used the export function it is in internal storage/mhcp folder
[Magisk] mvincent2k:
I thought so too but the storage/mhcp folder is completely empty even though it shows as a valid fingerprint

Performed the backup with root priv as well so doubly confused as to where it went...
[Magisk] zgfg:
If you just used the Terminal emulator to execute

getprop ...

it won't be stored anywhere - you can copy yourself from the Terminal (or from the DOS box on the PC if you use ADB)

Of course (elementary *nix knowledge), you can print the result to eg myFile.txt on Internal memory:

su

getprop ro.build.fingerprint >> /sdcard/myFile.txt

Also, folder for MHPC is

/data/adb/mhpc

and

/data/adb/modules/MagiskHidePropsConfig

You need root explorer (like MiXPlorer) to access those folders - it's not /mhpc folder on Internal memory
[Magisk] mvincent2k:
Perfect. I see all the files there now via root.

Problem now is that I searched within every .conf, .sh etc. file and didnt see any string matches to anything from the fingerprint that I have reported as active.
[Magisk] vithuselservices:
Hi all,

Just referring to this post i made on the official Github Repo.

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/issues/160

Till Didgeridoohan returns. Im going to take over updating this project. It will take a few weeks before i make my first release. What i need is fingerprints. I've put a link to my discord channel in the github issue above. Please submit your fingerprints there as i depend on you to update the list.

This is not a prank or a trick. I know Android 13 is around the corner for a lot of devices so i want to make sure this module is ready for it!

Thank you for your help in advance
[Magisk] rodken:
Are you only accepting FPs via Discord or did I misunderstand?
[Magisk] vithuselservices:
For the moment that is correct. I would need to either create a new XDA Thread which mods might not like or open up my gitlab instance to collect fingerprints there. Im limited on server resource so cannot allow account creation on my gitlab instance so discord seemed like the optimal place temporarily. Do you think this is a bad idea?
[Magisk] rodken:
It all depends on how many users who are not on Discord are willing to register just to upload certain lines of code.
[Magisk] zgfg:
It'snot that plain simple and sorry I will not answer you further

You need to understand how Magisk modules work and fpr what purpose are eg files (all in /data/adb/modules/MagiskHidePropsConfig:

system.prop

post-fs-data.sh

and the subfolder there:

system

where you will find the file:

xbin/props

(even if they don't have extensions like sh or so, files are textual)

Please carefully read Magisk documentation on on Magisk GitHub, find part for developers, structure for Magisk modules is described there and what for are particular files and folders

It all depends what kind of props you change, are they 'plain' props (they will go to system prop) or they need to be 'replaced' (mounted over) with delay, upon the boot is finished

Even if you are not a programmer, read eg the script post-fs-data.sh and try to understand how it works (comments will also help you), which further scripts and files it reads or executes

And play by changing one prop at a time and analyze (looking to the log files, check file timestamps and study the renewed files)

Btw, I don't see that an ordinary user needs to understand all those details how MHCP works.

Of course, who wants to do that, fine, he can do but he would need to have in-sights about the structure of Magisk modules files, scripting, etc

Good luck
[Magisk] vithuselservices:
Ah. That does make sense. Ill also open a submission page to make it easier for people. Ill first work on overhauling the existing scripts so they point to the new repo and take it from there. Ill link the submission page on the repo once its created.
[Magisk] vithuselservices:
Hi!

Thanks for reaching out.

Completely understand what you mean. I've been working as a Linux sys admin for the last 6 years focusing on scripting for automation of large production servers. Both full time and via my own business. I've already done a initial scan of the existing scripts and only took this on as im very confident managing this is within my skillset. I've also done a fair bit of work creating scripts for Android over the years (Mainly to fix Galaxy Wear on samsung phones with custom roms) so i know my way around the android eco system. Especially props.

I'm compiling my own personal development manual to help map out the existing features and their locations so i can then create a roadmap for any potential future updates and fixes.

Thank you for your supportive and very descriptive message.

Vit
[Magisk] rocketda7331:
If I use the export option in mhpc(su, props, ,7, x, y = mhcp/propsconf_conf) then it creates a file in internal storage with all the props I have modified so what am I missing?. of course you can find them in data/adb/ as well.
[Magisk] vithuselservices:
Just to add onto my earlier post. New Fingerprint submissions can be made on the below form.

Submit Fingerprint

Ill also get this link added to the new repo for ease of access

I have also created a new thread for the forked version of this module.

https://xdaforums.com/t/module-magi...re-forked-and-ready-to-go-live-again.4510729/