Shami’s Knee Trouble Derails Australia Dream, But Rohit Keeps the Door Ajar

WhatsApp Group Join Now
Telegram Group Join Now

India’s Test and ODI captain, Rohit Sharma, delivered disappointing news on Tuesday during a press conference ahead of the first Test against New Zealand in Bengaluru. When asked about the rehabilitation progress of pacer Mohammed Shami, Rohit all but confirmed that Shami is unlikely to travel with the team to Australia for the upcoming Border-Gavaskar Trophy, a five-match Test series. Shami has been sidelined since the conclusion of the 2023 ODI World Cup, and despite multiple reports of his potential return, setbacks have continued to hinder his recovery.

Addressing the media, Rohit explained that even if Shami regains fitness, the team is not inclined to take him to Australia. The reason for this decision stems from Shami being “undercooked,” given his prolonged absence from competitive cricket.

“Honestly, it’s tough to make a decision about him for the Australia series. He had a setback, with swelling in his knees, which set him back further, and he had to restart the recovery process. Currently, he’s at the NCA working with doctors and physios. We don’t want to take an underprepared Shami to Australia, but we’re still hoping for the best,” Rohit said.

Shami, however, has previously dismissed rumors regarding his unavailability for the series. In response to reports about his recovery delays, Shami took to X (formerly Twitter), refuting the claims and clarifying that he has not been ruled out of the Border-Gavaskar series.

“Why are these baseless rumors being spread? I’m working hard and doing my best to recover. Neither I nor the BCCI have said I’m out of the Border-Gavaskar Trophy. I urge people to stop paying attention to such unofficial news. Please refrain from spreading fake news without any official statement,” Shami wrote.

While Rohit has cast doubt over Shami’s participation, he stopped short of completely ruling out the pacer’s involvement in the Australia series.

Back to top button
error: Content is protected !!