Related
Earlier in this week a friend of mine gave me a Redmi Note 3 pro that was pattern lock.
I tried the traditional hard reset hoping to reset pattern lock, but was unable too.
Since the bootloader was locked it was not able to, due to the issue of not being able to go to the recovery menu.
I tried to flashing a fastboot but couldn't because the bootloader was locked.
After some extensive researching throughout the forum I decided to put what I gathered up
and put it to use, I tried a few different methods and came up with many errors. the conclusion is
I figured a method that worked perfectly without having the usb debug mode on.
Perquisites
(note: I only done it on the Redmi Note 3 pro, but i'm sure it will all work the same since the tools are used for all xiaomi devices)
1. Redmi Note 3 (it should work on all xiaomi devices)
2. PC with windows x64 (I did it on Windows 10 x64)
3. MiFlash_2016.03.30.exe
4. Fastboot 7.1.8 rom (get correct rom according to your device, my device is the redmi note 3 pro and use global seem to work best)
Note: Fastboot 7.2.5 Rom is now available, you can use that and skip ota modifying and flashing part:Fastboot 7.2.5 rom
5. unlocked_emmc_appsboot.mbn Recovery flashable
6. Minimal adb and fastboot (or any adb installation)
7. adb edl boot file
8. install necessary drivers
you can find majority of the files in the link below (except fastboot_edl.zip it is provided below). provided by Sudeep Duhoon
http://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
1. first thing you want to do is put your device into fastboot mode, by holding vol down and power button together until device reboots.
it will then shows a anime image of a rabbit and droid being repaired.
since you don't have usb debugging enable, using adb commands in terminal won't recognize the device properly.
(don't worry about this, because it does in a sense recognizes your device in a sense... for me it says cannot find null or something in that manner with null)
2. what we want to do is put our device into fastboot edl mode so we can begin the process of flashing a fastboot rom.
I have provided a link for the fastboot edl boot file that runs the command automatically for you. after downloading the file,
extract it to a folder. located the folder and open edl.cmd, it will automatically put your phone into fastboot edl mode.
(As long as edl.cmd can put your device into fastboot edl mode, you are in the clear.)
3. Next is download proper fastboot rom for your device and extract the files to a foldering using 7z.
located the folder open it and go into the image folder.
4. Download unlocked_emmc_appsboot.mbn Recovery flashable, and extract it to the image folder of
your fastboot rom, it will ask you to replace click yes. if it turns up a error, extract the file to your desktop,
cut and paste the file into the image folder and click yes to replace /overwrite the file.
5. follow the step 10 only in the unlock bootloader from this link http://forum.xda-developers.com/showpost.php?p=66379587&postcount=3
after the flash is finish you are introduce with newly flash and unlocked device.
if the device happens to brick you can always put your device into fastboot mode.
and run the command fastboot aboot emmc_appsboot.mbn
to take yourself out the brick or try reflashing again.
there are many other great articles or fixing your bricked devices or flashing a rom.
******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-
i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD
I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp
Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.
pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img
Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000
XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.
Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...
How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !
Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?
rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?
ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74
Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!
How to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission on the Latest MIUI 8 - V8.0.6.0.LHOMIDG. (as of 22-11-16)
Here you have the step by step procedures to successfully unlock your Redmi Note 3 SnapDragon global variant with latest global stable rom MIUI 8. Please follow the steps carefully.
The rom used for this procedure is the latest global stable fastboot rom MIUI V8.0.6.0.LHOMIDG.
This is the working guide for the Xiaomi redmi note 3 (SD) on latest MIUI 8.0.6.0 as on 22-11-2016. I did lots of experiments, bricked my device several times to find this working guide for latest rom, however you are free to link to this page for reference.
You dont need to apply for official unlocking and wait for a month or more to get the sms confirmation from xiaomi to officially unlock the bootloader, the problem with the official method is many users have reported that they did not receive the confirmation sms from xiaomi, even if they receive the confirmation sms the unlocking process stucks at some percentage and fails to unlock the bootloader. So for everyone here is the easy way to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission.
First of all take a backup of all important files from your phone to your PC before starting. Because all data will be formatted while flashing the rom.
I have simplified most of the procedures and complicated works for this guide. A good part of the credit goes to some other developers because their works were helpful to me for experimenting to find this working full unlocking guide for the latest miui rom for redmi note 3 (SD) as of 22-11-2016.
REQUIREMENTS:
Xiaomi Redmi Note 3 (SD) Mobile
Micro USB data cable (or) compatible usb cable
Desktop or Laptop (Widows based)
Download all the tools, rom and other files from this androidfilehost folder link and keep all files in one folder for easy access:
https://www.androidfilehost.com/?w=files&flid=137618Files List:
1. AnF.zip
2. fastboot_edl.zip
3. Fastboot Rom: "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz"
4. MiFLash_v2016.08.30.0.zip
5. minimal_adb_fastboot_v1.4_setup _working.exe
6. MiPcSuiteSetup_v3.2.1.3111_2717.exe
7. Root Checker Basic v5.9.7.apk
8. SR1-SuperSU-v2.78-SR1-20160915123031.zip
9. twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip
10. ADBdriversetup.zip (alternate use, in case device specific drivers are not properly installed)
***Carefully remove your sim card & sd card from mobile (if inserted) before you begin and do not connect to internet until all steps are completed, because the phone would automatically sync with Xiaomi servers at first boot and may cause problems.
Make sure your phone is charged 60% and above.
The complete video go through of step by step procedures in this guide is available in this YouTube video,
https://www.youtube.com/watch?v=rj4gVMk3y0o
FOLLOW THE STEPS CAREFULLY, IF YOU FACE ANY TROUBLE, START OVER AGAIN FROM STEP 1, IF YOU FACE ANY OTHER ERROR OR BOOTLOOP OR STUCK IN LOGO LOOK AT THE TROUBLE SHOOT SECTION AT THE BOTTOM.
Step 1:
Enable Usb Debugging, if not done before:
Open Settings in your device"Redmi note 3 (SD)", scroll to bottom in settings and click on "About phone" and now tap on MIUI version 7 times, it will show a message like "You are now a developer" and Developer options will be revealed.
Next go back to Settings main screen and then -> Additional settings -> Developer options -> Enable Developer options, Enable OEM Unlock, Usb Debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: After that when you connect your phone to the Pc to execute adb commands, a prompt may appear on your phone with computer's fingerprint key, you should confirm it when it appears. In case if you already done this for your computer with proper adb drivers installed, you don't need to bother about this.
Step 2:
DISABLE DRIVER SIGNATURE ENFORCEMENT IN YOUR PC:
You now have to disable driver signature enforcement in your PC, to do this you have to open the settings window by pressing the shortcuts"Windows button + i -> Update & Security -> Recovery -> Advanced startup -> Restart now. Now the system will logout and show Recovery options, from there select Troubleshoot -> Startup Settings in Advanced options -> Restart. Your system will now reboot and show the "Startup settings" screen, a list of options will be available, you have to choose option number 7 to disable driver signature enforcement. Then the system will boot into the OS with driver signature enforcement disabled. After that do not restart your pc until all the below steps are completed, in case if you restart your pc for any reason you need to redo this step again because system reboot might enable driver signature enforcement again. That's it. Refer this video if you need further guidance.
Step 3:
To install ADB, Fastboot and other drivers in your PC:
Install the " minimal_adb_fastboot_v1.4_setup _working " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiPcSuiteSetup_v3.2.1.3111_2717.exe " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiFLash_v2016.08.30.0.zip " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Step 4:
Extract AnF.zip file and execute the commands:
Now extract the "AnF.zip" file downloaded from the link I provided above. Connect your phone to Pc using the Usb cable. Open the extracted AnF folder and double click on the cmd.exe file, which will open a adb command window from there.
Execute the below command through adb command window to check and confirm the phone is connected via adb interface. If connected properly it should show device serial like "******** device"
adb devices
Incase if your phone shows a prompt for computer's fingerprint key approval, allow it. Then execute the command again. You should see your phone serial number as shown in the image below, which means your phone is properly connected via adb. Incase if the device is not connect properly via adb, disable and enable USB debugging on your phone. If that also helping to install the phone's adb drivers, extract and run the"ADBdriversetup.zip" downloaded from the link I provided above to install the specific drivers for your phone.
Step 5:
Reboot the phone to EDL mode:
Now you have to reboot your phone to edl mode aka Emergency download mode. To do this execute the below command via adb window with phone still connected to Pc.
adb reboot edl
Your phone will now reboot into blank screen or edl mode and new driver named "qshusb qloader 9008" will be installed in your Pc, now only red led notification light will be blinking on your phone. Once the driver is installed properly, the phone is now connected in edl mode. Now close the adb command window.
Step 6:
Setup MiFlash Tool & Flash the ROM:
Open the MiFlash tool (MiFLash_v2016.08.30.0.zip) application you installed earlier, click refresh button and your phone will be visible as port number (ex: COM10) in MiFlash tool. Exe file is in this path,"C:\Xiaomi\XiaoMiFlash"
Now extract the "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz" fastboot rom file downloaded from the link I provided above. In your MiFlash tool window, click the Browse button and locate the extracted fastboot rom folder. Then select "clean all" button at the bottom of MiFlash window. The flash tool is now configured. Now click the Flash button.
Wait for few minutes for the flashing process to complete, once the process is complete and MiFlash tool window will show task finished. But do not disconnect the phone.
Step 7:
Reboot to Fastboot mode & execute Fastboot commands:
Now while the phone is still connected to your pc, reboot your phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the boot screen and release, the phone will now enter into fastboot mode.
Now double click and open the cmd.exe file from AnF folder you extracted earlier to open the command window. Then execute the below command.
fastboot oem device-info
This command will show you the current bootloader status. The bootloader status shows "Device Unlocked: False", execute the below command in command widow, it will Unlock the bootloader.
fastboot oem unlock-go
Your device might restart now, if restarts press Volume down button and Power button simultaneously to reboot phone to fastboot mode again to check your bootloader status again by executing the below command. It should show "Device Unlocked: True" in the command window. Which means the device's bootloader is unlocked.
fastboot oem device-info
Now to flash TWRP recovery and Supersu for root permissions, jump to step 8, or if your aim is to unlock the bootloader only, you may restart your phone and skip all below steps.
Step 8:
Flash TWRP:
Now restart phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the fastboot screen.
Extract the "twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip" file downloaded from the link I provided above to the AnF folder.
Then open the AnF folder, double click and open the cmd.exe file, paste the below command in the command window to flash twrp recovery.
fastboot flash recovery twrp-3.0.2-2-kenzo.img
After flashing the recovery image reboot the phone to TWRP recovery by pressing Volume Up button and Power button simultaneously until you see the boot screen. It will boot the phone into TWRP recovery, on the front screen just swipe the slider to mount system as read only. That's it now to flash supersu proceed to step 9.
Step 9:
Flash SuperSu:
While the phone is in TWRP recovery connect the phone to Pc, it will be detected as mass storage device, just copy the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" file downloaded from the link I provided above to your phone's mass storage device.
On the twrp menu click on Install option and locate the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" to install via twrp, now swipe the slider to right to install supersu to have root access in your phone's OS and then wipe dalvik cache using the button below in twrp.
If twrp shows any read/write error while flashing supersu, on the twrp mainscreen choose mount option and click on system in the next menu, then go back to main screen and try again to install.
That's it, now supersu is installed, to check the root status follow to step 10.
Step 10:
Check root status:
After completing all the steps successfully, reboot the phone into the system normally and complete the initial setup without Sim card, the first boot may take a little more time to boot into OS, In case if the phone stuck in boot screen for very long(10+ mins), go to troubleshoot section at the bottom and start over the steps. Otherwise you are good to go.
Connect device to Pc after initial setup completes, now copy the "Root Checker.apk" file to your phone and install it, open the root checker app and click on verify root, you will be prompted by Supersu for root permission, allow it, your root access will be verified. Voila, you have successfully rooted, flashed twrp and installed supersu on your Redmi Note 3 with latest rom installed.
That's it. Now you are ready to rock.
KNOWN ISSUES:
No issues found so far, in case if you find any issues after successfully unlocking using the above method, kindly let me know.
After successfully unlocking your bootloader, incase if you update your rom via official updates, your will lose root access and twrp custom recovery and may end up with locked bootloader again, if you face this situation by some reason, you may start over and follow this guide from step 1 to revert back to unlocked bootloader. Do not update the rom and turn off automatic updates in settings as a precautionary measure.
Troubleshoot:
If your device gets bricked or Stuck in Boot logo, try this,
Reboot your phone into edl mode by following below step.
If you are stuck on bootscreen, you may not be able to enter into edl mode using the normal method above because of bootloop or Stuck in Boot logo, in that case try this method to enter into edl mode from fastboot, download "fastboot_edl.zip" file from the link I provided above, extract the zip file and open the extracted folder, connect the phone to your Pc in fastboot mode(vol down + power), double click and run this file "edl.cmd", the phone will automatically enter into edl mode if the phone's drivers and adb drivers are installed properly.Now follow step 6 and follow on from this step.
If QHUSB_BULK drivers are not properly installed while the phone in edl mode,
If QHUSB_BULK drivers are not installed while the phone in edl mode, your device may not be visible in MiFlash tool(ex:COM10) even after you click refresh button, in this case open the device manager in your Pc, the phone will be visible as QHUSB_BULK with some alert sign, right click on it and select Update driver software. Then click browse my computer and browse to the location of the driver files in path "C:\Program Files\Xiaomi\MiPhone\Qualcomm\Driver" and proceed and when prompted to Install this Driver Software anyway, allow it and complete the driver installation. Now open MiFash tool and click refresh button your device will be detected in MiFash tool, now you can flash the fastboot rom by following the steps above.
Does this work for Kate version also? OP doesn't specify
Will I lose my warranty by using this method of bootloader unlock?
This method still works for Global Snapdragon phone. Finally got it last night after 2 days of torture (I didn't sleep).
The important part is firstly the image with the modified file you are going to flash to the phone. Here he is using v8.0.6.0 which is the newest (and now last) update for android 5.1 (which is needed, phone will not flash 6.0 without a proper Cache and data clear). I ended up using version 7.3.2.0 which is 1 patch before the version my phone came with (7.3.7.0). Then I replaced emmc_appsboot.mbn with the one from here then flashed the file in EDL mode.
After the flash is done is just as important I found. You place it in fastboot mode (power button + vol down) and run a script. I wasn't able to manually unlock the device via cmd line 'fastboot oem unlock-go'. Instead I found a script that worked from here called 'Root_Folder' (this site also has majority of the files needed). You use the script called 'Root' in the folder to finish the unlock. Notice there is a 'recovery.img' in the folder as well, I replaced it with ZCX TWRP.
Now run through the script after the flash in fastboot mode. Follow the instructions from script, sometimes you take cable out or force phone back into fastboot mode. The key goal here is to have the script boot into TWRP in the end. If this happens you can do all that's needed now.
Another thing I noticed was you have to give debug permission to computer your using and save permission. Debug mode/oem unlock - connect cable, on phone you should get a prompt to accept PC and save permission. If you don't get this prompt make sure you have ADB and Fastboot installed.
Important steps are:
1. Phone connect to computer via debug/oem mode.
2. Flash correct modified ROM with MiFlash in EDL mode.
3. Once flash is done hold power and volume down button for fastboot mode.
4. Run script to attempt to unlock bootloader and/or install TWRP.
MikeyLee said:
Does this work for Kate version also? OP doesn't specify
Click to expand...
Click to collapse
You would have to look it up for Kate specifically. If anything at all that changes it's the Image you use to flash the phone.
zeon321 said:
Will I lose my warranty by using this method of bootloader unlock?
Click to expand...
Click to collapse
Don't think so. You don't 'officially unlock it' and you can flash a stock image that relocks the phone automatically.
Thank you works 100% !!!! :laugh:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
zeon321 said:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
Click to expand...
Click to collapse
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Narcle said:
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Click to expand...
Click to collapse
Thanks, I flashed old version of twrp and formatted the storage. Now phone is working fine.
Can i use this tuto on a Redmi note 4 MTK?
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !!
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !! @Sci Subi
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
W7nstroll said:
Can i use this tuto on a Redmi note 4 MTK?
Click to expand...
Click to collapse
This method is for Redmi Note 3 pro, (Kenzo) variant.
can i use it for global stable 8.2.3 ??
The heart of this - the unofficial bootloader unlock - are taken from: http://en.miui.com/thread-345728-1-1.html (It's generally polite to link your sources).
This _does_ work on `kate`. However, this is using a modified 'emmc_appsboot.mbn'. If you flash an original emmc_appsboot.mbn, you may well find your bootloader no longer unlocked and you needing to reflash your device back to stock.
Also, for those wanting to use it on kate (because Xiaomi seems singularly incompetent when it comes to supporting the official bootloader unlock for that devcie): your device will identify itself as a kenzo, so you may have trouble flashing things like the 'miuifirmware_x.zip' updates for kate. Also, those 'miuifirmware_x.zip' files often include the emmc_appsboot.mbn, so be careful.
On another note, if anyone has an actual infallible method to get an official bootloader unlock for the kate device, please let me know.
Can I use this method for 2GB / 16 GB version of Redmi Note 3 Pro (Snapdragon)?
Thanks
Works Thanks
Tested On 18/05/17
This method works But You are stuck on a older rom with no OTA/Later Updates. Method Does not work with MM Roms.(Maybe with different emmc_appsboot.mbn it would work.
Some Pointers
I was on MIUI8 before using this.
1. This downgrades your ROM from the latest ROM, therefore Points to follow.
2. Use This Method Instead Works with latest firmware as on date.
Works, Simply Nicely Perfectly Done, Just follow the steps things will never goes wrong. :highfive:
Sci Subi said:
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
Click to expand...
Click to collapse
hi my phone was on miui 8 marshmallow i used the above method nd flashed the rom ( rom is 5.1.1) which is given after that unlocked bootloader nd installed twrp also but now i downloaded a new rom nd i want to flash it i placed the rom in micro sd card nd wiped everything in phone nd flashed the rom with gapps now phone boots but its stuck at the boot logo of the rom i also tried many other roms of 7.1.1 but same is happening phone is not going ahead its stuck in the rom boot logo what should i do also when i flashed that given rom when i charge the phone the red light blinks which seems like edl light help me out of this !! thanks in advance !!
You have flashed a recovery rom and that's why you are in bootloop.
Try to flash in EDL mode a fastboot rom.
PS: Hope you haven't tried to downgrade already because you can loose IMEI and baseband.
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Let me link you my ingenious, allmighty Axon 7 Companion Thread.
Try to install twrp with MiFlash if you can enter edl mode
macerf said:
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Click to expand...
Click to collapse
Your phone works normally
You don't have fastboot
You have stock recovery
If this is the case then most surely you have EDL working...
Install TWRP from EDL mode:
This is taken from Controllerboy's guide
BE SURE THAT WINDOWS SHOWS FILE NAME EXTENSIONS!
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
macerf said:
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
Click to expand...
Click to collapse
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Choose an username... said:
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Click to expand...
Click to collapse
Hello and thanks for the advice. Unfortunately it does not change anything.. I have done exactly as you say but the result does not change anything...io have connected the device, Open command window, type "adb devices ", is viewed as "Cd07b2e9 device ", I type "adb reboot EDL ", it restarts in EDL, then go to management Devices and is viewed as "QUSB_BULK ", Run command "Axon7tool-r GPT boot recovery " but it says "Failed to connect ", then I'll return to Device Manager, hold volume up & Down & Power, Icon disappears and returns after a few seconds, close window and launch command "Axon7tool-r GPT boot recovery " but still give "failed to connect "...
So, recapping: I have bootloader unlocked, I can get into EDL but PC does not see device although on Device Manager it exists...
I now launch device into the wall... problem solved.
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
kitcostantino said:
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
Click to expand...
Click to collapse
Of course I'm kidding... have just purchased this device, have a great hardware but the software does not go well for nothing. I have had a dozen phones, I changed about 60 ROMs, so for me it is not difficult to change the software...ma in this case have problems. Is it possible that I fail to solve this problem? Be a way to reset everything and start from scratch? Okay, the bootloader be unlocked but not be any other way to go back? I have seen many guides but not able to solve the problem. I fail to make flash of TWRP, fail to do downgrade to MM....io hope someone help me... thanks.
are you using a USB 2.0 or 3.0 port? it may not apply to this scenario, but with Motorola and RSD Lite, I always had to use usb 2.0 ports or it wouldnt see my device when flashing.
also, the steps @choose an username listed out are the best way to start from scratch, but obviously you have to be able to have your computer see the phone in the desired mode.
@DrakenFX has several guides in the axon 7 forums that should help once the computer sees the phone as well.
I use USB 3.0 with original cable ... but if you now tell me that maybe this is my problem, then I use USB 2.0. Thank you...
Good morning...
Nothing to do... I put the original cable on USB Port 2.0, have redone procedure from window PowerShell, on command "adb devices " Everything OK, on command "adb reboot EDL " It enters EDL mode, but then all the procedures are failed... if command "Axon7tool-R recovery GPT boot "I always get out of the inscription " Failed to connect ", it remains in EDL and I just have to reboot... I replaced the drivers with Zadig 2.3 but did not change anything... are there any other moors to make flash of TWRP? exist lthough an app that do this? I remember that for LG G3 I'll fix everything with an app...
Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter (The above command does require your bootloader to be unlocked so kindly keep that in mind before passing the command)
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol ?
Reply if you face any problem
Peace!
addymishra said:
Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol
Reply if you face any problem
Peace!
Click to expand...
Click to collapse
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg
sieg01 said:
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg
Click to expand...
Click to collapse
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!
addymishra said:
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!
Click to expand...
Click to collapse
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?
sieg01 said:
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?
Click to expand...
Click to collapse
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool
sieg01 said:
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool
Click to expand...
Click to collapse
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash
Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse
biits1993 said:
Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
Click to expand...
Click to collapse
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!
addymishra said:
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!
Click to expand...
Click to collapse
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots
addymishra said:
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash
Click to expand...
Click to collapse
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating
biits1993 said:
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots
Click to expand...
Click to collapse
Strange :/ you can try miflash tool for that case. Download the lastest mi flash tool, enter into EDL mode using "fastboot oem edl" command then in mi flash drop down menu in left corner select "flash_factory.bat" and click flash. It will take around 400 seconds. Make sure you are in edl mode with red blinking light otherwise it will wipe your IMEI. Hope it works!
sieg01 said:
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating
Click to expand...
Click to collapse
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/
addymishra said:
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/
Click to expand...
Click to collapse
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg
sieg01 said:
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg
Click to expand...
Click to collapse
Man, I think its some sort of hardware issue then. Or maybe your messed up your blobs or your partitions real bad and corrupted them. QFIL helped in my case. Got no more tips, maybe its time to visit service center brother One last shot you can give is to try flashing with QFIL first then with Mi Flash. That's last hope! All the best!
flash failed in QFIL please help
sohanaw said:
flash failed in QFIL please help
Click to expand...
Click to collapse
Which version of QFIL and which ROM are you flashing with? I managed to flash the said version in OP through QFIL without any error. However, other official versions like 9.xx fail to be flashed by QFIL
A solution that worked after all these troubles
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!
biits1993 said:
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!
Click to expand...
Click to collapse
will try this tonight, thanks bhai
sohanaw said:
will try this tonight, thanks bhai
Click to expand...
Click to collapse
Let me know bro what happens, hope it works for you
I wanted to use RR rom though, but in the end no ROM worked for me except this one. So I'm just happy with it.