Homebrew RELEASE ChoiDujourNX - a system firmware installer homebrew for the Nintendo Switch

[rajkosto]

also, Cartridge Controller firmware concerns.... i would keep that switch on 3.0.2 or lower because of that.

 

[anickname]

Do you know if controller firmware upgrade is like cartridge firmware upgrade: once upgraded, not working anymore on lower OS firmware versions ?

 

[shchmue]

Do you know if controller firmware upgrade is like cartridge firmware upgrade: once upgraded, not working anymore on lower OS firmware versions ?

someone probably would've noticed by now if it did

 

[Xyphoseos]

Just to be sure, I place my update on my SD card, I launch the homebrew, install update and then I will be with autorcm and I just need to launch hekate without touch .ini, just launch hekate
I'm wrong ?

 

[ocomma]

Worked great going from 2.1.0 to 2.3.0 incl exfat. Thank you!

 

[Azel]

What does the name of this program mean?

It means "Choice of the Day"/"Choice of Today"

 

[risq]

Yes, and yes. If you stay on AutoRCM and never boot without it again, you will not burn fuses.
You have to boot your Switch with Hekate though everytime. If you boot original Horizon once, it'll burn your fuses.

thx for the quick answer. just to make sure: i can use ReiNX as well (instead of hekate)? as long as i use autorcm

 

[Pacote]

Awesome, wasnt expecting a tool like that to be release so soon!

 

[Azel]

thx for the quick answer. just to make sure: i can use ReiNX as well (instead of hekate)? as long as i use autorcm

There's no reason to use ReiNX. It is worse than SXOS (they actually wrote some code that can't be found anywhere else, and also aren't illegally distributing nintendo sysmodules inside their packages).
1. add all the kips inside the sysmodules folder to your hekate launch profile (there likely arent any other than the standard 2), congratulations, now you can use hekate instead of ReiNX.bin which is a crippled version of it
2. while you're at it, replace loader.kip and sm.kip with the original versions from atmosphere (working versions easily found in tomger sdfiles), then rename your ReiNX folder to atmosphere (literally the only change Rei has made to the atmosphere loader.kip), congratulations, you dont have to worry about keep using the ReiNX "modded" versions of these anymore (or keeping 2 separate folders with the same stuff because of the folder name change).

there are no advantages and only disadvantages of using the ReiNX "CFW" (more like repack), so I see no reason to support it's problems.

 

[LeMageFro]

im still on 2.0.1, and i have only been using ReiNX so far. can i update to with ChoiDujourNx to 4.0.1. or higher without any negative impacts? can i downgrade with this to 2.0.1 for a possible coldboot solution later?

To develop on what raj said, the only negative impact is that if you want to keep the possibility to use gamecards on your 2.0.1 after downgrading then you will have to disable them on any firmware higher than 4.0, and should be careful never to select a launch target without the kip1patch=nogc option. Or in reverse, if you chose to use gamecards on a firmware higher than 4.0 then you won't be able to use them on 2.0 after downgrading.
Personally I was on 2.0.0 and only owned two games on gamecard so I updated to 5.1.0 (why stop at 4.0.1?), it worked like a charm and I can finally enjoy recent games bought on the eShop. If you're worried about accidentally updating your card reader then just edit the hekate_ipl.ini file and either remove any launch target that doesn't have the kip1patch=nogc option, or add the option to every launch target. And also delete the regular hekate.bin from your computer and only keep the one provided by raj so there is no chance of messing up by using the wrong payload .

 

[alucard_xs]

Choix du jour = choice of the day
It's like the chef's special of the day.

--------------------- MERGED ---------------------------

So it does not work with SX pro ?

 

[charlieb]

Do you know if controller firmware upgrade is like cartridge firmware upgrade: once upgraded, not working anymore on lower OS firmware versions ?

Correct, there are 2 fusesets, one for the main console and the other for the card reader. Upgrade to 3.02 if you want as that is does not update card reader, anything after will unless you use nogc KIP.

 

[shchmue]

read again. they were asking about the controller firmware update.

 

[Rahkeesh]

edit: nvm, go to reinx thread if you want to figure out how to get this tool working with it

 

[rajkosto]

What "controller" ? JoyCon ? Those are totally reversible and dont seem to affect much anyway.
Any time i say controller i mean the GC controller, not JoyCon, that would be silly.

 

[Draxzelex]

Just to be sure, I place my update on my SD card, I launch the homebrew, install update and then I will be with autorcm and I just need to launch hekate without touch .ini, just launch hekate
I'm wrong ?

No, you're correct.

So it does not work with SX pro ?

SX OS cannot be customized like Hekate so it still won't save your cartridge slot. However, you can chainload Hekate as an alternative.

 

[Adrian5]

What do you mean by chainload hekate? Can I edit my hekate_ipl.ini and create a profile that launches sx os bin and applies the nogc kip?

 

[Draxzelex]

What do you mean by chainload hekate? Can I edit my hekate_ipl.ini and create a profile that launches sx os bin and applies the nogc kip?

SX Pro can send payloads from the SD card so you use the dongle to send Hekate which will load the ini. SX OS cannot be modified to launch with the ini because TX doesn't allow it. They use predetermined patches in their CFW.

 

[Adrian5]

Yea, thats what I figured. I've been using the dongle to launch external payloads.

 

[Xyphoseos]

No, you're correct.
SX OS cannot be customized like Hekate so it still won't save your cartridge slot. However, you can chainload Hekate as an alternative.

Sure ? I've nothing to do ? My fuse won't burn and my cartbridge slot won't be updated ?