Skip to content

Commit 0d45385

Browse files
DefenderOfHyruleDefenderOfHyrule
committed
update hekate_ipl.ini to reflect changes for hekate 6.3.0, update updating CFW page for an alternative way of dumping firmware, added instruction to SD prep page for macOS users, edited blocking Nintendo servers page to align with the NH server's terminologies, file/folder tree was added to the SD prep page, general improvements across several pages were added
1 parent 18f59a1 commit 0d45385

File tree

11 files changed

+269
-88
lines changed

11 files changed

+269
-88
lines changed

‎docs/extras/blocking_nintendo.md‎

Lines changed: 69 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22

33
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.
44

5-
## Instructions (AMS DNS redirection)
6-
You can configure Atmosphère 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.
5+
## Instructions (DNS.MITM)
6+
You can configure Atmosphère 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 your emuMMC (unless applied on sysCFW).
77

88
### What you need:
9-
- <a href="/files/emummc.txt" download>emummc.txt</a>
9+
- The <a href="/files/emummc.txt" download>emummc.txt</a> file
1010
- Atmosphère 0.18.0 or higher
1111

1212
### Setup:
@@ -18,63 +18,110 @@ You can configure Atmosphère to automatically redirect any requests directed to
1818
1. If it doesn't exist already, create a folder named `hosts` in the `atmosphere` folder.
1919
- You should end up with the `sd:/atmosphere/hosts` directory.
2020
1. Copy the `emummc.txt` file into the hosts folder.
21-
- If you want to apply the DNS redirection to sysmmc instead of emummc, rename the file to `sysmmc.txt`
21+
- If you want to apply the DNS redirection to sysmmc instead of emummc, rename the file to `sysmmc.txt`.
2222
1. Eject the `UMS` device safely from within your computer's operating system and boot into CFW.
2323

2424
::: tip
2525

26-
**Verify functionality**
27-
28-
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.
29-
30-
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
31-
32-
![dnsmitmlog](../extras/img/dnsmitm.png)
33-
26+
**Verifying functionality**
27+
28+
You can verify the functionality of the DNS redirection by booting into emuMMC (or sysCFW, if you applied the config to sysCFW), and powering off afterwards.
29+
30+
A report will be generated in `sd:/atmosphere/logs` called `dns_mitm_startup.log`. If this file contains the following text, the DNS redirection is active.
31+
32+
```js
33+
DNS Mitm:
34+
Adding defaults to redirection list.
35+
Selecting hosts file...
36+
Skipping /hosts/emummc_<emummc_id>.txt because it does not exist...
37+
Selected /hosts/emummc.txt
38+
Redirections:
39+
`*ctest.cdn.nintendo.net` -> 95.216.149.205
40+
`*conntest.nintendowifi.net` -> 95.216.149.205
41+
`*nintendoswitch.cn` -> 127.0.0.1
42+
`*nintendoswitch.com.cn` -> 127.0.0.1
43+
`*nintendoswitch.com` -> 127.0.0.1
44+
`*nintendo.pl` -> 127.0.0.1
45+
`*nintendo.ch` -> 127.0.0.1
46+
`*nintendo.se` -> 127.0.0.1
47+
`*nintendo.co.za` -> 127.0.0.1
48+
`*nintendo.ru` -> 127.0.0.1
49+
`*nintendo.pt` -> 127.0.0.1
50+
`*nintendo.no` -> 127.0.0.1
51+
`*nintendo.nl` -> 127.0.0.1
52+
`*nintendo.it` -> 127.0.0.1
53+
`*nintendo.hu` -> 127.0.0.1
54+
`*nintendo.gr` -> 127.0.0.1
55+
`*nintendo.fr` -> 127.0.0.1
56+
`*nintendo.fi` -> 127.0.0.1
57+
`*nintendo.de` -> 127.0.0.1
58+
`*nintendo.dk` -> 127.0.0.1
59+
`*nintendods.cz` -> 127.0.0.1
60+
`*nintendo.be` -> 127.0.0.1
61+
`*nintendo.at` -> 127.0.0.1
62+
`*nintendo.co.nz` -> 127.0.0.1
63+
`*nintendo.com.au` -> 127.0.0.1
64+
`*nintendo.com.hk` -> 127.0.0.1
65+
`*nintendo.tw` -> 127.0.0.1
66+
`*nintendo.co.kr` -> 127.0.0.1
67+
`*nintendo.es` -> 127.0.0.1
68+
`*nintendowifi.net` -> 127.0.0.1
69+
`*nintendo-europe.com` -> 127.0.0.1
70+
`*nintendo.co.uk` -> 127.0.0.1
71+
`*nintendo.co.jp` -> 127.0.0.1
72+
`*nintendo.jp` -> 127.0.0.1
73+
`*nintendo.net` -> 127.0.0.1
74+
`*nintendo.com` -> 127.0.0.1
75+
`receive-lp1.er.srv.nintendo.net` -> 127.0.0.1
76+
`receive-lp1.dg.srv.nintendo.net` -> 127.0.0.1
77+
```
3478
:::
3579

