Toggle sidebar

sysNAND brick or is there hope?

G

glitcher

Member
Newcomer
Level 1
Joined
Dec 28, 2025
Messages
12
Reaction score
0
Trophies
0
XP
21
Country
Austria
Hi all!

I have a Switch Mariko which has a sysNAND whch (was or is) on FW11 which I did not boot for about 5 years.
The sysNAND booted to the second N* Switch logo and stuck there.
I deleted my FW19 emuNAND to make a fresh install not knowing that my stock FW is not booting.
Therefore I need to re build the sysNAND!

I tried using NAND Fix Pro with the Level 2 rebuild which did not help (same issue) and then I tried FW19 instead, using the same method. It only shows black screen after that and the HW info in Hekate shows "Burnt Fuses (ODM 7/6): 20 - 0 (HOS: Unknown)". I dont know if this just means boot is broken or a larger issue.

Then I tried Level 3, but I have ancient pros.keys from FW11 only, which is recognized as encrypted.

What can I do now? How do I resotre my sysNAND?
An alternative method I would accept is only having an emuNAND. Is it possible to generate one even if sysNAND is broken?

I would be glad for any help!
 
glitcher said:
Yes sure, I did so! But I can only extract from FW11 because that is what my sysNAND is (was) on. I tried again which resulted in the same file (only 200 lines)...
Click to expand...

I guess lockpick_rcm think you are firmware 11, and hekate doesn't know your firmware even though fuse count 20. A proper NAND backup would have solve all your problems, you could have just restore your emunand nand on to sysnand though.
 
Hayato213 said:
I guess lockpick_rcm think you are firmware 11, and hekate doesn't know your firmware even though fuse count 20. A proper NAND backup would have solve all your problems, you could have just restore your emunand nand on to sysnand though.
Click to expand...
Yes that would be the easy solution, sadly I did everything wrong with that console...

I tried the "EmmcHaccGen.GUI" and generated a new FW using a stock FW19 and flashed it using lockpick. At least it shows the first logo and then only the black screen.

The fuses are now "ODM 7/6: 20|0 - HOS: 19.0.0 - 19.0.1". Seems better.

What does the black screen mean?
 
glitcher said:
Yes that would be the easy solution, sadly I did everything wrong with that console...

I tried the "EmmcHaccGen.GUI" and generated a new FW using a stock FW19 and flashed it using lockpick. At least it shows the first logo and then only the black screen.

The fuses are now "ODM 7/6: 20|0 - HOS: 19.0.0 - 19.0.1". Seems better.

What does the black screen mean?
Click to expand...

Normally it is just something wrong with the NAND. I mean you can try again to see if lockpick_rcm give you the keys then try level 3 again.
 
Will it go into maintenance mode (hold volume + & - together on boot)? You can try to factory reset from there. Wait, you have a mariko unit. That means you have to have a mod chip. Fuse mismatch shouldn't matter to CFW. Does sysCFW not work?
 
Hayato213 said:
Normally it is just something wrong with the NAND. I mean you can try again to see if lockpick_rcm give you the keys then try level 3 again.
Click to expand...
Sadly, the Switch seems to need a first boot to convert the prod.keys, because it's still the same file and NAND fix pro still thinks it's encrypted...
Post automatically merged:

l7777 said:
Will it go into maintenance mode (hold volume + & - together on boot)? You can try to factory reset from there. Wait, you have a mariko unit. That means you have to have a mod chip. Fuse mismatch shouldn't matter to CFW. Does sysCFW not work?
Click to expand...
I tried, but when doing that it just boots into Hekate...
I also tried a factory reset using Tegra Explorer without success.
 
glitcher said:
Sadly, the Switch seems to need a first boot to convert the prod.keys, because it's still the same file and NAND fix pro still thinks it's encrypted...
Post automatically merged:


I tried, but when doing that it just boots into Hekate...
I also tried a factory reset using Tegra Explorer without success.
Click to expand...
You're pressing the buttons too early if it goes to hekate. Set a boot delay of 2 seconds if you don't already have one, once the Hekate boot screen disappears that's when you press and hold the buttons.
 
l7777 said:
You're pressing the buttons too early if it goes to hekate. Set a boot delay of 2 seconds if you don't already have one, once the Hekate boot screen disappears that's when you press and hold the buttons.
Click to expand...
I have a boot delay of 3s and it just boots into Hekate, guess there is no recovery partition...
I managed to get through Level 3 recovery!
But it does not boot at all.

When I select Tools -> Restore eMMC -> eMMV Boot0 & BOOT1, then I am getting the warning "Size of the SD Card Backup does not match eMMC's selected part size!". I guess this is a main issue? (I justed proceeded which obvoiusly did not work)

I have the following partitions and sizes:
eMMC Physical Partitions:
1: BOOT0 Size: 4096 KiB Sectors: 0x00002000
2: BOOT1 Size: 4096 KiB Sectors: 0x00002000
3: RPMB Size: 16384 KiB Sectors: 0x00008000
0: GPP Size: 29820 MiB Sectors: 0x03A3E000

GPP (eMMC USER) Partition Table:
Idx Name Size Offset Sectors
00 PRODINFO 3 MiB 22h 1FDEh
01 PRODINFOF 4 MiB 2000h 2000h
02 BCPKG2-1-Normal-Main 8 MiB 4000h 4000h
03 BCPKG2-2-Normal-Sub 8 MiB 8000h 4000h
04 BCPKG2-3-SafeMode-Main 8 MiB C000h 4000h
05 BCPKG2-4-SafeMode-Sub 8 MiB 10000h 4000h
06 BCPKG2-5-Repair-Main 8 MiB 14000h 4000h
07 BCPKG2-6-Repair-Sub 8 MiB 18000h 4000h
08 SAFE 64 MiB 1C000h 20000h
09 SYSTEM 2560 MiB 3C000h 50000h
10 USER 26624 MiB 53C000h 340000h

Is something wrong with the partitions? Maybe old FW11 partition sizes?
Post automatically merged:

I had little progress. I was able to create an emuNAND with FW21.
I can boot Atmosphere and after the N Switch logo, error "2162-0002 (0x4a2)" occurs. How do I fix that, what's the issue?

What I did to recover is creating a new emuMMC and using NAND Fixer Pro in Level 3 to restore the emuNAND...
 
Last edited by glitcher,
Maintenance mode is started after the atmosphere logo and Nintendo logo. If you're seeing hekate, you're pressing the volume buttons too early. Wait until you see the atmosphere logo then hold.

 
l7777 said:
Maintenance mode is started after the atmosphere logo and Nintendo logo. If you're seeing hekate, you're pressing the volume buttons too early. Wait until you see the atmosphere logo then hold.

Click to expand...

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?
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Emulation Homebrew PS1/2 Emulator  ARMSX2-NX Initial Release

Homebrew Homebrew game  Half Life 2 (Source Engine) - Switch Port

Homebrew Homebrew game  GTA: Chinatown Wars - Switch port

Feedback Homebrew  Essential Homebrew

Homebrew Homebrew game  Lego Star Wars: The Complete Saga · Switch Port

Homebrew Homebrew game Project  So... Dan didn't want to reveal his Vulkan, so I made mine.

Homebrew Homebrew game  Chrono Trigger - Switch port

Homebrew Homebrew game  Final Fantasy IV 3D Remake - Switch port