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

[drfunkenstein2k]

OK, so i updated to 5.1.0 just fine and NO BURNED FUSES! woot
I can load SX-OS just fine, BUT
when i try to launch the firmware from Hekate payload i get two options:
STOCK-DANGEROUS
PreventGCUpdate

i choose PreventGCupdate but it seems i cannot get into HBloader from Gallery

 

[rajkosto]

You are not supposed to keep using the created hekate_ipl.ini.
Use whatever you feel like, just heed the warning about gamecart controller update (which means adding the kip1patch=nogc line to your new inis) if it applies to you.

 

[FR0ZN]

OK, so i updated to 5.1.0 just fine and NO BURNED FUSES! woot
I can load SX-OS just fine, BUT
when i try to launch the firmware from Hekate payload i get two options:
STOCK-DANGEROUS
PreventGCUpdate

i choose PreventGCupdate but it seems i cannot get into HBloader from Gallery

Your "hekate_ipl.ini" has been overwritten in the process.
Make sure that the one you used before has the "kip1patch=nogc" entry.

 

[rajkosto]

They were on 4.x already so they dont need it at all...

 

[drfunkenstein2k]

I made sure to make backups of all the hekate_ipl.ini

so my backup says the following:

"
{ }
{-- Custom Firmwares --}
[CFW]
kip1=modules/newfirm/loader.kip
kip1=modules/newfirm/sm.kip
kip1patch=nogc,nosigchk
[CFW for Firmware 1.0]
kip1=modules/oldfirm/loader.kip1
kip1=modules/oldfirm/sm.kip1
{ }

Is this right?

 

[Wierd_w]

They were on 4.x already so they dont need it at all...

Quite right. Same story for me. (factory at 4.0.1). I cannot downgrade below 4.0.1, as the fuse set is wrong, AND the GC slot firmware is already updated from the factory.

 

[wurstpistole]

When I bought the switch my firmware was updated to 4.1.0 then later I updated it to 5.1.0 before installing SX OS. I have no intention of downgrading the firmware but I would like to confirm if I were to use this tool to update to a higher firmware again in the future I will always need to boot into SX OS otherwise the fuses will burn if I accidentally boot into OFW correct?

I don't really know if SX OS is possible - since booting the switch with a choidujour update needs specific patches by hekate. But the way I read it you'd have to boot once with this modified file in hekate, and can then continue using your CFW of choice.

 

[drfunkenstein2k]

MY EXPERIENCE WITH ChoiDujourNX:
I started off on firmware 4.1.0 retail with 5 burned fuses (from stock).
I use SX-OS v1.4

I started by updating my hbloader to "nx-hbloader_with_debug.zip" "https://github.com/rajkosto/nx-hbloader/releases"
Then i put the ChoiDujourNX.nro in my "switch" dir on my sdcard
I made a folder on root called "firmwares"
Inside this dir i had 2 dirs named "fw410" and "fw510"
note: use xbins to find the firmwares.

GOING TO FW 5.1.0
1. Load SX-OS menu
2. launch external payload. "hekate_fspatches_v3.bin"
3. Checked FUSE info, as i mentioned i had 5 from stock already because i am on FW 4.1.0
4. I turned OFF the console.
5. I made a back up of my original "hekate_ipl.ini"
6. I made another "hekate_ipl.ini" but named it "hekate_ipl.iniNOGC" this one i modified with the code:
{ }
{-- Custom Firmwares --}
[CFW]
kip1=modules/newfirm/loader.kip
kip1=modules/newfirm/sm.kip
kip1patch=nogc,nosigchk
[CFW for Firmware 1.0]
kip1=modules/oldfirm/loader.kip1
kip1=modules/oldfirm/sm.kip1
{ }

7. Loaded SX-OS menu
8. launched payload "hekate_fspatches_v3.bin"
9. Launched CFW from payload.
10. Launched ChoiDujourNX from HBloader
11. Choose "fw510" dir with the option "5.1.0 (exfat)
12. it did its thing then asked to reboot.
13. I still had my SX-dongle in my console
14. it booted to SX-OS menu
15. I launched SX-OS and confirmed I was on 5.1.0 and played "Captain Toad" and "Go Vacation"

GOING BACK TO FW 4.1.0
First i swapped my "hekate_ipl.ini" to my "hekate_ipl.iniNOGC"
This means i took "hekate_ipl.iniNOGC" and named it "hekate_ipl.ini"
and i named "hekate_ipl.ini" to "hekate_ipl.inibak2"

1. Load SX-OS menu
2. launch external payload. "hekate_fspatches_v3.bin"
3. Checked FUSE info again (I am still at 5)
4. Launched CFW
5. Launched ChoiDujourNX from HBloader
6. Choose "fw410" dir with the option "4.1.0 (exfat)
7. It did its thing until it asked for reboot
8. Launched into SX-OS and checked firmware it read 4.1.0
9. I then uninstalled AutoRCM
10. I checked FUSE INFO one last time and I am still at (5 burned fuses)

Thanks for all those that helped me here. Hope this helps someone or gives them the confidence to use the tool.
This tool works great!

 

[cherup]

Just update to 5.1 perfectly with that tool. Thanks a the prefect work!

Just a question - will exFat be integrated automatically ?
I used the NX-5.1.0_exfat for updating which I created on the PC upfront (old method) - which integrated the exFat driver.

 

[rajkosto]

Just install the exFAT version of the firmware ?

 

[ToOldGamer]

drfunkenstein2k have you Installed AutoRCM in SX-OS v1.4 before you do this?

nice tool make it easy for old noobs like me.

 

[LeMageFro]

You guys are overthinking (and confusing tegra fuses with the gamecart controller fuses, they are separate) the whole gamecard update thing.

@muniategui so yeah, we weren't crazy, gamecart fuses indeed exist ! I don't think there is a way to check hown many are burnt though. Maybe it's somewhere in either "fuse info" or "kfuse info" ?

 

[rajkosto]

@muniategui so yeah, we weren't crazy, gamecart fuses indeed exist ! I don't think there is a way to check hown many are burnt though. Maybe it's somewhere in either "fuse info" or "kfuse info" ?

theres absolutely no way to know since they are on a separate black-box chip and all we know is that it wont run an older firmware once it has run a newer one.

 

[drfunkenstein2k]

drfunkenstein2k have you Installed AutoRCM in SX-OS v1.4 before you do this?

nice tool make it easy for old noobs like me.

No i did not. When i used ChoidujourNX it set up autoRCM automatically.
at the end of the experience when i went back to 4.1.0, I did use SX-OS to uninstall autoRCM.

 

[WiiFoundLove]

• Copy the SYSTEM:/Contents/registered folder from another Switch that is running the firmware version you want
• Copy the SYSTEM:/Contents folder from a Switch that has a "System update is pending" notification. This will let you pick either the currently running firmware, or the pending firmware to install.

So i need a second Switch to do this?

 

[drfunkenstein2k]

So i need a second Switch to do this?

No you do not. This is just one of the ways to obtain the firmware.

 

[WiiFoundLove]

Ah, ok. Thanx

 

[Reisyukaku]

For anyone who already has ReiNX installed and wants to keep using it after the whole updating procedure, you have to once use a hekate payload like: https://github.com/rajkosto/hekate/releases
Then you simply create a "hekate_ipl.ini" at the root of your SD card with this content:

[config]
autoboot=5
bootwait=3
customlogo=1
verification=2

{-------- CFW -------}
[ReiNX (SVC Perms)]
kip1=ReiNX/sysmodules/loader.kip
kip1=ReiNX/sysmodules/sm.kip
kip1=ReiNX/sysmodules/FS.kip
fullsvcperm=1

I used to do it like this on my 3.0.0 Switch and updated to 5.1.0 with ChoiDujourNX. Other FW versions like 1.0.0 probably require the debugmode entry as it's stated in the FAQ in OP.
The reason why you once need hekate, is because ReiNX most likely doesn't give full SVC permissions for homebrews, which ChoiDujourNX needs, or else it will crash upon launch (maybe @Reisyukaku can add it if he sees reason in that).

After the whole procedure, you can delete the created "hekate_ipl.ini" and copy the needed ReiNX files for your updated FW version. It offers all the neccessary patches like nogc, sigpatch and nocmac out of the box w/o further configuration.
Even exFAT is enabled in case you didn't choose to install the exFAT version of your desired update for some reason.

NOTE: I see a lot of arguments which CFW is better, or why choose it over the other. This post it not meant to start another discussion about CFW vs. CFW, I simply used ReiNX because I already had it on my SD card and tried to update with the least amount of "hassle" and keep on using it after the procedure. Freedom of choice should be allowed without verbal "fights", so please let this post fly under the radar.

Regards,
iCEQB

I'll add svcperm to my to-do list

Concerning ReiNX--

If you update, you need to put the correct files on your SDcard for the updated version. Works just fine if you do that.

Yea the way things are progressing, hoping this weekend to have everything on the fly.

 

[Wierd_w]

I'll add svcperm to my to-do list


Yea the way things are progressing, hoping this weekend to have everything on the fly.

Oh good! On the fly patching means no Ninty Copyrighted stuff, which means full sigpatch version here on GBAT. Still cant bundle romenu though, even though it is an improperly updated tinfoil.

 

[CatmanFan]

You can't downgrade using this right?