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

[rajkosto]

That has nothing to do with this, while it does overwrite hekate_ipl.ini in the 4.0.0+ case you should probably know how to get it back to what it was.
Your error is likely due to you now not using the appropriate sysmodule replacements for your firmware (as it has changed).

 

[gallymimu]

So I updated from 4.1 to the latest using ChoixDujourNX and I noticed my hetake.ini was overwritten. After that I deleted everything from my SD and I got the latest version files from /tumGER/SDFilesSwitch (version 6.1). When I load CFW + Signature patch and when I try to enter a backup game it says "The software was closed because an error occurred.". Any solution for that? Thank you for your amazing work!

I am having a similar problem though I have not updated yet. I am on 4.0.1 and the 6.1 pack, when using CFW with sigpatch, I get errors upon launching installed NSPs.

 

[mooglazer]

These are common cartridges and firmware versions they contain:

I've read Taiko no Tatsujin (JPN) contains a 5.1.0 update partition. Is this true?

EDIT: Confirmed Taiko no Tatsujin (JPN) contains a 5.1.0 update. Updated from non-exFAT 5.1.0 to a proper exFAT version. This is brilliant. My only complaint is it overwrites your hekate_ipl.ini without backing up the previous version (I'm an idiot for not catching that in OP), not a huge deal but a minor annoyance. Everything else worked beautifully! Keep up the great work!

• 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.

 

[mooglazer]

Excuse me, but how did you manage to extract the update files?

hactool -x --intype=xci --updatedir=outupdatefolder Name.Of.The.Dump.xci

 

[shchmue]

backing up the original hekate_ipl.ini before replacing would be nice. otherwise this is great! used it to fix up my CD 1.0.2 upgrade which I guess was missing something

 

[mooglazer]

Is there any potential downside to running with `fullsvcperm=1` all the time?

 

[rajkosto]

Is there any potential downside to running with `fullsvcperm=1` all the time?

its probably better to just update hbloader, the release i link on my fork is the same as current master version (the change was accepted into mainline)

 

[veddermandan]

No. The ReiNX "community" (of noobs and children? it seems) is dismissive and hostile against anyone who criticizes their god-emperor.
I will not support it, especially since there's no benefit to using it over other solutions atm (no matter how much you wish to claim otherwise).

I only wrote what I wrote because of all the "Lol but muh REINX how use on that" posts in this thread. Anyone still making those can refer to it. I have nothing more to say.

Beautifully summed up mate. Besides you already tore them a new arsehole. Let them and they're weird fanboys lick their wounds.

 

[rajkosto]

backing up the original hekate_ipl.ini before replacing would be nice. otherwise this is great! used it to fix up my CD 1.0.2 upgrade which I guess was missing something

1.0.1 fixes your woes

 

[benson733]

Thanks for this!!! Appreciate the hard work and effort rajkosto!
So when it comes time for me to go from 4.1.0 to 5.1.0 and wanting to use SX OS I'll have to either have to launch hekate and use the forked hbl with enabled debugging svcs and launch the app or wait for TX to allow this with their hard-coded hbl? (This assumes TX adds this in the following update....)

 

[Zocker4444]

So I updated from 4.1 to the latest using ChoixDujourNX and I noticed my hetake.ini was overwritten. After that I deleted everything from my SD and I got the latest version files from /tumGER/SDFilesSwitch (version 6.1). When I load CFW + Signature patch and when I try to enter a backup game it says "The software was closed because an error occurred.". Any solution for that? Thank you for your amazing work!

I think you are missing the proper ES patch for for launching the games? look in the ReiNx/titles (if using reinx) or in the atmosphere/titles folder(if using atmosphere+hekate).
AFAIK there should be a folder ending with 33. If it isn't there, get the ES patching folder for your 5.x firmware.
But since it is copyright protectes you won't find that file here. And please don't ask for it

 

[rajkosto]

This isn't the thread for that. If you have pre-patched sysmodules in your "CFW" profile you might need to change them for your new firmware version.
The extent in which you verify if ChoiDujourNX "worked" is: Does it boot normally under [stock] or [PreventGCUpdates] (whichever one you need to use) ? If so, then it worked.

Getting "CFW" back up and working the way it was before you upgraded firmware is out of the scope of this thread or software.

 

[Pluupy]

Beautifully summed up mate. Besides you already tore them a new arsehole. Let them and they're weird fanboys lick their wounds.

What are you talking about?

 

[charlieb]

It only does so on 4.0.0+, theres no reason to do it earlier.

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



the child knows how to access the power menu ? i thought they would just put the switch to sleep, which has no problems.
(you can also shutdown just by holding the power button for 12 seconds, that wont come back up unless re-plugged into usb)

I'll see if i can get them to understand, again their young like 4 years old young. Thanks for this app btw, its a game changer!

 

[lordelan]

Idk.. .I thought OFW burns efuses even if its being launched by hekate

Not the OFW is burning the fuses but the original Nintendo bootloader (which boots the OFW) does. That happens if you don't have AutoRCM enabled and do a "normal" boot.
Booting into RCM (or having AutoRCM enabled while booting) and using hekate (or the TX payload 1.3 or above) replaces the step that the Nintendo bootloader would do while (obviously) not burning your fuses.

To make it clearer, coming from a completely turned off Switch:

1. Booting -> Nintendo Bootloader (say goodboy to your fuses) -> OFW
2. RCM booting -> hekate or TX payload -> OFW/CFW/whatever

 

[Deleted User]

@rajkosto I haven't had to use this yet but looking ahead this helps me and anyone intending to keep their modded switch offline. I just wanted to thank you for your work and continued support.

 

[veddermandan]

What are you talking about?

This sort of stuff

 

[wurstpistole]

This sort of stuff

Cringe.

 

[risq]

im still on 2.0.1, and i have only been using ReiNX so far. can i update to with ChoiDujourNx to 4.0.1. or higher without any negative impacts? can i downgrade with this to 2.0.1 for a possible coldboot solution later?

 

[wurstpistole]

im still on 2.0.1, and i have only been using ReiNX so far. can i update to with ChoiDujourNx to 4.0.1. or higher without any negative impacts? can i downgrade with this to 2.0.1 for a possible coldboot solution later?

Yes, and yes. If you stay on AutoRCM and never boot without it again, you will not burn fuses.
You have to boot your Switch with Hekate though everytime. If you boot original Horizon once, it'll burn your fuses.