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

Adran_Marit · Feb 22, 2019

sys64738 said:
Okay, i have disabled with Hekate.
Now if i power on with jig in and vol +, power buttons and injecting with Tegra RCM GUI, just black screen, but Tegra RCM GUI says payload successfully injected.

reboot pc, sounds like rcmgui bugged

sys64738 · Feb 22, 2019

Adran_Marit said:
reboot pc, sounds like rcmgui bugged

I have with REI Toolkit enabled, then disabled again and then is working fine.

hipmp5 · Feb 22, 2019

Can i use this to downgrade from 7.0.1 to 6.2 on atmosphere 0.8.4?

Draxzelex · Feb 22, 2019

hipmp5 said:
Can i use this to downgrade from 7.0.1 to 6.2 on atmosphere 0.8.4?

Yes, you can use it to downgrade to any firmware. However when downgrading across major firmwares, you may need to perform a system initialization. 7.0.1 to 6.2 may or may not require one but I believe most people haven't required one.

W9qI8k5QMf · Mar 5, 2019

why are people downgrading from 7.x firmwares?

Draxzelex · Mar 5, 2019

W9qI8k5QMf said:
why are people downgrading from 7.x firmwares?

7.X is a tad bit unstable with certain homebrew applications such as Goldleaf or Tinfoil by Adubbz.

Philliyxx · Mar 7, 2019

Trying to upgrade to 6.2 again but switch refuses to boot after upgrading to 6.2

Flashed the exfat update upon upgrading. Coming from 5.1 going to 6.2: chose not to initialize. = Reinx and ofw will not boot after restarting switch once upgrade was done.
Restore NAND, 5.1 booting and working again.
Copy over fresh 6.2 firmware files from *cough*. Upgrade, choose exfat, and this time initialize. =Reinx and OFW will not boot. (hang on nintendo switch logo)
Format SD card, try fat32 nothing will boot
Restore NAND 5.1 booting and working again. This time I get atmosphere to work on 5.1 too.
Upgrade to 6.2 again and choose exfat update, no initialize. =Atmosphere will not boot.
Format SDcard (exfat) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Format SDcard (fat32) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Enter maintenance mode, initialize console.
Boot into atmosphere, get the logo, no nintendo logo black screen and top left corner charging icon, then all black.
Boot into atmosphere, get the nintendo logo, then black screen and no switch logo. Stuck
Boot Reinx 2.0, splash screen, black screen
Format SDcard (exfat) clean install reinx, boot, black screen after reinx boot logo.

Restoring my 5.1 nand now, anyone got tips on how the hell to get to 6.2?

I tried again this time initializing. Same thing. Going to try 7.0.1 tomorrow after I restore back to 5.1 tonight

Adran_Marit · Mar 7, 2019

Philliyxx said:
Trying to upgrade to 6.2 again but switch refuses to boot after upgrading to 6.2

Flashed the exfat update upon upgrading. Coming from 5.1 going to 6.2: chose not to initialize. = Reinx and ofw will not boot after restarting switch once upgrade was done.
Restore NAND, 5.1 booting and working again.
Copy over fresh 6.2 firmware files from *cough*. Upgrade, choose exfat, and this time initialize. =Reinx and OFW will not boot. (hang on nintendo switch logo)
Format SD card, try fat32 nothing will boot
Restore NAND 5.1 booting and working again. This time I get atmosphere to work on 5.1 too.
Upgrade to 6.2 again and choose exfat update, no initialize. =Atmosphere will not boot.
Format SDcard (exfat) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Format SDcard (fat32) and fresh atmosphere install = switch will not boot (does not get to switch logo, hangs on black screen after nintendo)
Enter maintenance mode, initialize console.
Boot into atmosphere, get the logo, no nintendo logo black screen and top left corner charging icon, then all black.
Boot into atmosphere, get the nintendo logo, then black screen and no switch logo. Stuck
Boot Reinx 2.0, splash screen, black screen
Format SDcard (exfat) clean install reinx, boot, black screen after reinx boot logo.

Restoring my 5.1 nand now, anyone got tips on how the hell to get to 6.2?

I tried again this time initializing. Same thing. Going to try 7.0.1 tomorrow after I restore back to 5.1 tonight

honestly sounds like you might have got a bad copy of 6.2

Philliyxx · Mar 8, 2019

5.1 atmosphere 0.8.5 boots fine.
Upgrade to 7.0.1 system initialize option. Switch reboots and get sept boot logo, atomosphere boot logo, nintendo boot logo, and then nintendo switch bootlogo infinetly hangs.
Re-format SDcard(exfat)= same thing.

xneuromancer · Mar 8, 2019

I'm having a strange problem. Once I open ChoiDujourNX, I can't move or select anything at all. The joycon's are directly connected to the Switch. The only buttons on the joycon's that work once I'm inside the app are camera, +, or home. all other buttons won't do anything at all. I've confirmed the joycons are working fine correctly on the home screen and every other homebrew app I have.

I also tried rebooting via Atmosphere to RCM, while the controllers were connected directly to the switch.

M7L7NK7 · Mar 8, 2019

Use the touchscreen

xneuromancer · Mar 8, 2019

Haha, I'm such an idiot. I didn't even realize the Switch had a touch screen! Thanks

tekken999 · Mar 9, 2019

I recently update from 4.0 to 6.2 with auto rcm via hekate. So once it’s been updated, is it still necessary to keep auto rcm on at all times in order to prevent burning the fuse?

Draxzelex · Mar 9, 2019

tekken999 said:
I recently update from 4.0 to 6.2 with auto rcm via hekate. So once it’s been updated, is it still necessary to keep auto rcm on at all times in order to prevent burning the fuse?

rajkosto said:
Q: I thought updating the firmware burned fuses, why would I use this instead of the official way of upgrading my Switch firmware (via cartridge or online, if I want the latest version)

A: Because fuses are burned on first normal boot, not during the install. By default, ChoiDujourNX will enable AutoRCM on any flashed firmware image, meaning that the normal nintendo bootloader will never get the chance to burn the fuses. And therefore, you can downgrade any time you want back to the firmware you started from. You can also arbitrarily downgrade to whatever firmware you want, as long as you are not using the nintendo bootloader to launch it (which will burn fuses if not enough fuses are burned, and panic if too many fuses are burned, check the table here http://switchbrew.org/index.php?title=Fuses#Anti-downgrade).

tekken999 · Mar 9, 2019

tekken999 said:
I recently update from 4.0 to 6.2 with auto rcm via hekate, once it’s been updated, is it still necessary to keep auto rcm on at all times in order to prevent burning the fuse?

So could I theoretically downgrade back to the original 4.0 fireware and then take off auto rcm and not worry about the Nintendo boot loader not burning fuses? Or would I have to use system initialize and reformat the microsd in order to avoid detection?

I also just don’t want the switch to accidentally somehow boot normally without auto rcm and have the fuses messed with. Not that it’s likely to happen

Kotomine Kirei · Mar 9, 2019

I installed firmware 6.2.0 (from 5.1.0), but I did not choose the exFat option (I must have missed it), and now the Switch goes to a black screen after leaving Hekate (I am guessing it is because my SD card is in the exFat format).
Can someone help me fix this?

Never mind.
I had to use a different SD card in the Fat32 format and re-install 6.2.0 with exFat support through ChoiDujourNX.
When I did that and switched back to the exFat SD card, everything seemed to work.

Draxzelex · Mar 9, 2019

tekken999 said:
So could I theoretically downgrade back to the original 4.0 fireware and then take off auto rcm and not worry about the Nintendo boot loader not burning fuses? Or would I have to use system initialize and reformat the microsd in order to avoid detection?

I also just don’t want the switch to accidentally somehow boot normally without auto rcm and have the fuses messed with. Not that it’s likely to happen

Well you can disable AutoRCM when you return back to your original firmware. But the system initialize isn't for avoiding detection because it is a well-known fact that system initializations don't prevent bans. The purpose of initializing your system is to allow downgrading across major firmware versions such as ones that differ in expected fuse counts. Some people are able to downgrade without doing it while others aren't and I haven't seen any official documentation explaining the requirements.

Fuses are also only burnt when you boot normally such as without AutoRCM while running a firmware higher than your fuse count. As long as you keep track of your current firmware, AutoRCM status, and number of fuses currently burnt, you will be fine.

tekken999 · Mar 9, 2019

Draxzelex said:
Well you can disable AutoRCM when you return back to your original firmware. But the system initialize isn't for avoiding detection because it is a well-known fact that system initializations don't prevent bans. The purpose of initializing your system is to allow downgrading across major firmware versions such as ones that differ in expected fuse counts. Some people are able to downgrade without doing it while others aren't and I haven't seen any official documentation explaining the requirements.

Fuses are also only burnt when you boot normally such as without AutoRCM while running a firmware higher than your fuse count. As long as you keep track of your current firmware, AutoRCM status, and number of fuses currently burnt, you will be fine.

Awesome, appreciate the help cheers!

lionheartzel · Mar 12, 2019

my nintendo switch cant use touch screen anymore. and i cant fix it
so i cant update by using choidujournx.

anyone know another way to using choidujournx with button/joycon or another homebrew?

(

FanboyKilla · Mar 12, 2019

We all know that it's possible to upgrade/downgrade via ChoiDujourNX, BUT, is it possible for someone to SIDEGRADE to a different firmware AND still be able to play online? I got a buddy who's on 5.1.0 FW and was thinking about upgrading his FW so that he could play online. He's not really into CFW "YET" but I think that will eventually change after he gets bored of playing online etc. So I told him that he should at least wait and let me see if there was a way for him to sidegrade to 6.2.0 FW. I thought I remember seeing somewhere that one of the ways to do it was to find a game that required the firmware you wanted to be on, and then just use the game cartridge to update to that FW. But since I don't know of ANY games that require 6.2.0 FW, I'm wondering if there is another way that's possible?

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

Walküre's Hacker

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Walküre's Hacker

Well-Known Member

Member

Well-Known Member

Member

Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

Active Member

Well-Known Member

Similar threads

Popular threads in this forum