Rolling an app back to a version that worked
Sometimes an update removes a feature, breaks compatibility with an older phone, or simply crashes. Android has no rollback button, but it will let you install an older build if you handle the data and the signature correctly. There are three parts: getting the right file, replacing the installed copy, and preventing the automatic update from putting you back where you started.
Choosing which version to go back to
Do not jump to a build from three years ago. Go back one release at a time, because the further back you go the more likely it is that the app's servers no longer accept that client at all.
- Find your current version In the app's settings, usually under About, or in Android's app info screen.
- Open the version history The Old Versions link on the app's APKCombo page lists every build with its date and Android requirement.
- Take the release just before yours If that still misbehaves, step back one more rather than guessing.
- Check the architecture Old builds sometimes only exist as universal APKs, which is fine, or as separate arm64 and armeabi-v7a files, which is not interchangeable.
广告
Installing it over the current version
Android refuses to install a lower version code over a higher one. That is a deliberate protection, and the way round it is to remove the installed app first.
- Check what syncs Sign-in state, chat history and game progress each behave differently. Chat apps usually offer their own backup step, and it is worth running it manually.
- Uninstall the app Not disable, uninstall. Disabled system apps behave differently and often cannot be replaced at all.
- Install the older APK Allow installs from your file manager or browser if prompted.
- Restore, then check Open the app and confirm the thing that was broken now works before you spend time setting it up again.
Stopping it updating back
This is the step that matters. Play Store auto-update runs on its own schedule and will happily reinstall the build you just removed.
| Where | What to turn off |
|---|---|
| The app's Play Store page | The three-dot menu, then clear Enable auto update |
| Play Store settings | Auto-update apps, set to Do not auto-update or WiFi only if you prefer to decide each time |
| Some phone makers | A separate app store with its own updater, which needs turning off separately |
Pinning a version is a temporary measure, not a permanent state. An app frozen for a year stops receiving security fixes, and eventually its server refuses the old client. Revisit it when the next release lands.
When a downgrade will not work
- Offline tools and utilities
- Media players and file managers
- Most games with local progress
- Apps whose update simply changed the interface
- Banking apps, which enforce a minimum client version
- Apps whose data format changed and cannot be read backwards
- System apps updated as part of Android itself
- Anything where the server has dropped the old protocol
One version back, uninstall before installing, and turn off auto-update for that app or the phone will undo your work by morning.
Frequently asked questions
Will I lose my data?
Yes, unless the app syncs to an account or you exported a backup first. The uninstall step is what removes it, not the older version.
Can I downgrade without uninstalling?
Not on a normal phone. The package manager blocks a lower version code, and the flag that allows it is only available over ADB on debug builds.
Is an older version less secure?
It can be, and increasingly so over time. Treat a rollback as something you undo once the app is fixed.
Read next
This is not a rivalry. Each does something the other cannot.
You are not buying encryption. You are buying an operator whose income does not depend on you.
For a plain ZIP either works. For a split, password-protected archive, only one does.
