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.
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 got a security update today. Patch level May 1 2018. VS99620c. Security software version MDF v3.1 Release 2
bilbo60 said:
I got a security update today. Patch level May 1 2018. VS99620c. Security software version MDF v3.1 Release 2
Click to expand...
Click to collapse
So you don't care about bootloader unlock, TWRP custom recovery, and root?
Why are you still getting Verizon updates?
You should be on converted US998 with unlocked bootloader and rooted...
Any update from June on will probably thwart the easy bootloader unlock exploit. Be warned. Unlock bootloader now while you can.
See post #193 of the WTF thread:
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
ChazzMatt said:
So you don't care about bootloader unlock, TWRP custom recovery, and root?
Why are you still getting Verizon updates?
You should be on converted US998 with unlocked bootloader and rooted...
Any update from June on will probably thwart the easy bootloader unlock exploit. Be warned. Unlock bootloader now while you can.
See post #193 of the WTF thread:
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
Click to expand...
Click to collapse
I also got the update but have not installed it. I have been reading very carefully about switching to US998. I've been hesitating to be honest. It's a long process and I'm afraid of messing up lol. I'm gonna have to take the risk. Plus, I don't see alot of ROMS that is compatible with US988, that's another reason that's keeping me from switching.
Sent from my VS996 using Tapatalk
WebDev28 said:
I also got the update but have not installed it. I have been reading very carefully about switching to US998. I've been hesitating to be honest. It's a long process and I'm afraid of messing up lol. I'm gonna have to take the risk. Plus, I don't see alot of ROMS that is compatible with US988, that's another reason that's keeping me from switching.
Click to expand...
Click to collapse
It's not a long process. From flashing Nougat US998and then OREO US998 KDZ, even with Master Reset in between, takes 10 minutes.
Then flashing bootloader unlock code, TWRP and root is another 10 minutes.
What takes some time is the prep beforehand. Getting all the stuff downloaded, ready to go.
From beginning to end can be 20 minutes.
@acidikjuice, was it easy?
acidikjuice said:
Success Here!
Took a LS phone form ebay and cross-flashed to US998. It was super easy. Just make sure to follow the instructions to make the correct folder in Windows and make sure to install LG drivers and software. It was easy using the provided notes.
The unlocking part was super easy.... too easy! The door will shut on this. That is too bad! I might get one more V30 The rooting part was a little harder only because my Android tools were out of date. I had to force Windows to take the latest Oreo drivers and then fastboot commands worked fine.
Outcome: I now have a V30+ running on the Verizon network with US998 Oreo. The reception is killer strong and have no 3G/4G LTE connectivity issues at all. Got on the network instantly. I'll worry about voice mail and perhaps wifi calling later. Rooted and unlocked.
Thanks everyone for putting this together! To bad the door shuts in June it sounds like. So happy I could get in before the lock!
Click to expand...
Click to collapse
A couple of downside is no wifi calling and I don't have a signal if it's not 4G. My phone will not switch to 3G it just won't give me a signal. Other then that root and unlocked bootloader are a plus but it all depends on that's most important to you.
DroidForLife33 said:
A couple of downside is no wifi calling and I don't have a signal if it's not 4G. My phone will not switch to 3G it just won't give me a signal. Other then that root and unlocked bootloader are a plus but it all depends on that's most important to you.
Click to expand...
Click to collapse
Don't blame that on bootloader unlocking and root.
You can have Wi-Fi calling and you have the exact same 3G bands you had before.
ChazzMatt said:
Don't blame that on bootloader unlocking and root.
You can have Wi-Fi calling and you have the exact same 3G bands you had before.
Click to expand...
Click to collapse
I'm not blaming anything on anyone. Everything done on your phone is your choice. I found the instructions for wifi calling and that's a no go. Others have reported the some. Wifi calling not a big as getting 4g and 3g working correctly.
ChazzMatt said:
So you don't care about bootloader unlock, TWRP custom recovery, and root?
Why are you still getting Verizon updates?
You should be on converted US998 with unlocked bootloader and rooted...
Any update from June on will probably thwart the easy bootloader unlock exploit. Be warned. Unlock bootloader now while you can.
See post #193 of the WTF thread:
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
Click to expand...
Click to collapse
No, I'm not interested in root, but wanted to alert others, because I had heard that the carriers were apt to block the exploits in the future.
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
Folks with the Google purchased unlocked version....did you get the update? I have not so far. I know I can side load it but I am curious if it is just me.
Nothing for me. I'm curious tho, I had to sideload the Nov update to get the Verizon build. So now I'm waiting to see if the OTA will come for Dec.
Nothing for me either. If I wanted to sideload the OTA, would I get the one for US carriers? I don't see a Verizon specific one this time around.
Frankie1588 said:
Nothing for me either. If I wanted to sideload the OTA, would I get the one for US carriers? I don't see a Verizon specific one this time around.
Click to expand...
Click to collapse
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
I haven't received the update yet either. I've got the files downloaded and ready but I'm gonna wait a little bit to see what happens.
I believe the .a1 update is for Canada, correct me if I'm wrong
bizdiddy said:
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
Click to expand...
Click to collapse
I sideloaded the US carrier OTA to both mine and my wife's Verizon P6Ps with no issues.
spotmark said:
I sideloaded the US carrier OTA to both mine and my wife's Verizon P6Ps with no issues.
Click to expand...
Click to collapse
Just to confirm, yours are the unlocked variant from Google right? Thanks!
Frankie1588 said:
Just to confirm, yours are the unlocked variant from Google right? Thanks!
Click to expand...
Click to collapse
No, they are both bootloader locked Verizon variants.
Edit - My apologies. I didn't notice that you were asking about unlocked models.
At this point I've seen no evidence that anyone in the US on Verizon has had the update properly pushed OTA to their phone.
I miss the days when the "Check for Update" button worked and would actually pull the update.
jimistixx said:
At this point I've seen no evidence that anyone in the US on Verizon has had the update properly pushed OTA to their phone.
I miss the days when the "Check for Update" button worked and would actually pull the update.
Click to expand...
Click to collapse
Yup. I never got any OTAs since day 1 on mine. Had no issues with this with my 2 XL or 5.
I'm using unlocked on Verizon and had to sideload the US update. So far the phone is a lot more stable and reception seems to be slightly better.
Guyinlaca said:
I'm using unlocked on Verizon and had to sideload the US update. So far the phone is a lot more stable and reception seems to be slightly better.
Click to expand...
Click to collapse
Thanks! Going to sideload now.
Lets light up the Google forum a bit. There is already a thread on it so please add your experience. There is something missing between Google and Verizon.
Pixel 6 Pro not getting December update - Google Pixel Community
support.google.com
bizdiddy said:
My question exactly. I'm wondering if they are now doing away with the Verizon specific builds and keeping it standard across all US carriers. Same situation here and no update yet.
Click to expand...
Click to collapse
They always work towards having one US version. If you look at the history of the other phones on the factory image page you will see where they split apart but often come back together in a month or two.
So as we sideload we load the US version.
I have a pixel 6 pro unlocked purchased from Google and haven't received the update. I hate to ask but can someone point me in the right direction to side load the update. I've never side loaded an update and could use the assist. Thank you all in advance
jughead75 said:
I have a pixel 6 pro unlocked purchased from Google and haven't received the update. I hate to ask but can someone point me in the right direction to side load the update. I've never side loaded an update and could use the assist. Thank you all in advance
Click to expand...
Click to collapse
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are full instructions at the link above but let me give you cliff notes.
Download the platform tools to your computer so you have ADB.
Download the CORRECT OTA image from the link above and copy the zip to the platform tools folder. Do not extract it, leave it as a zip.
Connect your phone to your computer with USB Debugging turned on in Developer Options.
Reboot into recovery then issue the adb command to load the OTA file.
TonikJDK said:
Lets light up the Google forum a bit. There is already a thread on it so please add your experience. There is something missing between Google and Verizon.
Pixel 6 Pro not getting December update - Google Pixel Community
support.google.com
Click to expand...
Click to collapse
They don't even have the update on their software update page yet. The 11/16 update states it is October patch level. Lame. No wonder no one is getting it. There is zero reason to wait for a Verizon OTA any longer. I have the Google version unlocked on Verizon and flashed the US December build.
Google Pixel 6 Software Update | Verizon Customer Support
Get instructions on downloading the latest software update for performance improvements to your Pixel 6, including current Android security patches.
www.verizon.com
TonikJDK said:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are full instructions at the link above but let me give you cliff notes.
Download the platform tools to your computer so you have ADB.
Download the CORRECT OTA image from the link above and copy the zip to the platform tools folder. Do not extract it, leave it as a zip.
Connect your phone to your computer with USB Debugging turned on in Developer Options.
Reboot into recovery then issue the adb command to load the OTA file.
Click to expand...
Click to collapse
Thank you! I appreciate the help
Bumping this with a title change. Just learned my kids unlocked has not updated. He is on ATT.
So wondering if other carriers have the same issue.
I got impatient and sideloaded the OTA for my unlocked P6P on Verizon's network. I used the .017 OTA image and all went smoothly.
My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?
The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/
Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?
If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.
TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.
chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.
chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!