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

Console runs hekate fine but won't boot HOS, error 2134-0501

Bradlin

Member

Newcomer

Level 2

Sep 21, 2023

Patched v1 switch, I installed a picofly and the console boots into hekate with no issue, but will very rarely boot HOS. Symptoms:

Most of the time, the battery won't charge in hekate. If I try to boot into Atmosphere (emuMMC or sysMMC), the "switch" logo takes a long time to appear (8-9 seconds instead of the usual 3-5 seconds) and the console gets stuck on it or ends up giving the error 2134-0501 (USB_PD error). Same symptoms if I boot full stock HOS (holding + and - when powering on).
If the battery charges (hekate shows positive current), then I can boot to Atmosphere (both emuMMC and sysMMC work), the battery will charge without issues in HOS, and everything will work fine until I power off the console.
The only times I was able to boot into Atmosphere was after a long time with the console powered off.

I've tried to clean up the area around the M92T36 with some IPA, and immediately after I was able to boot to HOS, but only once. I think the IPA cooling down the chip may have something to do with it.

Some googling shows that the error code 2134-0501 is normally fixed with a replacement of the M92T36. But I have no shorted cap around it or abnormal diode mode reading.

However, when soldering the wires, I did accidentaly remove the 2 caps which go to pins 5 and 6 of the M92T36 and had a hard time putting them back (I worked without a microscope), and I think I may have turned on the console with pins 5 and 6 bridged.

Should I just replace the M92T36? Or is there anything I can do to check which component should be changed?

Last edited by Bradlin, Sep 21, 2023

Console runs hekate fine but won't boot HOS, error 2134-0501

Member

Similar threads

Popular threads in this forum