yashsingh1/xdaforums huggingface dataset:
[Magisk] Emerald Juice:
Please update fingerprint for Samsung Galaxy S9+ (SM-965F) for Android Q (10.0.0).

Thanks @
[Magisk] Ninive:
Hi,

Here is my small contribution to the fingerprint list.

Xiaomi Mi 8 Lite (Global Version - Extracted from stock rom as I already installed a custom rom but worked fine for me) :

Fingerprint :

Xiaomi/platina/platina:10/QKQ1.190910.002/V11.0.2.0.QDTMIXM:user/release-keys

Security_patch :

2020-04-01

Manufacturer :

Xiaomi

Model :

MI 8 Lite

Xiaomi Poco X3 NFC (European Version - Directly from a non-modified device) :

Fingerprint :

POCO/surya_eea/surya:11/RKQ1.200826.002/V12.5.7.0.RJGEUXM:user/release-keys

Security_patch :

2022-03-01

Manufacturer :

Xiaomi

Model :

M2007J20CG

Hope it helps.
[Magisk] sunchau:
Manufacturer :ASUS

Device: Zenfone 8

ROM: WW-31.1010.0410.72

Fingerprint:

asus/WW_I006D/ASUS_I006D:12/SKQ1.210821.001/31.1010.0410.72:user/release-keys

security patch :2022-04-05
[Magisk] dodo2244:
ROM Info source Firmware.Mobi
[Magisk] 0wdj:
So I used Device Simulation and got my OnePlus 8T broken into bootloops.

I managed to get out of it by going into Safe Mode and disabling the module. I was wondering if I can uninstall it now via Magisk in a safe way and be sure not to have corrupted props, or do I have to re-enable the module and do a clean reset of the settings before uninstalling it?

Basically, my goal is to get all the default settings back on the props.
[Magisk] zgfg:
Now, when the modules are disabled, reboot in Magisk and uninstall the module(s) you want

Modules are systemless, hence MHPC will not leave any mess
[Magisk] m0han:
just as a 'sidenote': some of the latest twrp recovery 'mods' have a feature to (2)

disable

last/all module and

remove

last module.

also seen is a (1)

fake encryption

feature. wonder if that can be used to avoid detection in momo, e.g. knowledgeable comments, pls. - if not ot.
[Magisk] 0wdj:
My device is working again and so does GPay, but the main problem with my OnePlus 8T is that the fingerprint authentification doesn't work anymore.... If I disable MHPC, Fingerprint is working but GPay recognized my rooted device and is blocked...

How do I solve this issue?

My Android security patch is saying 05 february 2022 so I guess it's not about the date?

Much thanks
[Magisk] tejljr:
Sony Xperia Z Ultra​

Android version: 12L

ROM: LineageOS 19.1 Unofficial

Root Method: Magisk 23.0 Unofficial

Codename: togari

Device Fingerprint: Sony/C6833/C6833:5.1.1/14.6.A.1.236/834130922:user/release-keys

Security Patch Date: 2022-05-01

Manufacturer: Sony

Model: C6833
[Magisk] m0han:
replying to myself. "Fake encryption" is a module for Magisk, which adds a flag to system.prop to falsely enable encryption. And the system thinks that encryption is enabled.

it works; avoids detection in momo. go here if interested in screenshots.
[Magisk] ashatter:
I found the module is from a Russian website which I don't have an account. Do you know if I can get it somewhere else other than TWRP?
[Magisk] Sid220:
Anyone has tried this module on LineageOS 19.1 or any A12 rom?
[Magisk] ShaDisNX255:
Samsung Galaxy A52 4G (SM-A525F)​

Build fingerprint:​

samsung/a52qnsxx/a52q:11/RP1A.200720.012/A525FXXU4BVC2:user/release-keys

Android version:​

12

Security patch:​

ro.build.version.security_patch=2022-03-01

Manufacturer:​

ro.product.system.manufacturer=samsung

Model:​

