Hekate: Genuine Boot Option

[H4X0R46]

Is there any chance you could consider adding a genuine boot option? Mariko users right now don't have any option to boot the system cleanly for online play and sysnand updates when using Atmosphere, since Atmosphere is so new on Mariko. We can boot stock, sure, but a completely clean boot with HOS bootloader would be ideal to avoid bans.

[urherenow]

Can you not already do that yourself in the .ini? I don't have a mariko unit, so I'm not sure.

There are stock setups in the template, even for using a stock emummc. You likely want [Stock ALL FW]

@CTCaer just noticed that the emummc_force_disable=1 flag is in the readme list (and template), but the description for stock says emummc_force_disabled=1.

[H4X0R46]

Can you not already do that yourself in the .ini? I don't have a mariko unit, so I'm not sure.

There are stock setups in the template, even for using a stock emummc. You likely want [Stock ALL FW]

@CTCaer just noticed that the emummc_force_disable=1 flag is in the readme list (and template), but the description for stock says emummc_force_disabled=1.

Yeah you can, that works, but my concern is if it's safe enough to use for legit online play and sysnand updates without a very high ban risk. Is it "clean" enough?

[masagrator]

Genuine boot rrquires locking glitching until reboot.
Using stock in hekate won't boot 1:1 as OFW.
This issue seems more related to spacecraft than Hekate as spacecraft needs function for this to be implemented and then Hekate could take advantage of it.

[H4X0R46]

Genuine boot rrquires locking glitching until reboot.
Using stock in hekate won't boot 1:1 as OFW.
This issue seems more related to spacecraft than Hekate as spacecraft needs function for this to be implemented and then Hekate could take advantage of it.

I've been hesitant on flashing spacecraft honestly. I'm still on SX firmware for my Core. But I'm thinking if TX was able to do it, shouldn't it be easy enough to implement into Hekate? Or did TX do underhanded proprietary crap like they're known for?

[BlackRabbit22]

@masagrator

According to balika011, it is an issue that is related to hekate and not spacecraft-nx here in this comment.

[H4X0R46]

@masagrator

According to balika011, it is an issue that is related to hekate and not spacecraft-nx here in this comment.

That's good to know! Since atmosphere is so new on Mariko, and we don't actually have an easy way to boot 100% stock since our exploit is a soldered modchip, a genuine boot option would be ideal! 👍

[CTCaer]

It's not an issue with hekate.
hekate will never get distributed with copyrighted data such the one needed for the "genuine boot".
Now if you really want that, it's purely a modchip/fw issue. And ask them to fix that.

As for hekate, best you can get is the OFW option reinstated for patched consoles.
And that's only if you have proper secondary BCTs.

Stock option from hekate is always the better option if you don't want to burn fuses.
That option only replaces ninty's secmon with exosphere and nothing else for Marikos. Everything else is kept official.

EDIT:
Because some are DMing what is that OFW option, here's an explanation:
hekate always supported real OFW. That's the Reboot (Normal) in TUI and Reboot -> OFW in Nyx.
This goes through nintendo's bootloader without burning fuses.

It causes a panic and a specific value written to a register. Because of how the system works on that, it does not deassert the SYS_RESET pin or disables all regulators. Because of that, a glitch doesn't happen and the bootrom tries every BCT until one is valid. If valid one is found it loads the nintendo's bootloader. That bootloader checks that register and skips the fuse burning and continues to load OFW.

The change is purely in Nyx for that. And it was just added back.
No extra interaction with anything is needed or any copyrighted blob.