Fix missing RetroArch menu icons and assets on Android
Identify the active menu driver first. RGUI intentionally uses text and ASCII instead of icons. For Ozone, XMB, or GLUI, back up the configuration, run Online Updater → Update Assets, restart RetroArch, and verify the configured assets directory. If the updater is unavailable or cannot write, repair the official app package or directory permission rather than downloading a random theme archive.
Do this in order
- 01
Record the RetroArch distribution, version, active menu driver, assets directory, and whether text is readable even when icons or backgrounds are absent.
- 02
If the driver is RGUI, stop treating missing icons as a fault; RGUI intentionally uses text and ASCII characters.
- 03
For Ozone, XMB, or GLUI, back up `retroarch.cfg`, open Online Updater, and run Update Assets from a trusted network.
- 04
Wait for extraction to finish, close content safely, restart RetroArch, and check the same menu before changing the driver or theme.
- 05
If nothing changes, inspect Settings → Directory → Assets and confirm the path is readable and writable by this app installation.
- 06
If the updater is hidden, blocked, or the package is incomplete, repair or reinstall from the same official distribution and restore only the reviewed configuration.
Decision and diagnostic table
| Symptom | Most likely boundary | Next check |
|---|---|---|
| RGUI shows text but no icons | Expected RGUI design | No repair needed |
| Ozone/XMB text appears; icons are blank | Missing or wrong assets directory | Update Assets, restart, verify path |
| Assets download finishes but extraction fails | Write permission or free-space problem | Check directory and storage before retrying |
| Only custom theme elements are missing | Theme path or theme package mismatch | Return to the default theme first |
Menu driver decides what should exist
Libretro documents four principal RetroArch menu drivers. Ozone, XMB, and GLUI use graphical resources differently, while RGUI is deliberately lightweight and does not support icons.
Changing drivers before recording the current one can turn a missing-assets problem into a second navigation problem. Capture the driver and restart requirement first.
Update Assets is narrower than reinstalling
The official Online Updater exposes Update Assets separately from core info, databases, overlays, shaders, and thumbnails. Updating the assets package repairs menu resources without changing game files or selecting another core.
Restart after the update because the menu may keep loaded resources in memory. A successful network message is not proof that extraction reached the configured assets directory.
Path and distribution ownership matter on Android
Android packages can use different writable locations and may expose different updater entries. Reusing a configuration from another distribution can leave the assets path pointing at a directory the current app cannot access.
Prefer the same official distribution's repair or reinstall path when its bundled resources are incomplete. Random asset or theme archives add provenance and compatibility uncertainty without fixing a wrong directory.
Menu assets are separate from game artwork. Do not use an asset repair as a reason to download unauthorized box art, cabinet art, logos, ROMs, BIOS files, CHDs, music, or proprietary theme packs.