What is the payment fail? I'd like to know if the 5G with dual sim (dsds) made it into the build.
Pixel 5 OTA monthly update
- Thread starter Ali988
- Start date
If you migrate from an older Pixel via cable (like I did), GPay payments fail with an unknown error. Neither does cleaning the app cache+storage and re-adding the cards fix it, nor does wiping and reinstalling (works only for some while it does not for others). Therefore I hesitate to wipe my device since it may cause a lot of work without fixing the issue.
Further information can be found here: https://support.google.com/pixelphone/thread/77996914?hl=en
Now I remember. Wow I thought that was fixed but I guess not. Why not take the hour and wipe it? I use it all the time so I'd have to but that depends on how much you need it. I think I would remove the cards you currently have first then do the wipe. Damn what a pain.
Not everything is restored after wiping, lots of apps require to be reconfigured. I'd rather avoid this.
I know. It will probably take you about an hour. Some apps will auto fill in credentials. Still a royal pain.
And it is not 100% guaranteed it will work after a wipe. So I'd prefer a fix of the root cause.
I don't believe they are acknowledging it, however. At least not yet. It's been a month since and no reply from Google as far as I can tell. So you think it's software and not hardware? Have you tried the new GP?
Super frustrating moving to a Pixel 5....
What does this mean? I use AT&T as my carrier but I bought my phone fully, globally unlocked from any carrier and the bootloader is also now unlocked after the November update.
Is the 010 image for AT&T-locked bootloaders only?
Is the 011 image inclusive of all unlocked devices, no matter the carrier?
Why is Verizon even noted if their bootloaders are locked?
11.0.0 (RQ1A.201205.010, Dec 2020, AT&T)
11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
What does this mean? I use AT&T as my carrier but I bought my phone fully, globally unlocked from any carrier and the bootloader is also now unlocked after the November update.
Is the 010 image for AT&T-locked bootloaders only?
Is the 011 image inclusive of all unlocked devices, no matter the carrier?
Why is Verizon even noted if their bootloaders are locked?
11.0.0 (RQ1A.201205.010, Dec 2020, AT&T)
11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
@digger16309 Not all users on Verizon have locked bootloaders. You can use any unlocked device on Verizon. I'm on Verizon and can unlock my bl and flash any image I want. It's been a while but I think all full images are for bl unlocked phones and all OTA images are for locked ones.
OK, fair enough on VZ. I should have thought of that. I'm still unclear though as to which image I'm supposed to flash to update my carrier-unlocked, bootloader-unlocked device if AT&T is my carrier (or if that matters).
Locked bootloader doesn't mean you can't sideload ROMs. What it means is that you can't sideload UNSIGNED ROMs, and thats an important distinction. You CAN sideload an official stock image without unlocking the bootloader, and in fact, i actually did after not receiving the December updates for 1.5 days
As for what to flash on it - check if its currently running the previous generic build, and if it is, just flash the generic build.
What is the generic build? I don't see one. I'm on RD1A.200105.003.C1 which is the generic build for the November patch. The only two options for December are:
11.0.0 (RQ1A.201205.010, Dec 2020, AT&T)
11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
So is .011 the generic build?
Yep. The 010 is an AT&T customized one. And there should be one more, Verizon-customized, which isn't there yet. I had the same one on mine before flashing RQ1A.201205.011 as well. So far so good.
I haven't bl unlocked in some time but don't you get an OTA when available even unlocked? If I see a specific build for my carrier I would certainly load that image even if I have to wait the week, which I do now and did last month. The thing about the November build you are on is that there was no ATT specific build like they have in December. Last month was odd because all VZW customers did not get the OTA until a week later and no one knew what was going on. Then it was announced it would be a week late whereas this month they specified every carrier and excepted Verizon.
Really? Wow I've been out of the game for longer than I care to think about. I only thought you could sideload an OTA not a full image with a locked bl.Locked bootloader doesn't mean you can't sideload ROMs. What it means is that you can't sideload UNSIGNED ROMs, and thats an important distinction. You CAN sideload an official stock image without unlocking the bootloader, and in fact, i actually did after not receiving the December updates for 1.5 days
You flash factory images, which require an unlocked bootloader, regardless of carrier.
Full OTA images are sideloaded via ADB/FASTBOOT without needing an unlocked bootloader.
They are equivalent, software wise, besides the requirement (or not) of an unlocked bootloader.
The main difference being that normally when during the process, you unlock/lock the bootloader the device is wiped, bringing it back to a factory state. Whereas, sideloading the OTA will not return it to a factory state.
As an FYI for those thinking of sideloading the global OTA onto their unlocked (purchased from Google) Pixel 5 while on Verizon: I did that for November's update and did notice that I completely lost signal one day in an area that I normally would have signal. It was about five mile stretch of road in a town where I normally travel and has decent 4G signal. I've traveled this stretch of road before during the month and no issues except this one time.
I don't know if it has anything to do with sideloading the global version of November's update or Verizon having trouble that day (down detector was reporting complaints for Verizon Wireless that day, along with a bunch of services using AWS).
Otherwise, I had no issues with my wireless service. (Other than thinking it's b s that it says "5G" all the time, when I know I'm in a 4G area.)
Edit: I did not receive the December OTA despite being on the global version of OS. I think the Verizon SIM somehow prevents the global OTA.
I don't know if it has anything to do with sideloading the global version of November's update or Verizon having trouble that day (down detector was reporting complaints for Verizon Wireless that day, along with a bunch of services using AWS).
Otherwise, I had no issues with my wireless service. (Other than thinking it's b s that it says "5G" all the time, when I know I'm in a 4G area.)
Edit: I did not receive the December OTA despite being on the global version of OS. I think the Verizon SIM somehow prevents the global OTA.
Last edited:
Yeah, that's what I thought. @InfX You might want to verify your experience. I didn't think you could flash a full image yet you said you did.
I had a bad Magisk module corrupt my device and I had to factory reset today. When I did, I flashed the original image (October) then let it update itself to November, then update again to December. Google pushed out the AT&T 010 December update to me, not the global one 011. I had an AT&T Sim card inserted at the time, so I'm assuming there is good reason to be on that variant if your carrier is AT&T.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone