Xiaomiβs current MIUI-enclosed smartphones and the new HyperOS feature a multi-stage security system that actively uses CC certificates to verify the authenticity of applications and network connections. In most cases, this feature works unobtrusively to the user, providing protection against malware and phishing attacks. However, developers, testers and advanced users often face the need to deactivate this verification to properly work debugging tools or specific software.
Disabling certificate verification may be required when installing applications from unknown sources that are not digitally signed, or when using traffic sniffers to analyze network packets. It is important to understand that manipulation of system certificates carries certain risks, and should only be performed with full confidence in your actions. In this article, we will discuss in detail how to circumvent protection, work with superuser rights and the nuances of setting up the development environment.
Before you make any changes, you need to be aware that you are temporarily reducing your device's security, and that completely disabling signature verification allows you to install modified versions of system applications, which is not possible in standard mode. We'll look at both software methods through the developer menu and deeper file system interventions that require root rights.
Why is it necessary to disable certificate verification
The main reason users are looking for a way to disable the CC certificate checker is to install apps that havenβt been officially moderated in the Google Play or GetApps store. APK-files, if their digital signature does not match the already installed version of the program or if the signature is missing at all.
Additionally, application developers often use traffic sniffers like Charles Proxy or Fiddler to debug network queries, and these tools require embedding their own root certificate into a trusted system storage. Without disabling standard security checks or installing user CA-certificate, encrypted HTTPS traffic will remain unavailable for analysis, as the application will reject the connection to the proxy server.
β οΈ Note: By disabling signature verification, you allow the system to install applications from any authors, which can cause the device to become infected with viruses, identity theft, or operating system instability.
It is also critical for those who are interested in modifying system files or installing custom recavators, and in such cases, the standard bootloader and system partition verification procedure can prevent the modified software from running. Understanding ADB and access rights is a key success factor in these operations.
Activation of the developer mode and debugging via USB
The first step to any deep setup is to activate the hidden menu for developers. Without this section, most of the switches we need will not be available. The process is standard for all Android devices, but in the shell MIUI has its own peculiarities associated with increased security aggression.
First, you need to go to the Settings menu. β About the phone and find the line Version MIUI. You need to press this line quickly. 7-10 Once in a row, until a pop-up notice that you have become a developer appears, and then a new option will appear in the main settings menu, in the Additional section, For developers.
Inside this menu, you need to find and activate the USB Debugging Switch. The system will alert you to the risks, we agree. Next, you should find the Installation via USB and also turn it on. Here Xiaomi will require an account binding and a SIM card, as well as the mobile Internet enabled to check the status of the device for locks.
- π± Go to Settings. β About the phone and tap according to the version MIUI before the activation message appears.
- π In the menu For developers, include toggles Debugging by USB and Installation through USB.
- π‘ Make sure your device is connected to a mobile network, not just Wi-Fi, to pass a security check.
- βοΈ When connecting to the computer, select the mode of operation. USB File transfer (MTP).
It is important to note that without activating these functions, the team ADB (Android Debug Bridge) will not run, and you will not be able to send commands to the device from your computer.This is a fundamental stage without which further manipulation is impossible. USB Driver and platform SDK Platform-Tools.
βοΈ Verification of readiness for modification
Using ADB to change security settings
The most secure and common method of working with system parameters without obtaining root rights is the use of the ADB toolkit. This method allows you to send commands directly to the system, bypassing the graphical interface, and change global security settings, including those related to application verification.
First, connect your smartphone to your computer through a high-quality USB-Open the command line or terminal in the tool folder ADB And you type in the connection check command: adb devices. You'll see a request for debugging permission on your phone screen -- make sure you tick Always allow from that computer and click OK.
To disable application verification during installation, you can use the following command, which changes the value of the global parameter:
adb shell settings put global verifier_verify_adb_installs 0This command tells Android that when installing apps via ADB, no additional verification is required through Google Play Protect services. However, completely ignoring signatures often requires changing deeper settings, which may require root rights or the use of specialized modules.
β οΈ Attention: Teams ADB It can have irreversible consequences if you use it incorrectly, only enter commands that you fully understand. A syntax error can lead to a cyclic reboot).
There is also a command to disable signature verification when updating apps, which developers often need:
adb shell pm install --bypass-low-target-sdk-block package_name.apkUsing the --bypass-low-target-sdk-block flag allows you to install applications that target older versions of the API, which is usually blocked by modern versions of Android.This is a special case of circumvention of the limitations associated with compatibility, but it demonstrates the flexibility of the ADB toolkit.
Working with root rights and Magisk modules
For users who need full certificate management, having superuser rights (Root) is almost a prerequisite. On Xiaomi devices, root access is usually achieved through unlocking the bootloader and installing a modified boot image with the Magisk patch.
Once Magisk is successfully installed and rooted, modules that can change the behavior of the system on the fly without affecting the system partition directly become available to the user. One of the most popular solutions is the Always Trust User Certs module, or analogues that force user certificates to be added to the system repository of trusted roots.
The installation process of the module is as follows: download ZIP-The module archive, open the Magisk app, go to the Modules section and click Install from storage. Once the device is restarted, the changes will take effect. This allows applications that verify the presence of a system certificate (for example, banking applications or corporate clients) to work with user-generated applications. CA.
- π Unlock the bootloader through the official website of Xiaomi Unlock Tool.
- π οΈ Install a custom Recovery (TWRP) or patch boot.img via Magisk.
- π¦ Download the module for working with certificates in format ZIP.
- β Activate the module in the Magisk menu and reboot.
It is important to understand that root rights can trigger some security applications, and that banking and anti-cheat games can refuse to run. To circumvent this restriction, Magisk needs to enable Zygisk and configure the Denilist, hiding root rights from specific applications.