Today I have had the same issue 3 times. Not a single one before (MI9 6+128 global since July).
Check the phone, lock, to the pocket. Later, take the phone to check it and screen off, not responding to anything.
At the third occurrence I tried to connect via adb, but no device detected.
The only way to revive was to Pwr+VolDown to Fastboot and then Pwr until reboot. Some bootloops happened though but it finally came through, for now.
Any idea what is happening??? As mentioned, phone is 100% stock, no root or custom stuff whatsoever.
Hi friend,
So you can try "factory reset".
Good luck.
[email protected] said:
Hi friend,
So you can try "factory reset".
Good luck.
Click to expand...
Click to collapse
Today happened again. I managed to PWR+VOLUP to reboot. So far so good.
30min of standby later, irresponsive again. No key combination would switch on the phone. No reaction to charger, PC connection, nothing.
Incidentally, both occurrence sets (yesterday and today) happened at home; in the office I have had no issues. Some wifi issue? A neighbor testing a EMP device?
Let's go for warranty... but I seriously doubt I will keep with this brand... they need to take software and QA more seriously. My wife's Redmi Note 5A is also victim of these spurious "blackouts" though they have been recoverable so far.
Related
So last night I tried booting in to recover. My phone powered down and never turned back on. Haven't been able to get any response since. I've tried multiple button combinations. I've tried the unbrick tool and so far nothing has worked. Finally contacted One Plus and none of the things they've asked me to try have worked. Think they are going to make me send it in for repair before they replace it, so I have to go weeks without a phone. Never dropped it, wasn't in water. I've never had a phone do this. Is it really worth staying with a device that stops working after a reboot? Any help would be appreciated.
I was running stock with Blu spark and no root just TWRP.
justibasa said:
So last night I tried booting in to recover. My phone powered down and never turned back on. Haven't been able to get any response since. I've tried multiple button combinations. I've tried the unbrick tool and so far nothing has worked. Finally contacted One Plus and none of the things they've asked me to try have worked. Think they are going to make me send it in for repair before they replace it, so I have to go weeks without a phone. Never dropped it, wasn't in water. I've never had a phone do this. Is it really worth staying with a device that stops working after a reboot? Any help would be appreciated.
I was running stock with Blu spark and no root just TWRP.
Click to expand...
Click to collapse
Have you tried plugging into power source? Samsung had a weird thing (soft brick) where only connecting the charger would recover.....
Other than that a freak incident has occurred & shouldn't discourage you from what is a great device....[emoji106]
Brought to you by my ElementalX Powered Oneplus 3T
Duncan1982 said:
Have you tried plugging into power source? Samsung had a weird thing (soft brick) where only connecting the charger would recover.....
Other than that a freak incident has occurred & shouldn't discourage you from what is a great device....[emoji106]
Brought to you by my ElementalX Powered Oneplus 3T
Click to expand...
Click to collapse
It's been plugged in for almost 10 hours.
justibasa said:
It's been plugged in for almost 10 hours.
Click to expand...
Click to collapse
Disconnect then try the power & volume down, then reconnect & do the same , be patient and allow 10-15 seconds on both, if that fails, I can only put it down to a freak occurrence & return your unit.
Brought to you by my ElementalX Powered Oneplus 3T
Duncan1982 said:
Disconnect then try the power & volume down, then reconnect & do the same , be patient and allow 10-15 seconds on both, if that fails, I can only put it down to a freak occurrence & return your unit.
Brought to you by my ElementalX Powered Oneplus 3T
Click to expand...
Click to collapse
Been doing that for the last 2 hours. I've tried everything I can think of.
justibasa said:
Been doing that for the last 2 hours. I've tried everything I can think of.
Click to expand...
Click to collapse
Yeah if you have been through all options (and followed correctly) which I assume you have and been attentive to the guides, then I can only assume there has been a hardware malfunction.....and although an extreme annoyance its best to return....
Sorry to here of your experience. Best of luck.....[emoji106]
Brought to you by my ElementalX Powered Oneplus 3T
On April 6, my Mi 9 started turning off at random times - I tried but was not able to reproduce it, so could not identify the root cause to any app / battery level / etc. I could turning it on again by just pressing the power button. It would be stable for a couple of hours until it would shut down again.
On April 7, same symptoms shown, but just pressing power would not turn it on again. I had to press volume up and power, get to recovery menu and mark "reboot to system".
On April 8, same symptoms show, but this time, no key combination would turn it back on. If I connect the charging cable to power, no led would blink and there was no battery charging animation. Connecting to the computer, there was no USB device identified. It was dead.
On April 9, in the morning, while trying to turn it back on, it would blink the notification led twice, but that was it. So I sent it to a service repair shop - not a Xiaomi authorized service repair.
On April 13, the service repair shop has provided me a quote for fixing the phone: reformatting the phone. Since for me this was a hardware and not a software problem, I collected the phone back.. and it was working as if nothing happened, no software was updated.
On April 14, it shut down again, twice. Pressing the power up worked fine.
On April 15, I unlocked the bootloader and flashed the software again with MiFlash on fastboot mode.
The phone is now stable, although it's my secondary phone now - so I use it much less frequently. But since I have no idea what triggered the problem, I don't know if the phone is stable enough, or if the issue will repeat at any minute - especially when I most need the phone.
Also, I tried contacting the service shop technician, to check if he reconnected the battery cable or checked for any short circuit on the board, but couldn't because of the lockdown. So I have no idea why phone is back from the dead, and no idea if/when it will turn itself randomly again.
So my question to the experts:
1) What could have caused this issue with the phone? What are the possible ways to monitor / check what could have caused the issue? Is there any way to capture a crash report after fact?
2) How can I ensure that this won't happen again? I already reflashed the phone, but I wonder if I should do something else..
3) What can be done to try to reproduce the issue? If there is a way to learn from the phone crashing, what are the things I can do to improve the odds of the phone crashing again?
Thanks!
Update: I left the phone to be serviced... and they could not find any issue with the phone. It is now working, but I'm pretty sure in 1 or 2 days it will stop entirely again...
.. and have no way to monitor it
tha same problem here. my mi9 suddenly died! what can i do? waiting the service or buy a new one?
the same problem, my phone just suddenly said the system was destroyed
Same problem here. Service said "no warranty - damage due to damp"
I doubt it. But now I have to handle it on my own.
@lusp00ky: Does your phone still work after you re-flashed it?
Still hope the best ;-)
bollacken said:
Same problem here. Service said "no warranty - damage due to damp"
I doubt it. But now I have to handle it on my own.
@lusp00ky: Does your phone still work after you re-flashed it?
Still hope the best ;-)
Click to expand...
Click to collapse
Unlock BL and clean flash did not work for me.
Now it is dead until the battery is drained. After that it can be brought to live again by a charger.
I don't get it. -.-"
My X2 Pro has been a great buy up until this morning when I went to look at my phone and it was off having been on during the night,
I pressed the power button and the Realme logo was flashing for around five minutes,
(The logo might stay steady for a few seconds then go back to flashing),
It eventually got to the password screen. Not the SIM password screen which would usually come first on a proper boot up,the phone would not accept my password but luckily I was able to power off the device from here and it rebooted normally,
Bit scary though this behaviour,I'm on the EU model running RUI .24 update unrooted,
Thinking of doing a hard reset but wondering what could cause this ?
maybe the battery is bad, was it low when it happened
does it work now?
Derek100 said:
maybe the battery is bad, was it low when it happened
does it work now?
Click to expand...
Click to collapse
There was around 50% left,phone is working fine since though,Am just putting it down to a bug in RUI.If it happens again I will hard reset
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Essex_Hal said:
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Click to expand...
Click to collapse
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
BorisMKD said:
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
Click to expand...
Click to collapse
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Essex_Hal said:
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Click to expand...
Click to collapse
They fix it, it said it was software problem, got stuck on rebooting. I get it today (2 weeks later) and it worked. They managed to turn it on but without a factory reset, every app was there, every picture, video, contacts, call history, etc. I don't know how they did it, but they did. So when I got my phone back I tried to restart it normal way, long press of the power button, then tap Restart and again restart. The phone restart it without a problem. I was happy. Then later that day (2 hours ago when I'm writing this, I notice that always on display when i touch the phone screen will show up but doesn't switch off after 10 seconds (I set it up like that), instead it started to blink in intervals like i was touching the screen continuously. Then I did a deep soft reset. You know, when you press Volume down and Power button at the same time and.... got the same problem again. Phone is non functional, none combination of pressing buttons worked, just like i describe it in the OP. Just for information, I did the same on my previous phone Galaxy A7 2018 and never had this problem. I did it on this phone too, never had a problem. Then I remember it that on both phones when i do that and not having problems were running on Android 10. this phone now update it to Android 11 and that buttons combination is probably bricking the phone. It's just a thing I notice. So I am planning to call the official service that fixed the phone how did they do it, so maybe I can do it myself too. I don't want to wait for another 2 and a half weeks.
I am facing the same issue. And I think my warranty is out. Did you get to ask them how can you turn it on yourself!!
I would really appreciate some help here!
BorisMKD said:
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
Click to expand...
Click to collapse
have same issue too anyways to fix it?
Hey all! New here. I just soft bricked my phone, i woke up to it not booting. I tried various fw in Odin, but no success. This is my day to day use phone, I don't have anything else, so I'd like to make it work again ASAP, hopefully without factory reset.
Hi
what manipulation did you do to get there before flashing a lot of stuff in odin?
I've been just pressing the buttons all around, then I read about Odin, so I tried it. Now my battery died, let's see if I can get to wipe the cache...
Update: no success. Is there a way to get it into recovery? the old volume up+bixby doesn't seem to work.
Sometimes its because the recovery itself is error so that button combination is not working..
Charge your battery until full, then factory reset it with odin, let see if that works
But before you do that make sure you download correct fw that match your phone model. dont try all fw available there, make sure you download fw for SM N950F..
Well it worked and it broke again... Back to square one.
Your infos are kinda vague.
Did you modify your phone and it got triggered by user-action, or did it hit the fan by itself?
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
fzoli469 said:
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
Click to expand...
Click to collapse
This was happening to me too before my phone just started bootlooping to recovery
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
fzoli469 said:
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
Click to expand...
Click to collapse
Try changing build prop, ro.config.tima to 0