"App Not Installed" When Installing a Patched APK: Causes and Fixes

"App not installed" is Android's least helpful error. It covers half a dozen different problems with the same message. With patched APKs it's almost always one of the causes below, roughly in order of how often they come up.

1. The original app is still installed

This is the big one. Every APK is signed, and Android only lets you install an update over an app if both are signed with the same key. A patched APK is re-signed by whoever built it, so it can't replace the Play Store version.

Fix: uninstall the original app first, then install the patched one. Be aware this deletes the app's local data. Anything that isn't synced to an account (offline downloads, local settings, unsynced notes) is lost, so back it up first if the app has an export option.

Some patches rename the app's package so it can sit next to the original. When a build does that, its page says you can keep both. If it doesn't mention it, assume you can't.

2. An older patched build from a different source

The same signature rule applies between patched builds. A YouTube you patched yourself in Morphe Manager is signed with your own key. A pre-patched download from here is signed with the build pipeline's key. They can't update each other, so uninstall one before installing the other.

3. You're trying to install an older version

Android won't downgrade an app in place. If the installed version is newer than the APK, even if it's the same patched build, the install fails. Uninstall first, or wait for the patched build to catch up.

4. Wrong architecture

An ARM64-only APK won't install on a phone running 32-bit Android, and an ARMv7-only APK won't install on recent Pixels. If the app page offers several downloads, try another one. This guide explains which one your phone needs.

5. Play Protect blocked it

Google Play Protect sometimes flags modified apps. Depending on your Android version you'll see a warning with an "Install anyway" option, or the install silently fails. You can scan the APK yourself first, then either choose "Install anyway" or pause Play Protect's app scanning in the Play Store settings while you install. Turn it back on afterwards.

6. Android version too old, or the app too old for your Android

Every app has a minimum Android version, and the patched build keeps the original's. The requirement chip on each app page shows it. The reverse also happens: Android 14 and newer refuse to install apps built for very old Android versions. That rarely affects anything on this site, but it's why some ancient APKs from elsewhere won't install.

7. The download is incomplete

A connection drop can leave you with a truncated file that Android can't parse. It usually shows up as "There was a problem parsing the package" rather than "App not installed". Compare the file size with the size on the download box and download again if it's short.

8. Not enough free space

Installing needs room for the APK and the unpacked app at the same time, so a 150 MB APK can need well over 300 MB free. Clear some space and retry.

9. It's a system app you can't remove

On some phones the app you want to replace is part of the system image. Google Phone on Pixels and the stock keyboard on some brands are examples. You can disable those, but not fully uninstall them without root, so a patched build with the same package name can't be installed. Check the app's page; it mentions this where it applies.

Still stuck?

If none of this helps, the problem is probably with the build itself. Each app page links to the patch bundle it was built with. Search that repository's issues for your error before opening a new one, and include your phone model, Android version and the exact file you downloaded.