yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
You're on a stock ROM so you don't need this module. You'll pass SafetyNet out of the box...

For Gpay:

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
[Magisk] Hyflex:
Yep no difference

I just checked that... There are hundreds that have attest in the first column, surely there is a better/easier way?
[Magisk] Didgeridoohan:
Up until now, no. That's the only way that's been confirmed to work recently. There's a Magisk module that does things automatically in there somewhere.

If you need further assistance with Gpay, I would suggest that thread and this: https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] .:B:.:
Has anyone been seeing any funky issues with ASB patch levels? I am on a recent LOS 16.0 build, with the latest ASB patches applied (LOS just pulled them in a few days ago). When I remove flash the Magisk removal zip, the ASB shows as September 2019. Once I re-flash Magisk, it shows as November 2018, which is when I think I submitted my device (XZ1 Compact) for inclusion on the fingerprint list...

Anyone seeing something similar?

Edit: just tested while keeping Magisk but just removing the Props module, that resets the patch level information in the system settings screen to September 2019 as it should be. So it's something the Props module seems to do.
[Magisk] sliding_billy:
Here is the post with the module information.

https://xdaforums.com/showpost.php?p=79643248&postcount=176
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...y-devices-android-security-patch-date-changed
[Magisk] .:B:.:
Thanks [MENTION=4667597]Didgeridoohan[/MENTION]. My banking app so far seems not to mind about the SafetyNet test failing, but they don't seem to probe every single time one opens it, so I'll keep an eye on it.
[Magisk] spacer7007:
Can you add support for oneplus one. this lineage os bug reort contains the correct fingerprint

