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

Lithium: Lightweight Easy to Use Title Installer for 7.X

protomouse

Well-Known Member

Newcomer

Level 4

Jul 27, 2021

#461

EDIT: Two seconds after I posted the below I figured out that when I rewrote the script that creates the index JSON, I made it send absolute URLs instead of relative ones. I changed that behavior back and things started working again.

Hi @blawar! I'm running into an issue I swear I've never seen before. I'm connecting to an HTTP site using basic auth. I'm serving up a JSON index for Lithium, and that works well. But when I grab one of the files, Lithium doesn't seem to set the Authorization header (or any of the other headers) and I get "Failed to open NSP":

Request

Code:

GET / HTTP/1.1
Host: example.com
Authorization: Basic ...
Accept: */*
Accept-Encoding: deflate, gzip
Theme: ...
UID: ...
Version: 12.1
Language: en
HAUTH: ...
UAUTH: ...

Response

Code:

HTTP/1.1 200 OK
Content-Length: 282
Date: Tue, 27 Jul 2021 14:42:17 GMT
Content-Type: application/json

{
  "files": [
    {
      "url": "http://example.com/path/to/file.nsp",
      "size": 422012489
    }
  ]
}

Request

Code:

GET /path/to/file.nsp HTTP/1.1
Host: example.com
Range: bytes=0-1048575
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.85 Safari/537.37
Accept: */*

Response

Code:

HTTP/1.1 401 Unauthorized
Content-Type: text/plain
Www-Authenticate: Basic realm="example"
Date: Tue, 27 Jul 2021 14:44:34 GMT
Content-Length: 17

401 Unauthorized

This used to work. Not sure if I was on an older version, but one thing that's definitely changed is that I'm handling authentication in Traefik instead of nginx.

Last edited by protomouse, Jul 27, 2021

Homebrew RELEASE Lithium: Lightweight Easy to Use Title Installer for 7.X

Well-Known Member

Similar threads

Popular threads in this forum