Miyoo Mini Plus Wi-Fi file transfer: games and Pokémon saves

Choose the transfer method for the device you have

These network services are documented for the Wi-Fi-equipped Miyoo Mini Plus with Onion 4.3. This is not an instruction for a non-Plus Mini or unidentified seller firmware. Start with the browser route for one prepared game; choose a client when you already use it for file management.

The handheld and sending device must be able to reach each other on your local network. Turning on a file service is a separate action from connecting Wi-Fi. A phone using mobile data or an isolated guest network may not reach the handheld’s local address.

Transfer from a phone or computer through the browser

In Onion, open Apps → Tweaks → Network → HTTP: Web-based file sync. Enable the service and authentication, then exit Tweaks. Read the handheld’s current IP at the top of its Network page and enter that address in the sending device’s browser.

The documented initial web login is admin / admin. The HTTP browser has user management; change that default password at the first login. Keep this transfer on your own trusted local network, and disable the service when the session is complete.

1. Identify the prepared file in your phone’s or computer’s file manager.
2. Open the intended destination directory in the handheld’s web file browser.
3. Use its upload action and select that exact file.
4. Wait for completion, then inspect the destination name and size.
5. Return to Onion and perform the separate library or Continue check for that file category.

Example: your phone has the creator’s patch and the output you generated from your own base. Select the completed output from the Files app, not whichever download appears first. The next section gives a concrete GBA destination.

Put the playable GBA output in the game directory

For a GBA game, Onion documents the GBA ROM folder. On the card, use Roms/GBA. Supported extensions include .gba, .bin, .zip and .7z; a plain prepared .gba makes the first transfer easier to inspect.

The example filename is fictional. A transport success does not prove that the creator’s required base or patch output is correct. Use the patching workflow for that preparation and Heart & Soul’s documented Onion setup when playing that particular adventure.

Do not rename a patch to a game extension. Its contents would remain a patch, regardless of where the upload puts it.

Refresh the library after the remote upload

From the game list, press Y for Game List Options and choose Refresh roms for its cache. The Games-tab SELECT → Refresh all roms route is also documented. Use one refresh, then reopen the GBA list.

1. Confirm the uploaded file exists inside the intended directory.
2. Refresh and check whether that exact new entry appears.
3. If absent, use the remote-upload discovery checks.
4. If present but it fails to launch, investigate game output and selected core.
5. If it opens without the intended progress, move to the save-import task.

Example: the browser reports an upload finished, but you are looking at a keyword-filtered list. The missing entry does not yet show that the file was damaged. Check the list view and actual folder before uploading another copy under a different name.

Download or upload an ordinary save as a separate task

First save in-game, wait for completion and close the game normally before copying its progress. The Onion FAQ places ordinary saves under Saves/CurrentProfile/saves/[CORENAME] and states under Saves/CurrentProfile/states/[CORENAME]. Identify the active profile, core and actual game basename.

1. Keep an independent copy of any existing destination progress.
2. For a download, select the ordinary save that belongs to the checkpoint you recorded.
3. For an import, confirm the source/destination game and runtime compatibility first.
4. Upload only a working copy into the identified save directory, with the destination’s expected name.
5. Launch without relying on the old state and inspect trainer, party and location through Continue.

A network transfer does not convert a state or make two game builds save-compatible. Use the wireless-save check for the next verification, and the local save-copy comparison if you need to compare two downloaded individual copies before launch.

Example: the file you downloaded is an emulator state screenshot or a state slot, while you wanted the trainer’s ordinary progress. Return to the saved-game directory and identify the file category; changing its extension would not repair that selection.

Use an SFTP client when you want encrypted file transfer

Onion enables this through Apps → Tweaks → Network → SSH: Secure shell. Enable authentication. The documented initial client credentials are onion / onion, using the device IP shown in Network. Select the SFTP protocol in a compatible client, rather than plain FTP.

Browse to the actual card directory exposed by your connection and inspect a familiar folder before sending anything. Client interfaces differ, so this guide does not invent one universal upload button or remote starting directory. Transfer the selected game or save as its own task and use the same destination checks above.

If a connection fails, compare the protocol with the service you enabled. An FTP service and an SSH/SFTP service are different endpoints; repeatedly changing the filename cannot solve that mismatch. Turn the service off after completing the transfer rather than leaving it running on an open network.

If using FTP, select binary transfer for game and save files

The Onion FTP route is Apps → Tweaks → Network → FTP: File server; exit Tweaks to apply it. Its documented credentials are onion / onion. With authentication enabled, an anonymous login fails.

The maker specifically warns that some FTP clients damage binary files unless transfer type is set correctly. In FileZilla, the named route is Transfer → Transfer type → Binary. Verify that setting before sending a game or save.

1. Retain the original file outside the handheld.
2. Choose binary transfer in the client.
3. Send a fresh working copy to the intended directory.
4. Compare name and size; for an ordinary save, optionally download it again and compare the copies locally.
5. Check game launch or Continue separately.

The size comparison is a quick check, not proof of identical contents. If the source works but only the transferred copy fails, investigate the transport before repatching. Use the transferred-output branch to keep discovery and launch symptoms separate.

Plain FTP traffic is unencrypted. The maker recommends turning it off away from a trusted network; choose the SFTP route when you need encrypted transport.

Use an existing Samba share from Windows

Enable Apps → Tweaks → Network → Samba: Network file share. In Windows, enter the current device IP prefixed by two backslashes to open its available shares. The documented login is onion / onion.

Choose a share exposing the folder you actually need. Onion’s share submenu can toggle individual shares; a missing underlying folder produces an error. The full-card __sdcard share is deliberately disabled by default. You do not need to expose the whole card merely to inspect a missing narrower share.

Example: you can open one share but the game directory is absent. That establishes reachability, not permission or configuration for every folder. Inspect the enabled share and existing destination rather than diagnosing all Wi-Fi as broken. For this task, the browser transfer route can be simpler than editing share definitions.

Choose the branch that matches the transfer failure

Record one attempt: service, current device IP, sending device, selected source, remote destination, completion result and the first failed game/library/save check. That gives the next attempt a clear comparison. Do not change the patch, core, game name and service together.

Finish with the task verified and the original retained

For a new game, the finish is a visible entry that opens through the intended core. For a progress import, it is the recognizable adventure through Continue and a later in-game save that persists. For a backup, it is the independently stored selected file you can locate again.

A selected-file download is not a complete pre-update card backup. Use the update backup inventory when the next task is an Onion upgrade. Keep the original game/save until the relevant follow-up check is complete, then turn off the transfer service.

This guide does not provide ROMs, BIOS files or prepatched games. It describes moving your own prepared files, not a download source or a compatibility test.

Sources and software scope

• Onion HTTP file server
• Onion FTP and binary-transfer note
• Onion SSH/SFTP
• Onion Samba shares
• Onion GBA folder and extensions
• Onion Game List Options
• Onion FAQ: filenames, library and saves

Onion 4.3 documentation checked 8 Oct 2026. Service controls and reference credentials are documentation defaults; use your actual installed settings if changed. Examples and diagnostic order are editorial guidance. No transfer speed, physical-unit test, complete backup or recovered progress is claimed.

Continue with your setup

Miyoo Mini Plus with Onion: full overview · All Pokémon handheld paths