I confirm the operation went with a bang! Everything plows like a clock .. ThanksAlexPashenko .GOOD LUCK EVERYONE! : D.

Post has been editeddraiv88 - 04.10.16, 17:24

The other day I received the second phone. I installed a weekly official 6.9.29, dislocated on it, I install it through FastBoot TWRP (TWRP-3.0.2-1-Gemini.img), but after installation it does not respond to pressing the screen, reinstalled several times, including that version that costs On the previous phone - the result is the same ..., I waited for about 20 minutes, it does not help. I connect the mouse everything works fine .... who faced with it and what other options can I try?

focus880, Xiaomi Mi5 - MIUI Firmware (OS 6.0) (Post Andreym1 # 53326219)

I can not go into the recovery after installing TWRP, the image of the device with a lace is constantly popping up and further reboot into the system. When installing TWRP on the command prompt, all procedures run out approx.
What am I doing wrong? (
All instructions have already watched.
I want to install the firmware on the official global from Xiaomi.eu

So it is not all, because in some of the nickname, the first time in the recovery it is advised through the team in fastboot, and not buttons.

Almost all instructions from this forum went through. On some, it goes into an infinite loading with the inscription MI, it simply turns off on the other and after a few minutes it loads into the system, and silence pops up in third lace ...

This is not the official global and custom firmware from localizers.
You tried, first recovery.img throw into the phone, then with the help of the team in the fastboot to go to the TVP
FastBoot Boot Recovery.img and from TWRP Installation-Installation IMG - Find and Choose Recovery.img
Swipe
Restart into recovery?
And then sew according to the instructions the desired firmware.
In general, who came up with the initially renamef file for example TWRP-3.0.2-0-gemini.img in recovery.img, I will not say thank you. Because of the laziness to prescribe a long name in the command window now such a tank in the forum with a double extension .img.img {Although there are the simplest commands to highlight commands from the copy statement (Ctrl + C) and the insertion in the command window (Ctrl + V)}

Post has been editedflexible1126 - 04.10.16, 20:39

I put on top of the official global Multulang Castomny from Xiaomi.eu, more precisely trying through TWRP.
I tried and renamed the file in recovery.img and left the original names simply changing the command to the corresponding name of the .img file

Sonik100,
Now try using the fact that I wrote the post above. And most importantly, put the driver first for the computer here and select the desired X-bithttps://yadi.sk/d/YD7LWnWurZCNPAnd connect the phone without extension cords in the MatPlat.

Post has been editedflexible1126 - 04.10.16, 21:18

I received a phone today. Due to confusion with EDL, did not bother and did it easier:
1. Since the phone came with the Chinese global, I changed it through 3 points to the Chinese developer.
2. Entered into his account.
3. The permission to unlock was obtained for a long time, so unlocked in a couple of seconds.
4. Threatened through the fastbet to the global developer.

PS: Upset the fact that it is impossible to turn off with regular means of google-trash and miui mail with a browser (although on Mi4 it was possible on MIUI 8). But since the bootloader is unlocked, then:
1. Loaded in TWRP (without its firmware)
2. Installed SuperSU.
3. With the help of the titanium, frozen google-trash with MIUI mail and browser (you can not freeze "Google's applications" for from recently it is integrated into the shell and you can grasp the bootlup).
4. Removed Supersu from the program itself (agreeing to the program request to restore the original bootloader and recovery to obtain trouble-free update by OTA)
5. The phone itself rebooted.

That's all, lightweight system, all that wanted to turn off and can be updated by OTA.
True, after hard-cutting, it will be necessary to repeat everything again with the installation of SuperSU and the disabling programs. But it does not occupy a lot of time if that ...

Nowhere else has nowhere.

Post has been editedIceman2000 - 04.10.16, 21:20

Sonik100,
But I did not guess with the drivers, put what I suggest you, otherwise you can not install until the morning.

Posted on 10/04/2016, 21:22:

axil31,
FastBoot Boot Recovery.img Without Flesh, only one team and you in TVP, always do that.

Post has been editedflexible1126 - 04.10.16, 21:23

In fastbut mode, type command:

Whererecovery.img This is the image of TWRP in a folder with fastboot.exe (as a rule, the file lies or in the ADB folder, or, like me, in the Platform-Tools folder)


Post has been editeddraiv88 - 28.02.17, 20:11

Mk902ii,

By the way, about the firmware "through three points". For the sake of interest, being on the firmware 6.9.22 from Xiaomi.eu, I tried to slip this program firmware file 6.9.29 from the same localizer. Well, this program issued the message "data encryption" and the progress bar of this process. I was already not so interesting and I rebooted the phone. But still: there are those who waited for the completion of the process? Can anyone explain what kind of encryption it started?
I interrupted the process because someone once after the firmware one of the old global I was surprised that the data in the phone was encrypted and I could not recover from the backup that I did not really like it.

Maybe it was just a coast of translation from localizers? In globates, there is a progressbar "Decipheration of the firmware" or something like that. The device unpacks the firmware before installing. Here, probably, the same, only the coryavo translated on our great and mighty :) ...

I'm trying to flash the phone here, I flashed through the EDL global weekly version, I successfully made the unlock, and then I flashed through FastBoot TWRP and BOOT (recovery.img and boot.img), after which the phone is not loaded (MI is not on all the time and the load does not go on ). When you try to enter the TWRP (volume up and the power button), the logo MI appears and nothing further (I have been waiting for little? But hardly)
What now? From ideas just to roll back a weekly global, so that the phone does not sat down.

If it does not connect to ADB and writes Device Offline, you need to download the latest version of Android Debug Bridge.
Quote found material:

You can check the current version of ADB using ADB Version, for example, before the update I was issued: Android Debug Bridge Version 1.0.26, and after - Android Debug Bridge Version 1.0.31. You can download the ADB update at the following links:

For Linux:https: //dl-ssl.google....ools_r19.0.1-linux.zip.
For Windows:https: //dl-ssl.google....ls_r19.0.1-windows.zip.
For MacOSX:https: //dl-ssl.google....ols_r19.0.1-macosx.zip.
Also links to the latest versions of Platform Tools can be found in the SDK-repository. Come on the link and in Xml looking for a platform-toool * .zip string corresponding to your version of the OS. Then download it by referencehttps: //dl-ssl.google....ry/platform-tools*.zip.. After we downloaded platform-tools_r19.0.1-windows.zip (in my case it is the version under Windows), unpack it into a separate folder and make ADB Kill-Server, and after ADB Devices. If you are all done correctly and you have version 1.0.31 - the device status will change with offline on unathorized, and when trying to make the following using ADB, an authorization request will appear on the device screen. Accept RSA FingerPrint on the device - after which ADB is running.

Link to the originalADB Device Offline

The display and truth from LG was, another recovery on the link from the cap helped.

euseller,
In this thread somewhere flashed the game Gapps-Arm64-6.0-pico.zip, which is suitable foruntouched Chinese firmware, look. OpenGapps may not come up, high likelihood of errors, except the PICO version has chances.

Post has been editedtheZest - 07.10.16, 18:20