https://review.lineageos.org/c/LineageOS/android_device_oneplus_bacon/+/243112/1/lineage_bacon.mk#35
[Magisk] CarbonGTR:
You can use any fingerprint you want to. Or else, Just Install stock rom back and use the "grep prop" command to get the proper, tested fingerprint for your device.
[Magisk] Didgeridoohan:
I will eventually get some time to finally sit down and go a proper update of both the fingerprints list and the module (all that's really needed is some bug spray and proper testing, but that takes time that I simply do not have).

But yes, until then pretty much any certified fingerprint can be used, or if you have a print that's not included in the module you can just enter that print manually.
[Magisk] spacer7007:
I already did, I just posted here for completeness sake. That bug report i linked is outdated, they rolled it back some more. I just hate not "owning" the hardware i buy and i think you're doing a great job. Thanks for your work.
[Magisk] Avarast:
Pulled off of a Xiaomi Mi 9T, specifically the European (EEA) version

Xiaomi/davinci_eea/davinci:9/PKQ1.190302.001/V10.3.12.0.PFJEUXM:user/release-keys

getprop ro.build.version.security_patch

2019-07-01
[Magisk] DragonLe:
Fingerprint for K20 Pro android 10

Redmi K20 Pro (android 10, for those on beta/custom ROMS):

Xiaomi/raphael/raphael:10/QKQ1.190716.003/V10.4.6.0.QFKCNXM:user/release-keys
[Magisk] panda822:
I have selected 1. Edit Device Fingerprint with Samsung Note 3 and 3. Improved hiding and still my banking app doesn't work.

Then I've selected Device Simulation and I got a boot loop.

I've fixed the boot loop but how to make my banking app work?
[Magisk] Didgeridoohan:
I'm assuming you're passing SafetyNet now, with the certified Note 3 fingerprint. And the "Improved hiding" feature is placebo at best... It'll actually be removed in the next update (with a possible revival in a future update, slightly altered).

But, there are many more things that an app might be looking for that's not covered by this module. Take a look here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] ipdev:
Need the corresponding security date to test/use it.

If you are running the rom, you can grab it with adb shell or a terminal app.

getprop ro.build.version.security_patch

or

getprop | grep ro.build

(This will display all ro.build.** values.)

Otherwise, you can find it in the one of the prop files.

(system/vendor)build.prop, default.prop, prop.default or the updater scripts.

Cheers.
[Magisk] panda822:
I have repackage magisk with another name Toggle Hide On/off and now it works.

Thanks!

---------- Post added at 08:08 AM ---------- Previous post was at 07:58 AM ----------

After each reboot I need to toggle Magisk Hide on/off...
[Magisk] Didgeridoohan:
That's a known bug that affects some devices. Not much to do until it's been fixed... Although you could make a boot script/Tasker profile or similar that runs this at boot (to automate):

magiskhide disable
magiskhide enable
[Magisk] Dreamer(3MF):
Download The Module Of MultiFunctions From This Thread https://xdaforums.com/apps/magisk/module-multifunctions-bootloop-t3933386 For Getting The Ability To Use The Sub-Function Of Hide Enabler Under The Main Function Of MagiskHideList Cleaner.
[Magisk] Didgeridoohan:
[MENTION=4161707]panda822[/MENTION] Just make sure to read the description and instructions for that module carefully before use. It'll also do a lot of other stuff that you might not want and has the potential of causing issues.
[Magisk] garylawwd:
Device;

Xiaomi mi a3 (global version)

Rom;

Latest stock

Security patch;

5th September, 2019

Fingerprint;

Xiaomi/laurel_sprout/laurel_sprout:9/PKQ1.190416.001/V10.3.6.0.PFQMIXM:user/release-keys

[MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] x86cpu:
Asus Zenfone 6 (9.0)=asus/WW_I01WD/ASUS_I01WD:9/PPR2.181005.003/16.1220.1909.193-0:user/release-keys__2019-09-01

Tested and working. (I know you test them too [MENTION=4667597]Didgeridoohan[/MENTION] )
[Magisk] aseferfan:
Xiaomi mi 9 lite retail unit, obtained using getprops command in termux

.

edit : apparently, it seems he bought a Chinese mi 9 lite(cc9) with global version on it, this fingerprint is NOT genuine, if someone has mi 9 lite genuine fingerprint, please do add
[Magisk] NE0HP:
Mi A2 September security patch

xiaomi/jasmine/jasmine_sprout:9/PKQ1.180904.001/V10.0.14.0.PDIMIXM:user/release-keys

Also would like to know here that is it anything to do with security patch and selected certified fingerprint? I've just tried this module and selected the available certified fingerprint i.e 10.0.7.0 and it indeed works fine and ctsprofile showing true but at the same time when I check the security patch under Android version, it is showing March 2019 instead of September 2019?
[Magisk] Didgeridoohan:
That's perfectly normal. Take a look in the docs:

https://github.com/Magisk-Modules-R...y-devices-android-security-patch-date-changed
[Magisk] ark906i:
Dear Didgeridoohan:

Thank you for making this module. Unfortunately, it cause bootloop. Please see the detail as the following.

Device: Xiaomi Mi5

Rom: LineageOS 16.0 GSI

https://xdaforums.com/project-treble/trebleenabled-device-development/gsi-lineageos-16-0-gsi-arm64-ab-how-to-t3908029/page41#post80416327

I have configured according to the this guide.

https://github.com/phhusson/treble_experimentations/issues/116

The concern is after I have set the below config. It cause OS to bootloop.

At step no. 2, I have tried "v- Use vendor fingerprint (for Treble GSI ROMs)". It also produces bootloop too.

I have attached log in the below hyperlink.

https://1drv.ms/u/s!Ars2CqwZ9_2biBi6REAN1gGqGATZ?e=odzyHF

Can you help me to solve this issue? Thank you so much.
[Magisk] Didgeridoohan:
As far as I can see, those logs are collected on a functioning and booting system, with the module completely reset to the default values. Nothing there for me to work with, so if you need further help I need logs that actually show the issue.

That "guide" is complicating things too much (which actually is explained in the updated info). All you should have to do is to pick a fingerprint from the list available under "Edit device fingerprint", or using the "Use vendor fingerprint" (if that fingerprint is certified). And, if things don't work try using different boot stages (just like stated in your link). Take a look in the module docs for more info (I've got most issues covered there).

I did a quick test of the vendor fingerprint available on your device, but it does not pass CTS. The print for the Mi5 that's available in the list works though. Of course, I don't have any device running a GSI, so I can't test if there are any extra shennanigans there.
[Magisk] ark906i:
Thank you so much for promptly reply.

I think the log is not included bootloop event because I have misunderstanding how to log. Thus the former log is on non-bootloop event.

I have capture new log as the followings:

1. First boot: I install "MagiskHide Props Config" then set fingerprint according the my first post.

2. Reboot then OS is become bootloop (second boot)

2.1 Connect USB, "adb shell", "props", Select "8 - Collect logs", yes, exit (no file has been saved)

2.2 "logcat > /data/media/0/test.log"

I have saved 2 files from 2 times of bootloops: Bootloop_catlog1.log, Bootloop_catlog2.log

