Database Users

[Q] [Help] Bricked UMI ZERO

Hey people, can anyone get me a MTK droid backup of UMI ZERO? I need it to see if i can recover my bricked UMI
pleaaasseee.....
Also, it seems my scatter file backup from MTK does not have all t info?? and SP flashtools does not accept the ones included in the Ota-updates... so if anyone please can also get me a good scatter file ... i would be much apreciated.

Hello, you can get the rom including scatter file from Needrom! Just flash trough sp tool and you will be fine.
Sent from my UMI ZERO using XDA Free mobile app

I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway

reisamm said:
I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway [/QUOTE
please tell me how did you make it work...as i am in the same boat..the pc wont recognise it
Click to expand...
Click to collapse

reisamm said:
I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway
Click to expand...
Click to collapse
please tell mew how you did it . i am so upset that my phone is absoluteley dead

Hi there raducux,
Well, this was about another situation, but mixing with ROM's cooking I was able to brick it again it was mrsim who help me (mod at china-devices.com, credit where is due). But I will tell you how I did it.
You need to have the adb android drivers installed and flashtool v5.1 or up (the one I used, but some people use the 3.1 version).
Download this ROM from needrom (scatter file compatible with FT).
Link: http://www.needrom.com/wp-content/uploads/2014/11/Y800_UMI_20141104_1907xx-s7yler.zip or
http://www.needrom.com/download/umi-zero/
Extract, and in flashtools select the scatter file inside the directory you extracted. Press flash, and (after pressing flash) connect the phone to the USB port holding the volume down key (so the phone connects in META mode), and the process should begin.
If all works well after flashing the phone should boot the new ROM, its version 3.01 so you have to upgrade it.
If that does not work, tell me a few things... I suppose the phone does not start or appear the 'Zero' logo, but tell me if when you connect it to the computer you ear the normal plugin USB sound?
FlashTools (all versions)
http://helpadude.com/sp-flash-tools/
Universal ADB Driver
http://www.needrom.com/download/universal-adb-driver/
Tell me if it worked, or if you need more help tell me what happened and how the phone responds. lot of people here also that can help. My 1st thing I check when buying a new phone (for many years now), is if it's 'XDA' Supported...
cheers

reisamm said:
Hi there raducux,
Well, this was about another situation, but mixing with ROM's cooking I was able to brick it again it was mrsim who help me (mod at china-devices.com, credit where is due). But I will tell you how I did it.
You need to have the adb android drivers installed and flashtool v5.1 or up (the one I used, but some people use the 3.1 version).
Download this ROM from needrom (scatter file compatible with FT).
Link: http://www.needrom.com/wp-content/uploads/2014/11/Y800_UMI_20141104_1907xx-s7yler.zip or
http://www.needrom.com/download/umi-zero/
Extract, and in flashtools select the scatter file inside the directory you extracted. Press flash, and (after pressing flash) connect the phone to the USB port holding the volume down key (so the phone connects in META mode), and the process should begin.
If all works well after flashing the phone should boot the new ROM, its version 3.01 so you have to upgrade it.
If that does not work, tell me a few things... I suppose the phone does not start or appear the 'Zero' logo, but tell me if when you connect it to the computer you ear the normal plugin USB sound?
FlashTools (all versions)
http://helpadude.com/sp-flash-tools/
Universal ADB Driver
http://www.needrom.com/download/universal-adb-driver/
Tell me if it worked, or if you need more help tell me what happened and how the phone responds. lot of people here also that can help. My 1st thing I check when buying a new phone (for many years now), is if it's 'XDA' Supported...
cheers
Click to expand...
Click to collapse
indeed. i too have been messing on xda a lot for a long time.
i managed to get into twrp again.
so that must be good...after. the battery died..;.butr mtk preloader doesnt instal;l
please tell me..first i need to hit download only...and after that.... ? the steps are a bit missleding .
---------- Post added at 03:10 PM ---------- Previous post was at 02:58 PM ----------
i managed to bioot the device in emui !!!! this morning..i could acces twrp. pressing volume down when connected to pc ..and the chinesse recovery pressing volume up ... rootjoy cant flash the device as it sais it is unsupported, now...i reeallly need to know the steps for going back to stock
---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------
i am running antarct s emui . with twrp recovery... i need dto know the sp flash tools steps correctly to flash back to stock
preloader doesnt install correctly in pc because volume down...takes me to twrp...and volume up...to the chinesse recovery of huawei,
so preloader starts installing, but when in recovery..it gets dissconected

Could you tell how did you put it in meta mode? I have a Zero with no preloader and in windows it shows up as unknown device. No matter how I try to boot it up (vol- vol+). Other than showing in windows, it's dead. Is there a way to revive ti?

[Q] LG G2 F320L got bricked, almost give up here [PLEASE HELP]

Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance

ecko no yaro said:
Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance
Click to expand...
Click to collapse
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk

I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english

Mati0807 said:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
Click to expand...
Click to collapse
did you try to go from lollipop to kitkat?

heavy_metal_man said:
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means

Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/

ecko no yaro said:
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means
Click to expand...
Click to collapse
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
---------- Post added at 06:20 PM ---------- Previous post was at 06:05 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Right, you need to follow this guide i think. Ensure your read it fully before you attempt anything. Now, the lollipop update apparently changed some partitions so I would flash the bumped twrp from the development section instead of the 2.6.3.2 version recommended. Then once you can boot into recovery flash the rom recommended in this post

heavy_metal_man said:
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
Click to expand...
Click to collapse
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode

ecko no yaro said:
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode
Click to expand...
Click to collapse
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!

heavy_metal_man said:
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!
Click to expand...
Click to collapse
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so

ecko no yaro said:
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so
Click to expand...
Click to collapse
Hmmm. im stumped. I think its a bit of a catch 22 here. What i think has happened is that the rom flash that was done has changed some of the partition layout, but the methods of fixing that issue is either with DD commands from a custom recovery (which you dont have and cannot flash) or with DD commands using ubuntu when the device is auto-mounting all of your partitions. Its worth a look if you have an ubuntu disk around, if not download here, burn to disk or mount it to a bootable usb and see if ubuntu has any luck with it. Either that or try installing any drivers you can on the pc to get download mode working.
there is also this as a last resort but i've never had to do this so i cannot vouch for it :-/ Good luck pal.

Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
and install bumped recovery 2.8.5.1, then next with otg cabble flash these http://forum.xda-developers.com/showpost.php?p=59079665&postcount=536.
and now i install cloudyg2 and i feel great xD thank you!

Mati0807 said:
Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
dear do you have above mentioned tool bcoz i can not download , this page do not open
Click to expand...
Click to collapse

new link http://www39.zippyshare.com/v/UphAeXOO/file.html
With all files for d802. i used these for my phone!
Only run these tool, and smile

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

Reviving the hard bricked yu yureka authentic method

hey guys today I am here to help you with your hard bricked beloved yu .when I got my device bricked(you yureka plus) I searched almost every corner on web to rectify the problem but every where I found words like"yu yureka hard bricked but can be detected by windows as Qualcomm hsb bulk ,fake guides on you tube some other guides which do not match peoples consequences
ANALYISING THE PROBLEM
this guide will work if you found following characteristics in your dead yu
1)its not detected in windows weather you put the PC on test or install the Qualcomm drivers
2)only a red led near the recover glow when you connect it to a power source
RECTIFYING YOUR PROBLEM
okay let's start first make a backup emmc image for yu which will send it to fastboot mode
fetch a memory card of 16gb format it in fat32 now using a IMG writing tool (I used win32 disk manager)write the emmc image on it(will take around 20mins)
I know some people has resource deficiency(like me) but get your yu's battery charged at least 40% now unscrew your you on the main board you will see six golden points now insert battery connect data cable to PC and phone(I had assumed here you have installed yu latest drivers in PC) you will see the red led glows again now press the vol up button and short the 2and 6 points on the main board (by a copper wire)pressing the power button
you will several colored lines come on screen and your device will connect as a verified USB device this is the fastboot mode in yu
Now the real works starts as some people still has locked bootloader I here use the official cyanogen as only stock ROM will automatically boot the device now download the requested files I had given the link viz official firmware for yu
The firmware zip contains ygdp tool open it(password 369) fill the CPB file click on start and done on the first boot several lines will appear they will vanish after you warm up your yu by playing games:laugh:
All credits for ygdp assembly tools goes to the coolpad corporation ,Android mtk for firmware files again coolpad for general coolpad drivers
sorry if you found a little tedious here its my first post by my revived you
Mind a little financial help
paytm no 7404034359(Rs 50 or 20 whatever you like)

