Related
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
bjoostema said:
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
Click to expand...
Click to collapse
I thought I was the only one, I didn't get the OTA yet either, I'm still waiting even though it's supposed to be out and Verizon normally has it ready to download immediately when they say it's ready on their software update page.
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Well that helps, I have a play store phone but Verizon service and I haven't been able to get OTA yet even when I tell it to go look. I guess I will have to wait until Verizon gets going on this. Taking the sim card out and rebooting does not help.
Sent from my BTV-W09 using Tapatalk
bjoostema said:
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Click to expand...
Click to collapse
I got the OTA, it's 7.1.2 and definitely the NHG47K
LaosPerson said:
I got the OTA, it's 7.1.2 and definitely the NHG47K
Click to expand...
Click to collapse
Are you able to grab the link?
rozyman17 said:
Are you able to grab the link?
Click to expand...
Click to collapse
Link for what? Sorry I'm confused lol.
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Any time there is an update I just grab it from https://developers.google.com/android/images. I haven't tried flashing the OTA from the page since I usually grab the full factory image (I don't mind starting over lol). I am on Verizon and my build number after I flash the factory image is N2G47E. There are no Verizon apps on the images , but during set up it will prompt to download all that Verizon crap-ware, which you can cancel or uninstall.
As of last night, Verizon has released the K build, which is not up on the developer site. Must be something in there that is better than the E build on their network. Just an FYI.
rozyman17 said:
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Click to expand...
Click to collapse
I did the same thing earlier this week. Just checked for updates and nothing. Hope I am not hosed lol.
I ended up with the Verizon version OTA last night (non rooted, google play phone on Verizon service). I did not notice any Verizon-ware installed on the phone, at least not yet. Seems pretty flawless so far.
Sent from my Pixel XL using Tapatalk
Anyone able to upload the OTA?
I would be concerned with the Verizon firmware locking the bootloader on Google Play store Pixels
I don't think that's how it works.
After the frustration it took for me to get stock 7.1.2 on my PXL, I'll wait to see how people like the K build before I consider going back to 7.1.1 so I can be recognized and offered the OTA.
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Trooper27 said:
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Click to expand...
Click to collapse
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
It seems to bounce back and forth, sometimes there is a Verizon specific firmware sometimes there isn't, but it would be nice to know before side loading how many branches of the firmware there will be.
Sent from my Pixel XL using Tapatalk
destruya1 said:
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
Click to expand...
Click to collapse
I am not unlocked so I have no option of doing that. I had no clue there would be a Verizon specific build or what I have not sideloaded earlier this week. Guess I have to learn patience LOL.
But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
https://mobilesupport.lenovo.com/us/en/solution/MS118647
Pig Vomit said:
But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
https://mobilesupport.lenovo.com/us/en/solution/MS118647
Click to expand...
Click to collapse
I'm on the NPN25.137.35 with the latest security patch level showing from January. Phone is telling me it is up to date Not sure it maters but I'm in Salt lake City, UT.
I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk
redbeard1083 said:
I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk
Click to expand...
Click to collapse
Stange, why would you have had the update for a week and I havn't even received it yet?
emoney1219 said:
Stange, why would you have had the update for a week and I havn't even received it yet?
Click to expand...
Click to collapse
It's very typical for carriers and manufacturers (including Google for Nexus/Pixel) to do staggered rollouts of updates. It reduces server load, but more importantly, if there is a bug the people who get it early (there are typically not that many who get it early) would report the bug. Then the second batch of people getting it is bigger, then the third even bigger. Rollouts can last 3-4 weeks. I wouldn't panic. We are their beta testers.
Location probably doesn't matter. I'm based in OC, but currently in the Palm Springs area.
redbeard1083 said:
I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk
Click to expand...
Click to collapse
Flashable from TWRP or fastboot?
Edit: Question Answered
Pig Vomit said:
But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
Click to expand...
Click to collapse
Hi,
Identical to the RETEU update from the last week! Still waiting for a "real" update.
Still nowt for retgb
I tried to adb sideload the zip above but I get an error. Any ideas? I dropped the name "BLUR version" and renamed the zip "update.zip"...got the error. I redownloaded and renamed to NPNS25.137-35-5...same error
Edit: here is the error message "package expects build thumbprint of 7.0/NPNS25.137-35-5/5 user release-keys or 7.0/NPN25.137-35/37 user release keys; this device has 7.0/NPN25.137-33/35 user/release -keys"
Is there another firmware that I need to download and apply first?
Edit 2: does motorola require fastboot all the files (unzipped) instead of adb? In my other phones I just put the update.zip file on the root directory and applied with stock recovery. That did not work either. Same error message.
long2ski said:
I tried to adb sideload the zip above but I get an error. Any ideas? I dropped the name "BLUR version" and renamed the zip "update.zip"...got the error. I redownloaded and renamed to NPNS25.137-35-5...same error
Edit: here is the error message "package expects build thumbprint of 7.0/NPNS25.137-35-5/5 user release-keys or 7.0/NPN25.137-35/37 user release keys; this device has 7.0/NPN25.137-33/35 user/release -keys"
Is there another firmware that I need to download and apply first?
Edit 2: does motorola require fastboot all the files (unzipped) instead of adb? In my other phones I just put the update.zip file on the root directory and applied with stock recovery. That did not work either. Same error message.
Click to expand...
Click to collapse
You should probably just wait until the OTA pops up on your device.
Nothing yet for me. Pennsylvania, RETUS. Will notify once I have it available.
arhncmh said:
Nothing yet for me. Pennsylvania, RETUS. Will notify once I have it available.
Click to expand...
Click to collapse
I'm in NYC and just got it. I installed it but it was weird, my security updates updated to May 2017, but my build number is still NPNS25.137-33-5. I checked again for updates but it said I'm current. Also, my kernel is 3.18.31 dated 5/11/2017. Did I update?
MrBelter said:
Still nowt for retgb
Click to expand...
Click to collapse
I installed this https://www.androidfilehost.com/?fid=961840155545581088 using the toolkit on this forum and works all ok here in the UK.
Wifi, NFC, etc all seem to be working. Even got Google Assitant fired up
Happy days
esoh said:
I'm in NYC and just got it. I installed it but it was weird, my security updates updated to May 2017, but my build number is still NPNS25.137-33-5. I checked again for updates but it said I'm current. Also, my kernel is 3.18.31 dated 5/11/2017. Did I update?
Click to expand...
Click to collapse
yep. they added -5.
redbeard1083 said:
yep. they added -5.
Click to expand...
Click to collapse
I think my security updated to May but I don't think my firmware upgraded. It was on 50MB file.
Adb sideload
Has anyone tried to do a ADB sideload with the OTA yet?
QUOTE=redbeard1083;73003392]I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk[/QUOTE]
I would say just be patient. I received the update yesterday. You've waited this long, right?
Pig Vomit said:
But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
https://mobilesupport.lenovo.com/us/en/solution/MS118647
Click to expand...
Click to collapse
This update should contain the bugfixes up through the May security bulletins if I understand it correctly.
https://source.android.com/security/bulletin/
Started prompting me for this update last weekend on amz branch.
Im in NYC as well and just got the update. It showed as NPN25.137-35 but it said it was a 20MB download. I have the amazon prime version of the phone and once i finished the update, it still shows NPN25.137.33 and the security patch level still shows Jan1, 2017.
Now when i check for updates, software is up to date. Wierd. Anyone else experience this?
I've checked for a US g5+ support page fairly regularly since getting the phone. It hasn't even been listed on the support page until the last week or so. But, while it's finally listed.......there's only a generic Lenovo placeholder on it. Several months after the phone's release.
https://mobilesupport.lenovo.com/us/en/products/Cell-Phones/Android-Series/Moto-G-Plus-5th-Gen
I've got a Lenovo laptop......their customer service and software upgrades suck. I once sent in my rather expensive Yoga laptop for warranty trackpad repair......and they had it for two months and despite repeated checking their website and calling, I could never get an estimated repair date. Finally, they gave me a date......4 more months. I raised holy hell and they sent me a new, more recent Yoga release. The support page for the laptop seems to update with Lenovo bloatware "upgrades" fairly regularly.....but their support for more important basic drivers is pretty lacking (wifi, bluetooth and graphics drivers from 2015 and 2016, anybody? Yeah, didn't think so.). And, yeah, first thing I do when getting any new PC is a clean install with no bloatware, but Lenovo also makes it tough to keep drivers updated through forced windows updates by using hardware IDs which make it hard for you to install generic component drivers, unimportant drivers like Intel graphics drivers. So you install the latest, and a forced windows update uninstalls the Intel release and installs a mid-2016 driver for you. Thanks! So there are obscure ways to defeat that.
Oh, and then there's the touchpad Synaptics drivers (Lenovo specific) where two finger tap (right click menu) has NEVER been fixed. Takes a registry modification to fix it.
Anyway...enough venting about Lenovo/Moto poor support. I knew it when I purchased the phone, and I'd still buy it again.
Has anyone seen this yet?
I saw the files were available for manual, but nothing on the OTA front yet.
İf you mean Oreo 8.1 January patch, it is already pushed one week ago. Maybe you can try forcing it by pushing check updates in settings?
Same here, still no update
Scythe said:
İf you mean Oreo 8.1 January patch, it is already pushed one week ago. Maybe you can try forcing it by pushing check updates in settings?
Click to expand...
Click to collapse
Surprisingly that's where I've been checking, hence the post.
I havent gotten it either. Boot loader is locked and on stock image
Can manually install the ota. https://developers.google.com/android/ota
I never got it either. I'm locked and stock on VZW. Manually sideloaded with no issues.
Flyhalf205 said:
Can manually install the ota. https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know, I said I saw the manual available
wonder why it's not been pushed to OTA though
y2grae said:
I know, I said I saw the manual available
wonder why it's not been pushed to OTA though
Click to expand...
Click to collapse
I've read articles in the past that say they push them in waves over a couple weeks. My 6p has taken over a month before to get the update.
I had to side load mine I'm stock and nothing showed up
Gizmoe said:
I've read articles in the past that say they push them in waves over a couple weeks. My 6p has taken over a month before to get the update.
Click to expand...
Click to collapse
They said in January pressing the check for update would push it to the device.
Those who have a computer (which is all I hope) and ADB set up why bother waiting for the damn OTA! Sideloading FTW!
drozek said:
They said in January pressing the check for update would push it to the device.
Click to expand...
Click to collapse
They lied obviously lol. Maybe next month...
Nothing here as well
I was prompted to update, and then followed the Magisk instructions to remove and then install the OTA, then put Magisk back on slot 2, but the install of the OTA failed. Any suggestions?
I never received the update either. Dropped off beta program and was able to get the monthly security update. It didn't have to reset my pixel either
Update finally arrived
Restarted my phone today and after the reboot it said finishing update. Never got notified about it. Weird.
TheCelt said:
I never got it either. I'm locked and stock on VZW. Manually sideloaded with no issues.
Click to expand...
Click to collapse
Same here
Sent from my Pixel XL using Tapatalk
I got it finally today!
For the June security update, there's a version specific to T-Mobile (OPM4.171019.021.E1). My carrier is an MVNO of T-mo. Should I load that version or the standard OPM2.171026.006.C1 image?
P2 XL, stock rooted.
why not just check for updates, it will give you the correct OTA, no need to flash factory images for the security patch.
angus242 said:
For the June security update, there's a version specific to T-Mobile (OPM4.171019.021.E1). My carrier is an MVNO of T-mo. Should I load that version or the standard OPM2.171026.006.C1 image?
P2 XL, stock rooted.
Click to expand...
Click to collapse
You could also go to "Settings" , "System" then "About Phone" and it will give your current build at the bottom. Just see which May OTA you have installed and use the corresponding June update.
NeroDan said:
You could also go to "Settings" , "System" then "About Phone" and it will give your current build at the bottom. Just see which May OTA you have installed and use the corresponding June update.
Click to expand...
Click to collapse
The May update does not have a T-Mobile specific option; only Fi or not.
angus242 said:
The May update does not have a T-Mobile specific option; only Fi or not.
Click to expand...
Click to collapse
It will start with OPM2 or OPM4 though. Just download whatever one you currently have.
NeroDan said:
It will start with OPM2 or OPM4 though. Just download whatever one you currently have.
Click to expand...
Click to collapse
I have OPM1 LOL
I want to do a fresh install. I think I'll just do the May factory OPM2, allow the OTA to run for June and then root.
Thanks!
uicnren said:
why not just check for updates, it will give you the correct OTA, no need to flash factory images for the security patch.
Click to expand...
Click to collapse
I've been on the system update downloading screen for over a half hour (88.3MB). I'm just going to do a fresh install with the May factory image and allow the OTA to run before rooting again.
angus242 said:
For the June security update, there's a version specific to T-Mobile (OPM4.171019.021.E1). My carrier is an MVNO of T-mo. Should I load that version or the standard OPM2.171026.006.C1 image?
P2 XL, stock rooted.
Click to expand...
Click to collapse
The t mobile version is because people were having problems with Lte reception when using pixel 2 on t mobile network. It's the same as the other June update but with added radios. I normally flash the reg pixel update (non-carrier version) from Google.
Today I dirty flashed the t mobile version on top of the non-carrier specific may version from last month.
It worked flawless.
I noticed the last month or so my Lte is weird. No service or reception sporadically. So apparently they made an update just for factory unlocked pixel 2's running on T-Mobile. BTW TMobile don't even sell pixel 2's, so it's not a t mobile specific rom
T-Mobile seems to be your best bet....
Im on the same boat... I'm on Sprint. I got the June date and my Build number is OPM4.171019.021.E1 Which is the same build number as the factory image for T-Mobile. I guess its not specific to only T-Mobile... Im about to do a clean flash to root and install magisk. I hope it works lol
I'm on MintMobile(Tmo towers) and flashed the OPM4 image which apparently is meant Google Fi customers but so far I haven't noticed a difference between it and the OPM2 image I usually go with.
I'm on T-Mobile, installed the T-Mobile image (which I do every month because I'm rooted and use a custom kernel), now no more WiFi calling for me
Have these fixes been upstreamed into the P betas?
sirxdroid said:
I'm on T-Mobile, installed the T-Mobile image (which I do every month because I'm rooted and use a custom kernel), now no more WiFi calling for me
Click to expand...
Click to collapse
Did you get this resolved? I am considering downloading the T-Mobile version since my LTE randomly doesn't work even when I have a strong signal.
PuffDaddy_d said:
Did you get this resolved? I am considering downloading the T-Mobile version since my LTE randomly doesn't work even when I have a strong signal.
Click to expand...
Click to collapse
Moved to Pie since, but while on Oreo I did use the T-Mobile builds.
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.