OnePlus Halts OxygenOS 16 Rollout After Boot-Loop Bug Hits Two Builds

OnePlus stopped the rollout of two OxygenOS 16 builds this week after users reported their phones rebooting on a loop and getting stuck during startup, freezing software shipments to its India and United States fleets within days of pushing them out. The pulled builds are OxygenOS 16.0.7.XXX, the version queued for the OnePlus 15 in India, and OxygenOS 16.0.5.XXX, the version reaching a broader set of older Nord and recent flagship models.

The pause landed in the same week the company began pushing OxygenOS 16.1 to the OnePlus 15 and OnePlus 13 series, a feature-heavy release built around a new lock-screen capsule called Live Space.

What OnePlus Paused This Week

On the company’s community forum, a OnePlus engineer posted that the rollout of 16.0.5.XXX and 16.0.7.XXX had been “immediately paused” after a small number of users reported abnormal restarts and boot-related problems. The team apologized, acknowledged the disruption, and said engineering was taking the matter seriously.

The wording is unusually direct for an over-the-air halt. Most original-equipment manufacturers quietly choke off staged rollouts in the background and let the served percentage drop to zero without a press note. This time OnePlus moved to the front page of its community hub for the OnePlus 15 build and named the bad versions by exact string.

Affected users have been told to wait, with no date for the queue to resume. Anyone whose phone is already on 16.0.5.XXX or 16.0.7.XXX has been told not to sideload unofficial mirrors, which has historically been the failure path when communities try to brute-force their way out of a paused rollout.

The company also said it is reviewing its internal testing and quality assurance processes to reduce the chance of similar regressions in future updates.

Inside the Two Affected Builds

OxygenOS 16.0.7.XXX was the rapid-cycle update meant to follow 16.0.5.XXX into the same device families. The earlier build had already been deployed to a cross-section of older Nord and flagship hardware in India and the United States. The later build was meant to extend coverage and add the OnePlus 15 to the mix in India before the global ramp to 16.1.

The bug signature is restart-during-boot, not restart-after-boot. That distinction matters because a device that cannot finish bringing itself up locks the user out before the system process can apply a corrective patch. It is closer to a brick than to an app-layer crash, and it is what users on the community forum and on aggregator posts have described in the worst cases.

The Devices and Regions Caught in the Pause

OnePlus has not published a definitive device list. Reports based on user posts place the impact across the Nord CE 4 through the recent flagships, with the OnePlus 15 in India added on the 16.0.7 ramp. The geographic footprint is India plus the United States, two of OnePlus’s largest update-active markets.

For users in those two countries, the practical consequence is two-fold. If the over-the-air notification has not yet arrived, OnePlus has effectively done the holding for you; the paused builds are not being served. If the install already completed and the device is showing restart symptoms, OnePlus is collecting bug logs through the community forum and, in some cases, routing affected handsets through service centers for guided recovery.

Anyone outside India and the United States with a OnePlus device should still see a normal update notification cadence. The paused builds are regionally segmented, which is one reason OnePlus could halt them without disrupting OxygenOS 16.1’s parallel push to the OnePlus 15 and OnePlus 13 series elsewhere.

OxygenOS 16.1 Arrives on Flagships the Same Week

While the older-fleet builds froze, OnePlus began rolling out OxygenOS 16.1 to the OnePlus 15 and the OnePlus 13 series. The headline feature is Live Space, a pill-shaped capsule that lives on the lock screen and surfaces notifications, timers, and music controls without covering the wallpaper. The visual concept is close to Samsung’s Now Bar on One UI 7 and to the Dynamic Island layout on recent iPhones.

Live Space supports several gestures. Users can swipe down to collapse lock-screen notifications into the capsule and swipe up to expand them. Tapping the album-art tile opens a music focus mode that fills the screen with cover art and lyrics. Tapping a timer expands the countdown to a full-screen view without requiring an unlock.

The 16.1 release also brings:

• An Organise tab in the app drawer that auto-arranges icons by category in a single tap
• Refreshed system animations across navigation, multitasking, and notification panels
• Upgraded AI capabilities, including improvements to the on-device assistant and writing tools
• A redesigned camera app interface with a layout that closely resembles the recent iPhone shutter and mode-picker arrangement

