Thanks again, Draxzelex, you’re an invaluable source of information!
I was thinking about when exactly to update the console. I’m planning on following your advice to another user and going with method #2: using ChoiDuJour (not NX) while in RCM, after backing up the SysNAND with Hekate (as per your recommendation), and updating to the latest firmware without burning any fuses. Questions:
1. Should I use CTCaer? Is that a branch of Hekate?
2. ChoiDuJour gives you the option to update the firmware while preventing the cartridge slot from updating, right?
3. How is that process different than booting into SX OS (without updating first), creating an EmuNAND, and then using ChoiDuJourNX to perform the update?
4. Regardless of the method, I should still never boot into the OFW, or it will burn fuses, correct? Is there any risk of that happening if AutoRCM is on (and it’s enabled by default when updating with Choi, as you mentioned)? If so, what’s the best way of preventing that from happening?
As for game backups, since I’m determined to maintain my cartridge slot in its original state, I may have to download them instead of dumping from my own carts. I’ve been reading about NSOs and XCIs, but couldn’t come to a conclusion.
5. Is there a consensus as to which one is better? I’ll be using SX OS, so I believe I can run both;
6. I’ve read something about “trimming” files, is that similar to what people used to do to PSP ISOs, back in the day?
6.1 If so, can I just download the trimmed versions? Do they perform the same?
6.2 Are there tools so I can trim the files myself? Is that easy/recommended to do?
7. I’ve also read about updates to the controllers’ firmwares. How can one go on about updating those?
8. Forgot to ask this one: if you update applying the exFAT patch, can you revert to the same firmware without it (“remove” the patch and use the FAT32 version) or vice-versa?
I’m on the same boat, buddy, the only difference being that I’m on 1.0.0.
It’d be great if we could define the proper order of doing things. Here’s what I got (adding to your own list):
- Boot into RCM using a jig and load CTCaer mod (= improved Hekate?) as a payload via a USB dongle;
- Make a System NAND Backup including boot0/boot1 and raw eMMC GPP while still in RCM;
- Use the biskeydump payload to backup my BIS keys. They would allow me to reinstall any firmware version manually (optional?)
- use ChoiDujour to install the 6.2.0 update without burning fuses (better than doing it on the EmuNAND, or does it end up being the same thing?)
- Prevent the cartridge slot from updating (if there really is such an option in Choi) - that way, you can truly revert your system to its original state later;
- Enable AutoRCM through Hekate (apparently, auto-enabled by default when using Choi);
- Boot stock FW through Hekate (by that, do you mean CFW or OFW?)
- Forgot to add this step: link a Nintendo account (Nintendo ID) as soon as you boot into CFW (or is it OFW? I’m not sure), so if it’s required for anything and you’re banned later, it’s alteady there;
- Play Pokémon (a legit copy, I assume, so you just used the CFW to bypass the firmware requirement and avoid burning fuses by booting into the OFW/Horizon?).