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.

Spoiler

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:

   [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

 

[Draxzelex]

Hi, I followed the tutorial to migrate from SX OS (emunand) to atmosphere (using SX core)
When I launch Atmosphere CFW thru Hekate I get a message "failed to to apply 'nosigchk'
I assume it is due to the fact that the patches "Hekate.zip" are missing as the download link seems to be dead.
Any idea where I could get the patches?
Thanks

https://gbatemp.net/threads/sigpatc...te-fss0-fusee-primary-fusee-secondary.571543/

 

[synce]

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]

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

 

[LordMarMer]

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]

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.

Spoiler

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:

   [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.

Spoiler

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:

   [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

Spoiler

"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

 

[Gamerxxx]

can android be installed on switch lite with chip?

 

[pcwizard7]

can android be installed on switch lite with chip?

no, Erista switches only

 

[wurstpistole]

Spoiler

"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]

Spoiler

"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]

Spoiler

"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.

 

[D4M28]

Does anyone have a guide to sxos to ams after learning some games don't work on old fw

 

[Draxzelex]

Does anyone have a guide to sxos to ams after learning some games don't work on old fw

The first post has a link to another guide.

 

[mspy]

I use to load XCI games without installing with SX OS, so they are kinda there but need to be mounted first in order to play. Some of these XCI games do have NSP updates or DLCs installed, so if I were to install the base XCI game while on Atmosphere (because Atmosphere does not support XCI loading) will I encounter any problems? Will the updates and DLC already installed with SX OS of the XCI games be good or do I need to completely uninstall/delete these games from the menu plus remove their updates and DLC first and install them again from scratch including the updates and DLC?

 

[icegold]

de nada

 

[sh2dc]

OK I read

https://rentry.org/mys8q


Now I understand it could be super easy



I was use "sx os emunand on file" with switch's SD card


Not hide - partition


So dual boot sx os and ams on same sd card basically cant be done


I won't create any hide - partition emunand or emummc



However

Because I want newest game running so i must use 13.0-13.2 firmware


So I need create another 32 GB ams 13.0-13.2 firmware Emummc( just like sx os emunand ) on another SD card right??



=========


https://rentry.org/mys8q



This guide work on file-based sx os emunand?


If it work

I can just copy my entire SD card emunand to a new SD card

Then I update this new sd card emunand to 13.2?!


This way I can keep one SD card with old sx os ( with all the save/ game / cheat )


Then Migrate sx os emunand 13.2 to ams emummc on new SD card?


I will get 13.2 running on ams

And all the game needs to be reinstall?!


All the save / cheat no longer can be use?!


Right?


==========


Hmm



Sorry for late reply


I must update sx os emunand firmware to 13.2 first


Before use this guide right?

https://rentry.org/mys8q





I use sx os emunand 10-11.0


So once I updated 13.2 firmware on SD card sx os will unable to boot


Then I put all the file from " https://rentry.org/mys8q " said to SD card


I get 13.2 running after use hekate migrate this emunand to emummc?


Right?



All the game/ save locate on old sx os cfw 10-11.0 etc will be gone once I use ams? Right?!