Tutorial [Tutorial] From SX OS to Atmosphere

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
16,227
Trophies
1
Age
27
Location
New York City
XP
11,078
Country
United States

synce

だいこんちゃんのだいふぁん
Member
Joined
Nov 5, 2009
Messages
537
Trophies
0
XP
574
Country
Comoros
The OP update is confusing. Do I no longer need to do the additional steps if I'm using an SX dongle? I want to migrate from SXOS + dongle to only Atmosphere without emunand.
 

Nema

Member
Newcomer
Joined
Jan 31, 2016
Messages
23
Trophies
0
Age
30
XP
106
Country
United States
The OP update is confusing. Do I no longer need to do the additional steps if I'm using an SX dongle? I want to migrate from SXOS + dongle to only Atmosphere without emunand.
I'm testing around now I put hekate files into sd and atmosphere files into sd also
fusee-primary.bin into payload inside bootloader payload folder from hekate files then start sxos like normal and go options then start hekate_ctcaer.bin (hekate) then go payloads and run fusee-primary.bin
Also keep you sxos files and backup them since you will need them to use dongle
Also download sigpatch files and add to atmosphere folder they're to play backups
Sometimes atmosphere breaks on me
 
Last edited by Nema,

LordMarMer

Member
Newcomer
Joined
Aug 11, 2019
Messages
12
Trophies
0
Age
39
XP
45
Country
Belgium
I followed the guide on
https://rentry.org/mys8q

I have SX Pro with a dongle and I want to migrate to Atmosphere. I did everything till the last step but when I want to Migrate emuMMC it doesn't work. The option is greyed out and I can't select it??
 

HellaJvke

Well-Known Member
Member
Joined
Oct 25, 2016
Messages
152
Trophies
0
Location
In your mind
XP
873
Country
United States
This is outdated. It works in its basic ideas, but has no updated links whatsoever anywhere. Look - if you want to migrate from SX to Atmos and don't have Emunand, just grab Atmos files and sigpatches, and boot Atmos with fusee-primary using your favorite means of launching payloads. That's it.

If you're on SX emunand, have a look at this tutorial. That is what I used myself to migrate to Atmos and emummc, and it works just fine. Contains links to everything you need. It also covers the problem of having an SX dongle, but wanting to boot another CFW with it.


This tutorial does absolutely not cover anything Ipatched-unit, Mariko or SX Core/Lite Modchip related. Please don't ask any questions about that here. I can and will not help you with that.


How to migrate from SX OS to Atmosphere
This short guide will show the basic steps to move from SX OS to Atmosphere, or have them both next to each other. I won't boast it up with images or even videos, since it's mostly only dragging and dropping files around. It's very straightforward and should be done in maybe ten to fifteen minutes.
It is especially relevant to users who boot their console with the SX Pro Dongle, because with it come certain limitations and issues when trying to boot Atmosphere or even dual-boot. This guide also provides a solution for that.

Why would I want to switch to Atmosphere and what are the ups and downs?
Pros:
  • Most up-to-date CFW support for newer Firmwares
  • KIP Support (external modules, 'add-ons' if you want)
Cons:
  • No XCI Loading
  • No USB Loading
  • No installing games from USB media
To put it in other words: if you don't need or want
  • XCI Loading
  • USB HDD support,
then there are no sensible reasons to hold on to SX OS.

Regarding EmuNAND/EmuMMC
Given that I do not use EmuNAND/EmuMMC, I can neither tell you how to move that nor provide support for it. There is already a guide that covers this, so if you are looking to move your EmuNAND as well, take a look at this guide by thaikhoa.

Basic Atmosphere Setup for existing SX OS users
  • Get the latest Atmosphere files (zip and fusee-primary.bin), put the contents of the zip on the root of your MicroSD
  • Get Sigpatches if needed (to run unsigned code), put the contents of the zip on the root of your MicroSD
  • SX Installer does not work on Atmosphere, so get another title installer like Goldleaf, Tinfoil or Lithium and put it into your \Switch folder
  • Since 0.8.5, Atmosphere supports cheats as well and they are compatible with the format that SX uses. User KuranKu already described what you need to move to make it happen, so have a look at this guide if you need this
  • If you have any XCI files left, you will either have to install them with the latest versions of Tinfoil or Lithium or grab them again as NSPs from your most favourite source. Don't install them via the SX menu, they won't work on Atmosphere
  • If you don't have or use the SX dongle, just use whatever loader you were using before but instead of pushing the SX payload, push the Atmosphere fusee-primary.bin payload
