Help Accidently blue screened my switch!!!

[Hayato213]

You mean on hardware level?

You got a solid blue screen?

 

[jkyoho]

unmatch boot0/1 and fuse would also lead to blue screen from OFW boot

 

[Noobot]

You got a solid blue screen?

Yes

Post automatically merged: Apr 17, 2024

unmatch boot0/1 and fuse would also lead to blue screen from OFW boot

Is there a fix?

 

[Hayato213]

Yes

Post automatically merged: Apr 17, 2024

Is there a fix?

What is your fuse count, do you know what firmware was the nand backup from?

 

[Noobot]

What is your fuse count, do you know what firmware was the nand backup from?

The backup I think it's 16.0.1, for the fuses, I don't remember at all

 

[Hayato213]

The backup I think it's 16.0.1, for the fuses, I don't remember at all

Check hekate fuse count

 

[Noobot]

Check hekate fuse count

I looked it up on the net, but all I've found askes me to check the menu firmware first, thing that the bluescreen prevents me to do

 

[Hayato213]

I looked it up on the net, but all I've found askes me to check the menu firmware first, thing that the bluescreen prevents me to do

This is an example it will say burnt fuse, and a number, like that 8

 

[jkyoho]

If you can boot to Hekate, then you could check fuse count.
If you have prod.key backup, then you could mount your RAWNAND GPP to PC and use NxNandManager to check emmc firmware version

 

[Noobot]

NX type: Full nand
Device ID: KEYSET NEEDED!
FW version: NOT FOUND!

I guess that explains something, hopefully

 

[jkyoho]

NX type: Full nand
Device ID: KEYSET NEEDED!
FW version: NOT FOUND!

I guess that explains something, hopefully

import your prod.key

FYI: Use this NxNandManager to have FW18.0.0 support

 

[Noobot]

import your prod.key

FYI: Use this NxNandManager to have FW18.0.0 support
View attachment 432617

Done, now only the FW ver. says not found.

 

[jkyoho]

Done, now only the FW ver. says not found.

Did you download from Action or just the latest release on 2022 APRIL?

Or you can post the system versions nca file name here like this

 

[RyanTheArchivist]

You mean on hardware level?

Yes

 

[Noobot]

Did you download from Action or just the latest release on 2022 APRIL?

Or you can post the system versions nca file name here like this

View attachment 434408

 

[jkyoho]

So you are on HOS FW 18.0.0. Hekate 6.1.1 and AMS 1.7.0prelease should be able to support this verison.
I believe you need to rebuild you nand using Tegraexplorer system_wipe to FW18.0.0

 

[Noobot]

So you are on HOS FW 18.0.0. Hekate 6.1.1 and AMS 1.7.0prelease should be able to support this verison.
I believe you need to rebuild you nand using Tegraexplorer system_wipe to FW18.0.0

Is that something I can do from the pc while keeping the sd connected? Or do I have to move the sd back to the switch and do a payload to inject this program? In second case, I suppose I'll have to do tinfoil in the joycon thing. What do I do if I get just bluescreen again? After all, I already tried to use a payload, but my pc didn't found anything

 

[jkyoho]

Is that something I can do from the pc while keeping the sd connected? Or do I have to move the sd back to the switch and do a payload to inject this program? In second case, I suppose I'll have to do tinfoil in the joycon thing. What do I do if I get just bluescreen again? After all, I already tried to use a payload, but my pc didn't found anything

file transfer can be done through Hekate(even from another switch). Boot 0/1 can be generated from emmchhaccgen on PC with prod.key from the Blue screen console.
If you can't/don't know how to make unpatched switch into RCM mode, you are on your own.