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

[Xyphoseos]

if you can PLAY a cartridge, it's kind of obvious your game cart reader has been updated to actually read the cart, don't you think ?

yes that's true ^^

 

[Xyphoseos]

without nogc, gamecart firm will be updated and in ealier firmware we'll not able to play gamecart but why we would play gamecart in older firm, if we update to install softmod we will be able to update then in latest version and finaly play gc isn't it ?

 

[M7L7NK7]

Exactly, with backup loading you don't really need your cart fuse

 

[muniategui]

I have a doubt, i've i'm on 4.1 and i update to 5.1 (since gc is already fuse due to swtich come stock 4.1 ). Then after using CFW on 5.1 i've decide for X reason i want to downgrade again to my stock 4.1. After downgrading if i start OF would i get burned fuses or not? Teorically i've been always in the same version in OF perspective or i'm wrong? So i would get 2 burned fuses, 1 or 0?

 

[Azel]

without nogc, gamecart firm will be updated and in ealier firmware we'll not able to play gamecart but why we would play gamecart in older firm, if we update to install softmod we will be able to update then in latest version and finaly play gc isn't it ?

I don't know, but NEVER boot stock fw and NEVER boot hekate without kip1patch=nogc in you hekate ini, or you will update you cart reader fw and fuse count.

If you don't know why you want something...why even bother about it ?

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.

EDIT : had trouble running it, found how to do it :

I modified my ini like this :

kip1=modules/newfirm/loader.kip
kip1=modules/newfirm/sm.kip
kip1patch=nogc,nosigchk

thanks for your help, was really impressed with ChoixDuJour fuctionality and UI/Touch!

 

[Xyphoseos]

I don't know, but NEVER boot stock fw and NEVER boot hekate without kip1patch=nogc in you hekate ini, or you will update you cart reader fw and fuse count.

If you don't know why you want something...why even bother about it ?



Sorry to bother you with this again, but like I said, with no gc, I want my owned cart in eshop format, I know this is out of the scope of this thread, but many ppl will come back asking for this, I can't figure out how to run Hekate with reinx fs.kip, probably since I've never played with any of this before.

Obviously, I managed to use hekate_fspatches_v3>ChoixDuJour v101 just fine to go from 3.0.1 to 5.1, and boot to 5.1. gotta say I'm impressed with the GUI and functionality of this :o

then it a stall :

I modified my ini like this :

[config]
autoboot=0
bootwait=3
customlogo=0
verification=2
{ }
{Launch Homebrew Menu by pressing}
{"R" while launching the album}
[CFW and PreventGCUpdate]
kip1patch=nogc
kip1=modules/atmosphere/loader.kip
kip1=modules/atmosphere/sm.kip
kip1=modules/atmosphere/fs.kip
logopath=modules/atmosphere/atmosphere.bmp
[CFW2 and PreventGCUpdate]
kip1patch=nogc
kip1=modules/newfirm/loader.kip
kip1=modules/newfirm/sm.kip
kip1=modules/atmosphere/fs.kip
logopath=modules/atmosphere/atmosphere.bmp

none of the two options boot, I get a red "REQUESTED PATCH 'nogc' NOT APPLIED.

modules/atmosphere/loader.kip, modules/atmosphere/sm.kip, modules/newfirm/loader.kip, modules/atmosphere/fs.kip are from TumGER's SDFilesV61

modules/atmosphere/fs.kip is from reinx archive reinx/sysmodules/

I have sd:\atmosphere\titles\0100000000000033\ files.

I guess I'm close, but yeah, not there yet. :\

If I understand to "Stock DANGEROUS" option in .ini will update my gc AND burnt my fuse ?
Or just gc ?

 

[Azel]

Yes

 

[Xyphoseos]

Yes

Is there a way to update gc without burnt efuse ?

 

[muniategui]

Is there a way to update gc without burnt efuse ?

Can't post hyperlinks since new but look for that title in gbatemp, it is explained how to update with no GC burn nor normal fuse burn(firm burns)

how-to-install-run-any-switch-firmware-unofficially-without-burning-any-fuses

 

[Xyphoseos]

Can't post hyperlinks since new but look for that title in gbatemp, it is explained how to update with no GC burn nor normal fuse burn(firm burns)

how-to-install-run-any-switch-firmware-unofficially-without-burning-any-fuses

I want no fuse burnt with the gc port updated

 

[Azel]

I suppose this guide is deprecated since ChoixDuJourNX is out.

 

[muniategui]

I want no fuse burnt with the gc port updated

Once you update if you use a sysmodule to skip gc burn you will have gc updated with no burn (as long as you dont bot OF firmware obiously)

I suppose this guide is deprecated since ChoixDuJourNX is out.

It is also explained in point 6 that from there all can be done with Choi

 

[Xyphoseos]

Once you update if you use a sysmodule to skip gc burn you will have gc updated with no burn (as long as you dont bot OF firmware obiously)



It is also explained in point 6 that from there all can be done with Choi

which sysmodule ?

 

[muniategui]

which sysmodule ?

IF YOUR CARTRIDGE SLOT WORKS ON <4.0.0 FIRMWARE AND YOU WISH TO KEEP IT THAT WAY, YOU MUST ALWAYS LOAD 4.0.0 OR HIGHER FIRMWARE USING THE [FS_XXX] OPTION WHICH USES REPLACEMENT FS_XXX_nogc.kip1 SYSMODULE VIA HEKATE ! EVEN A SINGLE BOOT WITHOUT THAT SYSMODULE REPLACEMENT USED WILL PERMANENTLY UPGRADE THE GAME CARTRIDGE CONTROLLER FIRMWARE TO THE 4.0.0 VERSION, MAKING IT UNUSABLE IN EARLIER FIRMWARES (so any "CFW" ini files you use YOU MUST ADD THE PROPER FS_XXX_nogc.kip1 LINE TO ALL ENTRIES).

However with Choi

• Q: I've never run firmware 4.0.0 or higher on my switch, so my gamecard controller firmware is still not updated. How do i make sure my gamecard controller works after i downgrade back to < 4.0.0 ?
• A: When flashing the firmware image for any 4.0.0 or later firmware, ChoiDujourNX will generate a protective hekate_ipl.ini on your microsd, with a "PreventGCUpdate" launch target. You must ALWAYS boot using this launch target (or add kip1patch=nogc to any launch target you wish to use in the future) and use a Hekate that supports the kip1patch option (releases here do: https://github.com/rajkosto/hekate/releases) if you want to prevent use and updating of your GC controller firmware on firmware versions 4.0.0 and up.

So its even easyer

 

[Xyphoseos]

IF YOUR CARTRIDGE SLOT WORKS ON <4.0.0 FIRMWARE AND YOU WISH TO KEEP IT THAT WAY, YOU MUST ALWAYS LOAD 4.0.0 OR HIGHER FIRMWARE USING THE [FS_XXX] OPTION WHICH USES REPLACEMENT FS_XXX_nogc.kip1 SYSMODULE VIA HEKATE ! EVEN A SINGLE BOOT WITHOUT THAT SYSMODULE REPLACEMENT USED WILL PERMANENTLY UPGRADE THE GAME CARTRIDGE CONTROLLER FIRMWARE TO THE 4.0.0 VERSION, MAKING IT UNUSABLE IN EARLIER FIRMWARES (so any "CFW" ini files you use YOU MUST ADD THE PROPER FS_XXX_nogc.kip1 LINE TO ALL ENTRIES).

it doesn't help me


I want no fuse burnt but I want to be able to play cartridge

 

[muniategui]

it doesn't help me


I want no fuse burnt but I want to be able to play cartridge

As i understand you will have a cartridge of firmware 5.1 (if u update to 5.1) without burned fuses as long as you boot cfw and never the OF
You mean that without a burn cart will not work on 5.1? I think that it's patched to avoid fuse verification (at least SX SO i don't know atmosphere but i supose that also included)

 

[LeMageFro]

If I understand to "Stock DANGEROUS" option in .ini will update my gc AND burnt my fuse ?
Or just gc ?

I think there is misunderstanding between you and Azel. If you use the "Stock DANGEROUS" option it WILL NOT burn the efuses related to your firmware version, hekate always prevent efuse burning. But I think I read somewhere that the card reader also has it's own efuses, and therefor updating it would burn some of these, and that's probably what Azel meant when he answered yes. I have no idea if these "card reader" efuses actually exist though, it's just a vague memory and may be completely false. Maybe someone more informed could help.

 

[Xyphoseos]

I think there is misunderstanding between you and Azel. If you use the "Stock DANGEROUS" option it WILL NOT burn the efuses related to your firmware version, hekate always prevent efuse burning. But I think I read somewhere that the card reader also has it's own efuses, and therefor updating it would burn some of these, and that's probably what Azel meant when he answered yes. I have no idea if these "card reader" efuses actually exist though, it's just a vague memory and may be completely false. Maybe someone more informed could help.

So if I launch "STOCK DANGEROUS"
I will be able to play cartridge with no fuse burnt
Right ?

 

[LeMageFro]

As i understand you will have a cartridge of firmware 5.1 (if u update to 5.1) without burned fuses as long as you boot cfw and never the OF

You can absolutely boot the OF and not burn efuses. The piece of software that burns efuses is the original nintendo bootloader, not the firmware itself. As long as you use autoRCM + hekate (which replaces the nintendo bootloader) you won't burn efuses. Again guys, read the damn FAQ, I'm merely rephrasing it here !

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

So if I launch "STOCK DANGEROUS"
I will be able to play cartridge with no fuse burnt
Right ?

Right ! I woud still advise against it though since it's an irreversible process, but hey if you're sure you won't ever need to use cards on a firmware lower than 4.0 then it's your choice .

 

[muniategui]

You can absolutely boot the OF and not burn efuses. The piece of software that burns efuses is the original nintendo bootloader, not the firmware itself. As long as you use autoRCM + hekate (which replaces the nintendo bootloader) you won't burn efuses. Again guys, read the damn FAQ, I'm merely rephrasing it here !

So my doubt is if i use autoRMC + hekate after flashing, the second time i boot my NS if i boot OF fuses will burn since its oficial bootloader again right?