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

Homebrew Tutorial Updated

Setup a DevKitPro environment on Windows.

DevKitPro is a set of packages needed to build homebrew for different consoles including:

GP2x
GP32
Game Boy (Advanced)
DS
3DS
Wii
WiiU
Switch

And is composed of three main toolchains:

devkitARM
devkitPPC
devkitA64

DevKitPro can be installed on several OSes and you can get it from the official web https://devkitpro.org/wiki/Getting_Started.

You can install using the standalone installer https://github.com/devkitPro/installer/releases or if you have a working pacman environment, like MSYS2 you can use the manual installation and setup of DevKitPro following the instructions on https://devkitpro.org/wiki/devkitPro_pacman

The Windows Stand Alone package install a custom MSYS2 environment on a non standard path.

I choose to use the pacman environment installation because is lot probable you already have a MSYS2 environment working, by example following the tutorial https://gbatemp.net/threads/install-msys-environment.652234/

For that you need to start a MSYS2 window, by example MINGW64 environment:

First you need to edit the pacman.conf on c:\msys64\etc\ folder, and add the next lines at end of it:

Code:

[dkp-libs]
Server = https://pkg.devkitpro.org/packages

[dkp-windows]
Server = https://pkg.devkitpro.org/packages/windows/$arch/

Then on the MINGW64 window Import the cypher keys of DevKitPro

Code:

pacman-key --recv BC26F752D25B92CE272E0F44F7FD5492264BB9D0 --keyserver keyserver.ubuntu.com

In case the command fail because the server didn’t send the correct file or is down, you can obtain the message:

Code:

gpg: keyserver receive failed: General error
==> ERROR: Remote key not fetched correctly from keyserver.

The content of the file pubring.gpg is:

Code:

Save this to a file with the name pubring.gpg

Then import it manually:

Code:

pacman-key --import "FULL_PATH_TO_FOLDER_CONTAINING_pubring_gpg"

By example:

Code:

pacman-key --import "C:\downloads\DevKitPro"

Code:

pacman-key --import ~

NOTE: the path to the file must be full and DO NOT end on the «\» character

Next sign locally the key:

Code:

pacman-key --lsign BC26F752D25B92CE272E0F44F7FD5492264BB9D0

Then verify the key is working well:

Code:

pacman-key -l BC26F752D25B92CE272E0F44F7FD5492264BB9D0
pacman-key -l F7FD5492264BB9D0

You should get a response just like:

Code:

pub  rsa4096 2018-02-28 [SC]
      BC26F752D25B92CE272E0F44F7FD5492264BB9D0
uid          [  full  ] Dave Murphy (WinterMute) <[email protected]>
sub  rsa4096 2018-02-28 [E]

Now you are ready to Install DevKitPro Keyring:

Code:

pacman -Syuu --needed --noconfirm
pacman -U https://pkg.devkitpro.org/devkitpro-keyring.pkg.tar.xz

Update and verify and update package databases until there are no packages to update:

Code:

pacman -Syuu --needed --noconfirm

By now you have a DevKitPro installation ready to be used.

Optionall but recomended, install DevKit-Env Package:
The DevKitPro's package devkit-env install a shell which setup the different environment variables needed by homebrew to be build.
you can install the package with the command:

Code:

pacman -Syuu --needed --noconfirm devkit-env

Once you install that package the environment must be initialized, you can close and reopen the MINGW window or you can run the command:

Code:

source /etc/profile.d/devkit-env.sh

Last edited by impeeza, Apr 3, 2024

Reactions: lordelan, Blythe93, DigitalDesignDude and 7 others

Click to expand...

Dat one with the Rez

¡Kabito!

Well-Known Member

¡Kabito!

Similar threads

Popular threads in this forum