Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ entries, updated outdated info, large scale grammar fixes #185

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 8 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/extras/adding_udev.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <a href="https://github.com/pheki/nx-udev" target="_blank">nx-udev</a>, or if you're on Ubuntu / Debian:

Expand Down
14 changes: 7 additions & 7 deletions docs/extras/alternate_bootsetups.md
Original file line number Diff line number Diff line change
Expand Up @@ -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


Expand All @@ -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`
30 changes: 15 additions & 15 deletions docs/extras/autorcm.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
## AutoRCM
## autoRCM
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is called AutoRCM in Hekate, so it's probably better to stick with the capitalized A


!!! 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**.
Expand All @@ -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`
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.
28 changes: 13 additions & 15 deletions docs/extras/blocking_nintendo.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:

- <a href="../../files/emummc.txt" download>emummc.txt</a>
- Atmosphere 0.18.0 or higher

#### 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
- 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 ""
Expand All @@ -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.
Expand All @@ -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.
ha1vorsen marked this conversation as resolved.
Show resolved Hide resolved
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` |
Expand All @@ -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
ha1vorsen marked this conversation as resolved.
Show resolved Hide resolved
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)


2 changes: 1 addition & 1 deletion docs/extras/dumping_title_keys.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion docs/extras/game_modding.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading