wxxsfxyzm/InstallerX-Revived: +105 stars this week

Rank of wxxsfxyzm/InstallerX-Revived in each topic for today, this week and this month
Topic	Today	This week	This month
Kotlin	–	#79of 128	#84of 186
Android	–	#143of 241	#166of 385

InstallerX Revived (Community Edition)

English | 简体中文 | Español | 日本語 | Deutsch

A modern and functional Android app installer. (You know some birds are not meant to be caged, their feathers are just too bright.)

Looking for a better app installer? Try InstallerX!

InstallerX Revived is a modern Android package installer and the community-maintained continuation of the original InstallerX project.

It is designed to replace limited stock or OEM package installers with a cleaner interface, broader package support, configurable installation profiles, and privileged workflows through Shizuku, Root, Dhizuku, or the system package manager mode.

Documentation

The full user guide, installation instructions, advanced options, system integration notes, and FAQ are maintained on the documentation site.

Highlights

Package formats: APK, APKS, APKM, XAPK, APK files inside ZIP archives, and batch APK installation.
Dialog batch selection: clearing a single-version package row clears its files; selecting it again restores the file choices from before clearing, including split and dex metadata choices. This applies to both UI styles within the same analysis; individual file edits or explicit APK-wide selection changes supersede the saved choices.
Install flows: dialog installation, background notification installation, automatic installation, silent installation when privileges allow it, and Android 16+ Live Activity progress on supported systems.
Authorizers:
- Root: can perform all privileged operations, but may be slower because of cold app_process startup.
- Shizuku: obtains shell or root capabilities depending on how it is activated, and is usually faster than direct Root.
- Dhizuku: can perform DevicePolicyManager-based operations such as default installer locking and app installation, but is limited for other privileged tasks.
- None: is fully limited by the system, but can silently install when InstallerX is running as the system package installer.
Profiles: define how installation and uninstallation requests are handled, including install mode, authorizer override, installer/requester metadata, target user, DexOpt, auto-delete behavior, split selection, blacklist policy, and signature gates.
System integration: InstallerX can be locked as the default installer from the Home page status card, used with LSPosed modules such as InxLocker, or installed as a replacement system package manager by advanced users.
Modern UI: Material 3 Expressive and Miuix interface styles, dark mode, dynamic color, advanced palettes, system icon packs, colorful dialogs, standard notifications, Live Activity, and Xiaomi HyperOS-style island notifications on supported Xiaomi devices.
Safety controls: package-name and SharedUID blacklists, signature mismatch and unknown-signature policy gates, permission preview, install flags, and one-time smart suggestions for selected blocked cases.

Supported Android Versions

Full support: Android SDK 34 - 37.0
Limited support: Android SDK 26 - 33

Limited support means InstallerX may work, but some features can be unavailable or behave differently because of Android framework, OEM, or authorizer limitations.

Downloads

Stable releases: https://github.com/wxxsfxyzm/InstallerX-Revived/releases/latest
Alpha builds: https://github.com/wxxsfxyzm/InstallerX/releases
CI builds: https://github.com/wxxsfxyzm/InstallerX-Revived/actions/workflows/auto-preview-dev.yml
Telegram channel: https://t.me/installerx_revived

When reporting bugs, please reproduce them on the latest Alpha or CI build whenever possible, because issues in Stable may already be fixed.

InstallerX is now published as a single APK. Network access is controlled by an in-app setting. The release filename continues to include online only for compatibility with older in-app update clients; it no longer identifies a separate build variant.

Building

InstallerX Revived is an Android Gradle project.

Prerequisites

JDK 25 with JAVA_HOME configured correctly.
Android SDK / Android Studio with the required platform and build tools installed.
GitHub Packages credentials for the snapshot miuix dependency.

GitHub Packages Authentication

GitHub Packages requires authentication even for public packages. Add your GitHub username and a classic personal access token with the read:packages scope to your global Gradle properties file:

Linux / macOS: ~/.gradle/gradle.properties
Windows: %USERPROFILE%\.gradle\gradle.properties

gpr.user=YOUR_GITHUB_USERNAME
gpr.key=YOUR_PERSONAL_ACCESS_TOKEN

Do not commit these credentials to this repository.

Build Commands

For a local debug build:

./gradlew assembleUnstableDebug

For a PR-style test build with a separate application id:

./gradlew assemblePreviewDebug -PAPP_ID="com.rosan.installer.x.revived.test"

Common Questions

Where should I report bugs or ask questions?

Use GitHub Issues for reproducible bugs and concrete feature requests. Good suggestions are welcome. Use GitHub Discussions or the Telegram channel for general questions and compatibility discussion.

Before opening an issue, please read CONTRIBUTING.md for the required logs and reproduction details.

I cannot lock InstallerX as the default installer

Some OEM systems strictly control the default package installer. Open the default installer page from the Home page status card and try locking from there. If the ROM still prevents it, use an LSPosed module such as InxLocker.

HyperOS says installing system apps requires a valid installer

This is an OEM security restriction. InstallerX can declare installer metadata through profiles, and on HyperOS it uses com.android.shell as the default compatibility installer package. Shizuku or Root is required for this workflow; Dhizuku is not enough.

Notification installation progress is stuck

Some ROMs restrict background services aggressively. Set InstallerX to unrestricted background/battery mode if notification installation stalls. InstallerX cleans up its foreground service shortly after the installation task finishes.

How do I replace the system package manager?

This is a high-risk advanced workflow. The short version is: use Core Patch to overwrite the APK, flash a matching module, or integrate the matching package into super / a ROM build. Before flashing or packaging, verify the package name, mount path, and permissions file for your ROM.

See the system integration guide for details: https://wxxsfxyzm.github.io/InstallerX-Revived-Website/guide/system-integration