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

  • Thread starter Thread starter rajkosto
  • Start date Start date
  • Views Views 917,786
  • Replies Replies 1,978
  • Likes Likes 147
if not needing to prevent GC controller updates, boot stock with hekate, not whatever freaky profile you might have.
 
Seem to be having some issues with SX OS -- I suppose this is to be expected since you don't launch the Homebrew menu the same way.. Works perfectly with Hekate though!
 
Very important question, but first this is my situation;

In a week I will be taking a trip to Europe. I bought myself a couple new Switch games to play, except they both require higher firmwares and I'm still on 4.1.0.

I would like to finally mod out my switch and apply this firmware update, BUT....does this in any way risk my console from getting banned if I decide to play Rocket League online or something. I mean I'm going to assume I'll be fine because all I want to do is mod for firmware and that's it, but I figured I'd ask just in case.

I actually don't mind updating, but if I can avoid burning fuses I will. I just want to make sure everything works right.
 
Very very nice work! Just a small question. If I use this to update, it already installs autoRCM after that? In essence I want to know if I just need to short the pins to start the installers and if I don't need a jig afterwards to make sure I don't burn the fuses.
 
@rajkosto

I'm trying to load the application on firmware 1.0.0, it tries to start but closes immediately.
I'm using SDFiles v6 with these options added to hekate_ipl.ini:

debugmode=1
fullsvcperm=1

Tried with sigpatchpayload.bin (from SDFiles arhive), hekate 3.2.
Also updated hbloader as per FAQ.

Do you have any idea ?

Thanks.
 
@rajkosto Could you please provide some detail on the autoRCM implementation used in your tool (which looks AWESOME BTW). I want to understand how it works. Does it cause the boot process to fail? Or does it force the boot process to load a particular binary on the SD card. I presume if it forces load of a particular binary it has a fixed filename.

I'm simply trying to understand the options for launching Hekate vs ReiNX, swapping them etc. after using this for an update.

Thanks for the help.
 
@rajkosto Could you please provide some detail on the autoRCM implementation used in your tool (which looks AWESOME BTW). I want to understand how it works. Does it cause the boot process to fail? Or does it force the boot process to load a particular binary on the SD card. I presume if it forces load of a particular binary it has a fixed filename.

I'm simply trying to understand the options for launching Hekate vs ReiNX, swapping them etc. after using this for an update.

Thanks for the help.
AutoRCM subtly corrupts the BOOT0/1 partitions, forcing the Switch to enter RCM on each coldboot. That's all it does.

By forcing the Switch to enter RCM on each coldboot, it can't have the chance to boot normally and burn your efuses. It will always enter RCM, whereupon you will load Hekate, ReiNX, etc. in order to boot the OS without burning efuses.
 
  • Like
Reactions: gallymimu
@rajkosto

Found the problem. I was thinking that

debugmode=1
fullsvcperm=1

are global options, and they aren't, they are entry options. Changed the options and the application starts.

P.S. Nice application GUI.
 
Really not a fan of AutoRCM as it modify the NAND.
I've got a SX Pro right now, and I prefer the classic method 'Jig and dongle' every boot.
AutoRCM can't be disabled ?
 
So, if I used this on my 5.1.0 Switch that I got on day 1, I could downgrade to 1.0.0, even if I've previously burned fuses?
 

Site & Scene News

Popular threads in this forum