Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Cerealbowl218 said:
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Click to expand...
Click to collapse
You won't get the OTA until you pull out of the Android beta program. You can pull out for any of your enrolled devices here:
https://www.google.com/android/beta#devices
Just opt out there and you should receive the OTA to go back to Oreo. You won't get any OTA otherwise
TCUofficial said:
You won't get the OTA until you pull out of the Android beta program. You can pull out for any of your enrolled devices here:
https://www.google.com/android/beta#devices
Just opt out there and you should receive the OTA to go back to Oreo. You won't get any OTA otherwise
Click to expand...
Click to collapse
Did that yesterday afternoon, still waiting on the OTA to come through. Ironically the reboots has lessoned considerably, only twice today so far. I've used it minimally though and 1 time was due to trying to open the camera.
Cerealbowl218 said:
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Click to expand...
Click to collapse
You really should post this in the XL forum. There seems to be a much larger userbase, and you'll get more device-specific information and help there.:good:
Related
The weirdest damn thing happened to me...I received a system update available notification (i.e. ICS) as I was going to bed. I thought I'd just do it in the morning. When I woke up, the notification was gone, and if i try to go to manually do a system update, it says device is up to date.
anyone experience such an issue, and how can I resolve this?
thanks
Same thing happened to me. I was on 3G and decided when I get home I'd use wifi to download and update. Now it says up to date.
so weird!! all other updates previously would remain for days... anyone find a solution to this yet?
Same happened to me to this morning, it disappeared
alizawi said:
The weirdest damn thing happened to me...I received a system update available notification (i.e. ICS) as I was going to bed. I thought I'd just do it in the morning. When I woke up, the notification was gone, and if i try to go to manually do a system update, it says device is up to date.
anyone experience such an issue, and how can I resolve this?
thanks
Click to expand...
Click to collapse
wait or
you can update ics by making manual promotion
I prefer to avoid manual for two reasons:
1- I still believe the actual OTA version varies slightly than what is claimed to be the official OTA release in zip format. Little touches are always done before pushing an OTA update.
2- I have a broken power button, so can't do much in bootloader, or even get into it.
Perhaps google took it back to do some more bug fixing. But I'd like to hear an official statement if that's the case
szk5230 said:
wait or
you can update ics by making manual promotion
Click to expand...
Click to collapse
Please explain. I've tried:
Checkin
System Updates
Resetting phone.
Seems like the update was pulled. No matter what I do it says the phone is up to date. With all these stories of people bricking their phones I want to stay relatively legit.
alizawi said:
The weirdest damn thing happened to me...I received a system update available notification (i.e. ICS) as I was going to bed. I thought I'd just do it in the morning. When I woke up, the notification was gone, and if i try to go to manually do a system update, it says device is up to date.
anyone experience such an issue, and how can I resolve this?
thanks
Click to expand...
Click to collapse
Same thing. When I heard google started pushing ICS, I flashed back my nandroid backup of my stock 2.3.4 to get the OTA update, Immediately I got 2.3.6 update and installed it, and few hours later when I wasn't home I got the 4.0.3 update, and I thought I'll do it when I get home, but then it disappeared and doesn't comes back no matter what I do.
I did backup to the corrent stock (2.3.6) and tried to flash back to 2.3.4, thought maybe it will push me again, but now it doesn't push me 2.3.6 either.
Are OTA updates one-time only ? or it supposed push me 2.3.6 again ?
anyways I restored 2.3.6 and I wait hopefully to 4.0.3 again.
Please update here if you know any solution. I know I can install it manually, but I prefer clean OTA version.
after I update to ICS manually, the VPN doesnot work, so I flashed back to 2.3.6 and want to update by OTA.
but till then, the 2.3.6 system says it's up to date...
looks like it's pulled by google...hopefully for some enhancements... still waiting for something official
we had it in our hands and we lost it
Same story.
Last night I saw the system update notification and after 30' (charging the battery) I lost it.
I suppose it's due to issues with ICS 4.0.3. For example I can't make outgoing calls (SMS, incomming calls and data - works fine). Had to revert back to 2.3.6. Now everything works. So for two days i saw update notification and today it dissapeared. So I hope they found a problem and will fix it soon.
yeah, I guess I'm glad I didn't install it then. I'm sure it was pulled for a valid reason, so it's best to wait...fingers crossed that it won't be too long of a wait.
In the mean time I think I need to get my power button fixed, or hope the widgetlocker works on ICS so I can use my volume locker to wake the screen!!
yeah, I guess I'm glad I didn't install it then. I'm sure it was pulled for a valid reason, so it's best to wait...fingers crossed that it won't be too long of a wait.
In the mean time I think I need to get my power button fixed, or hope the widgetlocker works on ICS so I can use my volume locker to wake the screen!!
Not an official story by any means but it looks like there is definitely something going on.
http://mobilesyrup.com/2011/12/20/g...te-for-nexus-s-over-purported-battery-issues/
EDIT: I just noticed one of his sources links back here.
I had to reset my surface rt and now it is on 8.1 update 1. When I try to check for updates it constantly checks but never finds anything so I can get the 8.1 update 3 fix. Are there any recovery images specifically with update 3 already installed?
I have exactly the same problem! Used the current recovery image via USB to get my RT back running. Then some of the Updates installed, but now it is always searching for new updates but never find new ones. I also want Update 3 but this one never shows up! Has anyone an idea how to get to Update 3?
Im having the exact same issue. had to reset last night and now when i download updates, it downloads a few and then it hangs at "checking for updates" screen but can never find update 3. Bump for some info on this. if someone has a direct download for kb3033055 thatd be awesome too.
numus said:
I had to reset my surface rt and now it is on 8.1 update 1. When I try to check for updates it constantly checks but never finds anything so I can get the 8.1 update 3 fix. Are there any recovery images specifically with update 3 already installed?
Click to expand...
Click to collapse
Had the same thing with my wife's RT. A sudden glitch stopped her touch keyboard from working (except for the number keys??????????????). The virtual keyboard still worked though. I downloaded a recovery image
https://www.microsoft.com/surface/e...ervice-and-recovery/downloadablerecoveryimage
and installed, bringing RT back to Win 8.1 factory setting. Like you the update seemed stuck on checking for updates, but I've seen on a lot of forums that it's a time thing - at least an hour - time thing. So I left it checking - plugged in, power setting to 'never' shut down, for 2-3 hrs. Shut the RT down & rebooted. Was greeted with 'updates available' and there were 176 listed when I looked. Clicked on download and left the RT to get on with it. All done now and RT is updating regularly as it should. Hope this helps.
Clwyd said:
Had the same thing with my wife's RT. A sudden glitch stopped her touch keyboard from working (except for the number keys??????????????). The virtual keyboard still worked though. I downloaded a recovery image
https://www.microsoft.com/surface/e...ervice-and-recovery/downloadablerecoveryimage
and installed, bringing RT back to Win 8.1 factory setting. Like you the update seemed stuck on checking for updates, but I've seen on a lot of forums that it's a time thing - at least an hour - time thing. So I left it checking - plugged in, power setting to 'never' shut down, for 2-3 hrs. Shut the RT down & rebooted. Was greeted with 'updates available' and there were 176 listed when I looked. Clicked on download and left the RT to get on with it. All done now and RT is updating regularly as it should. Hope this helps.
Click to expand...
Click to collapse
Is it on update 3? (do you have the start menu back?) I have had it update from the recovery image but it hangs before either update 2 or update 3 and then started cycling the same update (it was a small 23 kb update but it will install and then if you checked for updates it would show the same exact update again. Reboot and it still shows the same update needs to be installed).
I have the same problem. After the update 1 my surface get stucked in "checking for updates", I've let it checking for more than 24 hours, nothing popped out, always "checking for updates". It started after the KB2029xxx (which is the Update 1).
I've opened a thread about it:
https://forum.xda-developers.com/windows-8-rt/rt-general/surface-rt-windows-rt-8-1-windows-t3517074
Did someone find a fix?
See this photo:
https://goo.gl/photos/Ns9nKJotNX7mZnhz6
It seems that the digit in the top right corner of notification stops updating, and always showing the old time.
It will only update if i try to switch the time format to 24h and switch back, and it stays there since then.
A reboot will fix it but the bug may appear randomly. So I may get the wrong time and be late...
Pixel XL using totally stock rom without root or unlock, build number NDE63X(manually updated through google's full ota link, i didn't recieve any ota update since bought with NDE63N)
Anyone has the same issue?
Same issue here this morning with my Pixel.
After an hour the time was up to date again.
Build number NDE63V
Haven't had this problem on the pixel yet, but used to get it once and a while on my Samsung phones. I always thought it had to do with the network feeding the phone the wrong information. After a while it would update and be back to normal
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.
Hi,
Hope you are well.
I had bought my Google Pixel about 2 months ago. It was completely new and working fine. I then upgraded it to Android P beta which ofcourse is buggy. After some time, I had random crashes and freezes on my phone so citing that I decided to move back to the stable update. Once I did that, the phone started behaving abnormally. I was unable to use it completely without anything installed or with the usual softwares. It would work fine in Safe Mode. It used to restart and then get stuck at Google Icon with a bar showing at the bottom of it. I then went back to beta where I had the exact issue but it then started working fine. However, yesterday on the beta version as well its speaker did not work. I restarted it and every app got stuck then it restarted on its own and got stuck like the stable version. But I rebooted forcefully and it worked fine. As I have it in warranty from a local vendor (now google in Pakistan), so I decided to reinstall the stable version as we now had June patch. As soon I installed the stable version, without anything installed the phone started restarting just like it used to. It gets stuck on google icon with a progress at the bottom and doesn't work until I use the power button to forcefully shut it down.
I want to unlock the bootloader and flash a previous build but I don't know whether I should do that or just send it back as I am not able to judge up until now whether that's the hardware or the software.
I will really appreciate some help as I have got multiple responses on google searches but these explain motherboard as culprit. :crying:
Update: The phone again is working absolutely fine in safe mode. I just tried that. However, I am unable to even touch it in the normal mode on stable version. I have already tried the rescue OTA.