Marker file in user accessible directory

[ZingyAwesome]

Hi, I'd like to request that the module checks for a marker file in a user accessible location (i.e. a location that the user can write to without root, for example internal storage) and if this is detected then all modules and scripts are disabled as normal.

I think this feature would be useful for a good subset of users. I use avbroot for root which allows the bootloader to be re-locked after flashing the rooted image. If all goes wrong I cannot perform the method described in the README where you flash the zip from recovery as my recovery won't allow zips to be flashed while the bootloader is locked. I also don't know if that method works on encrypted devices.
However if this feature was implemented, I could use the recovery's adb sideload feature to install a rootless version of the system without erasing data, this sideloaded zip must be signed by the avb key of course. I could then boot into the system as normal since magisk modules can't load in rootless mode and create the marker file. Then after sideloading the rooted version again, the module would see the marker and disable all modules. That would let me get back to the Magisk app and remove whatever module caused the bootloop.

[KaluaBilla]

You could just change the value of service.sh and post-fs-data.sh to /storage/emulated/0 or any custom directory to make the script look for marker files there, but it may not work because internal storage is generally not mounted when the script starts, so it might not be able to read/write from there and may not work as expected.

[ZingyAwesome]

You could just change the value of service.sh and post-fs-data.sh to /storage/emulated/0 or any custom directory to make the script look for marker files there, but it may not work because internal storage is generally not mounted when the script starts, so it might not be able to read/write from there and may not work as expected.

Do you know which directories are available to scripts but are still writable when unrooted? Of course /data/adb isn't as that's owned by root but maybe there are some other ones that are?