Menu plus X etc stop working after a core crash + reboot

[alexdante]

I’m having a similar issue to this thread but the solutions listed there didn’t work for me.

I was trying to get some Amiga games running & Retroarch seemed to hang completely so I rebooted the device. Afterwards, the default hotkeys for opening the menu, quitting, modifying speed etc stopped working in all cores. I’ve used Restore Tasks in the Toolkit to restore both the Retroarch config & the overrides but there’s no difference: none of the hotkeys work.

So far the only solution I’ve found is to reflash, is there another option I’ve missed?

Thanks.

[Delibirb77]

how did you reboot the device? With the reset button, or with the safe restart combo?

More info is in the link below, as it says at the end, pressing the reset button can mess things up resulting in requiring a reflash

When should the reset button be used?

What does the reset button do? The reset button is hardwired to cut all power to the system instantly and does not allow muOS to safely close anything currently running. This is like pulling the plug from your PC while it is still running, and is likely to cause corruption of important files. This may not become apparent until much later when your device starts exhibiting weird behaviours. Because of this, it should only ever be used as a last resort. What should I do instead to minimise corru…

[alexdante]

Ah, that’s definitely what did it then. The restart hotkeys didn’t work so I ended up using the reset button.

Cheers.