ro.product.system.model=SM-A525F
[Magisk] fineb:
I messed up my XZ2. it was on Stock ROM, rooted with Magisk and I wanted to pass the SafetyNet checks and used MagiskHide Props config to spoof the fingerprint, result was a non booting device .-(

I can start TWRP, trying to fetch the logfiles has no success, all files under data/media/0 have strange filenames like ZTX7dthXB6PJDJRQh5sq5B, I can't open these files in the TWRP terminal nor can I copy them to my PC.

I tried to put the original fw with the help of munjenis newflasher on the device, no success, the error message:

ERROR: boot_a: Hash of data does not match digest in descriptor.

The only access to the phone is via TWRP, ADB sideload works, but I don't know what to do.

Any help is welcome
[Magisk] zgfg:
To pass SafetyNet with Stock ROM you needed first to try with USNF - for stock (if ROM is certified) there is no need to spoof fingerprints by the MHCP module

With TWRP you should put the file named disable (exactly as that) or uninstall to the folder:

/data/adb/modules/MagiskHidePropsConf/

But if TWRP does not recognize files and folders on /data then:

- you either didn't type in your Android pin/pass when booted to TWRP

- you are not using correct (the latest) TWRP for your phone

- or there is no TWRP supporting your device/ROM (generally, TWRP does not support yet encryption on Android 12 and therefore it cannot work with the files and folders on Data and Internal memory)

In that case bad luck, you could not resolve by TWRP.

You have two other options, Android Safe Mode (booting once to Safe Mode will disable all modules) or using adb to uninstall all modules:

adb wait-for-device shell magisk --remove-modules

For more details, consult GitHub Magisk site, Wiki, find the chapter how to resolve bootloop caused by the module
[Magisk] Invisible 09:
I Hope I'm Not Late

Xiaomi Redmi 9C Non NFC

( codename : Angelica )

Rooted With Magisk V25 Official

ROM: Stock

Redmi/angelica_global/angelica:10/QP1A.190711.020/V12.0.11.0.QCRLMCR:user/release-keys

(Fingerprint)

2022-04-01

(Security Patch)

Xiaomi

(Manufacturer)

M2006C3MG

(Model)

Passing Basic Integrity and CTS Profile with Deny List and Universal Safety Net
[Magisk] Rickyster:
I am using OnePlus 9RT India (MT2111), the latest fingerprints added shows only OnePlus 9RT China (MT2110). Should I use that or wait for fingerprints of Indian model? Or is there other way to pass CTS?
[Magisk] ipdev:
You should be able to use any of the certified prints.

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

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

If you can find the OnePlus 9RT India (MT2111) fingerprint and matching security date. Feel free to submit it. 🙂

MHPC Documentation - GitHub

- Please add support for device X - Link

- Finding a certified fingerprint - Link

- Matching the Android security patch date - Link

- How do I submit a fingerprint? - Link

Cheers. :cowboy:
[Magisk] ZenurikSD:
Hello, I'm currently on a Moto G5S (montana) and using the official LineageOS 18.1 from @JarlPenguin. I have only this module active but I the fingerprint doesn't seem to be applying correctly. Verifying YASNAC and Momo my android version and security patch date do not change, resulting in not passing the basic integrity test.

They still show as follows

Android version:	Security patch level:
11 (API 30)	22-05-05

When I believe it should be version 8.1.0 and sec.path 19-08-01, as those were/are the defined fingerprint values:

I should probably add: I tried a bunch of other devices fingerprints and the behavior is the same.

I'm I wrong assuming this?

Any help would be appreciated.
[Magisk] mrspeccy:
Samsung Galaxy Tab A7 10.4 LTE (2020)

[ro.product.manufacturer]: [samsung]

[ro.product.model]: [SM-T505]

Android 12L (security path 1st June 2022)

Fingerprint:

samsung/gta4leea/gta4l:12/SP1A.210812.016/T505XXU3CVE7:user/release-keys
[Magisk] pigbedleg:
I have the same model phone looking for a forum not well designed phone the best part is the rugged screen with a low cost phone one fall out of pocket bricks phones with a glass screen these things are cheaper than a screen repair. Better design for outdoors.
[Magisk] ShaDisNX255:
Samsung Galaxy A52s 5G (SM-A528B)​

Build fingerprint:​

samsung/a52sxqxx/a52sxq:12/SP1A.210812.016/A528BXXS1CVF1:user/release-keys

Android version:​

12

Security patch:​

ro.build.version.security_patch=2022-06-01

Manufacturer:​

ro.product.system.manufacturer=samsung

Model:​

ro.product.system.model=SM-A528B
[Magisk] ipdev:
*** New Device Forum Requests *** - Link

No guarantee. 🙃

Cheers. :cowboy:
[Magisk] ipdev:
Hmm. 🤔

Moto G5S (montana)

Released (2017) with Android 7.1 ?

When you test SafetyNet using YASNAC.

What does it show for Evaluation Type?

Basic or Hardware

After you change the fingerprint with this module and reboot.

What do you get when you check the props using the command line?

getprop | grep fingerprint

getprop | grep security_patch

Cheers. :cowboy:
[Magisk] shock3minutes:
Android version: 11

ROM: LineageOS 18.1 official

Root Method: Magisk 23.0 official

Codename: platina

Build fingerprint :

Xiaomi/platina/platina:10/QKQ1.190910.002/V12.0.3.0.QDTMIXM:user/release-keys

Android version :

11

Security patch :

2022-06-05

Manufacturer :

Xiaomi

Model :

Mi 8 Lite
[Magisk] itzmeandyos:
Doesn't work with LineageOS 17.1 (unofficial) Android 10 on Samsung Galaxy J7 2016 j7xelte SM-J710F, help bc its my main phone rn
[Magisk] ShaDisNX255:
If you want people to help you out, it'd be better if you provided more details than just your ROM and device. What safetynet checker are you using? What are you failing? What other steps have you taken?
[Magisk] Noobiemada:
I need this please help me
[Magisk] Smu1zel:
Search "bkerler mtkclient GitHub" and you can find it. I basically just made a full flash backup with the "rf" command (Incase something went wrong) and followed the steps under "Root the phone". I just used a VM of the livedvd but Windows may work too.

Volume down while plugging the phone in with the tool running should get you into BROM mode as far as I can remember.

Be warned in that for some odd reason I've had this phone with it's battery out for a while now because it literally will turn itself on at exactly 5:02AM (might just be buggy firmware I don't know).

Just read the readme in the GitHub page and you can probably figure it out from there. It's very easy to brick you device with this (not much of a loss with these things at $50 a piece), so don't run a command (or click a button like "Erase preloader" in the GUI) if you don't know what it does!

Will also note these things won't let you past setup without an active sim card (an inactive one doesn't work).
[Magisk] Noobiemada:
Ok thanks alot for your help it's greatly appreciated.
[Magisk] sappounet:
I've temporary re-flashed the latest Samsung ROM for my S10e, so please find below latest props values.

Samsung S10e - SM-970F

Official Samsung ROM G970FXXSFHVF1 on Android 12

Samsung Galaxy S10e (SM-G970F) - XEF - G970FXXSFHVF1 firmware

Fast download latest Samsung Galaxy S10e firmware SM-G970F from France with G970FXXSFHVF1 and Android version 12

www.sammobile.com

ro.build.description: beyond0ltexx-user 12 SP1A.210812.016 G970FXXSFHVF1 release-keys
ro.build.display.id: SP1A.210812.016.G970FXXSFHVF1
ro.build.fingerprint: samsung/beyond0lteeea/beyond0:12/SP1A.210812.016/G970FXXSFHVF1:user/release-keys
ro.build.product: beyond0lte
ro.build.tags: release-keys
ro.build.type: user
ro.build.version.release: 12
ro.build.version.security_patch: 2022-06-01
ro.debuggable: 0
ro.product.brand: samsung
ro.product.device: beyond0
ro.product.manufacturer: samsung
ro.product.name: beyond0lteeea
ro.product.system.model: SM-G970F
[Magisk] pvchernoff:
Hi guys, if your smartphone doesn't pass SafetyNet CTS profile after the latest security patch update (May'22), so just change your rooted device fingerprint through MagiskHide Props Config Magisk module: install it, then reboot your smart and then open any terminal (e.g. Termux) and enter commands:

