This reads like Rudy Giuliani talking about the cyber.
The first time you booted into any firmware >= 4.0.0, without any NOGC patches, your gamecard slot was updated.
The method described in the first posting to get nogc patches up and working is defunct - at least as far as running atmosphere is concerned.
Atmosphere 0.8.1 should have automatically applied nogc patches to safe your ass - seems like you didn't use the most current version.
Other than that you could have doubled down and used these nogc patches as well: https://gbatemp.net/threads/i-heard-that-you-guys-need-some-sweet-patches-for-atmosphere.521164/
Both of those methods work (even in combination) - and you should have gotten a "your gc slot doesnt respond, please reboot or contact nintendo" message on boot. If you didn't your gamecard slot firmware is updated. No way to downgrade.
What you "should do now" is up to you - "what is best firmware to have" is a silly game to play - that gets old after the first time (you are not the first one trying to play it though - so have solace in that).
You are getting the update nags, because you went online with your system. Having a ban deathwish or something. Asking for the yes please give me update nags, all the time Nintendo treatment. The intelligent persons approach would have been to use 90DNS (https://gbatemp.net/threads/90dns-dns-server-for-blocking-all-nintendo-servers.516234/) even before installing a CFW - so Nintendo gets blacked out in everything you do online. (No online play either. No "easy" game updates. Thats the tradeoff, with Atmosphere - at least currently. (No emunand))
edit: Didn't step far enough into Rudy Guliani thought process mode.
5 Fuses burned means firmware 4.0.0-4.1.0 to begin with. So this guy didnt ever need to prevent the Gamecard slot update, because he always had it.
See: https://switchbrew.org/wiki/Fuses
But hey - I also often start talking about stuff I have no Idea about what it means... Not.
Atmosphere 0.8.1 didnt apply the NOGC patch in his case - because he already had the update on the system (4.0.0+). Most likely.
I updated several times to firmware 6.2.0 from 6.1.0 sxos cfw and back down again to test Smash out I saw this updated gamecard controller firmware thing pop up in Choidujour but everything works as it should and it says firmware 6.2.0 atmosphere 0.8.1. in settings. I mean what is the PreventGCUpdate when it is at home does anyone really know and does it really matter when your flashing to the newest firmware? I think you might find your doing something else wrong it has nothing to do with this preventgcupdate.Hi all!
So I updated to 6.2.0 via choidujournx in order to use the Nintendo User and Save Transfer Tool.
Now, after I installed it, I was able to boot successfully into CFW via hekate but I didn't realise that for some reason, my hekate didn't give me the 'PreventGCUpdate' option that you're supposed to use after updating via choidujournx.
Now I am getting update nags whenever I try to open the save transfer tool, and when checking my firmware it says system update ready. My burned fuses are still on 5 and I can still open atmosphere no problem.
So should my course of action now be to downgrade via choidujournx, and then upgrade back to 6.2.0 via choidujournx again, and make sure to use the PreventGCUpdate option? Tbh I still don't know why the option wasn't there the first time, but maybe there's a newer hekate package or something?
Did you pick with or without exFAT?Hello one and all.
I've encountered a problem and would be much obliged to any help or suggestions the community could provide. I used ChoiDujourNX today to update from frimware version 5.1 to 6.1 on SX OX v2.3. The files were placed in the appropriate locations, the homebrew application verified the 6.1 files and installed them without incident. Once finished, when prompted to reboot I selected the in-app option to shutdown. Once powered down I tethered my system to my PC and attempted to inject the appropriate payload. The splash screen displayed, but then went blank and nothing else worked. Subsequent attempts at payload injection encountered the same problem.
Unable to boot into CFW I instead opted to boot up OFW. That was successful but I was then immediately prompted for an update to the microSD card slot and Joycons. The system reads 6.1 but it would appear something went wrong or I failed on my end somehow. I cannot get SX OX to boot properly. AutoRCM works, the payload injection works, I can access the CFW options menu, but attempting to boot into CFW results in a blank screen.
I'm not certain if the system can no longer read the SD card. Though if that were true SX OX shouldn't boot at all, correct? I haven't had my system connected to the internet in any way since I originally hacked it months ago. I presume if I were to attempt to do so now to update I wouldn't be able to simply update my SD card slot and Joycons but would be forced to update to 6.2. And also likely banned soon after. I'd like to avoid that if possible but if that's not an option to get CFW up and running again then so be it. I do have a OFW 5.1 NAND backup from before hacking the system. I've never set up emuNAND though.
Again, any help would be greatly appreciated.
Thanks in advance.
nt tThanks to ChoiDujourNX, I updated to 6.0.0 without burning fuses.
But I don't remember exacly where I got the update files from @.@ I wao update to 6.0.1
Does the website in page1 give a link to download the update files? Unless I'm a dummy, I didn't see them.
Yes, you do. Otherwise the system wont recognize your exFAT formatted card and you won't be able to boot into CFW.This is probably one hell of a stupid question but if i all ready have the exfat driver installed on my switch and i update with choidujournx do i need to choose the exfat option when updating?
This is where you can play consumers help consumers, because they feel that group identity of consuming a thing - all day long. In a few weeks time.Welcome To The Team-Xecuter 2018 Community!
Where all of our loyal users gather to discuss our products and get support and help each other out!
https://team-xecuter.com/community/
So that's a no then, which would have sufficed. I only got SXOS because it has emunand and there's no current freeware emunand solution, and I was buying an SX gear anyway because I'm sick of using my computer to boot.Rant rant rant rant rant.....
I've been using ReiNX until now. I'm literally only using EmuNand because some fuckheads out there are creating malware to fuck up switches, I couldn't give a shite about your morality (which is what your post was about, trying to be the "moral" person). Once ReiNX or some other CFW gets EmuNand, I'll be jumping to that.It wouldnt have sufficed. But it would have been more convenient for you.
Remember - I'm not in here to work as your support agent. I actually care about what makes this community. You care about product support, and "most features piracy".
As always - I'm writing this in the hope that others in a similar situation might see this, and take different actions than you did. And in the hope, that some folks start thinking structurally - and actually stop using their smartphones as "quick question please answer" windows into a world they dont care to understand.
Nook question is there anyway to not have firmware of the game cart updated and still be able to play cart games while on a higher firmware.
my switch is on 3.0.1
Want to be able to update switch to play smash cart
steps i got so far
1:update cfw with kosmos
2: use chou with nogc enabled
3 update to 6.2
now here is where i get confused. So now the game cart slot is disable and i cant play games using it but if i disable to nogc and try to play my gc firmware will update. Is there anyway to play cart games and/orrip v2 carts without updating the gc firmware