APK / DIAGNOSTICS
Independent Android troubleshooting reference

A practical guide for a failed install

Understand the error.
Keep your data.

An APK installation failure is a clue, not a reason to disable security checks or erase the existing app. Paste the error returned by ADB, or choose a code below, to see the most useful next checks.

No APK uploadsNo account requiredData-preserving steps first
INSTALL SESSION

$ adb install app.apk

Performing Streamed Install

Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]

↳ Check the package and signing certificate before changing the installed app.

01 / Decode

Paste the exact ADB message

The decoder matches known error codes locally in your browser. It does not upload your text or inspect an APK. Remove serial numbers or other private details before sharing an error elsewhere.

Choose a code below or paste an ADB result.

02 / Diagnose

Common installation results

Exact code meanings can vary with Android version and the complete diagnostic message. Use these as starting points, not a guaranteed fix.

01Protect existing data

Existing app and new APK do not match

INSTALL_FAILED_UPDATE_INCOMPATIBLE

Android can return this when an installed package with the same name has a different signing certificate. The file may be from another release channel or an unexpected source.

  1. Confirm the package name and the source of both builds.
  2. Compare the signing certificates with apksigner verify --print-certs app.apk where available.
  3. Back up local app data before considering any uninstall. Do not remove the old app merely to force the new file through.
Android app-signing documentation
02Check compatibility

APK libraries do not match the device

INSTALL_FAILED_NO_MATCHING_ABIS

The APK's native libraries may not include an architecture supported by this device. This is a compatibility issue, not evidence that the APK is safe or unsafe.

  1. Check the device ABI with adb shell getprop ro.product.cpu.abilist.
  2. Check which ABI the APK release provides; choose the publisher's matching build.
  3. Do not install a random “universal” repack from an unrelated site.
Android 64-bit compatibility guide
03Check requirements

Device Android version is too old

INSTALL_FAILED_OLDER_SDK

The package requires a higher minimum Android version than the device provides. An older app version might exist, but only use a trustworthy, clearly identified release.

  1. Record the device Android version and APK minimum SDK.
  2. Check the publisher's compatibility information.
  3. Avoid changing package metadata or downloading altered APKs just to bypass the requirement.
Android package-manager source
04Check free space

Not enough installation space

INSTALL_FAILED_INSUFFICIENT_STORAGE

Installation can need more free space than the APK's download size because Android has to stage and unpack files.

  1. Check available device storage in Settings.
  2. Remove unneeded downloads or other disposable files—not app data you want to keep.
  3. Retry only after confirming there is sufficient space; if it still fails, read the complete ADB output.
Android package-manager source
05Protect existing data

New file has a lower version code

INSTALL_FAILED_VERSION_DOWNGRADE

The APK may be older than the installed build. A lower version number in a filename does not necessarily tell the whole story; compare Android's version codes and release provenance.

  1. Confirm the version code of the installed app and the APK.
  2. Ask why an older build is needed and whether the publisher supports it.
  3. Back up data before any uninstall or downgrade experiment. Do not treat a forced downgrade as a routine fix.
Android package-manager source
06Security restriction

App targets an obsolete Android API

INSTALL_FAILED_DEPRECATED_SDK_VERSION

Newer Android versions may block installation of apps built for much older target SDKs. This restriction protects users from applications that do not adopt newer privacy and security behavior.

  1. Check the exact Android warning and the app's target SDK.
  2. Look for a current, maintained release from a trustworthy source.
  3. Do not bypass the low-target-SDK block simply to install an unverified APK.
Android 15 behavior changes

03 / Before any reset

Capture the evidence. Then decide.

A failed install and a Play Protect threat warning are not the same event. This decoder only interprets selected ADB package-install failures; it does not assess malware or verify a download. Keep Play Protect enabled, preserve playlists and other app data, and compare the APK against a trusted release before changing an installed package.

For a product-specific walkthrough, the YMusic installation guide explains the Android install path and checks to make before opening its APK. This is an example—not a blanket assurance that any APK is safe.

Sources & scope

How to use this reference

Descriptions are based on Android developer documentation and Android Open Source Project package-manager definitions, linked from each result. Error codes can have additional context in the full ADB output and vary by OS version. This tool runs entirely in your browser; it does not accept APK files, send pasted text to a server, diagnose malware, or promise that a file is safe. Last content review: 9 October 2026.