Misc Launch SXOS from Hekate?

[fatherjack]

I originally had an SX Core chip installed and used SXOS on my ipatched Erista switch.
Time moved on - Team SX didnt - and I have been using Atmosphere now for aaaaaaaaaaages.
currently have Stock FW 10.1.0 Hekate 6.3.1 and Atmosphere 1.9.3 with emunand FW 19.0.0

Can I / How would I - set up SXOS again as a launch option from Hekate payloads?

 

[FR0ZN]

The latest SX OS (version 3.1.0) only had support up to FW 11.0.0 - if you realy want to go that route, you will be locked out from playing games from the last 5 years (more or less).

In hekate you simply create a new entry in your .ini file and use the "payload=" configuration, to point to the SX OS binary.

 

[fatherjack]

Thanks FR0ZN - I’m aware of the limitations of this,do you know where I could find a suitable .bin for payloads folder?
only ooold files I could find on my PC where boot.dat and license.dat

 

[FR0ZN]

Did you try google?

 

[mikefor20]

I prefer a dual emunand setup for my sx\atmo machine. I made them both hidden partitions for stability. I was able to shrink the sxos emunand to 8GB to save space as this is enough for game updates and saves. I wrote a tutorial and it included the sxos files at one point... I am not sure if the links broke by now. You could check there for the files. Look up dual hidden emunands in the tutorials written by me

If i recall correctly, all you need is the BOOT. DAT and the LISCENSE file. Add an entry to the INI to point to the BOOT.DAT file....

 

[fatherjack]

thanks @mikefor20
I did google and found an SX_Launcher bin and I do have my existing boot.dat and license.dat files

However, my sd card already has a boot.dat present, which I understood was a modified boot.dat to let my SX core chip boot Hecate? and won’t sxos be looking for the right boot.dat at sd root?

Thanks for your help

 

[mikefor20]

thanks @mikefor20
I did google and found an SX_Launcher bin and I do have my existing boot.dat and license.dat files

However, my sd card already has a boot.dat present, which I understood was a modified boot.dat to let my SX core chip boot Hecate? and won’t sxos be looking for the right boot.dat at sd root?

Thanks for your help

Leave the boot.dat in your sd root alone. You can point hecate anywhere with the entry in the INI file. Point hecate to the sxos payload

Thh i don't have the chip. Try it out.

 

[ber71]

You hake to keep sysnand or emunand on fw11, but even so the sxos payload doesn't work when launched through recent hekate releases.
https://github.com/CTCaer/hekate/issues/861
Reverting to a very old version of hekate doesnt play well with atmosphere.
The only way to launch sxos actually is as the main payload.

 

[mikefor20]

You can use 2 emunands. This bypasses the limitations. One for atmosphere and one for sxos...

 

[fatherjack]

@ber71 - thanks for the info mate, looked deliberate by CTCaer
@mikefor20 - read your (very detailed) guide, I have never used hidden partition nands, I always wanted to see what was filling up my SD cards! given ber71 post above, looks like your way is the only option,
Thanks for your help guys.

 

[mikefor20]

Idk if it still works but you could try using Tesla. I was able to switch between SXOS and Atmo using Tesla.