Hello guys, this is my first post here! I just got a MIG Switch card out of curiosity and I was tinkering with it. For those who don't know, it's used by placing XCI dumps as well as other game specific bin files in the sd card of the MIG Switch, and are obtained from the original cartridge by using an app like nxdumptool. Two of these bin files are mandatory to get the game to boot: Initial Data.bin and Certificate.bin. They stay the same for every cartridge of a specific game. Now, if you want to use an XCI dump from a shady website it's impossible to get it to work without those files. By using the Certificate.bin from another game it has no problem, but this does not count for the Initial Data.bin. So I looked for a way to obtain this Initial Data from an XCI file and read a bit of the XCI file documentation from switchbrew dot org. Here's what I understood so far: The Switch checks if the cartridge is valid by doing a challenge–response authentication on the Initial Data. The Package ID is contained both on the XCI and the Initial Data, on positions 0x110 and 0x0 respectively. The Initial Data hash is on the XCI at position 0x160. It is calculated by doing a SHA-256 hash on the full Initial Data content. So I was wondering, is there a way to to construct a functional Initial Data file starting from an XCI dump? I also tried a reverse approach by editing the Package ID in the Initial Data from another game, generating the Initial Data hash and putting it in the XCI file but is not enough to get the Switch believe it's a real game. Sorry if this may seem stupid but let me know what you think.

mig switch not working/updating??

stickybit · 2024-03-28T19:59:51+00:00

just got my mig switch and followed instructions to the T to update it and all im getting is a red light and then a message saying cart not recognised, all im trying to do is update it to the latest firmware, it says it should flash blue when...

Tutorial Updated

Dealing with NAND/ EMUNAND safely

YOU HAVE BEEN WARNED
This tutorial will give you useful information on how to deal with NAND/ EMUNAND safely. 99% be safe to follow this tutorial but bear in mind that there is always at least a risk to brick your Switch.
> Make a backup/ copy of NAND and/or EMUNAND before doing anything.

YOU'RE AT YOUR OWN RISK
I TAKE NO RESPONSIBILITY FOR ANY DAMAGES

First thing first, SX's emunand is extremely safe to be bricked by purpose. It creates a full nand backup of the Switch including boot0/1 and all partitions. If you have a working emunand, there is probably no need to backup sysnand as it will be the same. In the event of accidentally bricking sysnand/ emunand, importing all partitions from emunand to sysnand will definitely work and vise versa.

SX 2.3 supports separated Nintendo folder as Emutendo for emunand. Linked the two nands on the same possible firmware is recommended.

PRODINFO and PRODINFOF are identical compare to the ones of your Switch on every firmware versions.
All BCPKG2 partitions are the same from other devices on the same firmware versions.
Game savedata is stored in USER partition under /save/*.*

In this topic, we will focus on SYSTEM partition.

GET BISKEY

https://files.sshnuke.net/biskeydumpv6.zip
Run the payload and write down (or scan QRCode)

SYSTEM
BIS KEY 2 (crypt): NUMBERS
BIS KEY 2 (tweak): NUMBERS

USER
BIS KEY 3 (crypt): NUMBERS
BIS KEY 3 (tweak): NUMBERS

HACDISKMOUNT SYSNAND

- memloader
https://files.sshnuke.net/memloaderv2.zip
Copy *.* in [sample] folder to SD and plug it in the Switch
Run the payload [memloader.bin]
Unplug any USB cable
> Choose emmc line
> Plug USB C <> USB A cable to the Switch and PC

- HacDiskMount
https://files.sshnuke.net/HacDiskMount1055.zip
Run the tool under Administrator permission
> Open Physical Disk > Choose Linux line

SYSTEM
> Double click on SYSTEM and fill BisKeys2 in the small table on top
Crysto > BIS KEY 2 (crypt): NUMBERS
Tweak > BIS KEY 2 (tweak): NUMBERS
> Press on [Test] > you will get OK! Entropy
> From Drive Letter table > Choose a drive disk, N for example.
> Press on [Mount]
Install driver if needed.
Acess N drive from My Computer

USER
> Double click on USER and fill BisKeys3 in the small table on top
Crysto > BIS KEY 3 (crypt): NUMBERS
Tweak > BIS KEY 3 (tweak): NUMBERS
> Press on [Test] > you will get OK! Entropy
> From Drive Letter table > Choose a drive disk, N for example.
> Press on [Mount]
Install driver if needed.
Acess N drive from My Computer

HACDISKMOUNT EMUNAND

- HacDiskMount
https://files.sshnuke.net/HacDiskMount1055.zip
Run the tool under Administrator permission
> File > Open file > Choose full.00.bin

SYSTEM
> Double click on SYSTEM and fill BisKeys2 in the small table on top
Crysto > BIS KEY 2 (crypt): NUMBERS
Tweak > BIS KEY 2 (tweak): NUMBERS
> Press on [Test] > you will get OK! Entropy
> From Drive Letter table > Choose a drive disk, N for example.
> Press on [Mount]
Install driver if needed.
Acess N drive from My Computer

USER
> Double click on USER and fill BisKeys3 in the small table on top
Crysto > BIS KEY 3 (crypt): NUMBERS
Tweak > BIS KEY 3 (tweak): NUMBERS
> Press on [Test] > you will get OK! Entropy
> From Drive Letter table > Choose a drive disk, N for example.
> Press on [Mount]
Install driver if needed.
Acess N drive from My Computer

THINGS CAN DEAL WITH
Mount SYSTEM using HacDiskMount

+ Clean Ticketblob
> access save folder
> Delete 80000000000000e1 and 80000000000000e2

+ Clean Error Logs
> access save folder
> Delete 80000000000000D1

+ Move user profiles/ play history from nand to nand
> access save folder
> Copy 8000000000000010 and 8000000000000011 from any nands to your target nand.
Play history will work if on the same nand or sysnand/ emunand is linked.

+ Disable firmware update nag when running a game by accidentally connecting to the Internet in lower firmware than requirement.
> access save folder
> Delete 8000000000000045

+ Manually factory restore settings
> access save folder
> Delete all files except 8000000000000120

MANUALLY BACKUP SAVEGAME DATA FROM USER
Mount USER using HacDiskMount

On emunand, files are splitted into full.0x.bin
> User command line to merge them in
> copy /b full.00.bin+full.01.bin+full.02.bin+.... full.0x.bin full.nand.bin

Open the nand file using HacDiskMount and mount USER following with Biskey3

> access save folder
> Backup all files to a folder
> Run extract_nand_gamesave run.bat with all your savedata backup to /save/

This tutorial is for you guys to take a note in case you will need to deal with in the future. I will keep updating this topic when I knew something else.

Enjoy while it lasts.