FAQ

📝 Before Reporting Issues

Please read the FAQ below before reporting bugs. Please reproduce and report issues with the latest Alpha/CI build whenever possible, because problems in the Stable build may already be fixed.

Alpha/CI builds can export logs from Settings -> About. Please attach that exported log and include:

• Device Brand & Model
• System Version (Android version & ROM version)
• App Version
• Authorization Method (Shizuku, Dhizuku, or Root)
• Steps to reproduce

Dhizuku is not working?

• Please update Dhizuku to the latest version.
• On customized Chinese ROMs, random errors are often caused by the system killing Dhizuku's background process. Please try restarting the Dhizuku app.
• Dhizuku has limited permissions compared to Shizuku. It cannot perform advanced operations like bypassing system intent interception or specifying installation sources. We recommend using Shizuku if possible.

Cannot lock the installer?

• Some systems strictly restrict 3rd-party installers. You need to use an LSPosed module to intercept the intent and forward it to InstallerX.
• We recommend using it with InxLocker for the best experience.
• Other locker modules are no longer recommended.

Error: No Content Provider or Permission Denial during analysis?

• This happens if you are using Hide My Applist (HMA) or similar modules.
• Please configure the whitelist to allow InstallerX to access the necessary providers.

HyperOS/Vivo error: "Installation requires a valid installer declaration"?

• This is a system security restriction. You need to declare the installer package name in the settings.
  • HyperOS: Recommend com.android.fileexplorer or com.android.vending.
  • Vivo: Recommend the Vivo App Store package name.
• Shizuku/Root works fine; Dhizuku does not support this.
• On HyperOS, InstallerX automatically adds a config for com.android.shell on startup. You can change this in Settings.
• If Smart Suggestions is enabled, you can click the suggested option to bypass this restriction upon failure.

HyperOS: Installer lock reverts to default automatically?

• Tap the default installer status card on the home page and enable "Auto Lock Installer" on the Default Installer page.
• On some HyperOS versions, locking is simply not possible due to system constraints.
• HyperOS intercepts USB installation requests (ADB/Shizuku) via a dialog. If you click "Deny" when installing a new app, the system might revoke the installer preference and force it back to default. If this happens, please re-lock it.

Notification progress bar gets stuck?

• Some customized systems manage background processes very aggressively. Please set the Background Battery Usage for InstallerX to "No restrictions" (Unrestricted).
• The app is optimized for background management. It will automatically clean up background services and exit 1 second after the installation task is complete (user clicks finish or clears notification). Enabling "No restrictions" will not cause extra battery drain.

Issues on Oppo / Vivo / Lenovo / etc.?

• We do not have devices from these brands for testing. Please visit Discussions or our Telegram Channel for help.
  • Oppo/Vivo: You likely need a locker module to replace the system installer.
  • Honor: When using Shizuku, disable "Monitor ADB Installation" in Developer Options, otherwise installation will hang.

How to install Magisk/KernelSU modules?

1. Go to Settings -> Laboratory and enable "Enable Module Flashing".
2. Open the ZIP file using InstallerX (via file manager "Open with" or "Share to").

How to replace the System Package Manager?

This is a high-risk operation. The full guide lives in System Integration: System Package Manager Mode.

In short: you can either overwrite the APK after Core Patch or flash a module. Before flashing, verify that the system package manager package name, mount path, and permission files match the build you choose.