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

[binkinator]

If I don't plan on going online, is there still a reason to have both EmuNANDs? My oldest NAND backup is post-SXOS. Should I just save the extra space by having one hidden partition for SXOS and putting Atmosphere on my SysNAND?

Having something to copy and fiddle with as necessary is comforting. also helps knowing that if the odd brickware somehow makes it in, the grenade will blow up inside a copy rather than inside the system itself. This guide goes through how to shrink an emunand as well, so you’re not saving that much space.

 

[simbin]

helps knowing that if the odd brickware somehow makes it in, the grenade will blow up inside a copy rather than inside the system itself

Good point, thanks

 

[mikefor20]

Good point, thanks

Yes, EmuNANDs are protection. While in EmuNAND it's like a completely separate Switch. In fact, you can have as many EmuNANDS on many SD cards. I made separate EmuNANDS for Kids and for Adults. That way I keep my save files safe and I can have kid friendly games only for them.

I would also like to point out that the EmuNAND space is not wasted. You can install to it. The majority of it will be used by your games.When in EmuNAND if you install to System you are installing to the EmuNAND. IIRC about 2GB is for the system files. The remainder is used when installing to EmuNAND.

Plus you can shrink the EmuNAND.

I use 6GB for SXOS. I only use it for archival purposes. During the guide I copied and converted the SXOS EmuNAND to an Atmopshere EmuNAND. Bringing with it All my saves and my installed games. I have >11.0 Games on the USB drive in Super XCI. That way all the DLC and UPDATES are in the XCI on the HDD as well.. I deleted all installed games and DLC then I shrank down the SX EmuNAND (this breaks installed content in the SXOS EmuNAND anyway but not the saves) . The SXOS EmuNAND is only for save files on my system. 6GB has been enough for me. Mileage may vary. Consider your needs.

 

[simbin]

I use 6GB for SXOS.

Wow! That's even better than I expected. Does the shrinking process just hard cut all your installed data, so you only need to delete whatever tiny amount of broken remnants are left afterwards?

Am I also understanding correctly that I can build both EmuNANDs from the rawnand.bin I dumped of SysNAND?

 

[mikefor20]

Emunand files is basically a portable emunand folder structure that allows you to make backup copies of the said emunand to store on a PC or USB drive. It holds all the cache data like game icons user accounts ect
I think the key point that most ppl are missing is that Emunand files is a great option to have if you decided to upgrade your SD card b/c its a simple drag and drop on the new card. There are ways to back up partition, but its more complicated and requires specific software to do it. So personally if you don't care enough to upgrade the SD card just go hidden partition.

This is terrible advice. While most of the above is true it's missing the most important part.The important difference between Files based vs Hidden EmuNAND is corruption. Hidden EmuNANDs are very stable. No R/W issues. No corrupting if you power off at the wrong time. Outside of removing the SD during a write operation you're okay. SDs can fail anyway but when you are dealing with a file based EmuNAND you're dealing with the switch's shitty SD drivers. The FAT32.standard is better than ExFAT on switch but it's still shit. Just use hidden EmuNANDs. No.corruption or allocation errors.

To backup your EmuNAND or move it, you can use the tools in the tutorial. Or clone your SD bit by bit. It's easy and definately not a reason to stick with a shoddy file based EmuNAND.

 

[MastaG]

Thanks for the detailed guide.
I currently have Hekate + Atmosphere installed and I'm using the AIO switch updater app for everything.
It has a copy_files.txt file which will copy the Hekate update.bin payload to the root of my SD called "/payload.bin" which gets picked up by the RCM x86 chip.
This makes it so I don't have to connect the switch to my PC ever for updates.

I find atmosphere a very good CFW and I like his detailed changelogs very much.

What's the benefit of having SX OS compared to Hekate/ams?

 

[MasterJ360]

This is terrible advice. While most of the above is true it's missing the most important part.The important difference between Files based vs Hidden EmuNAND is corruption. Hidden EmuNANDs are very stable. No R/W issues. No corrupting if you power off at the wrong time. Outside of removing the SD during a write operation you're okay. SDs can fail anyway but when you are dealing with a file based EmuNAND you're dealing with the switch's shitty SD drivers. The FAT32.standard is better than ExFAT on switch but it's still shit. Just use hidden EmuNANDs. No.corruption or allocation errors.

To backup your EmuNAND or move it, you can use the tools in the tutorial. Or clone your SD bit by bit. It's easy and definately not a reason to stick with a shoddy file based EmuNAND.

