Xiaomi Redmi Note 5 - MIUI firmware
under the messages to which you want to add links. 
fackstrot , But I'm afraid will not help, say miflash sypit mistakes, so wait until someone will be able to overcomeGuys, a couple of questions:
1. The update menu, if you go to the list of changes, writes that there is no access to the journal update. It should be? Phone a new, not unlock anything, ROSTEST
2. If you go to Mi account, there is an inscription that the account is not verefitsirovan how to verify and is it all necessary?
Post has been editedbatt13 - 11.07.18, 16:07
1. The update menu, if you go to the list of changes, writes that there is no access to the journal update. It should be? Phone a new, not unlock anything, ROSTEST
2. If you go to Mi account, there is an inscription that the account is not verefitsirovan how to verify and is it all necessary?
Screenshots
 |
 |
Post has been editedbatt13 - 11.07.18, 16:07
Reason for editing: Error
Announcement for those who got the brick.
What happened - xiaomi unannounced introduced new loaders with new signatures, or roll back the installation custom firmware results in brick.
All known methods of repairing do not work.
Solving the problem - only the new firmware under the fastboot, while just sitting waiting, do not pull, we can be recharged.
While it is not yet a corpse, Scene too long will not help.
P.S. One Horsham forumchanin trying to get us a server xiaomi closed factory firmware nademsya.
Good day to all. Spread among the residents of your housing department:Xiaomi Redmi Note 5 Global / Note 5 China- unofficial firmware (Post noteMASTER_11 # 75005231)
In short:roll back to 8.7.9 will make your device nonrecoverable (So ​​far no methods) brick .
Post has been editedCrazyzyman - 12.07.18, 12:28
In short:roll back to 8.7.9 will make your device nonrecoverable (So ​​far no methods) brick .
Post has been editedCrazyzyman - 12.07.18, 12:28
Reason for editing: In the header
Masik в„ў U 1.4
Updated: July 12, 2018 (14:40)
LOADER will not be upgraded, so from this firmware can be rolled back to any version of MIUI.
BOOTLOADER WILL NOT BE UPDATED, SO WITH THIS ROM YOU CAN DOWNGRADE TO ANY VERSION OF MIUI.
REFERENCE TO POST WITH FIRMWARE
Successful use. For any questions you can always come to me in a PM.
Post has been editedStaseg-preved - 12.07.18, 15:07
Updated: July 12, 2018 (14:40)
LOADER will not be upgraded, so from this firmware can be rolled back to any version of MIUI.
BOOTLOADER WILL NOT BE UPDATED, SO WITH THIS ROM YOU CAN DOWNGRADE TO ANY VERSION OF MIUI.
REFERENCE TO POST WITH FIRMWARE
Successful use. For any questions you can always come to me in a PM.
Post has been editedStaseg-preved - 12.07.18, 15:07
I came to fastboot
whyred_global_images_8.7.12_20180712.0000.00_8.1_global_e775b9c0d5.tgz
http://en.miui.com/a-234.html
one brick - try
Post has been editeddron3d - 12.07.18, 16:08
whyred_global_images_8.7.12_20180712.0000.00_8.1_global_e775b9c0d5.tgz
http://en.miui.com/a-234.html
one brick - try
Post has been editeddron3d - 12.07.18, 16:08
Updated through the air with 8.7.5 on 08.07.12
The menu themes added fonts
More update components from the bottom to the top of the list moved
Post has been editedBloodyskam - 12.07.18, 17:31
The menu themes added fonts
More update components from the bottom to the top of the list moved
Attached images
 |
 |
 |
Post has been editedBloodyskam - 12.07.18, 17:31
Good day, ladies and gentlemen! I sympathize with all okirpichevshimsya - this is real tin, as it is ..: angry:
I also have a question of this kind: unlocked the bootloader, I rolled Masik 1.3 version, I forgot to remove the "Delete Encryption" daw. Now connecting the phone to the PC in Fastbut mode - the phone is rebued in the fastbut without stopping and does not allow anything to do with the recovery. Only in the upper left corner hangs inscription - press any key to reboot. In general, the recovery is locked, it stands native Mi-Recovery 3.0, the bootloader is open. I want to upgrade to Masik 1.4 version, get root-rights and stay on it. By the way, Masika has no problems with AntirollBekk, I have code 3 (who is interested). Tell me how can I roll a custom recovery now? Thank you in advance.
P.S .: INFA for all members of theEDL-mode : Do not spoil the cable, the nerves and the cover of the phone - everything is much easier! The decision to float on the surface, but no one came in handy. Downloading and set this prog. At the first start look at the top line -> ADB Attached - it should be your number devaysa the connected (with a properly installed in the wood). If everything is connected properly, Hit paragraph 2 (Reboot Android), hereinafter referred to paragraph 6 (Reboot EDL (Xiaomi)) and wait for literally less minuty.Telefon he goes into fastbut mode (hare in a fur hat) and immediately goes off the screen and in the system, see "Ports", you will see Qualcomm HS-USB QDLoader 9008 . And that it was necessary to: thank_you:
P.S.S .: carefully prokurivayu theme in solidarity with all seeking solutions to break the deadlock, although the device itself and is working, but I will try all possible ways to help. All good, the beaver and the restoration of bricks!)
A couple of years ago with very namayalis raskirpichivaniem HTC One M7 802W. I had to roll Linux and a couple of days to sit and read the forums until revived device. Yes, Hemorrhoids still that ...: drag:
Post has been editedGvozdOFF - 13.07.18, 02:43
I also have a question of this kind: unlocked the bootloader, I rolled Masik 1.3 version, I forgot to remove the "Delete Encryption" daw. Now connecting the phone to the PC in Fastbut mode - the phone is rebued in the fastbut without stopping and does not allow anything to do with the recovery. Only in the upper left corner hangs inscription - press any key to reboot. In general, the recovery is locked, it stands native Mi-Recovery 3.0, the bootloader is open. I want to upgrade to Masik 1.4 version, get root-rights and stay on it. By the way, Masika has no problems with AntirollBekk, I have code 3 (who is interested). Tell me how can I roll a custom recovery now? Thank you in advance.
P.S .: INFA for all members of theEDL-mode : Do not spoil the cable, the nerves and the cover of the phone - everything is much easier! The decision to float on the surface, but no one came in handy. Downloading and set this prog. At the first start look at the top line -> ADB Attached - it should be your number devaysa the connected (with a properly installed in the wood). If everything is connected properly, Hit paragraph 2 (Reboot Android), hereinafter referred to paragraph 6 (Reboot EDL (Xiaomi)) and wait for literally less minuty.Telefon he goes into fastbut mode (hare in a fur hat) and immediately goes off the screen and in the system, see "Ports", you will see Qualcomm HS-USB QDLoader 9008 . And that it was necessary to: thank_you:
P.S.S .: carefully prokurivayu theme in solidarity with all seeking solutions to break the deadlock, although the device itself and is working, but I will try all possible ways to help. All good, the beaver and the restoration of bricks!)
A couple of years ago with very namayalis raskirpichivaniem HTC One M7 802W. I had to roll Linux and a couple of days to sit and read the forums until revived device. Yes, Hemorrhoids still that ...: drag:
Post has been editedGvozdOFF - 13.07.18, 02:43
A simple program to check the status of anti roll back
Before using the program in a mode Phone Translate FASTBOOT!
Download:
Status anti roll back.exe(4.8 MB)
Post has been editedgyord - 11.08.20, 23:44
Before using the program in a mode Phone Translate FASTBOOT!
Download:
Status anti roll back.exe(4.8 MB)Post has been editedgyord - 11.08.20, 23:44
Reason for edit: Not wearing a hat
It did not seem to
Redmi Note 5 Pro / Redmi Note 5 8.7.12 fastboot
fastboot 8.7.12
Post has been editedeserguei - 13.07.18, 09:26
Redmi Note 5 Pro / Redmi Note 5 8.7.12 fastboot
fastboot 8.7.12
Post has been editedeserguei - 13.07.18, 09:26
TOOLKIT TWRP
by fendyperdana
Decompress in a convenient place ->run "KLIK 2X TOOLKIT INI.bat"
translate laziness - if someone will translate - perezalil!
Download:
TOOLKIT_TWRP_REDMI + NOTE + 5 + WHYRED.rar (108.61 MB)
by fendyperdana
 |
