Downgrade Kodi on Firestick the right way and you can get your old setup back without starting from scratch. Here’s the short version: back up your .kodi folder, uninstall the current Kodi, and sideload an older APK from the official mirrors.kodi.tv archive. Then restore your addons and addon_data selectively. Fire OS won’t install an older version over a newer one, so uninstalling first is the only reliable route. No shortcuts, no magic flags.
Nearly every Kodi guide out there pushes you forward to the newest release. This one goes the other way. You hit “update,” and now your favorite addon throws errors, your build looks wrecked, or the skin you depended on just won’t load.
Good news: as of 2026, you can still downgrade Kodi on Firestick without much fuss. The catch is knowing three things up front. What Fire OS blocks, what uninstalling wipes, and how to bring your data back without corrupting it.
Why You Might Need to Downgrade Kodi on Firestick
Kodi moves in big jumps. Nexus (20) landed in early 2023, Omega (21) followed in spring 2024, and each jump can change internal APIs, database formats, and skin requirements all at once. The third-party ecosystem doesn’t always keep up.
Addons That Stop Working After a Major Version Jump
The most common complaint? A Kodi update broke your addons. Every addon lists the Kodi components it depends on inside its addon.xml file, and if the developer hasn’t updated that file for the new release, the addon may refuse to install, fail without any message, or crash the moment you open it.
Abandoned addons are the worst case. Nobody maintains them. They may never support the new version, so you’ll need to downgrade Kodi on Firestick if you want to keep using them.
Builds and Skins That Lag Behind New Releases
A Kodi build bundles a skin, a stack of addons, and custom settings, and it almost always targets one specific Kodi release. Drop a Nexus build onto Omega and you’ll often get missing menus, dead widgets, or plain old Estuary staring back at you where your build used to be.
Skins suffer the same way. Kodi’s GUI engine shifts between versions, so skin authors have to push updates. Some manage it in a couple of weeks. Others take months, and that wait is why many people downgrade Kodi on Firestick.
When Downgrading Is Not the Right Fix
Be honest with yourself first. If Kodi won’t install at all, crashes at the splash screen, or shows a specific error code, you’re dealing with an installation problem, not a version problem. Fix the error before anything else.
There’s also a trade-off. Older Kodi means older bug fixes and older security patches. You can downgrade Kodi on Firestick just fine, but treat it as a temporary bridge until your addons catch up.
Why Fire OS Won’t Install an Older Kodi Over a Newer One
This is where most people who try to downgrade Kodi on Firestick get stuck. They grab an older APK, hit install, and Fire OS answers with a flat “App not installed.” The file isn’t broken. Android is doing exactly what it was built to do.
How Android Version Codes Block Downgrades
Every Android app carries a hidden internal number called a version code. During an update, Android checks that the incoming version code is higher than the installed one. Lower? Rejected.
Fire OS sits on top of Android, so it inherits this rule wholesale. Kodi 20.5 has a lower version code than any 21.x release, which means it simply can’t overwrite it, so the only dependable way to downgrade Kodi on Firestick is removing the newer Kodi first.
What Uninstalling Actually Deletes
Now the painful bit. Kodi keeps everything in Android/data/org.xbmc.kodi/files/.kodi on internal storage, and when you uninstall, Android deletes that entire folder.
Everything lives there. Addons, repositories, settings, sources, favorites, watched history, library databases. Downgrade Kodi on Firestick without a backup and you’re staring at a completely blank Kodi.
Why the ADB Downgrade Flag Usually Fails on Retail Firesticks
Forum threads love to recommend adb install -r -d kodi.apk. The -d flag allows a version downgrade while keeping your data intact. On paper, it’s perfect.
In practice, Android’s own documentation limits that flag to debuggable packages. Official Kodi release APKs aren’t debuggable, and retail Fire TV devices run production builds, so the odds are stacked against you. Try it if you’re curious. Just don’t build your plan to downgrade Kodi on Firestick around it.
Back Up Before You Downgrade Kodi on Firestick
Don’t skip this section. When you downgrade Kodi on Firestick, five minutes of backing up separates a quick rollback from rebuilding your whole setup from memory at 11 p.m.
Which Kodi Folders Matter: userdata and addons
Inside the .kodi folder, two subfolders do the heavy lifting:
- addons – the installed addon code, repositories, skins, and dependencies. You can skip the “packages” subfolder, which only holds cached zip files.
- userdata – your settings, including addon_data (per-addon settings and logins), Database (library and addon databases), sources.xml, favourites.xml, and advancedsettings.xml if you created one.
The “temp” folder is disposable. Leave it out and the backup shrinks.
Using a File Manager to Copy the .kodi Folder
One Fire OS quirk matters a lot here. Newer models on Fire OS 8 (built on Android 11), such as the 2023 Fire TV Stick 4K Max, block most third-party file managers from opening Android/data thanks to scoped storage rules. Older Fire OS 6 and 7 devices are more forgiving, and apps like X-plore can usually still get in.
Want a backup method that works on any model before you downgrade Kodi on Firestick? Use Kodi’s own File Manager. Kodi can always read its own folder:
- Plug in a USB drive through an OTG adapter (on models that support it), or set up a network share on your PC or NAS.
- Open Kodi and go to Settings > File manager.
- On the left pane, open Profile directory (that’s your userdata folder). On the right pane, open your USB drive or network share.
- Highlight a folder, open the context menu (long-press Select or use the menu button), and choose Copy.
- Repeat for the addons folder by browsing to Home folder if it’s listed, or adding special://home/ as a source.
Name the backup with the Kodi version and date, something like “kodi-21.3-backup-2026-01.” Future you will be grateful.
Protecting Saved Logins and API Keys in Your Backup
That backup isn’t harmless. The addon_data folder can hold debrid tokens, Trakt authorizations, IPTV portal credentials, and personal API keys, and advancedsettings.xml may even contain database passwords if you run a shared MySQL library.
So don’t toss that folder into a public cloud link or paste it into a forum thread while asking for help. My guide to backing up IPTV and Kodi settings without leaking logins walks through safer storage and what to strip out before sharing.
Picking the Right Older Kodi Version
Before you uninstall anything, pin down two things: exactly which version you’re returning to, and which APK variant your device needs.
Kodi Release Names and Version Numbers Explained
Every major Kodi release gets a codename. Point releases (20.5, 21.3, and so on) are bug-fix updates inside the same major version. When you downgrade, grab the newest point release of whichever major version your addons support.
| Version | Codename | Rollback Notes |
|---|---|---|
| 18.x | Leia | Last release using Python 2. Most current addons won’t run on it. |
| 19.x | Matrix | First Python 3 release. Very old for 2026 use. |
| 20.x | Nexus | The usual target for a Kodi 21 to Kodi 20 downgrade. |
| 21.x | Omega | Current stable line for most Fire TV users in 2026. |
| 22.x | Piers | The next major release. Check its status on kodi.tv before upgrading. |
See “requires Kodi 20 or newer” on an addon page? Nexus is a safe landing spot. Don’t go back further than you need to.
Read next: Kodi 21.3 Firestick Upgrade: Back Up, Update, and Roll Back Without Losing Addons
ARMv7a (32-bit) vs ARM64: Which APK Your Firestick Needs
The official mirrors offer two Android builds: armeabi-v7a (32-bit) and arm64-v8a (64-bit). Plenty of Fire TV models pair a 64-bit processor with a 32-bit operating system, and on those the 64-bit APK just won’t install.
That makes the 32-bit APK the safest default for nearly every Fire TV Stick. To confirm, check Settings > System > System info > Hardware inside your current Kodi before uninstalling it (easy to forget once it’s gone), or look up your model in Amazon’s developer documentation.
One device warning. The Fire TV Stick 4K Select, which Amazon launched in late 2025, runs Vega OS instead of Android-based Fire OS. It can’t sideload Android APKs at all, so none of this guide applies to it.
Getting Older Builds Only From the Official Kodi Mirrors
Kodi keeps every past release on its official archive at mirrors.kodi.tv/releases/android/. Open the arm folder for 32-bit builds. Older point releases often hide in an “old” subfolder.
Skip the third-party “old version APK” sites. Some repackage APKs with adware or modified code, and you can’t tell from a file name. If it didn’t come from Kodi’s own servers, keep it off a device that stores your logins.
Step-by-Step: Downgrade Kodi on Firestick
Backup saved, target version chosen. The actual rollback takes four steps. New to sideloading? My step-by-step guide to downloading Kodi on Firestick covers the Downloader setup in more detail.
Step 1: Uninstall the Current Kodi
- From the Fire TV home screen, open Settings > Applications > Manage Installed Applications.
- Scroll to Kodi and select it.
- Choose Uninstall, then confirm.
Check your backup one more time before confirming. After this step, the .kodi folder is gone for good.
Step 2: Sideload the Older APK With Downloader
- Install Downloader from the Amazon Appstore if you don’t already have it.
- Go to Settings > My Fire TV > Developer Options > Install unknown apps and turn Downloader on. If Developer Options is hidden, open Settings > My Fire TV > About and click your device name seven times.
- Open Downloader and enter the mirrors.kodi.tv address. Browse to the arm folder and select the exact APK you want, such as the latest 20.x release.
- When the download finishes, select Install. Delete the APK afterward if storage is tight, or keep it as your known-good copy.
Step 3: Launch Once Before Restoring Data
Open the freshly installed Kodi and let it reach the home screen. Accept the storage permission prompt if one pops up. That first launch builds a clean .kodi folder and fresh databases in the format this version expects.
Then close Kodi properly from the power menu. Restoring files into a folder that doesn’t exist yet, or while Kodi is still writing to it, is asking for trouble.
Step 4: Restore Your Addons and Settings Selectively
This step separates a clean rollback from a messy one. When you roll back a Kodi update on Firestick across major versions, don’t overwrite the whole userdata folder. Restore it piece by piece.
Using Kodi’s Settings > File manager, copy these from your backup into the new install:
- The individual addon folders you need (from addons), including their repository and dependency folders.
- userdata/addon_data for addon settings and saved logins.
- sources.xml, favourites.xml, and the keymaps folder, if you customized them.
- advancedsettings.xml, if you had one.
Leave userdata/Database and guisettings.xml alone for now. Restart Kodi, head to Add-ons > My add-ons, and enable anything that shows up disabled.
Database and Library Problems After Rolling Back
Even a careful rollback can leave gaps. Most trace back to one thing: database versions.
Why Your Watched History or Library May Disappear
Kodi stores your library in SQLite files with version numbers baked into their names. Nexus uses MyVideos121.db, for example, while Omega uses MyVideos131.db. Peek inside your own Database folder to see exactly what’s there.
Newer Kodi migrates old databases forward. Older Kodi can’t read newer formats, though, so if you copy Omega’s database into Nexus, Nexus hunts for its own file number, ignores the newer one, and shows you an empty library.
Rebuilding the Library vs Restoring Old Database Files
Still have database files from before the upgrade? Kodi often leaves the older-numbered file in place after migrating, so copy that matching file into the new Database folder and your library and watched status come back exactly as they stood on upgrade day.
No matching file? Rescan your sources to rebuild the library. Any watched history from the newer version is effectively lost, unless you sync it through Trakt or an addon that stores history on its own.
Addons That Refuse to Load Because of Python or Dependency Versions
Sometimes the rollback goes fine and an addon still won’t install. Usual cause: the repo already pushed an addon version that needs components only the newer Kodi provides. Kodi throws a dependency error and stops.
Two fixes. Install an older addon version (open the addon’s info page, select Versions, and pick an earlier one if the repo keeps them), or wait for the developer to restore compatibility.
Stop the Same Problem From Happening Again
Once you’ve managed to downgrade Kodi on Firestick, set things up so one update can’t knock everything over again.
Set Addon Updates to Notify Instead of Install
- Go to Settings > System. If you don’t see the Add-ons tab, click the gear at the bottom left until the level reads Advanced or Expert.
- Open Add-ons > Updates.
- Choose Notify, but don’t install updates.
Want finer control? Open an individual addon’s info screen and switch off its Auto-update toggle. That pins a working version while the rest of your setup keeps updating normally.
Hold Off on Major Kodi Releases Until Your Addons Catch Up
Here’s the upside: a sideloaded Kodi on Fire TV never updates itself. Every new install is your call, so there’s zero reason to jump on day one.
My own rule is to wait until the first or second point release (like 21.1 or 21.2) and confirm my key addons list support. When you’re ready, my Kodi 21.3 Firestick upgrade guide covers the forward path with a rollback plan built in.
Keep a Known-Good APK and Backup on Hand
Store two things on a USB drive or network share: the APK of the version that works, and a dated .kodi backup made on that same version. With that pair, any future rollback becomes roughly a 10-minute job.
The habit carries over to other apps too. If you also run Stremio, see my guide on updating Stremio and rolling back for its equivalent routine.
Security Trade-Offs of Running an Older Kodi
Rolling back fixes a compatibility problem. It isn’t free.
What You Give Up With Older Releases
Each Kodi point release fixes bugs, and some of those fixes close security holes. Older versions also miss newer codec support and Android compatibility improvements, and the further back you go, the wider that gap gets.
Once a major version stops getting point releases, its problems stay unpatched. Plan to move forward as soon as your addons support the newer release.
Pairing an Older Kodi With Safer Addon Habits
Most Kodi risk lives in third-party repos. Install addons only from sources you’ve checked, look at what permissions and services they request, and remove anything abandoned. My Zap Kodi addon safety check shows the kind of vetting process you can apply to any addon.
Plenty of readers also run Kodi behind a VPN for privacy on public or shared networks. Worried about buffering? My piece on whether a VPN slows down Kodi explains which protocols and servers matter on Fire TV hardware.
Final Thoughts on Rolling Back Kodi
To downgrade Kodi on Firestick safely, stick to the order: back up, uninstall, sideload an official older APK, launch once, then restore selectively. Skip the ADB shortcut. Avoid unofficial APK sites. Leave mismatched database files out of the restore.
Then fix the root cause. Switch addon updates to notify-only, keep a known-good APK and backup around, and move forward again once your addons are ready.
⚖️ Legal Disclaimer: IPTV Wire does not own or operate any streaming service, application, or website mentioned in this article. We do not verify whether third-party services carry proper licensing. Users are responsible for ensuring they comply with copyright laws in their jurisdiction.
Frequently Asked Questions
Can I downgrade Kodi on Firestick without losing my addons?
Yes, but only with a backup. Uninstalling Kodi deletes its data folder, so copy your addons and userdata folders first. After installing the older version, restore individual addon folders and addon_data, not the whole userdata folder.
Why does my Firestick say “App not installed” when I install an older Kodi version?
Android blocks installing an APK with a lower version code over a newer one. Uninstall the current Kodi through Settings > Applications > Manage Installed Applications, then install the older APK. A wrong architecture (64-bit on a 32-bit system) triggers the same error.
Where do I download older versions of Kodi safely?
Use the official archive at mirrors.kodi.tv/releases/android/. Every past release lives there, often in an “old” subfolder. Avoid third-party APK sites, which can host modified or bundled files.
Should I use the 32-bit or 64-bit Kodi APK on a Fire TV Stick?
Go with the 32-bit armeabi-v7a APK unless you’ve confirmed your device runs a 64-bit OS. Many Fire TV models pair a 64-bit chip with a 32-bit operating system, which makes the 32-bit build the safe default.
Will downgrading Kodi delete my watched history?
It can. Older Kodi can’t read newer database files, so your library may show up empty. Restoring a matching older database file brings back history up to the upgrade date. Otherwise, rescan your library or lean on Trakt sync.
How do I stop Kodi addons from updating automatically?
Go to Settings > System > Add-ons > Updates and choose “Notify, but don’t install updates.” Set the settings level to Advanced if the option is hidden. You can also turn off auto-update per addon from its info screen.





Comments
Leave a comment
Your email address will not be published. Comments are moderated before they appear.