SysNAND on 11.0.1

[dbrown1986]

I'm working on a switch that is still on 11.0.1 SysNAND (friend has always used EmuNAND and updates EmuNAND with Daybreak).
He updated SysNAND at some point to 11.0.1 and had not heard about the Xecuter bust at the time.
My question is this, were any fuses burned between 11.0.0 and 11.0.1 and can I safely downgrade his SysNAND back to 11.0.0 and still have it boot?
He's running 13.0.0 on EmuNAND at the moment, with no fuses burned beyond 11.0.1, but he would like to preserve SX OS compatibility for his console on the SysNAND, so assuming no fuses were burned during what seems like an incremental update, this shouldn't pose any issues, correct?

 

[Hayato213]

11.0.0 and 11.0.1 share the same fuse count, so you should be fine to downgrade.

 

[Maupiti]

I'm working on a switch that is still on 11.0.1 SysNAND (friend has always used EmuNAND and updates EmuNAND with Daybreak).
He updated SysNAND at some point to 11.0.1 and had not heard about the Xecuter bust at the time.
My question is this, were any fuses burned between 11.0.0 and 11.0.1 and can I safely downgrade his SysNAND back to 11.0.0 and still have it boot?
He's running 13.0.0 on EmuNAND at the moment, with no fuses burned beyond 11.0.1, but he would like to preserve SX OS compatibility for his console on the SysNAND, so assuming no fuses were burned during what seems like an incremental update, this shouldn't pose any issues, correct?

He could also have 2 emunands, and sysnand “untouched “.

 

[binkinator]

11.0.0 and 11.0.1 share the same fuse count, so you should be fine to downgrade.

Correct, Just did this exact thing myself.

11.0.0-12.0.1 are all 14 fuses so you can go up or down within that range with zero issues.

everything you wanted to know about fuses here (see very bottom of page for fw/fuse counts):

https://switchbrew.org/wiki/Fuses