Hacking Question How To Launch Hekate From SX Core?

[gudenau]

That's the most frustrating thing for Mariko users, like myself. Hoping the firmware or boot.dat can be unlocked like the X3 Bios on the XBOX back in the day.

Do you know if it is possible to add the keys back if they where dumped before? I probably have the keys on my SD card somewhere.

 

[Draxzelex]

Do you know if it is possible to add the keys back if they where dumped before? I probably have the keys on my SD card somewhere.

Its not possible.

 

[gudenau]

Its not possible.

I did figure out a way to get the keys back, but it requires tethering. Would be cool if you could just dump them onto the SD card and have the tools patch Horizon to use it.

 

[Paco46]

@SciresM
Updates on this:

• I got it installed and it works, can boot pirate land software just fine (as expected)
• Hekate works (unexpected)
• Atmosphere black screens (expected)

If you want me to do anything, ask.

@gudenau
Im late to this topic. Sorry about that OP.
Was atmosphere not working because you tried using the payload tab in the SX-OS boot menu? I'm in the same boat now (SX-Core installed on unpatched v1 switch) and I wonder if atmosphere will work if I use an RCM jig instead.

 

[BaamAlex]

I'm in the same boat now (SX-Core installed on unpatched v1 switch) and I wonder if atmosphere will work if I use an RCM jig instead

Using a sx core chip in a fusée gelée unit is wasted money.

 

[ChronicGamer]

@gudenau
Im late to this topic. Sorry about that OP.
Was atmosphere not working because you tried using the payload tab in the SX-OS boot menu? I'm in the same boat now (SX-Core installed on unpatched v1 switch) and I wonder if atmosphere will work if I use an RCM jig instead.

i have a patched v1 aka Erista Unit, that runs atmosphere fine. The only issues i have is that you have to run the cleanup process everytime u want to boot atmosphere, and even then to prevent black screening you need to boot through hekates launch buttons, so it works with fusee-secondary but not fusee-primary.
Edit to Add: running the clean up process leads to the sx modchip taking abit longer to boot if u have to restart because it has to reapply the change it makes to boot0 part

Using a sx core chip in a fusée gelée unit is wasted money.

i agree there, especially as you could just use the other hard mod options (Trinket M0 & RCM x86) (Thank You BaamAlex)

 

[BaamAlex]

sorry i forgot the name

Trinket M0 or RCM x86

 

[Paco46]

Using a sx core chip in a fusée gelée unit is wasted money.

Although I agree with you, the SX-modchip is path I took to mod my unpatched system. It seemed like more fun

i have a patched v1 aka Erista Unit, that runs atmosphere fine. The only issues i have is that you have to run the cleanup process everytime u want to boot atmosphere, and even then to prevent black screening you need to boot through hekates launch buttons, so it works with fusee-secondary but not fusee-primary.
Edit to Add: running the clean up process leads to the sx modchip taking abit longer to boot if u have to restart because it has to reapply the change it makes to boot0 part

Would having a dedicated sd card for atmosphere remove the need for the clean up process? (I ask because I'm going to continue mainly using my sxos emunand sd, but every so often i'd like to run a cfw sysnand so I could use some atmosphere-exclusive systools.

 

[gudenau]

When something is free it is not a waste of money. .-.

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

Hey @BORTZ you mind locking this? The Atmosphere and Hektate people don't want to support this and this thread is just a huge waste of time at this point.

Thank you.

 

[Paco46]

@gudenau Yep I read through the entire thread and doesn't look like there are too many suggestions for us.
Its simple. The situation goes as follows: Sx-Core installed on unpatched switch. How do we run atmosphere? Is the use of an RCM jig required for proper functionality ?

 

[gudenau]

@gudenau Yep I read through the entire thread and doesn't look like there are too many suggestions for us.
Its simple. The situation goes as follows: Sx-Core installed on unpatched switch. How do we run atmosphere? Is the use of an RCM jig required for proper functionality ?

The only way to make this stuff work is to try and boot into hekate which is hit or miss and use that to go into RCM and boot that way.

 

[Basketto]

@gudenau
Im late to this topic. Sorry about that OP.
Was atmosphere not working because you tried using the payload tab in the SX-OS boot menu? I'm in the same boat now (SX-Core installed on unpatched v1 switch) and I wonder if atmosphere will work if I use an RCM jig instead.

If you on a version 1 switch, other users confirmed you can run everything from sx core that a version 1 fusee gelee switch can.
The hardware is the same inside. The fact your using an sx chip should make zero difference.
Atmosphere doesnt work on MARIKO units, which is what Sciresm is working on.
Why you would put an sx core on an unpatched version 1 is well beyond me aswell. Trinkets have been around for years, & autorcm exists.

 

[Paco46]

Solved on my end.
Atmosphere works great with an SX-Core modchip installed on v1 unpatched switch.

The steps I took to get it working go as follows:
1. Set up SD card for Hekate/Atmosphere as you regularly would for an ordinary unpatched switch (I used NH Switch's Guide)
2. Drop boot.dat and hekate_ctcaer_"version".bin onto the root of the SD
3. "Cleanup" sysnand through SXOS. (Power on switch -> Options -> SX Core -> Cleanup -> Continue)
Since SXOS seemingly dirties your boot0/1, this is necessary to not blackscreen when launching atmosphere from Hekate.
4. Launch Hekate payload through SXOS. (Options -> SX Core -> Payloads -> hekate_ctcaer_"version".bin)
5. Launch Atmosphere through Hekate after all of your necessary backups.

That's it. Its quite simple.
A few things to note is that you need to have SXOS "cleanup" your sysnand after every power-on since SX-Modchip dirties your boot0/1 during your next power-on (this is why your switch will take an additional 30sec or so to power-on after powering-off a "cleaned up sysnand" state. Also I suggest you backup boot0 and boot1 through Hekate and save those files onto pc since those are the cleaner backups with less SXOS infection. Finally, note that booting into Hekate through SXOS can be sketchy every so often like @gudenau mentioned, so don't be surprised when see a glitchy UI. Just power-off then back on and it should work on your next try or 2.