yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Did you try with the late prop option (to take place after the boot is completed)

But it could be that your prop is reset 'back" by your SIM card or by the negotiation when attaching to the mobile network
[Magisk] westruk:
1) Tried all options...not working(

2) Sim card not inserted

I'm use Note 8 Pro with custom Bliss rom (a 12) (gsi based)
[Magisk] parpagnas:
I rooted my phone with magisk, i installed the module safetynet fix + props, i hid magisk, i added the custom prop com.revolut.revolut, and cleaned the cache of the app, but Revolut still detects the root... Any Idea? Thanks.
[Magisk] pndwal:
USNF + MHPC?

Use this:

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

Disable MHPC

Check deviceIntegrity passes in Play Integrity API Checker...

Assume you took Hide the Magisk app option in Magisk settings here...

What 'custom prop'? 🤔...

Guessing you mean you hid that process in denylist...

Need to clear data for many bank apps...

I have as above on Xiaomi RN8T but also swap denylist for Shamiko Magisk module for proper root hiding. I get:

View attachment 5768051

Am I in?... PW
[Magisk] THEVAN3D:
how do i reset the changes that i made with this module?

i went and enabled bunch of stuff that were recommended not to do.

and now my phone bootloops.

i can boot with unpatched, original boot.img, but everytime i flash patched boot.img i get bootloops.

i tried cleaning the magisk modules folder, but in vain. still got bootloops.
[Magisk] zgfg:
Read Magisk GitHub, Documentation, Wiki, find about modules and bootloops

Modules can be disabled through TWRP (if TWRP available for the given phone), by booting to Safe Mode (search on the Net what is the key combination for your phone) and on some phones by a particular adb command

Details are in the Wiki
[Magisk] THEVAN3D:
I tried everything. Cant access TWRP. Can use LineageOS Recovery and ADB.

Tried deleting the modules folder but seems empty already:

View attachment 5771021

then i tried renaming magisk.apk to uninstall.zip but that does nothing too (i only get installation texts. no mention of *uninstall* anywhere, is that how its supposed to behave?) anyway i still get bootloops after that too.

What I'm thinking is that somehow this module changed my device fingerprint (or something) somewhere else, not inside modules folder. so whenever i change the boot.img it automatically bootloops.

safe mode does nothing either.
[Magisk] zgfg:
This module works systemlessly (if not familiar with, google about), therefore, changes are only applied when you boot, Magisk initializes and initializes the modules

Boot with the unpatched img, ie without Magisk and there will be no changes applied by this module

However, next time you boot with Magisk, Magisk will find the module, module will initialize and changes will be applied again

-

If there is really no /data/adb/modules directory, the module will not be able to apply changes

But after deleting, you had to reboot

That's how things work. However, I cannot know what else you maybe did, not by this module, that causes the bootloops now

---

Btw, from your screenshot it is not clear how did you execute that - if you don't boot with Magisk = root or not through TWRP, then adb shell will not access /data and will not be able to remove anything

---

To wipe /data, you can also make Factory reset
[Magisk] zgfg:
This module works systemlessly (if not familiar about, please google), therefore, changes are only applied when you boot and Magisk initializes

Boot with the unpatched img, ie without Magisk and there will be no changes applied by this module

However, next time you boot with Magisk, Magisk will find the module, module will initialize and changes will be applied

However, if there is really no /data/adb/modules directory, the module will not be able to apply changes

But after deleting, you had to reboot

That's how things work. But if you maybe did other changes not through this module, they could also cause the bootloops now

---

Btw, from your screenshot it is not clear how you executed that - if you didn't boot with Magisk = root or not through TWRP, then adb she'll was not able to remove anything from /data

PS: If your custom ROM is pre-rooted, uninstalling Magisk by flashing uninstall.zip will not work
[Magisk] micgeb:
You must flash the twrp.zip in twrp
[Magisk] THEVAN3D:
cant access twrp for some reason. i have lineageos recovery. and cant do "fastboot flash recovery twrp.img" and "fastboot boot twrp.img"

nothing happens after that. there is no more recovery for me unless i flash back the lineage os recovery.
[Magisk] pndwal:
Can you flash the twrp.img from in LOS recovery? (Then reboot to recovery.) PW
[Magisk] THEVAN3D:
does not work. tried adb sideload twrp.zip too. twrp just wont install at all. i either have lineage os recovery or no recovery at all.

whenever i try installing twrp i end up in fastboot/bootloader instead of recovery. i have no recovery anymore after that. i have to flash back lineage os recovery to have any kind of recovery at all.
[Magisk] micgeb:
fastboot boot twrp.img must work. Reboot your bootloader and your pc or you use a wrong twrp version.
[Magisk] pndwal:
Is this OnePlus 8?

