Table of Contents
How to set up CFW and emuMMC for an unpatched Switch (Erista)
This page is for setting up CFW for an unpatched Switch console which uses the RCM exploit to inject payloads to start CFW. And creating an emuMMC with Nintendo connections blocked.
Afterwards you will have a good setup to keep using sysMMC as before, for eShop and playing online. While the separate emuMMC can be used when needing to install homebrew games, forwarders and game backups you've dumped.
Notes
≣ No SD reader needed (click to expand)
- Windows: With an unpatched Switch and Windows you can use the a Switch as a card reader. All you need is TegraRCMgui and the Switch in RCM, see instructions here.
- Hekate: As soon as you have Hekate working you can use Hekate's USB Tools to make the Switch function like a micro SD card reader. And easily connect the Switch to your PC or phone to transfer files.
- These are safer alternatives to taking the micro SD card out and putting it back. (The SD card reader is known to break with little use.)
≣ Disable cloud saves and automated backups (click to expand)
- If you don't have NSO or never enabled cloud saves, it's disabled.
- How to:
- Open
(System Settings) ➔ Data Management ➔ Save Data Cloud ➔ Settings and disable Automatically Back Up Save Data and Automatically Download Save Data
- Open
- This can be turned back on again on sysMMC after creating emuMMC.
- Partition or file emuMMC: You can read here about the benefits of both, so that you may later decide on which emuMMC type to pick.
- If unsure choose partition, it is the better option.
- Auto RCM: This guide will have you enable
AutoRCMby default. Once you've used Hekate to enable it, the console will always go into RCM when turned on. Making the "jig" not needed unlessAutoRCMis removed/disabled. - Never exFAT with Switch: Once you have completed setting up your device, ensure that you never format your SD card to exFAT. exFAT users are much more likely to experience SD card corruption than FAT32 users. This is a Switch, HOS specific issue.
- Mac/Linux users: If using a Mac remember to always use Hekate's "Fix Archive Bit" tool after copying files to your micro SD card. Mac often does a minor bit change to files/folders causing issues for the Switch and those files/folders will not show.
- From Hekate's main menu press:
Tools ➔ Arch bit • RCM • Touch • Pkg1/2 ➔
Fix Archive Bit
- From Hekate's main menu press:
Step 0 - Getting ready
Checklist
- Unpatched Switch (Unpatched Erista model)
- a PC and a USB-C cable (or an alternative way to inject payloads and getting files onto the micro SD card)
- A micro SD card reader or TegraRCMgui and your Switch, see notes
- 64 GB Micro SD card, or larger.
- 30 GB free space on your micro SD card
- Cloud saves disabled, see notes
- CFW files
CFW files you need
Everything you need to download. (On GitHub scroll down and find the file under Assets)
- TegraRcmGUI (Windows) - Download TegraRcmGUI_v*.*_Installer.msi
- or use a different payload injector (Mac, Android, dedicated device + )
- Hekate - Download hekate_ctcaer_*.*.*_Nyx_*.*.*.zip from the latest release.
- Atmosphère - Download atmosphere-*.*.*-master-*********+hbl-*.*.*+hbmenu-*.*.*.zip from the latest release
- SigPatches - Download patch-*.*.*-**.*.zip (alternative download)
- Updated for Atmosphère 1.11.2 (5388824be) & OFW 22.5.x
- All previous versions' patches are included
Step 1 - SD backup
- Backup of all files from your micro SD to a PC (if it was used for the same Switch)
- If you're using Windows you can use the Switch to browse the SD card contents via USB, using TegraRCMgui (recommended)
- When backup is complete delete all files on your micro SD card
Step 2 - CFW files to micro SD
Extract the following to the root of your micro SD card:
bootloaderfolder from thehekate_ctcaer_*.*.*_Nyx_*.*.*.zipatmosphere-*.*.*-xxxxxx-*********+hbl-*.*.*+hbmenu-*.*.*.zippatch-x.x.x-xx.x.zip
Step 3 - Hekate launch options
- This configuration gives you 2 launch options:
CFW emuMMC - Atmosphere- for emuMMC that loads patches and blanks prodinfo.Stock- for sysMMC without Atmosphère.
- If you want to use Atmosphère on both sysMMC and emuMMC, you'll need an additional launch option for that.
- It also sets a Hekate setting to make Hekate the reboot payload. Meaning you'll restart to Hekate when you use Restart from the power menu. (Hold the power button for 3 seconds, then choose Power Options and select Restart)
-
Create a file named
hekate_ipl.iniinside of your/bootloader/folder -
Copy (You can use the clipboard button top right 📋) and paste this within the file:
[config] autoboot=0 autoboot_list=0 bootwait=3 backlight=100 autohosoff=0 autonogc=1 updater2p=1 bootprotect=0 [CFW emuMMC - Atmosphere] pkg3=atmosphere/package3 emummcforce=1 cal0blank=1 kip1patch=nosigchk icon=bootloader/res/icon_payload.bmp [Stock] pkg3=atmosphere/package3 stock=1 emummc_force_disable=1 icon=bootloader/res/icon_switch.bmp
Step 4 - Blocking Nintendo | Avoiding a console ban
≣ Notes about serial blanking and blocking connections: (click to expand)
📝 Both blanking the console's identifying serial information and blocking connections will be used
- Atmosphère can blank serial info. This is enough to avoid a ban but using only this will cause a crash from version 1.7.0 of Atmosphère. We set this setting with both the
cal0blank=1line in the launch option, and also by having thisexosphere.iniwith the lineblank_prodinfo_emummc=1.- Having both is redundant but not harmful, and makes user error less likely.
- Having both is redundant but not harmful, and makes user error less likely.
- Atmosphère can block specified connections via it's built in DNS.mitm feature using a hosts file. This is the emummc.txt we'll add in this step.
- Using the setup in this guide, Nintendo will only blocked while using emuMMC.
4.1 Blocking Nintendo connections
-
Create a file named
emummc.txtin/atmosphere/hosts/(thehostsfolder won't exist, so make sure to create it) -
And copy and paste this in your
emummc.txtfile: (You can use the clipboard button top right 📋)# Block Nintendo Servers 127.0.0.1 *nintendo.* 127.0.0.1 *nintendo-europe.com 127.0.0.1 *nintendoswitch.* 157.230.80.146 *conntest.nintendowifi.net 157.230.80.146 *ctest.cdn.nintendo.net
4.2 Blanking serial info
-
Create the file
exosphere.iniin the root of your SD card -
Copy and paste this in your
exosphere.inifile: (You can use the clipboard button top right 📋 )[exosphere] debugmode=1 debugmode_user=0 disable_user_exception_handlers=0 enable_user_pmu_access=0 blank_prodinfo_sysmmc=0 blank_prodinfo_emummc=1 allow_writing_to_cal_sysmmc=0 log_port=0 log_baud_rate=115200 log_inverted=0
Step 5 - Injecting payload
- Create a folder named
Hekateon your desktop (or name it whatever you want and place it where you want payloads) and extracthekate_ctcaer_x.x.x.binfromhekate_ctcaer_x.x.x_Nyx_x.x.x.zipinto it. (where the x.x.x will be the version number)- This is the payload .bin file you'll use to start Hekate.
- Place your SD card back into your switch
- Enter RCM: Insert your RCM jig in the right side of your rail, hold volume up (
) button and press the power button (
).
- Once the Switch is in RCM the jig can be removed.
- If you've used Hekate previously and enabled "Auto RCM" you simply press the power button (
).
- Instead of the Switch turning on normally you get just a black screen, this is RCM. You are ready to inject a payload with one of these methods:
≣ Alternative A) Using a Windows PC: (click to expand)
- On your pc run
TegraRcmGUI_vx.x_Installer.msi. - Once installed, launch TegraRcmGUI. Once TegraRcmGUI is running, go to the Settings tab and click on Install Driver.
- Once the driver is installed, back to the
Payloadtab. - Press the folder icon, and navigate to the folder named
Hekatethat you created and pick the file namedhekate_ctcaer_x.x.x.bin. - Connect your Switch to your PC, press Inject payload, and you'll launch into Hekate.
- Make sure TegraRcmGUI is running, and injected the payload successfully.
- (If you get
Smashed the stack with a 0x0000 bytein TegraRcmGUI, then your switch is patched)
- (If you get
- Make sure TegraRcmGUI is running, and injected the payload successfully.
- Once Hekate has started on the Switch continue to Step 6 - Creating emuMMC and finish
≣ Alternative B) A payload launcher or other alternative: (click to expand)
- If you're not injecting payloads from a Windows PC see the How to launch a payload page, for alternatives to TegraRcmGUI.
- You will still use Hekate's payload file named hekate_ctcaer_x.x.x.bin.
- Once you've injected Hekate successfully continue to Step 6 - Creating emuMMC and finish
Step 6 - Creating emuMMC and finish
Pick which emuMMC type you want to use. emuMMC partition (recommended), or emuMMC file.
Follow either alternative A or B:
≣ Alternative A) Partition-based emuMMC (recommended) and final instructions: (click to expand)
- Select the Tools tab, then select Partition SD Card, and finally press Ok.
- Move the emuMMC (RAW) slider until it says
29 full, then press Next Step and finally press Start. - Once the operation is done, press Close and then select the Home tab.
- Select emuMMC in the main menu, then select Create emuMMC
- Select SD Partition and then select Part 1.
- Wait for your emuMMC to get created. Once its done, select Close and again Close.
- Select Tools then select Arch bit • RCM • Touch • Pkg1/2 and pick AutoRCM then Close when it's set after a second.
- Move back any previously deleted files into your SD card:
- Connect the Switch to your PC and enable "USB Mass Storage in Tools" (see guide page) and move back any previously deleted files. Eject Switch safely and select Close ➔ Close ➔ Home in Hekate to get back to the main menu.
- IF you instead turn your device off by pressing Power off ➔ Power off, and use the card reader you used earlier to move files back into your SD card. You'll have to inject payload again after you've placed your SD card back into your Switch.
- Once you're in Hekate, click on launch, and select emuMMC - Atmosphere CFW to launch emuMMC with Atmosphère.
- If you need to go into sysMMC without your CFW, select Launch and then select Stock
- If you want to use Atmosphère with both sysMMC and emuMMC, add an additional launch option to hekate_ipl.ini. See this section.
- You did it! You finished cfw and emuMMC setup.
-
Make a complete sysMMC backup if you haven't already.
-
Suggestion: After starting emuMMC for the first time, change system theme to white (or black) so it's different from sysMMC, and you'll have a simple visual to differentiate sysMMC from emuMMC.
≣ Alternative B) File-based emuMMC and final instructions: (click to expand)
- Select the Tools tab, then select Partition SD Card, and finally press Ok.
- Press Next Step and finally press Start.
- Once the operation is done, press Close and then select the Home tab.
- Select emuMMC in the main menu, then select Create emuMMC. Select SD File
- Wait for your emuMMC to get created. Once its done, select Close and again Close.
- Select Tools then select Arch bit • RCM • Touch • Pkg1/2 and pick AutoRCM then Close when it's set after a second.
- Move back any previously deleted files into your SD card:
- Connect the Switch to your PC and enable "USB Mass Storage in Tools" (see guide page) and move back any previously deleted files. Eject Switch safely and select Close ➔ Close ➔ Home in Hekate to get back to the main menu.
- IF you instead turn your device off by pressing Power off ➔ Power off, and use the card reader you used earlier to move files back into your SD card. You'll have to inject payload again after you've placed your SD card back into your Switch.
- Connect the Switch to your PC and enable "USB Mass Storage in Tools" (see guide page) and move back any previously deleted files. Eject Switch safely and select Close ➔ Close ➔ Home in Hekate to get back to the main menu.
- Once you're in Hekate, click on launch, and select emuMMC - Atmosphere CFW to launch emuMMC with Atmosphère.
- If you need to go into sysMMC without your CFW, select Launch and then select Stock
- If you want to use Atmosphère with both sysMMC and emuMMC, add an additional launch option to hekate_ipl.ini. See this section.
- You did it! You finished cfw and emuMMC setup.
-
Make a complete sysMMC backup if you haven't already.
-
Suggestion: After starting emuMMC for the first time, change system theme to white (or black) so it's different from sysMMC, and you'll have a simple visual to differentiate sysMMC from emuMMC.
SHISE Guide pages
Getting Started ↧⤒
Getting started with CFW:
᛫ Is my Switch hackable?
᛫ Avoid getting banned
᛫ Launching payloads
᛫ Create/Restore a NAND backup
᛫ Dumping device keys
᛫ Terminology (Switch/Homebrew)
CFW setup & migration ↧⤒
Unpatched Switch setup:
᛫ Set up Atmosphère with emuMMC for an unpatched Switch
᛫ Set up Atmosphère for an unpatched Switch
Modchipped Switch setup:
᛫ Set up Atmosphère with emuMMC for a modchipped Switch
᛫ Set up Atmosphère for a modchipped Switch
Migrate setup from old micro SD or CFW:
᛫ Migrate your emuMMC to a new SD card
᛫ Cleanup (or Migrate from Atmosphère 0.x to 1.+)
᛫ Migrate from SXOS to Atmosphère
Updating CFW, FW + ↧⤒
Updating CFW / FW:
᛫ Update your CFW
᛫ Dump your Switch firmware
᛫ Upgrade Switch firmware, offline
Migrate setup from old micro SD or CFW:
᛫ Migrate your emuMMC to a new SD card
᛫ Cleanup (or Migrate from Atmosphère 0.x to 1.+)
᛫ Migrate from SXOS to Atmosphère
Modchip firmware:
᛫ Update Picofly chip firmware
᛫ Flash Spacecraft-NX (HWFLY-NX) to SX Core / Lite
᛫ Update Spacecraft-NX (HWFLY-NX) chip firmware
Homebrew & misc. ↧⤒
Homebrew:
᛫ Tesla overlay menu
᛫ Emulating Amiibos
᛫ Guide for installing themes (HOS themes)
᛫ Manage system modules
᛫ Manage Cheats
PC related use:
᛫ How create or restore a full system backup
᛫ Backup or restore your Switch save files
᛫ Dumping Titles
᛫ Installing dumped titles - USB Installations
᛫ Browse SD Card Contents Via USB
᛫ Verifying Dumps
Additional guides and information:
᛫ What are bans / Avoiding bans
᛫ Exosphere / DNS.mitm Setup (blocking Nintendo)
᛫ Incognito Setup (deprecated)
᛫ Enable Gamecard Reader
᛫ Launching payloads
᛫ How to dump device keys
᛫ Format SD Card To FAT32
᛫ Atmosphère CFW on Both sysMMC and emuMMC options