ok, I can't get a clear answer in other posts, So I have an Update 8.1.0 on wait, I am on 8.0.1 which I updated to from 4.1.0 using ChoiDujourNX, So my question is how can I get rid of that Update without burning fuses? I have AutoRCM on. is there a way to do that?
Have you tried booting into maintenance mode then from there just turning the switch off? I think that's how people got rid of 6.2 nag when updated with ChoidujourNX
Is it safe to update using ChoiDujourNX v1.02 from 8.0.1 to 8.1.0? Or to wait for the updated version of ChoiDujourNX? Some of the guys from discord nbg report black screen?
ChoiDujourNX doesn't need to be updated. I wouldn't trust anything the HBG Discord says. The black screen can be due to a multitude of things.
That's probably because they had some KIPs enabled (emuiibo, for instance) and as far as I've heard they can cause those kind of issues after updating to 8.1.0
Hi all.
I have SX OS and am trying to use ChoiDujourNX (latest version) to update from 4.0 to 5.0.1.
I am able to run homebrew such as Tinfoil without issue.
When I attempt to run Choi Dujour, my switch crashes (see: )
Any ideas how to manage this issue?
I have SX OS and am trying to use ChoiDujourNX (latest version) to update from 4.0 to 5.0.1.
I am able to run homebrew such as Tinfoil without issue.
When I attempt to run Choi Dujour, my switch crashes (see: )
Any ideas how to manage this issue?
make sure you download the firmware on your PC, then format your SD Card to fat32 (if it isn't already), copy the firmware folder to the root of the SD card and you should be ok. I'm also using SX OS have have updated my emuNAND from 3.0.2 to 6.something, then later from 6.whatever to 7.0.1 with no issues.
the only difference I can see is I used choidujourNX v1.01 (it was before 1.02 was released).
If I remember correctly ChoiDuJourNX isn't compatible with SXOS due to the OS not giving some authorisations to homebrews or something like that, so the simplest thing is probably to temporarily use atmosphere to install the update. May I ask why you want to update to 5.0.1 and not directly to the latest firmware supported by SX ? (8.1 is supported now I think). There is no downside to updating to the latest firmware if you do it via Choi and activate autoRCM since you won't burn fuses and thus you will be able to downgrade in the future if needed.
hmm that might be incorrect information.. see my post above where I used choidujourNX v1.01 to update my emuNAND firmware under SX OS v2.71 beta successfully. ChoiduhourNX definitely runs under SX OS with no issues (at least version 1.01 did).
Haha well I clearly remembered incorrectly then ! Sorry for the wrong answer.
Yes, but you can only do this on an unpatched system's sysNAND, and it's not recommended. You would have to use a bootloader like fusee-primary or Hekate each and every time you want to coldboot the system, and that makes downgrading pointless.
Why do you want to downgrade? Atmosphere is compatible with 8.1.0 on unpatched systems.
Last edited by Lacius,
Reason being is I’m On SXOS Pro and since updating to 8.1 some games including BOTW (which I tried playing last night) are saying that they are corrupted. I’m guessing it’s a bug on the SXOS latest firmware.
u can but you need to go though hekate to boot it to bypass the fuse check
--------------------- MERGED ---------------------------
is your sd card formatted Exfat it maybe corrupted ?
Can anyone on 8.1 sxos pro try the game for me in xci format please? I’ve just formatted my card added it back on and still the same issue.
That sounds like an SX OS bug. Everything works fine with Atmosphere on 8.1.0.
Similar threads
- No one is chatting at the moment.
-
-
-
-
@
Psionic Roshambo:
Ken I have that sort of set up on Drastic on Pi for games that don't require touch -
-
-
@ HiradeGirl:
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1 -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
