yashsingh1/xdaforums huggingface dataset:
[Magisk] margalvezsimarro:
Is it valid if I update magisk? Because... Before installing the module I had just updated to v20.1. gonna try reinstalling later
[Magisk] casouzaj:
Yes, I'm running this module in order to pass the CTS profile test, which the custom ROM I'm running on my Sony Xperia Z5 Compact phone doesn't originally pass that test. Nevertheless, it's only working (including tricking the Intune app, provided that it is hidden in Magisk Hide list) , after I run (only once) the props command in a terminal emulator app, and enter 1 > f > brand > model > y > y. After reboot, profit!
[Magisk] MrHomebrew:
Got another working key in preparation for a new twrp and custom ROM release for another variant of the Galaxy Tab A sm-t597 to be more specific. There are 3 variants of the Galaxy Tab A 10.5.

DEVICE KEY IS AS FALLOWS BELLOW:

Galaxt Tab A (LTE SM-T597) (9)=samsung/gta2xlltespr/gta2xlltespr:9/PPR1.180610.011/T597PVPU2BSH7:user/release-keys__2019-08-01
[Magisk] MrHomebrew:
Latest key needed for the soon to be released TWRP and custom ROM for Galaxy Tab A 10.5

Galaxt Tab A (LTE SM-T595) (9)=samsung/gta2xlltexx/gta2xllte:9/PPR1.180610.011/T595XXU3BSF3:user/release-keys__2019-06-01

---------- Post added at 01:33 AM ---------- Previous post was at 12:40 AM ----------

Fixed those two nvidia shield TV 2017 and shield TV pro device keys.

Both tested and working on multiple devices.

Nvidia Shield TV (2017) (9)=NVIDIA/darcy/darcy:9/PPR1.180610.011/4086637_1604.6430:user/release-keys__2019-07-05

Nvidia Shield TV (Pro) (9)=NVIDIA/foster_e_hdd/foster:9/PPR1.180610.011/4086637_1604.6430:user/release-keys__2019-07-05

I know it takes time but will be nice to see all these added to the list of fingerprints in the model.

Appreciate all your help, time and work put into this module.
[Magisk] olivercervera:
Hey, here's the fingerprint for Xiaomi Redmi Note 8T

xiaomi/willow_eea/willow:9/PKQ1.190616.001/V10.3.5.0.PCXEUXM:user/release-keys

Security Patch date: 2019-10-01
[Magisk] Didgeridoohan:
Fingerprints list updated to v69

A few more fingerprints submitted, tested and added. Thank you to [MENTION=5234347]Leonidas87[/MENTION] and [MENTION=3341206]olivercervera[/MENTION] for providing them.

New

Samsung Galaxt Tab A LTE

Xiaomi Redmi Note 8T

Updated

Nvidia Shield TV 2017

Nvidia Shield TV Pro
[Magisk] Dark Sam:
No fingerprints list for realme devices??
[Magisk] Didgeridoohan:
The current list with all included fingerprints can be found both in post #3 and in the documentation.

No Realme devices at the moment...

If you'd like to, you can help finding prints for those devices and post them here.
[Magisk] carlos974:
[MENTION=4667597]Didgeridoohan[/MENTION]

Samsung A3 2015 SM-A300FU

I added in the prints.sh file this fingerprint.

It works ! :good:

- Certified store

- SafetyNet control passed with:

ctsProfile: true

basicIntegrity: true
[Magisk] BenDavid:
New Xiaomi Redmi Note 4 fingerprint:

xiaomi/mido/mido:7.0/NRD90M/V9.6.1.0.NCFMIFD:user/release-keys
[Magisk] dirafm:
any clue how to fix fingerprint in treble gsi? i tried to change fingerprint but nothing happened
[Magisk] Didgeridoohan:
Exactly what does "nothing happened" mean? I'm assuming that CTS still doesn't pass, but did the module fail or something else?

There's a feature under "Edit device fingerprint" specifically for Treble GSIs, did you use that? Or, if not, what exactly did you do to set up the module?

