Will SXOS boot to launcher menu on unsupported FW?

[joeh1974]

So, I've used a SXOS Pro dongle for a few years now, and have Atmosphere on the card as well as a selectable boot option from the SXOS boot menu. I'm looking to migrate to just Atmosphere on a separate SD Card, and ordered a RCM Loader. The RCM loader froze to a solid blue light upon first time trying to connect it to the PC. Tried using a push pin to reset it, but that didn't work, so I'm ordering a replacement.

In the meantime, I'm wondering if the SXOS dongle will still boot to the payload selection menu if the Switch is on a unsupported FW?

 

[fatherjack]

depends what you're trying to boot.
SXOS normal boot.dat will not work past firmware 11.0
I boot into Hekate to load atmosphere, but there is lots of information on these forums with links and a multitude of different setups available - read up and see what you fancy

 

[joeh1974]

Only trying to boot into the SXOS menu to launch Atmosphere, not boot into the SXOS FW. Basically use the SXOS dongle to boot into Atmosphere until the new RCM Loader comes in.

Basically it's set up: SXOS loader menu -> Hekate -> Atmosphere

 

[MasterJ360]

Only trying to boot into the SXOS menu to launch Atmosphere, not boot into the SXOS FW. Basically use the SXOS dongle to boot into Atmosphere until the new RCM Loader comes in.

Basically it's set up: SXOS loader menu -> Hekate -> Atmosphere

You don't need the sxos boot menu for that. Just setup atmosphere on the SD card and make sure you have the hekate payload.bin file on the root of the SD card. This will boot directly into Hekate using the sxos dongle then you can choose which nand to play on via atmosphere. Thats what I do with my atmosphere switch, so that dongle is extremely useful.

 

[joeh1974]

You don't need the sxos boot menu for that. Just setup atmosphere on the SD card and make sure you have the hekate payload.bin file on the root of the SD card. This will boot directly into Hekate using the sxos dongle then you can choose which nand to play on via atmosphere. Thats what I do with my atmosphere switch, so that dongle is extremely useful.

Awesome to hear, I'll give that a shot! I just use Atmosphere on Sysnand, so hopefully even easier. Thanks.

 

[binkinator]

Only trying to boot into the SXOS menu to launch Atmosphere, not boot into the SXOS FW. Basically use the SXOS dongle to boot into Atmosphere until the new RCM Loader comes in.

Basically it's set up: SXOS loader menu -> Hekate -> Atmosphere

You can do that OR set up hekate as a boot.dat itself (just rename your current boot.dat to boot.orig).

upload hekate.x.x.x.bin here: https://sx-boot-dat-creator.herokuapp.com/

 

[Donnie-Burger]

Only trying to boot into the SXOS menu to launch Atmosphere, not boot into the SXOS FW. Basically use the SXOS dongle to boot into Atmosphere until the new RCM Loader comes in.

Basically it's set up: SXOS loader menu -> Hekate -> Atmosphere

This works on all and is most up to date files for all:

Erista
Erista patched
Mariko
Mariko Lite
Aula Oled

 

[joeh1974]

Appreciate the help! I'll give the suggested options a try.

 

[joeh1974]

You don't need the sxos boot menu for that. Just setup atmosphere on the SD card and make sure you have the hekate payload.bin file on the root of the SD card. This will boot directly into Hekate using the sxos dongle then you can choose which nand to play on via atmosphere. Thats what I do with my atmosphere switch, so that dongle is extremely useful.

Trying this method just gives me a red "boot.dat?" screen. I guess it's still looking for the SXOS boot.dat file. Do I still need that on the root of the card?

 

[joeh1974]

You can do that OR set up hekate as a boot.dat itself (just rename your current boot.dat to boot.orig).

upload hekate.x.x.x.bin here: https://sx-boot-dat-creator.herokuapp.com/

I tried this method as well. Converted hekate_ctcaer_x.x.x.bin into a boot.dat, renamed the SXOS dat file to boot.orig, and unfortunately it just black screened.

 