Help.....
I have done the above steps and and the flashing of stock firmware is done successfully, but when i turn on the phone it always shows low battery. Is there a problem with my battery or Motherboard?

i had a friend's yureka with bootloop on YU logo,i flashed it using adb fastboot,the phone started vibrating and dint even turned on,only goes to fastboot mode after long pressing volume up and shows red light on connection.I also tried emmc image burning on sd card method but still in same condition.Please help

ygdp tool reference
iamtj said:
i had a friend's yureka with bootloop on YU logo,i flashed it using adb fastboot,the phone started vibrating and dint even turned on,only goes to fastboot mode after long pressing volume up and shows red light on connection.I also tried emmc image burning on sd card method but still in same condition.Please help
Click to expand...
Click to collapse
Bro try flashing stock ROM go to android mtk download from there drivers as well as rom

may be bad battery
davidchellappah said:
I have done the above steps and and the flashing of stock firmware is done successfully, but when i turn on the phone it always shows low battery. Is there a problem with my battery or Motherboard?
Click to expand...
Click to collapse
Bro after flashing stock ROM do it rebooted it self?

It worked dude...million thanks to you!!! Since i burned those emmc image to my brand new sandisk 16gb sd card...it is not formatting nor showing the correct size.. Nothing.... so can you tell me how to use the sd card normally again with detailed and 100%working steps. Thanks in advance!!!!

