yashsingh1/xdaforums huggingface dataset:
[Magisk] Samrat Sengupta:
Hi Didgeridoohan,

Any luck with the fingerprint key provided, hopefully you have had a bit of time to check...:rolleyes: thanks..
[Magisk] Samrat Sengupta:
[MENTION=4667597]Didgeridoohan[/MENTION],

Did the fingerprint work out.. hopefully you had some time to check out.. thanks

---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------

Sorry I wasn't sure if my prior message got delivered hence followed up with the second
[Magisk] Didgeridoohan:
[MENTION=9266890]Samrat Sengupta[/MENTION] I have actually, but first attempts where negative. Have not had an opportunity to test more, since I haven't had my test device at hand since... You can also test the fingerprint if you don't want to wait. You can either enter it manually in the props ui or use the configuration file (see the documentation) to set it.

You should be able to use the Z00L print without issue though. Using a different device's fingerprint is not really an issue, and since we're just talking about a variation of the same device it'll be fine.
[Magisk] 2nqey:
Okay wow, it worked for me. I am using Samsung's Note 3 on android Nougat fingerprint on my Moto 2 play.

At first i used Moto Z2 play fingerprint on 8.0.0 it didn't work. I checked magisk safety net, it didn't pass. I downloaded safety net checker app I still got the same fail. So i thought it was Xposed, i disabled the Xposed magisk module but i still got the same error. So i decided to change the fingerprint to Samsung's Note 3. And then i checked the safety net but it still didn't pass, I was getting "invalid response" I checked using the safety net checking app, I still got the same error.

So i decided to just try to log in to my Snapchat one last time, and it logged in.

PS: Xposed magisk module was disabled when it logged me in.

So i am not sure or can't say if Xposed was an issue.

Am going to enable my Xposed module back now!!

If anyone feels like Xposed shouldn't be an issue should please let us know. Thanks!

Thank you developer for your brilliant work.

EDIT: After I re enabled my Xposed module, my playstore still showed CERTIFIED so i guess Xposed wasn't an issue.

But i still don't understand why it isn't showing on Magisk and the safety net app that safety net has been passed.
[Magisk] daddylonglegs:
I just realized you edited the post. I downloaded the app as you recommended but is there a guide out there for using it? My phone is completely rooted and I love this type of stuff but man is this app confusing.

Do I use it with the native tethering app?
[Magisk] helgi1507:
Hello!

When I change my smartphone to the latest custom prop I would pass SafetyNet(via YASNAC check, CTS match) but Google Pay always refuses to work. But when I change to the pre-installed outdated prop GPay works fine.

I use Samsung S10e on LOS 19.1

My custom prop

Samsung Galaxy S10e (12):samsung:SM-G970F=samsung/beyond0ltexx/beyond0:12/SP1A.210812.016/G970FXXSEGVA9:user/release-keys__2022-02-01

Does anyone have correct prop for Samsung Galaxy S10e Android 12 or what is the secret? I used to this signature before reinstalling the system.
[Magisk] gumba2880:
Hello so I just started messing around with rooting and stumbled across this post along with many other great tools out there. So I'm going through the code for the Magisk module prodhide and I can't seem to figure out where these files are created from

