I am using a Verizon pixel 2 xl. Decided to get in to the beta program. Too many of the apps I use on a daily basis crash .After 2 hours I unenrolled on the beta program website. Still have not got the un update yet. Can flash the factory image from https://developers.google.com/android/images or should I just wait longer?
ckilps said:
I am using a Verizon pixel 2 xl. Decided to get in to the beta program. Too many of the apps I use on a daily basis crash .After 2 hours I unenrolled on the beta program website. Still have not got the un update yet. Can flash the factory image from https://developers.google.com/android/images or should I just wait longer?
Click to expand...
Click to collapse
Did you try and check for update? I was enrolled for a few hours and it didn't update until I checked
I am already on P. I want to go back to oreo
ckilps said:
I am already on P. I want to go back to oreo
Click to expand...
Click to collapse
If stock, bootloader locked, unenroll from the beta, you'll get an OTA to downgrade you.
If rooted, then just clean fastboot the latest factory image.
Ok thanks I wait until I get the downgrade then
ckilps said:
Ok thanks I wait until I get the downgrade then
Click to expand...
Click to collapse
I don't think you will get an update back to 8.1 until nexts months security patch.
ckilps said:
I am using a Verizon pixel 2 xl. Decided to get in to the beta program. Too many of the apps I use on a daily basis crash .After 2 hours I unenrolled on the beta program website. Still have not got the un update yet. Can flash the factory image from https://developers.google.com/android/images or should I just wait longer?
Click to expand...
Click to collapse
According to the FAQ it can take up to 24 hours to either get the beta ota or the opt out ota that wipes your phone
Yes, finally got the downgrade at 9 o'clock last night. Was up all night setting it back up. Sorry, I will be waiting until P is offical. Do not run on your main device.
ckilps said:
Yes, finally got the downgrade at 9 o'clock last night. Was up all night setting it back up. Sorry, I will be waiting until P is offical. Do not run on your main device.
Click to expand...
Click to collapse
Most Apps seem to work, some need to be reinstalled to fix the crashing, haven't had any other problems other than my fingerprint sensor, but I'll get that fixed as well.
ckilps said:
Yes, finally got the downgrade at 9 o'clock last night. Was up all night setting it back up. Sorry, I will be waiting until P is offical. Do not run on your main device.
Click to expand...
Click to collapse
They must have fixed the lag of the downgrade, i opted out, checked for an update immediately and the downgrade ota downloaded instantly.
It doesn't appear that even if your in the beta program that you can unlock the boot loader on a Verizon Pixel 2 xl, is that the case for everyone else? I still have the OEM Unlocking toggle grayed out even though I've to P installed via the OTA
thetriplejranch said:
It doesn't appear that even if your in the beta program that you can unlock the boot loader on a Verizon Pixel 2 xl, is that the case for everyone else? I still have the OEM Unlocking toggle grayed out even though I've to P installed via the OTA
Click to expand...
Click to collapse
Why would it change? It isn't a firmware based lock. If you were locked before, you'd be locked on p as well, just like I am on my Verizon pixel 2 xl
Related
With pixel xl bought say pixel store, when does ota usually Côme for 7.1.1?
GCbard said:
With pixel xl bought say pixel store, when does ota usually Côme for 7.1.1?
Click to expand...
Click to collapse
OTA updates roll out in phases. Can be as little as a couple of hours after release, or as much as 10 days to 2 weeks.
You can speed up the process by just sideloading the ota. I gave up on it coming automatically (I'm impatient) and went ahead and installed manually and running great.
xxfwmxx said:
You can speed up the process by just sideloading the ota. I gave up on it coming automatically (I'm impatient) and went ahead and installed manually and running great.
Click to expand...
Click to collapse
Need an unlocked bootloader for that?
GCbard said:
Need an unlocked bootloader for that?
Click to expand...
Click to collapse
Nope not at all I am completely stock and locked. I used the skipsoft Unified Android toolkit and was very easy to do.
GCbard said:
With pixel xl bought say pixel store, when does ota usually Côme for 7.1.1?
Click to expand...
Click to collapse
The first week of each month is when security updates are usually released.
That doesn't mean you'll get it the first week (unless you manually sideload the update).
But that's when updates are released.
Kind of like Microsoft releasing updates every second Tuesday of each month.
Except those get applied a lot faster, to more devices at a single time.
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
aaronpw0621 said:
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
Click to expand...
Click to collapse
I got the same problem as well. I'm on Verizon and haven't found a fix.
I've got a Google Play Pixel XL on Verizon, no problem with update. Full stock locked bootloader.
Sent from my BTV-W09 using Tapatalk
I don't understand how you got the OTA so quick. Even with Google saying last month that doing a check for update manually should now get you OTAs instantly, it's not working on my stock bootloader unlocked XL.
Same here.. got the OTA October Android 8.0 Oreo Security Patch without a hiccup... I also have a locked bootloader as well on Verizon Pixel XL version. Really wish these bootloaders could be unlocked but that's another topic that has been saturated to death... lol.
Damn that sucks for you guys that aren't getting it instantly. Checking for update seems to work for me. But try clearing your Google play services app and then see if it will let you download the update you guys.
alobear said:
Damn that sucks for you guys that aren't getting it instantly. Checking for update seems to work for me. But try clearing your Google play services app and then see if it will let you download the update you guys.
Click to expand...
Click to collapse
No need, hes going to brake GPServices and get bunch of force closes.
The check for updates now works on demand when you press it. This has already been confirmed by bunch of folks, and even myself when i did on my wife's phone.
aaronpw0621 said:
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
Click to expand...
Click to collapse
I just did the manual way of flashing the ota. All good now.
lucky_strike33 said:
I just did the manual way of flashing the ota. All good now.
Click to expand...
Click to collapse
Wish I could. I am out of town working till the weekend.
Google Pixel XL unlocked bootloader and update failing to install. Showing me update size of 50.6 MB.
Will try and patch manually.
I have a Verizon Pixel XL on T-Mobile and i got the October 5th patch yesterday without issue. It took a while for only 64.5mb, but it took it. I did have 1 random reboot this morning though.... BTW, like i said, i took the update with a TMO SIM and still have gray OEM Unlocking
I had the same error. I disabled Block This! and it installed without problems.
Sent from my Pixel XL using Tapatalk
Still waiting for my OTA Oct 5 update. I am complete stock, locked bootloader (never unlocked or rooted). Damn Check for update button not working for me.
So I tried flashing the September patch to both slots manually and taking the OTA but it failed still. So I went ahead and manually flashed the October patch.
I am wondering if it has to do with me upping to Unlimited Data plan on Verizon.
I just checked for an OTA update manually and nothing showed up. I'm still on September patch. Google edition, locked bootloader and not rooted.
westside80 said:
I just checked for an OTA update manually and nothing showed up. I'm still on September patch. Google edition, locked bootloader and not rooted.
Click to expand...
Click to collapse
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
lucky_strike33 said:
I just did the manual way of flashing the ota. All good now.
Click to expand...
Click to collapse
Hi, can you please share the steps to manual flashing the update i am on stock, rooted SU, september. Thank you.
veskostoev said:
Hi, can you please share the steps to manual flashing the update i am on stock, rooted SU, september. Thank you.
Click to expand...
Click to collapse
Go to Google ota and download October. You can flash the ota through twrp. Flash as you would a rom. That's it.
aaronpw0621 said:
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
Click to expand...
Click to collapse
I bought the phone off eBay so I'm not sure if it was enrolled but I doubt it was. I guess I could check to make sure.
---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------
aaronpw0621 said:
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
Click to expand...
Click to collapse
It was enrolled in the beta program. I just checked. I unenrolled it but since I'm already on the stable build it didn't send me an OTA so I won't have to wipe the phone. I'll go check for an update again and see what happens now that I unenrolled the phone.
westside80 said:
I bought the phone off eBay so I'm not sure if it was enrolled but I doubt it was. I guess I could check to make sure.
---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------
It was enrolled in the beta program. I just checked. I unenrolled it but since I'm already on the stable build it didn't send me an OTA so I won't have to wipe the phone. I'll go check for an update again and see what happens now that I unenrolled the phone.
Click to expand...
Click to collapse
I didn't think about the beta program - that would sort of make since as to the cause of not getting latest October OTA. Please let us know if you get it now when you do a manual check for update.
I have a quick question for those that are a lot smarter than I.
Still nothing for me on the 8.1.0 OTA December update. I have an unlocked Pixel 2 XL and an unlocked OG Pixel XL. I was running the Beta on my OG Pixel and I unenrolled from the Beta and factory reset. Waited 24 hours for a stable version of Android Oreo.... still nothing and it is still showing that I'm on 8.1.0 with the November security patch. Also, when I reset my phone or power back on it's still showing that my phone is on the Beta. I have no idea what's going on with it.
Would any of you guys/gals have any other suggestions? I'm not comfortable with flashing or anything like that since I've never done it before. Should I just wait patiently because it will come eventually?
Thanks.
Shrews824 said:
I have a quick question for those that are a lot smarter than I.
Still nothing for me on the 8.1.0 OTA December update. I have an unlocked Pixel 2 XL and an unlocked OG Pixel XL. I was running the Beta on my OG Pixel and I unenrolled from the Beta and factory reset. Waited 24 hours for a stable version of Android Oreo.... still nothing and it is still showing that I'm on 8.1.0 with the November security patch. Also, when I reset my phone or power back on it's still showing that my phone is on the Beta. I have no idea what's going on with it.
Would any of you guys/gals have any other suggestions? I'm not comfortable with flashing or anything like that since I've never done it before. Should I just wait patiently because it will come eventually?
Thanks.
Click to expand...
Click to collapse
I got my Dec 5th patch update last night, so I'm sure it's only a matter of time for you.. If you're not comfortable flashing, than I would say just wait it out. It shouldn't be long.
What the poster above me said, just wait you will eventually get it. They roll it out in stages so they don't overload the servers. We all like instant gratification, which is why a lot of people flash it when it is released, but you will get it.
COMTB said:
What the poster above me said, just wait you will eventually get it. They roll it out in stages so they don't overload the servers. We all like instant gratification, which is why a lot of people flash it when it is released, but you will get it.
Click to expand...
Click to collapse
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Shrews824 said:
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Click to expand...
Click to collapse
When you unenroll, it will send you an OTA. Did you get that OTA? You mentioned you factory reset, but that's not what actually takes you off of the beta.
thacounty said:
When you unenroll, it will send you an OTA. Did you get that OTA? You mentioned you factory reset, but that's not what actually takes you off of the beta.
Click to expand...
Click to collapse
No, I did not get an OTA. I've checked on the site and it says that my device is no longer enrolled, however when I restart my phone (from a powered off standpoint) it still says I'm enrolled in the Beta. I check for an update and it says I'm up to date, yet it's running 8.1.0 with the November 5th security patch.
Sorry for so many questions, but I just thought I might be missing something. It's really not that big a deal to me because I know it will come eventually, but I just wondered why it was doing that. I reached out to Google via the chat and they said wait 24 hours for a stable version however it's been well over 24 hours and still nothing. I've unenrolled the device from previous beta's and have never had to wait. The OTA would immediately show up and I was good to go.
Is it safe to take the actual ota while rooted/TWRP/custom kernel? Will it just replace the boot partition or will it fail? I'm thinking I should do a flash all with the -w removed of the 8.1 instead of letting it go the ota. I just got the notification for it.
Shrews824 said:
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Click to expand...
Click to collapse
DId your OG Pixel XL get the officialy release?
COMTB said:
DId your OG Pixel XL get the officialy release?
Click to expand...
Click to collapse
No, it hasn't received the latest 8.1.0.
Shrews824 said:
No, I did not get an OTA. I've checked on the site and it says that my device is no longer enrolled, however when I restart my phone (from a powered off standpoint) it still says I'm enrolled in the Beta. I check for an update and it says I'm up to date, yet it's running 8.1.0 with the November 5th security patch.
Sorry for so many questions, but I just thought I might be missing something. It's really not that big a deal to me because I know it will come eventually, but I just wondered why it was doing that. I reached out to Google via the chat and they said wait 24 hours for a stable version however it's been well over 24 hours and still nothing. I've unenrolled the device from previous beta's and have never had to wait. The OTA would immediately show up and I was good to go.
Click to expand...
Click to collapse
At this point I would sideload and hope the Check for Update is fixed in January as expected.
thacounty said:
At this point I would sideload and hope the Check for Update is fixed in January as expected.
Click to expand...
Click to collapse
Well, I had mentioned in the original post that I'm not extremely comfortable doing that so I may just wait it out.
I have a question in regards to getting the OTA updates.
I'm in Australia and got my pixel 2 xl on a plan with Telstra as they are the exclusive carrier here. But I use a Vodafone sim in the phone.
Will this cause me to not get the OTA updates?
Hi, I have pixel xl on tmo and I'm still on August security patch.
For some reason my phone isn't getting the update..
Anyone else is having the same issue?
levyitay said:
Hi, I have pixel xl on tmo and I'm still on August security patch.
For some reason my phone isn't getting the update..
Anyone else is having the same issue?
Click to expand...
Click to collapse
Are you rooted?
Phalanx7621 said:
Are you rooted?
Click to expand...
Click to collapse
nope
Were you in the beta program? Try opting out. Ironically, I had to opt out and back in to get my update. I'm on Fi though...
Of course there's the easy way too, just unlock the bootloader and flash with fastboot. You can also, if you don't want to unlock the bootloader, side load the OTA via stock recovery.
Same issue here. I'm dead stock and opted out of the Beta program and can't pull down the September OTA. I guess I'll have to sideload it :/
No Update yet..
I also have got the same issue. On Stock ROM with no Root privileges, No OTA update yet..
levyitay said:
Hi, I have pixel xl on tmo and I'm still on August security patch.
For some reason my phone isn't getting the update..
Anyone else is having the same issue?
Click to expand...
Click to collapse
I am having the same issue. I even did a full reset a few weeks ago. After the P update, I could barely use my phone, it would take forever to get anything to work. Finally sideloaded yesterday with no issues.
Anyone been able to successfully receive an OTA to the beta yet? Enrolled my device last night the moment I got it home and nothing so far.
Disclaimer: I'm using a carrier and bootloader locked T-Mobile version; still hoping I can eventually get TForce to carrier unlock this for me sooner rather than later otherwise i'll just return it and get one direct from good old El Goog.
Did they get magisk for the 3XL yet; last I read over there they didn't have it for Q on the XL.
This true. I spent a couple hours on this last night and it does not work. I went back to pie.
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
That's pretty much what I figured, but wasn't certain. Good to have some feedback from others; sounds like we can pretty much confirm that it isn't being pushed to the 3a devices yet.
I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?
DanRyb said:
I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?
Click to expand...
Click to collapse
Yep. It's possible they are withholding the OTA from carrier devices...
P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.
alphahere said:
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.
Click to expand...
Click to collapse
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.
P$udo said:
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.
Click to expand...
Click to collapse
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Looks like Pixel 3a and 3a XL were removed from eligible devices on the beta sign up page.
I wonder what's up?
if anyone is looking for the download you can find it here
alphahere said:
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Wow. Thanks for that. I thought fastbootd was a mistype when they were compiling. I didn't know that it was a whole other thing. Seems to be more akin to what recovery previously was on some older devices.
I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.
elpindian said:
I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.
Click to expand...
Click to collapse
I did not get the OTA. I downloaded the firmware image and flashed it.
Android q beta isn't ready for the pixel 3a/3a xl until June
An FYI... I just wandered over to Papajohnwu's Twitter and he is saying he'll be ready for Q.That's some good news, hate to be stuck on Pie forever.
If you have a 3a (xl) from a carrier like T-Mobile where to boot loader is locked, if you're able to use adb/fastboot to flash beta 3, you very well may not be able to revert the phone to Pie. I'm stuck as I got mine on the day TMO put them on sale, then opted in to the beta expecting to be able to opt out, well considering they removed that option, I'm now stuck on Q..
Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.
I'm curious how you got it unlocked from T-Mobile. I picked mine up on release day and when I got around to checking, OEM Unlocking was greyed out. Did you do this before installing a SIM?
Thanks!
PhoenixPath said:
Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.
Click to expand...
Click to collapse