So it looks like new Nexus phones are not supported yet, and its also reported that you look band 12 with M and Project Fi. So does it work on Tmo?
Yes. I'm on T-Mo with a stock N6 running Android 6.0 and LTE discovery (app) is showing lte band 12 right now.
Android M doesn't support any bands. It's hardware.
danarama said:
Android M doesn't support any bands. It's hardware.
Click to expand...
Click to collapse
Dan, are you saying we don't need to wait for the update that T-Mobile says it will have ready for us later this week?
http://www.tmonews.com/2015/10/t-mobile-to-begin-pushing-nexus-6-android-6-0-update-this-week/
JimSmith94 said:
Dan, are you saying we don't need to wait for the update that T-Mobile says it will have ready for us later this week?
http://www.tmonews.com/2015/10/t-mobile-to-begin-pushing-nexus-6-android-6-0-update-this-week/
Click to expand...
Click to collapse
The problem with an OTA is that it can only update a specific build. The normal OTA everyone else will get will not be able to update a t-mobile rom, so t-mobile will have to release their own.
Bands themselves for LTE are hardware in the SoC.
As for WiFi calling, that's built into Marshmallow..my understanding is you just need the "my tmo" app from play or something.
But yes, if you want to receive an OTA then you'll have to wait, but you should also be able to flash the system.img and boot.img
danarama said:
The problem with an OTA is that it can only update a specific build. The normal OTA everyone else will get will not be able to update a t-mobile rom, so t-mobile will have to release their own.
Bands themselves for LTE are hardware in the SoC.
As for WiFi calling, that's built into Marshmallow..my understanding is you just need the "my tmo" app from play or something.
But yes, if you want to receive an OTA then you'll have to wait, but you should also be able to flash the system.img and boot.img
Click to expand...
Click to collapse
Thank you sir! I'm rooted, so I plan to update manually with fastboot anyway. I'm seeing conflicting reports from others that have manually updated about WiFi calling working or not, and band 12 being available or not. Guess I'll wait another day or two and see how it shakes out.
I am a stock non rooted T-mobile user and i upgraded to Marshmallow using the standard image that google posted. everything works, LTE and wifi calling included. I have had no issues so far.
I'm running stock factory 6.0 rooted with twrp and T-Mobile WiFi calling works perfect. Thanks marshmallow
Sent from my Nexus 6 using Tapatalk
.A.J. said:
Yes. I'm on T-Mo with a stock N6 running Android 6.0 and LTE discovery (app) is showing lte band 12 right now.
Click to expand...
Click to collapse
Thanks. Are u on latest build? Fi users reporting that M killed band 12 for them on N6
Band12 data support is removed for Fi users in the M radio because Fi will not support T-Mobile's proprietary VoLTE. So, no band12 data with the Fi SIM installed.
If you run M on your N6 with a T-mobile SIM in, you do get band12 ?
Sent from my VS985 4G using Tapatalk
Related
So I currently have an att sims card in my device. And I'm noticing a ' T-Mobile update service Update postoned' message. Is it safe to take the update even though I'm using att with this device?
anyone's input how this may affect an at&t user appreciated.
SysAdmNj said:
anyone's input how this may affect an at&t user appreciated.
Click to expand...
Click to collapse
I don't think it should be any problem to update the phone with the att SIM on... at least in theory. I unlocked my T-Mobile Note 4 and it's working flawlessly on att at full LTE speeds, minus Wi-Fi calling and VoLTE of course, but I don't really care for those features on AT&T.
bartolo5 said:
I don't think it should be any problem to update the phone with the att SIM on... at least in theory. I unlocked my T-Mobile Note 4 and it's working flawlessly on att at full LTE speeds, minus Wi-Fi calling and VoLTE of course, but I don't really care for those features on AT&T.
Click to expand...
Click to collapse
I'm going to root/custom recovery later anyways so I'd probably over write it with a custom rom. Probably doesnt pay to update.
SysAdmNj said:
I'm going to root/custom recovery later anyways so I'd probably over write it with a custom rom. Probably doesnt pay to update.
Click to expand...
Click to collapse
It will update your baseband (modem) and a few other things that are inaccessible to the user, so yes, update it. In fact, the update does update the modem to version NJ7 (you're probably on NIH).
siraltus said:
It will update your baseband (modem) and a few other things that are inaccessible to the user, so yes, update it. In fact, the update does update the modem to version NJ7 (you're probably on NIH).
Click to expand...
Click to collapse
I am on N910TUVU1ANIH, So updating the baseband is needed to be compatible with custom roms? I'm just worried about bonking my signal since its not a tmobile sims.
SysAdmNj said:
I am on N910TUVU1ANIH, So updating the baseband is needed to be compatible with custom roms? I'm just worried about bonking my signal since its not a tmobile sims.
Click to expand...
Click to collapse
I unlocked, upgraded to ANJ7 from that version, did this: http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
then this:
http://forum.xda-developers.com/not...v1-4-4-4-tw-anj7-extremely-t2916463?nocache=1
with no problems using the t mobile one with an att sim, have been connected to 4G LTE all day.
SysAdmNj said:
I am on N910TUVU1ANIH, So updating the baseband is needed to be compatible with custom roms? I'm just worried about bonking my signal since its not a tmobile sims.
Click to expand...
Click to collapse
I'm on the latest update with latest modem and I have absolutely great reception on at&t with my T-Mobile Note 4. Better than my Nexus 5 for sure.
Not sure if I'm actually supposed to update to 5.1.1 given I'm bootloader unlocked and i'm pretty sure OTA's don't work with unlocked bootloader, any advice?
It'll update just fine with a unlocked boot loader. If you are rooted tit won't take.
Sent from my Nexus 9 using Tapatalk
But surely the UK doesn't have a 5.1.1 ROM given they're for the US Only?
wright_ac said:
But surely the UK doesn't have a 5.1.1 ROM given they're for the US Only?
Click to expand...
Click to collapse
At some point, they were bound to start pushing a more "general" update. Could be that you're getting it.
wright_ac said:
But surely the UK doesn't have a 5.1.1 ROM given they're for the US Only?
Click to expand...
Click to collapse
I got the 5.1.1 OTA in the UK last week and it works fine. It's LMY47Z, same as the factory image that says Sprint, USC only
wright_ac said:
But surely the UK doesn't have a 5.1.1 ROM given they're for the US Only?
Click to expand...
Click to collapse
They're not US only. Its just they're the only US carriers that can use that particular update...its the generic update. Other US carriers (namely TMO and Verizon) have their own specific updates. That's why the generic update can only be used by the other US carriers.
Received an update notification for my n6 in Canada. Being rooted and running a noon encrypted kernel had to skip the OTA. Fastboot the sprint/USC factory image last week and haven't had an issue.
mymusicathome said:
Received an update notification for my n6 in Canada. Being rooted and running a noon encrypted kernel had to skip the OTA. Fastboot the sprint/USC factory image last week and haven't had an issue.
Click to expand...
Click to collapse
All nexus 6 ROMs will work on all nexus 6 without issue. Just Verizon and TMO users will lose features, hence that Z build saying USC / Sprint only. Actually its not USC / sprint only. Its USC / Sprint only in the US, and everyone everywhere else in the world
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
kmandel said:
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
Click to expand...
Click to collapse
I have run all the MRA builds (K, N, R) on T-Mobile and they all support and have fully functioning WiFi calling, Band 12 support, and VoLTE. Not sure what's specific about X but I decided to switch to it just because it's "official".
Sent from my Nexus 6 using Tapatalk
nnorton44 said:
I have run all the MRA builds (K, N, R) on T-Mobile and they all support and have fully functioning WiFi calling, Band 12 support, and VoLTE. Not sure what's specific about X but I decided to switch to it just because it's "official".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
How did you switch? Did you flash a 5.1.1 factory image and then take the OTA?
kmandel said:
How did you switch? Did you flash a 5.1.1 factory image and then take the OTA?
Click to expand...
Click to collapse
For X I flashed the factory ProFi 5.1.1 then sideloaded the 48I to 58X OTA.
T-Mobile and ProFi will both use X.
Sent from my Nexus 6 using Tapatalk
I hope there's a factory release. Please post here if anyone gets it
kmandel said:
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
Click to expand...
Click to collapse
Someone posted about this on the Android Central comments section: http://www.androidpolice.com/2015/1...etting-an-over-the-air-update-to-marshmallow/
Looks like if you are on K you will get the X updated OTA
blazinazn said:
Someone posted about this on the Android Central comments section: http://www.androidpolice.com/2015/1...etting-an-over-the-air-update-to-marshmallow/
Looks like if you are on K you will get the X updated OTA
Click to expand...
Click to collapse
According to the T-mobile document
https://support.t-mobile.com/docs/DOC-18109
It's only the L* releases that can be updated with the OTA.
kmandel said:
According to the T-mobile document
https://support.t-mobile.com/docs/DOC-18109
It's only the L* releases that can be updated with the OTA.
Click to expand...
Click to collapse
I don't see where it says *only* L releases get the update but it may just be a matter of semantics.
"To be able to update to the current software version, the below requirements must be met:"
^^^ I take this to mean that you must have at least L to get the update. If you are on M already then you still meet that requirement. That's just my thoughts though. Dez is always in the know and that's what he said. Guess we'll just have to wait and see.
i am completely unable to install mra58x no matter how i try to sideload the update from 5.1.1
Tmobile goes back to MRA58K
It confused me.
https://i.imgur.com/vQYNKiL.jpg
I got the ota today, from 28m
Sent from my Nexus 6 using XDA Free mobile app
joshtb86 said:
i am completely unable to install mra58x no matter how i try to sideload the update from 5.1.1
Click to expand...
Click to collapse
I noticed that your signature says "Nexus 6 rooted". If that is in fact the case, you will not be able to install any OTA. Neither via sideloading nor "over the air". The installer looks at the system file, and if there is ANY change from stock (including being rooted), it will abort the install. I've had it fail, even with a couple of apps frozen.
It looks like the document
https://support.t-mobile.com/docs/DOC-18109
has been updated. It now list MRA68K as eligible for the OTA to MRA68X. Earlier
it just listed the L* releases.
cam30era said:
I noticed that your signature says "Nexus 6 rooted". If that is in fact the case, you will not be able to install any OTA. Neither via sideloading nor "over the air". The installer looks at the system file, and if there is ANY change from stock (including being rooted), it will abort the install. I've had it fail, even with a couple of apps frozen.
Click to expand...
Click to collapse
yeah tried on a clean flash without root, still not luck
i installed mra58k clean rom from the andriod dev page until someone makes an X rom
Wow
And for those with MRA58N currently, there was a hint that TMO would OTA push MRA58X as well.
I am starting to think that was Des speaking before he had the details
Sent from my Nexus 6 using Tapatalk
Dougshell said:
I am starting to think that was Des speaking before he had the details
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Check their support web site
Sent from my Nexus 6 using Tapatalk
I see they added it. Well again, sitting here with a nexus device, waiting.
Sent from my Nexus 6 using Tapatalk
BigDig said:
Check their support web site
Click to expand...
Click to collapse
TMO's update site is questionable in and of itself.
I've been loving my R1 HD since I bought it this summer. I followed the tutorials here to unlock and root and remove Amazon ads. It worked like a charm, and the phone has been running great. I've been using Freedompop in SIM1 and H2O in SIM2. Because of AT&T's 2G migration, I had to switch my SIM2 service to T-Mobile. My questions for the experts here:
* Should I restore to OEM system, so I can receive the latest OTA update? The Band 12 support didn't matter to me when I was on H2O, but now, I want it, right?
* If I do go ahead to convert back to stock, is this the thread to follow? https://forum.xda-developers.com/showthread.php?t=3432499 I'm on V6.5 right now (dated 2016/07/29). Or is there a quicker and easier way to restore the phone to its original state now that I've unlocked and rooted?
* If I go back to stock following those directions, can I choose the "non-Prime" version and still get the latest OTA update? Or do I need to go back to the Prime version (which is how I bought it)?
Any and all advice will be greatly appreciated by this n00b. I appeal to the fellowship of R1 users for your wisdom. Thanks.
Do NOT take the OTA! It not only restores the ads but disables the use of SP Flash Tools You want to install the modified versions of the rom. This is probably the thread that you want: https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
Both the prime and non-prime versions have exactly the same updates - the only difference is the amazon apps installed.
A couple of people have asked, but so far I have not seen any confirmed reports here of VoLTE working on t-mobile with the updated rom. Reports of it either working or not working would be appreciated. Has t-mobile certified Blu's VoLTE implementation and enabled VoLTE for this model phone yet?
Thanks! So will flashing that ROM give me Band 12 support? (VoLTE isn't as much of a concern for me.) Much appreciated.
There have been reports here of band 12 working after the update, but not of VoLTE on t-mobile. Make sure that you back up anything you need on the phone before you start messing with it.
T-Mobile Unofficially Speaks To Us About Band 12 LTE / VoLTE And Unlocked Smartphones, And Yep It's Still Confusing
Understanding LTE band 12
Hey, I have successfully flashed a Sprint LG V40 v405ua to US firmware 20g but VoLTE is not working. I am on Tmobile network and every time I make a phone call it switches from LTE to H. I heard Tmobile will be moving all phone calls to VoLTE in the middle of 2022. How can I enable VoLTE? Am I missing something? Thanks!
megadrive007 said:
Hey, I have successfully flashed a Sprint LG V40 v405ua to US firmware 20g but VoLTE is not working. I am on Tmobile network and every time I make a phone call it switches from LTE to H. I heard Tmobile will be moving all phone calls to VoLTE in the middle of 2022. How can I enable VoLTE? Am I missing something? Thanks!
Click to expand...
Click to collapse
if you have access to the OP section, try to change it in cust.prop ro.vendor.lge.build.target_operator = OPEN to TMO
megadrive007 said:
Hey, I have successfully flashed a Sprint LG V40 v405ua to US firmware 20g but VoLTE is not working. I am on Tmobile network and every time I make a phone call it switches from LTE to H. I heard Tmobile will be moving all phone calls to VoLTE in the middle of 2022. How can I enable VoLTE? Am I missing something? Thanks!
Click to expand...
Click to collapse
I'd suggest looking at the apn settings. That should be working (volte) without any system modifications.
I checked the APN settings and they are all correct. I am using US firmware version 20g, should I try using an earlier one like 20f? What versions are wokring for you? thanks
megadrive007 said:
I checked the APN settings and they are all correct. I am using US firmware version 20g, should I try using an earlier one like 20f? What versions are wokring for you? thanks
Click to expand...
Click to collapse
I don't have a v40 anymore but remember any version I tried of us open cross flashed to my at&t would work no problem. I remember my carrier mint mobile required you to select 'vowifi' in the account to get that to work. But volte always worked.
you might want to consider joining the v40 tele grp see if they can further assist. Maybe also consider calling t-mo, re your account may not be provisioned for volte? Not sure that's even possible but why not check anyway?
If it is like AT&T does whitelisting, ROM does not matter, but IMEI.