TL;DR: A OnePlus bootloop after an update usually means the custom kernel no longer matches OxygenOS. Check the active A/B slot first. Then restore stock boot-chain images from the exact model, region and build. Do not wipe data as a first step. Back up anything still accessible before changing partitions.
By the PrivacyPortal team
Last updated August 2026
An OxygenOS update can replace parts of the kernel and boot chain. An older custom kernel may then load mismatched modules, device-tree data or vendor binaries. The safe response is to stop flashing random files. Record the model, region, OxygenOS build and active slot. If the bootloader is already unlocked, restore matching stock images. If it is locked, remember that unlocking normally wipes all user data. A factory reset rarely fixes an incompatible kernel.
What causes a OnePlus bootloop after an update?
A custom kernel must match more than the Android version. It also depends on the device tree, vendor modules and Kernel Module Interface. The KMI defines how a kernel communicates with loadable modules. An OTA may change any of these parts.
Common causes include:
- A kernel built for an older OxygenOS security patch.
- Modules compiled for a different KMI or kernel release.
- A boot image taken from another model, region or build.
- Flashing boot.img when the ramdisk belongs in init_boot.img.
- Mismatched vendor_boot, dtbo or device-tree data.
- Rollback metadata older than the installed security patch.
- A root module running code too early during startup.
An oxygenos update bootloop may also be unrelated to root. A failed OTA, damaged storage or faulty hardware can produce similar symptoms.
Image caption: The Android boot chain links the bootloader, kernel, ramdisk and vendor modules.
Diagnose a oneplus bootloop before flashing
Start with the last change. A loop that began directly after an OTA suggests a compatibility fault. A loop after installing a module points towards that module. Sudden loops without any change may indicate storage or hardware trouble.
Note where the failure occurs:
- Bootloader only: the selected slot or boot image may be invalid.
- OnePlus logo: suspect the kernel, ramdisk, device tree or verified boot.
- Boot animation: Android started, so a module or userspace service may be failing.
- Recovery loop: the slot may be unbootable or an OTA may remain incomplete.
Do not relock the bootloader while modified images remain installed. Verified Boot may reject them. Recovery can then become harder.
Check the active A/B slot
Most recent OnePlus devices use seamless A/B updates. Android runs from one slot while an OTA writes to the other. The phone then tries the updated slot after a reboot.
Android’s official A/B update design applies an update to the unused slot while the device continues running from the active slot.
In the bootloader, run fastboot getvar current-slot. Record whether it reports a or b. Some devices expose slot information through fastboot getvar all. Do not publish that full output because it may contain a serial number.
The official Android A/B update documentation explains slot switching and boot-success checks.
Failure patterns and the safest response
| Observed pattern | Likely cause | First response |
|---|---|---|
| Old slot boots, updated slot loops | OTA or custom-kernel mismatch | Use the working slot and obtain exact stock images |
| Both slots stop at the logo | Both boot chains were modified or damaged | Restore exact stock boot-chain images |
| Loop starts after a root module | Early-boot module conflict | Disable or remove modules from recovery |
| Fastboot works but recovery does not | Wrong vendor_boot, init_boot or recovery layout | Verify the device partition map |
| Image flashes but will not boot | Wrong build, KMI or rollback level | Stop and verify the complete build number |
| No fastboot, recovery or charge response | Possible hard brick or hardware fault | Seek model-specific professional recovery |
How to restore a compatible stock boot chain
This method is for your own OnePlus device with an already unlocked bootloader and working fastboot access.
- Back up first. Copy any accessible photos, files, app exports and recovery keys. Partition work can cause permanent data loss.
- Charge the phone above 50%. Use a reliable USB cable and a direct computer port.
- Install Android SDK Platform-Tools 36.0.0 or newer. Open a terminal inside its directory.
- Boot into the bootloader. Run fastboot devices and confirm that one device appears.
- Run fastboot getvar product and fastboot getvar current-slot. Save both results.
- Get the full OxygenOS package for the exact model, region and installed build. Do not substitute a similar OnePlus package.
- Extract the package and obtain its stock boot.img. Also obtain init_boot.img, vendor_boot.img and dtbo.img when that build contains them.
- Compare the package build with the installed OTA. Stop if the build number or regional branch differs.
- Flash only the required matching images to the affected slot. Use the partition names exposed by that device, then reboot to the bootloader.
- Start Android and allow several minutes for the first boot. Verify the build, mobile radio, Wi-Fi, camera and root state before changing anything else.
Prerequisites and files
You need a Windows, macOS or Linux computer with current platform tools. You also need the full matching OxygenOS package. A payload extractor may be required when images are stored inside payload.bin.
Look for Android SDK Platform-Tools, the correct OxygenOS package and a maintained payload extractor in the “Modules, apps & files to try” section. Verify checksums when the publisher provides them.
Do not unlock a locked bootloader just to follow this tutorial. OnePlus bootloader unlocking normally performs a factory reset. It may also affect warranty support, over-the-air updates and protected apps.
Choose the correct partitions
Partition layouts differ between OnePlus generations. Never assume that another model’s command list applies. Modern devices may separate the kernel, generic ramdisk and vendor ramdisk across boot, init_boot and vendor_boot.
Android 13 introduced init_boot for devices launching with Android 13, separating the generic ramdisk from the boot partition.
The Android generic boot partition documentation describes boot, init_boot and vendor_boot layouts.
Use fastboot getvar has-slot:boot to check whether boot is slotted. Repeat that check for init_boot, vendor_boot and dtbo before adding an _a or _b suffix. Some logical partitions require fastbootd. Bootloader fastboot and fastbootd are different modes.
Image caption: Fastboot output identifies the active slot and available boot partitions.
Verify the repair before rooting again
A successful repair should reach the lock screen without repeated restarts. Test calls, mobile data, Wi-Fi, Bluetooth, camera and fingerprint unlock. Check the complete OxygenOS build in Settings.
Keep the phone stock for at least one clean reboot. This separates a boot-chain repair from later root changes. If the stock build still loops, capture bootloader errors or recovery logs. Reflashing a custom kernel will only hide the original fault.
When root is restored, banking and media apps may still reject the device. Play Integrity results can change without notice. No module can be promised to defeat a specific app’s checks.
OnePlus custom kernel bootloop checks
A oneplus custom kernel bootloop often comes from a kernel that was safe on the previous build. The filename alone is not proof of support. Read the release notes and confirm the exact device codename, OxygenOS branch and security patch.
Check these items before reinstalling:
- The kernel targets the phone’s exact codename.
- The release explicitly supports the installed OxygenOS build.
- Its KMI matches the updated vendor modules.
- The package supports the phone’s boot-image layout.
- Its device-tree changes match the current firmware.
- The installer does not restore an old boot or vendor_boot image.
OnePlus kernel compatibility is build-specific. “Android 16 compatible” is too broad. Two Android 16 builds can ship different vendor modules or rollback levels.
Why vendor binaries can stop boot
A vendor binary bootloop occurs when the kernel and vendor-side components no longer agree. Wi-Fi, display, camera and radio drivers may load as kernel modules. An OTA can replace those modules while a custom kernel remains old.
Android may reject a module because its symbol versions or KMI do not match. The phone can then restart, freeze or lose key hardware. Copying one module from another release is not a sound fix. Restore the complete matching set instead.
Android’s Generic Kernel Image model keeps a stable KMI so vendor modules can work with a compatible generic kernel, but the required KMI generation must still match.
See the official Generic Kernel Image guide for the relationship between GKI kernels and vendor modules.
Root managers and post-update risk
Magisk patches a boot-chain image and provides a module system. KernelSU, KernelSU Next and SukiSU Ultra place root support in the kernel. APatch also depends on kernel-level patching. These methods are not interchangeable.
A Magisk-patched boot image is not a KernelSU kernel. Likewise, a KernelSU image from another KMI can trigger a oneplus bootloop. GKI support alone does not prove that an image suits your phone.
Disable optional modules before taking an OTA. Restore stock images when the root manager’s official update path requires it. Keep a copy of the current stock images and the last known working set.
Our practical Magisk rooting guide explains boot-image patching and module risks. The Android bootloader unlocking guide covers wipes, backups and verified boot.
Recovery mistakes that make bootloops worse
- Factory resetting first: this deletes data but does not repair a mismatched kernel.
- Flashing both slots blindly: this can destroy the last working boot path.
- Using a global image on a regional build: similar names do not ensure matching firmware.
- Downgrading one partition: rollback rules may reject older boot-chain metadata.
- Relocking too soon: a modified partition may fail Verified Boot after relocking.
- Mixing recovery guides: OnePlus partition layouts vary by model and release.
- Trusting a successful flash: fastboot confirms the write, not image compatibility.
In practice, the safest repair changes one known variable at a time. Keep notes of every image, slot and command. Stop when the device behaves differently.
Image caption: A recovery worksheet records each slot, firmware build and flashed image.
When to stop and seek specialist help
Stop if fastboot reports an unknown product, an invalid sparse image or an anti-rollback error. Also stop if the package source cannot be verified. Repeated attempts with uncertain images raise the risk of losing both bootable slots.
Professional help is sensible when the device cannot enter fastboot or recovery. Qualcomm emergency download recovery may need authorised tools, signed loaders or model-specific access. Random “firehose” files can damage partition data or expose the computer to malware.
If you prefer a supported privacy-first device without doing the flashing yourself, PrivacyPortal offers de-Googled privacy phones. That option is most relevant when reliability matters more than maintaining a custom kernel.
Frequently asked questions
Will a factory reset fix a OnePlus bootloop?
Usually not when the kernel or boot chain is incompatible. A reset removes user data. It does not replace boot.img, init_boot.img, vendor_boot.img or dtbo.img. Restore the exact stock images first when fastboot access and an unlocked bootloader are available.
Can I switch to the other slot without wiping data?
Switching slots does not itself format user data. However, the older slot may use incompatible encryption or database formats. It may also contain an older security patch. Record the current slot and confirm the other slot was previously working before switching.
Why did the OTA break a previously stable kernel?
The OTA may have changed the KMI, vendor modules, device tree or boot-image layout. A custom kernel built for the old release can no longer communicate with the new vendor components. Restore stock first, then wait for explicit kernel support.
Can I flash a boot image from another OnePlus region?
Do not assume it is safe. Regional releases may differ in firmware, rollback metadata and vendor components. Use images from the exact device model, region and OxygenOS build.
Will restoring stock boot remove root?
Usually, yes. Magisk root is lost when its patched image is replaced. KernelSU or APatch may also disappear when the stock kernel returns. A clean stock boot is useful because it proves whether root caused the fault.
Can root hiding guarantee that banking apps work?
No. Apps can use Play Integrity, hardware-backed signals and their own checks. Detection methods change often. Root, an unlocked bootloader and custom firmware may stop banking, wallet, work-profile or streaming apps from working.
PrivacyPortal sells ready-to-use, de-Googled GrapheneOS Pixels — hardened, kept updated, and shipped with our encrypted Graphite messenger. Browse privacy phones →
