sysNAND brick or is there hope?

glitcher · 2026-06-29T18:48:21+0100

l7777 said:
interesting, is that with your backup or after you've tried a rebuild? I've been playing with my own switch and got it to a state where 1e was crashing for both normal system boot and maintenance mode boot. In my case I started from 22.1 and tried to downgrade to 19 without going into maintenance mode and initializing the console. I went through several programs, 25, 39, 1e removing saves one by one to see if it would boot without initializing. Once I got to 1e I think I deleted all the system saves and that didn't work either. Starting with a fresh downgrade and using maintenance mode worked just fine every time though.

No, just Level 3 repair from NAND Fixer Pro with my own prod.keys and a downloaded Firmware (update).
So, you got into maintenance mode as shown in the video? Also on the emuNAND?
Did you also try using the tegra explorer system wipe? This also didn't work for me...

Hayato213 said:
I believe the contents should be in emuMMC/RAW1/Nintendo/Contents/

if your'e using an emuMMC, then back up the Contents folder to your PC.
emuMMC/RAW1/Nintendo/Contents/

Do you mean sd:/emuMMC/RAW1? I don't have a Nintendo or Contents folder there...
Or do you mean in the emuMMC partition? I don't have a Nintendo or Contents folder either...
Or somewhere else?

Hayato213 · 2026-06-29T18:54:33+0100

glitcher said:
I tried that: boot into hekate -> Launch emuNAND -> Hekate loading Screen -> Atmosphere screen -> when atmosphere screen is gone pressing + and - at the same time -> Switch logo appears -> Atmosphere Error from above.
What did I do wrong?

Post automatically merged: Yesterday at 5:26 PM

The Atmosphere error "2162-0002 (0x4a2)" is more detailed caused by Program ID: "010000000000001e" which is the "Account services system module". I don't have a folder called "Contents" anywhere which is the main fix to delete it.
Doe someone know how to fix that?

The 010000000000001e you are getting is it on sysnand or emunand?

glitcher · 2026-06-29T19:18:06+0100

Ok, wait, I can boot into sysNAND now!!

What I did was booting the following boot entry (as I think Atmosphere on sysNAND):

Code:

[Atmosphere PKG3 sysMMC]
pkg3=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp

After that I could boot and set up the Console and after that I can also boot sysNAND now without Atmosphere

Still WiFi is not working as before but I think that's a Hardware issue...

Now I will generate a emuNAND from that!

sysNAND brick or is there hope?

Member

Newcomer

Member

Similar threads

Popular threads in this forum