GOOD NEWS EVERYBODY!!! I have decided to make a..

How to have
SEPARATE ATMOSPHERE AND SXOS EMUNAND HIDDEN PARTITIONS ON THE SAME SD TUTORIAL!

​

PLEASE READ THE ENTIRE GUIDE BEFORE PROCEEDING. I WILL DO MY BEST TO MAKE THIS COMPLETE AND EASY TO FOLLOW.

I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS DUE TO THE USE OF THIS GUIDE. I DO THIS FOR FUN AND AM NOT A PROFESSIONAL. i HAVE TESTED THIS METHOD AND HAVE SET UP A COUPLE SD CARDS.

USE AT YOUR OWN RISK!!!!

The intent of this guide is to make ONE SD CARD with TWO HIDDEN EMUNANDS. One on 11.0 for SXOS and one with current firmware for Atmosphere.

More than likely the currently installed games WILL NOT WORK IN ATMOSPHERE if they were installed with the SXOS installer.

Tinfoil/awoo installed games may work fine. This is SXOS 's fault as the installer patched stuff in a way that is not compatible with the other CFWs.

There is also a section on SHRINKING the SXOS partition if you intend to only use it for USB loading. To minimize the impact it has on your SD and keep your HDD functionality for all 3000+ compatible games.. If you do this the current SXOS EmuNAND will break including installed games and saves.. IF you made backups of the save data you can restore them later.

Bottom line is, you will probably be reinstalling games and you need a backup of everything.

This guide make a few assumptions.. I will assume you are a current SXOS user with a working 11.0 Hidden Partition EmuNAND with a FAT32 SD. No Atmosphere installation required. There many ways to accomplish most things in this guide. I am doing the bulk of the work on the PC to limit the amount of times we take the SD out of the fragile Switch SD slot.

If you do not understand the above then this tutorial may be out of your league. Please google beginner switch hacking and learn some basics.

EmuNAND is the same thing as EmuMMC. It's just an older term. I call it by the old school term. Old habits..

This guide starts with a SXOS installation in place. If you wanted to go the other direction, adding a SXOS partition to an Atmosphere EmuNAND SD you would have to adjust accordingly but the main concept still stands.


DO NOT USE EXFAT!!! EVER! NINTENDO'S FAULTY DRIVER WILL CAUSE DATA LOSS!! DONT BE LAZY! FORMAT TO FAT32 AND DO IT RIGHT TO AVOID FUTURE ISSUES! I KNOW YOU DON'T WANT TO. DO IT ANYWAY! ANY EXPERIENCED PERSON WILL TELL YOU THE SAME. WHY WOULD WE ALL GO THROUGH THE HASSLE IF IT WASN'T NECESSARY? DO IT!


THERE ARE OTHER MULTI BOOT METHODS. THIS ONE IS THE MOST STABLE. YOU COULD JUST MAKE A FILE BASED EMUNAND FOR ATMOSPHERE. FILE BASED EMUNANDS ARE KNOWN TO CORRUPT. Good way to lose all your saves.

You will need a few things

