TBH, I didn't mentioned syscheck until you fixed your console because that wasn't really needed at the time.
In fact I didn't step in until you fixed the console because I don't want to be another random guy that might confuse you further. I stepped in just so you might learn a little bit of what you were doing.
I mentioned syscheck so that we can check if your softmod is up to date.
There are a few possibilities for booting problems like yours. The most obvious are banner brick and menu brick
Trying to fix banner brick without knowledge of what has been done to the console that causes the brick is dangerous and confusing
Menu brick actually is much simpler to fix although it is dangerous if you are not playing attentions
1. if it is the ios that caused the problem, it is safe to reinstall it and so should be tried first. You mentioned ios60 in your first post so everyone would assume you are on system menu 4.1 and start from there.
2. if it is the system menu itself, and you don't have bootmii@boot2, if would be dangerous to replace the system menu cause it will remove priiloader and if you didn't managed to reinstall it before rebooting, you will have no brick protection in case anything went wrong.
System menu requires the matching ios to work and has to match with the region of your console.
But as I said, if it is the system menu that caused the problem, you have no way out but to reinstall it.
PS. there are two types of bootmii:
a. bootmii@boot2 which reside itself in the Wii's boot loader which take control even before Prilloader and is the best brick protection - but only the first few batches of Wiis are vulnerable
b. bootmii as ios - as later Wiis blocked bootmii@boot2, bootmii can only be installed as ios but that provides very little brick problem if any
hackmii installer will install HBC and bootmii as boot2/ios automatically depending on your Wii's vulnerabilities.