A brand new system software update has been released. Nintendo has just put out a milestone firmware release for the Nintendo Switch, bringing the OFW to 19.0.0. Despite the version number, it seems that this new update is purely focused on stability. That means support for custom firmware Atmosphere has been broken for now, with SciresM planning on fixing things in the next few days.

Failed to fetch tweet https://twitter.com/SciresM/status/1843443316446376123

Source

 

[NinStar]

OLED, with a chip - I updated sysNand to 19.0 accidentally (not whiled running cfw, just on stock playing Zelda) and can't boot into it even with this method. I can successfully get into hekate and boot emunand on 18.1, but it seems I've been completely locked out even from the stock OS on my Switch. Hopefully atmosphere/hekate updating fixes it? Unless I'm doing something wrong…

That's strange, booting into stock with the original bootloader shouldn't depend on Hekate or Atmosphere at all. Mine also has a modchip (it is a regular LCD Mariko), I also updated it without running cfw on sysnand and the current fuse count is 20 and it works fine without using Hekate.

I'm assuming your fuse count is somehow higher than expected, and from what I know (someone more experienced than me can correct me) it will always crash the original bootloader.

 

[JVG]

That's strange, booting into stock with the original bootloader shouldn't depend on Hekate or Atmosphere at all. Mine also has a modchip (it is a regular LCD Mariko), I also updated it without running cfw on sysnand and the current fuse count is 20 and it works fine without using Hekate.

I'm assuming your fuse count is somehow higher than expected, and from what I know (someone more experienced than me can correct me) it will always crash the original bootloader.

How can I check my fuse count? Really hoping this isn’t a permanent issue…

 

[NinStar]

How can I check my fuse count? Really hoping this isn’t a permanent issue…

In Hekate, go to Console Info > HW & Fuses, check the line that says "Burnt Fuses", it should the 4th line on the left side of the screen, the actual count is the text in white, that number should be 20.

 

[JVG]

In Hekate, go to Console Info > HW & Fuses, check the line that says "Burnt Fuses", it should the 4th line on the left side of the screen, the actual count is the text in white, that number should be 20.

19 | 0 - HOS: 17.0.0+

So still not sure why I can’t boot OFW

 

[NinStar]

19 | 0 - HOS: 17.0.0+

So still not sure why I can’t boot OFW

Somehow your Switch isn't burning an additional fuse, it has to be 20 in order to boot 19.0.0 without using Hekate bootloader. I don't really know how to help with that.

 

[frankGT]

switchFuseContext.addBurning(1);

 

[rodrigues14]

Someone managed to fix the right ES and FS patches for FW 19?

 

[JVG]

Somehow your Switch isn't burning an additional fuse, it has to be 20 in order to boot 19.0.0 without using Hekate bootloader. I don't really know how to help with that.

Oh no I hope I'm not totally screwed

 

[kcmando]

creator is going to release a pre release friday if all seems good he said

 

[TankedThomas]

To use the original bootloader you just have to do what @LuigiGad said, while in the Hekate home screen you select Reboot -> OFW, if you are using a modchip you can also do that by holding the volume buttons while turning on the console.

I'm using a modchip. I tried that but it doesn't seem to work. Seems I have the same problem as @JVG since I only have 19 fuses burnt. Not sure if there's a way to burn them manually or if I even should try.
Oh well, guess I'll just keep waiting.

Would be nice if I could fix the errors on emuMMC though. Apparently it's because I'm using emummc.txt for my hosts file instead of default.txt (since I want connectivity on SysMMC). Guess there's not much I can do but put up with it, since I don't use emuMMC much anyway.

 

[LuigiGad]

I'm using a modchip. I tried that but it doesn't seem to work. Seems I have the same problem as @JVG since I only have 19 fuses burnt. Not sure if there's a way to burn them manually or if I even should try.
Oh well, guess I'll just keep waiting.

Would be nice if I could fix the errors on emuMMC though. Apparently it's because I'm using emummc.txt for my hosts file instead of default.txt (since I want connectivity on SysMMC). Guess there's not much I can do but put up with it, since I don't use emuMMC much anyway.

you could solve the e-fuse problem by creating a complete nand but with the correct version for your e-fuses. then you update officially by making the e-fuses burn correctly

 

[froggy55]

