I'm getting around to making the move on my Switch Lite running SX OS, but I'm really nervous about screwing it up by missing something. However, SX OS is so picky with SD cards that I think I'm sick of its quirks enough to finally "risk" it. Never had any experience with Atmosphere, Switch softmods etc. I did some reading on this, but still felt unsure on some points.
So, this is more or less a pre-flight check for me that I'd also like to run through all you good people so that I - possibly - avoid doing or assuming asomething stupid.
SX OS 3.1.0, EmuNAND, hidden partition. Bought second hand as and at that - as far as I know not updated via ChoiDujourNX (no ChoiDujourNX found on SD card).
No SysNAND backup (yet, at least - for reason stated above).
Following this guide: https://rentry.co/mys8q
I have the files ready as per the guide, configs used for Mariko and EmuNAND, and I did rename hekate_ctcaer_x.x.x.bin to payload.bin (this is an odd disclaimer to put there - surely everyone following this particular guide HAS TO BE using "SX Core/Lite & SX Pro"... right?)
I looked at the flipside to get a wider picture: https://rentry.org/AtmosToSXOSEmuNAND
It looks to me that the SX OS -> Atmo migration is basically adapting directories / renaming the existing SX files so that Atmo can use them which is also the reason why - theoretically - I'd need to migrate back to SX OS in order to boot to SX OS - am I right on this, in broad terms?
And a paranoid bonus question, because I like to have a Plan D: if I clone my current SX OS SD card and migrate to Atmosphere on my second card will I be able to boot to both of them depending on which card I insert? Not interested in dual booting, just in a fallback plan.
Am I making sense? Is this really everything to it? I'm suspicious of everything this simple.
So, this is more or less a pre-flight check for me that I'd also like to run through all you good people so that I - possibly - avoid doing or assuming asomething stupid.
SX OS 3.1.0, EmuNAND, hidden partition. Bought second hand as and at that - as far as I know not updated via ChoiDujourNX (no ChoiDujourNX found on SD card).
No SysNAND backup (yet, at least - for reason stated above).
Following this guide: https://rentry.co/mys8q
I have the files ready as per the guide, configs used for Mariko and EmuNAND, and I did rename hekate_ctcaer_x.x.x.bin to payload.bin (this is an odd disclaimer to put there - surely everyone following this particular guide HAS TO BE using "SX Core/Lite & SX Pro"... right?)
I looked at the flipside to get a wider picture: https://rentry.org/AtmosToSXOSEmuNAND
It looks to me that the SX OS -> Atmo migration is basically adapting directories / renaming the existing SX files so that Atmo can use them which is also the reason why - theoretically - I'd need to migrate back to SX OS in order to boot to SX OS - am I right on this, in broad terms?
And a paranoid bonus question, because I like to have a Plan D: if I clone my current SX OS SD card and migrate to Atmosphere on my second card will I be able to boot to both of them depending on which card I insert? Not interested in dual booting, just in a fallback plan.
Am I making sense? Is this really everything to it? I'm suspicious of everything this simple.