Anyway to have emunand be lower than sis?

[viper3344]

Hey all. Purchased an unpatched switch that was updated to FW13.

If I want to use SXOS, is there anyway to create an emunand with FW11 on it and run SXOS?

Thanks!

 

[sley]

Hey all. Purchased an unpatched switch that was updated to FW13.

If I want to use SXOS, is there anyway to create an emunand with FW11 on it and run SXOS?

Thanks!

Yes there is but I'm going to assume that this will be your first time messing with Switch CFW stuff.

SXOS is outdated and is more complicated in general when trying to use it with games that need a newer firmware.
Is there any reason why you don't want to use atmosphere instead?

 

[viper3344]

Yes there is but I'm going to assume that this will be your first time messing with Switch CFW stuff.

SXOS is outdated and is more complicated in general when trying to use it with games that need a newer firmware.
Is there any reason why you don't want to use atmosphere instead?

Nope! Been with the switch scene since the start! I have my main switch with FW11 which I use lots of XCIs with and an emunand with atmo at 3.2 for all the newer games nsps (easier with family to switch XCIs via usb than switching sd cards with a reboot)

Just wondering how I can do the REVERSE on my backup switch I just got. Is it possible to keep my sysnand at 3.2 and boot into a FW11 emunand sxos?

 

[kidkat210]

it is possible.
step 1) create emunand
while thats going download atmosphere (we only need this for daybreak.nro and downgrading firmware) it come bundled with atmosphere. its a safer version of choidujournx.
2)download 11.0 firmware.
3) boot atmosphere on emunand. "Update" firmware with daybreak to 11.0
4) Reboot and boot sx
5) profit
This is the overall steps needed to do it. i havent done it my self, so if you run into any issues i more than likely wont be able to help

 

[binkinator]

it is possible.
step 1) create emunand
while thats going download atmosphere (we only need this for daybreak.nro and downgrading firmware) it come bundled with atmosphere. its a safer version of choidujournx.
2)download 11.0 firmware.
3) boot atmosphere on emunand. "Update" firmware with daybreak to 11.0
4) Reboot and boot sx
5) profit
This is the overall steps needed to do it. i havent done it my self, so if you run into any issues i more than likely wont be able to help

Ive done it successfully to my V1 pretty much just like @kidkat210 laid out. Great high level overview to “update“ to 11.0.0.

good luck.

 

[MasterJ360]

Nope. The Switch is at Firmware 13 meaning Emunand would be the same FW
Creating Emunand is making a copy of the sysnand.
He can't downgrade b/c the fuse count is most likely burnt

 

[binkinator]

Nope. The Switch is at Firmware 13 meaning Emunand would be the same FW
Creating Emunand is making a copy of the sysnand.
He can't downgrade b/c the fuse count is most likely burnt

Respectfully disagree. I downgraded from 13 to 11 using Daybreak with no issues. I’m using SXOS on 11.0.0 as we speak (with Sysnand at 13.2.0). Fuse checks are bypassed by Hekate.

 

[kidkat210]

Nope. The Switch is at Firmware 13 meaning Emunand would be the same FW
Creating Emunand is making a copy of the sysnand.
He can't downgrade b/c the fuse count is most likely burnt

anytime you boot into cfw, you dont need to worry bout efuses. thats cause the payloads bypass the fuse check. and since this is bout booting emunand, your always gonna bypass the fuse check.
so efuses are irrelevant when booting cfw. now if you would try to downgrade on sysnand, any time you booted without booting into cfw, your switch would throw a panic.

 

[viper3344]

Hey all! So I think I follow but am stuck on one part

So I know how to create an emunand and I assume with daybreak I can just downgrade to 11 no prob but…

How do I then launch sxos on the emunand? That’s where I’m stuck. Any help there appreciated

 

[viper3344]

Hey all! So I think I follow but am stuck on one part

So I know how to create an emunand and I assume with daybreak I can just downgrade to 11 no prob but…

How do I then launch sxos on the emunand? That’s where I’m stuck. Any help there appreciated

Ok so I was able to create an emunand and downgrade it to FW11! But for the life of me I now have ZERO idea how to boot into the emunand using SXOS!
How do you now boot into SXOS with the emunand at FW11?

 

[fragged]

Ok so I was able to create an emunand and downgrade it to FW11! But for the life of me I now have ZERO idea how to boot into the emunand using SXOS!
How do you now boot into SXOS with the emunand at FW11?

You would need to have Hekate use the SX OS Payload.bin & have your license.dat file on the root of your emunand.
I would really recommend using Atmosphere for CFW though, SX OS will never be updated again. It's been completly unsupported for over a year now.

 

[binkinator]

Ok so I was able to create an emunand and downgrade it to FW11! But for the life of me I now have ZERO idea how to boot into the emunand using SXOS!
How do you now boot into SXOS with the emunand at FW11?

Here’s a tangential thread where I posted my configs:

https://gbatemp.net/threads/how-to-...e-same-sd-tutorial.601607/page-5#post-9704668

This will get you both atm and SXOS dual booting via Hekate and swapping between them via Tesla and fastCFWswitch. Everything boots into Hekate (even SXOS) and then Hekate launches the correct payload from there. Basically Hekate boots the SXOS payload which then boots boot.dat and references your license.dat…tadah!

I agree with @fragged that SXOS is a dead CFW but being able to boot 6 different operating modes is one of those things you do because you can, not because you should.

 

[Draxzelex]

Ok so I was able to create an emunand and downgrade it to FW11! But for the life of me I now have ZERO idea how to boot into the emunand using SXOS!
How do you now boot into SXOS with the emunand at FW11?

You use the SX OS payload.

 

[urherenow]

what did you use to create the emunand? Easiest way, you should have used SX payload to create it. THEN boot it with Atmosphere, and use daybreak to downgrade.

 

[viper3344]

You use the SX OS payload.

What I was actually missing was the fact that you have to edit the atmo .ini to boot into the sxos FW . All good now!