[Completed] My Nexus 5x doesn't turn on at all, what can I do? - XDA Assist

So this is what happened, a couple of days ago I was using my Nexus 5x normally when it turned off. I tried to turn it on but nothing happened so i tried to turn it on whith the power and volume buttons it turned on but the screen froze when the loading the colored dots. I tried to turn it on again with safe mode and it worked but the screen froze again after a couple of minutes. Now this freezing thing happened every time i tried to turn on the phone.
A friend told me to wipe the cache partition but nothing happened. the told me to factory restore it, the I was able to turn on the phone but started to reboot some times or just froze when starting, so another friend who knows about android phones told me to do the wipe data/factory reset and thats when the phone turned off while wiping the data, now the phone doesn't turn on at all. I saw the red light like when the phone is out of battery so I started charging it but the red light started blinking a couple of times then stoped.
One more thing, one of the times I turned it one it looked like it was everything ok except that the finger reader wasn't working and there was no google imprint menu so I restarted the phone and de finger reader was working but the phone was rebooting spontaneously. This happened before trying with the wiping the cache and doing the factory reset.
Thats basically what happened, is there something I can do?
My phone is the LG Nexus 5x 16GB whit android nougat 7.0

XDA Visitor said:
So this is what happened, a couple of days ago I was using my Nexus 5x normally when it turned off. I tried to turn it on but nothing happened so i tried to turn it on whith the power and volume buttons it turned on but the screen froze when the loading the colored dots. I tried to turn it on again with safe mode and it worked but the screen froze again after a couple of minutes. Now this freezing thing happened every time i tried to turn on the phone.
A friend told me to wipe the cache partition but nothing happened. the told me to factory restore it, the I was able to turn on the phone but started to reboot some times or just froze when starting, so another friend who knows about android phones told me to do the wipe data/factory reset and thats when the phone turned off while wiping the data, now the phone doesn't turn on at all. I saw the red light like when the phone is out of battery so I started charging it but the red light started blinking a couple of times then stoped.
One more thing, one of the times I turned it one it looked like it was everything ok except that the finger reader wasn't working and there was no google imprint menu so I restarted the phone and de finger reader was working but the phone was rebooting spontaneously. This happened before trying with the wiping the cache and doing the factory reset.
Thats basically what happened, is there something I can do?
My phone is the LG Nexus 5x 16GB whit android nougat 7.0
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here:
> LG Nexus 5X > Nexus 5X Q&A, Help & Troubleshooting
All questions regarding your device belong in the forum linked above. You'll need to create an account first so you can post in the main forums.
Good luck

Related

Phone in bootloop all in a suddent, unable to access Bootloader/Fastboot

Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.
Blitztorm said:
Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.
Click to expand...
Click to collapse
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.
pigstew said:
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.
Click to expand...
Click to collapse
Good Lord!! It actually did work, but how to explain the ART and Dalvik thingy?!
thanks

Nexus 5 Lollipop - Issues after Factory Reset

Hi,
I received the Lollipop OTA last night. I installed the Update and the phone was working "ok" today. As it seemed to be a bit slow (for example the animations and the response to touch input), I thought about doing a factory reset tonight to set up the system from scratch on.
After backup of all my data, I selected "Factory reset" from the settings menu. The phone turned off and started to delete all data after I had entered my locksreen pattern. Now the problems started:
1) After around 5 minutes of erasing data, the process stopped and the screen showed the android figure with the red exclamation mark.
2) I restarted the phone by pressing the On/Off Button --> Deleting of files continues again. The phone is now deleting files for around 45 minutes, but nothing happens.
Is this normal? I am a bit scared that I am stuck in some king of "erase loop". As I need my phone in a few hours, I would be happy if someone could help me.
Some more information if needed:
- OTA to Android 5 from 4.4.4
- German Nexus 5 bought on Google Play
- Phone was never rooted
Thank you in advance for your help!
According to this here, be patient and let it run its course.
I'm in the exact same position you were in. Please tell me this worked out ok....
EDIT: it's finished, and now booting up... nearly an hour, and it's back.
Neokazaki said:
Hi,
I received the Lollipop OTA last night. I installed the Update and the phone was working "ok" today. As it seemed to be a bit slow (for example the animations and the response to touch input), I thought about doing a factory reset tonight to set up the system from scratch on.
After backup of all my data, I selected "Factory reset" from the settings menu. The phone turned off and started to delete all data after I had entered my locksreen pattern. Now the problems started:
1) After around 5 minutes of erasing data, the process stopped and the screen showed the android figure with the red exclamation mark.
2) I restarted the phone by pressing the On/Off Button --> Deleting of files continues again. The phone is now deleting files for around 45 minutes, but nothing happens.
Is this normal? I am a bit scared that I am stuck in some king of "erase loop". As I need my phone in a few hours, I would be happy if someone could help me.
Some more information if needed:
- OTA to Android 5 from 4.4.4
- German Nexus 5 bought on Google Play
- Phone was never rooted
Thank you in advance for your help!
Click to expand...
Click to collapse
It took 90 minutes to delete the data before the phone booted again. The first boot took also around 10 minutes but now everything is working fine and fast
Gesendet von meinem Nexus 5 mit Tapatalk
I'm having the same problem, sitting on the android guy and erasing... I also went to the android guy with a red exclamation mark twice already. It has been doing your for about an hour. I really hope it finishes soon, this takes way too long!

