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

Atmo 16 emunand update issues

viper3344

Well-Known Member

Member

Level 8

May 10, 2023

Hey all!
Having an odd issue....
So I use emunand to run atmo and when setting up new sticks I have always just:
partitioned
set up emunand (from my fw11 sysnand)
boot into emunand
run daybreak to update to whatever latest FW
having daybreak reset to factory settings
reboot into emunand and set it up like a new swtich. profit

For existing cards, I just run daybreak and update preserving settings.

For some odd reason since FW16, whenever I set up the initial emunand it will CRASH if I have daybreak do the factory settings reset.
I have to say "preserve settings" then once the emunand is set up with the latest 16FW, initialize the unit to get the emunand back to factory fresh settings.
I tried with FW15 and it works just fine.

No themes
Fresh SD cards
latest everything including hekate, atmo, sig patches etc...
But yeah for some reason the ONLY way I can now set up a new card with FW16 is to have daybreak preserve setting and reset it after its done. Works great then, no issues just so odd that I have to preserve settings first then reset it.
FW15 works just fine having daybreak do the initialize.
Any possible thoughts?

Atmo 16 emunand update issues

Well-Known Member

Similar threads

Popular threads in this forum