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

[salvatore]

after update to 6.1 ask me to update joy what to do?

 

[takeitfish]

I'm an idiot... my 200GB SDXC card turns out to not be 200GB at all but a fake 32GB one. After so many issues I finally ran h2testw over the whole card and it confirmed - only the first 32GB worked, the rest all failed. No wonder all those Firmware update files kept going missing after copying :/

I used my real 32GB card and it updated me just fine. I went to 6.0.1 on EmuNAND..but haven't agreed to the controller update yet. But then why not ey.

 

[Bushido1992]

is that right that i can downgrade my 6.1.0 to 5.1.0 with fusesburn Count from 6.1.0 (7 burned)? Also 5.1.0 with Hekate Bootloader and SX OS?

 

[Draxzelex]

is that right that i can downgrade my 6.1.0 to 5.1.0 with fusesburn Count from 6.1.0 (7 burned)? Also 5.1.0 with Hekate Bootloader and SX OS?

Yes but you will lose access to sleep mode upon doing so.

 

[XaneTenshi]

is that right that i can downgrade my 6.1.0 to 5.1.0 with fusesburn Count from 6.1.0? Also 5.1.0 with Hekate Bootloader and SX OS?

Yes and no. In theory, you can even use ChoiDujourNX to downgrade all the way down to FW 1.0.0 if you'd like, but because your fuses are burned you would always have to boot using a custom bootloader. More importantly, sleep will be broken if you downgrade to a firmware that doesn't match your fuse count, because the fuse check is unfortunately also done on wake up from sleep mode-.-

EDIT: Draxzelex, you damn ninja!!!

 

[Bushido1992]

Yes and no. In theory, you can even use ChoiDujourNX to downgrade all the way down to FW 1.0.0 if you'd like, but because your fuses are burned you would always have to boot using a custom bootloader. More importantly, sleep will be broken if you downgrade to a firmware that doesn't match your fuse count, because the fuse check is unfortunately also done on wake up from sleep mode-.-

EDIT: Draxzelex, you damn ninja!!!

okay, thanks !

 

[mikefor20]

Hello all! Rajkosto San!
Thank you for all your work. I am trying to update with ChoiDuJour and there is some really wrong. I am on 3.0.1 and I really want to update to 5.1 or higher so I can play a few new titles. Every attempt with ChoiDujourNX resulting a being stuck on the Switch logo, I tried getting the update files from several sources. Formatting the SD in ExFat and FAT32. Tried 3 different SD cards. Tried running Choi under SXOS, ReiNX, Atmosphere and of course RajNX. I am out of ideas except initialize the system. Any ideas? Plus if I initialize the system ill lose my User profile. I want my saves to work. Should I go online and download the profile after initialization? will error logs and such still be present after initialization? Also I noticed on your pastebin there is a BackupUser.Js and RestoreUser.JS.. Could there be a solution? Thank you for your help.

 

[notimp]

You would do a factory reset, wont you?

Do you know what FAQ means? Like the FAQ listed in the first posting?

FAQ:

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

Also, its heartwarming to hear your entire story for why you want to use choixdujournx - but this still isnt a propper error report:

Every attempt with ChoiDujourNX resulting a being stuck on the Switch logo

 

[notimp]

Then please provide a proper issue description.

We trolls cant mindread, if you did read stuff or not. (You have to provide us with that information.) So we start with the most likely scenario.

Second most likely scenario interpreting your issue description as "program just crashes upon launch" - as with all instances where everyone says something works - but one guy says it doesnt, is that you have a corrupt file system.

Also - of course, I wont support you on the issue any further. Im no masochist.

(What the mill... doesnt know is that not all trolling is bad. But everyone in his agegroup tells him it is, so he starts to character assassinate people actually trying to help him.)

 

[mikefor20]

You would do a factory reset, wont you?

Do you know what FAQ means? Like the FAQ listed in the first posting?



Also, its heartwarming to hear your entire story for why you want to use choixdujournx - but this still isnt a propper error report:

I am using that build, I can read. Troll

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

it copied that version over again in case and now when i click the album I get error 2347-0003 under kosmos.atmo

 

[notimp]

To give anyone wanting to pick up for this consumer a hand - the switch logo isnt supposed to show up at any point in the process - so he is doing some real user error level stuff wrong.

He said, that he already did, whats stated in the faq - when did it "again", then his error profile changed.

Also - kosmos.atmo isnt a thing - and if we start supporting "easy setup bundles" instead of proper installations, we can just hang ourselves beforehand, that saves everyone some time.

I actually might suggest - giving this user some space - to create his own safespace - on the road to finding out, that listing specific error codes, usually doesnt help either. Let him figure this one out. (To prevent the biggest casualties: Factory reset is not a solution.)

 

[mikefor20]

I apologize for my attitude I was just following suit. You must admit, you are kind of abrasive...

The "Heartwarming story"was about telling you details.

seems it wants a nro, it's there. ill figure this out yet

Same bootloop

It said to extract to root but didn't say to install the nsp... maybe I should.

 

[notimp]

Dont install the nsp - this is actually the only nsp you never will install.

edit:

The choixdujournx "app" is an .nro - you will launch it through hbmenu (https://github.com/switchbrew/nx-hbmenu/releases/tag/v3.0.0). (When this tutorial was written accessing hbmenu usually was done through gallery - and not through a menu shortcut, or anything of that sort)

The nx-hbloader (https://github.com/rajkosto/nx-hbloader/releases) linked in the faq, actually also shouldnt be needed with current atmosphere setups... So maybe remove those files from your sdcard again - on second thought. (That one is on me - I'll get into more details on it later).

The intended launch process is as follows:

Firmware (f.e. atmosphere) gets booted up, loads a loader nsp (currently called hbl.nsp (the one in the faq package is called loader.nsp, which makes me weary of recommending using that package - seems "old")), which is the only nsp that you should never install, it gets executed in place. This loader nsp then is responsible for loading hbmenu - when you click on gallery. (hbmenu.nro has to be in root as well.)

This loader nsp also has to provide hbmenu and then choixdujournx with some debug syscalls, which not all of them did in the past, but actually most current ones (Kosmos) should do. If the current one in Kosmos actually does, I dont know - you'd have to ask the package provider. (It should though.)

At no point do you actually actively launch a nsp by clicking on an nsp icon - try to stick to opening hbmenu via the gallery button just to rule out other possible issues ("after the switch logo shows up?"). No switch logo should show up at any point.

So here is what you do.

1. Reboot the system - try if using the hb loader from the faq actually solved your issue (you have to reboot after copying it on the sdcard - or it might not work, if you already did that (= if f.e. you did take out the sdcard which makes you reboot the system), you can skip this step.

2. Remove the files from the hb loader package in the faq from your sdcard again. Reboot the system - try to launch choixdujournx again - this time through the gallery (>hbmenu then choixdujournx). This should work.


If it doesnt.

3. Doublecheck the Kosmos package installation. Maybe copy all the files and folders over again (Dont use MacOS to rule out other potential issues).

If that doesnt work, ask in the Kosmos thread, if anyone has the same issues as you do with Choixdujournx.



Here are known working versions of hbloader ( https://github.com/switchbrew/nx-hbloader/releases/ ) and hbmenu ( https://github.com/switchbrew/nx-hbmenu/releases/tag/v3.0.0 ) that work with current atmosphere (including the sigpatches, if that matters). But - how the hbloader is named (hbl.nsp or loader.nsp), and how it gets the debug permissions, depends on the actual CFW you are using.

So this is where you trust your "package provider" (Kosmos) or do some legwork on your own.

As you see - this isnt the easiest issue to troubleshoot.

And all the while - every issue here could be caused by a corrupt filesystem, and the files on the sdcard being actually faulty - but this time, lets not assume that straight away.

 

[notimp]

Also - if your excellent issue description of "resulting being stuck on the switch logo" actually means, that you successfully launched choixdujournx and flashed a firmware - and are now stuck booting it - which you recovered from HOW?

Then everything I just posted was useless and wrong.

Because at this point this has nothing to do with choixdujournx anymore - but with "my CFW wont boot" - but for that to be the case you really must have skipped heaven and earth in your error description.

Of course none of what you posted immediately makes sense, and you refuse to actually post an error description that isnt a grammatically wrong fragment of a sentence, that actually isnt very descriptive.

("I've tried everything." "Sure. Now whats the issue" "I stuck at the logo." "What, where? Trying to do what?" "I've tried everything, should I factory reset or use javascript applets?")

 

[Bushido1992]

Is it possible to downgrade from 6.1.0 to 6.0.0 then create sx os emunand (also i test it in 2 other switches it works perfekt on 6.0.0) and then go back to 6.1.0 with sysnand + emunand? Also i mean because the sleep Mode

 

[XaneTenshi]

Is it possible to downgrade from 6.1.0 to 6.0.0 then create sx os emunand (also i test it in 2 other switches it works perfekt on 6.0.0) and then go back to 6.1.0 with sysnand + emunand? Also i mean because the sleep Mode

No fuses are burned between 6.0.0 and 6.1.0, so this shouldn't be an issue at all. Do mind that 6.2.0 does burn 1 additional fuse, so going from 6.1.0 to 6.2.0 will burn a fuse (or several, if your fuse count matches a lower firmware).

 

[Bushido1992]

No fuses are burned between 6.0.0 and 6.1.0, so this shouldn't be an issue at all. Do mind that 6.2.0 does burn 1 additional fuse, so going from 6.1.0 to 6.2.0 will burn a fuse (or several, if your fuse count matches a lower firmware).

Fusesbwas burned on Update 6.1.0 count 7.the idea behind is that ive think emunand actually is bugged on 6.1.0. (ive try to create emunand on a friend Switch on 6.0.0 that worked, then Updatet via choidojournx to 6.1.0 worked as well)

 

[mikefor20]

The trolling around here is rampant. People around here from time to time pretend to know things and be helpful even though they are just childish trolls.

Hello all! Rajkosto San!
Thank you for all your work. I am trying to update with ChoiDuJour and there is some really wrong. I am on 3.0.1 and I really want to update to 5.1 or higher so I can play a few new titles. Every attempt with ChoiDujourNX resulting a being stuck on the Switch logo, I tried getting the update files from several sources. Formatting the SD in ExFat and FAT32. Tried 3 different SD cards. Tried running Choi under SXOS, ReiNX, Atmosphere and of course RajNX. I am out of ideas except initialize the system. Any ideas? Plus if I initialize the system ill lose my User profile. I want my saves to work. Should I go online and download the profile after initialization? will error logs and such still be present after initialization? Also I noticed on your pastebin there is a BackupUser.Js and RestoreUser.JS.. Could there be a solution? Thank you for your help.

My original "heartwarming story", as you called it, has all the information you say I omitted.

You would do a factory reset, wont you?

Do you know what FAQ means? Like the FAQ listed in the first posting?



Also, its heartwarming to hear your entire story for why you want to use choixdujournx - but this still isnt a propper error report:

, I read fine. And my "story" states that I ran Choi, its obviously not a problem getting in to HBL. I'll entertain your theory as I am out of guesses and why not..

Then please provide a proper issue description.

We trolls cant mindread, if you did read stuff or not. (You have to provide us with that information.) So we start with the most likely scenario.

Second most likely scenario interpreting your issue description as "program just crashes upon launch" - as with all instances where everyone says something works - but one guy says it doesnt, is that you have a corrupt file system.

Also - of course, I wont support you on the issue any further. Im no masochist.

(What the mill... doesnt know is that not all trolling is bad. But everyone in his agegroup tells him it is, so he starts to character assassinate people actually trying to help him.)

I did provide a description. It seems you make an effort for a second. It looked that way at least so I stroked your ego a bit to try to get you to be civil. What a waste of time. And trolling is bad. You call out people for BS. Confising the issue and pissing people off without any real knowledge to back it up. You didn't even read my posts.

To give anyone wanting to pick up for this consumer a hand - the switch logo isnt supposed to show up at any point in the process - so he is doing some real user error level stuff wrong.

He said, that he already did, whats stated in the faq - when did it "again", then his error profile changed.

Also - kosmos.atmo isnt a thing - and if we start supporting "easy setup bundles" instead of proper installations, we can just hang ourselves beforehand, that saves everyone some time.

I actually might suggest - giving this user some space - to create his own safespace - on the road to finding out, that listing specific error codes, usually doesnt help either. Let him figure this one out. (To prevent the biggest casualties: Factory reset is not a solution.)

Here's were you really let your troll self show. The Switch logo show AT BOOT, Like I said. Just because your comprehension is sub par does not mean I am wrong. There is no error code in a boot loop. Troll, I mean try again. The only error code happened after I put the HBL with svc mode title files you liked to. That was the only error.. and you caused it. You didn;t need to interperate my statement. I speak english, and Kosmos , is SDfiles, SD files IS Atmosphere setup. I said Kosmos/Atmosphere to let you know it was up to date. If you knew your stuff and read my "story" you would know that.

Dont install the nsp - this is actually the only nsp you never will install.

edit:

The choixdujournx "app" is an .nro - you will launch it through hbmenu (https://github.com/switchbrew/nx-hbmenu/releases/tag/v3.0.0). (When this tutorial was written accessing hbmenu usually was done through gallery - and not through a menu shortcut, or anything of that sort)

The nx-hbloader (https://github.com/rajkosto/nx-hbloader/releases) linked in the faq, actually also shouldnt be needed with current atmosphere setups... So maybe remove those files from your sdcard again - on second thought. (That one is on me - I'll get into more details on it later).

The intended launch process is as follows:

Firmware (f.e. atmosphere) gets booted up, loads a loader nsp (currently called hbl.nsp (the one in the faq package is called loader.nsp, which makes me weary of recommending using that package - seems "old")), which is the only nsp that you should never install, it gets executed in place. This loader nsp then is responsible for loading hbmenu - when you click on gallery. (hbmenu.nro has to be in root as well.)

This loader nsp also has to provide hbmenu and then choixdujournx with some debug syscalls, which not all of them did in the past, but actually most current ones (Kosmos) should do. If the current one in Kosmos actually does, I dont know - you'd have to ask the package provider. (It should though.)

At no point do you actually actively launch a nsp by clicking on an nsp icon - try to stick to opening hbmenu via the gallery button just to rule out other possible issues ("after the switch logo shows up?"). No switch logo should show up at any point.

So here is what you do.

1. Reboot the system - try if using the hb loader from the faq actually solved your issue (you have to reboot after copying it on the sdcard - or it might not work, if you already did that (= if f.e. you did take out the sdcard which makes you reboot the system), you can skip this step.

2. Remove the files from the hb loader package in the faq from your sdcard again. Reboot the system - try to launch choixdujournx again - this time through the gallery (>hbmenu then choixdujournx). This should work.


If it doesnt.

3. Doublecheck the Kosmos package installation. Maybe copy all the files and folders over again (Dont use MacOS to rule out other potential issues).

If that doesnt work, ask in the Kosmos thread, if anyone has the same issues as you do with Choixdujournx.



Here are known working versions of hbloader ( https://github.com/switchbrew/nx-hbloader/releases/ ) and hbmenu ( https://github.com/switchbrew/nx-hbmenu/releases/tag/v3.0.0 ) that work with current atmosphere (including the sigpatches, if that matters). But - how the hbloader is named (hbl.nsp or loader.nsp), and how it gets the debug permissions, depends on the actual CFW you are using.

So this is where you trust your "package provider" (Kosmos) or do some legwork on your own.

As you see - this isnt the easiest issue to troubleshoot.

And all the while - every issue here could be caused by a corrupt filesystem, and the files on the sdcard being actually faulty - but this time, lets not assume that straight away.

I already ruled all this out too IF you read my Heartwarming story. I understand how to run homebrew. I am not new to this. I am not asking how to run Choi. I just want to update WITHOUT A BOOTLOOP.

1. plenty of reboots, the HBL from the FAQ was tried early on in my process. I may have installed the damn nsp though. Not sure was weeks ago.
2. I have launched Choi through Atmo, Kosmos, ReiNX, RajNX and SXOS all with the same result. Like I said in my Heartwarming story.
3. I tried re-downloding EVERY file,4 SD cards, Fat32 and ExFAT and several sources for the update files. Like I said in my Heartwarming Story. Did you even read this stuff?

Why would I ask in the Kosmos thread? EVERY CFW GETS THE SAME RESULT. IT'S NOT KOSMOS SPECIFIC. READ

Also - if your excellent issue description of "resulting being stuck on the switch logo" actually means, that you successfully launched choixdujournx and flashed a firmware - and are now stuck booting it - which you recovered from HOW?

Then everything I just posted was useless and wrong.

Because at this point this has nothing to do with choixdujournx anymore - but with "my CFW wont boot" - but for that to be the case you really must have skipped heaven and earth in your error description.

Of course none of what you posted immediately makes sense, and you refuse to actually post an error description that isnt a grammatically wrong fragment of a sentence, that actually isnt very descriptive.

("I've tried everything." "Sure. Now whats the issue" "I stuck at the logo." "What, where? Trying to do what?" "I've tried everything, should I factory reset or use javascript applets?")

Once again, yes NoTip, everything you post is useless. It has everything to do with Choi or something lingering on my system from prior fuckery. Or maybe something I am not seeing. Before I came here I already tried all your solutions. They are all obvious. Same boot loop. Next thing is make sure my system isn't causing it. Some ghost in the machine. So I was wondering how to stay offline, do a system initialization and not lose my save games. I know how to read so I am aware initialization will delete my user profile, which my saves are linked to, rendering my saves useless. Rajkosto, who wrote ChoiDuJour in case you didn't comprehend that post either, wrote a JavaScript to Backup/Restore user. It's in his PasteBin. I was asking if I could use that to backup my profile, initialize the system, and the restore user without going online. That's when you stepped in . confused the issue, and took me on a wild goose chase. I happily followed because I am running out of ideas.

I hope that the mods don't cut this to hell. I hope they at least leave the information in there so I can find a solution,. Hopefully Rajkosto will read this. He might have an idea. This issue may occur again to someone else. and this may be useful in the future. I promise a full write up of any solution I find.

So just one more time in case so mods have something good to leave behind. I am attempting to update from 3.0.1 to 5.1 or higher so I can play new titles. My Switch is a launch switch. The update history is as follows. I updated from 1.0 to 3.0 using CDN to download the Zelda DLC 1. Haven't been online since. I update to 3.0.1 using the SMO cart, to 3.0.2 using Xenoblade 2 cart. Back down to 3.0 with Hekake as it was my "Cleanest" backup after my first Choi boot loop.. then back up to 3.0.1 with SMO again. I sold Xenoblade 2. fuse count is 4 burnt fuses.(3.0.1-3.0.2)

I do not wish to go online until/IF a proven unbanable solution exists. I am trying to use ChoiDuJourNX to update offline. I have tried running Choi under all current CFWs (Rei ,Raj ,Atmo/Kosmos and SXOS) All go through the process and get stuck on a bootloop switch logo at boot. I have tried 4 different SD cards now. it's not the card. Tried ExFAT and FAT32, and tried Windows disc manager, panasonic Sd formatter and gpart to format. It's not the file system architecture. Tried 4 sources for the update files. Tried to install 6.0, 5.1 and 4.1 Not the files. I tried to boot after install, on all firmware listed, with all CFW as well. Same boot loop. To fix the loop I have restored a backup made and restored with SXOS and tried my backup made and restored with Hekate. All restore fine. Then I try again and get another loop. I am wondering if it's something in my console so I want to initialize. But I want to be able to restore my User profile without going online.

I think a few months ago I installed the NSP in the FAQ (nx-hbloader with debug svcs enabled)..oops. Also, it may be pertinent to mention I can't get HDD loading to work right on SXOS but I think it's a power issue. I am waiting on a y-cable, that's another issue.

Anyone know how to backup and restore user profiles? Any other ideas to get updated? I might go get a used Octopath to update then return it... I am hoping for something a little easier..

 

[XaneTenshi]

Hello all! Rajkosto San!
Thank you for all your work. I am trying to update with ChoiDuJour and there is some really wrong. I am on 3.0.1 and I really want to update to 5.1 or higher so I can play a few new titles. Every attempt with ChoiDujourNX resulting a being stuck on the Switch logo, I tried getting the update files from several sources. Formatting the SD in ExFat and FAT32. Tried 3 different SD cards. Tried running Choi under SXOS, ReiNX, Atmosphere and of course RajNX. I am out of ideas except initialize the system. Any ideas? Plus if I initialize the system ill lose my User profile. I want my saves to work. Should I go online and download the profile after initialization? will error logs and such still be present after initialization? Also I noticed on your pastebin there is a BackupUser.Js and RestoreUser.JS.. Could there be a solution? Thank you for your help.

Okay, I've lurked long enough, might aswell give my input too, though I don't know if it will really help or not. I've read everything you posted, but forgive me if I end up suggesting something you have already tried, you posted QUITE the detailed (but long) report.

With everything you've tried, it sounds to me like the problem could be with the switch itself, so maybe a system initialize could help. If all you really care about are your saves, your should be able to use a homebrew save manager application, like Checkpoint, to backup your saves and put these back on the system after you have initialized it (I assume you can still boot the switch to HOS as you have a nand backup to circumvent the boot loop you experience after Choi Upgrade).

If your saves are not enough, you might be able to just use the regular ChoiDujour (pc version) to update your switch, though this can be a daunting task: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

As an easier alternative, it might be enough to just mount the user partition with hacdiskmount (see above guide) and copy the user folder to your pc, then unmount, do a regular upgrade with the NX version and choose initialize, and finally mount the switch user partition again and copy paste the user folder. But this is all just a theory, I have no idea if it actually works.

Hope you manage to sort out your problem.

 

[mikefor20]

Okay, I've lurked long enough, might aswell give my input too, though I don't know if it will really help or not. I've read everything you posted, but forgive me if I end up suggesting something you have already tried, you posted QUITE the detailed (but long) report.

With everything you've tried, it sounds to me like the problem could be with the switch itself, so maybe a system initialize could help. If all you really care about are your saves, your should be able to use a homebrew save manager application, like Checkpoint, to backup your saves and put these back on the system after you have initialized it (I assume you can still boot the switch to HOS as you have a nand backup to circumvent the boot loop you experience after Choi Upgrade).

If your saves are not enough, you might be able to just use the regular ChoiDujour (pc version) to update your switch, though this can be a daunting task: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

As an easier alternative, it might be enough to just mount the user partition with hacdiskmount (see above guide) and copy the user folder to your pc, then unmount, do a regular upgrade with the NX version and choose initialize, and finally mount the switch user partition again and copy paste the user folder. But this is all just a theory, I have no idea if it actually works.

Hope you manage to sort out your problem.

Tank you for your constructive reply. I havent used the ChoiPC version. Maybe that's a shot. I am backing up my saves now and I will initialize soon.(fingers crossed) I may go pick us a used octopath traveler, use it to update to 5.1 and then return it but I will initialize first,

Anyone now if initialization, for sure, kills the store error reports and stuff? If It does I could go online and update I suppose. But first wait for 6.2 compatible CFW..



I FIXED IT!! Here's what I did for anyone else.

1. Backup saves with Checkpoint
2. Backup SD
3. Put Kosmos and a fresh Download of 5.1 on my 4 GB SD
4. Boot in to hekate and remove AutoRCM.(I was on 3.0.1 and so were my fuses so meh. Not sure if necessary but I couldn't get in to maintenance mode without disabling AutoRCM for some reason.
5. Boot in to Maintenance mode
6. choose to initialize without deleting saves and profile.(maybe backing up saves was pointless?)
   
7. boot in to hekate--.HBL-->ChoiDuJour->install 5.1

This time it worked. Something in my Switch was fucking it all up. Only thing is IF I had deleted the user profile I think my old error logs go with it... Maybe I will