I see, I'll remember that for future advice.ChoiDujour does not currently support firmware 6.2.
I see, I'll remember that for future advice.ChoiDujour does not currently support firmware 6.2.
What do you mean it doesn't support 6.2?ChoiDujour does not currently support firmware 6.2.
He's not wrong though.Come on now, that's not very nice to say to them.
Not a big deal when you can just install nsps.I don't understand why that has to be separated. One of the reasons I wanted to homebrew mine was to mod Ultimate, so I was pretty upset I couldn't load any game cards.
It should, so your guess is as good as mine. Maybe since he's been using different CFWs, when he was testing the cartridge slot on 5.1 he had the nogc patch enabled, but he ran 5.1 without it enabled at some point before or after that so the GC firmware got updated. Anyway all he should have to do is make sure nogc isn't enabled when he's trying to use carts on 5.1 and it should work.Why wouldn't the cart slot work once he went to 5.1 though?
ChoiDujour != ChoiDujourNX. These are 2 completely different applications. One is a Windows program and the other is a Switch homebrew application.What do you mean it doesn't support 6.2?
I worked flawlessly on mine
because he went from 2.1.0. to 5.2.Why wouldn't the cart slot work once he went to 5.1 though?
the GC slot gets upgraded after 4.#I don't understand why that has to be separated. One of the reasons I wanted to homebrew mine was to mod Ultimate, so I was pretty upset I couldn't load any game cards.
Not a big deal when you can just install nsps.
The GC slot gets upgraded after 4.#
to allow people to downgrade and still use the GC when they go back down before 4 a lot of OS's disable the GC because if you update the GC and then go back to before 4.# the offical OS will not be able to comunicate to it as it wont know the new commands its sending because of the update.
so as I said. if you want to upgrade and use the card slot you will have to disable the auto GC slot disabler to make it update it and it will work on 4.x+
but then if you go back to 2.1.0 your GC wont work at all
I agree with this, especially because you can just put the switch in sleep mode and keep it in the cfw. If it dies you can just use a phone to boot it or a cfw loader that you can get for like 10 bucks from aliexpress or amazonSo many poor bastards being dumb and holding out for a supposed "coldboot exploit for lower firmwares" that will never be released. Hilarious to me. Just suck it up, update to the latest, and continue enjoying everything again.
I agree with this, especially because you can just put the switch in sleep mode and keep it in the cfw. If it dies you can just use a phone to boot it or a cfw loader that you can get for like 10 bucks from aliexpress or amazon
there are switch cfw loaders that have a special jig slot where you can keep it so you only need to carry around a small usb stick just in case it dies or you need to rebootYeah people seem to not realize that sleep mode is legit, and your Switch is either being used or docked in a charger somewhere just like any modern-day smartphone. How often do we reboot our phones? If you're like most people, hardly ever.
I was over at the PS1 Classic hack scene on Reddit a few days ago and everyone is super giddy like it's this amazing thing. I mentioned that you can do all of this plus SO much more on a hacked Switch, and it turns out they're pretty much all petrified of jigs, and such comments I've made get down-voted to oblivion lol. I actually had a bit of pity for them. One guy made a post brainstorming an idea to attach a mini monitor to the PS1 Classic so you can play on the go. /facepalm.. Get a Switch!
I dont get the issue here.
Why not updating to 6.2 with auto rcm (choidojournx) and a cfw like sxos where fuse count and burning are bypassed.
You'll have a console with fuse count=2 and a working gc slot+latest firmware where all games are working. When gc downgrade becomes available you can safely downgrade to 2.1 again. Maybe its just me but I dont see any benefits of doing so...
Have fun with your switch
Don't know what SX OS is or how to use it, but at the moment, I'm still trying to figure out the issue with my crashing Switch, since I was at 2.1.0 initially, choided to 5.1.0 and then downgraded, with choid, back to 2.1.0 (wasn't sure if it would mess it up, so I didn't check exFAT as an option before installing) and it crashes with an error if I try to change my pfp, insert a game card or use the Homebrew Menu. At the moment, I am receiving help from Kafluke, but have not received a response in a while. So until then, I can't do any other methods to even try to get the GC Slot working again until I can figure out how to load my NAND of 2.1.0 from before I did any kind of homebrew on it.
If you upgraded to 5.1 and didn't disable the game card slot, then you can't use it on 2.1
Just update to 5.1 again or even 6.2, which all main line cfw support
"or use the Homebrew Menu"
Already mentioned it doesn't open, unless there's another way.
i know they shouldnt have to but think people need to put in big red letters that you can not update switch firmware and then downgrade.
firmware updates burn fused, firmwares require set number of fuses to run, if fuses dont match, firmware wont boot, thus console be bricked.
why do people insist on fucking about with their systems without knowing their shit first.
there is no valid reason to remain on a redundant firmware anymore
I asked so many questions too before I started any of this, even about ChoiDujourNX. I'm very disappointed nobody told me it would mess up the GC Slot. Well, I guess that ends my homebrew days with my Switch already and I was only a couple of weeks in too. Might as well throw it away since nobody will want to buy this. Don't even know what the point was in backing up the NAND in the first place if it was this easy to ruin it.
Well, I mean if it's broken already anyway, I might as well try to update the Switch through Nintendo's servers, since I have nothing else I can do to fix it.
If I don't receive any other solutions to address this in about the next hour, I will most likely try to just risk my FUSES and update through Nintendo servers anyway, since there's no point if I can't even load the Homebrew Menu at all anymore.
I don't understand why that has to be separated. One of the reasons I wanted to homebrew mine was to mod Ultimate, so I was pretty upset I couldn't load any game cards.
You're complaining too much. Your console is far from bricked or even "half" bricked. Once your cartridge slot gets updated (which by now it most certainly has) there's no current way to downgrade it.
But there's no reason you can't just update to 6.2.0 now (hurry before 7 comes out!) and use Atmosphere like a bunch of other people are here. And if you still want to preserve your fuse count (in hopes that a way of downgrading the gamecard slot is released in the future), you can do that too. Or you can use an NSP for Ultimate and still load all your mods.
Heck, if you're just going to throw it away anyway, the least you can do is sell it to me for $50 instead. Even if you upgrade to 6.2.0 and blow your fuses, you're in no worse situation than anybody else running homebrew on 6.2 right now (which I am). And if you do end up upgrading to 7, you'll be in no worse situation than anybody that is just using their Switch normally, without hacks or CFW.
Just be thankful you're not bricked, and either upgrade your Switch, or use NSPs.
If I have the NAND, as I've said many times already, I'd prefer to restore 2.1.0 and then upgrade to 5.1.0 to load Ultimate. And as I also said, I can not load the Homebrew Menu right now. So, to clarify then, is updating my Switch manually through their servers the only way I will be able to use it for Homebrew again? Is there no way for me to load my NAND without the Homebrew Menu?
Also, I said most of what I said out of stress at the time. I obviously didn't plan on throwing it away, but it just seemed like all hope was lost based on my first response initially telling me it was ruined. And I'm still patiently awaiting for a solution since they now told me I could still restore my NAND.