Dolphin Wii NAND: Importing, Isolating, and Verifying System State
Import a lawfully dumped Wii or vWii NAND into Dolphin without confusing console system data with disc images, standalone saves, or the emulator's working profile.
A Wii NAND dump is a snapshot of the console’s internal flash-backed system storage, not another name for a game image or a single save file. It can include the Wii Menu, channels, saved data, configuration, and device-specific system state. Some Wii titles and system features depend on files present only in a full NAND dump, which is why Dolphin documents a dedicated import path instead of treating NAND as part of the game disc.
This workflow is for a console owner using a dump they are authorized to create and use. The dump can contain personal saves, console identity material, and other sensitive data. Keep the original private, do not upload it to a public issue tracker, and follow the applicable law and the emulator project’s documentation. Dolphin’s guide describes using BootMii on a homebrewed Wii or a vWii backup method on Wii U; hardware and software support differ, so do not assume a vWii image is identical to a retail Wii image in every operational detail.
Keep the three storage layers separate
| Data | What it represents | Typical handling |
|---|---|---|
| Game disc image | The contents read from a game disc | Preserve and verify as a separate source artifact |
| Individual save or channel export | One selected piece of user content | Transfer through the game’s or Dolphin’s supported save workflow |
| Full Wii NAND | System menu, channels, saves, configuration, and device-specific state | Import as an emulated console’s system storage |
Copying only a save file is appropriate when the goal is to continue one title and no other system files are needed. Importing a full NAND is broader: it can add channels and system configuration, but it also brings more personal data and makes recovery more consequential. Do not replace a working Dolphin profile with a full dump merely to resolve one game’s missing-save message.
Preserve the source before importing
Keep the original backup as an immutable acquisition. Store it in a protected location, record its file size and SHA-256 digest, and make a second verified copy before starting an import. The hash protects against accidental alteration in storage or transfer; it does not prove that the console dump itself was complete or authentic. Record the console model (Wii or vWii), the dump method, date, and the Dolphin version used for the import.
Use a separate Dolphin user-data directory or otherwise make a complete backup of the current emulator profile before importing. The user directory contains more than the NAND: it may also hold configuration, controller profiles, save data, logs, and other state. Isolating the import lets you compare a clean baseline with the imported system and provides a rollback path if the dump is incomplete or the imported configuration causes a title to behave differently.
Use Dolphin’s supported import operation
Dolphin’s NAND guide documents automatic import of a BootMii NAND backup through Tools → Import BootMii NAND Backup. The guide says this option is available in Dolphin 5.0-3416 and newer. Dolphin decrypts and unpacks the backup into its emulated NAND and extracts device credentials and system files used by some network-service emulation paths. Do not use the age-specific manual extraction instructions from an old guide as a substitute for checking the current build; the supported GUI operation is easier to audit and avoids hand-editing a live user directory.
The source backup should remain untouched while Dolphin imports its own working copy. If the menu item is unavailable, first verify the Dolphin build and read the current project guide. Do not improvise by copying partially extracted files over the active Wii directory: a mixed set of NAND files can be harder to diagnose than a clean import, and manual procedures may have version-specific requirements.
Verify the result as system state, not just a successful dialog
After import, restart Dolphin and inspect the intended user profile. Confirm that the Wii Menu or the system path required by the test can start, that the expected channel or save is present, and that the original game image still has its independent identity and hash. If the problem concerned one title, launch that title and test the exact save operation that failed; a visible menu alone is only a smoke test.
Keep a short test record containing:
- Dolphin version and operating system;
- source dump type (Wii or vWii), acquisition date, and source hash;
- user-data directory used for the import;
- the feature or game that required system files;
- whether the Wii Menu, channel, save, or service-dependent flow was checked;
- any missing files, warnings, or compatibility limitations.
Do not assume that successful NAND import enables every online feature or makes a service available. Network endpoints, account state, server retirement, region, and the legality of a particular service or data transfer are separate matters. Use the current Dolphin network documentation for any online test and do not share device credentials in logs or support requests.
Recovery and cleanup boundaries
If a test profile fails, close Dolphin before restoring that profile’s backup. Keep the failed directory separately for diagnosis rather than merging selected files back into the source NAND. Then repeat the import into a new empty profile and compare the result. This distinguishes a malformed dump from stale state left by a previous Dolphin experiment.
For a single corrupted GameCube or Wii save, prefer the emulator’s save manager or a console-owner transfer workflow described by Dolphin rather than importing an entire NAND. For a Wii channel, determine whether the goal requires a channel package or a full system environment; those are different data sets with different dependencies. For a disc-preservation task, use Dolphin’s disc-dumping and verification guidance, not the NAND workflow.
The most recoverable setup preserves the original dump, uses an isolated emulator profile, records the exact import version, and validates only the system feature the test needs. A NAND import is useful when a Wii title depends on system state; it is not a universal compatibility patch and should not become the only copy of a user’s console data.
Related:
- Recovering Emulator Save Data After an Interrupted or Incompatible Write
- Dolphin Introduces RVZ as a Lossless, Emulation-Ready Disc Format
Sources: