From c07eac118c8ed4622a088397aa3f36d5afc4b511 Mon Sep 17 00:00:00 2001 From: Roshabor Date: Sat, 31 Jan 2026 13:48:16 -0500 Subject: [PATCH] Update ota.md Hi there, appreciate you and your work. Proposing a small change to the A/B device update instructions, based on your changes within the Magisk app which made those instructions outdated/ invalid. Specifically, after installing Magisk to the new slot, apparently Magisk then instructs to go back to the system update and hit restart now, instead of the prior instructions which remain on this website of rebooting within the Magisk app. I just did testing, and rebooting within the Magisk app does not result in slot switch, which must be why you noe instruct to go back to system update for the restart now. Just thought I'd update the instructions for anyone who might be confused. Thx! --- docs/ota.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ota.md b/docs/ota.md index 9965c33a7..c0c832e89 100644 --- a/docs/ota.md +++ b/docs/ota.md @@ -21,7 +21,7 @@ It is possible to have the OTA installed to the inactive slot and have the Magis

-- After installation is done, press the reboot button in the Magisk app. Under-the-hood, the Magisk app forces your device to switch to the updated slot, bypassing any possible post-OTA verifications. +- After installation is done, follow the final instructions at the end of the Magisk installation on how to reboot into the new slot, currently involving going back to the regular system update and hitting "restart now" (previous method of using reboot within Magisk App may not result in rebooting to new slot). Under-the-hood, the Magisk app tracks your device switch to the updated slot, bypassing any possible post-OTA verifications.