Related
For some reason my phone will not let me take the newest update for the Verizon G4. Does anybody know of another way besides OTA or Verizon Update Assistant that I could update my phone? Can't find the KDZ to try and flash. Any help would be appreciated. Thank You
Mine won't see it either. They may have pulled the update?
Are you rooted?
geoff5093 said:
Are you rooted?
Click to expand...
Click to collapse
No not rooted
I would also love to hear of a way to update to Verizon's 12a without OTA. I unrooted my 11a version in order to get 12a to fix touchscreen issues. It seems the 12a OTA is not around, at least verizon doesn't want to give it to me.
Oddly enough after using kdz for 11a my software showed status as "Official". But a few hours later it switched to Modified, even though I'm not rooted. Not sure why.
I don't see it either
photos.by.fako said:
For some reason my phone will not let me take the newest update for the Verizon G4. Does anybody know of another way besides OTA or Verizon Update Assistant that I could update my phone? Can't find the KDZ to try and flash. Any help would be appreciated. Thank You
Click to expand...
Click to collapse
Same here, my phone is unrooted, and it is on Verizon Network.
I have tried OTA update, it keep saying i already have the latest update (which is 11A)
I have also tried Verizon Update Assistant Installer (working in windows 7, but not in Windows 10), same thing, when I tried to update, it keep saying I already have the latest update (which is 11A)
do any one know Verizon push OTA by the list? (e.g. some people will get first, and some people will get last) or every one should get OTA at once?
Also, is possible Verizon pull the 12A update due to notification issue?
thanks
It's highly likely that Verizon pulled this update. Nobody has reported receiving it since about 10/10. I'm sure we'll see a new one drop soon that fixes whatever was wrong with 12A.
oldblue910 said:
It's highly likely that Verizon pulled this update. Nobody has reported receiving it since about 10/10. I'm sure we'll see a new one drop soon that fixes whatever was wrong with 12A.
Click to expand...
Click to collapse
Thanks for the info.
Hoping Verizon does not take too much time, We will get Marshmallow soon, then 12A is no longer needed.
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!
Has anyone flashed the NKG47L June Security update for Tmobile/Fi Carriers to their Pixel? If so, did you lose VoLTE or Wifi Calling or both?
Wifi Calling and VoLTE were working fine on N2G47O and then I flashed the NKG47L OTA to my Pixel, which I am using with T-mobile, and I can no longer make a call without dropping to HSPA, and calls will not be made over wifi anymore.
Because you said you flashed the OTA I'm going to assume you didn't wipe your phone, so I would try doing that first after backing up all your data.
If that doesn't fix it then I would try flashing NJH47B and seeing if that solves it. NJH47B has the same radio and modem images as N2G47O.
Was going to leave a comment to you on reddit but felt like it would do more help here.
Namelesswonder said:
Because you said you flashed the OTA I'm going to assume you didn't wipe your phone, so I would try doing that first after backing up all your data.
If that doesn't fix it then I would try flashing NJH47B and seeing if that solves it. NJH47B has the same radio and modem images as N2G47O.
Was going to leave a comment to you on reddit but felt like it would do more help here.
Click to expand...
Click to collapse
thanks for the reply.
I have a Verizon Pixel that I am using on Tmobile, so it wont let me unlock the bootloader to flash another image. I cant flash the OTA for NJH47B because it says its older than my current baseband.
just wondering if anyone else has the same problem so I can know if its my phone or the update.
0ri0n said:
thanks for the reply.
I have a Verizon Pixel that I am using on Tmobile, so it wont let me unlock the bootloader to flash another image. I cant flash the OTA for NJH47B because it says its older than my current baseband.
just wondering if anyone else has the same problem so I can know if its my phone or the update.
Click to expand...
Click to collapse
I'm waiting for the OTA I'd rather not sideload. I'm in the same position as you are, Project Fi, Verizon locked phone. I'll let you know once they push the update.
edit: I just thought that this might be the reason the OTA hasn't gone out yet? Perhaps they are working this out before they push it. Be interesting to see if anyone else that sideloaded has this issue. Can you post the reddit thread for perusal?
Sent from my Pixel using XDA-Developers Legacy app
I sideloaded the ota and everything works for me. I'm using a play store bought phone though
Sent from my Pixel XL using Tapatalk
Works normal for me, on Fi on T-Mo.
I'm on T-Mobile and turned off WiFi calling several months ago because incoming callers didn't hear a ring on their end and would hang up before I could answer. Can anyone verify if this is working on the latest release?
bobby janow said:
I'm waiting for the OTA I'd rather not sideload. I'm in the same position as you are, Project Fi, Verizon locked phone. I'll let you know once they push the update.
edit: I just thought that this might be the reason the OTA hasn't gone out yet? Perhaps they are working this out before they push it. Be interesting to see if anyone else that sideloaded has this issue. Can you post the reddit thread for perusal?
Click to expand...
Click to collapse
Still waiting for the ota also, patiently
It appears to be fixed in the June update... for me at least. (After data wipe) Everyone used to complain about not hearing a ring when they called me while wifi calling was enabled. They now tell me that it's ringing when they call.
As far as the volte and wifi calling issue I had, a factory wipe fixed it. Sux that I had to do it, but it's working properly now on NKG47L
DROITURK182 said:
Still waiting for the ota also, patiently
Click to expand...
Click to collapse
id flash it myself
Okay good news I got the notice for the ota today by going into settings and manually clicking check for system updates. It's there but won't let me download it with my data, says to connect to wifi to download and install. But after June 15th it will let you download with data?
Verizon Pixel XL, but switched to T-Mobile, due to then saying their device was unlocked as well. Still on the May 2017 security patch though. Never received an OTA update for the June security patch. It's now July 4th. Anyone have the same problem? Anyone know how to fix it without having to sideload?
TBG3,
I'm having the same issue. I spoke with Google two days ago and the tech said that they hadn't pushed all of the June security updates out yet. I questioned him on that because it's now July. I asked him why hadn't all of Junes updates been pushed through? No logical answer was given. I'm hoping to receive an update for July.
TBG3 said:
Verizon Pixel XL, but switched to T-Mobile, due to then saying their device was unlocked as well. Still on the May 2017 security patch though. Never received an OTA update for the June security patch. It's now July 4th. Anyone have the same problem? Anyone know how to fix it without having to sideload?
Click to expand...
Click to collapse
I was lucky enough to be running the android o beta and unenrolled front the beta and it pushed the TMO June sec patch to my phone. WiFi calling and volte is working fine.
I have a ATT branded Moto Z2 with a Cricket SIM. I got the phone in late november, and it came with Android 7.1.1 with the June 1 SPL. I know that ATT has released several updates, the latest in December with the November 1st SPL,
but everytime I check for updates it says that my phone is up-to-date.
So far I tried to check for updates after a factory reset, and also tried to do an OTA update with an old ATT SIM in it. Nothing seems to be working.
I have posted on the lenovo support page but so far I have not got any answer. I am not the guy that has to have the latest software running, but the updates fixed the BlueBorne security hole...
Othat than using a Cricket SIM, the phone is stock, not rooted.
has anybody encountered the same problem? Thank you
So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
ululi said:
I have a ATT branded Moto Z2 with a Cricket SIM. I got the phone in late november, and it came with Android 7.1.1 with the June 1 SPL. I know that ATT has released several updates, the latest in December with the November 1st SPL,
but everytime I check for updates it says that my phone is up-to-date.
So far I tried to check for updates after a factory reset, and also tried to do an OTA update with an old ATT SIM in it. Nothing seems to be working.
I have posted on the lenovo support page but so far I have not got any answer. I am not the guy that has to have the latest software running, but the updates fixed the BlueBorne security hole...
Othat than using a Cricket SIM, the phone is stock, not rooted.
has anybody encountered the same problem? Thank you
Click to expand...
Click to collapse
Chrisy8s said:
So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
Click to expand...
Click to collapse
At least the T-Mobile versions can be rooted. As far as I know, the ATT cannot as of yet.
theres only been one update since august and thats a fixed august. the other being the oreo update thats available now
if you would like to update your phone we have the ota updates and can get you updated without unlocking your bootloader just let me know [email protected] on hangouts
Chrisy8s said:
So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
Click to expand...
Click to collapse
What OTA for Tmobile? Mine has NCX26. 7 as stated in Tmobile support site, I do know that OCX oreo release is suppose to be live but support site doesn't show it andy phone hasn't gotten it.
Found a way to get it to download updates.
So, after wasting my time with Motorola and ATT so-called "technical support", I decided to try something: I rebooted the phone in recovery mode (VOlume down + Power button) and put it in recovery mode. Rebooted from recovery mode, and bingo, it downloaded the next update (September SPL). It now shows "background installation..." in progress. Hopefully this is going to be the solution.
I did the update manually using the file nash_opx 27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC. Xml. zip and it worked perfectly.
djsboy said:
I did the update manually using the file nash_opx 27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC. Xml. zip and it worked perfectly.
Click to expand...
Click to collapse
I think I may have found the right recipe. The trick is to check for updates while NOT on WiFi. So move away from WiFi coverage, but still within Cell coverage, with Data on. Check for updates. It will say that an update is available and will be download when within WiFi range. Move back to where you have WiFi, and bingo, it will start downloading. I did it twice yesterday afternoon, once to go from the Sept to the Oct SPL, and then from the Oct SPL to the Nov SPL, which is the last available update according to the ATT page. All of this with my Cricket SIM. WHy this works is beyond my pay grade to figure out. I will eagerly wait for the next update to be posted to see if this trick works consistently. Again,
this seems to work with my ATT branded phone.
My ATT Z2 force, starting from last evening (1/24/2018), kept getting security update, from September, 2017. Then this morning, October 2017 and November 2017. Does this mean we are going to get Oreo update soon ?
So I've had my Moto zforce 2 for 3 days now. We're is the Oreo update ? T-Mobiles site says it was released Dec 22nd ?
lcc014 said:
My ATT Z2 force, starting from last evening (1/24/2018), kept getting security update, from September, 2017. Then this morning, October 2017 and November 2017. Does this mean we are going to get Oreo update soon ?
Click to expand...
Click to collapse
Dude..Let us know when u get Oreo update....So am I
Anyone on TMobile receive the ota update ?
There are issues with calling and sms on the T-Mobile variant. The update has been pulled while they sort out the issues.
Well that makes sense why I'm not seeing it then.
I am still not able to get the AT&T update past June. I tried the reboot into recovery and nothing. Is there a way to manually install the update from an SD card which would allow for OTA updates in the future?
TheLooq said:
There are issues with calling and sms on the T-Mobile variant. The update has been pulled while they sort out the issues.
Click to expand...
Click to collapse
Good. On my account we got 2 of them for Christmas. A few days after Christmas, one of them updated to Oreo. At this point, the Galaxy S7 Edge on our account could not hear the Z2 Force. Went through everything with T-Mobile support including network settings reset, factory resetting both the Samsung and Motorola phones. Didn't fix it. Meanwhile, the Z2 Force that was still on Nougat was fine. A few days later, it also updated to Oreo, and now neither Z2 Force can be heard on the Samsung. I hope they get this mess cleaned up soon since it's been a month.
It seems to be only between those two phones. Until the next update/patch is released, the workaround is to disable VoLTE in call settings on the z2.
Got AT&T update to 8.0.0 this morning.
I received notice of the Tmobile Oreo update, downloaded it, but cannot install it. It only says something went wrong and didn't install the update. I have the bootloader unlocked and Magisk installed. I followed the instructions for Magisk dual partition updates. I uninstalled Magisk using Restore Images and did not reboot. I went to System Updates and downloaded the update again. It never went to Security Update Installing, step 1. I am on Magisk v 16.0 which passes the SafetyNet check, ctsProfile: true and basicIntegity: true. At this point, should I completely uninstall Magisk, flash the OreoFlashAll.zip or the NASH_TMO_C_OCX27.109-36_subsidy-TMO-regulatory-DEFAULT_CFC.xml.zip? Or something different?
lcc014 said:
Got AT&T update to 8.0.0 this morning.
Click to expand...
Click to collapse
Let us know if you lose the animated home button as I did after the At&t update. I asked the question in the room and no one answered. Hopefully I didn't break any rules by asking here. Thank you.
Sent from my Moto Z (2) using Tapatalk
Guys, I'm reading mixed articles and opinions online and I'm returning to Android after a long time with iOS. The only incentive for me here would OTA updates the day of release. I'm thinking of getting the phone from Verizon and wondering if their updates arrive the same day as Google releasing them, or is there a delay?
Kind regards
Prasad
You will always have a little delay before yout get the OTA, because they are released by stages. I always download the OTA image from google and sideload it via stock recovery. Its the fastest way and you don't need an open bootloader or something.
hells
The way I get the OTA updates, is, I pop out my Sim, clear data from Google play store and Google play services, and then reboot. When I check for an update it will say up to date, but when I put my SIM back in and check again about 30 seconds later the update is already installing.
Only downfall to this method is you have to set up android pay again.
Otherwise you can download the OTA from googles website but it's a pain to do, and it's a big download.
The check for updates issue has been fixed in Google Play Services v12.2.09 or later which is still in beta but I believe a stable version will be released in March. I checked within 1 hour after the March security update was released and had the update available for download. I am running the beta GPS currently.
There is no delay. The pixel series receives their updates directly from Google and can update the day google releases.