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

[marcx987]

No

so does anyone know when the cart firmware updates? so that maybe can block that specific event or anyway to put it apart of the bootloader like how autorcm prevents fuses from being burnt.
i know when the firmware updates its supposed to update gc firmware as well but is this an everyboot process? does it auto update if cart with newer firmware is inserted?

 

[Draxzelex]

so does anyone know when the cart firmware updates? so that maybe can block that specific event or anyway to put it apart of the bootloader like how autorcm prevents fuses from being burnt.
i know when the firmware updates its supposed to update gc firmware as well but is this an everyboot process? does it auto update if cart with newer firmware is inserted?

Its applied the second the console turns on.

 

[marcx987]

Its applied the second the console turns on.

and let me guess the nogc patch cant be turned off from cfw without restarting console

 

[Draxzelex]

and let me guess the nogc patch cant be turned off from cfw without restarting console

Yup. The nogc patch is applied at runtime so it can't be disabled without turning the Switch off or rebooting it.

 

[marcx987]

Yup. The nogc patch is applied at runtime so it can't be disabled without turning the Switch off or rebooting it.

heres hoping would be able to play smash sometime today. and not have to get a new microsd. and not make my 3.0.1 nand obselete

 

[S3phi40T]

Switch with 3.0.1
Want to update to 6.1.0 with exfat and don't care about fuses.

I just want to confirm:
- put 6.1.0 at sdcard
- run SX OS and ChoidjourNX
- Chose ExFat version
- disable autoRCM

...or should I install fat version first and then reinstall exfat after reboot?

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

 

[Draxzelex]

Switch with 3.0.1
Want to update to 6.1.0 with exfat and don't care about fuses.

I just want to confirm:
- put 6.1.0 at sdcard
- run SX OS and ChoidjourNX
- Chose ExFat version
- disable autoRCM

...or should I install fat version first and then reinstall exfat after reboot?

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

Nah, just install the exFAT version first and toggle AutoRCM off the installation process.

 

[S3phi40T]

Nah, just install the exFAT version first and toggle AutoRCM off the installation process.

Done, thx!

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka

 

[vree]

If i'm on 6.1 and want to go to 6.2. Never used choudujour before. Will I have issues with the gamecard? Or will it still be usable afterwards?

 

[Draxzelex]

If i'm on 6.1 and want to go to 6.2. Never used choudujour before. Will I have issues with the gamecard? Or will it still be usable afterwards?

If you haven't updated your gamecart slot before, you will still need the nogc patch to prevent it from being updated. But if you have booted a firmware of 4.0 or higher without it, it is most likely already updated. And there has so far been only one update to that slot which is found in firmware 4.0. By the way, this is a thread about ChoiDujourNX. ChoiDujour can be found here. There is a difference because one takes less than 5 minutes and the other takes at least half an hour.

 

[loon111]

Hi, never used this before an i use sxos, now its been updated, i want to update to 6.2 with this, any idea where i get this 6.2?

Regards

 

[anthonyplep]

Updated to 6.2.0 from 5.X.X, but didn't choose the exFAT version. Switch is now buggy, has trouble turning on and nags me to update the console to use exFAT even though I already installed it ages ago. Unable to update it anyways because banned. What can I do? Using an 120gb card. I have access to smaller SD cards

 

[Draxzelex]

Updated to 6.2.0 from 5.X.X, but didn't choose the exFAT version. Switch is now buggy, has trouble turning on and nags me to update the console to use exFAT even though I already installed it ages ago. Unable to update it anyways because banned. What can I do?

If you didn't choose exFAT when updating, you lost exFAT support when you updated your firmware. exFAT support is not universally applied to the console; it has to be manually applied to the firmware before installation hence why the exFAT prompt is there. Reinstall the firmware but choose exFAT again. You will have to keep pressing exFAT in the future for other firmware updates if you plan to continue using exFAT.

 

[smf]

and nags me to update the console to use exFAT even though I already installed it ages ago.

You uninstalled it when you told choidujournx to install the version without exfat as choidujournx first removes all the old OS files and then copies the new ones.

What can I do? Using an 120gb card. I have access to smaller SD cards

