yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Fingerprints list updated to v127

@Displax has (as usual) dropped this months Pixel prints (and a couple more). Thank you very much!

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 have disabled automatic updates.

Updated

Google Pixel 3-5 (all variants)

Xiaomi Mi A3 (Global and Europe)
[Magisk] moyses:
Please, i m on the last PA Beta3 and i want to use my Bank app

I tried the methode abouve but dont work

Always Safetynet fails

SafetyNet API Error

BasicIntegrity -

ctsProfile -

evalType N/A

How to solve it please
[Magisk] Didgeridoohan:
That's not a SafetyNet failure:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_API_error

It's just the Magisk app not being able to use the SafetyNet API. It's fixed already on the Canary channel, but there's no need to update just for that since it's merely cosmetical... Use another SafetyNet tester app.
[Magisk] moyses:
I just tried other apk to check the safety SafetyNet Test and Safetynet Checker

the 2 app passed succesfully Safetynet but Bank App stil detect that my device is rooted

The app is S-PushTAN from Sparkasse Germany
[Magisk] Didgeridoohan:
The app doesn't use SafetyNet, most likely...

There are many things that apps can use to detect a "compromised" device:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] guno095:
SM-A505FN FreshROM 3.1.2 Stable MAGISK 22.1 MagiskHidePropsConf, Busybox android NDK

did everything according to the instructions, when you enter the props it writes

/system/bin/props[76]: .: /modules/MagiskHidePropsConf/common/util_functions.sh: No such file or directory

what should be done in this case?
[Magisk] Didgeridoohan:
That's got nothing to do with this module, so I suggest you ask about that in the Smali Patcher thread instead...

Which you already have, so I don't get why you double post and create clutter in unrelated threads. Patience is a virtue (and also note forum rule #5).
[Magisk] Seagold:
Check the pix and tell how to resolve that
[Magisk] Didgeridoohan:
I already have...

https://github.com/Magisk-Modules-R...ter/README.md#an-option-is-marked-as-disabled
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION] just did a commit for fixes to Busybox:

https://github.com/topjohnwu/Magisk/commit/59f78d7dfce51d3f61351bb60ceb2dfd727c0daa
[Magisk] osm0sis:
Yeah, unrelated to your previous problem though.

Edit: Oh yeah, I'd meant to pitch no coloring at all for your signature text, that way the forum theme automatically makes it white for the dark and black for the light. :)
[Magisk] Hitti2:
Just curious about safety net. I use PayPal to purchase things off of Google Play Store what is Google pay for if you can use PayPal and what is the purpose of this module if you can use PayPal to skip Google pay?
[Magisk] mattman83:
Because Google Pay is not just about the play store. Many countries it can be used with NFC tap-and-pay terminals for in store payment instead of using your card. If safetynet is broken, it does not work.

M.
[Magisk] martyfender:
Can you clarify unrelated? I thought that was supposed to fix it, I guess I misunderstood.

Thanks, I may switch to that but I just changed to Royal Blue per [MENTION=4667597]Didgeridoohan[/MENTION] 's recommendation, how does that look for you on your dark theme?

Thanks
[Magisk] Didgeridoohan:
Google Pay is very much more than just paying for apps and stuff from the Play Store...

A bit old, but the basics are still true:

https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/

The fix was actually how the binaries are built, and that happened several days ago. Seemingly unrelated to your issues we've discussed here. If you had waited a couple of days and used a newer Magisk build when installing the module, you probably wouldn't have seen any issue at all...

About your signature, RoyalBlue doesn't really work either... It's better, but the text still kind of blends together.
[Magisk] martyfender:
I am using todays builds with topjohnwu's commits with the new busybox.

The module is working so I have not tested re-installing it. I can, if you would like me to, though.

It is ugly on my end, but I removed the color. The only reason I did a signature was to show my hardware and Android version, etc., so I would not need to post it constantly.
[Magisk] martyfender:
Kantjer build 2018081222

