sysNAND brick or is there hope?

glitcher · 2026-06-26T22:27:20+0100

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!

raphaeld82 · 2026-06-26T22:46:01+0100

So you updated the switch sysnand successfully to 19? Besides the black screen afterwards.

glitcher · 2026-06-26T22:47:49+0100

I have no idea, because it's not booting... Can i check that?

Hayato213 · 2026-06-26T22:48:28+0100

No NAND backup?

glitcher · 2026-06-26T22:54:56+0100

Sadly not, I would restore if I would have been more careful...

Hayato213 · 2026-06-26T22:56:56+0100

glitcher said:
Sadly not, I would restore if I would have been more careful...

You can try lockpick_rcm see if you can get a more updated keys list. Fuses count 20 expect firmware 19.0.0 and 19.0.1

glitcher · 2026-06-26T22:59:18+0100

I am only able to access the sysNAND FW11 where I have the prod.keys from using lockpick...

Hayato213 · 2026-06-26T23:00:30+0100

glitcher said:
I am only able to access the sysNAND FW11 where I have the prod.keys from using lockpick...

Lockpick now can be run via hekate nowadays

glitcher · 2026-06-26T23:05:11+0100

Hayato213 said:
Lockpick now can be run via hekate nowadays

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)...

Hayato213 · 2026-06-26T23:08:48+0100

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)...

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.

glitcher · 2026-06-26T23:19:02+0100

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.

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?

Hayato213 · 2026-06-26T23:21:49+0100

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?

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.

sysNAND brick or is there hope?

Member

Member

Member

Newcomer

Member

Newcomer

Member

Newcomer

Member

Newcomer

Member

Newcomer

Similar threads

Popular threads in this forum