Tesla-Menu VS Payload_Launcher

Install Tesla Menu https://github.com/WerWolv/Tesla-Menu

I believe 420000000007E51A is the Tesla overlay and nx-ovlloader. Try updating them from https://github.com/WerWolv/nx-ovlloader and https://github.com/WerWolv/Tesla-Menu or delete /atmosphere/contents/420000000007E51A and /switch/.overlays/ovlmenu.ovl.

try this i just seen that what you posted that page was last updated in january so its always best to check each github https://github.com/WerWolv/Tesla-Menu/releases

https://github.com/WerWolv/Tesla-Menu Tesla-Menu

update the overlay. https://github.com/WerWolv/Tesla-Menu/releases/tag/v1.2.1

Basically you have nintendo dns blocked if you've done things properly, but that includes the ntp server which sets your system time. There is a Tesla plugin called QuickNTP which can act as a simple replacement.

For updating Atmosphere itself, I recommend installing the Payload Launcher homebrew so you can get back to Hekate. From there, you can use Hekate's USB feature.

Payload Launcher - hijacks Atmosphere's "reboot to payload" function to launch user-defined payloads

Payload Launcher This is effectively a non-Tesla-based way to switch between payloads. Probably not super useful if you're going to lean into Tesla.

If you never shut the Switch all the way off, then you don't 100% require the jig; you can reboot between payloads using the Payload Launcher homebrew.

You can in fact do so with the Payload Launcher homebrew, actually.

Payload Launcher to simplify moving from one environment to another

You can use the Payload Launcher to reboot to a given payload file directly from Atmosphere. Additionally, Atmosphere allows you to name a payload file reboot_payload.bin and reboot to it from the Switch's menu.

Then you can grab the Payload Launcher homebrew to get around the fact that you can't use Hekate to swap between sysNAND and emuNAND.

Alternately, you can use this tool to do it.