Hacking [Help] Switch Lite Picofly (RP2040) - emuMMC crash at 52% with visual glitches, now Black blinking Screen

ezqulo · Mar 29, 2026

Hi everyone, I really need your help with my Switch Lite. I just had an RP2040 (Picofly) installed and I’m losing my mind.

Here is the timeline:

At first, the chip worked. Official SysNAND booted perfectly fine. But whenever I tried to launch CFW (emuMMC), I got a pure Blue Screen of Death.

I removed everything on my sd card, reformatted it and put the official Hekate and Atmosphere release files. I tried to go into Hekate to partition the SD card and create a fresh emuMMC

During the emuMMC creation in Hekate, it crashed at 52%. The screen started glitching heavily (black lines everywhere, green spots)

After rebooting, I got red text: Payload file is missing! and Missing Minerva lib!

I took the SD card out, went to my PC, cleaned it via Diskpart, and reformatted it again to FAT32 (and this time I put 32kb cluster instead of 64kb) using Rufus. I put a fresh install of Hekate and Atmosphere on the root (with payload.bin) and my current situation is:

- If I insert the SD card: The screen stays black and blinks, nothing happens.

- If I remove the SD card: The console boots instantly to the modchip's "No SD" screen (so the chip and screen are definitely alive).

The SD card is a 256GB card that worked perfectly fine in my PS Vita right before this.

Thanks in advance for your help!

thesjaakspoiler · Mar 29, 2026

You maybe missed a step :
The primary payload, from Hekate (hekate_ctcaer_x.x.x.bin), should be renamed to payload.bin and placed on the root of the SD card.

The third picture is Hekate complaining that it is missing the minerva library, which is responsible for memory related stuff.
That blue screen is the Switch freaking out about it's memory.
So maybe also check if you copied the files correctly.
Hekate should be in the bootloader folder and Atmosphere has the atmosphere folder.
(If you are on a Mac, mind the archive bit).

CMDreamer · Mar 29, 2026

I'm almost sure what you answer will be, but have you tested your microSD card against damage?

The fact that the Switch works without it, seem to be related with a damaged microSD card.

Sylpa · Mar 29, 2026

Ofw v22.0.0 ?

Edit : what's happen when you try to boot without sdcard with vol+ and vol- pressed together?

ezqulo · Mar 29, 2026

thesjaakspoiler said:
You maybe missed a step :
The primary payload, from Hekate (hekate_ctcaer_x.x.x.bin), should be renamed to payload.bin and placed on the root of the SD card.

The third picture is Hekate complaining that it is missing the minerva library, which is responsible for memory related stuff.
That blue screen is the Switch freaking out about it's memory.
So maybe also check if you copied the files correctly.
Hekate should be in the bootloader folder and Atmosphere has the atmosphere folder.
(If you are on a Mac, mind the archive bit).

Hi, thanks for the reply. I have already renamed the Hekate .bin file to payload.bin and placed it at the root of the SD card. I am on Windows, so I am not affected by the Mac archive bit issue.

I have double-checked my file structure and it is exactly as you described: the atmosphere and bootloader folders are at the root, and I made sure to include all the files from the Hekate Nyx zip. I even performed a diskpart clean followed by a fresh FAT32 format with a 32kb cluster size using Rufus to be sure.

Despite having the correct files and naming, the situation remains the same:

With the SD card inserted: The screen stays black and blinks.
Without the SD card: The console immediately boots to the modchip No SD screen.
Removing the SD card during the black screen : sleeplib error and glitch on the screen

Post automatically merged: Mar 29, 2026

Sylpa said:
Ofw v22.0.0 ?

Edit : what's happen when you try to boot without sdcard with vol+ and vol- pressed together?

Hello, thanks for your reply. I tried booting without the SD card while holding both Vol+ and Vol- together, and I indeed got a solid Blue Screen.

Since this is happening even without the SD card, it seems like a hardware or soldering issue. As I mentioned before, the console crashed with heavy visual glitches during the emuMMC creation. Before that happened, everything was working perfectly; I could still play Minecraft on the official firmware without any issues.

Do you think this is a sign of a bad solder joint or a failing component? Should I open the console to inspect ?

Sylpa · Mar 29, 2026

Oh, bad news... Seems your original firmware is corrupt or you have a hardware issue. Maybe try to remove the modchip and fix your switch before something else. I don't know how to get ride this bsod...

ezqulo · Mar 29, 2026

Sylpa said:
Oh, bad news... Seems your original firmware is corrupt or you have a hardware issue. Maybe try to remove the modchip and fix your switch before something else. I don't know how to get ride this bsod...

That's what I feared. However, since the console was working perfectly just before the crash at 52% during emuMMC creation, I suspect a soldering joint might have failed due to thermal stress. Thank you for your help.

Hacking [Help] Switch Lite Picofly (RP2040) - emuMMC crash at 52% with visual glitches, now Black blinking Screen

New Member

Attachments

Well-Known Member

Well-Known Member

Member

New Member

Member

New Member

Similar threads

Popular threads in this forum