That's strange, booting into stock with the original bootloader shouldn't depend on Hekate or Atmosphere at all. Mine also has a modchip (it is a regular LCD Mariko), I also updated it without running cfw on sysnand and the current fuse count is 20 and it works fine without using Hekate.

I'm assuming your fuse count is somehow higher than expected, and from what I know (someone more experienced than me can correct me) it will always crash the original bootloader.

hello there there is an alternate way to boot to stock when in hekate on the lower right had side of the screen press reboot then select OFW it will then boot onto stock mode i had this problem when i accidently updated to firmware 17.0 to soon but since then i have learned my lesson and pay attention to what i am doing on my switch i hope this helps

 

[TankedThomas]

you could solve the e-fuse problem by creating a complete nand but with the correct version for your e-fuses. then you update officially by making the e-fuses burn correctly

Sounds risky. Not sure how to do change the e-fuse count on a NAND image anyway.

hello there there is an alternate way to boot to stock when in hekate on the lower right had side of the screen press reboot then select OFW it will then boot onto stock mode i had this problem when i accidently updated to firmware 17.0 to soon but since then i have learned my lesson and pay attention to what i am doing on my switch i hope this helps

The issue is an unburnt fuse, so that won't work. I assume it's because we updated on Sys CFW (at least, I did).

I figure booting into recovery mode and forcing the update again once Hekate and Atmosphere are updated will probably solve it, but I'm not sure. Haven't managed to find anyone else with this issue other than the two of us, but I figure it's probably more common than it seems.

 

[Exnor]

Then please, by all means, debunk it. Not a fan of people who make these types of comments because they add nothing to the argument.

Even if the eShop is somehow a web browser, how is that an excuse ?

It's a lousy excuse that's what it is.

In comparison the 3DS eShop worked better ffs .

 

[froggy55]

Sounds risky. Not sure how to do change the e-fuse count on a NAND image anyway.


The issue is an unburnt fuse, so that won't work. I assume it's because we updated on Sys CFW (at least, I did).

I figure booting into recovery mode and forcing the update again once Hekate and Atmosphere are updated will probably solve it, but I'm not sure. Haven't managed to find anyone else with this issue other than the two of us, but I figure it's probably more common than it seems.

ok yes when i accidently updated to soon i was in stock mode not in sys cfw all i know is when i accidently updated i could no longer boot into stock from the launch menu and someone on this forum directed me to use the reboot function in hekate so i did and for me it worked i will admit i dont know about burnt fuses or what is even about cuz i dont know what the fuseses are that are being talked about in the switch

 

[NinStar]

ok yes when i accidently updated to soon i was in stock mode not in sys cfw all i know is when i accidently updated i could no longer boot into stock from the launch menu and someone on this forum directed me to use the reboot function in hekate so i did and for me it worked i will admit i dont know about burnt fuses or what is even about cuz i dont know what the fuseses are that are being talked about in the switch

Fuses are used by Nintendo to prevent firmware downgrades, every time you boot the console using the original bootloader (i.e. using the reboot function you mentioned), the console checks how many fuses are burnt, if it is less than expected, it will burn all the necessary fuses until the count matches the current firmware (firmware 19.0.0 expects that count to be 20) and proceeds to boot, if the number is higher or for some reason remains below expected after that process it will refuse to boot at all.

As far as I know, booting into anything (sysCFW, emuCFW or OFW) using the hekate bootloader prevents fuses from being burn.

 

[froggy55]

Fuses are used by Nintendo to prevent firmware downgrades, every time you boot the console using the original bootloader (i.e. using the reboot function you mentioned), the console checks how many fuses are burnt, if it is less than expected, it will burn all the necessary fuses until the count matches the current firmware (firmware 19.0.0 expects that count to be 20) and proceeds to boot, if the number is higher or for some reason remains below expected after that process it will refuse to boot at all.

As far as I know, booting into anything (sysCFW, emuCFW or OFW) using the hekate bootloader prevents fuses from being burn.

thank you for the explanation ive always wondered what people were talking about when they would refere to fuses now i have a better understanding

 

[linuxares]

I wonder how much this update will break and how much need to be rebuilt.


https://x.com/SciresM/status/1844582911976275995
https://x.com/SciresM/status/1844587366234849652

 

[M7L7NK7]

There's already a testing version that works

 

[update-freak]

Does this mean due to Ryujinx did not get any updates it is not recommended to install the v19 because then Atmosphere mod for e.g. Mario Kart CTGPDX does not work anymore?