I've done some searches here and via Google, can't seem to find any discussion of this issue. Maybe I'm using wrong keywords?
Back story: I've had my 32GB black Pixel since launch. I got my wife a 32GB silver Pixel about 5 weeks ago when her Galaxy S4 died. SO ... theoretically, we have identical phones, right? Bootloaders are locked.
My phone is doing just fine.
My wife's phone has been having problems. I don't know for certain that it's related to the February update, but the timing would suggest they're connected. It started happening late last week, soon after she got NOF26V.
The symptom reported to me is that the phone "can't make or receive calls." Looking it over, I find that the mic, bottom-firing speaker and earpiece speaker don't work. (I meant to check if a wired headset would work, but got sidetracked.) On reboot, the boot animation is very strange. It just sits at the Google logo, never shows the "dancing dots", and then shows the lock screen. Everything works okay except mic and speakers.
I cleared cache, no joy. I did a factory reset, no joy. I'm not sure how, but yesterday we finally got it to reboot "normally" - we saw the dancing dots - and the mic and speakers were working. However, today it's acting up again.
I'm wondering if something went wrong when the February OTA was installed. I'm thinking I should unlock her bootloader and install a clean copy of the February update, then re-lock the bootloader.
Thoughts?
I would unlock and flash the full factory image with the flashall bat file. But it sounds like a hardware failure to me.
This is the exact same as my device. Google advised me to RMA.
Same here on my wife's Pixel after the February update. My Pixel XL is fine. Bootloader was already unlocked (Verizon model). "flash-all.bat" worked like once, but it quickly broke again for good. I even tried the 7.1.2 beta.
Replacement will be delivered tomorrow.
So i bought a brand-new google pixel feom guy on Craigslist and the issue is that sometimes when i receive a call i cant hear the person.and google voice search doesnt work,after i restart everything wprks fine. Think i can warranty from google
UnusualSuspect said:
I've done some searches here and via Google, can't seem to find any discussion of this issue. Maybe I'm using wrong keywords?
Back story: I've had my 32GB black Pixel since launch. I got my wife a 32GB silver Pixel about 5 weeks ago when her Galaxy S4 died. SO ... theoretically, we have identical phones, right? Bootloaders are locked.
My phone is doing just fine.
My wife's phone has been having problems. I don't know for certain that it's related to the February update, but the timing would suggest they're connected. It started happening late last week, soon after she got NOF26V.
The symptom reported to me is that the phone "can't make or receive calls." Looking it over, I find that the mic, bottom-firing speaker and earpiece speaker don't work. (I meant to check if a wired headset would work, but got sidetracked.) On reboot, the boot animation is very strange. It just sits at the Google logo, never shows the "dancing dots", and then shows the lock screen. Everything works okay except mic and speakers.
I cleared cache, no joy. I did a factory reset, no joy. I'm not sure how, but yesterday we finally got it to reboot "normally" - we saw the dancing dots - and the mic and speakers were working. However, today it's acting up again.
I'm wondering if something went wrong when the February OTA was installed. I'm thinking I should unlock her bootloader and install a clean copy of the February update, then re-lock the bootloader.
Thoughts?
Click to expand...
Click to collapse
https://productforums.google.com/forum/m/#!category-topic/phone-by-google/IW_gxTpXX3s
Same thing happened to my VZW Pixel. Got a warranty replacement overnight.
Related
I've been searching the interwebs and XDA for days regarding the random reboots that the Nexus S is cursed with and I was wondering if there are any confirmed solutions? (Phone randomly reboots, and gets stuck at a bootloop with a very dark screen until battery pull).
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
Mine has been doing it at the most random times, which is a major inconvenience for me if I rely on the alarm clock to wake me up in the morning.
I've run factory wiped, flashed stock, Cyanogen, and NSCollab and they all have had the problem. Can anyone provide me with some help?
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.
I just got an AT&T version for my wife during the "free upgrade" promotion. I have not rooted or installed any roms and this phone is having some issues. Reboots at completely random times, goes into boot loops, and even locks on a black screen with the buttons lit. I have been searching for about 2 hours without any real answers. I have been through Aria, Captivate and now NS. Flashing roms and dealing with android quirks is usually not an issue, but I want to retain my ability to return this phone if it is faulty.
What I have tried:
1. Uninstalled questionable user apps
2. Switched SIM cards (used my SIM)
3. Factory Reset
Model: GT-I9020A
Ver: 2.3.4
Base: I9020AUCKE1
Build: GTJ61
Some help/suggestions from some experienced Nexus S owners would be appreciated. Thinking tomorrow will be a return to Best Buy.
andythefan said:
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.
Click to expand...
Click to collapse
I ended up doing an exchange at BB today and the problem is gone. I would definitely attribute your problem to a hardware issue. The new NS that I have is running smoothly and has not had one freeze or reboot yet. Get yours traded in before it is too late.
I would like to add that it seems there is a lot less support/community advice in the NS section than some of the other sections I visit. Strange...
I get the same thing, and frequently woke up (late) to bootlooping...
This is far from a fix or diagnosis.. but this is how I manage:
1. Buy a cheap alarm clock
2. when the phone is bootlooping, I plug in the usb (to computer), open dos prompt and type adb reboot or adb reboot recovery (then fix permissions). If you have the android sdk installed on your computer, of course.
I have a case.. and it's a pita pulling the battery out.
However, before i go to sleep, I've been turning off auto-sync (gmail, contacts, etc, all of them), and it hasn't bootlooped overnight since.
Something to try.. but good luck My signature has my phone version and setup.
Thanks for replying everyone. I went ahead and arranged to have it replaced. In my area only one Best Buy had Nexus S's in stock and they were sold out online. There was an armed robbery in the area near the Best Buy, but I went anyways!
I've got the last Nexus they had and just nandroid restored. Everything seems fine so far!
Not even a week into having a replacement Nexus S the reboots have started happening again. It's happened twice today. This leads me to think, is this a software issue?
Try a different kernel.
Wipe cache & dalvik.
Fix permissions.
After getting a new Oneplus One phone back in July, I have not been using my D800. I have been turning it on every couple of weeks to update the CM11 nightly and the apps. The last update was about a week or so ago. After doing the update I played with the phone for a while then shut it off and stored it.
I got the phone out this morning, turned it on and all of a sudden my screen started going crazy as though it has a mind of its own. My touches almost have no effect. With the screen off sitting on the table it will on its own come on and start tapping at the status bar opening my calendar and quick toggles. It seems that most of the activity is happening at the top of my phone.
I manually entered TWRP recovery and saw that the screen problem is there too. Therefore, it would be dangerous to attempt to make any selections on screen in TWRP because there is a good chance it will select something I do not need selected!
Does this sound like a bad digitizer? My phone has never been dropped. It is in mint condition.
I would like to restore one of my stock rom nandroids but am unsure about how to do that outside of TWRP. Can I do this in download mode and adb? If so, would you mind a few general steps?
I am the second owner of the phone. The original owner purchased it outright from Best Buys about February this year. If I send it in for a warranty repair I would like to have it back as close to stock as possible.
Thanks.
EDIT: Well I managed to restore a stock rom nandroid with twrp. Problem still there. I called LG cust service and the phone is still under warranty until December. Got an RA so I will be shipping to Texas tomorrow.
I was watching a video on my pixel when suddenly the display freezed and turned off. Since then it has been restarting and crashing again and again. I have already done factory reset. I am unable to attach image here which would have given a better idea of the problem ibb. co/ jDdU6b . Remove the spaces in the link to see the photo.
Instead of a factory reset have you tried flashing the factory image via fastboot? I would attempt to backup what is important and run the flash_all.bat with the file unaltered. This will allow the image to be flashed and all user data would be wiped giving a clean install.
Sent from my Pixel using Tapatalk
chaitan123 said:
I was watching a video on my pixel when suddenly the display freezed and turned off. Since then it has been restarting and crashing again and again. I have already done factory reset. I am unable to attach image here which would have given a better idea of the problem ibb. co/ jDdU6b . Remove the spaces in the link to see the photo.
Click to expand...
Click to collapse
Just for humor, it is the same concept!! https://youtu.be/kKAjay0iWwI
Bro, let me know what you find out because this ****ing phone has got me sick and tired of these reboots. It just ****ing reboots at random times and even when it boots up after a reboot it will freeze and reboot again. Honestly, I have never said this to anyone because I am a hardcore nexus user but **** this phone, google really ****ed this one up.
I been having this issue, and preformed a factory reset on Jan 1. I cant say I have seen it re-appear. I am 7.1.2 by the way. If it is across the board with 8 and 7.1.2, then it may be some wonky google app that is common to both. It was not any specific application that it happened on either.
I just did an RMA, my warranty ended in dec 27 and they still sent me a new one. I hope the new one doesn't have problems, it probably is a google app.
Return it before your warranty runs out. This happened to me on december 15th. My warranty expired nov 17th and google refused to do anything and ubreakitifixit cannot fix it. This is a known issue, but google won’t stand behind their product. Eventually your phone will shut down and never turn back on.
carm01 said:
I been having this issue, and preformed a factory reset on Jan 1. I cant say I have seen it re-appear. I am 7.1.2 by the way. If it is across the board with 8 and 7.1.2, then it may be some wonky google app that is common to both. It was not any specific application that it happened on either.
Click to expand...
Click to collapse
I wanted to update this as it is possible I might have stumbled across something.
After wiping it and restoring some apps, I had no issues with it until the week of the 22nd of January. I installed one app and it started to reboot randomly. That app was Android Pay. Once it started to happen I uninstalled it, and have not had any re-boots since again.
Best Regards
This just started happening to my girlfriend's pixel. Bone stock, never rooted. If you even have a HINT that your phone is rebooting for no reason, I suggest you send it in for repair as soon as possible. Her phone now just bootloops, and you can't boot recovery mode either.
Google support said that the warranty expired in October, and so they told me I can go pound sand.
Well I can call UbreakiFix... I got a quote of ~$500 to replace the motherboard + screen, and no one else sells it that I can find.
A flagship phone lasting barely more than a year is not acceptable to me. Google should be offering me a replacement device, and I'm rather pissed that they aren't.
xdraconis said:
This just started happening to my girlfriend's pixel. Bone stock, never rooted. If you even have a HINT that your phone is rebooting for no reason, I suggest you send it in for repair as soon as possible. Her phone now just bootloops, and you can't boot recovery mode either.
Google support said that the warranty expired in October, and so they told me I can go pound sand.
Well I can call UbreakiFix... I got a quote of ~$500 to replace the motherboard + screen, and no one else sells it that I can find.
A flagship phone lasting barely more than a year is not acceptable to me. Google should be offering me a replacement device, and I'm rather pissed that they aren't.
Click to expand...
Click to collapse
Yeah man same thing just happened to me, like wtf
Same here. Just bootlooping... Thanks google
This is what I get for updating my damn phone, Same problem here.
Now happening yet again to my Pixel and this is the 3rd handset I've had in 18 months. Now need to send this back to Google so that'll make 4 Pixels I'll have had before my contract ends and I can escape to a handset that works.
This problem seems to be pretty widespread. Mine Pixel’s been doing this for a while now - sometimes it’ll go days without me at least noticing a reboot, other times it will happen so often as to make the phone useless. I just tried a factory reset - anyone know if there’s a permanent fix to this? It sucks when I’m in the middle of a call and then all of a sudden the phone shuts down and starts rebooting.
When I tap the WiFi toggle option, either from top menu or from the settings, it refuses to turn on. It is the exact problem being shown in the video I've attached at the bottom of this post.
Details:
- The phone is Mate 9 (MHA-AL00).
- I can't claim warranty.
- I've tried wiping the cache in recovery mode.
https://www.youtube.com/watch?v=Q-VfQrMA-4s
This is really strange. Today morning when I tried to turn on the WiFi, it just turned on as if nothing had happened. Really strange.
So weird issue.
Check whether you have some special network management app installed on your device which would block the WLAN feature.
Anyone found a solution here
Hello,
For 2 days now, I have exactly the same issue with wifi and Bluetooth. As soon I switch them on, they get switched off instantly.
I have tried to reboot, safe mode, cache wipe, full factory wipe, but no results. This happened a month ago but came back to normal by itself. But this time it won't.
I contacted Huawei, they told me that my phone comes from China, where they have only one year warrenty, so they cannot it fix it in France even if we have 2 years warrenty here! Super!
Do you have any idea or tutorial on how to purchase and change the wifi/Bluetooth antenna?
Thank you for your help.
Great I'm on a MHA-L29C567 (US) model and as of about a month ago the same thing started happening me. I thought at first it was a radio update and reset the entire device back to stock but now the device is doing the same thing and worse now randomly reboots.
Really frustrating because I really love the phone but for the rear color camera focus sticking and this issue now. Looks like I may need to abandon the phone.
Your motherboard is crapping out, there is no other fix but a board replacement.
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
dutch_in_seattle said:
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
Click to expand...
Click to collapse
No, but I know who can fix it for free, because it's a brand new phone that's still under warranty...
Of course I'll reach out to Google, but I wanted to see if anyone else is seeing this, too.
Will google cover when it is bought at Virgin Megastore?
dutch_in_seattle said:
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
Click to expand...
Click to collapse
Have you backed up to Google one and done by a reset?
A reset might solve your problem?
I've read on GitHub that it's an issue with the 5g hand over to LTE on the T-Mobile network.. I had the same issue until I switch to use LTE and it's not shut off since. Hopefully Google is aware and it gets fixed
GitHub link - https://github.com/GrapheneOS/os-issue-tracker/issues/1809
dutch_in_seattle said:
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
Click to expand...
Click to collapse
This issue exists from October...
After December update more users reportthing this
Pixel 7 pro freezes and reboots - Google Pixel Community
This happened to me this morning. American Verizon service with December update installed.
Happening to me even on custom ROM. I'm really wondering if this is an actual hardware issue rather instead of the OS issue.
lebangood said:
This happened to me this morning. American Verizon service with December update installed.
Click to expand...
Click to collapse
The december beta had this problem so it might apply to the stable one as well, I suggest you update to the stable january build.
ekin_strops said:
Happening to me even on custom ROM. I'm really wondering if this is an actual hardware issue rather instead of the OS issue.
Click to expand...
Click to collapse
If they're based on the december build it might be due to the kernel (the december build had some issues), since I updated to the january build I did not have any other random reboot.
MarcoReckless said:
If they're based on the december build it might be due to the kernel (the december build had some issues), since I updated to the january build I did not have any other random reboot.
Click to expand...
Click to collapse
I tried updating to TQ1A.230105.002 today which I think is the latest stable Jan build..? And just got the random shutdown again.
shinigenEddy said:
I tried updating to TQ1A.230105.002 today which I think is the latest stable Jan build..? And just got the random shutdown again.
Click to expand...
Click to collapse
I'd suggest to do a full factory reset while flashing all partitions, that's what I did and I don't have this issue anymore, otherwise it could very well be a hardware issue, but doing a full wipe is worth a try.
MarcoReckless said:
I'd suggest to do a full factory reset while flashing all partitions, that's what I did and I don't have this issue anymore, otherwise it could very well be a hardware issue, but doing a full wipe is worth a try.
Click to expand...
Click to collapse
I did do a full factory reset before flashing.. I was surprised to still have the shutdown issue as well since it must be a hardware issue then.. but it's so weird that a hardware issue would just randomly surface without dropping the device or anything at all..? Or could it be that the January Stable Build still has the software issue? I'll reach out to Support tomorrow.. for now I'm going to try putting it in my pocket with the screen facing up and not towards my leg and seeing if that makes a difference.
I didn't have this issue, i updated to the January patch and everything was ok, now today my phone started to shutting down tl not sure what is going on
I have the same problem since yesterday. Every time I block the phone and put it in my pocket, the next time I get it it's turned off. I'm sure the pocket isn't pressing any button, but it keeps powering off. I bought it on launch day and I had 0 problems with it until now.
EDIT: Updated applications since yesterday (22 of January): Google, IFTTT and my bank application.
EDIT2: I've just tested to use it on Safe Mode, and I got the same behaviour. I suspect it must be some screen or screen sensor problem... of maybe It has something to do with the fingerprint sensor.
EDIT3: After triple-checking (my phone was in the December update) it finally has updated to the January one. I'll update with more feedback after update.
I changed to only LTE and for some time it was not shutting down. Since pixel pro doesn't have a cache partition like others phones i opened the "files app from Google" and i cleaned the junk files , i rebooted the phone and since then i have no issues at all. Maybe is a coincidence but it's working for some days without shutting down
zenthek said:
I changed to only LTE and for some time it was not shutting down. Since pixel pro doesn't have a cache partition like others phones i opened the "files app from Google" and i cleaned the junk files , i rebooted the phone and since then i have no issues at all. Maybe is a coincidence but it's working for some days without shutting down
Click to expand...
Click to collapse
I had the same issue on the december beta, after wiping the device fully and flashing the january stable this issue disappeared; some users also reported this on GrapheneOS on previous Pixels so I just think it's a bug that went unnoticed.
I started having this issue after the February 5th Update. After reading through this thread it got me into thinking. I couldn't reproduce the issue into safe mode, I uninstalled new 3rd party apps and that didn't fix it. However, disabling the flip to shhh setting did! So disabling the sensor for when your phone is placed upside down to silence the phone seems to have resolved the problem for me. Let me know if this fixes it for others.
So same problem here, random shut downs while in my pocket, long press to power up, temperature check and no over heating. After a couple of chat sessions with FI support which were worthless, finally spoke to Google support and they seemed to be convinced that there is a problem, I think they know. They agreed to a replacement and awaiting a new phone from Google, we shall see.