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?

Hacking cant boot to hekate

Thread starter dust213dust
Start date Jun 2, 2020
Views 1,423
Replies 5

dust213dust

Well-Known Member

Newcomer

Level 4

Jun 2, 2020

im on atmosphere and when i was rebooting or using reboot to payload system was loading to hekate 5.1.1. some time ago i have updated atmosphere to latest version and since then every time i reboot it automatically loads atmosphere. tried tegrarcm with latest hekate and got an error... is therer a way to disable this auto boot or whatever is this?

Lacius

Well-Known Member

Member

Level 26

Jun 2, 2020

You need to replace /atmosphere/reboot_payload.bin with the Hekate payload.

dust213dust

Well-Known Member

Newcomer

Level 4

Jun 2, 2020

can you explain in more details? replace? delete reboot_payload.bin and place hekate_ctcaer_5.2.1 there? or renameit or how?

Lacius

Well-Known Member

Member

Level 26

Jun 2, 2020

dust213dust said:
can you explain in more details? replace? delete reboot_payload.bin and place hekate_ctcaer_5.2.1 there? or renameit or how?

Replace it and name it reboot_payload.bin. If you do this, reboot to payload will boot Hekate.

Reactions: white_n0ise and dust213dust

dust213dust

Well-Known Member

Newcomer

Level 4

Jun 2, 2020

thank you, that worked!!!

Lacius

Well-Known Member

Member

Level 26

Jun 2, 2020

If you're using Atmosphere, however, using fusee-primary is recommended. If you want to use Hekate for whatever reason as your primary bootloader, you can chainload fusee-primary using Hekate.

Reactions: dust213dust