yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
In that case you've got something else going on. I can try to help if you can provide the necessary logs. Both the Magisk logs and module logs would be useful (they're in /cache).
[Magisk] topbasework:
Hai sorry for off topic

All my safety net is pass.i try yr module.all working well.but my local bank still detect root.

Any work around solution for this.i dont know how my bank app ( Public Bank ) still detect root.also i already hide using magisk hide on setting.sorry for bad English
[Magisk] HonorCode:
Thanks Didgeridoohan, but I just flashed the magisk unistall and then reflashed magisk. The second time I tried to use props, it worked... ctsProfile: true. I'm not sure what went wrong the first time.
[Magisk] SnowFuhrer:
Look here for help with that: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] salim0786:
Is it possible that I use an s9 fingerprint on my device which inturn will make amazon video play in hd on my device.
[Magisk] Didgeridoohan:
You can defiinietly use an S9 fingerprint. But, if it'll actually make any difference for HD content is questionable but please give it a shot and report back.
[Magisk] RKRN3@1997:
So, after I update this module to v54 or v55 on MagisK 19.1 or 19.2, no app opens after reboot. I then have to flash the v52 and then everything comes back to normal. I use Pixel Experience CAF on my Redmi Note 3.
[Magisk] HonorCode:
Updated Magisk to 19.2... ctsProfile now false.
[Magisk] Didgeridoohan:
The version numbers you describe isn't for the module, but the fingerprints list. The module is currently at v4.0.3... If I'm going to be able to help I need logs:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs

But first I'd suggest you take a look here:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

If both CTS and basic integrity fails, try toggling MagiskHide off and on again. If it's only CTS and you do have a certified fingerprint applied in going to need logs to be able to help:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] dewettie:
Please add fingerprints and spoofs for AndroidTV devices.

AndroidTV devices run different apps than normal Android and it might cause incompatibilities for apps if you can only spoof phone devices.

Three popular AndroidTV device fingerprints that can be added are

Nvidia Shield

Nexus Player 6.0

https://gist.github.com/wuhx/bfd814bba5f2523449f1

Xiaomi Mi S 8.1

https://www.reddit.com/r/MiBox/comments/9tpay9/xiaomi_mibox_s_mdz22ab_buildprop_file_for/
[Magisk] Didgeridoohan:
Thank you. I already have two Nvidia Shield fingerprints in the list, if you want more you'll have to provide them...

Tested the two others you linked and the Nexus player works fine, but the Xiaomi print does not pass CTS.
[Magisk] Didgeridoohan:
Fingerprints list updated to v56

Quick update of the fingerprints list. Thank you to [MENTION=5438998]dewettie[/MENTION] for the Nexus Player print.

List will update when the props command is run, or by using the -f option or from the Edit fingerprints menu.

New

Google Nexus Player

Updated

OnePlus 3 & 3T (Android Pie, yay)
[Magisk] takxus:
Please this is what it's displaying. Any fix? It is the latest module I'm using.

Here are the logs....
[Magisk] joluke:
No links or images can be seen. Fix your post
[Magisk] ideal4ever:
service.sh not loading at startup

hey guys,

all of a sudden the module is not loading properly for me. it used to work fine. i blame the new magisk's updates, but who am i to say. please, can somebody take a look at the attached logs, and point me in the right direction on how to fix this?

much appreciated
[Magisk] Didgeridoohan:
Disable EdXposed, it is known to cause this issue (the Magisk boot stages are all messed up and running in the wrong order).
[Magisk] raystef66:
[MENTION=4667597]Didgeridoohan[/MENTION]

latest FP on Mi9 - don't know if it's already mentioned but imo this one is newer then the one in 4.0.3

ro.build.fingerprint=Xiaomi/cepheus_eea/cepheus:9/PKQ1.181121.001/V10.2.24.0.PFAEUXM:user/release-keys

ro.build.version.security_patch=2019-04-01
[Magisk] ipdev:
Updated Pixel and Essential fingerprints.

Including Pixel 3a and 3a XL

OnePlus released updates for 7 Pro.

So of course I snagged it

Cheers. :)
[Magisk] salim0786:
Tried that..... Didnt work
[Magisk] Didgeridoohan:
Fingerprints list updated to v57

A few new fingerprints and a bunch of updated ones as well. Shoutout and thanks to [MENTION=5334294]raystef66[/MENTION] and [MENTION=7280276]ipdev[/MENTION] for providing them.

