Smartphone Xiaomi Redmi Note 3 Pro (codenamed kenzo) is deservedly considered a legend of the budget segment, but the regular firmware MIUI 9 is based on Android 5.1.1 has not received official security updates and functional improvements, and many users still use this device, wanting to breathe new life into it by installing a new version of the operating system. Switching to Android 6.0 Marshmallow or custom builds based on it allows you to access new ones API, Improved application permission management and increased stability.
The upgrade process is not trivial like installing a regular application from Google Play. You will have to unlock the bootloader, install a special TWRP recovery mode and work with system partitions. Errors at any stage can lead to data loss or software failure, so it is important to read each paragraph of the instructions carefully and understand the essence of the actions performed. In this article, we will discuss in detail all the nuances of transition to the new version of the software.
It’s worth noting that switching to custom firmware or upgrading to Android 6 through third-party methods removes the device from warranty service if it’s still formally in place. However, for the Redmi Note 3 Pro, it’s often the only way to continue comfortable smartphone use in today’s environment. We’ll look at both official methods and time-tested ways to install modified software from the development community.
Device preparation and data backup
Before any manipulation of system software is initiated, it is critical to retain all important information. The firmware procedure often involves a complete cleanup of the device’s internal memory, so ignoring this step will lead to the irretrievable loss of photos, contacts and documents. USB-cable.
Make sure your Xiaomi Redmi Note battery is charged 3 Pro is not less than 60-70%. The flashing process can take a long time, and a sudden power outage at the time of writing system files is fatal for the bootloader. USB-cable: use original wire or quality analogue that supports data transfer, not just charging.
⚠️ Warning: Do not use damaged or too long USB-cables when connecting the smartphone to the computer in Fastboot mode. An unstable connection can interrupt the recording of the bootloader image, which will turn the phone into a “brick” requiring a programmer to restore the device.
To work, you will need a Windows computer (ADB and Fastboot drivers work best in this environment) and USB debugging enabled. To activate this mode, go to Settings → About phone and quickly click on the MIUI version seven times, after which the Debugging over USB option will appear in the developer menu, which you need to activate.
☑️ Firmware preparation
Unlocking the Bootloader bootloader
Xiaomi defaults to lock the bootloader of its devices, which prevents the installation of unofficial software. To upgrade to Android 6 on the Redmi Note 3 Pro, this protection must be removed. The official method involves submitting an application through a Mi Account and waiting 3 to 15 days, although older models sometimes get permission faster.
The process starts with tying an account to a developer menu, and then you download the Mi Unlock Tool to your computer, log in to your account, and put your smartphone into Fastboot mode, holding both the power and volume buttons, and by connecting the device to your PC, you can initiate unlocking through the program.
It is important to understand that unlocking the bootloader automatically triggers the process of complete data cleanup (Wipe Data). Even if you plan to just upgrade, this step is mandatory and irreversible without completely reflashing the stock version with the closed bootloader. After successfully unlocking, the Unlocked icon or the image of a rabbit fixing a robot will appear on the boot screen.
💡
If Mi Unlock gives a timer error or requires you to wait 168 hours, do not try to reset your account or reinstall drivers - this will reset the timer.
There are paid services that offer instant unlocking, but this is rarely necessary for Kenzo, as official restrictions are often already removed or bypassed by simple methods through the use of a free-to-use system. EDL-The system if the standard method does not work.
Installation of custom TWRP Recovery
Staff_recovery_ does not allow you to install third-party firmware and make full partition backups, so the installation TWRP (Team Win Recovery Project is a must-see phase. 3 Pro has several versions of the recovery, but the most stable version is considered to be from the developer pitchblack or OrangeFox.
Download the.img image file corresponding to your CPU model (for the Pro version it is Snapdragon). 650, Not MediaTek, which is important not to confuse. ADB-Enter the command for the firmware image: fastboot flash recovery twrp-3.x.x.x-kenzo.img. Immediately after the command is executed, you need to pinch the combination of buttons to enter the recovery mode, otherwise the system will restart in normal mode and replace it. TWRP backstaff.
Once you’ve successfully logged in to the TWRP menu, the first thing you do is clear the Dalvik/ART Cache, Cache, System, and Data partitions, called Advanced Wipe, and ensure there is no conflict between the old file system and the new firmware. Formatting the Data partition may require you to enter a password if you’ve locked your screen before.
⚠️ Attention: When installed TWRP Android 6 You may need to move to a new partition table. If you see a message after you've run the backpack, "Failed to mount." /data», You may need to convert the file system to Ext4 via Wipe menu → Format Data that will permanently delete all files.
TWRP is fully touch-sensitive and intuitive. To install the firmware, you'll need a pre-loaded archive with the operating system to your memory card or internal storage, and support for exFAT and NTFS file systems allows you to use large-volume flash cards without formatting.
Selection and installation of Android 6 firmware
Finding a pure Android 6 for the Redmi Note 3 Pro is harder than the newer versions, as the community has long since switched to Android 7, 8 and 9. However, there are MIUI 8 ports based on Android 6, as well as custom builds like CyanogenMod 13 or LineageOS 13, which are based on Marshmallow.
When choosing firmware, pay attention to the build type: Stable (stable) or Nightly (nightly, updated daily). For everyday use, it is recommended to look for stable versions marked with the Final or Stable tag, as they have been tested and are free of critical errors. Nightly builds can contain bugs that affect the camera or Bluetooth.
The installation process is as follows: in the TWRP menu, select Install, find the downloaded zip archive with firmware and confirm the swipe. Once you have completed the installation of the main system, you often also need to flash the GApps package (Google Apps) if it is not built into the firmware, otherwise you will not have the Play Market store and Google services.
| Type of firmware | Basis | Stability | Recommendation |
|---|---|---|---|
| MIUI 8 Global | Android 6.0 | Tall. | For fans of MIUI shell |
| LineageOS 13 | Android 6.0 | Medium | For fans of pure Android |
| CyanogenMod 13 | Android 6.0 | Medium | The Legendary Classic |
| Resurrection Remix | Android 6.0 | Low. | For experiments and settings |
Remember, after the first installation, the initial boot can last up to 5-10 minutes. This is normal, because it's the optimization of applications and the creation of cache. Don't force the phone to turn off at this point, even if the screen goes out - just wait for the logo to appear.
Configuring drivers and working with ADB
Successful communication between Xiaomi’s computer and smartphone requires properly installed drivers. In Windows environments, drivers often conflict when the device is defined as “Unknown Device” or “Unknown Device «QHSUSB_BULK». The solution lies in manual installation of drivers through the Device Manager.
You will need Qualcomm HS-USB QDLoader 9008 drivers for EDL mode and standard Android Bootloader Interface for Fastboot mode. You can download them as part of the Minimal ADB and Fastboot package or separately from the developer's website. When you install manually, select "Update driver" → "Select from the list of available drivers" and specify the path to the.inf file.
You can check the connection with the command line adb devices, and if you see the serial number of the device and the status of the device, you've got the connection, and if you're unauthorized, look at the phone screen and confirm the debugging.
adb reboot bootloader
fastboot devices
fastboot getvar allThese commands allow you to go to bootloader mode, check visible devices and get full information about the lock status and the current firmware version. The fastboot getvar all command is especially useful for diagnosing: it will show whether the bootloader is unlocked and which memory slot is active.
What if your computer can’t see your phone in Fastboot?
Possible errors and ways to eliminate them
When upgrading to Android 6 on the Redmi Note 3 Pro, users often face typical problems, one of the most common being a “Bootloop” (cyclical reboot), which occurs when the firmware is incompatible with hardware or the Wipe step is missed, and the solution is one: go back to TWRP, make Full Wipe and reflash.
Another common problem is a broken sound or camera, which indicates that the radio module and the firmware are incompatible. For Kenzo, it is important that the firmware version be Android version. Before installing custom firmware, you often need to upgrade or roll back the base firmware to a specific version of MIUI.
⚠️ Note: If the touch screen doesn't work after the firmware, chances are you've installed the firmware for the MediaTek (Kate) version and you have Snapdragon (Kenzo), or vice versa.
There may also be an “Error 7” error when installed via TWRP. It means that the installation script checks the device model and prevents you from installing the firmware, in which case editing the updater-script file inside the firmware archive (deleting model checks) or using another version of the backpack helps.
💡
90% of all errors in the Redmi Note 3 Pro firmware are due to using the wrong firmware version (Kenzo vs Kate) or skipping the full data cleanup step (Wipe).