SysNAND and Atmosphère both black screen / frozen logo

Ferdigacha

New Member
Newbie
Joined
Aug 18, 2026
Messages
1
Reaction score
0
Trophies
0
Age
18
XP
7
Country
Spain
Hi everyone,


I'm hoping someone can help me diagnose a "brick" issue with my Switch. Here's a summary of everything I've checked so far:


Setup:


  • Console has an RCM chip installed (auto-injects Hekate payload on boot, no jig/SD needed to reach Hekate)
  • Chip had been working fine for months, then stopped working suddenly (no updates, drops, or SD removal that I'm aware of)

Symptoms:


  • Hekate itself boots and works perfectly (menu is fully navigable, battery reads)
  • Neither SysNAND (stock) nor Atmosphère will boot — both result in either a black screen or a frozen logo (Nintendo logo for stock, freezes before fully loading)
  • This happens with or without the SD card inserted — I tried booting stock SysNAND directly with no SD at all, and it still fails the same way
  • The SD card is the one I've always used, previously working fine with Atmosphère

Troubleshooting done so far:


  • Backed up boot0/boot1 partitions from Hekate → completed with no errors
  • Confirmed both "Launch SysNAND" and "Launch Atmosphère" options exist in Hekate's boot menu, tried both, same result
  • No error codes appear on screen — just black screen or frozen logo, no crash text

Given that stock SysNAND fails even without CFW/SD involved, I'm suspecting eMMC/NAND corruption in the system partitions rather than an Atmosphère or SD issue, but I don't have a full NAND backup (rawnand.bin) from before this started — only the boot0/boot1 backup I just made.


Has anyone run into this exact pattern before? Any pointers on next diagnostic steps (BIS keys check, partition table inspection, etc.) or whether this is realistically only fixable with hardware-level repair at this point would be really appreciated.


Thanks in advance!
 
Does it still run on the battery without the charger plugged in?
You need a healthy battery else both CFW/OFW will not boot.

Check your fuse count in Hekate.
Maybe the fuse count is too high for the OFW to boot past the logo.

If you see the Nintendo logo then the BOOT0 and BOOT1 partition are probably fine.
eMMC corruptions are very rare.
Does Hekate say anything about the emmc running in 1 bit mode maybe?

Sometimes multiple unrelated issues happen at the same time like a bad fuse count for OFW and an issue with your SD card.
Before going all-in on restoring your NAND, I would recommend grabbing another SD card, install the latest hekate/atmosphere or a HATS package and update the primary payload you try to inject also to the latest version.
Note that an outdated primary payload with a newer hekate version on the SD card also gives funky results.
The injected payload version needs to match the files on the SD card.
 

Site & Scene News

Popular threads in this forum