And, after the 3DS got its recent system update, this time it looks like it's the Switch's turn. Firmware 9.1.0 has been released by Nintendo for all regions and the changelog states it's meant to fix an issue with the colour animation not showing correctly when attaching a Joy-Con to the console... alongside with the usual stability. However, there may also be something else under the hood, as @SciresM has warned that TrustZone might have received an undocumented change, so current CFWs may break if you install the update.

Ver. 9.1.0 (Released December 4, 2019)

General system stability improvements to enhance the user's experience, including a solution for the following:

• Resolved an issue where the color animation was not displaying correctly when attaching a Joy-Con controller to the Nintendo Switch console.

On a Wednesday :(

Looks like TrustZone might have updated -- if it did, I'll stream diffing later tonight. https://t.co/0CfRnFkgY8

— Michael (@SciresM) December 5, 2019

​

Needless to say, given those premises, it may be best to avoid updating for the moment if you're running a CFW or if you wish to mod your console. Not much else is known at the time of writing - this post will be updated with any useful hacking and homebrew-related info.

EDIT: For devs (and the curious), a summary of the TrustZone changes by SciresM found in FW 9.1.0 is now available here.

EDIT 2: SX OS, Atmosphère and Hekate have all been updated to support firmware 9.1.0 since then.

Source

 

[hallo23]

So, is it safe to update my Sysnand to 9.1.0 and keep my emunand on 9.0.1? My sysnand is 100% clean and I use it for online with my legit games.......

It seems like won't be able to launch stock if you update.
Atleast when I try to launch stock through hekate it just sends me back to the hekate menu.

Wonder if there is another way to launch stock without hekate.

 

[s0litary]

If you don't use auto rcm, you can just launch stock by rebooting, no?

 

[johnma2]

Messing up with your switch without backups is like having bareback with a hooker and expecting no STI

Yeah, about that... could we move on from criticism and actually look for methods that help please?

It seems like won't be able to launch stock if you update.
Atleast when I try to launch stock through hekate it just sends me back to the hekate menu.

Wonder if there is another way to launch stock without hekate.

You can still launch stock after the update, but you can't launch CFW. You also have to boot normally without trying through hekate.

 

[johnma2]

Master key is obviously what I'm talking about since the topic/convo is about 9.1.0 content games dlc and updates. Here I'll even be more specific.. it's the key that can be used for piracy and isn't allowed to be shared here.

Okay, well, I believe I have my master key. However, I believe my problem might just be in the boot partitions being corrupted. So if there is a way to restore those by using the firmware update package then I might have a chance of getting it back online. Sorry, forgot to put this bit into my last post.

 

[MasterJ360]

Okay, well, I believe I have my master key. However, I believe my problem might just be in the boot partitions being corrupted. So if there is a way to restore those by using the firmware update package then I might have a chance of getting it back online. Sorry, forgot to put this bit into my last post.

A dumped Master key is only needed for those not on the latest firmware, but want to keep playing newer games when building or converting xci and nsp game packages. I have no knowledge of the boot issue since I never update unitl cfw is supported and this is the 1st time Ive heard of something like this from just updating to a newer firm.

 

[Flora Cherry]

u_u i got the joycon drift i press update by error

 

[NovaXoXO]

Updated my firmware to 9.1.0.
Emunand works fine as long as you dont update and keep it offline.

(if you dont have emunand, install it before updating & keep it on airplane mode )
also, if you already have the update prompt, booting into your emunands recovery and shutting down will remove the prompt.

currently:
sysnand OFW: 9.1.0 | emunand CFW: 9.0.1 E

i've also gone online with my official firmware while keeping emunand offfline and no issues at all
-though i only use homebrew to back up my saves to my PC-

your experience may differ.

 

[hallo23]

You can still launch stock after the update, but you can't launch CFW. You also have to boot normally without trying through hekate.

The thing is I updated without burning fuses. If I would just boot up the switch without entering RCM/hekate first the fuses would be bruned.
So I need a way to launch the sysnand with activating the nintendo bootloader which burns the fuses.

 

[deSSy2724]

Updated my firmware to 9.1.0.
Emunand works fine as long as you dont update and keep it offline.

(if you dont have emunand, install it before updating & keep it on airplane mode )
also, if you already have the update prompt, booting into your emunands recovery and shutting down will remove the prompt.

currently:
sysnand OFW: 9.1.0 | emunand CFW: 9.0.1 E

i've also gone online with my official firmware while keeping emunand offfline and no issues at all
-though i only use homebrew to back up my saves to my PC-

your experience may differ.

So, can you confirm...... can we boot the latest stock firmware from Hekate/SX OS menu (any non official bootloader)? The thing is, I have no burnt fuses and I would like to keep it that way, so, using a official bootloader is no option for me.

 

[MasterJ360]

So, can you confirm...... can we boot the latest stock firmware from Hekate/SX OS menu (any non official bootloader)? The thing is, I have no burnt fuses and I would like to keep it that way, so, using a official bootloader is no option for me.

Aslong you have AutoRCM enabled it will prevent burnt fuses. You already burnt fuses if you updated the stock firmware from Nintendo.

 

[deSSy2724]

Aslong you have AutoRCM enabled it will prevent burnt fuses. You already burnt fuses if you updated the stock firmware from Nintendo.

Nope, still no burnt fuses..... Im updating the official way and I never used AutoRCM, basically all you need to do is holding down the "volume +" key after the update is installed (before the console restarts). ofc, the jig needs to be inserted before this.

 

[hallo23]

Aslong you have AutoRCM enabled it will prevent burnt fuses. You already burnt fuses if you updated the stock firmware from Nintendo.

The fuses are burnt the moment after you restart the Switch and the offical Nintendo bootloader loads the sysNand.
With this Method you can update your sysNand without bruning fuses: https://gbatemp.net/threads/an-easy...ch-firmware-without-burning-any-fuses.511847/

 

[deSSy2724]

No need to keep messsing with enabling/disabling AutoRCM....... you only need to boot to stock from a 3rd party bootloader and not let the Switch restart without pressing the "volume +" key if you are updating the stock firmware the official way, thats all you need to do.

 

[MasterJ360]

The fuses are burnt the moment after you restart the Switch and the offical Nintendo bootloader loads the sysNand.
With this Method you can update your sysNand without bruning fuses: https://gbatemp.net/threads/an-easy...ch-firmware-without-burning-any-fuses.511847/

Yeah AutoRCM is the best way to handle this b/c your switch wont boot to stock or cfw unless you inject a payload.
Without AutoRCM enabled you can accidentally power on the switch and then your fucked b/c fuses are burned.

 

[NovaXoXO]

So, can you confirm...... can we boot the latest stock firmware from Hekate/SX OS menu (any non official bootloader)? The thing is, I have no burnt fuses and I would like to keep it that way, so, using a official bootloader is no option for me.

for me Booting to stock OFW works without TegraRCM as it naturally does, with RCM once i'm in the bootloader i can access Emunand. I have not tried booting to OFW or CFW on sysnand through bootloader since it's made clear that 9.1.0 is currently a CFW killer .

-my emunand is on 9.0.1 cfw since I set it up prior to updating-

(idk about any technical aspects, i'm just reporting whats working on my end)

 

[s0litary]

Yeah AutoRCM is the best way to handle this b/c your switch wont boot to stock or cfw unless you inject a payload.
Without AutoRCM enabled you can accidentally power on the switch and then your fucked b/c fuses are burned.

Why do fuses still matter with an unpatched Switch? The exploit is on a hardware level anyways, and it doesn't matter what firmware your OFW is on.

Just trying to understand...

 

[grcd]

Why do fuses still matter with an unpatched Switch? The exploit is on a hardware level anyways, and it doesn't matter what firmware your OFW is on.

Just trying to understand...

I suppose not burning the fuses gives you the versatility of being able to go back to previous firmware versions without problems on your SYSNAND? I think effectively you get to keep your options open about downgrading, which is always better than being permanently stuck in a higher firmware.

 

[MasterJ360]

Why do fuses still matter with an unpatched Switch? The exploit is on a hardware level anyways, and it doesn't matter what firmware your OFW is on.

Just trying to understand...

It matters to ppl who want to preserve the ability to coldboot in the future while older firmwares will have a better chance for that support.
As grcd states switching to different firms gives you more control over your switch in case a newer firm may break certain homebrew apps or a custom theme stops working properly. You can simply go back to an older firm when it was compatible.

 

[deSSy2724]

Why do fuses still matter with an unpatched Switch? The exploit is on a hardware level anyways, and it doesn't matter what firmware your OFW is on.

Just trying to understand...

Simple answer..... why not? And because it can be done.

Having more options is always better than having only one option.... im just looking/waiting for a better coldboot method. I know that we have some coldboot and warmboot methods but in its current state its not something I want to use....

 

[StealthRoaR]

seems there is a Pre-release supporting 9.1.0 FW

see Atmosphère 0.10.0 github