How to downgrade an Android app to an older version

Why Android refuses a downgrade

The installer compares the version code of the package with the version code of the installed app. A lower number is rejected with App not installed or, in the system log, INSTALL_FAILED_VERSION_DOWNGRADE. There is no user-facing switch to override this on a normal device, so a downgrade always means removing the current version first.

Step by step

1. Find the version you want on the app's version page. Check the Requires Android field and pick a build your device supports.
2. Back up anything the app stores only on the device. Chat apps, note apps and games without cloud saves lose local data on uninstall.
3. Uninstall the current version. On most phones a long press on the icon offers Uninstall; on Samsung use Remove.
4. Install the downloaded APK or XAPK as described in the install guide.
5. Open Google Play, go to Manage apps and device, find the app and turn off auto-update for it, otherwise Play replaces it with the latest version at the next update cycle.

Keeping your data

If the app has a built-in export or account sync, use it before uninstalling. For everything else, the only reliable way without root is adb backup, which many modern apps opt out of. Assume local data is gone and plan accordingly. Signed-in apps normally restore server-side data on the next login.

Stopping the re-update

Google Play updates apps it installed originally. After you install from an APK, Play still recognises the package and may update it if the signature matches. The per-app Enable auto-update toggle inside the Play listing is the switch to turn off. On the version page you will also find the version code, which you can compare with Play to make sure you are still on the build you chose.

When a downgrade does not help

• Server-backed apps (banking, ride-hailing, most social networks) can refuse to run on builds the developer has retired. The app opens and then demands an update.
• Games with online saves may migrate the save format; an old build cannot read the new one.
• An older build may need a lower Android version than you have. Very old builds sometimes fail on Android 14 and later because of stricter security defaults.

In those cases a slightly older version often works where a much older one does not. Try the newest build before the one that caused the problem first.