For any further troubleshooting I'm going to need the module logs... Take a look in the docs for details:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] Didgeridoohan:
Fingerprints list updated to v70

There's been a couple of fingerprint submissions recently, so I figured I would check them out. Thank you to [MENTION=7764478]BenDavid[/MENTION] and [MENTION=7480554]carlos974[/MENTION] for providing them. List updated to v70.

New

Samsung Galaxy A3 2015

Updated

Xiaomi Redmi Note 4/4X
[Magisk] foobar66:
Thanks. Works great. Was banging my head on getting Google Pay to work on the rooted beta6 OnePlus 7pro android 10.

Worked flawlessly with this module (using the 7T fingerprint).
[Magisk] wmiki75:
I have a little problem.

I installed Canary Magisk, Busybox module, then this Props Config, and then Terminal EMulator.

Enter SU is ok, but when i enter props command, i get: not found :(

What is wrong?
[Magisk] Didgeridoohan:
Your device doesn't mount the system mirrors properly (not at all, in fact), so Magisk can't do it's thing of mounting files over those systemlessly.

A fresh install of Magisk might help...
[Magisk] wmiki75:
Uninstalled MAgisk, reinstall Magisk 20.1. zip , BusyBox, Magisk Hide, and i got the same message in Terminal:

props - not found :(
[Magisk] trancinguy:
Met too, usually after I install Osmosis Busy box, I get props, but Lineage17 s10+ says

"Inaccessible or not found".

Edit. Actually it worked the problem was the internal lineage command prompt, Termux worked, but when I rebooted to recovery because lineage 17 s10+with Magisk demands that, I got boot loop.
[Magisk] Didgeridoohan:
Same issue. If you want to use modules that mount files systemlessly you're gonna have to take a look at fixing that. I can currently not remember if there's any easy fix. Search in the Magisk forums...

You can still use this module though, since you can set it up completely without running the props script. Take a look in the docs on how to use the configuration file:

https://github.com/Magisk-Modules-R...nfig/blob/master/README.md#configuration-file
[Magisk] dirafm:
thansk for the respond, first when i select edit device fingerprint, something show like ro build fingerprint doesn't seem exist, and second yeah i remember there was treble gsi option when i was in unff lineage , but theres nothing like that after i use gsi:confused:
[Magisk] Didgeridoohan:
From that description it sounds like the collection of the original prop values isn't working as expected on your device... Without the aforementioned logs I can't say more than that.

If you haven't tried it already, you should be able to select a certified fingerprint regardless if the module can detect the ro.build.fingerprint prop or not.

But, logs would be awesome.
[Magisk] wmiki75:
There is older versions of MagiskHideProps v5.1.0-v70 ? Where can i find?

I make a try an older version. props not found yet :(
[Magisk] Didgeridoohan:
All releases can be found on GitHub (link in post #1).

But it won't make a difference for your issue, since it's not module related. It's an issue with Magisk on your device.

And like I said earlier, you can get things set to with the configuration file so you won't need the props script at all.
[Magisk] wmiki75:
I do not understand, how the configuration file is work :D
[Magisk] Didgeridoohan:
Have you read through the instructions in the module documentation and in the configuration file itself (scroll down)?

If you've read through that (it's quite detailed, so make sure to read it all) and still don't know what to do, your going to have to start asking more specific questions about what it is you do not understand. I'll have a really hard time providing any kind of help otherwise...
[Magisk] wmiki75:
I try to read, but my english knowledge is weak.

So i understand the half of the text.

If i correct: i must to copy the propsconf_conf to the root of my i9195i internal storage ?

But before it, i must edit the propsconf_conf file, but i not understand, how?

There is some edited propsconf_conf files somewhere?

I have a Samsung S4 mini VE i9195i, with custom ROM, android 7.1.

I want to show it a most popular, unrooted phone, with original FW.

Samsung S9, S10e, Honor10, Huawei P30 or an other wide supported phone.
[Magisk] Vanmanman:
TWRP Install

Can you install this with TWRP and no magisk? Will it work without magisk? Magisk puts my phone into recovery bootloop that im not sure how to fix yet. MI9T MIUI 11.0.1.0
[Magisk] JudgeDread11:
Read the OP. If after that you don't know the answer, better not use this.
[Magisk] Didgeridoohan:
Ok. So if I understand you correctly, you want to simulate other devices. There's a pretty basic (as in: it might not work as well as you'd like) feature in the module that does that by changing some prop values based on the currently set fingerprint.

If you can't fix Magic Mounting on your device, you can use the configuration file as you've described. To set it up you would have to take a certified fingerprint (take a look in the prints list) and change the CONFFINGERPRINT variable in the config file to that print.

To then enable device simulation you need to change CONFDEVSIM, and then also the other variables under the "Device simulation" section of the configuration file, to true.

Keep in mind that this feature has a great risk of causing your device not to boot. If that's the case you've got some tips in the documentation on how to proceed.
[Magisk] Didgeridoohan:
This is purely a Magisk module... If you don't have Magisk you'll just have to edit build.prop the old-fashioned way (if possible).
[Magisk] Vanmanman:
My installed magiskhide doesn't show up in magisk modules list but if I enable magiskhide in terminal app it shows up on the magisk side menu to hide root from apps after a minute or two
[Magisk] ipdev:
Some fingerprint updates. (Not sure if these have been updated yet.)

Was waiting for the Pixel 4 updates, then got sidetracked by life and a device/project.

Essential: PH1

OnePlus: 3, 3T, 6 and 6T.

Pixel: All phones. (sailfish/marlin got a December update).

Cheers. :cowboy:
[Magisk] :
Fingerprint for Redmi Note 8 Pro(India) Redmi/begoniain/begoniain:9/PPR1.180610.011/V10.4.4.0.PGGINXM:user/release-keys
[Magisk] Didgeridoohan:
Thank you, but the security patch date is also needed.
[Magisk] Didgeridoohan:
I'm sorry, but I actually don't know what you're saying here... You're going to have to try to be more clear.
[Magisk] :
Is it same as android security patch level? If so then my patch is 2019-09-01
[Magisk] Vanmanman:
Sorry I re edited it but dosnt update your quote. Was like I was drunk writing that.

My installed magiskhide doesn't show up in magisk modules list but if I enable magiskhide in terminal app it shows up on the magisk side menu to hide root from apps after a minute or two. Probably the wrong place to ask. But other modules seem to be doing an install but not showing up in masgisk module list if you can be of any assistance? :)

When Installing I had to do the below to stop a bootloop. Not sure if its affected the magisk install modules list

Go to /data/adb/magisk/chromeos find "futility" file. Permission 644 for it.

Go to /data/adb/magisk find "BusyBox" file and permission 664 for it.
[Magisk] Didgeridoohan:
Yes, you're right that this has nothing to do with this thread or module. This module is

not

MagiskHide, but simply a tool to change props. MagiskHide is an integral part of Magisk, not a module.

Changing those permissions are the reason you have to manually enable MagiskHide and why you can't install modules. You're breaking important internal parts of Magisk by doing that... It's not a solution, merely a poor workaround.

I'd suggest you keep discussing in your device's forum and try to work together to figure it out.
[Magisk] uriii13:
In Magisk 20.1, Hide is not working on my bank app ("Sabadell Wallet"). Someone knows something? Should I downgrade some Magisk version?
[Magisk] Didgeridoohan:
You've ended up in the wrong thread for that kind of topic...

But, take a look here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

There's a plethora of information on how to hide root from apps there. If you still can't figure it out, you'll need to try to figure out what's triggering the app, or ask for help in the general support thread or one if the many threads on the same topic (bank apps detecting root).
[Magisk] truelies1:
Do you have an example on how to use this to modify a build.Prop line?
[Magisk] Didgeridoohan:
You mean the "Custom props" function? It's generally as easy as running the props command in a terminal and then following the on-screen instructions...

Also take a look in the docs:

https://github.com/Magisk-Modules-R...master/README.md#changeset-custom-prop-values

Note that the build.prop file won't actually be edited...
[Magisk] Kuro95:
Hey,

first of all, thanks for providing this tool to the community, it is really powerful!

I tried to fix the fingerprint of my Mi6 because of the false ctsProfile. Module loaded fine, typed su into the termimal and the tool worked flawless.

But, my fingerprint is still the same after reboot, regardless if I reset it or choose the fingerprint corresponding to the model. It seems to be just locked at this wrong fingerprint.

Do you have any idea what could be happening? No other modules active other than busybox.

Thanks in advance!
[Magisk] Didgeridoohan:
[MENTION=7136554]Kuro95[/MENTION] According to that screenshot you've successfully changed the fingerprint from a Mi 6 to a Pocophone F1. What makes you say that it failed?

Could it have something to do with this:

https://github.com/Magisk-Modules-R...rop-doesnt-change-after-setting-a-custom-prop

If not I'll need more info (and preferably logs).

Edit: taking a closer look, you might not be using this module to change your fingerprint, so that might be part of the problem. The above mentioned logs and details would be nice.
[Magisk] Didgeridoohan:
Fingerprints list updated to v71

Can't sleep, so I might as well pretend to be productive...

Have had a bunch of certified and tested fingerprints waiting to be added, so here goes. Thank you to [MENTION=7280276]ipdev[/MENTION], [MENTION=8944774]Sanish Patil[/MENTION] and [MENTION=4658360]corsicanu[/MENTION] for providing the prints for this update.

New

Samsung Galaxy A51

Samsung Galaxy M20

Samsung Galaxy S10 Plus SM-G975F

Xiaomi Redmi Note 8 Pro

Updated

Google Pixel

Google Pixel XL

Google Pixel 2

Google Pixel 2 XL

Google Pixel 3

Google Pixel 3 XL

Google Pixel 3a

Google Pixel 3a XL

Google Pixel 4

Google Pixel 4 XL

OnePlus 3

OnePlus 3T

OnePlus 6

OnePlus 6T
[Magisk] shivang_bagh:
I used the module and set my fingerprint as pixel 4 and enabled device simulation too ,but after reboot it set my fingerprint as pixel 2 and not pixel 4 , now no matter what I do choosing any different fingerprint or resetting the fingerprint , nothing works , it's fixed as Google walleye pixel 2 and not changing from that value , I am unable to reset to my original device fingerprint also.
[Magisk] TigerKing:
Xiaomi Redmi Note 4/4x fingerprint:

getprop ro.build.fingerprint

xiaomi/mido/mido:7.0/NRD90M/V11.0.2.0.NCFMIXM:user/release-keys

getprop ro.build.version.security_patch

2018-12-01

Finding a certified fingerprint For Xiaomi devices only (more easier method):

1. Download latest firmware file (not recovery/fastboot ROM) from https://xiaomifirmwareupdater.com/

(If you have latest recovery ROM file for your device then you can try that)

2. Copy firmware file to device and flash it through recovery.

3. Then copy recovery log to device,

In TWRP recovery goto "Advanced>Copy Log>Copying Logs to SD card.." (untick on Include Kernel Log)

4. Open that "recovery.log" with notepad++ or any text editor and search for -

"Target: "

5. After "Target: " you will get Certified Fingerprint of your device.

Tried and Tested on Redmi Note 4x

Thank you. :)
[Magisk] Didgeridoohan:
I'll need logs if I'm going to be able to say anything at all about that... The instructions are in the docs:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] TigerKing:
EdXposed Manager 4.5.2 and 4.5.2 are getting detected..

