1. I see. But as soon as it loads a CFW (SX OS or Atmosphere, for example), it “exits” RCM mode, right? So if I’m running SX OS/Atmos, put the Switch in sleep mode and leave it charging, I should be fine?
2. Ah, okay. As long as AutoRCM is enabled, everything’s good, then.
3. No need to worry if the system isn’t connected to the internet, though?
4.
5. Interesting. So the SD card format doesn’t matter for NAND backups. And you don’t have to keep it in the card that you’re using for homebrew? I could back up the original 1.0.0 SysNAND to an SD card formatted in exFAT and have the system update to a firmware in FAT32 using a different card?
6. Got it. Kinda sucks that even the cartridge slot is protected by its own firmware, but that’s Nintendo for you.
- Yes, the only purpose of RCM is to send a payload. Once you send a payload, you either boot into CFW or OFW. Sleep Mode is fine with or without AutoRCM
- Yes
- Yes
- Filler
- Yes. You can also back it up to a hard drive or a cloud if you want
Because everyone has different definitions of the ideal setup. Obviously my advice is going to differ from someone else's. I really don't know why that user recommends both SysNAND and EmuNAND to be on the same firmware version especially since one of the purposes of EmuNAND is to avoid having to update SysNAND. I don't have that much experience with their EmuNAND since its not perfect so things like backing up the EmuNAND don't routinely come up as a question but it seems like the the tutorial deals with that if you follow it through.Will my sysnand be ok on 4.1 I don't want to brick or mess up.
How come u didn't tell me to back up emunand how do I do it? I don't understand that tut can u explain the back up method?
Why is it recommended tho? I don't want to brick or mess up my system? R u sure I'm safe on lower sysnand?
How do I make a copy of emunand? I don't understand that tut
But Hekate isn't a CFW, its a bootloader that is loaded in RCM which is triggered before the NAND. As for an untraceable CFW, that's impossible as whatever tricks hackers can do to mask CFW, Nintendo can fire back with a new system update that adds telemetry. Hence why being undetectable is usually never the goal of a CFW because it would result in a never-ending battle that doesn't really benefit the scene. The point of a CFW is to open up options to users for their consoles, not avoid getting banned. That's why majority of hackers buy 2 or more consoles.Wait but isnt getting a NAND backup also being in hekate which is basically CFW? (Traceable)
also will there be an untraceable cfw in the future?
It is a possibility but Nintendo has learned from their mistakes on the 3DS and has included checks to see if the header matches the base game. If they don't, you will get flagged for a ban.Question, I was wondering if in a sense does switch backups works a bit like early 3ds hacks. What I mean by that is. There was a time on the 3ds that if you were using a flash cart to play your game dumps in order to play online "safer" you had to inject your personal cart headder into the ROM file.
Is that still a possibility/necessity?
NopeAny way to get fortnite on banned switch?