3. Reboot to recovery/TWRP (for copying log file to PC):

3.1 propslogs.tar.gz is not found in /data/media/0/ (sdcard's directory) <-- Please suggest why propslogs.tar.gz is not available and how to get log properly.

3.2 Got 2 logcat files as shown in 2.2

4. Reboot to system, bootloop, "adb shell", "props", reset setting

5. Reboot to system, normal boot: I have saved 2 files on normal boot.

5.1 logcat: Normal_catlog.log

5.2 props log: propslogs.tar.gz

Please refer the attachment for all files.

Sorry for long post. This concern is not urgent. Please have a look when you are available. I am appreciated for your help.
[Magisk] Didgeridoohan:
[MENTION=1182504]ark906i[/MENTION] Those logs are way too big for me to look at, at the moment. I'm fully mobile right now and that's not very convenient when looking at big logs.

But, instead of trying to save a propslogs.tar.gz file, for module logs and files you can grab almost everything you need from /cache. The Magisk log together with all propsconf files found there, and also the propsconf_late from /data/adb/mhpc, are all very useful when troubleshooting.

I would advice you to try some simple things first:

Apply a certified fingerprint, nothing else, and reboot. If it bootloops we know more about where the issue lies, if the device boots up we continue.

Check if CTS passes. If it does your done. Yay. If it doesn't try changing the script fingerprint boot stage to post-fs-data (under "Script settings" "Edit device fingerprint") and reboot.

Try one thing at a time like that until you pass CTS, or you find what causes the bootloop, and then report back.
[Magisk] ark906i:
Thank you for your best effort to support me. :D

I will do according to your recommendation. I might need time for investigate by systematic approach and do more research.

In case I have any additional progress, I will inform you. ;)
[Magisk] LuisCarlosHK:
I am using oneplus 5 with lineageOS 16.0. I already installed this module, but ctsProfile still reporting false while basicIntegrity reports true.
[Magisk] Didgeridoohan:
If you've run the props command and picked a fingerprint for the OP5 but CTS still fails, take a look here:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Scunkanełi:
I installed busybox and Props Config and sucessfully changed my device fingerprint in order to pass ctsprofile/Safetynet.

Now that this works, am I allowed to uninstall busybox again, while still maintaining ctsprofile=true? I am afraid of apps that check for busybox and ban my account if they find it.

Thank you!
[Magisk] Tahsin Can:
I'm using Nokia 8. How do I solve this problem? I tried the module but Nokia 8 does not.
[Magisk] garylawwd:
Read the op. This module will only help pass cts profile and not basic integrity.
[Magisk] Didgeridoohan:
As long as you're using the Busybox module found in the Magisk modules repo and you've got the apps in question on the Hide list, they won't be able to detect Busybox.

But, if you have everything set up as you want there shouldn't be any problems uninstalling Busybox. The boot scripts will use the Magisk Busybox.

If you mean that there's no Nokia 8 fingerprint, you could help with that:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

But, as already stated, it's not likely that the module can help you if you're also failing basic integrity (sometimes it does, but those are exceptions). There's a corresponding part of the docs for that as well:

https://github.com/Magisk-Modules-R...EADME.md#i-cant-pass-the-basicintegrity-check
[Magisk] VincentJoshuaET:
I've been seeing problems about ctsProfile. I was using the stock 10.3.1.0 fingerprint for Redmi Note 5 whyred (which worked until a couple days ago), already included in my ROM. I changed to Pixel 2 XL using this module and ctsProfile passed again.
[Magisk] martyfender:
[MENTION=4667597]Didgeridoohan[/MENTION] somewhere in the Magisk forums you, (I think) gave better details of the problems edxposed causes and some work arounds. I can't seem to find it now. Do you remember where you posted this? I am trying to give this info on a non-xda thread to those that are clueless that it appears to be an edxposed problem and not a Magisk issue.

Thanks
[Magisk] Didgeridoohan:
Well, I've written about EdXposed in a number of places... All I know about it though, is that EdXposed can break the Magisk boot process and cause the boot stages to get messed up. You can usually see this in the Magisk log, where late_start service fires off right after post-fs-data instead of last, after mounts and MagiskHide.

