General recommendations wanted FAT32 or exFAT? Which emuNAND Type, AutoRCM?

Bierfreund

Junior Member
Apr 2, 2019
13
3
Germany
My current situation:
I have a hackable Switch on Firmware 7.0.1 with a 64GB micro SDCard which was used as intended by Nintendo up to now ;)
I bought a SX Pro and a 200GB SDCard which should replace the 32GB Card.
I want to be as safe as possible from a possible ban.
My plan is that I create a NAND backup and afterwards use SX OS with EmuNAND.
I read the FAQs and manual but i still have a few questions:

1. The manual says that "FAT32 is recommended to prevent SD corruption". Is this still true? Does SX OS have problems with exFAT? Otherwise I would prefer using exFAT, because I don't see any disadvantages.
2. According to the manual there are three EmuNAND types: System NAND, microSD as Partition, microSD as Files.
Which one would you recommend? I would guess System NAND is fastest but most unsafe because if (accidentially) boot into OFW, it can be found easily and lead to a ban
3. If I decide for microSD as Partition or microSD as Files are there other traces on the System NAND or would it be (kind of) safe to boot with my old (unchanged) 64GB micro SDCard to OFW and only use the new 200GB for SX OS? Or is the one and only way to boot OFW a restore of my backed up clean System NAND? (I don't have any plans to use OFW for playing online or something like that, but let's see what happens if i playes Mario Kart the first time ;) )
4. Would you recomment to use AutoRCM? I read in some other forum that they don't recommend it, but unfortunately i can't remember the reason and I also can't find it at the moment.
 

imprezgc8

Bannnnnn-Kai!
Staff member
Troll Eating Dogs
Nov 26, 2007
2,424
138
The Cloud
1. It's not SX that has an "issue" with exfat. It's the Switch itself that does not handle exFAT very well when it comes to homebrew.

2. I use SD files personally, but some people think the hidden partition is safer. I do believe there is a big with the hidden partition and SX 2.6.1 though.

3. If you never boot CFW to your sysnand it should be "clean". Of course like you mentioned make a nand backup before doing anything. Booting to the SX bootloader does not put anything on the sysnand.

4. AutoRCM is almost 100% a way to get banned. You should never use this if you are worried about getting banned and really only need it if you are trying to save your fuses, which you have already burned up to 7.0.1 anyways.

As a note, there is honestly not sure fire way to not get banned once you mode your console. You are taking the right steps to lessen the chance, but if you ever connect to Nintendos servers you can for sure be banned even if you are booted to OFW. No one has confirmed what Nintendo is even checking to ban consoles.
 
  • Like
Reactions: Bierfreund

Bierfreund

Junior Member
Apr 2, 2019
13
3
Germany
Great, thanks for the answers, helps a lot.
Think i will use FAT32 and emuNAND on microSD as Files and don't use AutoRCM then.
Can you or anyone else explain the thing with the fuses? (link to an explanation is also fine)
When are they burned? Each time i boot using the Rig? What effect does it have when one or more (how many are possible?) are burned? And I don't understand why "which you have already burned up to 7.0.1 anyways"? I have not done any modifications yet, until now I only used my Switch as intended by Nintendo.
 

lordplops

Senior Member
Feb 8, 2019
135
28
France
The upgrading of Firmware burns the fuses - this means you cannot then downgrade to a lower firmware, because the fuses must match. Having Auto RCM avoids the possibility of burning fuses but may flag up your console as stated. You yourself have not modified anything, it's just the natural process as performed by the Switch itself.
 
  • Like
Reactions: Bierfreund

imprezgc8

Bannnnnn-Kai!
Staff member
Troll Eating Dogs
Nov 26, 2007
2,424
138
The Cloud
The console has "e" fuses which Nintendo uses to force the console to only boot the FW that the fuses match. It is a way for them to "stop" people from running lower FWs after they update to the newest (thought there are ways around that, but I would not honestly worry about that). This only happens once when a new FW is installed on the console (usually a major update). For instance 7.0 burned a new fuse, but I am not sure that 7.0.1 did. There are 32 "e" fuses total I believe and if 7.0.1 is booted without the use of the SX bootloader up to 8 fuses are burned I believe. Don't quote me on that number, I have not checked recently on the number for 7.0.1.

Since you have already installed FW 7.0.1 and you did not use ChoijudourNX and autoRCM your "e" fuses have been burned to the number that 7.0.x forces.

Sorry, this might not be the most clear explanation.
 

MacD

Full Member
Feb 28, 2019
41
8
Cornwall
1. FAT32 on the micro SD card.
2. ExFAT on a USB.

Install backup roms via the USB which you plug into the dock. Which will then allow you to copy more than 4gb.

3. Auto RCM off when you backup your NAND.


No matter how careful you are exFAT will eventually corrupt one or more files. When a file is open and something happens (eg you hit the home key, or the console crashes or anything else like that) the handle on the file gets lost from the file allocation table.

It can never be recovered since the system doesn't know where to look for it.

FAT32 uses two file allocation tables meaning it can use the second one to restore the table when it needs to.
 

sixtynine

Junior Member
Dec 4, 2018
18
3
Like Imprez said. It's not Team-Xecuters fault on the exfat sdcard corruption. The blame lies with Nintendo, it's their crappy driver, hopefully some day Nintendo will fix it.
I got tired of having to always remove my card and plug it into PC to reformat and copy XCI files back to card, then boot back into SX-OS. So I switched to FAT32 and haven't had a single corruption issue since. My switch never crashes or needs to be rebooted so I'm always in SX OS and just use FTP to transfer stuff back and forth.
 

Bierfreund

Junior Member
Apr 2, 2019
13
3
Germany
Now i'm already using SXOS since a few days, i have some additional questions:
1. Can i safely configure Wifi in SXOS e.g. to use functions like the FTP server or does this increase changes of being banned?
If i cinfigure Wifi in SXOS it's still unconfigured in OFW, correct?
2. If i'm in SXOS everythin looks identical to OFW except the album app. So my qurstion is, if i'm in SXOS do i run a complety independent OS or do i in fact run the OFX and only if i'm opening the album something different is started?
 

Hackerjac

The Minifigure
Staff member
Troll Eating Dogs
Jun 2, 2010
1,332
108
Denmark
Yes you can configurer ftp and such in SXOS, and if will still be unconfigured in OFW

If your not using emunand you are not running independent OS, with that i mean if you in SXOS play a xci game, when then going to OFW you will still ba abel to see that game have been played
 
  • Like
Reactions: Bierfreund