u0_a87@NX16A8116K:/ $ su

u0_a87@NX16A8116K:/ # md5sum /sdcard/busybox

d41d8cd98f00b204e9800998ecf8427e /sdcard/busybox

u0_a87@NX16A8116K:/ # md5sum /sdcard/busybox-q

170133693c4af03a6f311179793569ec /sdcard/busybox-q

han/MHPCBB/master/busybox-x86; md5sum /sdcard/busybox-d <

Connecting to raw.githubusercontent.com (151.101.184.133:443)

wget: note: TLS certificate validation not implemented

wget: clock_gettime(MONOTONIC) failed

d41d8cd98f00b204e9800998ecf8427e /sdcard/busybox-d

u0_a87@NX16A8116K:/ #
[Magisk] Seagold:
Link ? to new busybox pls
[Magisk] Didgeridoohan:
Whenever you run that command in terminal, you're using [MENTION=4544860]osm0sis[/MENTION]' Busybox, not Magisk's. Magisk's Busybox is only used when you install modules and stuff like that. [MENTION=4544860]osm0sis[/MENTION] have not yet updated his build configuration, so you won't see any improvement there until there's been an update for his Busybox module.

https://github.com/topjohnwu/ndk-busybox

It's just the internal Magisk Busybox though, so you'll get it eventually (whenever it's released or if you use an unofficial snapshot).
[Magisk] martyfender:
So he will need to incorporate [MENTION=4470081]topjohnwu[/MENTION] 's fixes or come up with his own fixes?

I uninstalled and reinstalled the module with the new unofficial build with the new busybox and it still failed to download the busybox for your module. That was on the device with [MENTION=7187684]ianmacd[/MENTION] 's latest unoffical with the new busybox, also.

Edit: by running the internal busybox from the terminal, I discovered that [MENTION=7187684]ianmacd[/MENTION] 's latest build has topjohnwu's 1.28.4, while [MENTION=3306843]kantjer[/MENTION] 's latest build has 1.29.2. I'm not sure why since ian's changelog shows that busybox commit in it also. I ran it with this command, if that is the proper way to do it.

/sbin/.core/mirror/bin/busybox

Sorry for my misunderstanding.

Thanks
[Magisk] Didgeridoohan:
No worries. But, why did the new build suddenly fail? I would love to see the logs from that...
[Magisk] martyfender:
I think the explanation is in my edit above, the older busybox version?

Time to go to bed.

Thanks
[Magisk] osm0sis:
John's lastest fixes are for Android Pie's seccomp, and to bring it up to 1.29.2, nothing to do with the monotonic issue. What fixed the monotonic issue most likely is John's switch to the FrankeNDK to build it. I'm going to have to come up with an actual patch to fix it for my builds since I plan to continue to use the official NDK. I'll start looking into it today hopefully.
[Magisk] martyfender:
Apparently the FrankeNDK did not fix it. I am using both [MENTION=3306843]kantjer[/MENTION] and [MENTION=7187684]ianmacd[/MENTION] 's builds with it and when I install this module it still fails to download with the:

wget: note: TLS certificate validation not implemented

wget: clock_gettime(MONOTONIC) failed.
[Magisk] Seagold:
Busybox downloaded. I'm using busybox from magisk download module
[Magisk] martyfender:
Yes, the problem is apparently only with the x86 version.
[Magisk] Seagold:
Even with busybox installed, am not passing SafetyNet yet.
[Magisk] zfk110:
"Patience is a virtue", but you are the Master. The reason I was asking here to see if it is possible to hide Modules within Magisk's manager for other apps to detects.
[Magisk] ipdev:
Seems like something did not install correctly, something is broken with your magisk install, something else...

You could try uninstalling this module and reboot.

Install the module again, save the install log and reboot.

If the module is now working, you are good to go.

If not, attach the log files to a post here or upload the log files and post a link to the log files.

Take a look at this section in the docs.

MHPC ReadMe (How-To) GitHub - The boot scripts did not run - Link

Take a look at this section to get the log files.

MHPC ReadMe (How-To) GitHub - Logs - Link

Cheers. :cowboy:
[Magisk] Didgeridoohan:
That's the second report I have of this in a short period:

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

I cannot reproduce though... As stated above, logs will be necessary.
[Magisk] allrockedout:
So I'm on mi 9 safety net not passing. What boot order should I be using. Was told when I updated magisk that it would fail. Haven't messed with this module in a bit so I'm kind of rusty. Thanks
[Magisk] Didgeridoohan:
Not sure what you mean exactly...

There's no need to mess with the boot order (except in very rare circumstances), and what would fail when updating Magisk?

Maybe you need to take a look in the docs first, and then ask specific questions if there's anything that's unclear:

https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1
[Magisk] Svg.Sakib:
Redmi Note 6 Pro Global

Android security patch level 2020/11/05

Android version 9 fingerprint :

xiaomi/tulip/tulip:9/PKQ1.180904.001/V12.0.1.0.PEKMIXM:user/release-keys
[Magisk] Didgeridoohan:
Thank you @Svg.Sakib, but I would also need the security patch date for that print.
[Magisk] Svg.Sakib:
i added that. i need a help can you help me
[Magisk] Didgeridoohan:
Thank you.

If I can help you depends entirely on what you need help with...
[Magisk] Svg.Sakib:
in my device i am facing 'find device storage corrupted device is unsafe to use now' i have tried orange fox custom recovery to flash persist.img file through terminal commands but it didnt work it says

"Invalid spars file format at header magic failed to read spars file"

Using redmi note 6 pro global
[Magisk] Didgeridoohan:
That is quite outside the scope of this thread and I have no knowledge of how your particular device works.

I suggest you use your device's forum instead and try to find info/seek help there (since I'm not gonna be able to help):

