Database Users

Axon 7 A2017G from Lineage OS go back to Stock and Lock Bootloader without Problems

1.) You must have a full ZIP from ZTE
2.) Flash back the Original Recovery from the Original ZIP e.g. B08 B10 with ADB Fastboot command ( You must ticked OEM unlock on and USB debugging on in Developer Setting ) in Lineage.
2.1) push Power and tick restart in Bootloader.
2.2) go to Minimal ADB and Fastboot and type fastboot flash recovery recovery.img.
2.3) After this push with the Volume down recovery ,tick power.
OK! You can see the ORIGINALRecovery from ZTE.
3.) You must put a SD Card in Phone with the Original Update.zip
4.) Go in recovery and tick Update from SD card. Search the Update.zip and press Power.
5.) Wait until the Flash Process is finished.
6.) Tick Factory reset with Volume up/down push Power wait.
7.) Tick format Cache with Volume up / down push Power wait.
8.) Push Power to start your Phone with the Original Stock.
9.) After this you go to Settings / Build Number and Tick that seven Times to activate Developer Options, go back to setting and tick Developer Options ,here you must tick the OEM unlocking and USB debugging.
10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
11.) in the Comand window you type" Fastboot oem lock" the Phone reboot and the bootloaer is locked. All your Data is lost in this Process!!![COLOR="Red"][/COLOR]
Voila all is done!! Original AXON 7 with Stock Rom .
I have test this with my Axon 7 Model A2017G and i have no Problem.
Sorry for my bad English.

Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?

spacemanvt said:
Thanks for writing this out. Will be useful in case I need to switch back in the future
Where do you get the stock rom zip file though? zteusa.com somewhere?
Click to expand...
Click to collapse
There is a global site where you can get the file. http://www.ztedevice.com/support/detail?id=C3BAC27838C4497C80C05EE008527885
Sent from my ZTE A2017G using XDA-Developers Legacy app

Hello,
I recovered my old stock recovery and when trying to apply update from sd card, it gives me this error: "Couldn´t mount /sdcard. installation aborted"
What can I do?
Edit: Solved by formatting the SD card

What is the ADB fastboot command to flash stock recovery?

JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery "stock Recovery"

Flash the Original recovery.img from your Update.zip!!
JP_93 said:
What is the ADB fastboot command to flash stock recovery?
Click to expand...
Click to collapse
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.

julk13 said:
fastboot flash recovery "stock Recovery"
Click to expand...
Click to collapse
Thanks!
tester2017 said:
open Update.zip with e.g Winrar and unpacking recovery.img to the ADB directory. OK?!
Then open a Command Window and Type : fatboot flash recovery recovery.img . Wait.
Shutdown your Phone . Restart Phone wit push Power and Volume up.
tick with the Volume down botem update from SD card.
Click to expand...
Click to collapse
Thanks for the help, I will try now

10.) Open Command window on PC and type "fastboot reboot bootloader" the phone shut down and restart in bootloader mode.
Click to expand...
Click to collapse
You made a mistake there as you have to enter "adb reboot bootloader" instead of fastboot. Other than that, it works perfectly. Thank you.

I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.

idigg said:
I can't get my bootloader locked. Under dev options, "OEM Unlocking" it grayed out.
Click to expand...
Click to collapse
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either

spearman792 said:
Did you find a solution to this? I'm running into the same problem with OEM unlocking being grayed out. I returned to stock just fine, but my problem is booting into the bootloader. Every time I try, it just goes to the "your device cannot be checked for corruption and will reboot in 5 seconds" screen. During this screen and during the screen that comes up you press the volume keys for the options menu, the fastboot oem lock command does not seem to work. Fastboot devices doesn't show any devices listed either
Click to expand...
Click to collapse
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.