Insted of that use old EdXposed Installer 2.2.4 release

Working for me..
[Magisk] Biggest_Noob:
Can u add realme fingerprint
[Magisk] Didgeridoohan:
Not quite sure what that has to do with the module... If you mean that SafetyNet fails with EdXposed, have you tried the EdXposed Manager blacklist?

But, please keep that discussion in a more relevant thread.
[Magisk] Didgeridoohan:
I could if had a fingerprint for it...

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] TigerKing:
Safety Net Fails with EdXposed,

EdXposed Manager blacklist also not worked for me tried hiding everything with sudohide but no help.

Then tried earlier version EdXposed Installer 2.2.4 which worked, SafetyNet passed.. at least for me on Redmi Note 4x (mido)

Sorry for irrelevant post, I read "SafetyNet failed with EdXposed blacklist workaround" in previous post.. so posted it quickly.
[Magisk] tlf55:
Hi, as you closed the private message I ask here, do you use exposed installer 2.2.4 with this module magiskhide props ? And also does the safety net pass even after a simple reboot ? Also do you use the black list mode in exposed installer ?

Edit : anyway i tired myself and didn't work so either you're lucky either it won't last :)
[Magisk] TigerKing:
Fingerprint Lenovo K6 Power K33a42:

127|K33a42:/ $ getprop ro.build.fingerprint

