• Copy zip to phone memory
• Boot into recovery
• Install zip
• Reboot
• Wipe will make TWRP

MiuiSu_7.3.30_RN4X_by_maer1977.zip(25.56 MB)

MiuiSu_7.4.6_RN4X_by_maer1977.zip(24.29 MB)

We go to the settings-about the device-tap according to the version of MIUI, until it registers that you became a developer. Further settings-extra-for developers (developer mode) we look to enable factory unlocking and USB debuggingYou can also see the bootloader unlock status (the easiest way), sometimes the item may differ slightly, instead ofBootloader status-Unlocked m. Lock open (unlocked) or closed (locked)
Note, it is desirable to connect the cable from the phone to the computer from the "back" side (from the motherboard side), there are people who have the front side defined in the controller and in the MTP mode, but with commands via fastboot, which we will use below, sends computer mother.
1. We startadb-windows.zip(9.26 MB)
and unpack, preferably on the C drive (I call the folder in Latin, without spaces or dashes) I did
2. We transfer the phone to fastboot (power button + volume minus, until a hare appears in the earflap with the inscription FASTBOOT) and connect it to the computer.
3. Check (for example, windows 7), go to the Control Panel — all the device manager programs should be, without question marks, if the question mark is downloading drivers from the topic headerADB + driver + v1.17 + lite.zip(9.04 MB)
depending on your system (32/64)
4. Next we go to the folder with adb and the shift combination + right mouse button- a window will appear select Open command window (it may not always work the first time) Appear
5. To check that our device was defined, we enter a command, for a startget confirmationproduct: mido mido - is our device, then enter the commandif the device is determined to appear its number, if not prescribe waiting device
If our device is determined, enter the commandand getwhere oppositedevice unlocked worth it true means the bootloader is unlocked if false is closed. This command tz. more sure way to check bootloader

Before starting the procedure, I propose to get acquainted with the first spoiler instructions . And for starters, links to the official TWRP look here Link to the spoiler in the header with TWRP here

Everything is simple, download the desired SU, or mods, fixes, scripts and other improvements, etc. At the moment, I recommend installing SU 2.65 on the 7th 2.79 on firmware based on the 6th android here or magisk what is closer to you, all instructions and descriptions in these branches. I'd recommend a patched SU PRO from uv.Cobra111111 link to his updated post here Do not forget to thank the person. Downloaded rebooted to TWRP, then click Install / Instal, select our downloaded file, tap on it, swap to install and reboot into the system.

For simplicity, we translate into
Cleaning what is it done for and what to live on
1) Before flashing another firmware do the followingTap on the screen as a tick 1 to 4 on 5 (svayp for cleaning)Personally, I recommend, "wipe up and the device Memory section, as well as format the Data section

for a more complete and proper cleaning and later rolling the firmware through a removable card, or downloading the firmware from the phone, after a full cleaning, it is also IMPORTANT to remember when you wipe (clear) the device memory all data from the phone will be erased, so transfer the data to the card or computer in advance , if there is no such possibility then before flashing it is desirable to delete two folders Android and Miui

