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.
Related
Updated to the Dec 5th security patch on Verizon and using signal refresher and then turning on the Hotspot no longer works, looks like Verizon patched it. If anyone has any ideas, let me know. Now I am wishing I rooted. Do not take the update if you are on Verizon with unlimited data and plan on using the Hotspot.
How did you install it? I can't find the ota file anywhere
EDIT: forgot I was in the pixel forum.
Yup, this sucks. I was hoping to enjoy my phone without rooting but I guess when 7.1.1 gets root I'll be going to the dark side.
Is SuperSU root broken on 7.1.1?
root works just fine on 7.1.1 i have native tethering working by doing the build prop text editor....
Same.
well..thats how i got it to work period.
unlimited verizon user here.
still on 7.1 though...unlocked bootloader and rooted.
I came to see about factory resetting then trying to update as i am unable to update as is now...
I wish I would have unlocked my bootloader before updating, should have waited to update. Hopefully there will be a solution in the future.
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.
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
aaronpw0621 said:
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
Click to expand...
Click to collapse
I got the same problem as well. I'm on Verizon and haven't found a fix.
I've got a Google Play Pixel XL on Verizon, no problem with update. Full stock locked bootloader.
Sent from my BTV-W09 using Tapatalk
I don't understand how you got the OTA so quick. Even with Google saying last month that doing a check for update manually should now get you OTAs instantly, it's not working on my stock bootloader unlocked XL.
Same here.. got the OTA October Android 8.0 Oreo Security Patch without a hiccup... I also have a locked bootloader as well on Verizon Pixel XL version. Really wish these bootloaders could be unlocked but that's another topic that has been saturated to death... lol.
Damn that sucks for you guys that aren't getting it instantly. Checking for update seems to work for me. But try clearing your Google play services app and then see if it will let you download the update you guys.
alobear said:
Damn that sucks for you guys that aren't getting it instantly. Checking for update seems to work for me. But try clearing your Google play services app and then see if it will let you download the update you guys.
Click to expand...
Click to collapse
No need, hes going to brake GPServices and get bunch of force closes.
The check for updates now works on demand when you press it. This has already been confirmed by bunch of folks, and even myself when i did on my wife's phone.
aaronpw0621 said:
So I am having the issue posted in my pics. I am not part of beta. I am Verizon on September patch. Never touched my sim since I got device. Bootloader is unlocked but that shouldn't matter. Anyway if someone can help me figure out according to the screenshots why I can't update it would be greatly appreciated.
Click to expand...
Click to collapse
I just did the manual way of flashing the ota. All good now.
lucky_strike33 said:
I just did the manual way of flashing the ota. All good now.
Click to expand...
Click to collapse
Wish I could. I am out of town working till the weekend.
Google Pixel XL unlocked bootloader and update failing to install. Showing me update size of 50.6 MB.
Will try and patch manually.
I have a Verizon Pixel XL on T-Mobile and i got the October 5th patch yesterday without issue. It took a while for only 64.5mb, but it took it. I did have 1 random reboot this morning though.... BTW, like i said, i took the update with a TMO SIM and still have gray OEM Unlocking
I had the same error. I disabled Block This! and it installed without problems.
Sent from my Pixel XL using Tapatalk
Still waiting for my OTA Oct 5 update. I am complete stock, locked bootloader (never unlocked or rooted). Damn Check for update button not working for me.
So I tried flashing the September patch to both slots manually and taking the OTA but it failed still. So I went ahead and manually flashed the October patch.
I am wondering if it has to do with me upping to Unlimited Data plan on Verizon.
I just checked for an OTA update manually and nothing showed up. I'm still on September patch. Google edition, locked bootloader and not rooted.
westside80 said:
I just checked for an OTA update manually and nothing showed up. I'm still on September patch. Google edition, locked bootloader and not rooted.
Click to expand...
Click to collapse
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
lucky_strike33 said:
I just did the manual way of flashing the ota. All good now.
Click to expand...
Click to collapse
Hi, can you please share the steps to manual flashing the update i am on stock, rooted SU, september. Thank you.
veskostoev said:
Hi, can you please share the steps to manual flashing the update i am on stock, rooted SU, september. Thank you.
Click to expand...
Click to collapse
Go to Google ota and download October. You can flash the ota through twrp. Flash as you would a rom. That's it.
aaronpw0621 said:
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
Click to expand...
Click to collapse
I bought the phone off eBay so I'm not sure if it was enrolled but I doubt it was. I guess I could check to make sure.
---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------
aaronpw0621 said:
We're you part of the Beta Program? If so that can be a reason why. You will have to unenroll your device
Click to expand...
Click to collapse
It was enrolled in the beta program. I just checked. I unenrolled it but since I'm already on the stable build it didn't send me an OTA so I won't have to wipe the phone. I'll go check for an update again and see what happens now that I unenrolled the phone.
westside80 said:
I bought the phone off eBay so I'm not sure if it was enrolled but I doubt it was. I guess I could check to make sure.
---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------
It was enrolled in the beta program. I just checked. I unenrolled it but since I'm already on the stable build it didn't send me an OTA so I won't have to wipe the phone. I'll go check for an update again and see what happens now that I unenrolled the phone.
Click to expand...
Click to collapse
I didn't think about the beta program - that would sort of make since as to the cause of not getting latest October OTA. Please let us know if you get it now when you do a manual check for update.
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
Hi, I have pixel xl on tmo and I'm still on August security patch.
For some reason my phone isn't getting the update..
Anyone else is having the same issue?
levyitay said:
Hi, I have pixel xl on tmo and I'm still on August security patch.
For some reason my phone isn't getting the update..
Anyone else is having the same issue?
Click to expand...
Click to collapse
Are you rooted?
Phalanx7621 said:
Are you rooted?
Click to expand...
Click to collapse
nope
Were you in the beta program? Try opting out. Ironically, I had to opt out and back in to get my update. I'm on Fi though...
Of course there's the easy way too, just unlock the bootloader and flash with fastboot. You can also, if you don't want to unlock the bootloader, side load the OTA via stock recovery.
Same issue here. I'm dead stock and opted out of the Beta program and can't pull down the September OTA. I guess I'll have to sideload it :/
No Update yet..
I also have got the same issue. On Stock ROM with no Root privileges, No OTA update yet..
levyitay said:
Hi, I have pixel xl on tmo and I'm still on August security patch.
For some reason my phone isn't getting the update..
Anyone else is having the same issue?
Click to expand...
Click to collapse
I am having the same issue. I even did a full reset a few weeks ago. After the P update, I could barely use my phone, it would take forever to get anything to work. Finally sideloaded yesterday with no issues.