Help needed: Black screen after nintendo logo on sysnand

cputime · 2026-09-04T17:06:25+0100

Hi all,

I have an unmatched v1 Switch.
I almost only used it with CFW on emunand from day one.
Today I wanted to transfer a save from it to my Switch 2.
To do so I first booted the sys and on CFW and used jksv.
I then reboot on OFW and connected to wifi and try to associate an account . I got asked to update and so I did.

Upon reboot the screen now stays black after the Nintendo logo.

I've got a nand backup from 2018 but I can't remember which version it was.
What are my options here?
Should I try restoring the backup ?
What about the fuse count? I imagine it would have been updated running the update .

On hekate I've got:
Burnt fuses odm 7/6 : 23 ¦ 0 Hos: unknown

Why is it unknown ?

I tried booting CFW on sys and and got:
Unkown pkg1 version
Hos version unsupported

And same with backup bootloader

Any help is appreciated , thanks

Hayato213 · 2026-09-04T17:16:40+0100

Fuse count 23 expect firmware 22.0.0-22.5.0, since it says unknown the system doesn't know what firmware it is on.

If you are on older Atmosphere and Hekate file you can try updating the files see if it help it boot.

impeeza · 2026-09-04T17:22:07+0100

cputime said:
Hi all,

I have an unmatched v1 Switch.
I almost only used it with CFW on emunand from day one.
Today I wanted to transfer a save from it to my Switch 2.
To do so I first booted the sys and on CFW and used jksv.
I then reboot on OFW and connected to wifi and try to associate an account . I got asked to update and so I did.

Upon reboot the screen now stays black after the Nintendo logo.

I've got a nand backup from 2018 but I can't remember which version it was.
What are my options here?
Should I try restoring the backup ?
What about the fuse count? I imagine it would have been updated running the update .

On hekate I've got:
Burnt fuses odm 7/6 : 23 ¦ 0 Hos: unknown

Why is it unknown ?

I tried booting CFW on sys and and got:
Unkown pkg1 version
Hos version unsupported

And same with backup bootloader

Any help is appreciated , thanks

Upgrade your CFW by upgrading hekate and atmosphère, remember to disable or update all sysmodules you have.

cputime · 2026-09-04T17:56:03+0100

OK I'll try updating atmosphere and hekate and report back.
But wouldn't that only help with CFW? It's OFW I want to fix more importantly

impeeza · 2026-09-04T18:19:15+0100

cputime said:
OK I'll try updating atmosphere and hekate and report back.
But wouldn't that only help with CFW? It's OFW I want to fix more importantly

it affects OFW if you boot using a payload. the only way to boot OFW is a clean boot the console without injecting a payload.

If you boot using a injected payload Hekate/atmosphère must be updated to run OFW because is not pure OFW

cputime · 2026-09-04T18:24:13+0100

Resolved thanks.

I updated

impeeza said:
it affects OFW if you boot using a payload. the only way to boot OFW is a clean boot the console without injecting a payload.

If you boot using a injected payload Hekate/atmosphère must be updated to run OFW because is not pure OFW

I didn't inject payload when booting OFW.
I thought that's what it means Original firmware => without any payload.

Anyway thanks guys, I don't exactly understand :

I updated hekate and atmosphere then booted sysnand with CFW.
and when I rebooted without a payload it works again.
no idea why but it works.
thanks

Hayato213 · 2026-09-04T19:09:29+0100

It didn't successfully boot that why the system doesn't know the system firmware, fuse count 23 can be from 22.0.0 to 22.5.0

Help needed: Black screen after nintendo logo on sysnand

Member

Attachments

Newcomer

¡Kabito!

Member

¡Kabito!

Member

Newcomer

Similar threads

Popular threads in this forum