su

props

then choose option "1" and then choose option "f" (Pick a certified fingerprint), where just find a fingerprint you prefer. Reboot. All done.

This solved my problem after today update my Oneplus 8T (rooted Android 12 with magisk). GPay now works fine.
[Magisk] ZenurikSD:
Hey, thanks for the reply and sorry for the delay! I kinda forgot about this.

Precisely.

By the way, magisk's denylist was active for both Momo and YASNAC for all tests, I don't know if thats relevant, but removing them from the list had no effect.

With all modules disabled​

YASNAC reports:

- Evaluation Type as Basic

- Android 11 and Sec.patch 22.05.05

- Fails both tests: "Basic integrity" and "CTS profile match".

Fingerprint (Without module):

[ro.bootimage.build.fingerprint]: [motorola/montana_retail/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys]
[ro.build.fingerprint]: [motorola/montana_retail/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.odm.build.fingerprint]: [motorola/montana_retail/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys]
[ro.product.build.fingerprint]: [motorola/montana_retail/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys]
[ro.system.build.fingerprint]: [motorola/montana_retail/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys]
[ro.system_ext.build.fingerprint]: [motorola/montana_retail/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys]
[ro.vendor.build.fingerprint]: [motorola/montana_retail/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys]

Security patch (without module):

