Fix missing RetroArch core info files on Android
Confirm the core binary is installed first, then run Online Updater → Update Core Info Files and restart RetroArch. Core info files describe the core; they do not install the core, repair a damaged binary, supply BIOS files, or add games to a playlist. Validate those layers separately before reinstalling anything.
Do this in order
- 01
Record the RetroArch package channel and version, Android architecture, selected core name, and the exact missing or generic label shown in the menu.
- 02
Back up the active configuration and confirm the core binary appears under Load Core; a missing binary is not a core-info problem.
- 03
Open Online Updater and run Update Core Info Files, then wait for completion without starting a second updater task.
- 04
Restart RetroArch so menus, playlists, supported extensions, and firmware status are rebuilt from the updated metadata.
- 05
Load the core without content where supported and inspect Information → Core Information before scanning any authorized files.
- 06
Update Databases only if playlist recognition is also wrong, then test one lawful file and retain the original configuration until the result survives a cold restart.
Decision and diagnostic table
| Symptom | Layer implicated | Next check |
|---|---|---|
| Core shows a generic or incomplete name | Core info metadata | Update Core Info Files and restart |
| Core is absent from Load Core | Core binary or package policy | Check install channel, architecture, and Core Downloader availability |
| Firmware status is missing or stale | Metadata plus System/BIOS directory | Refresh info, then verify the named file and hash |
| Core exists but a game is absent from playlists | Database or playlist identity | Update Databases and audit the scan separately |
Metadata is not the executable
A core info file tells RetroArch a core's display name, supported content extensions, firmware expectations, database associations, and selected capabilities. The loadable library is a different file with an architecture and package boundary of its own.
If the binary is not listed, updating metadata cannot create it. First identify whether the Android package permits core downloads and whether the installed binary matches the device architecture.
Restart before judging the update
Libretro's playlist guidance explicitly pairs updated core info and databases with a RetroArch restart. Testing before the restart can leave a menu or scan using the previous in-memory description.
After restarting, inspect Core Information with no large library scan running. That small test reveals whether the metadata is readable before database matching and storage access add more variables.
Firmware and playlists remain separate
A refreshed info file may name required firmware and hashes, but it does not provide copyrighted firmware. Check your lawful file in the configured System/BIOS directory and preserve its source record.
Likewise, a core's supported extension does not prove a playlist database match. A strict scan uses its own database identity, while a manual playlist can name content that the core still cannot load.
Core metadata and firmware hashes are technical identifiers, not download permissions. Do not use a missing firmware name or hash to search for unauthorized BIOS, ROM, CHD, artwork, or music.