GBA handhelds for Pokémon games and ROM hacks

Choose the GBA workflow you want to maintain

Start with the exact Pokémon game and a task you want to complete. The same patched GBA output can be part of different software setups, but the library, controls and progress files still need their own configuration.

Already own a device? Establish a working baseline there before comparing replacements. For a new purchase, name the unmet task—readable move names, comfortable shoulder controls or another platform—rather than assuming a larger specification list solves it.

A first-session check before a long Pokémon adventure

This is a suggested check, not a measured device result. Keep the exact patched game, software version and core recorded so you can investigate a problem without changing everything together.

1. Input: verify movement, confirm, cancel, shoulder controls, Start and Select in the game you actually want to play.
2. Readability: inspect dialogue, longer move names, HP and compact menu numbers. For Onion, use the scaling guide to compare image options.
3. Progress: save in-game at a recognizable location, close normally and reopen through Continue.
4. Pause or shutdown: test the device's own documented behavior separately from saving. Do not infer save success from a resumed picture.
5. Backup: locate the cartridge-save file your selected software created and preserve a copy outside the working game folder.

Before updating KNULLI, follow the update and backup guide. If changing KNULLI storage, use the second-card guide before relying on the destination library.

Controls, time, trading and save transfers

Steam Deck standalone mGBA: fast-forward and controller profiles

• Miyoo Mini Plus Pokémon fast-forward: Onion controls and checks
• Miyoo Mini Plus Pokémon clock: RTC, WiFi and daily-event checks
• Pokémon GBA trading on Steam Deck: local mGBA setup
• Import a Pokémon GBA save on Retroid Pocket 5

Each guide names its software path and separates documented instructions from untested game behavior.

Which GBA handheld setup fits you?

Miyoo Mini Plus with Onion

Onion 4.3 documents mGBA as its default GBA core. Prepare the matching Mini Plus firmware and SD card, enable GBA and copy the patched .gba file into Roms/GBA.

Heart & Soul on Miyoo Mini Plus: installation and saves

Anbernic RG35XX Plus with KNULLI

A different SD-card and game-library workflow. The RG35XX Plus guide covers model matching, KNULLI installation, per-game emulator settings and save checks.

Anbernic RG35XX SP with KNULLI

Prefer a hinged design? The RG35XX SP guide adds lid-close settings and save checks to the SD-card workflow. Closing the shell is not proof that progress is saved.

TrimUI Brick with KNULLI

The original Brick guide covers a compact vertical alternative, text and shoulder-button checks, and the configurable toggle switch.

Retroid Pocket 5 with Android

Use Android emulator instructions rather than Onion or SteamOS folders. The Pocket 5 overview connects RetroArch/mGBA setup, save locations and matching Pokémon profiles.

Steam Deck with EmuDeck

EmuDeck documents standalone mGBA on SteamOS, with games in Emulation/roms/gba and in-game saves in Emulation/saves/mgba/saves. These paths are relative to your EmuDeck installation.

Compare Miyoo Mini Plus and Steam Deck for GBA setup

From patch to playable game

1. Open the game profile and match its required base game, region and revision.
2. Use the creator's patch instructions. IPS, UPS and BPS are patch formats; the resulting GBA game is the file you open in the emulator.
3. Map A, B, L, R, Start and Select. Check text readability and D-pad use.
4. Save in-game, close normally and reopen through Continue. Back up that save before changing game version or emulator.

For Gaia, a working input and a missed evolution are different results. Use the game-specific evolution diagnosis before changing the runtime. Record the species, action and location alongside the device setup; an original FireRed trade guide does not establish Gaia’s changed method.

Fast-forward and clock-dependent events need checks with the exact hack and emulator. A platform label does not establish their behavior.

Complete GBA emulator and save guide · Check your base file · Patch locally

Emerald Rogue: a mid-run stop needs the game’s own check

For a run-based game, establish the game-managed stopping point before testing handheld shutdown. Pokabbie’s documented Emerald Rogue workflow uses a REST option; an automatically loaded emulator state can obscure whether you completed that action.

Use the Rogue REST procedure and source boundary first. Then test the installed emulator’s normal exit and reopen route with the same edition and build. Record the game action and the resumed location separately. If your installed menu differs, return to that build’s creator instructions before making a long adventure depend on a guessed save method.

Example: confirm/cancel and text readability work, yet you have only tested sleep with the current scene still open. Controls passed; durable game progress is still untested. Choose a suitable checkpoint, finish the documented game action and verify the normal reopen path. This is a proposed test, not a measured hardware result or cross-edition migration procedure.

If the character is back at the hub, compare the game’s completion/wipe loop before classifying it as lost progress. A game-specific return and a missing save require different evidence.

GBA Pokémon ROM hacks to explore

• Pokémon Unbound — Pokémon FireRed (English v1.0). Check the profile's patch and save requirements.
• Pokémon Heart & Soul — Pokémon Emerald Version (U). Check the profile's patch and save requirements.
• Pokémon Inclement Emerald. Check the profile's patch and save requirements.

These are catalog examples, not a tested compatibility list. Heart & Soul is a GBA demake; its Johto setting does not make it a DS game.

Looking for Nintendo DS instead?

Handhelds for Nintendo DS Pokémon · All Pokémon handheld paths

Find the first failed stage of your GBA setup

1. Preparing the game: if the patcher rejects the input, investigate the creator's required base and revision. Use patch diagnosis before changing the handheld.
2. Finding the game: if the output does not appear, inspect the active library and file. Follow Onion or KNULLI's discovery guide.
3. Launching: if the listed game fails to open, preserve the output and confirm emulator/core and creator requirements.
4. Operating: if it opens but inputs or text are awkward, compare the relevant remap or scaling options while keeping the game unchanged.
5. Continuing: if progress is missing, identify the cartridge save independently of an automatically restored state.

Example: a new file appears in Onion after refreshing, but opens without your old team. Library discovery is now working. Move to save diagnosis rather than repeatedly refreshing or rebuilding the same game.

Record game release, emulator/core, firmware, launch route and the first failing stage. One change at a time gives you a useful comparison; changing the game, core and card together removes that evidence.

Keep a handheld session record

A short record helps you compare one change with the previous attempt. For GBA, record what Continue actually shows and the game build you selected, rather than assuming a successful import. Leave anything you have not checked blank: the export marks it as “Not recorded”.

GBA handheld session notes

User-entered observations; not a compatibility verdict or verified diagnosis.



Device and operating system:
Not recorded

Game and build / edition:
Not recorded

Emulator and core / version:
Not recorded

Launch route:
Not recorded

Task and expected observation:
Not recorded

One change tried:
Not recorded

Observed result:
Not recorded

Next question or action:
Not recorded

Sources and scope

• Onion installation and model requirements
• Onion GBA cores
• Onion SD-card setup
• EmuDeck mGBA on SteamOS

Software documentation checked 4 Oct 2026. Game profiles retain their own source dates. Use legally obtained files; Pocket Deal Radar provides no ROMs, BIOS files or prepatched games.