mountify

To achieve unmounting, it is recommended to use Zygisk providers like NeoZygisk, NoHello, ReZygisk, or Zygisk Assistant.

If using Zygisk Next, set the Denylist Policy to "Enforced" or "Unmount Only".

Then, configure the following in config.sh:

1. Set the provider type:
   • MOUNT_DEVICE_NAME="APatch" (for APatch)
   • MOUNT_DEVICE_NAME="KSU" (for KernelSU forks)
   • MOUNT_DEVICE_NAME="magisk" (for Magisk)
2. Enable in-kernel unmount methods (as a second choice to Zygisk):
   • mountify_custom_umount=1 (default is 0)

To add support for a new language in the Mountify WebUI, follow these steps:

1. Fork the repository.
2. Create the translation file: Copy webui/public/locales/en.xml to the strings folder and rename it to {language-code}.xml (e.g., es.xml). Use standard language codes (refer to Crowdin language codes).
3. Register the language: Add an entry to webui/public/locales/languages.json. The format must be "language-code": "Language name in your language". Maintain alphabetical order in the JSON object.
4. Translate: Translate all string values within your new .xml file.
5. Credit: Add your information to webui/public/locales/CONTRIBUTOR.md.
6. Submit: Open a pull request.

{
    "en": "English",
    "fr": "Français",
    "zh-CN": "简体中文"
}

To use Mountify, ensure your environment meets these requirements:

• Kernel Config: CONFIG_OVERLAY_FS=y is required. CONFIG_TMPFS_XATTR=y is highly encouraged.
• Compatibility: Works as a KernelSU metamodule, and is compatible with APatch and Magisk.
• Limitations:
  • Fails with De-Bloater because it uses dummy text instead of proper whiteouts.
  • Recommendation: Use System App Nuker instead, as it uses proper whiteouts.

You can prevent Mountify from mounting a specific module by creating a trigger file in the module's directory (/data/adb/modules/<module_id>/):

• KernelSU / APatch (Metamodule mode): Create a file named skip_mount.
• Magisk: Create a file named skip_mountify.

When using tmpfs mode (the default methodology), you can use the following settings in config.sh:

• test_decoy_mount=1: Enables testing for decoy mounts on tmpfs mode.

Mountify can be configured through its WebUI or by manually editing /data/adb/mountify/config.sh.

General Configuration

• mountify_mounts: Set to 2 to mount all modules with a system folder (default), or 1 to mount only specific modules listed in modules.txt.
• FAKE_MOUNT_NAME: Set a custom name for the fake folder (e.g., FAKE_MOUNT_NAME="mountify").
• mountify_stop_start: Set to 1 to restart Android at service (required for certain modules).

Module Selection

If mountify_mounts=1, you must list the desired module_ids in /data/adb/mountify/modules.txt:

module_id
Adreno_Gpu_Driver
DisplayFeatures
ViPER4Android-RE-Fork
mountify_whiteouts

# Example modules.txt content
module_id
Adreno_Gpu_Driver
DisplayFeatures
ViPER4Android-RE-Fork
mountify_whiteouts

If your setup is tmpfs_xattr capable, you can force ext4 sparse mode using these settings in config.sh:

• use_ext4_sparse=1: Forces the use of ext4 mode.
• spoof_sparse=1: Attempts to spoof the sparse mount as an Android service.
• FAKE_APEX_NAME="com.android.mntservice": Customizes the name of the spoofed Android service.
• sparse_size="2048": Sets the sparse image size in MB.
• enable_lkm_nuke=1: Attempts to load an experimental LKM to remove ext4 nodes.
• lkm_filename="nuke.ko": Defines the filename for the LKM.

The Module Selector allows you to choose which installed modules Mountify will interact with. It scans /data/adb/modules for directories containing a system folder but no etc/hosts file. The selection is persisted to /data/adb/mountify/modules.txt.

To use this programmatically or understand the logic:

1. The UI fetches the list of eligible modules using exec.
2. It reads the current selection from /data/adb/mountify/modules.txt.
3. Upon saving, it writes the selected module names back to /data/adb/mountify/modules.txt using a newline-separated list.

The Web UI includes a switch to toggle whether the module uses updateJson or updateLink in its module.prop file. This is managed via a sed command executed through the system.

Logic:

• If updateJson is present, it replaces it with updateLink.
• If updateLink is present, it replaces it with updateJson.