If you don't restore a clean NAND backup prior to going online, regardless if you're currently in CFW or OFW, you risk getting banned since traces of CFW persist even after the console is shut off.Picked up a brand new hackable Switch last week running 4.1.0 on OFW and loaded up Hekate and Atmosphere after full NAND backup. So far I've done nothing aside from play with the Retroarch NRO and haven't gone once into OFW or loaded a single NSP or updated beyond 4.1.0. I hear you can use a modified eShop NSP to access Homebrew with full RAM access without a ban risk though so now I'm curious.
If I switch from CFW to OFW from the Hekate launcher and try to access the eShop via normal Wi-Fi (no 90DNS) is this a high risk scenario for a ban in itself? I presume it's only risky to access eShop from within a CFW.
Also, would it be better to update to latest system update officially or via Choi at this point? I know the former burns fuses but I'm more concerned about Choi triggering a ban accessing the eShop in OFC. That is unless updating officially kills Hekate/CFW access...
Thanks for any help here!
Also, there is no "better" way to update as both have their pros and cons. Updating without burning fuses lets you retain the ability to downgrade in case future exploits come out for lower firmwares such as a hypothetical untethered coldboot but you risk getting banned this way. You can update officially which will most likely not lead to you getting banned (if done safely) but by doing so, you will irreversibly burn fuses rendering yourself unable to downgrade meaning you may be stuck using a jig and USB cable to boot CFW for a very long time. Weigh which one is more important to you, downgrading or being banned.
Kosmos has its own updater tool that you can use to update the package whenever there is a new version. You can use this without getting banned if you setup 90DNS on your Wi-Fi settings (they are literally just DNS settings). The offline alternative is downloading the latest Kosmos and replacing any files/folders from the old Kosmos.Anyone know what s the easiest way of keeping your home brew apps and cfw up to date?
I'm using Kosmo atm and switch has been in airplane mode since I hacked it.
If you want to transfer, make a copy of your Nintendo folder and rename it to Emutendo. By the way, the Nintendo/Emutendo folder only contains data for installed content on the SD card; it does not have any save data or content installed to internal memory.Hi, looking for advice from the geniuses on here! I''ve been using sxos for quite a while and have finally created an emunand. I'm on 6.1 at the moment but plan to update to 6.2 with choidujournx.
After creating the emunand I now have an emutendo folder on my sd card - am I supposed to transfer everything from my nintendo folder into that folder? Or only some files? Or just leave it as is? Any help much appreciated!
Your SysNAND's firmware has not been patched for exFAT support. Either patch it by either updating to the latest firmware which will irreversibly burn fuses or with homebrew applications such as ChoiDujourNX. Or the simplest option is reformat the SD card to FAT32.Need help, ok so I have SX OS installed emuNAND 6.1.0 and on sysNAND I am on 4.0.1. I updated with ChoiDujourNX with exFAT support. In the SX OS boot menu emuNAND is currently enabled. When I disable it and try to boot CFW the nintendo logo comes up but quickly disappears and I am left with a black screen and have to force shutdown. Is this happening because I updated in emuNAND? Also when I boot up into sysNAND is there anyway to NOT get the “update system to use microSD card” notification? Thank you for the answers!
Retroarch had some Gamecube support however something happened which caused them to pick up support for the N64 over the Gamecube meaning the only option left is running Dolphin via Lakka which is not pretty. PS2 emulation will probably also be handled by Retroarch since there are no other PS2 emulators planned on being added to the Switch.I will ask again since my first post never got answered. Is there any plans for a game cube and ps2 emulator for the switch? or r there already ones out to download? P.s will they be added to the hb app store.
You can either use Hekate or SX OS to dump the NAND. I recommend using Hekate since, unlike SX OS, it can verify the backup. Hekate is a payload so you can either send it as the primary payload with a USB-C cable or chainload it from the SX OS menu.Hi guys,
Ive been reading as much as i can to prepare myself to install my SXPRO but still have a few questions.
So i know i need to create a back up of my clean NAND before installing the SXPRO cfw, probably a silly question but how is this done?
Also i still need some clarification on updating the system software once CFW is installed. Am i right in saying that once i have created emuNAND i can use ChoiDujourNX to update sysnand from 5.1.0 to 6.1?
is 6.1 the most desirable to to upgrad sysnand to?
Lastly, once i have updated my sysnand to 6.1 what version will emuNAN be on?
Thanks in advance, really appreciate the support this site offers!
While you can use ChoiDujourNX to update your SysNAND, if you want to play online without getting banned with SysNAND, it would be best to avoid using a homebrew application to update your SysNAND.
Right now, most people would say 6.2 is the "most desirable" firmware since it is the latest firmware and the exploit works on all firmware so most people are going to end up on the latest firmware one way or another.
When EmuNAND is first created, it is a 1:1 copy of your SysNAND so its firmware will be whatever your SysNAND was on when you created EmuNAND.