How to Install OTA Updates on a Rooted OnePlus: 6 Methods

Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.

Yes, a rooted OnePlus can often install an OxygenOS OTA without losing data or root. For a stock, A/B-slot phone rooted with Magisk, the safest route is to restore Magisk’s stock images, install the update, install Magisk to the updated inactive slot, and only then reboot. The order matters: rebooting before patching the new slot usually means the phone starts unrooted.

These steps are not universal across OnePlus models or OxygenOS versions. Direct changes to verified partitions, a custom recovery, a custom kernel, or a different firmware branch can change the procedure or make an OTA fail. Confirm your exact model, region, build, and device-specific instructions before using manual flashing commands.

#	Preview	Product	Price
1		OnePlus Open Dual SIM, 512GB + 16GB RAM, Voyager Black - Unlocked (Renewed)		Buy on Amazon

Before you update: check your setup

First identify what “rooted” means on your phone. Magisk installed systemlessly on otherwise stock OxygenOS is the best case. Magisk modules may still cause problems after an update, while direct changes to /system, /vendor, or other verified read-only partitions can prevent OTA verification. Magisk specifically warns that modifying read-only partitions can interfere with its documented OTA process (Magisk OTA guide).

• Back up important data. Include photos, messages, authenticator recovery information, and app data. An OTA is generally intended to preserve data, but a failed update or firmware recovery may erase it.
• Record your exact model, region, current OxygenOS build, Magisk version, and active slot. A package or image for a similar-looking model may still be wrong.
• Disable automatic system updates in Developer options if available, so an update does not install and reboot before you can patch the new slot.
• Remove or disable risky modules, custom kernels, overlays, and boot scripts before updating. Re-enable modules one at a time only after confirming the new build boots reliably.
• Charge the phone and make sure there is enough free storage for the update. For computer-based methods, have a reliable cable, working ADB/Fastboot Platform-Tools, and any required USB driver.
• Keep a matching stock image or firmware package if possible. Use Magisk only from its official project repository.

If you are running a custom ROM rather than stock OxygenOS, these OxygenOS OTA instructions generally do not apply. Do not relock the bootloader just because an update completed; continued Magisk use normally requires an unlocked bootloader.

#1 Best Overall

OnePlus Open Dual SIM, 512GB + 16GB RAM, Voyager Black - Unlocked (Renewed)

Buy on Amazon

Why A/B slots matter

Many modern Android phones use A/B slots. The phone boots one slot while an update is written to the other; once the update is ready, the bootloader switches to the updated slot. The previous slot can provide a fallback if the new one does not boot. The exact implementation varies by device, so do not assume every OnePlus model exposes identical slot names or behavior. See Android’s explanations of A/B updates and bootloader slot updates.

Before:  Running slot A + Magisk
Update:  OxygenOS writes updated system to inactive slot B
Before reboot: Magisk patches slot B
After:   Boot slot B + updated OxygenOS + Magisk

Magisk’s A/B OTA procedure depends on installing Magisk to the updated inactive slot before the first reboot. Its menu wording can vary by release; look for the inactive-slot or “after OTA” option rather than relying on one exact label.

Method 1: Normal OTA, then install Magisk to the inactive slot

Best for: a stock OxygenOS A/B phone with Magisk root and no direct modifications to verified partitions. This is the preferred, least-invasive route when the updater accepts the update.

1. Open Magisk and choose Uninstall → Restore Images. This restores the stock images Magisk backed up. Do not reboot.
2. Open Settings → System updates (the exact path may vary) and download and install the OTA normally.
3. Wait until the updater finishes both installation and optimization. When it offers to restart, do not select Restart now.
4. Return to Magisk and choose Install, then the option to install to the inactive slot—often labelled Install to Inactive Slot or Install to Inactive Slot (After OTA).
5. Wait for Magisk to finish. Return to the system updater and use its restart control to boot into the updated slot.
6. After boot, check the OxygenOS build and confirm Magisk reports an installed version and root access works.

This method can preserve root, but it is not a guarantee: it depends on the device’s slot implementation, Magisk compatibility, and a sufficiently stock verified-partition state. Magisk documents the restore-images, no-reboot, inactive-slot sequence in its OTA instructions.

