Hacking Rumor SX OS is not over

[Hayato213]

Never heard of hekate or created an emunand before so this is all level 0 stuff to me. Ill do some research and see what I can dig up! But the goal is what? I have my switch powered off. I still assume I use my jig and injector, but switch between payloads for atmos VS sxos?

https://www.reddit.com/r/SwitchPirates/comments/e2twk7/sxos_emunand_alongside_hekate_emunand/

Here is some reference to set up dual emunand, hope it help

 

[godreborn]

I checked axiom verge 2 after I bought it. It is indeed sdk 12+, but it still uses key 0a. Does any game use the new 0b?

 

[viper3344]

I checked axiom verge 2 after I bought it. It is indeed sdk 12+, but it still uses key 0a. Does any game use the new 0b?

I can read the key with XCI explore, but it does indeed say SDK 12. There are other games like Spelunky 2 that use SDK 12 that SXOS refuses to boot. I think its not the key thats the issue, its the SDK actually using code that requires that SDK12 that

 

[godreborn]

hmm...I know nothing about switch exploits (haven't done them), but I have been downloading the games I own, so I do know about converting and compressing content.

 

[Hayato213]

I can read the key with XCI explore, but it does indeed say SDK 12. There are other games like Spelunky 2 that use SDK 12 that SXOS refuses to boot. I think its not the key thats the issue, its the SDK actually using code that requires that SDK12 that

yea you can't boot games that use masterkey 0b with SX OS.

 

[viper3344]

yea you can't boot games that use masterkey 0b with SX OS.

Axiom Verge 2 uses the earlier key (0a) but the SDK is built on 12. That's the issue as well.

 

[Hayato213]

Axiom Verge 2 uses the earlier key (0a) but the SDK is built on 12. That's the issue as well.

Base on info, it says require firmware is 12.0.2

 

[godreborn]

Base on info, it says require firmware is 12.0.2

Sdk is also 12+

--------------------- MERGED ---------------------------

I just pulled it up:

 

[BaamAlex]

Never heard of hekate

Hekate is a custom bootloader. It can boot a cfw and create an emuMMC for example. emuMMC is a copy of your internal storage stored on your sd card. Either as a file based emuMMC or in a hidden partition.

 

[Kallrkyle]

You would have to leave Sysnand at 11.0.0, have an emunand for SX OS, and have a second emunand for Atmosphere.

And why do you belive yoiu need to have sysnand on 11 for booting SXOS emunand 11 ?

One og my Switches is on sysnand 12.1 and still boot SXOS emunand 11

 

[Hayato213]

And why do you belive yoiu need to have sysnand on 11 for booting SXOS emunand 11 ?

One og my Switches is on sysnand 12.1 and still boot SXOS emunand 11

Not saying you have too, but it is better off to have a sysnand on 11.0.0 for recreating SX OS emunand if needed.

 

[Kallrkyle]

Or you could just make a backup of your SXOS emunand on your pc

 

[JayPea]

You would have to leave Sysnand at 11.0.0.

Not saying you have too

 

[Kallrkyle]

I was wondering that too

 

[nWo]

So, let´s say I update my sysnand to FW 12.x.x but also create a emunand for SX OS on FW 11.0

That should be enough to have them dual boot? my switch is banned so I dont care about online etc. Only want to have SX OS for the XCI mounting and atmosphere on latest for the games that are coming out.

 

[Hayato213]

So, let´s say I update my sysnand to FW 12.x.x but also create a emunand for SX OS on FW 11.0

That should be enough to have them dual boot? my switch is banned so I dont care about online etc. Only want to have SX OS for the XCI mounting and atmosphere on latest for the games that are coming out.

If you update then create emunand then it would be on the firmware you update not 11.0.0

 

[Draxzelex]

So, let´s say I update my sysnand to FW 12.x.x but also create a emunand for SX OS on FW 11.0

That should be enough to have them dual boot? my switch is banned so I dont care about online etc. Only want to have SX OS for the XCI mounting and atmosphere on latest for the games that are coming out.

emuMMC is a copy of sysMMC so if sysMMC is on 12.X, then when you make emuMMC, it will be on the same firmware so you will have to make the emuMMC before updating the firmware.

 

[nWo]

emuMMC is a copy of sysMMC so if sysMMC is on 12.X, then when you make emuMMC, it will be on the same firmware so you will have to make the emuMMC before updating the firmware.

Thanks. So, first do the emuMMC of SX now that I'm on 11.0, then after the emu is created, update the sysnand to use atmos there. I think I got it right this time. It is the first time ever that I am going to use emunand, so, I appreciate your help. I am going to use the SX emu only to mount XCI.

Lastly, I got the system memory full of games, so those are going to need the exact same size of SD on emuMMC? Or the sysMMC is shared between emu and sys? Thanks again.

 

[Kallrkyle]

Its going to need the same space on the SD, sys and emu doesnøt share the same space

If you want to move the games on your sysnand over to your newly created emunand, you need to make a copy of your Nintendo folder and call it Emutendo

 

[Augusto101]

Can we let this thread die already? Oh my god it's so stupid face it it's the end of sx os the only thing left are the chip clones ...that's it.