Decompress in a convenient place ->run "KLIK 2X TOOLKIT INI.bat"
translate laziness - if someone will translate - perezalil!
Download:
TOOLKIT_TWRP_REDMI + NOTE + 5 + WHYRED.rar (108.61 MB) Whyred unbrick
(Precast post)
(Precast post)
Part 1: Introduction
A quick write, there will be many edits.
Before you read any further, I highly recommend to get acquainted withby thismessage. You do not need to understand everything at once. Just flip through.
As shown by today (conversation in the QMS) and past debriefing, users generally do not read anything, but quickly get down to business. Matter and problems.
Before you read any further, I highly recommend to get acquainted withby thismessage. You do not need to understand everything at once. Just flip through.
As shown by today (conversation in the QMS) and past debriefing, users generally do not read anything, but quickly get down to business. Matter and problems.
Part 2. Antirollbek
The Xiaomi this took a long time and here's the first result: all through the income statement *.
At the same Samsung, in firmware version, bootloader version available. Where is she here? The question is rhetorical.
Antirollbek - a mechanism prohibiting downgrade software. On platforms Qualcomm implementation of this mechanism it is possible (and recommended) through the processor QFPROM.
At the same Samsung, in firmware version, bootloader version available. Where is she here? The question is rhetorical.
Antirollbek - a mechanism prohibiting downgrade software. On platforms Qualcomm implementation of this mechanism it is possible (and recommended) through the processor QFPROM.
Part 3: Firmware Version
Pro chain downloaders
If you extract any file with the firmware for your device, you will see the following files in it: abl, cmnlib, cmnlib64, devcfg, hyp, keymaster, mdtpsecapp, pmic, rpm, tz, xbl.
All of them are boot loaders. This is the minimum set of components to run the platform. Exactly the same set of files you can see in the firmware of any other device on the same processor.
All feeders (in our case) are digitally signed Xiaomi.
All feeders are composed of three certificates. In one of the certificates listed bootloader version.
If XBL has the wrong version (or just does not work) platform will open the 9008 emergency.
If XBL works, but plugging in one of these downloaders, the platform will open the emergency 900E.
In all other cases, the device falls into the Fastboot or Recovery. But it provided that all the coders have done according to the rules.
All of them are boot loaders. This is the minimum set of components to run the platform. Exactly the same set of files you can see in the firmware of any other device on the same processor.
All feeders (in our case) are digitally signed Xiaomi.
All feeders are composed of three certificates. In one of the certificates listed bootloader version.
If XBL has the wrong version (or just does not work) platform will open the 9008 emergency.
If XBL works, but plugging in one of these downloaders, the platform will open the emergency 900E.
In all other cases, the device falls into the Fastboot or Recovery. But it provided that all the coders have done according to the rules.
Watched a few firmware for your model (figure on the right - loader version chain), it turns out like this:
20180705 8.7.5 Global 2
20180712 8.7.12 China 3
yyyymmdd 8.7.12 Global 3
20180410 9.5.6.0 Global 2
20180629 9.5.17.0 Global 2
20180712 8.7.12 China 3
yyyymmdd 8.7.12 Global 3
20180410 9.5.6.0 Global 2
20180629 9.5.17.0 Global 2
A full list can be found inthis message. Thank you say
Netv : yes2: What you see in the modefastbooton command
fastboot getvar anti
Part 4. About okirpichivanie
MSM_HW_ID: 0x000cc0e1
OEM_PK_HASH: 0xa7b8b82545a98eca23d6e9105fb464568d1b5828264903441bdef0cd57e3c370
SBL SW Version: 0x00000003
OEM_PK_HASH: 0xa7b8b82545a98eca23d6e9105fb464568d1b5828264903441bdef0cd57e3c370
SBL SW Version: 0x00000003
As you can see the SBL (XBL) third version. Version of XBL are registered in QFPROM when you downloaded the 8.7.12 and click the trigger.
After some time, you lower firmware version, which included a second version of XBL. At the start, the main processor in the loader (PBL) sees that the XBL version on a flash drive below that he is registered in QFPROM and opens emergency port for downloading the "right" firmware.
Hoses (Firehose programmers) for your device also have versions. It is believed that now Xiaomi will not die easily (in EDL / 9008 mode), as it was earlier. After downloading the programmer (Firehose), the latter is waiting (or requires) from us some kind of team. Password may not be clear. Those. Now in all devices on Qualcomm, may (and will) implement a specific authentication mechanism. For the firmware of the devices, either additional files or special flash drives will be required. In some cases, it may be necessary to enter the network. Those. Flash heer will knock on the server ..
Part 5. About recovery
miflash log
[9:37:48 COM4]: file C: \ 123 \ images \ prog_emmc_firehose_Sdm660_ddr.elf transferred successfully
[9:37:50 COM4]: send nop command
[9:37:50 COM4]: send command:<? xml version = "1.0"?><data><nop verbose = "0" value = "ping" /></ data>
[9:37:50 COM4]: get response from target
[9:37:50 COM4]: dump:<? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Binary build date: Jul December 2018 @ 1:02:39" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Chip serial num: 4294967295 (0xffffffff)" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Supported Functions: program configure sig nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark readtorageinfo getsha256digest erase peek poke" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Binary build date: Jul December 2018 @ 1:02:39
"/>
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "fh.attrs.Verbose is set to 0" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Chip serial num: 4294967295 (0xffffffff)" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Supported Functions: program configure sig nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark readtorageinfo getsha256digest erase peek poke" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<response value = "ACK" />
</ data>
[9:37:50 COM4]: send configure command
[9:37:50 COM4]: send command:<? xml version = "1.0"?><data><configure verbose = "0" AlwaysValidate = "0" ZlpAwareHost = "1" MaxPayloadSizeToTargetInBytes = "131072" MemoryName = "emmc" SkipStorageInit = "0" /></ data>
[9:37:50 COM4]: get response from target
[9:37:50 COM4]: dump:<? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "ERROR: Only nop and sig tag can be recevied before authentication." />
</ data>
[9:37:50 COM4]: send nop command
[9:37:50 COM4]: send command:<? xml version = "1.0"?><data><nop verbose = "0" value = "ping" /></ data>
[9:37:50 COM4]: get response from target
[9:37:50 COM4]: dump:<? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Binary build date: Jul December 2018 @ 1:02:39" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Chip serial num: 4294967295 (0xffffffff)" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Supported Functions: program configure sig nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark readtorageinfo getsha256digest erase peek poke" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Binary build date: Jul December 2018 @ 1:02:39
"/>
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "fh.attrs.Verbose is set to 0" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Chip serial num: 4294967295 (0xffffffff)" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "Supported Functions: program configure sig nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark readtorageinfo getsha256digest erase peek poke" />
</ data><? xml version = "1.0" encoding = "UTF-8"?>
<data>
<response value = "ACK" />
</ data>
[9:37:50 COM4]: send configure command
[9:37:50 COM4]: send command:<? xml version = "1.0"?><data><configure verbose = "0" AlwaysValidate = "0" ZlpAwareHost = "1" MaxPayloadSizeToTargetInBytes = "131072" MemoryName = "emmc" SkipStorageInit = "0" /></ data>
[9:37:50 COM4]: get response from target
[9:37:50 COM4]: dump:<? xml version = "1.0" encoding = "UTF-8"?>
<data>
<log value = "ERROR: Only nop and sig tag can be recevied before authentication." />
</ data>
send nop command
Programmer it shows all the available commands
"Supported Functions: program configure sig nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke"
Miflesh sends a configuration command
send configure command
send sig command
And if he did not send, I need another flasher. Or something else that the logs are not specified. After talking with several owners of the bricks, which tried thus restore their devices, managed to "isolate" a common point. After entering your account, all of them have seen the same image, such as "Your account is not authorized." Here is the script (or algorithm, as you wish) runs between the teams (see. Log)nopandconfigure.
There on some forum accounts collect ID may be "to authorize manually." Personally, I'm worried about the other question: how (in general) it will (or should) work in the future? So, if I have a new device, the account I have not had time to make all - tube pipe? Let's wait - we'll see.
There is another option. It will be a service programmer (firehose), which does not require authorization. Or something else.
The same problem (in piercing of EDL mode) experienced users Mi 6x, Mi 8, Redmi S2 / Y2. There are bricks.
Part 6. Final
Questionable
Who is now ARB4 Nothing you can not flash the EDL mode. Nothing at all, until the "Authorized Account". That the "authorization" means, in practice, will soon find out.
Who is now ARB3 , The flash mode may EDL any firmware version of the second loaders (and firehose) and not be able to flash the EDL mode EEPROM with a third version of the downloaders. Firehose third version will require authorization (verified).
Who is now ARB3 , The flash mode may EDL any firmware version of the second loaders (and firehose) and not be able to flash the EDL mode EEPROM with a third version of the downloaders. Firehose third version will require authorization (verified).
In connection with the emergence of conflicting information and lack of (the owners working units) of interest in solving the problems, the post is frozen for an indefinite period.
I ask each and everyone (especially the owners of the bricks) are not hysterical, not flood the topic and (especially) the PM.
No need to ask questions that (so far) no answers.
Thank you for your attention: thank_you:
Right now (see. Edit date) information is cross-checked. Too many gaps.
Post has been editedSasha Gray - 17.07.18, 15:53
The reason for editing: cosmetic changes, the reference to a list of boot versions (Part 3)
MIUI 10 EU 8.7.12
Forum EU
DownloadAFH
Warning - there is no mention of antiotkate like masik, if you are on anti 3, can not comment.
Changelog
Lockscreen, Status Bar, Notification Bar Optimization - Face unlocking speed (07-12) Fix The problem of flashing screen in the process of fingerprint unlocking (07-12) Fix Fixed background in PIP mode Themes Fix Fixed themes details loading Fix Fixed Nature sound missing in sounds
Security Optimize New Security Center UI Notification Optimize - Media volume can be 'changed only when media playing (same as in MIUI 9) Camera New -Al Portrait mode for single camera devices (07-06) New AI Portrait mode for the front camera ( 07-06)
Security Optimize New Security Center UI Notification Optimize - Media volume can be 'changed only when media playing (same as in MIUI 9) Camera New -Al Portrait mode for single camera devices (07-06) New AI Portrait mode for the front camera ( 07-06)
Forum EU
DownloadAFH
Warning - there is no mention of antiotkate like masik, if you are on anti 3, can not comment.
Unlock FastBoot teams!
Flashing TWRP! (ARB4)
After the introduction of closed steel ARB4 some fastbuta team, including firmware TVRP.
This method allows you to restart or start twrp fastboot command
1. Download the fastboot-unlock-anti-4-whyred ofattachments
2. The image format .img throw in a folder with adb and there to run the command line
3. Start fastboot, execute this command
fastboot flash antirbpass dummy.img
4. Now you can flash the TWRP, and run any command fastboot.
you have to perform dummy / unlock every time you enter the fastboot, or ARB blocks your commands.
Resembles revert to ARB3
LEADS TO bricks!
Duplicate attachment:fastboot-unlock-anti-4-whyred.zip(178 bytes)
Sourse of information:https: //forum.xda-deve...ing-anti-roll-t3816219
Automated program:
Xiaomi Redmi Note 5 Global / Note 5 China - firmware MIUI (Post gyord # 75082655)
Important! I am not responsible for your actions and the consequences. I'm just sharing the information indicating the source of the original.
Post has been editedCrazyzyman - 15.07.18, 14:26
Flashing TWRP! (ARB4)
After the introduction of closed steel ARB4 some fastbuta team, including firmware TVRP.
This method allows you to restart or start twrp fastboot command
1. Download the fastboot-unlock-anti-4-whyred ofattachments
2. The image format .img throw in a folder with adb and there to run the command line
3. Start fastboot, execute this command
fastboot flash antirbpass dummy.img
4. Now you can flash the TWRP, and run any command fastboot.
you have to perform dummy / unlock every time you enter the fastboot, or ARB blocks your commands.
 |
Resembles revert to ARB3
LEADS TO bricks!
Duplicate attachment:
fastboot-unlock-anti-4-whyred.zip(178 bytes)Sourse of information:https: //forum.xda-deve...ing-anti-roll-t3816219
Automated program:
Xiaomi Redmi Note 5 Global / Note 5 China - firmware MIUI (Post gyord # 75082655)
Important! I am not responsible for your actions and the consequences. I'm just sharing the information indicating the source of the original.
Post has been editedCrazyzyman - 15.07.18, 14:26
Reason for editing: Refinements
for fastingUnlock FastBoot commands! TWRP firmware! (ARB4) collected another easy example program!
you have to perform dummy / unlock every time you enter the fastboot, or ARB blocks your commands
Resembles revert to ARB3
LEADS TO bricks!
Softinkoy sewing section dummy.img and twrp immediately!
antirbpass.exe(36.41 MB)
Post has been editedgyord - 15.11.19, 15:47
you have to perform dummy / unlock every time you enter the fastboot, or ARB blocks your commands
Resembles revert to ARB3
LEADS TO bricks!
Softinkoy sewing section dummy.img and twrp immediately!
antirbpass.exe(36.41 MB)Post has been editedgyord - 15.11.19, 15:47
Way to pick up a brick (my translation)
Original post on XDAhttps: //forum.xda-deve...5-pro-unbrick-t3816178
Right tools:
- version Miflash, which is attached to the post.
- Qualcomm HS-USB QDLoader 9008 driver (attached to the report).
- extreme developer firmware for fastboot (can be found in the header).
important Note
Provide the account ID at the office. Online Xiaomei your brick in the form of a comment in this threadhttp://ru.miui.com/thread-10664-1-1.html
After that, your ID will be registered in the list of bricks and queued for release.
Step 1. Download the latest firmware complexed MiUi 10 to fastboot, and unzip it.
Step 2. Download and install the above drivers (Qualcomm HS-USB QDLoader 9008).
Step 3. Connect your device via testpoint (how to do it is in the subject header)
Step 4: Download, extract MiFlash Tool v.2018.5.28.0.
Open MiFlash Tool.
Select download and unzip the firmware.
Press "Start".
Step 5. Log E account, which is attracted to the device. OTHERWISE YOU WILL NOT BE ABLE beg your device!
Once entered a valid username, then sew
QDLoader HS-USB Driver.7z(13.12 MB)
f267b936-45cd-4b3d-b15a-947fb4b674b1.zip(49.41 MB)
Post has been editedcahta1122 - 15.07.18, 01:45
Original post on XDAhttps: //forum.xda-deve...5-pro-unbrick-t3816178
Right tools:
- version Miflash, which is attached to the post.
- Qualcomm HS-USB QDLoader 9008 driver (attached to the report).
- extreme developer firmware for fastboot (can be found in the header).
important Note
Provide the account ID at the office. Online Xiaomei your brick in the form of a comment in this threadhttp://ru.miui.com/thread-10664-1-1.html
After that, your ID will be registered in the list of bricks and queued for release.
Step 1. Download the latest firmware complexed MiUi 10 to fastboot, and unzip it.
Step 2. Download and install the above drivers (Qualcomm HS-USB QDLoader 9008).
Step 3. Connect your device via testpoint (how to do it is in the subject header)
Step 4: Download, extract MiFlash Tool v.2018.5.28.0.
Open MiFlash Tool.
Select download and unzip the firmware.
Press "Start".
Step 5. Log E account, which is attracted to the device. OTHERWISE YOU WILL NOT BE ABLE beg your device!
Once entered a valid username, then sew
Attached files
QDLoader HS-USB Driver.7z(13.12 MB)f267b936-45cd-4b3d-b15a-947fb4b674b1.zip(49.41 MB)Post has been editedcahta1122 - 15.07.18, 01:45
For owners BRICKS
I will add a little postvovcik3
I know that an accordion, but put because I want to draw attention to paragraph в„–2
Tomorrow is waiting for letters from the Chinese and try to be sewn. Good luck to all of us.
Post has been editedNetv - 15.07.18, 06:44
I will add a little postvovcik3
If you do not have an official service center in your city, or guarantee, you can try this.
Make sure your phone is defined as QHSUSB 9008
1. Open your browser and sign in Russian Forum Miui. Place there MI ID, do not worry, it will be seen only by moderators. Use on Google Translate.
http://ru.miui.com/thread-10664-1-1.html
collection term Mi ID:
16 July 12: 00 [Beijing time (GMT / UTC +8
2. Wait for confirmation of your account, they will send you a message.Standby time up to July 16 12:00 [Beijing time (GMT / UTC +8 hours)
3. Download the latest Miui10 disk fast download 07/08/12 Global
http: //bigota.d.miui.c.../whyr...e775b9c0d5.tgz
4. Login and download the latest Miflash here.
https://c.mi.com/thread-1220989-1-0.html
5. Try using a flash MiFLASH and choose Clean All.
6. If you do not flash, try a power cycle. Disconnect from the PC holding the power button for 20-30 seconds. Try to flash repeatedly.
Make sure your phone is defined as QHSUSB 9008
1. Open your browser and sign in Russian Forum Miui. Place there MI ID, do not worry, it will be seen only by moderators. Use on Google Translate.
http://ru.miui.com/thread-10664-1-1.html
collection term Mi ID:
16 July 12: 00 [Beijing time (GMT / UTC +8
2. Wait for confirmation of your account, they will send you a message.Standby time up to July 16 12:00 [Beijing time (GMT / UTC +8 hours)
3. Download the latest Miui10 disk fast download 07/08/12 Global
http: //bigota.d.miui.c.../whyr...e775b9c0d5.tgz
4. Login and download the latest Miflash here.
https://c.mi.com/thread-1220989-1-0.html
5. Try using a flash MiFLASH and choose Clean All.
6. If you do not flash, try a power cycle. Disconnect from the PC holding the power button for 20-30 seconds. Try to flash repeatedly.
I know that an accordion, but put because I want to draw attention to paragraph в„–2
Wait for confirmation of your account, they will send you a message.Standby time up to July 16 12:00 [Beijing time (GMT / UTC +8 hours)
Tomorrow is waiting for letters from the Chinese and try to be sewn. Good luck to all of us.
Post has been editedNetv - 15.07.18, 06:44
Otklyuchalka applications Root is not needed! Disables system applications(NOT ALL!)
Miuidisabler.apk(414.71 KB)
Post has been editedgyord - 15.07.18, 14:06
Miuidisabler.apk(414.71 KB)Post has been editedgyord - 15.07.18, 14:06
©savagemessiahzine.com2005-2021 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement