As title says i want to edit build prop, any modules or something?
@topjohnwu is currently implementing this into Magisk Manager. As for now you can use:
Code:
/data/magisk/resetprop build.prop.item value
loserskater said:
@topjohnwu is currently implementing this into Magisk Manager. As for now you can use:
Code:
/data/magisk/resetprop build.prop.item value
Click to expand...
Click to collapse
Ok im lost not sure how to do that? I need to make a module?
You can either make a module or a script that you put in /magisk/.core/post-fs-data.d. More details in the All-In-One wiki (stickied thread).
And as stated above, in upcoming versions you'll be able to change prop values in a GUI in the Magisk Manager. It's on the to-do list, but of course there's no ETA.
Didgeridoohan said:
You can either make a module or a script that you put in /magisk/.core/post-fs-data.d. More details in the All-In-One wiki (stickied thread).
And as stated above, in upcoming versions you'll be able to change prop values in a GUI in the Magisk Manager. It's on the to-do list, but of course there's no ETA.
Click to expand...
Click to collapse
Thanks, if i use magisk hide it will hide this too right?
Cheers
I added this:
/data/magisk/resetprop ro.product.model "Pixel XL"
/data/magisk/resetprop ro.opa.eligible_device true
/data/magisk/resetprop ro.product.brand "google"
/data/magisk/resetprop ro.product.manufacturer "Google"
In the post fs data of another module so i basically hacked in the build prop, but magisk hide fails (doesn't fail when i don't mess with the build prop)
metrize said:
I added this:
/data/magisk/resetprop ro.product.model "Pixel XL"
/data/magisk/resetprop ro.opa.eligible_device true
/data/magisk/resetprop ro.product.brand "google"
/data/magisk/resetprop ro.product.manufacturer "Google"
In the post fs data of another module so i basically hacked in the build prop, but magisk hide fails (doesn't fail when i don't mess with the build prop)
Click to expand...
Click to collapse
There's a module for activating Google assistant in the repo already. Have you tried that?
Didgeridoohan said:
There's a module for activating Google assistant in the repo already. Have you tried that?
Click to expand...
Click to collapse
I'm more interested in changing the device so that it thinks it's a pixel. It fails safetynet even with magisk hide when i do this though
metrize said:
I'm more interested in changing the device so that it thinks it's a pixel. It fails safetynet even with magisk hide when i do this though
Click to expand...
Click to collapse
Why?
I'm not sure about the details, but if your device doesn't match a profile Google have on their servers you won't get a CTS profile match. That might be why...
Can you pass basic integrity with the mods you made?
Didgeridoohan said:
Why?
I'm not sure about the details, but if your device doesn't match a profile Google have on their servers you won't get a CTS profile match. That might be why...
Can you pass basic integrity with the mods you made?
Click to expand...
Click to collapse
it's for google photos unlimited original backup (only on pixels)
Without the mods i did above I can pass safetynet and everything fine
With the mods nothing psses not even basic integrity.
Can build.prop be reset with magisk hide or is that functionality not possible on android?
If it could reset build.prop to the original build.prop then I would pass safetynet, but I'm not sure if magisk can do this? @topjohnwu maybe might know?
metrize said:
it's for google photos unlimited original backup (only on pixels)
Without the mods i did above I can pass safetynet and everything fine
With the mods nothing psses not even basic integrity.
Can build.prop be reset with magisk hide or is that functionality not possible on android?
If it could reset build.prop to the original build.prop then I would pass safetynet, but I'm not sure if magisk can do this? @topjohnwu maybe might know?
Click to expand...
Click to collapse
It's possible... You can edit the enable and disable files in /magisk/.core/magiskhide/ to do what you want.
Didgeridoohan said:
There's a module for activating Google assistant in the repo already. Have you tried that?
Click to expand...
Click to collapse
Didgeridoohan said:
It's possible... You can edit the enable and disable files in /magisk/.core/magiskhide/ to do what you want.
Click to expand...
Click to collapse
Thanks this seems promising, however i don't understand the syntax. If you have time could you tell me what to add with the build prop changes i wanted earlier in the thread. Thanks a lot for all the help
metrize said:
Thanks this seems promising, however i don't understand the syntax. If you have time could you tell me what to add with the build prop changes i wanted earlier in the thread. Thanks a lot for all the help
Click to expand...
Click to collapse
Look at how ro.debuggable, ro.secure and the other ro props are handled in the enable file. Match what you want to do to those and then add similar code with your other desired changes in the disable file.
It should be as simple as copying, pasting and changing variable names and props to match your desired setup.
Didgeridoohan said:
Look at how ro.debuggable, ro.secure and the other ro props are handled in the enable file. Match what you want to do to those and then add similar code with your other desired changes in the disable file.
It should be as simple as copying, pasting and changing variable names and props to match your desired setup.
Click to expand...
Click to collapse
Am I right in assuming when magisk hide is disabled the build prop will be changed back to the pixel one?
thanks
ok it's working just going to do the disable one
Okay, when I did the enable magiskhide and changed it, it passes safetynet but then when I changed the dsiable magiskhide file it fails safetynet now even when i enable magiskhide.. weird
core only works though with changes to both enable and disable so now im muffed
Dammit... Now you piqued my curiosity.
I'm heading to bed (shoulda done that 3 hours ago), but if you post your enable and disable files I'm sure someone can take a look at it. If not, I'm around again after a few hours of z and some breakfast.
Attached enable and disable.
(Renamed it to txt file otherwise wouldn't let it upload)
For the module it's just a system.prop module with the following lines;
# This file will be read by resetprop
# Example: Change dpi
# ro.sf.lcd_density=320
ro.product.model=Pixel
ro.product.brand=google
ro.product.manufacturer=Google
When I go core only mode, enable magisk hide then disable (to get the build prop change) then enable magisk hide again it works though. So I think it's something with the module that makes it fail
metrize said:
When I go core only mode, enable magisk hide then disable (to get the build prop change) then enable magisk hide again it works though. So I think it's something with the module that makes it fail
Click to expand...
Click to collapse
How about without the module installed and Core only mode disable?
Since you seem to have a working setup with the enable/disable scripts I'd consider just using those. You could even set up automation with Tasker or a similar app. Use the following code in a Run Shell action:
Code:
sh /magisk/.core/magiskhide/enable
And the same for the disable script.
Related
SYSTEM/LESS MODULE TEMPLATE FOR MAGISK
This template is a modified version of the original one.
Its purpose is to make Magisk Modules install in either Magisk (as a module) or directly in /system.
How to use/create a module:
Clone / download this repo
Open config.sh, follow the instructions written at the beginning of the file. You should at least change config.sh and module.prop
Zip your files, the zipped file is a flashable zip for both Magisk Manager and custom recoveries
Please check Notes for precautions
You can make a module from this template almost the same as you can make one in the Original template.
It should be easy to transition from there to here.
ADDITIONAL STUFF
Installation is configurable. It means that you can control on where it installs (system or magisk), and a few other variables that is also important.
For Devs:
Installation is configurable in config.sh. You can control the variables (starting in line 95) that will help you how to configure your module.
Code:
Variables:
[B]MAGISKINSTALL [/B]- forces magisk installation (might conflict with SYSTEMINSTALL) (values: [B]true [/B]or [B]false[/B])
[B]SYSTEMINSTALL [/B]- forces system installation (might conflict with MAGISKINSTALL) (values: [B]true[/B] or [B]false[/B])
[B]INITPATH [/B]- sets path to install scripts (post-fs-data.sh, service.sh) if system install (values: [B]directories[/B])
[B]BUILDPROP [/B]- sets properties from system.prop directly to build.prop (values: [B]true [/B]or [B]false[/B])
[B]PERMANENTDELETE [/B]- PERMANENTLY delete folders in $REPLACE (values: [B]true [/B]or [B]false[/B])
[B]ERROREXIT[/B] - exits with an error on every failed attempt to install to Magisk (enabled by default) (values: [B]true [/B]or [B]false[/B])
set_permissions_system
It behaves like set_permissions, but it sets them on whatever file you want and will be executed in system install only.
System Install
The directories in system folder will correspond to which directory the files will be copied.
Ex. if you put in the zip /system/example.file, it will be copied to /system/example.file.
Click to expand...
Click to collapse
For Users:
If a module is based on this template, you can also configure it's installation.
The variables that is in /dev/.config will overwrite the dev's setting for the module.
Code:
Variables:
[B]MAGISKINSTALL [/B]- forces magisk installation (might conflict with SYSTEMINSTALL) (values: [B]true [/B]or [B]false[/B])
[B]SYSTEMINSTALL [/B]- forces system installation (might conflict with MAGISKINSTALL) (values: [B]true[/B] or [B]false[/B])
[B]INITPATH [/B]- sets path to install scripts (post-fs-data.sh, service.sh) if system install (values: [B]directories[/B])
[B]BUILDPROP [/B]- sets properties from system.prop directly to build.prop (values: [B]true [/B]or [B]false[/B])
[B]PERMANENTDELETE [/B]- PERMANENTLY delete folders in $REPLACE (values: [B]true [/B]or [B]false[/B])
They need to be in /dev/.config to be read by the installer.
To enter them, just create the file and then add.
How to do it on Terminal:
Code:
Example:
echo "SYSTEMINSTALL=TRUE" >> /dev/.config
You can add them in different lines to be valid.
I put it in /dev/.config to make it a temporary file. So whenever a module is flashed, the file will be gone and won't interrupt the installation process of the currently installing module.
Click to expand...
Click to collapse
XDA:DevDB Information
System/Less Module Template for Magisk, Tool/Utility for all devices (see above for details)
Contributors
veez21, topjohnwu
Source Code: [url]https://github.com/veez21/unify-magisk-module-template[/URL]
Version Information
Status: Beta
Current Beta Version: v0.3
Beta Release Date: 2017-06-11
Created 2017-06-11
Last Updated 2017-06-14
Reserved
Reserved
reserved+
UPDATE TO v0.2
commit 3709f37
Changelog:
add more notes
fixed some terms
fix setting PERM
added ERROREXIT variable
added post-fs-data and late_start service scripts notes and better compatibility with system install
Hi veez. I like to know about how to edit default.prop using magisk module. There are somes ro. In default.prop i want to edit. I had seen some module make by others and i look at post-fs-data.sh they edit ro.fingerprint or dpi screen using magisk module it for build.prop. but now i want to edit default.prop . Can u help me how to edit default.prop using magisk module. I search on google some people said that i must to unpack boot.img to edit defaukt.prop thanks before. And I newbie for this magisk module.
Duden17 said:
Hi veez. I like to know about how to edit default.prop using magisk module. There are somes ro. In default.prop i want to edit. I had seen some module make by others and i look at post-fs-data.sh they edit ro.fingerprint or dpi screen using magisk module it for build.prop. but now i want to edit default.prop . Can u help me how to edit default.prop using magisk module. I search on google some people said that i must to unpack boot.img to edit defaukt.prop thanks before. And I newbie for this magisk module.
Click to expand...
Click to collapse
If you just want to set a new value to the prop, it's the same procedure as the modules you've been looking at. Just add the prop and new value to the system.prop file of the module and you're done. Shameless promotion: if you don't want to make a module yourself, my MagiskHide Props Config module can actually set custom props for you.
If you want to edit the default.prop file itself you're going to have to go about the way you found about unpacking the boot image, etc.
Didgeridoohan said:
If you just want to set a new value to the prop, it's the same procedure as the modules you've been looking at. Just add the prop and new value to the system.prop file of the module and you're done. Shameless promotion: if you don't want to make a module yourself, my MagiskHide Props Config module can actually set custom props for you.
If you want to edit the default.prop file itself you're going to have to go about the way you found about unpacking the boot image, etc.
Click to expand...
Click to collapse
Oke. I use ur module man. Its great for people need to change their cts or selinux. Good job :good::good: i will look at to ur magiskhide prop again. Thanks man
Not sure where to post this as I was looking for guide/s on how to create a magisk module for this feature.
iZLeeP said:
Not sure where to post this as I was looking for guide/s on how to create a magisk module for this feature.
Click to expand...
Click to collapse
This isn't. Also this template is abandoned.
You should start here https://github.com/topjohnwu/magisk-module-template
veez21 said:
This isn't. Also this template is abandoned.
You should start here https://github.com/topjohnwu/magisk-module-template
Click to expand...
Click to collapse
That was the first thing I did. I was just looking for additional sources to better understand on how to make a Magisk module as this is the first time I'm doing so. Anyway, thanks for pointing out.
Old topic but this is a great idea, I think a better way of doing this would be automatically detecting if magisk is installed and acting accordingly otherwise install to system..
Hi i want to make auto face unlock module
Could you please help me
and also want to make quick pin unlock module
ntrimurthulu said:
Hi i want to make auto face unlock module
Could you please help me
and also want to make quick pin unlock module
Click to expand...
Click to collapse
Not possible with magisk
Sent from my Moto G 2015 using XDA Labs
DanGLES3 said:
Not possible with magisk
Click to expand...
Click to collapse
Oh sad
---------- Post added at 05:11 PM ---------- Previous post was at 05:11 PM ----------
DanGLES3 said:
Not possible with magisk
Click to expand...
Click to collapse
Do you know other way
ntrimurthulu said:
Oh sad
---------- Post added at 05:11 PM ---------- Previous post was at 05:11 PM ----------
Do you know other way
Click to expand...
Click to collapse
The only way would be a custom ROM or xposed but it only supports up to Oreo and I don't think there's a module for face auto unlock
Sent from my Moto G 2015 using XDA Labs
DanGLES3 said:
The only way would be a custom ROM or xposed but it only supports up to Oreo and I don't think there's a module for face auto unlock
Click to expand...
Click to collapse
Yeah no such module that's why i want to create
BTW thank you
!Magisk is not activated !... abort
! Installation failed
obviously magisk is activated 19.1 ... is this template too old ?
edit: nevermind ... i just edited the zip directly from github so there was a folder in the root of the zip :silly:
I'd even take an explanation of how to do it, I could possibly figure it out from there.
You might wanna try this:-
https://forum.xda-developers.com/moto-z-play/how-to/how-to-enable-miracast-t3565852
How to enable Miracast | Moto Z Play - XDA Forums - XDA Developers
Sent from my Moto G3 Turbo Edition
Is there a way to do that with a Magisk module?
ird0 said:
Is there a way to do that with a Magisk module?
Click to expand...
Click to collapse
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Much appreciated, thanks.
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Just to make sure, did I do it right?
http://imgur.com/ZkE0tin
ird0 said:
Just to make sure, did I do it right?
http://imgur.com/ZkE0tin
Click to expand...
Click to collapse
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Didgeridoohan said:
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Click to expand...
Click to collapse
Thanks for spotting that. I can't test it until I get home. Much appreciated
Didgeridoohan said:
If it's just about changing a prop you can easily do that with a boot script, make a Magisk module, or use my MagiskHide Props Config to set a custom prop.
Click to expand...
Click to collapse
Didgeridoohan said:
Yup. If it doesn't work at first, try going to the script settings (currently menu option 6) and change the boot stage to post-fs-data.
Edit: NO! I looked again. You've done a typo, it's supposed to be "enable", not "enabled".
Click to expand...
Click to collapse
Seems I can connect but then my phone does a UI restart. I guess it just doesn't work or I'm missing some kind of library or something.
I'm stuck at the same point on my P2XL. Did you ever figure it out?
Stuck here too. I can enable the menu but when I try to connect, I get a restart of the UI and I go back to the lock screen. Pixel 2 XL
I finally gave up.
I just saw a recent post on the Pixel forum with a guide to get it working (at least for the original Pixel.) Maybe this could prove useful:
https://forum.xda-developers.com/pixel/how-to/guide-how-to-enable-miracast-pixel-t3888780
Credit to sbjbs
Sent from my Pixel 2 using Tapatalk
Hi Guys!
Recently I hope to use Tasker to do something automatically when the phone is turned on, but I found that Tasker can't start when my phone is turned on but locked.
So I wrote an Android app that uses the shell to enter the password at boot time, but even if I used DirectBoot mode(developer.android.com/training/articles/direct-boot) it still doesn't work.
So I tried to write a module using Magisk, and automatically entered the password when I booted. This time I raised succeeded.
I think there may be other people who have the same needs as me, so I do a function that can customize the password for others to use.
At first we need install AutoInputBootPinManager(github.com/ZeroingIn/AutoInputBootPinManager) to configure your PIN. The application needs to grant root privileges.
Next we download and install this module(github.com/ZeroingIn/AutoInputBootPin) and reboot phone to enjoy it.
If you have any questions, please submit an issue.
Thank you all.
Interesting idea.
There are several modules available that use a shell script UI, run through a terminal emulator, to change settings for the module. App systemizer, Unified Hosts Adblock, MagiskHide Props Config, Energized Protection, etc. Take a look at them for inspiration.
A couple of things:
An explanation of the command in post-fs-data.sh might be a good idea.
Code:
supolicy --live "allow untrusted_app default_android_service service_manager find"
And, why are you setting this prop? As far as I can tell that's for the app Brevent...
Code:
log.tag.BreventServer=DEBUG
Didgeridoohan said:
Interesting idea.
There are several modules available that use a shell script UI, run through a terminal emulator, to change settings for the module. App systemizer, Unified Hosts Adblock, MagiskHide Props Config, Energized Protection, etc. Take a look at them for inspiration.
A couple of things:
An explanation of the command in post-fs-data.sh might be a good idea.
Code:
supolicy --live "allow untrusted_app default_android_service service_manager find"
And, why are you setting this prop? As far as I can tell that's for the app Brevent(play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en)...
Code:
log.tag.BreventServer=DEBUG
Click to expand...
Click to collapse
Thank you very much for your advice, I will try it. Any progress, I will be posted in this post.
The setting of this prop is my mistake, and you have carefully discovered this bug that I have not noticed.
Because I was a beginner to make the Magisk module, I didn't see the Magisk Module Template(github.com/topjohnwu/magisk-module-template) at first, so I wrote it with reference to the Privileged Api Booter(github.com/Magisk-Modules-Repo/magisk-privileged-api-booter).I will fix this problem right away.
ZeroingIn said:
Thank you very much for your advice, I will try it. Any progress, I will be posted in this post.
The setting of this prop is my mistake, and you have carefully discovered this bug that I have not noticed.
Because I was a beginner to make the Magisk module, I didn't see the Magisk Module Template(github.com/topjohnwu/magisk-module-template) at first, so I wrote it with reference to the Privileged Api Booter(github.com/Magisk-Modules-Repo/magisk-privileged-api-booter).I will fix this problem right away.
Click to expand...
Click to collapse
In that case you have a couple of more things to rectify. The first part I mentioned, about the post-fs-data.sh script is also from that module. So, I'm going to assume you do not need it for your purpose. I'd suggest removing that as well... And after you've done that, you should also go in and edit config.sh and change PROPFILE and POSTFSDATA from true to false, because you're not using them anymore. From the looks of it you're only using service.sh, so only LATESTARTSERVICE needs to be active.
Didgeridoohan said:
In that case you have a couple of more things to rectify. The first part I mentioned, about the post-fs-data.sh script is also from that module. So, I'm going to assume you do not need it for your purpose. I'd suggest removing that as well... And after you've done that, you should also go in and edit config.sh and change PROPFILE and POSTFSDATA from true to false, because you're not using them anymore. From the looks of it you're only using service.sh, so only LATESTARTSERVICE needs to be active.
Click to expand...
Click to collapse
You are right, I modified it with reference to the template.Thanks a lot.
Are you going to.update this at all?
I have a bug if you are...
I only have 1 pin... But all 3 fire... Since there's no way to stop them without deleting it from the script
Hello,
I need to tinker my build.prop file to test out a few things.
I read about resetprop, so i have a few questions.
1. What should the filename of the text file be?
2. Where do i need to paste that file for magisk to load it upon startup everytime to alter build.prop systemlessly?
Hey @Didgeridoohan please help!
Thanks.
Short answer: use MagiskHide Props Config.
Long answer when I get an opportunity.
Didgeridoohan said:
Short answer: use MagiskHide Props Config.
Long answer when I get an opportunity.
Click to expand...
Click to collapse
I tried that.
But the boot process is ridiculously slow. It takes over a minute for every boot.
I just need to change a couple of variables systemlessly.
I am reading the documentation since the last 2 days. I read about the magisk boot process from the Magisk Documentation and documentation on "Magisk Hide Props" too, but still had these doubts.
I just need to know that where should i place "resetprop" with relevant flags and options, for magisk to make changes to the fingerprint automatically on boot.
Even a brief help would suffice!
That's interesting... If you wouldn't mind, could you install the module again, set it up and then provide me with the module and Magisk logs? It should not cause that kind of boot delay...
Anyway, just like I write in the introduction of MagiskHide Props Config in the documentation, the module is just a way to make a Magisk boot script to set props using resetprop.
All you need to do to spoof a device fingerprint is to use a boot script in service.d. I've described it in the Magisk guide already, right here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Spoofing_device_fingerprint
i don't know about the context, but it looks to me like it's as simple as creating a magisk module
Developer Guides
The Magic Mask for Android
topjohnwu.github.io
you'll need to place property entries in system.prop
Hello,
i need help to create a small magisk module to make Samsung SHealth working again on my Samsung S20 Ultra 5G. At the moment device is rooted but /system is readonly. to make changes to build.prob a magisk module should work.
In build.prop the value of ro.config.tima=1 must be changed to 0.
That's all.
Maybe some of the experts could create a small magisk module for me?
Thanks!
If you can't create your own module, try MagiskHide Props Config. You can easily change prop values with that.
don't know how it works, but with your help shealth is now working.
thanks
Didgeridoohan said:
If you can't create your own module, try MagiskHide Props Config. You can easily change prop values with that.
Click to expand...
Click to collapse
Any tutorials how to use props-config?
rxk said:
Any tutorials how to use props-config?
Click to expand...
Click to collapse
I linked the relevant part of the docs above, but here's a link to the documentation in general:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
If all you want to do is to change a prop value, you just need to install the module, run the props command and pick the "Add/edit custom props" option and just follow the on-screen instructions.
Thanks mate. I not knowledgeable in doing this stuffs but i will try once i rooted my new galaxy s20 (xsa australian stock).
Still searching for easy to follow procedure on how to root s20 ultra.
Thank you.
rxk said:
Thanks mate. I not knowledgeable in doing this stuffs but i will try once i rooted my new galaxy s20 (xsa australian stock).
Still searching for easy to follow procedure on how to root s20 ultra.
Thank you.
Click to expand...
Click to collapse
As far as I've seen, if you can unlock the bootloader it should just be a matter of following the official instructions:
https://topjohnwu.github.io/Magisk/install.html
Of course, you might find more info on the S20 forums here on XDA.
Didgeridoohan said:
I linked the relevant part of the docs above, but here's a link to the documentation in general:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
If all you want to do is to change a prop value, you just need to install the module, run the props command and pick the "Add/edit custom props" option and just follow the on-screen instructions.
Click to expand...
Click to collapse
Hi didgeridoohan,
I already installed Magiskhide Prop Config and Busybox modules and termux app as well.
steps :
open termux >
su
ro.config.tima (but it returns not found)
I am not sure what the correct props command syntax for changing ro.config.tima to "0" for S Health to work.
Thank you.
rxk said:
Hi didgeridoohan,
I already installed Magiskhide Prop Config and Busybox modules and termux app as well.
steps :
open termux >
su
ro.config.tima (but it returns not found)
I am not sure what the correct props command syntax for changing ro.config.tima to "0" for S Health to work.
Thank you.
Click to expand...
Click to collapse
Well, yes... If you enter nothing but that into the terminal prompt that would be the result.
If you want to use the MagiskHide Props Config module to change the prop you'll have to start by running the command "props" (without quotation marks). Pick option 4 ("Add/edit custom props") and then follow the on-screen instructions.
If you need more info, the linked docs cover the use of the module pretty well.