Hacking Switch seemingly bricked after attempting to upgrade firmware to 16.0.2

[N3M29]

Hello everyone. Massive noob to the scene here,


I have recently updated my atmosphere, hekate and nyx to their latest versions (1.5.2, 6.0.3 and 1.5.3 respectively.) I also downloaded the latest switch firmware (16.0.2). I launched fusee.bin and went onto daybreak in order to upgrade my firmware. After a seemingly successful update, I rebooted and was met with a fatal error screen with the code 2001-0123. I tried to reboot but was stuck in a crash loop, and I couldn't inject a payload to go back into hekate. I have since turned the console off by holding the power button and it will not turn on again. I would greatly appreciate any help in attempting to get my switch to work again.

Thank you

 

[Gazzza]

found this about the error : https://github.com/Atmosphere-NX/Atmosphere/issues/1306
is possibile that you have autorcm so you reboot in rcm and you need to inject the payload again

 

[OrGoN3]

Hello everyone. Massive noob to the scene here,


I have recently updated my atmosphere, hekate and nyx to their latest versions (1.5.2, 6.0.3 and 1.5.3 respectively.) I also downloaded the latest switch firmware (16.0.2). I launched fusee.bin and went onto daybreak in order to upgrade my firmware. After a seemingly successful update, I rebooted and was met with a fatal error screen with the code 2001-0123. I tried to reboot but was stuck in a crash loop, and I couldn't inject a payload to go back into hekate. I have since turned the console off by holding the power button and it will not turn on again. I would greatly appreciate any help in attempting to get my switch to work again.

Thank you

Show a screenshot of the error. We need the other information from the error screen that you did not already share.

 

[N3M29]

Show a screenshot of the error. We need the other information from the error screen that you did not already share.

 

[impeeza]

Backup and remove the SD:/ATMOSPHERE/CONTENTS folder you have an old sysmodule it a theme installed

 

[N3M29]

Backup and remove the SD:/ATMOSPHERE/CONTENTS folder you have an old sysmodule it a theme installed

Done. Shall I try to enter fusee.bin/emmuMMC now?

Post automatically merged: May 2, 2023

Backup and remove the SD:/ATMOSPHERE/CONTENTS folder you have an old sysmodule it a theme installed

Success! I can access fusee.bin fine now, with the latest firmware! If you may choose to enlighten me, can you explain how this sysmodule problem occured?

Thank you for the help!

 

[m00k00]

Done. Shall I try to enter fusee.bin/emmuMMC now?

Post automatically merged: May 2, 2023

Success! I can access fusee.bin fine now, with the latest firmware! If you may choose to enlighten me, can you explain how this sysmodule problem occured?

Thank you for the help!

Sysmodules often need to be changed and / or recompiled for newer firmware Versions. You probably have one ore more that's just not compatible with firmware 16.0.2! I'd recommend to update your sysmodules and read their changelogs. Hopefully most, if not all of the ones you are using, have been updated for 16.X already. Good luck!

 

[OrGoN3]

Done. Shall I try to enter fusee.bin/emmuMMC now?

Post automatically merged: May 2, 2023

Success! I can access fusee.bin fine now, with the latest firmware! If you may choose to enlighten me, can you explain how this sysmodule problem occured?

Thank you for the help!

The sysmod is Tesla. You have to make sure you are using the latest nx-ovlloader. https://github.com/WerWolv/nx-ovlloader/releases/tag/v1.0.6

On top of that, you need to make sure you're using a new version of tesla menu

Tesla-Menu with dock workaround (not the libnx fix): https://github.com/WerWolv/libtesla/files/11126965/ovlmenu.zip

Then you need to update the REST of your Tesla overlays to working versions for firmware 16.x.x and possibly preliminary docked support.

Edizon: https://github.com/proferabg/EdiZon-Overlay/releases/download/v1.0.5/EdiZon-Overlay.zip

I don't know which you use. All can be found by looking around.

 

[impeeza]

Done. Shall I try to enter fusee.bin/emmuMMC now?

Post automatically merged: May 2, 2023

Success! I can access fusee.bin fine now, with the latest firmware! If you may choose to enlighten me, can you explain how this sysmodule problem occured?

Thank you for the help!

As recently told, the module which is crashing is Tesla, when you update your Atmosphére (not matter if is because a new firmware or only a new version released) you need to update your sigpatches and look if all the homebrew need be updated too. on the case of Tesla and the OVLs all they needed new versions because a new library was released for Firmware 16.x.x support.

You can go to https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/post-10121629 and download the latest versions of Tesla, OVLMenu and the Overlays you use and update your SD Card.

More information abot sysmodules on https://rentry.org/switchHackingIsEasy