Have problem accessing sxos on switch

[AceLighting]

Hi I have two emunands on my switch one for sxos and one for atmosphere

Recently I had updated atmosphere and it's firmware (I used kefir package but I kept the sxos boot.dat etc...)
atmosphere works perfectly though with sxos it now produces an error code 2162-0002

This had always worked and I haven't done anything specific to sxos or its emunand so I assume it is something conflicting on the micro sd card which is causing this error.
I am not sure how to resolve this so any advice would be greatly appreciated.

Many thanks
Kind regards

 

[BigOnYa]

Is your EmuNand with SXOS on FW 11? I believe that was the last FW supported by SXOS.

 

[Hayato213]

Correct, you need firmware 11.0.0 to use SX OS 3.1.0

 

[AceLighting]

First of all thanks for your replies, much appreciated.

I hadn't done anything specifically to sxos emunand in a long while so it should be on that version or earlier.
With having updated atmosphere recently etc... can there be any file on the micro sd which would conflict with sxos causing that error?
Because it was working perfectly before I had applied changes to atmosphere etc..
Other than loading xci files I never do anything else with sxos, just find it a bit confusing.

 

[Hayato213]

First of all thanks for your replies, much appreciated.

I hadn't done anything specifically to sxos emunand in a long while so it should be on that version or earlier.
With having updated atmosphere recently etc... can there be any file on the micro sd which would conflict with sxos causing that error?
Because it was working perfectly before I had applied changes to atmosphere etc..
Other than loading xci files I never do anything else with sxos, just find it a bit confusing.

Do you know what firmware is the emunand on?

 

[AceLighting]

It should be on the last supported which was 11.0.0

I have 2 emunand one for sxos and one for atmosphere.

 

[Hayato213]

Do you have any theme by the way?

 

[ELY_M]

time to give up sxos

 

[AceLighting]

@Hayato213
I have sxos theme installed but i hadnt updated the specific firmware of that emunand so i dont think that would be the problem, is there a way to delete it manually just to check?

I feel that the problem is either with using kefir it might have either placed a file on the micro sd which sxos does not like or some configuration is active that is causing the error or causing it to try and load the wrong emunand.
Though wouldn't know where to start with that.

---

@ELY_M
The only reason why I still keep sxos was the xci files.

---

On a side note is it possible to update the payload on this ? Thanks

 

[Hayato213]

I have sxos theme installed but i hadnt updated the specific firmware of that emunand so i dont think that would be the problem, is there a way to delete it manually just to check?

I feel that the problem is either with using kefir it might have either placed a file on the micro sd which sxos does not like or some configuration is active that is causing the error or causing it to try and load the wrong emunand.
Though wouldn't know where to start with that.

You can check for folder name 01000000000001000 inside atmosphere/contents since you said you also have an atmosphere emunand.

 

[ELY_M]

I think you have to plug it in pc and see if you can access the disk on it.

 

[SonGoku78]

@AceLighting
I just updated AMS yesterday and have an sxos setup too.
Had the same problem that sxos was not loading, only difference was, that i didn´t get an error message like you.
My switch did hang/stop at the nintendo logo on sx os boot.
But what is same is that we both didn´t touch any files/folders/configs related to sxos.
I found a solution that worked for me today, maybe it will help you too:
When updating AMS you also update all hamebrew, sys-patch etc etc right ?
I had updated fastcfwswitch too for new AMS/switch firmware 21 obviously.
So i remembered to have fastcfwswitch work under sxos, you had to copy manually the files from nx-ovlloader to the folder "sxos\titles\".
As tesla was replaced with ultrahand and new nx-ovlloader files, i assumed these and the old fastcfwswitch files under the mentioned sxos folder will not work correctly together.
I just deleted the folder "sxos\titles\420000000007E51A\ " (only the folder in bold letters !) on the sd card and now i can boot into sx os again.
I just lost the possibility to fastcfwswitch from sx os into ams.
Which is not a big problem and just needs a reboot with hekate payload through rcm loader dongle, as i have autircm enabled.