Yes I know Fat32 is better its pretty basic in the scene. Ive been using the Emunand SD file for sxos ever since 2018. Yes I did have 3 SD failures simply b/c I was using homebrew heavy apps with an exfat dumping copies of my owned games/dlc. But thats not a daily use issue atleast for me from years of experience, thats all im saying. SD Emunand file recovery is just a simple drag/drop no tutorials or steps needed.

I do use hidden Emu for my Atmosphere switch b/c its fat32. Overall, corruption is not a problem aslong you have a backup to recover data.

 

[binkinator]

Thanks for the detailed guide.
I currently have Hekate + Atmosphere installed and I'm using the AIO switch updater app for everything.
It has a copy_files.txt file which will copy the Hekate update.bin payload to the root of my SD called "/payload.bin" which gets picked up by the RCM x86 chip.
This makes it so I don't have to connect the switch to my PC ever for updates.

I find atmosphere a very good CFW and I like his detailed changelogs very much.

What's the benefit of having SX OS compared to Hekate/ams?

one feature and one feature only…

SXOS can mount XCIs like a virtual game card instead of having to install it like an NSP. Unfortunately it can only do this for games that require 11.0.0 or less. Still cool af.

 

[simbin]

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

How are you doing this part?
I tried renaming boot.dat to sxos.bin

 

[mikefor20]

Yes I know Fat32 is better its pretty basic in the scene. Ive been using the Emunand SD file for sxos ever since 2018. Yes I did have 3 SD failures simply b/c I was using homebrew heavy apps with an exfat dumping copies of my owned games/dlc. But thats not a daily use issue atleast for me from years of experience, thats all im saying. SD Emunand file recovery is just a simple drag/drop no tutorials or steps needed.

I do use hidden Emu for my Atmosphere switch b/c its fat32. Overall, corruption is not a problem aslong you have a backup to recover data.

It's not just FAT32 that's the issue. the file based option on top of FAT32 is an issue. Just it right. If you like having to back up your EmuNAND frequently and are okay with losing save files, enjoy! I am not here to debate the issue.

FILE BASED EMUNANDS ARE UNSTABLE! Period. Use hidden partitions. They are stable. You cut corners and get what you deserve. I don't care what you do. Please don't come to my thread and promote lazy solutions that lead to more issues. The dual hidden EmuNAND option is sturdy and smart. I don't want to deal with the issues that may arise from noobs making lazy irrational choices due to your misinformed recommendations. I appreciate your intentions but this is the wrong thread for that.

 

[mikefor20]

Wow! That's even better than I expected. Does the shrinking process just hard cut all your installed data, so you only need to delete whatever tiny amount of broken remnants are left afterwards?

Am I also understanding correctly that I can build both EmuNANDs from the rawnand.bin I dumped of SysNAND?

The shrinking process IIRC deletes the data. I still deleted everything maually before hand.for my OCD OCD OCD.. iirc it tells you it is formatting the user partition It may delete the saves. I honestly don't remember. Back everything up and be prepared to restore saves.i dont recall.

You can use the dump to build both. The difference between SX and Atmo EmuNANDs is the location on the SD. The Nand Manager software can convert it. The guide covers that too. Please read it from cover to cover. If something isn't clear let me know and I can fix the guide.

 

[simbin]

Thanks everyone for the help today. I'm going to give it a rest before I mess something up. The good news is that I got all the partitions setup; AMS emuMMC is booting from hekate, and I can manually swap to the SXOS boot.dat for EmuNAND. . so I just need to figure out that little bit, update AMS firmware, and start fixing my games/saves etc. Overall a pretty good day.

 

[mikefor20]

Thanks for the detailed guide.
I currently have Hekate + Atmosphere installed and I'm using the AIO switch updater app for everything.
It has a copy_files.txt file which will copy the Hekate update.bin payload to the root of my SD called "/payload.bin" which gets picked up by the RCM x86 chip.
This makes it so I don't have to connect the switch to my PC ever for updates.

I find atmosphere a very good CFW and I like his detailed changelogs very much.

What's the benefit of having SX OS compared to Hekate/ams?

one feature and one feature only…

SXOS can mount XCIs like a virtual game card instead of having to install it like an NSP. Unfortunately it can only do this for games that require 11.0.0 or less. Still cool af.

I think you forgot to mention,XCI loading AND Usb loading.

