Database Users

[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recovery

DO NOT FLASH HYDROGEN ROMS ON HELIUM, OR YOU GONNA HAVE A HARDBRICK.
IN CASE YOU HAVE ONE, HERE IS THE SOLUTION.
This was tested with Xiaomi Mi Max 128GB helium and localized rom from xiaomi eu.
I am not responsible for bricked devices or anything else. So at your own risk:
1. Install official MiPhone drivers
2. Download and install MiFash beta.
3. Download and unpack TWRP for miflash: 32gb or 64-128gb thanks @Abdess76.
4. Download ROM for your device, I recommend to try this one. You can install RR/CM Rom as well.
5. Run MiFlash with admin rights.
6. Turn off the phone, plug the cable to PC and halfway to the phone.
7. At the same time press Volume + and Volume - and plug in the cable.
8. Refresh MiFlash phone should show up. (If it didn't then make sure you did it right and u got drivers)
9. Navigate to your unpacked TWRP and flash it.
10. Now, boot ur phone with volume up. It's a bit slow. If it's stuck on miui logo, just release button and wait.
From here start to pay more attention:
11. TWRP can ask for password, press cancel and allow modifications by moving slider.
If you just need ROOT and your current rom, skip to the step 16. Also there is a recovery from boot in system folder. If you won't remove it, recovery may be replaced with stock one after reboot. Keep it that way if you want OTAs.
12. Format data.
13. Enable MTP and put modified zip in your phone.
14. Go to mounts and unmount system **
15. Flash your rom.
16. Flash latest supersu.
17. Reboot the phone.
In case u got NO OS message, then it means that u probably ignored step 15.
Also first boot may take like 15-20 minutes, since eu rom is deodexed.
Just to be sure, after installation mount system partition and navigate to the /system folder using TWRP's file manager and make sure it's not empty.
* In my case system didn't install because script could mount system partition since it was already mounted.
P.S. In order to update, you need to install OTA for offical rom via TWRP. Then without rebooting flash SuperSU, and finally using TWRP's file manager navigate to system folder and delete file named recovery from boot. Doing so will keep root and recovery.

Thank you so much for the guide! I will try it tonite
Waiting for boot loader is just too long..

WOW!!!! Just, wow..... I can not believe it but it worked like a charm. It took me forever to figure out my issue with the drivers, but after solving that I followed you step-by-step. And, lo and behold, it WORKED! Note for other users, Twrp took about a minute or two to finally boot up and it took me personally about 15-20 minutes before MIUI 8 finally booted. Just wait it out and you should have the amazing results that Doom Slayer has so graciously provided you
THANK YOU!!!!

I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.

flywithme said:
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
Click to expand...
Click to collapse
Yeah, dirty flash is you keep your data and format system and caches .
Clean flash is u format data as well.
The thing is that u have root, and ur phone is also secured. It's linked to ur Mi account, while it's locked. It's better to keep that way

Theoretically If you will ignore steps from 12 to 16. (Maybe u can ignore data formatting too)
Then you can get a ROOT and TWRP on your current rom.
And also theoretically while on miui 8 rom ,u can try to unlock bootloader without waiting.
Try this manual.

I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?

agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Open it up and remove battery for a few minutes, then try again from step 6...

agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Which rom did u flash, give the link please.
Are u sure it's for your version? It can be a broken file as well.
Does the device connects when u hold both volume buttons?
It's called emergency download mode, u can istall rom with miflasher.
There is a testpoint method also.
All u need is a pic from this post on http://4pda.ru/forum/index.php?showtopic=749580&st=700#entry51154086
U need to disconect battery, connect testpoint to battery and flash ur device with miflash.
After that let it charge, since this in your state phone consumes battery.

thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up

agreusar said:
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
Click to expand...
Click to collapse
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.

Doom Slayer said:
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Click to expand...
Click to collapse
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.

agreusar said:
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
Click to expand...
Click to collapse
Well, I guess system was mounted and it gived u the error,but formatted it.

hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.

alain belay said:
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
Click to expand...
Click to collapse
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.

Updated tutorial.
Uploaded TWRP for helium, so you don't need to edit updater script anymore, since script will get correct model.
Now you can try to get root on your current rom and unlock bootloader without Xiaomi's confirmation.
People having helium with unlocked bootloader may also have problems installing roms from xiaomi eu, if they have TWRP from hydrogen.
You may update using my recovery.img from archive using fastboot, or TWRP(will also work for locked bootloader).

Doom Slayer said:
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Click to expand...
Click to collapse
hi Doom. Thank you for reply. But what do you mean by " disable drivers signature". I did not do anything but install the drivers and when I am on what I think is EDL mode(screen isi black) the driver is recognized as Qualcomm HS-USB QDLoader 9008(COM20).
Anyway, I will give another try and let you know. Thank you again.
---------- Post added at 09:14 AM ---------- Previous post was at 08:22 AM ----------
I followed your guide and I could get the twrp installed. So I tried to install rom(following your link). It said rebooting in 5 seconds, and then nothing. The screen is black, no power anymore, no logo, no vibes, and no life at all.
I cannot get any more reaction from it. I plugged it to my pc, but nothing is connected. I was so happy with twrp working... Any idea?...

one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...

alain belay said:
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
Click to expand...
Click to collapse
Looks like you installed hydrogen TWRP and that caused all your problems.

I've been very careful to install the helium twrp from this thread...

[UNBRICK] Xiaomi Mi Max 64/128 GB a.k.a Helium - %100 Tested Recover From Hard Brick

Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.

Different reactions
Hi,
My device could still boot on fastboot mode, and flashes successfully through it on MiFlash Beta. However, the device remains stuck on Mi logo. I've already tested flashing on EDL mode apparently successfully, with the same results. I've flashed TWRP, but the device don't enter recovery mode. What can I do? Any suggestion will be welcome.

benzersizadam said:
Many thanks for this thread, I stuck on my mi max with no reaction at anything, I read more than 100 threads, I tried testpoint, DFC (deep flash cable), click inside usb terminal to pc, windows 8, 7 10, 32 bits, 64 bits, programms like qfil (qpst), flasher tools for other phones and nothing, before with other apps at first second gives me error "can not read from port COM...", and now at least advance to 5 seconds with same error, I need to know it is neccesary too disconnect, remove two plastic cables down where places the battery
Click to expand...
Click to collapse

Working also with Hydrogen. Thanks.

@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!

coffee-turtle said:
@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!
Click to expand...
Click to collapse
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance

SubwayChamp said:
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance
Click to expand...
Click to collapse
Hi @SubwayChamp Everything I did was in the post and video from above in the first post by benz....
His instructions were perfect along with the youtube video. It's tricky, true, but with patience you can go through the steps and get your device running again. I was so glad that @Qulox gave me this link to this thread.
As you go through the steps, if you get stuck, we can try to give you advice.

This works for Hydrogen as well.
Many thanks

I have two dead mi max. One 128gb helium and one 32gb hydrogen.
128gb helium is completely lifeless. No charging led, no vibrations, no fastboot mode. Though i could bring it up to edl mode showing right qualcomm device in device manager. I tried flashing stock rom as mentioned in this guide which rather went successful without giving any error, even while battery connector was removed.
But mobile is still in same lifeless condition. Other than flashing process going through, it didnt make any difference. Dont know whats wrong. Also i didnt have to use two miflash versions as mentioned in steps as flashing process didnt give any error.
32gb hydrogen, boots up in flashboot mode, shows charging led, mi logo even edl model worked without any issue. It even boots up, but gives error of encryption unsuccessful asking me to reset device. I tried factory reseting it. Tried flashing twrp and wiping, formatting data, changing file system to all formats like fat, f2fs, ext1, ext2, ext3, ext4. Tried flashing crdoid and RR based on orea. Nothing working.
With twrp it keeps bootlooping showing mi logo. And with stock rom, recovery shows up encryption error. Followed procedure mentioned in this guide as well.
Is there anything am i missing or can do? Btw, bootloader is locked for both the devices. I could flash twrp referring another guide which suggested to replace stock recovery in rom files/ folder and flashing it like stock rom through miflash tool.

Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .

cobben said:
Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .
Click to expand...
Click to collapse
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....

Hello,
trying with both Helium & Hydrogen. Still on error like say these logs.
log#1
Code:
[0,02 COM7]:[COM7]:start flash.
[0,02 COM7]:received hello packet
[0,02 COM7]:can not found programmer file.
log#2
Code:
[0,00 COM7]:[COM7]:start flash.
[2,03 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[4,56 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,11 COM7]:try to reset status.
[7,13 COM7]:Switch mode back
[7,13 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,14 COM7]:Riferimento a un oggetto non impostato su un'istanza di oggetto.
Hope anyone can help me. What's my wrong following the guide.
Thanks

harpy.eagle said:
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....
Click to expand...
Click to collapse
Hi there.. The link of video & image of test points is not working. Can anybody please share working links

Hi there.. The link of video & image of test points is not working. Can anybody please share working links

rizkhan77 said:
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
Click to expand...
Click to collapse
This is the video of Test Point https://youtu.be/SqcVY8IWkZI

benzersizadam said:
Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.
Click to expand...
Click to collapse
hi, could someone share with me the miflash beta? I can download the rest but I cannot download the beta one.
thanks

Wanted to say thank you was able to recover my mi max 64gb unit.

[Sharing Method] Bootloader Locked+Dead Boot+OEM Lock+Recovery Stuck

Hello XDA
As title say, I 'm going share my experience in this thread.
History
I purchased this device almost 8 month back.Purchased from a local store.Was very smooth and i was satisfied with the performance.Battery was good.Got regular update and these updates are from google,so why not install it,right?Then this Android N came,and i was so happy.7.0.0 was good.Then the nightmare 7.1.2 came.Phone started to lag continuously,Battery drained too much.But I was like Okay.May be this will fixed in new update.Then suddenly one day my phone was stuck.Not booting.Stucked at Google.I understood that phone already booted and fingerprint was too working but it showed nothing on display just black light.I was afraid as i didn't purchase it from Google Play or any authorized seller.So no warranty or chance of having replacement.So I started searching about this issue and found not only me many people are facing this.But there are no proper guideline or solving this issue.Tried everything and ended up with Locked Bootloader Irony!
Journey
As i never try to mess with my phone because it was Nexus 5x! So i never touch OEM or try to unlock the bootloader.So i tried to access stock recovery,But Alas! in recovery Volume up and down wasn't working.So I couldn't wipe or factory reset.So Now ended up with :
1.Locked Bootloader
2.Locked OEM
3.Recovery Stuck
Googled and found many solutions but none of them came to solve my issue.So i thought why not flash stock rom.But HOW! Cause fastboot only work with unlocked bootloader.And you can't unlock bootloader when your OEM is locked and you can't unlock it with fastboot.It can be only unlocked from developer option only.GOD!
Now I have only 2 options left:
1.Fastboot mod where no functions working
2.Download Mod (This will save you)
Now fastboot option is out and only download mod option is available.So what can i do with Download Mod?
LGUP TOOL helped me.Downloaded a tot file for Global version (LGH791) and flashed it and stucked at google logo and in recovery too.But next time i flashed the same file in a different way.Ok here it is:
1.Drivers are important here.I'm using windows 10.I have adb and fastboot and Lg drivers.Workplace okay.
2.Opened device manager and change the com port of Android phone 3 to 41. Port Changed!
3.Connected my phone to pc using 3rd party cable (Careful here,try to use original cable.) and entered into download mod and.
4.Opened LGUP Tool ,checked REFURBISHED mod,checked BIN file and select the tot file downloaded before.And quicky close it.(No need to click start)
5.Then again opened lg tool and click start.(BIN Checked and it showed the previously selected tot file).No need add anything new this time,just open and click START.
6.Rebooted and again stucked at Google screen.But wait! recovery is working.Pressing and holding volume up button for a while then a android logo with red cross inside will come up.Now holding power button and volume down button at the same time,Recovery will show and menu is working.Great!
7.Now Wiped cache and factory reset.And after that selected Apply update from Adb sideload
8.My device was connected to pc from the beginning,right? Now i downloaded a file previously called bullhead-ota-opp2.170420.019-c449d2bb.zip from Google Nexus 5x OTA update page.
9.In Adb folder,copied the file and named it ota.zip.Opened a command prompt using shift+right click in the folder.Phone was on Adb sideload mode.Typing this command adb sideload ota.zip
10.This took more than 8-9 minutes to finish.After flashing and phone rebooted.WOW
11.Couldn't believe my eyes.The OTA update was about Android O.I quickly enabled the developer menu and made oem unlcocked and usb debugging on.Boot into bootloader and unlock bootloader with this command fastboot flashing unlock
12.Now bootloader is unlocked and i flashed TWRP recovery for future need.
13.Rebooted the phone and after using for 1 minute the phone freezed again
14.This is the end of the story for today.
Planning
I'm thinking the OTA update was the problem.Now I'm downloading 6.0.1 version.And will do a clean install.Let's see what happens next.
Any kind of help is appreciated.If you think there is something i'm missing here then please suggest.
And Thanks to XDA.I got all these helps from here.Will update the post tomorrow.

You downloaded Android O Developer Preview. Final OTAs are here:
https://developers.google.com/android/ota
Just try flashing newest Factory Image via fastboot, but don't forget to flash TWRP back:
https://developers.google.com/android/images

TBH I NEVER thought this phone will be dead by hardware failure all of a sudden, I dont mind another few hundreds bucks but the problem now is the fking data within it.
Cant even pass google logo if you choose Recovery Mode
GG LG, well played

I have a 16gb variant dead....same issue like urs .....can i use the same lgh791 tot file?... in fastboot it says lgh791 16gb

usefully
usefully

I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).

same of my expirience, flash 4CoreOreo..
my nexus 5x now is fully working

the_uker said:
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
Click to expand...
Click to collapse
I suppose that makes sense. Then again, when an instruction is telling you to boot into download mod.....using common sense I'm gonna understand that's a typo and they meant download mode. But you're right, for some folks that may be a bit of a challenge. Common sense isn't as common as it was when I was young.

And the links?
I'm brazilian and i'm having a hard time to find the links to download stuff. Mine is dead and bootloader blocked. The tutorial seems to work but i can't understand well

Interesting. Thanks

I bricked my Oneplus 6t from tmobile and would like to unbrick it if possible.

So I finally rooted my Oneplus 6t from t mobile. I bought the phone from swappa and it worked great. I installed a random rom and it bricked my phone.
I assume it is a soft brick since i can access adb mode but it requires me to power off the phone
and hold the volume keys along with the power button. Otherwise the phone will just boot up and
will be sutck in a continous boot loop. I then tried to fic this issue by using an msm tool found in
the xda fourms. I then entered recovery mode and perfomed a "wipe data/factory reset. I think it hurt more than it helped. Any suggestions on how to unbrick my phone?
I tried using alll three msm tools in this fourm.
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Also the update would fail if i were to use the msm tool (MSMDownloadTool 9.0v1 and MSMDownloadTool 9.0.13)
I have tried reinstalling the qualcom drivers but no luck.
I tried deleting the drivers and allowing windows to detect the phone nad download its own usb drivers
but it did not help.
i apologize if i post this in the wrong section. I am new here.
all links and info i followed to attemp to unbrick my phone can be found in this fourm
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com

falzer2007 said:
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Click to expand...
Click to collapse
that's not very descriptive, produce the error and share results here

dmtec said:
that's not very descriptive, produce the error and share results here
Click to expand...
Click to collapse
Okay so I open the msm tool. Then I have my oneplus 6t (t mobile) turned off. I hold both volume buttons and keep holding them while I connect the USB cable to the phone. Its basically in edl mode at this point. Then I press the start option on the msm tool. The bar fills up with green and completes itself. However a number appears that saids "4s" inside of the square. I assume that means 4 seconds left or completed in 4 seconds. My phone is still in edl mode at this time and will not boot up in any menu (normal.menu, boot menu/recovery mode). Unlesss I boot it manually.
And yes I tried a scenario where I held down both volume buttons, connected USB cord, and then let go. I also tried the scenario where I held both volume buttons, connected usb cord and kept holding the volume buttons until the process completed itself but I would get the same result. "4s"

dmtec said:
that's not very descriptive, produce the error and share results here
Click to expand...
Click to collapse

falzer2007 said:
So I finally rooted my Oneplus 6t from t mobile. I bought the phone from swappa and it worked great. I installed a random rom and it bricked my phone.
I assume it is a soft brick since i can access adb mode but it requires me to power off the phone
and hold the volume keys along with the power button. Otherwise the phone will just boot up and
will be sutck in a continous boot loop. I then tried to fic this issue by using an msm tool found in
the xda fourms. I then entered recovery mode and perfomed a "wipe data/factory reset. I think it hurt more than it helped. Any suggestions on how to unbrick my phone?
I tried using alll three msm tools in this fourm.
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Also the update would fail if i were to use the msm tool (MSMDownloadTool 9.0v1 and MSMDownloadTool 9.0.13)
I have tried reinstalling the qualcom drivers but no luck.
I tried deleting the drivers and allowing windows to detect the phone nad download its own usb drivers
but it did not help.
i apologize if i post this in the wrong section. I am new here.
all links and info i followed to attemp to unbrick my phone can be found in this fourm
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, Falzer. had all but given up and was prepared to head to T-Mobile to buy the 1+ 9 Pro (I almost wish I did not fix my phone... *BUT* I DID!
My issue occurred trying to flash a Magisk patched boot.img to my newly unlocked bootloader phone. I was following an article that alleged one could root the phone without TWRP. I will say this TWRP is your friend; don't dis "him". By the way, unlocking my phone wiped my data so always important to read the whole article first as it was mentioned in the NEXT step.
[Should be including the actual error here - it is found throughout these forums but I cannot recall the exact display. Basically, if you have an unlocked bootloader and then get to the CrashDump screen, follow from here:]
Retrieve the file, boot11.1.1.1.img and download from this thread/link:
OOS stable boot image and patched magisk boot image both for 11.1.1.1.
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out. Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"...
forum.xda-developers.com
Do *NOT* mess with the other file to the right.
Hold all 3 buttons (2 volume buttons + power) and once/if you see Fastboot Mode, release the buttons.
Have ADB installed (you should be able to find plenty of directions for doing this).
From either PowerShell (or *maybe* CMD Prompt started as Administrator as I had been using this "successfully" for most functions):
fastboot devices
fastboot flash boot boot11.1.1.1.img
fastboot reboot
I could not believe my phone ACTUALLY booted (even with the McLaren animation intact; I'm sure one of the gurus here knows why) after all the failed attempts fooling around with MSM Download Tool [4.0] which almost EVERYONE swears by fixes/restores any brick. I understand ON ONE is forcing anyone to use any specific resolution; I am just trying to provide another last ditch effort.
EDIT/Caveat: I did not even check to see how old that thread above is, I believe late September and I had actually taken updates [via TMobile??] until the last one with a week to 10 days *but* that was probably wiped with the boot unlock so I do not know which "update" I got but figured I didn't have much to lose as I already had a "bad" version of a boot.img flashed anyway. Anyone with any technical explanations, feel free to comment. Thanks!

Need help with a bricked Realme 2 Pro

Yesterday I tried to install a different ROM for my Realme 2 Pro (RMX1801)
I tried to flash TWRP but it does not boot into TWRP recovery instead reboot to normal booting, I tried other version of TWRP for RMX1801 but all of them didn't work at all.
After that I accidentally flash TWRP to boot instead of recovery. It ended up soft bricked my phone, goes to bootloop and things. I tried to flash the original ColorOS recovery and boot but I think I got the wrong one and ended up bootlooping so I was stuck
After that, I've made a terrible mistake. I ran the command fastboot flashing lock and the bootloader is now locked. I made the the brick even harder now.
Now my phone can only goes Download mode I guess. I can't get it into fastboot to flash it with different image. It only vibrate and, show the Realme logo and show "boot/recovery has been destroyed, please flash the correct image..."
I can see Qualcomm HS_USB QDLoader 9008 (COM-3) in my device manager, tried to install driver, but using the flash tool it shows "No Device is connected through this port"
I tried to use QFil, but I have trouble finding the right flash file, stock rom can't do the job because it's mising essentials files for QFil to Download
I am truly stuck now, I don't want to go to customer service as my last option. Please help me

no help ?

thuanc177 said:
no help ?
Click to expand...
Click to collapse
Any update?

PrateekPanwar64X said:
Any update?
Click to expand...
Click to collapse
sadly, no

I got it fixed, I connected phone to PC, Pressed all 3: Power btn, vol up & vol down and heard a sound in pc.
My phone was detectable in Device Manager > Enable hidden items and has Q_BULK in Communication Ports. Installed Vivo drivers & contacted a telegram group who fixed it by flashing stock ROM using MSM tool for $10 via teamviewer (You need oopo's username & password authorization so you cannot do it).
You can already see in COM-3 port, All you need is to flash using MSM tool (I tried finding passwords online they didn't worked so ended up paying). So try that (Beware, First check if they're legit guys & do not use personal chat with anyone / Send full payment before your phone is fixed).
& Remember never lock your bootloader.

PrateekPanwar64X said:
I got it fixed, I connected phone to PC, Pressed all 3: Power btn, vol up & vol down and heard a sound in pc.
My phone was detectable in Device Manager > Enable hidden items and has Q_BULK in Communication Ports. Installed Vivo drivers & contacted a telegram group who fixed it by flashing stock ROM using MSM tool for $10 via teamviewer (You need oopo's username & password authorization so you cannot do it).
You can already see in COM-3 port, All you need is to flash using MSM tool (I tried finding passwords online they didn't worked so ended up paying). So try that (Beware, First check if they're legit guys & do not use personal chat with anyone / Send full payment before your phone is fixed).
& Remember never lock your bootloader.
Click to expand...
Click to collapse
Vivo driver

PrateekPanwar64X said:
I got it fixed, I connected phone to PC, Pressed all 3: Power btn, vol up & vol down and heard a sound in pc.
My phone was detectable in Device Manager > Enable hidden items and has Q_BULK in Communication Ports. Installed Vivo drivers & contacted a telegram group who fixed it by flashing stock ROM using MSM tool for $10 via teamviewer (You need oopo's username & password authorization so you cannot do it).
You can already see in COM-3 port, All you need is to flash using MSM tool (I tried finding passwords online they didn't worked so ended up paying). So try that (Beware, First check if they're legit guys & do not use personal chat with anyone / Send full payment before your phone is fixed).
& Remember never lock your bootloader.
Click to expand...
Click to collapse
hi can you tell me the telegram group cause i'm in the same problem like you had.

Retr0_680 said:
hi can you tell me the telegram group cause i'm in the same problem like you had.
Click to expand...
Click to collapse
I had found in xda form like this, I’ll find and message.

i have same issue flashed
NusantaraROM - RMX1801 which requires magisk did install rom. then since banking apps were not working so i uninstalled magisk and my device bricked. now no matter which os i install none is able to pass the rom logo. i check my hardware for emmc issue that guy said hardware is all good. i flashed through edl mode using msm download tool agent charged me 800 and the device still stuck in realme logo.​

i request u guys please help me