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

Shorted USB-C with power - dead.

Thread starter FezMonki
Start date Jun 10, 2022
Views 684
Replies 3

FezMonki

Member

Newcomer

Level 1

Jun 10, 2022

Hey everyone, I did a stupid today. On my way to the ribbon cable over the battery connector with my tweezers, they slipped and of course, had to bridge the positive battery pad with the usb-c port.

I've had the console for all of three days since picking it up cheap on local ads and replacing the screen, and now I killed it again lol.

I'm not quite there yet on diagnostics but should be able to replace whatever blew (have a hot air station as well), could anyone be kind enough to point me to what I probably blew up and how to make sure? Thank you in advance.

FezMonki

Member

Newcomer

Level 1

Jun 10, 2022

Well never mind I guess, after 20 minutes with the battery disconnected the thing is working again. Back to figuring out how I messed up my hwfly install then (blinks purple -> red) lol.

Reactions: binkinator

thesjaakspoiler

Well-Known Member

Member

Level 8

Jun 12, 2022

Most people say it's bad contacts/soldering when someone mentions this problem.
In rare cases the hwfly contains the old version of spacecraft instead of 0.2.0/.