If you have a NAND backup:
: While the Amiibo character data itself is "fixed" (read-only), the "unfixed" section contains information that changes, such as in-game save data, levels, or stats.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. unfixed-info.bin
: When writing to a blank NTAG215 tag, the app uses this key to re-encrypt the data so a Nintendo console will recognize it as an official product. How to Use unfixed-info.bin
In the ecosystem of Amiibo homebrew tools, there are typically three core key files that work together in a specific hierarchy. If you have a NAND backup: : While
: You must have both unfixed-info.bin and locked-secret.bin (sometimes combined as key_retail.bin ) to decrypt/encrypt the data.
The files are named exactly unfixed-info.bin and locked-secret.bin (all lowercase, matching extensions). If you share with third parties, their policies apply
For most Amiibo writing applications to function, these keys must be "imported" into the software. Common tools that require this file include:
. Alongside its counterpart, locked-secret.bin , this tiny 80-byte binary file serves as the cryptographic foundation for the entire Amiibo backup and emulation community. Without it, popular Near Field Communication (NFC) applications like TagMo (Android) or Ally (iOS) cannot process the raw dump files (.bin) required to clone or simulate Amiibo characters.
When setting up TagMo to create custom cards, you will receive an error if these keys are missing.