Library / SDK
zacharee/InstallWithOptions avatar
zacharee/InstallWithOptions

Install with Options: shell-level installs, and the three options that do less than they say

Simple-ish app using Shizuku to install APKs on-device with advanced options

3,447 stars175 forksKotlinMIT

At a glance

What is it?
Install with Options is a small Android app that installs APKs with permissions it does not have, by borrowing shell access from Shizuku. What it enables, test-only builds, low target SDK installs, some downgrades and split APKs, comes with limits the project states plainly: it cannot bypass signature verification, it cannot grant special permissions, and two of its most attractive switches stop working on Android 14.
Who is it for?
Install with Options earns its place on a device you own for developer work: reading an app that only ships a test build, installing a split APK you assembled, or getting an older build onto a device where the platform has closed the door. Two conditions come with it.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 22 days ago.
What is it written in?
Mainly Kotlin, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • zacharee/InstallWithOptions3,447 ★ · +179
Star history
Repository2026-09-242026-11-15
zacharee/InstallWithOptions3.3k3.4k

179 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What the app installs, and the four things it explicitly cannot install over

The stated purpose is advanced app installs without ADB. It borrows shell permissions through Shizuku, and on Android 11 and later that is enough to install test-only apps, get around Android 14's target SDK limit, downgrade certain packages, install split APKs and batch-install several separate apps, all from the phone.

The same file is equally clear about the ceiling. Four capabilities are ruled out in its own words.

Signature verification is not bypassed. `Disable Verification` only disables basic package verification for certain special APKs, and an update signed by someone other than the installed app still fails with `INSTALL_FAILED_UPDATE_INCOMPATIBLE`; without root and specific system patches, the only route is uninstalling the old version first.

Special permissions are not granted. `Grant All Requested Permissions` covers runtime permissions such as camera and microphone. All Files Access and accessibility services are not in scope.

Managed profiles are not escaped. App installs inside a work profile or a guest user are refused by the platform and the app says so. And on Android 14 the installer package field can be set but the originating package field cannot, with no workaround.

Everything the app can do is bounded by whichever Shizuku it is given

There is no root requirement and no separate privilege of its own. The elevated access belongs to Shizuku, and Install with Options is a client of it. That is the security boundary in one sentence: the blast radius of this app equals the shell access the Shizuku instance on the device has been granted.

The compatibility statement widens that boundary deliberately. The app is described as compatible with the original Shizuku and with any forks using different package names or hiding themselves. Forks are a reasonable answer to a broken Shizuku release, but a fork that hides itself is also the shape a malicious one takes, and nothing in the file verifies which Shizuku is answering. If that binary came from an unofficial mirror, this app inherits its permissions without telling you.

The two documented download sources for the app itself are the GitHub releases page and the IzzyOnDroid repository. Nothing else is named, and the package identifier in that repository path is `dev.zwander.installwithoptions`, which no longer matches the repository owner, so the listing address and the project name have drifted apart over the app's life.

Four installer error strings and what each one is actually telling you

The troubleshooting section is the most useful part of the file, and all four of its errors are platform refusals rather than app bugs.

`INSTALL_FAILED_NO_MATCHING_ABIS` means the APK carries native C or C++ libraries, which must be compiled per CPU architecture. An x86 or amd64 device with an ARM-only build fails, and there is no workaround beyond finding a build for your architecture. The same error appears on ARM64 devices when the APK contains only ARM32 libraries, because newer chipsets and Android versions are dropping ARM32 support.

`INSTALL_FAILED_VERSION_DOWNGRADE` is Android being stricter over time. On Android 14 and later a downgrade works only with root or when the app was compiled with debugging or test mode enabled, and the file states that this holds even when the `Allow Downgrade` option is selected.

`INSTALL_FAILED_USER_RESTRICTED` has two sources: a managed profile or guest user, which the app cannot bypass, or an Android skin that limits sideloading, which is governed by developer options on the device.

The fourth is not a package error at all. Shell access to user X missing is a work profile, the kind created by Shelter or TestDPC, where a user restriction has to be lifted by whoever created the profile.

The work profile case needs the profile's creator, not the phone owner

That last error deserves its own paragraph because the fix is not on the device. When an app is installed inside a work profile created by something like Shelter or TestDPC, the shell user has no permission to reach that profile's user, and the profile carries a restriction that blocks debugging features from being enabled inside it. Turning that restriction off requires an app that manages profiles to do it from within the profile, and if the tool that created the profile does not offer the option, the file says you have to ask that developer to add it.

So the boundary here is not technical. It is a permission held by a different piece of software. That is the same shape as the managed profile case above it, where the platform refuses installs outright, and the file groups them by pointing the work profile question back to the shell permission section rather than pretending it is a settings problem.