Method 2: Local install with a full OTA ZIP

Best for: when the rollout has not reached your phone, you want to install a full package, or you have missed updates. Follow the same Magisk inactive-slot sequence as Method 1; only the way you provide the update package changes.

1. Get a full OTA ZIP that explicitly matches your exact model, region, and software branch. Verify its checksum when one is provided. A full package is often more suitable than an incremental package for rooted phones or larger jumps, but it cannot fix every modified-partition or firmware problem.
2. Copy the ZIP to internal storage. Do not use a rollback package, service firmware, recovery-only package, or incremental ZIP as if it were a full OTA.
3. Use Magisk’s Uninstall → Restore Images if its stock backup is available. Do not reboot.
4. Open Settings → System updates, then find Local install in the menu or updater controls. Select the package and let installation and optimization finish.
5. Do not reboot yet. In Magisk, install to the inactive slot, then restart from the system updater.

OnePlus documents a Local install flow in its OxygenOS 14 manual, but names and locations differ by release and region. If the option is missing, the updater may not recognize that package type, or your version may expose a different path. Oxygen Updater is a third-party app that can help locate OTA packages; it is not OnePlus support. Check the package details rather than assuming a download is correct (Google Play listing).

Full OTA versus incremental OTA

An incremental OTA updates a particular source build and normally expects the phone to match that base state. It is more sensitive to the exact starting build and modifications. A full OTA contains the target build’s broader set of files and is generally the more defensible choice if rooted, if you skipped updates, or if making a supported track change. Neither type is safe if it is for the wrong model or region, and a full package does not bypass all verification checks.

Method 3: Restore stock images, update, then root again

Best for: OTA verification failures, a missing inactive-slot option, or a root setup that is not clean enough to preserve root through the update. Root will be absent during the update, but this is often a clearer fallback than repeatedly retrying a failing OTA.

1. Back up data and remove or disable Magisk modules and custom kernels.
2. In Magisk, use Uninstall → Restore Images if the matching stock backup is present. If not, obtain the exact stock boot-related image from firmware matching your current build. Do not substitute an image from another build or device.
3. Install the matching OTA normally and reboot into the updated, unrooted system.
4. Obtain the correct boot-related image from the new firmware and patch it with Magisk on the phone. Magisk’s installation guide explains image patching and stresses using an image that matches the device and firmware (Magisk installation guide).
5. Use the device-specific instructions to flash the patched image, then reboot and complete any Magisk setup prompt.

This route may require a computer for manual flashing. Which image and partition to use—boot, init_boot, or recovery—depends on the phone’s boot architecture and how Magisk was installed. Do not flash all of them.

Method 4: Patch the new image and flash it with Fastboot

Best for: someone comfortable with a computer who needs manual control, such as when root was lost after an update or the normal inactive-slot path is unavailable. This is not the first choice when Method 1 works.

1. Download firmware for the exact phone, region, and target build, then extract the correct boot.img, init_boot.img, or recovery.img.
2. Copy that image to the phone. In Magisk, choose Install → Select and Patch a File, select the image, and wait for the patched file to be created.
3. Copy the resulting patched image to the computer. With USB debugging and the appropriate tools configured, a typical workflow may include:

adb pull /sdcard/Download/magisk_patched_[random_strings].img
adb reboot bootloader
fastboot getvar current-slot
# Flash only the correct image to the correct partition, as specified for your device.
fastboot reboot

Magisk’s documentation gives generic fastboot examples such as fastboot flash boot magisk_patched.img, but this is not a universal OnePlus command. Some devices use another image or partition, and A/B devices may require careful slot targeting. Do not copy a fixed boot_a or boot_b command without checking device-specific instructions and the slot that will boot. The Magisk installation guide explains the image-patching approach; Android documents bootloader slot handling here. Never flash an image shared by someone else just because the model name looks the same.

Method 5: Use a custom recovery only when its guide supports it

Best for: a device and software combination whose recovery and firmware documentation explicitly supports installing that package through recovery. This is a legacy or specialist path, not the general recommendation.