[ro.build.version.security_patch]: [2022-05-05]
[ro.vendor.build.security_patch]: [2019-08-01]

With only magiskhide-props-config enabled​

Default settings, fingerprint is set to Moto G 5G (kiev) (version 10)

- YASNAC reports the exact same as before, still fails both checks.

Fingerprint (with module):

[ro.bootimage.build.fingerprint]: [motorola/kiev_retail/kiev:10/QZKS30.Q4-40-81-3-4/88702:user/release-keys]
[ro.build.fingerprint]: [motorola/kiev_retail/kiev:10/QZKS30.Q4-40-81-3-4/88702:user/release-keys]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.odm.build.fingerprint]: [motorola/kiev_retail/kiev:10/QZKS30.Q4-40-81-3-4/88702:user/release-keys]
[ro.product.build.fingerprint]: [motorola/kiev_retail/kiev:10/QZKS30.Q4-40-81-3-4/88702:user/release-keys]
[ro.system.build.fingerprint]: [motorola/kiev_retail/kiev:10/QZKS30.Q4-40-81-3-4/88702:user/release-keys]
[ro.system_ext.build.fingerprint]: [motorola/kiev_retail/kiev:10/QZKS30.Q4-40-81-3-4/88702:user/release-keys]
[ro.vendor.build.fingerprint]: [motorola/kiev_retail/kiev:10/QZKS30.Q4-40-81-3-4/88702:user/release-keys]

Security patch (with module):

[ro.build.version.security_patch]: [2021-07-01]
[ro.vendor.build.security_patch]: [2019-08-01]

So I can see things DID change, but they had no effect? And the sec.patch shows both the original and new dates. What's up with that?
[Magisk] ReimarPB:
Moto G31​

ro.build.fingerprint=motorola/cofud_ge/cofud:11/RRWDS31.Q3-26-83-3/e22e68:user/release-keys
ro.build.version.security_patch=2022-05-01
ro.product.manufacturer=motorola
ro.product.model=moto g31(w)

Denver SDQ 52004L​

ro.build.fingerprint=Denver_Electronics/SDQ_52004L/SDQ_52004L:7.0/NRD90M/1517911052:user/release-keys
ro.build.version.security_patch=2018-02-05
ro.product.manufacturer=Denver_Electronics
ro.product.model=SDQ_52004L
[Magisk] downhere:
OnePlus 9 Europe LE2113

Android 12

ro.build.fingerprint = OnePlus/OnePlus9_EEA/OnePlus9:12/SKQ1.210216.001/R.202204081955:user/release-keys

ro.build.version.security_patch = 2022-04-05

ro.product.manufacturer = OnePlus

ro.product.model = LE2113
[Magisk] innit:
Hi. Would you be willing to grab that fake encryption module from your twrp and post it here? Thanks.
[Magisk] m0han:
this is what i'm running..
[Magisk] innit:
Thanks a lot.
[Magisk] Fif_:
It's a just "resetprop ro.crypto.state encrypted", but cool nevertheless.
[Magisk] balthor80:
Hi all !

I'm trying to make work GPAY on my old Motorola X890 (Razr I).

What I have done :