robertaramar said:
Seconded, I'm having the very same problem. Strange thing is, I cannot boot into booloader. I can boot into recovery, I can boot to system but whan I try to boot into bootloader via adb reboot bootloader, the phone just boots into system. If I try Power/Vol-Down, I will eventually land in FTM mode.
Anybody any clue?
SOLVED: After using the Windows based Axon7Toolkit which used Miflash to restore fastboot, I was able to boot into bootloader and also re-lock it.
Click to expand...
Click to collapse
You couldn't boot into bootloader because there was no bootloader mode. As soon as you update to a recent Nougat build (or an upcoming one) via official zips, your aboot.img will be changed and you won't have bootloader mode anymore. Axon7toolkit relies on fastboot, so it flashes a package through MiFlash that gets you fastboot support.
Jus sayin

Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?

robertaramar said:
Thanks for the clarification.
Is there an aboot.img I can flash e.g. via axon7tool so I can enable fastboot again?
Would that be counted as a warranty void by ZTE?
Click to expand...
Click to collapse
You can use the A2017U_FASTBOOT_UNLOCK_EDL from 4pda guys with MiFlash. Doesn't matter if you have a G, use this one
Actually axon7toolkit seems to flash that every time it does something related to fastboot. And after you lock it, you can install an official update zip (the latest one for example) and you'll get your phone totally stock, bootloader mode will be blocked.

Cannot enter recovery mode xperia c4

I cannot enter recovery mode when I press and hold power and volume up button, it vibrates 3 times and nothing happens. I used to be able to do it with 5.1 now I flashed my phone to marshmallow like 5 months ago and cannot do it anymore . I don't know if its something to do with the flashing the phone please help me

same
bandutiz said:
I cannot enter recovery mode when I press and hold power and volume up button, it vibrates 3 times and nothing happens. I used to be able to do it with 5.1 now I flashed my phone to marshmallow like 5 months ago and cannot do it anymore . I don't know if its something to do with the flashing the phone please help me
Click to expand...
Click to collapse
i have literally the same problem and i can't get out of this!
sony didn't make the update for xperia c4 to start automatically, so i flashed marshmallow 6.0 in this device.
And now, i can't get in recovery mode, i used a tons of guides, i try to do it with codes on sdk, on sony's flashtool(emma), on adb, it's totally useless i think there isn't a way to get the recovery mode on xperia c4 with marshmallow 6.0.
Sony, wtf?

no one?
Any helps?.. it is really impossible to root this phone?

same problem here too.. need help

bandutiz said:
I cannot enter recovery mode when I press and hold power and volume up button, it vibrates 3 times and nothing happens. I used to be able to do it with 5.1 now I flashed my phone to marshmallow like 5 months ago and cannot do it anymore . I don't know if its something to do with the flashing the phone please help me
Click to expand...
Click to collapse
Search for stock recovery or TWRP recovery .img file on web. ( Remember, Google is your friend! ) Rename it to recovery.img and put it into the adb folder. Then, open a command prompt there ( as admin ) then type: cd <directory to adb folder> e.g. cd C:\adb then boot into fastboot mode or bootloader and then type: fastboot flash recovery recovery.img . Now it should flash a new recovery to your recovery partition.
P.s. You need to unlock your bootloader! But you need to backup your files cuz this is going to delete them!!! Go to setings> slide down> click on about your phone> click 7 times on build till you see a message like: "You are a developer!"> then click back button> go to "Developer settings"> and find an option called: "Oem Unlock." toggle it> Then go to fastboot mode or bootloader mode and in fastboot type: "fastboot oem unlock" or "fastboot oem go-unlock" then click "Yes" when prompting. BUT you can also boot in edl mode and flash it without unlocking bootloader. To do this, try power combinations, or go on google and search for them. It may also happen that you don't have an EDL mode, so you'll have to unlock the bootloader. So: What you have to do.
1. If you have a locked bootloader, unlock it.
2. Get a recovery image ( img. ).
3. Flash it!
Well that's it! Hope you understand me! Happy flashing!
riecards29

And now what i do with my Axon 7?

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...

[guide] how to fix totally dead redmi note 4 | stuck in bootloop | qfil flashing

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.

[Guide] Returning to Android One

