This section concerns Nintendo's dedicated Classic Mini and Classic Edition systems. It does not describe an original cartridge-based NES or the later small SNES hardware revision. Read the label and identify NES, Famicom, Super NES or Super Famicom before selecting a package, controller arrangement or recovery procedure.
Record the starting hardware
Photograph the model label, power connector, HDMI output and controllers. Use Nintendo's regional hardware manual to establish a working stock setup. Different cosmetic designs and bundles do not automatically use identical controllers or replacement parts. A similarly shaped unlicensed clone is not established as a supported hakchi target.
Test the existing menu, one built-in game, sound and a suspend-point reload. Record any pre-existing modification and retain files supplied by the previous owner. Knowing whether the console already has a modified kernel helps avoid applying an incompatible installation sequence.
Use the actual hakchi project
Team Shinkansen's hakchi2 CE repository and documentation are the primary source for that branch. Older hakchi and hakchi2 tutorials can describe a different workflow. Preserve the tool version, complete distribution and instructions used rather than combining old screenshots with a new executable.
The project documents installation through a suitable micro-USB data connection for its supported Nintendo mini targets. Ordinary charging success does not prove a cable supports data. Confirm the selected console type and follow the tool's exact prompts for the connected model.
Prepare before synchronization
- Identify the actual console and establish stock power and display behavior.
- Record existing modifications and preserve available original backups.
- Install the documented tool and appropriate connection requirements.
- Retain its original backup outputs before any kernel change.
- Start with a small supported test library and conservative menu layout.
- Verify launch, controls and saved progress before expanding the collection.
Do not interpret a synchronization confirmation as proof that every imported game runs correctly. The stock emulators were designed around the built-in selection and have title-specific limitations. A third-party core may solve a particular compatibility issue, but needs its own version and configuration record.
Compatibility and storage limits
For NES software, cartridge mapper support matters. For SNES software, special hardware and emulator behavior can matter. Check a game's actual requirements rather than relying only on its extension. The project documentation distinguishes additional emulator modules from the stock setup.
Keep enough working space for saves and system functions. An external-storage arrangement needs the kernel and accessory support documented for that project; a USB drive plugged into an arbitrary connector is not a general stock expansion feature.
Preserve a reviewable result
Record each imported game's source, identifier, region and selected emulator. Keep tool settings, modules and ordinary saves with the library backup. Avoid downloading another console's unknown kernel as a substitute for a missing original backup.
Continue with library and save preservation before major synchronization, and recovery and accessories for connection faults. A useful guide names the precise mini model and tool branch instead of presenting all Nintendo retro hardware as one target.
Sources and review
Reviewed October 11, 2026. The linked manufacturer and project documentation establishes supported behavior. The diagnosis checklists and preservation suggestions are original editorial guidance. Menus, services and project support can change; verify the linked instructions before an irreversible change.