Confused on the 6.0 and up, updates....

[zrxoa1]

Ok, my phone was originally purchased from Google. The first SIM that was installed was from T Mobile. The phone then had the T Mobile build of 5.1.

Then I bought the phone and installed my ATT SIM. Then came Marshmallow. I read on here about my phone having to wait for T Mobile to send out update, even though I am on ATT. So I side loaded 6.0

My build is MRA58K. I have not gotten any patches since October. My Nexus 7 has all the updates. I busted out my old, defective Nexus 5 (won't turn on most of the time) which was actually the first phone in the house to get 6.0 ota. It actually turned on and began updating and ended with the January security patch. But now won't turn on again. LOL

So....what is the deal with my Nexus 6? Why am I not getting the security patches?

Posted via the Android Central App

 

[jj14x]

Nobody seems to know... these carrier variants have been a pain in the rear. I got frustrated with this a long time ago, and just started flashing the factory images whenever they came out (instead of waiting for an elusive OTA). - I just keep my bootloader unlocked.

 

[kct1975]

Ok, my phone was originally purchased from Google. The first SIM that was installed was from T Mobile. The phone then had the T Mobile build of 5.1.

Then I bought the phone and installed my ATT SIM. Then came Marshmallow. I read on here about my phone having to wait for T Mobile to send out update, even though I am on ATT. So I side loaded 6.0

My build is MRA58K. I have not gotten any patches since October. My Nexus 7 has all the updates. I busted out my old, defective Nexus 5 (won't turn on most of the time) which was actually the first phone in the house to get 6.0 ota. It actually turned on and began updating and ended with the January security patch. But now won't turn on again. LOL

So....what is the deal with my Nexus 6? Why am I not getting the security patches?

Posted via the Android Central App

From what I have read, the simple answer is that you flashed the 6.0 instead of waiting for either the Tmo OTA or the AT&T OTA. So from what I understand, you won't be receiving any more OTA updates.

I'd suggest doing what the previous poster suggested, and keep flashing updates yourself.

 

[jj14x]

Well, that may not be entirely true. Flashing a factory image (or sideloading the update) doesn't prevent an OTA - I'm sure because I've seen the OTA prompt show up on my phone when I didn't flash one of the monthly updates right away.

Thinking more about the question in the first post, I suspect the issue is that there may not be an update from MRA58K to the newer releases when on an ATT SIM. If memory serves me right, MRA58K was a T-Mo build. So, with an ATT SIM, there may not be an update for MRA58K.

It sounds like AT&T released MMB29K (Dec security patch level) last week. So, if you want to get back on the AT&T track, you can download and flash that (I don't think there is an OTA file to sideload unfortunately). Flashing factory images does require an unlocked bootloader, so if you don't already have that, your data will be wiped when you do that.

If you do flash MMB29K to be back on track for AT&T OTAs, be aware that you may not get the latest update right away - AT&T has not yet released the Jan security patch. But whenever ATT does release the next update, it will likely be an OTA from MMB29K to the new version, so it should work just fine.

Personally, I just flash the latest factory images (no data wipe) everytime - doesn't take more than 5 minutes or so. That way, I don't have to wait/hope for OTA

 

[zrxoa1]

When I side loaded that build, it was the same build for all carriers.

 

[IAmSixNine]

Check out the different builds and this should help you understand the differences.
https://developers.google.com/android/nexus/images?hl=en
While you may be right about the builds for 6.0 going forward are no longer split into carrier versions its possible that your ATT sim is holding updates back. Why who knows. I have TMO in mine and i have gotten the updates. Even on WiFi i got the updates. Kinda like my Note 4 better recently.

 

[BartmanJax]

Nobody seems to know... these carrier variants have been a pain in the rear. I got frustrated with this a long time ago, and just started flashing the factory images whenever they came out (instead of waiting for an elusive OTA). - I just keep my bootloader unlocked.

Same here.

 

[zrxoa1]

Quick question.. I stuck my deactivated Fi sim card in. It immediately is downloading the update to 6.0.1. Should I let that install??

 

[zrxoa1]

Oops, I grazed the install link so it is installing. Guess we'll see what happens! Haha

 

[zrxoa1]

Well, that seems to have worked. First I was updated to 6.0.1 then the January patch and now I set on build MMB29S.

Now I have the ATT sim back in and all is fine.

Suppose I'm back on track for the monthly OTA updates?

Posted via the Android Central App

 

[IAmSixNine]

Well, that seems to have worked. First I was updated to 6.0.1 then the January patch and now I set on build MMB29S.

Now I have the ATT sim back in and all is fine.

Suppose I'm back on track for the monthly OTA updates?

Posted via the Android Central App

Let us know when the next batch of updates come out.
If they do then that one you were on didnt like the ATT sim card. If they dont then it is ATT sim card holding them back.
Looking forward to seeing if you do get the next update in time like the rest of us have been.

 

[JW0914]

Well, that may not be entirely true. Flashing a factory image (or sideloading the update) doesn't prevent an OTA - I'm sure because I've seen the OTA prompt show up on my phone when I didn't flash one of the monthly updates right away.

Personally, I just flash the latest factory images (no data wipe) everytime - doesn't take more than 5 minutes or so. That way, I don't have to wait/hope for OTA

Could the OTAs being received after flashing factory images directly from Google be an OTA that was pushed out by Google and not by the carrier?

 

[jj14x]

Could the OTAs being received after flashing factory images directly from Google be an OTA that was pushed out by Google and not by the carrier?

OTAs are always pushed out by Google - some of them seem to require carrier approval, some don't. The OTA you receive seems to depend on the SIM that you have on your phone, and the build that your phone currently has. So, if you flash a T-Mo factory image, and put in a T-Mo SIM, you'd get the next T-Mo build whenever it is released.

(Note that now, the Nexus 6 supposedly has a unified build - so all N6 devices can get all builds - at least in theory. I suspect that the carriers will still have their say in which build is pushed out to devices with their SIMs)

 

[tonyr6]

Nobody seems to know... these carrier variants have been a pain in the rear. I got frustrated with this a long time ago, and just started flashing the factory images whenever they came out (instead of waiting for an elusive OTA). - I just keep my bootloader unlocked.

Same here. I flash all updates day 1 when they come out.