https://xdaforums.com/c/xiaomi-redmi-note-6-pro.8406/

Tip: The search function of the forum can be a handy tool in instances like this. Try searching for the error message in your device's category (you can limit the search to a specific thread, forum or device category).
[Magisk] Svg.Sakib:
thanks
[Magisk] Didgeridoohan:
Update on this:

Seems like this was connected to busybox issues in Magisk v22.1. If you install Magisk v23 and then reinstall this module you should be good to go.
[Magisk] Svg.Sakib:
thanks a lot
[Magisk] allrockedout:
So I got it working by installing safety net fix 1.1.1 through magisk.

Thank you sir
[Magisk] rodken:
Trying to get custom props to stick. Should I place the config file in /data/cache on a A/B device?
[Magisk] Didgeridoohan:
That's a rather old post you're quoting, but the link to the docs on how the configuration file works is still valid...

On an A/B device you would use /data/cache, yes, but nowadays you don't have to use /cache. Check the docs for details.
[Magisk] rodken:
Quite a battle getting a test Custom Prop to stick. I placed the edited config file in the root of my internal, reflashed the module which recognizes the file and cannot get the custom prop to stick. Maybe, I am using an incorrect version of Notepad++ to edit?
[Magisk] rodken:
View attachment 5309179
[Magisk] Didgeridoohan:
@rodken Post your logs (there's an entry for that in the main menu) and configuration file and I can take a look.
[Magisk] Didgeridoohan:
@rodken Thanks. I'll take a closer look later, but from a quick peek it could be a bug...
[Magisk] rodken:
No worries. I am patient.
[Magisk] 73sydney:
Anyone else i would go looking for the bug myself so i could call them a pillock, but not him

Definitely not him

His game, and scripting, is strong :)
[Magisk] Didgeridoohan:
@rodken The configuration file is a bit broken. Somehow the closing quotation mark for CONFPROPSDELAY has been deleted. Add that back in and things should work.
[Magisk] ipdev:
@Didgeridoohan

