[Magisk] ipdev:
@JacobBoi_

To (hopefully help) explain the link that Didgeridoohan gave you. ;)

Since you are having an issue running the props command, you will most likely have to gather the log files manually.

Reboot the device.

Run the props command.

Then gather the log files.

Try running props -l

Example.

barbet:/ $ props -l

Loading... Please wait.

MagiskHide Props Config v6.1.1
by Didgeridoohan @ XDA Developers

=====================================
Collect logs
=====================================

This will package the Magisk log and the
module specific log files, together with
all the original and current prop values
and save it on your device.

If you are having issues, please upload
the packaged file to the support thread
@ XDA, with a detailed description.

Do you want to contine?

Enter y(es) or n(o): y

MagiskHide Props Config v6.1.1
by Didgeridoohan @ XDA Developers

=====================================
Collect logs
=====================================

Logs and information collected.

The packaged file (propslogs.tar.gz)
has been saved to the root of your device's
internal storage.
If it did not, please see the documentation
for details on how to collect the logs
manually.

Attach the file(s) to a post in the support
thread @ XDA, with a detailed description
of your issue.

Press enter to continue...

MagiskHide Props Config v6.1.1
by Didgeridoohan @ XDA Developers

=====================================
Bye bye.
=====================================

barbet:/ $

The propslogs.tar.gz file will be saved to your internal storage.

/sdcard/propslogs.tar.gz​

If that does not work, you can try to gather the log files manually.

- You will need root permission to access /cache/ and /data/

There is a few ways you can do this.

You could use a file manager app that has root access.

Copy the log files and compress them using the file manager or a different compression app.​

From command line it is five steps.

You could do it in two steps but, five steps is a little cleaner.

su

cd /sdcard/

mkdir propslogs

cp /cache/magisk* /data/adb/mhpc/* propslogs/

tar -czf propslogs.tar.gz propslogs

Example.

Two step.

barbet:/ $ su
barbet:/ # tar -czf /sdcard/propslogs.tar.gz /cache/magisk* /data/adb/mhpc/
removing leading '/' from member names
removing leading '/' from member names
removing leading '/' from member names
barbet:/ #

The compressed file archive that looks like this.

barbet:/ # tar -tf /sdcard/propslogs.tar.gz
cache/magisk.log
cache/magisk.log.bak
data/adb/mhpc
data/adb/mhpc/propsconf_install.log
data/adb/mhpc/propsconf.log
data/adb/mhpc/script_check
data/adb/mhpc/propsconf_late
data/adb/mhpc/defaultprops
data/adb/mhpc/propsconf_boot_verbose.log
data/adb/mhpc/propsconf_verbose.log
data/adb/mhpc/propsconf_last.log
data/adb/mhpc/propsconf_boot_verbose_last.log
data/adb/mhpc/propsconf_verbose_last.log
barbet:/ #

Five step.

barbet:/ $ su
barbet:/ # cd sdcard/
barbet:/sdcard # mkdir propslogs
barbet:/sdcard # cp /cache/magisk* /data/adb/mhpc/* propslogs/
barbet:/sdcard # tar -czf propslogs.tar.gz propslogs
barbet:/sdcard #

The compressed file archive that looks like this.

barbet:/sdcard # tar -tf propslogs.tar.gz
propslogs/
propslogs/magisk.log
propslogs/magisk.log.bak
propslogs/defaultprops
propslogs/propsconf.log
propslogs/propsconf_boot_verbose.log
propslogs/propsconf_boot_verbose_last.log
propslogs/propsconf_install.log
propslogs/propsconf_last.log
propslogs/propsconf_late
propslogs/propsconf_verbose.log
propslogs/propsconf_verbose_last.log
propslogs/script_check
barbet:/sdcard #

If that does not work, you can try to grab the logs using a custom recovery that allows root access.

TWRP for example.

Open the Magisk app and view the Magisk log file.

The bug icon on the bottom bar.

Save the current Magisk log file.

Reboot into recovery.

Make a directory on /sdcard/

Copy the files from /data/adb/mhpc/ to the directory you created.

You can use the built in file manager of the recovery or command line (adb shell).​

Reboot into system and compress the log files.

---

Once you have the log files.

Attach it to a post or upload the file(s) somewhere (gDrive) and give a link to the log file(s).​

Hope it helps more than confuse. 🙃

Cheers. :cowboy: