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

Black Screen when updating Hekate 6.0.4?

Thread starter Gilgamashu
Start date May 10, 2023
Views 1,503
Replies 1

Gilgamashu

Active Member

Newcomer

Level 3

May 10, 2023

It's my first time updating Hekate. I'm currently running hekate 6.0.2 with atmosphere 1.5.2 and emummc 16.0.2 fw.
I updated atmosphere first and so Im now running atmosphere 1.5.3. Then I tried updating hekate next by merging the bootloader folder from the downloaded file to the current one.
Then, it wouldnt boot anymore only black screen.
It boots normally though if I install the old hekate 6.0.2. . . Maybe I'm missing something? I stop on updating the emummc fw for now.

TeamAllison

New Member

Newbie

Level 1

Jun 24, 2023

Gilgamashu said:
It's my first time updating Hekate. I'm currently running hekate 6.0.2 with atmosphere 1.5.2 and emummc 16.0.2 fw.
I updated atmosphere first and so Im now running atmosphere 1.5.3. Then I tried updating hekate next by merging the bootloader folder from the downloaded file to the current one.
Then, it wouldnt boot anymore only black screen.
It boots normally though if I install the old hekate 6.0.2. . . Maybe I'm missing something? I stop on updating the emummc fw for now.

Did you ever find out the problem?