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

hacpack and basenca/romfs

KurosuDesu

New Member

Newbie

Level 1

Mar 17, 2024

I am trying to recreate with hacpack an update NSP file ("patch romfs" according to hactool) using either of the basenca/baseromfs options, without success. I suspect the BKTR section remains incorrect.

hacpack rebuilds a regular (base) NSP from its NCA files in a way that is succesfull to an emulator (but obviously not a Switch). And by fail, it is eg LibHac.Tools.FsSystem.NcaUtils.Nca.OpenRawStorageWithPatch throwing a failure.

All were basically extracted with nstool (not sure the basenca is useful here but specified it) and modified to plaintext by hactool.

I've tried using as base NCA the extracted cyphered version as well as its plaintext version, and for baseromfs "hactool --raw --romfs=rom" from these 2 versions as well, and no success.

Maybe I failed one of these tests, but has anyone an idea how I'm using wrong nstool/hacinfo/hacpack, or what would be the correct workflow.

I'm wondering if the BKTR section couldn't be kept verbatim, or it is just a matter to specify an offset corresponding to the (program NCA in the) rebuilt base NSP.

Last edited by KurosuDesu, Mar 17, 2024

hacpack and basenca/romfs

New Member

Similar threads

Popular threads in this forum