Johnny Manziel issues apology to Texas A&M fans via Twitter

Nov 5, 2015; Cincinnati, OH, USA; Cleveland Browns quarterback Johnny Manziel (2) against the Cincinnati Bengals at Paul Brown Stadium. The Bengals won 31-10. Mandatory Credit: Aaron Doster-USA TODAY Sports
Nov 5, 2015; Cincinnati, OH, USA; Cleveland Browns quarterback Johnny Manziel (2) against the Cincinnati Bengals at Paul Brown Stadium. The Bengals won 31-10. Mandatory Credit: Aaron Doster-USA TODAY Sports

Johnny Manziel recently felt remorseful on Twitter and took it upon himself to apologize to Texas A&M fans.

Back during his college days, Johnny Manziel was a fan favorite. OK, so opposing fans weren’t so welcoming of the confident, sometimes cocky, Heisman winner, but the dual-threat quarterback won over the hearts of Texas A&M Aggies fans with his fantastic play.

Manziel became the first freshman to ever win the Heisman and he did so after he passed for 3,706 yards, 26 touchdowns and nine interceptions while rushing for another 1,410 yards and 21 scores.

Entering his sophomore season, he was suspended for the first half of the first game against Rice for potential NCAA violations. That was just the beginning of his off-field issues as the NFL hasn’t been so kind to him, either. He was involved in a domestic violence incident and has been fighting to stay sober.

You could say that Texas A&M fans have been disappointed at what their poster child has become. He is no longer a valued representative of the university because of his antics, but that doesn’t mean the Aggies don’t look back and smile at the good times when he was a nightmare for opposing defenses.

Over the weekend, Texas A&M’s Twitter page posted a ’49 days until Aggie football’ tweet and Manziel had this to say:

Maybe this is the start of his career turnaround, but it’s just that: a start. He has a long way to go to show he’s truly sorry for his actions and it starts by being sober and getting his football career back on track.

For more NCAA Football coverage, check out our hub page.

Loading recommendations... Please wait while we load personalized content recommendations