Lenovo/karate/K33a42:7.0/NRD90N/K33_S231_171114_ROW:user/release-keys

127|K33a42:/ $ getprop ro.build.version.security_patch

2017-11-01

Below are the other versions of firmware with build date before 2018=

Lenovo/karate/K33a42:7.0/NRD90N/K33_S229_170908_ROW:user/release-keys

Lenovo/karate/K33a42:7.0/NRD90N/K33_S223_170610_ROW:user/release-keys

Lenovo/karate/K33a42:6.0.1/NRD90N/K33_S150_161114_ROW:user/release-keys
[Magisk] Biggest_Noob:
Will try to provide you
[Magisk] TigerKing:
May be because security patch for my device is 2019-4-1..

please don't discuss here..

Not related to op..

[MENTION=3835192]tlf55[/MENTION]

Try installing HiddenCore module in EdXposed..

Or try installing SafetyPatch in Magisk Manager

For me, on Redmi note 4 - EdXposed Installer worked with blacklisting

On Lenovo K6 Power - SafetyPatch module in Magisk and EdXposed blacklisting worked

On OnePlus X - HiddenCore Module in EdXposed with blacklisting worked

If not then try hiding EdXposed app from Google Play Store, services and services framework using SudoHide..

Hope it helps..
[Magisk] dlhxr:
Xiaomi MIX2 Newest Fingerprint