- Last (unofficial) rom : Lineage 16

- Install Magisk 25.1 (OK)

- Install USNF 2.3.1 (OK)

- Install MHPC 6.1.2 (OK)

YASNAC without MHPC :

- Basic integrity OK

- CTS FAIL

YASNAC with MHPC :

- Basic integrity FAIL

- CTS FAIL

getprop | grep fingerprint

[ro.bootimage.build.fingerprint]: [google/sailfish/sailfish:9/PQ3A.190801.002/5670241:user/release-keys]

[ro.build.fingerprint]: [google/sailfish/sailfish:9/PQ3A.190801.002/5670241:user/release-keys]

[ro.vendor.build.fingerprint]: [google/sailfish/sailfish:9/PQ3A.190801.002/5670241:user/release-keys]

(OK, not my phone)

getprop | grep security patch

[ro.build.version.security_patch]: [2019-08-01]

[ro.vendor.build.security_patch]: []

(FAIL ?)

Thanks for your help
[Magisk] Neitsab:
Hi, reporting here a strange discrepancy: despite successfully applying a different fingerprint as confirmed by queries in a terminal:

~ $ getprop ro.build.fingerprint
Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys
~ $ getprop ro.build.version.security_patch
2021-08-01

YASNAC still reports the original security patch date:

View attachment 5655755

Setup:

- Xiaomi Mi 9T (davinci)

- Firmware V12.1.1.0.RFJEUXM

- TWRP 3.6.2_9-0-davinci.img

- Arrow OS 11 Vanilla (2022-02-26)

- Magisk v25.1 --> Zygisk enabled, Exclusion List enabled and YASNAC selected

- MicroG 0.2.24.214816 flashed via MinMicroG as a Magisk module

- (Shelter managing the work profile, if that matters)

As you can see everything fails and the patch date is the original one.

After installing Universal SafetyNet Fix I am able to get the Basic Integrity to pass:

View attachment 5655767

However no amount of fiddling got me to CTS match heaven.

How come this discrepancy between getprop result and YASNAC? Should I try setting a custom security_patch prop, or change the stage?

Thanks for any hints!

Edit: Installing Shamiko and disabling the enforcing of the Exclude list by Magisk didn't change anything... I'm surprised seeing how many people got a working setup like that 🤔

More info:

~ $ getprop | grep fingerprint
[ro.bootimage.build.fingerprint]: [Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys]
[ro.build.fingerprint]: [Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.odm.build.fingerprint]: [Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys]
[ro.product.build.fingerprint]: [Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys]
[ro.system.build.fingerprint]: [Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys]
[ro.system_ext.build.fingerprint]: [Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys]
[ro.vendor.build.fingerprint]: [Xiaomi/davinci_eea/davinci:11/RKQ1.200826.002/V12.1.1.0.RFJEUXM:user/release-keys]

~ $ getprop | grep security_patch
[ro.build.version.security_patch]: [2021-08-01]
[ro.vendor.build.security_patch]: [2021-05-01]
[Magisk] Rickyster:
How to use `getprop ro.build.fingerprint` to get the fingerprint of stock rom of oneplus 9rt MT2111? Can someone help me with the process? Will be really grateful. 🙏
[Magisk] zgfg:
In Terminal app - screenshot

Similarly like you use (if you do) DOS box and DOS commands on PC, you can use Terminal and Linux commands on Android (since Android is based on Linux)

And google is your friend for more info
[Magisk] Rickyster:
Really appreciate ur help.
[Magisk] Rickyster:
OnePlus 9RT MT2111 Android 11

ro.build.fingerprint

OnePlus/MT2111_IND/OP5155L1:11/RKQ1.211119.001/1657522882684:user/release-keys

ro.product.manufacturer

OnePlus

ro.product.model

MT2111

ro.build.version.security_patch

2022-06-05
[Magisk] daddylonglegs:
I have been trying to get around T Mobile's tethering detection for five years now and I still can't figure out how they detect it (I was always able to fool Verizon Wireless).

Is there some sort of setting this module can edit that would not let T-mobile know I am tethering?
[Magisk] 73sydney:
Almost all methods ive personally seen involve running a proxy/VPN as i think carriers were able to detect and nullify any props bypasses years ago

