What is the differnce between TegraRCM and SMashRCM.
I only know of
TegraRCMSmash. I've never heard of TegraRCM or SmashRCM.
I believe they were talking about TegraRCMSmash and
TegraRcmGUI.
My understanding is that the latter works in conjunction with the former to provide a GUI (Graphical User Interface).
@Draxzelex can confirm that information. He also mentioned multiple times in this thread that TegraRcmGUI has some issues, and since I've been wanting to know what exactly those issues are for a while, this is the perfect opportunity to ask.
Well... I am completely lost here...
Does anyone as some kind of tutorials for the pros and cons of updating the firmware prior using OS OX Pro ?
I have a Switch in 1.0.0. Better keep it that way ?
My problem is that I do not have exFat support with 1.0.0 and thus I am wondering if SX OS Pro will be able to launch the CFW... ?
If so, After updating the Emunand in 6.2, should I format (and ducplicate) my sd card in exfat for it to work with XCI or NSP files.
Sorry for my questions but I really want to do things properly... There is too many stuff on the forum that I am unable to understand what is best...
Thank you so much !
another question; before my sx os comes i wanna understand this burn fuse thing so ChoiDujour updates the system without burning fuse so this lets you downgrade back to where you started from correct ? also from what i understand ChoiDujour installs autoRCM to prevent the fuse from being burned so as long as it's enabled im safe yes ? so when sx os ask me to install auto rcm i can pick "no" right becuase ChoiDujour already installed it ? and im still not 100% which guide to follow when it arrives, i found one that includes emunand setup ill provide the link
here for someone here to give me the o.k on it or recommend a better one that i should go with instead.
For updating, your best bet is to update without burning fuses and the best way to do that is with the homebrew application
ChoiDujourNX. Unfortunately for ChoiDujourNX to work on 1.0, you need to enable debug mode which SX OS does not support (at least to the best of my knowledge).
Atmosphere not only supports debug mode, but firmware 1.0 as well (not sure if SX OS supports 1.0 at all). Obviously since 1.0 does not support exFAT, you need to format the SD card to FAT32.
If SX OS does support firmware 1.0, you should try setting up EmuNAND then updating it with ChoiDujourNX. If that doesn't work, then you'll have to update SysNAND with ChoiDujourNX to whatever firmware you want then setup EmuNAND.
That guide seems fine to me although it doesn't seem to detail any steps about updating without burning fuses; it just discusses setting up EmuNAND as well as the various pros/cons of each version (which is handled quite nicely). The problem is I don't think you can use ChoiDujour to update EmuNAND since EmuNAND cannot be read by hacdiskmount. What you can use instead is the homebrew application ChoiDujourNX since you can just load ChoiDujourNX in EmuNAND to update without burning fuses.
Correct. Also please refrain from double posting
I'm bundling up those questions (and Drax's reply) because you seem to be in the same boat.
The first step is to make a copy of (backup/dump) your clean NAND. You should boot into RCM (using a jig as the safest method) and inject a payload in order to proceed with the backup (
CTC-aer's mod of Hekate is recommended).
In RCM (or ReCovery Mode), it doesn't matter if your microSD's file system is exFAT or FAT32, regardless of your system version (OFW, or Official FirmWare). Because of that, I suggest using a microSD card that is larger than 32GB and formatted as exFAT - that way, the NAND will be dumped on its entirety and you won't have to deal with split files.
After backing up your NAND, BIS keys and everything else, save/upload those copies to safe locations (local and cloud storage). Use the 3-2-1 backup rule: have at least 3 total copies of your data, 2 of which are local but on different mediums (read: devices), and at least 1 copy offsite (cloud storage, such as Google Drive or iCloud).
The next step, since you're both using SX OS, is to create an emuNAND. The
guide linked by
@GATWYAY3.2 is, indeed, very well written and you're okay to follow it. Boot into RCM again, inject the SX OS bootloader payload (just insert the SX Pro dongle, if you have one) and follow that guide to the letter. I can confirm that it works on system version/OFW 1.0.0, so there's no need to update - yet (
edit: check the update at the bottom of this post).
The final step is to "install" CFW (you don't really install it, you merely run it from your microSD card) and update your emuNAND (not your system NAND, or sysNAND). As Drax said, you can use ChoiDuJourNX for that.
Again, I can confirm that even the latest beta release of SX OS runs on OFW 1.0.0. So, just load SX OS (while making sure that you're on emuNAND) with ChoiDuJourNX's files in the root directory of your SD card (the actual root dir, outside of the Emutendo folder created after the emuNAND process) and select that homebrew application inside of SX OS (open the "Album" app to get there, then press R to move to the Homebrew section).
ChoiDuJourNX's enables AutoRCM by default (so you don't need to insert a jig every time you power off/on the console), but that only applies to the emuNAND, so it's useless. To enable AutoRCM for SX OS, you need to do that in SX OS's bootloader - the same you used to create the emuNAND. Go to options and select that option, you should see a message confirming that it is enabled.
Update: You can only run SX OS 2.5 beta (the latest version, as of today) if you already have emuNAND on 6.2.0. So, download the previous beta version of SX OS (2.4.1 - google "SX OS BETA REPOSITORY - Downloads all beta versions" for a link) and use that to create the emuNAND and update it to 6.2.0 using ChoiDuJourNX.
You can then use SX OS 2.5 if you want to (it's a matter of dragging and dropping the new boot.dat file onto your microSD card). Just bear in mind that beta version 2.5 has issued with game mods, if you're planning on installing those.
I decided to stick with 2.4.1 for the time being. So far, so good.
Update 2: Before finishing the update process to 6.2.0, ChoiDuJourNX should give you the option of rebooting your system or powering it off completely. Since AutoRCM does not work on emuNAND, you should choose to power off the system completely, and then power it back on with a jig inserted (unless you want to reboot with the jig already inserted). That's the only way to boot into RCM again, for now.
Inject the SX OS's bootloader payload (insert the dongle) and enable AutoRCM via the Options menu, as mentioned before. Otherwise, you risk having a heart attack after your system reboots straight into OFW/Horizon (the name of Nintendo Switch's OS), ignoring RCM (even if that happens, you should be fine if you only updated the emuNAND, since the sysNAND will remain on 1.0.0 and the fuses, not burned).
K3Nv2
DinohScene
