You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -8,17 +8,8 @@ After following our guide, your system will consist of three core elements that
8
8
9
9
When updating Atmosphère, always make sure to _read the release notes_. They may list important changes and modifications to your system.
10
10
11
-
::: warning
12
-
13
-
**Updating from below Atmosphère 1.0.0**
14
-
15
-
If you update from below Atmosphère 1.0.0, there are additional steps to follow. You will have to delete the `sept` folder from your microSD, delete `fusee-secondary.bin` from your `atmosphere` folder and update your hekate config file: <ahref="/files/emu/hekate_ipl.ini"download>hekate_ipl.ini</a> in the `bootloader` folder.
16
-
17
-
:::
18
-
19
11
When a new version of Atmosphère releases, you can update Atmosphère by following these steps:
20
12
21
-
22
13
1. Enter RCM and inject the hekate payload.
23
14
- 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.
24
15
1. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
@@ -41,83 +32,48 @@ When a new version of hekate releases, you can update by following these steps:
41
32
1. 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.
42
33
1. Eject the `UMS` device safely from within your computer's operating system.
43
34
1. Go back to hekate's main menu and press `Reload` > `Reload` to reload hekate from your microSD card.
44
-
1. From here, you're done and you can boot into CFW.
35
+
1. From here, you're done and you can boot into CFW and update your firmware. (See sections below.)
36
+
-**Note:** If your system does *not* boot as expected after updating, please consult the [Common crashes after updating](#common-crashes-after-updating) section below.
37
+
45
38
46
39
## Updating your firmware
47
40
48
41
Always check _before_ updating your system firmware if the latest version of Atmosphère _as well_ as the latest version of hekate support the firmware version you are updating towards.
49
42
50
-
In addition, updating to or past some firmwares update the gamecard firmware. Reference the table below for information about these.
51
-
52
-
| Updating from | Updating towards | Updates gamecard firmware |
| On or above 4.0.0, but below 9.0.0 | At least 4.0.1 but below 9.0.0 | No |
57
-
| On or above 4.0.0, but below 9.0.0 | 9.0.0 or above | Yes |
58
-
| On or above 9.0.0, but below 11.0.0 | At least 9.0.1 but below 11.0.0 | No |
59
-
| On or above 9.0.0, but below 11.0.0 | 11.0.0 or above | Yes |
60
-
| On or above 11.0.0 but below 12.0.0 | At least 11.0.1 but below 12.0.0 | No |
61
-
| On or above 11.0.0 but below 12.0.0 | 12.0.0 or above | Yes |
62
-
| On or above 12.0.0 but below 14.0.0 | At least 12.0.1 but below 13.2.1 | No |
63
-
| On or above 12.0.0 but below 14.0.0 | 14.0.0 or above | Yes |
64
-
| On or above 14.0.0 | Latest supported Atmosphère & hekate revision | No |
65
-
66
-
If at least one of the versions you are updating towards also updates the gamecard firmware, you will not be able to downgrade below that version without making the gamecard slot unusable until you update.
67
-
68
-
Atmosphère (and hekate) come bundled with patches that automatically disable the gamecard slot if it is detected that the system has an older gamecard firmware that would be updated. If you boot into RCM on each boot (for example by using AutoRCM), this means that the gamecard slot will not be updated and you can downgrade below that version. If this happens, you will not be able to use the gamecard slot as long as you are on the newer firmware.
69
-
70
-
Otherwise, you can safely update your system firmware through the system settings.
71
-
72
-
::: warning
73
-
74
-
**Note about autoRCM**
75
-
76
-
If you have autoRCM enabled and you're updating your system while in stock firmware, **updating will disable autoRCM** and you will need to enter RCM manually to boot custom firmware again.
77
-
78
-
To prevent autoRCM from being disabled, boot CFW on sysMMC and update through settings from there, as booting without AutoRCM <ins>will burn any preserved fuses</ins>.
79
-
80
-
:::
81
-
82
43
### About emuMMC
83
44
84
-
sysMMC and emuMMC have separate system firmwares and need to be updated separately.
85
-
86
-
If you keep your emuMMC offline, you will have to use a gamecard to update your system firmware, synchronize it with another Nintendo Switch or dump an updated firmware from your sysMMC.
45
+
Your sysMMC and emuMMC have separate system firmwares and need to be updated separately.
87
46
88
-
### Updating emuMMC by dumping an updated firmware from your sysMMC
89
-
90
-
::: warning
47
+
If you keep your emuMMC offline, you have 3 options:
91
48
92
-
**Before starting; do you have an eMMC NAND backup?**
49
+
1. You can dump the currently installed firmware version from your sysMMC
50
+
1. You can dump the firmware from another Switch you own
51
+
1. You can use a gamecard to update your firmware (keep in mind that no gamecard contains the latest available firmware version at the time of writing)
93
52
94
-
Please do not start this guide without performing an eMMC RAW GPP and eMMC BOOT0/BOOT1 NAND backup!
53
+
Only the first option is covered in the steps below.
95
54
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 following 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).
101
-
102
-
:::
55
+
### Updating emuMMC by dumping an updated firmware from your sysMMC
103
56
104
57
::: danger
105
58
106
59
**Downgrading**
107
60
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.
61
+
This guide is made for updating your emuMMC's firmware. It is **not** for downgrading. Downgrading at all, sysMMC or emuMMC, is not supported, not recommended and not worth it. Downgrading is also very dangerous and can lead to serious complications even when performed correctly.
109
62
110
63
:::
111
64
112
65
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
66
67
+
-**Note:**
68
+
If you have an unpatched Switch, have autoRCM enabled and you're updating your system while in stock firmware, **updating will disable autoRCM** and you will need to enter RCM manually to boot custom firmware again.
69
+
To prevent autoRCM from being disabled, boot CFW on sysMMC and update through settings from there, as booting without AutoRCM <ins>will burn any preserved e-fuses</ins>.
70
+
114
71
::::: tabs
115
72
116
73
:::: tab default Dumping your firmware via Goldleaf
117
74
118
75
#### What you need:
119
76
- The latest release of [Goldleaf](https://github.com/XorTroll/Goldleaf/releases) (`Goldleaf.nro`)
120
-
- The latest release of [Atmosphère](https://github.com/Atmosphere-NX/Atmosphere/releases) (`atmosphere-(version)-master-(version)+hbl-(version)+hbmenu-(version).zip`)
121
77
122
78
#### Preparing your microSD card
123
79
@@ -189,3 +145,97 @@ On Mariko ("V2") consoles, this method of dumping the sysMMC's firmware requires
189
145
1. Wait until Daybreak completes installing the dumped firmware.
190
146
1. Once it completes, it will ask if you want to reboot. Tap `Reboot`.
191
147
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.
148
+
-**Note:** If your system does *not* boot as expected after updating, please consult the [Common crashes after updating](#common-crashes-after-updating) section below.
149
+
150
+
## Common crashes after updating
151
+
152
+
After updating your firmware, you might run into crashes due to incompatible [sysmodules](/homebrew.html#terminologies). The following crashes are the most common ones, but is not an exhaustive list.
153
+
154
+
-**Note:** hekate and fusee are both bootloaders, these bootloaders have different ways of presenting error screens to the user. Errors displayed by hekate will typically be yellow and errors displayed by fusee will typically be white.</br>
155
+
- Below you will find the way it's presented depending on how you normally boot into CFW.
156
+
157
+
#### Custom theme crash
158
+
::: tip
159
+
160
+
161
+
162
+
:::
163
+
164
+
This crash typically happens due to the currently installed custom theme not being compatible with the HOME menu of your currently installed firmware version. In order to fix this crash, navigate to `sd:/atmosphere/contents` and delete the folder named `0100000000001000`. You may reinstall your custom theme afterwards using the `Installing a theme` section [here](/homebrew/nxtheme-installer.html#installing-a-theme).
165
+
166
+
#### MissionControl crash
167
+
168
+
::: tip
169
+
#### hekate crash screen:
170
+
171
+
#### fusee crash screen:
172
+
173
+
174
+
:::
175
+
176
+
This happens due to your current version of [MissionControl](../homebrew/mission-control) not being compatible with your currently installed Atmosphère version. If there is a newer version of MissionControl available for your currently installed Atmosphère version, you should update to that newer version if you wish to keep using MissionControl. If not, you can fix this crash by navigating to `sd:/atmosphere/contents` and deleting the folder named `010000000000bd00`, which will uninstall MissionControl.
177
+
178
+
#### ldn_mitm crash
179
+
180
+
::: tip
181
+
#### hekate crash screen:
182
+
183
+
#### fusee crash screen:
184
+
185
+
186
+
:::
187
+
188
+
This happens due to your current version of [ldn_mitm](../homebrew/ldn_mitm) not being compatible with your currently installed Atmosphère version. If there is a newer version of ldn_mitm available for your currently installed Atmosphère version, you should update to that newer version if you wish to keep using ldn_mitm. If not, you can fix this crash by navigating to `sd:/atmosphere/contents` and deleting the folder named `4200000000000010`, which will uninstall ldn_mitm.
189
+
190
+
### Fully yellow/blue screen on boot
191
+
192
+
This usually happens due to mismatched Atmosphère files being installed (for example, due to an incomplete Atmosphère update). Even if you're sure you've updated Atmosphère, re-update to the latest available version.
193
+
194
+
### 'Unknown pkg1 version. HOS version not supported!'
195
+
196
+
If there is a line of white text saying `Found pkg1 ('XXXXXXXXXXXXXX').`, X being any number, this is most likely due to an incompatible version of hekate being installed. Even if you're sure you've updated hekate, re-update to the latest available version. The pkg1 ID is the ID of the installed firmware version, if the pkg1 field is empty or contains scrambled text, please ask for assistance in `#switch-assistance-1` or `#switch-assistance-2` in the [NH Discord server](https://discord.gg/C29hYvh).
197
+
198
+
### Gamecards don't work after updating my firmware
199
+
200
+
Please unfold the `Legacy information` section at the bottom of this page and see if that resolves your issues.
201
+
202
+
### Still running into issues?
203
+
204
+
If you still run into issues at this point, please ask for assistance in `#switch-assistance-1` or `#switch-assistance-2` in the [NH Discord server](https://discord.gg/C29hYvh)
205
+
206
+
:::: details Legacy information {closed}
207
+
208
+
::: warning
209
+
210
+
#### **Updating from below Atmosphère 1.0.0**
211
+
212
+
If you update from below Atmosphère 1.0.0, there are additional steps to follow. You will have to delete the `sept` folder from your microSD, delete `fusee-secondary.bin` from your `atmosphere` folder and update your hekate config file: <ahref="/files/emu/hekate_ipl.ini"download>hekate_ipl.ini</a> in the `bootloader` folder.
213
+
214
+
:::
215
+
216
+
#### **Gamecard reader firmware**
217
+
218
+
In addition, updating to or past some firmwares update the firmware of the gamecard reader of your Switch. Refer to the table below for information about which firmware updates updated the firmware of the gamecard reader.
219
+
220
+
| Updating from | Updating towards | Updates gamecard firmware |
| On or above 4.0.0, but below 9.0.0 | At least 4.0.1 but below 9.0.0 | No |
225
+
| On or above 4.0.0, but below 9.0.0 | 9.0.0 or above | Yes |
226
+
| On or above 9.0.0, but below 11.0.0 | At least 9.0.1 but below 11.0.0 | No |
227
+
| On or above 9.0.0, but below 11.0.0 | 11.0.0 or above | Yes |
228
+
| On or above 11.0.0 but below 12.0.0 | At least 11.0.1 but below 12.0.0 | No |
229
+
| On or above 11.0.0 but below 12.0.0 | 12.0.0 or above | Yes |
230
+
| On or above 12.0.0 but below 14.0.0 | At least 12.0.1 but below 13.2.1 | No |
231
+
| On or above 12.0.0 but below 14.0.0 | 14.0.0 or above | Yes |
232
+
| On or above 14.0.0 | Latest supported Atmosphère & hekate revision | No |
233
+
234
+
If at least one of the versions you are updating towards also updates the gamecard reader's firmware, you will not be able to downgrade below that version without making the gamecard reader unusable until you update.
235
+
236
+
Atmosphère and hekate come bundled with patches that automatically disable the gamecard reader if it is detected that the system has an older gamecard reader firmware that would be updated. If you boot into RCM on each boot (for example by using AutoRCM), this means that the gamecard slot will not be updated and you can downgrade below that version. If this happens, you will not be able to use the gamecard slot as long as you are on the newer firmware.
237
+
238
+
Otherwise, you can safely update your system firmware through the system settings.
0 commit comments