• Latest version of Hekate.
• Latest NxNandManager
• Latest EmuTool
• Atmosphere SD files
• Latest Sig Patches (the GBATemp thread)
• A Raw Backup Of your SXOS EmuNAND (if you don't have one we will make one.)
• A Backup of your current Atmosphere EmuNAND (if you don't have a current Atmosphere EmuNAND we will convert your SXOS EmuNAND)
• A partition manager capable of moving and making partitions installed on your PC, I will be using MiniTool Partition Wizard but any capable partition manage should work.
• A PC. Any should do, this guide is written with Windows in mind
• A WORKING FOLDER ON YOUR COMPUTER (NxNandMnager and EmuTool can be quite finicky about external drives and things. Just make a new folder. For the sake of this tutorial I will use a folder CALLED C:\NANDS)
• Keys.txt You can get these using Lockpick RCM or find them online.

BACK UP YOUR SAVES!!! I USE JKSV
BACK UP YOUR ENTIRE SD TO YOUR PC
This process will FORMAT YOUR SD!!!!!!

PREPARATIONS

Now we will set up the programs

On your PC:

1. Make a folder for NXNandMananger. Folder can be anywhere except the working folder as long as you can find it.
2. Unzip the NXNandManager .ZIP file to this folder
3. Place the Keys.txt in the same directory as NXNandManager.
4. Open NXNandManager, click OPTIONS then CONFIGURE KEYSET then IMPORT FROM FILE and point it to the Keys.txt.
5. Unzip EmuTool and put the emutool.exe file anywhere except the Working folder as long as you can find it.

BACKUP CURRENT SXOS EMUNAND

If you have a raw backup already you may skip this step. Just put it in the working directory.

1. Using a SD Reader insert SD with your SXOS EmuNAND in to computer.
2. Run NxNandManager
3. Select File > Open Drive> Select your SD.
4. Select Full Dump
5. Select Output Directory and choose your WORKING DIRECTORY. Name your backup. For the guide I name it SXOSemunandFULL
6. Wait Until done
7. Press OK

If you have a current Atmosphere EmuNAND you can back it up using the same steps now. Name it ATMOemunandFULL

OPTIONAL: Shrink SXOS EmuNAND

If you shrink your EmuNAND make sure you backup all saves first! Back them saves up even if you don't shrink the EmuNAND

If you would like to shrink your SXOS EmuNAND now is the time. This will make all installed NSP stop working. You can reinstall but it won't hold much. The intent is to make SXOS's impact minimal. I make SuperXCI (XCI files that contain all updates and DLC for the game) I convert NSP files and make Super XCIs out of them as well. This way Everything for SXOS compatible games is on the HDD. Except a Small EmuNAND.

You can select whatever USER data size you want. I only intend to have SAVE data on this EmuNAND so 8GB is enough for me. I play all NSP off of my SD in Atmosphere. SXOS is just for XCI USB loading.


In NxNandManager

1. Select File>Open File and select your EmuNAND raw backup.
2. Select Options > Resize EmuNAND
3. Check Format User (this is optional, however this process will render the current USER data useless anyway so just format it to make it clean, Input file will not be altered)
4. Select New Size.. I went with 5504 MB for user partition (8 GB Total) to keep enough room for saves.. some games have fairly large save files, you can choose whatever you want,
5. Click Save As,, name the file whatever you want and choose the working directory. I call mine SXOSemuRESIZED
6. Click Save.

Convert Hidden SXOS EmuNAND to Atmosphere File Based EmuNAND.

This will convert your Hidden Partition SXOS EmuNAND to Atmosphere EmuNAND files in the event that you don't have a Atmosphere EmuNAND backup. You should be able to migrate your saves and games over. GAMES INSTALLED USING THE BUILT IN SXOS INSTALLER WILL NOT WORK IN ATMOSPHERE.

If you have a raw backup from an Atmosphere Nand you can use that instead and skip this step. This section duplicates and converts your SXOS backup if you don't have an Atmosphere EmuNAND.

1. Open EmuTool
2. Under source select SXOS Hidden Partition
3. Click "Select SD card" and select the SD with the SXOS Hidden Partition
4. Under Select target select Atmosphere File.
5. Under TARGET Click "Click to Select SD Card" Name the backup and save to the working directory. Ill Call it SX2ATMOemu
6. Click START

Create New SXOS EmuNAND Partition

IF YOU ALREADY HAVE A SXOS EMUNAND IN A HIDDEN PARTITION ON THE TARGET SD YOU MAY SKIP THIS STEP
THIS SECTION WILL REFORMAT YOUR SD WITH THE NEW SHRUNKEN EMUNAND! YOU WILL LOSE ALL DATA!!! BACK UP THE SD FILES

In NxNandManager

1. Select File > Open file and select the (Shrunken or not) backup of the SXOS EmuNAND
2. Select Options > Emunand Creation Tool
3. Check NAND path is pointing to your SXOS EmuNAND backup (Shrunken or not)
4. Under "Select Emunand Type" Select SD partition
5. Under "Select Target Disk" Select your target SD.
6. Click "Create Emunand"

Resize FAT32 Partition and Make New Hidden Partition

THIS WILL MAKE ROOM FOR A SECOND HIDDEN PARTITION.


Now we will RESIZE your FAT32 Partition to leave a 29.2GB Unallocated Partition at the end of the SD

1. Open MiniTool Partition Wizard
2. Find the TARGET SD
3. Right Click on the FAT32 partition
4. Select Resize
5. Reduce the size of the FAT32 Partition by 29.2GB using the slider. Make sure that the unllocated space AFTER the FAT32 partition is 29.2GB and DON'T MESS WITH THE UNALLOCATED SPACE BEFORE THE FAT32 PARTITION! THIS IS SXOS EMUNAND!!
6. Press OK
7. Right Click on the New Unallocated Partition after the FAT32 partition. (once again not the first one. That is your SXOS Partition.)
8. Click CREATE
9. In the "CREATE NEW PARTITION" window Select the following:
   1. Create As: PRIMARY
   2. Drive Letter: NONE
   3. File System: UNFORMATTED
   4. Cluster Size:; NONE
   5. Click OK
10. In the MAIN WINDOW press Apply

That should format the unallocated space so the tools can see it.

Make new Atmosphere Hidden Partition EmuNAND

In EmuTool

1. Under "Select source" select Atmosphere files (Or hekate back up files if that's what you have)
2. Select "Click to select SD Card" and point to the Converted SXOS to Atmosphere Backup files (SX2ATMOemu) or your Atmosphere Backup, You must point to the directory with the BOOT1 BOOT2 00,01 etc etc files, Probably emummc\(A Numeric Code)\eMMC\
3. Under "Select Target" Select Atmosphere Hidden partition
4. Select "Click to select SD card" and point to your Target SD card.
5. Press START.

Restore SD backup and install Atmosphere
If all went well you should be able to copy your SD files you backed up in the beginning of the guide. That should get SXOS back up and running. then you can install Atmosphere. There are a TON of guides. just get the newest SDfiles and toss them on the SD. You'll need sigpatches too if you want to play downloaded content.

1. Copy FILES YOU BACKED UP IN THE BEGINNING OF THE GUIDE back to the SD FAT32 Partition .
2. Copy all Atmosphere files to your SD
3. Copy Sigpatches to the SD

If you are converted your EmuNAND from SXOS to Atmosphere and you didn't shrink your EmuNAND you need to copy the files in the EMUTENDO folder contents from SXOS to the Atmosphere NINTENDO folder (emuMMC/XXXX/Nintendo, XXXX is a Alpha Numeric 4 digit ID) this should make everything compatible work.
(Remember games installed with the built in SXOS installer will probably need to be reinstalled.)

Make EmuNAND visible to Atmosphere.

1. Unzip Hekate files to the ROOT of your SD.
2. Insert SD in to the Switch
3. Boot Hekate using the hekate payload and your favorite payload launching method.
4. Select EmuMMC
5. Select Migrate EmuMMC
6. Select Fix Raw
7. Select OK

Now you should be able to boot in to SXOS and Atmosphere each with their own EmuNANDS!!! Just boot the payload for the CFW you want using your favorite injection method.

Now you can update the firmware for your Atmosphere EmuNAND using daybreak. There are MANY guides on the subject. Google it!

Make sure your games work. Then you can uninstall duplicate games from the SXOS. You can move games from SD to System NAND in the Switch Data management Menu while in EmuNAND. This will move them from the FAT32 partition to the Hidden EmuNAND to free up the FAT32 even more. Remember to leave room for save files.


EXTRAS!

Here I would like to make a few suggestions....

TESLA with the FastCFWSwtich overlay,

If you would like a convenient way to switch between the CFWs (and other things too) I recommend you install TESLA with the FastCFWswitch overlay. Once installed you can Hold down L and DPad Down then Click the right joy stick to bring up Tesla at any time. It allows you to run "overlays" that are basically just homebrew programs. Emuiibo is a great Amiibo emulator, there is a fast reboot, a UMS feature, FTP etc. in this case I recommend FastCFWswitch.

FastCFWswitch allows you to switch between different CFWs with a few clicks.

TESLA page on GBATemp
This is the page for Tesla. In this instance the trick is to install it for BOTH SXOS AND ATMOSPHERE.

1. Download the latest fastCFWswitch NX-ovlloader and Tesla-Menu
2. Unzip all to the root of the SD
3. You must manually copy all the \atmosphere\contents files from NX-ovloader zip file to SXOS\titles\ to make it work in SXOS too, (I will make a pack if the developer gives me the green light.)

That's it. in SXOS or Atmosphere you can press the hotkey combo.. (hold down L and DPad Down and Click the right joy stick) to bring up the TESLA menu, then select fastCFWswitch and the CFW you want and off you go.

I suggest using different themes on your EmuNANDs so that you can tell them apart at a glance. There are SXOS and Atmosphere versions of my skeletal themes,

Skeletal Switch Theme
Skeletal TV theme
Skeletal HDD for SXOS Theme <-- Made this today

I will add more stuff and tweak this out as I have time. Please feel free to ask questions. It will help me fine tune this tutorial.

CHEERS!

Thanks to Maupiti for all the help.

 

[jimmmeh]

1. I have Tesla/fastCFWswitch working between SXOS and Atmosphere (and vice versa). You have to approach it from the perspective of a completely new install of the stack on SXOS with just a shared config file.

2. For the config I used hekate.bin to boot everything (well, update.bin so I didn’t have to change the name between releases) and made use of the ID system so basically everything is booted by Hekate but you pass what you want Hekate to boot. I‘m adding a snippet of my config/fastCFWswitch/config.ini and my bootloade/hekate_ipl.ini so you can get the gist…there’s stuff that’s specifically for my system and you need to massage things for your setup so I don’t recommend you copy them directly.

Spoiler: hekate_ipl.ini

[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=55
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
emummcforce=1
kip1=atmosphere/kip_patches/*
logopath=/graphics/splash/atmosphere.bmp
icon=/graphics/icons/current/atmosphere.bmp
id=atmo

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=/graphics/icons/current/stock.bmp
id=sysn

[SX OS]
payload=bootloader/payloads/sxos.bin
logopath=/graphics/splash/sxos.bmp
icon=/graphics/icons/current/icon_sxos.bmp
id=sxos

Spoiler: config.ini

[CFWS]
type=section
name=CFW

[ATMOSPHERE]
name=atmosphere
path=/bootloader/update.bin
bootId=atmo

[SXOS]
name=sxos
path=/bootloader/update.bin
bootId=sxos

[LAKKA]
name=lakka
path=/bootloader/update.bin
bootId=lakk

[ANDROID]
name=android
path=/bootloader/update.bin
bootId=andr

[L4T]
name=ubuntu
path=/bootloader/update.bin
bootId=ubun

[SYSNAND]
name=sysnand
path=/bootloader/update.bin
bootId=sysn

[TOOLS]
type=section
name=TOOLS

[HEKATE]
name=hekate
path=/bootloader/update.bin

[LOCKPICKRCM]
name=lockpick
path=/bootloader/payloads/Lockpick_RCM.bin

[CPR]
name=CPR
path=/bootloader/payloads/CommonProblemResolver.bin

[UMS]
type=section
name=UMS

[SD_CARD]
name=SD
path=/bootloader/update.bin
ums = sd

[EMMC_BOOT_0]
name=EMMC BOOT 0
path=/bootloader/update.bin
ums = emmc_boot0

[EMMC_BOOT_1]
name=EMMC BOOT 1
path=/bootloader/update.bin
ums = emmc_boot1

[EMMC_GPT]
name=EMMC GPT
path=/bootloader/update.bin
ums = emmc_gpt

[EMU_BOOT_0]
name=EMU BOOT 0
path=/bootloader/update.bin
ums = emu_boot0

[EMU_BOOT_1]
name=EMU BOOT 1
path=/bootloader/update.bin
ums = emu_boot1

[EMU_GPT]
name=EMU GPT
path=/bootloader/update.bin
ums = emu_gpt

Ahh thanks so much for this - I think I know why it wasn't working on SX OS - or at least it seemed to be related to the firmware version - so initially my sys, sx os and atmosphere emunands were all running 4.0.1 - I upgraded atmosphere to 13.2 possibly before trying the overlay - it worked but SX OS one was still at 4.0.1 - I updated the SX OS emunand to 11 and now it's working - I think I was getting confused with what the payloads were for the rest - it should just be the thing that I am sending to my switch via TegraRcmSmash I guess which as you've pointed out I can just configure in hekate and link that way!

Thanks again!

 

[Sovikos]

autonogc setting is what you’re looking for. It used to be in the deprecated stratosphere.ini. You can get to it via GUI in Hekate/Nyx.

I see it and it's set to on... do I turn it off then?

 

[binkinator]

I see it and it's set to on... do I turn it off then?

Let’s not flip settings without understanding the full issue. I’m making an assumption that you recently upgraded Atmosphere as part of this process. By default SciresM set it up so you don’t burn your game card fuses if you were below 9.0.0. The down side to that is your game card will be disabled and you’ll get this message if you try to play a game card. Its quite possible I’ve assumed incorrectly so if this is not your scenario we have something else on our hands.

 

[Sovikos]

Let’s not flip settings without understanding the full issue. I’m making an assumption that you recently upgraded Atmosphere as part of this process. By default SciresM set it up so you don’t burn your game card fuses if you were below 9.0.0. The down side to that is your game card will be disabled and you’ll get this message if you try to play a game card. Its quite possible I’ve assumed incorrectly so if this is not your scenario we have something else on our hands.

Yeah I'm trying to migrate from SXOS SysNAND to a dual boot with Hidden SXOS EmuNAND and Hidden ATM EmuNAND.

 

[binkinator]

Yeah I'm trying to migrate from SXOS SysNAND to a dual boot with Hidden SXOS EmuNAND and Hidden ATM EmuNAND.

What version of FW are you coming from on Sysnand and what versions are on both of your new hidden emunands?
are you in fact attempting to play a game card based game?

 

[Sovikos]

I'm on 11.0.0 and both hidden emunands are supposedly copies of those, except under Launch in Hekate, none of them Launch SXOS...

All seem to be ATM except Stock.

Wasn't trying to play any game on cart, I just had a cart in there so that message would pop up anytime I went into ATM.

 

[binkinator]

I'm on 11.0.0 and both hidden emunands are supposedly copies of those, except under Launch in Hekate, none of them Launch SXOS...View attachment 291980 All seem to be ATM except Stock.

Wasn't trying to play any game on cart, I just had a cart in there so that message would pop up anytime I went into ATM.

Please post your hekate_Ipl.ini.

Should probably pull the cart out to see if ATM will run clean without it.

 

[Sovikos]

Please post your hekate_Ipl.ini.

Should probably pull the cart out to see if ATM will run clean without it.

Here is my hekate_ipl.ini that is in /bootloader/

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=82
autohosoff=1
autonogc=0
updater2p=0
bootprotect=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

Here is the root of my SD card. This tutorial in the OP just says copy the files I backed up back onto the hard drive, but I have a feeling it's missing a step and I need to put them under emuMMC or Emutendo as well? I am not sure??

Right now I took the card out and everything is fine. That message doesn't come up anymore

 

[binkinator]

Here is my hekate_ipl.ini that is in /bootloader/

Heres mine:

I auto boot my (emmunand based) ATM (autoboot=1) after 1 second (bootwait=1) with auto No Game Card turned on (autonogc=1).

You’re missing an SXOS section pointing to the payload you would normally use to start SXOS (mine is called sxos.bin). This is the payload that will kick off your boot.dat and thus SXOS.

Dont copy paste mine as my splashscreens (logopath) and icons are specific to my setup. Just get the gist of whats going on and use what makes sense for your setup.

Spoiler: hekate_ipl.ini

[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=55
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
emummcforce=1
kip1=atmosphere/kip_patches/*
logopath=/graphics/splash/atmosphere.bmp
icon=/graphics/icons/current/atmosphere.bmp
id=atmo

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=/graphics/icons/current/stock.bmp
id=sysn

[SX OS]
payload=bootloader/payloads/sxos.bin
logopath=/graphics/splash/sxos.bmp
icon=/graphics/icons/current/icon_sxos.bmp
id=sxos

Here is the root of my SD card. This tutorial in the OP just says copy the files I backed up back onto the hard drive, but I have a feeling it's missing a step and I need to put them under emuMMC or Emutendo as well? I am not sure??

Right now I took the card out and everything is fine. That message doesn't come up anymore

View attachment 291989

Off the cuff this looks like a reasonable file structure for Atmosphere. The emummc.ini will contain which directory it’s actually using and have a pointer to the disk offset where your hidden partition starts. If you’re missing any of the directories I believe it will create them for you as needed. One of them probably isn’t needed but it’s not gonna hurt anything either.

Let’s get you dual booting first and you can carefully clean things up afterwards.

 

[Sovikos]

Heres mine:

I auto boot my (emmunand based) ATM (autoboot=1) after 1 second (bootwait=1) with auto No Game Card turned on (autonogc=1).

You’re missing an SXOS section pointing to the payload you would normally use to start SXOS (mine is called sxos.bin). This is the payload that will kick off your boot.dat and thus SXOS.

Dont copy paste mine as my splashscreens (logopath) and icons are specific to my setup. Just get the gist of whats going on and use what makes sense for your setup.

Spoiler: hekate_ipl.ini

[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=55
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
emummcforce=1
kip1=atmosphere/kip_patches/*
logopath=/graphics/splash/atmosphere.bmp
icon=/graphics/icons/current/atmosphere.bmp
id=atmo

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=/graphics/icons/current/stock.bmp
id=sysn

[SX OS]
payload=bootloader/payloads/sxos.bin
logopath=/graphics/splash/sxos.bmp
icon=/graphics/icons/current/icon_sxos.bmp
id=sxos

Off the cuff this looks like a reasonable file structure for Atmosphere. The emummc.ini will contain which directory it’s actually using and have a pointer to the disk offset where your hidden partition starts. If you’re missing any of the directories I believe it will create them for you as needed. One of them probably isn’t needed but it’s not gonna hurt anything either.

Let’s get you dual booting first and you can carefully clean things up afterwards.

OK I see... Had no clue about the .ini file and the settings. I will look into that when I get home here later today. Brought my Switch with me, but forgot the MicroSD reader for my laptop. As for the file structure, I should actually learn what they all are. Before I moved my files over there was EmuMMC and Emutendo... Can you tell me what these folders correspond to or are used for?

Right now I would be happy with just wiping out all the games I've installed and starting fresh... But I am not sure how I do that just yet, as they all seem to show 0 bytes in SXOS and ATM, but I might need to do some more testing here. I have all the saves backed up I believe anyway. Only thing I care about right now is getting Animal Crossing going for my kids lol. I've tried reinstalling the game and the updates (to which I believe was the last version I had), but the game doesn't seem to want to start yet on either CFW. I am guessing I don't have the update installed that I was on before I did all this. But that's something to worry about later, as I am hoping once I update to FW 13.2 in ATM that the latest Animal Crossing update will work.

I will get back to you though once I look at the ini files later. Thank for your help!

 

[binkinator]

OK I see... Had no clue about the .ini file and the settings. I will look into that when I get home here later today. Brought my Switch with me, but forgot the MicroSD reader for my laptop. As for the file structure, I should actually learn what they all are. Before I moved my files over there was EmuMMC and Emutendo... Can you tell me what these folders correspond to or are used for?

Right now I would be happy with just wiping out all the games I've installed and starting fresh... But I am not sure how I do that just yet, as they all seem to show 0 bytes in SXOS and ATM, but I might need to do some more testing here. I have all the saves backed up I believe anyway. Only thing I care about right now is getting Animal Crossing going for my kids lol. I've tried reinstalling the game and the updates (to which I believe was the last version I had), but the game doesn't seem to want to start yet on either CFW. I am guessing I don't have the update installed that I was on before I did all this. But that's something to worry about later, as I am hoping once I update to FW 13.2 in ATM that the latest Animal Crossing update will work.

I will get back to you though once I look at the ini files later. Thank for your help!

Nintendo folder is where OFW stores games/screenshots/etc. Emmutendo is where SXOS stores games/screenshots/etc.

Emmumc/XXXX/ is an instance of Atmosphere where XXXX is a unique identifier. There is a corresponding Nintendo folder under that path that stores games/screenshots/etc.

You can delete the other XXXX path but like I said it won’t hurt anything. We should get everything working first.
(If/when you want to get rid of it, just move it somewhere else and make sure everything still works and only then delete it.)

The emmumc.ini file under the emummc directory will tell you which XXXX path is the active one and the sector (in hex) on the SDcard where the raw partition starts.

Here is what mine looks like. Yours will be different depending upon where your data actually sits so don’t copy mine:

Spoiler: emummc.ini

[emummc]
enabled=1
sector=0x2a358000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

 

[DoobyDude]

Just a quick question about keeping SXOS to be able to play games from external drives.

This will only work with games that need firmware v11.0 or lower?
Anything requiring a FW above that needs to be run using Atmosphere from the internal or sd card?

 

[binkinator]

Just a quick question about keeping SXOS to be able to play games from external drives.

This will only work with games that need firmware v11.0 or lower?
Anything requiring a FW above that needs to be run using Atmosphere from the internal or sd card?

Correct. SXOS will not work above 11.0.0. Some games can be modified if they don’t require any of the new libraries but more recent games are being released with new features that cannot be downgraded.

You must use Atmosphere to install NSPs for games requiring 11.0.1 and higher.

 

[Sovikos]

Nintendo folder is where OFW stores games/screenshots/etc. Emmutendo is where SXOS stores games/screenshots/etc.

Emmumc/XXXX/ is an instance of Atmosphere where XXXX is a unique identifier. There is a corresponding Nintendo folder under that path that stores games/screenshots/etc.

You can delete the other XXXX path but like I said it won’t hurt anything. We should get everything working first.
(If/when you want to get rid of it, just move it somewhere else and make sure everything still works and only then delete it.)

The emmumc.ini file under the emummc directory will tell you which XXXX path is the active one and the sector (in hex) on the SDcard where the raw partition starts.

Here is what mine looks like. Yours will be different depending upon where your data actually sits so don’t copy mine:

Spoiler: emummc.ini

[emummc]
enabled=1
sector=0x2a358000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

Ok sorry I haven't had anytime to get on here and finish this, so I apologize, but I am very appreciative of your help so far. So anyways here is my emummc.ini file, looks similar to yours and should be fine right?

Spoiler: emummc.ini

[emummc]
enabled=1
sector=0x2a3438e9
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

As for my hekate_ipl.ini, I noticed 3 of them (in bold) look to be pretty much almost the exact same thing right? I've added SXOS to the bottom, not sure if I keep the id=sxos like yours has? Also noticed autohosoff=1 and updater2p=0 are different from yours. I looked up what they are, but honestly have no idea what they mean or are lol. Should I just leave them as they are? What should I remove or add to mine?

Spoiler: hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=82
autohosoff=1
autonogc=1
updater2p=0
bootprotect=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

[SX OS]
payload=bootloader/payloads/payload.bin
icon=/graphics/icons/current/icon_payload.bmp
id=sxos

Here is my SD Card in MiniTool too just incase. It shows a weird drive name for the middle part there, and that came after I had reformatted it.

Spoiler: SD Card

https://gbatemp.net/attachments/1641415051935-png.292516/

 

[binkinator]

Ok sorry I haven't had anytime to get on here and finish this, so I apologize, but I am very appreciative of your help so far. So anyways here is my emummc.ini file, looks similar to yours and should be fine right?

Spoiler: emummc.ini

[emummc]
enabled=1
sector=0x2a3438e9
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

emmumc.ini looks good.

As for my hekate_ipl.ini, I noticed 3 of them (in bold) look to be pretty much almost the exact same thing right? I've added SXOS to the bottom, not sure if I keep the id=sxos like yours has? Also noticed autohosoff=1 and updater2p=0 are different from yours. I looked up what they are, but honestly have no idea what they mean or are lol. Should I just leave them as they are? What should I remove or add to mine?

Spoiler: hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=82
autohosoff=1
autonogc=1
updater2p=0
bootprotect=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

[SX OS]
payload=bootloader/payloads/payload.bin
icon=/graphics/icons/current/icon_payload.bmp
id=sxos

The highlighted ones are close looking but are very different in action.

First one runs CFW on the stock nand
Second one runs CFW on emunand
Third one runs without CFW on stock nand

You want to boot the second one.

You can make it always boot the second entry automatically by changing autoboot=0 to autoboot=2.
If you ever want to override the autoboot just hit (Vol -) when the Hekate splash screen displays.

autohosoff=1is fine. It is an edge case power-off thing. It won’t impact you so you can leave it default. Read up on this and AutoRCM at a later date.

updater2p=1 means my Hekate checks and updates my reboot2payload to be Hekate if it ever changes to anything else. I do everything through Hekate so I was being pedantic. You can leave it default of 0 for now. It won’t impact anything either.

Here is my SD Card in MiniTool too just incase. It shows a weird drive name for the middle part there, and that came after I had reformatted it.

Spoiler: SD Card

View attachment 292516
https://gbatemp.net/attachments/1641415051935-png.292516/

This name is only for Windows. You might want to change ito something reasonable but I don’t think you have to for any Switch reasons.

 

[Sovikos]

The highlighted ones are close looking but are very different in action.

First one runs CFW on the stock nand
Second one runs CFW on emunand
Third one runs without CFW on stock nand

You want to boot the second one.

You can make it always boot the second entry automatically by changing autoboot=0 to autoboot=2.
If you ever want to override the autoboot just hit (Vol -) when the Hekate splash screen displays.

autohosoff=1is fine. It is an edge case power-off thing. It won’t impact you so you can leave it default. Read up on this and AutoRCM at a later date.

updater2p=1 means my Hekate checks and updates my reboot2payload to be Hekate if it ever changes to anything else. I do everything through Hekate so I was being pedantic. You can leave it default of 0 for now. It won’t impact anything either.

OK. Now those 3 all will run Atmosphere then as they point to package3? The Stock FW, is that my sysNAND then where I originally had SXOS?

Also the Fusee one, I can just delete that one right?

The SXOS one I added above, is that running off SysNAND or EmuNAND then?

My next step I guess is testing them out and then possibly updating to Firmware 13.2.0 on the ATM emuMMC correct?

Oh and what program should I use to install games and such now?

 

[Sovikos]

I found when using Goldleaf on ATM EmuMMC that I run into this problem though:

https://gbatemp.net/threads/invalid...-a-too-low-firmware-4518.582479/#post-9542714

So I wonder if maybe I should use the Fusee one to launch?

Also the system seems to crash in ATM EmuMMC games I installed while under the Fusee one. I am not sure if I ever got any games to install under ATM EmuMMC yet.

 

[binkinator]

OK. Now those 3 all will run Atmosphere then as they point to package3? The Stock FW, is that my sysNAND then where I originally had SXOS?

1 and 2 are atmosphere.
3 does not do atmosphere…it’s OFW on Sysnand (stock)

For SXOS you need a copy of the sx bootloader. Rename it to match (or change the following line to point to wherever you put it):

payload=bootloader/payloads/payload.bin

Then you use Hekate to boot it and it will in turn kick off your boot.dat and reference your license.dat files…just like normal SXOS except you start it fro, the Hekate menu. One stop shopping

Also the Fusee one, I can just delete that one right?

There are so,e edge cases where it can be useful but to keep things simple you don’t need that entry.

The SXOS one I added above, is that running off SysNAND or EmuNAND then?

For SXOS you need to be sure to enable hidden partition emmunand in the boot tool. You might need to hit (Vol -) during the SXOS splash screen to get to the tools.

My next step I guess is testing them out and then possibly updating to Firmware 13.2.0 on the ATM emuMMC correct?

Make sure you set up exosphere.ini before hand.

See step #3 in this doc:
https://rentry.org/EristaSysNAND

Once set up make sure you select CFW on emunand (entry #2) and use Daybreak to upgrade your firmware.

Oh and what program should I use to install games and such now?

Any of the major installers will do. I have Tinfoil and Awoo but it‘s religion really.

 

[Sovikos]

For SXOS you need to be sure to enable hidden partition emmunand in the boot tool. You might need to hit (Vol -) during the SXOS splash screen to get to the tools.



Make sure you set up exosphere.ini before hand.

See step #3 in this doc:
https://rentry.org/EristaSysNAND

Once set up make sure you select CFW on emunand (entry #2) and use Daybreak to upgrade your firmware.



Any of the major installers will do. I have Tinfoil and Awoo but it‘s religion really.

I will have to take a look at Tinfoil again or Awoo, but I found when using Goldleaf on that option #2, that I run into this problem though:

https://gbatemp.net/threads/invalid...-a-too-low-firmware-4518.582479/#post-9542714

So I wonder if maybe I should use the Fusee one to launch?

Also the system seems to crash in ATM EmuMMC on games I installed while under the Fusee one. I am not sure if I ever got any games to install under ATM EmuMMC yet.

Another question, with all the old crap I had installed from before, how do I just delete all that stuff? I really only care about keeping my users and the Animal Crossing saves I think. I found when I went into Data Management, almost all the games showed 0 Bytes.

 

[binkinator]

I will have to take a look at Tinfoil again or Awoo, but I found when using Goldleaf on that option #2, that I run into this problem though:

https://gbatemp.net/threads/invalid...-a-too-low-firmware-4518.582479/#post-9542714

if it’s exactly like that thread…you prolly need to upgrade FW daybreak and that “dark sternie firmware”.

So I wonder if maybe I should use the Fusee one to launch?

Also the system seems to crash in ATM EmuMMC on games I installed while under the Fusee one. I am not sure if I ever got any games to install under ATM EmuMMC yet.

Another question, with all the old crap I had installed from before, how do I just delete all that stuff? I really only care about keeping my users and the Animal Crossing saves I think. I found when I went into Data Management, almost all the games showed 0 Bytes.

‘You can remove them using the built in DataManage….the fact that they are showing 0 bytes means you just have the index and it cant find the actual data. Deleting them and reinstall is a quick solution.