ADB install failed errors (all error codes)
ADB install errors are notoriously cryptic. Here's a complete reference for every INSTALL_FAILED_* error code and the fix that actually works.
Most ADB install failures fall into three buckets: wrong ABI (use a matching APK), signature mismatch (add -r to reinstall), or blocked target SDK (add --bypass-low-target-sdk-block). Full error-code table below.
Your device doesn't have enough free space. Clear app caches or uninstall something — usually you need at least 2× the APK size to install.
You're trying to install an older version over a newer one. Either uninstall the existing app first, or pass adb install -d to allow the downgrade.
Same package, same signature, same version. Use -r to reinstall: adb install -r app.apk.
The APK is corrupt, truncated, or not actually a valid APK. Re-download the file.
An app with the same package name is installed but signed with a different key. Uninstall the existing app — there's no way around this without losing the user data.
Your work profile or parental controls are blocking the install. Contact your admin.
The APK requires a newer Android version than your phone runs. Find a build for your API level.
The package is already installed. Reinstall over it with adb install -r app.apk (keeps data) or uninstall first with adb uninstall <package> then install fresh. -r is the quickest fix when you're updating your own build.
The APK doesn't contain native libraries for your device's CPU architecture — for example an arm64-only APK on an x86 emulator, or vice versa. Use an APK built for the right ABI, a universal APK, or adb install --abi where supported. For split APKs, install all the matching splits together.
The APK's minSdkVersion is higher than your device's Android version, so it can't run. You need an older build of the app that supports your Android version, or to update the device. There's no flag that bypasses a genuine minSdk requirement.
ADB couldn't even start the install — usually the device is offline/unauthorized, the APK path is wrong, or storage is full. Confirm adb devices shows "device", check the file path, free up space (INSUFFICIENT_STORAGE), and retry. The specific INSTALL_FAILED_* line after it tells you the real cause.
A single adb install fails for split APKs — use adb install-multiple base.apk split_config.*.apk (or install-multi-package for several apps). GUIs like Andora detect a split bundle and install all parts automatically.
Andora wraps ADB in a clean Windows GUI — drag-drop APK installer, wireless setup, screen mirroring, and one-click fixes for the errors above.
Download Andora