Assuming you have the needed drivers for Mi A2.
How to return to stock ROM (the safe way):
Download the latest Mi Flash from here
Download the stock ROM for Mi A2 from here
Download the Mi A2 toolkit from here
Step 1 - Put all the files in a folder and organize everything so you don't get confused.
Step 2 - Open the Mi A2 tool kit by opening the toolkit.bat and select 5, then select 2 (reboot into EDL).
Step 3 - Open the XiaoMiFlash.exe you downloaded (the one inside the folder, not the executable outside the folder, that one doesn't work) as administrator.
Step 4 - Press refresh and see if your phone gets detected.
Step 5 - Extract your stock ROM zip to a folder.
Step 6 - Select that stock ROM folder on Mi Flash, select clean all and press flash.
If you're getting errors while flashing (hello packet or object reference), simply hold POWER + Volume down until it restarts back to fastboot (it should be a black screen, don't worry its normal) then do Step 2, 4, and 6 again.
Step 7 - After flashing is complete, close Mi Flash and press POWER + Volume down to boot back to fastboot (it should be a black screen, don't worry its normal)
Step 8 - Extract your Stock ROM zip again but this time extract the contents to the same folder where's your fastboot and adb files (mine is C:\ADB for example)
Step 9 - Open the flash_all.bat file from where you extracted your Stock ROM zip (same folder where's your fastboot and adb files)
Step 10 - After the flashing is complete (if the phone reboots,press POWER + Volume down to boot back to fastboot), open the Mi A2 toolkit and select 1. Lock/Unlock Bootloader, then select 6 Lock flashing critical and lock your bootloader (a message should appear on your phone to lock your bootloader).
Step 11 - Boot back into fastboot again, open Mi A2 toolkit, select 1. Lock/Unlock Bootloader then select 5 lock flashing and lock your bootloader (a message should appear on your phone to lock your bootloader).
Step 12 - Let the phone restart and welcome back to Android One (remember to do your system updates since the Stock ROM you downloaded isn't the latest version).

Thanks mate, excellent tutorial, saved my life.

Excelent! By doing this i relock my BL and the message about unlocked phone on boot will disapear? Thx for the tutorial A LOT!

this don't works on arb 4 right?

felipedon said:
this don't works on arb 4 right?
Click to expand...
Click to collapse
Yes, if phone is updated to ARB 4 mean you can not revert to A2 or Android One. But still you can flash custom roms like PE and Havoc.

How to check if m phone works on arb 4 ?

polak13133 said:
How to check if m phone works on arb 4 ?
Click to expand...
Click to collapse
To check ARB version of your phone put the phone into fastboot and enter below code
fastboot getvar anti

Hi first thx for this awesome guide,but I'm facing a problem where the camera is stuck on black screen after back to stock rom,any solution?

Hello and thank you for the detailed guide. Just a question, after returning to stock, it seems when I boot up the phone it's entering in edl mode (vivration plus black screen, and when I quick press the power button it vibrates). If I hold the power button it will boot on system. Before I began messing arround with flashing, I juste had to press and hold the power button and the system would load. Now I have to press and hold, vibration, keeping holding and wait for a second light vibration to load the system. Is there something I'm missing?
Thanks.

jayreen said:
Hello and thank you for the detailed guide. Just a question, after returning to stock, it seems when I boot up the phone it's entering in edl mode (vivration plus black screen, and when I quick press the power button it vibrates). If I hold the power button it will boot on system. Before I began messing arround with flashing, I juste had to press and hold the power button and the system would load. Now I have to press and hold, vibration, keeping holding and wait for a second light vibration to load the system. Is there something I'm missing?
Thanks.
Click to expand...
Click to collapse
I have the same problem

Hello. i tried several times and i everytime i get "hello packet" error. i rebooted the machines three times and change the usb ports... i dont know what more to do. Any help?

Hey, im stuck to edl mode cant reboot the phone to fastboot or recovery and it shows QDloader 9008

Thank you so much! Battery was really bad on havoc so i decided to go back to stock. Folowed tutorial without relocking the bootloader and all is perfect. Cheers! ?

Hi
Mine just says flashing and time goes on and on how long does the flash take?

I won't be able to support anyone any longer, I sold my Mi A2 and got a Nokia 7 Plus.
However the guide that I wrote still applies just as normal if you're returning from MIUI and HAVE NOT locked the bootloader nor flashed an ARB enabled version.