robert bartsch (and takata)
2h10m05s. Unreliable a/s.
This is an ACARS message, not a DFDR trace. Something was bollux with IAS in the cockpit to generate the maintenance entry into log.
Takata, you are assuming that ACARS report is real time, and by inference that ACARS reports simultaneously with fault. Impossible.
The Speeds were reported for time 'x' prior to loss of PRIM.
"So the nose-up input was likely caused by the incorrect assumption that AS was too high; right?"
"If a stall was being caused by too much AS, wouldn't there be other physical indications (wing shutter, nose over, etc.) to confirm this?"
Here, rb suggests the pilot may have alertly already responded to bunk data. The ACARS report a/p dropout first, not UAS. If the PF was aviating in Normal Law for a time certain prior to AD hash, his pull and roll would be indicated as correct. He could also manipulate the stick with impounity, and let the protections sort out life on the edge of Stall or wing drop.
Just because our Pilot responded to overspeed doesn't make him wrong.
Overspeed and turbulence may have killed the autopilot, instead of UAS. Although you have said that UAS is without question true.