Database Users

Jiayu S3 3Gb boot loop, i can only access to fastboot

Hello everybody !
I 've spend a long time on this forum and i've found a lot of interesting and useful tips.
I'm in a bad situation today and I can not find a solution so i thank you for the time spent reading this.
Yesterday i've seen an icon on my desktop and i couldn't remember what application it is. I clicked and it was the beginning of an endless nightmare... A huge lag began by making the phone unusable and apps was installing one after one...
When it has calmed down a bit, i tried to install cleaning softwares but i couldn't do anything so I tried to do a factory reset. After that... the malware was still here... So i've decided to clean all by installing a new ROM.
This is a Jiayu S3 4G 5.5 Inch MT6752 Octa Core RAM 3GB 1080P Screen Dual SIM 4G LTE Mobile Phone (invoice description) so i wanted to try the CM12.1 for Jiayu S3 (found on needrom).
My phone was Rooted and TWRP was installed so i've copied the ROM files on a SD card, rebooted in recovery mode, wiped cache, data, dalvic and system and tried to install the new ROM. it was abnormally rapid and now the phone bootloops.
The only thing i can do is activate Fastboot (if i choose normal boot or recovery it continues to bootloop).
I've tried to flash recovery with :
fastboot flash recovery recovery.img
but i get an error message : FAILED (remote : partition 'recovery' not support flash).
Does anyone has ever been in this situation and solved it ?
Thanks for your help !

Hello,
I got exactly the same problem. Did you find a solution?
My phone is in a bootloop, I can only access to the fastboot mode. (fastboot devices show my device).
In this mode, I can't flash my recovery.img:
fastboot flash recovery recovery.img --> partition 'recovery' not support flash.
I can't see my device with the command adb devices (adb devices doesn't show my device, I think because USB debugging is off, but i can't switch it on)
Did someone find a solution ?
Any help would be appreciated, thanks !

That's the behavior of a wrong preloader that was flashed / malware that affected preloader.
Grab a full spftools ROM set, and flash the entire ROM using " upgrade mode"
Cheers
PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
PPS: this will destroy all of your data, so back it up first ..

Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?

mick605 said:
Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?
Click to expand...
Click to collapse
There is no special mode, please serach the forum on how to use sptools, i am sure you will find plenty of them.

Sorry for late answer !
Thanks for this advice, i will try as soon as possible and post if it's ok or not.

Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !

Thanks mick605 !
I travel for work so i can't try all the advices on this forum atm.
I'll check this when i get back home and i'll tell you if it's ok
Thanks again !

mick605 said:
Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !
Click to expand...
Click to collapse
First of all hi I'm new in this thread,
I have installed everything correctly but I still have only 3 seconds before my phone showes the the charging icon and disconnects.
Can anybody please help me? I actually have been stuck with this problem for months now and all these months I have been using the samsung galaxy s advance (launched in 2011) on marshmallow.

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

Damaged recovery, unable to ADB debugging, bootloop

[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom

Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed

Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:

Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*

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

Phone Bricked. PLEASE HELP

I will try to explain everything from the beginning. I was about to install a custom rom install (it was in 7.1.1 stock, unlocked bootloader) so when I was going to do full wipe with lastest TWRP there was an error. Wait for about 15 minutes just in case, but nothing happened so I decided to restart it to try again. But the phone stuck in the ZTE logo and if it tried to enter TWRP was stuck in the logo too, I tried with all versions of TWRP and no one works. Find a post that said I could use TWRP tenfars tool to recover my phone and had to enter the EDL mode. I managed to put the phone in edl mode but now I can not get out of it. I press and hold the power button for a minute and nothing happens (no vibration, no led, no ZTE logo) my pc just does the unplug windows sound. My pc recognizes the phone as QUSB_BULK. When I try to use the tenfars tool I get this message:
C:\Users\Alejandro Saavedra\Downloads\minimal_adb_fastboot_1.4.1_portable>axon7tool -w recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Also try using the xiaomi MiFlash tool (even change the drivers from QUSB_BULK to COM COM 5) but something similar happens, also tells me can not recive hello package.
I'm a little new to this so I beg you a little patience
Please work very hard to buy this phone, there has to be some way to unbrick it. :crying:
If you need any additional information just tell me

If you use axon7tool :
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
If you use MiFlash :
get latest version : https://www.androidfilehost.com/?fid=673368273298954241
check in Devices Manager if is called Qualcomm 8004.

CelesteBlue said:
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
Click to expand...
Click to collapse
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund

Smedslund said:
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Click to expand...
Click to collapse
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.

CelesteBlue said:
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
Click to expand...
Click to collapse
You will find tenfar 3.0.2-2 TWRP at download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Once unzipped, copy it to recovery.bin:
copy twrp_rec_tenfar.img recovery.bin

Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something

ale0796 said:
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
Click to expand...
Click to collapse
That's because you reset the EDL that way. the method is weird but seemed to work...
If you hold the 3 buttons for ~10 secs while the device is in EDL it will reset it

@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.

CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
Actually, it is a nice feature for the few seconds it lasts, but read HERE if you must. Be careful!
Good luck

CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
I'd advice against doing it... I had no trouble with it but a bunch of people now have paperweights. But yeah, the link is the one provided by the other guy above me

Thank you so much @Choose an username... and @amphi66 : that worked !
Anyway I am on G B04 (Nougat).
Do you know some cool mods I should do ?
Like debloat, remove the boot message (done), etc...