Everyone, I have a locked Verizon P2XL running Android P DP3. I've been on the DP train since it went live after I/O and I've had so few problems it's actually surprised me. But that all changed on Wednesday. I have been using Google Pay with no problems up until Wednesday night when I took my wife to Starbucks for a coffee and a chat. I was unable to pay for our products using Google Pay. Weird but okay, I just used my debit card and moved along. When I got home I checked into it. I saw that my device is listed as uncertified in Google Play Store app settings. This was not the case previously. I rebooted into the bootloader and my device states that it is indeed locked. I've already done 2 factory resets, this didn't fix or change anything except that now I have had to sideload Netflix as it won't install from the Play Store on an uncertified device. So that is problem #1, what could have caused this? Will it be fixed (best guesses please) when the DP4 OTA hits my phone? If not will the official release ROM for Android P correct this?
Problem #2 is that I can't get back to stock Android Oreo. I've tried doing it the official way by Opting Out on the DP webpage and taking the OTA. Installation fails with no indication as to why. I've also downloaded the latest official Oreo OTA and used adb sideload to install it. It also fails but using this method I actually get an error message stating that the OTA is older than the currently installed ROM so installation was aborted. I called Google about this, no help. But the support rep agreed with my current idea to try to rollback to Oreo when July's OTA is released as the timestamp will be newer than DP3 so Pixel downgrade protection will be circumvented. Or should be. Back to problem #1, will flashing the July Oreo OTA fix my device uncertified problem? I haven't had this phone very long so I'm disappointed with myself for effing around with the beta program before I really had a chance to use it (got the device in late April).
Thanks for any help.
Problem #1 has been fixed by following the advice of @Phazonclash here: https://forum.xda-developers.com/pixel-2-xl/help/google-pay-issue-t3810129
Problem #2 remains but I'm less eager to revert to Oreo now that the first problem is fixed.
Glad you got it sorted! Anyway, dp4 will be here soon....
Same thing happened to me. DP 3 was running great then out of nowhere the Android Pay was disabled.
I used the ADB commands and reflashed the Oreo Image. Now everything is back to normal. I have read on several forums the same problem.
Looked like some sort of timing issues that inactivates the Android pay after a certain date anticipitating a new build?
Cc
cc999 said:
Same thing happened to me. DP 3 was running great then out of nowhere the Android Pay was disabled.
I used the ADB commands and reflashed the Oreo Image. Now everything is back to normal. I have read on several forums the same problem.
Looked like some sort of timing issues that inactivates the Android pay after a certain date anticipitating a new build?
Cc
Click to expand...
Click to collapse
Which model phone do you have specifically and which Oreo image did you use? As I said I have a Vzw P2XL and I tried to flash the June OTA for the P2XL and it was a no go. I'd love to hear how you managed to do what I failed so miserably at.
Image
I have an unlocked Google version of the Pixel 2 XL. Download the image from the Google site. You can also download the Verizon version.
Cc
Related
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Capture the URL for it ?
Here is the link: https://ota.googlezip.net/packages/ota-api/google_marlin_marlin/d872269d3aff80d3b7f81d28c972d1d59f36f8f6.zip
(I'm not allowed to link to it directly due to my account age - sorry!)
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
This happened to me. I have a Verizon version dePixel8 and sideloaded E build a few days ago. Today I got the update message and it upgraded to K in about 2 minutes.
Gather this is for the Verizon models?
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
It's an update specifically for the Verizon Pixels. It contains a number of bug fixes and improvements according to the release info. A simple Google search will locate more info including the specifics of the bug fixes and improvements.
So this OTA will update my Google store device to the Verizon build? Weird. I'll just flash the whole build later.
So, after applying this update - what build does it show?
Just flashed the OTA. It does indeed update Google Store devices to the Verizon build of 7.1.2, NHG47K. Looking in the OTA zip, the update may only affect the system and vendor partitions.
I had this happen after I flashed the January build I think it was. I have a play store pixel on vzw and it was trying to update my regular stock rom the vzw-specific version. It sounds like if you're on vzw service then you'd benefit from their improvements. I'm waiting for beans to update his rom before I update from 7.1.1. I just hope it includes these vzw changes.
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
alsip1023 said:
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
Click to expand...
Click to collapse
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
hub1 said:
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
Click to expand...
Click to collapse
I was referring to the difference between the 7.1.2 builds, not the phones.
alsip1023 said:
I was referring to the difference between the 7.1.2 builds, not the phones.
Click to expand...
Click to collapse
So was I.
TonikJDK said:
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
Click to expand...
Click to collapse
Thanks for playing the guinea pig. Good to know nothing obvious was added in terms of bloat.
With that being said, that Pixel update is handed to Verizon to "test and certify". Then it is sent to the Pixels. Verizon only promised to not delay updates. They may still add apps, bloat, etc... Should they so choose.
Added information:
Google Store Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the right (as in enabled) but is overall greyed out after "K" update.
Verizon Purchased Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the left (as in disabled) but is overall greyed out after "K" update.
Not sure what this means. If anything, I found it interesting. Once it's unlocked, unless I submit a relock, it can't be relocked by OTA right?
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
gordonlw said:
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
Click to expand...
Click to collapse
Hello,
You bought a Google version, you are fine. You can sideload Verizon's OTA if you are on Verizon's network. Otherwise, no benefits...
Even true Verizon's unlocked Pixel owners, as long as they don't lock bootloader, it will stay unlocked, no matter what they flash FYI.
You can install SU with fastboot boot twrp as well.
Cheers...
Worked great thanks!
I have several Moto Z Plays here; two are retus and one is reteu. The reteu one is running 7.1.1 (official version, not a soak test, NPN26.118-22) because I downloaded the official update and sideloaded it yesterday. It has the July security patch. I was never a soak tester, either. The retuses are still on 7.0, May security patch (NPN25.137-24.4).
Here's the issue. When I sideload NPN26.118-22 (7.1.1. official) on a retus, I get an error saying "E3002: Package expects build thumbprint of 7.1.1/NPN26.118-22/21:user/release-keys or 7.0/NPN25.137-24.3/4:user/release-keys; this device has 7.0/NPN25137-24.4/5:user/release-keys," and it fails. (This also happened on reteu, but I happened to have the package it wanted to see, so I installed it first. See below.)
So, my next move is to replicate what worked on reteu, which was to flash the other package I have first, but I get another error saying "E3002: Package expects build thumbprint of 7.0/NPN25.137-24.3/4:user/release-keys or 7.0/NPNS25.137-24-1-9/10:user/release-keys; this device has 7.0/NPN25.137-24.4/5:user/release-keys."
I'm sort of at a loss from here of what to do, since the May security update for retus does seem to prevent compatibility with flashing any new package. The reason this wasn't an issue on the reteu one was, I'm assuming, because it was on the April security update, and I was able to install the second package, and then finally official 7.1.1 to get it current.
Anyone have any ideas? I can't be the only one running this freaking NPN25.137-24.4 (May) update on the retus Z Play that is preventing me from sideloading official 7.1.1. Thanks in advance!
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Zeljko1234 said:
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Click to expand...
Click to collapse
I appreciate your reply, but this isn't really relevant to my question at all. I acknowledge there are risks with flashing, but I did it successfully on one of my devices and it's really not the scariest thing I've ever done on ADB.
If you're content to wait, that's fine; what I want to know is the reason why I can't seem to do it on 2/3 of my devices. I'd appreciate responses that are relevant to my question.
I replied to your post on reddit, but I'll share it here too. Someone may even correct me here on XDA if I've got any info wrong.
The 7.1.1 that was released to most of us (retbr, retca, etc) require the build number NPN25.137-24.3 (May 2017 security patch) to be installed.
The May security patch on retus has the build number of NPN25.137-24.4 (I guess there was a change that warranted the .4 over .3). All retus phones will have this build number if they've installed the May patch.
This is why you were getting errors when trying to sideload 7.1.1 onto the retus phones (trying to install an update not meant for the device). retus will likely get a different install package for Android 7.1.1
How do you sideload using stock recovery? I tried adb devices and my device is not listed. I want to sideload Google stuff to stock ROM, any idea how to do that? Tried to install the APK files manually but I got force closed after that. Thank you.
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
I updated my Google Edition Pixel 3XL to 10 two nights ago. Now today, I received a notification that an update failed to install.
I am thrown off because I turned off updates, but regardless of that, if I just updated to 10 two nights ago, what is with this update wanting to install in my device?
I am on vzw OG unlimited data plan, the build # of my currently installed Android version 10 is: QP1A.190711.020.C3. Anyone can enlighten me on this?
Thanks in advance
You're on andriod 10. But you're on the sept, 2019 update. So your phone is probably trying to update to a more current version.
statustray said:
I updated my Google Edition Pixel 3XL to 10 two nights ago. Now today, I received a notification that an update failed to install.
I am thrown off because I turned off updates, but regardless of that, if I just updated to 10 two nights ago, what is with this update wanting to install in my device?
I am on vzw OG unlimited data plan, the build # of my currently installed Android version 10 is: QP1A.190711.020.C3. Anyone can enlighten me on this?
Thanks in advance
Click to expand...
Click to collapse
If your bootloader is unlockable, look at this Guide:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Prerequisites: Factory Images
Then do #4 'keep data' to install the latest Factory image. Do #9 to root.
Thanks for the replies. I appreciate it
I have since updated my device again. I used the "OTA" method to do the update. All-in-all it took about 15 minutes or so. Now the security patch level is: October 5, 2019. I suspect that it will tell me sooner or later that there is an even newer update. Hmmm...
I'm still waiting in the even newer updates to come down to my device. I do like the fact though that I can install an ota with magisk and don't have to connect to a computer.
I just wish I could speed up the updates using that method too. I was thinking that it would install the latest/greatest the first time out of the gate. Lol
I'm still waiting in the even newer updates to come down to my device. I do like the fact though that I can install an ota with magisk and don't have to connect to a computer.
I just wish I could speed up the updates using that method too. I was thinking that it would install the latest/greatest the first time out of the gate. Lol
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
ptmuldoon said:
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
Click to expand...
Click to collapse
I also haven't received on the same device and version. So, it's seems like a slow rollout
If you manually check for updates in settings does it tell you you're up to date? If so, I'd just get the update from Oxygen Updater and do a local install. Some people did have issues with the first release of OOS12 (C36) but those should have all been resolved in the next one (C39). I never had any issues with the update personally.
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
ptmuldoon said:
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
Click to expand...
Click to collapse
Probably because C36 is the full update. If it won't let you download both C36 and C40 at the same time (before updating), I'd make sure you have access to wifi in case you're one of the lucky few affected by the mobile network issue in C36. But most likely you'll be fine, the other issues were very minor and you wouldn't even notice if you just install the second update right away.
Does Chrome auto fill work for you on 12? I heard that it was broken, but don't know whether it's been fixed with C40? Holding off on updating until someone can confirm. Thx
EDIT: Decided to bite the bullet and upgraded to C40 on my L2125. I actually like it quite a bit, but can confirm that for me, at least, Chrome auto-fill doesn't work. Other nit is you cannot put the battery percentage in the status bar AND remove the icon; either you have both, none, or just the icon. Also, Netflix is pre-loaded, but won't open or uninstall and update and when I go to the Play Store it shows as incompatible with my device?? (bootloader unlocked, but not re-rerooted yet). Also the power menu no longer gives you a recovery or bootloader option in rebooting. Good things include having more gestures (raise phone to answer) and a panel to control apps that auto-start or not. Also, somehow m yreboot sequence no longer includes the danger, your bootloader has been unlocked, screen (which I didn't think was possible to get rid of).
Rolling back to Android 11 for now. Also, many more root options still available there (like Gravity Box and JamesDSP)