Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Nov 10, 2016, 10:30 AM (IST)
Edited: Nov 10, 2016, 10:43 AM (IST)


After suffering from hamstring injury towards the end of the first day of first Test between India and England at Rajkot, pacer Mohammed Shami come back in style by scalping Moeen Ali‘s wicket on day two. The second day of the match began with England‘s score being at 311 with the loss of four wickets. Moeen was unbeaten at 99 and took no time to get to his maiden Test ton against India as he did that on the third ball of the day. He took 195 balls to complete his hundred, which included nine boundaries and it was surely a hard earned century for him. Full Cricket Scorecard: India vs England 1st Test at Rajkot
Further, Moeen looked quite comfortable in the crease with four more boundaries to Indian pacers. Moeen along with Ben Stokes, was scoring runs at quick rate and India were in much need of a wicket. At the meantime, Shami, who was bowling bouncers regularly since the start of the day, bowled a decent in-swinging good length delivery to Moeen, which he misjudged and decided to leave. The ball did no go the way Moeen thought it will and it hit the off stump, which began rolling after the moment that delivery touched the wicket. It was surely a strange choice from Moeen. Had he tried to touch that delivery and got an edge, he could have survived as Indian fielders are not at their best currently.
That ball by Shami has created a stir among the fans, who loved it and have gone mad as it can be seen in the social zone. We present some of the tweets from social zone.
Shami to Moeen. pic.twitter.com/w2rwBmT8lq
â Clive (@vanillawallah) November 10, 2016
WTF just happened! Brother Shami cleans up Brother Moeen. The fissures in the social fabric of the Ummah are real. #IndvsEng
â Not A Journo (@ItsARipper) November 10, 2016
U beauty Shami…
What a ball to dismiss Moeen Ali..
Finally got a wicket..
â Kaushik Pawanist (@SRT__forever) November 10, 2016
What a Wicket! Shami did a wonderful job!
Moeen Ali bowled total runs: 117(213)â Saurashtra Cricket (@saucricket) November 10, 2016
Shabaash Shami but job done Moeen. Can India keep them below 450? #INDvENG
â Nikhil  (@CricCrazyNIKS) November 10, 2016
Shami should have his tail up after sending Moeen’s offstump flying. But what was Moeen doing? Brain freeze @HTSportsNews
â Sanjjeev (@Sanjjeev) November 10, 2016
Error in judgement from Moeen Ali and the off stump goes cartwheeling. Mohammad Shami gets the reward for some fine bowling. 343/5 #INDvENG
â #LiveScores (@Cricket_CAREER) November 10, 2016
Moeen Ali’s gone! Shouldering arms to an in-ducker from Shami which uproots his off stump. Beautiful innings comes to an end on 117 #INDvENG
â AllOutCricket (@AllOutCricket) November 10, 2016
Field position played tricks in Moeen Ali’s mind. Shami got one now
â SELVA BALAJI M (@SELVA_BALAJI191) November 10, 2016
Shami uprooted the stumps of moeen , superb reverse swing .#EngVsInd
â Jamal Hassan (@JamalSherazi) November 10, 2016
Aur Shami Moeen Ali ka Shamiyana ukhadte hue… #OkBye#INDvENG #EngVsInd
â Chinmay Jawalekar (@CricfreakTweets) November 10, 2016
Moeen choose worst way to get out. Bowling Shami #INDvENG
TRENDING NOW
â Shivaji Bajpai (@ShivajiThinks) November 10, 2016
Currently, England have went past 350 and are looking strong to score a big total, which will surely make this contest interesting as no team in recent times have been able to score big.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.