Nintendo switch wont start after NAND reset

[Yoshi_yogurt]

I followed the homebrew guide on my unpatched Switch and it went smoothly. Then I installed Tinfoil and NUT to transfer games until I realized that the Tinfoil was installed on sysMMC and not emuMMC. I connected to the Wi-fi, but I did not opened E-shop.

I decided to reset the NAND and it went well. I followed the guide again but when I uppdated Hekate and Atmosphere and rebooted the switch it wont turn on.

I have tried regular and hard reset using the power button. When I place it in the dockstation, the green light blink/flash one fast time. I also tried disconnect the battery but the problem still remains.

Anyone have and idea what I can do or had similar problem?

 

[Yoshi_yogurt]

I managed to fix the problem by trying to access the RCM multiple times and inject Hekate payload!

But I ran into another problem, I cant access stock firmware. When I shut down the switch and start it again, it shows only a black screen.

 

[Hayato213]

You factory reset the switch ?

 

[Yoshi_yogurt]

You factory reset the switch ?

No, I just restored the NAND backup according to the NH switch guide " Restore a NAND backup to the switch".

 

[Hayato213]

No, I just restored the NAND backup according to the NH switch guide " Restore a NAND backup to the switch".

What is your fuse count and the firmware the system is on?

 

[Yoshi_yogurt]

What is your fuse count and the firmware the system is on?

The firmware is 16.0.3 (uppdated by transfer the file via usb). Not sure how to check that, I checked "Hw & fuses info" and it says " burnt fuses (odm 7/6)".

 

[Hayato213]

The firmware is 16.0.3 (uppdated by transfer the file via usb). Not sure how to check that, I checked "Hw & fuses info" and it says " burnt fuses (odm 7/6)".

It should boot ofw if you are on 16.0.3

 

[Yoshi_yogurt]

It should boot ofw if you are on 16.0.3

The fw 16.0.3 is on the emuNand. I thinks it a earlier version on stock but cant check it since I cant access it.

 

[a_username_that_is_cool]

The fw 16.0.3 is on the emuNand. I thinks it a earlier version on stock but cant check it since I cant access it.

You will have to be very fast with this to not be banned. In fact, you might get banned anyway.
Go to CFW on sysMMC. Then upgrade to 16.0.3.
Reboot. Try to go into stock.
If it didn't work, I don't know

 

[Hayato213]

The fw 16.0.3 is on the emuNand. I thinks it a earlier version on stock but cant check it since I cant access it.

If you are on a lower firmware for sysnand and the fuse count is for 16.0.3 it would explain why it won't boot OFW.

 

[Yoshi_yogurt]

You will have to be very fast with this to not be banned. In fact, you might get banned anyway.
Go to CFW on sysMMC. Then upgrade to 16.0.3.
Reboot. Try to go into stock.
If it didn't work, I don't know

I will do it. So you mean only on CFW sysNAND and not stock?

Do I get banned even if I not connected to internet/wifi?

Post automatically merged: Aug 11, 2023

If you are on a lower firmware for sysnand and the fuse count is for 16.0.3 it would explain why it won't boot OFW.

So it means that it is not possible to boot OFW if the firmware on sysNAND is lower than emuNAND?

 

[Daaabs]

I followed the homebrew guide on my unpatched Switch and it went smoothly. Then I installed Tinfoil and NUT to transfer games until I realized that the Tinfoil was installed on sysMMC and not emuMMC. I connected to the Wi-fi, but I did not opened E-shop.

I decided to reset the NAND and it went well. I followed the guide again but when I uppdated Hekate and Atmosphere and rebooted the switch it wont turn on.

I have tried regular and hard reset using the power button. When I place it in the dockstation, the green light blink/flash one fast time. I also tried disconnect the battery but the problem still remains.

Anyone have and idea what I can do or had similar problem?

I have the exact same problem. Accidentally overwrote the (version 16) sysMMC with the files of a (version 13) emuMMC. Tried overwriting it with the original NAND backup but that was version 13 too and didn't help at all. Totally blank and unresponsive. Still boots into RCM, thank god, but Hekate says that 7/6 fuses have been burnt. Did you manage to fix it?

 

[Hayato213]

I have the exact same problem. Accidentally overwrote the (version 16) sysMMC with the files of a (version 13) emuMMC. Tried overwriting it with the original NAND backup but that was version 13 too and didn't help at all. Totally blank and unresponsive. Still boots into RCM, thank god, but Hekate says that 7/6 fuses have been burnt. Did you manage to fix it?

What is your fuse count?

 

[Daaabs]

What is your fuse count?

Hekate says:

Burnt Fuses (ODM 7/6): 18-0 (HOS: 16.0.0+)

I don't really know what that means though

 

[Hayato213]

Hekate says:

Burnt Fuses (ODM 7/6): 18-0 (HOS: 16.0.0+)

I don't really know what that means though

It expect firmware 16.0.0 to 16.1.0, it would explain why if you restore a lower firmware why it won't boot. If you boot with hekate does it boot?

 

[Daaabs]

It expect firmware 16.0.0 to 16.1.0, it would explain why if you restore a lower firmware why it won't boot. If you boot with hekate does it boot?

No, I can boot into Hekate via RCM but if I try to boot the stock OS from Hekate it goes blank/unresponsive.

Would it help if I used Hekate to flash an updated (16.1.0) emuMMC over the sysMMC?

 

[Hayato213]

No, I can boot into Hekate via RCM but if I try to boot the stock OS from Hekate it goes blank/unresponsive.

Would it help if I used Hekate to flash an updated (16.1.0) emuMMC over the sysMMC?

You can try.

 

[Yoshi_yogurt]

No, I can boot into Hekate via RCM but if I try to boot the stock OS from Hekate it goes blank/unresponsive.

Would it help if I used Hekate to flash an updated (16.1.0) emuMMC over the sysMMC?

Did you manage to fix it? How did you do?