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.

duckstation for Switch

catlover007 · 2024-04-22T04:06:40+00:00

duckstation is an excellent Playstation 1 emulator by Stenzek. It has a very good compabiility and it is quite performant. It also supports all kinds of enhancements such as high resolution rendering and PGXP which can lessen the "wobble" and...

Hacking Question Pkg2 decryption failed - Hekate 4.6

Thread starter chardido
Start date Dec 17, 2018
Views 8,762
Replies 6

chardido

Member

Newcomer

Level 1

Dec 17, 2018

Hi everybody,

I'm using Hekate 4.6 payload, with Kosmos configuration, I'm on 6.2.0.

When I try to boot either in stock firmware (OFW) and CFW, it gave me this error:

Code:

Read pkg2
Pkg2 decryption failed!
Failed to launch firmware

What should I do?

chardido

Member

Newcomer

Level 1

Dec 18, 2018

m4xw

Ancient Deity

Developer

Level 17

Dec 18, 2018

chardido said:
UP

https://github.com/CTCaer/hekate/issues/169

chardido

Member

Newcomer

Level 1

Dec 18, 2018

m4xw said:
https://github.com/CTCaer/hekate/issues/169

Ehm.. It's me on github

m4xw

Ancient Deity

Developer

Level 17

Dec 18, 2018

chardido said:
Ehm.. It's me on github

You got your answer.

chardido

Member

Newcomer

Level 1

Dec 18, 2018

m4xw said:
You got your answer.

He replied just 8 min ago.

He said:
"You need to you choidujour to fix your emmc and have the correct 6.2 files".

I've already tried to reinstall 6.2 firmware with choidujour, but I have problem retrieving keys with HACGUI (I've also tried with HACTOOL, with no luck).
Do you know another way to get keys?