Haku33 - Clean Switch NAND / Restore Stock OS without Backup
This guide will show you how to use Haku33 by Kronos2308 to delete custom firmware files and logs from your Switch console. This is useful if you wish to “clean” your system, return to the stock firmware and play online without being banned. This method will completely erase the information on your Nintendo Switch’s SysNAND (Internal Storage). Backup your saves with EdiZon. SD files or games installed to your SD (on EmuNAND) will not be touched.
If you plan on running SysNAND and EmuNAND concurrently, it is advised to create your EmuNAND partition prior to cleaning your SysNAND. You will require hekate to boot into stock firmware on the SysNAND, this comes with the added benefit of not burning fuses as long as Auto-RCM is enabled. hekate is safe to use with stock firmware, as it is a bootloader and does not store files on your NAND.
If you do not plan to use EmuNAND and wish to use only the stock Nintendo Switch official firmware, disable Auto-RCM in hekate and allow your Switch to boot as normal.
Like with all homebrew that make large changes to your Switch’s internal storage; it is advised to create a backup of your NAND before running Haku33, just to be on the safe side.
Nintendo Switch with Custom Firmware
- The Haku33 requires a hacked switch with CFW such as Atmosphere
- You cannot run homebrew applications with unhacked or stock Switch consoles
- This guide assumes you have all the basic requirements to enter RCM and boot into CFW
- USB Dongle that can be used to boot your Switch into Atmosphere without a PC or USB cable
- RCM Jig Included
- Compatible with emuMMC / Stock OS Dual Boot for safer online play
- Add or Update payloads (.bin files) via USB
- Enter coupon code NOTEGRA for a $5 discount
You will be running Haku33 on your SysNAND so temporarily disable any EmuNAND setups if you are using one. This can easily be achieved by temporarily renaming the
/emuMMC/ folder on the root of your SD.
/switch/folder on your SD card
- Insert your SD card into your Switch and push your preferred payload to boot into CFW
- From the Home screen, launch the Album to access the Homebrew MenuSome CFW setups may require you to hold [R] or [L] to open the Homebrew Menu from the Album
- Launch Haku33 from the Homebrew Menu
- Press the [ZL] + [ZR] + [+] + [-] buttons together to begin
- Wait for your Nintendo Switch to reset (or enter RCM)
Your NAND has now been cleaned. If Auto-RCM was enabled, your Switch will enter RCM and you will require hekate to boot into stock official firmware. If not, you Switch will boot into the initial setup screen
/Nintendo/ folder will be backed up as
/Hamburgesa_Nintendo/ on the root of your SD
Now is the best time to create a clean Switch NAND backup with hekate if you do not have one.
Booting into Stock Official Firmware from RCM with hekate
- Insert your SD card into your PC
- Copy the
/bootloader/folder from the hekate
.zipfile to the root of your SD card
- Extract the Atmosphere
.zipfile and copy
/bootloader/payloads/folder on your SD card
- Go to the
/bootloader/folder on your SD card
hekate_ipl.iniin Notepad and add the following lines to the file and save
[Stock (SYSNAND)] fss0=bootloader/payloads/fusee-secondary.bin stock=1 emummc_force_disable=1 icon=bootloader/res/icon_switch.bmp
- Insert your SD card into your Switch and push the
- Select [Launch]
- Select [Stock (SYSNAND)] to boot into stock official firmware
- Your Switch will boot and load into the initial setup screen
You can now sign in to your Nintendo Account or create a new one to access the eShop.
You can also update your SysNAND firmware via Nintendo servers, EmuNAND firmware will be unaffected.
/eMMC/folder if you wish to boot into EmuNAND, DO NOT inject your CFW payload without ensuring that the EmuNAND is enabled. This could lead to unintentionally getting your SysNAND banned.
Congratulations on successfully cleaning your Switch NAND and restoring the official firmware. You can now enjoy the online services while still having access to custom firmware via the EmuNAND if you wish to do so. Ensure that you keep the SysNAND environment clean and create a fresh NAND backup now if you haven’t already.