Hacking A Couple Questions About EmuNAND

[csimmons222]

The firmware on my virgin Switch was 8.1.0. I just received my SX Pro. I put in the jig and dongle and booted into RCM / SX OS screen. I immediately backed up my SYSNAND to my FAT32 formatted SD Card. I copied that backup over to my PC. I then went through the process of installing EmuNAND on a hidden partition of the SD card. My questions are:

1. Upon the completion of the EmuNAND install, I only see one partition on my SD Card which is smaller than the total size of the SD card. I assume that this is because the EmuNAND is installed on the hidden partition that I cannot see. However, the partition that I can see has the following directories in it: config, Emutendo, Nintendo. Is this visible partition simply used as "storage" that the EmuNAND on the hidden partition access to load homebrew, game backups, etc.?

2. When saving backups and installing homebrew, do I need to save everything in the Emutendo folder to keep it "hidden" from nintendo? Or, can I simply create a directory called "switch" at the root level and put my homebrew applications in that folder?

3. If I do not enable AutoRCM, if I mistakenly boot into the SysNAND without going through the SX OS screen using RCM and the jig then does that "blow" an efuse which prevents me from restoring my OFW from a backup that is an earlier release?

Sorry for some of the Noob questions. I have been reading a ton and it's a bit tough when I am not sure if I am getting correct info due to the fact that I am reading old posts.

 

[gamemasteru03]

The firmware on my virgin Switch was 8.1.0. I just received my SX Pro. I put in the jig and dongle and booted into RCM / SX OS screen. I immediately backed up my SYSNAND to my FAT32 formatted SD Card. I copied that backup over to my PC. I then went through the process of installing EmuNAND on a hidden partition of the SD card. My questions are:

1. Upon the completion of the EmuNAND install, I only see one partition on my SD Card which is smaller than the total size of the SD card. I assume that this is because the EmuNAND is installed on the hidden partition that I cannot see. However, the partition that I can see has the following directories in it: config, Emutendo, Nintendo. Is this visible partition simply used as "storage" that the EmuNAND on the hidden partition access to load homebrew, game backups, etc.?

2. When saving backups and installing homebrew, do I need to save everything in the Emutendo folder to keep it "hidden" from nintendo? Or, can I simply create a directory called "switch" at the root level and put my homebrew applications in that folder?

3. If I do not enable AutoRCM, if I mistakenly boot into the SysNAND without going through the SX OS screen using RCM and the jig then does that "blow" an efuse which prevents me from restoring my OFW from a backup that is an earlier release?

Sorry for some of the Noob questions. I have been reading a ton and it's a bit tough when I am not sure if I am getting correct info due to the fact that I am reading old posts.

The emutendo folder is used to store game data for your emunand. Everything else is stored normally on your sd card.

You create a dictionary called switch on the root of your sd card and put homebrew in there.

Yes if you update your sysnand firmware while keeping autorcm on then you will not burn fuses but if you launch your sysnand with autorcm off on a firmware with more fuses burnt than your system then your fuses will be burnt which will not allow you to downgrade to a lower firmware.

No problem it's better to ask questions than to mess your switch up!

 

[microchipman]

So if one boots into RCM/SX OS and immediately backs up the NAND, the nand is still clean at that point correct? Is this as clean as RCM with Hekate and taking NAND backup?