Phones stuck in endless restart cycles, unable to function
In the quiet dependency we place on our devices lies a vulnerability rarely acknowledged until it surfaces: software meant to improve can sometimes diminish. OnePlus, a prominent Android manufacturer, has paused two OxygenOS updates after they left a portion of users across the United States and India with phones trapped in endless restart cycles. The company's candid apology and commitment to revisiting its quality assurance processes speak to a broader truth — that the speed of modern software delivery sometimes outruns the rigor required to make it trustworthy.
- Two OxygenOS updates — versions 16.0.7 and 16.0.5 — began locking affected phones into boot loops immediately after installation, leaving users without functioning devices.
- The disruption spread across a wide range of models, from the flagship OnePlus 15 to older Nord-branded phones, touching users in both the US and Indian markets.
- OnePlus moved quickly to halt further distribution, framing the pause as a precaution to protect device stability before the problem could reach more users.
- Engineers are now reverse-engineering the failure, building a patch while the company has pledged not to resume the rollout until stability is fully verified.
- With no release timeline announced, affected users remain in limbo — and OnePlus has made an unusually direct public apology alongside a commitment to overhaul its testing processes.
OnePlus has pulled two OxygenOS software updates after they began trapping users' phones in relentless restart cycles, rendering the devices temporarily unusable. The company announced the halt on its community forum, acknowledging that a subset of users who installed versions 16.0.7.XXX and 16.0.5.XXX found their phones caught in boot loops — unable to complete startup and therefore unable to function at all.
The failures emerged across devices in the United States and India. Version 16.0.7.XXX had been aimed at the OnePlus 15 series, while 16.0.5.XXX targeted a broader range including the OnePlus 13, 12, 12R, and several Nord models. Though OnePlus described the number of affected devices as small, the span of models involved suggests the impact reached a meaningful slice of its user base.
The company's engineering team is now working to identify the root cause and develop a corrective patch. OnePlus has stated it will not resume the rollout until the software's stability has been fully validated — though no timeline has been offered, leaving affected users in an uncertain waiting period.
What distinguished OnePlus's response was its tone: a notably direct apology, largely free of corporate deflection, paired with a commitment to reviewing its testing and quality assurance practices. For a major phone manufacturer to openly acknowledge that its pre-release vetting fell short is uncommon — and it signals that the company understands the trust at stake when the devices people depend on most become the source of the problem.
OnePlus has pulled the brakes on two software updates after they began trapping devices in endless restart cycles, effectively rendering phones unusable until a fix arrives. The company announced the halt of OxygenOS versions 16.0.7.XXX and 16.0.5.XXX on its community forum, acknowledging that a subset of users who installed the updates found their phones stuck in boot loops—caught in a cycle of restarting that leaves them unable to function.
The problem emerged after the updates rolled out to devices in the United States and India. OnePlus reported that "a small number of devices" experienced abnormal restart behavior and boot failures following installation, prompting the company to pause further distribution. For those users, the updates transformed their phones into expensive paperweights, at least temporarily. The company framed the decision as a precaution, citing concerns about device stability and the overall user experience.
OnePlus's engineering team is now working backward through the code, hunting for what caused the malfunction while simultaneously developing a patch. The company said it will not resume rolling out these updates until it has fully resolved the underlying issue, validated the software's stability, and verified its reliability across devices. No timeline has been announced for when users might expect the corrected versions to arrive.
The OnePlus 15 series was the primary target of version 16.0.7.XXX. Version 16.0.5.XXX was intended for a broader range of older models: the OnePlus 13, OnePlus 12, OnePlus 12R, and several Nord-branded phones including the Nord 5, Nord 4, Nord CE 5, and Nord CE 4. The company's statement did not specify exactly how many devices were affected, only that the number was small, though the range of models suggests the impact could be felt across a significant portion of OnePlus's user base.
In its public statement, OnePlus apologized to affected customers and said it is taking the matter seriously. The company also committed to reviewing its testing and quality assurance processes to prevent similar failures in the future—a rare acknowledgment from a major phone manufacturer that its pre-release vetting fell short. The apology was notably direct, without the corporate hedging that often accompanies such statements from larger competitors. Still, OnePlus offered no specific date for when the corrected updates would be available, leaving users in a holding pattern.
Notable Quotes
OnePlus acknowledged that a small number of devices experienced abnormal restart and boot issues after updating, and said it paused the rollout due to concerns about device stability and user experience.— OnePlus community statement
The Hearth Conversation Another angle on the story
Why would OnePlus release updates that brick devices in the first place? Shouldn't testing catch something this fundamental?
That's the question OnePlus is asking itself right now. The company says it's reviewing its QA processes, which suggests the testing protocols either didn't catch the boot loop issue or didn't test on a wide enough range of hardware configurations.
How many people are we talking about here—is this affecting thousands of users?
OnePlus called it "a small number," but they never gave a hard count. The updates were rolling out to multiple device lines across two major markets, so even a small percentage could mean hundreds or thousands of people with unusable phones.
What happens to someone whose phone is stuck in a boot loop right now? Can they fix it themselves?
Not easily. A boot loop means the phone keeps restarting and never fully loads the operating system. Users are essentially locked out until OnePlus releases a corrected update or provides a workaround—which they haven't done yet.
Is this unusual for OnePlus, or does this happen across the industry?
Major software failures do happen, but the fact that OnePlus is publicly apologizing and committing to process changes suggests they see this as a significant misstep. It's the kind of thing that erodes trust, especially for users who depend on their phones.
When will the fixed updates actually roll out?
That's the frustrating part—OnePlus hasn't said. They're waiting until they've fully validated the fix, which is responsible, but it leaves users in limbo with no clear timeline.