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

[mitcha]

Not sure why you would need to downgrade first instead of just updating straight

a bad knowledge , a logical way is to update staight , but i read some threads here and ppl are reporting errors and problems for updating to 6.x.
so i will update to 6.2 ,and update hekate and sdfiles also.

 

[Draxzelex]

a bad knowledge , a logical way is to update staight , but i read some threads here and ppl are reporting errors and problems for updating to 6.x.
so i will update to 6.2 ,and update hekate and sdfiles also.

I think that was when 6.2 wasn't supported by CFW so unfortunately, they were destined to have a bad time. Another potential issue is if you have exFAT on your current firmware and then update officially, you will lose exFAT support and have to redownload the exFAT update.

 

[mitcha]

I think that was when 6.2 wasn't supported by CFW so unfortunately, they were destined to have a bad time. Another potential issue is if you have exFAT on your current firmware and then update officially, you will lose exFAT support and have to redownload the exFAT update.

i have the exfat support right now on 5.1.0 , thank you for the advice.
i don't want to update soon officially , because im having faith for the "no JIG to enter CFM" for the < 4.x.x firmwares

 

[xecutionx]

How can I run ChoiDujourNX on Firmware 2.0? I tried using Atmosphere, but opening the album to open the home brew launcher freezes the Switch.

 

[Finalxfantasy]

How can I run ChoiDujourNX on Firmware 2.0? I tried using Atmosphere, but opening the album to open the home brew launcher freezes the Switch.

• Q: After selecting ChoiDujourNX from the homebrew menu, it tries to start but closes immediately (or gives me a FATAL error, or just hangs at a black screen) !
• A: The debug svcs are not accessible to homebrew on your system. Either update your hbloader (from the release here: https://github.com/rajkosto/nx-hbloader/releases) or add fullsvcperm=1 to your hekate launch profile. Additionally, if you are trying to run ChoiDujourNX on 1.0.0, you must also add debugmode=1 to your hekate launch profile (this is not required on 2.0.0 or newer, which allows read-only debugging without it).

 

[xecutionx]

I can’t even get the Homebrew menu to open... I think I’m on too low of a firmware (I’m on 2.0).

 

[mspy]

I've seen some reports recently about bricking when upgrading with ChoiDujourNX, especially when we go from firmware 5.x to 6.2.

I do not run autoRCM but just to be safe I will run it when upgrading the firmware in case something goes wrong and I need to downgrade or restore the NAND using the 5.1 backup that I have in store and then deactivate it when I see that everything is OK.

So first I want you to know that I use SX OS, my question is, should I enable autoRCM on SX OS or should I just tick AutoRCM feature on ChoiDujourNX? I'm assuming that having both autoRCM enable will be bad. If I use AutoRCM feature on ChoiDujourNX how do I disable it afterwards when I check that everything went OK?

Another method that I'm thinking to upgrade the firmware, this time without autoRCM enable, is to just press shutdown instead of reboot in ChoiDujourNX when it finish the installation, then I start the console with the jigg and boot into RCM manually and inject SX OS loader, if everything goes well I should be able to use SX OS without any issues, am I correct stating this or not... (I assume that after shutdown if we boot into RCM manually and run SX OS it does not burn any fuses) ?

ps. I do not care about burning fuses, I only care to downgrade if the installation goes wrong so I only need the fuses not to be burn in this small interval that I have between upgrading the firmware and checking that everything is OK, I do not plan to downgrade later for whatever reason, so in order to burn the fuses I just need to boot the console normally without the jigg, correct ?

 

[shchmue]

I've seen some reports recently about bricking when upgrading with ChoiDujourNX, especially when we go from firmware 5.x to 6.2.

I do not run autoRCM but just to be safe I will run it when upgrading the firmware in case something goes wrong and I need to downgrade or restore the NAND using the 5.1 backup that I have in store and then deactivate it when I see that everything is OK.

So first I want you to know that I use SX OS, my question is, should I enable autoRCM on SX OS or should I just tick AutoRCM feature on ChoiDujourNX? I'm assuming that having both autoRCM enable will be bad. If I use AutoRCM feature on ChoiDujourNX how do I disable it afterwards when I check that everything went OK?

Another method that I'm thinking to upgrade the firmware, this time without autoRCM enable, is to just press shutdown instead of reboot in ChoiDujourNX when it finish the installation, then I start the console with the jigg and boot into RCM manually and inject SX OS loader, if everything goes well I should be able to use SX OS without any issues, am I correct stating this or not... (I assume that after shutdown if we boot into RCM manually and run SX OS it does not burn any fuses) ?

ps. I do not care about burning fuses, I only care to downgrade if the installation goes wrong so I only need the fuses not to be burn in this small interval that I have between upgrading the firmware and checking that everything is OK, I do not plan to downgrade later for whatever reason, so in order to burn the fuses I just need to boot the console normally without the jigg, correct ?

there's no reason you should brick upgrading with this. it enables AutoRCM by default (togglable in the options) and overrides any previous AutoRCM setting since by design it's writing fresh info to the area AutoRCM affects. disable it afterwards by using Hekate. the rest is correct, if you boot RCM you halt the console before the fuse check and by launching an alt bootloader you skip the check.

 

[mspy]

there's no reason you should brick upgrading with this. it enables AutoRCM by default (togglable in the options) and overrides any previous AutoRCM setting since by design it's writing fresh info to the area AutoRCM affects. disable it afterwards by using Hekate. the rest is correct, if you boot RCM you halt the console before the fuse check and by launching an alt bootloader you skip the check.

OK then I may just not enable autoRCM at all and shutdown the console and boot into RCM manually with the jigg.

 

[lpoolm]

i get the following error "unknown package version (=20181107105733) failed to launch firmware" at the end after i have installed the firmware and rebooted?

 

[shchmue]

i get the following error "unknown package version (=20181107105733) failed to launch firmware" at the end after i have installed the firmware and rebooted?

update your CFW files on SD. you're using a version that predates 6.2.0 support

 

[Depechem70]

Hello i am to stupid. I have updated from 6.0 to 6.2 with no extfat. Now i cant load cfw because its an extfat sd Card. What can i do? Thanks for Help.

 

[Draxzelex]

Hello i am to stupid. I have updated from 6.0 to 6.2 with no extfat. Now i cant load cfw because its an extfat sd Card. What can i do? Thanks for Help.

Reformat the SD card to FAT32. If its bigger than 32 GB, you'll have to use a third-party app such as GUIFormat.

 

[Depechem70]

Thanks i test it tomorrow

 

[ChokingVictim87]

Wonder if anyone can help me here as I am going outta my mind!

Ive followed this guide https://team-xecuter.com/forums/thr...anned-Nintendo-Switch-with-ChoiDujourNX/page5

So far so good. However,when it comes to creating a folder called "Firmware" and placing it on the root of my SD card,this is where I am having problems. Ive downloaded the latest Firmware 6.2.0,extracted it from the zip and placed the contents of this in the folder marked "Firmware" on the root of the card. Upon booting Choidujour up, this folder is not showing up (it looks like any other file and I cannot "choose" it)

Any ideas?

 

[Mugiwara.]

Updated to 6.2 so i can run more games, now i am getting a prompt to update controllers, how to remove that?

 

[Trice]

Updated to 6.2 so i can run more games, now i am getting a prompt to update controllers, how to remove that?

Don't think you can remove it, but there's no harm in updating the controllers anyway.

 

[Sparky076]

• Q: I just want to install exFAT on the current firmware version I already have. Can I do this using ChoiDujourNX ?
• A: Absolutely, just place a folder containing the exFAT version of the firmware you are currently running and choose it inside ChoiDujourNX. It will only install the required couple of packages needed for exFAT, and you can even disable the AutoRCM option (if you are sure the firmware you are installing is the same burned fuse count as the one you are currently running).

How can I get the version for 4.1.0? How do I make sure its exFAT(Just make sure the SD Card is formatted as exFAT?)? Where should I put this folder(In the root? Under "switch"?)?

Edit: NVM. Found it.

 

[ChokingVictim87]

Got it all sorted now

 

[Mugiwara.]

Don't think you can remove it, but there's no harm in updating the controllers anyway.

Would if i could, switch is banned