This story is being continuously updated…. New updates are being added at the bottom…..
Original story (from June 08) follows:
Sometimes, it is pretty easy to forget just how complex the engineering that goes on behind the scenes to make our smartphones work correctly is. Often times, our devices are a single misstep away from disaster and the countless update recalls are a testament to this.
Not too long ago, we brought to light that Asus ZenFone Max Pro M2 users were having issues with their devices after an update to build .073. More on that story here.
That was way back in March this year and many affected users have been stuck with unusable devices since then. Recently, we highlighted that Asus was working to fix ZenFone Max Pro M2 ‘stuck while booting’ issue, this even at a time when the affected users were borderline losing hope altogether.
Now, it is coming to light just how extensive the problem for the affected Asus devices is. According to users who tried to get help on this issue from Asus, the issue requires that the affected devices undergo a motherboard replacement.
Sadly, the company required the users to fork out their money and foot the cost of motherboard replacement for their device, despite the issue being caused by an update rolled out by them.
This was no doubt, bound to rub all the affected users the wrong way. Many of these users have been rallying themselves online, trying to petition Asus to issue a recall for the Asus ZenFone Max Pro M2.
Luckily, it seems as though the company really does listen to the cries of its users. We are reliably informed by one of the affected users that Asus is going to swap the affected users’ handset defected with this boot issue.
If Asus indeed decides to do this for all affected users, this could see an end to almost three months of suffering for Asus ZenFone Max Pro M2 users. We shall continue to keep an eye on this story and update as and when we get more info.
Many thanks to Chouhan for sharing the details of his case.
Update 1 (June 10)
It appears the company is handling the cases one by one, as now one more complainant has mentioned that they’re getting a replacement device. (Thanks again for the info Chouhan!)
Update 2 (June 10)
We’ve reached out to the company to know their official stand on the matter. As and when we’ll hear back, we’ll update this post. Meanwhile, we’d encourage affected users to share their experience in the comments section below.
Update 3 (June 13)
We’re conducting a poll to assess how many ZenFone Max Pro M2 units are affected by this bootloop issue and what all have the users got to hear from the company so far. So be part of the poll and share with us your experience.
Update 4 (June 17)
Asus responds to the Zenfone Max Pro M2 boot loop issues. Head here for more details.
Update 5 (June 25)
This issue has persisted for long, so we’ve compiled a story highlighting every development so far. We’ll be actively updating that story with every new development, so those affected can keep a track of that.
NOTE: We have these and many more Asus stories in our dedicated Asus section.
PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.