Hacking Confused about fuses?

[freeza]

Hey guys... So i'm a bit confused on the efuse situation on my switch.

for a brief history, I got SX Pro back in July and followed a guide to update from 4.1.0 to 5.x without burning any fuses. briccmii reported 5 fuses burnt before and after the update.

Fast forward to today, I am looking to setup EmuNAND and update that to 6.x whilst leaving OFW at 4.1.0 via nand restore. After backing up all of my game saves with checkpoint, disabling autoRCM, and a brief boot into OFW, both briccmii and hekate 4.2 all of a sudden report my fuses as 6 burnt? Anyway, I decided to restore my clean NAND from back in July and was successful in doing so. Attempted to boot switch to a black screen (which i figured might happen since fuses burnt = 6??), using SX Pro, I tried booting again to a white screen. One last attempt to boot got me into Horizon on my 4.1.0 FW, both OFW and CFW booted successfully. How is this possible with fuses burnt = 6? I'm now creating a 15GB EmuNAND from SX OS and will factory reset OFW to leave at 4.1.0 and update EmuNAND to latest FW. I'm kind of baffled at the eFuses situation going on here, could someone shed some light on this? Thanks!

 

[Draxzelex]

After backing up all of my game saves with checkpoint, disabling autoRCM, and a brief boot into OFW, both briccmii and hekate 4.2 all of a sudden report my fuses as 6 burnt?!

Booting the Switch up with a firmware higher than your count and without RCM will burn fuses; that is quite literally the whole point of AutoRCM. What on earth made you decide it was a good idea to remove AutoRCM and not burn fuses?

 

[freeza]

Booting the Switch up with a firmware higher than your count and without RCM will burn fuses; that is quite literally the whole point of AutoRCM. What on earth made you decide it was a good idea to remove AutoRCM and not burn fuses?

good question whatever emunand guide is in the tutorial section is what made me remove autorcm.

 

[Kubas_inko]

Part of me wants to say: "That's what you get for using their """EmuNAND"""."
The other part would say: "What an idiot would tell this to anyone (without a proper explanation...)."
I am 100% sure, that once you have created the """EmuNAND""" you can enabled it again.

Now you either have to boot thru RCM to your 4.1.0 OFW or update it.

 

[The Real Jdbye]

good question whatever emunand guide is in the tutorial section is what made me remove autorcm.

If you use emuNAND, obviously that won't burn fuses. But if your sysNAND is a newer firmware than the fuses burnt it will.

 

[kkcheong]

Fuse is overrated.

 

[Dust2dust]

Fuse is overrated.

It's all about options, for those who want to be able to downgrade easily. But I gotta admit that protecting fuses to eventually use a hacked entrypoint on lower firmwares might be a pipe dream at this point.

 

[LamahHerder]

But I gotta admit that protecting fuses to eventually use a hacked entrypoint on lower firmwares might be a pipe dream at this point.

Yea I am thinking to set a date and give up once it is crossed...

 

[Thandor]

Fuse is overrated.

This.

I'm lurking around here since 4 months, haven't seen a single purpose of saving fuses, EmuNAND and especially firmware downgrades yet, just because the games and update need a specific firmware/masterkey revision to run.

Just because there may be a small benefit somewhere in the future, it's not worth the stress with updates and AutoRCM for me. I couldn't care less, especially as a SX Pro user. It's plug and play.

 

[wurstpistole]

So what you're saying is that you are...

(•_•)
( •_•)>⌐■-■
(⌐■_■)

confused.

 

[Spadezilla]

the software update burns an actual, physical fuse?

wtf is this black magic shit

 

[wurstpistole]

the software update burns an actual, physical fuse?

wtf is this black magic shit

Yes. Tiny physical fuses in the CPU.

 

[thla]

No physical fuses are burnt. Software fuses are "burnt" as in, some marker set.

Huh, no.

That's the entire point, the CPU is physically altered so that no matter what you compromise on the software part the fuses will still be "blown"

 

[kkcheong]

No physical fuses are burnt. Software fuses are "burnt" as in, some marker set.

Physical fuses are burnt. That's why it's permanent. Pls don't say something that you don't know. It sounded weird

 

[wurstpistole]

Huh, no.

That's the entire point, the CPU is physically altered so that no matter what you compromise on the software part the fuses will still be "blown"

Physical fuses are burnt. That's why it's permanent. Pls don't say something that you don't know. It sounded weird

Which is exactly what I said

Yes. Tiny physical fuses in the CPU.

 

[kkcheong]

Which is exactly what I said

Why you change your comment? Your previous comment still in our quote.

 

[wurstpistole]

Why you change your comment? Your previous comment still in our quote.

No! You Faked this! Clearly an elaborate plot against my reputation

 

[kkcheong]

No! You Faked this! Clearly an elaborate plot against my reputation

LoL

 

[Kafluke]

Hey guys... So i'm a bit confused on the efuse situation on my switch.

for a brief history, I got SX Pro back in July and followed a guide to update from 4.1.0 to 5.x without burning any fuses. briccmii reported 5 fuses burnt before and after the update.

Fast forward to today, I am looking to setup EmuNAND and update that to 6.x whilst leaving OFW at 4.1.0 via nand restore. After backing up all of my game saves with checkpoint, disabling autoRCM, and a brief boot into OFW, both briccmii and hekate 4.2 all of a sudden report my fuses as 6 burnt? Anyway, I decided to restore my clean NAND from back in July and was successful in doing so. Attempted to boot switch to a black screen (which i figured might happen since fuses burnt = 6??), using SX Pro, I tried booting again to a white screen. One last attempt to boot got me into Horizon on my 4.1.0 FW, both OFW and CFW booted successfully. How is this possible with fuses burnt = 6? I'm now creating a 15GB EmuNAND from SX OS and will factory reset OFW to leave at 4.1.0 and update EmuNAND to latest FW. I'm kind of baffled at the eFuses situation going on here, could someone shed some light on this? Thanks!

OP is saying he/she can boot to official firmware with burnt fuses. I dont see how this is possible unless he/she loaded homebrew boot loader first.

Theres no way to boot straight to OFW with incorrect fuse count.

 

[kkcheong]

OP is saying he/she can boot to official firmware with burnt fuses. I dont see how this is possible unless he/she loaded homebrew boot loader first.

Theres no way to boot straight to OFW with incorrect fuse count.

You can if boot higher firmware