How To Install Atmosphere Switch

Ultimate-Guide-to-Drift-SXOS-SX-Core-to-Temper

Latest support: Firmware 12.1.0

Drift from SXOS iii.0.5 (SX Core hardware modernistic) to Temper 0.nineteen.3

I had been away from SXOS scene for more than a year, and recently just got back to power on my Switch to play some of the contempo titles in 2022. I have prior feel in jailbreaking Nintendo 3DS, the new Nintendo 3DS, Sony Playstation PSP Slim, Sony Playstation Vita (phat), and Sony Playstation Vita (Slim). While the tools used differ for each panel, they practise share some similarities and I discover information technology easier to empathize and compare the procedure.

Having said that, I decided to wrote this as a log to my attempts, and something that I could read back in the future. I wrote down each rationale for the steps and then that you can improve understand the process yourself. You may follow information technology if yous accept the same setup as I did! I remember information technology is important to emphasize that is not a guide to compete with other awesome guides out there that covers all possible scenarios/panel variants do achieve the same migration outcome. Rather this is merely written from my perspective in my scene experience with other console/handhelds, and on my scenario.

Annotation: If you e'er decide to follow my steps, please advisedly read through all the steps, brand sure all the release links are available, and understand what y'all are doing. And I exercise non hold responsible if you bricked your Switch console, which is very unlikely though.

All the files I downloaded are the latest release that I could obtained as of May 29, 2022.

tldr: I successfully updated to Atmosphere from SXOS. Turned out that the error is not due to SXOS, but the XCI game file itself! Merely I'm glad I transitioned since SXOS is support is stagnant at firmware xi. And I might update my sysNAND to latest firmware in the futurity to support online play for the outset fourth dimension.

TODO:

This is merely the first draft that I wrote, so I might keep on revising it if there are demands.

[DONE] Put all the tools/payload into this repo so you could easily install and link with my steps. (if there is a request)
Include more than screenshot

Mutual Traits for the Exploits

For historical purposes only.

Regardless on which exploit on which handhelds, the exploit process or result do share some similarities, in which they would:

Replace/redirect the function of an official app to Homebrew Bill of fare launcher, where you will then launch homebrew
A title manager (package installer manager) to extract a game container into a destination (internal eMMC or external microSD menu)
The initial container format usually dominated or fabricated pop past the first company that release the exploit publicly. In 3DS, Gateway was the offset commercial company that did the exploit before a9lhax, and their Gateway cards back up game container in .3ds format. With that format, you tin just mountain it, then it would replace the official cartridge on the card. You don't have to extract and install those using title manager. Similarly, TeamXcecutioner with their SXOS lineup was the get-go commercial company that promote xci format with their SXOS, with mounting capabilities without having to excerpt/install.
The successor container (3ds: CIA / Switch: NSP) would require the use of a title director (3ds: BigBlueMenu BBB / Switch: Tinfoil, Goldleaf, Awoo) to excerpt and install those titles. No mounting pick is possible with this type of container. The pros is once installed, you can simply launch it directly from the home menu screen, without having to to to homebrew carte du jour, select a game, go back to habitation menu, and select the first icon/cartridge. This is suitable for titles that you intend to play for long, and not simply testing information technology.

Prelude on Why I update to Temper from SXOS

I get-go encountered the dreaded Error 2002-4153 in the first few seconds when launching recent titles like New Pokemon Snap, Monster Hunter Rising, and Super Mario + Bowser'due south Fury. Many had pointed this error to a possible corrupted microSD card, so I format the microSD into FAT32 since some users reported that NS have a funky exFAT driver that sometimes caused corruption issues. With FAT32 I had to split up my XCI into each files of 4GB using SAP tool. Even with it, I am still facing the aforementioned 20.xxx fault when launching those recent titles.

After updating to Atmosphere, the same trouble persist!

I and so suspect that it could be the Installer Managing director that I used to install the NSP, which is Awoo-Installer at start. So I tried Tinfoil. Over again the same error in the first few seconds on boot. To make sure my previous games that used to work in SXOS, I converted a couple of the XCI into NSP, and alas it works without freeze! So this could but means 1 thing...
Turned out that the error is caused past the XCI that I downloaded from HBG using TotalCommander (FileManager) via rclone mount. To be safe, it is better to utilise rclone copy ... instead of a mounted file manager. I am still puzzled every bit to why this happen, and I am sure my HDD did not powered off unexpectedly the last time. I ostend that information technology is indeed the files because the fault only occured on all the games I downloaded in the same day. Checking the checksums and I plant that they are Dissimilar! So my suspecious is correct!
P/Due south: I was about to update the firmware on the emuNAND using Daydream as the last resort, glad I didn't do that and is able to pinpoint the issue!

