Back Up Saves and Settings Before Updating Odin 3, Thor, or Odin 2

Protect progress before updating

Before installing firmware on your Odin 3, Thor, or Odin 2, make a separate copy of your saves and essential settings. A routine system update may preserve user data, but a failed update, recovery procedure, or clean installation can put it at risk. Read the instructions for your exact device and update method; do not assume every installation is non-destructive.

The goal is not to duplicate your entire game library. It is to protect the small, difficult-to-replace files that hold your progress and configuration.

AYNTime Community is an independent resource, not affiliated with AYN. Menu names, storage access, and backup options can vary by firmware and app version — check your own device.

Know what needs backing up

Start with the games and apps you actually use. Your backup checklist should include:

• In-game saves: progress written through a game's own save system.
• Emulated memory cards: some emulators store multiple games' saves together in card files.
• Save states: useful extras, but not a substitute for normal saves. Compatibility can change with emulator or core updates.
• Emulator settings: controller mappings, graphics settings, per-game profiles, and custom layouts.
• Frontend settings: library paths, collections, favorites, and interface preferences.
• Android game progress: local saves, account connections, and cloud-sync status where supported.
• Device preferences: performance modes, fan settings, display options, and button assignments worth recording.

For Thor, also record any custom second-screen arrangement or emulator layout you would want to recreate.

Finish saving and close your apps

Load each important game and make a normal in-game save where possible. Exit emulation cleanly so the app can finish writing its files. Avoid copying a memory card or save folder while a game is running.

If you use cloud sync, let it finish first and check its reported status. Then close the relevant apps before copying their data.

Cloud sync is not the same as a separate backup. A sync service may propagate a deletion or overwrite a good file. Keep a dated copy outside the synced folder as well.

Find the real save locations

Do not assume saves live beside your game files or on the microSD card. An emulator may read games from removable storage while keeping progress in internal storage.

Open each emulator's settings and look for options such as save directory, memory card, user data, or export backup. Prefer the app's own export feature when available, and check what it includes: a settings export might exclude saves, while a save export might exclude configuration.

For RetroArch, inspect its configured save and save-state directories. If you customized your setup, also preserve relevant configuration files, overrides, controller remaps, and shader presets. Custom assets referenced by those settings may need separate copies.

Android restricts access to some app-private folders, including parts of `Android/data`. A file manager or USB connection may not expose everything. If you cannot access a location, use the app's supported export method rather than assuming an empty folder means there is nothing to save.

Some Android games offer no user-accessible local backup. Confirm the correct account is connected and consult the game's own backup or recovery options. Do not assume Android's general backup feature covers every app.

Make an off-device copy

Create a clearly labeled folder, such as `Odin2-before-update-YYYY-MM-DD`, and organize it by app:

• `saves`
• `save-states`
• `emulator-settings`
• `frontend-settings`
• `screenshots-and-notes`

Copy exported archives and accessible save folders to a computer, external drive, or trusted cloud-storage location. If using USB, select file-transfer mode when prompted and verify that the destination contains the actual files, not just empty folders.

A microSD copy can be useful, but keep at least one copy off the handheld. Do not rely on a card remaining untouched during recovery or a clean installation.

Capture screenshots of settings without an export option. Note emulator versions, RetroArch core names, custom GPU driver selections where applicable, and important storage paths. Copy those screenshots off-device too.

Verify before installing firmware

Spend a few minutes checking the backup:

1. Confirm that every important emulator or game has an entry.
2. Check file sizes and modification times for anything unexpectedly empty or old.
3. Open exported archives with a suitable archive tool, if their format supports it.
4. Read the app's restore instructions so you know how the export will be imported.
5. If possible, test restoration in a separate, disposable setup without overwriting your working saves.

Avoid uninstalling apps or clearing app storage as a backup test. Those actions can erase the data you are trying to protect.

Check progress after the update

After updating, verify storage access and open a few important games. If your saves and settings are intact, there is no need to restore over them.

If restoration is necessary, close the app first and follow its import procedure. Preserve any newer progress before replacing files. Be especially careful with memory-card files containing several games and with cloud-sync prompts that might overwrite the restored copy.

Keep the backup until you have confirmed normal saves load and your controls, layouts, and library paths work correctly.

Got a better tip? Share your device-specific backup steps or corrections with the AYNTime Community.