ro.build.fingerprint

Xiaomi/chiron/chiron:9/PKQ1.190118.001/V11.0.3.0.PDEMIXM:user/release-keys

security patch

2019-09-01
[Magisk] DjDiabolik:
i have right now installed the module 5.1.0 v68. from magisk manager i see it's available the v71. how i can update them whit maintain the current preferences?
[Magisk] Didgeridoohan:
If you have an older fingerprints list installed you just have to run the props script and the list will update (or add the -f option of you've disabled automatic updating of the list).
[Magisk] DjDiabolik:
and i don't need to update the module on magisk manager?
[Magisk] Didgeridoohan:
No, but that would work as well.
[Magisk] Micdu70:
Xiaomi Mi 9T MIUI 11 Android 10 Global and EEA fingerprint build (Thanks to [MENTION=5886033]robi10101298[/MENTION] for the EEA one!)

ro.build.fingerprint

Xiaomi/davinci/davinci:10/QKQ1.190825.002/V11.0.1.0.QFJMIXM:user/release-keys

security patch

2019-12-01

----------------------------

ro.build.fingerprint

Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V11.0.1.0.QFJEUXM:user/release-keys

security patch

2019-12-01
[Magisk] Micdu70:
And many thanks for your amazing Magisk module! :)
[Magisk] DjDiabolik:
exact.... but after the installation I should reconfigure everything :) I leave installed the v58 module at this point :)
[Magisk] Didgeridoohan:
User settings are always kept when updating or reinstalling...

Only in special circumstances would you need to reconfigure everything.
[Magisk] jelbo:
Tried this on my S10 using the propsconf_conf configuration file, in which I added two lines with custom props.