Harish Topgi said:
It worked dude...million thanks to you!!! Since i burned those emmc image to my brand new sandisk 16gb sd card...it is not formatting nor showing the correct size.. Nothing.... so can you tell me how to use the sd card normally again with detailed and 100%working steps. Thanks in advance!!!!
Click to expand...
Click to collapse
well you see the memory card used by me belonged to
one of my friend and i returned him as it is with image file
written on it. when i asked him how he got it normal he said that he put it in a net setter dongle and formatted by going in disk management but i think a simple card reader will do the job for you

Mosam panghal said:
well you see the memory card used by me belonged to
one of my friend and i returned him as it is with image file
written on it. when i asked him how he got it normal he said that he put it in a net setter dongle and formatted by going in disk management but i think a simple card reader will do the job for you
Click to expand...
Click to collapse
Yeah.. Formatting didn't seem to work so spending some time on internet I repartitioned the memory card using a software and I'm good to go now!!

ZUK Z1 Hard Bricked!!!

please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!

Akshatpunj said:
please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!
Click to expand...
Click to collapse
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84

ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84
Click to expand...
Click to collapse
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!

Akshatpunj said:
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!
Click to expand...
Click to collapse
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..

ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?

This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Akshatpunj said:
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?
Click to expand...
Click to collapse
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG

ADDICTED777 said:
This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG
Click to expand...
Click to collapse
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!

Akshatpunj said:
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!
Click to expand...
Click to collapse
Yo there is a button for that ...u know I'm kind of GREEDY...

ADDICTED777 said:
Yo there is a button for that ...u know I'm kind of GREEDY...
Click to expand...
Click to collapse
Already done...

ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!

Sahaj Desai said:
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!
Click to expand...
Click to collapse
u need a video tutorial that shows how to install .inf file
here is the one:
https://www.youtube.com/watch?v=lJ7WTRW7psA
Now before u proceed make sure u have disabled the driver signature verification.

ADDICTED777 said:
u need a video tutorial that shows how to install .inf file
here is the one:
Now before u proceed make sure u have disabled the driver signature verification.
Click to expand...
Click to collapse
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.

Sahaj Desai said:
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.
Click to expand...
Click to collapse
:good::good::good:

Hei!!! You are the best. I followed your instructions and it seems it works 100%. You saved my day. I cant thank you enough.

ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
Click to expand...
Click to collapse
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(

Walter Black said:
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(
Click to expand...
Click to collapse
keep it charged overnight... fix the power button...then try the mentioned method...

ZUK Z1 Hard Bricked
Greetings, everyone. I've got a hard bricked zuk z1 which just went into the state all of a sudden.
I was using lineage o.s pie roms, and had faced some Random Reboots also. Not sure what happened, but here's what i did:
Installed zuk drivers
installed qualcomm drivers
installed adb and fastboot(minimal abd and fastboot)
installed qfil, which comes with QPST v2.7.0.460
--------------------------------------------------------------------------------
Downloaded the zuk stock firmware files
pressed vol+ and plugged the usb
Got detected in 9008 mode
QFIL also detected it and chose the correct files and started downloading in FLAT build
mode
now, QFIL shows this error at the end:-
Code:
10:17:52: INFO: Looking for file 'gpt_main0.bin'
10:17:52: INFO: Looking for file 'gpt_backup0.bin'
10:17:52: INFO:
Total to be tansferd with <program> or <read> is 78.85 MB
10:17:52: INFO: Sending <configure>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
10:18:17: {ERROR: Could not write to '\\.\COM3', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times}
Writing log to 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
Log is 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Fail:Process fail
Finish Download
Hope someone can help me . Oh, by the way, the bricking is like "fully-dead" bricking. No vibrations, display, led, nothing.
I feel i haven't done anything wrong in the steps also. SO, How to decode this situation??

i am face same problem "help please expert" my zuk z1 show logo and blew light after 10se not display on screen when touch with pc via usb many partition opening with error how to solve it

Hard partition damaged
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil

naseera422 said:
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil
Click to expand...
Click to collapse
Hello there!. As far as i know, from what you've said,
The phone still vibrates and shows led, which is a good thing.
About the qfil:
Check whether you are using the latest version of QFIL. Many errors did arise while using the earlier ones.
Make sure you haven't messed up any QFIL configuration settings, and check whether the selected build type is "FLAT".
If you are having trouble with the current firmware files, then download another one for the zuk z1, and check if it works. This is because errors can come from wrong/bad programmer files.
::::: This is all assuming that there are no driver issues & that you know well, how to work with QFIL :::::
Hope this helps....