Terminology

Cadre Components

Hekete: The primary Bootloader that user (us) can admission to launch a payload (next booting point) upon Tegra SOC power upward. Information technology allows root access and permit you to choose which environment to kicking next, due east.g. stock OFW from your sysMMC, CFW Atmosphere on your sysMMC or CFW Atmosphere on your emuMMC. The boot entries are defined in hekate_ipl.ini file (run across the next 1). Without this, the stock bootloader volition always boot to SYSNAND (internal eMMC). IMO, calling information technology main might be debatable to some embedded systems engineer, in the sense that the truthful chief or first stage bootloader is always internal flake ROM bootloader of Tegra SOC.
hekate_ipl.ini: Contains the boot entry to boot into different environment from Hekate (after initial payload injection via RCM or SXOS SX Gear). Kicking entry are such as stock (OFW) on sysMMC (or sysNAND in 3DS scene), CFW (Atmosphere) on emuMMC (or emuNAND), CFW (Atmosphere) on sysMMC. As with all other .ini file, each kicking option is in the [choice] block, where you can define the boot flag, payload, icon for each booting option. All the possible settings tin can be institute at the Bootloader configuration section in https://github.com/CTCaer/hekate. In Linux world, if you lot have dual boot Linux and Windows, y'all volition know GRUB.
Payload: A binary file to boot next from the offset stage bootloader like Hekete. It could be another bootloader such as temper fusee primary, or program like Lockpick RCM to dump your Switch panel keys (full encryption/decryption).
RCM: Recovery style to inject payload
Chainload: Loading payload by booting into Hekete bootloader start, i.east. you select Payload from Hekete carte du jour option, instead of modifying the payload.bin file from your root microSD card.
fusee primary: Payload (bootloader) to boot into temper from injection (upon ability on in RCM or SXOS). You tin load this by modifying the SXOX boot.ini file. Make sure to apply the right sigpatches in club to exist able to install XCI file by bundle director without mistake.
fusee secondary: Payload (bootloader) to kicking into temper ONLY FROM Hekate AKA chainloading. You can Simply load this by modifying the Hekate bootloader entry file /bootloader/hekate_ipl.ini file, particularly the fss0 field. Make sure to use the different sigpatches made for Hekate+Atmosphere boot, and not using the i from Atmosphere. Without the right sigpatches, you lot will 100% encounter XCI installation fault when using package installer similar Awoo!
SX Gear: Bootloader from SXOS developer Team Xecutor allowing us to boot into RCM way directly to inject payload such equally Hekete without having to use TegraRCM (jig to boot into recovery fashion)
autoRCM: As well known as machine Recovery Way. This is a soft brick that always decadent both boot0 and boot1 partitions so that the Switch never boot into Stock bootloader, which instead booting into Hekate or Atmosphere via payload injection. This finer bypass fuse check, and forbid the fuse from beingness blown by stock booloader when it check its current fuse diddled against the expected fuse to exist blown for the booting firmware. This is important considering in the effect for total bombardment drainage of the unpatched Switch or corruption, the organization will boot into stock bootloader upon battery charging. For Mariko patched Switch user still, this method is not applicable equally Nintendo patched it, hence the patched switch. It is very likely that Mariko user would accept SXOS Cadre SX hardware modernistic, which always ensure that it never got the chance to kicking into stock bootlader, and it will always boot into the payload, thereby making this method unnecessary.

Homebrew App

Tinfoil, Goldleaf, Awoo: Package manager to install game containers (NSP, NSZ, XCI). It is comparable this to BigBlueMenu (BBB) in 3DS scene
Edizon, jksv, Checkpoint: Relieve Manager (for import/export/migration)

File extensions

NRO: Programs for Homebrew. These will appear on the Homebrew Menu without needing any further installation.
NSP: Container for games. Can hold the base, updates, and dlc. Information technology has to be extracted and installe by title managing director like Tinfoil. This is similar to the CIA format in 3DS, which you lot would then install using championship manager like BigBlueMenu (BBB)
NSZ: A compressed format for NSP. NSZ files are typically 400MB less than NSP. It require installation via Installation Package Manager such as Tinfoil, Goldbrew, or allos.
XCI: Container for games. May be distributed as trimmed XCI which strip off all the empty/unused blocks in the storage. For instance, for a wink cartridge with 32GB storage, if the game is only using 8GB, then the trimmed XCI volition remove the remaining unused 24GB, and the concluding file size would be 8GB. This container is least compatible and difficult to work with to inject any updates or dlc. Recommend to use NSP instead. XCI can simply exist mounted every bit-is in SXOS (not Atmosphere), without needing further installation from the Switch via Installer Manager.

Other

Horizon Bone: Official Nintendo stock bootloader. Booting via this bootloader Will always check for fuse count, and blow information technology to lucifer the installed firmware. This is why unpatched Switch user demand to make sure autoRCM is ON.
autoRCM:

Comparison with 3DS Scene

Credits to github/Electric1447 and u/deleted for the corrections.

Aspect	Switch	3DS
Game Cartridge Dump	.XCI/.XCZ (trimmed)	.3DS
eShop Dump	.NSP/.NSZ (trimmed)	.CIA
Homebrew Apps	.NRO/.NSP	.3DSX/CIA
Title Manager	FBI, BigBlueMenu (BBB), DevMenu	Tinfoil,Goldleaf,Awoo
First Commercial Company	TeamXcecutioner	Gateway

My setup

NS Switch Mariko (a codename for NS switch sold with Reddish packaging box, with the longer battery life released afterwards 2022), with soldered hardware mods SXOS Cadre fleck.
Both my sysNAND and emuNAND was on firmare 10.0.two
512GB microSD card
Fill-in sysNAND and emuNAND
Never connected online in both emuNAND and sysNAND
Only booted to sysNAND less than ten times to play my legit game. Once more I never online in sysNAND or update the stock firmware.

Annotation:

I don't have to forcefulness my NS Switch into recovery mode using TegraRCM nor connect whatever USB cable from my Switch to PC, I don't think Mariko (patched or v2) Switch support that anyways. This is only because I accept the SXOS Core hardware modernistic soldered. You might have to do it if yours are not, e.grand. you are using dongle from SXOS Pro or jig to boot into SXOS.

What You Will Accept At the End of This Guide

By the end of going through Section ane to 3 this you would have

An emuMMC (emuNAND) equally a FILE. Partitioning is another pick just I find it easy to backup a file that you tin list without using Partitioning tool or Linux dd command.
A choice to always boot into Hekate upon power on, then select the possible booting choice (OFW Stock on sysMMC or CFW Atmosphere on emuMMC), or always boot into Atmosphere CFW upon power on.
A full dump of the prod.keys and partialaes.keys that you can use to catechumen between different game container, or apply it in Yuzu Switch emulator!
A peace of mind that no sensitive information most your Switch will be sent to Nintendo Server should you ever connect to the Internet when in Temper CFW. It will block any Cyberspace connexion to any of Nintendo servers via exosphere.

!!! Before YOU Continue WITH MY STEPS, MAKE SURE TO CLONE MY Unabridged GITHUB REPO https://github.com/dsync89/Ultimate-Guide-to-Migrate-SXOS-SX-Core-to-Atmosphere, Then RUN THE CHECKSUM.SFV TO MAKE SURE ALL THE FILES ARE CORRECT AND NOT CORRUPTED !!!

Near My Package

All the binder proper noun are are linked to each of the department below, so ane-1 would means all the files yous need to copy to your microSD root when doing Step i.1 Come across Hekate, your friendly Bootloader so on

1. Setting Upward for Atmosphere