The list will update when running the props command, or (if you've disabled automatic updates) by using the -f option or from the "Edit fingerprint" menu.

New

BLU R1 HD 2018

Google Pixel 3a and 3a XL

OnePlus 7 Pro

Updated

Essential PH-1

Google Pixel 1-3 both normal and XL and Pixel C

Xiaomi Mi 9
[Magisk] x86cpu:
Some updates.

Asus Zenfone 6 (9.0)=asus/WW_I01WD/ASUS_I01WD:9/PPR2.181005.003/16.1210.1904.115-0:user/release-keys__2019-04-01
LG V20 LS997 (7.0)=lge/elsa_spr_us/elsa:8.0.0/OPR1.170623.032/1819814314eb7:user/release-keys__2018-07-01

This one seems to have gotten missed:

LG G6 US997 (8.0.0)=lge/lucye_nao_us/lucye:8.0.0/OPR1.170623.032/181521705197f:user/release-keys__2018_06_01
LG V20 US996 (8.0.0)=lge/elsa_nao_us/elsa:8.0.0/OPR1.170623.032/183241436cd40:user/release-keys__2018-11-01
[Magisk] Didgeridoohan:
I'm not sure about that V20 US996 print, but I tested the G6 US997 print the last time it was submitted and it didn't pass on my device. I only add prints that I can confirm are working...
[Magisk] x86cpu:
Odd they fail. I'm not exactly sure how you test. They are pulled from the build.prop. The US996 I actively use, so I know that works. It's not a big deal to me, I use your module to only override the ro.build.version.security_patch date as I keep the ro.build.fingerprint the same.

https://review.lineageos.org/c/LineageOS/android_device_lge_us996/+/245349

$ pwd
./US99620f_00_1120_system/system
$ egrep 'ro.build.version.security_patch|ro.build.fingerprint' build.prop
ro.build.version.security_patch=2018-11-01
ro.build.fingerprint=lge/elsa_nao_us/elsa:8.0.0/OPR1.170623.032/183241436cd40:user/release-keys

https://review.lineageos.org/c/LineageOS/android_device_lge_us997/+/232353

$ pwd
./US99720b_01_0601_system/system
$ egrep 'ro.build.version.security_patch|ro.build.fingerprint' build.prop
ro.build.version.security_patch=2018-06-01
ro.build.fingerprint=lge/lucye_nao_us/lucye:8.0.0/OPR1.170623.032/181521705197f:user/release-keys
[Magisk] allrockedout:
Needed Mi 9 seen you just updated perfect thanks man
[Magisk] ipdev:
I'm not sure why but, even using a valid fingerprint, something seems to break SafetyNet on some devices.

Some fingerprints seem to work across the board. :confused:

Xiaomi Redmi Go for an example. It's on the certified list. Link

It passes SafetyNet and shows Certified in PlayStore if I test on my Nexus 7.

All other devices, SafetyNet is broken and device status is not certified or not shown in PlayStore.

If you (or anyone) want to try it, it's attached.

The Zenfone 6 and both V20 prints you provided work on my Nexus 7 and Poco F1.

The G6 fails.

17 different LGE G6 models on the list. (If I counted correctly.)

Including LGUS997.

Sorry, my other devices are not currently in a condition to test on.

I'll charge some up and clean flash some and try the G6 print again.

Cheers.
[Magisk] raystef66:
[MENTION=4667597]Didgeridoohan[/MENTION]

updated MI9

ro.build.fingerprint=Xiaomi/cepheus_eea/cepheus:9/PKQ1.181121.001/V10.2.26.0.PFAEUXM:user/release-keys

ro.build.version.security_patch=2019-04-01
[Magisk] Badusha1999:
I cant select device fingerprint option

Well in my Samsung g532f(j2 ace, with custom rom magic os ) does't get any response on MagiskHide Props Config v4.0.3 in option 1 - Edit device fingerprint on

f - Pick a certified fingerprint

If i type f on terminal then nothing happens. Because of i cannot choose any fingerprint. why is it not showing any device finger print please Help me .i hope u will kindly help me solv this problem
[Magisk] Didgeridoohan:
Can't help based on that. Too little info... Here:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] The War Profiteer:
Device will hang on "Phone is starting" after the unlock and will reboot the UI when this specific module installed. Looking for information about the logs that are needed.
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

If issues persist:

https://www.didgeridoohan.com/magisk/MagiskHelp

(And: https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs)
[Magisk] Badusha1999:
I hope this help
[Magisk] Didgeridoohan:
Not at all actually... Did you even open the link I posted for you? Logs, I need logs.
[Magisk] FLASH_ENTHUSIAST:
How to fix this one? here is the log for that
[Magisk] Didgeridoohan:
Once again it's a case of EdXposed destroying the Magisk boot process. Disable it and things will work again.
[Magisk] Akilesh_15:
Updated fingerprint for Nokia 7 plus

Security patch: May (2019-05-01)

Nokia/Onyx_00WW/B2N_sprout:9/PPR1.180610.011/00WW_3_53B:user/release-keys

Verified to pass safety net, on a GSI.
[Magisk] abirkan:
Service.sh not start
[Magisk] Didgeridoohan:
Dammit... I'm gonna have to put a message in there, in large friendly letters, not to panic and just disable EdXposed.

Your issue is that EdXposed messes up Magisk's boot stages.
[Magisk] Merazomo:
Are there apps that just won't work due to root no matter what? I mean, my problem is not so much passing the SafetyNet Check as both my "ctsProfile" and "basicIntegrity" are both green because I'm using the "No Device Check" module (Unless it's a fake pass, since I've heard you can't pass SafetyNet with Xposed installed). My problem is always getting the "this device does not meet the minimum security requirements" etc. for the "JackInTheBox" application for a split second, just to have the app get shut down milliseconds later.

I'm new to Magisk, modules, etc. I had always used SuperSu for basic needs before apps got smarter against root. So are there apps that won't get fooled by any of this "hide root" tricks? I just want to know that for peace of mind, as I feel like I'm doing something wrong here. Thanks.
[Magisk] boilerman92:
Whyred pie

ro.build.fingerprint=xiaomi/whyred/whyred:9/PKQ1.180904.001/V10.3.1.0.PEIMIXM:user/release-keys

ro.build.version.security_patch=2019-05-05
[Magisk] abirkan:
Ok thank you bro ?
[Magisk] Didgeridoohan:
Just passing SafetyNet isn't always enough. You can spoof a passed result with this module or the Xposed module you're using, but many apps are looking for much more than that. Just having the Xposed installer (or other known root apps) installed can get you flagged... And Xposed itself is impossible to hide (EdXposed seems to be easier to hide from detection, but it still seems to be rather experimental).

Here's a summary of some things that may trigger apps looking for root:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Merazomo:
Okay, thank you for the info. At least now I know I'm not crazy. I believed an app was supposed to automatically work just by passing the SafetyNet check. I'm using the LG V20 which doesn't have a lot of Custom ROMs available in comparison to other phones to try out. This phone is not like my older Samsung phones that could almost be used un-rooted. The LG V20 needs to be rooted because of an image retention problem it suffers from, that can only be kept under control by changing the screen colors through root. Thanks again.
[Magisk] Didgeridoohan:
Fingerprints list updated to v58

A few new and updated fingerprints added to the list, which is now at v58. The list will automatically update when you run the props command. Or, if you've disabled automatic updating, with the -f option or from the "Edit device fingerprint" menu.

Thank you to (in no particular order) [MENTION=2881807]x86cpu[/MENTION], [MENTION=5438998]dewettie[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=7908443]Akilesh_15[/MENTION], [MENTION=5334294]raystef66[/MENTION] and [MENTION=7645434]boilerman92[/MENTION] for providing the prints for this update.

New

Asus Zenfone 6

LG V20 LS997

LG V20 US996

Mecool KM8

Xiaomi Redmi Go

Updated

Nokia 7 Plus

Xiaomi Mi 9

Xiaomi Redmi Note 5 Pro
[Magisk] axel531444:
I have OnePlus X, with AEX by shabkhan99 and Magisk 19.3

Somehow (probably) after updating from 19.2 to 19.3 does not pass safety net

ctsProfile : false

basicIntegrity : false

i already try edit fingerprint into oneplus x 6.0.1 and changed my boot stage into post-fs-data

but still it wont pass through safetynet

ps: i dont have xposed or root with supersu. its a clean install, rooted with magisk only
[Magisk] Didgeridoohan:
Have you tried turning it off and on again?

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_fails_after_an_update
[Magisk] axel531444:
after turn off and on again the magisk hide for the second time, it works.

thank you :)
[Magisk] Regadas64:
How add a prop in build.prop with Magiskhide Props Config?

Hello.

My apologies for the writing errors (I'm Brazilian and I do not have a good command of English) and also if I'm posting my question in the wrong place ...

Come on.

I have a Moto Z Play. Android 8.0 with root, TWRP 3.02 and Magisk 19.3.

I need to enter the following key in build.pro:

"persist.debug.wfd.enable = 1"

But I can not because I do not have permissions to change.

I installed the Magiskhide Props Config module and also the BusyBox module.

I accessed Magiskhide and tried to add the prop "persist.debug.wfd.enable = 1" but I get the message that the key does not exist in build.prop.

I also tried to insert only "persist.debug.wfd.enable" and the message was the same.

Could anyone guide me to do this if possible?
[Magisk] Didgeridoohan:
I'm not exactly sure what your problem is about, but this would be the correct entries for what you want to accomplish:

props

5

n

persist.debug.wfd.enable

1

y

Then you need to reboot, which you can do by selecting y again.
[Magisk] Regadas64:
You're fantastic, my friend!

It worked!!!

My error was after step 4. The command does not exist in build.prop I received the message "this prop currently does not exist on your system".

And he did not continue the process thinking that he had gone wrong ...

Now I did the whole procedure according to the sequence you passed and activated what I needed.

Thank you very much...

It's been a few days since I've been looking for a solution to this problem.
[Magisk] Didgeridoohan:
No problem. I figured that it was something like that. That message is simply a piece of information, but you have shown me that it can be misunderstood. I'll make it clearer in a future update. Thank you.
[Magisk] Polkadot.blolobolo:
Hello everyone, sorry for my bad english

Maybe some one can help me

I'am using j500g with custom rom bootleger pie

When I finished installing this module via magisk, my phone always have a system ui force close

Can some one tell help me? Thanks :)
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

And of course:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs

And:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Polkadot.blolobolo:
Thank you sir, I will try it and post it :)
[Magisk] Doomkopf:
Hey, I've got a little problem with this module. I have the Redmi 5 Plus (Vince) and when choosing the Oreo fingerprint, it resets my security patch to March. Doesn't happen with the nougat fingerprint, just Oreo ^^ is this intended behavior?
[Magisk] zilan:
Hi [MENTION=4667597]Didgeridoohan[/MENTION]

my device is xiaomi mi6 running on android 9 pie. but your fingerprint list for xiaomi mi6 is android 8, is it okay to use it? or better use xiaomi mi9?

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

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint
[Magisk] DessertArbiter:
device fingerprint moto g6 ali

here is the device fingerprint from the moto g6 (ali) (not the plus or play) from the 2019-03-06 update (with security patch 2019-02-01):

motorola/ali/ali:9/PPS29.55-34/0c5d:user/release-keys

edit: i got it figured out, now it actually passes safetynet
[Magisk] Didgeridoohan:
Correct. The supplied fingerprint is not certified. The only sure way to get a certified fingerprint is to collect it directly from a device that passes SafetyNet fully.
[Magisk] DessertArbiter:
okay, i will restore my backup of stock and see if i can get a fingerprint that actually works from it

edit: figured it out, i was mostly correct except for the "ali_retail" part, it should be just "ali"

the vendor fingerprint is different from the system fingerprint for some odd reason, no idea why motorola did that

edited my previous post with the correct fingerprint
[Magisk] DessertArbiter:
error 1 in twrp

im trying to get the fingerprint set before it boot this rom, i got the rom and magisk installed fine, but when i put the propsconf_conf in /sdcard and flashed the module in recovery i get "Updater process ended with ERROR: 1"
[Magisk] garylawwd:
You cant do that.