3680
## Instructions (90DNS)
37-
You can add a custom DNS to your WiFi connection that will block all communication with Nintendo's servers. We will be using [90DNS](https://gitlab.com/a/90dns), a community-run custom DNS server. If you prefer, you can run your own DNS server following the instructions on the [GitLab repository.](https://gitlab.com/a/90dns/blob/master/SELFHOST.md)
81+
You can add a custom DNS to your Wi-Fi connection that will block all communication with Nintendo's servers. We will be using [90DNS](https://gitlab.com/a/90dns), a community-run custom DNS server. If you prefer, you can run your own DNS server following the instructions on the [GitLab repository.](https://gitlab.com/a/90dns/blob/master/SELFHOST.md)
3882

39-
Enter the console's System Settings, and then proceed to the Internet tab. From here:
83+
Enter the console's `System Settings`, and then proceed to the `Internet` tab. From here you can choose one of the 3 methods of setting up 90DNS below, depending on what you currently have set up on your Switch.
4084

85+
- Follow the [Setting up a new connection via Wi-Fi](#setting-up-a-new-connection-via-wi-fi) section if you wish to set up 90DNS on a Wi-Fi network you haven't connected to before.
86+
- Follow the [Editing an existing Wi-Fi connection](#editing-an-existing-wifi-connection) section if you wish to edit an existing, saved Wi-Fi network.
87+
- Follow the [Using homebrew to set 90DNS on all existing Wi-Fi networks ](#using-homebrew-to-set-90dns-on-all-existing-wifi-networks) section if you wish to use a homebrew app to configure 90DNS on all saved Wi-Fi networks.
4188

4289
### Setting up a new connection via Wi-Fi
4390

4491
::: warning
4592

46-
**Open WiFi networks without a password**
93+
**Open Wi-Fi networks without a password**
4794

48-
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.
95+
Not all Wi-Fi 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 Wi-Fi networks.
4996

5097
:::
5198

52-
1. Select your WiFi network from the list of networks.
99+
1. Select your Wi-Fi network from the list of networks.
53100
1. Enter an **incorrect** password that is 8 characters long and press `OK`.
54101
1. After a few moments of attempting to connect, the console will display a connection error.
55102
1. Press `OK` to close the error message.
56103
1. Press `Close` when it offers to display more details about the error.
57104
1. When asked if you want to re-enter the password, pick `View Settings`.
58105
1. Change `DNS Settings` to `Manual`.
59106
1. Pick the server that is the closest to your location out of the below chart and enter its `Primary` and `Secondary` DNS into your connection settings.
60-
1. Enter the correct password for your WiFi connection.
107+
1. Enter the correct password for your Wi-Fi connection.
61108
1. Save the settings and test the connection.
62109

63110
-----
64111

65-
### Editing an existing WiFi connection
66-
1. Select your existing WiFi network from the list of networks.
112+
### Editing an existing Wi-Fi connection
113+
1. Select your existing Wi-Fi network from the list of networks.
67114
1. Select `Change Settings`.
68115
1. Pick the server that is the closest to your location out of the below chart and enter its Primary and Secondary DNS into your connection settings.
69116
1. Save the settings and test the connection.
70117

71118
-----
72119

73-
### Using homebrew to set 90DNS on all existing WiFi networks
120+
### Using homebrew to set 90DNS on all existing Wi-Fi networks
74121
1. Download [switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the `/switch` folder.
75122
1. Launch CFW and open the homebrew menu.
76123
1. Launch `90DNS Setter`.
77-
1. Press X to apply 90DNS to all WiFi networks.
124+
1. Press X to apply 90DNS to all Wi-Fi networks.
78125
1. Press Y to reboot the Switch.
79126
1. Check in system settings if networks have a custom DNS applied.
80127

‎docs/extras/transfer_sd.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ You should first check whether you have a file or partition based emuMMC:
2727
- To do this, use [this guide](https://wiki.hacks.guide/wiki/Formatting_an_SD_card).
2828
1. Copy the files from your PC or directly from your old microSD card to your new microSD card.
2929
1. Eject the `UMS` device safely from within your computer's operating system.
30+
1. Boot into Hekate and launch your desired boot entry.
3031

3132
-----
3233

@@ -58,4 +59,4 @@ You need at least 30GB (or 60GB if using an OLED Switch) of free space to be abl
5859
1. Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
5960
- It is very important that for both of these the `SD emuMMC Raw Partition` option is enabled, otherwise you will be altering your sysMMC
6061
which is not what you want.
61-
1. 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.
62+
1. Your emuMMC is now restored on the new microSD card and you should be able to launch it from `Launch` -> `Atmosphere PKG3 emuMMC` in Hekate.

‎docs/extras/updating.md‎

Lines changed: 66 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -89,56 +89,103 @@ If you keep your emuMMC offline, you will have to use a gamecard to update your
8989

9090
::: warning
9191

92-
**Do you have an eMMC backup yet?**
92+
**Before starting; do you have an eMMC NAND backup?**
9393

94-
Please do not start this guide without doing a RAW GPP and a BOOT 0/1 eMMC backup!
94+
Please do not start this guide without performing an eMMC RAW GPP and eMMC BOOT0/BOOT1 NAND backup!
9595

96-
You can learn how to make one [here](../user_guide/all/making_essential_backups).
96+
You should always have *at least* one functional NAND backup, in the possible event of your console becoming "softbricked". This is not expected to happen while hollowing the steps below, but this is a general reminder for the people who *don't* have a NAND backup, as you *do* interact with internal system files during the steps below.
97+
98+
If you do already have a NAND backup stored somewhere safely, you may ignore this warning.
99+
100+
You can learn how to make a NAND backup [here](../user_guide/all/making_essential_backups).
97101

98102
:::
99103

100104
::: danger
101105

102106
**Downgrading**
103107

104-
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.
108+
This guide is made for updating your emuMMC's firmware. 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.
105109

106110
:::
107111

112+
There are two supported methods of dumping your sysMMC's firmware, these methods are detailed in the two tabs below. Either choice will provide the same end result, but can be more difficult depending on the console model you have.
113+
114+
::::: tabs
115+
116+
:::: tab Dumping your firmware via Goldleaf
117+
108118
#### What you need:
109-
- The latest release of [TegraExplorer](https://github.com/suchmememanyskill/TegraExplorer/releases)
110-
- The latest release of [Atmosphere](https://github.com/Atmosphere-NX/Atmosphere/releases)
119+
- The latest release of [Goldleaf](https://github.com/XorTroll/Goldleaf/releases) (`Goldleaf.nro`)
120+
- The latest release of [Atmosphere](https://github.com/Atmosphere-NX/Atmosphere/releases) (`atmosphere-(version)-master-(version)+hbl-(version)+hbmenu-(version).zip`)
111121

112122
#### Preparing your microSD card
113123

114124
1. Boot into Hekate.
115125
1. Go to `Tools` > `USB Tools` > `SD Card` and connect your Switch to your PC via USB.
116-
1. Download the latest release of `TegraExplorer.bin` and place it `sd:/bootloader/payloads`.
126+
1. Download the latest release of `Goldleaf.nro` and place it in `sd:/switch` on your microSD card.
127+
128+
#### Dumping your sysMMC firmware
129+
130+
1. Make sure your sysMMC is up to date. If your sysMMC is not up-to-date, boot into sysCFW and update it through `System Settings` > `System` > `System Update`.
131+
- sysCFW is recommended since it preserves e-fuses and preserves AutoRCM (if applicable).
132+
1. Boot into Hekate, and navigate to `Launch` > `Atmosphere PKG3 sysMMC`.
133+
- `Atmosphere PKG3 sysMMC` is sysCFW, this environment may be called something different if you do not use the config we provide in our guide.
134+
1. Once booted into sysCFW, open the homebrew menu in applet mode by opening the gallery applet on your home menu.
135+
- Title takeover mode (holding `R` while launching any title on your HOME menu) also works, but isn't *required* for this process.
136+
1. Find Goldleaf in your homebrew menu and launch the app.
137+
1. Navigate to `Console & Goldleaf settings` > `Firmware and updates` > `Export update` > `Directory`, then wait for Goldleaf to finish dumping your currently installed firmware version.
138+
1. Once done, reboot back to hekate by holding power for 3-4 seconds and selecting `Power Options` > `Restart`, or by using the `Reboot to Payload` homebrew app in your homebrew menu (Erista ("V1") console users only).
139+
140+
::::
141+
142+
:::: tab Dumping your firmware via TegraExplorer
143+
144+
#### What you need:
145+
- The latest release of [TegraExplorer](https://github.com/suchmememanyskill/TegraExplorer/releases) (`TegraExplorer.bin`)
146+
147+
::: warning
148+
149+
On Mariko ("V2") consoles, this method of dumping the sysMMC's firmware requires you to have dumped your console's `prod.keys` prior to starting the steps below. To do this, you will need Lockpick_RCM.
150+
- We do ***not***, under any circumstance, assist with the sourcing (locating) of the Lockpick_RCM payload, please refrain from asking about where to obtain it.
151+
152+
:::
117153

118-
Make sure your sysMMC is updated before moving onto the instructions below.
154+
#### Preparing your microSD card
155+
156+
1. Boot into Hekate.
157+
1. Go to `Tools` > `USB Tools` > `SD Card` and connect your Switch to your PC via USB.
158+
1. Download the latest release of `TegraExplorer.bin` and place it `sd:/bootloader/payloads` on your microSD card.
119159

120160
#### Dumping your sysMMC firmware
121161

122-
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.
162+
1. Make sure your sysMMC is up to date. If your sysMMC is not up-to-date, boot into sysCFW and update it through `System Settings` > `System` > `System Update`.
123163
- sysCFW is recommended since it preserves e-fuses and preserves AutoRCM (if applicable).
124-
1. Inject `TegraExplorer.bin` using your favourite payload injector (Like you would with Hekate).
125-
- 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`).
126-
1. Using the joystick and the A buttons, select `FirmwareDump.te`, then select `Dump sysmmc`.
164+
1. Boot into hekate and navigate to `Payloads` > `TegraExplorer.bin`.
165+
1. Using the joystick and the A buttons, select the `FirmwareDump.te` script, then select `Dump sysmmc`.
127166
- If navigation doesn't work with your Joycons, navigating using the volume buttons and selecting using the power button also works.
128167
(This is also required for Switch Lite console users.)
129-
1. Wait about 1-2 minutes for the script to dump your firmware.
168+
1. Wait approximately 1-2 minutes for the script to dump your firmware.
169+
- It may take a little longer depending on the specifications of your microSD card.
130170
1. When the script finishes, press any button.
131171
1. Select `Reboot to bootloader/update.bin`.
132172

133-
#### Updating your emuMMC with Daybreak
173+
::::
174+
175+
:::::
176+
177+
#### Updating your emuMMC's firmware with Daybreak
134178

135-
1. In Hekate go to `Launch -> Atmosphere FSS0 emuMMC`.
136-
1. Once booted, hold `R` while launching a game to boot into the homebrew menu.
179+
1. In Hekate go to `Launch -> Atmosphere PKG3 emuMMC`.
180+
1. Once booted into your emuMMC, open the homebrew menu in applet mode by launching the gallery applet on your HOME menu.
181+
- Title takeover mode (holding `R` while launching any title on your HOME menu) also works, but isn't *required* for this process.
137182
1. Find Daybreak in the homebrew menu and launch it.
138-
1. Tap on `Install` and navigate to `sd:/tegraexplorer/Firmware/<latest firmware number>`.
183+
1. Tap on `Install` and follow the instructions corresponding to the method you used to dump your firmware below.
184+
- For users who dumped their firmware using Goldleaf: Navigate to `sd:/switch/Goldleaf/export/update/<latest firmware version number>`.
185+
- For users who dumped their firmware using TegraExplorer: Navigate to `sd:/tegraexplorer/Firmware/<latest firmware version number>`.
139186
1. Tap on `Continue` and then `Preserve settings`.
140187
- If you see the message `Warning: exFAT firmware is missing or corrupt`, you likely don't have the exFAT drivers installed on your sysMMC. Just press continue if this is the case.
141-
1. If it is available choose `Install (FAT32 + exFAT)`, otherwise `Install (FAT32)` and then `Continue`.
188+
1. If it is available choose `Install (FAT32 + exFAT)`, otherwise select `Install (FAT32)` and then `Continue`.
142189
1. Wait until Daybreak completes installing the dumped firmware.
143190
1. Once it completes, it will ask if you want to reboot. Tap `Reboot`.
144-
1. Once rebooted, launch into emuMMC and verify your system works. You can verify your system has been properly updated in `Settings -> System`.
191+
1. Once rebooted, launch into emuMMC and verify your system works. You can verify your system has been properly updated in `System Settings` > `System`, it will tell you the installed firmware version underneath the `System Update` button.

0 commit comments

Comments
 (0)