What version of 6.0 were you running? The latest release is the 'R' version, which includes the November update. I just flashed the full image to update to that, and haven't had any subsequent downloads, but would be pretty ticked if I suddenly had T-Mo issue a downgrade December patch...
Will T-Mobile Nexus 6 ever get 6.0?
- Thread starter Dylan Gorski
- Start date
What version of 6.0 were you running? The latest release is the 'R' version, which includes the November update. I just flashed the full image to update to that, and haven't had any subsequent downloads, but would be pretty ticked if I suddenly had T-Mo issue a downgrade December patch...
ElronTheElder
Well-known member
- Jan 7, 2015
- 419
- 0
- 0
Just got the Nov Marshmallow OTA security patch MRA58N.
On Fi running sideloaded 6.0.
I'm happy on a couple of levels.
On Fi running sideloaded 6.0.
I'm happy on a couple of levels.
Will t-mobile ever get Android 6.0? Well, maybe, but I'm guessing it won't be anytime soon. Why? We'll I just checked out the t-mobile store and they no longer seem to be selling the Nexus 6. So, if you don't sell it, why bother updating it? Sideloading would seem to be the only viable option. Let's hope Google puts out an OTA for Android 6 from LYZ28N. They eventually did for LYZ28M....
I could easily see Google thinking it would be a waste of effort developing further updates to provide the best possible experience for users with devices on T-Mobile until such time as T-Mobile cares enough about its own customers to actually allow the OTA to pass through. I went ahead and flashed the image (took about 20 minutes), which given the amount of data Google now backs up meant there was very little inconvenience as far as reconfiguration (mostly just logging back in to some apps).
I don't think even Legere is quite that cold blooded. TMo's well aware that they have a good number of chumps like me still paying N6s off on the JUMP program. Sure, not enough to make 'em put in a lot of overtime, but enough to make simply walking away from the N6 impractical.
And if you consider how long it took TMo to get WiFi Calling operational on the N6 in the first place--about a good 6 months--that kind of puts the delay in OTAing 6.0 into perspective. There's got to be something effed up about the N6 radio software/firmware on the one hand and TMo's own technology on the other that's got their people banging heads on desks.
I don't like it, but I can force myself to understand it. Still, it would be nice if someone at least took a shot at releasing an official explanation.
I too can understand it but the question is well the tmo ota take 6 months just like WiFi calling?
And if it does what does that mean for the 7.0 ota we've been promised by Google and the 8.0 that we might hopefully get?
Can't imagine that second or third ota OS update will be any faster than this one, probably slower.
And if it does what does that mean for the 7.0 ota we've been promised by Google and the 8.0 that we might hopefully get?
Can't imagine that second or third ota OS update will be any faster than this one, probably slower.
Are you familiar with adb? Just flash the latest 6.0 on it and then you'll get all that WiFi and visual voicemail built into the dialer. If you don't know how to do that then I suggest you take the phone back and tell them you don't use fi and why they have you that or they need to give you a brand new one.
Posted via the Android Central App
It's only been a couple weeks to maybe a month. It won't be too long. If you want they update already either flash the image, sideload the ota zip or try to take the SIM out, hard reset, connect to WiFi and then check for update without the t-mobile SIM card in the phone.
Posted via the Android Central App
That is not possible. When you say installed, do you mean receive the ota update or did you flash an image?
Posted via the Android Central App
I see many comments from people saying that Google shouldn't allow t-mobile to tinker with the os and add their stuff. Please understand that t-mobile doesn't do anything to the os. They add specific network tweaks based on the SIM card, like Wi-Fi calling.
Also, ever since marshmallow all builds are the same and t-mobile doesn't do anything. The phone recognizes the t-mobile SIM card, and then activates specific features that are built into the new os like Wi-Fi calling and visual voicemail from the dialer.
I do agree that t-mobile shouldn't hold an update from coming to a phone but the update still comes from Google servers.
If you remove your t-mobile SIM card from your phone and reset it, the phone will most likely update, then you are good to go. Remember that this is the first Android build that has all these features come native so t-mobile wants to make sure it works correctly, although they are taking too long to test it.
Posted via the Android Central App
Also, ever since marshmallow all builds are the same and t-mobile doesn't do anything. The phone recognizes the t-mobile SIM card, and then activates specific features that are built into the new os like Wi-Fi calling and visual voicemail from the dialer.
I do agree that t-mobile shouldn't hold an update from coming to a phone but the update still comes from Google servers.
If you remove your t-mobile SIM card from your phone and reset it, the phone will most likely update, then you are good to go. Remember that this is the first Android build that has all these features come native so t-mobile wants to make sure it works correctly, although they are taking too long to test it.
Posted via the Android Central App
ItsMeMandi
Well-known member
- Aug 19, 2010
- 226
- 3
- 0
They still haven't done OTA for Project Fi which is as "pure google" as you can get. There have been issues per a statement posted on the official Project Fi (closed) forum:
You don't have to wait for ota if you don't want to. The latest build for nexus 6 works for all of them. It's 1 build for all.
Posted via the Android Central App
That's about as generic a statement as anyone's ever produced, but at least it's some sort of acknowledgment, of frustration if nothing else.
Adding stuff is fine, especially if it adds real value (such as compatibility with T-mo's proprietary VOIP). From my perspective, the issue is created when a build is deployed to lean it towards one carrier in such a way that it can't be easily restored to a non-carrier-oriented, pure Google build, by a FDR (FDR doesn't roll back the OS build, so if you're on a carrier build before, you're still on it after). While flashing a boot image isn't terribly difficult if one has a moderate technical aptitude and ability to follow instructions, many people would have difficulty with the process.
That i understand. You shouldn't have to flash another build to get it to work properly. That is why with marshmallow only 1 build is needed whether you are on tmobile, att or verizon.
Chuckl
Well-known member
- Dec 3, 2010
- 75
- 6
- 0
I was mistaken, I swore I got the OTA shortly after T-mobile announced it's availability in Oct.
ItsMeMandi
Well-known member
- Aug 19, 2010
- 226
- 3
- 0
I'm aware. And plenty of Fi users have sideloaded 6.0, but if there are issues I'd rather wait.
Could it be because its a Motorola made phone? After all Moto stabbed its fans in the back regarding updates and it makes no sense for a Google Fi unlocked Nexus 6 to not get OTA unless somehow Tmo is also blocking that since it will be on their network.
Day 42 (6 weeks) since Google started 6.0 OTA rollout. My T-Mobile Nexus 6 has yet to get the update.
Day 42 (6 weeks) since Google started 6.0 OTA rollout. My T-Mobile Nexus 6 has yet to get the update.
Similar threads
- Question
Facebook
Twitter
Instagram