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.

DBI language error

kevinxyz · 2024-04-01T01:04:31+00:00

My dbi language change every time i open it. How to change it to default eng?

Hardmodded Switch no longer booting into hekate

Spamap

Member

Newcomer

Level 1

Jul 9, 2023

Hello!

About a year ago I hardmodded my V1 patched switch with a HWFLY chip. It has worked fine for that entire year but just recently stopped working after I updated the firmware on the sysNand.
Now, the light on the modchip will flash purple for a while when it is first turned on, but will go onto solid purple after a while and the switch will boot into normal OFW without going into hekate. (The solid purple light indicates that it failed glitching)

I have flashed the chip firmware to the latest version and updated hekate/atmosphere, and also unplugged the battery of the switch in an attempt to reset the chip. I have read somewhere else that the training data for the chip needs to be reset, but according to the guide on the hwfly github page I need to be able to boot into hekate to do that (Which I cannot do). Is there another way to reset it?

Thanks