Thank you for your answer, would you mind linking me to a guide on how to setup and use daybreak and atmosphere? Are they compatible with SXOS?On a dirty NAND, you should update using Daybreak on Atmosphere (recommended), or you can update using ChoiDujourNX. On a clean NAND, you should update using the system settings. If you have AutoRCM installed on a clean NAND and you don't want to burn fuses, you'll want to update through the system settings while running Atmosphere to preserve AutoRCM.
If you want to use Daybreak, do the following:Thank you for your answer, would you mind linking me to a guide on how to setup and use daybreak and atmosphere? Are there compatible with SXOS?
Did you move any contents from the Nintendo folder to emummc/Nintendo_XXXX?Potentially a dumb question, but I'm not seeing any obvious answers about it anywhere--
I've currently got an emuMMC set up on a partition on the same SD card that I use for stock. It's a ~500GB SD card and I've got a bunch of games I've downloaded legitimately, but when I boot into emuMMC it doesn't seem to recognize that those games are already downloaded-- it only sees the games that were stored in the console base memory at the time the emuMMC was cloned. Is there any way to tell the emuMMC that "hey these downloaded games are all already right over here"?
Did you move any contents from the Nintendo folder to emummc/Nintendo_XXXX?
You either have to pick a location (sysMMC or emuMMC) or have them in both places. This is for good reason.Negative, but that was likely the trick I was missing. Is there any way to get the emummc to look at the existing /Nintendo directory at the root of the SD card, or do all the game files have to be copied into both locations for both stock and emuMMC to see them?
Things get messy when data is shared between a sysMMC and an emuMMC, but their tickets do not comport with each other (tickets are stored on the MMC).I'm curious as to what the reason is, since my first instinct would be "Move them back and forth depending on what I'm booting into"-- I'm not planning on installing NSPs, and being able to keep the emuMMC's games updated/added to legitimately without risking taking the emuMMC online would be A Good Thing in my book. Are the game files modified in some way on the emuMMC side that makes bringing them back across to the stock location risky?
I'd keep anything I want to mod on the emuMMC, and I'd keep everything else on the sysMMC. You can update games automatically using something like HBG on the emuMMC.Retroarch and modding, mostly. I'd much rather be mostly in the emuMMC and only hop back to stock to run updates/online games, vs "emuMMC for retroarch/modded games and stock for literally everything else", since in the former situation I'm by defintion near a computer than can send a payload.
Atmosphere is the CFW.Hi, can i update Atmosphere without to update Cfw?
(ex.: Atmos 0.14.1 on cfw 10.0.4)
lol, 'without to update HOS' was meant, obviouslyAtmosphere is the CFW.
i#m confused now.. what is atmosphere? nvm.
i meant more, if i stay on "10.0.4" (Fw), can i just update Atmos to latest,an pload "10.0.4 (with atmos 0.14.1)" ?