I was using my Nexus 5X, suddenly the phone turned off, and then turned on alone, then the Google screen appeared and disappeared, and is appearing and disappearing the google screen and the phone does not start
Someone had the same trouble and can help me?
@gustavobrze: this is called bootloop and often discussed here, enter sudden death in search.
Most likely the solution is a new motherboard, so i hope you still have warranty.
Related
Hi board !
a view weeks ago I had to reinstall my Universal and used Ranju_v76_WM61_19209_19209_1_0_2 (actually my first WM6) but I am running into several problems:
1) the phone-part of the device is often turning off itself. I mean, I have to go to wireless manager then and turn it on again. The main problem is, that often I do not realize that and I even do not realize that people can not call me.
2) Often, when I receive a call and the screen is turned off, the screen turns on, but i takes about half a minute, till the phone starts to ring (I can´t even pick up then by using the hardware button, the device is like freezes).
Does anyone have similar problems or knows solutions for this strange behaviour of the device ?
Thanks in advance,
Otto
your questions about this ROM, I think it's better to do here:
http://forum.xda-developers.com/showthread.php?t=367448
In addition, if you read the post, it is likely that your problem has already been exposed and resolved.
Greetings.
anyone had problem with the screen not responding after waking up?
There's no way to turn off the phone / make it respond unless to unplug the battery and plug it in again. Had this problem on the first GN and my second replacement GN.
Yep, happened to me the other day as well. There was a crash right before which made the phone reboot. Once it came back, the hardware buttons responded fine but the touchscreen was dead until a battery pull.
Hasn't happened since though.
Had this at lunch today also had it a few days ago.
When returning from sleep the touch input seems to be completely unresponsive.
I left mine for a while to see if it recovered, it did, it came up with the crash report for "System Process" The screen was then responding fine.
Weird. This is indeed different to the sleep of death, because the screen comes on.
Although maybe it's related in some way?
This just happened to me, and so I googled to find an answer. It thankfully led me here. It's like you guys described: I just tried unlocking my phone, but the screen was completely unresponsive. Not a single touch would register, even when trying to touch the Power Off option.
I read robaldred's comment, so I decided to try the waiting game. Thankfully, after a few minutes the screen just came on and the device was ready to use. I don't believe I saw a crash report though.
I hope this won't become a serious issue. I'd hate to be stranded at a point when I need to use my phone.
I had this problem too. have you guys used custom notification sounds?
Sent from my Galaxy Nexus using XDA App
I had this exact problem and I found it was due to Juice Defender (I have the Ultimate version as well). It kept happening after I installed and but since removing it over a week ago no problems.
Just had it happen here, had to pull batt. Using BatteryXL but will keep it on and see if it happens again.
So my Gnex has been working fine since I got it (I am not sure exactly when but it was relatively soon after it came out). I unlocked it but never ended up flashing any ROM or anything. The only issue I've had with it has been that since I installed Google Drive on it about once every hour it asks me if I want it to use Gmail or Drive to perform an action without any other prompt.
Current Problem: The phone will not boot without being plugged in. However, when I do get it to turn on, it gets stuck at the Google logo screen. Something is definitely wrong at this step because a few times the word Google seemed to be popping up all around the screen and shaking around. A few other times at this step the word Google disappeared and then very slightly green stripes started rolling up the screen and slowly getting narrower.
I figure it is probably dead, and I was not able to find any other threads on this but I figure it is worth seeing if anyone else has encountered this.
Randthepeaceful said:
So my Gnex has been working fine since I got it (I am not sure exactly when but it was relatively soon after it came out). I unlocked it but never ended up flashing any ROM or anything. The only issue I've had with it has been that since I installed Google Drive on it about once every hour it asks me if I want it to use Gmail or Drive to perform an action without any other prompt.
Current Problem: The phone will not boot without being plugged in. However, when I do get it to turn on, it gets stuck at the Google logo screen. Something is definitely wrong at this step because a few times the word Google seemed to be popping up all around the screen and shaking around. A few other times at this step the word Google disappeared and then very slightly green stripes started rolling up the screen and slowly getting narrower.
I figure it is probably dead, and I was not able to find any other threads on this but I figure it is worth seeing if anyone else has encountered this.
Click to expand...
Click to collapse
Did you try using fastboot?
Sent from my Galaxy Nexus using XDA Premium HD app
that called semi-bricked.. can u boot to odin page???
or your pc just detect ur devices as omap?? i faced it twice..
galaxy nexus i9250
Hi i have this supper anoying problem after 5.0.2 update! So basicaly What it does is when ever i will pick up the phone it would turn off like the screen would dim (not rebbot or shut down) and after a little tapping on a screen it would turn on again and sometimes when it does that it would glitch a little. While typing this it happened twice its sooooo anoying idk what to do now if i wont find any solutions i will just buy samsung galaxy or something like that. Also my carrier is Virgin Mobile thanks
Same problem, same phone.
Definitely annoying! Seems random but especially while rotating for me. I have not been able to dig up any solutions thus far.
Check out your proximity sensor settings in the HTC testing app, or try Gravity screen. Mine did the same thing a couple times, also clean off your screen at the very top left, if you look real good you can see the sensor just under the front camera hole in the glass, also sometimes a screen saver will mess with this sensor. One more thing is the stock lock screen can cause an issue similar to what you are talking about, hope one of these help yo out, cane0716
Sent from my 710C using XDA Free mobile app
hi
thanks for information i already gave that phone to my friend and i think he fixed it by actually having different lock screen i currently have samsung galaxy s5 its wayyyy better lol
Phone turns off during use and will not complete boot unless plugged to charger even when the battery is almost full.
This error started last night after I did factory reset because of observed phone lag. I did mistakenly "wiped internal storage" but got the alert of "no OS during reboot", so I restored from my backup from SD.
the phone started properly but went off during initial setup and will go back off each time I tried turning it back on. I thought it was battery so I plugged it to power.
it did boot but will go back off once I have few touches on the screen.
I had to leave it plugged to setup my accounts else it will go off.
I'm using its Wi-Fi to send this message via my PC because any 2 - 3 touches will switch the phone off.
once it does that, it won’t even boot to bootloader before it goes off again unless plugged to power.
what I do to solve this please??
Hey hey,
I'm experiencing the follow issue with my Pixel 3a XL. I put it onto charge at bedtime, and when I got up in the morning after the alarm went off the screen got black and unresponsive. I believe the phone is still working at this point because I can hear vibrations when I try to turn it off or boot into fastboot mode, but the screen is totally dead.
Anyone experiencing anything similar? Any ideas or suggestion on this one?
I experienced the same thing last week. Happened two days in a row and in addition to what you stated it seemed that my default home launcher had been unset in default apps, My phone seemed to bounce between launchers while navigating.
I'm running lineage and at 1st I thought maybe it was something in the update, but I don't think that was actually anything to do with it. If you're not running lineage then it for sure wasn't. Maybe a rogue app update, google services? I don't know.
I also don't know what cleared the problem up. Like I said the only thing I noticed was my default home launcher had become unset, and I set it back in default apps. Maybe something relating to that caused the phone to act seemingly dead?
Either way, if you just hold your power button for 15 sec or so it'll reset, and check your default home app. I don't really know the cause or solution, but it seems to have cleared up since then and everything is back to normal.
Hi,
I am experiencing the same thing with my pixel 3xl. I plugged it in before going to bed and in the morning it was unresponsive and black screen. I tried changing chargers and plug but nothing changed. When i plug it in a PC it shows QUSB_BULK_CID and then the serial number but nothing else. I have found many people in the google support forums that have the same issue (https://support.google.com/pixelpho...-pixel-3xl-black-screen?hl=en&msgid=121361292) but no one has replied with a fix or even an update.
Have you resolved your issue?
This is an annoying problem that I've been suffering from my pixel 3a xl for a long time. This would sometimes happen to me when just using my phone regularly but happened a lot more often when charging my phone overnight. When it first started happening to me, I noticed that I could resolve the problem by not having any magisk modules enabled.
However, this didn't seem to be a permanent solution. Nowadays my phone occasionally locks up in the way you describe, but if I leave it alone it usually comes back to a working state in about 4-8 minutes. It's very annoying and motivating me to get a new phone.
It might be worth taking a look at this issue thread on the magisk GitHub that describes the same error: https://github.com/topjohnwu/Magisk/issues/3171
My phone did this yesterday. I woke up and it was unresponsive, seemed dead. I just held the power button, restarted, and back to normal. I know had a bunch of google apps update the day before and even that morning. If I remember right, I had google apps update the last time it happened. I think there something there that's causing the problem, and once the phone is restarted it's good.
I can't say that's it for sure, but it's something I noticed. It is kind of odd that when it happen to one person here, there's usually another in about the same time frame.
Yeah mines still dead and unresponsive. I lost hope like two days ago. There was nothing out of the ordinary when it happened and no weird updates. Just plugged it in like every night and then it bricked during the night.
vagelisot said:
Hi,
I am experiencing the same thing with my pixel 3xl. I plugged it in before going to bed and in the morning it was unresponsive and black screen. I tried changing chargers and plug but nothing changed. When i plug it in a PC it shows QUSB_BULK_CID and then the serial number but nothing else. I have found many people in the google support forums that have the same issue (https://support.google.com/pixelpho...-pixel-3xl-black-screen?hl=en&msgid=121361292) but no one has replied with a fix or even an update.
Have you resolved your issue?
Click to expand...
Click to collapse
Hi!
It turned out that there was an issue with the screen (I completely don't understand why). I had it replaced and everything is back to normal.
Hope you will have your issue resolved!