Watch the astonishing video by Sthetix on MIGRATING FROM THE SX OS TO ATMOSPHERE (https://www.sthetix.info/migrating-from-the-sx-os-to-atmosphere/) to become familiarize with the steps. Then follow my steps below starting from 1.ane!

My case is Instance#iv are for Patched Switch (Regular/Lite) with Emunand. Simply jump to time 12:42 in that video and follow them EXACTLY till the finish.

TODO: I might put a screenshots for the steps in the video for reference. But as of the date of the writing, all his tools and steps are valid.

All the following steps and softwares are packaged, CRC checked, and adjusted by me afterwards watching Sthetix videos, and various articles from r/SwitchPirates and GBAtemp.

1.ane Run across Hekate, your friendly Bootloader

Remove microSD card from Switch console and insert to USB microSD Card reader to your PC
Copy and supercede all files in 1-i See Hekate, your friendly Bootloader folder to the root of your microSD menu.
Reinsert microSD menu to your console
Boot it upwardly and you should come across Hekate boot screen.

1.2 Migrate your existing emuNAND (SXOS) to emuMMC (Optional)

Note: Only exercise this if y'all desire to deport your emuNAND in SXOS to Atmosphere, without starting from scratch and recreating one. Skip this if you desire to start fresh. I would like to resume mine so I continue.

Skip the date/fourth dimension if y'all want. It is only used to brandish the time in Nyx (the skin/theme you come across in Hekate). It will not change your Switch system fourth dimension.
Select emuMMC icon
Select Migrate emuMMC icon at the height correct.
Select emuNAND push
Select Keep button
Select OK button when information technology is done
Select Close button at the top right
Select Power Off button at the bottom right.

1.3 Install Atmosphere to your microSD

Insert microSD card to your PC.
Copy and supersede all files in 1-3 Install Atmosphere to your microSD folder to the root of your microSD card.
Cull either 2.1a or ii.1b in the side by side section depending on how you would like to boot into.

2. Launching into Temper

There are two means to boot into Atmosphere, and I chose the second i. Some claimed that booting via chainload (Hekate) is faster, and I verified it. From my experience, it have 30-60 seconds just to boot into Atmosphere earlier yous can see the Homescreen using Method 2.1a. It took less than 10 seconds using Method 2.1b.

Edit on May 31, 2022: I used to choose method 1, only the waiting fourth dimension is likewise long, and I desire the pick to boot into Stock OFW hands without having to press Volume - push button every time I want.

Regardless on which method you utilise, you volition know you are booting into Atmosphere CFW if you come across three logos in succession before seeing the homescreen.

Indigo groundwork with atmosphere logo
atmosphere triangle shaped logo
Official Nintendo Switch logo

2.1a Auto boot into Atmosphere, bypass Hekate

Booting Flow: SXOS payload injection -> fusee_primary.bin (payload.bin) -> turn a profit!

Note: This is the method used by Sthetix in his video on MIGRATING FROM THE SX OS TO ATMOSPHERE (https://www.sthetix.info/migrating-from-the-sx-os-to-temper/)

Choose this method if yous e'er wanted to kicking into Atmosphere upon power on. Yous can nevertheless boot into Hekate, only would need to hold the Book - button for iii seconds when ability the Switch on.

Re-create and replace all files in 2-1a Auto boot into Atmosphere, featherbed Hekate folder to the root of your microSD card.
Insert microSD card back to Switch and power it on.
Go to toilet and go a loving cup of coffee. Y'all deserve it! It will take at least thirty seconds to boot into the Nintendo domicile screen.

2.1b Kicking into Hekate get-go, so select boot mode AKA "Chain Load"

Booting Flow: SXOS bootloader -> hekete.bin (payload.bin) -> Your boot entry (mutual entries are OFW Stock sysMMC, CFW on sysMMC or CFW on emuMMC)

This is the well-nigh flexible method and you tin ever choose where to boot adjacent, well-nigh common options are

OFW Stock on sysMMC
CFW on sysMMC
CFW on emuNAND

I never intend to put CFW stuffs into my sysMMC since I would like to have a clean sysMMC to play my legit game online, with minimal chance for banning. And then I only created 2 entries in the bootloader options.

Copy and supersede all files in ii-1b Boot into Hekate first, and so select boot mode folder to the root of your microSD carte du jour.
Insert microSD carte du jour back to Switch and ability it on.
Select Launch icon at the superlative left, and choose either one to boot next, OFW (sysMMC) or CFW Atmosphere (emuMMC).

3. Post Install

Do the following to foreclose possible ban by connecting your Switch to the Net while in CFW. They will assist you to hibernate all your Switch info or cake Internet connectedness to any of Nintendo servers, if y'all always accidentally connect to the Internet while in CFW.

3.1 Blank prodinfo (prevent ban) using exosphere (if you use CFW on emuMMC)

3.2 Dumping prod.keys (Full Encryption/Decryption Keys on Your Switch)

Before you can start to convert between XCI<->NSP using SAK, y'all take to dump the Full set of keys prod.keys from your bodily Switch console, using Lockpick_RCM ONLY. Lockpick NRO can only dump total cardinal if you firmware is below seven.0.0, which is very unlikely, and mine is 10.0.2.

I was using the prod.keys dumped from Lockpick NRO, and converting in SAK always shown check your keys. There is a YouTube video that claimed that the solution to this is to uncheck the Read only attribute of the file, merely mine was already unchecked! So the culprit IS INDEED the invalid partial keys.

Note that Lockpick NRO (homebrew app) volition but dump a subset of the keys. I verified these after comparing the prod.keys from Lockpick_RCM and Lockpick NRO, and the keys from Lockpick_RCM has more keys, and most chiefly it has the masterkey_00 to masterkey_0a, and not just the derrived keys dumped by Lockpick NRO.

Encounter the following for comparison. The left pane is the prod.keys dumped from Lockpick NRO, the right pane is the prod.keys dumped from Lockpick_RCM. Notice how the right pane has more keys (highlighted in Crimson) that is missing from the left.

To beginning dumping the keys,

Copy and replace all files in iii-ii Dumping prod.keys (Full Encryption Decryption Keys on Your Switch) binder to the root of your microSD carte.
Insert microSD menu back to Switch and ability it on.
Select Payload icon from the center bill of fare, and cull Lockpick_RCM.
Hold your switch vertically. For navigation, apply book + or - to go upward and down, and Power button to enter.
Press Power push button to first dumping all keys from sysMMC
Power Switch off
Reinsert microSD menu to your PC
Copy and fill-in the full encryption/decryption keys establish in switch/partialaes.keys and switch/prod.keys.

NOTE: I would highly suggest you to backup these ii keys and put information technology to your sysNAND FULL BACKUP!

Steps

Copy and replace all files in 3-1 Blank prodinfo (prevent ban) using exosphere (if you lot use CFW on emuMMC) folder to the root of your microSD carte du jour.
Insert microSD card back to Switch and ability it on.
All the stuffs are done under the hood when you connect to the Internet on CFW.

Notation: I never connect my Switch to Internet in both sysMMC or emuMMC, so this is but for extra peace of mind. I did this subsequently reading a comment by u/igromanru on Reddit.

iii.3 Incognito Way

According to https://rentry.co/SettingUpIncognito this is not supported in "Mariko" switch, so I didn't do it.

4. Prepping Games

Since atmosphere cannot mount XCI straight like SXOS could, I had to catechumen the XCI from HBG (a paid membership admission store with all the dumped games). In HBG, you'll find that not all titles are available in NSP format. A game is usually in one of the container, rather than both. And then I have to catechumen all XCI into NSP.

Edit: Some Championship Installers similar awoo and Tinfoil tin can already extract and install XCI files, and so yous can use them instead of having to catechumen to NSP. I did this because I didn't know at first, but it is a good affair to learn.

iv.one Switch Ground forces Knife (SAK)

I used Switch Army Knife (SAK) (https://github.com/dezem/SAK) that has a very good GUI with all the function I need to catechumen between XCI to NSP or vice versa. It basically packet all the command line tools for different conversion into a program. Without this, I had to use script similar NSZ (https://github.com/nicoboss/nsz) to convert.

Earlier y'all tin start to catechumen from whatsoever of the container, y'all would need to put your Switch prod.keys to the bin folder. Refer to Section three.2 Dumping prod.keys (Full Encryption/Decryption Keys on Your Switch) to see how yous can dump the cardinal.

Note: Do Not Utilize any prod.keys you found circulating from the Net. There'south no hazard in that location (demand further confirmation) but why exercise that if you already hack your Switch and take full access?

Once yous put the prod.keys to bin folder, you can so click any of the x to y push

Note: Splitting NSP/XCI to FAT32 max file size limit (4GB) does not crave prod.keys.

five. Install Games

Recall that Atmosphere cannot mount the XCI and won't detect them from Homebrew carte, so you have to apply Installer to extract NSP to either your internal storage (Switch eMMC) or SD card. Always choose SD card for the destination since the internal storage is supposed to only store files for your cleaned sysNAND and leave no trace of CFW!

At that place are iii popular installer to choose from:

Tinfoil (https://tinfoil.io/Download)
Goldleaf (https://github.com/XorTroll/Goldleaf)
Awoo (https://github.com/Huntereb/Awoo-Installer)

Before installing your package manager, create a folder called [NSP] in your root microSD card where you will put all the NSP container games.

NOTE: You don't have to put all the NSP at the root microSD card unlike XCI mount in SXOS. Recall in SXOS y'all have to put all XCI games at the root microSD, otherwise the "Album" app would not notice the game. This is considering the Championship Installer volition extract the NSP contents (which could have base of operations, dlc, updates) into the emuMMC. So that should go along your root microSD card clean!

five.one Package Manager

5.1.1 Tinfoil

I used Tinfoil v12 NRO, not NSP!

Steps

Open up download.txt from v-1-1 Tinfoil Package Manager.
Paste the link to your browser and download it
Extract to your root microSD card. The switch folder should appear at the top most level.
Launch Tinfoil from atmosphere CFW. If this is the start time launching it, I suggest launching Homebrew menu by launching whatsoever title and so hold the R push, from in that location select Tinfoil. After that the Tinfoil icon should appear at your habitation menu. The next fourth dimension you can just click it to launch straight.
Get familiarize with Tinfoil carte UI, then select File Browser > sdcard > NSP to see your NSP games!

5.2 Transfer via PC (Optional)

five.2.1 TinNUT

Edit @ 2022-June-01: Since I chose to boot to Atmosphere via Hekate and NOT using fusee-primary every bit the payload, Tinfoil will only show blank screen when launching via Homebrew Menu (with or without Applet) are the same. Of course without Tinfoil TinNUT would not work. It seems like information technology will only launch if you boot using fusee-primary. So for now I volition choose Awoo and so transfer games to it via NS-USBloader v5.0 (see 5.2.2 for details).

To simplify the transfer and non having to have out the microSD card from my Switch, I downloaded Tin NUT v2.7 (https://github.com/blawar/nut), which is a server program that you run on your PC. Once it is running, you can then launch Tinfoil, and select File Browser -> usbfs: to see all the drives on your PC!

Copy all the files from 5-2-two TinNUT (Server for Transferring Games from PC to Switch) to Tinfoil to your PC
Run tinfoil_driver.exe to install a modified USB driver to communicate with Switch when you plug in USB3 cable.
Double click tinfoil.reg to extend the MTP transfer timeout. This will add together entry to your Windows registry, I've checked the content and information technology is harmless.
Run nut.exe, and so paste the path on the top left field that contains all your NSP files! This will open up a web server that you can access from Tinfoilon your switch.

Adjacent, on your Switch, v. Launch Tinfoil homebrew app. six. Select [File Browser], and then select usbfs:. You should see all your PC drives. seven. Select a folder containing all the games, then printing A to start transfer. The download progress bar will show on the summit correct.

On my PC, each transfer is averaging 30-40MBps fifty-fifty when I am connected to USB 3.1 and using USB3 cable. I was expecting 80MBps but at least it works!

5.ii.2 NS-USBloader v5.0

I also tried out NS-USBloader v5.0 (crave Java runtime) (https://github.com/developersu/ns-usbloader), and it works flawlessly!

You lot just accept to select USB when launching Awoo, then launch NS-USBloader! I chose Awoo because Tinfoil failed to launch since I boot to Atmosphere via Hekate chainload, and not using fusee-master.

half dozen. Post Install

6.1 Transfer saves in emuNAND into sysNAND for legit game

WIP Basically the gist is

Total backup sysMMC earlier connecting Online for the commencement fourth dimension
Launch OFW on sysMMC (no trace of CFW ever) and so connect to Net
Reboot and do another full fill-in of the sysMMC. This is because some boosted files will be written to sysMMC when you connect for the start tiem, maybe some files downloaded from Nintendo server. Y'all want to always restore from this full backup in the hereafter, non the first one, whenever you want to launch a clean OFW with your history of Internet Connection. If you restore from the full backup in step 1, there will be mismatch for the tape when Nintendo matches the data. No one knows how and what files Nintendo server is checking, since their implementation is close source.

6.ii Update sysNAND to latest firmware for online play

WIP

7. Problems

Blank screen when trying to wake up from idle screen (sleep mode). No longer happening.

microSD card corrupted Many had pointed the culprit to the exFAT file organisation on the microSD card. I one time forgot to ability the unit off and unplug the microSD card. When booting over again, my games get corrupted. And so I had to format to FAT32 and volition stick to information technology from now on and run across if the problem reoccur. Fortunately I don't have to recreate my emuNAND, instead I just have to reinstall those NSPs via Awoo + USB!

Lesson learnt: ALWAYS POWER YOUR SWITCH OFF BEFORE REMOVING THE MICROSD Card!

8. FAQ (Technical)

Q: What is Fuse and should I care? A fuse is a 1 time programmable (write) hardware registers. The i-fourth dimension only function is exactly the same as the fuse y'all will find in ALL power adapter, extension cord (power strip) or Power Supply Unit (PSU) on your PC. The lead inside the fuse will be shorted or suspension once in the event of very loftier surge of voltage/electric current flowing through. In other words, the fuse is the last line of defense that protect the surged volage to get through and damage any connected electronics.

The same logic applies hither. Think of it as a storage somewhere in the powerful Tegra X1 SOC in Switch that store either '0' or '1'. In one case that is written AKA blown/fused/burned, it will stay in that location permanently, hence the term former. However information technology can exist read as many times as possible. Information technology is very infeasible to modify the fused registers even for professional engineer.

Nintendo store a table somewhere in the firmware that contains the expected number of fuses to be burnt for each firmware version. The detail tin can be found here https://gist.github.com/jonluca/0d7ce7da7c84de5163be0b49b3e319cc. Though it is slightly outdated and just covers until firmware 10.x.

The fuse is only checked or burn by the stock Nintendo bootloader when you power on the console. Information technology will never exist burn one time bootloader booted into the OS, either OFW (Horizon OS) or CFW (Atmosphere).

Power on Assuming that y'all never hacked/mod your Switch and power it on, the stock (official Nintendo) bootloader will get-go read the number of fused burnt in the Tegra X1 SOC, then it will compare that number to the expected number of fuses to exist burnt for the firmware to be loaded. At that place are Iii possible cases for the matching results:

NOTE: Booting via payload injection such equally hekate or atmosphere fusee-primary volition ALWAYS DISABLE FUSE CHECK.

Instance 1: If the number of burnt fuses is LESS THAN the expected number of fuse for the booted firmware, it volition burn the remaining fuses until the total matches the expected number of fuses to exist burnt for that firmware version. For example, if yous are on Firmware 8.i.0, past default your unit of measurement would already have 10 fuses burnt (For retail unit). If you are previously updating the OFW firmware to 10.0.ii and this is the reboot, the organisation will automatically burnt all the remaining 3 fuses, and this brings the total of burnt fuses to 10+three = xiii.

!!! IMPORTANT Of import Of import!!! IF You lot DONT Desire TO E'er ACCEIDENTALLY BURNT THE FUSE, BE SURE TO INJECT PAYLOAD TO HEKATE OR ATMOSPHERE FUSEE-PRIMARY (AND ENABLE AUTORCM IF You lot ARE USING UNPATCHED V1 CONSOLE, TO PREVENT THE Arrangement TO E'er BOOT INTO STOCK BOOTLOADER)

Example 2: If the number of burnt fuses is EQUAL to the expected number of burnt fuses of the booting firmware, it will not burn any fuse and keep to boot. For example, if you are on firmware 10.0.ii and the number of burnt fuses is 13, information technology matches with the expected number for that firmware, i.due east. 13. So it volition not exercise anything.

Case 3. If the number of burnt fuses is GREATER to the expected number of burnt fuses of the firmware, it will decline to proceed. The only fashion to boot into the arrangement is using Hekate payload or Atmosphere fusee-primary payload that automatically bypass the fuse check. This case would simply happen if you lot are trying to DOWNGRADE the firmware by booting into sysMMC with CFW installed, since you accept to utilize Daybreak homebrew to downgrade and you would not be able to boot into OFW Horizon Os. For case, y'all are on firmware 10.0.2 (current burnt fuses number is 13), and are trying to downgrade to firmware 8.1.0 (expected burnt fuses number is 10).

Bootloader such every bit Hekate volition bypass the fuse check, which is why you could apply homebrew app like Daydream to downgrade/upgrade your firmware anytime y'all want.

There are only ii means that the fuse will exist burnt when you boot upwards your Switch.

Via the stock/unmodded (never hacked) Nintendo Switch
Via the 18-carat Kicking option in SXOS Core.

Now the aureate question, should you intendance about the burnt fuse? You don't actually, Just IF yous DO NOT have programme to DOWNGRADE your system firmware on sysMMC. Or for those OCD that wanted to keep their switch at their fresh retail state.

I'm yet waiting for description from veteran whether booting Stock OFW from Hekate with the following bootentry (on hekate_ipl.ini) will featherbed the fuse check when I boot into stock. So far I oasis't kick into stock using that entry since I update to Atmosphere.

              [OFW Stock (sysMMC)] emummc_force_disable=1 fss0=temper/fusee-secondary.bin icon=bootloader/res/icon_switch.bmp stock=1

Q. What is fusee-primary and fusee-secondary in temper? They are essentially payload that contains the bootloader code to boot into Atmosphere CFW.

Y'all use fusee-principal whenever you want to automatically kick into Atmosphere. If you are on SXOS like me, y'all would go SX Gear and put both boot.dat and kick.ini in the root microSD. Then modify boot.ini payload to fusee-primary.bin, or simply rename fusee-chief.bin to payload.bin.

You use fusee-secondary Only in the first stage bootloader such as Hekate to boot into Atmosphere CFW. For example, if yous are on SXOS similar me, you would get SX Gear and put both kick.dat and boot.ini in the root microSD. So modify boot.ini payload to hekate_ctcaer_x.x.x.bin, or simply rename hekate_ctcaer_x.ten.ten.bin to payload.bin. This will brand certain your Switch kick into Hekate bootloader upon power up. Y'all would then have boot entry or /bootloader/hekate_ipl.ini that have the fusee-secondary.bin as the fss0 path so that you could boot into Atmosphere from Hekate. For case:

              [config] autoboot=0 autoboot_list=0 bootwait=3 backlight=100 autohosoff=0 autonogc=1 updater2p=0 bootprotect=0  [CFW Temper (emuMMC)] emummcforce=one fss0=atmosphere/fusee-secondary.bin icon=bootloader/res/icon_payload.bmp  [OFW Stock (sysMMC)] emummc_force_disable=1 fss0=atmosphere/fusee-secondary.bin icon=bootloader/res/icon_switch.bmp stock=one

Q. Which package manager to use? Case 1: If yous are using Atmosphere CFW:

Tinfoil and Awoo are amid the about popular ones. Based on my experience, I was getting Corrupted information is plant when installing i container format over another.

Following are my findings when installing different containers to Awoo via NS-USBLoader. The container are converted/merged using SAK.

Package Installer	NSZ (Base of operations Game)	NSZ (Update/DLC ONLY)	NSP (Base Game)	NSP (Merged)	XCI (Base Game)	XCI (Merged)
Awoo	Corrupted	OK	OK	Corrupted	*E1	Corrupted
Tinfoil

Merged above means Base + Update and/or DLC
E1: Partially installed contents can be removed ... OpenFileSystemWithId:124: Failed to open up filesystem. Brand sure your signature patches are upwards to date and gear up properly. Error code: 0x00234c02

Of import: If you lot boot to atmosphere via Hekate (i.e. using fusee-secondary as the payload), make certain you use the sigpatches downloaded from here (https://gbatemp.cyberspace/threads/sigpatches-for-temper-hekate-fss0-fusee-primary-fusee-secondary.571543/). Otherwise error E1 WILL occur at the very early beginning when you attempt to install XCI game cartridge game dump via Awoo. The reason is it require different sigpatches (need description). It will install normally if you kicking into temper directly (i.e. using fusee-principal every bit the payload), since information technology has the right sigpatches that you lot previously installed.

NOTE: From my experience, the Best and SAFEST mode to install games via Awoo is to e'er install the base game NSP first. Then install the updates/dlc separately (information technology doesn't matter which container format, and I've tried NSZ directly and it works), instead of merging them into one container using SAK.

Case 2: If you are using SXOS CFW:

All XCI (base game only) and (base of operations game + updates + dlc) tin be mounted without problem on SXOS. Still, some game that have a higher System Firmware requirement than the organization electric current Firmware will prompt Checking if software can be played... and so asking to connect to the Cyberspace. This is because using packaging installer similar Tinfoil and Awoo will bypass the check. I never connected to the Internet so I am not sure whether connecting volition help. Installing via Tinfoil might piece of work likewise (not verified by me).