Got SX up and running today. SX 2.7.1 on OS 8.0.1
I notice that when installing some .NSPs, when I try to install it in the fully fledged SX Installer App, I get an error popping up right away that the install failed.
However, when I try to install the same game on the Installer tab of the SX OS splash screen, it installs fine.
What am I doing wrong?
I am also wondering what the best way to exit out of retroarch is to prevent SD corruption ( I am formatted as FAT32). Retro stopped supporting .nsp so the only way I can find to exit retro is to use the 'quit retro' function from within the app. I found old posts saying don't exit like that, leads to corruption, but idk what else to do.
Maybe SX Installer is buggy
And normally I would think using the homebrew application's built-in exit function would be sufficient as I don't use Retroarch. I also know a lot of homebrew applications can be exited by pressing the + button.
Hello all,
I’ve got an SX pro.
When I got the dongle, I updated my OFW switch to 7.0.1.. and I have installed EMUNAND with firmware 7.0.1.
Now I’ve used the switch to play a game through the emunand, offline.
My son would like to play FORNITE and that is a free download but an online game
So I know that going online with an NSP or XCI is a super risk for a ban.. like 200% chance
But is going online with a free game through OFW safe? When I only used emunand for the other games.
If I would download the game…most likely it will ask for a firmware update and then it will install the latest game update as well.
It would make my NAND backup useless because there might be fuses getting burnt (now or in the future) when the game needs the latest firmware
I would like to see what your advice would be. What is the risk here about getting banned?
By OFW, I'm going to assume you meant SysNAND because booting OFW in EmuNAND isn't safe especially if you have already used CFW/homebrew within in. As long as SysNAND is clean and hasn't booted any CFW or homebrew, your son should be fine to play Fortnite there.
And since you mentioned burning fuses, I'm also going to assume your SysNAND firmware is not on the latest version which is 8.0.1 Burning fuses doesn't make older NAND backups useless, it just requires an additional step to use them after you restore it. All of the bootloaders (aka the payloads that boot into CFW) bypass the fuse check so technically you can boot any firmware as long as you use a bootloader that bypasses the fuse check. Now this isn't useful for downgrading for future exploits such as untethered coldboot because you would be using 2 exploits to load one (sending a payload is an exploit in of itself) but it is useful if you don't have a NAND backup that matches your current fuse count. If you do happen to burn fuses and want to restore your old NAND backup, simply enable AutoRCM after the restore which will force you to use a bootloader payload to turn on the Switch which will automatically bypass the fuse check.
Now there are ways of updating without burning fuses. The most notorious is the homebrew application ChoiDujourNX but using that in SysNAND may taint it. Another option is to insert a jig and manually boot into RCM once the system update is finished installing. This
guide covers that in greater detail. Lastly, you can do what I do which is to install system firmware updates downloaded online while running AutoRCM and CFW offline. What I mean is to have your console connect online and download the latest firmware update but do not install it. Then remove all Wi-Fi settings and reboot into a CFW that prevents AutoRCM from being removed during system updates such as the latest versions of Atmosphere or ReiNX (to my knowledge, SX OS does not preserve AutoRCM after system updates). Then install the update while running CFW which will not only update the system firmware but preserve AutoRCM and conversely the fuses. I haven't been banned for doing this yet even though it involves running CFW. Or you can just ignore all of this and update while burning fuses. It is your decision.