I've posted a workaround for my module in the module docs. For the general issue, there's no fix as far as I know. The EdXposed Github has several open issues related to this, but last I checked there'd been no real progress (apart from some suspicions that it had to do with the EdXposed SELinux scripts, or something along those lines).
[Magisk] Didgeridoohan:
There's been a few reports along these lines the last couple of days. That CTS suddenly fails where before it did not... It's of course possible that Google have ramped something up as a result of the LZPlay thing, we'll have to wait and see I guess.

But, I tested the whyred print I have in the module (same one, 10.3.1.0) and it passes with flying colours. There might be something else going on rather than the big G overlord suddenly deciding to bring out the big hammer...
[Magisk] Celphor:
Fantastic, works like a charm. Kodus and thank you
[Magisk] VincentJoshuaET:
I think it's because your module also changes to the corresponding security patch date of the fingerprint. The ROM I am using (PE 10) uses the whyred print, but uses the latest security patch date. Another user of the same device also experienced this ctsProfile check fail using another ROM (AOSiP Derpfest 10).
[Magisk] Didgeridoohan:
As far as I know, that's been a requirement for any Android release with a build date after March 16th 2018... Of course, it's possible that Google has been a bit slack about enforcing it up until now.
[Magisk] DragonLe:
My bad, here's the security patch level: 2019-09-05

Also, on Indian devices:

Xiaomi/raphaelin/raphaelin:10/QKQ1.190716.003/V10.4.8.0.QFKINXM:user/release-keys

Same security patch level
[Magisk] realsatarkar:
Just here to say thanks. Just saved my life.

As we all know by now Google did something fishy behind the back & all of a sudden CTS starting failing & as a result all banking apps started failing & detecting root & what else not. I freaked out so much that I was going to flash stock rom & relock bootloader.

Thanks to your hardwork in this module it saved my day. Mad respect for you [MENTION=4667597]Didgeridoohan[/MENTION] ✌?
[Magisk] swour:
After installing Lineage on my device I have found that Safetynet was failing due to a mismatch of the security patch date and fingerprint. The latest official update from Samsung is from September, so I set the custom prop to that value instead of having the module pick an old fingerprint.

Here is the one that should work with the patch date set to 2019-09-01 for Galaxy A5(2017):
[Magisk] VincentJoshuaET:
Yes. It seems that Google just now started what their rule actually is
[Magisk] LoV432:
Reboot does nothing
[Magisk] Didgeridoohan:
You've got EdXposed issues...

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#known-issues
[Magisk] nri_tech1183:
I want to change device fingerprint for my rooted Redmi note 7 pro.

There is no guide at all and never had to do it before.

I have installed Safetypatcher {Module} by hackintosh5

and CTFProfile now shows True and all apps working good but during reboot the phone gives an error:

"You vendor image does not match the system. Please flash HuaweiCLT-L29 vendor image for your device"

I want to clear this message. Please help!
[Magisk] Didgeridoohan:
You're in the wrong thread for support with Safetypatch (but, that message is because that module does not alter the vendor fingerprint). That shouldn't be news though, since I've already posted info about how to fix this in your other thread:

https://xdaforums.com/apps/magisk/csprofile-false-getting-resolved-t3978829

Please try to keep things on topic...
[Magisk] smohanv:
Device: Xiaomi Mi 9

ROM: MIUI 11 (from xiaomi.eu) [Android Q]

Magisk: Canary debug 19.5 flashed

Could not flash this module. Results in error (failed). I tried with magisk stable 19.3 and beta 19.4 as well.

With cts profile "false" could not use Google Pay. Also, Google play settings shows that "not certified".

I was fine when my Xiaomi Mi 9 was running on MIUI 10.

Thanks.
[Magisk] Didgeridoohan:
Installation log would be nice... (Won't work on Canary Manager 240, because of a ui bug).
[Magisk] MartinRK:
Hello, my ctsprofile failed so I use this module to change the device fingerprint. It worked, but the ctsprofile still failed. What else can I do to pass it? Thank you so much!
[Magisk] Didgeridoohan:
If you've successfully changed the fingerprint but still can't pass CTS (but pass basic integrity), take a look here:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] MartinRK:
Hello, it seems that I cannot change the date. Sorry that I always got "bad request" when uploading the graph, I just copy the text. It seems there is no other options for me to choose.

Current boot stage for security patch date is

.

Do you want to change it to ?

Enter , b(ack) or e(xit):
[Magisk] Didgeridoohan:
Something's wrong, obviously, so I'll need the logs.
[Magisk] smohanv:
Hi