/data/mhpc/*

The code below references it but I have search the code and can't see how those files get there.

/post-fs-data.sh

VLASTLOGFILE=$MHPCPATH/propsconf_boot_verbose_last.log

RUNFILE=$MHPCPATH/script_check

# Placeholder variables

common/util_functions.sh

MIRRORPATH=$TMPFSMOUNT/.magisk/mirror

SYSTEMFILE=$MODPATH/system.prop

RUNFILE=$MHPCPATH/script_check

UPDATECHECK=""

# Make sure that the terminal app used actually can see resetprop

Oh and why did using a custom prop from a few post back boot loop my device? is there a typo in my boot.prop or does that fingerprint actually cause something to happen? Sorry for the newbie questions, trying to get up to speed here.
[Magisk] rodrigodcf:
Poco X3 Pro (Vayu)

Work great with Android 12.1 LineageOS, I select Global Version (11).
[Magisk] Evo400:
Can someone tell me how do we revert back to factory fingerprint? Thanks
[Magisk] helgi1507:
Find reset fingerprint in props where you changed it before
[Magisk] zgfg:
Run props and go to the option you used previously, it will give you how to revert

There is also an option to revert everything you changed by the module (not just one by one prop)

Or disable/uninstall MHPC module

Reboot is always required
[Magisk] 73sydney:
Sorry just saw this, been busy...

If you look at developer contact on Google Play store it gives you his website with entire guides on how to use it

Every Proxy

www.everyproxy.co.uk

Always check the developer contact info on Google Play Store for links like the above :)
[Magisk] gumba2880:
anyone? so I can't get this to install on my zappiti so I was just trying to run the script on a linux box and I made it all the way to build the magisk binaries but then I realized that it was looking for /system/bin/linker64. I want to run this without actually installing so I can use the hideprop module. I'm basically trying to trick it so I can just get an output of the fingerprint by putting the /system/build.prop from my zappiti in place. That is why I was going through source code to see exactly how the module computes the fingerprint.

Is there an easier way? any help is appreciated. thanks
[Magisk] gumba2880:
So I was able to get the props script working on my device and entered in all the values:

SIMBRAND="NVIDIA"

SIMNAME="mdarcy"

SIMDEVICE="mdarcy"

SIMRELEASE="9"

SIMID="PPR1.180610.011"

SIMINCREMENTAL="4079208_2740.7538"

SIMDESCRIPTION="mdarcy-user 9 PPR1.180610.011 4079208_2740.7538 release-keys"

SIMDISPLAY="mdarcy-user 9 PPR1.180610.011 4079208_2740.7538 release-keys"

SIMSDK="28"

SIMMANUFACTURER="NVIDIA"

SIMMODEL="SHIELD Android TV"

so my question is . what else do I need to get play protected certified, I registered device with google but that was before I made these changes so it won't let me register and netflix is still not wrking it says "this tile is not avaialble to watch instantly" error tvq-pb-101 and I am pretty sure that has to do with restrictions on devices but I would of thought this process would of got around this? can anyone add something? Thanks
[Magisk] LOR3NZO_33:
would be nice for my device to be avaliable, Redmi Note 9 (merlin / merlinx / merlinnfc)
[Magisk] dearestk:
Need help here. Just installed the magiskhide props edit module and successfully spoofed my OnePlus 8T A12 to A11. However, the fingerprint sensor is not working now i.e. it can't sense any kind of touch onscreen. I've got the latest USNF module. Any suggestions or help to make the censor functional again is greatly appreciated.
[Magisk] zgfg:
There are three ways of disabling a module (all changes are Systemless hence when you disable/uninstall MHPC, all changes you made will be gone) - see Magisk Github, Wiki:

- TWRP if applicable, to disable a module

- adb command to uninstall all modules (technique not working on some devices)

-one time booting to Android Safe Mode to disable all modules

Btw, since your device boots, and if you previously granted root to adb,

you can execute from PC (see the subsequent post):

adb shell
su
touch /data/adb/modules/MagiskHidePropsConf/disable
exit
exit

(to create a file named disable in the module's folder) and reboot
[Magisk] Stillhard:
simply by type:

touch disable

inside the module's directory will do too
[Magisk] dearestk:
Thanks! I am able to regain the fingerprint sensor function by reverting the spoof. Is this a normal behavior for using MHPC to change fingerprint profile?
[Magisk] zgfg:
Drivers/system apps for various other components might be looking to the props hence you could always expect that something like camera or so could no more work correctly when you spoof the model (that's why the given props are ro = read only)
[Magisk] Marcus0513:
I can't pass CTS profile match on Xiaomi Mi 8 SE running PE A11. I enabled Zygisk and configured DenyList, installed Universal SafetyNet Fix module and tried changing device fingerprint with this module but nothing works. Which fingerprint should I use on this device because there are no fingerprints for Mi 8 SE. Is there anything else I can try?
[Magisk] 73sydney:
From the MHPC docs (on github)

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

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

A Pixel print is usually a safe bet....amusingly im running Stock Samsung A12 ROM, but it wont pass (even back to A10 print), but Pixel 4a/5/5a (A10/11/12) and even Pixel 6 A12 work fine...
[Magisk] tugaia56:
sorry, some user can tell me how to use the module for oneplus 10 pro? in the list of devices is not there and I do not know how to do it.

thanks for any replies
[Magisk] 73sydney:
See the previous post of mine, just above yours...

short version: you can try and use one close to yours (same Android version ideally) or go for a Pixel at same Android version (ideally)

i believe that phone launched with A12, so theres no earlier fingerprints to try, hence its omission in the list
[Magisk] gumba2880:
Can someone please help me out here. I am running magisk from command line on my android media player which has android 9 and when I run the command

./magisk -v --install-module MagiskHidePropsConf-v6.1.2.zip

all I get is that output below, it doesn't install anything <

4264ae49:MAGISK:D
[Magisk] zgfg:
"output below" is Magisk deamon version, response to your -v option

Try without -v option (it's not for verbose)

Better, type first just magisk and read its 'man page' with all options, args and usage
[Magisk] gumba2880:
Thanks for the response. Yeah I think I getting a little ahead of myself, that's basically the version that in the output.

So a few questions to clear things up for me:

1) From what I have been reading I should use busybox when interacting with magisk?

2) I still have not patched my image so I guess I need to use magiskboot for that?

3) I tried downloading the apk and attempted to patch from the gui but for one it doesn't give me the option to check recovery because I have a vmbeta.img so I used the recoveryimg.bin that is on my firmware restore usb. I keep getting a parse error and unsupported image(I have tried all of the *.img files as well.

4) I rather use the command line anyway, I will keep digging and get back with my findings

Thanks again

EDIT - looks like I can use boot_patch.sh
[Magisk] gumba2880:
Not sure why it doesn't want to unpack boofile.image , return value is 1 so it returns

case $? in

0 ) ;;

1 )

abort "! Unsupported/Unknown image format"
[Magisk] gumba2880:
Well this might have something to do with it. This is a media player from Zappiti (Zappiti neo) I know it's running Android 9. Kind of stumped at the moment. Those French, they have to complicate things. lol kidding

[root@fedora mkbootimg]# ./unpack_bootimg.py --boot_img /mnt/hgfs/david/android/bootfile.image

Traceback (most recent call last):

File "/usr/local/android/platform/system/tools/mkbootimg/./unpack_bootimg.py", line 563, in <module>

main()

File "/usr/local/android/platform/system/tools/mkbootimg/./unpack_bootimg.py", line 558, in main

info = unpack_bootimg(args.boot_img, args.out)

File "/usr/local/android/platform/system/tools/mkbootimg/./unpack_bootimg.py", line 488, in unpack_bootimg

raise ValueError(f'Not an Android boot image, magic: {boot_magic}')

ValueError: Not an Android boot image, magic:
[Magisk] 0wdj:
There is always the same problem on OnePlus phones (and maybe even OPPO). Once you edit the device fingerprint, the fingerprint doesn't work anymore.

There was this same problem on the Universal SafetyNet fix, but it was fixed recently with the last update.

2.1.0 Breaks Fingerprint Sensor - OP8T · Issue #92 · kdrag0n/safetynet-fix

Installing the latest release of safetynet-fix "breaks" the fingerprint sensor on the OnePlus 8T. After installing the finger print sensor will say hardware unavailable. Removing the module and reb...

github.com

I wonder if the problem is similar for MagiskHideProps?
[Magisk] DocMAX:
Can i get support for:

Unihertz/Jelly2_EEA/Jelly2:11/RP1A.200720.011/root.20220108.162257:user/release-keys

?
[Magisk] 73sydney:
This is also a general bit of advice for anyone wanting a fingerprint added/supported

You can create your own custom fingerprint file with directions here which may be quicker as while you can submit fingerprints, didgeridoohan is busy in real life and isnt updating as regularly at the moment:

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

If you need to find the fingerprint info and for correct formatting:

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

for example i made a custom printlist file the other day when testing for the latest Google Pay issue, for my S20+

contents:

Samsung Galaxy S20+ 5G SM-G986B (11):Samsung:SM-G986B=samsung/y2sxxx/y2s:11/RP1A.200720.012/G986BXXSCDUJ5:user/release-keys_2021-11-01
Samsung Galaxy S20+ 5G SM-G986B (10):Samsung:SM-G986B=samsung/y2sxxx/y2s:11/QP1A.190711.020/G986BXXU5BTJ3:user/release-keys_2020-10-01

Everything before the = is the label in the (custom) menu in props in terminal - and all after the = is the fingrprint, in my case

samsung/y2sxxx/y2s:11/RP1A.200720.012/G986BXXSCDUJ5:user/release-keys_2021-11-01

and

samsung/y2sxxx/y2s:11/QP1A.190711.020/G986BXXU5BTJ3:user/release-keys_2020-10-01

for Android 11 and 10 respectively
[Magisk] KITT1995:
LG G8S ThinQ G810EAW

Security patch: 2022-06-01

lge/betalm/betalm:11/RKQ1.210420.001/2215400139237:user/release-keys

ro.product.manufacturer: LGE

ro.product.model: LM-G810
[Magisk] MisterY52:
Updated Asus Zenfone 5Z printslist (current certified fingerprint on github can't pass ctsProfile check):

Asus ZenFone 5Z ASUS_Z01RD (10):Asus:ASUS_Z01RD=asus/WW_Z01RD/ASUS_Z01R_1:10/QKQ1.191008.001/WW_100.10.107.123_20210131:user/release-keys__2021-01-05

Tested with Magisk modules: MagiskHide Props Config, Universal SafetyNet Fix.
[Magisk] damian101:
I am unable to install this module. Through Lygisk it never finishes and the LineageOS recovery throws an error message.

Just a few days ago it worked just fine, had to reset my phone, don't know what I'm doing wrong this time.
[Magisk] oslo83:
Anyone here with a huawei's kirin cpu have any ideas about how to pass safetynet since last july 2022 updates :

-zygisk is ok for huawei's with snapdragons, but with kirins cpu you get random reboots.

So, there is riru alternatives with kdrag0n's safetynet-fix or even huskyDG's riru-integrityfix modules ; But these do not help to pass safetynet anymore...
[Magisk] Displax:
Releases · HuskyDG/safetynet-integrity-fix

A workarround to pass SafetyNet / Play Integrity API on rooted devices with unlocked bootloader - HuskyDG/safetynet-integrity-fix

github.com
[Magisk] oslo83:
I guess I should have tryed with magisk23 as with latest magisk stable, riru-integrityfix helps a bit, but not enough to pass safetynet.
[Magisk] ipdev:
I am not sure if I ever installed this module from recovery.

If I did it was a long time ago and would have been TWRP.

I am not surprised that it does not install from Lineage recovery.

The next time I install Lineage on a device I will try it and see what error it gives. 🙃​

The module should install though Magisk's Module installer.

Next time please save and attach the logcat from Magisk when the module install stalls, stops or fails.

--

You say you reset your device for some reason.

For me, this normally is a complete wipe/format and clean install of system (rom) and everything else.

Unless you completely wiped data/formatted data, it is possible that something is left over from the prior install.

Make sure to save what you want to keep and store it off device (Computer, removable storage, cloud storage,...) before wiping/formatting data.

You could could try deleting the /data/adb directory and reboot.

Magisk will recreate the directory and it's database but, you will start from scratch as far as Magisk goes.

- You will have to setup Magisk again, configure root access, install modules, ...

Cheers. :cowboy:
[Magisk] damian101:
thanks, deleting /data/adb worked
[Magisk] matt1313:
Could anyone provide some suggestions.

Currently have a P5 running protron 12.4.1 early release. I can't get gpay working.

Magisk 25.2

Tried

Safetynet fix by display

Props changing fingers prints to p5 12, p5 11, p4 5g

Clear caches/data

Google API shows basic is good, play store shows verified. Others don't pass.

Thanks in advance.
[Magisk] pndwal:
Proton ROMs generally have SafetyNet Fix integrated AFAIK; after all, SNF was developed by @kdragon for Proton and USNF was/is really SNF made available for other ROMs/devices...

I haven't looked into Proton apart from its SNF implementation; perhaps @kdragon makes ROMs w/o fixes for CTS Profile (fingerprint/security patch level spoofing) available?

Not sure how USNF copes with embedded SNF, but I'm aware others have reported difficulties with ROMs incorporating the fix... Perhaps @Displax may say if this is actually the problem (I think it's likely) or another issue...

If it is, it may be possible to make a module that only spoofs A6 fingerprint for gms attestation process for use with ROMs w/ integrated SNF... (!?)

Also, have you checked Proton forums in case there are user comments about this?... PW
[Magisk] ipdev:
Without the USNF module, does SafetyNet return Basic or Hardware test?

If it shows basic, then the Proton rom is forcing basic attestation.

With changes to Google's security, SafetyNet is being replaced by Play Integrity.

You device can pass SafetyNet but fail Play Integrity.

xda member @1nikolas made an app to check Play Integrity.

Play Integrity API Checker - PlayStore

For example.

Spoiler content hidden.

Cheers. :cowboy:
[Magisk] matt1313:
Without USNF it only passes basic. Same as with the module.
[Magisk] matt1313:
Where in props do you see the months of finger prints
[Magisk] ipdev:
This module's fingerprint list does not support multiple same level build fingerprints.

Support for different Android levels per device but, the current print will be replaced by the newest print when supplied.​

MagiskHidePropsConfig - [GitHub] - [fingerprint list] - Link

Before Play Integrity, this was not an issue.

Normally any certified print could be used to pass SafetyNet on any device.

You can generally go by the matching security date.

I thought it showed the security date when you selected a fingerprint but, I see it does not.

The current Pixel 12 prints in the fingerprint list are from the October 2021 release.

--

If you use a custom fingerprint list (printslist), you set the device name shown.

Spoiler content hidden.

Attached is a custom prints list for Pixel 5.

January (2022) though July (2022).

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

The next time you run props it will show up in the finger print list as 3 - Custom.

Cheers. :cowboy:

PS.

Yes. Google generally builds their updates a month before release.
[Magisk] matt1313:
Thank you for the detailed help and support. Unfortunately I still cant get it to pass. Going back to stock for now.

Thanks again!!
[Magisk] nasrrafiq:
How can i upload my own signature?

Redmi/secret_id/secret:11/RP1A.200720.011/V12.5.8.0.RKLIDXM:user/release-keys
[Magisk] 73sydney:
The dev is very busy outside of XDA in real life as of a while ago and probably currently.

If youre just posting here to submit, you have done all thats required and can do

If however youre looking to use that fingerprint in the module itself, then you should create a printslist file as per these instructions:

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

Once created and on internal memory (sdcard), you can access it via the Custom menu in the module

There are examples of the correct formatting for such a file through this thread, and i referenced some for my device here last week in correct printslist format, as below:

Samsung Galaxy S20+ 5G SM-G986B (11):Samsung:SM-G986B=samsung/y2sxxx/y2s:11/RP1A.200720.012/G986BXXSCDUJ5:user/release-keys_2021-11-01

So basically:

<Manufacturer> <Model> <Model Number> (Android Version):<Manufacturer>:<Model Number>=<fingerprint>
[Magisk] Finnzz:
Is there any way possible with Magisk, to change a build.prop value and have it take effect without a reboot? It doesn't seem possible with MagiskHide Props, but it's there a way to pull it off in combination with some other module, or another module all together?
[Magisk] zgfg:
Magisk makes Systemless changes only while (re) booting

Modules do not write over the System but define their changes at /data/adb/modules, Magisk reads and mounts the changes while initializing

If you have and old phone white writeble System, you could make then manually changes directly to System, by using root but not through MHCP
[Magisk] 2B_4G10:
Guys do we install and forget or are we supposed to tweak things? The Github guide seems bit outdated in options

Thanks
[Magisk] 73sydney:
Read the documentation, we refer to it all the time, so not sure where its "outdated" as its core functions havent changed in eons

If you feel its outdated, please show an example and someone will comment further.

Users are expected to read at least the opening sections especially:

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

If after reading this you are stuck by all means post back and ask for help/clarification if you dont understand, but no ones going to regurgitate the extremely detailed info from the dev every time someone posts here...you can appreciate how messy the thread would be

The documentation is set out in case usage sections, so only you know which case you fit....