This is what I understood all along when I made my first post, reply #19.
The next step I would do is to trace what connects to the FET gates. The FET gates (IIRC on an H bridge) will be connected in pairs.* So there will be two semiconductors driving these two pairs. (Maybe the same chip/driver driving both pairs). There will also be a series resistor in between this driver and the FET gates, which you can probably just ignore. Find that part/s. The driver. If your lucky, you can buy this part.
At rate, you can remove it, and you can probe all the pads on this part while turning on the machine. You will hopefully find that the input to this semiconductor is still alive. That there's one of these pads/traces that changes voltage when the motor is supposed to run this way, then that, on startup. If that's not there, then you continue working back. This working back from here might be impractical unless you can find the datasheet for this part, so hopefully you find the datasheet and find live signals on the input pins (or pads, after you remove this part).
I suppose it is possible that the main brain/micro is still running, but the output pins that drive these FETs got burnt. Then you're basically stuffed. I've never seen this happen. The micro always dies, too, IME, but I've heard of it.
*Edit: I rescind. I refuse to look at an H bridge schematic/tutorial. But logically speaking, I believe there should have to be 4 separate control signals, one for each FET.
This would be something I could use my multi channel logic probe for, one probe soldered to each FET gate, so see which half (or both) of the bridge isn't receiving gate drive when the motor is supposed to be moving. Then same on the FET driver chip's (most likely a single IC with like 20 ish pins) inputs.