Practical reading: if your workflow depends on installing into a work profile, this app does not solve it, and the person who built the profile tool is the one who has to change something.

Three options are narrower than their labels, and one of them only exists on Android 14

The FAQ collects the switches that surprise people, and the pattern is that the platform moved and the option kept its name.

`Bypass Low Target SDK Block` is only there because Android 14 added a low target SDK block. On Android 13 and earlier the flag is not shown at all, and if an old app fails to install on those versions the cause is something other than this block, since base Android only gained it in 14. So the option's absence is not a bug and its presence tells you nothing about versions below 14.

`Grant All Requested Permissions` grants runtime permissions only. Camera and microphone are runtime permissions and get granted. All Files Access is a special permission and accessibility services are a special app access, and neither is granted or enabled automatically.

Setting the installer package name is the one with no path forward. Android 14 restricted what the shell user may do about install attribution: ADB can still set the installer package field, but not the originating package field. The file says there is no workaround, and that a workflow depending on a custom originating package value will not work on Android 14 or later.

Shizuku 13.6.0 is broken on Mediatek and the fix has been waiting about a year

The dependency has a version trap worth knowing before you blame the app. Version 13.6.0 of Shizuku does not work on Mediatek devices. A fix has been merged in the Shizuku repository, but the file notes it has been almost a year since 13.6.0 was released, so the released version most people install is the broken one on that hardware.

The stated ways out are to downgrade to Shizuku 13.5.4 or to use a fork, with thedjchi's Shizuku offered as an example. Both have costs. Downgrading means running an older service, and a fork means trusting a different binary with the shell access that this whole design depends on.

The app's own release history has the same shape of slow cadence: 0.9.0 on 21 September 2025, 0.9.1 on 31 January 2026 and 0.9.2 on 14 March 2026, still inside the 0.9 range, while the default branch was pushed on 9 September 2026. So the newest published build is several months behind the source, which matters when the fixes you need are platform compatibility fixes.

The file points elsewhere for anything beyond these cases, and its screenshots are empty tags

The scope statement is in the open rather than implied. InstallerX Revived is named as an advanced package installation manager that includes the features of this app and more, and the recommendation is explicit: if you need or want more features, use that instead. Install with Options is kept simple on purpose, and that framing also explains the four error sections and the short FAQ.

What the file does not contain is any usage walkthrough. There is no section on picking an APK, no description of the interface, and no configuration beyond option names. Downloads are two links, translations run through Crowdin, and the screenshots section is six empty image tags with no sources, so the visual documentation is absent rather than merely old.

The repository itself is a conventional Gradle project with Kotlin build scripts, a committed .idea directory, fastlane for releases and a changelog file. So the gaps are in the README rather than in the project, which is worth remembering before concluding that a missing answer means the feature is missing.

Editorial conclusion

Install with Options earns its place on a device you own for developer work: reading an app that only ships a test build, installing a split APK you assembled, or getting an older build onto a device where the platform has closed the door. Two conditions come with it. It is only as trustworthy as the Shizuku instance granting it access, and the file explicitly welcomes forks that hide themselves, so verify where that binary came from before you let it act on a phone. And it does not widen your rights beyond package installation: signature verification, special permissions like accessibility or all files access, and work profile restrictions stay in place, and on Android 14 the downgrade and originating package options stop working regardless of what the app interface shows. If you want a full package manager rather than these specific cases, the project names InstallerX Revived as the alternative to look at first.

Frequently asked questions

What is Install with Options used for?

It installs APKs on your own device with shell permissions borrowed from Shizuku, so you can install test-only apps, get around Android 14's target SDK limit, downgrade certain packages, install split APKs and batch-install apps without using ADB.

Is Shizuku safe to use with Install with Options?

The file does not assess Shizuku's safety. It says the app should be compatible with the original Shizuku and with any forks using different package names or hiding themselves, and it notes that Shizuku 13.6.0 does not work on Mediatek devices.

Does Install with Options bypass signature verification?

No. The Disable Verification option only disables basic package verification for certain special APKs. A signature mismatch gives INSTALL_FAILED_UPDATE_INCOMPATIBLE, and without root and specific system patches the old version has to be uninstalled first.

Why can Install with Options not install apps in a Work Profile?

The shell user has no permission to reach that profile's user, and a user restriction has to be disabled from inside the profile by the app that created it. If the profile creator does not offer the option, the file says you have to ask that developer to add it.

install with options alternative

The project names InstallerX Revived, an advanced package installation manager app that includes the features of Install with Options and more, and says to use that instead if you need or want more features.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. zacharee/InstallWithOptions on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/zacharee-installwithoptions.svg)](https://hysenlabs.com/projects/zacharee-installwithoptions)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/zacharee-installwithoptions.svg)](https://hysenlabs.com/projects/zacharee-installwithoptions)

Was this useful?