Thanks for helping. I installed with stable magisk manager and also flashed stable version 19.3.

See attached log and also screenshot of my magisk manager.

I tried SafetyPartch-v3.zip and flashed in magisk without error. Now my cts profile is passed and safetynet is fully passed. Google Play shows, Certified. Also, Google Pay installed and working well.

SafetyPatch-v3.zip uses Huawei fingerprint keys.

# Code used in post-fs-data.sh

#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
MODDIR=${0%/*}

# This script will be executed in post-fs-data mode
sed 's/ORANGE/GREEN/i' /proc/cmdline | sed 's/YELLOW/GREEN/i' > /data/local/tmp/cmdline
mount -o bind /data/local/tmp/cmdline /proc/cmdline

sed 's;^ro.*\.build\.fingerprint=.*;ro.build.fingerprint=HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys;' /system/build.prop > /data/local/tmp/build.prop
mount -o bind /data/local/tmp/build.prop /system/build.prop
# The build.prop thing seems to be useless, but at some point Google are sure to catch on and check in the raw build.prop to see if we're abusing getprop/resetprop.
resetprop ro.build.fingerprint 'HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys'
resetprop ro.bootimage.build.fingerprint 'HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys'
#resetprop ro.vendor.build.fingerprint 'HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys'
#The above caused issues (critical services not starting) on my Honor

View attachment 4838239
[Magisk] abirkan:
Not working for me :( lineage os 15.1 8.1 Lenovo p2a42
[Magisk] smohanv:
Try SafetyPartch-v3.zip in my post above.
[Magisk] abirkan:
Not working safety patch :/
[Magisk] nri_tech1183:
If you first patched MagiskHidePropsConf.zip disable it from modules, Reboot. Then delete it and reboot again.

Then reboot to recovery and flash SafetyPatch-v3.zip and it should work perfect.
[Magisk] abirkan:
Not working bro :crying:
[Magisk] smohanv:
Use a good root file explorer and add this line in to build.prop (this can be under root/system folder).

After adding this line reboot your device and check safetynet in magisk.

ro.build.fingerprint=HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys

See screenshot of my build.prop and also confirming safetynet pass.
[Magisk] abirkan:
Not working bro.. :S thnx all
[Magisk] Didgeridoohan:
Your installation issue has nothing to do with the fingerprint used. It's an Android 10 issue that I'm fixing for the next release (thanks for confirming). I keep saying I hope to have some time to finish that update soon, but I never do... Let's say soon™. :laugh:

Safetypatch and this module do the exact same thing in regards to the CTS test. My module is just a little more interactive with more settings available. Safetypatch is "flash and forget" (with the limits that follows).

Judging by your screenshot you've got other issues than just not having a certified fingerprint (you're not even passing basic integrity). You need to figure that out first. Take a look here:

https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] smohanv:
Understood. Thanks for your work. I am fine at the moment with SafetyPatch. But will look forward to your module.
[Magisk] casouzaj:
You mean props, don't you?
[Magisk] oslo83:
Friendly bug report 1:

When setting a new custom prop, if you abort creation process like told with n key, it gets stuck.

Friendly bug report 2:

When pasting a string on new prop creation, if you delete some characters, the last you deleted is not.

Friendly bug report 3:

By pasting a wrong string (not sure which one) into new prop creation, now I can't reset anymore that prop (patch02 set to patch02).

Log needed or you see what's happening?
[Magisk] abirkan:
Guys, fix safetynet pass working now :)

nocheck device xposed app :good:
[Magisk] Didgeridoohan:
Great that you found that Xposed module. It can help spoofing the CTS profile response for SafetyNet, true...

But, that's a bit too off-topic for this thread (it's the support thread for MagiskHide Props Config, not a general SafetyNet troubleshooting thread), so could you please edit your post and remove that video (it's hurting my eyes :crying:). :good:
[Magisk] DjDiabolik:
Hi friends... Someone has suggest to use this module.

It's my situation:

I have an oneplus one... I'm currently use tugapower latest v32 whit android 8.x but recently i see i can't, for example, install latest Google chrome browser instead the "old" tugabrowser.

I have installed this module... By built-in terminal i can execute "props" but i don't have idea how i need to configure.

Someone can be suggest how i need to do?

I read some old post here...some speak about cts and security checks inside magisk. Actually i can pass both check whitout any problems and i'm only need to change my SeLinux state to "enforce" instead to "permissive"...