Not really, but too much to unpack in there.
In short, most planes don’t have an AOA indication, but it is fed into the computers. If the input is wrong, that can cause the aircraft to think it is in a regime of flight it is not. In this case, it was trying to force the aircraft nose down, because it believed the aircraft was approaching a stall. As it tries this, the pilots can force the opposite input to try to stop it, but can run out of elevator control if they have what is called a “runaway stabilizer” pitching the aircraft down. Accordingly, there are STAB CUTOFF switches on the pedestal to the right of the throttles by the FO trim wheel. Had they trimmed opposite the runaway stab and used the switches, they could have flown the aircraft back to the airport. Sadly, in their struggle to understand and oppose what what happening, it appears they didn’t know exactly what the problem was or how to stop it and/or correct it once their initial fight against it proved somewhat unsuccessful, so the aircraft accelerated and descended to their death.
With hindsight, it is always easy to second guess what happened and why, and to inject rationality into what was an horrendous situation in a brand new aircraft with which they were both undfamiliar and facing a fault that almost never happens. So, in the cold harsh light of day, it can be said that an aircraft fault was exacerbated by incorrect inputs and actions by the crew. However, when something goes wrong on a flight deck, it is often something that is far from obvious, easy to identify, or requires a simple “turn it off,” because flying is such a dynamic activity. Everything is somehow connected to everything else. So many things are interconnected that sometimes even understanding what caused X to happen is a chain of events that was invisible to the crew and only indicated to them by a secondary or even tertiary event that they must correlate within seconds to correct. Not an easy thing!
Some people think an engine blowing up is the worst thing that could happen, because it is loud, violent, often makes the aircraft shake and is one of the two things keeping the aircraft in the air. However, I think most pilots would agree that it is the insidious faults, the ones that mask their primary failure, that are the ones we hate the most. In this instance, figuring out what was causing the problem was hard enough, but correcting the problem once it started was always going to be harder without an almost complete “turn it off and revert to manual everything,” because the inputs being received to the Primary Flight Displays and controls WERE the problem, but they just couldn’t get there quickly enough.
The FAA just issued an Emergency Pilot Bulletin for this aircraft accident, re-emphasizing the corrective actions for the multitude of messages and actions that MIGHT be caused by this anomaly. Sobering stuff!