Before flashing, confirm that the recovery is built for the exact model and OxygenOS/Android generation, and that its maintainer explicitly supports the update package. An update may replace recovery-related images, and a recovery from another generation can fail to boot or disrupt installation. Magisk now describes custom-recovery installation as deprecated and generally recommends patching the appropriate image instead (Magisk installation guide).

If the device-specific guide calls for this route, follow its exact package and recovery steps, then reinstall recovery or Magisk only as instructed. Do not wipe data or caches by habit; wipe only what the relevant guide requires. A rooted OTA does not necessarily preserve TWRP or another custom recovery.

Method 6: Recover with full stock firmware, then update and reroot

Best for: a boot loop, corrupted slot, repeatedly failed OTA, or an incompatible firmware state. This is a recovery route, not a routine update method. Some service or rollback packages can erase data, and the correct recovery process varies substantially by OnePlus model and region.

1. If the phone still boots, back up data and record the exact model and build. If it does not, avoid guessing at firmware or partition commands.
2. Use the OnePlus support channel or a reputable, model-specific guide to identify the correct stock firmware and recovery process. Start at OnePlus support; confirm whether the package is full firmware, rollback firmware, or a service package and whether it wipes data.
3. Restore stock firmware using only the method documented for that device. Do not relock the bootloader as part of an improvised recovery.
4. Once stock OxygenOS boots, install the intended update if needed, then patch and flash the matching new image using the device-specific Magisk procedure.
5. Reinstall modules individually after confirming the system is stable.

Troubleshooting by symptom

The OTA says installation failed

Common causes include an incremental package for the wrong base build, a wrong-region or wrong-model package, modified verified partitions, a custom recovery or kernel, or a damaged stock-image backup. Stop repeated attempts with the same ZIP. If the phone still boots, disable modules, restore matching stock images, and try a verified full OTA for the correct branch. If the phone cannot boot, inspect the slot before changing it.

For a computer-connected device, fastboot getvar current-slot can report the current slot on supported devices. Commands such as fastboot set_active a or fastboot set_active b are not interchangeable guesses: use one only when you have identified the known-good slot and verified that your device supports the command. Android’s bootloader update documentation describes slot metadata and switching.

The phone boots, but root is gone

The update may have booted the new slot with its stock boot image because Magisk was not installed there before reboot. If the old rooted slot is still bootable, use device-specific instructions to return to it; otherwise, patch the matching new image and flash it to the correct target. Reinstall the Magisk app only from the official project source.

The phone boot-loops after updating

A module, custom kernel, wrong patched image, or wrong slot can prevent startup. Allow the normal first boot to complete before intervening, but do not repeatedly force-restart. If supported, use safe mode or recovery options to disable modules; otherwise, follow the device-specific method to remove the offending module or restore the matching stock image. Returning to a known-good slot may help only if that slot remains bootable. Treat a factory reset or full firmware restore as a later step, after considering data backup and the risk of erasure.

The update removed TWRP or another custom recovery

This can be expected: the update may replace boot- or recovery-related images. Root and custom recovery are separate goals. Reinstall recovery only if a current guide for your exact model and software supports it.

Local install is missing or will not accept the ZIP

Menu placement varies by OxygenOS version and region. The package may be incremental, a rollback or service file, for another model or region, or otherwise not recognized by the updater. Check the package type and build carefully; do not rename or force a file to make it appear valid.

Banking apps or Play Integrity checks stop working

A successful update does not guarantee that banking, payment, or Play Integrity-dependent apps will accept a rooted device. Compatibility can change independently of whether OxygenOS and Magisk boot correctly. Verify root and ordinary phone functions first; do not assume a root-hiding workaround will remain effective.

Quick Recap

Bestseller No. 1

OnePlus Open Dual SIM, 512GB + 16GB RAM, Voyager Black - Unlocked (Renewed)

Verify the update before restoring modules

• Confirm the new OxygenOS version and build number in Settings.
• Confirm Magisk is installed and root access works, if preserving root was the goal.
• Check whether TWRP or another custom recovery remains; do not assume it survived.
• Test calls, mobile data, Wi-Fi, camera, encryption, and biometric unlock.
• Re-enable Magisk modules one at a time, checking stability after each.
• Check any critical apps separately; their root or integrity policies can change.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.