KARACHI: Senior player Mohammad Hafeez said that a lot has been said regarding his injury in the World T20 and promised to speak up about it soon.
The 34-year-old is unhappy with the way certain sections of the media first said he is faking an injury and then claimed that he had been carrying a knock since the Asia Cup and had been hiding it.
“I’ll speak the truth; I’m waiting for the right time and I’ll speak quite openly,” said Hafeez. “Pakistan couldn’t do well [in the Asia Cup and World T20] and all of us should take responsibility for it, including me. It isn’t right to put all the blame on one person.”
PCB appoints Sarfraz Ahmed new T20I captain
Hafeez also welcomed the board’s decision to appoint Sarfraz Ahmed as the new T20I skipper stating that it shows continuity, and backed the 28-year-old to succeed.
Meanwhile, Pakistan ODI skipper Azhar Ali also echoed Hafeez’s words in backing Sarfraz’s appointment, saying that the wicketkeeper has shown his captaincy credentials at all levels. Azhar added that Sarfraz has proven himself as a leader with his performances as captain for Pakistan U19 and Pakistan Super League outfit Quetta Gladiators.
“I’m very happy for Sarfraz because he is a very close friend of mine and it’s a good decision,” said Azhar. “I hope he’ll have success similar to what he did with the U19s and the Gladiators.”
PCB chief apologises to Waqar Younis over leaked confidential report
Azhar revealed that he has been unable to play cricket for the past few months but is targeting the upcoming Pentangular Cup as a good opportunity to regain his form ahead of the series against England.
The 31-year-old also backed the idea of having a long training camp for the national side, suggesting that it is important for the players to improve their fitness levels.
Published in The Express Tribune, April 7th, 2016.
Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