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.

duckstation for Switch

catlover007 · 2024-04-22T04:06:40+00:00

duckstation is an excellent Playstation 1 emulator by Stenzek. It has a very good compabiility and it is quite performant. It also supports all kinds of enhancements such as high resolution rendering and PGXP which can lessen the "wobble" and...

Hekake won’t boot after upgrading stock to 18.0

Frok

Member

Newcomer

Level 1

Apr 6, 2024

First of all I’m a noob, I’ve an OLED Switch modded with Hwfly and so far everything worked perfectly.

Since all online tutorials say that stock and emu are totally disconnected, I upgraded the stock firmware to 18.0, to avoid the constant nag to update the console every time I launched a game. On the emu I still have 17.0.

Well, after the update I’m no more able to boot in Hekake. When I press the power button I see for a while the Nintendo logo, then the screen goes black. I can see the Hwfly led pulsing green and that’s all.

Pressing some buttons randomly while booting (I guess Vol– and Vol+) I can start the stock firmware, but something is still strange: the mod chip led keeps pulsing green and, if I launch a game, I can’t return to system or turn the console off because the Home and Power button don’t do anything.

Do you have any idea about what it could have happened?

Do I need to update some file on the SD card? Did Nintendo find a way to disable the chip in the last update? I don’t know what to do.

Thanks.