Hacking Black screen - Cannot boot into Stock/Emu anymore

Merihel · May 19, 2026

Hello everyone,

I tried to search for every possible solution to this but I can't find anything to help me.
Last day while playing, my V1 Switch did a white screen and froze completely. I reset it with Hekate, boot up my emunand as usual. But no matter what I tried, I cannot get into HOS anymore, I get a black screen after Atmosphere Blue then black logo, or after the Nintendo logo (on stock).
Sometimes, Atmosphere boots up with a fatal error with a program ID. I had 2 different. Now it doesn't show any error anymore, just a black screen. I tried rebooting multiple times to see that error again, without success.

Bit of information :
- Hekate doesn't show anything wrong with the nand or emunand
- Battery looks good, I tried with my old official battery, same issue
- Burnt fuses shows HOS 9.1.0 to 9.2.0 (for all this years I only used and updated the emunand)
- Emunand is on previous firmware version (not the latest)

What I already tried :
- Boot into 100% stock, without Hekate
- Boot into semistock
- Format the SD card then reinstall completley the SD Card, barebone
- Flash L4T Ubuntu Noble on another SD card (don't boot either, I have a "BAD CRC Data" error, "cannot find kernel")
- Flash LineageOS, it freezes on splash screen
- As some people recommended in some other threads : wait on black screen, change the battery, reinstall everything+format, ...

TLDR : After a weird freeze, my Switch boots into a black screen on Stock and EmuMMC, Ubuntu and Lineage doesn't boot either.

So what I want to know is:

Could it be hardware related ?
Is there a payload that does a sort of "system health checkup" or do I need to boot into Linux for that ?
Is there a way to get more logs ?

Thanks a lot in advance if people reads this and can help me out!

thesjaakspoiler · May 19, 2026

The only thing that the OFW and CFW have in common are the Boot0 and Boot1 partitions that are used after Hekate to boot either OFW of CFW.
After that the CFW is completely running independent on the emummc.
If you are not using an emummc but the SysMMC to run the CFW, then both OFW and CFW will use the internal emmc and both experience the same issues if there is something wrong with the internal emmc.
Things like data corruption affect both.

Does the following screen show anything strange?
If there is a hardware issue (like a bad connection between the emmc and mainboard) then it should also cause problems here.

You can check your battery status and health in Hekate.
Hekate boots with a dead battery, OFW and CFW does not.

Merihel · May 19, 2026

Hello, thank you so much for your answer.

I do use an emuMMC and it was working without issues before the crash. Not anymore, it does the same as booting on sysMMC via CFW, semi-stock or 100% stock. I even disabled the autorcm feature to try booting normally.

I attached screenshots of Hekate showing battery health and eMMC. I don't see anything wrong but I'm not sure.

Thanks again.

Hacking Black screen - Cannot boot into Stock/Emu anymore

New Member

Well-Known Member

New Member

Attachments

Similar threads

Popular threads in this forum