[fatherjack]

If your struggling I uploaded my initial setup files here:
https://easyupload.io/cukzh8

Backup your files - particularly your license.dat then
unzip the rar onto your SD and see if it works - should boot into Hekate from which you can load atmospere.
I personally have setup emunand and auto boot (in Hekate)

 

[binkinator]

I tried this method as well. Converted hekate_ctcaer_x.x.x.bin into a boot.dat, renamed the SXOS dat file to boot.orig, and unfortunately it just black screened.

might want to try direct with fusee.bin

 

[CanIHazWarez]

If you want to boot straight into something besides the SX bootloader, you need to set it up like the SX Core. Search on the forum for instruction.

 

[joeh1974]

If your struggling I uploaded my initial setup files here:
https://easyupload.io/cukzh8

Backup your files - particularly your license.dat then
unzip the rar onto your SD and see if it works - should boot into Hekate from which you can load atmospere.
I personally have setup emunand and auto boot (in Hekate)

Thanks for providing. While I didn't copy your files directly over, a comparison showed that I was just missing the SXOS boot.dat file. Placing that on the root of my SD card allows me to boot into the SXOS menu, and choose the Hekate payload to launch for Atmosphere.

Here is the strange thing, when I choose to boot Atmosphere I receive the following error:

"A fatal error occurred when running fusee.
Failed to run tsec_keygen firmware!
Press POWER to reboot"

When I press the power button, it seems to load Atmosphere fine? The splash screen comes up and when I go into Album, the hbmenu is there. Is this running normally?

 

[joeh1974]

If you want to boot straight into something besides the SX bootloader, you need to set it up like the SX Core. Search on the forum for instruction.

Thanks. Ultimately I was trying to use a RCM loader, but the one I received yesterday didn't work and the new one is set to arrive on Friday. Was trying to use the SXOS dongle until then. My ultimate question is if I can continue to use the SX dongle to get to the menu and load Atmosphere if the Sysnand FW is higher than what SXOS supports?

 

[binkinator]

Thanks for providing. While I didn't copy your files directly over, a comparison showed that I was just missing the SXOS boot.dat file. Placing that on the root of my SD card allows me to boot into the SXOS menu, and choose the Hekate payload to launch for Atmosphere.

Here is the strange thing, when I choose to boot Atmosphere I receive the following error:

"A fatal error occurred when running fusee.
Failed to run tsec_keygen firmware!
Press POWER to reboot"

When I press the power button, it seems to load Atmosphere fine? The splash screen comes up and when I go into Album, the hbmenu is there. Is this running normally?

‘I’ve seen this before. One moment…let me find the link.

 

[binkinator]

‘I’ve seen this before. One moment…let me find the link.

See if what this clown did will help you:

https://gbatemp.net/threads/hack-sxos.582831/page-71#post-9651425

 

[joeh1974]

See if what this clown did will help you:

https://gbatemp.net/threads/hack-sxos.582831/page-71#post-9651425

Ha! Nice self-reference. I had actually found that thread on a search, but I think that I'm already pointing to package3? Here is a copy of my hekate_ipl config file...I used the rentry.org setup guide:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock sysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Any suggested changes?

 

[Krazyeye]

Ha! Nice self-reference. I had actually found that thread on a search, but I think that I'm already pointing to package3? Here is a copy of my hekate_ipl config file...I used the rentry.org setup guide:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock sysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Any suggested changes?

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
fss0=atmosphere/package3 <-------- (Add this line)
icon=bootloader/res/icon_payload.bmp

**someone can verify & confirm but it should work.

 

[binkinator]

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
fss0=atmosphere/package3 <-------- (Add this line)
icon=bootloader/res/icon_payload.bmp

**someone can verify & confirm but it should work.

@Krazyeye wins the points!

edit: you have package3 for the Sysnand entry but not the Emunand entry. I may or may not have removed the fusee.bin line…been drinking a lot since then.