Assistant
We strongly recommend to readRules section "Android - firmware"
New threads need to be created only inroot partition! In the future, they will be processed by moderators.
REPLY |
Xiaomi Redmi Note 3 Pro - MIUI firmware |
Message#2 06.03.16, 11:00 | |
Experienced [offline] Group: Friendssavagemessiahzine.com Messages 512 Check in: 09.07.12 Xiaomi Mi Mix 2S 6/128 Reputation: 116 | I apologize to kaneshna, how did I install Google play? All the necessary things are in the Google installer This one that I attached from Xiaomi Attached files Google installer ???????. Apk(1009.36 KB) Post has been editedMannur - 27.08.16, 21:15 -------------------- If you are a pigeon in a dovecote and are sitting above the others - this does not mean that you can crap at everyone below. |
Message#3 14.03.16, 13:55 | |
Experienced [offline] Group: Friendssavagemessiahzine.com Messages 512 Check in: 09.07.12 Xiaomi Mi Mix 2S 6/128 Reputation: 116 | [email protected], 13:43 Mistakilla, the firmware for your link is an archive for recovery? From it you can gash version for Mi flash? Is there any chance of installing it with a loader in some way? For Redmi 3, for example, it is adapted for MiFlash from the multirome even. Sewn with a locked bootloader. There is. I figured out how to even raise a brick. 1 way. (If the phone is not Kerpich) Open the settings. We are looking for developer option. Turn on adb debug there Open a terminal window and write adb reboot edl. Wellcome phone switched to flashing mode via miflash 2 way (if the phone is kerpich) Clamp 3 buttons (volume +, volume-, power) connect the phone to whom We wait until the body turns on (will show the icon mi) release the power and hold the volume buttons. On the computer is determined com diagnostic 900e We continue to hold the buttons. After 10-15 seconds, the phone switches to loader 9008 mode for flashing miflash. The second option is not described anywhere. I had to search for the dock by snepdregan. This is how it is. Post has been editedMannur - 27.08.16, 21:09 -------------------- If you are a pigeon in a dovecote and are sitting above the others - this does not mean that you can crap at everyone below. |
Message#4 14.03.16, 21:04 | |
WAR. WAR NEVER CHANGES! [offline] Group: Friendssavagemessiahzine.com Messages 829 Check in: 15.06.11 Xiaomi Mi 5S 3/64 Reputation: 400 | GLOBAL FIRMWARE KENZO 7.1.7.0 FIXED Global 7.1.8 TWRP Although Xiaomi was putting sticks in the wheels, I successfully removed everything that I laid out in the morning and what slipped into the office. Forum, only for Indian devices initially)) But now everything is ok))). The admins gave it to me, but only warnedindianInitially mobiles, I said ok and started picking it, if you just flash it, what they gave me, we get ala softbrick, bootlup and tear our hair))))) Instructions on firmware: 1) Get unlock bootloader 2) PutTWRP 3.0 3) Go to the recovery, make a full backup and transfer it to the computer! 4) Make a facie reset 5) Copy the firmware to the internal memory and flash Profit!Special thanks to my testersashkapermHe tested my successful and not successful creations, you can slap him + After all, I still have a locked bootloader))) DownloadHERE! Developer Room (Global)HERE I will add one, after my firmware, if I flash the original image through the update, the recovery will fly off, but the phone will become a virgin Indian version! We cannot check for Loku Bota yet, for we are waiting for the evening! Everything is checked! This way you completely transform the Chinese version into a global one. Post has been editedMannur - 27.08.16, 21:02 Reason for editing: Added at the very bottom! -------------------- War. War never changes! |
Message#5 15.03.16, 11:35 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 157 Check in: 14.12.10 Xiaomi Redmi Note 3 Pro Prime Reputation: 36 | Getting the root. Option 1 Procedure:
A source: Chainfire developer blog:Google+/ Mods fromCobra111111: ® SuperSU (Post Cobra111111 # 49516322) Option 2 It is also possible to simply replace the stock recovery in the firmware with a custom one without unlocking ... and flash it through MiFlash. In more detail the whole process is described here:Xiaomi Redmi Note 3 Pro - MIUI Firmware (OS 5.x - 6.x) (Post byboyko # 51003896) Items 1 to 3.1 Well, then flash the archive itself with the root. Post has been editeddantist_140 - 17.11.16, 16:45 |
Message#6 17.03.16, 06:23 | |
WAR. WAR NEVER CHANGES! [offline] Group: Friendssavagemessiahzine.com Messages 829 Check in: 15.06.11 Xiaomi Mi 5S 3/64 Reputation: 400 | General instructions for firmware via MiFlash + Unlock boot + TWRP recovery Requirements Everything is taken from the topic headings! For pure sewing on any firmware you need:
All further actions will be shown on the example.Windows 7 x64bitIt is assumed that the system is installed on diskWITH:and all programs installed in the guide are set on the default path! Procedure
WHO HAS A PERMISSION TO UNLOCK THE BOTTLOADER Requirements Everything is taken from the topic headings!
All further actions will be shown on the example.Windows 7 x64bit It is assumed that the system is installed on disk WITH: and all programs installed in the guide are set on the default path!
Do not forget to say thanks to the userKicum He noticed that you can put the developer room on top of globalki! but we all forgot () Xy, few people know what it is, but it exists)))) they don’t give it to anyone, but we still have it, even on MIUI.com they haven’t posted it yet)))) Post has been editeddantist_140 - 28.07.16, 11:32 Reason for editing: Spoiler -------------------- War. War never changes! |
Message#7 18.03.16, 11:13 | |
Veteran [online] Group: Friendssavagemessiahzine.com Messages 1705 Check in: 10.10.10 Reputation: 132 | It means that. If someone (like me) with the firmware recovery (twrp), the installation passes, but does not enter the recovery itself (the place of it is the phone drawing), you need to install it via the fastboot. 1. upload files from the twrp folder along the path C: \ adb, rename the file RN3_kenzo.img to recovery.img 2. type the following commands cmd cd C: \ adb fastboot erase recovery fastboot flash recovery recovery.img fastboot erase cache Install the patched please rut.All) Thanks for the help - varalex: thank_you: |
Message#8 19.03.16, 13:15 | ||
Novice [offline] Group: Active users Messages 31 Check in: 06.12.06 Reputation: 8 | My instructions on how to make a phone brick from the firmware. (Bootloop) (The instructions for scratching are attached.) The process of obtaining bricks: The process of obtaining bricks: They gave me a phone with raw firmware (in my opinion it was 7.1.99.99, I don’t remember exactly). Was standingWindows 10 x32 . We act according to the instructions described in the header -GENERAL INSTRUCTION, FROM AND TO! . On6th paragraph had to additionally put MiPCSuite (in the same instruction, in the requirements - MiPhone Manager ), after that the drivers were installed normally. On10th paragraph we get - " Not enough memory to process the command. (0x80070008) ": Phone reboot, it hangs on the logo "MI ". adb devices sees it as connected " device ": adb reboot edl - reboot the phone, the red indicator starts to flash, the COM-port appears: Repeated firmware via MiFlash gives the same result - "Not enough memory to process the command. (0x80070008)" Disconnect the cable, the phone stops flashing red, clickVol + & Vol- (I do not remember what is happening without pinching), we connect the cable, the red display lights up, we get an unknown device: MiFlash does not see, drivers are not substituted, adb is empty. What can be done with the phone in this state: 1. Power (~ 5 sec) - reloads the phone 2. Power + Vol + - reboots the phone in the Recovery mod, adb devices gives out sideload , adb reboot edl just restarts the phone. 3. Power + Vol- - reboots the phone in FastBoot, adb gives nothing sensible. 4. Fastboot + Vol- (~ 50 sec.) - Turns off the phone. 5. Phone off + Cable plug - the phone shows the% battery charge and most likely starts charging, adb gives nothing. Spreading process: I tried to follow the instructions on another computer and laptop withWin7x64 , drivers on " USB MTP device "was installed with an error adb devices saw offline either sideload with recovery mod. Installed on computerWin10x64_Eng , acted on the above instructions, on 6th paragraph, as the first time, I had to put MiPCSuite . adb devices showed offline with the logo "MI". Did the following: Booted inWin10x32 adb devices - " device " adb reboot edl - right away as soon as the phone screen went out, pulled cable , the display did not light up . Rebooted inWin10x64_Eng , with pre-installed drivers. Pre went to"C: \ Program Files (x86) \ Xiaomi \ MiPhone \ Qualcomm \ Driver"on fileqcser.inf right click ( PKM ) - To install . I connected the phone and then a new device was found, the drivers were installed automatically and a COM port appeared: Further according to the instructions from10th item. Of course, if you can’t restart your phoneadb reboot edl , he is unlikely to help here, but you can try. Apparently in my case, eitherWin10x32 I knew something extra, to work with the phone, or the phone trusted Windows, with which I started the firmware process, I can not say for sure. I hope someone will help. Post has been editedMannur - 27.08.16, 21:08 | |
Message#9 19.03.16, 19:18 | |
status quo [offline] Group: Friendssavagemessiahzine.com Messages 5029 Check in: 08.02.11 Pocophone F1 6/64 Reputation: 3060 | I understand correctly that all files from a folder with TWRP need to be copied to adb? Mini instructions for using the utilityfastboot If you are flashing in modefastbootthen all the files you want to upload to the device should be placed in the folder with the filefastboot.exe. There also usually lies andadb.exebut he has nothing to do with it. The recovery file or the boot.img file can be named as you like, the main thing is that on the command line you write the exact name of the file that you are stitching. If the file has a nameboot.img, the command is written with this name. Enter the phone modefastbootkey combinationVolume-andPower buttonat the same time. A hare will appear in a hat, then the phone is in modefastboot. Next we enter the directory on the computer where our files are located. I have, for example, on the diskWITHhave a foldertoolsin which the tools for working withadbandfastboot. There usually throw files.imgfor firmware. I run the command line on the computer. I enter the teamcd C: \ toolswhich means changing the directory to C: \ tools. Next, I enter the commandfastboot deviceswhen connected by USB phone modefastboot. The command line interface displays the device identification number (a combination of letters and numbers unique to your phone). If this does not happen and the list of devices is empty, then your phone is not connected. Either a problem with firewood, or with a connection. Suppose that the phone is defined. Next, enter the command fastboot flash boot boot.img So we requestedboot.img. If you need to flash recovery, then do the same. The recovery firmware command looks like this: fastboot flash recovery recovery.img fastboot flash recovery twrp.img I hope it is clear. After flashing the file, you can enter the command: fastboot reboot fastboot boot twrpXXX.img You pushEnterand the phone should boot into TWRP virtual recovery. You work in recovery. You install everything you need (RTH, patches, etc.). Rebooting into the system and virtual recovery is no longer necessary. Until the next dive into it in a familiar way. Fastboot utility commands fastboot devices - a list of devices connected to the computer (used to test the connection) fastboot reboot - device reboot fastboot reboot-bootloader - reboot the device in the bootloader fastboot flash boot filename.img - kernel firmware included in boot.img flashboot flash radio filename.img - firmware radio module fastboot oem lock - close the bootloader. fastboot oem unlock - open bootloader (erases all user data) Not all teams worked for me. check. Who does not have these tools, I suggest an archive with a foldertools . tools.rar (849.73 KB) Inside are two utilitiesadb.exe and fastboot.exe . Unzip to root WITH and use the instructions above. Post has been editedMannur - 27.08.16, 21:07 Reason for editing: spoiler and archive -------------------- "Of all the arts, cinema is the most important for us ..." as well as TWRP firmware and recovery modes for many devices |
Message#10 21.03.16, 22:45 | |
a guest [offline] Group: Users Messages 7 Check in: 05.10.12 Sony Ericsson Live with Walkman Reputation: 24 | Finally. Raskirpichil. Through the test point. I tried all the ways - but this, of course, the latest and universal. And, as it turned out, very simple. http://en.miui.com/thread-245347-1-1.html http://choimobile.vn/t...wnload-mode-edl.65098/ You can add to the header, as a radical 100% working solution. From me a couple of words: Nothing complicated, the body is removed with a fingernail as in the video. couple of important points: 1. (corny) do not confuse the screws - they are different in length and color. 2. If you have not noticed on the video - under the tiny sticker "Mi" there is also a cog. 3. The small bus connectors (from the volume buttons on the left and another on the right) are opened by prying up (with a fingernail, toothpick) of the black back. 4. Four connectors at the bottom (antenna (FM?), Battery, display and USB) do not need to open. just ward off the board like a video. 5. when you get to the back side - do not repeat the mistake of the author of the video - do not try to peel off the big figured black sticker (this is copper foil) - there is a small rectangular hole in it to access the pins. 6. If you overloaded the computer while the device was in the EDL and the device stopped responding and being determined in general, you always have the acb-to-board connector at hand. can poke out-stick in case of a dead end. 7. When disassembling the camera, do not touch it - I do not advise it - and do not pull it out of the board. and it is also desirable to carry it out in a "dust free" room. even though the eyes of the cameras are microscopic, it is not enough. 8. If you slightly pulled the display bus out of the clip in the heat of the work, as I do - it also opens by prying up, but already at the front part (into which the wire enters) 9. Well, just in case - the very first movement after removing the cover is to remove the touchscreen plug from the motherboard with a fingernail. I wish everyone good luck - it's easier than it seems. I managed ten minutes. Post has been editedMannur - 27.08.16, 21:08 |
Message#12 04.04.16, 13:35 | |
User Researcher [offline] Group: Friendssavagemessiahzine.com Messages 2576 Check in: 11.05.13 HTC U11 Plus 6/128 Reputation: 4298 | Who needsOPERATORS LOGOin sitebar near antenok, needroot-rights required. NotoColorEmoji.rar(2.07 MB) Unpack and throw the file intosystem / fontswith the replacement (do not forget to keep the original) and setting rights as near in the fonts and use: in the keyboard where the menu is different - emoticons, etc., we select the crown, we put our operators on the SIM cards and enjoy, watch screenshots: Madepatch for installation via TWRP recovery Logo_Oerator.zip(2.21 MB) P.S.Logo suitable for any firmware. thankbetep_okfor work, the file took somewhere from hereDiscussion topics for MIUI v6 / v7 ProgramSimCardColorer_for_MIUIv6_1.04andSimCardColorer_for_MIUI-7_android-5x.for operators logos in the callAlcatel One Touch Idol X 6040 - MIUI Firmware (andrey_artphoto Post # 39489886) Screenshot The program to create patches to changeoperator logos on MIUI 8 Xiaomi Redmi Note 3 - Official MIUI 7/8 firmware (OS 5.0.2) (andrey_artphoto # 50630513 Post) Post has been editedAndreyZo - 29.06.16, 19:11 Reason for editing: added a program for operator logos on MIUI 8 -------------------- My works About myself |
Message#13 05.04.16, 23:36 | |
Angry doctor! [offline] Group: Curators Messages 10710 Check in: 07.06.10 Xiaomi Mi Max 2 4/64 Reputation: 1722 | Disable driver signature verification Disconnect using special boot options In the first case, open “Pparameters� � �Change computer settings". In point "Upgrade and Repair"Select"Recovery", Then - special download options and click"Reboot now�. After reboot, selectDiagnostics, then - Download options and click "Restart".On the screen that appears, you can select (with the numeric keys or F1-F9) the item “Disable mandatory driver signature verification�. After loading the operating system, you can install any unsigned driver. Disable using Local Group Policy Editor The next way to disable driver digital signature verification is to use the Windows 8 and 8.1 Local Group Policy Editor. To launch it, press the Win + R keys on the keyboard and enter the commandgpedit.msc In the local group policy editor, openUser Configuration - Administrative Templates - System - Driver Installation . After this, double click on the item “ Digital Signature Device Drivers �. Select "Enabled", and in the "If Windows detects a driver file without a digital signature," select "Skip." That's all, you can click "OK" and close the local group policy editor - checking is disabled. Post has been editedMannur - 27.08.16, 21:13 -------------------- |
Message#14 06.04.16, 23:36 | |
User [offline] Group: Friendssavagemessiahzine.com Messages 80 Check in: 11.02.12 Reputation: 0 | guys, there is such a problem! I sewed on the instructions through the fastboot on 7.1.8.0 with the substitution for an unlocked bootloader! The phone booted up, everything is fine, then I put TVRP on the instruction! Everything went well! but the devil pulled out of the TVRP again to flash 7.1.8.0, as a result, he received a permanent MI logo. when trying to re-enter the TVRP, black screen and reboot! when enabled, the fastboot mode is defined as Diagnostics 900E (COM10)! In MiFlash is not defined as COM10, but asd2bdb40e! When trying to flash, it gives outunrecognized error (0x8004005: FAILED remote device is locked. Cannot flash images) the first time I flashed normally, without glitches and the first time, it means the problem is not related to the drivers and operating system! (x64 Windows7)! Having read the instructions for scratching, I found a difference in the fact that for all the devices everything was exactly defined as COM 9008, and not like my Diagnostics 900E! I ask for help, thoughts and ideas out loud! |
Message#15 11.04.16, 12:30 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 117 Check in: 17.10.11 Xiaomi Redmi Note 3 Pro Prime Reputation: 5 | serg_tvr, If someone translates IT and puts it in a hat, I think the bricks will be slightly reduced. Adapted translation of instructions for creating from the official firmware .zip file suitable for flashing from TWRP without scaling the phone. The original with illustrations here:http://en.miui.com/thread-257262-1-1.html Posted by raaj52. Adapted translation of the instructions for creating from the official firmware a .zip file suitable for flashing from TWRP without scaling the phone: Now we can easily unlock the bootloader in an official or unofficial way. Mogiy then try to flash the official firmware for recovery from TWRP, just like any other zip file being flashed. The result is a BRICK. In this post, I will explain how to modify the official firmware for recovery to get the firmware, safely flashed through TWRP. Standard warning: I am not responsible for rigged devices, dead SD cards, thermonuclear war, or for what you will burn (will be fired) due to the failure of the alarm application. Requirements: 1. Unlocked bootloader. 2. Installed TWRP. 3. Computer with Windows. 4. WinRar / 7zip. 5. Patience. 6. Backup. 1. Open the official firmware in zip format using WinRar / 7zip. 2. Locate the emmc_appsboot.mbn file in the open archive and delete it from the archive (this may take a long time, depending on the performance of the computer, be patient). 3. Download the modified emmc_appsboot.mbn via the following link https: //drive.google.c....elwRcv3VTRwOTRfalhSTUk (all thanks to @magdad for his amazing work). 4. Drag (using Drag and drop) the modified emmc_appsboot.mbn to the open archive (to the same place where the original version of the file was deleted). At the same time, in the archiver's dialog box, click OK and DO NOT change other parameters (compression method, archive format, etc.). 5. Download the hacked boot.img for your firmware version from http://www.miuidroid.com/rn3/boot_images/ (again, all thanks to @magdad for his amazing work). If you did not find the modified cracked_boot.img for your firmware version - do not worry, we have a great thread @ feds64. Follow the procedure described in the thread to create your own cracked boot.img. http://en.miui.com/for...ight=android%2Bkitchen 6. Rename the downloaded cracked_boot.img to boot.img. 7. Delete the original boot.img from the archive with your firmware. 8. Drag (using Drag and drop) the modified and renamed boot.img to the open archive (to the same place where the original version of the file was deleted). At the same time, in the archiver's dialog box, click OK and DO NOT change other parameters (compression method, archive format, etc.). 9. Now you have made your own official firmware flashing through TWRP. Copy the firmware to your phone and reboot into TWRP. 10. Make Wipe cache, Dalvik cache, System and Data from TWRP. Do not clear the Internal Storage! 11. Select Install and select your .zip. 12. Make Wipe Cache / Dalvik caсhe. 13. Reboot. You did it! Happy stitching! Note: I personally tested this and my RN3 works fine. If you do not understand what is written above or you cannot do it - stay away from this instruction, because you easily ruin your phone. If the phone does not boot or does not turn on - you can try to pick up the phone with the help of this thread (splitting the phone)http://en.miui.com/thread-235865-1-1.html (thanks and thanks @Muz_paray). I will add an adapted translation of the instruction: how to make your modified boot.img for flashing the official firmware version via TWRP. Original here:http://en.miui.com/for...ight=android%2Bkitchen Posted by: feds64 How to make your modified boot.img for flashing the official firmware version via TWRP. 1. Download Android Image Kitchen Tool and unpack. http: //forum.xda-devel...d=3638835&d=1454959265 2. Download the .zip image of the official firmware you need for recovery. Unzip it, find boot.img and put it in the folder with Android Image Kitchen. (next to the files cleanup.bat, repackimg.bat, unpackimg.bat). 3. In the above folder, right-click the boot.img file and drag it to the unpackimg.bat file (the "Open with unpackimg.bat" dialog will appear). Unpacking is performed in command line mode. 4. Go to the ramdisk folder and find the file fstab.qcom. 5. Open the fstab.qcom file with any text editor and use the "search" function to find in the text all the values "verify" (without quotes, exactly as written, without a space between the comma and the word) and carefully delete them. Save the file. Example: from the text “wait, verify / dev / block / bootdevice / by-name / userdata” we get “wait / dev / block / bootdevice / by-name / userdata”. 6. Now we need to pack the modified boot.img. Run the repackimg.bat file, this will create a new boot file called image-new.img. (Before transferring the image-new.img file to the firmware, rename it to boot.img). 7. So you made a modified file with the modifications that are required in order to flash through TWRP. WARNING: At your own risk. Firmware can turn your phone into a BRICK. Post has been editedMannur - 27.08.16, 21:08 |
Message#16 12.04.16, 02:23 | |
Local [online] Group: Friendssavagemessiahzine.com Messages 317 Check in: 14.02.09 Xiaomi Mi Mix 2 Reputation: 95 | The modem will only be flashed with an unlocked bootloader! Instructions for installing a modem from Global 7.1.7 on any other firmware: 1.Download modem fileNON-HLOS.bin 2. Throw in one folder with fastboot.exe 3.Proshit team fastboot flash modem NON-HLOS.bin UPD: I tried to flash a modem from Global 7.1.7 on Xiaomi.eu 6.4.9 - 4G appeared on the first slot (Speedtest 24Mbit / s issued). UPD2: The second slot also has 4G. The reception level shows less than Global 7.1.7, but the speed and stability of the network is the same (c 4G does not fly off even if there are no reception strips). Post has been editedMannur - 27.08.16, 21:07 |
Message#17 12.04.16, 22:46 | |
Local [offline] Group: Friendssavagemessiahzine.com Messages 156 Check in: 21.07.12 Xiaomi Mi Mix 3 6/128 Reputation: 27 | Recovery / Change Imei What is required: 1) Presence of root rights 2) A set of tools fromIMEI restore tools.rar(16.6 MB) 3) Any hex editor This guide is based onthis materialfrom comrade DrWillz, for which he has a separate respect. However, the approach was changed in favor of editing the qcn file (which allows you to change both Imei), rather than the values in the phone itself. All this is done at your own risk! - Unpack the contents of the archive - Open the imei.qcn file with a hex editor and look for values 08 8A 96 72 01 42 99 81 05 - Sim1 08 8A 96 72 01 42 99 81 86 - Sim2 The Imei data, judging by the site, is valid, but I generated them to be something to rely on. - Open the program Imei Converter from the archive, enter the target decimal Imei in the left margin and get its hex version - Replace the received hex version of one of the imei in the file (or both), save - Turn on USB debugging, if this has not already been done - Go to the unzipped adb folder (you may already have a similar one) - Enter the command adb devices and make sure the phone is detected (or we check that debugging is enabled and debugging with BB is enabled) - Next, enter and confirm access root on the phone when prompted adb shell su setprop sys.usb.config diag, adb At this point, the phone will disconnect from the debugging interface, but this is normal, the device has entered diagnostic mode. Go to the device manager and check that Com-port diagnostics has appeared. - Among the unzipped material we find and install QPST (better immediately with msi) - Run QPST and see if the phone is found. - If the phone was found immediately go further, if the window is empty go to the Ports section and add the COM port that appears. The device showed up. - Go to the menu StartClients ->Software Download - In the window that appears, we are interested in two tabs: Backup and Restore. If you can, it’s best to back up your current settings. - Go to Restore, specify the modified .qcn file and click Start. The firmware process will take a couple of minutes, after which you need to reboot the device. Post has been editedMannur - 27.08.16, 21:04 |
Message#18 16.04.16, 17:20 | |
Ancient [offline] Group: Friendssavagemessiahzine.com Messages 992 Check in: 27.03.10 Reputation: 146 | FAQ (Frequently Asked Questions) General questions on firmware, root, unlock, etc.
Solving problems with ADB, fastboot, MiFlash, driver, scratching When the following messages appear in MiFlash: - destructive crash 0x8000ffff - not enough memory to process the command (different code) - send configure command (more than 3 minutes) - receiving hello package (more than a minute) - end of file reached (different code) - required resource is busy It is necessary to disconnect the cable from the phone, wait 3-5 seconds, hold down the power button and hold for a long time until the mi logo appears, then release. After loading the phone, flashing the body again by connectingUSB cable to another connector (only not USB3.0). The phone should only be in fastboot edl mode. You may also need to restart the PC, and once again - check all the drivers. If all else fails, then you need to remove all usb device drivers viaUSBDeviewand try to install zanogo. If the "HS-USB Diagnostics 900E (COM-xx)" equipment is observed in the device manager, it means that the phone's CPU has switched to the service mode. The solution is above. Installation of the Qualcomm (Relink) HS-USB QDLoader 9008 driver requires installationMi PC Suite. • To transfer the phone to EDL, if nothing helps (for flashing via MiFlash / MiPhone), you can try holding down the volume buttons (both), connect the USB cable (the phone must be turned off). The command in fastboot to check the status of the bootloader. fastboot oem device-info We leave the native recovery intact for OTA updates, having root and unlock. It is not necessary to flash TWRP, it is possible to load it separately, without affecting the native recovery. Put last imgformTWRP to the folder with fastboot and rename it to twrp.img. Execute the commandfastboot boot twrp.img. After the reboot, the native recovery will remain. After switching from MIUI8 or CM13 (Android 6.0.1) to any previous firmware (Android 5.1.1)blocked boot. To re-unlock useMiFlashUnlock. For those who like to look for workarounds for the firmware of the device, without installing Windows, being in * nix systems. It does not follow flashing the phone through the "virtual machine". There is a high probability of problems or getting bricks . When trying to flash a modem from MIUI firmware to custom (CM, AOSP, etc.) or when switching from custom to office. firmware without following the rules for downgrade - getIMEI reset. Simple interface to log into EDL, Fastboot and recovery. From SW.benzolifinil . Xiaomi Redmi Note 3 Pro - MIUI Firmware (OS 5.x - 6.x) (Post benzolifinil # 58646193) For those who have Mi Account blocked. From SW.all1651 . Xiaomi Redmi Note 3 Pro - MIUI Firmware (OS 5.x - 6.x) (Post all1651 # 58314937) Instructions for unlocking LTE band 20 for our device (conditional unlocking, because there is no hardware support). From SW.klever3 . Xiaomi Redmi Note 3 Pro - Official firmware (Post klever3 # 50022522) Working with the efs section. Write and read partition with locked bootloader. Backup and rewrite IMEI / MAC / MEID and more. Thank you so much.emusic . General principles of restoring bootloaders on Qualcomm (Post emusic # 50332273) Repair IMEI after unsuccessful modem firmware. From SW.Woodman46 . Xiaomi Redmi Note 3 Pro - MIUI Firmware (OS 5.x - 6.x) (Post WoodMan46 # 49811592) How to make a backup in TWRP. From SW.dantist_140 . Xiaomi Redmi Note 3 Pro - Official firmware (Post dantist_140 # 48969554) Splash method from the forum en.miui.com. http://en.miui.com/for…=viewthread&tid=257227 Post has been editedgrandgreed - 12.03.17, 02:39 |
Message#19 18.04.16, 13:38 | |
Experienced [offline] Group: Friendssavagemessiahzine.com Messages 552 Check in: 10.09.10 Xiaomi Redmi Note 5 Pro Reputation: 26 | I have been fighting for 4 days in an attempt to revive a brick. It is impossible to transfer to the EDL mode even by closing the contacts. The loader is locked, it loads only fastboot. Okirpichen after neofits. unlock and firmware via TWRP with patch.butom |
Message#20 19.04.16, 08:56 | |
Angry doctor! [offline] Group: Curators Messages 10710 Check in: 07.06.10 Xiaomi Mi Max 2 4/64 Reputation: 1722 | How to make a backup in TWRP
PS: More information about TWRP can be found in this topic: TWRP recovery FAQ Post has been editedMannur - 27.08.16, 21:06 -------------------- |
Message#21 22.04.16, 00:45 | |
Contrabashka [offline] Group: Friendssavagemessiahzine.com Messages 1201 Check in: 15.06.11 Xiaomi Mi 6 6/64 Reputation: 285 | now indulged with unofficial unlocking. (I am writing this remark, because I have not seen anything like this in posts) caught the next moment (so far I can’t confirm it, because a one-time accident could have taken place) - if the “unlocked” bootloader is flooded via MiFlash (along with firmware), if you don’t perform a unlock operation (fastboot oem unlock-go), then the phone goes away in "soft brick" (shuts up on Diagnostic 900E). and notest points give nothing(tested on a clean Win7x64 system, with which QDLoader 9008 has already returned). then it turned out that I had the unlocked bootloader flooded! I rebooted into fastboot and unlocked it. after which the body normally loaded ... China Dev 6.4.14 firmware 1. "unlocked" bootloader does not allow to boot in 9008 2. (conclusion following from item 1) it is possible that this "unlocked" bootloader is NOT from XRN3Pro UPD. Apparently, the matter is different, because the body already does not want to go into 9008 :( Post has been editedjaddar - 22.04.16, 07:55 -------------------- Mi6 6/64 Black / A 8.0 / MIUI 9.3 / EU 8.1.11 Shl. if sho - look in skyrim |
mobile version | Now: 05/11/19 09:36 |