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

  • Thread starter Thread starter rajkosto
  • Start date Start date
  • Views Views 921,680
  • Replies Replies 1,978
  • Likes Likes 147
You can download with auto-xbins.

Automated way: Use auto-xbins! It will automatically connect to IRC, message our bot, get your login and connect to our ftp. It takes time to do this, so be sure to watch the status window
autobins download file gave back a virus positive
 
Antivirus softwares will do that. However, as long as the source you are getting it from is reputable, it should not be a virus. I downloaded autoxbins and was able to use it without any issues.
Why would it being an ftp client? What could possibly trigger an alarm unless they are doing shady shit that a simple ftp client shouldn't be able to do. I could see toolkits being flagged, but an ftp client?
 
Antivirus softwares will do that. However, as long as the source you are getting it from is reputable, it should not be a virus. I downloaded autoxbins and was able to use it without any issues.
I updated into 4.1(exfat) without trouble. But it gave me a ''error',

Writen preventative hekateipi.ini to microsd
You MUST use the prevent cgupdate launch configuration every boot if you want to prevent GC controller update


This doesnt apply to sxos or my problem , right? Since I updated 4.1 to 4.1 it wont burn fuses or anything?
 
Why would it being an ftp client? What could possibly trigger an alarm unless they are doing shady shit that a simple ftp client shouldn't be able to do. I could see toolkits being flagged, but an ftp client?
Your guess is as good as mine. When I initially downloaded it, Malwarebytes removed it when I tried running the program.
I updated into 4.1(exfat) without trouble. But it gave me a ''error',

Writen preventative hekateipi.ini to microsd
You MUST use the prevent cgupdate launch configuration every boot if you want to prevent GC controller update


This doesnt apply to sxos or my problem , right? Since I updated 4.1 to 4.1 it wont burn fuses or anything?
Yes, you're already on firmware 4.1 so your GC slot is already updated.
 
  • Like
Reactions: Lacius
I updated into 4.1(exfat) without trouble. But it gave me a ''error',

Writen preventative hekateipi.ini to microsd
You MUST use the prevent cgupdate launch configuration every boot if you want to prevent GC controller update


This doesnt apply to sxos or my problem , right? Since I updated 4.1 to 4.1 it wont burn fuses or anything?
You're correct that you don't need to worry about the GC controller update. You already have the 4.0 cartridge update installed, so it's pointless for you.
 
  • Like
Reactions: Draxzelex
Your guess is as good as mine. When I initially downloaded it, Malwarebytes removed it when I tried running the program.
Yes, you're already on firmware 4.1 so your GC slot is already updated.
You're correct that you don't need to worry about the GC controller update. You already have the 4.0 cartridge update installed, so it's pointless for you.

Great so I'm good to go using SXOS right away? Just format microsd into exfat and transfer all the files over?
 
Your guess is as good as mine. When I initially downloaded it, Malwarebytes removed it when I tried running the program.
I'm guessing the fact it is bundled with irc...

https://team-xecuter.com/forums/threads/53694-Auto-Xbins

And the whole point of xbins is so the masses can't find these illegal files as easily as tech minded people otherwise the fuzz will take it down.
Way to go building a tool so Joe Billy Bob can now go and grab this one tool and share it with his friends and sister-wife.

rip xbins.

EDIT: nm it was made like decades ago. I guess Microsoft never cared, now that you can get ninty files though I wonder how soon before Reggie calls swat?
 
Last edited by Mr. Wizard,
  • Like
Reactions: Draxzelex
SX OS does not support ChoiDujourNX I believe. However you can use the SX OS menu option to load into Hekate or load into Hekate directly.
Nono, all that is done as you said the page before. I mean AFTER installation of exfat update, I just need to transfer my old files from fat32 from the new exfat sd card and thats it?
 
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

This part for NOGC is kind of confusing me. I'm on 3.0.1 and want to update to 5.1.0. If I use the TomGer SD files (incl. Hekate 4.0 and ReiNX) is this something I need to worry about, if I leave everything else alone? I mean can I mess up anything by accident?
 
if you were to disable autorcm, would it boot (burn fuses) like you just upgraded normally?
What burns fuses is the bootloader of the Switch, nx-bootloader. AutoRCM bricks the Switch so it can't use its bootloader hence why we use the exploit in RCM to substitute our own, preferably one that doesn't burn fuses. Without AutoRCM, you do still have a chance to save your fuses but so long as you're booting into RCM after the system update. Otherwise by the time you see the Nintendo logo, your fuses are done. And AutoRCM is also removed during all types of system updates; this includes online, cartridge, and exFAT updates.
 
Marvelous tool, I updated from the latest version to 6.0.0. I was impatient sorry, the sx os dongle works only to get us into the menu, hitting boot custom firmware leads to a black screen every time. However, choosing launch external payload and selecting one of your choosing loads perfectly and your lovely nsps and xci run well. A slight hindering from ninty but that’s fine with me.
 
Im experiencing some problems with my switch in playing games (some do not start some do) i have narrowed down that the fault is probably the software on my switch. the switch is on 5.1.0
my question is when updating a firmeware, does the system software get repaired aswell or is it more of an just incrementing stuff and a software fault in the system does get carried over to a newer fw version?

I was thinking in downgrading to 5.0.1 and then updating again to get a clean system software.

Or is getting a rawNand from a other switch console on 5.1.0 and then using my own switchs keys to restore a fresh Nand a better option?
 
Please, enlighten us all with your troubleshooting process and how you came to this conclusion.

Well, I bought a switch which was specified as having a faulty game card reader.
After getting the switch I noticed that cardridges inserted in the switch are recognized and I can start them but 4 out of 5 times the game crashes right away with the following error „the software was closed because of an error“
But 1 out of 5 times the game actually plays. I can’t say if it might crash at a later point in the game.
So to find out if it was really the card readers fault I loaded hekate and made a backup and then loaded ReiNX with some nsp I got from cdnsp
What I found out is that a few games like Celeste,hollowknight and super Mario tennis play just fine without any problems at all
But a bunch of other games has the exact same behavior as with the legit cardridges and they keep crashing at the start with the same error
I tried RajNX afterwards to make sure it is not caused by the cfw but it’s the same behavior.

I don’t know what other hardware could cause this type of effect apart maybe from some memory reading or smth. Especially with it happening with just some certain games. As it happens with physical and digital titles I came to the conclusion that maybe something software related is wrong with the switch
But I’m totally open to new suggestions as I am just a noob trying to make sense of this weird behavior.
 
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)
 

Site & Scene News

Popular threads in this forum