That doesn't mean a burnt fuse. There have been several minor updates that didn't burn fuses.All updates replace boot0/boot1
That doesn't mean a burnt fuse. There have been several minor updates that didn't burn fuses.All updates replace boot0/boot1
If history is any indication, it probably won't burn additional fuses.Oh I meant did fuses burn between 6.0 and 6.0.1
Is it safe? YES!!!!
Should you update?epends on if u wanna idk maybe have an older firmware (use tx's emunand to update)
bye
F-That I just updated to v6.0 about a week ago. Plus! I already burned enough fuses on my Switch.
I'll just stay parked at v6.0 or I'll just go into RCM Mode and use ChoiDujour when v6.0.1 becomes available for download...
PS
My Switch seems to be running smooth on v6.0 and even if no fuses were not to burn while updating to v6.0.1 I still don't trust this update.
Unless it's 120% confirmed that is save to upgrade to v6.0.1....
it doesent but o dint know if the implement something to detect itSupposedly it bricks the Emunand.
"Is it safe" becomes "it depends". If you use themes or "Emunand" - then no. If you use neither - should be safe as it's a minor version bump (same fuse burn count as 6.0).
This is why I rather stick with 6.0...TX just posted a bug fixed SXOS 2.01 a few hrs ago and Nintendo countered with 6.01.
This is why I rather stick with 6.0...
Who knows! Other than taking the chance on getting banned. Maybe Nintendon't has something up there sleeves by trying to get into a back door so they could brick or screw things up for anyone that has there Consoles Modded...
It just seems very strange on how all of the sudden Nintendon't dropped a new OFW so soon...
i read on this thread again that normal updating burns fuses, but what does that mean ?
i was on 5.x some weeks ago and updated with that homebrew app called choujoerux? i updated to 6.x with that app, that did not burn fuses, but whats the benefit of not burning the fuses guys?
What does that mean exactly? The link is not very clear. Does it mean that updating to 6.0.1 on sysnand trashes the emunand partition? Or is it only when updating on emunand?
Sysnand 6.0.1
Emunand 6.0.0
WORKS Perfectly.
The problem is when updating Sysnand, the firmware will patch BOOT0/1. Emunand signature is on BOOT1, after updating, SX OS won't recognize Emunand anymore.
Solution: Backup BOOT1 (unchanged after updating) when having Emunand setup.
Use Hekate to restore BOOT1 back after updating System to 6.0.1
It took Nintendo nearly half a year to release an update that stopped the pin bending joy con exploit and most people just used a jig instead so they aren't timelyTX just posted a bug fixed SXOS 2.01 a few hrs ago and Nintendo countered with 6.01.
It's a stability update, not a major update!I'm still waiting for them to update my mother in law. She is bloated, slow and commands too many resources...
the same, I press retroNX in dashboard and It say update, I dont read clearly and press error, fw now is 6.0.1 and cant boot to cfw (black screen)I red in my fb group that 6.0.1 broke sx os and it now black screens on them when payload is injected. Anybody here on 6.0.1 and sx os?