Put your CFW, choidujournx and 6.2 on a FAT32 formatted card, install the exfat version & then go back to your 120gb card.

 

[anthonyplep]

If you didn't choose exFAT when updating, you lost exFAT support when you updated your firmware. exFAT support is not universally applied to the console; it has to be manually applied to the firmware before installation hence why the exFAT prompt is there. Reinstall the firmware but choose exFAT again. You will have to keep pressing exFAT in the future for other firmware updates if you plan to continue using exFAT.

You uninstalled it when you told choidujournx to install the version without exfat as choidujournx first removes all the old OS files and then copies the new ones.



Put your CFW, choidujournx and 6.2 on a FAT32 formatted card, install the exfat version & then go back to your 120gb card.

Should have guessed it was that easy. Problem solved!

 

[xs4all]

Not sure how I feel about reading all 67 pages to find an answer, but if anyone knows.

I know for OFW/CFW, if you use this to update your FW, AutoRCM must be turned on to prevent a fuse being burnt, every time you boot up.

Now, what if you use this to update EmuNAND FW, does the flag to burn a fuse be carried over to OFW/CFW as well? Or it's just within EmuNAND only?

I thought I found my answer a while ago, OFW and EmuNAND was on 6.0.1, I updated EmuNAND to 6.1 and disabled AutoRCM. Booted into OFW, then booted into SX OS and launched the Hekate Ctcaer payload to check my fuses, the fuse count was still 7. Then I thought sweet, didn't burn a fuse
After some digging around, it came to my attention that if your upgrading firmware within v6.0 and v6.1 you wont burn a fuse, only a jump from the next version v6.2.x will burn a fuse!

 

[Draxzelex]

Not sure how I feel about reading all 67 pages to find an answer, but if anyone knows.

I know for OFW/CFW, if you use this to update your FW, AutoRCM must be turned on to prevent a fuse being burnt, every time you boot up.

Now, what if you use this to update EmuNAND FW, does the flag to burn a fuse be carried over to OFW/CFW as well? Or it's just within EmuNAND only?

EmuNAND will not burn any fuses because you cannot normally boot into EmuNAND. You can only boot into EmuNAND with SX Loader which bypasses the fuse check making burning fuses with EmuNAND impossible.

 

[xs4all]

EmuNAND will not burn any fuses because you cannot normally boot into EmuNAND. You can only boot into EmuNAND with SX Loader which bypasses the fuse check making burning fuses with EmuNAND impossible.

Ah yes it does make sense now, since your using the RCM JIG to boot into SXOS to load EmuNAND it's essentially the same as using AutoRCM on OFW.

Now I got that part understood, now what would happen if I just boot into OFW once EmuNAND FW has been updated without AUTORCM? Would the flag to burn fuse a once off or is it always on until a fuse has been burnt, forcing us to use AUTORCM in OFW to prevent burn fuse?

 

[Draxzelex]

Ah yes it does make sense now, since your using the RCM JIG to boot into SXOS to load EmuNAND it's essentially the same as using AutoRCM on OFW.

Now I got that part understood, now what would happen if I just boot into OFW once EmuNAND FW has been updated without AUTORCM? Would the flag to burn fuse a once off or is it always on until a fuse has been burnt, forcing us to use AUTORCM in OFW to prevent burn fuse?

EmuNAND has no bearing on OFW because it is completely separate from SysNAND. That all depends on what the current fuse count is and what firmware OFW/SysNAND is running.

 

[S3phi40T]

Ah yes it does make sense now, since your using the RCM JIG to boot into SXOS to load EmuNAND it's essentially the same as using AutoRCM on OFW.

Now I got that part understood, now what would happen if I just boot into OFW once EmuNAND FW has been updated without AUTORCM? Would the flag to burn fuse a once off or is it always on until a fuse has been burnt, forcing us to use AUTORCM in OFW to prevent burn fuse?

No, fuse is not burnt.
I have 5.x OFW and 6.2 EmuNAND.
No AutoRCM.
6 fuses burnt (normal for 5.X).

Wysłane z mojego Redmi Note 4 przy użyciu Tapatalka