added admonition to the android installation page for android 14, rew…

…orded section at the bottom of faq, fixed links in faq (external links, changed to local links) and added link to defender's modchip installation guide on modchip introduction page

docs/extras/installing_android.md

@@ -1,6 +1,6 @@
 # Installing Android
 
-This page will detail the setup of the latest release of Switchroot Android (Android 11) for the Nintendo Switch.
+This page will detail the setup of Switchroot Android (Android 11) for the Nintendo Switch.
 
 !!! warning "Have you partitioned your microSD card?"
     This page assumes that you've followed our guide to set up Atmosphère. Before starting, your microSD card needs partitions for Android set up via Hekate.<br>
@@ -10,6 +10,9 @@ This page will detail the setup of the latest release of Switchroot Android (And
 !!! info "Looking for Android 10?"
     An unfortunate bug with clocking on Android 11 results in degraded performance for Erista (v1) units on Android 11. Android 10 installation is not covered here, but there is a [guide](https://wiki.switchroot.org/wiki/android/10-q-setup-guide) on the Switchroot Wiki. However, Android 11 is the currently supported version and uses much more updated drivers.
 
+!!! info "Looking for Android 14?"
+    Recently, Android 14 was released for the Switch. You can follow the official [LineageOS guide](https://wiki.lineageos.org/devices/nx_tab/) to install Android 14.
+
  The Switch lacks a cell modem; simply installing Android does not grant your Switch access to cell towers. This means, unlike most Android devices, you will not be able to make emergency phone calls, and you will still need Wi-Fi to access the Internet. You can, however, natively run Android programs and games.
 
 This page will also *not* detail things such as rooting and overclocking; external links to these types of additions can be found in the [Power User Guides](#power-user-guides) section at the bottom of this page.

docs/extras/transfer_sd.md

@@ -9,7 +9,7 @@ We will be using [hekate](https://github.com/CTCaer/hekate/releases/) to both ba
 You should first check whether you have a file or partition based emuMMC:
 
 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.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your microSD card.
 2.  Tap on the `emuMMC` button.
 3.  Under `emuMMC Info & Selection`, check the text next to `Type`.
     - If you have one it should be either `SD Raw Partition` or `SD File`.
@@ -18,7 +18,7 @@ You should first check whether you have a file or partition based emuMMC:
 ### **If you are using a file based emuMMC or are using no emuMMC at all:**
 
 1. Enter RCM and inject the Hekate payload.
-    - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your SD.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your microSD card.
 2. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
 2. Copy the contents of your microSD card somewhere to your PC.
 4. Access your new microSD card via a microSD card reader or similar.
@@ -30,15 +30,15 @@ You should first check whether you have a file or partition based emuMMC:
 -----
 ### **If you are using a partition based emuMMC:**
 
-!!!warning "Space for the backup"
+!!! warning "Space for the backup"
     You need at least 30GB (or 60GB if using an OLED Switch) of free space to be able to restore the emuMMC!
 
 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.
 2.  In the main menu, tap on `Tools`, then `Backup eMMC` and set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
 3.  Backup both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
 4.  Once both are done, go back to the main menu, navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
-5.  If Windows asks you to format a drive, discard it and select the drive with your SD contents.
+5.  If Windows asks you to format a drive, discard it and open the accessible drive containing the contents of your microSD card.
 6.  Copy the contents of your old microSD card somewhere to your PC.
 7.  Follow the `Preparing Hekate` section at the bottom of [this page](../user_guide/rcm/sending_payload.md) (Unpatched Switch users only) to prepare your new SD card with Hekate's files.
     - If you have a modchipped Switch, follow [this page](../user_guide/modchip/preparing_hekate.md) instead.
@@ -48,7 +48,7 @@ You should first check whether you have a file or partition based emuMMC:
 10. Navigate to `/backup/<some characters>/emummc` on your microSD card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to `/backup/<some characters>/restore/emummc`.
 11. Eject the `UMS` device safely from within your computer's operating system.
 12. Tap on `Tools`, `Restore eMMC`, set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
-13. Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP may take a while).
+13. Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
     - It is very important that for both of these the `SD emuMMC Raw Partition` option is enabled, otherwise you will be altering your sysMMC
       which is not what you want.
 14. 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.

docs/extras/updating.md

@@ -15,7 +15,7 @@ When a new version of Atmosphère releases, you can update Atmosphère by follow
 
 
 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.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your microSD card.
 2. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
 3. Download the latest release of <a href="https://github.com/Atmosphere-NX/Atmosphere/releases" target="_blank">Atmosphere</a> (Download the `atmosphere-(version)-master-(version)+hbl-(version)+hbmenu-(version).zip` release of Atmosphere.)
 4. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD card.
@@ -30,7 +30,7 @@ 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. 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.
+    - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your microSD card.
 2. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
 3. Download the latest version of <a href="https://github.com/CTCaer/Hekate/releases/" target="_blank">Hekate</a> (Download the `hekate_ctcaer_(version).zip` release of hekate).
 4. 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.
@@ -74,12 +74,12 @@ If you keep your emuMMC offline, you will have to use a gamecard to update your
 
 ### **Updating emuMMC by dumping an updated firmware from your sysMMC**
 
-!!!warning "Do you have an eMMC backup yet?"
+!!! warning "Do you have an eMMC backup yet?"
     Please do not start this guide without doing a RAW GPP and a BOOT 0/1 eMMC backup!
 
     You can learn how to make one [here](../user_guide/all/making_essential_backups.md).
 
-!!!danger "Downgrading"
+!!! danger "Downgrading"
     This guide is made for updating your emuMMC. It is **not** for downgrading. Downgrading at all, sysMMC or emuMMC, is not recommended and not worth it. Downgrading is also very dangerous and can lead to serious complications even when performed correctly.
 
 #### **What you need:**
@@ -88,18 +88,18 @@ If you keep your emuMMC offline, you will have to use a gamecard to update your
 
 #### **Preparing your microSD card**
 
-1. Load Hekate, start Hekate UMS by going to `Tools` > `USB Tools` > `SD Card`
-2. Connect your Switch to your PC via a USB cable. An Android phone may also work.
-3. Download `TegraExplorer.bin` and place it somewhere on your device (A good idea is to put it where you keep all your Switch payloads like Hekate).
-4. Update Atmosphère and Hekate by using the above guides.
-5. If you haven't already, update the sysMMC to the latest firmware using the steps below.
+1. Boot into Hekate.
+2. Go to `Tools` > `USB Tools` > `SD Card` and connect your Switch to your PC via USB.
+3. Download the latest release of `TegraExplorer.bin` and place it `sd:/bootloader/payloads`.
+
+Make sure your sysMMC is updated before moving onto the instructions below.
 
 #### **Dumping your sysMMC firmware**
 
 1. Make sure your sysMMC is up to date. If your sysMMC is not up-to-date, boot into Stock or sysCFW and update it through the System Settings.
     - sysCFW is recommended since it preserves e-fuses and preserves AutoRCM (if applicable).
 2. Inject `TegraExplorer.bin` using your favourite payload injector (Like you would with Hekate).
-    - If you are using a modchipped Switch, you can simply put `TegraExplorer.bin` in `sd:/bootloader/payloads` on your SD card, then turn on your console and load TegraExplorer via Hekate's payloads menu (`Payloads` > `TegraExplorer.bin`).
+    - If you are using a modchipped Switch, you can simply put `TegraExplorer.bin` in `sd:/bootloader/payloads` on your microSD card, then turn on your console and load TegraExplorer via Hekate's payloads menu (`Payloads` > `TegraExplorer.bin`).
 3. Using the joystick and the A buttons, select `FirmwareDump.te`, then select `Dump sysmmc`.
     - If navigation doesn't work with your Joycons, navigating using the volume buttons and selecting using the power button also works.
       (This is also required for Switch Lite console users.)

docs/faq.md

@@ -11,11 +11,11 @@ The serial number on the back of the box can possibly tell you which consoles ar
 See <a href="https://gbatemp.net/threads/switch-informations-by-serial-number.481215/" target="_blank">here</a> for an up to date list.
 
 
-### **How do I use the exploit? How can I boot into RCM?**
+### **How do I use fusee-gelee? How can I boot into RCM?**
 
-To launch CFW through the exploit, the Switch needs to be in "Recovery Mode"(RCM).
+To launch CFW through the fusee-gelee, 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.
+Several methods and designs to do this exist, see [our guide](user_guide/rcm/entering_rcm.md) 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.
@@ -139,14 +139,15 @@ If you suspect your microSD card is fake or damaged, see the instructions <a hre
 
 
 
-### **My homebrew is not showing up on the menu**
+### **My Homebrew apps are not showing up in the Homebrew menu!**
 
-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 may need to unset the archive bit with Hekate.
+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 apps, you may 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/)
-2. Click on `Tools` on the top menu bar
-3. In the bottom left corner click on `Arch Bit • AutoRCM • Touch • Pkg1/2`
-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.
+1. Inject the Hekate payload using your favorite payload injector.
+    - If you have a modchipped Switch, place the Hekate payload on the root of your microSD card and rename it to payload.bin, reinsert your microSD card into your Switch and turn it on.
+2. Click on `Tools` on the top menu bar.
+3. In the bottom left corner click on `Arch Bit • AutoRCM • Touch • Pkg1/2`.
+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/all/launching_cfw.md/) to launch Atmosphere.

docs/user_guide/getting_started.md

@@ -65,7 +65,7 @@ If your serial number is not listed above, your device is not vulnerable to the
 | 8.1.0 and up     | [**RCM**](rcm/index.md)               | [**Modchip**](modchip/index.md) (no software exploit)          | [**Modchip**](modchip/index.md) (no software exploit)| [**Modchip**](modchip/index.md) (no software exploit)|
 
 !!! note "About Mariko Switch models"
-    All Mariko (V2) Switch models (`HAC-001(-01)`, `HDH-001`, `HEG-001`) are currently unhackable via software. If **Modchip** is listed as a method for your console model, then that means the device is currently unhackable without a hardware modification. If there are theoretical exploits that may lead to CFW or homebrew for that device, you also have the choice to "wait" for their release. These exploits may (and will likely) never launch and there is **NO ETA**, so what you choose to do is up to you. This guide assumes you have a functional modchip installation if you *do* have a Patched console.
+    All Mariko (V2) Switch models (`HAC-001(-01)`, `HDH-001`, `HEG-001`) are currently unhackable via software. If **Modchip** is listed as a method for your console model, then that means the device is currently unhackable without a hardware modification (modchip). If there are theoretical exploits that may lead to CFW or homebrew for that device, you also have the choice to "wait" for their release. These exploits may (and will likely) never launch and there is **NO ETA**, so what you choose to do is up to you. This guide assumes you have a functional modchip installation if you *do* have a Patched console.
 
 
 ### **Console Preparation**

docs/user_guide/modchip/index.md

@@ -1,8 +1,19 @@
 ### **Introduction to Modchips**
 
-!!! info "information"
-    Unlike "unpatched" consoles, modchips enable CFW via CPU voltage glitching, which bypass bootROM firmware verifications. It allows a ``payload.bin`` file to be launched in place of BOOT0, loaded via a modchip firmware module named `sdloader`. This is much different from RCM and its exploit, [fusee-gelee](https://github.com/Qyriad/fusee-launcher/blob/master/report/fusee_gelee.md), which "unpatched" consoles use.
-    Modchips allow any console (like all "patched" consoles) to run CFW!
+### **Prerequisites**
+A modchip is a physical modification to the motherboard of your Switch. It cannot be installed without decent microsoldering experience. You can outsource this work to people who are willing to do the job for you, or you can also view the following guide if you are willing to install one yourself.
+
+[Modchip Installation guide](https://guide.nx-modchip.info/){ .md-button .md-button--primary }
+
+**Note:** The above guide is not hosted or supported by NH Server; we cannot provide support for reviving consoles ruined by inexperience.
+
+-----
+
+### **Information**
+Unlike "unpatched" consoles, modchips enable CFW via CPU voltage glitching, which bypass bootROM firmware verifications. It allows a ``payload.bin`` file to be launched in place of BOOT0, loaded via a modchip firmware module named `sdloader`. This is much different from RCM and its exploit, [fusee-gelee](https://github.com/Qyriad/fusee-launcher/blob/master/report/fusee_gelee.md), which "unpatched" consoles use.
+Modchips allow any console, including all patched consoles, to run CFW!
+
+-----
 
 ### **General knowledge**
 
@@ -33,7 +44,7 @@ If you do decide to follow the recommended emuMMC path later in the guide, make
 !!! danger "Disclaimer"
     We **ONLY** support the Picofly modchip (the `RP2040 Zero` development board and the "modchip variant" of it). Installing a modchip safely is your responsibility, so if you don't trust yourself, get someone trusted to perform the install.
     There is always a risk of your Switch being rendered dysfunctional when messing with its hardware without proper experience.
-    The NH-Discord server is not for fixing bad modchip installations.
+    The NH-Discord server is not for fixing bad/failed modchip installations.
     We can give advice and installation tips for the installation as long as it's for a Picofly modchip.
 
 [Continue to Preparing Hekate :material-arrow-right:](preparing_hekate.md){ .md-button .md-button--primary }