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

Gaming Any way to access eShop without updating to 3.0.0?

Thread starter Meteor7
Start date Jun 25, 2017
Views 1,831
Replies 3

Meteor7

Guess where this thumb goes.

Member

Level 15

Jun 25, 2017

It used to be that a full power cycle allowed eshop access without the need to update. Recently, though, even doing that still results in a 2124-3000 error code. Is there any other way to bypass the need to update, or is updating the only way, now?

Sonic Angel Knight

Well-Known Member

Member

Level 23

Jun 25, 2017

Dunno, I updated right away, the system needs to focus more on adding new features to make it more complete and feel like a $300 system rather than relying on exploits. I assume updating is the current way for now.

Deboog

Well-Known Member

Member

Level 6

Jun 25, 2017

Doesn't the exploit still work on 3.0?

Meteor7

Guess where this thumb goes.

Member

Level 15

Jun 25, 2017

Deboog said:
Doesn't the exploit still work on 3.0?

Pegaswitch? It might, but apparently the 3.0.0 update "fixes a known vulnerability in the NS sysmodule". That, and it might turn out 3.0.0 fixed an as of yet unknown vulnerability which might be crucial for future hacking, so if it's at all possible, I'd like to stay on 2.0.0.

Last edited by Meteor7, Jun 25, 2017