Urgent question: my Switch is a launch unit (1.0.0), but I only have a 128GB microSDXC card.
OFW (Horizon) won’t even recognize that card. Will I still be able to use it to backup the sysNAND after booting into RCM and injecting CTCaer-Hekate?
Can I then load a CFW and use ChoiDuJourNX to update the emuNAND? Or do I need a smaller HC card for the entire process?
2/3. Ah, I see. It’s just that you said using regular Choi was your personal recommendation, so I was willing to try that method. Since I have a bunch of jigs (SX Pro, R4S, RCMclip), I could probably use the official update method and then “brick” into RCM after it’s completed, but I’ll have to look up a video so I don’t end up messing up and burning fuses by accident.
4. So, just to make it clear: if AutoRCM is on, even if the battery dies/the Switch is turned off completely, AutoRCM still won’t be disabled? Only an official update in OFW/Horizon will do that?
5. I’ve read about the different firmware checks and learned that the “ignore” function of Tinfoil only works for the updates, not the native requirement of the games (which, in the case of Smash, is 5.1.0, as you mentioned). Is there really a point in not updating to the latest system version if I’m not burning fuses and have a clean sysNAND backup? It seems fairly safe to do so, right?
I already explained to you that dumping the NAND with Hekate is not performed in Horizon so exFAT support is irrelevant. CFW is loaded in Horizon so if you do plan to use an exFAT formatted SD card, you will need exFAT support. However 1.0 doesn't even support exFAT so it will have to be formatted to FAT32. Since its larger than 32 GB, you will have to use a third-party tool such as
GUIFormat.
4. I don't even know how running out of battery would remove AutoRCM hypothetically
5. The ignore function actually won't work for the updates either since they are encrypted with the new masterkey found only on 6.2. However since that key is the only thing inflating the firmware requirement, you can patch it to a lower firmware such as 5.1 with NSC Builder. And to actually answer your question, if you are updating without burning fuses, there's really no reason
not to update since you can downgrade in case something goes wrong. Usually updating immediately to a new firmware is a bad idea as it may break CFW such as with 6.2 but once the scene catches up, its usually safe to update.
So is 7 the expected number of burnt fuses on system version 6.2.0? If I were to ever disable AutoRCM and turn on my Switch with the normal bootloader again, my Switch would burn another fuse?
6.2 has a fuse count of 8. For future reference, you can check fuse counts for firmwares
here. And yes, if you disable AutoRCM at this point, your console will burn another fuse.
Just read that Reinx has updated with warmboot support. What exactly is meant by warmboot?
Sent from my Nexus 6P using Tapatalk
Warmboot is a fancy term for sleep mode. In the context of the new ReiNX update, its support for when you put your console into sleep when you have more fuses burnt than the firmware. Before, this would prevent the console from waking up and enter a sort of "worser" RCM (it will show up as an APX device but won't accept payloads). Now your console will wake up if you have more fuses burnt than your firmware aka you downgraded with burnt fuses. Not that there is much point in downgrading with burnt fuses anyhow unless you're a developer and want to make sure stuff works across all firmwares.
Once I install one exFAT update, I don't need to keep choosing the exFAT version of every update on ChoiDujour, right?
Yes you do. exFAT does not get applied to the console, it gets applied to the firmware. This is what led people to believe that updating officially removes exFAT. Instead they updated to a firmware without the exFAT patch. The advantage of ChoiDujourNX is that it can allow you to repatch the firmware to have exFAT support if you are currently on a firmware with the exFAT patch. If you update officially and have the exFAT patch applied to your current firmware, you actually have to update twice as Nintendo doesn't let you download the exFAT patch and firmware in one go unless your firmware is missing the exFAT patch.
Imagine this. You are on 6.2 with exFAT. Now Nintendo releases 6.3. If you update officially, you will update to 6.3 without exFAT. At this point, to get exFAT officially, you will have to insert an exFAT SD card to get the patch. The only way to go to 6.3 with exFAT in one download is if you are on say 6.2 without exFAT. ChoiDujourNX can let you go to 6.3 with exFAT regardless if you have it or not.