Hacking Question Can you burn fuses when updating SXOS emuNAND?

_silencer_ · Nov 29, 2018

Will the below scenario result in burnt fuses?
and
Will this also cause my sysNAND to become inoperable given that sysNAND is on 5.1.0 and emuNAND is now on 6.1

Switch currently on 5.1.0 ==> load SXOS and create emuNAND on microSD ==> boot into emuNAND ==>
Scenario 1: update firmware to version 6.1 using ChoiDujourNX with autoRCM disabled
Scenario 2: update firmware directly from Nintendo's servers (when 6.2 becomes supported)

From my understanding the only way to burn fuses is by updating directly from Nintendo's servers, or by not having autoRCM enabled with ChoiDujourNX ... but do these rules still apply whilst in emuNAND/updating firmware in emuNAND?

Kubas_inko · Nov 29, 2018

Neither of those will burn fuses.
The only way of burning fuses is by booting through default bootloader.

casio · Nov 30, 2018

Could you clarify the following based on scenario 1 please, so sysnand is on 5.1.0 and SD emuNAND is now on 6.1. Auto RCM is NOT enabled. Would booting to sysNAND through default bootloader (by mistake for example) burn fuses as if it was loading 6.1? Or will the sysNAND not take any notice of the emuNAND f/w version for fuse burning? Thanks

Kubas_inko · Nov 30, 2018

casio said:
Could you clarify the following based on scenario 1 please, so sysnand is on 5.1.0 and SD emuNAND is now on 6.1. Auto RCM is NOT enabled. Would booting to sysNAND through default bootloader (by mistake for example) burn fuses as if it was loading 6.1? Or will the sysNAND not take any notice of the emuNAND f/w version for fuse burning? Thanks

No? Why would it burn fuses for something which does not exist?

S3phi40T · Nov 30, 2018

casio said:
Could you clarify the following based on scenario 1 please, so sysnand is on 5.1.0 and SD emuNAND is now on 6.1. Auto RCM is NOT enabled. Would booting to sysNAND through default bootloader (by mistake for example) burn fuses as if it was loading 6.1? Or will the sysNAND not take any notice of the emuNAND f/w version for fuse burning? Thanks

I have such scenario. No fuses burned.
5.1 nand boots like a charm.

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

ssssss13 · Nov 30, 2018

S3phi40T said:
I have such scenario. No fuses burned.
5.1 nand boots like a charm.

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

how IS it posible? How did you update your emunand? Thought choidujour? I dont understand how dont burn fuses

--------------------- MERGED ---------------------------

Kubas_inko said:
Neither of those will burn fuses.
The only way of burning fuses is by booting through default bootloader.

But without auto rcm if you turn off emunand and turn on without a payload it will burn fuses right?
I' scared of burning more fuses than muy ofw is in. Im on 4.1 without updating emunand because i' m afraid ir a brick if a burn more than4.1 fuses(5 i think)

FabioCapela · Nov 30, 2018

ssssss13 said:
how IS it posible? How did you update your emunand? Thought choidujour? I dont understand how dont burn fuses

Because what burns fuses isn't the update, but booting to the higher FW version without CFW. And you can't ever boot into EmuNAND without CFW.

(AFAIK, this happens because the command that burns fuses is locked down during boot, likely to eliminate the possibility of a system or game bug/crash bricking the console by wrongly issuing the burn fuse command; this means the firmware itself is actually incapable of burning fuses, only the bootloader can do it.)

S3phi40T · Nov 30, 2018

ssssss13 said:
how IS it posible? How did you update your emunand? Thought choidujour? I dont understand how dont burn fuses

--------------------- MERGED ---------------------------

But without auto rcm if you turn off emunand and turn on without a payload it will burn fuses right?
I' scared of burning more fuses than muy ofw is in. Im on 4.1 without updating emunand because i' m afraid ir a brick if a burn more than4.1 fuses(5 i think)

Choidjur
EmuNAND is not real nand so it is still 5.1 for me.
EmuNAND is 6.1 so for Switch I'm still on 5.1.

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

ssssss13 · Nov 30, 2018

I still dont understand if you install autorcm in choidujuour emunand what happens. Activates autorcm for all or what

S3phi40T · Nov 30, 2018

ssssss13 said:
I still dont understand if you install autorcm in choidujuour emunand what happens. Activates autorcm for all or what

No AutoRCM.
Normal NAND is 5.1. Period.
EmuNAND + update with Choidjour or whatever is the proper name.
Whatever EmuNAND is, it's different story.
Both boot OK.
For Switch I'm still on 5.1

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

S3phi40T · Nov 30, 2018

Never tried to turn AutoRCM on during EmuNAND update.
Thought it would be at least weird.

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

ssssss13 · Nov 30, 2018

S3phi40T said:
Never tried to turn AutoRCM on during EmuNAND update.
Thought it would be at least weird.

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

Ah, so when updating thought choidujour untick the autorcm option?

S3phi40T · Nov 30, 2018

If you update EmuNAND? Yes.

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

Hacking Question Can you burn fuses when updating SXOS emuNAND?

Active Member

"Something funny goes here."

New Member

"Something funny goes here."

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum