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.

Fusee.bin with the new Pre-release of Atmoshere 1.7.0

Mimikyu · 2024-03-30T15:42:14+00:00

Hello, little problem again... I tried to update my Switch again because of the new 18.0.0 Update of Nintendo. I'm reading a lot on the Website WiiDataBase and that's how and why i wanted to update now. My problem is that i can't access my custom...

Switch will not turn on after installing MissionControl

tmnr1992

Well-Known Member

Member

Level 10

Apr 15, 2024

So I recently hacked my unpatched Switch, got Atmosphere and sigpatches working just fine, and today I tried installing the latest version of MissionControl (0.11.0). After copying the files and rebooting the console I went to Hekate and selected my emunand but got the error "panic occured while running Atmosphere", so I turned off the console, deleted the MissionControl files and rebooted the console to make sure everything was still working properly. After this I tried the previous version of MissionControl (v0.10.0), as I thought maybe the latest version was bugged or not compatible with my version of Atmosphere (1.6.2). So again I copied the files and tried rebooting the console, but this time the console did not turn back on, and pressing the power button does not put it in recovery mode either, because I'm connecting my phone but it's not giving me the option to inject a paylad anymore.

I should also mention that the battery was fully charged while doing all this and it's only been a few minutes since then.

[EDIT]

Apparently there was some bug with Rekado where the option to inject a payload was not showing up, but I finally got it working, the console was already in recovery mode, booted Atmosphere just fine with MissionControl 0.10.0 installed.

Last edited by tmnr1992, Apr 15, 2024

Reactions: Blythe93

Switch will not turn on after installing MissionControl

Well-Known Member

Similar threads

Popular threads in this forum