You have to boot the rom flash the module in magisk, reboot, open a terminal app,

type;

su

props

And then follow the instructions on screen to set a fingerprint, reboot and thats it
[Magisk] Didgeridoohan:
I would need the recovery log to know that's going on.
[Magisk] Didgeridoohan:
Actually, that should be perfectly possible. It's also similarly possible I've messed something up in a recent update though... Don't think I've tested that particular feature in a while.
[Magisk] DessertArbiter:
heres the relevant part of the log, i have magisk 19.3:

Installing zip file '/sdcard/MagiskHidePropsConf-v4.0.3.zip'
Checking for Digest file...
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
***********************************
Please install the latest Magisk!
***********************************
Updater process ended with ERROR: 1
I:Install took 0 second(s).
Error installing zip file '/sdcard/MagiskHidePropsConf-v4.0.3.zip'
Updating partition details...
I:Data backup size is 15MB, free: 22984MB.
...done
[Magisk] Didgeridoohan:
That suggests that Magisk didn't actually install fine, but without seeing the recovery log for that I won't be able to say much.

I do not currently have time to test myself, but as far as I can see it should work...
[Magisk] jcmm11:
/data/adb/magisk/util_functions.sh is correct.

I'm running latest Canary. If you have a /data/magisk/ directory I have no clue how you got it or where it came from, but something's not right.
[Magisk] DessertArbiter:
after a reboot the /data/adb/magisk directory appeared so its all good

