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

 

[wurstpistole]

You'd better be off searching support for that in the Atmosphere thread, since it's 99.9% not caused by using my tutorial

 

[wurstpistole]

Reformatted (with tabs), done for now. Let's wait until any FW or SX OS update fucks anything up again.

 

[The Real Jdbye]

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.

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 Emunand
• No USB Loading
• No installing games from USB media

To put it in other words: if you don't need or want

• Emunand
• XCI Loading
• USB HDD support,

then there are no sensible reasons to hold on to SX OS.

General Warning for SX OS users!
This guide will not cover anything Emunand-related nor provide support for something SX OS-specific that you did set up on SX and now won't work anymore on Atmosphere. Assuming you have an Emunand running, you have to get rid of that before migrating to Atmosphere for the obvious reason that Atmosphere does not run Emunand (yet). You'll have to figure that out yourself though.

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

General Warning for SX OS users!
This guide will not cover anything Emunand-related nor provide support for something SX OS-specific that you did set up on SX and now won't work anymore on Atmosphere.

Thanks for this completely useless guide that's clogging up my google searches and preventing actually relevant results from showing up first. No really, thank you.

 

[wurstpistole]

Thanks for this completely useless guide that's clogging up my google searches and preventing actually relevant results from showing up first. No really, thank you.

What in the eff is wrong with you? This guide is both up to date and working as of now. No idea what you're on about.

(edit) seeing that you quoted the warning you probably misread that as "this guide is not working anymore". What I meant is that users shouldn't come to me if they set up emu on SX, now use atmosphere and something isn't working anymore. I dont use emunand myself, that's why I can't support it. I don't see why it wouldn't work with this guide though. If you use partition based emunand, you have to obviously do the steps on the emunand partition (is it too much to assume that this would be common sense if you made it that far and successfully set up emunand) and if you use file based emunand, there shouldn't be any difference except that you boot emunand instead of sysnand.

 

[The Real Jdbye]

What in the eff is wrong with you? This guide is both up to date and working as of now. No idea what you're on about.

(edit) seeing that you quoted the warning you probably misread that as "this guide is not working anymore". What I meant is that users shouldn't come to me if they set up emu on SX, now use atmosphere and something isn't working anymore. I dont use emunand myself, that's why I can't support it. I don't see why it wouldn't work with this guide though. If you use partition based emunand, you have to obviously do the steps on the emunand partition (is it too much to assume that this would be common sense if you made it that far and successfully set up emunand) and if you use file based emunand, there shouldn't be any difference except that you boot emunand instead of sysnand.

No. What I meant is it doesn't explain how to move your emuNAND, which is what everyone coming from SX OS wants to know. You telling people you're not gonna help with that doesn't change that fact.
https://gbatemp.net/threads/tutorial-from-sx-os-to-atmosphere.533337/
This guide actually explains that, and it works.

 

[wurstpistole]

No. What I meant is it doesn't explain how to move your emuNAND, which is what everyone coming from SX OS wants to know. You telling people you're not gonna help with that doesn't change that fact.
https://gbatemp.net/threads/tutorial-from-sx-os-to-atmosphere.533337/
This guide actually explains that, and it works.

Please try to be situationally aware. This tutorial was written in March, when Atmosphere Emummc was still more than three months away. I am in no way obliged to cover that topic and owe you nothing. If you are dissatisfied with my tutorial, feel free to write up your own, but don't be coming into my thread bashing me because it doesn't include what you assume everyone wants.
Also, you linked my tutorial. I assume you meant this one, which I will just link in my OP for anyone who needs that step.

 

[The Real Jdbye]

Please try to be situationally aware. This tutorial was written in March, when Atmosphere Emummc was still more than three months away. I am in no way obliged to cover that topic and owe you nothing. If you are dissatisfied with my tutorial, feel free to write up your own, but don't be coming into my thread bashing me because it doesn't include what you assume everyone wants.
Also, you linked my tutorial. I assume you meant this one, which I will just link in my OP for anyone who needs that step.

That's fine, but you should make that clear in the OP. Don't just make excuses.
Sorry if I'm taking my anger out on you right now, I'm mad that my shit isn't working and the Nintendo Homebrew discord were being dicks about it. It's not your fault. It just feels like the entire Internet is useless when it comes to this, and that guide is the only thing that works, and them getting pissed as soon as I mentioned Tinfoil and banning me does not help things.

I did mean that one, yeah. Your guide was the first thing that showed up on Google, and actually finding the other one was not easy, so it would be a huge help if you linked it in the OP, thanks.

 

[wurstpistole]

I did mean that one, yeah. Your guide was the first thing that showed up on Google, and actually finding the other one was not easy, so it would be a huge help if you linked it in the OP, thanks.

I did that now and clarified that part up. So the above average user (which tbh anyone should be who messes with that emunand merging, doesn't look like a point and click solution) should probably be able to get what they need or want from either one of those. I'm banned anyway, don't care about Emunand, that's why I won't do an all in one solution. I could of course, but that would mean getting into the topic of Emunand myself without having any advantage from it. I just wrote this guide here because I set up a dual boot solution myself at that time and ran into issues.

 

[Smoker1]

I am already on Atmosphere 0.9.2 . Thing is, not sure if I even have EmuNAND. I just run it with AutoRCM, and have the TegraRcmGUI set to Auto. How do I go about getting SX OS added?

8.0.1 (AMS 0.9.2)

 

[wurstpistole]

I am already on Atmosphere 0.9.2 . Thing is, not sure if I even have EmuNAND. I just run it with AutoRCM, and have the TegraRcmGUI set to Auto. How do I go about getting SX OS added?

8.0.1 (AMS 0.9.2)

If you're not sure whether you have Emunand, you probably don't have it. If you push your payload with Tegra, just copy the SX files to your SD and start their payload, done. To set it up that you can switch between the cfws, follow the guide on setting hekate up

 

[The Real Jdbye]

I did that now and clarified that part up. So the above average user (which tbh anyone should be who messes with that emunand merging, doesn't look like a point and click solution) should probably be able to get what they need or want from either one of those. I'm banned anyway, don't care about Emunand, that's why I won't do an all in one solution. I could of course, but that would mean getting into the topic of Emunand myself without having any advantage from it. I just wrote this guide here because I set up a dual boot solution myself at that time and ran into issues.

It would have been a point and click solution, if Atmo hadn't changed the format of the emummc.ini file. I knew exactly what to put there to make my emuNAND work, but it just ignored it because the format changed.
Since it ignored my config and booted sysNAND anyway, I might end up banned. I did make an eMMC SYS backup beforehand just in case, so hoping there's nothing in the USER partition that could get me banned, but if I get banned I'll just buy another Switch, fuck it.
I understand why it's not a priority for you though.

 

[wurstpistole]

It would have been a point and click solution, if Atmo hadn't changed the format of the emummc.ini file. I knew exactly what to put there to make my emuNAND work, but it just ignored it because the format changed.
Since it ignored my config and booted sysNAND anyway, I might end up banned. I did make an eMMC SYS backup beforehand just in case, so hoping there's nothing in the USER partition that could get me banned, but if I get banned I'll just buy another Switch, fuck it.
I understand why it's not a priority for you though.

Second post there looks complicated, but I guess that's not necessary if you just move the emunand.

 

[The Real Jdbye]

Second post there looks complicated, but I guess that's not necessary if you just move the emunand.

I still want to be able to use SX OS though.
I'm just gonna go back to SX OS for now, because Atmosphere will happily boot my sysNAND and has done so about 20 times tonight. That's not an option. My sysNAND stays clean.

 

[wurstpistole]

I still want to be able to use SX OS though.
I'm just gonna go back to SX OS for now, because Atmosphere will happily boot my sysNAND and has done so about 20 times tonight. That's not an option. My sysNAND stays clean.

And now you see another reason why it would be quite complicated to satisfy all needs in one tutorial. Those who want to switch from SX to Atmos completely, then those who want to be able to dual boot, then those who have the SX Pro Dongle which makes things a tad more complicated and then those who use EmuNAND and may want to switch from SX to Atmos and continue using said EmuNAND and then people (like you) who want to be able to dual boot both SX and Atmos with both being able to boot the EmuNAND. That's a lot of different needs in there and would make a hella hard to organize (and keep up to date) tutorial.

 

[The Real Jdbye]

And now you see another reason why it would be quite complicated to satisfy all needs in one tutorial. Those who want to switch from SX to Atmos completely, then those who want to be able to dual boot, then those who have the SX Pro Dongle which makes things a tad more complicated and then those who use EmuNAND and may want to switch from SX to Atmos and continue using said EmuNAND and then people (like you) who want to be able to dual boot both SX and Atmos with both being able to boot the EmuNAND. That's a lot of different needs in there and would make a hella hard to organize (and keep up to date) tutorial.

Indeed. Not that that helps. Seems like there isn't really a perfect solution yet, which I guess shouldn't be a surprise, what is surprising though is that SX OS seems to be superior.
SX Pro is useless for dual booting, more or less. Those users would be better off just buying a better dongle.
Honestly, so far Atmosphere seems like the most unstable piece of shit ever. I never had Tinfoil crash on me on SX OS. Maybe that's just Tinfoil being poorly coded and only tested on SX OS, but Goldleaf is even more crashy (and has always been) so that's not really an option either. Not really sure what to do at this point, but SX at least works so I'm gonna stick to that for now.
At least I did get Atmosphere working eventually, it's just not working as well as I'd like.
Again, sorry for taking my anger out on you.

 

[Dennieh]

and the Nintendo Homebrew discord were being dicks about it. It's not your fault. It just feels like the entire Internet is useless when it comes to this, and that guide is the only thing that works, and them getting pissed as soon as I mentioned Tinfoil and banning me does not help things.

Hi, I'm one of the people you call dick here. If you're already venting about Nintendo Homebrew it would be cool if you would atleast not lie about it.
You were never banned for mentioning Tinfoil, you weren't even banned at all (at the moment of writing this you're still in the server).

We removed your access to the assistance-channels because you were talking about a piracy tool (Tinfoil), then after you got made aware that we don't support that here
you continued talking about it, then a mod told you we, on the day of this writing, don't support NSP installation at all and that you should stop it right now.
Said mod even said another time that "it ends here", yet 2 minutes later you still brought up the topic again.

This was the reason you got takehelp-ed and it would have been an easy appeal, but then you choose to violate another 2 rules by DM-ing that mod over it and trying to bring up drama.
We have a Mod-Mail for this exact purpose and if you would give a damn about our rules or atleast even read them you would know that.

And just saying, from my perspective it really didn't help that you acted all entitled and played the "i'm popular on gbatemp"-card:

Sorry for bringing this into drama-zone again, and Chary/Swebow/whoever can feel free to delete it, It just annoyed me that it was a classic "i didn't do anything and they just snapped and banned me" again, again with no context whatsoever provided.

 

[The Real Jdbye]

Hi, I'm one of the people you call dick here. If you're already venting about Nintendo Homebrew it would be cool if you would atleast not lie about it.
You were never banned for mentioning Tinfoil, you weren't even banned at all (at the moment of writing this you're still in the server).

We removed your access to the assistance-channels because you were talking about a piracy tool (Tinfoil), then after you got made aware that we don't support that here
you continued talking about it, then a mod told you we, on the day of this writing, don't support NSP installation at all and that you should stop it right now.
Said mod even said another time that "it ends here", yet 2 minutes later you still brought up the topic again.

This was the reason you got takehelp-ed and it would have been an easy appeal, but then you choose to violate another 2 rules by DM-ing that mod over it and trying to bring up drama.
We have a Mod-Mail for this exact purpose and if you would give a damn about our rules or atleast even read them you would know that.

And just saying, from my perspective it really didn't help that you acted all entitled and played the "i'm popular on gbatemp"-card:

Sorry for bringing this into drama-zone again, and Chary/Swebow/whoever can feel free to delete it, It just annoyed me that it was a classic "i didn't do anything and they just snapped and banned me" again, again with no context whatsoever provided.

I didn't say anything after "this ends here", that was the last message in the channel when you muted me, as far as I can recall. Not that I have any way to check now.
Tinfoil works just fine. i solved my problem, no thanks to you. What you are doing is simply pushing your own Blawar-hating agenda, which really has no place on a help community, and using excuses to try to cover up that fact. The mere mention of Tinfoil, no mention of piracy or anything like it, is all it takes.
Guys, there are legitimate uses to nsps, and the sooner you realize that, the better. I legitimately own the game I was trying to install, and if it was a matter of that, I could have provided proof, but you never asked for such a thing.
Whether you banned me or just removed my access is semantics. Makes no difference. The point is that you removed my access for mentioning Tinfoil, it's that simple, no point in trying to cover it up with excuses.

It's got nothing to do with me being popular or not. But why should people bother to go there when you do shit like this? They probably aren't gonna get the help they need from you.
I spend every day helping people on the Switch and 3DS sections and I've never treated someone like this.

And just to clarify, I did not call you a dick. I said you were being dicks about it. Pretty significant difference.

 

[Dennieh]

I didn't say anything after "this ends here", that was the last message in the channel when you muted me

Lying is not the best idea when there are logs of everything

And regarding the NSP installation: I do very well see the non-piracy usecases of them, but i didn't make the rules and just like you I have to follow them.
Imagine how quickly we would be a piracy hub when we would help with installation of NSPs just because someone says "i own the game, trust me"

Anyway, my discord is Denn#4733 and i'm happy to discuss this in DMs (this time it's asked for) instead of this thread

 

[The Real Jdbye]

Lying is not the best idea when there are logs of everything

And regarding the NSP installation: I do very well see the non-piracy usecases of them, but i didn't make the rules and just like you I have to follow them.
Imagine how quickly we would be a piracy hub when we would help with installation of NSPs just because someone says "i own the game, trust me"

Anyway, my discord is Denn#4733 and i'm happy to discuss this in DMs (this time it's asked for) instead of this thread

I'm not lying, I genuinely can't see the logs.

I didn't really see the point in appealing when it's clear you aren't gonna give me the help I need anyway. I was treated similarly when I asked for help with 3DS in the past.

And hence, that's why I offered to provide proof of ownership. You didn't seem to care about that though.

 

[Alchemy_Gaming]

SX actively blocks loading fusee-primary.bin through their launcher (boot.dat) since SX OS 2.6

Pretty sure Atmosphere blocks their own payload from being launched with the SX bootloader. Link?