Hacking [HELP] Switch Lite + PicoFly stuck on 2 blinks short yellow LED after updating sysNAND to 21.0.0 (No Hekate)

[Amirelox]

Hello everyone,


I have a Nintendo Switch Lite with PicoFly installed, and after updating my sysNAND to firmware 21.0.0, my console can no longer boot Hekate or Atmosphere at all.


Before the update, everything was working.

---

⚠​

Now, when I turn on the console with the SD card inserted, the PicoFly chip gives:

→ short yellow flash twice (short yellow “​

and nothing else happens.


Hekate does NOT appear anymore after updating sysNAND.


Screen stays black or I sometimes see the “No SD Card” screen from the modchip, without SD CARD but Hekate never loads.


When I turn on the console without the SD card, sysNAND boots normally.
So the console itself is NOT bricked — only the CFW side is broken.

---

⚙​

I have tested all the usual solutions:

✔ Reformatted the SD card to FAT32​

✔ Tried multiple different SD cards​

✔ Clean Atmosphere + Hekate files​

✔ Hard power resets​

✔ Cleaned SD slot​

✔ Tried old and new Atmosphere/Hekate versions​

Still no Hekate. Still short yellow LED.

---

​

• Boot without SD → sysNAND works
• Boot with SD → short yellow **
• Hekate never appears
• Black screen
• SD card works fine on PC
• Multiple SD cards tested — same problem

This looks like the PicoFly cannot initialize SD communication after the sysNAND update (DAT0 / CMD / CLK issue).
Maybe a loose pad or wiring problem that became visible after reboot.


I’m not sure if the sysNAND update triggered timing differences, or if the chip simply stopped reading SD properly at the same time.

---

​

Has anyone seen this short yellow LED + no Hekate after sysNAND update on picoFly?


Is this definitely:

• SD init failure (DAT0 lifted)?
• CMD / CLK issue?
• Bad SD slot?
• Old PicoFly firmware not compatible with 21.0.0 boot timing?
• Or something else?

Should I take it to a modchip technician to reflow/recheck the DAT0/CMD/CLK points?


Any help or guidance is appreciated.
Thanks!

 

[ikynx]

Hello everyone,


I have a Nintendo Switch Lite with PicoFly installed, and after updating my sysNAND to firmware 21.0.0, my console can no longer boot Hekate or Atmosphere at all.


Before the update, everything was working.

---

⚠​

Now, when I turn on the console with the SD card inserted, the PicoFly chip gives:

→ short yellow flash twice (short yellow “​

and nothing else happens.


Hekate does NOT appear anymore after updating sysNAND.


Screen stays black or I sometimes see the “No SD Card” screen from the modchip, without SD CARD but Hekate never loads.


When I turn on the console without the SD card, sysNAND boots normally.
So the console itself is NOT bricked — only the CFW side is broken.

---

⚙​

I have tested all the usual solutions:

✔ Reformatted the SD card to FAT32​

✔ Tried multiple different SD cards​

✔ Clean Atmosphere + Hekate files​

✔ Hard power resets​

✔ Cleaned SD slot​

✔ Tried old and new Atmosphere/Hekate versions​

Still no Hekate. Still short yellow LED.

---

​

• Boot without SD → sysNAND works
• Boot with SD → short yellow **
• Hekate never appears
• Black screen
• SD card works fine on PC
• Multiple SD cards tested — same problem

This looks like the PicoFly cannot initialize SD communication after the sysNAND update (DAT0 / CMD / CLK issue).
Maybe a loose pad or wiring problem that became visible after reboot.


I’m not sure if the sysNAND update triggered timing differences, or if the chip simply stopped reading SD properly at the same time.

---

​

Has anyone seen this short yellow LED + no Hekate after sysNAND update on picoFly?


Is this definitely:

• SD init failure (DAT0 lifted)?
• CMD / CLK issue?
• Bad SD slot?
• Old PicoFly firmware not compatible with 21.0.0 boot timing?
• Or something else?

Should I take it to a modchip technician to reflow/recheck the DAT0/CMD/CLK points?


Any help or guidance is appreciated.
Thanks!

Have had similar issues where modchip fails after seemingly doing a specific action, when in fact it was coincidence. My modchip had issue with DAT0, and would fail randomly and more often if the circuitry was cooler. Since I very rarely rebooted my device (and usually only when doing an upgrade since my list of modules is stable), it felt like a fw update nuked my modchip when in fact it had nothing to do with it. Get your device modchip checked / remodded (and if you do, ask to have DAT0 done the kamikaze way). PM me if you are in Europe and need a skilled technician.

By SysNAND you mean OFW@SysNAND, not CFW@SysNAND. Your modchip install is probably fucked. Get it fixed.

For the error code, refer to the picofly guide in the relevant sticky post.

 

[ElMeteK]

• ** RST is not connected