Xiaomi HyperOS: How to remove the update and disable autoboot

The transition to the new HyperOS shell has been a landmark event for owners of Xiaomi, Redmi and POCO devices, but not all users are ready to immediately accept changes in the interface and logic of work. It often happens that the system starts downloading a package of updates on its own, taking up valuable space in memory or causing instability after installation.

Unlike previous versions of MIUI, where there were simple switches, HyperOS controls have become stricter, but the control remains. You will need to perform a series of sequential actions in hidden menus and system settings to ensure that you do not load background load. It is important to understand that completely removing update components can disrupt some system services, so we will consider safe locking methods.

This guide covers all the current methods, from standard disabling notifications to deeper blocking of system services through the engineering menu, you will learn to distinguish between types of updates, understand which processes you can stop and which you should not touch, and this will allow you to maintain control over your device without the risk of turning your smartphone into a brick.

Analysis of Update Types in HyperOS

Before embarking on drastic locking actions, it is important to clearly understand what exactly we are fighting.The HyperOS system divides updates into several categories, and locking one type doesn't always mean protecting against the other. Users often confuse security updates, Google Play patches and major Android versions, leading to confusion when setting up.

The main data stream is through the OTA (Over-The-Air) service, which checks the manufacturer's servers for new builds. This channel is most often annoying users with constant notifications. However, there are also background downloads of Google components and system application updates that can initiate re-activation of the main update module.

It’s worth noting that in some firmware regions (especially Global and EEA), update verification mechanisms are built deeper than in the Chinese versions. In HyperOS, a critical component is System Update, which has increased rights and can restart itself after a reset, so simply cleaning the cache is often not enough for a long-term result.

Understanding the update architecture will help you choose the right strategy, and if your goal is to simply remove the red dot on the settings icon, just one set of actions is enough, and if you want to completely ban modifications to the system partition, you need a comprehensive approach using multiple methods at once.

Basic settings and disabling notifications

The easiest and safest level of protection is to adjust the visibility of notifications, which won’t stop files from loading completely in the background, but it will save you from constant visual noise, and first you need to find the appropriate section in the settings menu, which HyperOS has been slightly redesigned compared to MIUI 14.

Go to Settings → About the phone and click on the system version logo. In the window that opens, look for the three-dot button in the top right corner. This is where the key switches are hidden. You need to select Update Options (or Update Settings).

💡

If the “Update Options” item is hidden, try quickly tapping 7-10 times on the current firmware version to activate the hidden update developer menu.

In the menu that opens, you'll see the "Download Updates Automatically" switch, which needs to be put inactive, and the "Notify Updates Available" option is also recommended to be turned off, which will create the first barrier that the system will try to bypass, but for most users, this is enough.

You should also check the notification settings for the System Update app itself. Go to Settings → Notifications and Status bar → Notification management, look in the System Update list, and disable all types of notifications, including audible and pop-up notifications, which will hide any reminders, even if the update process is already running.

Forced shutdown and cleanup of service data

If standard settings do not produce the desired effect or the switches return to their original position, a more aggressive method is to completely stop the process and clean up the accumulated data, which resets the state of service to the factory, often forgetting about pending updates.

To do this, open the Settings menu → Apps → All apps. In the upper right corner, click on the menu icon (three dots) and select Show System Processes. This is a critical step, because without it, you won’t find the component you want.

Find an app called System Update on the list. Tap it and select the Stop button. If the button is inactive, click Clear first» → «Clear all data. Confirm the action. After that, the system will stop "remembering" that the update was found.

Immediately after cleaning the data, it is recommended to turn on In-Flight mode for 10-15 seconds to break the current network connection and then turn it off, which will prevent instant re-query to the server, which is effective for a temporary solution to the problem until the system again conducts a routine check.

Blocking through a special menu and debugging

HyperOS still has the ability to use hidden codes and debugging menus for deeper management, a technique that is suitable for advanced users who are not afraid to work with technical settings, and it allows you to limit the background activity of services Google and Xiaomi responsible for telemetry and updates.

The first step is to activate the developer mode. Go to Settings → About Phone and quickly click on “MIUI/HyperOS Version” before the message “You became a developer” appears. Then go back to the main settings menu, select “Additional” → “Developers”.

Inside the developer menu, find the section related to background processes. Although there is no direct OTA lock, you can limit background activity. Find the item "Background Process Limit" and set the value "No More than 1 Process" temporarily to interrupt the download, but remember to return the "Standard Limit" so that the messengers do not disrupt the work.

You should also pay attention to the Wi-Fi settings. In some cases, disabling the "Use mobile network to download updates" feature helps. This is in the menu of the updates themselves. Make sure that the tick is removed so that the system does not start downloading gigabytes of data through your mobile traffic at the most inopportune time.

Using ADB for Advanced Blocking

The most radical and effective way is to use the Android Debug Bridge (ADB) toolkit from a computer, which allows you not just to stop the service, but to “freeze” or disable the system package responsible for updates, making it physically unable to run without root rights.

To start, you need to enable USB debugging in the Developer Menu (see previous section). Then connect your smartphone to your computer with a cable. The PC should have an ADB platform installed. Open the command line or terminal in the ADB folder.

Enter the following command to disable the update package:

adb shell pm disable-user --user 0 com.android.updater

If the command is successful, the update app will disappear from the installed list and the system will stop checking the new version.

adb shell pm enable com.android.updater

💡

Using ADB is the only way to guarantee that you will not automatically install the update, as the system package is physically disabled.

Be careful: in some HyperOS builds, the package may be called differently, such as com.miui.otupdater or have the prefix com.android.carrierconfig depending on the region. If the first command does not work, try to find the exact name of the package through the command adb shell pm list packages | grep.

Comparison of methods of blocking updates

So, to give you the best option for your situation, we've developed a summary table that shows the effectiveness, complexity and risks of each of the methods described above, and not all of them are suitable for long-term use.

As you can see from the table, simple methods are good for a temporary solution, but for full control you need ADB. However, if you do not plan to use your smartphone for years without security updates, it is better to manually check for critical patches periodically (once every six months).

Remember that disabling updates not only deprives you of new features, but also of patches of security vulnerabilities. In the mobile OS world, this is an important factor, especially if you use banking applications and store sensitive data.

Frequently Asked Questions (FAQ)