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.

 

[binkinator]

So file based for SX OS is the way to go? That's what I thought, too much at play on a single SD Card, I remember before Hekate introduced the Partition Manager I had to use this Linux script that barely worked in order to get Linux, Android, EmuNAND, and Lakka all working at once. I would hate to have to do anything like that again, so just using a file partition saves me the headache, and cost vs risk isn't too bad. Thanks.

disclaimer: Files based emunand is susceptible to file system corruption. Partition based emunands, while on the same sd card, are isolated from the files system.

It’s the only way I could get all of mine running on the same card. I honestly tried for a long time.

Maybe @mikefor20 or someone else has a better way make this happen.

 

[OldGnashburg]

I did this and the issue I ran into was that SXOS requires that its emunand partition be the first partiton on the sdcard. This is fine if you have Atmos and SXOS dual boot because you only need three partitions (Atmos and SXOS emunand partitions on the ends and fat32 in the middle). This all works using MBR. You can even add L4T without any issues…however, when you add Android, it requires another 1/2 dozen partitions, which requires you to use GPT and GPT uses some of the initial sd card range that SXOS uses for its Emunand so the Header corrupts the partition and SXOS won’t boot anymore. I ”solved” this by running SXOS using a shrunken files based Emunand. I only use SXOS to run mounted XCIs so the need to write to disk (and therefore the risk of corruption) is greatly reduced. Since I don’t install anything, if I lose it all, I don’t have to recover anything anyway so it’s all good…in my mind.

I’m open to suggestions if anyone has worked out a way around this…nit saying it can‘s be done…just wasn’t done by me.

So I've converted an 11.0.0 EmuNAND to an SXOS filebased EmuNAND, I have an Atmosphere partition based EmuNAND, Android, Linux, and Lakka all on the SD, but when I try to launch the sxos payload it just reboots back to Hekate almost instantly. Is it trying to read the partition and not the file-based NAND? How do I force it to go filebased?

 

[binkinator]

So I've converted an 11.0.0 EmuNAND to an SXOS filebased EmuNAND, I have an Atmosphere partition based EmuNAND, Android, Linux, and Lakka all on the SD, but when I try to launch the sxos payload it just reboots back to Hekate almost instantly. Is it trying to read the partition and not the file-based NAND? How do I force it to go filebased?

What does your hekate_ipl.ini look like?

 

[OldGnashburg]

What does your hekate_ipl.ini look like?

[config]
autoboot=0
autoboot_list=0
bootwait=5
backlight=220
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
{}

