You know Google is a thing...ive never used hekate or briccmii and not sure where to find them ? homebrew section?
and the nsw was stock not like modded or anything so im just not sure how the whole fuse process works I suppose updating at all thru nintendos servers must burn them with the implied context of your response
And for fuses, they are burnt when you are running a firmware higher than the fuse count with the stock bootloader. Updating officially doesn't burn the fuses; its when the console reboots after installing the update that fuses are burnt.
Hello everyone,
I have some questions /problems (?) and I hope someone can help me out. So I own a switch since day 1 + SX Pro (Dongle + Jig)
I think I made a backup of my NAND so far but thats it.
My switch is currently on 5.1.0 BUT I used ChoiDujourNX to get on this firmware. If I remember right, AutoRCM is enabled by "default" after updating to 5.1.0 (or whatever FW that would burn fuses)
So the first problem is, that I can't boot into SX CFW even with the jig + dongle (RCM is activated). The only way is to get a USB cable and sent the CTCaer Hekate payload to the switch and from this part I inject the SX Payload, so I can finally boot into SX. Is there maybe a "fix" or other way to do it?
My second question is if it is necessary to "protect" the fuses? I mean after seraching for some tools / homebrews they'll always get updates for the newest FW. I mean everything works so far but it is kinda laborious to get everything running. Isn't a Mod Chip like SwitchME the best choice for me?
and the last question: What is the difference between XCI and NSP? NSP will be installed on the NAND or how can I imagine that? With SX I only put the XCI on the SD card and thats it. So is the NSP basicly an internal installation?
Thanks in advance for any helpful comment.
- I've never heard of this issue with the SX Pro. Although if you have AutoRCM, you don't need the jig anymore. Ensure that you fully power down the console. If it has AutoRCM installed, this has to be done from RCM as powering it down from Horizon (e.g. CFW/OFW) will cause it to reboot into RCM. Acceptable shutdown options include Hekate's Power Off function or performing a manual shutdown. Then once the console is fully powered off, press the power button once so AutoRCM causes it to boot into RCM. Without the jig, instead just plug the dongle in and see what happens
- The reason why you wouldn't burn fuses is in case a future exploit comes out for lower firmwares that doesn't need a jig and USB cable/dongle/modchip. Some users have not even hacked their console yet as they find the current exploit too involved. If you don't mind using the current exploit until the end of time, you can burn your fuses. If you want to at least keep your options open, then do not burn them. I also don't think avoiding burning fuses is laborious in the slightest. In fact, not having burnt fuses usually leads to less problems such as for those who burnt a fuse when updating to 6.2. That firmware breaks all CFW so if they hadn't burnt a fuse, they would be able to downgrade without ease but since the fuse was burnt, when they downgrade, they lose sleep mode
- .NSP is the format for content that is installed and can go on either the SD card or the NAND. .XCI is a copy of a retail Switch cartridge. .NSP are slightly faster as well as smaller than .XCI files but cannot be loaded from an HDD like .XCI files; they each have their own advantages and disadvantages.
If you have ran CFW before making a NAND backup, it won't be "clean" anymore (by clean, I mean safe for restoring prior to going online in case you want to avoid being banned) but the first step towards any hacking is making a NAND backup. The best tool to do so is Hekate (again, Google is your friend) which can also restore the NAND. If your console ever gets bricked, RCM will always work and Hekate is loaded in RCM so it will be able to restore your NAND in those situations. Also a corrupted SD card won't brick the console, it'll only affect the SD card. Lastly, you should make a new NAND backup every time you burn fuses since the previous NAND backup won't match the new fuse count of the console.is it too late to make a backup of your nand after you have updated/ran installed cfw?
i have NOT done that yet and now have a memory card and time to spare to do this, if its not too late whats the most simple method of getting this done - as I understand its around 29 gb of space that will be used and it takes several hours for it to complete do you need to make a bakcup of this everytime you switch fw ? or upgrade? and then whats the method of actually using this backup to help you in a situation where you are bricked or stuck and would have to use this at all? worst fear would be a corrupted sd card for myself based on reasons ive read it happening so not too concerned but safe than sorry is the way to go