Blue screen after udating sysmmc with hwfly

[sj33]

I have an OLED Switch with a hwfly mod, and both a sysmmc and emummc. I thought it would be safe to update the sysmmc to 17.0.0 and updated this within stock sysmmc. I now get a blue screen when booting the sysmmc. It works fine from emummc, just not sysmmc.

Have I broke my sysmmc?

 

[Hayato213]

So how did you updated, did you updated to 17.0.0 before updating Atmosphere and Hekate?

 

[sj33]

Right, it seems to work if I reboot out of hekate into OFW rather than using the Stock sysmmc option. At least I know it is not bricked.

 

[Hayato213]

You need a new warmboot for 17.0.0 for you to be able to boot into stock to fix it.

 

[sj33]

Right, panic averted. I assumed it would be enough to simply update hekate, but I needed to update Atmosphere too. I was hoping to avoid this because Tinfoil doesn't work with it yet, but oh well. It's all working at least!

 

[Hayato213]

Right, panic averted. I assumed it would be enough to simply update hekate, but I needed to update Atmosphere too. I was hoping to avoid this because Tinfoil doesn't work with it yet, but oh well. It's all working at least!

Next time don't update when a firmware just come out.

 

[sj33]

In case anybody happens to stumble across this in the future with the same issue, new sigpatches sorted it. I incorrectly assumed that booting stock through Hekate would not need them.
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10269993