Last updated: November 16, 2026. Short answer: InstallerX Revived is a free, open-source (GPL-3.0) replacement for the Android app installer, and it’s popular with Xiaomi owners because it can take over from the stock HyperOS package installer. The current stable version is 26.09 (September 30, 2026), and a newer preview, 26.11, came out on November 12. It installs APK, APKS, APKM, XAPK and APKs inside ZIP files, can install silently and allow downgrades, and has a HyperOS-style (Miuix) interface. You don’t need root: Shizuku is enough. On HyperOS 4 (Android 17), use the community Shizuku 13.7.0 build by thedjchi. Download InstallerX only from the project’s GitHub.
InstallerX Revived download
Both files come from the official wxxsfxyzm/InstallerX-Revived releases on GitHub. Since 26.09 there is only one APK: the “online” in the file name is kept for in-app updates, and network access is a setting inside the app.
| Version | Released | File | Best for |
|---|---|---|---|
| 26.09 (stable) | September 30, 2026 | InstallerX-Revived-online-26.09.apk (5.8 MB) | Daily use |
| 26.11.caccb78 (preview) | November 12, 2026 | release page (5 MB) | Testing. Adds an experimental Shizuku non-ADB installation mode (see below), HyperOS 4 “glass” styling in the Miuix settings, and a fix for a crash when switching from the Miuix to the Material 3 theme |
SHA-256 of the 26.09 APK, as downloaded from GitHub on November 16, 2026: fe7ac4737885a0426042222e27ed0a637e481e72c742ebe09142fd51448ae85b.
Requirements: full support on Android 14 to 17 (HyperOS 1, 2, 3 and 4); limited support on Android 8.0 to 13. 26.09 is the last version for Android 8.0 and 8.1. Later versions need Android 9 or newer. The developers warn that switching between stable, preview and CI builds may require clearing the app’s data or reinstalling.
What’s new in InstallerX Revived 26.09
- One APK instead of separate online and offline builds, with an Allow Internet access switch and three download modes for installing from links (Full download, Smart, Low storage).
- Signature controls: signature analysis on or off, optional split analysis, signature details, and per-profile blocks for apps whose signature doesn’t match or is unknown. It also recognizes the new Android 17 signature schemes.
- Operation history (up to 100 entries) and backup and restore of profiles, scopes, settings and history.
- Module version check: when you flash a Magisk, KernelSU or APatch module, InstallerX compares it with the installed version.
- Automatic installer locking was removed. On HyperOS you lock InstallerX as the default installer manually (see below).
The previous big release, 26.05 (May 2026), added the Miuix and Material 3 Expressive redesign, Xiaomi Super Island notifications and a Control Center tile.
Why Xiaomi owners use it
- More formats: APK, APKS, APKM, XAPK, APKs inside ZIP archives and batch installs. You can choose which split parts (languages, screen density, CPU) to install.
- Options the stock installer doesn’t have: silent install, downgrade, install for another user, installing test-only apps and apps that target an old Android version, and setting which app is recorded as the installer.
- Profiles per source: for example, installs from a file manager show a dialog, while installs from an app store go silently in the background.
- Looks native on HyperOS: Miuix (HyperOS-style) or Material 3 Expressive interface, Live Activity progress on HyperOS 3.0.300 and newer, and Xiaomi Super Island notifications.
- Flashing Magisk/KernelSU/APatch modules from a ZIP, if you have root (Settings → Laboratory → Enable Module Flashing).
Don’t uninstall the stock installer (com.miui.global.packageinstaller on global ROMs) to “replace” it. Our HyperOS debloat guide lists it as unsafe to remove: APK installs can break, and bootloops have been reported. InstallerX works alongside it.
Root, Shizuku or Dhizuku: what you need
InstallerX needs elevated access for most of its features. These are the four authorization modes, as the official documentation describes them:
| Mode | What it can do |
|---|---|
| Shizuku (default, recommended) | Shell or root-level access depending on how Shizuku was started. Works without root and is usually faster than direct root. |
| Root (Magisk, KernelSU, APatch) | Everything, including module flashing. A bit slower to start. |
| Dhizuku | Locking the default installer and installing apps only. It can’t fix the HyperOS “valid installer” error. |
| None | Uses the normal system install dialog. Silent installs only work if InstallerX is the system installer. |
Shizuku on HyperOS 4: the official Shizuku 13.6.0 (May 2025) predates Android 17 and doesn’t work properly on it. Use the community build Shizuku 13.7.0 by thedjchi, which adds Android 17 support. On HyperOS 1 to 3, the official Shizuku works.
How to set up InstallerX Revived on HyperOS without root
- Download the APK above and open it. The stock installer will ask you to allow installs from your browser or file manager.
- Install Shizuku (the thedjchi build on HyperOS 4).
- Turn on Developer options: Settings → About phone → tap OS version several times. Then, in Settings → Additional settings → Developer options, enable Wireless debugging (the phone must be on Wi-Fi).
- In Shizuku, choose Start via Wireless debugging → Pairing, then pair it in Developer options → Wireless debugging → Pair device with pairing code, and press Start. Without root, you need to start Shizuku again after every reboot.
- Open InstallerX. On first use it asks for notifications, all-files access and Shizuku access. Allow them. Shizuku is the default authorizer, and you can check it on the Home tab.
- Tap the default installer status card on the Home tab and run the lock action. From now on, opening an APK uses InstallerX.
Then set the battery usage of InstallerX to No restrictions. HyperOS kills background services aggressively, which can freeze the progress notification. The developers say this doesn’t cause extra battery drain, because the app closes about a second after the install finishes.
HyperOS problems and fixes
- “Installation requires a valid installer declaration” (HyperOS isolation violation): HyperOS only lets a system app update system apps. On HyperOS, InstallerX already declares
com.android.shellas the installer. If it still fails, the developers recommend declaringcom.android.fileexplorerorcom.android.vendingin the settings, or tapping the Smart Suggestion that appears after the error. This needs Shizuku or root; Dhizuku isn’t enough. - The default installer goes back to the stock one: tap the status card on Home and lock again. HyperOS shows its own dialog for installs over USB/ADB (which includes Shizuku), and if you press Deny on a new app, the system can reset the default installer. On some HyperOS versions locking isn’t possible at all. Then the developers recommend the LSPosed module InxLocker, which needs root.
- “User restricted” or “installing via USB is not enabled”: HyperOS treats Shizuku installs as ADB installs. Enable Install via USB in Developer options and try again. If you can’t, try the 26.11 preview: in Settings → Laboratory, turn on Shizuku non-ADB installation backend. It creates the install session as InstallerX itself instead of the shell, so ROM limits on ADB installs don’t apply. The catch: it only installs for the current user, and the installer is always recorded as InstallerX, so the installer declaration trick for system apps doesn’t work in this mode.
- Slow installs on global ROMs (usually Play Protect scanning): try Disable System Install Verification in the InstallerX settings.
- Uninstalling a system app fails: HyperOS blocks this path for system apps. For debloating, see our debloat guide.
- Super Island on HyperOS 4: an open bug report (October 25) says Super Island notifications turn into standard notifications on HyperOS 4 / Android 17. Use Live Activity or normal notifications until it’s fixed.
What owners report on 4PDA
The InstallerX Revived thread on 4PDA follows every release, and the HyperOS tips there go beyond the official FAQ:
- xiaomi.eu HyperOS 3 doesn’t accept the default declaration for system-app updates. The suggestion in the thread is to set the installer source to one of
com.google.android.apps.nbu.files(Files by Google),com.xiaomi.mipicks(GetApps) orcom.xiaomi.discover(System apps updater) (post). Another owner says the installer source setting works under Shizuku on Android 15 and 16, “but not always” (post). - Not every install goes through InstallerX. Owners on HyperOS 3.3 report that Firefox and third-party app stores still open the stock installer, and apps with their own updaters (banking apps, for example) keep using the system one. That’s when the thread points to the InxLocker module.
- KernelSU users: use Shizuku. The developer explained (relayed in the thread) that KernelSU’s superuser list blocks overlays, so InstallerX can’t get root access through KernelSU and some of its forks until they fix it (post).
- “Installing via USB is not enabled” on the November previews was reported on November 2 (post). The non-ADB mode described above came out two days later.
- An alternative: the developer also suggests trying Shizuku PackageInstaller by vvb2060, on which the non-ADB mode is based. It installs next to the stock installer instead of replacing it (post).
Replacing the system package installer (advanced)
Advanced users can go further and make InstallerX the system package manager. According to the official guide, this means overwriting the APK after Core Patch, flashing a matching module, or building it into the ROM. On China HyperOS, the guide says to enable Use native installer in Cemiuiler (System Framework → Other) before flashing the AOSP build. The developers call this a high-risk procedure: you need root, and the package name, mount path and permission file have to match your ROM. Follow the official system integration guide and have a Fastboot ROM for your phone ready. For most people, locking InstallerX as the default installer is enough.
FAQ
Is InstallerX Revived safe?
It’s open source under GPL-3.0, with about 7,500 stars on GitHub, and it continues the original InstallerX by iamr0s. Download it only from the GitHub releases or the project’s Telegram channel @installerx_revived, and compare the SHA-256 above. Copies on APK sites can be modified.
Does InstallerX Revived need root?
No. Shizuku, started through Wireless debugging, is enough for silent installs, downgrades and the HyperOS installer declaration. Root is only needed for module flashing, InxLocker and replacing the system installer.
Does it work on HyperOS 4 and Android 17?
Yes. Android 17 has full support. Use Shizuku 13.7.0 by thedjchi, because the official Shizuku 13.6.0 doesn’t work properly on Android 17. If HyperOS blocks Shizuku installs as USB installs, try the non-ADB mode in the 26.11 preview. Known HyperOS 4 issues: Super Island falls back to a standard notification, and a crash when switching themes was fixed in the 26.11 preview.
Online or offline APK: which one do I download?
Since 26.09 there is only one APK. The file name still says “online”, but you can turn off Internet access in Settings → Network settings.
Can it install XAPK and APKS files on Xiaomi?
Yes: APK, APKS, APKM, XAPK and APKs inside ZIP archives, and you can choose which split parts to install.
Sources: InstallerX Revived README and release notes (26.05, 26.09, 26.11.caccb78); official documentation: Installation, Quick Start, FAQ, Exceptions, System integration; GitHub issue #881 (Super Island on HyperOS 4); pull request #895 (Shizuku non-ADB installation); thedjchi Shizuku 13.7.0 release notes; 4PDA InstallerX Revived thread (header updated November 12, 2026, owners’ posts May–November 2026).
Xiaomi firmware & news on Telegram
New firmware, HyperOS 4 rollout updates, guides and Xiaomi news, all in one channel.

