Develop Bugs

April Security Update - Two Versions? April 1st vs. April 5th

Many users reported TWO different variants of the April Security Update. One which is labeled April 1st and another April 5th. I am confused by this as well, I want to get all the hotfixes but my build does not match Google's OTA page.
I'm using a Pixel XL 2 and I have April 1st version on TELUS network. I got it yesterday night, the download was 46.6 MB My build number is OPM4.171019.015.A1 BUT per Google official OTA website it says I should have 8.1.0 (OPM2.171019.029, Apr 2018)
Can anyone shed some light on these TWO variants? Many Rogers users got April 1st but a few got April 5th. Bell seems to be all on April 5th. Telus/Koodo seems to be a mixed bag also.

The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.

ilal2ielli said:
The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.
Click to expand...
Click to collapse
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants

Waibashi said:
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants
Click to expand...
Click to collapse
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5

Two versions a couple of days apart of actually pretty common.

ilal2ielli said:
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5
Click to expand...
Click to collapse
That's explained a lot, thanks!
BUT for the Pixel security update. That means im missing on all the bugfixes if I understood correctly... It says here that all the hotfixes are included in. The 2018-04-05 version.
https://source.android.com/security/bulletin/pixel/2018-04-01

The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.

stevemw said:
The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.
Click to expand...
Click to collapse
So what would explain I have only received the April 1st update ? Is it possible to have two updates in one month? I never noticed that.
This is the first time I get the 1st patch too. I'm not the only one

I was able to update to the 4/5 patch at 8PM, 4/4. I'm on the Pixel 2 XL. Which model do you have? Have you done anything to the stock software?

Pixel 2 XL 64GB Stock OS.
I used the Beta Enrollment in the past, but this is a fresh phone from RMA.

Unable to update Latest Pack
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL

navi_j said:
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL
Click to expand...
Click to collapse
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:

Badger50 said:
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:
Click to expand...
Click to collapse
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks

navi_j said:
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks
Click to expand...
Click to collapse
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update ?

Badger50 said:
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update
Click to expand...
Click to collapse
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.

navi_j said:
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.
Click to expand...
Click to collapse
Just put your phone in bootloader mode, connect to pc, open up your command prompt, and run the command...fastboot flashing unlock_critical....
Again, this Will completely wipe your phone! ?

Has GPS lock issue been fixed?

Seems my thread got hijacked

Problems w/ P2XL running PPP3 (device uncertified and can't opt out)

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

Android Q Beta on the Pixel 3a XL

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

Question Should I upgrade before rooting my Pixel 6 Pro?

Hey, I'm on 210817.036 (Nov. 2021) on an unlocked Pixel 6 Pro.
I was finally able to unlock it today from AT&T and wondering if I should update to the latest Android update before rooting.
Thanks for any advice!

I wouldn't bother, because OTAs take longer than flashing full firmware. i.e. As part of the rooting process, I would go ahead and flash the latest full firmware instead.
SDK Platform Tools
Get the Google USB Driver
Official Google Android Flash Tool

Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.

DevanteWeary said:
Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.
Click to expand...
Click to collapse
You're welcome!
I never had any issues at all, even with the fingerprint reader, from the end of October when I received mine through the second February patch. Hopefully, yours will be the same way.
At worst, once you unlock the bootloader if you have any issues with how things run, you can always flash any firmware you like. Be careful. You can also accidentally flash the wrong firmware. Coincidentally, I accidentally gave you a link to the official flashing site, which is good for staying stock unrooted, but if you're going to be rooted, I actually recommend the Pixel 6 Pro Factory Images. Just only ever use images that have Raven in the name as flashing the wrong thing can make it so that your phone would be unrecoverable.
Forgive me if I'm repeating anything you already know.

How to unroot and reset a pixel 3a XL to factory settings?

I am trying to unroot my Pixel 3a XL and reset to the factory settings and lock the boot loader so I can trade in my phone. It is currently on Android 10 Build QQ1A.191205.011. I believe I used something called ElementalX. It was rooted with Magisk a number of years ago. I don't know a whole lot about this whole process, so was hoping someone could point me in the right direction. I have seen some guides but they are generally older and I am not really sure which files I need to download.
So far I have the:
Newest platform tools
(Downloaded from Google’s Factory Images page) bonito-sp2a.220505.006-factory-5adf2317.zip