As for the dongle update, on the rcm loader i only need to replace the bin file on it with the new hekate bin, just need to rename it accordingly on the correct rcm loader folder. It needs to be named payload.bin.
Connect you dongle to USB A on your pc and check if you can see the device in windows explorer. the you can just replace the file i think.

Hope it helps, cheers

Edit: If you have any other software that worked in both sx os and AMS like fastcfwswitch, i would advice to delete that stuff from the sx os folder too. Its probably just incompatibility with FW 21 of something in sx os.

 

[ricky8324]

@AceLighting
I just updated AMS yesterday and have an sxos setup too.
Had the same problem that sxos was not loading, only difference was, that i didn´t get an error message like you.
My switch did hang/stop at the nintendo logo on sx os boot.
But what is same is that we both didn´t touch any files/folders/configs related to sxos.
I found a solution that worked for me today, maybe it will help you too:
When updating AMS you also update all hamebrew, sys-patch etc etc right ?
I had updated fastcfwswitch too for new AMS/switch firmware 21 obviously.
So i remembered to have fastcfwswitch work under sxos, you had to copy manually the files from nx-ovlloader to the folder "sxos\titles\".
As tesla was replaced with ultrahand and new nx-ovlloader files, i assumed these and the old fastcfwswitch files under the mentioned sxos folder will not work correctly together.
I just deleted the folder "sxos\titles\420000000007E51A\ " (only the folder in bold letters !) on the sd card and now i can boot into sx os again.
I just lost the possibility to fastcfwswitch from sx os into ams.
Which is not a big problem and just needs a reboot with hekate payload through rcm loader dongle, as i have autircm enabled.

As for the dongle update, on the rcm loader i only need to replace the bin file on it with the new hekate bin, just need to rename it accordingly on the correct rcm loader folder. It needs to be named payload.bin.
Connect you dongle to USB A on your pc and check if you can see the device in windows explorer. the you can just replace the file i think.

Hope it helps, cheers

Edit: If you have any other software that worked in both sx os and AMS like fastcfwswitch, i would advice to delete that stuff from the sx os folder too. Its probably just incompatibility with FW 21 of something in sx os.

Hi @SonGoku78

Do you know how to switch between sxos and AMS?
Because the sxos couldn't be launched the ultrahand

 

[SonGoku78]

Hi @SonGoku78

Do you know how to switch between sxos and AMS?
Because the sxos couldn't be launched the ultrahand

I could only switch from ams to sx os with the method i wrote, for switching back, i neef to reboot to hekate and load ams cfw.
You need to delete that folder i mentioned.

 

[ricky8324]

I could only switch from ams to sx os with the method i wrote, for switching back, i neef to reboot to hekate and load ams cfw.
You need to delete that folder i mentioned.

Hi @SonGoku78:
but I used ultrahand in AMS, then used fastcfwswitch switch to sxos, it only go to hekate UI, not go to sxos,
because it triggered the sxos.bin from "path=/bootloader/payloads/sxos.bin", it shouldn't be worked
Do you have the SD card folder or files structure?

 

[SonGoku78]

Hi @SonGoku78:
but I used ultrahand in AMS, then used fastcfwswitch switch to sxos, it only go to hekate UI, not go to sxos,
because it triggered the sxos.bin from "path=/bootloader/payloads/sxos.bin", it shouldn't be worked
Do you have the SD card folder or files structure?

Did you update to new nx-ovloader files under ams ?
And did you delete sxos\titles\420000000007E51A\ " (only the 420000... folder) ?
And yes, the correct payload bin file has to be there how its configured in your ini file.
I dont remember though which ini file it was, guess from fastcfwswitch.

 

[josete2k]

Is SXOS compatible with oled?

I think that alula switch is newer than fw 11.0.1... Oled came with 13.0.0