FAQ

If you have any questions about ReiNX, CFW, or hacking your Switch in general, please go through and see if your question is here before asking for further assistance in the Discord. Chances are you might answer your question just reading through.

This FAQ will be updated as new questions are asked over time.

ReiNX Specific Questions

Why should I use ReiNX over other CFW alternatives?

We consider ReiNX to be the most end-user friendly CFW in terms of ease of use and the features it provides enabling the user to do what they want with their Switch with a no-judgement approach on our end.

  • We believe ReiNX is the easiest CFW to setup and go. No configuration needed, and everything is baked in and ready to go.
  • The ReiNX Toolkit allows for users to easily update ReiNX, change splashscreens, create NAND backups, manage sysmodules, etc.
  • Sigpatches are baked into ReiNX itself, so no need to ever worry about them.
    • We also regard them as the best currently offered because of their flexibility and compatibility.
  • Preliminary SX OS compatibility implemented so you can run ROMMENU without any issues.
    • More functionality is planned such as native cheats, XCI loading and more!

All while having full compatibility with homebrew that the community creates!


Will ReiNX have emuNAND?

This functionality is being discussed internally, but we cannot currently confirm or deny its inclusion in the future at this time.


Will ReiNX be able to load .xci games, or have USB HDD support?

With the preliminary implementation of SX OS compatibility, XCI loading and USB HDD is certainly being discussed internally. However as we personally do not find .xci loaders or being tethered to an external hard drive as particularly useful or practical we cannot confirm or deny its inclusion just yet.


If I am switching from another CFW that primarily uses .xci loading, will I lose my saves?

Nope! Saves are tied to the TitleID of a specific game, and the TitleID is the same for eShop titles and game carts for the majority of the Switch library meaning saves will carry across to both methods. There are very few games that do not follow this rule however (such as Binding of Isaac), but you can easily backup and restore your saves using Checkpoint or any other save data manager of your choosing.


Does ReiNX include creport/fatal?

Yes - ReiNX comes with a custom 'creport' that disables all error reporting / error dumping. However creport is not something that we believe will help in keeping your console safe from bans. Unlike what you may have heard, this does not prevent bans as Nintendo looks at more than just error reports when a console is going online.

We also have a custom 'fatal' screen for fatal errors and reboot to payload functionality.

If you are an advanced user that would like to easily access error logs and would like to use Atmosphere's custom creport instead, you can simply copy over the 0100000000000036 folder to your ReiNX/titles/ folder.


How do I install patches?

Place any patches (.rxp files) into the ReiNX/patches folder on your SD card.


I am a total fan of this CFW and would love to donate!

Aww, thanks!! If you would like to donate to this project, you can check out our Patreon here, in the footer or at the menu above.

Hacking Related Questions

What is a CFW?

CFW is short for Custom Firmware. This is what allows us to run our own unsigned code on the console from outside sources without Nintendo's explicit permission.


Is hacking your Switch dangerous?

In short, not usually.

While the process is incredibly easy and relatively harmless, we cannot say that it is without error. You are making modifications to the Switch that were never intended by Nintendo. So while it is incredibly rare for something to go wrong, it is important to still keep this in mind. As long as you run code from trusted sources, you should almost never run into issues. Be sure to never run anything from an untrusted source under any circumstances!

It is also important to create a NAND backup for exactly this reason, which you can learn how to do on the Step 3 - Post-Installation page.


Will I be banned?

Yes.

Nintendo has stepped up their security game considerably and are able to detect a hacked Switch quite easily, especially if you are not careful. If you go online with a hacked console, your console will very likely be automatically flagged by Nintendo and you will be queued up for an upcoming banwave in the coming months. Hacking online will also very likely get you banned pretty quickly, usually in the realm of days or weeks.

For more information on bans, please refer to Draxzelex's ban thread on GBAtemp.


What is AutoRCM, and should I use it?

AutoRCM is a clever method used to force the Switch to always enter into RCM Mode without the user needing to intervene eg. using a Joycon rail jig, or other methods of shorting select pins. It effectively 'bricks' your system by modifying the Boot0 system partition in just a way that it is easily reversible, but also so that the system panics and spits you out to RCM since it cannot boot.

You can learn more about it on the Step 3 - Post-Installation page.


You mentioned 'burning fuses' a few times, what does that mean?

