Restore RetroArch storage access after an Android reinstall
Treat a reinstall as a new app instance: first confirm which files still exist outside app-specific storage, then reselect the authorized shared folder through the distribution's file browser or Android system picker and reapply RetroArch's Directory settings. A copied `retroarch.cfg` can name a location, but it cannot by itself recreate Android access to that location.
Do this in order
- 01
Record the old and new RetroArch package identifiers and versions before copying any configuration.
- 02
Use Android's Files interface to confirm which authorized content, saves, and backups still exist in shared or user-selected storage.
- 03
Assume files in the removed app's internal or app-specific external directories were deleted unless an independent backup proves otherwise.
- 04
Open RetroArch's Directory settings and reselect the surviving folder through the access method exposed by that distribution.
- 05
Test one authorized item directly, then verify save and state directories separately before rebuilding a playlist.
- 06
Save the current configuration, quit through the menu, cold-start, and confirm that the same directory remains readable.
Decision and diagnostic table
| Observed state | Likely boundary | Safe next action |
|---|---|---|
| Shared files visible in Files, absent in RetroArch | App access or configured directory | Reselect folder and save config |
| Old app-private folder gone | Uninstall cleanup | Restore only from an independent backup |
| Playlist remains but launch fails | Stale content reference | Direct-load, then rebuild entry |
| Folder works until relaunch | Configuration or grant not retained | Record package, picker flow, and save result |
A path string is not an Android permission
RetroArch can restore a textual directory setting while Android still refuses the newly installed package access. Prove the folder through the current app's supported picker instead of editing the path repeatedly.
Uninstall changes the recovery question
Android documents that app-specific files are removed when an app is uninstalled. Shared documents can survive, but survival and access are separate facts; inspect both before calling data lost.
Direct loading is the control experiment
A playlist can retain an old reference after the file moves or the package loses access. Direct-loading one authorized item distinguishes storage access from playlist metadata before a bulk rescan.
Restore only content and backups you are entitled to possess. A surviving filename, playlist, or storage grant does not authorize a ROM, BIOS, CHD, artwork, or music file.