xiaomi_usb_driver.rar(8.27 MB)
Now more specifically about the firmware.
1. On the firmware from which the phone came (most likely it will be a Chinese stabilizer on miui 9.5), you tie an account to the device through the developer menu. I got it the first time without any vpn and dns.
2. Get permission to unlock the bootloader, if it already exists, then download the latest version of miunlock and unlock the device. It is likely that the software will ask you to wait up to 360 hours, personally, everything broke up right away.
When unlocking, all data from the phone is erased.3. Take twrp and adb from the header, and also install the drivers if they are not there (links in the attachment). In principle, you can immediately take the fastboot firmware from the same header (Chinese developer based on Miui 10) and fill it, but it’s better to do it first
Backpack, and for this you need twrp. Throw twrp in the folder with adb, enter the phone in fastboot mode by pressing the volume buttons - and turning it on.
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
where twrp.img is the name of your tvrp
4. Be sure to back up the firmware using twrp and reset it to the computer.
5. Do all the wipe except persist and otg. Moreover, the format of the date section is best done through the word YES. Reboot to rekarer
It is worth noting that this is where I made the mistake of making a wipe Persist. The fact that he was not sewn together with the rest of the firmware in the classic mode. Pour it separately through fastbut then impossible because the section is write-protected. And edl regime is not yet far from clear, it is possible to use it will be possible only through the service cable. When the damaged / remote section Persist problems begin with a camera and sensors - they cease to function. The solution is to taking persist.img file from the folder img unpacked firmware for fastbuta, place it in the root of the phone's file system and flash the vehicle through the same tvpr install imgage button.
6. Download or install pre-downloaded firmware for recovery from the header, so far it is only Chinese developers and install. (I did not start up the firmware from MS with the Russian language when installing on a clean phone, i.e. with all the wipes, or when flashing over a Chinese developer of the same version.) There should not be any errors during the installation process. After the firmware, I once again rebooted into the recovery in order to make a wipe date and only after that I loaded into the system.
Then everything is the same as when it was first turned on, with the only difference being that you have to enter the password from your account, since the device is already attached to it. If immediately after turning on you have a screen with a lock and two buttons with hieroglyphs, then press the one that says WIFI, enter the password and connect to the wireless network. Then a screen appears with the input of the password from my account, also filled with hieroglyphs, and fill in the only field. Only after that it will be possible to choose the language of the system.
You are now in the hands of the Chinese developerka with updates over the air, but without the Russian language. The hat was a video on how to install Google services on the firmware, but it was removed from youtube. In short, go to the App Store, there are looking for google, the result will be, so do not make a mistake, pressing instal button, then open. Then the phone offer allow installation from unknown sources and begin to install the necessary proposals. Following, I would advise you to roll out of play Market normal keyboard with Russian language and can be used.
P.S. Xiaomi.eu presented a ROM based on a Chinese developer
It rolls through TvRP with all the wipes without any problems, the Russian language is present, but the translation is not yet complete, in some places English is encountered. Also in the presence of Google services. After installation, the magic check safety net passes, google works. But there is no unlock face, possibly because in this version of the firmware it functioned rather badly and they decided to cut it temporarily, and the interface itself is rather slow, at least compared to the 9.5 stabilizer.
Post has been editedDogsly - 23.07.18, 09:05Reason for editing: In the header