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...

Hacking Question Migrated SD. CFW (Atmosphere) reads SD but OFW does not

Thread starter Alex634547
Start date Mar 19, 2020
Views 821
Replies 1

Alex634547

New Member

Newbie

Level 1

Mar 19, 2020

I migrated my EMUMCC partition and Fat32 partition over to a new card (128gb -> 256gb). The only difference in the cards are the size and cluster size. 32 for 128 and 64 for 256. OFW thinks there is no SD inserted and CFW boots and runs fine. I am able to see the SD card and play games off of it when using CFW. Any ideas why the OFW would have trouble reading the card when CFW reads it just fine?

Draxzelex

Well-Known Member

Member

Level 23

Mar 29, 2020

Alex634547 said:
I migrated my EMUMCC partition and Fat32 partition over to a new card (128gb -> 256gb). The only difference in the cards are the size and cluster size. 32 for 128 and 64 for 256. OFW thinks there is no SD inserted and CFW boots and runs fine. I am able to see the SD card and play games off of it when using CFW. Any ideas why the OFW would have trouble reading the card when CFW reads it just fine?

Have you checked if the SD card is fake or not?