From f2d9867e4e7cf8e02d5ed288fac937ae815dce6e Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Wed, 9 Mar 2022 18:43:35 -0500 Subject: [PATCH 1/9] Grammar and updating https://discord.com/channels/196618637950451712/533041632283459595/951263946038444073 --- docs/extras/adding_udev.md | 2 +- docs/extras/alternate_bootsetups.md | 14 +-- docs/extras/autorcm.md | 32 +++---- docs/extras/blocking_nintendo.md | 28 +++--- docs/extras/dumping_title_keys.md | 2 +- docs/extras/game_modding.md | 2 +- docs/extras/glossary.md | 2 +- docs/extras/nandrestore.md | 37 ++++---- docs/extras/save_management.md | 4 +- docs/extras/theming.md | 14 +-- docs/extras/transfer_sd.md | 46 +++++----- docs/extras/updating.md | 22 ++--- docs/faq.md | 90 +++++++++---------- docs/index.md | 4 +- docs/user_guide/emummc/launching_cfw.md | 16 ++-- docs/user_guide/emummc/linux_partitioning.md | 12 +-- docs/user_guide/emummc/making_emummc.md | 30 +++---- docs/user_guide/emummc/partitioning_sd.md | 26 +++--- docs/user_guide/emummc/sd_preparation.md | 32 +++---- docs/user_guide/getting_started.md | 15 ++-- docs/user_guide/rcm.md | 12 +-- docs/user_guide/sysnand/launching_cfw.md | 12 +-- .../sysnand/making_essential_backups.md | 26 +++--- docs/user_guide/sysnand/sd_preparation.md | 24 ++--- 24 files changed, 252 insertions(+), 252 deletions(-) diff --git a/docs/extras/adding_udev.md b/docs/extras/adding_udev.md index 1427ce93..50cef075 100644 --- a/docs/extras/adding_udev.md +++ b/docs/extras/adding_udev.md @@ -44,7 +44,7 @@ You should now be able to run the payload sender without having to use `sudo`. ## Option 2: Installing a package with the rules !!! tip "Note:" - These rules will actually allow _ANY_ user to access your switch via USB, not only _your_ user. + These rules will actually allow _ANY_ user to access your Switch via USB, not only _your_ user. You may just follow the instructions at nx-udev, or if you're on Ubuntu / Debian: diff --git a/docs/extras/alternate_bootsetups.md b/docs/extras/alternate_bootsetups.md index 5f2e031c..60857178 100644 --- a/docs/extras/alternate_bootsetups.md +++ b/docs/extras/alternate_bootsetups.md @@ -20,11 +20,11 @@ If you need to troubleshoot something, or need to try a different boot setup, re ### Instructions !!! tip "" - 1. Insert your Switch's SD card into your PC - 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your SD card - 3. Copy `fusee.bin` to the atmosphere folder on your SD card - 4. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your SD card - 5. Copy `hekate_ipl.ini` to the `bootloader` folder on your SD card + 1. Insert your Switch's microSD Card into your PC + 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD Card + 3. Copy `fusee.bin` to the atmosphere folder on your microSD Card + 4. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your microSD Card + 5. Copy `hekate_ipl.ini` to the `bootloader` folder on your microSD Card 6. Setup is complete, now you can boot CFW by injecting the hekate_ctcaer `.bin` file from the Hekate zip @@ -40,6 +40,6 @@ If you need to troubleshoot something, or need to try a different boot setup, re ### Instructions !!! tip "" - 1. Insert your Switch's SD card into your PC - 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your SD card + 1. Insert your Switch's microSD Card into your PC + 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD Card 3. Setup is complete, now you can boot CFW by injecting `fusee.bin` diff --git a/docs/extras/autorcm.md b/docs/extras/autorcm.md index c3063492..b263e5a7 100644 --- a/docs/extras/autorcm.md +++ b/docs/extras/autorcm.md @@ -1,9 +1,9 @@ -## AutoRCM +## autoRCM -!!! tip "What is AutoRCM?" - AutoRCM causes the console to believe it is bricked, and will automatically launch RCM upon boot for recovery purposes, without needing a jig. As RCM is a recovery mode from repair specialists, this is an intended feature from the device developer, though is also considered a softbrick. If you aren't careful, misuse of AutoRCM can lead to real **damage**, especially with units that cannot inject custom RCM payloads (like Mariko hardware). Please take care when using it. Please keep in mind that the console can no longer boot on its own, so you'll need a PC, phone, or other payload injector to start the console after a coldboot. +!!! tip "What is autoRCM?" + AutoRCM causes the console to believe it is bricked, and will automatically launch RCM upon boot for recovery purposes, without needing a jig. As RCM is a recovery mode from repair specialists, this is an intended feature from the device developer, though is also considered a softbrick. If you aren't careful, misuse of autoRCM can lead to real **damage**, especially with units that cannot inject custom RCM payloads (like Mariko hardware). Please take care when using it. Please keep in mind that the console can no longer boot on its own, so you'll need a PC, phone, or other payload injector to start the console after a coldboot. - Note: If the console screen stays black when pressing the power button after activating AutoRCM, remember that it's not broken. It's in RCM. + Note: If the console screen stays black when pressing the power button after activating autoRCM, remember that it's not broken. It's in RCM. !!! warning "If you don't have a BOOT0/1 backup yet..." You really want to kill your console, huh? If you haven't made a BOOT0/1 backup yet, it is recommended to make one **right now**. @@ -12,29 +12,29 @@ 2. Go to `Tools`, and select `Backup eMMC` 3. Then tap `eMMC BOOT0 & BOOT1` and let the process complete. -!!! danger "Disadvantages of AutoRCM" - There are some disadvantages you should consider before installing AutoRCM: +!!! danger "Disadvantages of autoRCM" + There are some disadvantages you should consider before installing autoRCM: - - Please keep in mind that the console can no longer boot on its own, so you'll need a PC, phone, or other payload injector to start the console after letting the console fully shut off. (AutoRCM by itself is considered a "tethered jailbreak"). - Note: Sleep Mode is not considered "powering off/on" the console. Sleep Mode will still work as intended and is fully unchanged with AutoRCM. + - Please keep in mind that the console can no longer boot on its own, so you'll need a PC, phone, or other payload injector to start the console after letting the console fully shut off. (autoRCM by itself is considered a "tethered jailbreak"). + Note: Sleep Mode is not considered "powering off/on" the console. Sleep Mode will still work as intended and is fully unchanged with autoRCM. - When completely discharged, your Switch will take a very long time to charge while in RCM. To solve this, charge the console for approximately twenty minutes before booting into Hekate and selecting a boot option. After it's done booting, the console will now charge at a normal speed with a battery icon in the corner. - - When a system update is completed while stock firmware is running, AutoRCM becomes disabled so you need to turn it on again. AutoRCM can be preserved by updating while CFW is active. + - When a system update is completed while stock firmware is running, autoRCM becomes disabled so you need to turn it on again. autoRCM can be preserved by updating while CFW is active. -!!! tip "Advantages of AutoRCM" +!!! tip "Advantages of autoRCM" AutoRCM can be used for good as well: - If you were having trouble getting into RCM before (i.e you were using the tinfoil method), now you can get into RCM without any hassle. - - If you want to keep fuses unburned, you can do so with AutoRCM, as the Switch never gets the chance to burn them. Nintendo's bootloaders burn the fuses, but those bootloaders cannot be used if AutoRCM is enabled. - Note: updating the console while booted into Hekate's "stock" configuration will clear AutoRCM on the next reboot. Please update while using custom firmware, or be sure to use a jig after the console reboots. + - If you want to keep fuses unburned, you can do so with autoRCM, as the Switch never gets the chance to burn them. Nintendo's bootloaders burn the fuses, but those bootloaders cannot be used if autoRCM is enabled. + Note: updating the console while booted into Hekate's "stock" configuration will clear autoRCM on the next reboot. Please update while using custom firmware, or be sure to use a jig after the console reboots. - It's easier to inject a payload using a payload injector, as using your jig and booting into RCM manually is no longer required. !!! tip "Other information..." - This method corrupts a single byte in both your BOOT0 and your BOOT1 partitions. This is why a backup of those is recommended. - - This software version of AutoRCM can almost always be reversed, so don't freak out if it doesn't work out the way you'd like it to. + - This software version of autoRCM can almost always be reversed, so don't freak out if it doesn't work out the way you'd like it to. -If, despite all of the warnings above, you still wish to install AutoRCM, and understand the risks, do the following: +If, despite all of the warnings above, you still wish to install autoRCM, and understand the risks, do the following: 1. Boot Hekate 2. Go to `Tools` -3. At the bottom of the page, tap `Arch Bit • AutoRCM • Touch • Pkg1/2` -4. Then tap `AutoRCM`. It will show a little `ON` next to the option once you have done this. +3. At the bottom of the page, tap `Arch Bit • autoRCM • Touch • Pkg1/2` +4. Then tap `autoRCM`. It will show a little `ON` next to the option once you have done this. diff --git a/docs/extras/blocking_nintendo.md b/docs/extras/blocking_nintendo.md index a26af9f6..edfb1c2b 100644 --- a/docs/extras/blocking_nintendo.md +++ b/docs/extras/blocking_nintendo.md @@ -3,24 +3,24 @@ This page will help you set up a method to block all communication with Nintendo. This will stop any updates and reporting to Nintendo, but it will prevent use of the eShop and online games. ### Instructions (AMS DNS redirection) -You can configure Atmosphere to automatically redirect any requests directed to Nintendo to nothing instead. Documentation about this feature can be [found here](https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/dns_mitm.md). The section below will help you set up DNS redirection on your emummc. Note that this will only apply when you are using cfw. +You can configure Atmosphere to automatically redirect any requests directed to Nintendo to nothing instead. Documentation about this feature can be [found here](https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/dns_mitm.md). The section below will help you set up DNS redirection on your emuMMC. Note that this will only apply when you are using CFW. -#### What you need: +#### What you need: - emummc.txt - Atmosphere 0.18.0 or higher #### Setup: -1. Insert your SD into your pc +1. Insert your SD into your PC 2. Enter the Atmosphere folder 3. If it doesn't exist already, create a folder named `hosts` in the atmosphere folder 4. Copy the emummc.txt into the hosts folder - - If you want to apply the DNS redirection to sysmmc instead of emummc, rename the file to `sysmmc.txt` + - If you want to apply the DNS redirection to sysMMC instead of emuMMC, rename the file to `sysmmc.txt` !!! note "Verify functionality" - You can verify the functionality of the DNS redirection by booting into emummc (or sysmmc if you applied the config to sys), and powering off after. - + You can verify the functionality of the DNS redirection by booting into emuMMC (or sysMMC if you applied the config to sys), and powering off after. + A report will be generated in sd:/atmosphere/logs called `dns_mitm_startup.log`. If this starts with the following, the dns redirection is active !!! tip "" @@ -33,13 +33,13 @@ You can add a custom DNS to your WiFi connection that will block all communicati !!! tip "" Enter the console's System Settings, and then proceed to the Internet tab. From here: - + ### Setting up a new connection via WiFi - + !!! warning "Open WiFi networks without a password" Not all WiFi networks require a password to connect. If your network does not use one, you can use the `Manual Setup` option, located at the very bottom of the `Internet Settings` screen below all other WiFi networks. - + 1. Select your WiFi network from the list of networks. 2. Enter an **incorrect** password that is 8 characters long and press `OK`. 3. After a few moments of attempting to connect, the console will display a connection error. @@ -62,14 +62,14 @@ You can add a custom DNS to your WiFi connection that will block all communicati ----- ### Using homebrew to set 90dns on all existing WiFi networks - 1. Download [switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the switch folder. + 1. Download [switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the /switch folder. 2. Launch CFW and open the homebrew menu. 3. Launch `90dns setter`. 4. Press X to apply 90dns to all WiFi networks. - 5. Press Y to reboot the switch. + 5. Press Y to reboot the Switch. 6. Check in system settings if networks have a custom DNS applied. - + | Location | Primary DNS | Secondary DNS | |:--------------------------------------|:--------------------|:--------------------| | Europe (Server located in France) | `163.172.141.219` | `207.246.121.77` | @@ -95,11 +95,9 @@ You can add a custom DNS to your WiFi connection that will block all communicati !!! tip "" 1. Download the latest release of the [90dns Tester](https://github.com/meganukebmp/Switch_90DNS_tester/releases) - 2. Place the `Switch_90DNS_tester.nro` in the `switch` folder on your SD + 2. Place the `switch_90DNS_tester.nro` in the `/switch` folder on your SD 3. Enter the homebrew menu and run the 90dns Tester 4. After the test finished it should look similar to the below picture, with every `nintendo` domain being blocked !!! tip "" ![tester example](../extras/img/90dns_tester_switch.jpg) - - diff --git a/docs/extras/dumping_title_keys.md b/docs/extras/dumping_title_keys.md index 55dbf350..54a173e1 100644 --- a/docs/extras/dumping_title_keys.md +++ b/docs/extras/dumping_title_keys.md @@ -19,4 +19,4 @@ This section is for dumping your games' title keys. 1. Enter RCM and inject the Hekate payload. 2. Tap the `Payloads` option, then press Lockpick_RCM.bin. 3. If Lockpick_RCM asks you to select between SysNAND or EmuNAND, choose SysNAND by navigating with the volume buttons and pressing the power button. - 4. Lockpick_RCM should now inform you that your title keys have been saved to `/switch/title.keys` on the SD card. + 4. Lockpick_RCM should now inform you that your title keys have been saved to `/switch/title.keys` on the microSD Card. diff --git a/docs/extras/game_modding.md b/docs/extras/game_modding.md index 08be2053..5dc8481c 100644 --- a/docs/extras/game_modding.md +++ b/docs/extras/game_modding.md @@ -7,7 +7,7 @@ LayeredFS, a tool built in to Atmosphere, allows you to replace game files with ### Instructions !!! tip "" - Make a folder on your SD card inside the `atmosphere/contents/` folder, with the name being the title ID of the game you would like to replace the files of. **Note: On Atmosphere 0.9.4 and below `contents` is called `titles`** + Make a folder on your microSD Card inside the `atmosphere/contents/` folder, with the name being the title ID of the game you would like to replace the files of. **Note: On Atmosphere 0.9.4 and below `contents` is called `titles`** Switch game title IDs can be found on [http://nswdb.com/](http://nswdb.com/). If you have a pre-made mod, the files would be placed here. Then, once the title is launched while in Atmosphere, your mod should load. By default, holding the L button while launching a game will disable any mod. diff --git a/docs/extras/glossary.md b/docs/extras/glossary.md index bf77a314..2123e930 100644 --- a/docs/extras/glossary.md +++ b/docs/extras/glossary.md @@ -8,7 +8,7 @@ The following list is in alphabetical order. - **90DNS**: DNS that blocks system updates on the Nintendo Switch. This can be enabled by following the guide [here](blocking_nintendo.md). - **[Atmosphere](https://github.com/Atmosphere-NX/Atmosphere)**: The CFW developed by the Atmosphere-NX organization on GitHub and the one used in this guide. -- **AutoRCM**: A method that corrupts parts of your boot0 and boot1, causing the Switch to boot into RCM automatically. Using this requires an additional peripheral (such as a computer, phone, dongle or trinket) to be able to boot your Switch. +- **autoRCM**: A method that corrupts parts of your boot0 and boot1, causing the Switch to boot into RCM automatically. Using this requires an additional peripheral (such as a computer, phone, dongle or trinket) to be able to boot your Switch. - **boot0 and boot1**: Two partitions of the Switch NAND. - **CFW**: Short for custom firmware. Custom firmware permits you to completely modify how your Switch works. - **Deja Vu**: An unreleased exploit chain for the Nintendo Switch. The completely unpatched version of this chain will grant access to TrustZone, which effectively means being able to enter CFW. The TrustZone part of this exploit was patched in firmware version 5.0.0 and up, but normal homebrew access can still be gained up to firmware version 6.0.1. diff --git a/docs/extras/nandrestore.md b/docs/extras/nandrestore.md index 31b2faa6..26919042 100644 --- a/docs/extras/nandrestore.md +++ b/docs/extras/nandrestore.md @@ -1,38 +1,39 @@ -## Restore a NAND backup to the switch +## Restore a NAND backup to the Switch !!! danger "Warning:" - -This will reset all of your saves, games, system version and other system settings back to a point when you made the the nand backup. Keep this in mind, as you probably don't have to restore a nand backup unless you have bricked your switch or want to go back online safely after using cfw. - + -This will reset all of your saves, games, system version and other system settings back to the point when you made the NAND backup. Keep this in mind, as you probably don't have to restore a NAND backup unless you have bricked your Switch or want to go back online safely after using CFW. + -If you're going to restore an old NAND which will downgrade your firmware it's best to create a second NAND backup before restoring the first one in case something goes wrong. ### What you need: -- Your `rawnand.bin` (Combined or in 15 or 30 parts) +- Your `rawnand.bin` (combined or in 15 or 30 parts) - Your `BOOT0` and `BOOT1` - If you're missing any of the files above, ask for further help in the [Nintendo Homebrew](https://discord.gg/C29hYvh) Discord server. - The Hekate Payload -- A microSD card larger than 32gb +- A microSD Card larger than 32GB ### Instructions: -Before we start, check if you have a tree of folders called `backup/[8 Character NAND id]/restore` on your sd card. +Before we start, check if you have a tree of folders called `backup/[8 Character NAND id]/restore` on your microSD Card. -!!! warning "If you don't see a backup or [8 Character NAND id] folder on your sd card:" - This means you do not have a nand backup, it is highly recommended you make one as soon as possible. Follow the steps below to make one. +!!! warning "If you don't see a backup or [8 Character NAND id] folder on your microSD Card:" + This means you do not have a NAND backup, it is highly recommended you make one as soon as possible. Follow the steps below to make one. - 1. Launch the latest Hekate payload on your switch. - 2. Navigate to `Tools > Backup eMMC > eMMC BOOT0 & BOOT1` and let it do its thing. - 3. Wait for the process to complete. When it's completed, you now have a `backup/[8 Character NAND id]/restore` folder on your sd card. Continue with step 1 of the guide. + 1. Inject the latest Hekate payload to your Switch. + 2. Navigate to `Tools > Backup eMMC > eMMC BOOT0 & BOOT1` and let the task complete. + 3. Once it's completed, you'll now have a `backup/[8 Character NAND id]/restore` folder on your microSD Card. Continue with Step 1 of the guide. -1. Copy your `rawnand.bin` (combined or in 15 or 30 parts, this can be done by using the joiner scripts on the hekate github release page), `BOOT0`, and `BOOT1` to the `backup/[8 Character NAND id]/restore` folder on the sd card. -2. Put your sd card into your switch, and launch Hekate. +1. Copy your `rawnand.bin`, `BOOT0`, and `BOOT1` to the `backup/[8 Character NAND id]/restore` folder on the microSD Card. + • The `rawnand.bin` might instead be split into many small `rawnand.bin.xx` files, where `xx` will be a number. Place **all of these** in the restore folder mentioned above. +2. Put your microSD Card into your Switch, and launch Hekate. 3. Navigate to `Tools > Restore eMMC`. Select `Restore eMMC BOOT0 & BOOT1`. Wait for this process to complete. 4. In that same menu, select `eMMC RAW GPP` and wait for the process to complete. This will take a very long time to complete. !!! danger "If you're downgrading using your NAND backup" - If the security version you were on before you performed the NAND restore is HIGHER than the NAND backup itself, you have to enable autoRCM to not get stuck in a boot crash. - A system update is considered a security version when a fuse is burned, you can check **which versions burn fuses here**. + If the security revision you were on before you performed the NAND restore is HIGHER than the NAND backup itself, you have to enable autoRCM to not get stuck in a crash on boot. + A system update is considered a security revision when a fuse is burned. You can check **which versions burn fuses here**. - If you were in autorcm before you upgraded to a newer security version (and still were after the upgrade) you don't have to do this. + If no fuses were burnt between the NAND backup you are restoring, and the Switch's current version, you can ignore this. - 1. In Hekate's main menu, navigate to `Tools` and go to the bottom of the page where you will find a button called `Archive bit - AutoRCM` - 2. Select the `AutoRCM` buttom and you will see `ON` written next to it. This means it is enabled. + 1. In Hekate's main menu, navigate to `Tools` and go to the bottom of the page where you will find a button called `Archive bit - autoRCM` + 2. Select the `autoRCM` button, and you will see `ON` written next to it. This means AutoRCM is enabled. diff --git a/docs/extras/save_management.md b/docs/extras/save_management.md index 9cfc2688..b9dd9923 100644 --- a/docs/extras/save_management.md +++ b/docs/extras/save_management.md @@ -1,8 +1,8 @@ # Save Management -For save management, [JKSV](https://github.com/J-D-K/JKSV) is recommended. It can be used to back up and restore game saves to your SD card. +For save management, [JKSV](https://github.com/J-D-K/JKSV) is recommended. It can be used to back up and restore game saves to your microSD Card. -[Checkpoint](https://github.com/FlagBrew/Checkpoint) is also a save manager. It can be used to back up and restore game saves to your SD card. It also has the ability to share save data over FTP and WiFi. +[Checkpoint](https://github.com/FlagBrew/Checkpoint) is also a save manager. It can be used to back up and restore game saves to your microSD Card. It also has the ability to share save data over FTP and WiFi.   diff --git a/docs/extras/theming.md b/docs/extras/theming.md index 7f02871d..221e0ee7 100644 --- a/docs/extras/theming.md +++ b/docs/extras/theming.md @@ -27,7 +27,7 @@ The latest release of /` on your SD card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to the `restore` folder. -11. Eject the SD card and insert it into your switch. -12. Inject the hekate payload once again. +6. Copy the contents of your microSD Card somewhere to your PC. +7. Follow only [this page](https://switchgui.de/switch-guide/user_guide/emummc/partitioning_sd/) to partition the new microSD Card for an emuMMC setup. +8. After it’s done, exit and insert your new microSD Card into your PC. +9. Copy the contents of your old microSD Card to your new one. +10. Navigate to `/backup//` on your microSD Card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to the `restore` folder. +11. Eject the microSD Card and insert it into your Switch. +12. Inject the Hekate payload once again. 13. Tap on `Tools`, `Restore eMMC`, set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`. 14. Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: 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 which is not what you want. -15. Your emuMMC is now restored on the new SD card and you should be able to launch it from `Launch` -> `Atmosphere FSS0 EmuMMC` in hekate. +15. Your emuMMC is now restored on the new microSD Card and you should be able to launch it from `Launch` -> `Atmosphere FSS0 emuMMC` in hekate. diff --git a/docs/extras/updating.md b/docs/extras/updating.md index dc7bf489..f0d5c4ce 100644 --- a/docs/extras/updating.md +++ b/docs/extras/updating.md @@ -14,12 +14,12 @@ When updating Atmosphere always make sure to _read the release notes_. They may When a new version of Atmosphere releases, you can update Atmosphere by following these steps: -1. Turn off your Nintendo Switch and plug your SD card in your computer. +1. Turn off your Nintendo Switch and plug your microSD Card in your computer. 2. Download the latest release of Atmosphere (Download the `atmosphere-(version)-master-(version)+hbl-(version)+hbmenu-(version).zip` release of Atmosphere.) -3. Copy *the contents of* the Atmosphere `.zip` file to the root of your SD card. +3. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD Card. - If you are prompted to overwrite files, do so. 4. (If your hekate is not on the latest version) Update hekate via the steps below -5. Put your SD card back in your Switch and launch CFW. +5. Put your microSD Card back in your Switch and launch CFW. ## Updating Hekate @@ -27,10 +27,10 @@ When updating Hekate always make sure to _read the release notes_. They may list When a new version of Hekate releases, you can update by following these steps: -1. Turn off your Nintendo Switch and plug your SD card in your computer. -2. Download the latest version of Hekate (Download the `hekate_ctcaer_(version).zip` release of hekate). -3. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your SD card. If you are asked to overwrite or merge files while copying, say yes to merge/overwrite them. -4. Put your SD card back in your Switch and launch Hekate. +1. Turn off your Nintendo Switch and plug your microSD Card in your computer. +2. Download the latest version of Hekate (Download the `hekate_ctcaer_(version).zip` release of Hekate). +3. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your microSD Card. If you are asked to overwrite or merge files while copying, say yes to merge/overwrite them. +4. Put your microSD Card back in your Switch and launch Hekate. 5. Go to the Options tab at the top right of the screen. Turn "Update Reboot 2 Payload" on the bottom right ON (if it isn't on already). Tap "Save Options" at the bottom of the screen. ## Updating your firmware @@ -55,13 +55,13 @@ In addition, updating to or past some firmwares update the gamecard firmware. Re If at least one of the versions you are updating towards also updates the gamecard firmware, you will not be able to downgrade below that version without making the gamecard slot unusable until you update. -Atmosphere (and Hekate) come bundled with patches that automatically disable the gamecard slot if it is detected that the system has an older gamecard firmware that would be updated. If you boot into RCM on each boot (for example by using AutoRCM), this means that the gamecard slot will not be updated and you can downgrade below that version. If this happens, you will not be able to use the gamecard slot as long as you are on the newer firmware. +Atmosphere (and Hekate) come bundled with patches that automatically disable the gamecard slot if it is detected that the system has an older gamecard firmware that would be updated. If you boot into RCM on each boot (for example by using autoRCM), this means that the gamecard slot will not be updated and you can downgrade below that version. If this happens, you will not be able to use the gamecard slot as long as you are on the newer firmware. Otherwise, you can safely update your system firmware through the system settings. !!!warning "Note about autoRCM" If you 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 will burn any preserved fuses. + To prevent autoRCM from being disabled, boot CFW on sysMMC and update through settings from there, as booting without autoRCM will burn any preserved fuses. ### About emuMMC @@ -85,9 +85,9 @@ If you keep your emuMMC offline, you will have to use a gamecard to update your - The latest release of TegraExplorer - The latest release of Atmosphere -### Preparing your SD card +### Preparing your microSD Card -1. Insert your microSD card into your computer. +1. Insert your microSD Card into your computer. 2. Download `TegraExplorer.bin` and place it somewhere on your PC (A good idea is to put it where you keep all your switch payloads like Hekate). 3. Update Atmosphere and Hekate by using the above guides. 4. If you haven't already, update the sysMMC to the latest firmware. diff --git a/docs/faq.md b/docs/faq.md index 0417e6ea..90257aa6 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -1,23 +1,23 @@ ## What firmware versions are currently hackable? !!! tip "" - Currently two hardware revisions of the Switch exist. Any Switch bought or manufactured before the middle of 2018 has a bootrom bug that allows us to run code regardless of the firmware version on the Switch. When Nintendo updates the system, however, CFW will usually need an update to account for it. + Currently two hardware revisions of the Switch exist. Any Switch bought or manufactured before the middle of 2018 has a bootrom bug that allows us to run code regardless of the firmware version on the Switch. When Nintendo updates the system, however, CFW will usually need an update to account for it. This bug cannot be fixed by Nintendo once the console leaves the factory, unless the console is sent in for repairs. This means that all current and future firmwares will be able to launch CFW through this exploit on the old hardware revision. Any console purchased after approximately August 2018 is **likely** to be patched. This includes the latest units on shelves, referred to as 'red box' or 'Mariko'. Mariko is hardware patched, but may come on a vulnerable firmware. Currently the only way to know if your Switch is hackable is by trying to send the payload in RCM. Even with this exploit fixed, many Switches on 8.0.1 and below will be hackable to some degree in the future (see [Should I update my Firmware?](#should-i-update-my-firmware) for much more detailed information). - The serial number on the back of the box can possibly tell you which consoles are patched and which aren't. + The serial number on the back of the box can possibly tell you which consoles are patched and which aren't. See here for an up to date list. ## How do I use the exploit? How can I boot into RCM? !!!tip "" - To launch CFW through the exploit, the Switch needs to be in "Recovery Mode"(RCM). - The easiest way to enter RCM is by grounding pin 10 in the right joycon rail and holding VOL+ on boot. - Several methods and designs to do this exist, see [our guide](https://nh-server.github.io/switch-guide/user_guide/emummc/entering_rcm) for more information. + To launch CFW through the exploit, the Switch needs to be in "Recovery Mode"(RCM). + The easiest way to enter RCM is by grounding pin 10 in the right joycon rail and holding VOL+ on boot. + Several methods and designs to do this exist, see [our guide](https://nh-server.github.io/switch-guide/user_guide/emummc/entering_rcm) for more information. Once the Switch is in RCM it needs to be connected to either a computer, phone or dongle to send the exploit and the payload. This procedure needs to happen every time the Switch boots from a completely "off" state, otherwise the Switch will boot into the stock firmware. @@ -26,11 +26,11 @@ ## What makes a good jig good? Can I use a paperclip? !!!tip "" - Most people prefer to use 3d-printed jigs to enter RCM. - These jigs are made in a way that they slide into the right joycon rail and have a piece of connected wire that then bridges pin 10 and one of the grounded pins on the Switch. + Most people prefer to use 3d-printed jigs to enter RCM. + These jigs are made in a way that they slide into the right joycon rail and have a piece of connected wire that then bridges pin 10 and one of the grounded pins on the Switch. A lot of different designs for these jigs exist, but it is important to understand, that these jigs can damage the Switch if they are made in a bad way. - Since the wire in the jig is supposed to touch the pads inside the Switch's joycon rail, it is important to use wire that is thin, not rigid and bent/not pointy. + Since the wire in the jig is supposed to touch the pads inside the Switch's joycon rail, it is important to use wire that is thin, not rigid and bent/not pointy. Paperclips make for potentially dangerous jigs, as they are made out of a hard material, are rigid and pointy and can easily scratch off the pads inside the Switch. A good jig uses 32Gauge(0.2mm diameter) wire and is bent in a way that the end of the wire does not scratch the pads. You can download and 3d-print your own jig and use the pictures on [this website](https://www.thingiverse.com/thing:2892320) to guide you on how to bend the wire correctly. @@ -40,11 +40,11 @@ ## Is there an easier way to enter RCM? !!!tip "" - To enter RCM more comfortably a solution called "AutoRCM" exists. - Once set up, this method will always boot the Switch into RCM, even without a jig or holding any buttons. - This works by "bricking" the Switch in a controlled manner. - The Switch detects that something is wrong and boots into RCM to get repaired. - The big downside of this method is, that it is impossible to boot the Switch without a computer, phone or dongle, as it will never boot into stock firmware by itself, and that it requires an SD card with the proper CFW files on it at all times. In addition, if the battery of the Switch is completely drained, the Switch will need to charge to at least 10% in Hekate before launching Atmosphere, otherwise the Switch will refuse to boot due to the low battery. Charging in RCM is not recommended as this is very slow. AutoRCM can be reversed, but it is advised to keep a working NAND and BOOT0/1 backup before using it. + To enter RCM more comfortably a solution called "autoRCM" exists. + Once set up, this method will always boot the Switch into RCM, even without a jig or holding any buttons. + This works by "bricking" the Switch in a controlled manner. + The Switch detects that something is wrong and boots into RCM to get repaired. + The big downside of this method is, that it is impossible to boot the Switch without a computer, phone or dongle, as it will never boot into stock firmware by itself, and that it requires an microSD Card with the proper CFW files on it at all times. In addition, if the battery of the Switch is completely drained, the Switch will need to charge to at least 10% in Hekate before launching Atmosphere, otherwise the Switch will refuse to boot due to the low battery. Charging in RCM is not recommended as this is very slow. autoRCM can be reversed, but it is advised to keep a working NAND and BOOT0/1 backup before using it. Many Android-phones are able to send the exploit to the Switch, making them a perfect portable way to launch CFW. Different designs for portable dongles exist, ranging from Raspberry Pi Zero and Arduino projects to internal dongles, that work completely autonomous. The latter should only be done by advanced users, as it requires soldering onto the Switch mainboard itself. @@ -55,14 +55,14 @@ If your Switch is one of the new hardware revisions that patched the exploit in RCM and you are on firmware 7.0.1 or lower, you should not update if you want to have CFW in the forseeable future. - If your Switch is one of the older hardware revisions and you don't mind having to use jigs/hardmods/AutoRCM and sending the exploit via computer, phone or dongle everytime you want to launch into CFW then it is completely safe to update. - If you want the chance to maybe, one day, not have to use a external device, then it is recommended to stay on a FW as low as possible. + If your Switch is one of the older hardware revisions and you don't mind having to use jigs/hardmods/autoRCM and sending the exploit via computer, phone or dongle everytime you want to launch into CFW then it is completely safe to update. + If you want the chance to maybe, one day, not have to use a external device, then it is recommended to stay on a FW as low as possible. Beware that this means that you potentially need to wait for a very long time (months to years) for this to happen, if ever. Private exploits to launch CFW over the Browser are known to exist for firmwares up to 7.0.1. - Downgrading on the Switch is possible, but it requires using AutoRCM and a custom bootloader payload to bypass the Switch's several hardware anti-downgrade mechanisms. + Downgrading on the Switch is possible, but it requires using autoRCM and a custom bootloader payload to bypass the Switch's several hardware anti-downgrade mechanisms. This will not work on an unpatched system, and is practically useless for most users. - On every boot the Switch firmware checks how many e-fuses have been burned and how many e-fuses the Switch expects to be burned. - Major updates to the Switch, or updates in which a large vulnerability has been patched, irreversibly burn one of the Switch's 64 "e-fuses". + On every boot the Switch firmware checks how many e-fuses have been burned and how many e-fuses the Switch expects to be burned. + Major updates to the Switch, or updates in which a large vulnerability has been patched, irreversibly burn one of the Switch's 64 "e-fuses". *If the Switch ever detects that more e-fuses have been burned than expected (meaning a downgrade happened), it will refuse to boot. Replacing e-fuses is not an option.* You can find more information about fuses here Atmosphere 1.2.6 works fine with the new 13.2.1 firmware update on unpatched units. The situation for patched and new units is this: @@ -73,23 +73,23 @@ - **Switch Lite** *(HDH-001): Do NOT update past 8.0.1. Units on 8.0.1 and below will likely get homebrew. Units on 8.1.0 and higher are not expected to be hacked and can be updated.* - A method to update without burning e-fuses exists, but, like downgrading, it forces you to use AutoRCM and sending the exploit via USB every time, as booting into the stock firmware even once would instantly burn the e-fuse. Note that other anti-downgrade mechanisms exist, making it for example impossible to boot game carts on a firmware below 4.1/9.0.0 if the Switch has ever launched a game on firmware 4.1+/9.0.0+. This can only be worked around by completely disabling the game cart slot while on 4.1/9.0.0 or greater, which is similarly impractical for most users. + A method to update without burning e-fuses exists, but, like downgrading, it forces you to use autoRCM and sending the exploit via USB every time, as booting into the stock firmware even once would instantly burn the e-fuse. Note that other anti-downgrade mechanisms exist, making it for example impossible to boot game carts on a firmware below 4.1/9.0.0 if the Switch has ever launched a game on firmware 4.1+/9.0.0+. This can only be worked around by completely disabling the game cart slot while on 4.1/9.0.0 or greater, which is similarly impractical for most users. ## Is it safe to use homebrew? Will I get banned? !!!tip "" - The Switch comes with a lot of telemetry, and has been called a "telemetry monster" by several prominent developers. - As long as the Switch is connected to the internet, Nintendo gets a report about a lot of different actions and states and has the option to log or act on them. + The Switch comes with a lot of telemetry, and has been called a "telemetry monster" by several prominent developers. + As long as the Switch is connected to the internet, Nintendo gets a report about a lot of different actions and states and has the option to log or act on them. Even if the Switch is offline and connects to the internet at a later point, Nintendo still recieves information about what happened while the Switch was disconnected. - - To disable some of this telemetry, it is advised to disable the sending of error reports in the System Settings of the Switch. + + To disable some of this telemetry, it is advised to disable the sending of error reports in the System Settings of the Switch. Additionally if you live in the EU you can set the "do not share" option on Nintendo's website to prevent your Switch from sending a lot of telemetry, although the effectiveness of this is questionable. - - Nintendo still receives a lot of information, even with those options disabled. - We also cannot know if Nintendo decides to look for something in the logs and ban people in retrospect. + + Nintendo still receives a lot of information, even with those options disabled. + We also cannot know if Nintendo decides to look for something in the logs and ban people in retrospect. They have also shown to expand their telemetry options with every other firmware update. - + !!!tip "Currently all bans have been for very obvious and intrusive actions, specifically:" - Developers using their unique Switch data to poke and reverse-engineer Nintendos Server responses - People pirating games and using them online @@ -99,13 +99,13 @@ - People installing homebrew NSP files, which Nintendo can pick up on with their telemetry - Atmosphere stops some, but ***not all*** of Nintendo's telemetry, and prevents crash reports from being sent. This means Nintendo can't tell if anything, including homebrew or modded games crashed, and Atmosphere dumps the crash log to the SD card to help homebrew developers. However, Nintendo still receives information about what is being played, and general system report information. + Atmosphere stops some, but ***not all*** of Nintendo's telemetry, and prevents crash reports from being sent. This means Nintendo can't tell if anything, including homebrew or modded games crashed, and Atmosphere dumps the crash log to the microSD Card to help homebrew developers. However, Nintendo still receives information about what is being played, and general system report information. - Atmosphere is not a silver bullet, and this does not mean that Nintendo won't decide to ban people for harmless homebrew in the future. If you are scared to get banned then don't use homebrew for now. Atmosphere now supports emuMMC (emuNAND): a copy of Switch system software, run entirely from the SD card instead. + Atmosphere is not a silver bullet, and this does not mean that Nintendo won't decide to ban people for harmless homebrew in the future. If you are scared to get banned then don't use homebrew for now. Atmosphere now supports emuMMC (emuNAND): a copy of Switch system software, run entirely from the microSD Card instead. This erases ban risks due to the fact that emuMMC is run in a quarantined, offline state, not touching the internal memory. You are still able to boot into original firmware to play online. - For patched units reliant on deja-vu, sysNAND will always have to be on a firmware below 4.1. For switches from 5.0 to 7.0.1 deja-vu isn't quite out yet but is coming soon. (Also please note that firmwares 8.0.0+ will never work with deja-vu) You can use an updated emuMMC dedicated to online/clean play, while your sysNAND is used offline for custom firmware. - + For patched units reliant on deja-vu, sysNAND will always have to be on a firmware below 4.1. For Switch units from 5.0 to 7.0.1 deja-vu isn't quite out yet but is coming soon. (Also please note that firmwares 8.0.0+ will never work with deja-vu) You can use an updated emuMMC dedicated to online/clean play, while your sysNAND is used offline for custom firmware. + We do not recommend the use of ReiNX or SX OS for many reasons, primary among them that they use lots of assets from Atmosphere and offer no real benefit that Atmosphere does not offer anyway. We also do not recommend Kosmos, as its large amount of extras on top of regular Atmosphere make it difficult to troubleshoot strange issues. All of these alternative CFWs also tend to use non-conventional setups which can cause issues that make it difficult to troubleshoot, which is another reason we prefer using Atmosphere. @@ -118,34 +118,34 @@ Homebrew can come in two different formats, namely in `nro` files and in `bin` files. - - `nro` Files are placed in the `switch` folder on your SD card and can be launched using the Homebrew menu. + - `nro` Files are placed in the `/switch` folder on your microSD Card and can be launched using the Homebrew menu. - `bin` This format is used as a payload and is to be pushed in RCM using a payload launcher like tegrarcmgui on windows and fusee-interfacee-tk on other operating systems. - + **Homebrew risks** *Be careful with launching downloaded homebrew! If you don't know the source, it's best not to launch it.* *Homebrew can potentially damage your system! Atmosphere provides protections against common bricking methods, but these are not guaranteed to always work!* -## What microSD card/format should I use? +## What microSD Card/format should I use? !!!tip "" - microSD cards that are 32GB or smaller can be used for homebrew, but are not recommended as these will not permit you to have a full NAND dump and/or an emuMMC on them. + microSD Cards that are 32GB or smaller can be used for homebrew, but are not recommended as these will not permit you to have a full NAND dump and/or a full-sized emuMMC on them. - The recommended microSD card size is 128GB. This will permit you to make a full NAND dump as well as having enough space to run an emuNAND in the future while also having adequate space for homebrew. + The recommended microSD Card size is 128GB. This will permit you to make a full NAND dump as well as having enough space to run an emuNAND in the future while also having adequate space for homebrew. The recommended filesystem format is FAT32. While the Switch supports exFAT through an additional update from Nintendo, this filesystem is prone to corruption and as a result is not advisable. -## Fake microSD cards +## Fake microSD Cards !!!tip "" - Do not buy microSD cards from sites like eBay. - These microSD cards are often fake and do not have the advertised amount of storage and will result in data corruption if used. - Amazon has had some problems with fake SD cards, so we recommend buying them at a physical store. Even on trustworthy sites, *always, always check reviews on a product before buying!!* + Do not buy microSD Cards from sites like eBay or AliExpress. + These microSD Cards are often fake and do not have the advertised amount of storage and will result in data corruption if used. + Even Amazon has had some problems with fake microSD Cards, so we recommend buying them at a physical store. Even on trustworthy sites, *always, always check reviews on a product before buying!!* + - - If you suspect your microSD card is fake or damaged, see the instructions here to verify the integrity of your SD card. + If you suspect your microSD Card is fake or damaged, see the instructions here to verify the integrity of your microSD Card. @@ -155,10 +155,10 @@ !!!tip "" This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your homebrew, you will need to unset the archive bit with Hekate. - 1. Send the Hekate payload to your Switch by following these instructions: [here](https://nh-server.github.io/switch-guide/user_guide/emummc/sending_payload/) + 1. Send the Hekate payload to your Switch by following these instructions: [here](https://nh-server.github.io/switch-guide/user_guide/emuMMC/sending_payload/) 2. Click on `Tools` on the top menu bar - 3. In the bottom left corner click on `Archive bit * AutoRCM` + 3. In the bottom left corner click on `Archive bit * autoRCM` 4. Click on `Fix Archive bit` - this might take a while 5. Press `Close` in the top right corner 6. Press `Home` in the top menu bar to get back from where you started - 7. Follow the instructions at the Launching CFW page [here](https://nh-server.github.io/switch-guide/user_guide/emummc/launching_cfw/) to launch Atmosphere. + 7. Follow the instructions at the Launching CFW page [here](https://nh-server.github.io/switch-guide/user_guide/emuMMC/launching_cfw/) to launch Atmosphere. diff --git a/docs/index.md b/docs/index.md index 458a5c30..ed5cc35d 100644 --- a/docs/index.md +++ b/docs/index.md @@ -60,7 +60,7 @@ A guide collaboration between Nintendo Homebrew's Helpers and Staff, from stock - This method is not covered by the guide, but you can read more about it at [this website](https://mologie.github.io/nxboot/) - You will also need a micro SD card that is at least 64 gigabytes or larger if you plan on following this guide through the emummc path, which is safer and strongly recommended. If you must use a smaller SD card, it is possible with the sysmmc path, but strongly not recommended. + You will also need a microSD Card that is at least 64 gigabytes or larger if you plan on following this guide through the emuMMC path, which is safer and strongly recommended. If you must use a smaller microSD Card, it is possible with the sysMMC path, but strongly not recommended. Finally, you will need a way to access Recovery Mode. (This will be further explained in the "Entering RCM section") @@ -74,4 +74,4 @@ It is advised that you read the entire guide from start to finish one or more ti   -#### [Continue to Getting Started ](user_guide/getting_started.md) +#### [Continue to Getting Started ](user_guide/getting_started.md) diff --git a/docs/user_guide/emummc/launching_cfw.md b/docs/user_guide/emummc/launching_cfw.md index 18249507..bc398724 100644 --- a/docs/user_guide/emummc/launching_cfw.md +++ b/docs/user_guide/emummc/launching_cfw.md @@ -14,7 +14,7 @@ Unlike systems such as the DSi, Wii, or 3DS, Switch CFW is currently volatile. I !!! tip "" 1. Power on your Switch into RCM, and inject the Hekate payload 2. Navigate to `Launch` using the touch screen - 3. Find `Atmosphere FSS0 EmuMMC` and launch it + 3. Find `Atmosphere FSS0 emuMMC` and launch it Your Switch is now booting into Atmosphere. @@ -30,12 +30,12 @@ To verify Atmosphere launched properly, open the Settings applet, and navigate t ### Launching the Homebrew Menu You will now be able to launch the Homebrew Menu by opening the album or by holding the R button while launching any game (including demos/cartridges), or application (e.g. Youtube/Hulu). If R is not held, the game or application will launch like normal. - + !!! warning "A note about using the album for the Homebrew Menu" - - Using the album for the Homebrew Menu instead of a game or application has several limitations, including but not limited to: a smaller amount of available memory (RAM), as well as being unable to launch a full-featured web browser. It is strongly recommended to launch homebrew through applications or games instead. If your games don't show up as "installed" on your switch, copy the contents of the `Nintendo` folder from the root of the sd card to the `emummc/RAW1/Nintendo` folder - + - Using the album for the Homebrew Menu instead of a game or application has several limitations, including but not limited to: a smaller amount of available memory (RAM), as well as being unable to launch a full-featured web browser. It is strongly recommended to launch homebrew through applications or games instead. If your games don't show up as "installed" on your Switch, copy the contents of the `Nintendo` folder from the root of the microSD Card to the `emummc/RAW1/Nintendo` folder. + !!! tip "Adding new applications" - - Place homebrew applications (`.nro` files) into the `switch` folder on your SD card. + - Place homebrew applications (`.nro` files) into the `/switch` folder on your microSD Card.   @@ -44,17 +44,17 @@ You will now be able to launch the Homebrew Menu by opening the album or by hold !!! tip "" - JKSV is a save manager, it can dump and restore saves from/to your system. For more information, see [Save Management](../../extras/save_management.md) - - FTPD is a ftp tool for connecting your Switch's sd card wirelessly to your pc. Tools like WinSCP can connect to your switch on `(ip of switch):5000` + - FTPD is a FTP tool for connecting your Switch's microSD Card wirelessly to your PC. Tools like WinSCP can connect to your Switch on `(ip of Switch):5000` - NX-Shell is a file explorer for the Switch. You can move files, listen to mp3's, view images etc. - NXThemeInstaller is a theme installer app. See the [Theming section of our guide](../../extras/theming.md) for more information - - hbappstore is a homebrew app store where a large collection of switch homebrew is kept. + - hbappstore is a homebrew app store where a large collection of Switch homebrew is kept.   ### Updating your setup !!! tip "" - Whenever a new Switch firmware update releases you may need to update your files to be able to use CFW on the new version. Make sure to follow the instructions on [this page](../../extras/updating.md) to update your setup correctly. \ No newline at end of file + Whenever a new Switch firmware update releases you may need to update your files to be able to use CFW on the new version. Make sure to follow the instructions on [this page](../../extras/updating.md) to update your setup correctly. diff --git a/docs/user_guide/emummc/linux_partitioning.md b/docs/user_guide/emummc/linux_partitioning.md index 57c65c68..c85f04a6 100644 --- a/docs/user_guide/emummc/linux_partitioning.md +++ b/docs/user_guide/emummc/linux_partitioning.md @@ -1,7 +1,7 @@ ## Manual Linux Preperations -!!! danger "SD card identification" - Make 100% sure you get your microSD card during the following steps. If you are not careful, you can end up wiping your entire linux filesystem. We are not responsible for data loss when doing this. +!!! danger "microSD Card identification" + Make 100% sure you get your microSD Card during the following steps. If you are not careful, you can end up wiping your entire linux filesystem. We are not responsible for data loss when doing this. !!! warning "Who is this for?" This section is for the people who do not want to let a tool automatically modify their sd, and want to do it manually for more control over what gets created. This section helps with that @@ -14,9 +14,9 @@ ### Manual instructions (Linux) 1. Open a terminal. -2. Run `sudo fdisk -l`. Enter your password if prompted. This will print information about all drives connected to your computer. Use the information about the file size to identify your microSD card. Specifically, take note of the line after `Disk `. This will look something like `/dev/xxx`, where `xxx` will differ on your system (can also be longer than three characters). It does NOT end with a number. +2. Run `sudo fdisk -l`. Enter your password if prompted. This will print information about all drives connected to your computer. Use the information about the file size to identify your microSD Card. Specifically, take note of the line after `Disk `. This will look something like `/dev/xxx`, where `xxx` will differ on your system (can also be longer than three characters). It does NOT end with a number. 3. Run `sudo gparted `. Enter your password if prompted. Replace `` in the command with the information you obtained from step 2. -4. You will see a list of partitions on your SD card. Go to `Device` -> `Create partition table`. Select `msdos` as the partition type and select Apply. This will remove all existing partitions from your SD card. +4. You will see a list of partitions on your microSD Card. Go to `Device` -> `Create partition table`. Select `msdos` as the partition type and select Apply. This will remove all existing partitions from your microSD Card. 5. Go to `Partition` -> `New`. And do the following: - Set `Free space following (MiB)` to `30000`. - Set `Free space preceding (MiB)` to `1`. @@ -38,9 +38,9 @@ To fix this, follow these instructions: 1. Open a terminal. - 2. Run `sudo fdisk -l`. Enter your password if prompted. This will print information about all drives connected to your computer. Use this information to determine the FAT32 partition on your SD card. Specifically, note the value under the column `Device`. This will look something like `/dev/xxx`, where `xxx` will differ on your system (can also be longer than three characters). It always ends with a number! + 2. Run `sudo fdisk -l`. Enter your password if prompted. This will print information about all drives connected to your computer. Use this information to determine the FAT32 partition on your microSD Card. Specifically, note the value under the column `Device`. This will look something like `/dev/xxx`, where `xxx` will differ on your system (can also be longer than three characters). It always ends with a number! 3. Run `sudo mkdosfs -s 64 -F 32 -I`. Enter your password if prompted. Replace `` with the value you got from step 2. - 4. Wait until it finishes running. Depending on the size of your microSD card, this might take a while. + 4. Wait until it finishes running. Depending on the size of your microSD Card, this might take a while. 5. Run `sudo fatlabel "sMicroSD"`. Enter your password if prompted. Replace `` with the value you got from step 2.   diff --git a/docs/user_guide/emummc/making_emummc.md b/docs/user_guide/emummc/making_emummc.md index 2fcb7c4e..26b79629 100644 --- a/docs/user_guide/emummc/making_emummc.md +++ b/docs/user_guide/emummc/making_emummc.md @@ -1,17 +1,17 @@ -# Making the Emummc, getting keys, and making essential backups +# Making the emuMMC, getting keys, and making essential backups   ### Making the emuMMC !!!warning "Before you start" - If you don't plan on using the internet on your emuMMC, it is recommended to boot your switch normally and delete all the wifi networks. You can add them back to your sysnand after completing this guide. + If you don't plan on using the internet on your emuMMC, it is recommended to boot your switch normally and delete all the wifi networks. You can add them back to your sysNAND after completing this guide. !!!tip "" 1. Enter RCM and inject the Hekate payload 2. Use the touch screen to navigate to `emuMMC` 3. Tap on `Create emuMMC`, then select `SD Partition` - 4. Tap on `Part 1`. It will start making the emummc now. After it's done return to the emuMMC menu using the `Close` buttons + 4. Tap on `Part 1`. It will start making the emuMMC now. After it's done return to the emuMMC menu using the `Close` buttons 5. Tap on `Change emuMMC`, then `SD RAW 1` 6. Go back to the main menu @@ -25,7 +25,7 @@ Once the backup is finished, **keep it somewhere safe.** The best backup is the one you have but never need, and the worst backup is the one you need but never made. To save space, it's recommended to compress the end-result with a `.zip` file or something similar. - It's highly recommended that you use an SD card that is formatted to FAT32 and has at least 32 gigabytes of space free. This will still work on smaller cards, but it's not ideal. + It's highly recommended that you use an microSD Card that is formatted to FAT32 and has at least 32 gigabytes of space free. This will still work on smaller cards, but it's not ideal. ### Instructions @@ -33,20 +33,20 @@ 1. Enter RCM and inject the Hekate payload 2. Use the touch screen to navigate to `Tools` and then `Backup eMMC` 3. Tap on `eMMC BOOT0 & BOOT1` - - This should only take a few seconds, but if your SD card is very slow, it may take around a minute. + - This should only take a few seconds, but if your microSD Card is very slow, it may take around a minute. 4. Tap on `Close` to continue, then tap on `eMMC RAW GPP` - - This will take a long time. Expect it to take between 10 minutes to an hour (or more, if your SD card is very slow). - - On FAT32 SD cards or cards that have less than 32 gigabytes of space available, the NAND will be split into 1 or 2 gigabyte parts. + - This will take a long time. Expect it to take between 10 minutes to an hour (or more, if your microSD Card is very slow). + - On FAT32 microSD Cards or cards that have less than 32 gigabytes of space available, the NAND will be split into 1 or 2 gigabyte parts. - Hekate will stop producing these parts when it runs out of space. When this happens, do the following: - Power off your system - - Insert your SD card into your PC - - Move all files from the `backup` folder on your SD card to a safe location on your PC - - Insert your SD card into your Switch + - Insert your microSD Card into your PC + - Move all files from the `backup` folder on your microSD Card to a safe location on your PC + - Insert your microSD Card into your Switch - Enter RCM again, inject Hekate again, and continue the backup by tapping on `Tools` > `Backup eMMC` > `eMMC RAW GPP` - Repeat the process until the NAND is completely dumped 5. Press `Close` > `Home` > `Power Off` - 6. Insert your SD card into your PC - 7. Copy the `backup` folder on your SD card to a safe location on your PC + 6. Insert your microSD Card into your PC + 7. Copy the `backup` folder on your microSD Card to a safe location on your PC   @@ -61,11 +61,11 @@ 1. Enter RCM and inject the Hekate payload. 2. Tap the `Payloads` option, then press Lockpick_RCM.bin. 3. If Lockpick_RCM asks you to select between SysNAND or EmuNAND, choose SysNAND by navigating with the volume buttons and pressing the power button. If not, continue with step 4. - 4. Lockpick_RCM should now inform you that your keys have been saved to `/switch/prod.keys` on the SD card. + 4. Lockpick_RCM should now inform you that your keys have been saved to `/switch/prod.keys` on the microSD Card. 5. Press any button to return to the main menu. 6. Navigate to 'Power off' with the volume buttons and select it with the power button. - 7. Insert your SD card into your PC. - 8. Copy `prod.keys` from the `switch` folder on your SD card to a safe location on your PC (it is suggested to copy it to the same place that you copied your NAND backup to). + 7. Insert your microSD Card into your PC. + 8. Copy `prod.keys` from the `switch` folder on your microSD Card to a safe location on your PC (it is suggested to copy it to the same place that you copied your NAND backup to).   diff --git a/docs/user_guide/emummc/partitioning_sd.md b/docs/user_guide/emummc/partitioning_sd.md index ec90bdf6..6e50bd2a 100644 --- a/docs/user_guide/emummc/partitioning_sd.md +++ b/docs/user_guide/emummc/partitioning_sd.md @@ -1,10 +1,10 @@ -# Partitioning the SD Card +# Partitioning the microSD Card -!!!warning "This will delete everything on your sd card" - Doing this will delete all your data from your sd card, be warned! +!!!warning "This will delete everything on your microSD Card" + Doing this will delete all your data from your microSD Card, be warned! !!! warning "Back up your existing Nintendo folder" - Before we start, if you are using a microSD card already as a storage device for your games, you will want to back up your `Nintendo` folder that is on the root of your microSD card to a safe place on your computer. This folder contains your downloaded games and game updates. + Before we start, if you are using a microSD Card already as a storage device for your games, you will want to back up your `Nintendo` folder that is on the root of your microSD Card to a safe place on your computer. This folder contains your downloaded games and game updates. ----- @@ -16,20 +16,20 @@ What you need: ### Instructions -1. Inject the TegraExplorer payload with your 64GB (or larger) SD card inserted into your Switch. +1. Inject the TegraExplorer payload with your 64GB (or larger) microSD Card inserted into your Switch. - If you forgot how to do this, re-read the [sending payload](sending_payload.md) section of the guide. -2. Navigate to `Partition the sd` and press the A button to enter the SD format menu. - - If you can't find the Partition the sd option, make sure that your SD card is inserted and select Mount SD. -3. Navigate to `Fat32 + EmuMMC` and press the A button to confirm. -4. Read the warning, and select Yes to partition & format your SD card. - - Note: This will delete all data on your SD card. Make sure you backed up your Nintendo folder! +2. Navigate to `Partition the SD` and press the A button to enter the SD format menu. + - If you can't find the Partition the sd option, make sure that your microSD Card is inserted and select Mount SD. +3. Navigate to `FAT32 + emuMMC` and press the A button to confirm. +4. Read the warning, and select Yes to partition & format your microSD Card. + - Note: This will delete all data on your microSD Card. Make sure you backed up your Nintendo folder! - This should not take more than a few seconds. 5. Press any button to return to the main menu. -6. Navigate to `Reboot to RCM` and press the A button to reboot to RCM. It's now safe to eject your sd card for the next part of the guide. +6. Navigate to `Reboot to RCM` and press the A button to reboot to RCM. It's now safe to eject your microSD Card for the next part of the guide. !!! warning "Windows complaining about an unreadable drive" - If you get the issue that Windows says the SD card is unreadable and wants to format it, do not format! This is likely your emuMMC partition. After partitioning your sd, your sd will show up as 2 drives on your pc. Use the drive that can be accessed - + If you get the issue that Windows says the microSD Card is unreadable and wants to format it, do not format! This is likely your emuMMC partition. After partitioning your sd, your sd will show up as 2 drives on your PC. Use the drive that can be accessed +   #### [Continue to SD Preparations ](sd_preparation.md) diff --git a/docs/user_guide/emummc/sd_preparation.md b/docs/user_guide/emummc/sd_preparation.md index bfd44788..bb4dac5a 100644 --- a/docs/user_guide/emummc/sd_preparation.md +++ b/docs/user_guide/emummc/sd_preparation.md @@ -1,6 +1,6 @@ # SD Preparation -We will now place the required files for the Atmosphere custom firmware and some additional homebrew files on the SD card. +We will now place the required files for the Atmosphere custom firmware and some additional homebrew files on the microSD Card. Atmosphere has its own bootloader, called fusee. For the purposes of this guide we will be using Hekate instead, so that we can back up the system's NAND (internal storage) and take advantage of other advanced features in the future. @@ -29,26 +29,26 @@ Atmosphere has its own bootloader, called fusee. For the purposes of this guide ### Instructions !!! tip "" - 1. Insert your Switch's SD card into your PC - 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your SD card - 3. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your SD card - 4. Copy the `bootloader` folder from the `bootlogos.zip` file to the root of your SD card + 1. Insert your Switch's microSD Card into your PC + 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD Card + 3. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your microSD Card + 4. Copy the `bootloader` folder from the `bootlogos.zip` file to the root of your microSD Card - If you're asked to merge the bootloader folders, do so. - 5. Copy `hekate_ipl.ini` to the `bootloader` folder on your SD card - 6. Copy `Lockpick_RCM.bin` to the `/bootloader/payloads` folder on your SD card - 7. Create a folder named `hosts` inside the `atmosphere` folder on your SD card, and put `emummc.txt` in it - 8. Create a folder named `appstore` inside the `switch` folder on your SD card, and put `appstore.nro` in it - 9. Copy `JKSV.nro`, `ftpd.nro`, `NX-Shell.nro` and `NxThemesInstaller.nro` to the `switch` folder on your SD card - 10. If you were already using your microSD card as a storage device for your games and backed up the Nintendo folder before partitioning your microSD card, please place it back on the root of your microSD card. - 11. Reinsert your SD card back into your Switch - - !!!danger "About emummc.txt" + 5. Copy `hekate_ipl.ini` to the `bootloader` folder on your microSD Card + 6. Copy `Lockpick_RCM.bin` to the `/bootloader/payloads` folder on your microSD Card + 7. Create a folder named `hosts` inside the `atmosphere` folder on your microSD Card, and put `emuMMC.txt` in it + 8. Create a folder named `appstore` inside the `switch` folder on your microSD Card, and put `appstore.nro` in it + 9. Copy `JKSV.nro`, `ftpd.nro`, `NX-Shell.nro` and `NxThemesInstaller.nro` to the `switch` folder on your microSD Card + 10. If you were already using your microSD Card as a storage device for your games and backed up the Nintendo folder before partitioning your microSD Card, please place it back on the root of your microSD Card. + 11. Reinsert your microSD Card back into your Switch + + !!!danger "About emuMMC.txt" Putting the `emummc.txt` file provided by this guide into `/atmosphere/hosts` will prevent your emuMMC (emuNAND) from connecting to Nintendo. Not doing this will likely result in a ban. !!! tip "" - Your SD card should look similar to this. The `Nintendo` folder will not be present if your switch has not already booted with the microSD card inserted. + Your microSD Card should look similar to this. The `Nintendo` folder will not be present if your switch has not already booted with the microSD Card inserted. ![sdfilesimg](../img/sdfiles.png)   -#### [Continue to Making EmuMMC ](making_emummc.md) +#### [Continue to Making emuMMC ](making_emummc.md) diff --git a/docs/user_guide/getting_started.md b/docs/user_guide/getting_started.md index 2f1875c9..23ee6335 100644 --- a/docs/user_guide/getting_started.md +++ b/docs/user_guide/getting_started.md @@ -2,11 +2,12 @@ ### Finding your serial number -The first thing to do is determine if your Switch is vulnerable to fusee-gelee, the exploit we will be using to launch CFW. +The first thing to do is determine if your Switch is vulnerable to the RCM exploit, which is used to launch into CFW. -This vulnerability was independently discovered by several different Switch hacking teams, and multiple variants of it were released to the public in April 2018 after a 90-day disclosure period ended. Nintendo and NVIDIA were made aware of the issue before the public release as a result, and Switch systems that are not vulnerable to the exploit started being spotted in the wild in July 2018. NVIDIA [publicly acknowledged the flaw](https://nvidia.custhelp.com/app/answers/detail/a_id/4660/~/security-notice%3A-nvidia-tegra-rcm-vulnerability) in April as well. In July 2019, Nintendo announced updated consoles, a handheld variant of the Switch called the Switch Lite (HDH-001), and a new model of original Switch (HAC-001-01) with better battery life. Both of these new models use a new processor called the T210b01 (also known as T214 and Mariko) with a new bootROM, and are not hackable at the current time. +This vulnerability, called fusee-gelee (CVE-2018-6242), was independently discovered by several different Switch hacking teams. Multiple variants of it were released to the public in April 2018 after a 90-day disclosure period ended. Nintendo and NVIDIA were made aware of the issue before the public release as a result, and Switch systems that are not vulnerable to the exploit started being spotted in the wild in July 2018. +NVIDIA [publicly acknowledged the flaw](https://nvidia.custhelp.com/app/answers/detail/a_id/4660/~/security-notice%3A-nvidia-tegra-rcm-vulnerability) in April. In July 2019, Nintendo announced updated consoles, a handheld variant of the Switch called the Switch Lite (HDH-001), and a new model of original Switch (HAC-001(-01)) with better battery life. Both of these new models use a new processor called the T210b01 (also known as T214 and Mariko) with a new bootROM, and have no software exploits which lead into custom firmware. -Patched and Mariko units can be identified by their serial number. This number can be found on the bottom of your Switch adjacent to the USB-C port, or in the Settings applet at **System -> Serial Information**. +Patched and Mariko units can be identified by their serial number. This number can be found on the bottom of your Switch adjacent to the USB-C port, or in the Settings applet at **System -> Serial Information**.   @@ -20,10 +21,10 @@ Patched and Mariko units can be identified by their serial number. This number c ### Determining if your Switch is vulnerable -The homebrew community has crowdsourced a list of known serial numbers which are vulnerable to fusee-gelee. +The homebrew community has crowdsourced a list of known serial numbers which are vulnerable to fusee-gelee. -- If your serial number is on this list as "potentially patched", follow the guide and see if your system works. -- If your serial number is listed as "patched", there is nothing you can do at this time. +- If your serial number is on this list as "potentially patched", follow the guide and see if your system works. +- If your serial number is listed as "patched", there is nothing you can do at this time. - If your system is patched, it is highly advised to keep it on 7.0.1 or lower, if possible, as there may be a vulnerability for these versions in the far future. **DO NOT update patched consoles past 7.0.1 if you want to ever have a chance of running homebrew and/or CFW on them.** !!! tip "Notice" @@ -73,7 +74,7 @@ The following information is based on [this GBATemp thread](https://gbatemp.net/   -| Firmware Version | Unpatched Switches (HAC-001) | Patched Switches (HAC-001) | "New" Switch (HAC-001-01) | Switch Lite (HDH-001) | +| Firmware Version | Unpatched Switches (HAC-001) | Patched Switches (HAC-001) | "New" Switch (HAC-001-01) | Switch Lite (HDH-001) | |:---------------|:--------------------------------|:---------------------------|:----------------------------|:-----------------------| | 1.0.0 | Nereba or [**RCM**](rcm.md) | **N/A** | **N/A** | **N/A** | | 2.0.0 - 3.0.2 | Caffeine or [**RCM**](rcm.md) | **N/A** | **N/A** | **N/A** | diff --git a/docs/user_guide/rcm.md b/docs/user_guide/rcm.md index ba66a7db..ef586f87 100644 --- a/docs/user_guide/rcm.md +++ b/docs/user_guide/rcm.md @@ -1,21 +1,21 @@ # RCM -RCM (short for ReCovery Mode) is a mode for the switch that allows nintendo to send the switch commands to do various things. People found out that on unpatched switches, you could send a payload, and then quickly copy it into the memory buffer behind the stack, overflowing the memory buffer into the stack, meaning you smash the stack and get full access to everything on the system. We use it here to launch atmosphere. +RCM (short for ReCovery Mode) is a mode for the Switch that allows nintendo to send the Switch commands to do various things. It was discovered, that on unpatched Switch units, one could send a payload, and then quickly copy it into the memory buffer behind the stack, overflowing the memory buffer into the stack, leading to a smashed stack early in the booting process. We use it here to launch atmosphere. !!!tip "emuNAND vs emuMMC vs sysNAND" - sysNAND stands for System NAND, meaning the internal storage in your actual Switch. - - emuNAND stands for emulated NAND, this means that your entire NAND (system memory) will run off your microSD card with Custom Firmware (CFW). This NAND's contents (games, applications, saves, etc.) are *completely separate* from your sysNAND. - - emuMMC is the name for the currently used implementation of emuNAND on Switch. It has no difference from emuNAND besides name. + - emuNAND stands for emulated NAND, this means that your entire NAND (system memory) will run off your microSD Card with Custom Firmware (CFW). This NAND's contents (games, applications, saves, etc.) are *completely separate* from your sysNAND. + - emuMMC is the name for the implementation of emuNAND on Switch. The suffixes **-MMC** and **-NAND** are interchangable. ---- ### emuNAND CFW (**Recommended**) !!!tip "What's needed for emuNAND" - - A microSD card that's 64GB or larger + - A microSD Card that's 64GB or larger #### Pros of using emuNAND over sysNAND CFW: - + - Using homebrew applications such as save editors, or cheating in games offline without "dirtying" or affecting sysNAND, allowing sysNAND to be used online without ban risk. - Allowing users on patched Switches using Caffeine to update their emuNAND to latest and use it online, keeping sysNAND at a lower vulnerable version. @@ -27,7 +27,7 @@ RCM (short for ReCovery Mode) is a mode for the switch that allows nintendo to s ### sysNAND CFW (**Not Recommended**) -This is for the people who don't have an 64GB microSD card or larger, or who don't want emuNAND for whatever reason. +This is for the people who don't have an 64GB microSD Card or larger, or who don't want emuNAND for whatever reason. !!!note "Note" If you set up an emuNAND you may still have CFW on your sysNAND if you choose to use it. You do not have to follow the guide linked below; all the files are the same, you simply select "sysNAND CFW" from Hekate/Nyx. diff --git a/docs/user_guide/sysnand/launching_cfw.md b/docs/user_guide/sysnand/launching_cfw.md index 5d72393b..385987a4 100644 --- a/docs/user_guide/sysnand/launching_cfw.md +++ b/docs/user_guide/sysnand/launching_cfw.md @@ -27,12 +27,12 @@ To verify Atmosphere launched properly, open the Settings applet, and navigate t ### Launching the Homebrew Menu You will now be able to launch the Homebrew Menu by opening the album or by holding the R button while launching any game (including demos/cartridges), or application (e.g. Youtube/Hulu). If R is not held, the game or application will launch like normal. - + !!! warning "A note about using the album for the Homebrew Menu" - Using the album for the Homebrew Menu instead of a game or application has several limitations, including but not limited to: a smaller amount of available memory (RAM), as well as being unable to launch a full-featured web browser. It is strongly recommended to launch homebrew through applications or games instead. - + !!! tip "Adding new applications" - - Place homebrew applications (`.nro` files) into the `switch` folder on your SD card. + - Place homebrew applications (`.nro` files) into the `/switch` folder on your microSD Card.   @@ -41,17 +41,17 @@ You will now be able to launch the Homebrew Menu by opening the album or by hold !!! tip "" - JKSV is a save manager, it can dump and restore saves from/to your system. For more information, see [Save Management](../../extras/save_management.md) - - FTPD is a ftp tool for connecting your Switch's sd card wirelessly to your pc. Tools like WinSCP can connect to your switch on `(ip of switch):5000` + - FTPD is a FTP tool for connecting your Switch's microSD Card wirelessly to your PC. Tools like WinSCP can connect to your Switch on `(ip of Switch):5000` - NX-Shell is a file explorer for the Switch. You can move files, listen to mp3's, view images etc. - NXThemeInstaller is a theme installer app. See the [Theming section of our guide](../../extras/theming.md) for more information - - hbappstore is a homebrew app store where a large collection of switch homebrew is kept. + - hbappstore is a homebrew app store where a large collection of Switch homebrew is kept.   ### Updating your setup !!! tip "" - Whenever a new Switch firmware update releases you may need to update your files to be able to use CFW on the new version. Make sure to follow the instructions on [this page](../../extras/updating.md) to update your setup correctly. \ No newline at end of file + Whenever a new Switch firmware update releases you may need to update your files to be able to use CFW on the new version. Make sure to follow the instructions on [this page](../../extras/updating.md) to update your setup correctly. diff --git a/docs/user_guide/sysnand/making_essential_backups.md b/docs/user_guide/sysnand/making_essential_backups.md index 79d2e5bf..d48d9768 100644 --- a/docs/user_guide/sysnand/making_essential_backups.md +++ b/docs/user_guide/sysnand/making_essential_backups.md @@ -12,7 +12,7 @@ Once the backup is finished, **keep it somewhere safe.** The best backup is the one you have but never need, and the worst backup is the one you need but never made. To save space, it's recommended to compress the end-result with a `.zip` file or something similar. - It's highly recommended that you use an SD card that is formatted to FAT32 and has at least 32 gigabytes of space free. This will still work on smaller cards, but it's not ideal. + It's highly recommended that you use an microSD Card that is formatted to FAT32 and has at least 32 gigabytes of space free. This will still work on smaller cards, but it's not ideal. ### Instructions @@ -21,20 +21,20 @@ 1. Enter RCM and inject the Hekate payload 2. Use the touch screen to navigate to `Tools` and then `Backup eMMC` 3. Tap on `eMMC BOOT0 & BOOT1` - - This should only take a few seconds, but if your SD card is very slow, it may take around a minute. + - This should only take a few seconds, but if your microSD Card is very slow, it may take around a minute. 4. Tap on `Close` to continue, then tap on `eMMC RAW GPP` - - This will take a long time. Expect it to take between 10 minutes to an hour (or more, if your SD card is very slow). - - On FAT32 SD cards or cards that have less than 32 gigabytes of space available, the NAND will be split into 1 or 2 gigabyte parts. + - This will take a long time. Expect it to take between 10 minutes to an hour (or more, if your microSD Card is very slow). + - On FAT32 microSD Cards or cards that have less than 32 gigabytes of space available, the NAND will be split into 1 or 2 gigabyte parts. - Hekate will stop producing these parts when it runs out of space. When this happens, do the following: - Power off your system - - Insert your SD card into your PC - - Move all files from the `backup` folder on your SD card to a safe location on your PC - - Insert your SD card into your Switch + - Insert your microSD Card into your PC + - Move all files from the `/backup` folder on your microSD Card to a safe location on your PC + - Insert your microSD Card into your Switch - Enter RCM again, inject Hekate again, and continue the backup by tapping on `Tools` > `Backup eMMC` > `eMMC RAW GPP` - Repeat the process until the NAND is completely dumped 5. Press `Close` > `Home` > `Power Off` - 6. Insert your SD card into your PC - 7. Copy the `backup` folder on your SD card to a safe location on your PC + 6. Insert your microSD Card into your PC + 7. Copy the `backup` folder on your microSD Card to a safe location on your PC   @@ -51,12 +51,12 @@ 1. Enter RCM and inject the Hekate payload. 2. Tap the `Payloads` option, then press Lockpick_RCM.bin. 3. If Lockpick_RCM asks you to select between SysNAND and EmuNAND, choose SysNAND by navigating with the volume buttons and pressing the power button. If not, continue with step 4. - 4. Lockpick_RCM should now inform you that your keys have been saved to `/switch/prod.keys` on the SD card. + 4. Lockpick_RCM should now inform you that your keys have been saved to `/switch/prod.keys` on the microSD Card. 5. Press any button to return to the main menu. 6. Navigate to 'Power off' with the volume buttons and select it with the power button. - 7. Insert your SD card into your PC. - 8. Copy `prod.keys` from the `switch` folder on your SD card to a safe location on your PC (it is suggested to copy it to the same place that you copied your NAND backup to). - + 7. Insert your microSD Card into your PC. + 8. Copy `prod.keys` from the `switch` folder on your microSD Card to a safe location on your PC (it is suggested to copy it to the same place that you copied your NAND backup to). +   #### [Continue to Launching CFW ](launching_cfw.md) diff --git a/docs/user_guide/sysnand/sd_preparation.md b/docs/user_guide/sysnand/sd_preparation.md index 57476ec6..00784cfd 100644 --- a/docs/user_guide/sysnand/sd_preparation.md +++ b/docs/user_guide/sysnand/sd_preparation.md @@ -1,13 +1,13 @@ # SD Preparation -We will now place the required files for the Atmosphere custom firmware and some additional homebrew files on the SD card. +We will now place the required files for the Atmosphere custom firmware and some additional homebrew files on the microSD Card. Atmosphere has its own bootloader, called fusee. For the purposes of this guide we will be using Hekate instead, so that we can back up the system's NAND (internal storage) and take advantage of other advanced features in the future.   !!! danger "FAT32 vs exFAT" - Your SD card will need to be formatted as either FAT32 or exFAT, but FAT32 is recommended as it is more stable and will work out of the box with the Switch's operating system. Using exFAT on the Switch should be avoided due to the filesystem being prone to corruption, and sometimes preventing custom firmware from booting. You will also need to install the exFAT update for your Switch, which is downloaded when you insert an exFAT formatted SD card in to your Switch. Note that this will update your console and requires an internet connection. + Your microSD Card will need to be formatted as either FAT32 or exFAT, but FAT32 is recommended as it is more stable and will work out of the box with the Switch's operating system. Using exFAT on the Switch should be avoided due to the filesystem being prone to corruption, and sometimes preventing custom firmware from booting. You will also need to install the exFAT update for your Switch, which is downloaded when you insert an exFAT formatted microSD Card in to your Switch. Note that this will update your console and requires an internet connection. !!! warning "File name extensions" @@ -33,19 +33,19 @@ Atmosphere has its own bootloader, called fusee. For the purposes of this guide ### Instructions !!! tip "" - 1. Insert your Switch's SD card into your PC - 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your SD card - 3. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your SD card - 4. Copy the `bootloader` folder from the `bootlogos.zip` file to the root of your SD card + 1. Insert your Switch's microSD Card into your PC + 2. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD Card + 3. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your microSD Card + 4. Copy the `bootloader` folder from the `bootlogos.zip` file to the root of your microSD Card - If you're asked to merge the bootloader folders, do so. - 5. Copy `hekate_ipl.ini` to the `bootloader` folder on your SD card - 6. Copy `Lockpick_RCM.bin` to the `/bootloader/payloads` folder on your SD card - 7. Create a folder named `appstore` inside the `switch` folder on your SD card, and put `appstore.nro` in it - 8. Copy `JKSV.nro`, `ftpd.nro`, `NX-Shell.nro` and `NxThemesInstaller.nro` to the `switch` folder on your SD card - 9. Reinsert your SD card back into your Switch + 5. Copy `hekate_ipl.ini` to the `bootloader` folder on your microSD Card + 6. Copy `Lockpick_RCM.bin` to the `/bootloader/payloads` folder on your microSD Card + 7. Create a folder named `appstore` inside the `switch` folder on your microSD Card, and put `appstore.nro` in it + 8. Copy `JKSV.nro`, `ftpd.nro`, `NX-Shell.nro` and `NxThemesInstaller.nro` to the `switch` folder on your microSD Card + 9. Reinsert your microSD Card back into your Switch !!! tip "" - Your SD card should look similar to this. The `Nintendo` folder will not be present if your switch has not already booted with the microSD card inserted. + Your microSD Card should look similar to this. The `Nintendo` folder will not be present if your Switch has not already booted with the microSD Card inserted. ![sdfilesimg](../img/sdfiles.png)   From 7756ae8e204a47c82c757e41b4d20fad0ed14b26 Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Wed, 9 Mar 2022 18:48:30 -0500 Subject: [PATCH 2/9] Clarified burning fuses --- docs/extras/nandrestore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extras/nandrestore.md b/docs/extras/nandrestore.md index 26919042..3fd3d451 100644 --- a/docs/extras/nandrestore.md +++ b/docs/extras/nandrestore.md @@ -33,7 +33,7 @@ Before we start, check if you have a tree of folders called `backup/[8 Character If the security revision you were on before you performed the NAND restore is HIGHER than the NAND backup itself, you have to enable autoRCM to not get stuck in a crash on boot. A system update is considered a security revision when a fuse is burned. You can check **which versions burn fuses here**. - If no fuses were burnt between the NAND backup you are restoring, and the Switch's current version, you can ignore this. + AutoRCM prevents fuses from being burnt. If autoRCM was installed ever since the NAND backup you are restoring, you don't need to worry about this. 1. In Hekate's main menu, navigate to `Tools` and go to the bottom of the page where you will find a button called `Archive bit - autoRCM` 2. Select the `autoRCM` button, and you will see `ON` written next to it. This means AutoRCM is enabled. From bf5323b6117adceee8c146eb355db9b60c440d39 Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Wed, 9 Mar 2022 19:29:36 -0500 Subject: [PATCH 3/9] Added step on RCM preparation, added FAQ entries https://discord.com/channels/196618637950451712/533041632283459595/951266584708649001 --- docs/extras/glossary.md | 22 +++++---- docs/user_guide/emummc/entering_rcm.md | 64 +++++++++++++------------ docs/user_guide/sysnand/entering_rcm.md | 62 ++++++++++++------------ 3 files changed, 78 insertions(+), 70 deletions(-) diff --git a/docs/extras/glossary.md b/docs/extras/glossary.md index 2123e930..7c03d95b 100644 --- a/docs/extras/glossary.md +++ b/docs/extras/glossary.md @@ -8,31 +8,35 @@ The following list is in alphabetical order. - **90DNS**: DNS that blocks system updates on the Nintendo Switch. This can be enabled by following the guide [here](blocking_nintendo.md). - **[Atmosphere](https://github.com/Atmosphere-NX/Atmosphere)**: The CFW developed by the Atmosphere-NX organization on GitHub and the one used in this guide. -- **autoRCM**: A method that corrupts parts of your boot0 and boot1, causing the Switch to boot into RCM automatically. Using this requires an additional peripheral (such as a computer, phone, dongle or trinket) to be able to boot your Switch. -- **boot0 and boot1**: Two partitions of the Switch NAND. +- **autoRCM**: refers to an environment where the Switch boots into RCM automatically, without the need of a jig. Please see https://switchgui.de/switch-guide/extras/autorcm/ for more info. +- **boot0 / boot1**: Two partitions of the Switch NAND that the console verifies in order to boot into the Switch OS. - **CFW**: Short for custom firmware. Custom firmware permits you to completely modify how your Switch works. - **Deja Vu**: An unreleased exploit chain for the Nintendo Switch. The completely unpatched version of this chain will grant access to TrustZone, which effectively means being able to enter CFW. The TrustZone part of this exploit was patched in firmware version 5.0.0 and up, but normal homebrew access can still be gained up to firmware version 6.0.1. - **DNS**: [Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System). Basically, it's the internet's addressbook. If you visit a website, the DNS is what tells you what server the site is hosted on. - **Dongle**: Device you can plug in the charging port of your Switch to automatically send a payload if your Switch is in RCM. - **Encryption keys**: Keys used to encrypt files from the Nintendo Switch. These can be dumped by following the guide [here](dumping_title_keys.md). - **BIS keys**: Specific keys used to decrypt the NAND. -- **[fusee-gelee](https://github.com/Qyriad/fusee-launcher/blob/master/report/fusee_gelee.md)/[ShofEL2](https://github.com/fail0verflow/shofel2)**: Two names for two different implementations of the same exploit. This is an exploit that grants full bootrom access to the Nintendo Switch from the Tegra X1s RCM and permits us to run CFW. This exploit requires an external device and a tiny hardware modification. fusee-gelee is developed by an ex-ReSwitched developer, while ShofEL2 is developed by the failoverfl0w team. This guide uses fusee-gelee. +- **Erista**: Also referred to as **T210** or **V1**, this refers to the original chipset used on full-sized Switch consoles manufactured before mid-2018, before the better-battery Switch. Erista units can be patched or unpatched. +- **[fusee-gelee](https://github.com/Qyriad/fusee-launcher/blob/master/report/fusee_gelee.md)/[ShofEL2](https://github.com/fail0verflow/shofel2)**: Two names for two different implementations of the same exploit. This is an exploit that grants full bootROM access to the Nintendo Switch from the Tegra X1s RCM and permits us to run CFW. This exploit requires an external device and a tiny hardware modification. fusee-gelee is developed by an ex-ReSwitched developer, while ShofEL2 is developed by the failoverfl0w team. This guide uses fusee-gelee. - **[hactool](https://github.com/SciresM/hactool)**: Software used to decrypt Nintendo Switch files like .XCI and .NSP files. - **[Hekate](https://github.com/CTCaer/hekate)**: A bootloader for the Nintendo Switch. The current guide uses this in combination with essential files from Atmosphere to boot CFW. - **Homebrew**: Unsigned code that can be ran on the Nintendo Switch. Examples of homebrew include save editors, emulators and ports of PC games, but can also include completely original games. To run this code, you need to have an exploit. - **Homebrew launcher**: Software developed by the Switchbrew team that lets you run other Homebrew. -- **Jig**: Refers to a piece of hardware that you can put in the Joycon rail to enter RCM. +- **Horizon**: Also referred to as **HOS** or **HorizonNX**, this refers to the official name of the Switch operating system. Horizon is also the name of the 3DS's OS, which HorizonNX is based off of. +- **Jig**: Refers to a piece of hardware that you can put in the Joy-Con rail to enter RCM. - **KIP**: Short for Kernel Initial Process. These files can be loaded in when the Switch boots in CFW and provide additional functionality. +- **Mariko**: Also referred to as **T214** or **V2**, refers to the chipset of any console made after late-2019. This includes Switch Lite, Switch (OLED Model), and the better-battery Switch. Units using Mariko chipsets are unhackable via software for the foreseeable future. - **NAND**: The internal filesystem used by the Switch. Contains boot0 and boot1, as well as PRODINFO and various other partitions. +- **NAND Backup**: A complete snapshot of the internal storage from a particular point in time. These are useful for brick recovery and to retrieve individual files from. - **nx-hbloader**: Intermediary program used to load the Homebrew Launcher from CFW developed by Switchbrew. Comes bundled with Atmosphere. -- **PRODINFO**: A partition on the NAND of your Switch. This along with boot0 and boot1 is the only part of your Switch that can render it unbootable if improperly modified. Atmosphere backs up this partition on booting and it is included in your NAND backup. +- **PRODINFO**: A crucial partition on the NAND of your Switch. Atmosphere backs up this partition on booting and it is included in your NAND backup. Losing or corrupting this file will permanently prevent a Switch from connecting to Nintendo servers. - **ReSwitched**: A hacking team that is one of the main developers for Atmosphere. -- **RCM**: A shorthand for "Recovery Mode". When talking about hacking the Switch, this commonly refers to the Recovery Mode in the Tegra X1 chip that is included in the Nintendo Switch. Can be entered by holding down the Tegra X1 home button. This button is not the same as the home button on the joycons. Ways of pressing this button can be found [here](../user_guide/emummc/entering_rcm.md). +- **RCM**: A shorthand for "Recovery Mode". This commonly refers to the Recovery Mode in the Tegra X1 chip that is included in the Nintendo Switch. Can be entered by holding down the Tegra X1 home button. This button is not the same as the home button on the Joy-Con controller. Ways of pressing this button can be found [here](../user_guide/emummc/entering_rcm.md). - **[TegraRCMGUI](https://github.com/eliboa/TegraRcmGUI/releases)/[fusee-interface-tk](https://github.com/nh-server/fusee-interfacee-tk/releases)**: Software used to run the fusee-gelee exploit on the Switch. -- **Tegra X1**: [A chip made by Nvidia that is used in the Nintendo Switch.](https://en.wikipedia.org/wiki/Tegra#Tegra_X1) -- **Trinket**: A tiny chip that is soldered on the Switch motherboard to automatically send a payload if it is in RCM. +- **Tegra X1**: A chip made by Nvidia that is used in the Nintendo Switch. There are two main revisions, [documented here.](https://en.wikipedia.org/wiki/Tegra#Tegra_X1) +- **Trinket**: A tiny chip that is soldered on the Switch motherboard to automatically send a payload upon RCM detection. - **TrustZone**: The highest security level on the Switch. -- **XCI/NSP**: Format used to dump games to. XCI is used for gamecard dumps, while NSP is for dumping digital titles. +- **XCI/NSP**: Format used to dump games to. XCI is used for gamecard dumps, while NSP is for dumping digital titles. Neither should be installed if you plan to go online to Nintendo servers. ## Resources diff --git a/docs/user_guide/emummc/entering_rcm.md b/docs/user_guide/emummc/entering_rcm.md index 982f2a0c..be0b765d 100644 --- a/docs/user_guide/emummc/entering_rcm.md +++ b/docs/user_guide/emummc/entering_rcm.md @@ -7,20 +7,21 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most   !!! danger "Patched Switch" - Note that patched units **can** enter RCM, but it is not possible to send a payload on those systems. Also note that RCM is a different recovery mode than the one accessed by holding Volume Up, Volume Down, and Power. + Note that all patched units **can** enter RCM, but it is not possible to send a payload on those systems. Also note that RCM is a different recovery mode than the one accessed by holding Volume Up, Volume Down, and Power (usually referred to as Maintenance Mode). !!! snippet "Note" - The order of methods on this page is in the order of ease. The easiest to immediately accomplish are listed at the top, and the most advanced/difficult methods are at the bottom. + The order of methods on this page is in the order of convenience. The easiest to immediately accomplish are listed at the top, and the most advanced/difficult methods are at the bottom.   ### Instructions !!! tip "" - 1. Power off the Switch and use one of the methods listed below to short the pins on the right joycon rail. - 2. Hold Volume Up and press the Power button. + 1. Unplug any USB-C cables from the console. + 2. Power off the Switch and use one of the methods listed below to short the pins on the right Joy-Con rail. + 3. Hold Volume Up and press the Power button. - If your Switch displays the Nintendo logo and boots normally or immediately shuts down, you didn't successfully enter RCM and should try again. Otherwise, if your console did not turn on normally, and the screen remained black with no backlight, your Switch is in RCM. + Your console should appear to have not responded, frozen on a black screen. *This is expected behavior.*. If you see the Nintendo > Nintendo Switch logo, then your Switch has booted up normally, and you'll need to attempt again. !!! tip "" ### RCM Jig (Easiest for beginners) @@ -28,20 +29,21 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most Click to expand! !!! snippet "Note" - Some jig designs use paperclips, inheriting the same risks as the Metal Bridge / Paperclip method. + Some jig designs use paperclips, inheriting the [same risks as using a paperclip outright](../faq/#what-makes-a-good-jig-good-can-i-use-a-paperclip). + Please do not suggest to (or attempt to) use a paperclip or other foreign object to enter RCM. - This method is similar to the Metal Bridge / Paperclip method, but is more reliable and safer in many cases. Jigs hold a wire in place so the correct pins (10 and a ground) are shorted every time. + This method is similar to the paperclip method, but is more reliable and safer in many cases. Jigs hold a wire in place so the correct pins (10 and a ground) are shorted every time. !!! tip "" ![switchjigs.com jigs](../img/entering_rcm_jig.jpg) - - In the case you plan to make you own jig, this image lays out the pads numbers on the console. Make sure your jig NEVER touches pin 4. Pin 4 provides 5v power to the Joycons, if connected to any other pin you will fry the console. + + In the case you plan to make your own jig, this image lays out the pads' numbers on the console. Make sure the jig's metal NEVER touches pin 4. Pin 4 provides 5v power to the Joy-Con controllers. If pin 4 is bridged to any other pin, you will damage the console. !!! tip "" - ![Console Numbered Pads Refrence](../img/entering_rcm_pads_numbered.jpg) - - Please note that once you have successfully entered RCM, you can take the jig out of the joycon rail. - + ![Console Numbered Pads Reference](../img/entering_rcm_pads_numbered.jpg) + + Please note that once you have successfully entered RCM, you can take the jig out of the Joy-Con rail. + !!! tip "" @@ -53,34 +55,34 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most This method requires opening your right Joy-Con, voiding its warranty. Not for the faint of heart. This method comes to us from the mind of pbanj#9188 on Discord. All pictures of this method in action were provided by him, with some supplementary images provided by eip ∞#3283 on Discord. - - The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however you will be soldering wires to pins 7 and 10 (shown below) and wiring them to the "Joycon release button" at the top back of the right hand Joycon. + + The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however you will be soldering wires to pins 7 and 10 (shown below) and wiring them to the "Joy-Con release button" at the top back of the right hand Joy-Con. !!! tip "" - ![joycon numbered pads refrence](../img/entering_rcm_solder_numbered.jpg) + ![Joy-Con numbered pads reference](../img/entering_rcm_solder_numbered.jpg) In order to start this method you will want to take two lengths of wire, and wrap one end of each into a small circle. !!! tip "" - ![wire refrence](../img/entering_rcm_button_1.jpg) - - You will then want to take the circular end of one of the wires and add a small amount of solder, keeping it mostly flat (ONLY DO THIS TO ONE OF THE WIRES!). You will then glue this wire down to the below point on the Joycon release button. Make sure glue doesn't cover the top of the solder/wire as it will act as a contact point. Also, ensure that you leave enough space for the button to function correctly. Try pushing the button from the outside and observing its travel path so that you can see where and how you should safely glue the solder glob. - + ![wire reference](../img/entering_rcm_button_1.jpg) + + You will then want to take the circular end of one of the wires and add a small amount of solder, keeping it mostly flat (ONLY DO THIS TO ONE OF THE WIRES!). You will then glue this wire down to the below point on the Joy-Con release button. Make sure glue doesn't cover the top of the solder/wire as it will act as a contact point. Also, ensure that you leave enough space for the button to function correctly. Try pushing the button from the outside and observing its travel path so that you can see where and how you should safely glue the solder glob. + !!! tip "" - ![Eip joycon button refrence](../img/entering_rcm_button_5.jpg) - + ![Eip Joy-Con button reference](../img/entering_rcm_button_5.jpg) + !!! tip "" - ![pbanj joycon button refrence](../img/entering_rcm_button_3.jpg) - + ![pbanj Joy-Con button reference](../img/entering_rcm_button_3.jpg) + The first wire should now be in place as seen by the green circle below. The second wire does not need any solder, instead you will hold it in place using the screw as shown by the red circle in the picture below. !!! tip "" - ![pbanj joycon button refrence](../img/entering_rcm_button_6.jpg) + ![pbanj Joy-Con button reference](../img/entering_rcm_button_6.jpg) - Pressing the Joycon button in you should now notice the solder point you created making contact with the piece of metal held in by the screw. Once you have these elements in place you want to connect one wire to pad 7 and the other to pad 10 (it doesn't matter which is which). After that you have successfully created an RCM button on your Joycon. You will now need to hold down the Joycon release button when attempting to boot RCM. + Pressing the Joy-Con button in you should now notice the solder point you created making contact with the piece of metal held in by the screw. Once you have these elements in place you want to connect one wire to pad 7 and the other to pad 10 (it doesn't matter which is which). After that you have successfully created an RCM button on your Joy-Con. You will now need to hold down the Joy-Con release button when attempting to boot RCM. !!! tip "" - ![pbanj joycon button refrence](../img/entering_rcm_button_2.jpg) + ![pbanj Joy-Con button reference](../img/entering_rcm_button_2.jpg) !!! tip "" @@ -94,7 +96,7 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however the goal is to solder pins 7 and 10 (shown below) together with a surface-mount 0805 10k resistor. Apart from using a physical switch/button, this is currently considered the safest method that involves soldering to pads. !!! tip "" - ![joycon numbered pads refrence](../img/entering_rcm_solder_numbered.jpg) + ![Joy-Con numbered pads reference](../img/entering_rcm_solder_numbered.jpg) Here is an example from stuckpixel#3421 on the ReSwitched Discord server. @@ -116,8 +118,8 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however the goal is to solder pads 9 and 10 (seen below) together. This can either be done using a small wire, or directly bridging the pads with solder. !!! tip "" - ![joycon numbered pads refrence](../img/entering_rcm_solder_numbered.jpg) - + ![Joy-Con numbered pads reference](../img/entering_rcm_solder_numbered.jpg) + Here is an example from YyAoMmIi#3705 on our Discord server. !!! tip "" @@ -138,7 +140,7 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily, and use a thin object such as a knife to gently bend pin 9 and 10 (shown below) slightly up and towards each other so they touch, shorting them. !!! tip "" - ![Joycon Pin Refrence](../img/enterting_rcm_pins_numbered.jpg) + ![Joy-Con Pin Reference](../img/enterting_rcm_pins_numbered.jpg) Here is an example from Sonlen#1414 on our Discord server. diff --git a/docs/user_guide/sysnand/entering_rcm.md b/docs/user_guide/sysnand/entering_rcm.md index b6b40965..2917b6eb 100644 --- a/docs/user_guide/sysnand/entering_rcm.md +++ b/docs/user_guide/sysnand/entering_rcm.md @@ -7,20 +7,21 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most   !!! danger "Patched Switch" - Note that patched units **can** enter RCM, but it is not possible to send a payload on those systems. Also note that RCM is a different recovery mode than the one accessed by holding Volume Up, Volume Down, and Power. + Note that all patched units **can** enter RCM, but it is not possible to send a payload on those systems. Also note that RCM is a different recovery mode than the one accessed by holding Volume Up, Volume Down, and Power (usually referred to as Maintenance Mode). !!! snippet "Note" - The order of methods on this page is in the order of ease. The easiest to immediately accomplish are listed at the top, and the most advanced/difficult methods are at the bottom. + The order of methods on this page is in the order of convenience. The easiest to immediately accomplish are listed at the top, and the most advanced/difficult methods are at the bottom.   ### Instructions !!! tip "" - 1. Power off the Switch and use one of the methods listed below to short the pins on the right joycon rail. - 2. Hold Volume Up and press the Power button. + 1. Unplug any USB-C cables from the console. + 2. Power off the Switch and use one of the methods listed below to short the pins on the right Joy-Con rail. + 3. Hold Volume Up and press the Power button. - If your Switch displays the Nintendo logo and boots normally or immediately shuts down, you didn't successfully enter RCM and should try again. Otherwise, if your console did not turn on normally, and the screen remained black with no backlight, your Switch is in RCM. + Your console should appear to have not responded, frozen on a black screen. *This is expected behavior.*. If you see the Nintendo > Nintendo Switch logo, then your Switch has booted up normally, and you'll need to attempt again. !!! tip "" ### RCM Jig (Easiest for beginners) @@ -28,19 +29,20 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most Click to expand! !!! snippet "Note" - Some jig designs use paperclips, inheriting the same risks as the Metal Bridge / Paperclip method. + Some jig designs use paperclips, inheriting the [same risks as using a paperclip outright](../faq/#what-makes-a-good-jig-good-can-i-use-a-paperclip). + Please do not suggest to (or attempt to) use a paperclip or other foreign object to enter RCM. - This method is similar to the Metal Bridge / Paperclip method, but is more reliable and safer in many cases. Jigs hold a wire in place so the correct pins (10 and a ground) are shorted every time. + This method is similar to the paperclip method, but is more reliable and safer in many cases. Jigs hold a wire in place so the correct pins (10 and a ground) are shorted every time. !!! tip "" ![switchjigs.com jigs](../img/entering_rcm_jig.jpg) - - In the case you plan to make you own jig, this image lays out the pads numbers on the console. Make sure your jig NEVER touches pin 4. Pin 4 provides 5v power to the Joycons, if connected to any other pin you will fry the console. + + In the case you plan to make your own jig, this image lays out the pads' numbers on the console. Make sure the jig's metal NEVER touches pin 4. Pin 4 provides 5v power to the Joy-Con controllers. If pin 4 is bridged to any other pin, you will damage the console. !!! tip "" - ![Console Numbered Pads Refrence](../img/entering_rcm_pads_numbered.jpg) - - Please note that once you have successfully entered RCM, you can take the jig out of the joycon rail. + ![Console Numbered Pads Reference](../img/entering_rcm_pads_numbered.jpg) + + Please note that once you have successfully entered RCM, you can take the jig out of the Joy-Con rail. !!! tip "" @@ -52,34 +54,34 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most This method requires opening your right Joy-Con, voiding its warranty. Not for the faint of heart. This method comes to us from the mind of pbanj#9188 on Discord. All pictures of this method in action were provided by him, with some supplementary images provided by eip ∞#3283 on Discord. - - The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however you will be soldering wires to pins 7 and 10 (shown below) and wiring them to the "Joycon release button" at the top back of the right hand Joycon. + + The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however you will be soldering wires to pins 7 and 10 (shown below) and wiring them to the "Joy-Con release button" at the top back of the right hand Joy-Con. !!! tip "" - ![joycon numbered pads refrence](../img/entering_rcm_solder_numbered.jpg) + ![Joy-Con numbered pads reference](../img/entering_rcm_solder_numbered.jpg) In order to start this method you will want to take two lengths of wire, and wrap one end of each into a small circle. !!! tip "" - ![wire refrence](../img/entering_rcm_button_1.jpg) - - You will then want to take the circular end of one of the wires and add a small amount of solder, keeping it mostly flat (ONLY DO THIS TO ONE OF THE WIRES!). You will then glue this wire down to the below point on the Joycon release button. Make sure glue doesn't cover the top of the solder/wire as it will act as a contact point. Also, ensure that you leave enough space for the button to function correctly. Try pushing the button from the outside and observing its travel path so that you can see where and how you should safely glue the solder glob. - + ![wire reference](../img/entering_rcm_button_1.jpg) + + You will then want to take the circular end of one of the wires and add a small amount of solder, keeping it mostly flat (ONLY DO THIS TO ONE OF THE WIRES!). You will then glue this wire down to the below point on the Joy-Con release button. Make sure glue doesn't cover the top of the solder/wire as it will act as a contact point. Also, ensure that you leave enough space for the button to function correctly. Try pushing the button from the outside and observing its travel path so that you can see where and how you should safely glue the solder glob. + !!! tip "" - ![Eip joycon button refrence](../img/entering_rcm_button_5.jpg) - + ![Eip Joy-Con button reference](../img/entering_rcm_button_5.jpg) + !!! tip "" - ![pbanj joycon button refrence](../img/entering_rcm_button_3.jpg) - + ![pbanj Joy-Con button reference](../img/entering_rcm_button_3.jpg) + The first wire should now be in place as seen by the green circle below. The second wire does not need any solder, instead you will hold it in place using the screw as shown by the red circle in the picture below. !!! tip "" - ![pbanj joycon button refrence](../img/entering_rcm_button_6.jpg) + ![pbanj Joy-Con button reference](../img/entering_rcm_button_6.jpg) - Pressing the Joycon button in you should now notice the solder point you created making contact with the piece of metal held in by the screw. Once you have these elements in place you want to connect one wire to pad 7 and the other to pad 10 (it doesn't matter which is which). After that you have successfully created an RCM button on your Joycon. You will now need to hold down the Joycon release button when attempting to boot RCM. + Pressing the Joy-Con button in you should now notice the solder point you created making contact with the piece of metal held in by the screw. Once you have these elements in place you want to connect one wire to pad 7 and the other to pad 10 (it doesn't matter which is which). After that you have successfully created an RCM button on your Joy-Con. You will now need to hold down the Joy-Con release button when attempting to boot RCM. !!! tip "" - ![pbanj joycon button refrence](../img/entering_rcm_button_2.jpg) + ![pbanj Joy-Con button reference](../img/entering_rcm_button_2.jpg) !!! tip "" @@ -93,7 +95,7 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however the goal is to solder pins 7 and 10 (shown below) together with a surface-mount 0805 10k resistor. Apart from using a physical switch/button, this is currently considered the safest method that involves soldering to pads. !!! tip "" - ![joycon numbered pads refrence](../img/entering_rcm_solder_numbered.jpg) + ![Joy-Con numbered pads reference](../img/entering_rcm_solder_numbered.jpg) Here is an example from stuckpixel#3421 on the ReSwitched Discord server. @@ -115,8 +117,8 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily. This is similar to the previous method, however the goal is to solder pads 9 and 10 (seen below) together. This can either be done using a small wire, or directly bridging the pads with solder. !!! tip "" - ![joycon numbered pads refrence](../img/entering_rcm_solder_numbered.jpg) - + ![Joy-Con numbered pads reference](../img/entering_rcm_solder_numbered.jpg) + Here is an example from YyAoMmIi#3705 on our Discord server. !!! tip "" @@ -137,7 +139,7 @@ There are several methods of entering RCM (**R**e**C**overy **M**ode). The most The goal of this method is to open the right handed Joy-Con to the point that you can reach the contact pads easily, and use a thin object such as a knife to gently bend pin 9 and 10 (shown below) slightly up and towards each other so they touch, shorting them. !!! tip "" - ![Joycon Pin Refrence](../img/enterting_rcm_pins_numbered.jpg) + ![Joy-Con Pin Reference](../img/enterting_rcm_pins_numbered.jpg) Here is an example from Sonlen#1414 on our Discord server. From 207cd71bff4bcea8d1cac3fad77fc2c6eab750c9 Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Thu, 10 Mar 2022 05:34:24 -0500 Subject: [PATCH 4/9] Incorporated a number of JeffV's suggestions Waiting more opinions on autoRCM stylisation. --- docs/extras/autorcm.md | 4 ++-- docs/extras/blocking_nintendo.md | 4 ++-- docs/extras/glossary.md | 4 ++-- docs/extras/nandrestore.md | 4 ++-- docs/extras/theming.md | 6 +++--- docs/extras/transfer_sd.md | 2 +- docs/faq.md | 4 ++-- docs/files/emu/hekate_ipl.ini | 2 +- docs/user_guide/emummc/partitioning_sd.md | 2 +- docs/user_guide/emummc/sd_preparation.md | 2 +- 10 files changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/extras/autorcm.md b/docs/extras/autorcm.md index b263e5a7..e5c6d271 100644 --- a/docs/extras/autorcm.md +++ b/docs/extras/autorcm.md @@ -36,5 +36,5 @@ If, despite all of the warnings above, you still wish to install autoRCM, and un 1. Boot Hekate 2. Go to `Tools` -3. At the bottom of the page, tap `Arch Bit • autoRCM • Touch • Pkg1/2` -4. Then tap `autoRCM`. It will show a little `ON` next to the option once you have done this. +3. At the bottom of the page, tap `Arch bit • AutoRCM • Touch • Pkg1/2` +4. Then tap `AutoRCM`. It will show a little `ON` next to the option once you have done this. diff --git a/docs/extras/blocking_nintendo.md b/docs/extras/blocking_nintendo.md index edfb1c2b..7856e6b7 100644 --- a/docs/extras/blocking_nintendo.md +++ b/docs/extras/blocking_nintendo.md @@ -12,7 +12,7 @@ You can configure Atmosphere to automatically redirect any requests directed to #### Setup: -1. Insert your SD into your PC +1. Insert your microSD Card into your PC 2. Enter the Atmosphere folder 3. If it doesn't exist already, create a folder named `hosts` in the atmosphere folder 4. Copy the emummc.txt into the hosts folder @@ -62,7 +62,7 @@ You can add a custom DNS to your WiFi connection that will block all communicati ----- ### Using homebrew to set 90dns on all existing WiFi networks - 1. Download [switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the /switch folder. + 1. Download [Switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the /switch folder. 2. Launch CFW and open the homebrew menu. 3. Launch `90dns setter`. 4. Press X to apply 90dns to all WiFi networks. diff --git a/docs/extras/glossary.md b/docs/extras/glossary.md index 7c03d95b..bfa52490 100644 --- a/docs/extras/glossary.md +++ b/docs/extras/glossary.md @@ -8,7 +8,7 @@ The following list is in alphabetical order. - **90DNS**: DNS that blocks system updates on the Nintendo Switch. This can be enabled by following the guide [here](blocking_nintendo.md). - **[Atmosphere](https://github.com/Atmosphere-NX/Atmosphere)**: The CFW developed by the Atmosphere-NX organization on GitHub and the one used in this guide. -- **autoRCM**: refers to an environment where the Switch boots into RCM automatically, without the need of a jig. Please see https://switchgui.de/switch-guide/extras/autorcm/ for more info. +- **autoRCM**: This refers to an environment where the Switch boots into RCM automatically, without the need of a jig. Please see [this page](/autorcm.md) for more info. - **boot0 / boot1**: Two partitions of the Switch NAND that the console verifies in order to boot into the Switch OS. - **CFW**: Short for custom firmware. Custom firmware permits you to completely modify how your Switch works. - **Deja Vu**: An unreleased exploit chain for the Nintendo Switch. The completely unpatched version of this chain will grant access to TrustZone, which effectively means being able to enter CFW. The TrustZone part of this exploit was patched in firmware version 5.0.0 and up, but normal homebrew access can still be gained up to firmware version 6.0.1. @@ -29,7 +29,7 @@ The following list is in alphabetical order. - **NAND**: The internal filesystem used by the Switch. Contains boot0 and boot1, as well as PRODINFO and various other partitions. - **NAND Backup**: A complete snapshot of the internal storage from a particular point in time. These are useful for brick recovery and to retrieve individual files from. - **nx-hbloader**: Intermediary program used to load the Homebrew Launcher from CFW developed by Switchbrew. Comes bundled with Atmosphere. -- **PRODINFO**: A crucial partition on the NAND of your Switch. Atmosphere backs up this partition on booting and it is included in your NAND backup. Losing or corrupting this file will permanently prevent a Switch from connecting to Nintendo servers. +- **PRODINFO**: A crucial partition on the NAND of your Switch. Atmosphere backs up this partition on booting and it is included in your NAND backup. Losing/corrupting this file will permanently prevent a Switch from booting and/or connecting to Nintendo servers. - **ReSwitched**: A hacking team that is one of the main developers for Atmosphere. - **RCM**: A shorthand for "Recovery Mode". This commonly refers to the Recovery Mode in the Tegra X1 chip that is included in the Nintendo Switch. Can be entered by holding down the Tegra X1 home button. This button is not the same as the home button on the Joy-Con controller. Ways of pressing this button can be found [here](../user_guide/emummc/entering_rcm.md). - **[TegraRCMGUI](https://github.com/eliboa/TegraRcmGUI/releases)/[fusee-interface-tk](https://github.com/nh-server/fusee-interfacee-tk/releases)**: Software used to run the fusee-gelee exploit on the Switch. diff --git a/docs/extras/nandrestore.md b/docs/extras/nandrestore.md index 3fd3d451..adab2eb8 100644 --- a/docs/extras/nandrestore.md +++ b/docs/extras/nandrestore.md @@ -35,5 +35,5 @@ Before we start, check if you have a tree of folders called `backup/[8 Character AutoRCM prevents fuses from being burnt. If autoRCM was installed ever since the NAND backup you are restoring, you don't need to worry about this. - 1. In Hekate's main menu, navigate to `Tools` and go to the bottom of the page where you will find a button called `Archive bit - autoRCM` - 2. Select the `autoRCM` button, and you will see `ON` written next to it. This means AutoRCM is enabled. + 1. In Hekate's main menu, navigate to `Tools` and go to the bottom of the page where you will find a button called `Archive bit - AutoRCM` + 2. Select the `AutoRCM` button, and you will see `ON` written next to it. This means AutoRCM is enabled. diff --git a/docs/extras/theming.md b/docs/extras/theming.md index 221e0ee7..e2e2950f 100644 --- a/docs/extras/theming.md +++ b/docs/extras/theming.md @@ -55,10 +55,10 @@ Make sure that the images you want to use are 1280x720 and in JPG! If you want to use community themes, for example from the **r/NXThemes**, you can follow the guide below to install a community provided nxtheme !!! tip "Homebrew app store" - If you want to use the homebrew app store for themes, you can simply install the theme you want via the appstore, and follow the instructions from step 2 onwards below. + If you want to use the Homebrew App Store for themes, you can simply install the theme you want via the App Store, and follow the instructions from step 2 onwards below. -1. Copy the `.nxtheme` files to the `/themes` folder on your microSD Card (It is recommended you put them into their own folders, e.g. /themes/awesome_theme/awesome.nxtheme). - - Create the `/themes` folder on the root of your microSD Card if it does not exist. +1. Copy the `.nxtheme` files to `/themes` on your microSD Card (It is recommended you put them into their own folders.For example, /themes/awesome_theme/awesome.nxtheme). + - Create the `themes` folder on the root of your microSD Card if it does not exist.   2. Boot Switch CFW, launch the Homebrew Menu and launch `NXThemes Installer`. 3. Your theme files should be listed here. You can install them one by one. diff --git a/docs/extras/transfer_sd.md b/docs/extras/transfer_sd.md index ea57fe62..090ba456 100644 --- a/docs/extras/transfer_sd.md +++ b/docs/extras/transfer_sd.md @@ -36,7 +36,7 @@ You should first check whether you have a file or partition based emuMMC: 4. Once both are done, go back to the main menu, remove your microSD Card and insert it into your PC. 5. If Windows asks you to format a drive, discard it and select the drive with your SD contents. 6. Copy the contents of your microSD Card somewhere to your PC. -7. Follow only [this page](https://switchgui.de/switch-guide/user_guide/emummc/partitioning_sd/) to partition the new microSD Card for an emuMMC setup. +7. Follow only [this page](../user_guide/emummc/partitioning_sd/) to partition the new microSD Card for an emuMMC setup. 8. After it’s done, exit and insert your new microSD Card into your PC. 9. Copy the contents of your old microSD Card to your new one. 10. Navigate to `/backup//` on your microSD Card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to the `restore` folder. diff --git a/docs/faq.md b/docs/faq.md index 90257aa6..73456fd0 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -155,10 +155,10 @@ !!!tip "" This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your homebrew, you will need to unset the archive bit with Hekate. - 1. Send the Hekate payload to your Switch by following these instructions: [here](https://nh-server.github.io/switch-guide/user_guide/emuMMC/sending_payload/) + 1. Send the Hekate payload to your Switch by following these instructions: [here](https://nh-server.github.io/switch-guide/user_guide/emummc/sending_payload/) 2. Click on `Tools` on the top menu bar 3. In the bottom left corner click on `Archive bit * autoRCM` 4. Click on `Fix Archive bit` - this might take a while 5. Press `Close` in the top right corner 6. Press `Home` in the top menu bar to get back from where you started - 7. Follow the instructions at the Launching CFW page [here](https://nh-server.github.io/switch-guide/user_guide/emuMMC/launching_cfw/) to launch Atmosphere. + 7. Follow the instructions at the Launching CFW page [here](https://nh-server.github.io/switch-guide/user_guide/emummc/launching_cfw/) to launch Atmosphere. diff --git a/docs/files/emu/hekate_ipl.ini b/docs/files/emu/hekate_ipl.ini index f8e3a456..b20e9da9 100644 --- a/docs/files/emu/hekate_ipl.ini +++ b/docs/files/emu/hekate_ipl.ini @@ -1,7 +1,7 @@ [config] updater2p=1 {------ Atmosphere ------} -[Atmosphere FSS0 EmuMMC] +[Atmosphere FSS0 emuMMC] fss0=atmosphere/package3 kip1=atmosphere/kips/* emummcforce=1 diff --git a/docs/user_guide/emummc/partitioning_sd.md b/docs/user_guide/emummc/partitioning_sd.md index 6e50bd2a..0bab1af2 100644 --- a/docs/user_guide/emummc/partitioning_sd.md +++ b/docs/user_guide/emummc/partitioning_sd.md @@ -19,7 +19,7 @@ What you need: 1. Inject the TegraExplorer payload with your 64GB (or larger) microSD Card inserted into your Switch. - If you forgot how to do this, re-read the [sending payload](sending_payload.md) section of the guide. 2. Navigate to `Partition the SD` and press the A button to enter the SD format menu. - - If you can't find the Partition the sd option, make sure that your microSD Card is inserted and select Mount SD. + - If you can't find the Partition the SD option, make sure that your microSD Card is inserted and select Mount SD. 3. Navigate to `FAT32 + emuMMC` and press the A button to confirm. 4. Read the warning, and select Yes to partition & format your microSD Card. - Note: This will delete all data on your microSD Card. Make sure you backed up your Nintendo folder! diff --git a/docs/user_guide/emummc/sd_preparation.md b/docs/user_guide/emummc/sd_preparation.md index bb4dac5a..fb3ee428 100644 --- a/docs/user_guide/emummc/sd_preparation.md +++ b/docs/user_guide/emummc/sd_preparation.md @@ -42,7 +42,7 @@ Atmosphere has its own bootloader, called fusee. For the purposes of this guide 10. If you were already using your microSD Card as a storage device for your games and backed up the Nintendo folder before partitioning your microSD Card, please place it back on the root of your microSD Card. 11. Reinsert your microSD Card back into your Switch - !!!danger "About emuMMC.txt" + !!!danger "About emummc.txt" Putting the `emummc.txt` file provided by this guide into `/atmosphere/hosts` will prevent your emuMMC (emuNAND) from connecting to Nintendo. Not doing this will likely result in a ban. !!! tip "" From eec9887c46e352e8b16b9ec6b361ae19c4ba322b Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Thu, 10 Mar 2022 05:38:21 -0500 Subject: [PATCH 5/9] Updated links --- docs/faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 73456fd0..88ddf865 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -155,10 +155,10 @@ !!!tip "" This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your homebrew, you will need to unset the archive bit with Hekate. - 1. Send the Hekate payload to your Switch by following these instructions: [here](https://nh-server.github.io/switch-guide/user_guide/emummc/sending_payload/) + 1. Send the Hekate payload to your Switch by following these instructions: [here](../user_guide/emummc/sending_payload/) 2. Click on `Tools` on the top menu bar 3. In the bottom left corner click on `Archive bit * autoRCM` 4. Click on `Fix Archive bit` - this might take a while 5. Press `Close` in the top right corner 6. Press `Home` in the top menu bar to get back from where you started - 7. Follow the instructions at the Launching CFW page [here](https://nh-server.github.io/switch-guide/user_guide/emummc/launching_cfw/) to launch Atmosphere. + 7. Follow the instructions at the Launching CFW page [here](../user_guide/emummc/launching_cfw/) to launch Atmosphere. From 98ffdc795428904dd98385ae013daca6dd162c5e Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Thu, 10 Mar 2022 08:21:06 -0500 Subject: [PATCH 6/9] .md --- docs/extras/transfer_sd.md | 2 +- docs/faq.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/extras/transfer_sd.md b/docs/extras/transfer_sd.md index 090ba456..0aec75c7 100644 --- a/docs/extras/transfer_sd.md +++ b/docs/extras/transfer_sd.md @@ -36,7 +36,7 @@ You should first check whether you have a file or partition based emuMMC: 4. Once both are done, go back to the main menu, remove your microSD Card and insert it into your PC. 5. If Windows asks you to format a drive, discard it and select the drive with your SD contents. 6. Copy the contents of your microSD Card somewhere to your PC. -7. Follow only [this page](../user_guide/emummc/partitioning_sd/) to partition the new microSD Card for an emuMMC setup. +7. Follow only [this page](../user_guide/emummc/partitioning_sd.md) to partition the new microSD Card for an emuMMC setup. 8. After it’s done, exit and insert your new microSD Card into your PC. 9. Copy the contents of your old microSD Card to your new one. 10. Navigate to `/backup//` on your microSD Card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to the `restore` folder. diff --git a/docs/faq.md b/docs/faq.md index 88ddf865..34b86c70 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -155,10 +155,10 @@ !!!tip "" This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your homebrew, you will need to unset the archive bit with Hekate. - 1. Send the Hekate payload to your Switch by following these instructions: [here](../user_guide/emummc/sending_payload/) + 1. Send the Hekate payload to your Switch by following these instructions: [here](../user_guide/emummc/sending_payload.md) 2. Click on `Tools` on the top menu bar 3. In the bottom left corner click on `Archive bit * autoRCM` 4. Click on `Fix Archive bit` - this might take a while 5. Press `Close` in the top right corner 6. Press `Home` in the top menu bar to get back from where you started - 7. Follow the instructions at the Launching CFW page [here](../user_guide/emummc/launching_cfw/) to launch Atmosphere. + 7. Follow the instructions at the Launching CFW page [here](../user_guide/emummc/launching_cfw.md) to launch Atmosphere. From 75a281446ff882b1fa62d877728b1c6ef6d8a04f Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Thu, 10 Mar 2022 08:27:30 -0500 Subject: [PATCH 7/9] Probably fixing the build? --- docs/faq.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 34b86c70..5484217a 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -81,7 +81,7 @@ !!!tip "" The Switch comes with a lot of telemetry, and has been called a "telemetry monster" by several prominent developers. As long as the Switch is connected to the internet, Nintendo gets a report about a lot of different actions and states and has the option to log or act on them. - Even if the Switch is offline and connects to the internet at a later point, Nintendo still recieves information about what happened while the Switch was disconnected. + Even if the Switch is offline and connects to the internet at a later point, Nintendo still receives information about what happened while the Switch was disconnected. To disable some of this telemetry, it is advised to disable the sending of error reports in the System Settings of the Switch. Additionally if you live in the EU you can set the "do not share" option on Nintendo's website to prevent your Switch from sending a lot of telemetry, although the effectiveness of this is questionable. @@ -155,10 +155,10 @@ !!!tip "" This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your homebrew, you will need to unset the archive bit with Hekate. - 1. Send the Hekate payload to your Switch by following these instructions: [here](../user_guide/emummc/sending_payload.md) + 1. Send the Hekate payload to your Switch by following these instructions: [here](/user_guide/emummc/sending_payload.md) 2. Click on `Tools` on the top menu bar 3. In the bottom left corner click on `Archive bit * autoRCM` 4. Click on `Fix Archive bit` - this might take a while 5. Press `Close` in the top right corner 6. Press `Home` in the top menu bar to get back from where you started - 7. Follow the instructions at the Launching CFW page [here](../user_guide/emummc/launching_cfw.md) to launch Atmosphere. + 7. Follow the instructions at the Launching CFW page [here](/user_guide/emummc/launching_cfw.md) to launch Atmosphere. From c67f81396924d11167b0f0ac41ef603fa9034cf5 Mon Sep 17 00:00:00 2001 From: Halvorsen256 Date: Thu, 10 Mar 2022 08:53:05 -0500 Subject: [PATCH 8/9] . --- docs/extras/transfer_sd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extras/transfer_sd.md b/docs/extras/transfer_sd.md index 0aec75c7..789ffaed 100644 --- a/docs/extras/transfer_sd.md +++ b/docs/extras/transfer_sd.md @@ -36,7 +36,7 @@ You should first check whether you have a file or partition based emuMMC: 4. Once both are done, go back to the main menu, remove your microSD Card and insert it into your PC. 5. If Windows asks you to format a drive, discard it and select the drive with your SD contents. 6. Copy the contents of your microSD Card somewhere to your PC. -7. Follow only [this page](../user_guide/emummc/partitioning_sd.md) to partition the new microSD Card for an emuMMC setup. +7. Follow only [this page](/user_guide/emummc/partitioning_sd.md) to partition the new microSD Card for an emuMMC setup. 8. After it’s done, exit and insert your new microSD Card into your PC. 9. Copy the contents of your old microSD Card to your new one. 10. Navigate to `/backup//` on your microSD Card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to the `restore` folder. From f4e1de62d8510b1e11266131a4cd02b2c4ce433e Mon Sep 17 00:00:00 2001 From: North <22641804+ha1vorsen@users.noreply.github.com> Date: Sat, 12 Mar 2022 03:51:19 -0500 Subject: [PATCH 9/9] Update docs/extras/blocking_nintendo.md Co-authored-by: lifehackerhansol --- docs/extras/blocking_nintendo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extras/blocking_nintendo.md b/docs/extras/blocking_nintendo.md index 7856e6b7..ef68d90e 100644 --- a/docs/extras/blocking_nintendo.md +++ b/docs/extras/blocking_nintendo.md @@ -62,7 +62,7 @@ You can add a custom DNS to your WiFi connection that will block all communicati ----- ### Using homebrew to set 90dns on all existing WiFi networks - 1. Download [Switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the /switch folder. + 1. Download [Switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the `/switch` folder. 2. Launch CFW and open the homebrew menu. 3. Launch `90dns setter`. 4. Press X to apply 90dns to all WiFi networks.