[Completed] Sometimes, my phone's screen doesn't turn on... Why might this be?

I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
XDA Visitor said:
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Dalvik cache trick throws a wrench into things, but I used to have a similar issue with an older device - the screen wouldn't come one, but the hard button backlight would - pulling the battery and rebooting relieved the problem for that fit. I ended up scaling down the max processor speed (as it was being overclocked on the current custom ROM) back to the stock value. The problem went away at the point. But that was for my device, and because yours requires a dalvik cache wipe, it is probably a different cause.
At any rate, please go ahead and create an XDA account. Then, venture over to post in the [Q&A] Help thread. Ask away! (Noob friendly) thread, (or at least) in the > OnePlus One > ONE Q&A, Help & Troubleshooting forum. Your device experts can be found there.
Hope this helps, and good luck!

Galaxy S6 Massive issues

Hi XDA, looking to you for answers...
The Device: I bought my Verizon Galaxy S6 straight out due to that phone trade in for $100 gift cards that happened way back in April. So I have no insurance on the device. No worries, as its in a otter box commuter case with tempered glass and I baby my devices.
The problem part 1:
-Last week just before I walked out the door for my anniversary dinner. I restarted my device and it didn't come back on.
- I plugged it in and got no light. Pressed volume +/-/home/power - and got the boot screen
- Accidentally factory reset the device when I let go off the combinations of buttons (why factory reset is the second option I have on idea)
- After the initial factory reset, I noticed it didn't go through. Rebooted and saw DM-Veritiy verification error
- Tried multiple times to get a clean factory reset until finally I got into the phone setup wizard
- Phone setup wizard froze on me about 3 times before I was able to get it to work
- Finally with finesse and some luck, I was able to get the phone partially restored but I knew something was fishy
- Brought the phone to Verizon which said I have no insurance, the only thing I may have is a manufacturer warranty with Samsung.
- The rep tried to factory reset the phone, however the DM-Veritify verification error came up again and could no longer continue.
- After some time there, I felt like I was wasting my time, Figured I would this myself.
- Went home and flashed the STOCK OS on my galaxy s6 with ODIN.
- After ODIN, and many OTA updates, I was on 5.11 and restoring my phone
After all this, the phone worked PERFECTLY FOR A WEEK
The problem part 2:
- Was in a parking lot to get some groceries, sent a text and put the phone in my pocket. When I looked at it again, the phone was off
- Tried to turn it on... nothing... I held the +/-/home/power buttons again and rebooted normally
- Phone started up just fine but froze after a minute.
- If I get the phone on, it will either freeze/hard-lock or when the screen turns off, then its just turns off, or restarts itself to failure
- I've tried to reboot into recovery volume +/home/power to wipe the cache, however I get an android in distress
- After a few attempts to get into recovery to wipe the cache, I managed to get past the distress icon and press get the menu selection down once before the device froze
- After more attempting to to wipe the cache. I don't even get the android in distress icon anymore, just the blue android screen hangs
- If I use all the buttons to reboot normally - the phone will freeze or once the screen turns off, its off.
thats it
I feel like I just ate $700
XDA please help
Phone freezes in "recovery mode" 3 seconds in. Managed to get one wipe cache in.
Getting a "system rev. check fail device: 3 binary 1 error" error when trying to flash ODIN.
Guess you can't flash stock OS from 5.1.1
got a factory reset to go through just fine. Restored phone for 30 minutes and proceeded to use it.
Seemed fine and then froze while texting.
Seems to be randomly freezing and then a sudden restart.
Contacted verizon for the number to call for warranty send off.
*looks around* I see MULTIPLE issues regarding the S6 randomly restarting.
I should have got the Note 4
Hi,
Sorry, but if it keeps happening persistently even after factory resets and successful stock installs, I'd call it a hardware problem. The best thing you can do is contact Verizon or Samsung and try getting a replacement.
All the best,
~Lord
Sent from my SM-G920I using Tapatalk