Does the user supplied propsconf_conf file replace the propsconf_conf in the module or is the one in the module appended to include the changes?

Would a config file like this work or would all the other setting be lost?

#!/system/bin/sh
CONFPROPS="google_knows_best.just_ask_them=true"

It has been a while since I used a config file and a few things have changed.

I reread the Configuration file section.

Then again, I might have just missed the answer to my question.

My search-fu seems to off today. ;)

Cheers. :cowboy:
[Magisk] Peshyy:
I would like to report a fingerprint for POCO X3 NFC (Europe) with MIUI 12 and Android 11:
[Magisk] ipdev:
Need the matching security_patch date for the print also. ;)

Cheers. :cowboy:
[Magisk] Peshyy:
It's 2021-04-01

View attachment 5311389
[Magisk] Didgeridoohan:
@ipdev Up until the other day when the broken configuration file showed up I hadn't really thought about that possibility.

I tested your idea just now and it kind of works (you'll need to keep the CONFTRANSF line in there though or the file won't be applied). Currently, all script settings will be disabled with a configuration file like that (but the prop will be applied) but that's something I could whip up an update for in the near future.
[Magisk] AusVGM:
I would like to report a fingerprint as well. I'm not exactly sure where the values come from though.

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

POCO/vayu_global/vayu:11/ (???) /V12.0.6.0.RJUMIXM:user/release-keys
[Magisk] Didgeridoohan:
Thanks but there's not much I can do with an incomplete print...
[Magisk] AusVGM:
Sorry about that. Went and flashed my phone again to get the proper fingerprint.

POCO/vayu_global/vayu:11/RKQ.200826.002/V12.0.6.0.RJUMIXM:user/release-keys

Latest security patch is 2021-04-01.
[Magisk] knowledge@heart:
Hey,

Are there any known issues to using older Android Version fingerprints on newer Android Version ROMS.

i.e. Can i use m device's android 10 fingerprint on Android 11 ROM?

I read the documentation, but want to know if there are any known issues with that.
[Magisk] ineedroot69:
some apllication use device fingerprint to create personalized profile like for instance you are playing a game and reached level 69 and decided to change device fingerprint once you run the game again it would think you are completely different user and would roll back to level 0 thou once you change back your device fingerprint linked to level 69 you just need to delete game data and that would have access to that account again
[Magisk] knowledge@heart:
Hi,

I guess my concern was misunderstood.

I am not thinking about changing prints mid usage.

I wanted to know whether i can use older android version prints on a newer android version.

Meaning, Android 10 fingerprint on Android 11.
[Magisk] Didgeridoohan:
There's always a chance that something is affected then changing props, and when it comes to the device fingerprint it's best to match the current setup as close as possible. But, it's perfectly possible to use a print that doesn't match the Android version:

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint
[Magisk] Didgeridoohan:
Unfortunately it doesn't seem like this print passes. Are you sure everything's correct?
[Magisk] Necrogente:
Hey there, just discovered something that I really don't understand...

I rooted my phone which is a One Plus 7t Pro running on OOS 11.0.0.2 and I couldn't check safetynet, no worries, i tried that module but nothing changed, i finally ended hiding magisk and it worked, but i recently discovered that I couldn't add another fingerprint anymore ?

Thing is, I deleted the module and I checked on my system apps, apparently there's an app called "com.qualcomm.qti.biometrics.fingerprint.service" and I don't have that on my phone, is it linked ? Can I patch it with that module ?

It kind of frustates me the fact that I have an incomplete phone... :(
[Magisk] Didgeridoohan:
This module has nothing to do with biometrics. Don't confuse the device fingerprint (that this module alters) with the fingerprint reader...
[Magisk] luk159:
Hi, there isn't Mi 9T Global in list. Was deleted in 109 update of list, dont know why
[Magisk] Didgeridoohan:
No, it wasn't deleted. It was simply given the right designation since it was a China print that was mislabeled.
[Magisk] Frax3r:
Hi, I noticed huawei p20 lite fp in the module is a little outdated. I was in the process of switching roms and might as well give the updated fp. Latest build available for c432 is 9.1.0.379 but fp in this build is for 368. Update cycle is near the end anyways so they don't even bother updating fp anymore. I want to warn ahead tho, fp in the module is from L21 variant which is dual sim. Mine is L01 which is single sim. Anyway heres the values

ro.build.fingerprint = HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys

ro.build.version.security_patch = 2020-08-01

ro.product.manufacturer = HUAWEI

ro.product.model = ANE-LX1

edit :

this fails cts profile

custom fp : HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys

custom prop : ro.build.version.security_patch "2020-08-01"

this passes cts profile

custom fp : HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys__2020-08-01

I don't know if this is a feature or bug but I wanted to report it anyway.
[Magisk] heihachi34:
Hi,

I am on Android 10 on my S10 plus. Magisk v23 working well. Except I have cts profile fail and eval type basic.

Masgiskhide props and univ. Safety net fix 1.1.1 both are installed and active.

The problem is, I cannot load the props from terminal. I do as follows,

1) su

2) props

3) please wait.. loading... ( Takes forever ).

Tried uninstalling and reinstalling the magiskhide props module.

Nothing helps.

Can anyone assist ?

Thanks in advance.
[Magisk] Didgeridoohan:
Logs? Since you can't run the props command you'll have to collect them manually:

https://github.com/Magisk-Modules-R...lob/master/README.md#collecting-logs-manually
[Magisk] heihachi34:
Thanks alot for the support. I am attaching the required logs here.

Thanks again.
[Magisk] Didgeridoohan:
There's something wrong with your Magisk installation, or rather the internal busybox. You've got this all over you Magisk log:

E : execve /sbin/.magisk/busybox/busybox failed with 8: Exec format error

That's likely why things are falling with the props command, since the internal Magisk busybox is used in the script.

You probably need to reinstall Magisk.
[Magisk] heihachi34:
Thanks alot for the assistance.

Indeed busybox was the problem.

But, I did not re-install magisk to fix it.

What I did follows,

My fix was simply replacing BusyBox file in the "./sbin/.magisk/busybox"

from "/data/adb/magisk/busybox"

And voila! It worked like a charm. Didn't even restart and props command was working.

I successfully changed my phone fingerprint and now I can pass safety net. With latest magisk installed.

Thanks alot for the directions.

Hopefully, this may help others facing similar issue.

😊
[Magisk] OhioYJ:
Sorry I just noticed this. Yes I'm using it in a custom list right now using this format:

Samsung Tab S5e SM-T720 (11):samsung:SM-T720=samsung/gts4lvwifixx/gts4lvwifi:11/RP1A.200720.012/T720XXU2DUD3:user/release-keys__2021-03-01

According to the built in "tester" in Magisk 23, it says everything passes? Need me to test anything else, or pull something else from the stock rom?
[Magisk] Didgeridoohan:
@OhioYJ I'll test it again.
[Magisk] knowledge@heart:
Hey, what terminal app are you using?
[Magisk] Displax:
Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.23.0.QDIMIXM:user/release-keys__2021-04-01

Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.19.0.QDLMIXM:user/release-keys__2021-05-01

Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.9.0.RFQMIXM:user/release-keys__2021-05-05

Xiaomi Mi A3 EU

(11): Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.7.0.RFQEUXM:user/release-keys__2021-05-05

(10): Xiaomi/laurel_sprout_eea/laurel_sprout:10/QKQ1.190910.002/V11.0.13.0.QFQEUXM:user/release-keys__2020-12-05