That is basically it. Now when in Atmosphere, launching any app while holding R (standard config) will open the Homebrew menu and allow you to run Homebrew from there.

All of the below is not necessary if you use any other dongle or payload launcher besides the SX Dongles! If you have a different method of launching payloads, just push the payload of your choice to go into SX or Atmosphere!

Booting Atmosphere with the SX Pro or Gear Dongle
If you want to use your existing SX Dongle to boot Atmosphere or to have a choice between Atmosphere and SX OS, there are some additional steps needed. SX actively blocks loading fusee-primary.bin through their launcher (boot.dat) since SX OS 2.6, so you need to install a little workaround and that is Hekate. I will show you how to set this up properly for both options - either having the dongle boot Atmosphere automatically, or leaving you a choice between Atmosphere and SX OS.

Setting up HekateOptional: Autoboot into Atmosphere

  1. Setting up Hekate
    For both options, we need Hekate.
    You can optionally set Hekate up as the Payload that the Reboot to Payload Homebrew boots into. Now when you use this Homebrew or your console crashes, the console will boot into Hekate, allowing you to dump your NAND, choose between SX OS and Atmosphere (if wished) etc.
    • Get the latest Hekate files and put the contents of the zip on the root of your MicroSD
    • Rename hekate_ctcaer_*.bin on the root of your MicroSD to payload.bin
    • Optional (if you want to have your console reboot into Hekate): Make a copy of the hekate_ctcaer_*.bin Payload, rename it to reboot_payload.bin and put it into the \atmosphere folder, overwriting the existing one. If you use the Reboot to Payload Homebrew, it'll now go into Hekate
    • Optional (if you want to continue using SX): Get the SX OS Payload, put it into \bootloader\payloads
    • Put the Atmosphere Payload fusee-primary.bin into \bootloader\payloads
  2. Optional: Have Hekate autoboot into Atmosphere
    You can set up Hekate so that you do not have to navigate its menu, but boot into Atmosphere directly. To achieve this, do the following:
    • Boot up Hekate at least once, so that the file hekate_ipl.ini in the folder \bootloader is created
    • Open hekate_ipl.ini and append the following lines at the end:
    Code:
    [Atmosphere]
    payload=bootloader/payloads/fusee-primary.bin
    { }
    • Change the value autoboot=0 to autoboot=1
    • This will make Hekate show a splashscreen for some seconds, and then autoboot into Atmosphere. During the splash screen, you can press one of the volume buttons to override the autoboot process and get into Hekate's menu.
    • Optional (if you want a longer time to be able to override): Change the value bootwait=3 to another time (in seconds)
    • Save the file
    If you go into Hekate now, it will show a splashscreen for the time specified in bootwait and then boot Atmosphere.

With this done, there is now two ways to continue, depending on whether you want to move to Atmosphere completely without being able to boot SX OS anymore, or whether you want to dual-boot. Since the whole SX OS CFW is written into the boot.dat, and the SX Dongle does not allow anything but starting boot.dat, both options require slightly different setups.

Atmosphere onlyAtmosphere and SX OS

  1. Using the SX Pro or Gear Dongle to boot Atmosphere without the possibility to load SX OS
    Utilizing the SX Gear boot.dat (which is just a chainloader), you can force the dongle to boot Hekate directly. As with the SX OS boot.dat, it will not launch Atmosphere directly and just blackscreen if you try to, and you'll also have to use Hekate to achieve getting into Atmosphere.
    • Follow all the steps above to set up Hekate
    • Get the SX Gear boot.dat, put that on the root of your microSD, overwriting any existing boot.dat
    • If you use the dongle to boot your console now, it will bring you into Hekate, where you can navigate to Launch > Payloads and choose fusee-primary.bin to launch Atmosphere
  2. Using the SX Pro or Gear Dongle while being able to run both Atmosphere and SX OS
    You cannot just use another boot.dat if you want to be able to run both Atmosphere and SX OS, because the boot.dat contains the whole SX OS CFW. So in that case,
    • Follow all the steps above to set up Hekate
    • Start your SX OS as usual
    • For SX OS, just launch the CFW as usual
    • For Atmosphere, go to Options > Payloads and launch payload.bin (this will bring you into Hekate)
    • Navigate to Launch > Payloads and choose fusee-primary.bin to launch Atmosphere
[/spoile
This is outdated. It works in its basic ideas, but has no updated links whatsoever anywhere. Look - if you want to migrate from SX to Atmos and don't have Emunand, just grab Atmos files and sigpatches, and boot Atmos with fusee-primary using your favorite means of launching payloads. That's it.

If you're on SX emunand, have a look at this tutorial. That is what I used myself to migrate to Atmos and emummc, and it works just fine. Contains links to everything you need. It also covers the problem of having an SX dongle, but wanting to boot another CFW with it.


This tutorial does absolutely not cover anything Ipatched-unit, Mariko or SX Core/Lite Modchip related. Please don't ask any questions about that here. I can and will not help you with that.


How to migrate from SX OS to Atmosphere
This short guide will show the basic steps to move from SX OS to Atmosphere, or have them both next to each other. I won't boast it up with images or even videos, since it's mostly only dragging and dropping files around. It's very straightforward and should be done in maybe ten to fifteen minutes.
It is especially relevant to users who boot their console with the SX Pro Dongle, because with it come certain limitations and issues when trying to boot Atmosphere or even dual-boot. This guide also provides a solution for that.

Why would I want to switch to Atmosphere and what are the ups and downs?
Pros:
  • Most up-to-date CFW support for newer Firmwares
  • KIP Support (external modules, 'add-ons' if you want)
Cons:
  • No XCI Loading
  • No USB Loading
  • No installing games from USB media
To put it in other words: if you don't need or want
  • XCI Loading
  • USB HDD support,
then there are no sensible reasons to hold on to SX OS.

Regarding EmuNAND/EmuMMC
Given that I do not use EmuNAND/EmuMMC, I can neither tell you how to move that nor provide support for it. There is already a guide that covers this, so if you are looking to move your EmuNAND as well, take a look at this guide by thaikhoa.

Basic Atmosphere Setup for existing SX OS users
  • Get the latest Atmosphere files (zip and fusee-primary.bin), put the contents of the zip on the root of your MicroSD
  • Get Sigpatches if needed (to run unsigned code), put the contents of the zip on the root of your MicroSD
  • SX Installer does not work on Atmosphere, so get another title installer like Goldleaf, Tinfoil or Lithium and put it into your \Switch folder
  • Since 0.8.5, Atmosphere supports cheats as well and they are compatible with the format that SX uses. User KuranKu already described what you need to move to make it happen, so have a look at this guide if you need this
  • If you have any XCI files left, you will either have to install them with the latest versions of Tinfoil or Lithium or grab them again as NSPs from your most favourite source. Don't install them via the SX menu, they won't work on Atmosphere
  • If you don't have or use the SX dongle, just use whatever loader you were using before but instead of pushing the SX payload, push the Atmosphere fusee-primary.bin payload
That is basically it. Now when in Atmosphere, launching any app while holding R (standard config) will open the Homebrew menu and allow you to run Homebrew from there.

All of the below is not necessary if you use any other dongle or payload launcher besides the SX Dongles! If you have a different method of launching payloads, just push the payload of your choice to go into SX or Atmosphere!

Booting Atmosphere with the SX Pro or Gear Dongle
If you want to use your existing SX Dongle to boot Atmosphere or to have a choice between Atmosphere and SX OS, there are some additional steps needed. SX actively blocks loading fusee-primary.bin through their launcher (boot.dat) since SX OS 2.6, so you need to install a little workaround and that is Hekate. I will show you how to set this up properly for both options - either having the dongle boot Atmosphere automatically, or leaving you a choice between Atmosphere and SX OS.

Setting up HekateOptional: Autoboot into Atmosphere

  1. Setting up Hekate
    For both options, we need Hekate.
    You can optionally set Hekate up as the Payload that the Reboot to Payload Homebrew boots into. Now when you use this Homebrew or your console crashes, the console will boot into Hekate, allowing you to dump your NAND, choose between SX OS and Atmosphere (if wished) etc.
    • Get the latest Hekate files and put the contents of the zip on the root of your MicroSD
    • Rename hekate_ctcaer_*.bin on the root of your MicroSD to payload.bin
    • Optional (if you want to have your console reboot into Hekate): Make a copy of the hekate_ctcaer_*.bin Payload, rename it to reboot_payload.bin and put it into the \atmosphere folder, overwriting the existing one. If you use the Reboot to Payload Homebrew, it'll now go into Hekate
    • Optional (if you want to continue using SX): Get the SX OS Payload, put it into \bootloader\payloads
    • Put the Atmosphere Payload fusee-primary.bin into \bootloader\payloads
  2. Optional: Have Hekate autoboot into Atmosphere
    You can set up Hekate so that you do not have to navigate its menu, but boot into Atmosphere directly. To achieve this, do the following:
    • Boot up Hekate at least once, so that the file hekate_ipl.ini in the folder \bootloader is created
    • Open hekate_ipl.ini and append the following lines at the end:
    Code:
    [Atmosphere]
    payload=bootloader/payloads/fusee-primary.bin
    { }
    • Change the value autoboot=0 to autoboot=1
    • This will make Hekate show a splashscreen for some seconds, and then autoboot into Atmosphere. During the splash screen, you can press one of the volume buttons to override the autoboot process and get into Hekate's menu.
    • Optional (if you want a longer time to be able to override): Change the value bootwait=3 to another time (in seconds)
    • Save the file
    If you go into Hekate now, it will show a splashscreen for the time specified in bootwait and then boot Atmosphere.

With this done, there is now two ways to continue, depending on whether you want to move to Atmosphere completely without being able to boot SX OS anymore, or whether you want to dual-boot. Since the whole SX OS CFW is written into the boot.dat, and the SX Dongle does not allow anything but starting boot.dat, both options require slightly different setups.

Atmosphere onlyAtmosphere and SX OS

  1. Using the SX Pro or Gear Dongle to boot Atmosphere without the possibility to load SX OS
    Utilizing the SX Gear boot.dat (which is just a chainloader), you can force the dongle to boot Hekate directly. As with the SX OS boot.dat, it will not launch Atmosphere directly and just blackscreen if you try to, and you'll also have to use Hekate to achieve getting into Atmosphere.
    • Follow all the steps above to set up Hekate
    • Get the SX Gear boot.dat, put that on the root of your microSD, overwriting any existing boot.dat
    • If you use the dongle to boot your console now, it will bring you into Hekate, where you can navigate to Launch > Payloads and choose fusee-primary.bin to launch Atmosphere
  2. Using the SX Pro or Gear Dongle while being able to run both Atmosphere and SX OS
    You cannot just use another boot.dat if you want to be able to run both Atmosphere and SX OS, because the boot.dat contains the whole SX OS CFW. So in that case,
    • Follow all the steps above to set up Hekate
    • Start your SX OS as usual
    • For SX OS, just launch the CFW as usual
    • For Atmosphere, go to Options > Payloads and launch payload.bin (this will bring you into Hekate)
    • Navigate to Launch > Payloads and choose fusee-primary.bin to launch Atmosphere

"fatal error occurred when running fusee failed to run tsec_keygen firmware!"

i am migrating from sxos and keep getting the error : fatal error occurred when running fusee failed to run tsec_keygen firmware!
i downloaded the needed files
im on fw 13 using my sx os dongle -> hekate then -> fusee.bin through the payload selector of hekate
 

wurstpistole

GBAtemp MVP
OP
Member
Joined
Nov 19, 2015
Messages
4,526
Trophies
1
XP
4,522
Country
United Kingdom
"fatal error occurred when running fusee failed to run tsec_keygen firmware!"

i am migrating from sxos and keep getting the error : fatal error occurred when running fusee failed to run tsec_keygen firmware!
i downloaded the needed files
im on fw 13 using my sx os dongle -> hekate then -> fusee.bin through the payload selector of hekate
no support here anymore
 

pcwizard7

Well-Known Member
Member
Joined
Aug 2, 2013
Messages
1,389
Trophies
0
XP
1,526
Country
Australia
"fatal error occurred when running fusee failed to run tsec_keygen firmware!"

i am migrating from sxos and keep getting the error : fatal error occurred when running fusee failed to run tsec_keygen firmware!
i downloaded the needed files
im on fw 13 using my sx os dongle -> hekate then -> fusee.bin through the payload selector of hekate

You running atmos 1.1.1 for fw 13.0?
https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.1.1
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
16,227
Trophies
1
Age
27
Location
New York City
XP
11,078
Country
United States
"fatal error occurred when running fusee failed to run tsec_keygen firmware!"

i am migrating from sxos and keep getting the error : fatal error occurred when running fusee failed to run tsec_keygen firmware!
i downloaded the needed files
im on fw 13 using my sx os dongle -> hekate then -> fusee.bin through the payload selector of hekate
Don't chainload.
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • Julie_Pilgrim @ Julie_Pilgrim:
    do you look under the buttons of your mouse
    Gift
  • El_Doot @ El_Doot:
    why do your friends look under the buttons of your mouse
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    they dont it's just that they saw the outside of my mouse and said it was disgusting
    Gift
  • El_Doot @ El_Doot:
    oh wait I understand my braincells have increased
    Gift
  • El_Doot @ El_Doot:
    by 1
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    funnily enough when i was telling my openly femboy furry bf and my friend(we talk about femboys sometimes) they said "nope we don't wanna hear that that's disgusting"
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    why is cheeto dust of all things
    the subject that crosses the line
    Gift
  • RichardTheKing @ RichardTheKing:
    Wait, Switch Online now has Super Mario 64, right?
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    i really hate to say this but
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    i dont think it does
    Gift
  • RichardTheKing @ RichardTheKing:
    Huh, makes sense; they did sell that through the 3D All-Stars collection.
    Gift
  • RichardTheKing @ RichardTheKing:
    Which, last I heard was removed from the eShop...so they might as well offer it again, I guess...
    Gift
  • RichardTheKing @ RichardTheKing:
    Will they use the same Shindou-translated ROM, or the original English ROM?
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    googling it, it seems that mario 64 is on the service
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    in japan they use the shindou version apparently but in the states and elsewhere they use the original rom
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    oh boy oh boy oh boy i sure do love living in japan and being a mario fan, i just got the new expansion pack, i cant wait to do some bljs!
    +1
    Gift
  • RichardTheKing @ RichardTheKing:
    From what I've heard about the Expansion Pack, the emulator used has some noticeable input delay and/or lag...would BLJs even be possible?
    Gift
  • RichardTheKing @ RichardTheKing:
    Apparently Nintendo adapted the 3D All-Stars emulator, instead of their old Virtual Console emulator - or, if nothing else, copying what fans have done.
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    from what i can seem to gather there's some issues but nothing dramatic enough to severely impact what you're playing
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    honestly the whole expansion pack confuses me since i thought the nes/snes games were just a neat little bonus
    Gift
  • El_Doot @ El_Doot:
    wait julie your bf is a femboy holy shit im jealous
    +1
    Gift
  • AkiraKurusu @ AkiraKurusu:
    So many planes flying overhead, and they sound close...
    Gift
  • DJPlace @ DJPlace:
    do you need friends to play the games online for the switch exapsion pack i know snes and nes do.
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    @El_Doot well hey hot people do get more benefits in life
    Gift
  • J @ Jephter:
    Please I need help with this. I just homebrew my old 3ds console and downloaded a CIA file, but after surfing through for only 10 sec or less this appears. please can someone help me? Thank you in advance.
    Gift
    J @ Jephter: Please I need help with this. I just homebrew my old 3ds console and downloaded a CIA file, but...