Hacking Cant boot Sysnand

PrizrakSVO · Mar 26, 2026

The technician installed a Picofly chip and Atmosphere/UltraNX on my Nintendo Switch V2. Everything worked fine, but only two days later I noticed that I can't boot into full stock — neither through reboot, nor through more configs, nor by removing the SD card. I see the Nintendo logo and then a black screen. If I enable logging, I see the following before booting:

Initializing... Atmosphere 1.10.2-70007035 via PKG3 Max HOS: 21.2.0 Unpacking... Done! Found pksi <>. Unknown pksi version. HOS version not Supported! Trying backup bootloader... Found pksi <''». Unknown pksi version. HOS version noorted! Rebooting to OFW in 5s...

I tried dumping the keys again for some reason, even though the technician already did a dump before, and I get this. The keys from emuNAND dump without errors.

[Lockpick_RCM v1.9.17] MMC init... done in 11339 US Master keys... done in 3393 us BIS keys... done in 805 us Unable to read PRODINFO. Unable to derive SSL key. Unable to read PRODINFO. Unable to derive ETicket key. [FatFS] Error: BRNL Unable to mount system partition. Lockpick totally done in 814865 us Found 217 prod keys. Found through master_key_14. Wrote 12280 bytes to sd:/switch/prod.keys Press VOL+ to save a screenshot or another button to return to the menu

I want to restore sysNAND so I can play online games and avoid getting banned. What's the best way to do this? What is the problem? I don't have any backups. I have a blank 512 GB SD card, new, formatted as FAT32 — could I use that?

thesjaakspoiler · Mar 26, 2026

First thing to check if you have the latest version of Hekate/Atmosphere installed.
Using older versions with OS 21.2.0 might give you these kind of errors.

Hacking Cant boot Sysnand

New Member

Attachments

Well-Known Member

Similar threads

Popular threads in this forum