New Switch and Xecuter SX Pro setup assistance

[iamfoesho]

Hello,

I have a new Nintendo Switch with the SysNAND on version 4.0.1. I plan on using the SX Pro to create an EmuNAND that I will update to version 6.2.0 using ChoidujourNX. I don't plan on using AutoRCM due to the battery/sleep issues, so will I have any boot issues or fuses burnt if I accidentally boot to SysNAND 4.0.1?

I don't plan on using any CFW, just leaving SysNAND on 4.0.1 and EmuNAND on 6.2.0 without AutoRCM enabled. Thanks.

 

[iamfoesho]

your efuses only update when you boot to sysnand without autorcm (or the sx bootloader).

Also, your efuses only update to the required version for the firmware you have installed on your sysnand at that time.

If you never update sysnand past 4.0.1, your efuses will remain the same.

So nothing will happen to my SysNand 4.0.1 and efuses unless I "accidentally" update it? Also, am I safe to use the SX Pro to boot to EmuNand 6.2.0 without AutoRCM and be able to keep SysNand on version 4.0.1?

I am just afraid that if I don't have AutoRCM enabled (strongly worded warning in ChoidujourNX) I will brick my console if it accidentally boots to SysNand 4.0.1 when the SX Pro Dongle isn't plugged in, I just need some reassurance. Thank you.

 

[Dabman]

Hey!
It‘s-a me again!

I am a little bit confused with this eFuse-System.
Searched this Forum and it led me to this thread.

There was a Post in the Thread ‚For all asking about os sx 7.0‘
Wich caused this confusion (i‘m sorry for that)
Screenshot:

So, if a switch console was normally updated to 7.0.x i will have 9 burnt efuses. (Source: https://switchbrew.org/wiki/Fuses )
Now -just for example- i will do a downgrade to 5.1.0 (6 burnt efuses) without using AutoRCM Booting into SysNAND - what could Happen?
If i have AutoRCM enabled, the efuses check won‘t happen ,right?
Am i forced to use the downgraded Version in EmuNAND and have SysNAND back to 7.0.x?
Or doesn‘t it matter if i will leave SysNAND on 5.1.0 .



Maybe some User with a good knowledge about this efuse-downgrade-Protection-System could help me out a Bit, or Maybe could Write a Little „efuses FAQ“ ?
The Switchbrew Wiki is good but i think to understand or know what happens if efuses are burnt or not - switchbrew Wiki Is a Bit too technically...

Thanks for Reading this!


Dabman ?

 

[gnilwob]

@Dabman
Say, your efuse is 9 (ofw 7.0.0)
if you downgrade your sysnand to 6.2.0, it needs efuse to match 8.
In this case, if you boot up your switch normally, you will get blank screen (because efuse mismatched, it is in panic mode)
We do not want this kind of blank screen.
And you will have to force shutdown the console by press and hold power button for 15 seconds.

If you boot into RCM(sysnand=6.2.0 and efuse = 9), it is also a blank screen (before injecting any payload).
But this blank screen is RCM which we want it to be.
You can then inject SX payload and you can boot into SX on 6.2.0 without problem.(assuming that you downgrade correctly and boot0 and boot1 are not damaged)
Because SX ignore efuse check.

efuse checks happen on OFW whether autoRCM is enabled or not.

 

[Dabman]

?Thank you very much for helping me out with this knot in my brain