Not only can you mount and run XCIs without installing you can mount them directly from any USB storage. You can use HDD,SD with a reader,SSD,Flash drives etc. You can even use a USB -C device or an OTG cable in handheld mode. I use a SSD.or 2 512GB USB C thumb drives in handheld and a 5TB HDD in docked. It's all so easy an 8 yo does it. Best feature ever

Thanks everyone for the help today. I'm going to give it a rest before I mess something up. The good news is that I got all the partitions setup; AMS emuMMC is booting from hekate, and I can manually swap to the SXOS boot.dat for EmuNAND. . so I just need to figure out that little bit, update AMS firmware, and start fixing my games/saves etc. Overall a pretty good day.

Did you go hidden partitions?

 

[simbin]

Did you go hidden partitions?

Yes. 8GB SXOS and full 29.2GB AMS. I was a little worried because NxNandManager didn't show an [Ok] or [Close] button once it finished. I just had to [X] out. I'm not sure if that's why my FAT32 had some garbled text in its name. I just reformatted in MiniTool Partition Wizard, rebuilding lost bits with Migrate emuMMC in Hekate.

Also: EmuTool wouldn't let me convert Hekate Backup Files (rawnand.bin) to Atmosphere Files, even tho the latest changelog said that was fixed. I had to instead create a full SXOS EmuNAND first, to then create my AMS files from there.

 

[MasterJ360]

It's not just FAT32 that's the issue. the file based option on top of FAT32 is an issue. Just it right. If you like having to back up your EmuNAND frequently and are okay with losing save files, enjoy! I am not here to debate the issue.

FILE BASED EMUNANDS ARE UNSTABLE! Period. Use hidden partitions. They are stable. You cut corners and get what you deserve. I don't care what you do. Please don't come to my thread and promote lazy solutions that lead to more issues. The dual hidden EmuNAND option is sturdy and smart. I don't want to deal with the issues that may arise from noobs making lazy irrational choices due to your misinformed recommendations. I appreciate your intentions but this is the wrong thread for that.

Explaining vs promoting are 2 different things. Your right its not a debate its preference - opinionated choice that I took. Lazy & super convenient for SD upgrading, but it works fine for me 4 years straight even with the "unstable" warnings so forgive me if you think im trying to defame your thread. If you don't want my input, anti-sheep wagon or criticism then cry to the Mods about it. I can voice wherever I want.

 

[binkinator]

How are you doing this part?
I tried renaming boot.dat to sxos.bin

It’s just SXLoader‘s payload.bin renamed to something at little more memorable/less generic.

 

[simbin]

It’s just SXLoader‘s payload.bin renamed to something at little more memorable/less generic.

This is where I'm getting stuck. I'm using the SX payload from TegraRcmGUI, but it just goes back to Hekate after launching it. License file is still in root. What am I missing here?

 

[mikefor20]

Explaining vs promoting are 2 different things. Your right its not a debate its preference - opinionated choice that I took. Lazy & super convenient for SD upgrading, but it works fine for me 4 years straight even with the "unstable" warnings so forgive me if you think im trying to defame your thread. If you don't want my input, anti-sheep wagon or criticism then cry to the Mods about it. I can voice wherever I want.

Wrong again. It's not a preference, it's a mistake. And a stupid one at that. Don't spread your bullshit. I don't care what you think. It's not a sheep wagon situation. This thread is about the correct, long term solution. There are already a ton of threads where lazy idiots circle jerk and pat each other on the back for their laziness. Go there. To come to this thread to promote your fail and look for approval is sad. And against policy. You are an irritant and not "in the spirit of the thread". I believe in complete information. I presented the other options. That's why i already addressed the reasons to avoid file based nands. You advice is piss poor. You have no viable argument. Just feelings. What's next? Tell people to use the EmuNAND on your NAND option? Please! You never had an issue? That's like me telling people not to use a condom because "I never had an issue". Go somewhere else. I don't need nor appreciate your erroneous input Leave. Troll.

 

[binkinator]

This is where I'm getting stuck. I'm using the SX payload from TegraRcmGUI, but it just goes back to Hekate after launching it. License file is still in root. What am I missing here?

To get the original files from TX you‘re gonna have to use the way back machine, my friend. It’s out there.

 

[simbin]

To get the original files from TX you‘re gonna have to use the way back machine, my friend. It’s out there.

Good idea. I forget what their website address was now though lol

I already have one payload.bin of theirs, but I think that was just to inject the license code or something. And of course I have the latest boot.dat file.

Update: found it
SX Loader 1.0 (payload.bin) is what I already had (from TegraRcmGUI)

Launching from latest Hekate, just goes back to Hekate