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.
List of domain same IP 174.143.104.95
GLOBAL RANK
Alexa Reach
Page length
Alexa Rank Country N/A
Daily Unique Visitors
Monthly Unique Visitors
United States
2,612
Indonesia
2,043
Taiwan
664
United Kingdom
590
Brazil
534
Nigeria
467
Egypt
392
Hong Kong
370
Canada
370
Australia
322
Philippines
231
India
225
Malaysia
221
Spain
183
Germany
178
Mexico
171
France
161
Italy
149
Turkey
137
Iraq
125
Thailand
122
Netherlands
117
Israel
116
Cambodia
96
Algeria
74
Ireland
67
Romania
65
Jordan
60
Poland
57
Ghana
55
Argentina
53
South Africa
48
Belgium
43
Czechia
39
Ukraine
37
Japan
37
Morocco
35
South Korea
34
Lebanon
33
Saudi Arabia
32
Austria
31
Hungary
29
Sweden
28
Singapore
27
Pakistan
26
Bangladesh
24
Denmark
23
Greece
22
Title | Tips | ||
Description | Tips | ||
Keywords | Tips | ||
Viewport | Tips | ||
Icon | |||
UTF-8 |
Host | Type | Class | TTL | Extra |
usawaterpolo.org | TXT | IN | 21600 | Txt: v=spf1 include:sendgrid.net include:_spf.google.com include:spf.mandrillapp.com ip4:64.30.227.98/31 ip4:64.30.227.100/30 ip4:208.42.236.139 ip4:208.42.236.152 ip4:208.42.236.134 ip4:208.42.236.130 ip4:208.42.236.148 -all Entries_0: v=spf1 include:sendgrid.net include:_spf.google.com include:spf.mandrillapp.com ip4:64.30.227.98/31 ip4:64.30.227.100/30 ip4:208.42.236.139 ip4:208.42.236.152 ip4:208.42.236.134 ip4:208.42.236.130 ip4:208.42.236.148 -all |
usawaterpolo.org | TXT | IN | 21600 | Txt: google-site-verification=u0EKytmo3AajTrQRTcr73jC5pMUufTh64NhWw4BG93c Entries_0: google-site-verification=u0EKytmo3AajTrQRTcr73jC5pMUufTh64NhWw4BG93c |
usawaterpolo.org | TXT | IN | 21600 | Txt: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB; Entries_0: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB; |
usawaterpolo.org | MX | IN | 21600 | Pri: 20 Target: ASPMX2.GOOGLEMAIL.COM |
usawaterpolo.org | MX | IN | 21600 | Pri: 20 Target: ALT2.ASPMX.L.GOOGLE.COM |
usawaterpolo.org | MX | IN | 21600 | Pri: 10 Target: ALT1.ASPMX.L.GOOGLE.COM |
usawaterpolo.org | MX | IN | 21600 | Pri: 30 Target: ASPMX4.GOOGLEMAIL.COM |
usawaterpolo.org | MX | IN | 21600 | Pri: 30 Target: ASPMX5.GOOGLEMAIL.COM |
usawaterpolo.org | MX | IN | 21600 | Pri: 10 Target: ASPMX.L.GOOGLE.COM |
usawaterpolo.org | MX | IN | 21600 | Pri: 30 Target: ASPMX3.GOOGLEMAIL.COM |
usawaterpolo.org | NS | IN | 21600 | Target: ns.rackspace.COM |
usawaterpolo.org | NS | IN | 21600 | Target: ns2.rackspace.COM |
usawaterpolo.org | A | IN | 21600 | Ip: 174.143.104.95 |
usawaterpolo.org | SOA | IN | 300 | Mname: ns.rackspace.COM Rname: hostmaster.rackspace.COM Serial: 1744638640 Refresh: 3600 Retry: 300 Expire: 1814400 Minimum-ttl: 300 |
IP | 174.143.104.95 |
Domain infomation | Domain Name: usawaterpolo.org
Registry Domain ID: 59d7f5956ccb4290839fa72e04ab48e0-LROR Registrar WHOIS Server: http://whois.godaddy.com Registrar URL: http://www.whois.godaddy.com Updated Date: 2024-08-31T03:19:23Z Creation Date: 2004-07-17T03:19:21Z Registry Expiry Date: 2027-07-17T03:19:21Z Registrar: GoDaddy.com, LLC Registrar IANA ID: 146 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.6028177308 Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited Registry Registrant ID: REDACTED Registrant Name: REDACTED Registrant Organization: Domains By Proxy, LLC Registrant Street: REDACTED Registrant City: REDACTED Registrant State/Province: Arizona Registrant Postal Code: REDACTED Registrant Country: US Registrant Phone: REDACTED Registrant Phone Ext: REDACTED Registrant Fax: REDACTED Registrant Fax Ext: REDACTED Registrant Email: REDACTED Registry Admin ID: REDACTED Admin Name: REDACTED Admin Organization: REDACTED Admin Street: REDACTED Admin City: REDACTED Admin State/Province: REDACTED Admin Postal Code: REDACTED Admin Country: REDACTED Admin Phone: REDACTED Admin Phone Ext: REDACTED Admin Fax: REDACTED Admin Fax Ext: REDACTED Admin Email: REDACTED Registry Tech ID: REDACTED Tech Name: REDACTED Tech Organization: REDACTED Tech Street: REDACTED Tech City: REDACTED Tech State/Province: REDACTED Tech Postal Code: REDACTED Tech Country: REDACTED Tech Phone: REDACTED Tech Phone Ext: REDACTED Tech Fax: REDACTED Tech Fax Ext: REDACTED Tech Email: REDACTED Name Server: ns.rackspace.com Name Server: ns2.rackspace.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2025-04-17T22:33:03Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. 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. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. 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. |