Related
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
iXanza said:
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
Click to expand...
Click to collapse
I got this error as well,
After some search it seems using a deep flash cable could, I cannot make one currently so maybe you could take a look and try it
http://forum.xda-developers.com/showpost.php?p=69727277&postcount=2
I just checked the second post in the xiaomi eu thread
"- NEVER wipe /system partition manually in your life!"
hmm, I have always done this
Edit:
Many people reporting the same issue their.
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
iXanza said:
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
Click to expand...
Click to collapse
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
No clue. I'm taking it to the shop for them to do it for me tomorrow.
https://www.youtube.com/watch?v=ED96PJ-qYMM
Do follow the videos, i was hard brick 2 times but now it's working
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Shaky156 said:
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Click to expand...
Click to collapse
I don't really think that this is the problem because the "rom" flash completely successfully. I don't think that the font flash would cause all this mess. Anyway, I left it charging overnight and I keep pressing power button with vol +/- but nothing happens. Thanks anyway. it seems I have to either use test points or deep flash cable.
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
EDIT: ok, got it booting now. The red blinking led is actually a good sign, it means low battery. I just let it charge for about 20 min and the led changed to yellow, and then I could boot it up.
It seems like in all that time the phone was plugged into my PC usb port for flashing, it didn't charge the battery. So I think we should take into account what Shaky156 said, just in case.
jiaming2009 said:
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
Click to expand...
Click to collapse
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
IMTLD said:
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
Click to expand...
Click to collapse
Good to know it also worked for you, I just didn't believe that my battery was depleted from 70% just by hardbriking it...
After installing TWRP it asks to decrypt data even though I did not encrypt, hmmm what now
Edit:
I just did factory reset in TWRP and now I can see sdcard.
IMTLD said:
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
Click to expand...
Click to collapse
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
idmissile said:
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
IMTLD said:
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
Click to expand...
Click to collapse
At that point, I didn't really care if I lost data since I didn't have much on it anyway. Nice to hear that you got yours back. Those were dark hours, yes?
Thanks for giving a hope (checking way to recover from video). I'll get proper screwdrivers soon and try do the same.
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Shaky156 said:
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Click to expand...
Click to collapse
but how my mi5 now hardbricked no fastboot no recovery no edl
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
I can confirm that this 100% works for me. You need to be a bit patient with the tweezers and getting the contact points right. It didn't immediately work for me, and I think I had to try a dozen times at least. But eventually it did recognize it. Once MiFlash can see it, you need to use the latest China stable rom. I tried the latest china dev, but it kept on giving errors of missing hello packets.
I have the one plus 3t have had no issues at all love the phone.
I updated the phone a few nights ago and last night it started acting weird rebooted and then got stuck on the One plus boot screen.
I tried going into fast boot and recovery and doing a factory reset and nothing happen but now the phone will not turn on at all.
I have been searching the internet for how to unbrick my phone. Ran across a method using the unbrick tool. I was able to get it started but with the tool, I get Firehose GetUsfInfo Failed and it stops.
Does anyone have ideas on how to get past this or how to un brick the phone?
I'm using WIndows 10 Pro in Test Mode
Were you rooted or had unlocked bootloader?
Aneejian said:
Were you rooted or had unlocked bootloader?
Click to expand...
Click to collapse
Everything was stock. No root or unlocked to my knowledge.
You said the phone started behaving weirdly after update. What was the exact issue at that time?
Aneejian said:
You said the phone started behaving weirdly after update. What was the exact issue at that time?
Click to expand...
Click to collapse
I went to click on a weather widget and it froze. It then rebooted and went right into a menu at the time that you normally have to push power and Volume up to get to. If I did nothing for 5 seconds it would go past it and get stuck on the one plus logo as it tried to boot.
Huffdowg said:
I went to click on a weather widget and it froze. It then rebooted and went right into a menu at the time that you normally have to push power and Volume up to get to. If I did nothing for 5 seconds it would go past it and get stuck on the one plus logo as it tried to boot.
Click to expand...
Click to collapse
I think the current issue is caused due to the unbrick method used. Your phone was never bricked it seems. What were the steps you followed?
Aneejian said:
I think the current issue is caused due to the unbrick method used. Your phone was never bricked it seems. What were the steps you followed?
Click to expand...
Click to collapse
After it got stuck on the on the one plus logo screen I did the following.
1. Loaded into Recovery wiped the cache.
That didn't do anything
2. Wiped everything
That did nothing
3. Reset all system settings
That did nothing and then it would not boot at all.
IF I would have known better I am betting I could have just flashed the default rom at this stage in the game before doing any wiping of any kind..
From there I went on to the unbricking method
1. Got the Qualcomm driver installed and made sure Windows 7 was in test mode
2. Made sure I could see the phone in device manager after I held power button for 60 seconds and then the volume button for 10 seconds
3. Ran the unbricking software msm 3.0 in administrative mode.
I also made sure windows defender was not running, any firewalls were off and no Anti Virus at the time
It would start trying to run and then would end up with where I am now.
I have tried Multiple usb ports and multiple cables at this point.
Right now the phone will not boot but I can tell the computer can see it however the msm 3.0 will not download anything it gets stuck every time.
I do have an appointment with tech support tomorrow with One Plus so that is nice
Hope it is in warranty period. When you connect phone to computer, can you see the storage?
use oneplus 3t unbricktool at androidbrick
ghe2167 said:
use oneplus 3t unbricktool at androidbrick
Click to expand...
Click to collapse
I tried that and even had One Plus help me with their tech support and nothing works. They think the motherboard might have an issue and is asking for $190 more since I am not the original owner. Kind of crazy if you ask me.
Not sure there are any other options I always get stuck at Firehose GetUsfInfo Failed. I have tried 2 computers now and 4 different cables.
Kinda at a loss of words. Unless something crazy happens I will have to sell my phone at a loss and will have to go back to an older phone most likely.
While I was using my k20 pro which runs on the latest miui11 update it suddenly restarted and got into a bootloop. Note that I have a locked bootloader and have not flashed any roms. Since I had no experience in the matter i tried to reboot it by pressing volume down and power buttons. I was not used to fastboot mode hence I tried to restart it with the power button and ended up with "this system has been destroyed" screen, which told to press power button to shutdown, which I did. Now the phone is not responding to anything. What to do? Is it possible to fix it without loss of data?
Please help.
nikhilr297 said:
While I was using my k20 pro which runs on the latest miui11 update it suddenly restarted and got into a bootloop. Note that I have a locked bootloader and have not flashed any roms. Since I had no experience in the matter i tried to reboot it by pressing volume down and power buttons. I was not used to fastboot mode hence I tried to restart it with the power button and ended up with "this system has been destroyed" screen, which told to press power button to shutdown, which I did. Now the phone is not responding to anything. What to do? Is it possible to fix it without loss of data?
Please help.
Click to expand...
Click to collapse
This is the only way to fix this error: https://forum.xda-developers.com/k20-pro/how-to/edl-flash-how-to-fix-hard-brick-t3968400
Good luck!
Service centre
Since the phone still is under warranty period I assumed it best to give it to an authorized service centre. They checked it and said there is some issue with the board and will have to change it. They tried removing the backside and using "edl", but to no avail. I'm told to wait 8 days until I get it back fixed.
I'll lose all my data though?.
Anyway to recover all the data once the board is changed?
nikhilr297 said:
Since the phone still is under warranty period I assumed it best to give it to an authorized service centre. They checked it and said there is some issue with the board and will have to change it. They tried removing the backside and using "edl", but to no avail. I'm told to wait 8 days until I get it back fixed.
I'll lose all my data though?.
Anyway to recover all the data once the board is changed?
Click to expand...
Click to collapse
Unlikely. The storage chip should be on the board too so you should be getting a blank chip.
nikhilr297 said:
While I was using my k20 pro which runs on the latest miui11 update it suddenly restarted and got into a bootloop.
Click to expand...
Click to collapse
Am I not sure if I should believe this or not. Sorry
take it to the service center as others have recommended since your phone is still under warranty.
Helllo,
My Mi A2 can't boot into the system it keeps restarting all the time. Even when I have tried go to fastboot mode, it goes it, but after several seconds it restarts, so I can'd do anything about it.
I have tried power+up, but "no command" error.
What can I do?
Is there any solution?
arshileus said:
Helllo,
My Mi A2 can't boot into the system it keeps restarting all the time. Even when I have tried go to fastboot mode, it goes it, but after several seconds it restarts, so I can'd do anything about it.
I have tried power+up, but "no command" error.
What can I do?
Is there any solution?
Click to expand...
Click to collapse
Open the phone with screwdriver and short the "test point" ...then when in edl flash the stock ROM ....and anyway after that ..in fastboot boot twrp and flash a zip from the global telegram group or my other posts to restore your persist
If after that your phone still fails to work it is a hardware problem causing this ....
Sent from my wayne using XDA Labs
KevMetal said:
Open the phone with screwdriver and short the "test point" ...then when in edl flash the stock ROM ....and anyway after that ..in fastboot boot twrp and flash a zip from the global telegram group or my other posts to restore your persist
If after that your phone still fails to work it is a hardware problem causing this ....
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
short the "test point" ...then when in edl flash
Can you share with me more details about it?
arshileus said:
short the "test point" ...then when in edl flash
Can you share with me more details about it?
Click to expand...
Click to collapse
It is a physical process not in software so just Google a video on YouTube so you can see the physical actions and copy it
Sent from my wayne using XDA Labs
Update:
I have replugged all the cables and while battery was drained I have turned it on again.
It worked!
I even make an update for android. But after some period of time, it started restarting and now I have the same loop.
I have unlocked the bootloader while it was working, but it doesn't help me right now at all.
Phone keeps restarting...
While it was working and charghing, some application was automatically opening and sensor started making some clicks.
When I had the same ecounter with other phones, it was battery fault.
What do you think guys?
I am also facing this issue. Sometime it reboots randomly but other times it works fine. Should I roll back to Android Pie?
arshileus said:
Update:
I have replugged all the cables and while battery was drained I have turned it on again.
It worked!
I even make an update for android. But after some period of time, it started restarting and now I have the same loop.
I have unlocked the bootloader while it was working, but it doesn't help me right now at all.
Phone keeps restarting...
While it was working and charghing, some application was automatically opening and sensor started making some clicks.
When I had the same ecounter with other phones, it was battery fault.
What do you think guys?
Click to expand...
Click to collapse
Hi! I am facing a similar issue: Suddenly my phone shut off. When I wanted to turn it on, it would shut itself off after ~3 seconds of the boot screen. If I plug it to charge, it would start rebooting every 3 seconds.
I have left it charging for a long time, and at a certain point it stops doing this and shows that it is fully charged. I have tried to unplug it and turn it on after this, but I am getting the same result. Once again, charged it, and tried to turn it on while connected. It turned on, but once I unplugged it (before unlocking it) it froze .
Recovery mode does not work (same result), but fastboot works. Unfortunately I can't flash it as I can't risk losing all my data.
Having said this, I want to know more details about what has worked for you. Did you drain the battery and then connected it to charge?
emee2k said:
Hi! I am facing a similar issue: Suddenly my phone shut off. When I wanted to turn it on, it would shut itself off after ~3 seconds of the boot screen. If I plug it to charge, it would start rebooting every 3 seconds.
I have left it charging for a long time, and at a certain point it stops doing this and shows that it is fully charged. I have tried to unplug it and turn it on after this, but I am getting the same result. Once again, charged it, and tried to turn it on while connected. It turned on, but once I unplugged it (before unlocking it) it froze .
Recovery mode does not work (same result), but fastboot works. Unfortunately I can't flash it as I can't risk losing all my data.
Having said this, I want to know more details about what has worked for you. Did you drain the battery and then connected it to charge?
Click to expand...
Click to collapse
same problem. i have gone to service center they are changing whole mother board and charging 500inr what to do?
Jeetesh00 said:
same problem. i have gone to service center they are changing whole mother board and charging 500inr what to do?
Click to expand...
Click to collapse
That seems quite cheap. It's up to you, I guess.
If you want to solve it yourself, you can give it a try to flash it in EDL mode. I have tried it with no success yet.
I just wanna ask after the oct update i got bootloop now when i try to go to service center they told me that the problem is the motherboard. When i explain to them the reason i just update it then bootloop they always tell me the problem is motherboard. And i need to fix it and the cost is half the price of the phone. Now i need some help. When i try to turn on its stuck to androide one then off whne i try to go to fastboot its okay. When i charge it it turns on and off. I jus need some help.
mrvonzuela said:
I just wanna ask after the oct update i got bootloop now when i try to go to service center they told me that the problem is the motherboard. When i explain to them the reason i just update it then bootloop they always tell me the problem is motherboard. And i need to fix it and the cost is half the price of the phone. Now i need some help. When i try to turn on its stuck to androide one then off whne i try to go to fastboot its okay. When i charge it it turns on and off. I jus need some help.
Click to expand...
Click to collapse
is your bootloader unlocked?
If so, have you tried booting latest twrp image from fastboot?
Code:
fastboot boot twrp.img
Sounds like you may at least have to try to wipe and format your phone at the cost of all data.
But then you could use the situation to install a good custom ROM..
If you were doing a normal update, your phone should revert to the previous slot after a few attempted reboots.
Keep trying to reboot.
If nothing else works, try flashing september version from EDL (search it on the forums).
I flashed and still couldn't boot at first. I tried restarting a lot of times, until it got on the "Retry" or "Power off" option. I let the phone sit on this screen until it shut itself off. After tried booting up a few more times until it finally did.
I was not plugged in during this.
I'm not going near that october patch ever again.
Hello everyone,
I'm using mi A2 (64gb). It is rooted and was running on Resurrection Remix 8.6.2. Somedays earlier, I let my phone idle, suddenly it starts rebooting, just like bootlooping. After seeing that I booted in recovery and wiped dalvik and cache then rebooted and the phone rebooted in system successfully. But then I noticed the power menu appearing continuously on the home screen, I tried to dismiss it but it rebooted again and so on. From then, only the splash screen appeared for 8 seconds and it reboots again. I can boot into recovery or fastboot but only for 2-3 seconds then it reboots.
I've searched on the internet and was flashing firmware manually from fastboot but accidentally, I flashed an image file in a wrong location and the phone screen turned off and nothing appeared. Then I found that it had entered in EDL mode. but still it is rebooting and I can't flash firmware from mi flashing tool as fastboot wasn't working.
This is the problem of my phone. A help would be amazing! Thank you!
Ps. I'm new here and it is my first post so if anything is wrong. I beg your pardon and sorry for my bad English.
Rm789 said:
Hello everyone,
I'm using mi A2 (64gb). It is rooted and was running on Resurrection Remix 8.6.2. Somedays earlier, I let my phone idle, suddenly it starts rebooting, just like bootlooping. After seeing that I booted in recovery and wiped dalvik and cache then rebooted and the phone rebooted in system successfully. But then I noticed the power menu appearing continuously on the home screen, I tried to dismiss it but it rebooted again and so on. From then, only the splash screen appeared for 8 seconds and it reboots again. I can boot into recovery or fastboot but only for 2-3 seconds then it reboots.
I've searched on the internet and was flashing firmware manually from fastboot but accidentally, I flashed an image file in a wrong location and the phone screen turned off and nothing appeared. Then I found that it had entered in EDL mode. but still it is rebooting and I can't flash firmware from mi flashing tool as fastboot wasn't working.
This is the problem of my phone. A help would be amazing! Thank you!
Ps. I'm new here and it is my first post so if anything is wrong. I beg your pardon and sorry for my bad English.
Click to expand...
Click to collapse
Try shorting testpoint in motherboard then enter EDL mode,
Then use mi flash tool.need to remove battery first.
How? Watch youtube, for mi6x. Mi 6x = a2, sort of.
~yes, you need to remove/open the phone.
shizuni said:
Try shorting testpoint in motherboard then enter EDL mode,
Then use mi flash tool.need to remove battery first.
How? Watch youtube, for mi6x. Mi 6x = a2, sort of.
~yes, you need to remove/open the phone.
Click to expand...
Click to collapse
Thank you for replying
One thing to note I'm in edl mode already. Do I need to short the test points again?
Rm789 said:
Thank you for replying
One thing to note I'm in edl mode already. Do I need to short the test points again?
Click to expand...
Click to collapse
U said rebooting even in edl, if not. Dont. Just make sure you have enough battery juice.
Use xiaomi tools. Or not, I uncompressed the file and click flash all.
shizuni said:
U said rebooting even in edl, if not. Dont. Just make sure you have enough battery juice.
Use xiaomi tools. Or not, I uncompressed the file and click flash all.
Click to expand...
Click to collapse
Yes, phone is rebooting in edl mode. I also charged it to around 40 minutes before connect it to pc but no hope. I got it
Thank you so much for the clarification.
i have a similar issue, phone reboots when flashing reached vendor b and goes into bootloop, anybody ?