After we select the folder where the firmware was downloaded and we taped on it (for example, on my sd card in the Download1 folder and in my case firmware miui.suIf you want to add more files for "joint" flashing (mods, supersu, etc. thenmarked in red / Add another zipand / or insteadyellow / swipe for firmware(I repeat, if in this way we sew up the stock, official firmware, together or after, you need to flash eitherscriptprotection, or SuperSu.) Now we wait for the system to flash and then Swap to boot the system, or press the checkmark / Sbip before flashing for firmware / Automatic restart after installation, in this case, restart after flashing to install the firmwareAfter that, wait until the initial installation screen appears.
2) Update firmware via TWRP. There are two ways to "dirty roll" and update with wipe. When dirty, just go to the folder where our firmware is downloaded, tap it and swipe for the firmware, the second way, before updating, go to Cleanup and select as in the screenshot, then go to the folder where our firmware is taped and if it was installed for example supersu We add another zip and select the supersu file (This is done because with the wipe the cache will fly off everything that was added by the mods not embedded in the firmware)
In the same way we can, through TWRP, separately to the firmware, you can sew mods, fixes, etc.
In case you did not backup the firmware and thanks to fashion, fix, etc. the phone does not boot (often hangs on the MI logo), you can artificially reboot into rekoveri (power button + volume plus, to the victorious "), make wipe cache and flash our firmware with a new one, in this case 99% of the firmware will safely boot, thus avoiding data loss
Note: TWRP is able to sew not only zip archives but files with the img extension. (often kernels, other TWRPs). In order to flash files with the img extension. find the folder where it is downloaded, then tap on

and after our files will appear with the img extension, we select and rekoveri will suggest through what to flash it, respectively, the kernel via boot, TWRP via recovery
Note: in some TWRPs there is a Select Storage key in the bottom left section for selecting a drive (SD card or OTG) if you want to select files for installation from there

Many before installing all sorts of different goodies (fashion fixes, Russifiers, core, etc.) have seen and read that the author recommends to backup / Backup / Because translation is clear that a return to the starting point, ie, make a backup, you can experiment with firmware climb and delete system files, change them, sew "risky" fashion and fixes well, and one of the most interesting, try a different firmware, if it does not please feel free to come back, and on the road to have a backup is always nice, if suddenly flew firmware for a number of different clear and understandable reasons. While the backup is possible to carry on the support, not necessarily in the memory of the device.
Boot in rekoveri and how to

screenshots

On the ground, respectively, select the backup on the second selectable items, is the main system, data, boot the first two and occupy the main memory, so I recommend prozhat ticks all where there are megabytes of memory, they will not take up much space. The volume of data memory can be varied and large and slightly downwards, depending on how many applications you have installed, and often all of the important information we need be stored in this section. And at the end of the third screenshot choose either back to further continue with rekoveri or safely reboot the system.
Recovery. The easiest and most reliable way to restore go to the item Cleaning>Selective cleaning>resideDalvik / Art Cache - System - Data - Cache >Swipe for cleaning>We leave on the initial screen and>

First screen click Restore
The second screen will choose our backup (I have one), but there may be several, next to each will be the date / time / firmware version
We select the third screen for the partitions to restore, in this case we select everything (I have only bktlouder saved by the example, you will have several, see the above backup) and a swipe to restore.
(There were several posts with problems of restoring backup, there were interesting answers to my koumiss possible in the topic, I decided to check it myself. Firstly, if I baked the three main items Boot (core) Sysytem (system, system files) and data (user section, programs and etc.) and then restore them, everything is restored and working normally.
Secondly, if you backed up all where there were megabytes, then when restoring (in my test version), you need to select everything exceptEfs and frimware errors occur on these two points.
And to summarize everything, I will write that the three main sections are sufficient when restoring the Boot Data System, and backing up all the megabytes just in case. Why does it give an error until I figured out I can only sin on the curvature of the custom recovery that exists under our apparatus.
Although there is information that in the modified TWRP 3.1.1-1 there are no such problems

Before starting the procedure, I propose to get acquainted with the first spoiler instructions
The latest official firmware for fastboot takehereand further as the screenshots, or in the cap threads there is a link. In the third screenshot swipe to our device, there choose either stable (there are two options for us than not otltchayutsya 1.Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File Download and 2.Redmi Note 4X Latest Global Stable Version Fastboot File Download ), a developer version (1. redmi Note 4 Qualcomm Latest Global developer version Fastboot File Download and 2. redmi Note 4X Latest Global developer version Fastboot File Download) The only thing just in case is checking mido postscript
From time to time, I recommend the stock firmware to be stable either weekly depending on your preferences, to clean the tails of previous reflashing, or simply deciding to return to full stock with OTA updates.
Download as above firmware for fastboot at the end of d. The .tgz extension is unpacked into our folder with adb and clickblue marked that the bootloader remained untouched ie open, red to return it to stock condition with a closed loader The firmware will start, about 3-5 minutes, after which the command window will disappear and the installation of the firmware will start 3-10 minutes, depending on which MM you put on the MM, it is longer, on the NUGA a little faster.
Ps. When flashing, by launching flash-all.bat, all data will be deleted.

For those who want to return OTA after flashing custom recovery SU
My example, I flashed the developer (it is possible and stable), but in order not to lose data, I patched the custom recovery, then I patched SuperSU, I restored the application data using Titanium backup.
1. Next, from under the recovery, delete SU to flash this archive.uninstallSU.zip(4.74 KB)
if you did not roll up the protection script, then we sew it before loading it into the systemlazyflasher-no-verity-opt-encrypt.zip(420.95 KB)
If you do not load, perform step 2, then the script can not sew.
2. Further, depending on what kind of firmware you have, we are looking for stock recovery in the folder with the firmware (I have an archive for fastboot in the images folder and from under this folder)We put the device into fastboot mode and the Shift + key combination + right mouse button - open the command window and prescribe
We press Enter, it is stitched to the stock recovery, we check it, we boot into the system, after that we can safely flash the OTA with an automatic machine without fear of getting a bootlap.
Note: if you deleted the system apk or other files, before returning to the stock condition, I highly recommend wiping both caches and flashing the firmware that you currently have, naturally, the firmware is needed for recovering with the zip ending.

Modems from the 6th android are not suitable for the 7th (everything will work except for phone calls) so be careful

Designations
/ firmware version // android version // miui v version /


Stable ROM
1. /8.1.10/ / 6 / / V 8 / - download
   
2. /8.1.2.0/ / 6 / / V 8 / -download
   
3. /8.1.15/ / 6 / / V 8 / -download
   
4. /8.2.10/ / 6 / / V 8 / -download
   
5. /8.2.20/ / 6 / / V 8 / -download
   
6. /8.2.5.0 / 6 / / V 8 / -download
   
7. /8.5.4/ / 7 / / V 8 / -download

1. /7.4.27/ / 7 / / V 8 / - download
   
2. /7.5.11/ / 7 / / V 8 / -download
   
3. /7.6.25/ / 7 / / V 8 / -download
   
4. /7.8.10/ / 7 / / V 9 / -to jump
   
5. /7.8.18/ / 7 / / V 9 / -download
   
6. /7.8.31/ / 7 / / V 9 / -download

Localized stable
/8.5.6.0/ / 6 / / V 8 / -download

Link to posthere

Link to post with instructionshere

To begin, I suggest to get acquainted with not a large article. about folder structure in androidhere

Not a big F.A.Q. on working with the program Titanium Backup

1. Make a backup of applications and games, as in the first screenshot press the top / right sheet with a checkmark, as recently as in the second screenshot, click the Start, in the third screenshot, select the applications that want zabekapit, by default, all that we have established will be ticked if that -That backup procedure, the duration depends on the number and scope of applications (those that have cash games TV to backup is not needed, press the tick to continue to the top / right squeeze the tick, the fifth screenshot gone, and only their data, so if you problems with internet, cash games copy in advance, are they on the way the internal memory / Android / data / obb), as the backup was made just in case (if the firmware on clean, with the removal of data and formatting the data transfer Titanium Backup folder as the fifth screenshot to other media.
2. Next, the recovery procedure, assume you have installed the firmware to clean, install the program on a TV phone, open it, then our folder with TV portable to replace the phone, or just the data from the folder in the folder TV, whisk in running programs TV programs, open for as the new sixth screenshot click restore, watch tick relevant / not relevant to the application as a recovery in the third image below and click the check box at the top / right and forward recovery is complete. It is also possible as in the seventh / eighth / ninth screenshot bekapit one application including and system, where you can also delete system applications (with a question mark is not a triangle zabekaplennye applications
applications that are marked in red, system, white, non-system, user-installed)

1. Removal. Some, like me, are hampered by the presence of unnecessary system software, I will show by example how the system can be removed and, as well as implementing it, I recommend using SuperSU Pro for this purpose The most important thing in this is to make a System backup via TWRP, or to have the firmware that we will clean, in order to flash it on top with wipes of both caches .
For this purpose I use ES Explorer PRO (bought or patched for you to choose), although you can also use the regular free version by downloading it in the google play market, that's about the versionES + File + Explorer + Pro-Pro + 1.0.9P.apk(5.94 MB)

We go into the conductor and give him superuser rights, as on the screenshots we get to the System folder and all our programs that are needed / not needed are located in the app and priv-app folders, we are looking for what we want to delete and, accordingly, delete it. Or you can use the program Titanium BackupTitanium + Backup-MoDaCo-8.0.0.apk(7.55 MB)
everything, thatredThese are system files, in this program tz. easier to find through the search, at the top, what's stopping us, after you delete through Explorer or Titanium you need to restart the device. When deleting some programs, such as "dialer", contacts, security in miui, there may be errors, everything is always very different, therefore I recommend deleting them in stages, in small batches, in order to understand after which errors orhereyou can still look
2. Implementation For what it is necessary, to each his own, some programs, program modifications do not want to work "correctly" without being systemic (such as a modified youtube, without ads), I will show again with an example es explorer, for example I need to make the AdAway program systemic, I create in the system folder>The AdAway app folder needs to be set to the right with the letter P (unless the developer requests otherwise in the instructions), then we throw the AdAway apk file into this folder and give it the right of the letter G, after all this, you need to reboot the device.

ResetScreenLock.zip (142.24 KB)

No one has yet canceled the backup, if you are root, then TWRP is also: nono:
So:
We download root explorer.A we allow him to edit the system and then simply. Open the root explorer file with the text editor - / system / buil.prop. We find there the following line:



This line tells the system which mode the mobile network should be switched to when booting. The value is a number that can be recognized as follows: dial in the dialer

and click on the item "Information about the phone." In the "Preferred network type" menu, we count from above to the desired mode. The bill starts from 0. That is, for a 3G smartphone, the values ​​will be as follows: WCDMA preferred (preferably 3G) is 0, GSM Only (2G only) - 1, WCDMA only (3G only) - 2, and so on. I counted to the right - I wrote down the number in the value. Now immediately after the reboot, the network will be activated exactly in the mode that is recorded in build.prop.
After changing the line in build.prop, we agree to the change. But in any case, the root explorer will create a file with the build.prop.bak attribute where the initial settings are saved.