My Nintendo Switch V1 with an RP2040-Zero Picofly modchip suddenly stopped booting after not being used for two weeks.

vuviett47 · May 21, 2026

My Nintendo Switch V1(patched) with RP2040-Zero Picofly modchip suddenly stopped booting.
I haven’t used it for around 2 weeks. The last time I used it, I was playing a game and just left the console in sleep mode, then forgot about it because I got busy.

Now it won’t turn on at all. I already left it charging for 1–2 days and I’m pretty sure it is charging normally.

When I press the power button, the modchip LED goes:

blue (4-5s) -> red (0-1s) -> off

The screen stays completely black, no backlight and no fan spin.

But when I connect it to my PC, TegraRcmGUI detects it and says “RCM Device detected”.

In USB Device Tree, It detect as "Nintendo Switch APX Mode"

Connection Status : DeviceConnected
Device Description : Nintendo Switch APX Mode
Manufacturer : NVIDIA Corp.
Product : APX
Driver loaded : libusbK
Power State : D0
Demanded Current: 32 mA

So now I’m confused if the problem is:

the battery
the Picofly/modchip
eMMC
or the motherboard itself

Has anyone had this happen before after leaving the Switch in sleep mode for a long time?

vuviett47 · May 21, 2026

CORRECT AGAIN: It blue-> purple -> off

thesjaakspoiler · May 22, 2026

It can be many things and many things combined.

Are you sure you have a Picofly modchip as those show error codes with short and long pulses? (color doesn't matter)
https://github.com/Ansem-SoD/Picofly

HWFly modchips use color codes .

Thread 'Hwfly led red'

Jan 24, 2023

Hello,
I have installed the hwfly chip in my oled and at first the green led light came out. When installing the files to the SD it worked apparently fine. However, it got stuck and I restarted it. Once I restart it, I only get the red light.
Do you know what could be due?
The connections are correct. The CFW that loads needs a specific payload that I did not do. could that be the mistake?.

Thanks in advance

Purple is a glitch timeout and usually indicates some issue with your installation like a loose cable or a DAT0 adapter that is not making good contact.
IF DAT0 is the issue, the console should boot into the original firmware if you updated both the official and CFW with the same version.
If you haven't updated your official firmware then you might see a black screen due to a fuse mismatch.

Try removing the SD card.
If the modchip is fine then it should show an error message.

Hekate should boot regardless of the battery,
Atmosphere needs a working battery else you will only get a black screen,
Turn on your Switch to see if you get a faint glowing screen or a completely black screen.
If it is completely black then usually it is due to a hardware error or flat battery.
A battery drains 1~2% per day so if you connect your Switch to a PC and see it draw a few hunderd miliamps, then it is an indication that it tries to charge itself. It will only charge if the battery is fine.
Dead/broken batteries won't charge.

If your modchip is set to autoboot into Atmopshere, Hekate logos / menus are skipped.
And in case of a bad battery, you will only see a black screen.
Check the Hekate config to see what your autoboot setting is.

My Nintendo Switch V1 with an RP2040-Zero Picofly modchip suddenly stopped booting after not being used for two weeks.

New Member

New Member

Well-Known Member

Similar threads

Popular threads in this forum