TL;DR: Magisk modules can block a LineageOS update or cause a boot loop after it. Back up first. Disable every module, reboot, install the update with LineageOS Updater, then confirm a clean boot. Re-enable modules one at a time. If boot fails, use Android safe mode or Magisk’s module removal command.
By the PrivacyPortal team
Last updated August 2026
A LineageOS update failed message does not always mean the ROM package is faulty. Modules can add system overlays, alter properties, change SELinux rules, run boot scripts or inject code through Zygisk. Those changes may clash with a new build. The safest Magisk LineageOS update process is to disable all modules and reboot before using the built-in Updater. Back up your files first. Bootloader unlocking wipes user data, while later repair work can also cause data loss.
A LineageOS phone displaying its update screen before all root modules are disabled.
Why Magisk modules can break LineageOS updates
Magisk provides systemless root. It changes the boot environment and mounts modifications without directly rewriting the Android system partition. That makes changes easier to reverse, but it does not make every module safe across updates.
A module may have been built for an older Android release, kernel or security patch. It can still install without an error. The fault may only appear when Android starts the module’s boot scripts or loads its Zygisk code.
Common causes include:
- Outdated system files mounted over newer LineageOS files.
- SELinux rules that no longer match the updated policy.
- Scripts which expect a service, path or property that has changed.
- Zygisk modules which crash an app process or Android’s Zygote process.
- Performance modules that write unsupported kernel settings.
- Several modules trying to change the same file or property.
Official Magisk v30.7 was the current stable release on 16 August 2026.
Work out which stage is failing
The timing of a failure gives useful clues. It also helps you avoid a needless clean flash LineageOS procedure.
| Failure point | Likely cause | First action |
|---|---|---|
| Download will not start | Network, storage or Updater state | Check free space and download again |
| Package verification fails | Damaged or wrong package | Remove the download and use the built-in Updater |
| Installation stops | Recovery, partition or firmware issue | Record the error before changing anything |
| Phone loops at the boot animation | Module, boot image or data issue | Enter safe mode and disable modules |
| Android boots but apps crash | Zygisk or framework module conflict | Disable injection modules first |
| Root has disappeared | The new slot has an unpatched boot image | Confirm the correct Magisk install path for the device |
A missing root prompt after an update is not proof of a bad ROM. On an A/B device, the update may have switched to an unpatched slot.
How to update LineageOS with Magisk safely
Use this numbered process on your own device while Android still boots normally.
- Back up photos, messages, authenticator recovery codes and any files that exist only on the phone.
- Record the device model, LineageOS build, active Magisk version and every installed module.
- Open Magisk v30.7 and check that the app can still manage root. Do not update Magisk and LineageOS in the same session.
- Open the Modules page and switch off every module. This includes Zygisk, framework, audio, performance and app-hiding modules.
- Reboot the phone. A module is not safely disabled until Android has completed this reboot.
- Check that the phone works without modules. Fix any existing crash or storage problem before updating.
- Open LineageOS Updater, download the correct offered build and let its verification finish.
- Install the update. Follow the device-specific update guidance if the Updater shows extra instructions.
- Reboot into the new build and test calls, mobile data, Wi-Fi, camera and storage before enabling any module.
- Enable one module, reboot and test again. Repeat until every required module has been checked.
Prerequisites before starting
Charge the battery to at least 60%. Keep a reliable USB cable and another computer nearby. Make sure that computer can recognise the phone through Android Debug Bridge, usually called ADB.
Download only files intended for the exact device and current Android base. The “Modules, apps & files to try” section supplied with this guide points to the named tools and tested sources. Do not substitute a similarly named package from a file mirror or chat attachment.
Read the official LineageOS update guides. Device-specific firmware, recovery and major-version rules take priority over generic advice.
How to verify the result
Open Settings and confirm the expected LineageOS build number and Android security patch date. Then reboot once more with all modules still disabled.
Check for unusual heat, repeated crashes and missing hardware. Inspect the Magisk Modules page for warnings. Only start module testing after two clean boots.
The new LineageOS build number being checked before any root module is restored.
What to do when the Updater reports failure
Do not keep pressing install after the same error. Capture the exact wording and note the percentage where it stopped. Different stages have different causes.
Check these points in order:
- Confirm every module was disabled before a full reboot.
- Check that internal storage has several gigabytes of free space.
- Remove a partial download and fetch the package again through Updater.
- Confirm the build belongs to the exact device codename.
- Check whether the LineageOS update crosses a major Android version.
- Read the device update page for required firmware or recovery changes.
Do not bypass signature checks or flash a package for a related model. Similar product names can still use different partitions, firmware or cameras.
LineageOS update requirements are device-specific; its official update guide should be checked before a major version change.
Recover from a boot loop after updating
Try Android safe mode first
Magisk detects Android safe mode and disables its modules. The button timing differs by phone. It often involves holding volume down while the boot animation appears.
If safe mode succeeds, open Magisk and confirm that all modules are disabled. Reboot normally and test the clean system. Remove the suspected module before trying it again.
Safe mode is not the bootloader or LineageOS recovery. A screen showing fastboot commands or recovery options means Android safe mode has not started.
Use ADB only when the phone accepts commands
If ADB becomes available during boot, an experienced user can run adb shell magisk --remove-modules. This removes all installed modules rather than merely disabling them. Treat it as a recovery action.
ADB must already be authorised for that computer in many states. Do not assume a new computer can connect to a locked phone. Recovery environments also differ, so a command that works inside Android may not exist in recovery.
Restore the correct boot image when needed
A bad Magisk patch or wrong boot image needs a different repair. Obtain the boot or init_boot image from the exact installed build. Which partition is used depends on the device.
Flashing the wrong image can prevent booting. It may also affect over-the-air updates. Follow the official Magisk installation instructions for the device layout.
Understand A/B updates and root retention
Many modern phones have two operating-system slots. An update is written to the inactive slot while the current slot keeps running. The device changes slots at reboot.
The new slot may contain a stock boot image. Root can therefore disappear even though the LineageOS update worked. Module state and root installation are related, but they are not the same thing.
Some Magisk setups offer installation to the inactive slot after an over-the-air update. That option is device-dependent and easy to misuse. Do not select it unless the official instructions support the phone’s partition layout.
Never reboot midway through a slot-patching workflow. Verify that Updater has finished first. Keep the matching original boot image available for recovery.
An A/B partition diagram showing an update moving from the active slot to the newly written slot.
Re-enable Magisk modules without hiding the culprit
Enable modules in a controlled order. Start with simple modules that do not use Zygisk or alter framework files. Leave broad system, kernel and app-injection changes until last.
Use this decision framework:
- Enable one module only.
- Reboot after each change.
- Test the feature the module affects.
- Check unrelated basics such as calls, camera and Wi-Fi.
- Leave the phone running for several minutes.
- Remove the latest module if the fault returns.
Enabling five modules together may save four reboots. It can cost hours if the phone loops again. One-at-a-time testing gives a clear result.
Do not install a second module to mask the first module’s fault. Find a maintained release that states support for the current Android and Magisk versions.
Modules that deserve extra care
Zygisk modules inject code into Android app processes. A stale build can cause repeated app crashes even when the system reaches the home screen.
Framework overlays and user-interface modules may depend on exact SystemUI files. They are common suspects after a major LineageOS change. Kernel tuning modules may also write settings that a new kernel removed.
Root-hiding modules add another source of conflict. Built-in Zygisk should normally be disabled when an external Zygisk implementation requires that setup. Running two implementations can cause unpredictable results.
Shamiko, Zygisk Next, ReZygisk and Magisk variants do not form one universal stack. Compatibility changes between releases. Do not mix instructions written for official Magisk, Magisk Alpha, APatch or KernelSU.
Security, warranty and app compatibility risks
Root grants powerful access. A hostile module can read private data, start background services or make a phone unbootable. Inspect the project source and release history. Avoid anonymous archives and re-uploaded ZIP files.
An unlocked bootloader weakens the device’s protection against unauthorised operating-system changes. Android Verified Boot documentation explains how boot-time cryptographic checks protect the software chain.
Android Verified Boot establishes a chain of trust from protected hardware to verified Android partitions.
Unlocking the bootloader normally wipes the device. Rooting may affect warranty support, automatic updates and workplace security policies. It can also cause banking, wallet, streaming or game apps to reject the phone.
No module can be promised to defeat a specific app’s checks. Play Integrity and app-side detection can change without notice. Hiding root is not the same as restoring a locked, fully verified device.
When a clean LineageOS flash is justified
A clean flash erases user data and should not be the first response to a module conflict. Try a module-free boot and the correct boot image first.
A clean installation becomes reasonable when partitions are inconsistent, an unsupported upgrade path was used or the device cannot boot after verified repair steps. It may also help when old data from several Android versions causes faults.
Back up before unlocking, relocking, formatting or flashing. Relocking a bootloader with unsupported software can brick the phone. Never relock merely to test whether an app starts working.
For preparation help, read PrivacyPortal’s practical LineageOS installation guide and guide to rooting Android with Magisk. Device-specific LineageOS instructions still take priority.
Frequently asked questions
Should I disable Magisk modules before every LineageOS update?
Yes. Disable all modules and reboot before installing an update. This reduces avoidable conflicts and gives you a clean baseline. Re-enable each module separately after the new build has completed two clean boots.
Why did my LineageOS update succeed but the phone now boot loops?
The package may have installed correctly while a module failed on first boot. System overlays, boot scripts, SELinux changes and Zygisk injection are common causes. Try Android safe mode so Magisk disables modules.
Will disabling modules remove root?
No. Disabling modules normally leaves Magisk root installed. An A/B update can still replace the patched boot environment on the new slot, which may remove root for a separate reason.
Can I update Magisk and LineageOS at the same time?
Avoid changing both at once. Update LineageOS with modules disabled, verify the result, then assess the Magisk update. Separate changes make faults much easier to trace.
Can I keep Zygisk enabled during an update?
The safer course is to disable Zygisk modules with all other modules. Zygisk itself is less likely to alter package installation, but injected modules can break the first boot or app processes afterward.
Does a LineageOS update restore Play Integrity?
Not reliably. Integrity results depend on the bootloader, software state, device certification and changing server-side checks. An update may improve, worsen or leave the result unchanged. No guide can promise support from a bank or other specific app.
What is the fastest way to find a bad module?
Start with every module disabled. Enable one module, reboot and test. The latest enabled module is the main suspect when the fault returns. Zygisk, framework overlay and kernel tuning modules deserve early attention.
Are KernelSU or APatch modules interchangeable with Magisk modules?
No. The systems have different root and module models. Some packages support more than one manager, but that support must be stated by the developer. Never assume a Magisk ZIP is safe for APatch, KernelSU or one of its forks.