What exactly happens when flash the twrp.img from in LOS recovery?... Is device like 8T having recovery_a/recovery_b partitions?... (Most A/B devices have none; recovery is in boot)...

Either way, I think member above is right... Try following more detailed 8T instructions for boot-only twrp first w/ 8 files (nb. Both models have .img and .zip files provided) and flash zip afterwards... (Nb.2. OP 8 instructions are limited):

https://twrp.me/oneplus/oneplus8t.html

👍 PW
[Magisk] THEVAN3D:
i have latest adb and latest twrp versions.

Yes, it is OnePlus 8 and after flashing twrp.img i get no error messages, it seems like as if it installed fine, but when i do "fastboot reboot recovery" it goes to bootloader/fastboot. Even if I manually select "recovery" with volume keys and press power button it still goes back to bootloader/fastboot. i just have no recovery at all. neither LOS recovery, nor TWRP.

After that all i can do is "fastboot flash recovery lineageosrecovery.img" and get it working back to that recovery instead.

And I believe it has A/B slots, but i dont know what to make of that.
[Magisk] pndwal:
Still not clear if you're following the prescribed method; you

don't

flash initially!... Please say if you've booted-only first (fastboot boot twrp.img... Sounds like you may be skipping this and just flashing?!) PW
[Magisk] linuxdep:
I'm probably too stupid, read back and forth here, but all pages are not, hence my question.

I wanted to use G-Wallet, which reports errors because of root+Magisk and Co. Then I ended up here, the fingerprint of the device should probably be changed. Then I found something:

type in Terminal: su props 1 ('change device fingerprint')

navigate to your device Fingerprint from the dialogue

but I have no choice.

It should also be possible to set it on the shell, but how does that work exactly?

# getprop ro.product.device
oriole
# getprop ro.build.fingerprint
google/oriole/oriole:13/TP1A.221105.002/9080065:user/release-keys

