I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
See if you still can get your phone into download, fastboot or recovery mode. Here you can see the button combos: https://m.youtube.com/watch?v=YFaq4g-oa2Q
If you can get to recovery mode, click on wipe cache and reboot. If your phone still is stuck afterwards, go to recovery again. There is an option to wipe and reset the phone. Note that your data will be lost!!! Do it at your own risk. But a reset often is the last working choice when your phone behaves strangely.
If you get none of the three mentioned modes to work, I think your Pixel has a hardware fault.
Hope this helps.
check the charging port first....whether it is charging or not......try to connect to PC
i guess the phone is not charging
So the bottom line is this is still somewhat ongoing, though I’ve confirmed the phone is definitely bricked. I brought it into UBreakIFix and after taking it apart (noting that the device seemed physically in great shape) that there wasn’t anything obviously wrong with any of the particular hardware (they mentioned that replacing the motherboard would likely do it, but it would be about as expensive and effective as buying a new phone anyway...).
I ended up writing back to Google and am in back and forth talks with them now. I’m not sure what they can or will do, but my final answer will have to be getting a new phone one way or the other.
Related
So I haven't used my Nexus for somewhere around 2 months since I got a new phone. The Nexus S was working fine prior, I had actually just got it back from Samsung after them fixing an issue related to my top volume button. After, I received it, the phone was in a complete stock condition, like it was just bought from a store (no unlocked bootloader, fastboot, Clockwork, etc.). A bit later, the OTA Jelly Bean update comes in, but I don't use it too much as I just got my new phone.
I left it on and ignored it for the past 2 months. I just assumed the battery would run out, and if I wanted to use it I would just plug it back in and that would work. Now the Nexus S won't show any sign of life. I've tried removing the battery and trying to turn it on while plugged in, when it's plugged in with my battery in, the charging indicator it used to show never shows up. Plugging it into my computer with or without a battery does nothing, it doesn't even show up in my device manager as "Unknown". I've also tried holding VOLUP + PWR for 10 seconds with all these different situations. Nothing. The phone is essentially dead. Any clue why this happened and how I should go about fixing it?
Nevermind. After leaving it plugged in with the battery for ~20 minutes it finally powered on! Hopefully this thread helps out someone in the same situation. It just seems as though it takes a long time to get it to a state in which it'll power on.
Hi,
Guys I am going through some **** right now. Plese read the scenarios below and help me. I got no help at the oneplus forums.
Scenario 1 -
My phone was working fine until last night, I mean this is when I last used it. I switched it off and went off to sleep and in school today when I was trying to power it on the boot logo came and it went and after many tries the cyanogen logo came and it went away there is 80% battery. It doesn't charge also, like the phone recognises the charger but remains at 80% when I go to recovery try wiping cache and data, the phone switches off in few seconds. I can go into fastboot and stay for like 3 seconds then the phone switches off but I can connect it to power and keep it. I am on stock, latest CM12S. The only unusual thing I did yesterday on my phone is that I charged it using a different adapter but same cable. I can't seem to find this issue on google.
Scenario 2 -
Guys,
My phone's really messed up and I am scared to tell my dad cause he warned me before getting it for me. After the OnePlus logo comes, when I press the volume button and hold it, it works and as soon as I leave the volume button, the phone switches off. What is wrong? Do I need to send it back. I got it from Oneplus.cn so I am a bit worried and it's going to be tough to check what's happening.
Scenario 3 -
I removed cm12s and tried to flash oxygenos and I failed so then I installed cm11s and still have the problem, my phone can only boot in safe mode and as soon as I leave the volume button it switches off, same for recovery. Used the onplus toolbox by Inthiaano to install CM11S 44S.
I've had this phone for about 2 months now, and from the beginning, it's had an issue where it would randomly freeze, restart, and get stuck in a boot loop for random amounts of time. Sometimes it would be fine after 2 minutes, sometimes it would need 10. I kept thinking this was a firmware issue - the phone WAS rooted with TWRP installed, but none of my past phones have had this issue and hardly anybody online seems to have had it, either - and just thought that maybe installing a custom ROM would fix it, but never got around to doing so.
3 days ago, my S7 went into a boot loop again, so I just decided to put it down and let it do its thing. After 20 minutes, however, it still wasn't booting, so I booted into TWRP, and cleared the cache and Dalvik cache. Another 20 minutes later, I went into panic mode and started doing Nandroid backups of my stuff. I decided that I had no other choice but to commence with finding a ROM to replace stock. In the meantime, I just plugged it in and let it keep looping, hoping against hope that it would just fix itself like it always did.
About half an hour later, I was ready to install the ROM I'd decided on. I went and picked up my phone, but all that I saw was the screen was black, and the blue notification LED was lit up. I tried holding Vol- + Power to start booting it into TWRP, but nothing happened. The phone didn't vibrate, the screen didn't change, and the LED stayed lit. I tried holding every button combination possible, for even as long as a minute, but the phone refused to respond. I tried plugging it into my computer, but Windows didn't detect anything.
Skip to today, and the phone's battery has long since died(the LED isn't lit up, so I can only assume...), and I just decided to plug the phone in for the hell of it just to see if maybe it would maybe work again. To my astonishment, 2 minutes later, the battery icon came up on the screen, but the charging animation wasn't there. When I held Vol- + Power, the phone actually responded and restarted! Though, it wouldn't boot past the Galaxy S7 splash screen, and when I tried to boot it into TWRP, it went back to being a brick. I let it sit for about 10 minutes, plugged it in, and this time tried to get it into Download Mode, and it worked!
I downloaded the Switzerland version of the G930F firmware, flashed it in Odin, and everything seems to have worked. Odin says it succeeded, but when the phone tried to restart, it got to the splash screen, and after a few minutes, the screen went black again. When I plug it in now, the Galaxy S7 screen will come up, but now I can't seem to get into Download Mode anymore(though, it DOES still seem to respond to me pressing Vol- + Power).
Does anyone have any idea what's going on? I can only seem to find 3 or 4 other threads on various forums about this problem, but none of them have any answers. People just keep saying the usual "Hold Vol- and Power to make the phone restart", but in case I haven't made it clear, THAT ISN'T WORKING.
And before you suggest that I return it to where I bought it for a replacement or refund: I bought this phone on eBay from a seller who said it was in pretty much mint condition. When the phone arrived, there was not a dent or scratch anywhere on the phone, even around the charger port, so I have no reason to believe he was lying. When I asked him about any possible problems with the phone's operational stability the other day, he says he tested it for about 2 weeks, and that he didn't notice anything.
Sounds like a hardware fault, not much else you can do other than flashing stock and factory resetting, which you've done
Considering it had a fault from day 1 it sounds like that fault finally caught up with it
Likely scenario if sent for repair, new motherboard replacement needed
Hi,
Last Thursday night my pixel 2 became unresponsive, I rebooted and it worked again, then it became unresponsive again, I rebooted but to no avail. The phone does have a large chunk of glass missing in the bottom left below the screen (https://drive.google.com/open?id=1NdlE-Xrwa9rPPGpMXT47FHqLWfW0MHd2), this happened due to a drop some time ago. At the time I tried booting into safe mode which didn't help, I also tried to go into recovery mode to factory reset the phone to rule out any software issues, but the phone wouldn't enter recovery mode, it just would go straight to the "google" logo and then would boot loop and sometime it would break the loop and just boot as normal. This unresponsive behaviour has been demonstrated before, but a reboot sufficed.
As the phone appeared to be functioning otherwise, I decided to order a replacement screen (I haven't received it yet), although I do find the ability to not go into recovery mode concerning.
Also, when I say unresponsive I mean just to touch, the fingerprint reader still lets me pull down the notification bar; the phone is not frozen. One final thing and I'm sure if it's related, is that I was getting some crackles and pops when using my headphones with the provided 3.5 to USB C, I assumed it was down to the cable getting damaged, but it might also be to do with phone's damage.
I hadn't touched my phone all weekend, I turned it back on last night so my alarm would go off this morning. It did and I was to my surprise responsive. I left my phone to sit on my desk over the weekend and I believe the battery drained completely and it turned off, I'm not sure if that complete battery drain was the reset it needed or what. It was definitely unresponsive for half a day of me rebooting, but who know how long that would have went on for.
I'm not sure now if I should replace the screen, I think I will just due to the physical damage the phone has, but I would want to return the screen if the phone is on the brink of being unusable regardless of the screen/digitizer hardware. As clearly the hardware does still work.
Any advice/help would be much appreciated
I've had this phone 3 years and it worked well. It's an unlocked ATT phone so no OTA updates other than the standard app updates. It's on Lollipop 5.1. Been working perfectly fine until yesterday, I was watching the CBS app, when the phone rebooted. Now it's stuck on a boot loop and initally went to optimizing apps which it rarely finishes but the times it does, the phone just powers off. It then got into another loop later last night where it'd get to the Kyocera logo then reboot over and over. I let it do that until the battery died 2.5 hours later. Then I kept attempting to boot until the batter was entirely drained to the point it wouldn't attempt to power up any more.(battery is not removable on this model). I've now charged it up, trying to enter recovery mode with power+volume down. That doesn't seem to register. Tried volume up+volume down+power with no effect. Now after charging, it will do the reboot loop mentioned earlier to the Kyocera logo. If I plug it into a charger, it will go to the optimizing apps portion and repeat the above. At the optimizing apps screen, if I unplug the charger, the phone powers off immediately. It appears to be holding a charge according to the charge indicator and the fact that I can try to boot over and over unplugged. Any suggestions? Phone wasn't dropped or damaged in anyway. Very weird what could have happened.
An update: Phone finally got past the "optimizing app" phase last night sitting on the charger. Out of no where the phone booted completely. However, it only works while plugged in. If I remove the charging cord, the phone shuts down after about 2 seconds. Booting without charging cord results in the same boot loop. I've considered the battery has failed however when plugging in the charger, battery shows 100% and it will decrease appropriately over time. I'm thinking there must be a hardware issues at this point. Somewhwere in the charging/power circuit. Any other suggestions?
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
djhurt1 said:
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
Click to expand...
Click to collapse
I have the same exact problem. It started the crazy booting process in my pocket, and I did all the same things you did. Factory reset didn't correct the problem, so I'm think the battery has had a stroke. Sine your problem and my problem are very close to the same time frame, our phones are also probably about the same age, and its a quality control issue. Not bad quality control, just that these batteries were designed to last X number of months or cycles, and probably they died. Too bad, because my E6560 is the very best cell phone I have ever owned. Built like a tank and thank God for that.