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
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!
Hello Everyone!
I am sure this has been passed around multiple times, but my searches are getting me no results, and this is driving me crazy.
For the life of me I cannot get SuperSU to install and root! I've included what I've attempted to install via TWRP below..
I also have another question relating to slots...
So when I install Lineage OS on Slot B, Lineage OS installs it's own custom recovery, which forces me to install TWRP on Slot A, I have to boot into bootloader to switch active slot to get back into TWRP, is there a way around that?
Phone: Google Pixel XL from Verizon
ROM: https://forum.xda-developers.com/pixel-xl/development/rom-lineageos-14-1-nightlies-google-t3601893 (Lineage OS 7.1.2)
SuperSU: I've tried v2.79-SR3, and v2.79-SR2, and also the latest beta version available: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TWRP: 3.1.0 RC2
Steps:
Booted into bootloader, fastboot twrp recovery, installed on slot A
switched into slot B via TWRP, formatted data, installed the latest ROM from list above.
Installed SuperSU (versions above)
Any help would be great!
You may need to search for magisk 13.1 and use that instead of SuperSU.
Milly7 said:
You may need to search for magisk 13.1 and use that instead of SuperSU.
Click to expand...
Click to collapse
Has Magisk 13.1 been ported for pixel yet?
i know 13 has, but there have been a lot of reports of people going back to 12 following the switch
y2grae said:
Has Magisk 13.1 been ported for pixel yet?
i know 13 has, but there have been a lot of reports of people going back to 12 following the switch
Click to expand...
Click to collapse
Not sure about that. But I know on other devices supersu doesn't play well with updated Roms
Do you have an un-updated Verizon Pixel? With the latest versions of Android, the bootloader can't be unlocked on the Verizon version
Seeing as the OP is booting into bootloader and switching slots... I'd say it was already unlocked
KeithGS said:
Hello Everyone!
I am sure this has been passed around multiple times, but my searches are getting me no results, and this is driving me crazy.
For the life of me I cannot get SuperSU to install and root! I've included what I've attempted to install via TWRP below..
I also have another question relating to slots...
So when I install Lineage OS on Slot B, Lineage OS installs it's own custom recovery, which forces me to install TWRP on Slot A, I have to boot into bootloader to switch active slot to get back into TWRP, is there a way around that?
Phone: Google Pixel XL from Verizon
ROM:https://forum.xda-developers.com/pixel-xl/development/rom-lineageos-14-1-nightlies-google-t3601893 (Lineage OS 7.1.2)
SuperSU: I've tried v2.79-SR3, and v2.79-SR2, and also the latest beta version available: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TWRP: 3.1.0 RC2
Steps:
Booted into bootloader, fastboot twrp recovery, installed on slot A
Installed SuperSU (versions above)
Any help would be great!
Click to expand...
Click to collapse
You're using the wrong supersu. You need 2.82 SR1
Crap nevermind lol. Just realized the link. Wow I'm cooked.
strra said:
Do you have an un-updated Verizon Pixel? With the latest versions of Android, the bootloader can't be unlocked on the Verizon version
Click to expand...
Click to collapse
Is this really true? I have the bootloader already unlocked but I was gonna file a claim to get it replaced eventually due to scratches and dinks I don't wanna end up with a pixel from Verizon that's perma bootloader locked.
So you guys are saying to use magik instead?
KeithGS said:
Is this really true? I have the bootloader already unlocked but I was gonna file a claim to get it replaced eventually due to scratches and dinks I don't wanna end up with a pixel from Verizon that's perma bootloader locked.
Click to expand...
Click to collapse
yes, as of 7.1.1, there is no bootloader unlock for Verizon Pixel
Thanks... So about magisk where do I get the pixel XL one because the official thread says there is no support for it yet.
strra said:
yes, as of 7.1.1, there is no bootloader unlock for Verizon Pixel
Click to expand...
Click to collapse
I wonder if a refurbished would be updated since Verizon outsourced their replacement team
KeithGS said:
Thanks... So about magisk where do I get the pixel XL one because the official thread says there is no support for it yet.
Click to expand...
Click to collapse
The unofficial version of Magisk is hosted in the Resurrection Remix rom thread. You should also be able to find which version of Magisk Manager is compatible with the unofficial build in that thread.
---------- Post added at 09:07 PM ---------- Previous post was at 08:58 PM ----------
KeithGS said:
I wonder if a refurbished would be updated since Verizon outsourced their replacement team
Click to expand...
Click to collapse
You would be taking a big chance if having an unlocked bootloader is important to you. 7.1.1 is from early this year and getting a refurbished phone that out of date is unlikely. Some Verizon users have reported getting the Google version with the oem unlock option available back instead of the locked Verizon version but that would be like winning the lottery --odds aren't good that would happen if you RMA'd your phone. Also, even if you did get a Google version back you would need to enable OEM unlocking immediately before accepting any system updates from Verizon. The first Verizon system update installed while OEM Unlocking is not enabled will permanently disable the option. Someone reported that they locked their bootloader but didn't disable OEM Unlocking and that a Verizon update disabled the option for them--so at this point you might actually need to have your bootloader unlocked before accepting any Verizon updates.
jhs39 said:
The unofficial version of Magisk is hosted in the Resurrection Remix rom thread. You should also be able to find which version of Magisk Manager is compatible with the unofficial build in that thread.
---------- Post added at 09:07 PM ---------- Previous post was at 08:58 PM ----------
You would be taking a big chance if having an unlocked bootloader is important to you. 7.1.1 is from early this year and getting a refurbished phone that out of date is unlikely. Some Verizon users have reported getting the Google version with the oem unlock option available back instead of the locked Verizon version but that would be like winning the lottery --odds aren't good that would happen if you RMA'd your phone. Also, even if you did get a Google version back you would need to enable OEM unlocking immediately before accepting any system updates from Verizon. The first Verizon system update installed while OEM Unlocking is not enabled will permanently disable the option. Someone reported that they locked their bootloader but didn't disable OEM Unlocking and that a Verizon update disabled the option for them--so at this point you might actually need to have your bootloader unlocked before accepting any Verizon updates.
Click to expand...
Click to collapse
Caused my phone to go into an infinite bootloop.
KeithGS said:
Caused my phone to go into an infinite bootloop.
Click to expand...
Click to collapse
I've never heard of anyone bricking a Pixel XL yet. Completely power down your phone. Let it sit for a minute. Power directly into the bootloader mode by pressing power and volume down at the same time. When the phone vibrates let go of both buttons. Once in bootloader mode you can flash-all.bat the latest factory image from Google's website and you should be fine.
What were you doing exactly that led to the bootloop?
I am a bit confused by all the posts about this subject
I would like to unlock my phone, for future rooting, when everything is more stable, meanwhile I want to get OTA updates on the phone "automaticaly", is that possible
You can definitely unlock the bootloader and still receive OTA.
And for your first point, rooting is plenty stable already, so no need to wait for that. Though if you aren't well versed in fastboot or root upgrade processes, you should definitely read all the most recent guides on it to make your transition smoother.
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
melorib said:
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
Click to expand...
Click to collapse
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
wtherrell said:
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
Click to expand...
Click to collapse
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
melorib said:
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
Click to expand...
Click to collapse
There's issues with Magisk and some other phones, but topjohnwu has a Pixel 2 I believe, so he tests on that.
Magisk for our phones is perfectly stable, the only issue is people don't like the dtbo image being edited to remove AVB 2.0/dm-verity.
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
canemaxx said:
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
Click to expand...
Click to collapse
Strange, there was at least an update in January
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
canemaxx said:
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
Click to expand...
Click to collapse
Why? I want OTA updates...
I'm not sure why they just have not come to my phone.
canemaxx said:
I'm not sure why they just have not come to my phone.
Click to expand...
Click to collapse
You only unlocked the bootloader? Maybe because it is Verizon, the bootloader is supposed to to be locked!
I can't see that being the reason as I bought the phone from the Google store
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
Sounds strange, maybe you updated before OTA was available for Verizon...
In 2 weeks I get mine, going to unlock before any update, it was bought December, so it has at least one update missing...
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
v12xke said:
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
Click to expand...
Click to collapse
Thanks I know how to sideload or flash the full image but just was hoping I wouldn't have to again and again
Are your phones enrolled on the Android Beta Program ? My P2 was and I never got the Jan. Update till I Unenrolled from the beta program. Immediately afterwards I checked and Jan update was available.
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
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