yes same as original fuses count but still remain same if i boot to OFW without hekate. i checked detected fuse count as my ofw version mean not the latest one which i upgraded emummc to latest version FW
can someone confirm i need to prevent booting sysnand ofw, just keep it there
if my switch console run out battery = totally switch off with no battery then i charge my nintendo switch will burn fuses?
my issue is sysnand already dirty meaning that using CFW for isntall NSP, that reason i want emunand to update using daybreak but want to confirm if there burn fuse when i accidently boot to sysnad OFW without jig and RCM?
i worry about burn fuses but let say my switch sysnand version 10.0.4 then my emummc version 13.2.0
If i accidently boot up sysnand OFW without RCM jig and Hekate - this will burn my fuses? because why i worry there are 2 different version sysnand 10.0.4 and emummc 13.2.0
Hello ALL, i have question do i need to do this step or skip this step? https://rentry.org/EristaEmuNAND
Select Toolsthen select Archive Bit - AutoRCMand pick Enable AutoRCM
fuse will burn or not ? if accidently boot without RCM or Jig into sysnand lower version than emmummc version? example my sysnand version 10.0.0.4 my emummc version 13.2 latest version
i don't want touch sysnand and leave it lower version and also i can running SX OS on this version 10.x.
important to update here, my switch is dirty running CFW on Sysnand and i scare will banned that reason i don't want update sysnand.
Can i update emummc to version 13 and leave it sysnand version 10.0.4? if there any issue if i boot back to sysnand 10.0.4 after updated my emummc version 13?
does this still work? can I update my emuMMC to 13.x.x and leave my sysNAND at 10.0.4? will my sysNAND still work after?
can i update emummc to version 13 and leave it sysnand version 10.0.4? if there any issue if i boot back to sysnand 10.0.4 after updated my emummc version 13?