I have the last security update from November on it. Do I actually have to set the fingerprint again after each update?
[Magisk] zgfg:
Instead of this module, find a thread for Universal SafetyNet Fix (USNF(and install the module with exactly the following name: safetynet-fix-v2.3.1-MOD_2.0.zip (supposing you have Magisk v25+ with Zygisk)
[Magisk] linuxdep:
ok, i have installed Magisk v25+ with Zygisk and safetynet-fix v2.3.1 without MOD... i have found it on github.

should i uninstall this module bevore?
[Magisk] 73sydney:
Yes
[Magisk] pndwal:
You can install over official...

Notes:

Google Pay/Wallet has migrated to Play Integrity API since S/N is now deprecated... official USNF is still Universal SafetyNet Fix, ie doesn't fix PI deviceIntegrity which you now need; @Displax fork mods USNF to pass new deviceIntegrity verdict...

Official USNF is enough for some devices (for PI also). Check if already pass deviceIntegrity using Play Integrity API Checker...

Most devices on A11+ need a modded version however... Either build for most devices, mod 2 is needed for Pixel 7 series (or other devices launched/launching with Android 13)... Usage / download links here:

Post in thread 'MAGISK MODULE ❯ Universal SafetyNet Fix 2.3.1' https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

🤠 PW
[Magisk] linuxdep:
You may be needed to wipe GMS data (not cache) if there is no result immediately.

How can I delete GMS data??? First of all what is GMS???
[Magisk] dr4go:
Gms Data Android

For those who think it's easier to annoy you than to Google 'Gms data android' themselves.

letmegooglethat.com
[Magisk] pndwal:
Not sure who you're replying to, but gms = Google Play Services (aka google EDIT: media mobile [should have googled!] services)... PW
[Magisk] linuxdep:
Oh man, is this a hidden object game...

Found it, everything here, but who is supposed to find the link to the current safetynet-fix-MOD in a >100 article entry on page 91? If you don't read along here all the time, you've got a bad hand. But for now it works on the new Pixel6, a test payment is still pending, but I think it will work. Thank you to all the developers of this software, even if you're probably not reading along here.

Short:

safetynet-fix-2-3-1-MOD Post
[Magisk] Erfirya:
can someone help me with my disney+ app issue. so I have:

Xiaomi POCO X3 NFC

xiaomi.eu MIUI v13.0.1

Android 12

Magisk v25.2

USNF (Displax mod)

my problem is I can't watch any of their content on FHD, it only shows up to HD quality even though I've subcribed to premium. I've tried logging in the same account on the same device but w/ locked bootloader and stock rom and it has a FHD quality option. I've also added disney+ to denylist but the issue still persist. I've checked if my device is certified using Play Integrity API Checker (Nikolas Spiridakis). Here's the result:

edit: f*ck wrong thread. sorry
[Magisk] Adolyer:
Has this project been terminated? Most of the new devices don't.
[Magisk] Lord Sithek:
Officially not, but dev hasn't been seen for quite a time. However, there is a fork currently under development: https://xdaforums.com/t/module-magi...re-forked-and-ready-to-go-live-again.4510729/
[Magisk] iBART:
So if the Android version is 12, can I use the 11 version of the fingerprint?
[Magisk] ipdev:
Yes.

You should be able to use any of the certified prints.

Normally recommended to stay as close as you can to your own device.

MHPC Documentation - [GitHub] - Can I use any fingerprint? - Link

Cheers. :cowboy:
[Magisk] pndwal:
... Or use @Displax USNF mod/fork which sets very old fingerprinting but targets gms (ie mismatched fingerprint won't break most stuff) to pass PI deviceIntegrity (unless you have some special purpose). See this:

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-2.3789228/post-87745127

and

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-2.3789228/post-87795077

Nb. We'll have official Universal deviceIntegrity Fix for PI API (upgraded USNF) any tick of the clock now:

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

🙂 PW
[Magisk] alnosr:
Hey guys.

I need some help please, I have a realme x2 pro CN version, tried the certified fingerprint but I still doesnt pass CTS. I suppose it's because it's global version.

I managed to find manually fingerprint for cn version in build.prop, but I'm not sure how should I manually add. I arealdy made a printslist located in internal storage root with

but I can't find the option to set it in the command line. Is it Edit/add custom prop? If yes, then what should I write?

Besides, the fingerprint starts after the "=" so for the first part I had to copy the certified fingerprint for global version. Can anyone check if it's correct? Here is the build.prop. I just worry I should have write "CN" or something.

Thanks !

EDIT : 1 Oh well. I added it manually in termux and got my custom fingerprint. However I still doesnt pass CTS. Any help? I use force basic key attestation with realme x2 Pro Global variant.

EDIT 2 : I also assume it's a certified one since you can see in the build.prop security date patch etc, right?

EDIT 3 : Tried display mod doesnt work either cant meet device and strong integrity

I use lineageOS.
[Magisk] pndwal:
@Displax USNF mod2?

Is LOS official or unofficial?

Zygisk = Yes in Magisk App home screen?

Try this:

- ALL modules disabled other than @Displax USNF mod2

- Nothing in denylist

Nb. You won't get/don't need strongIntegrity; need deviceIntegrity... 👍 PW
[Magisk] alnosr:
Yes USNF mod2.

Unofficial.

Zygisk = yes

I do pass CTS with YASNAC though. But I still can't use google pay.

I only have USNF for module

and I just tried nothing in denylist doesnt work
[Magisk] m0han:
What's with this MHPC-v7.0.1-beta.zip floating around on Telegram?
[Magisk] pndwal:
I've seen this issue (cannot pass deviceIntegrity) reported with other custom ROMs, eg Paranoid Android...

I'm guessing the issue could be when devs integrate SafetyNet Fix in ROM which may interfere with Magisk USNF modules updates incl. @Displax's fork... Or it may be something completely different incl. other prop manipulations...

Nb. Many Devs don't follow official LOS policy never to manipulate props/signals etc. in their unofficial builds...

Personally I prefer to use clean ROMs (eg official LOS) that won't/don't integrate spoofing/prop manipulation, and to add such 'fixes' using Magisk as there are less issues with conflicting Magisk modules as well as when changes (eg Google server end) are made...

It's just a hunch, but you may find there are no issues passing deviceIntegrity w/ official LOS or stock ROM...

Also, try this:

Disable @Displax USNF mod_2, Reboot, Clear Google Play Services Data, enable @Displax USNF mod_2 and reboot again...

Hope something here helps... PW
[Magisk] rmedure:
Is there a solution to have MHPC active and properly functioning fingerprint sensor on OnePlus8 Pro?

When MHPC is used to change to IN2025 A10 or A11, the fingerprint sensor does not work. When revert back to IN2025 A12, fingerprint sensor works, but device_integrity fails.

Addl'l info: Magisk 25.2, Zygisk, USNF 2.3.1
[Magisk] ipdev:
Quick look back and the last mention(s) are..

Post #6,371 and Post #6,426

Cheers. :cowboy:
[Magisk] pndwal:
Yes; don't use it to adjust fingerprint prop!...

Seems to need repeating over and over that w/ the advent of a 'Universal deviceIntegrity Fix for PI API' in @Displax's published Universal SafetyNet Fix mod/fork and an improved official implementation imminent, the use of MHPC to spoof a passing fingerprint/security patch date prop combination is no longer the best solution for passing Integrity attestations in gms, especially as props are set globally bu MHPC...

Current fix is here:

https://github.com/Displax/safetynet-fix/tree/integrity

- This properly sets mismatched but passing fingerprint targeting gms to bypass hardware based verdict enforcement in new Play Integrity API and allow deviceIntegrity to pass along with depreciated SafetyNet API verdicts... (Generally you'd disable MagiskHide Props Config module if you have it.)

You'll be able to migrate back to official USNF when this is done:

#207 (comment)

The @Displax modded USNF (and PR in official USNF GitHub) also include newer fixes for OnePlus fingerprint scanner issues I linked here:

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

Hope this prevents some time being wasted solving issues when users continue to attempt to use MHPC for passing SafetyNet / Play Integrity deviceIntegrity verdicts... 👀 PW
[Magisk] rmedure:
Thanks for the reply! You beat me to the punch, I actually found the Displax fork USNF (mod) but didn't get to update my post yet.

I too hope that these posts help others!! Especially OP owners; it looks like OP devices are susceptible to breaking fingerprint sensor.

Cheers!
[Magisk] iBART:
Thanks!
[Magisk] kramer04:
Hello

Can someone help me

I search fingerprint for samsung SM-N975F
[Magisk] pndwal:
What for?... PW
[Magisk] kramer04:
to try to pass cts profile
[Magisk] eried1:
Has anyone gotten the Danish Mit-ID app to work? I think you somehow have to conceal all traces of Lineage OS in the build.prop. Possibly even more actions are required.
[Magisk] pndwal:
Please my see previous post:

👀 PW
[Magisk] jojemiqe:
Hello guys, I am trying to use samsung smart tag but it only works with Samsung device so I used this module and selected s21 fingerprint and enabled everything inside simulation but samsung smart thing app still detects. Any recommendations for me?
[Magisk] byrnadd:
Dear friends, please help. I need a complete device uniqueization for the application, but with this module I can only change the name of the device and the software parameters. Is there in this module or in some other the possibility of replacing cpu, gpu and other biometric data from certain devices. Or just the ability to manually add it all? Thank you very much for your help.
[Magisk] ItsIgnacioPortal:
Fingerprint for the Moto e6 plus (64/4 variant, I don't know if the 32/2 variant has a different fingerprint):
[Magisk] torben5247:
i need to change "Ro.system.build.type" from "userdebug" to "user" i simply can´t figure out how to do it.

I have tried to change it using propeditor, but after reeboot the setting are reversed.

I am not sure, but i think that magisk is reversing the setting back.

Do i have to remove a setting in the menu "Set/reset MagiskHide Sensitive props"?

If someone could guide me and explain how to make the change so it will be "user" after reboot, i will be very greatfull.

Thanks in advance
[Magisk] torben5247:
Thank you very much.

wich option do you pick when you are asked:

"Pick an option below to change

what boot stage the prop will

be set in, or set/reset a delay:

1 - Default (current)

2 - post-fs-data

3 - late_start service

4 - Both boot stages

d - Delay"

Thanks in advance
[Magisk] ipdev:
I left it as default so I just continued with y(es).

1 - Default (current)

Cheers. :cowboy:
[Magisk] C4sp3R911:
I have a OnePlus 7t Running LoS 20 (Android 13). When I Edit Device Fingerprint>Pick a Certified Fingerprint>OnePlus>OnePlus 7t HD1905. My only fingerprint options are Android 10 and 11. Will running an Android 11 fingerprint on Android 13 have any adverse effects? Is this reversible if I do encounter any issue?
[Magisk] pndwal:
Re. "This tool is now dead...":

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87981619

Thanks @Didgeridoohan!... 👍 PW
[Magisk] zgfg:
Thanks to all what you did but IMO, it would be better now to freeze this thread as-is

Let further discussions go through the new thread:

https://xdaforums.com/t/module-magi...-ready-to-go-live-again.4510729/post-87802229

corresponding to his GitLab fork:

Vithurshan Selvarajah / MagiskHidePropsConf · GitLab

GitLab Enterprise Edition

git.vithusel.me
[Magisk] carmeloamg:
Fingerprint for OnePlus 7 using Android 12 (tested for me and working):

OnePlus/OnePlus7/OnePlus7:12/SKQ1.211113.001/P.202212132005:user/release-keys

ro.build.version.security_patch: 2022-08-05

ro.product.manufacturer: OnePlus

ro.product.model: GM1900
[Magisk] Youdeath:
Alguém ajuda, não consigo acessar o willbank

Mod translation: Someone help, I can't access the will bank
[Magisk] OrionExodus:
I tried device simulation after setting all to enabled, my phone ended up in a bootloop.it was almost bricked, cause my phone said there was no android filesystem found on the phone so no recovery or any partition was accessible,but managed to factory reset it.

I don't know how to get passed safety check.everything i tried was not helping at all.
[Magisk] pndwal:
😬... Did you read the warnings?....

Generally banks have already migrated to Play Integrity API as SafetyNet API is deprecated... Latest Universal SafetyNet Fix Magisk module has a solution for PI deviceIntegrity now, but it is failing intermittently for many, and Google Pay/Wallet users particularly are getting failures w/ 'Device doesn't meet Security requirements' message... I recommend you find @Displax's USNF modded fork and use that at least until official USNF is updated... PW
[Magisk] OrionExodus:
Didn't read the warning.... nevermind it is running again. But the safety net fix from @Displax can't be used because I'm using riru instead of zygisk.. also it says to update to 2.4 which is not working too.

EDIT: I changed from riru to zygisk and now it's working with 2.4 but there are many modules with riru that I want to use... what should I do?
[Magisk] pndwal:
You're making things difficult for yourself then... You can use official USNF for Riru to pass S/N w/ official Magisk 23.0, and you may pass PI deviceIntegrity depending on device/Android version... I'm guessing you're likely failing that however...

@huskydg has a Riru fork of USNF w/ PI fixes, and I believe it is usable with his 'Delta' Magisk fork of 24.0+ Magisk... Look for his Delta thread / GitHub if you want these...

Recommend using official Magisk and Zygisk however... And read stuff! 😝 PW
[Magisk] OrionExodus:
Well, HuskyDG's version didn't work. I will disable riru and use zygisk then... :(
[Magisk] m0han:
https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88001545
[Magisk] maikcrew:
The app works on LineageOS 20. I'm sorry the author doesn't have the energy to continue. I thank him for his help so far.
[Magisk] can't say why:
Fingerprint for the Xiaomi 13

MIUI 14.0.17 Stable China

ro.build.fingerprint=Xiaomi/fuxi/fuxi:13/TKQ1.220905.001/V14.0.17.0.TMCCNXM:user/release-keys

ro.build.description=fuxi-user 13 TKQ1.220905.001 V14.0.17.0.TMCCNXM release-keys

ro.build.version.security_patch=2023-01-01

ro.product.manufacturer=Xiaomi

ro.product.model=2211133C
[Magisk] zzattack:
Is there a boot prop I can fake so annoying apps are tricked into believing I have a full alphanumeric password set for device unlocking, when in practice I have only a simpler pattern set?
[Magisk] matfcb:
What's the correct prop for Xiaomi Mi 9 Pro 5G? I would like to pass Safety Net, to use McDonald's app.
[Magisk] zgfg:
It's not only about fingerprint

Better go to the thread USNF and try with the modules there. Read posts over the last days there and ask further there if necessary
[Magisk] matfcb:
I have newest USNF, I tried all methods in the thread, nothing is working.
[Magisk] V0latyle:
This thread is for MagiskHide Props Config. Please keep your questions regarding Universal SafetyNet Fix to this thread.
[Magisk] pndwal:
You don't need to set fingerprint w/ MHPC if newer USNF works properly, but if you do read in that thread you'll see there are issues with both official and forked 2.4.0 USNF builds so having the latest is undoubtedly your problem...

And the real issue is Play Integrity deviceIntegrity verdict not depreciated S/N results anyway...

Frankly, I very much doubt there's much to gain from playing with fingerprint or other props using MHPC now... Use the USNF bullds users are reverting to... PW
[Magisk] matfcb:
I used Xiaomi Mi 9T Pro fingerprints and Poco X3 Pro, neither one give me Safety Net Passed and deviced is certified in Play Store. It seems I will be unable to use McDonald's app on my phone.
[Magisk] pndwal:
Sure you will be able... But ask about working USNF version / resetting app detection flags in USNF thread as requested... PW
[Magisk] misterHomer:
Hi. I've already installed MagiskHide. But when I try to launch it, it says: props not found.

I've tried several versions. All the same.

Also tried adb shell, termux, terminal emulator. With 'su' and without.

I'm trying on memu emulator Android 9.

Maybe some knows how to solve this?
[Magisk] zgfg:
Do you really need the old MHPC?

What about disabling it and to use only safetynet-fix-v2.4.0-MOD_1.2
[Magisk] misterHomer:
Never heard about it. Can I change android parameters via this stuff?