Probably you have the Anti-Rollback activated and tried to flash another ROM. After a successful installation your phone just went dead.
Here's how you could fix it (or how I fixed it):
1. Windows PC with MiFlash Beta (!) tool
2. Download a Xiaomi Fastboot Rom (ends with *.tgz)
http://bigota.d.miui.com/8.8.30/nitrogen_images_8.8.30_20180830.0000.00_8.1_cn_66dfc4bb58.tgz
--> Beta (MIUI 10 8.8.30) (ANTI ROLL-BACK ACTIVATED!!!)
3. extract Rom to your PC
4. start MiFlash Beta tool and point to the extracted folder
5. press Vol+ & Vol- & Power on your MiMax3 for 10 seconds and connect it to your PC while holding the buttons another second after plugging it in
6. press refresh button on MiFlash tool
7. if your drivers are installed correct, your phone should be visible on COM-Port XXX
8. press flash and hopefully it will be flashed
9. if not: try several times
10. wait until it boots to the welcome screen (around 5 mins)
now your phone should be useable again.
If you want Treble-Rom to be installed, then go on:
11. turn phone off --> go into fastboot mode (Vol- & Power) --> install TWRP --> boot into TWRP
12. wipe date = yes --> reboot TWRP
13. make yourself a MiRom at https://mi-globe.com/rom-builder-features/?codename=nitrogen&img=mimax3.png&realname=Mi+Max+3
--> I used 8.8.30 version, and choose "advanced settings"--> set Magisk for root and build your zip
14. flash it through TWRP
15. reboot --> you will end up in a bootloop, but thats okay
16. go back to TWRP: swipe factory reset
17. install treble.img + gapps + Magisk and reboot and you're all good
thanks a lot! but i m in a different situation now!
i have baught the device from local store with so called fake rom. and as per some instruction found at different forums i have successfully flashed china developper rom, and than flashed again eu rom. the version was miui 10 8.8.30. some how, i was trying to install a gcam mod mistakenly wich was originally for mi a1, and the mobile suddenly stuck on "the system has been destroyed!" mode. i can eventually come to fastboot mode from this screen, but cannot flash rom, as it says now, it is locked. dont have the right to erase. so, i tried miflash unlock with my mi account, but it says current account is not bound to this device. even, i can't go to edl, so what is happening now, i m totally nobis here.
can some one help me. please? how can i achive unlock in this situation or how could i get rid of this and reboot to system?
So there is a way to recover the phone if you brick if from installing a firmware after having anti-rollback?
yes, but the anti-rollback will be still activated. You can flash the China Roms or a treble ROM as described. If you try to flash the EU Rom you will boot into the EDL mode without any warnings.
I need help.
The post in #1 doesnt work for me.
I have also tried a many of miflash beta; all not work.
I become always the info "can not open port ..."
didi_m said:
I need help.
The post in #1 doesnt work for me.
I have also tried a many of miflash beta; all not work.
I become always the info "can not open port ..."
Click to expand...
Click to collapse
The method does work!
You need to re-activate the EDL mode in a split second of accuracy and timing by luck!
Keep trying! Your finger has got to very very fast to hit the "Flash" in MiFlash tool in relation to the process of entering he EDL mode!
I was on China Beta 8.8.30 (ARB) and I tried miflashtool to China Stable 9.6.11.0 (Non-ARB) and my phone bricked with blank screen. Could not power on at all, and not even into the Fastboot mode.
You have to miflashtool to ARB version of China Stable 9.6.12.0 to be able to success.
Hi,
I see the com port.
It begin to flash, put then the Error: Only nop and sig tag can be recevied before authentication.
didi_m said:
Hi,
I see the com port.
It begin to flash, put then the Error: Only nop and sig tag can be recevied before authentication.
Click to expand...
Click to collapse
I see. No problem.
In that case. Don't use 9.6.11.0 to miflash.
Please use the 9.6.7.0 and retry to miflash again.
9.6.7.0 should work.
I think 9.6.12 is the wright rom.
Why now 9.6.7.0.
Have you i link for me for this rom.
Is 9.6.7.0 without ARB.
Sorry for my bad english.
didi_m said:
I think 9.6.12 is the wright rom.
Why now 9.6.7.0.
Have you i link for me for this rom.
Is 9.6.7.0 without ARB.
Sorry for my bad english.
Click to expand...
Click to collapse
This is because you would probably get the same error massages as with 9.6.11.0 if you miflash to 9.6.12.0 ARB directly and even though some users might be able to miflash to 9.6.12.0 directly without the error massages
Therefore, Miflash using 9.6.7.0 Non-ARB first, and if you wanna update to 9.6.12.0 ARB. You can just do it via the Updater! This is the best and safest way to do it!
Grab the 9.6.7.0 now ...... I mean NOW!!!!!!!! before it is unlisted by Xiaomi for users to download as it is a damn old freaking rom!!!!!!!!!
UNLESS.... 9.6.7.0 failed as well! Then, you have to miflash to 9.6.12.0 directly as a last option and pray it works!
http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz
I only found the zip Version.
I need for myflash the tgz Version.
Have you a link to this Version ?
---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------
thanks, you ar quicklier.
didi_m said:
I only found the zip Version.
I need for myflash the tgz Version.
Have you a link to this Version ?
---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------
thanks, you ar quicklier.
Click to expand...
Click to collapse
UNLESS....miflashing to 9.6.7.0 failed as well! Then, you have no choice but to miflash to 9.6.12.0 directly and pray that it works with your version of miflash tool and pc.
Good Luck!
by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks
didi_m said:
by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks
Click to expand...
Click to collapse
Your Mi account has been locked by Xiaomi! OMG!
If so, then. No one can help you except you taking a flight to China and take a Q number at China Xiaomi service centre..
No one is dare enough to share his Mi account with you because arb is hardware "coded" so to speak. . It can cause his Mi account to be locked by Xiaomi too using it on your Mi Max 3 . '(
For my similar case, my Mi account has not been locked by Xiaomi.
I had the same issue
silentext said:
thanks a lot! but i m in a different situation now!
i have baught the device from local store with so called fake rom. and as per some instruction found at different forums i have successfully flashed china developper rom, and than flashed again eu rom. the version was miui 10 8.8.30. some how, i was trying to install a gcam mod mistakenly wich was originally for mi a1, and the mobile suddenly stuck on "the system has been destroyed!" mode. i can eventually come to fastboot mode from this screen, but cannot flash rom, as it says now, it is locked. dont have the right to erase. so, i tried miflash unlock with my mi account, but it says current account is not bound to this device. even, i can't go to edl, so what is happening now, i m totally nobis here.
can some one help me. please? how can i achive unlock in this situation or how could i get rid of this and reboot to system?
Click to expand...
Click to collapse
I had the same issue and i opened the phone and did the test point to enter to edl mode and flashed the chinese miui 10 stable rom , and now i have to wait 720 hours to unlock the bootloader to flash twrp and a global rom
So I just helped someone boot successfully to 10.0.1.0 global stable fastboot whose phone got bricked trying to flash 8.8.9 eu (maybe he had ARB but didn't know it). It was the black screen of death basically as noted here. TEST-POINT METHOD WAS NOT NEEDED.
Follow these steps:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi...icial-recovery-fastboot-roms-mi-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
4) It should boot. If it doesn't and you get stuck on the Mi Recovery screen. Select Wipe Data. It should boot you back into the recovery again where you'll see Reboot, Wipe Data or Connect Using Mi Assistant. From here, get back to fastboot mode by holding Power and Volume Down together until you see the bunny fastboot screen.
5) Open or refresh MiFlashTool again and select 10.0.1.0 fastboot rom (it should remember from previous selection). At the bottom select 'Clean All Only' (do NOT select clean all and lock). Hit REFRESH button at the top and this time it will show your device number like normal instead of COM. Click Flash.
6) Phone will reboot on its own to Miui 10 Global login screen. Setup your phone from there.
mi max 3 hard brick
opasha said:
So I just helped someone boot successfully to 10.0.1.0 global stable fastboot whose phone got bricked trying to flash 8.8.9 eu (maybe he had ARB but didn't know it). It was the black screen of death basically as noted here. TEST-POINT METHOD WAS NOT NEEDED.
Follow these steps:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi...icial-recovery-fastboot-roms-mi-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
4) It should boot. If it doesn't and you get stuck on the Mi Recovery screen. Select Wipe Data. It should boot you back into the recovery again where you'll see Reboot, Wipe Data or Connect Using Mi Assistant. From here, get back to fastboot mode by holding Power and Volume Down together until you see the bunny fastboot screen.
5) Open or refresh MiFlashTool again and select 10.0.1.0 fastboot rom (it should remember from previous selection). At the bottom select 'Clean All Only' (do NOT select clean all and lock). Hit REFRESH button at the top and this time it will show your device number like normal instead of COM. Click Flash.
6) Phone will reboot on its own to Miui 10 Global login screen. Setup your phone from there.
Click to expand...
Click to collapse
WIl l be able to go back to xiaomi eu room after that ?
thanks
---------- Post added at 01:39 PM ---------- Previous post was at 12:53 PM ----------
didi_m said:
by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks
Click to expand...
Click to collapse
hi..you get the error message ("cannot read...") because there must be space in you directory path somewhere ....remove all spaces in any directory path... it works like a charm.. i used the global stable rom mentioned below V10.0.1.0.OEDMIFH/nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105.tgz
---------- Post added at 01:46 PM ---------- Previous post was at 01:39 PM ----------
didi_m said:
by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks
Click to expand...
Click to collapse
hi..you get the error message ("cannot read...") because there must be space in you directory path somewhere ....remove all spaces in any directory path... it works like a charm.. i used the global stable rom mentioned below nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105.tgz
vikram237 said:
WIl l be able to go back to xiaomi eu room after that ?
thanks
Click to expand...
Click to collapse
There is no ARB on xiaomi.eu roms (except maybe 8.8.30 as omer919 stated).
The real brick solution by ARB, it works for mi max 3 too.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
and this is the ARB in Mi MAX 3.
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503
I had that one. Please charge up your Mobile for at least %100, lt will reboot.
Related
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.
Do the camera and fingerprint work?
Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.
I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?
xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )
Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug#b. Enable OEM unlock
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:type: adb reboot-bootloader ___ (Wait 1-3 second)type: fastboot devices ___ (verify device is detected)#b. verify bootloader unlock statustype: fastboot getvar all ___ and you get= warranty: yes= unlocked: no#c. unlock bootloadertype: fastboot oem unlock ___ and you get-> start unlock flow---> on screen appear:vol UP=Yes; void warranty, clear ALL datavol DWN=no; no unlockPress Vol UP#d. verify bootloader unlock statustype: fastboot getvar all ___ and you get= warranty: no= unlocked: yes#e. May be phone restart
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txtas per normal way (You know this , after some trying...)
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons#b. choose recovery with Vol Up and confirm with Vol Down
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.
when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file
I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file
xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?
The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.
I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...
As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?
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.
Salve! As you may know, Xiaomi enabled ARB (Anti-Roll Back) for Mi 6X starting with MIUI 10. It means that if you try to downgrade from MIUI 10 to MIUI 9, your device will enter in a brick EDL state and the only way to recover it is to send it to Xiaomi or flash it using MiFlash and an Authorized Account.
Yes, I am stupid and it happened to me.
Now, as I read here on XDA, there are some people who managed to brick their device by triggering the ARB when they converted the Mi A2 to Mi 6X to test MIUI. So if you flashed MIUI 10 and didn't deleted firmware-update from the .zip file, you triggered the ARB. If you tried to flash MIUI 9 or stock Mi A2 ROM, you managed to brick your device and it stays in an EDL state (Qualcomm 9008). You SIMPLY CANNOT rollback to Android One yet but you can revive your device very easy without test point or Mi Authorized Account.
Steps are simple. You just need to restore the device to the latest available MIUI 10 with a modified version of MiFlash by using wayne (Mi 6X) ROM with patched files in order to bypass the Unauthorized Account thing.
Keep in mind that your device will be MI 6X forever! Forget about Android One! If you want to revert back to stock Android, flash AEX or Pixel Experience.
1. Download MiFlashTool and Patched Programmer files: CLICK
2. Download latest Mi 6X MIUI Developer ROM: CLICK
3. Unzip all the files on your Desktop
4. Copy the Patched Programmer files to images folder of ROM
5. Start MiFlashTool, select the folder with your ROM (do NOT select images folder), on the bottom-right select flash_all
6. Plug the phone on your computer, hit refresh and flash fast!
7. Your phone will start flashing. When "success" appears, unplug your device, press the power button for about 15 seconds and boom, it's alive again!
8. If you want root or to flash another ROM, download the TWRP image from the folder above and type:
fastboot boot «drop here the TWRP image»
Once booted, copy the TWRP image to internal memory
In TWRP, go to Install -> Install Image -> Select TWRP image -> Recovery
Reboot -> Recovery
Since this device is no longer a Mi A2, we have now a standalone recovery partition. With ARB triggered, you can flash any ROM from TWRP (MIUI 10, Pixel Experience, AEX, Treble etc.). If you flash again MIUI 9, you will brick again your device.
If you found this tutorial helpful, hit that thanks button!
What kind of insane person on earth flashes MIUI 10 onto a Mi A2?
linuxct said:
What kind of insane person on earth flashes MIUI 10 onto a Mi A2?
Click to expand...
Click to collapse
People that like the Look and Feel of MIUI. I would have bought the 6X but I need the bands supported by A2 only. I dont care about the Android One program, I will just stick with a "converted 6X" and use their Roms.
@djmitza222 Thank you for this Guide, will be useful for many users out there.
Great bro ?
wtf? :c
"[19:29:41]:0 COM3 3,0201117s [19:29:41 COM3]:[19:29:41 COM3]:dump:<?xml version="1.0" encoding="UTF-8" ?><data><log value="ERROR: Only nop and sig tag can be recevied before authentication."/></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" /></data>"
What ROM did you flashed before brick? Try with this version of MiFlash http://xiaomitips.com/getfile/1474/?ez_cid=CLIENT_ID(AMP_ECID_EZOIC)
That work!! Thank you so much!
If you get: error received hello packet; press button power 15 seconds
Catastrophic failure(0x8000ffff: cmd<?xml version="1"MaxPayloadSizeToTargetInBytes="131072"MemoryName="eMMc"SkipstorageInit="0" error after using flash tool u just gave link to please help.
[delete]
adaamweber said:
maybe you can help me so i have an A2, i started flashing the MIUI9 first but there was an error message: ACK count mismatch. Since then the phone is a brick. I can boot it but stuck on the MI logo, also i can boot to fastboot but neither way does the phone recognized by my and other computers. When the phone is turned of and i press the power button only once the led is blinking but if I plug it in to the computer it starts to boot and stuck at the MI logo. Is there any way to recover or should i return it to a service center? Sorry if it's an offtopic question but you are my only hope.
Click to expand...
Click to collapse
Boot the phone in EDL mode from fastboot (fastboot oem edl) and flash Mi A2 stock ROM. It should work.
after that and the cell phone resurrects, can this tutorial work?
https://en.miui.com/thread-3439864-1-1.html
No, it will brick again. Only if somebody makes a TWRP flash version for stock ROM.
[delete]
djmitza222 said:
No, it will brick again. Only if somebody makes a TWRP flash version for stock ROM.
Click to expand...
Click to collapse
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
here is the recovery version of mi a2 stock
But would it have to replace some file?
---------- Post added at 02:28 PM ---------- Previous post was at 02:23 PM ----------
The tutorial worked on my friend's cell phone. But he can not flash any ROMs through twrp. Receive error 7.
stopthetime said:
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
here is the recovery version of mi a2 stock
But would it have to replace some file?
---------- Post added at 02:28 PM ---------- Previous post was at 02:23 PM ----------
The tutorial worked on my friend's cell phone. But he can not flash any ROMs through twrp. Receive error 7.
Click to expand...
Click to collapse
Vendor related error 7 or System related error 7? Do NOT flash Mi A2 ROM again or you will brick your device.
djmitza222 said:
Vendor related error 7 or System related error 7? Do NOT flash Mi A2 ROM again or you will brick your device.
Click to expand...
Click to collapse
System error 7. With rom AOSP and Pixel Experience.
maybe problem in twrp?
EDIT:
just to add, they found a bypass to be able to use commands by ADB with arb
Look: 5- Unlocking Fastboot:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Restore to the latest stock MIUI 10 for Mi 6X, install TWRP and try again. It should work.
what happens if we update the miui from its own updater for new updates?
what happens if we update the miui from its own updater for new updates?
will it brick the device
Modified version MiFlash2018 work to flash Xiaomi Mi 6 Pro without Autorized account?
good ,thank you very much
i was successful ,my xiaomi redmi 6x has resurrected
Salve! As you may know, Xiaomi enabled ARB (Anti-Roll Back) for Mi 6X starting with MIUI 10. It means that if you try to downgrade from MIUI 10 to MIUI 9, your device will enter in a brick EDL state and the only way to recover it is to send it to Xiaomi or flash it using MiFlash and an Authorized Account. Now if you are like me and have a locked bootloader in a converted a2 to 6x wayne then the only way is testpoint and even if your device has an unlocked bootloader doing fastboot oem edl is very unlikely to work
Now, as I read here on XDA, there are some people who managed to brick their device by triggering the ARB when they converted the Mi A2 to Mi 6X to test MIUI. So if you flashed MIUI 10 and didn't deleted firmware-update from the .zip file, you triggered the ARB. If you tried to flash MIUI 9 or stock Mi A2 ROM, you managed to brick your device and it stays in an EDL state (Qualcomm 9008). You SIMPLY CANNOT rollback to Android One yet until they introduce ARB to that device too but you can revive your device very easy with test point but no need for Mi Authorized Account. Sorry it has to be this way but this is the only way took me about 8 times to try and finally someone showed me this file which helped
https://drive.google.com/uc?export=download&id=1wAqlpmxMdZpibzPBuyBEwOY9ggcifAdd - This has everything include including the xiaomiflash no patched files are required as they have already been modified to bypass edl authentication i would also turn your wifi off whilst flashing this as thats what worked for me..weird eh?
Credits go to Sunchai - Admin of Mi Max Thailand for creating this amazing bypass
https://ibb.co/fYYmq0P
https://ibb.co/rd81JfK
These are screenshots of everything working so yeah , also if you are a2 user converted when you install the pie beta via the older beta version enhance lowlight photo automatically is fixed
My device is mi 6x and arb var : 4, unlocked bootloader. Currently I'm using havoc rom. Is this possible to go back to official china dev rom without bricking the device?
faisal1hd2 said:
My device is mi 6x and arb var : 4, unlocked bootloader. Currently I'm using havoc rom. Is this possible to go back to official china dev rom without bricking the device?
Click to expand...
Click to collapse
Yeah it won't brick click the clean all not clean all and lock unless that's what you want try with fastboot oem edl however users have reported that opening the device works
Quantumkk123 said:
Yeah it won't brick click the clean all not clean all and lock unless that's what you want try with fastboot oem edl however users have reported that opening the device works
Click to expand...
Click to collapse
You're are saying to try fastboot oem edl first, if it doesn't work then open device and use test point, right?
faisal1hd2 said:
You're are saying to try fastboot oem edl first, if it doesn't work then open device and use test point, right?
Click to expand...
Click to collapse
Yup
@Quantumkk123 It's work if my device is bricked ? (reboot to edl automatically, Mi A2 triggered ARB 4 for be a true Mi 6X)
Mashrmallow said:
@Quantumkk123 It's work if my device is bricked ? (reboot to edl automatically, Mi A2 triggered ARB 4 for be a true Mi 6X)
Click to expand...
Click to collapse
If you open up the device two pin it and install everything specific to that folder including version of xiaomiflash etc, this could help save you from the brick
Quantumkk123 said:
If you open up the device two pin it and install everything specific to that folder including version of xiaomiflash etc, this could help save you from the brick
Click to expand...
Click to collapse
Ok but after unbrick my device, can I install xiaomi.eu MIUI 10 stable or weekly rom for Mi 6X ?
Mashrmallow said:
Ok but after unbrick my device, can I install xiaomi.eu MIUI 10 stable or weekly rom for Mi 6X ?
Click to expand...
Click to collapse
Depends if your bootloader is unlocked, yes if not only can go for pie beta stock cn
Quantumkk123 said:
Depends if your bootloader is unlocked, yes if not only can go for pie beta stock cn
Click to expand...
Click to collapse
My bootloader is unlocked and I can Install MIUI 10 stable V10.2.3.0.ODCCNXM_v10-8.1 (Oreo 8.1.0) by Xiaomi.eu if I wipe data, cache and dalvik's/ART cache
Mashrmallow said:
My bootloader is unlocked and I can Install MIUI 10 stable V10.2.3.0.ODCCNXM_v10-8.1 (Oreo 8.1.0) by Xiaomi.eu if I wipe data, cache and dalvik's/ART cache
Click to expand...
Click to collapse
Yeah
@Quantumkk123 I got this error: Your not autorized to download
ERROR
download the rom that you left, but when flashing it tells me " you are not authorized to download"
arnuvi said:
download the rom that you left, but when flashing it tells me " you are not authorized to download"
Click to expand...
Click to collapse
Lmao no one is doing it properly follow the instructions carefully and properly turn off WiFi/ethernet before you click on xiaomiflash and make sure you use one provided as well as that clear and delete and version of miflash previously installed on your PC
FAIL
https://ibb.co/X5ZJhF7
I did what you said but it is still giving error
arnuvi said:
https://ibb.co/X5ZJhF7
I did what you said but it is still giving error
Click to expand...
Click to collapse
Is your phone opened because if it isn't thats why it works for so many others but for you it doesn't there is something wrong your doing here
confirm, it works. boot to fastboot with bootloader unlocked. turn internet connection off. use the miflash provided with the rom.
Surely you wilm be.return to miui v.8.2.23, then able to update to v9.3.21 Pie
stevedat said:
confirm, it works. boot to fastboot with bootloader unlocked. turn internet connection off. use the miflash provided with the rom.
Surely you wilm be.return to miui v.8.2.23, then able to update to v9.3.21 Pie
Click to expand...
Click to collapse
my a2 does not enter fastboot mode, does not turn on only the pc recognizes it in edl mode, but when flashing the rom that they told me, it asks for account authentication
---------- Post added at 01:14 AM ---------- Previous post was at 01:11 AM ----------
Quantumkk123 said:
Is your phone opened because if it isn't thats why it works for so many others but for you it doesn't there is something wrong your doing here
Click to expand...
Click to collapse
I flashed the rom that led me to the problem by recovery that was miui 9 8.1, while I was in miui 10, after that I rebooted the cel, and did not want to restart it I enter in a way that only the pc recognizes it by edl, but when flashing the rom that you gave me stays in account authentication my flash
arnuvi said:
my a2 does not enter fastboot mode, does not turn on only the pc recognizes it in edl mode, but when flashing the rom that they told me, it asks for account authentication
---------- Post added at 01:14 AM ---------- Previous post was at 01:11 AM ----------
I flashed the rom that led me to the problem by recovery that was miui 9 8.1, while I was in miui 10, after that I rebooted the cel, and did not want to restart it I enter in a way that only the pc recognizes it by edl, but when flashing the rom that you gave me stays in account authentication my flash
Click to expand...
Click to collapse
the thread.says.its self as passby edl auth. it doesnt mean to save bricked phones.
I just want to share my trials and tribulations...
I tested many things and I manage to have my Poco F2 on Android 11 with easy way to root and have a Safetynet OK
There are many ways to do it but i never found it in only one post...
Here's my TO-DO list to make it...
1 / Starting from the bottom, I flashed the latest global rom (FASTBOOT METHOD to make a clean phone)
V12.0.3.0.QJKMIXM (Android 10)
- activate the phone after boot then go back to Fastboot Mode
2/ Unlock Bootloader via Mi Unlock (Fastboot Mode)
- activate the phone after boot then go back to Fastboot Mode
3/ Install TWRP via Fastboot mode
TWRP-3.4.1B-0328-REDMI_K30PRO
(XXXX is the name of your TWRP file)
- fastboot flash recovery XXXX.img
- fastboot boot XXXX.img
- After flash and the first boot to recovery, "format data" (The one you have to type YES) and reboot into recovery
4/ Install Latest Xiaomi.eu Stable (Or Weekly maybe)
[V12.1.2.0.RJKCNXM][Android 11]
- Copy the rom on your phone (from recovery)
- Install rom
- Wipe your data,cache,Internal storage,dalvik DONT WIPE SYSTEM OR YOU WILL BRICK YOUR DEVICE
- Reboot your device.
- If reboot to recovevy, then format data (again) and reboot system
- activate the phone after boot then start the phone to go to the desktop (google account, security,...)
5/ Root with Magisk Canary
- Reboot into recovery
- Flash Magisk-debug.zip then format cache
- Reboot till the phone ask for sim card code then restart
- Open magisk manager and check you on canary canal for update
- Root should be ok!!! (you can download the magisk zip from magisk manager then reflash it in recovery mode to be sure : i dit it lol)
Here, my safetynet was failed then my google pay didnt work
6/ For Safetynet, use MagiskHide Props (even if I don't use it cause i flashed persist.img from Official rom)
That's all from and for me
Hope it can help
PS : Maybe I have bugs but for the moment it's ok
Probably you loose possibilities to make fingerprint works again... I do the same things and now fingerprint doesn't work more, and there are no possibilities to make it works.
CarloBello said:
Probably you loose possibilities to make fingerprint works again... I do the same things and now fingerprint doesn't work more, and there are no possibilities to make it works.
Click to expand...
Click to collapse
Seems to not want to reset even after a fastboot flash rom
Maybe we need to find another persist.img file....
If you find a solution before me, tell me
Put your phone in EDL mode(install qualcomm driver) and flash fastboot rom via MiTool.
Persist.img not flash in fastboot or twrp method...only EDL
Sorry for bad English.
I try that to flash in edl mode but it not possible because Mi flash tools need authorized account, I whole day trying to flash rom in EDL mode without any luck..
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
the last thing that I now trying is to flash China stable fastboot rom through EDL mode, because Fastboot and TWRP dont change Persist.img , only EDL mode,hope that China rom dont need authrorization
tze_vitamin said:
I try that to flash in edl mode but it not possible because Mi flash tools need authorized account, I whole day trying to flash rom in EDL mode without any luck..
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
the last thing that I now trying is to flash China stable fastboot rom through EDL mode, because Fastboot and TWRP dont change Persist.img , only EDL mode,hope that China rom dont need authrorization
Click to expand...
Click to collapse
I am in the same case, after trying a lot of solutions, none have worked.
I prefer to wait for the arrival of orangefox than to open my device.
pennywise1985 said:
Put your phone in EDL mode(install qualcomm driver) and flash fastboot rom via MiTool.
Persist.img not flash in fastboot or twrp method...only EDL
Sorry for bad English.
Click to expand...
Click to collapse
NOSS8 said:
I am in the same case, after trying a lot of solutions, none have worked.
I prefer to wait for the arrival of orangefox than to open my device.
Click to expand...
Click to collapse
you think that orangefox will help?
tze_vitamin said:
you think that orangefox will help?
Click to expand...
Click to collapse
Maybe, I had sensors problem with my redmi note 7 and only orange fox was able to flash correctly the persist img.
Current twrp do not have access to this Partition, the result " FAILED remote: 'Partition is write protected".
I try this command with terminal "dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist" no error to report but not flash.
I try also to modify"rawprogram0.xml"in fasboot rom ,no error to report but no result.
https://ibb.co/QNx1Tz2
NOSS8 said:
Maybe, I had sensors problem with my redmi note 7 and only orange fox was able to flash correctly the persist img.
Current twrp do not have access to this Partition, the result " FAILED remote: 'Partition is write protected".
I try this command with terminal "dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist" no error to report but not flash.
I try also to modify"rawprogram0.xml"in fasboot rom ,no error to report but no result.
https://ibb.co/QNx1Tz2
Click to expand...
Click to collapse
I still searching for mi flash tools that allowed me to flash in edl mode
tze_vitamin said:
I still searching for mi flash tools that allowed me to flash in edl mode
Click to expand...
Click to collapse
I also tried in ELD mode and I have this error "cannot receive hello packet"...
NOSS8 said:
I also tried in ELD mode and I have this error "cannot receive hello packet"...
Click to expand...
Click to collapse
this is the closest that I get but with no luck..
For the safetynet on android 11, use magiskhide prop. Select Poco f2 pro + the option force basic key attestation. It works for me
tze_vitamin said:
I try that to flash in edl mode but it not possible because Mi flash tools need authorized account, I whole day trying to flash rom in EDL mode without any luck..
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
the last thing that I now trying is to flash China stable fastboot rom through EDL mode, because Fastboot and TWRP dont change Persist.img , only EDL mode,hope that China rom dont need authrorization
Click to expand...
Click to collapse
Which rom does not ask for permission?
NOSS8 said:
Which rom does not ask for permission?
Click to expand...
Click to collapse
MUI 12.2 20.9.17 Beta android 11 !
You need to use the last magisk manager canary version.
The prompt works for me!
Domi14fr said:
MUI 12.2 20.9.17 Beta android 11 !
You need to use the last magisk manager canary version.
The prompt works for me!
Click to expand...
Click to collapse
What are you talking about?
I solved the problem !!!!!
go to the CIT menu press the 3 dot in the top right of screen scroll down calibrate the FOD -> place a white thing on FOD click start before next step put something black on FOD and press next...wait until finish close restart and add your fingerprint have a nice day
I GOT THE SOLUTION AND IT WORKS!!!!
-Go to the CIT menu by pressing : *#*#64663#*#*
-Press the 3 dot to go in "additionnal tools"
-Go to number 12 : "fod fingerprint calibration"
-Follow the instructions :
1 / Put a white paper on the FOD then click start and wait
2/ Put a black paper (or something black) on the FOD then press next and wait
3/ Enjoy
tze_vitamin said:
I solved the problem !!!!!
go to the CIT menu press the 3 dot in the top right of screen scroll down calibrate the FOD -> place a white thing on FOD click start before next step put something black on FOD and press next...wait until finish close restart and add your fingerprint have a nice day
Click to expand...
Click to collapse
yes it works thank you very much :good::good::good:
Domi14fr said:
For the safetynet on android 11, use magiskhide prop. Select Poco f2 pro + the option force basic key attestation. It works for me
Click to expand...
Click to collapse
I still get device not certified in google play and safety net still fails after doing this.
Is decrypt for PIN on TWRP available?
Heard only pattern lock can be decrypted.