I did a system update on the sysNAND of my modchipped Switch Lite. Got a bluescreen.
Lemme try to explain:
I have a Switch Lite with a soldered modchip. It was running atmosphere.
Today I booted into clean sysNAND to unlink my Nintendo Account.
The console told me to do a system update before I can access eshop.
So I did that. And now I can still boot into hekate, but trying to boot sysNAND gives me a bluescreen.
I have a clean NAND backup of my console, but that was before the system update burned fuses.
I'm sure there is a way to rescue the console as hekate still works, but I'll ask for advice before I try something stupid and ruin it completely.
If anybody has an idea what I could do I'd absolutely appreciate your help.
I wish I had never tried to update the console, it was working fine before I did. :-/
Edit:
Do I need to recreate/replace boot0 of Firmware 13.2.0? Could it be that I corrupted boot0?
Lemme try to explain:
I have a Switch Lite with a soldered modchip. It was running atmosphere.
Today I booted into clean sysNAND to unlink my Nintendo Account.
The console told me to do a system update before I can access eshop.
So I did that. And now I can still boot into hekate, but trying to boot sysNAND gives me a bluescreen.
I have a clean NAND backup of my console, but that was before the system update burned fuses.
I'm sure there is a way to rescue the console as hekate still works, but I'll ask for advice before I try something stupid and ruin it completely.
If anybody has an idea what I could do I'd absolutely appreciate your help.
I wish I had never tried to update the console, it was working fine before I did. :-/
Edit:
Do I need to recreate/replace boot0 of Firmware 13.2.0? Could it be that I corrupted boot0?
Attachments
Last edited by Reynardine,