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

EdiZon/sys-netcheat cannot access heap & reporting base version build ID (Project DIVA MEGA39's)

nastys

ナースティス

Member

Level 9

Mar 3, 2020

Basically, I cannot use sys-netcheat anymore with Project DIVA MEGA39's and I can't figure out why. It just doesn't freeze when searching for any value and it aways yields no results. EdiZon has the same issue, ~~plus it reports the build ID of the base, 1.0.0 NCA despite having 1.0.3 installed, even if I put a modified 1.0.3 main nso myself in exefs.~~ I've also noticed that there's no heap bar and that the code bar is as big as the heap would be.

I've asked a friend to check if it works for him, and yep, it does. It shows the heap area, the correct build ID, and he can search the heap.

I have tried reinstalling both Kosmos and vanilla Atmosphère and even using his folders to no avail. I've also tried recreating the emuMMC twice and I moved all old folders on my microSD to a subfolder, so it should be clean. debugmode=1 is set and other games seem to work fine, ~~while no version of MEGA39's does, not even 1.0.0 whose build ID is reported~~. Possibly related: I could create a coredump with twili just fine before, but now it just creates a 0-byte elf.

What could be wrong?

EDIT: after formatting the microSD, creating a new emuMMC, formatting it, and installing up to the 1.0.2 update instead of 1.0.3, EdiZon reports a different build ID, but I still can't access the heap.
EDIT2: it turns out my build ID is the correct one, not my friend's, for some reason.
EDIT3: after changing the value by editing the save, I can access it with EdiZon, but it's in MAIN instead of HEAP, which doesn't make sense, Also, sys-netcheat still doesn't work.

Last edited by nastys, Mar 6, 2020