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

Is my setup for the Switch-OC-Suite correct?

ragnarok_approaches123

Well-Known Member

Newcomer

Level 3

Jun 13, 2023

I'm using Atmosphere version 1.5.3, Hekate 6.0.4, a HWFLY modchip and an OLED Switch

This is my hekate_ipl.ini file:

[config]
updater2p=1
{------ Atmosphere ------}
[Atmosphere FSS0 EmuMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/emu_boot.bmp
{}
[Atmosphere FSS0 SYS]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

I downloaded the files SdOut.zip and loader.kip from the latest release, posted last week according to GitHub.

I copied the content from SdOut.zip to the root of my micro SD card.

Using the online configurator I set the file loader.kip to the default settings for Mariko.

I copied the file loader.kip to /atmosphere/kips/.

Is this setup correct? How do you set the overclock settings for each game like you can on sys-clk?

Last edited by ragnarok_approaches123, Jun 13, 2023

Is my setup for the Switch-OC-Suite correct?

Well-Known Member

Similar threads

Popular threads in this forum