After a reboot it rebooted again, as the readme tells me:

What I forgot is that the S10 needs to reboot to recovery in order to boot with Magisk. Anyway, I rebooted to Android with Magisk myself, but then I was greeted with a Samsung account login screen behind my lockscreen, for which I had 2 seconds to fill in my password, before my phone locked again.

Ok, I thought, let's disable the module using mm. Problem persists. I'm trying to do a nandroid restore now...

/edit: nandroid restore is tricky because I updated my firmware after my last backup...
[Magisk] Didgeridoohan:
That sounds like a bit of a pickle...

I don't see how the module itself, or the reboot, could have caused that. What were the custom props you added?
[Magisk] jelbo:
A pickle indeed. These two lines:

# Set custom props
CONFPROPS="
ro.config.iccc_version=iccc_disabled
ensure ro.config.tima=0
"

from bullet 3 in this post. Maybe some other defaults in the config file triggered some Samsung security mechanisms.

I'm now at the point where I can boot normal Android again. I used Samsung's remote unlock to unlock my phone, But as soon as I boot Android with Magisk, Magisk manager force closes right away and causes a soft reboot. It then won't boot normal Android anymore, unless I clear cache and dalvik/art from TWRP.

I have now cleared Magisk Manager's data and uninstalled it from normal Android. I'm a little bit afraid to boot to Android with Magisk now. /edit: when I do it keeps soft rebooting after showing the initial Android GUI. So that's even without Magisk Manager. Non Magisk-patched Android does work. Uff. I'll have to think hard on the best next steps...
[Magisk] Didgeridoohan:
By default the config file does nothing... My best guess is that those props might have triggered something. But, I don't know much about Samsung's shenanigans, so I can't really say.

Sounds like you would be best served by doing a full reinstall of Magisk. And, considering my limited skills involving Samsung stuff you'd likely find better help in the Sammy forums.
[Magisk] jelbo:
Yeah, it's going to be Samsung specific now. I'll re-flash my Magisk-patched firmware files and hope that fixes it. Thanks for your replies.
[Magisk] ipdev:
Just some fingerprint updates.

Essential PH1

OnePlus 6T

Pixel 2(s) 3(s) and 4(s)

Cheers all. :cowboy:
[Magisk] Some_Random_Username:
[MENTION=4667597]Didgeridoohan[/MENTION]

Latest OnePlus 5 and 5T fingerprints from OOS 9.0.10 (Android Pie, 2019/12/01 security patch)

OnePlus/OnePlus5T/OnePlus5T:9/PKQ1.180716.001/1912311102:user/release-keys

OnePlus/OnePlus5/OnePlus5:9/PKQ1.180716.001/1912311102:user/release-keys
[Magisk] estofjlw:
ro.build.fingerprint (s) below

[MENTION=4667597]Didgeridoohan[/MENTION]

Does this Magisk Hide Props Config Module ALSO hide the unlocked bootloader like the SafetyPatch module does - claims to ??

I also posted this below in the SafetyPatcher forum

I would like to add my fingerprint to the safetypatcher startup shell file and remove the HUAWEI fingerprint

I have a Moto G7 Power (XT1955-5 Ocean RETUS) with cRDdroid on it and I have SafetyPatcher and Magisk Hide Props Config modules installed under Magisk.

Currently Magisk Manager reports the SafetyNet passes both green checks and the root checker reports HUAWEI as the fingerprint. It is also hardcoded in the /system/.build.prop file.

The ro.build.fingerprints are

motorola/ocean/ocean:9/PPOS29.114-134-4/e8b9:user/release-keys

motorola/ocean/ocean:9/PPOS29.114-134-7/d9234:user/release-keys

One is for the 134-4 version and the other is for the 134-7 version update 12/5/2019

I am not clear on how much of this and the format how to put in the startup shell in the /data/adb/modules/safetypatcher/post-fs-data.sh file

Can you provide me with that info so I do not screw up the SafetyPatch module booting and if I need to also manually edit the /system/build.prop file ??