The Switch comes with a hardware based anti-downgrade mechanism in the form of eFuses that are permanently 'blown' when updated to a new firmware. This will prevent the Switch from booting if it notices more fuses are burnt than expected, eg. if you attempt to run an old firmware after officially upgrading to a newer firmware. These are microscopic fuses on the SoC (System-on-Chip) that are non-user replaceable. Once they are burnt, it is impossible to restore them.

Please see below for a handy graphic regarding fuse count and booting, along with further documentation. Users can however safely ignore fuses as CFW completely ignores them.

 

OFW Fuse Behavior

Fuse Count < Expected Fuses - Boot and Burn
Fuse Count = Expected Fuses - Boot
Fuse Count > Expected Fuses - Does not Boot

CFW Fuse Behaviour

Fuse Count < Expected Fuses - Boot
Fuse Count = Expected Fuses - Boot
Fuse Count > Expected Fuses - Boot

 

To learn more about eFuses (including an actual image of one), we recommend checking out this article by the EE Times.

CFW Related Questions

Should I backup my NAND?

Absolutely! We highly recommend you backup your NAND just in case something happens. You can learn how to on the Step 3 - Post-Installation page.


Should I upgrade to the latest firmware?

Usually it is safe to do so, however please refer to the News section on the homepage on any updates regarding new firmware compatibility with ReiNX before proceeding.


What is warmboot?

Warmboot is a part of the bootloader that runs when you wake up from sleep mode. The term warmboot can also refer to a warmboot exploit that could allow you to run any code you want when waking up from sleep mode. Such an exploit can allow iPatched switch units to eventually run custom firmware.

Warmboot sigchecks have to be patched out for sleep mode to work when you're running a lower version than your fuses would indicate (a downgraded firmware). The latest version of ReiNX does this automatically so you don't have to do anything.


What are sigpatches?

Sigpatches is shorthand for Signature Patches. This is what allows you to run unsigned applications and games that are installed directly on your Switch without the Switch caring who made it, or where it came from.


What are sysmodules (.kip)?

Sysmodules are the modular portion of ReiNX that allow for extra features not found in the original release such as enabling system-wide FTP, or Discord rich presence. They come in .kip format, and can be found in the /ReiNX/sysmodules/ folder.

For more information, please refer to the Recommended Homebrew section of the Step 3 - Post-Installation page.


What is LayeredFS (fs_mitm.kip)?

LayeredFS is short for Layered Filesystem, and fs_mitm is short for Filesystem Man in the Middle. This sysmodule handles romfs and allows for files on the NAND to be dynamically patched to anything the user wants. Some examples would be game mods, home menu (qlaunch) themes, etc. Dynamic patching allows for the user to make changes to the system, without actually dangerously modifying the NAND itself.

The patches are loaded off of the SD card and can be found in the /ReiNX/titles/ folder.


I've heard reports of SD card corruption?

The exFAT filesystem is currently prone to corruption on the Nintendo Switch because of Nintendo's poor implementation of the driver. This affects all CFWs, not just ReiNX users. Unfortunately there is no current fix for the issue, so we recommend users use FAT32 instead.

You can find more information on the pros and cons of both filesystems on the Step 1 - Requirements page.

ReiNX Common Misconceptions

As rumors and misinformation from bad actors spread, it can be tough to identify what the truth is. We are hoping that we can help lessen this issue by addressing some common misconceptions about ReiNX in particular.


Is ReiNX just a clone of Atmosphere?

It is not. From the perspective of an end user both CFWs may appear very similar on the surface as both CFWs can be categorized as dynamic patching systems to modify Horizon OS (Switch OS) in similar ways. ReiNX distances itself from Atmosphere in particular when it comes to custom feature-set and the technical functionality under the hood such as how ReiNX uses membased patching versus Atmosphere's address based patching.

Where the misconception likely stems from is that ReiNX utilizes drivers (hwinit) written by Naehrwert, and we also bundle optional custom kernel extensions (sysmodules) based on Atmosphere's kernel extensions. As of ReiNX v2.1, we also bundle Exosphere and lp0fw for 7.0.0 and up compatibility.

If you would like to confirm this yourself, ReiNX is open-source and available for audit by anyone on our GitHub page.


Did ReiNX steal sigpatches from SX OS?

ReiNX did not, and in no way were the sigpatches derived from SX OS. ReiNX implemented its own original sigpatches created by Rei (ES patches) and the ReiSwitched community (FS patches) before Team Xecuter bundled their own sigpatches with SX OS.