rewrote parts of the updating guide, rewrote/retouched majority of the sdtransfer guide, updated links on tesla menu/nx-shell pages, rewrotesome info on partitioning pages in main guide

DefenderOfHyrule · DefenderOfHyrule · commit 1f5074b27ae9 · 2026-02-08T17:31:10.000+01:00
diff --git a/docs/extras/transfer_sd.md b/docs/extras/transfer_sd.md
@@ -4,7 +4,7 @@ The goal of this page is to transfer the contents from one microSD card to anoth
 
 We will be using [hekate](https://github.com/CTCaer/hekate/releases/) to both backup and restore the emuMMC, so make sure that you have its latest files on your microSD card already.
 
-## Instructions:
+### Checking whether you have a Partition or File based emuMMC:
 
 You should first check whether you have a file or partition based emuMMC:
 
@@ -13,25 +13,15 @@ You should first check whether you have a file or partition based emuMMC:
 1.  Tap on the `emuMMC` button.
 1.  Under `emuMMC Info & Selection`, check the text next to `Type`.
     - If you have one it should be either `SD Raw Partition` or `SD File`.
+    - If you have no emuMMC, it'll be disabled.
+    
+#### Depending on if you're using a Partition based emuMMC or File based emuMMC/no emuMMC at all, click the corresponding tab below:
 
------
-
-### If you are using a file based emuMMC or are using no emuMMC at all:
-
-1. Enter RCM and inject the hekate payload.
-    - If you use a modchipped Switch, you can simply just turn your Switch on with the hekate payload renamed to `payload.bin` on the root of your microSD card.
-1. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
-1. Copy the contents of your microSD card somewhere to your PC.
-1. Access your new microSD card via a microSD card reader or similar.
-1. Format your new microSD card to FAT32 if it isn’t already.
-    - To do this, use [this guide](https://wiki.hacks.guide/wiki/Formatting_an_SD_card).
-1. Copy the files from your PC or directly from your old microSD card to your new microSD card.
-1. Eject the `UMS` device safely from within your computer's operating system.
-1. Boot into hekate and launch your desired boot entry.
+<br>
 
------
+::::: tabs 
 
-### If you are using a partition based emuMMC:
+:::: tab default Partition based emuMMC
 
 ::: warning
 
@@ -41,22 +31,75 @@ You need at least 30GB (or 60GB if using an OLED Switch) of free space to be abl
 
 :::
 
-1. Enter RCM and inject the hekate payload.
-    - If you use a modchipped Switch, you can simply just turn your Switch on with the hekate payload renamed to `payload.bin` on the root of your SD.
-1.  In the main menu, tap on `Tools`, then `Backup eMMC` and set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
+#### What you need:
+
+- The latest version of [hekate](https://github.com/CTCaer/Hekate/releases/) (`hekate_ctcaer_(version).zip`).
+
+#### On your OLD microSD card:
+
+1.  Enter RCM and inject the hekate payload.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the hekate payload renamed to `payload.bin` on the root of your microSD card.
+1.  From hekate's `Home` menu, navigate to `Tools` > `Backup eMMC`, set `SD EmuMMC Raw Partition` at the bottom of your screen to `ON`.
 1.  Backup both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
 1.  Once both are done, go back to the main menu, navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
 1.  If Windows asks you to format a drive, discard it and open the accessible drive containing the contents of your microSD card.
 1.  Copy the contents of your old microSD card somewhere to your PC.
-1.  Follow the `Preparing hekate` section at the bottom of [this page](../user_guide/rcm/sending_payload) (Unpatched Switch users only) to prepare your new SD card with hekate's files.
-    - If you have a modchipped Switch, follow [this page](../user_guide/modchip/preparing_hekate) instead.
-1.  Follow only steps 1-3 on [this page](../user_guide/all/partitioning_sd) to partition the new microSD card for an emuMMC setup.
-1.  After it’s done, boot into hekate and navigate to `Tools` > `USB Tools` > `SD Card`, then plug your Switch into your PC via USB.
-1.  Copy the backup you made of your old microSD card on your PC to your new microSD card.
-1. Navigate to `/backup/<some characters>/emummc` on your microSD card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to `/backup/<some characters>/restore/emummc`.
-1. Eject the `UMS` device safely from within your computer's operating system.
-1. Tap on `Tools`, `Restore eMMC`, set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
-1. Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
-    - It is very important that for both of these the `SD emuMMC Raw Partition` option is enabled, otherwise you will be altering your sysMMC
+
+-----
+
+#### On your NEW microSD card:
+
+1.  Copy the *contents* of the previously downloaded hekate `.zip` to the root of your new microSD card.
+1.  Enter RCM and inject the hekate payload.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the hekate payload renamed to `payload.bin` on the root of your microSD card.
+1.  Navigate to `Tools` > `Partition SD card` once in hekate/Nyx.
+1.  Set the `emuMMC (RAW)` slider to `29 FULL` in the middle of the bar.
+    - Set the `emuMMC (RAW)` slider to `58 FULL` if you're on an OLED Switch.
+    - If you wish to install Android and/or Linux later, partition your microSD card here accordingly by moving the sliders you see during this step. We recommend setting the `Android (USER)` and `Linux (EXT4)` sliders to at least 16GB.
+1.  Navigate to `Next Step` at the bottom right, then select `Start` in the menu that appears.
+    - For Android; Select `Dynamic` partitioning for Android 13+ and `Legacy` partitioning for Android 10/11. Note that Android 10/11 are no longer supported, Legacy and Dynamic partitioning are also **NOT** intercompatible.
+1.  After it’s done, return to hekate's `Home` menu and navigate to `Tools` > `USB Tools` > `SD Card`, then plug your Switch into your PC via USB.
+1.  Copy the backup you made of your old microSD card on your PC to your new microSD card, replacing files if/when prompted.
+1.  Navigate to `/backup/<some characters>/emummc` on your new microSD card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to `/backup/<some characters>/restore/emummc`.
+1.  Eject the `UMS` device safely from within your computer's operating system.
+1.  From hekate's `Home` menu, navigate to `Tools` > `Restore eMMC`, set `SD EmuMMC Raw Partition` at the bottom of your screen to `ON`.
+1.  Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
+    - It's important that for both of these options the `SD emuMMC Raw Partition` option is enabled, otherwise you could be altering your sysMMC
       which is not what you want.
-1. Your emuMMC is now restored on the new microSD card and you should be able to launch it from `Launch` -> `Atmosphere PKG3 emuMMC` in hekate.
+1.  Your emuMMC is now restored on the new microSD card and you should be able to launch it from `Launch` -> `Atmosphere PKG3 emuMMC` in hekate.
+
+::::
+
+:::: tab File based emuMMC/no emuMMC at all
+
+#### What you need:
+
+- The latest version of [hekate](https://github.com/CTCaer/Hekate/releases/) (`hekate_ctcaer_(version).zip`).
+
+#### On your OLD microSD card:
+
+1. Enter RCM and inject the hekate payload.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the hekate payload renamed to `payload.bin` on the root of your microSD card.
+1. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
+1. Copy the contents of your microSD card somewhere to your PC.
+
+-----
+
+#### On your NEW microSD card:
+
+1.  Copy the *contents* of the previously downloaded hekate `.zip` to the root of your new microSD card.
+1.  Enter RCM and inject the hekate payload.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the hekate payload renamed to `payload.bin` on the root of your microSD card.
+1. Format your new microSD card to FAT32 using hekate. To do so, navigate to `Tools` > `Partition SD card` once in hekate/Nyx.
+1.  Leave all sliders on their default values.
+    - If you wish to install Android and/or Linux later, partition your microSD card here accordingly by moving the sliders you see during this step. We recommend setting the `Android (USER)` and `Linux (EXT4)` sliders to at least 16GB.
+1.  Navigate to `Next Step` at the bottom right, then select `Start` in the menu that appears.
+    - For Android; Select `Dynamic` partitioning for Android 13+ and `Legacy` partitioning for Android 10/11. Note that Android 10/11 are no longer supported, Legacy and Dynamic partitioning are also **NOT** intercompatible.
+1.  Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
+1. Copy the backup you made of your old microSD card from your PC (or directly from your old microSD card) to your new microSD card.
+1. Eject the `UMS` device safely from within your computer's operating system.
+1.  You've successfully followed this guide and your emuMMC is now accessible from `Launch` -> `Atmosphere PKG3 emuMMC` in hekate.
+
+::::
+
+:::::
diff --git a/docs/extras/updating.md b/docs/extras/updating.md
@@ -40,9 +40,42 @@ When a new version of hekate releases, you can update by following these steps:
 
 Always check _before_ updating your system firmware if the latest version of Atmosphère _as well_ as the latest version of hekate support the firmware version you are updating towards.
 
+### Updating your sysMMC's firmware
+
+-   Before continuing with this guide, make sure your sysMMC is up to date. If your sysMMC is not up-to-date, do the following depending on whether your Switch is modchipped or not:
+
+    :::::: danger
+    #### **Note regarding updating towards major firmware versions** 
+    
+    Updating your Switch firmware should be done via OFW or Stock on modchipped consoles when updating towards a major firmware version. The term "major" in Switch firmware version means that the first number in the firmware version number has changed. An example of a major firmware version update would be updating from `20.5.0` to `21.0.0`, the first number is the major firmware version number. You may also want to do the same thing for minor firmware versions (for example, updating from `21.1.0` to `21.2.0`).
+    
+    The reason why updating via OFW/Stock is recommended on modchipped consoles is because it ensures that you properly burn your e-fuses and preserve the ability to boot OFW afterwards (in the situations where Atmosphere and/or hekate haven't been updated to support the firmware version you've updated to). In rare instances, it also prevents issues that *can* occur when updating via sysCFW (incomplete firmware updates, improperly updated BOOT0/BOOT1 partitions, etc).
+    
+    #### Click one of the tabs below depending on your situation:
+    
+    </br>
+    
+    ::::: tabs
+    
+    :::: tab default Modchipped-console users
+    - **Modchipped-console users:** Boot hekate/Nyx, navigate to `Reboot` > `OFW` from hekate's `Home` menu and then update through `System Settings` > `System` > `System Update`. 
+        - **Note:** If you cannot boot `OFW`, please boot `Stock sysMMC` from hekate's `Launch` menu instead.
+    ::::
+    
+    :::: tab Unpatched/Non hardware modified-console users
+    - **Unpatched/Non hardware modified-console users:** Boot hekate/Nyx, navigate to `Launch` > `Atmosphere PKG3 sysMMC` (may be called something different if you aren't using our guide's hekate configuration) and then update your firmware via `System Settings` > `System` > `System Update`.
+        - **Note:** If you have an unpatched Switch, have autoRCM enabled and you're updating your system while booted into Stock or OFW, **updating will disable autoRCM** and you will need to enter RCM manually to boot custom firmware again. To prevent autoRCM from being disabled, boot sysCFW and update through settings from there, as booting without AutoRCM <ins>will burn any preserved e-fuses</ins>.
+    ::::
+
+    :::::
+    
+    Once you've successfully updated your firmware, continue with the rest of the guide below.
+
+    ::::::
+    
 ### About emuMMC
 
-Your sysMMC and emuMMC have separate system firmwares and need to be updated separately.
+Your sysMMC and emuMMC have separate system firmware versions and need to be updated separately.
 
 If you keep your emuMMC offline, you have 3 options:
 
@@ -62,11 +95,7 @@ This guide is made for updating your emuMMC's firmware. It is **not** for downgr
 
 :::
 
-There are two supported methods of dumping your sysMMC's firmware, these methods are detailed in the two tabs below. Either choice will provide the same end result, but can be more difficult depending on the console model you have.
-
-- **Note:**
-If you have an unpatched Switch, have autoRCM enabled and you're updating your system while in stock firmware, **updating will disable autoRCM** and you will need to enter RCM manually to boot custom firmware again.
-To prevent autoRCM from being disabled, boot CFW on sysMMC and update through settings from there, as booting without AutoRCM <ins>will burn any preserved e-fuses</ins>.
+There are three supported methods of dumping your sysMMC's firmware, these methods are detailed in the tabs below. All choices will provide the same end result, but can be more difficult depending on the console model you have.
 
 ::::: tabs
 
@@ -82,9 +111,7 @@ To prevent autoRCM from being disabled, boot CFW on sysMMC and update through se
 1. Download the latest release of `Goldleaf.nro` and place it in `sd:/switch` on your microSD card.
 
 #### Dumping your sysMMC firmware
-
-1. Make sure your sysMMC is up to date. If your sysMMC is not up-to-date, boot into sysCFW and update it through `System Settings` > `System` > `System Update`.
-    - sysCFW is recommended since it preserves e-fuses and preserves AutoRCM (if applicable).
+    
 1. Boot into hekate, and navigate to `Launch` > `Atmosphere PKG3 sysMMC`.
     - `Atmosphere PKG3 sysMMC` is sysCFW, this environment may be called something different if you do not use the config we provide in our guide.
 1. Once booted into sysCFW, open the homebrew menu in applet mode by opening the gallery applet on your home menu. 
@@ -95,6 +122,29 @@ To prevent autoRCM from being disabled, boot CFW on sysMMC and update through se
 
 ::::
 
+:::: tab default Dumping your firmware via nxdumptool
+
+#### What you need:
+- The latest release of [nxdumptool](https://github.com/DarkMatterCore/nxdumptool/releases) (`nxdt_rw_poc.nro`)
+
+#### Preparing your microSD card
+
+1. Boot into hekate.
+1. Go to `Tools` > `USB Tools` > `SD Card` and connect your Switch to your PC via USB.
+1. Download the latest release of `nxdt_rw_poc.nro` and place it in `sd:/switch` on your microSD card.
+
+#### Dumping your sysMMC firmware
+    
+1. Boot into hekate, and navigate to `Launch` > `Atmosphere PKG3 sysMMC`.
+    - `Atmosphere PKG3 sysMMC` is sysCFW, this environment may be called something different if you do not use the config we provide in our guide.
+1. Once booted into sysCFW, open the homebrew menu in applet mode by opening the gallery applet on your home menu. 
+    - Title takeover mode (holding `R` while launching any title on your HOME menu) also works, but isn't *required* for this process.
+1. Find nxdumptool (`nxdt_rw_poc`) in your homebrew menu and launch the app.
+1. Navigate to `dump system update` > `start dump`, then wait for nxdumptool to finish dumping your currently installed firmware version.
+1. Once done, reboot back to hekate by holding power for 3-4 seconds and selecting `Power Options` > `Restart`, or by using the `Reboot to Payload` homebrew app in your homebrew menu (Erista ("V1") console users only).
+
+::::
+
 :::: tab Dumping your firmware via TegraExplorer
 
 #### What you need:
@@ -115,8 +165,6 @@ On Mariko ("V2") consoles, this method of dumping the sysMMC's firmware requires
 
 #### Dumping your sysMMC firmware
 
-1. Make sure your sysMMC is up to date. If your sysMMC is not up-to-date, boot into sysCFW and update it through `System Settings` > `System` > `System Update`.
-    - sysCFW is recommended since it preserves e-fuses and preserves AutoRCM (if applicable).
 1. Boot into hekate and navigate to `Payloads` > `TegraExplorer.bin`.
 1. Using the joystick and the A buttons, select the `FirmwareDump.te` script, then select `Dump sysmmc`.
     - If navigation doesn't work with your Joycons, navigating using the volume buttons and selecting using the power button also works.
@@ -138,6 +186,7 @@ On Mariko ("V2") consoles, this method of dumping the sysMMC's firmware requires
 1. Find Daybreak in the homebrew menu and launch it.
 1. Tap on `Install` and follow the instructions corresponding to the method you used to dump your firmware below.
     - For users who dumped their firmware using Goldleaf: Navigate to `sd:/switch/Goldleaf/export/update/<latest firmware version number>`.
+    - For users who dumped their firmware using nxdumptool: Navigate to `sd:/nxdt_rw_poc/System Update/<latest firmware version number>`.
     - For users who dumped their firmware using TegraExplorer: Navigate to `sd:/tegraexplorer/Firmware/<latest firmware version number>`.
 1. Tap on `Continue` and then `Preserve settings`.
     - If you see the message `Warning: exFAT firmware is missing or corrupt`, you likely don't have the exFAT drivers installed on your sysMMC. Just press continue if this is the case.
diff --git a/docs/homebrew/simplemodmanager.md b/docs/homebrew/simplemodmanager.md
@@ -1,6 +1,6 @@
 # SimpleModManager
 
-SimpleModManager is a [homebrew app](index#terminologies) that allows easily adding and removing mods to the layeredFS directory from another directory on the SD card.
+SimpleModManager is a [homebrew app](index#terminologies) that allows easily adding and removing mods to the layeredFS directory from another directory on the SD card. Its official Github page can be found [here](https://github.com/nadrino/SimpleModManager).
 
 ### Common use cases for SimpleModManager:
 
@@ -16,7 +16,7 @@ SimpleModManager should not be used for some specific games like Super Smash Bro
 :::
 
 ## Installation requirements:
-- The latest release of [SimpleModManager](https://github.com/nadrino/SimpleModManager/releases/latest) (the `SimpleModManager.nro` file)
+- The latest release of [SimpleModManager](https://github.com/DefenderOfHyrule/SimpleModManager/releases/tag/v2.1.4) (the `SimpleModManager.nro` file)
 
 ## Installation instructions:
 1. Boot into hekate and go to `Tools` > `USB Tools` > `SD Card`, then plug your Switch into your PC via USB.
diff --git a/docs/homebrew/tesla-menu.md b/docs/homebrew/tesla-menu.md
@@ -20,15 +20,15 @@ Tesla-Menu is dependent on a [sysmodule](index#terminologies) called `nx-ovlload
 
 ## Installation requirements:
 - An archive manager like [7-Zip](https://www.7-zip.org/)
-- The latest release of [Tesla-Menu](https://github.com/WerWolv/Tesla-Menu/releases/tag/v1.2.3) (the `ovlmenu.zip` file)
-- The latest release of [nx-ovlloader](https://github.com/WerWolv/nx-ovlloader/releases/tag/v1.0.7) (the `nx-ovlloader.zip` file)
+- The latest release of [Tesla-Menu](https://github.com/DefenderOfHyrule/Tesla-Menu/releases/tag/v1.2.0) (the `ovlmenu.ovl` file)
+- The latest release of [nx-ovlloader](https://github.com/DefenderOfHyrule/nx-ovlloader/releases/tag/v1.2.0) (the `nx-ovlloader.zip` file)
 
 ## Installation instructions:
 1. Boot into hekate and go to `Tools` > `USB Tools` > `SD Card`, then plug your Switch into your PC via USB.
 1. Your microSD card should now be accessible on your PC, open it.
-1. Extract both `.zip` files to a location on your computer.
-    - If your archive manager allows for it, you can also simply open the `.zip` files directly.
-1. Copy the *contents* of each (extracted) `.zip` file to the root of your microSD card.
+1. Extract the nx-ovlloader `.zip` file to a location on your computer.
+    - If your archive manager allows for it, you can also simply open the `.zip` file directly.
+1. Copy the *contents* of the (extracted) `.zip` file to the root of your microSD card, then copy `ovlmenu.ovl` to `sd:/switch/.overlays`.
     - **Optional:** You can verify if you've installed Tesla-Menu and nx-ovlloader correctly, you should have a folder called `420000000007E51A` (nx-ovlloader) in `sd:/atmosphere/contents` and the `ovlmenu.ovl` (Tesla-Menu) file in `sd:/switch/.overlays`.
 1. Boot into CFW.
 
diff --git a/docs/user_guide/all/partitioning_sd.md b/docs/user_guide/all/partitioning_sd.md
diff --git a/docs/user_guide/all/partitioning_sd_syscfw.md b/docs/user_guide/all/partitioning_sd_syscfw.md