S7 dead? (Red Text)

Hi,
my S7 died after 5 days. I had those freeze/reboot issues. Tried changing SIM and SD Card, but the issue was still present. Today I tried factory reset (from settings menu). The phone started with resetting an came up with a red text:
BL2 exception(state: sleep&wakeup)
[ RST_STAT = 0x1000000]
esr(exceptopn class): 0x20000000 (EC=0) et:s0
elr(abort PC value): 0x0204b794 . _ . u0object[r:qmuxd_s
ocked:s
/dev/socket/qmux_badio(/.()?
I can't turn it of or get into recovery/download mode. Just pressing Vol down+Power works, but boots directly into the red text. I allready ordered a new one, but is there anything I can do to get in the filesystem to delete my personal data before I send it back? What happened here?
EDIT: just after I send this post, the battery was empty and it started up normal with factory defaults :/
EDIT2: Ok, still have the freeze/reboot issue, right after setting up the phone and watching the update process from WhatsApp.
Thanks
Pascal
Red text of deth? Samsung S 7
Hi Pascal
Have you found any solution on this problem?
My history
I got the exact same issue. After about a week, the phone went black. Nothing would wake it up except power+Vol down. It failed to boot several times (just looped). After several tries get into boot menu. It showed mr Android with a big exlamation over it. I cleared the cashe and it rebooted, but after some minutes it crashed and restarted. After a normal boot, it worked fine the rest of the day.
When I woke up the next day, it had drained all battery. I charged it to 100% before I started it, and it crashed during boot, then some boot loops and after clearing the cache and reboot the red text appear. I had to wait (a long time) to drain the battery. Now it hanged during the first bootup. After 3 times It booted normally, but while updating apps, it crashes and reboot (or just hang and impossible to wake up).
Im travelling far from home, so I cant return it at the moment. Hopefully someone can help (if its fixable).
Thx
Tommy
turbotape said:
Hi Pascal
Have you found any solution on this problem?
My history
I got the exact same issue. After about a week, the phone went black. Nothing would wake it up except power+Vol down. It failed to boot several times (just looped). After several tries get into boot menu. It showed mr Android with a big exlamation over it. I cleared the cashe and it rebooted, but after some minutes it crashed and restarted. After a normal boot, it worked fine the rest of the day.
When I woke up the next day, it had drained all battery. I charged it to 100% before I started it, and it crashed during boot, then some boot loops and after clearing the cache and reboot the red text appear. I had to wait (a long time) to drain the battery. Now it hanged during the first bootup. After 3 times It booted normally, but while updating apps, it crashes and reboot (or just hang and impossible to wake up).
Im travelling far from home, so I cant return it at the moment. Hopefully someone can help (if its fixable).
Thx
Tommy
Click to expand...
Click to collapse
Best thing we can do is reflash firmware using Smart Switch or odin good luck.
I returned my phone and got a new one. Since I have the new phone, no reboots or other issues.
Gesendet von meinem SM-G930F mit Tapatalk
[email protected] said:
Hi,
my S7 died after 5 days. I had those freeze/reboot issues. Tried changing SIM and SD Card, but the issue was still present. Today I tried factory reset (from settings menu). The phone started with resetting an came up with a red text:
BL2 exception(state: sleep&wakeup)
[ RST_STAT = 0x1000000]
esr(exceptopn class): 0x20000000 (EC=0) et:s0
elr(abort PC value): 0x0204b794 . _ . u0object[r:qmuxd_s
ocked:s
/dev/socket/qmux_badio(/.()?
I can't turn it of or get into recovery/download mode. Just pressing Vol down+Power works, but boots directly into the red text. I allready ordered a new one, but is there anything I can do to get in the filesystem to delete my personal data before I send it back? What happened here?
EDIT: just after I send this post, the battery was empty and it started up normal with factory defaults :/
EDIT2: Ok, still have the freeze/reboot issue, right after setting up the phone and watching the update process from WhatsApp.
Thanks
Pascal
Click to expand...
Click to collapse
Hi i have same problem, what do you suggest should I let battery die and charge the phone? tried using smartswitch to reinstall firmware button it doesnt recognise the phone.
My phone just started after the battery was dead. (Of course you have to charge it before)
Gesendet von meinem SM-G930F mit Tapatalk

Categories

Resources