(9): Xiaomi/laurel_sprout_eea/laurel_sprout:9/PKQ1.190416.001/V10.3.17.0.PFQEUXM:user/release-keys__2020-03-05

Please check if they pass SafetyNet.
[Magisk] OhioYJ:
Terminal Emulator , used it for years.
[Magisk] Didgeridoohan:
Yeah... Uhm... So... It passes. I'm just gonna leave the one I tested first (that failed) down below and those who want to play can try to spot the difference.

samsung/gts4lvwifixx/gts4lvwifi:11/RP1A.200720.012/T720XXU2DUD3:user/release-keys__2021_03_01
[Magisk] Didgeridoohan:
Fingerprints list updated to v128

A few oldies but goldies getting some new love and a couple of new players joining the list. Thank you to @Qtr1st, @Svg.Sakib, @Peshyy, @Frax3r, @OhioYJ and @Displax for providing the prints.

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 have disabled automatic updates.

New

Asus ROG Phone 5

Huawei P20 Lite Single SIM

Updated

POCO X3 NFC Europe

Samsung Galaxy Tab S5e

Xiaomi Mi A2

Xiaomi Mi A2 Lite

Xiaomi Mi A3 Europe

Xiaomi Mi A3 Global

Xiaomi Redmi Note 6 Pro Global
[Magisk] OhioYJ:
I see a difference... " ; " and " : " used to mess me up in programs as they look so similar. At least this difference is a little easier to see, but I guess that could be subjective.
[Magisk] CHT45:
Latest fingerprint at time of posting for Global POCO X3 NFC:

POCO/surya_global/surya:10/QKQ1.200512.002/V12.0.9.0JGMIXM:user/release-keys

Security patch:

2021-05-01
[Magisk] J.L.C.:
Is this module necessary again with Android 11? I just flashed the May update on a pixel 4xl and can't pass safetynet or get play store certified
[Magisk] Didgeridoohan:
If you're using the Google factory image you don't need this module. You'll need the new Universal SafetyNet Fix though, if you don't have that already (but that's not A11 specific).

First thing to try if SN is failing after an update is to toggle Hide off and on again. If that still doesn't help you've got other issues that you need to figure out.
[Magisk] J.L.C.:
Thank you! I didn't have the universal fix installed. Good to go now.

Netflix won't install, but the play store says I'm certified. Everything else is working
[Magisk] Displax:
Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.26.0.QDIMIXM:user/release-keys__2021-05-01
[Magisk] ipdev:
Still OT for this thread. ;)

Netflix does not require Google Play Services or a certified device.

Post 4,432 - Link

Cheers. :cowboy:
[Magisk] LESHIY_ODESSA:
What do I need to do that you added - Samsung Galaxy A41 (SM-A415F) 11 Android.
[Magisk] Didgeridoohan:
Details in the docs:

https://github.com/Magisk-Modules-R...aster/README.md#how-do-i-submit-a-fingerprint
[Magisk] F308:
As I was seeking - there's no fingerprints for Galaxy A41 on the list.

Of course one may use any other prints, but for myself I managed things work other way.

I don't need SafetyNet pass but I have it passed anyway, just for the sake of reaching success.
[Magisk] Machad3x:
Please add POCO F3/Redmi K40
[Magisk] Didgeridoohan:
Would love to. Need your help with that though:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] NOS_bzone:
Hi dev, please add device Samsung S21 (SM-G991B)

Fingerprint (Android 11): samsung/o1sxxx/o1s:11/RP1A.200720.012/G991BXXU3AUE1:user/release-keys

Thank you dev :)
[Magisk] ipdev:
Also need the matching security patch date. ;)

MHPC Documentation - Matching the Android security patch date - GitHub - Link

Cheers. :cowboy:
[Magisk] NOS_bzone:
Oh ya, this the revision:

samsung/o1sxxx/o1s:11/RP1A.200720.012/G991BXXU3AUE1:user/release-keys__2021-05-01

Thank you