---------- Post added at 17:56 ---------- Previous post was at 17:05 ----------

somehow no matter what boot stage i choose it doesnt pass, but if i use the fingerprint for moto g6 play it does work, i have no clue why the fingerprint i got from stock, which passed ctsprofile, wont pass ctsprofile with this module

i guess ill go back to stock again to try and figure it out

edit: it passes safetynet fine on stock but im still getting the exact same fingerprint and security patch that i already tried:

ali:/ $ getprop ro.build.version.security_patch
2019-02-01
ali:/ $ getprop ro.build.fingerprint
motorola/ali/ali:9/PPS29.55-34/0c5d:user/release-keys

i attached the relevant prop files (labeled to make them easier to tell apart and .txt bc xda wont let me upload .prop files), i give up for now
[Magisk] DessertArbiter:
i modified the safetypatcher module with the same fingerprints that i tried with this module and it works perfectly, so idk what the deal is
[Magisk] Didgeridoohan:
That is really interesting. You've given me two nice little mysteries to figure out (the other being why you would end up with /data/magisk rather than /data/adb/magisk). I'm very limited for time at the moment, but will try to experiment with this when I get an opportunity.
[Magisk] _cab13_:
Hello

The module works good, but when I use another devices fingerprint, my GSI (PHHUSSON) takes the overlay of the device which fingerprint I used. Any idea of to get my default layout back ?

Or I could use my vendors fingerprint, which is making my phone bootloop
[Magisk] Didgeridoohan:
I have no idea how the overlay on GSI's work, so I can't help with that. But GSI's should be able to use the vendor fingerprint function of the module, so use that instead.
[Magisk] Didgeridoohan:
That log doesn't say much (apart from those seg faults that I've no idea what they're about), except that the boot scripts actually finish and that whatever problem you're experiencing is happening after that.

Catch a boot log please, as described here:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] ~clumsy~:
Thanks. You can see the bootlog.log here
[Magisk] raystef66:
[MENTION=4667597]Didgeridoohan[/MENTION]

If you can do something with the android Q beta MI9 fingerprint, here it is ;)

ro.system.build.fingerprint=Xiaomi/cepheus/cepheus:10/QKQ1.190406.002/9.04.30.2.native.google.user:user/release-keys

ro.build.version.security_patch=2019-05-05
[Magisk] Didgeridoohan:
I'll see if anything can be found in there, but meanwhile, could you experiment a little?

Does it make any difference if you change boot stage for the fingerprint?

Does the same thing happen if you only use the module to change another prop (the custom props function)?

Install the latest Magisk Canary debug build and try again.

Etc...
[Magisk] ~clumsy~:
Thanks, here the follow up answers below.

Does it make any difference if you change boot stage for the fingerprint?

It doesn't seen to to have an affect (already tried it before you asked)

Does the same thing happen if you only use the module to change another prop (the custom props function)?

Only on fingerprint, everything else in the module doesn't affect the phone rebooting.

Install the latest Magisk Canary debug build and try again.

Canary debug build didn't seem to make a differnce, the same affect happens.
[Magisk] Didgeridoohan:
I got some help reading your log, and [MENTION=6815443]JohnFawkes[/MENTION] pointed out there are a lot of avc denials in there. Don't know why, but you could test booting with selinux permissive to see if that's what's causing an issue.

Also does it matter what fingerprint you're using? What if you pick one that's more closely matched to your device (or better yet, from your device)?
[Magisk] ~clumsy~:
I am having issues trying to set my phone to permissive. I tried the few options. The first one was using the boot image command line, that didn't work. Then I tried a boot script in magisk post-fs-data.d and that didn't work. Then finally i just tried by calling setenforce 0 and that returned:

setenforce: Couldn't set enforcing status to '0': Invalid argument

I also tried using toybox and the same result. I have also updated toybox and even my sh binary just encase there was an issues with that but same error is returned. The reason why that doesn't work could be reason why the change in fingerprint doesn't boot my device and probably those segfaults previously. If you have any ideas it would helpful.

Also does it matter what fingerprint you're using? What if you pick one that's more closely matched to your device (or better yet, from your device)?

Yeah, any fingerprint. I tired the one for my device and it still happened.
[Magisk] Didgeridoohan:
I've seen reports of some devices not being able to use "setenforce 0", but instead has success with "setenforce permissive". You could try that. But, it might also be that your device's kernel simply does not allow a permissive SELinux...