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

[Draxzelex]

Help i tried updating my switch firmware with this tool to 6.0 now it won't boot anymore. unknown package1, Failed to launch firmware.
(i don't have a backup)

https://gbatemp.net/threads/psa-do-not-update-to-a-new-firmware-immediately-e-g-6-0.516497/

Restore your rawnand.bin. There is absolutely no reason for you to be installing 6.0 at the current time.

 

[Buurmanzz92]

i don't have a rawnand.bin i know i just wanted to see if it worked. stupid of me.

 

[Draxzelex]

i don't have a rawnand.bin i know i just wanted to see if it worked. stupid of me.

Follow this tutorial on how to reflash your original firmware version: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

 

[Buurmanzz92]

Follow this tutorial on how to reflash your original firmware version: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

sorry but this is a bit overwhelming can you help me a bit ? do i have to complete all the steps ? make a backup now first ?

 

[Draxzelex]

sorry but this is a bit overwhelming can you help me a bit ? do i have to complete all the steps ? make a backup now first ?

Whatever you installed is preventing your console from booting up. I would suggest using ChoiDujour to generate a set of safe firmware files for you to copy and paste into your NAND using memloader hence why I linked the guide. A backup at this point is meaningless as the console is now semi-bricked. Also the tutorial I linked is very user-friendly and guaranteed to work if you follow it to the letter.

 

[ZachyCatGames]

Help i tried updating my switch firmware with this tool to 6.0 now it won't boot anymore. unknown package1, Failed to launch firmware.
(i don't have a backup)

You need a modified version of hekate or the latest ReiNX commit

 

[Buurmanzz92]

You need a modified version of hekate or the latest ReiNX commit

when i try to load up with latest hektate i get : Could not open /bootloader/hektate_ipl.ini. Make sure it exists in SD card

 

[ZachyCatGames]

when i try to load up with latest hektate i get : Could not open /bootloader/hektate_ipl.ini. Make sure it exists in SD card

Put the latest version of this on your SD card: https://github.com/tumGER/SDFilesSwitch/releases
then open /bootloader/hekate/hekate_ipl.ini on your SD card and remove the "kip1=modules/newfirm/pm.kip" and "kip1patch=nosigchk" lines because they don't work on 6.0 (you can try leaving them, but if I leave them it crashes)
And use this as the payload:https://drive.google.com/open?id=1UYgSqIm7e071l56CgcP2g36F7r72XyFq (its just hekate CTCaer 4.0 with SciresM's 6.0 patch)

It should start up, although some things might not work or be unstable.

 

[Buurmanzz92]

Put the latest version of this on your SD card: https://github.com/tumGER/SDFilesSwitch/releases
then open /bootloader/hekate/hekate_ipl.ini on your SD card and remove the "kip1=modules/newfirm/pm.kip" and "kip1patch=nosigchk" lines because they don't work on 6.0 (you can try leaving them, but if I leave them it crashes)
And use this as the payload:https://drive.google.com/open?id=1UYgSqIm7e071l56CgcP2g36F7r72XyFq (its just hekate CTCaer 4.0 with a patch to support 6.0 made by SciresM)

It should start up, although some things might not work or be unstable.

Wow ! thanks a lot dude i got it back to life with this method ! is this the only way to boot my switch as of now ? should i do something to get it back to 5.0.1 or should i just wait for a sx os solution ? also can i boot back in ofw now ?

 

[ZachyCatGames]

Wow ! thanks a lot dude i got it back to life with this method ! is this the only way to boot my switch as of now ? should i do something to get it back to 5.0.1 or should i just wait for a sx os solution ? also can i boot back in ofw now ?

The latest commit of ReiNX should also work, or if your fine with losing your fuses you could probably disable autoRCM and start it normally. As far as I know there's no way to go back to 5.x from 6.x without losing all of your save data without a backup. You can use the stock option in Hekate or as I said earlier if your fine without losing your fuse(s) you could probably disable autoRCM and start it normally (although I wouldn't recommend this for now)

 

[jacobtc]

I'm on 2.3 right now, and are thinking about updating to 5.1 through this. Would I be able to go back to 2.3 if needed in the future?

 

[shchmue]

I'm on 2.3 right now, and are thinking about updating to 5.1 through this. Would I be able to go back to 2.3 if needed in the future?

yep, but you won't be able to keep any of your savegames or settings, you'll need to back up the saves before you go back down

 

[wurstpistole]

yep, but you won't be able to keep any of your savegames or settings, you'll need to back up the saves before you go back down

Only if you update with AutoRCM active, without burning fuses. If you boot OFW once it burns the fuses to 5.0.0 min

 

[shchmue]

Only if you update with AutoRCM active, without burning fuses. If you boot OFW once it burns the fuses to 5.0.0 min

i meant when going from 5.x to anything lower

wait no that has nothing to do with the compatibility of system saves across firmware versions

 

[jacobtc]

Only if you update with AutoRCM active, without burning fuses. If you boot OFW once it burns the fuses to 5.0.0 min

It was my understanding that ChoidujourNX install AutoRCM automatically?

 

[wurstpistole]

It was my understanding that ChoidujourNX install AutoRCM automatically?

You have the option to select. By standard, it's turned on. You can turn it off.

 

[jacobtc]

So I'm about to do this, however I do not want my GC to update, so does Hekate 4.0 not allow this to be prevented or should I use https://github.com/rajkosto/hekate/releases instead?

 

[shchmue]

So I'm about to do this, however I do not want my GC to update, so does Hekate 4.0 not allow this to be prevented or should I use https://github.com/rajkosto/hekate/releases instead?

hekate 4 supports kip1patch=nogc

 

[Hondyn]

For those who are having the 2168-0008 error, just do this:

• Q: After selecting ChoiDujourNX from the homebrew menu, it tries to start but closes immediately (or gives me a FATAL error, or just hangs at a black screen) !

• A: The debug svcs are not accessible to homebrew on your system. Either update your hbloader (from the release here: https://github.com/rajkosto/nx-hbloader/releases) or add fullsvcperm=1 to your hekate launch profile. Additionally, if you are trying to run ChoiDujourNX on 1.0.0, you must also add debugmode=1 to your hekate launch profile (this is not required on 2.0.0 or newer, which allows read-only debugging without it).

to make it even easier to understand, just download the files above and paste them on your sd root.

that worked for me

 

[Aerogems]

I'm on 2.3 right now, and are thinking about updating to 5.1 through this. Would I be able to go back to 2.3 if needed in the future?

There's a bit more to it. There are apparently fuses on the game cart reader that were altered with I think firmware 3.0 when Nintendo introduced a new type of cartridge. So you will have to go through some extra steps to preserve the fuses on the cart reader, otherwise you'll lose access to playing games via cartridge if you ever flash back to 2.3. You can find more details on the Switch subforums here at GBATemp.