The May 2026 security patch is bundled with the OxygenOS 16 trunk going to the OnePlus 13 and OnePlus 13s, separately from the paused 16.0.x line.

A Repeat of OnePlus’s Old QA Problem

The community-facing apology is the second time in roughly a year that OnePlus has had to halt and reset an OxygenOS rollout. The company runs an unusually rapid build cadence by Android-OEM standards, splitting updates between feature versions (the 16.1, 16.2, 16.3 trunk) and incremental patch versions (the 16.0.5, 16.0.7 line). That cadence has historically widened the surface area for boot-recovery regressions.

To ensure device stability and protect user experience, we have immediately paused the rollout of the above-mentioned builds while our engineering team investigates the root cause and prepares a fix.

The statement came from a OnePlus engineer on the community forum. The company said it is “reviewing and strengthening” its testing and quality assurance processes. The promise is familiar from the prior pause cycle; the test is whether the next 16.0.x build that reaches India and the United States comes through cleaner.

For the OnePlus 15 specifically, the situation is unusual because the same device is on two parallel build trains at once: 16.0.7 (paused) and 16.1 (rolling out). A OnePlus 15 owner in India may receive 16.1 directly without ever passing through the bad 16.0.7 build, depending on which queue the device sits in when OnePlus reopens the gates.

What OnePlus Owners Should Do Right Now

For owners in India and the United States with OnePlus Nord or recent flagship hardware, the safest path is to delay the next update notification until OnePlus posts a clean replacement build. The company has not given a timeline, but past pauses of this type have resolved within one to three weeks.

Owners who have already installed 16.0.5.XXX or 16.0.7.XXX and are experiencing restart symptoms should file a log through the OnePlus Community feedback channel rather than performing factory resets or flashing recovery images from third-party sources. Wiping the device complicates the engineering investigation and can void coverage if a hardware swap becomes necessary.

OnePlus 15 and OnePlus 13 owners in markets receiving the 16.1 release should treat that build as separate from the pause. So far, OnePlus has not flagged the same boot-loop signature on the 16.1 train, and the rollout is continuing.

Frequently Asked Questions

Which OxygenOS 16 Builds Did OnePlus Pause?

OnePlus paused OxygenOS 16.0.5.XXX and 16.0.7.XXX, the two incremental builds that were reaching Nord and recent flagship devices in India and the United States. OxygenOS 16.1 for the OnePlus 15 and OnePlus 13 series is on a separate build train and is rolling out normally.

Should I Install the Update if My Phone Has Not Received It Yet?

Hold off on 16.0.5.XXX and 16.0.7.XXX until OnePlus posts a verified replacement. The over-the-air system will not push the paused versions, so for unaffected users the practical risk is low. If your device is queued for OxygenOS 16.1, the rollout is unaffected.

Will My OnePlus Phone Be Permanently Bricked if I Already Installed It?

No. Reports describe boot loops and abnormal restarts rather than unrecoverable hardware failure. Users with affected devices have been advised to contact OnePlus support through the community forum or an authorized service center for guided recovery instead of attempting third-party flashes.

How Do I Check Which OxygenOS Version Is on My Phone?

Open Settings, scroll to About device, and tap Version. The full build string appears under OxygenOS version. If you see 16.0.5 or 16.0.7 followed by additional digits, you are on one of the paused builds.

When Will OnePlus Resume the Rollout?

OnePlus has not given a date. The company said the rollout will resume only after the build passes additional stability and reliability checks. Previous OxygenOS pauses of similar scope have resolved within roughly one to three weeks.

Is OxygenOS 16.1 Affected by the Same Boot Bug?

There are no widespread reports linking OxygenOS 16.1 to the same restart symptoms. OnePlus is shipping 16.1 to the OnePlus 15 and OnePlus 13 series on a different build train and has not paused that release.

For OnePlus owners in India and the United States, the next over-the-air notification carries higher stakes than usual. If the replacement 16.0.x build lands clean within OnePlus’s usual one-to-three-week window, the apology buys back trust. If it slips or a second pause follows, the company’s QA promise stops counting as a promise.