Levelupvillage.info - Install OTA Updates on Rooted Android Devices with Magisk
Step 1: Disable Automatic OTA Updates Step 1: Disable Automatic OTA Updates Follow the steps below to disable Automatic System Updates in Android: Go to the Settings. Look for and select the About phone menu. Scroll down to the bottom and find the Build number section. Note: Please note that this setting can be buried even further in some Android devices. For example, in Samsung Galaxy devices, you should check here: Settings > About phone > Software information. Next, continuously tap on the ‘Build number’ section until you see some sort of toast message like ‘You are now a developer’. ‘Developer options’ is now enabled. After that, go to Settings > System > Developer options. Scroll down and turn off the Automatic system updates toggle.Step 2: Restore Stock Boot Image Step 2: Restore Stock Boot Image Next up, you need to restore stock boot images on your Android device. It is fairly simple – follow the below steps: Open the ‘Magisk Manager’ app. Tap on the UNINSTALL button. Select the RESTORE IMAGES option. Wait until you see the “Restoration done!” message on the screen. DO NOT REBOOT YOUR DEVICE AFTER THIS STEP; DOING SO WILL REMOVE MAGISK FROM YOUR PHONE. Go to the next step.Step 3: Install the OTA Update Step 3: Install the OTA Update Now you have stock boot image restored, you are good to install the OTA update on your rooted Android device. Go to the device Settings > System > System update Tap on the ‘Download and Install’ button. Wait for the installation process to complete. DO NOT REBOOT YOUR DEVICE AFTER THIS STEP; DOING SO WILL REMOVE MAGISK FROM YOUR PHONE. Go to the next step.Step 4: Retain TWRP Recovery after OTA Installation [Optional] Step 4: Retain TWRP Recovery after OTA Installation [Optional] This step is completely optional and only needs to be followed if you have rooted your Android device by flashing Magisk zip via TWRP recovery. In such a case, TWRP will be removed after you install the OTA update using the instructions below. In order to preserve TWRP after updating, download and install the ‘TWRP A/B Retention Script‘. Didn’t install via TWRP? No problem; move along to the next step! For this, you will need to download and install “TWRP A/B Retention Script” () from within Magisk Manager. To do so, follow the steps below: Open the ‘Magisk Manager‘ app. Tap on the menu on the top-left corner. Select ‘Downloads’. Next, search for ‘TWRP A/B Retention Script‘. Tap on the download icon and select the Install option. The Magisk Module (which is a small script, in this case) will now be installed on your phone. On to the next step!Step 5: Preserve Magisk Root after OTA Installation Step 5: Preserve Magisk Root after OTA Installation The last step to install Magisk to the other inactive slot. This is to make sure that you still have root even after you reboot your device after installing the OTA update. Open Magisk Manager. Tap on the INSTALL button and then again select the ‘INSTALL‘ option. Select ‘Install to Inactive Slot (After OTA)‘ when prompted to choose the installation method. Next, tap on ‘YES‘ to confirm. Magisk will now be installed on the inactive slot. Once the installation completes, tap on the ‘Reboot‘ button. Magisk Manager will reboot your Android device to the inactive slot where the OTA update was installed. Phew, that was a lengthy process and it is finally over. Now you should have root with Magisk on your Android device even after installing the OTA update. Questions? That’s why we have the comments section. Hit me up! Tags9 thoughts on “Install OTA Updates on Rooted Android Devices with Magisk” 9 thoughts on “Install OTA Updates on Rooted Android Devices with Magisk” 1.Is this process eligible for Samsung Galaxy M30 ? 2. Does it wipe my data & Settings ? Hi, thanks for the tutorial. In step 3 when I install the update I get the following message: “root is detected. system will begin downloading the full upgrade package.to ensure your data integrity, please perform a backup. your device will be unrooted once the upgrade is complete” What should I do? I am using a OnePlus 8T by the way. Is this going to remove all the settings and changes to apps that were installed/uninstalled since customizing the device? There is no explicit warning in this article. Does your android require A/B partition to perform this Do we have to perform this procedure each time an OTA is to be installed? or does it needed to be done once and then subsequent OTAs will be installed like normally? Yes. It’s not an one time thing. Thanks for your guide. When I got to step 3 to check for updates, it still says my system is up to date. I’m on Android 11 on pixel 5a and Android 12 is released. Any ideas why I can’t get the update even after restoring stock boot image? Thanks How is it possible to avoid the automatic reboot? Installing the OTA update always leads to a reboot.
Keywords on this domain
Search Results related to levelupvillage.info on Search Engine
Alexa Rank
GLOBAL RANK
Alexa Reach
Page length
Alexa Rank Country N/A
Daily Unique Visitors
Monthly Unique Visitors
Vistor via Country
United States
2,552
Indonesia
1,996
Taiwan
649
United Kingdom
576
Brazil
521
Nigeria
456
Egypt
383
Hong Kong
361
Canada
361
Australia
315
Philippines
225
India
219
Malaysia
216
Spain
179
Germany
174
Mexico
167
France
157
Italy
146
Turkey
134
Iraq
122
Thailand
119
Netherlands
115
Israel
113
Cambodia
94
Algeria
73
Ireland
66
Romania
63
Jordan
58
Poland
56
Ghana
54
Argentina
51
South Africa
47
Belgium
42
Czechia
38
Ukraine
36
Japan
36
Morocco
35
South Korea
33
Lebanon
32
Saudi Arabia
31
Austria
30
Hungary
29
Sweden
27
Singapore
26
Pakistan
25
Bangladesh
24
Denmark
23
Greece
21
Alexa Traffic Graph
SEOquake Zone
| Title | Tips | ||
| Description | Tips | ||
| Keywords | Tips | ||
| Viewport | Tips | ||
| Icon | |||
| UTF-8 |
Mini site formation by Alexa Rank
DNS Record
| Host | Type | Class | TTL | Extra |
Hosting and Whois Zone
| Domain infomation | Domain not found.
>>> Last update of WHOIS database: 2025-04-18T19:22:42Z <<< Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. |