[Atmosphere EmuNAND]
fss0=atmosphere/package3
cal0blank=1
kip1patch=nosigchk
kip1=atmosphere/kips/*
icon=bootloader/res/atmosphere.bmp
{}
[SXOS Boot]
payload=bootloader/payloads/sxos.bin
logopath=bootloader/res/bootlogo_sx.bmp
icon=bootloader/res/icon_sxos.bmp
{}
[Atmosphere SysNAND]
fss0=atmosphere/package3
cal0blank=1
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
[SXOS]
payload=bootloader/payloads/sxos.bin
logopath=bootloader/res/bootlogo_sx.bmp
icon=bootloader/res/icon_sxos.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

All the files seem to be the right stuff.

 

[binkinator]

[config]
autoboot=0
autoboot_list=0
bootwait=5
backlight=220
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
{}

[Atmosphere EmuNAND]
fss0=atmosphere/package3
cal0blank=1
kip1patch=nosigchk
kip1=atmosphere/kips/*
icon=bootloader/res/atmosphere.bmp
{}
[SXOS Boot]
payload=bootloader/payloads/sxos.bin
logopath=bootloader/res/bootlogo_sx.bmp
icon=bootloader/res/icon_sxos.bmp
{}
[Atmosphere SysNAND]
fss0=atmosphere/package3
cal0blank=1
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
[SXOS]
payload=bootloader/payloads/sxos.bin
logopath=bootloader/res/bootlogo_sx.bmp
icon=bootloader/res/icon_sxos.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

All the files seem to be the right stuff.

Assuming you've confirmed this file does in fact exist: bootloader/payloads/sxos.bin
What happens if you inject your sxos.bin file directly during RCM?

e: some big brain reading about files based emunand. The pdf they put together is pretty darn cool.
https://gbatemp.net/threads/sxos-and-atmosphere-sharing-emunand-android-10-accessing-fat32.587563/
(meaning it’s not directly applicable to your use case but…it‘s just for edutainment and better understanding of how GPT and SXOS clash)

 

[OldGnashburg]

Same thing, just boots into Hekate, and yeah sxos.bin is in the right path. Is there a config to force SXOS to launch a file-based EmuNAND?

 

[binkinator]

Same thing, just boots into Hekate, and yeah sxos.bin is in the right path. Is there a config to force SXOS to launch a file-based EmuNAND?

That shouldn't be. It should be giving you SXOS failure messages at worst and handing off to boot.dat at best.

Here are some specs (size and md5 checksum) on my sxos.bin file so we can make sure you have the right file.

# ls -la sxos.bin
-rw-r--r-- 1 wwiii wwiii 27748 Sep 28 2021 sxos.bin
# md5sum.exe sxos.bin   bash  18:21:4
3a21fe841873361be05384459cb64e81 *sxos.bin

 

[mikefor20]

So I've converted an 11.0.0 EmuNAND to an SXOS filebased EmuNAND, I have an Atmosphere partition based EmuNAND, Android, Linux, and Lakka all on the SD, but when I try to launch the sxos payload it just reboots back to Hekate almost instantly. Is it trying to read the partition and not the file-based NAND? How do I force it to go filebased?

I don't condone nor support file based emunands. They are unstable. This tutorial was designed to avoid shoddy file based emunands. There is a ton of tutorials about them. This thread is for dual hidden partitions. You can have android and linux too..

Please discuss file based emunand methods elsewhere.


Thanks

 

[binkinator]

I don't condone nor support file based emunands. They are unstable. This tutorial was designed to avoid shoddy file based emunands. There is a ton of tutorials about them. This thread is for dual hidden partitions. You can have android and linux too..

Please discuss file based emunand methods elsewhere.


Thanks

That was my bad, man. I mentioned it first. I agree files based emunand is susceptible to file system corruption. Added disclaimers and will take it elsewhere to keep your partition based tut thread clean.

 

[OldGnashburg]

I got it working now, I have no idea how. Clearly black magic. And I have clean backup of my (currently) empty SX OS file based EmuNAND, which I will only be using for HDD loading, so not worried about corruption since I'll barely be writing to it. I have a proper partition based Atmosphere EmuNAND. Now I have a Switch with Atmosphere, SX OS, Linux, Android & Lakka, it's perfect.

 

[binkinator]

I got it working now, I have no idea how. Clearly black magic. And I have clean backup of my (currently) empty SX OS file based EmuNAND, which I will only be using for HDD loading, so not worried about corruption since I'll barely be writing to it. I have a proper partition based Atmosphere EmuNAND. Now I have a Switch with Atmosphere, SX OS, Linux, Android & Lakka, it's perfect.

Awesome! Nicely done and congratulations!

I agree that since we’re only mounting XCIs the risk, while not completely eliminated, is greatly reduced.

 

[OldGnashburg]

I don't condone nor support file based emunands. They are unstable. This tutorial was designed to avoid shoddy file based emunands. There is a ton of tutorials about them. This thread is for dual hidden partitions. You can have android and linux too..

Please discuss file based emunand methods elsewhere.


Thanks

Would you have a solution for creating a setup for Partition based EmuNAND and SX OS + Linux + Android + Lakka? Manually creating just the EmuNAND partitions isn't difficult, but once you throw Android and Linux into the equation, things become extremely complex and a binkinator pointed out, things break by doing so because of MBR and GPT issues.

 

[binkinator]

I would LOVE to have SXOS using a partition based emunand for my Atmosphere, SXOS, Android, L4T and LAKKA enabled Switch. I’ve tried numerous ways to make it happen.

The problem statement is this:

Basically, the problem is the combination of these three [two] facts:
- android 10 requires a GPT partition layout, which uses sectors 1,2,... to describe the partitions.
- SXOS hidden partition style emunand is stored in the fixed sectors 1 ( TX NAND mark ) and starting on sector 2 ( actual emunand contents ).

e: from the attached doc btw

 

[OldGnashburg]

I would LOVE to have SXOS using a partition based emunand for my Atmosphere, SXOS, Android, L4T and LAKKA enabled Switch. I’ve tried numerous ways to make it happen.

The problem statement is this:

Basically, the problem is the combination of these three [two] facts:
- android 10 requires a GPT partition layout, which uses sectors 1,2,... to describe the partitions.
- SXOS hidden partition style emunand is stored in the fixed sectors 1 ( TX NAND mark ) and starting on sector 2 ( actual emunand contents ).

e: from the attached doc btw

Okay interesting, the way I read it there might be way? Cool. Btw, I'm having issues, I'm going to assume it has to do with my Game Card reader fuses. Only workaround (that I know of) is AutoNoGC, but if I have that enabled I can't leave a GameCard in when I boot into SX OS, which can be annoying, and if I forget I need to power off the whole Switch, and then put it back into RCM and push another payload. How did you work around this? I have tested XCI HDD loading yet, but don't you need a function GC Reader?

 

[binkinator]

Okay interesting, the way I read it there might be way? Cool. Btw, I'm having issues, I'm going to assume it has to do with my Game Card reader fuses. Only workaround (that I know of) is AutoNoGC, but if I have that enabled I can't leave a GameCard in when I boot into SX OS, which can be annoying, and if I forget I need to power off the whole Switch, and then put it back into RCM and push another payload. How did you work around this? I have tested XCI HDD loading yet, but don't you need a function GC Reader?

That’s my trick…I never buy game cards!

In all seriousness trying to juggle between Atmosphere at 14.1.2 and SXOS stuck at 11.0.0, I would forget about trying to preserve the feature for the outdated SXOS and just run my game cards on Atmosphere with latest and greatest FW both for HOS and the GC. I have GC disabled and don’t have issues mounting XCIs.

e:

on second thought, if you haven’t upgraded GC firmware beyond what’s required for 11.0.0, maybe just keep it enabled and down rev on SXOS and permanently disable for Atmosphere.

 

[OldGnashburg]

That’s my trick…I never buy game cards!

In all seriousness trying to juggle between Atmosphere at 14.1.2 and SXOS stuck at 11.0.0, I would forget about trying to preserve the feature for the outdated SXOS and just run my game cards on Atmosphere with latest and greatest FW both for HOS and the GC. I have GC disabled and don’t have issues mounting XCIs.

e:

on second thought, if you haven’t upgraded GC firmware beyond what’s required for 11.0.0, maybe just keep it enabled and down rev on SXOS and permanently disable for Atmosphere.

So XCI's work. My SysNAND is on latest, EmuNAND is like one or 2 FW behind, and SX OS EmuNAND is on 11.0.0. So keep AutoNoGC enabled? What do you mean by Down Rev on SXOS and permanently disable for Atmosphere?

And lol, at this point over the last 4 years I've probably spent nearly 1500 (in Canadian money, games are $80 here) on legit purchases just for my Switch. The Nintendo folder on my SD card alone is like 200GB or whatever, and that's with a large chunk of my games being cartridge only. Which is why I'm extremely frustrated that SX OS is the only way I can mount XCI's off HDD. When I have a partition based EmuNAND add another 232GB, plus ROM's and ISO's for Lakka/Retroarch plus 128GB for Linux, plus 32GB for Android. I have a 1TB microSD, they don't make anything bigger and I'm already just using half of it without pirating a single thing.

 

[dmc310]

So I had atmosphere and sx os on my sysnand and it never touched online but I recently decided to completely revert my switch to stock clean ofw to play online, would I be able to have SX OS and atmosphere EmuNAND and just have a stock OFW when I want to play legit?

 

[binkinator]

So I had atmosphere and sx os on my sysnand and it never touched online but I recently decided to completely revert my switch to stock clean ofw to play online, would I be able to have SX OS and atmosphere EmuNAND and just have a stock OFW when I want to play legit?

You would need to restore a backup from the last time your Switch checked in w/ Ninty. This would ensure the logs matched up. Log discrepancies are reported to be a bannable offense. You certainly wouldn’t want to do nothing about the logs you currently have in Sysnand because they will have a record of anything dirty you might have done, such as install XCIs or NSPs. One way to remedy the dirty log issue is to clean them with Haku33. Clean logs are suspicious as well but there are folks that say they’ ve done it and not been banned so it’s a decision you will have to make yourself.

bottom line: best way is to restore a clean backup. Everything else adds a non-zero amount of risk.

Once everything is clean, you absolutely can run Atmos and SXOS on Emunand Offline and clean OFW to play Online. This is how I run my Switch and it was done pretty closely inline with this guide.

 

[dmc310]

Thank you for the response I did restore back to a previous nand before it touched cfw I think? I also went thru Tegraexplorer payload and used the systemwipe script is that a less effective method than Haku33 I am already on 14.1.0 and using it online but now wanted to set up an emunand with Atmosphere and SX OS if I can idk if it will work now that I am on 14.1.0 officially stock I appreciate the help

 

[binkinator]

Thank you for the response I did restore back to a previous nand before it touched cfw I think? I also went thru Tegraexplorer payload and used the systemwipe script is that a less effective method than Haku33 I am already on 14.1.0 and using it online but now wanted to set up an emunand with Atmosphere and SX OS if I can idk if it will work now that I am on 14.1.0 officially stock I appreciate the help

You absolutely can. Start at the beginning of this tutorial and methodi walk through it. You will need to use the daybreak.nro that comes with atmosphere to “downgrade” the emunand you want to use for SXOS but other than that you just start at the top and work through each step.