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.

Fusee.bin with the new Pre-release of Atmoshere 1.7.0

Mimikyu · 2024-03-30T15:42:14+00:00

Hello, little problem again... I tried to update my Switch again because of the new 18.0.0 Update of Nintendo. I'm reading a lot on the Website WiiDataBase and that's how and why i wanted to update now. My problem is that i can't access my custom...

Switch OLED will not turn on. Questions about Picofly install.

Twiggs4625

Well-Known Member

Newcomer

Level 2

Nov 23, 2023

I installed a picofly just fine on multiple switch lites and V2 and a this OLED. All work fine. I only mention this because at this point I feel I can mod any version without issue. However this OLED model has the infamous DAT0 connection. In any regards, I was playing a game just fine and then went into a few homebrew apps to look at changing some icons. when doing this I got a screen that was simialr to the one below.

This was not my exact error but it was one of these type of errors. Again all was working fine until this happened. I pressed the POWER button to reboot and now it appears that the switch will not power on at all. Just a black screen.

Where do I start troubleshooting? Just happened out of nowhere when things have been working as I said fine with no issues.

HATS 1.6.2
FW 17.0.0
PicoFly OLED V6 with V6 DAT0 connector. Properly mounted and anchored.

I have not taken it apart yet. Curious what your thoughts are.

Post automatically merged: Nov 23, 2023

Dock Green LED blinks for a split second when docking it, but no other indicators

Post automatically merged: Nov 23, 2023

Here is a video of the code when I press the reset button on the picofly board.

Post automatically merged: Nov 23, 2023

Ok. I am seeing this is *== No eMMC CMD1 request (poor wiring, or dead CPU)... Everything was working so I am assuming poor wiring and CMD or CLK... I am using a flex cable on this install and I felt it was good enough quality. Again, worked on the first run. Will have to recheck these points I guess.

Is it common to have black screen when this error occurs?

Post automatically merged: Nov 23, 2023

Found out it was a short on the APU shield and the CLK and GND points. Working now.

PSA: solder mask and bend the shield to avoid this.