Hacking Question Hekate not booting anything

[StarveBread]

Updated my sysnand to 11.0.1 then updated atmosphere and hekate now nothing boots up, emunand or sysnand. It just shows a black screen, no logo.
Using an Erista Ipatched switch with sx core.

 

[GCS]

You can boot into SysNAND by going into SX Boot Menu and then Genuine Boot. This may burn fuses.
I believe you already do Clean Up before launching Hekate. If you used to boot to SysNAND with Atmosphere then it won't work until SX gets updated afaik.
What emuNAND are you using: SX OS or Atmosphere?

 

[StarveBread]

What emuNAND are you using: SX OS or Atmosphere?

Not sure but i've been using hekate to boot into sysnand.

 

[GCS]

Not sure but i've been using hekate to boot into sysnand.

Did you mean EmuNAND instead of SysNAND?

 

[StarveBread]

Did you mean EmuNAND instead of SysNAND?

sorry, yes I mean emunand

 

[GCS]

sorry, yes I mean emunand

-Your SysNAND won't be able to boot up until SX OS gets updated or you Genuine Boot.

-About your EmuNAND, are you sure that you are using the latest atmosphere and Hekate?

 

[StarveBread]

-About your EmuNAND, are you sure that you are using the latest atmosphere and Hekate?

yes, I took atmosphere from here: https://github.com/Atmosphere-NX/Atmosphere/releases
and hekate from here: https://github.com/CTCaer/hekate/releases
both the latest versions

 

[GCS]

yes, I took atmosphere from here: https://github.com/Atmosphere-NX/Atmosphere/releases
and hekate from here: https://github.com/CTCaer/hekate/releases
both the latest versions

It is probably caused by your firmware version, for now you should wait until SX OS gets updated as far as I understood.

 

[StarveBread]

Reinstalled the entire thing now it works. Didn't bother trying out the sysnand for now.

 

[StarveBread]

Happened to me again. turns out it happens when I do a full shutdown. Reboot to payload doesn't seem to trigger it.

 

[Draxzelex]

Happened to me again. turns out it happens when I do a full shutdown. Reboot to payload doesn't seem to trigger it.

That is because the SX Core modifies the console in such a way that prevents you from normally using other CFW.