Question How can I have a working dual boot setup SX OS / Atmosphere with the SX Dongle?

Maybe Tx will add it as an update feature , to avoid buying other dongles .

 

I highly doubt it, knowing TX they will probably never allow it on their own dongle.

 

Maybe they will be fix something diffrent for the lunch of the mariko console , after all they keep saying that they are still working on that .
Here they are selling switch before the mariko realease to US $420 , does it look expensive this price ?

 

This is the method I have to use. I boot SX OS and then if I want Atmosphere I use the Payload Launcher to reboot to Atmosphere.

 

it seems to be the optimal solution instead of booting to hekate.

 

What type of microprocessor does sx dongle have?

I use a modchip based on atsamd21, attached is the uf2 file I flashed for using with Argon:

Here's the sd card files:
https://github.com/Guillem96/argon-nx/releases/download/0.3/sd-files.zip

When the chip boots, it goes to the argon menu and you can select what to boot, it's easy to add/remove payloads and no more chip flashing for different CFW.

Screenshot:


The attached uf2 should work on any samd21 based chip.

 

mariko has not been released yet, the patched switches are different.

We have no idea if mariko will actually be released, nintendo may have ordered a complete redesign when fusee gelee was released.

That disclosure may have cost us the ability to hack mariko.

 

I'm not sure if this will work, but you can try it out.

CTCaer made a Python script awhile ago that merges Hekate into the SX OS boot.dat to create a custom boot.dat that will launch Hekate instead of the SX OS bootloader.

https://gist.github.com/CTCaer/13c02c05daec9e674ba00ce5ac35f5be

How to use:
1. Place the script, the latest Hekate bin, and the latest SX OS boot.dat in the same folder.
2. Either edit the script to change the name of the Hekate bin to "hekate_ctcaer_4.9.1.bin", or just rename the Hekate bin to "hekate_ctcaer_3.2.bin".
3. Run the script. There should be no output and the old boot.dat will be overwritten with the custom one.
4. Replace the boot.dat on your SD card with the new one you just generated.
5. Boot Switch into RCM with the SX dongle inserted, and it should boot directly into Hekate. If you have your SD/configs configured correctly then you should be able to choose between booting SX OS or Atmosphere.

In theory it should work, but this script is 8 months old so the new Hekate and/or SX boot.dat may not be compatible with it anymore. I would test it out myself but I'm at work and my Switch is at home.

EDIT: Now that I think of it, this wouldn't work for what you're trying to achieve. I don't think the resulting boot.dat has any ability to launch SX OS through Hekate.

 

Yeah I realized that after I made the post. Imo your best option is just using the reboot to payload homebrew. That way when you're in SX OS you can choose to reboot to Hekate or fusee, and while in Atmosphere you can choose to reboot to the SX Gear payload.

 

If you hold Vol+ when inserting the SX dongle it will load the SX launcher and from there you can launch the Atmosphere payload.

 

After installing Kosmos and updating my emuFirmware to 7.0, I can no longer use SX OX dongle to boor CFW. I can get into SX OX menu but when I click boot CFW, the screen goes black. Do I have to update SX OS? I'm on 2.5.3 now.
thnx

UPDATE:
I downgraded down to 6.2 and old xci files are working now. Why odes going up to 7.0 mess those up?
Thnx

 

Noob here...
I was using SX OX pro dongle and had most games working. I updated to emuNand from 6.0.1 to 7.0 using Choudejour and I also installed Kosmos. I did the update to play new games. Now I can no longer play a bunch of XCi files and also can't boot in to CFW from SX OX menu. The Wonder boy nsp works but nothing else. I'd like to be able to use all the xci games with SX OX. It's a mess now... What should I do to fix this?
thnx