Perhaps look at PDANet+

or

Try this (FREE): https://play.google.com/store/apps/details?id=com.gorillasoftware.everyproxy
[Magisk] daddylonglegs:
I appreciate it. I already use PDANet but it requires the host computer also have PDANet installed which isn't possible on any device other than a Windows pc. Forget about stuff like the Nintendo Switch or my work computer. Can't tether those with PDANet
[Magisk] 73sydney:
Try the proxy i added to my post, which you might have missed as i edited it in later
[Magisk] ipdev:
Hi all. :D

Some fingerprint updates.

Spoiler content hidden.

Spoiler content hidden.

Cheers all. :cowboy:
[Magisk] deepu458:
I really do appreciate your help in this regards. No probs . Life priority comes first. I don't know wht else can help me.
[Magisk] deepu458:
So Dev, finally I was able to pass cts on this device with the help of ur mod. But this time the change I did was to use a fingerprint from the list of another device that is pixel 2 xl (8.1.0) and that's all it did the magic of passing safety net back.

So now the question is does using the other device fingerprint cause any issue?
[Magisk] Didgeridoohan:
Not really. Your device might show up as a Pixel in certain situations, but nothing should come from that.

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint
[Magisk] pukkimonkey:
Is this relevant for Android Pie as well? I have OnePlus6 P (DP4) with TWRP and Magisk. If so, what options do I need to change in build.prop ?

Did it work for your Android 9.0 phone? Can you tell me what options you changed?

---------- Post added at 08:04 PM ---------- Previous post was at 07:50 PM ----------

Is this relevant for Android Pie as well? I have OnePlus6 P (DP4) with TWRP and Magisk. If so, what options do I need to change in build.prop ?

Did it work for your Android 9.0 phone? Can you tell me what options you changed?
[Magisk] mattman83:
This seems to be working for me too. Play store showing certified and Google pay allows me to complete setup. Have magisk running too, just with the repack option just because PokemonGo is a pain with it atm.

Xiaomi mix2s on miui10 pie dp2 beta

M.
[Magisk] Didgeridoohan:
It is relevant

only

for Pie... If you don't care about keeping /system untouched you can just manually edit your build.prop file and replace the current ro.build.fingerprint with a certified one. You'll have to do this every time you up update your system though (which, in my opinion, is one of the best thing about Magisk's systemless mods: they keep across system updates).

It will definitely work until resetprop is updated.
[Magisk] Seagold:
[MENTION=4667597]Didgeridoohan[/MENTION]

You have tried bro...bigups.....

I made it and am here with my testimony, confirmed with screenshots.

Samsung Galaxy J200H 2015 3G Dual SIM.

Running lollipop 5.1.1 stock

Magisk manager - latest version

Magisk module- latest beta version
[Magisk] pukkimonkey:
Thanks for the response.

What's the disadvantage of directly editing prop file as opposed to using magisk?

Also appart from fingerprint, should I change anything else in the prop file?
[Magisk] Seagold:
Terminal emulator
[Magisk] Didgeridoohan:
If you ever want to update your device through an OTA, you won't be able to if you have edited your system partition. That's what you'll do by editing build.prop manually. It's actually enough to just mount /system rw and back again to ro to make the integrity check during an OTA update fail.

Other than that, the only real disadvantage is that you'll have to redo the edit after a system update.

Edit: forgot about your second question... No, you don't have to edit anything else.

Thank's I'll put it on the fix list.
[Magisk] pukkimonkey:
That's not a problem for me then.. :)

Thanks again!
[Magisk] pukkimonkey:
It worked..

Once I updated my prop file, GPay starred working. I loved Magisk, but GPay was really important for me. Hopefully, soon I will be back once you guys have figured out a fix with Pie. :)
[Magisk] 2nqey:
Any idea what's causing that? Logs attached.
[Magisk] Didgeridoohan:
The boot script placeholders doesn't seem to have been updated. A reinstall might fix it. If you do reinstall, make sure to save the module installation log (from /cache) before rebooting. It'll likely show what's wrong if the reinstall doesn't work...
[Magisk] 2nqey:
Oh thank you. Let me try that.
[Magisk] 2nqey:
It worked. Thank you.