From 5e9ce3270d49721ca7cb148f950d1b2cb5eb3d24 Mon Sep 17 00:00:00 2001 From: lifehackerhansol Date: Fri, 27 Sep 2024 12:30:55 -0700 Subject: [PATCH] treewide: default to 4-space indents There is a mix of tabs, 4-space and 6-space indents; standardize indentation across all pages to 4-spaces to keep consistency. --- docs/extras/alternate_bootsetups.md | 2 +- docs/extras/autorcm.md | 14 ++++---- docs/extras/glossary.md | 2 +- docs/extras/nandrestore.md | 26 +++++++-------- docs/homebrew/nxtheme-installer.md | 8 ++--- docs/index.md | 32 +++++++++---------- docs/user_guide/all/cfw_environment.md | 8 ++--- docs/user_guide/all/launching_cfw.md | 14 ++++---- .../all/making_essential_backups.md | 8 ++--- docs/user_guide/getting_started.md | 12 +++---- docs/user_guide/modchip/index.md | 22 ++++++------- docs/user_guide/rcm/entering_rcm.md | 2 +- docs/user_guide/rcm/index.md | 8 ++--- docs/user_guide/rcm/sending_payload.md | 2 +- 14 files changed, 80 insertions(+), 80 deletions(-) diff --git a/docs/extras/alternate_bootsetups.md b/docs/extras/alternate_bootsetups.md index 0d78e46c..50e3564e 100644 --- a/docs/extras/alternate_bootsetups.md +++ b/docs/extras/alternate_bootsetups.md @@ -3,7 +3,7 @@ If you need to troubleshoot something, or need to try a different boot setup, read on. !!! danger "Do I need any of these?" - Unless you are experiencing problems with booting or Atmosphère itself, it's strongly recommended to use the main guide instead of these. They are provided for the sake of completeness. + Unless you are experiencing problems with booting or Atmosphère itself, it's strongly recommended to use the main guide instead of these. They are provided for the sake of completeness.   diff --git a/docs/extras/autorcm.md b/docs/extras/autorcm.md index 7b03b0a6..823b3492 100644 --- a/docs/extras/autorcm.md +++ b/docs/extras/autorcm.md @@ -5,18 +5,18 @@ AutoRCM causes the console to believe it is bricked, and will automatically laun - 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**. + 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**. - 1. Boot into Hekate - 2. Go to `Tools`, and select `Backup eMMC` - 3. Then tap `eMMC BOOT0 & BOOT1` and let the process complete. + 1. Boot into Hekate + 2. Go to `Tools`, and select `Backup eMMC` + 3. Then tap `eMMC BOOT0 & BOOT1` and let the process complete. ### **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. + - 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. @@ -26,11 +26,11 @@ 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. + - 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 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. ### **Enable/Disable AutoRCM** diff --git a/docs/extras/glossary.md b/docs/extras/glossary.md index 3178fbab..9351f05a 100644 --- a/docs/extras/glossary.md +++ b/docs/extras/glossary.md @@ -16,7 +16,7 @@ The following list is in alphabetical order. - **DNS**: [Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System). Basically, the internet's addressbook. If you visit a website, the DNS lookup is what tells you what server the site is hosted on. - **Dongle**: Device you can plug in the USB-C of your Switch to automatically send a payload if your Switch is in RCM. - **Encryption keys**: Keys used to encrypt data from the Nintendo Switch. - - **BIS keys**: Built-in Storage keys. They are used to encrypt/decrypt the NAND's contents. + - **BIS keys**: Built-in Storage keys. They are used to encrypt/decrypt the NAND's contents. - **[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](https://nvd.nist.gov/vuln/detail/CVE-2018-6242). This is an exploit that grants full bootROM access to the Nintendo Switch from the Tegra X1's RCM, and permitting us to run CFW. This exploit requires an external device or 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 Atmosphère to boot CFW. diff --git a/docs/extras/nandrestore.md b/docs/extras/nandrestore.md index 9a09d0a6..f891c8b0 100644 --- a/docs/extras/nandrestore.md +++ b/docs/extras/nandrestore.md @@ -1,14 +1,14 @@ ## 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 the point of 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. + - This will reset all of your saves, games, system version and other system settings back to the point of 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. + - 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 `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. + - 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 @@ -17,11 +17,11 @@ 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 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. + 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 microSD card. Continue with step 1 of the instructions below. + 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 microSD card. Continue with step 1 of the instructions below. 1. Enter RCM and inject the Hekate payload. - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your SD. @@ -33,13 +33,13 @@ Before we start, check if you have a tree of folders called `backup/[8 Character - This will generally take a long time to complete, the time it takes depends on your microSD card's specifications. (10-15 minutes is expected.) !!! 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. + 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. - - Note: This section can be disregarded for modchipped Switch users. + - Note: This section can be disregarded for modchipped Switch users. - A system update is considered a security version when a fuse is burned, you can check **which versions burn fuses here**. + A system update is considered a security version 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 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. - 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` buttom and you will see `ON` written next to it. This means it is enabled. diff --git a/docs/homebrew/nxtheme-installer.md b/docs/homebrew/nxtheme-installer.md index 9174c9f8..ac0be7ae 100644 --- a/docs/homebrew/nxtheme-installer.md +++ b/docs/homebrew/nxtheme-installer.md @@ -17,7 +17,7 @@ Using NXTheme Installer, you can install and create unique styles and layouts fo ### **Installing a theme** !!! note "Community Themes" - If you want to use community made themes, for example from the r/NXThemes subreddit or [Themezer](https://themezer.net), you can follow the guide below to install a community provided `.nxtheme` file. + If you want to use community made themes, for example from the r/NXThemes subreddit or [Themezer](https://themezer.net), you can follow the guide below to install a community provided `.nxtheme` file. #### **What you need:** @@ -27,11 +27,11 @@ Using NXTheme Installer, you can install and create unique styles and layouts fo 1. Download `NXThemesInstaller.nro` and put it in `sd:/switch`. 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. `sd:/themes/awesome_theme/awesome.nxtheme`). - - Create the `themes` folder on the root of your microSD card if it does not exist. + - Create the `themes` folder on the root of your microSD card if it does not exist. 1. Boot into sysCFW/emuMMC and launch the Homebrew Menu, then launch `NXThemes Installer` *with* an internet connection. - NXTheme Installer will automatically download the required theme patches if it has a connection to the internet. These theme patches are required for themes to work. - If you don't want to or don't have the ability connect to a Wi-Fi network, installing the theme patches can be done manually. - See the instructions [here](https://github.com/exelix11/theme-patches#if-you-dont-want-to-connect-your-console-to-the-internet) on how to install them manually. + If you don't want to or don't have the ability connect to a Wi-Fi network, installing the theme patches can be done manually. + See the instructions [here](https://github.com/exelix11/theme-patches#if-you-dont-want-to-connect-your-console-to-the-internet) on how to install them manually. 1. If you get prompted about extracting your home menu data, do so. - You can always do this manually via the `Extract home menu` tab in `NXTheme Installer`. 1. You should now see the main menu of `NXTheme Installer`, the `Themes` tab is where you will find your themes. To install them, press the folder name of your theme and go through each home menu section to install the desired theme for that section (e.g. going to `/awesome_theme` and selecting your theme for the specific menu you want to change, do the same for the other menus). diff --git a/docs/index.md b/docs/index.md index 6433e8b2..f6d3310e 100644 --- a/docs/index.md +++ b/docs/index.md @@ -102,26 +102,26 @@ Note: We are not currently, historically, or will we ever be, associated with An Furthermore, we resent any implication to the contrary. ??? "Frequently Asked Questions about this page" - - **Q: What are the differences between "first-generation" ("V1") consoles and "patched" consoles when it comes to running homebrew?**
- A: Once you boot into Horizon, not much. The primary things to keep in mind is that only V1 consoles support Atmosphère's "Reboot to Payload" function, but modchips automatically load payloads during reboots on their own. + - **Q: What are the differences between "first-generation" ("V1") consoles and "patched" consoles when it comes to running homebrew?**
+ A: Once you boot into Horizon, not much. The primary things to keep in mind is that only V1 consoles support Atmosphère's "Reboot to Payload" function, but modchips automatically load payloads during reboots on their own. - - **Q: What is Horizon?**
- A: Horizon is the name of the Switch's operating system. It is sometimes called "HorizonNX", because it is actually a derivative version of the Nintendo 3DS's operating system of the same name. + - **Q: What is Horizon?**
+ A: Horizon is the name of the Switch's operating system. It is sometimes called "HorizonNX", because it is actually a derivative version of the Nintendo 3DS's operating system of the same name. - - **Q: Why is it called Atmosphère?**
- A: Atmosphère "runs on top of the Horizon" operating system. Each layer of Horizon's security is referenced via the atmosphere's different layers. For example, the EL1 "kernel" reimplementation is called mesosphère, while the EL3 "TrustZone" reimplementation is called exosphère.
Learn more about ARM Exception Levels [here](https://developer.arm.com/documentation/102412/0103/Privilege-and-Exception-levels/Exception-levels). + - **Q: Why is it called Atmosphère?**
+ A: Atmosphère "runs on top of the Horizon" operating system. Each layer of Horizon's security is referenced via the atmosphere's different layers. For example, the EL1 "kernel" reimplementation is called mesosphère, while the EL3 "TrustZone" reimplementation is called exosphère.
Learn more about ARM Exception Levels [here](https://developer.arm.com/documentation/102412/0103/Privilege-and-Exception-levels/Exception-levels). - - **Q: What exactly is the "emuMMC path," and why is it recommended for the microSD card to be at least 128GB for this path?**
- A: The purpose of an emuMMC/emuNAND is to give you a safe place to use custom firmware functions without Nintendo catching sight. As it is an offline clone of your internal storage ran entirely from your microSD card, you will need to set allocate up to 64GB on your microSD card for it (depending on the size of your internal storage), plus a duplicate your of digital game data (emuMMC uses a separate Nintendo folder for game installs). + - **Q: What exactly is the "emuMMC path," and why is it recommended for the microSD card to be at least 128GB for this path?**
+ A: The purpose of an emuMMC/emuNAND is to give you a safe place to use custom firmware functions without Nintendo catching sight. As it is an offline clone of your internal storage ran entirely from your microSD card, you will need to set allocate up to 64GB on your microSD card for it (depending on the size of your internal storage), plus a duplicate your of digital game data (emuMMC uses a separate Nintendo folder for game installs). - - **Q: Why do I need to set my console as primary before starting this guide?**
- A: The Switch will otherwise try to connect to Nintendo servers before starting apps, which can lead to unexpected delays and make emuMMCs completely unusable. + - **Q: Why do I need to set my console as primary before starting this guide?**
+ A: The Switch will otherwise try to connect to Nintendo servers before starting apps, which can lead to unexpected delays and make emuMMCs completely unusable. - - **Q: Can I follow this guide if I have a smaller microSD card, and what are the risks involved in choosing the sysCFW path?**
- A: Nothing stops you from using sysCFW, but it is recommended for first-timers to get familiar with CFW by starting with an emuMMC. If used improperly, running sysCFW can cause software bricks and/or [bans](https://nx.eiphax.tech/ban.html). + - **Q: Can I follow this guide if I have a smaller microSD card, and what are the risks involved in choosing the sysCFW path?**
+ A: Nothing stops you from using sysCFW, but it is recommended for first-timers to get familiar with CFW by starting with an emuMMC. If used improperly, running sysCFW can cause software bricks and/or [bans](https://nx.eiphax.tech/ban.html). - - **Q: Are there any specific restrictions or limitations imposed by Nintendo on consoles running custom firmware and homebrew?**
- A: Nintendo has shown a distinct tolerance for users using CFW while online. They __do not__ ban for the presence of CFW, they ban for misbehavior - such as piracy or cheating online. Otherwise, you are treated like all other users. + - **Q: Are there any specific restrictions or limitations imposed by Nintendo on consoles running custom firmware and homebrew?**
+ A: Nintendo has shown a distinct tolerance for users using CFW while online. They __do not__ ban for the presence of CFW, they ban for misbehavior - such as piracy or cheating online. Otherwise, you are treated like all other users. - - **Q: Is there any community support or forums recommended for users who may have questions or issues during the process?**
- A: Of course! As well as the [Nintendo Homebrew Discord server](https://discord.gg/C29hYvh), you can also try the [r/SwitchHacks subreddit](https://www.reddit.com/r/SwitchHacks/)! + - **Q: Is there any community support or forums recommended for users who may have questions or issues during the process?**
+ A: Of course! As well as the [Nintendo Homebrew Discord server](https://discord.gg/C29hYvh), you can also try the [r/SwitchHacks subreddit](https://www.reddit.com/r/SwitchHacks/)! diff --git a/docs/user_guide/all/cfw_environment.md b/docs/user_guide/all/cfw_environment.md index 7fa20ea8..0931ba0d 100644 --- a/docs/user_guide/all/cfw_environment.md +++ b/docs/user_guide/all/cfw_environment.md @@ -97,8 +97,8 @@ For more information on terminology, please refer to the [glossary](../../extras Modchips directly infiltrate communication with the internal storage chip. Due to this, there are slight chances of NAND backups being tainted with corrupted data. If a bad backup is restored to sysNAND, the console can be bricked, and a modchip alone won't be able to fix it. To be safe, we recommend setting up an emuMMC on a console with a modchip, verify BOOT0/1 backups using tools like [NXNandManager (Windows)](https://github.com/eliboa/NxNandManager) or test NAND backups by running them as emuMMCs before you flash them to the sysNAND. ??? "Frequently Asked Questions about this page" - - **Q: Why is CFW referred to as being "never permanently installed"?**
- A: Unless you have a modchip of any kind, turning the console off will disactivate the custom firmware. There is no current method for Atmosphère to install-to or permanently replace any part of the Nintendo Switch, so it will need to be triggered by an exploit every time you turn on the console. Atmosphère will then patch Horizon to bring you custom firmware features. + - **Q: Why is CFW referred to as being "never permanently installed"?**
+ A: Unless you have a modchip of any kind, turning the console off will disactivate the custom firmware. There is no current method for Atmosphère to install-to or permanently replace any part of the Nintendo Switch, so it will need to be triggered by an exploit every time you turn on the console. Atmosphère will then patch Horizon to bring you custom firmware features. - - **Q: Should I personally use sys/emuMMC?**
- A: These questions are answered in detail within the webpage. Please make sure that you are fully reading the page before jumping here. + - **Q: Should I personally use sys/emuMMC?**
+ A: These questions are answered in detail within the webpage. Please make sure that you are fully reading the page before jumping here. diff --git a/docs/user_guide/all/launching_cfw.md b/docs/user_guide/all/launching_cfw.md index e9a03e77..69232d67 100644 --- a/docs/user_guide/all/launching_cfw.md +++ b/docs/user_guide/all/launching_cfw.md @@ -62,10 +62,10 @@ If you've partitioned your microSD card for preparation of Android/Linux earlier [Android installation guide :material-arrow-right:](../../extras/installing_android.md){ .md-button .md-button--primary } [Linux installation guide :material-arrow-right:](../../extras/installing_linux.md){ .md-button .md-button--primary } ??? "Frequently Asked Questions about this page" - - **Q: How can you verify that sysCFW / emuMMC launched properly?**
- A: Once you boot into the Switch's HOME Menu, navigate to Settings > System. The system version should be prefixed with an S or E, standing for SysMMC or EmuMMC respectively. Seeing either of these confirms which environment you are using. - - **Q: What options do you have for rebooting to Hekate while booted into CFW?**
- A: If you use a modchip, your console will automatically boot into whatever payload that your modchip would normally boot into via a coldboot, after clicking the restart button in the power-off menu. This can be any payload, but ideally is Hekate. - If you use no modchip (and you're using a V1 console), your console will "reboot-to-payload" by default, triggering whatever fusee payload is located in `atmosphere/reboot_to_payload.bin`. This can be any payload, but ideally is Hekate. - - **Q: Where can I find additional homebrew apps?**
- A: One of the more convenient sources is the (Homebrew App Store)[https://github.com/fortheusers/hb-appstore/releases], hosted by (4TU)[https://gitlab.com/4TU]. You can also browse the (r/SwitchHacks)[https://www.reddit.com/r/SwitchHacks/] subreddit. + - **Q: How can you verify that sysCFW / emuMMC launched properly?**
+ A: Once you boot into the Switch's HOME Menu, navigate to Settings > System. The system version should be prefixed with an S or E, standing for SysMMC or EmuMMC respectively. Seeing either of these confirms which environment you are using. + - **Q: What options do you have for rebooting to Hekate while booted into CFW?**
+ A: If you use a modchip, your console will automatically boot into whatever payload that your modchip would normally boot into via a coldboot, after clicking the restart button in the power-off menu. This can be any payload, but ideally is Hekate. + If you use no modchip (and you're using a V1 console), your console will "reboot-to-payload" by default, triggering whatever fusee payload is located in `atmosphere/reboot_to_payload.bin`. This can be any payload, but ideally is Hekate. + - **Q: Where can I find additional homebrew apps?**
+ A: One of the more convenient sources is the (Homebrew App Store)[https://github.com/fortheusers/hb-appstore/releases], hosted by (4TU)[https://gitlab.com/4TU]. You can also browse the (r/SwitchHacks)[https://www.reddit.com/r/SwitchHacks/] subreddit. diff --git a/docs/user_guide/all/making_essential_backups.md b/docs/user_guide/all/making_essential_backups.md index 1940ae31..c7ff6b9d 100644 --- a/docs/user_guide/all/making_essential_backups.md +++ b/docs/user_guide/all/making_essential_backups.md @@ -3,11 +3,11 @@ ### **Making a NAND Backup** !!! danger "Important" - A NAND backup is crucial to have, it's a full backup of the internal storage of your Switch and can be used to restore the device to a working state in case of emergencies. **DO NOT SKIP THIS STEP** + A NAND backup is crucial to have, it's a full backup of the internal storage of your Switch and can be used to restore the device to a working state in case of emergencies. **DO NOT SKIP THIS STEP** - 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. + 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 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. + 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:** @@ -54,5 +54,5 @@ ??? "Frequently Asked Questions about this page" - - **Q: Why is making a NAND backup considered crucial?**
+ - **Q: Why is making a NAND backup considered crucial?**
A: A NAND backup contains a complete snapshot of the internal files of your Switch, including console-specific files that cannot be regenerated if accidentally lost. This is why it is **mandatory** to keep at least one copy of your NAND backup in a safe place, even if it takes a lot of space. The consequence to not having one is, at best, a Switch that cannot connect to Nintendo Network, or at worst, a full brick. However, it is important to note that it is nearly impossible to permanently brick a hackable Nintendo Switch. diff --git a/docs/user_guide/getting_started.md b/docs/user_guide/getting_started.md index fa9a9ce2..c85db2ca 100644 --- a/docs/user_guide/getting_started.md +++ b/docs/user_guide/getting_started.md @@ -90,9 +90,9 @@ Before setting up for homebrew, install at least one eShop title to utilize "tit ??? "Frequently Asked Questions about this page" - - **Q: How reliable is the crowdsourced list of vulnerable serial numbers, and what if my serial number is not listed?**
- A: To our knowledge, there hasn't been a single console which has disproved the trends documented here. Unless your serial is potentially patched, you can be certain that the table is accurate to reality. - - **Q: Why is it essential to install at least one eShop title before setting up homebrew, and what is "title takeover"?**
- A: By default, the homebrew menu and its apps inherit the resources of the Album applet. Applets don't have as many system resources as full apps, and as such have inconsistent behavior when used for homebrew purposes. Title takeover ensures the best performance, and is required for some homebrew. - - **Q: Why is the "New" Switch (HAC-001(-01) not vulnerable to *déjà vu*, and what are the implications for Switch Lite (HDH-001) and OLED Switch consoles?**
- A: Despite being exploitable via software, *déjà vu* is actually a bootROM exploit that isn't present in the new bootROM of the Tegra X1+. + - **Q: How reliable is the crowdsourced list of vulnerable serial numbers, and what if my serial number is not listed?**
+ A: To our knowledge, there hasn't been a single console which has disproved the trends documented here. Unless your serial is potentially patched, you can be certain that the table is accurate to reality. + - **Q: Why is it essential to install at least one eShop title before setting up homebrew, and what is "title takeover"?**
+ A: By default, the homebrew menu and its apps inherit the resources of the Album applet. Applets don't have as many system resources as full apps, and as such have inconsistent behavior when used for homebrew purposes. Title takeover ensures the best performance, and is required for some homebrew. + - **Q: Why is the "New" Switch (HAC-001(-01) not vulnerable to *déjà vu*, and what are the implications for Switch Lite (HDH-001) and OLED Switch consoles?**
+ A: Despite being exploitable via software, *déjà vu* is actually a bootROM exploit that isn't present in the new bootROM of the Tegra X1+. diff --git a/docs/user_guide/modchip/index.md b/docs/user_guide/modchip/index.md index 3a3cf72c..433e3680 100644 --- a/docs/user_guide/modchip/index.md +++ b/docs/user_guide/modchip/index.md @@ -50,17 +50,17 @@ If you do decide to follow the recommended emuMMC path later in the guide, make [Continue to Preparing Hekate :material-arrow-right:](preparing_hekate.md){ .md-button .md-button--primary } ??? "Frequently Asked Questions about this page" - - **Q: Can you provide more information about modchip firmwares, specifically regarding their impact on the boot process and the ability to bypass the sdloader?**
- A: Modchip firmwares indirectly determine the functionality of your system. Modern modchips (such as Picofly) typically have firmware flashed to them that support all hardware configurations (namely eMMC brands like Hynix, Samsung and Toshiba) "out-of-the-box" and also allow you to bypass `sdloader`. If this is not the case however, flashing the firmware manually is required by opening up the Switch and using the USB debug port that comes with the modchip to flash the modchip directly. This is especially required in the cases where the eMMC brand is not supported, as your Switch wouldn't boot whatsoever and the modchip would be stuck while trying to glitch/train and write its payload to the `BOOT0` partition of the internal storage. + - **Q: Can you provide more information about modchip firmwares, specifically regarding their impact on the boot process and the ability to bypass the sdloader?**
+ A: Modchip firmwares indirectly determine the functionality of your system. Modern modchips (such as Picofly) typically have firmware flashed to them that support all hardware configurations (namely eMMC brands like Hynix, Samsung and Toshiba) "out-of-the-box" and also allow you to bypass `sdloader`. If this is not the case however, flashing the firmware manually is required by opening up the Switch and using the USB debug port that comes with the modchip to flash the modchip directly. This is especially required in the cases where the eMMC brand is not supported, as your Switch wouldn't boot whatsoever and the modchip would be stuck while trying to glitch/train and write its payload to the `BOOT0` partition of the internal storage. - - **Q: What different types of modchips are there?**
- A: There are three main types of modchips for the Nintendo Switch. Only two of them are relevant for this guide.
- On the V1 Nintendo Switch, a chip can be installed which automatically injects a payload whenever the console is detected in RCM. This type of modchip is **not** supported by this guide.
- On all other Switch consoles, there are DIY "Picofly" modchips which can be created with Raspberry Pi parts and custom cables. These use special firmwares, and are not compatible with firmwares intended for other modchips.
- There are also other "commercial" modchips of dubious origin by the name of "hwfly" or "SX Core/Lite"; we only will help with flashing new firmwares onto these, if you happen to already have one of them installed. Do not ask for assistance installing or sourcing this type of modchip. + - **Q: What different types of modchips are there?**
+ A: There are three main types of modchips for the Nintendo Switch. Only two of them are relevant for this guide.
+ On the V1 Nintendo Switch, a chip can be installed which automatically injects a payload whenever the console is detected in RCM. This type of modchip is **not** supported by this guide.
+ On all other Switch consoles, there are DIY "Picofly" modchips which can be created with Raspberry Pi parts and custom cables. These use special firmwares, and are not compatible with firmwares intended for other modchips.
+ There are also other "commercial" modchips of dubious origin by the name of "hwfly" or "SX Core/Lite"; we only will help with flashing new firmwares onto these, if you happen to already have one of them installed. Do not ask for assistance installing or sourcing this type of modchip. - - **Q: Can you further explain the concept of running homebrew "over a title" and why it allows for higher resource allocation?**
- A: The default way to run homebrew within Atmosphère is via the Album applet on the HOME Menu. However, applets have significantly less resources compared to full applications, and homebrew tools often run into constraints with these limits. By holding a button while launching normal apps while in CFW, you can load the Homebrew menu in their stead with full resources. + - **Q: Can you further explain the concept of running homebrew "over a title" and why it allows for higher resource allocation?**
+ A: The default way to run homebrew within Atmosphère is via the Album applet on the HOME Menu. However, applets have significantly less resources compared to full applications, and homebrew tools often run into constraints with these limits. By holding a button while launching normal apps while in CFW, you can load the Homebrew menu in their stead with full resources. - - **Q: What makes Picofly the only supported modchip, and what are the potential risks associated with installing a modchip on your Switch without proper experience?**
- A: Picofly is a fully open-source modchip, from the firmware to the RP2040 microcontroller it uses. Other "commercial" modchips have dubious origins, or were manufactured by [established illegal piracy groups](https://www.justice.gov/opa/pr/two-members-notorious-videogame-piracy-group-team-xecuter-custody) that have no place in the homebrew community. For the safety of your console and to respect the law of where NH Server is based, we will not assist with sourcing these types of modchips. + - **Q: What makes Picofly the only supported modchip, and what are the potential risks associated with installing a modchip on your Switch without proper experience?**
+ A: Picofly is a fully open-source modchip, from the firmware to the RP2040 microcontroller it uses. Other "commercial" modchips have dubious origins, or were manufactured by [established illegal piracy groups](https://www.justice.gov/opa/pr/two-members-notorious-videogame-piracy-group-team-xecuter-custody) that have no place in the homebrew community. For the safety of your console and to respect the law of where NH Server is based, we will not assist with sourcing these types of modchips. diff --git a/docs/user_guide/rcm/entering_rcm.md b/docs/user_guide/rcm/entering_rcm.md index 8f54ccfa..20e0be39 100644 --- a/docs/user_guide/rcm/entering_rcm.md +++ b/docs/user_guide/rcm/entering_rcm.md @@ -59,7 +59,7 @@ Methods to enter RCM can require nothing more than household items (not recommen #### Wire reference: ![wire reference](../rcm/img/entering_rcm_button_1.jpg){ width="675"} - 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 rail 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. + 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 rail 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. #### Joy-Con button: ![eip joycon button reference](../rcm/img/entering_rcm_button_5.jpg){ width="650"} diff --git a/docs/user_guide/rcm/index.md b/docs/user_guide/rcm/index.md index 5cbbc08d..3b785bb9 100644 --- a/docs/user_guide/rcm/index.md +++ b/docs/user_guide/rcm/index.md @@ -10,8 +10,8 @@ If you choose the emuMMC path introduced later in the guide, it'll be important [Continue to Entering RCM :material-arrow-right:](entering_rcm.md){ .md-button .md-button--primary } ??? "Frequently Asked Questions about this page" - - **Q: How does the RCM exploit work on unpatched Nintendo Switch consoles?**
- A: For more information, please reference [this page](../../fusee_gelee.md). There is also a Medium article about it [here](https://medium.com/@SoyLatteChen/inside-fus%C3%A9e-gel%C3%A9e-the-unpatchable-entrypoint-for-nintendo-switch-hacking-26f42026ada0). + - **Q: How does the RCM exploit work on unpatched Nintendo Switch consoles?**
+ A: For more information, please reference [this page](../../fusee_gelee.md). There is also a Medium article about it [here](https://medium.com/@SoyLatteChen/inside-fus%C3%A9e-gel%C3%A9e-the-unpatchable-entrypoint-for-nintendo-switch-hacking-26f42026ada0). - - **Q: Does RCM work on patched consoles?**
- A: Yes. RCM is an intended mode for all Switch consoles. The exploit is the unintended effect that only some consoles can use. Consoles with the Tegra X1+ have a completely new bootROM with no evidence of the exploit, while "patched" V1 systems have an IROM patch to the bootROM applied that effectively removes fusee-gelee as well. + - **Q: Does RCM work on patched consoles?**
+ A: Yes. RCM is an intended mode for all Switch consoles. The exploit is the unintended effect that only some consoles can use. Consoles with the Tegra X1+ have a completely new bootROM with no evidence of the exploit, while "patched" V1 systems have an IROM patch to the bootROM applied that effectively removes fusee-gelee as well. diff --git a/docs/user_guide/rcm/sending_payload.md b/docs/user_guide/rcm/sending_payload.md index 5e2b244b..11f22abb 100644 --- a/docs/user_guide/rcm/sending_payload.md +++ b/docs/user_guide/rcm/sending_payload.md @@ -44,7 +44,7 @@ Now that the device is in RCM, we will need to send it a payload. The methods ar #### **What you need:** - The latest release of [fusee-nano](https://github.com/DefenderOfHyrule/fusee-nano/releases) (also available on the [AUR](https://aur.archlinux.org/packages/fusee-nano)) - - If you use Arch Linux or a derivative distro, the AUR package is recommended. + - If you use Arch Linux or a derivative distro, the AUR package is recommended. - A USB-A to USB-C cable (or a standard USB-C cable if your computer natively supports USB-C) - The latest release of Hekate. The Hekate payload (`hekate_ctcaer_(version).bin`) is located inside of the `hekate_ctcaer_(version).zip`.