Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005
RockStar2005 said:
Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005
Click to expand...
Click to collapse
Non carrier get updates faster (wwe) and carrier specific tend to need to wait sometime for the lastest update. Correct me if I'm wrong haha. But carrier specific usually comes with bloatware .
Sent from my HTC ONE M8 HK
Steven How said:
Non carrier get updates faster (wwe) and carrier specific tend to need to wait sometime for the lastest update. Correct me if I'm wrong haha. But carrier specific usually comes with bloatware .
Sent from my HTC ONE M8 HK
Click to expand...
Click to collapse
That's correct. In case of the TMOB M8 (as I got this) the EPSM was missing even after the OTA to 1.70.111.x. so I decided to change CID/MID to WWE and reverted my M8 to the WWE variant using a stock backup as well as the FW of 2.22.401.4. Now all is fine and lately I even received the OTA "2.22.401.4 > 2.22.401.5" containing a GPS fix.
Sent from my HTC One_M8 using XDA Free mobile app
RockStar2005 said:
Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005
Click to expand...
Click to collapse
If you are talking about Firmware as in files in firmware.zip
ie
hboot
radio.img
modem_st1.img
rcdata.img
rconfig.img
rpm.img
etc......
then
radio is different for every major carrier which enables or disables specific radio bands.
true for US region.
Steven How said:
Non carrier get updates faster (wwe) and carrier specific tend to need to wait sometime for the lastest update. Correct me if I'm wrong haha. But carrier specific usually comes with bloatware .
Sent from my HTC ONE M8 HK
Click to expand...
Click to collapse
I see.
Well I know the phones come with bloatware vs unlocked/international ones......... but the firmware comes with it too? lol
RockStar2005
HTCNerdYoda said:
That's correct. In case of the TMOB M8 (as I got this) the EPSM was missing even after the OTA to 1.70.111.x. so I decided to change CID/MID to WWE and reverted my M8 to the WWE variant using a stock backup as well as the FW of 2.22.401.4. Now all is fine and lately I even received the OTA "2.22.401.4 > 2.22.401.5" containing a GPS fix.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Hello again HTC,
What's EPSM? And WWE?
Wow really?? The T-Mobile OTA was actually missing stuff the non-carrier one wasn't?? That's crazy. And here I was asking this cuz I was worried that by downloading the non-carrier variant of the firmware that I was perhaps missing things my phone would need to work at optimal level. Sounds like it's actually the opposite! lol I use the ViperOne M8 rom by Team Venom and they're VERY good about including all the important M8 updates for my phone (and some nice extras, like letting notif light still blink while charging for new msgs, turning off annoying high volume warning, etc), and they seem to have them out before T-Mobile does (see below). Yeah the newest firmware I got (not from Venon, but from here: http://www.renovate-themes.de/index.php?s=firmware) was necessary for Venom's OTA to work, but I did notice that when I finally got Venom's OTA that it mentioned a GPS fix too, so they got that in there as well.
I just wish T-Mobile would hurry up and get VoLTE activated for the M8. I know it's capable of VoLTE, but an OTA will be needed to activate it. Once it's activated, and ur in a VoLTE-activated area/city, the calls won't revert back to 4G but instead will stay at 4G LTE, and will be better quality and less likely to drop.
ViperOne prob beat T-Mo by 2 days on that GPS fix, but in reality, from what u said, I dunno if T-Mo's even has it yet or not(?) as it's not mentioned in their super vague description:
ViperOneM8 2.2.0 (August 19)
ADDED full T-Mobile carrier support
FIXED T-Mobile WIFI calling
FIXED Locked IPV4/6 Settings
FIXED AOSP incoming call workaround not working
ViperOneM8 2.1.0 (August 16)
Merged with HTC OTA 2.22.401.5
Added new stock kernel from OTA (Only full ROM)
GPS improvements and fixes from HTC
Workaround white gap in dialer when having custom stock navbar size
Fixed Notification icon color
Added longpress power custom actions
vs. T-Mobile:
Beginning August 18, the HTC One (M8) received a software update 2.22.531.5 (or firmware 2.22.401.4 or .5?).
Software version
Android version 4.4.3/ Software 2.22.531.5- Current version
Version
Android version 4.4.3/Software 2.22.531.5
Approved 08/18/14
Features
User experience improvements
Prerequisites
Device software is not rooted
50% battery life
Wi-Fi connection
And I can't even confirm if T-Mobile actually deployed it to my area on the 18th or not as I've been on ViperOne for weeks now, and so because of that, I wouldn't get the OTA notification anymore.
RockStar2005
smokin901 said:
If you are talking about Firmware as in files in firmware.zip
ie
hboot
radio.img
modem_st1.img
rcdata.img
rconfig.img
rpm.img
etc......
then
radio is different for every major carrier which enables or disables specific radio bands.
true for US region.
Click to expand...
Click to collapse
Smokin,
Ok. I'm just trying to pinpoint the pros and cons of downloading firmware or even regular OTA updates on a T-Mobile M8 vs a non-carrier specific M8. I def get that the radio bands will differ from one carrier to the next, but is there any gain or loss of quality etc in downloading a carrier-specific firmware or OTA, or no difference at all? The posts so far have suggested a difference in favor of the non-carrier versions.
RockStar2005
RockStar2005 said:
Hello again HTC,
What's EPSM? And WWE?
Wow really?? The T-Mobile OTA was actually missing stuff the non-carrier one wasn't?? That's crazy.
Click to expand...
Click to collapse
Actually I think it is very sad that those things were still missing, when I debranded mine, as all non-carrier devices got the EPSM with the day one update to give an example.
RockStar2005 said:
T-Mobile:
Beginning August 18, the HTC One (M8) received a software update 2.22.531.5 (or firmware 2.22.401.4 or .5?).
Software version
Android version 4.4.3/ Software 2.22.531.5- Current version
Version
Android version 4.4.3/Software 2.22.531.5
Approved 08/18/14
Features
User experience improvements
Prerequisites
Device software is not rooted
50% battery life
Wi-Fi connection
Click to expand...
Click to collapse
And reading the quote above I wouldn't put my ass on the line that the GPS fix realy is inclueded.
But maybe some T-MOB101 users could tell if this update finally got the EPSM, as well as the GPS fix!?
HTCNerdYoda said:
Actually I think it is very sad that those things were still missing, when I debranded mine, as all non-carrier devices got the EPSM with the day one update to give an example.
And reading the quote above I wouldn't put my ass on the line that the GPS fix realy is inclueded.
But maybe some T-MOB101 users could tell if this update finally got the EPSM, as well as the GPS fix!?
Click to expand...
Click to collapse
I see. But what's EPSM though? And WWE? Not sure I'm following on the "day one update"......do u mean the non-carrier devices got EPSM on the same day it was set to be released?
Yeah........ I mean, the carriers deploy the updates by regions over a set period of time. And note that it was APPROVED on August 18th by T-Mobile. I don't know if that was the same date they started deploying or not too. And since their description is so vague, I again can't say if that GPS fix was included or not. To me, the GPS on phones still aren't 100% perfect, so ANY fix that a company (phone maker or even carrier) can put out there that improves GPS quality is important. Just 2 weeks ago my GPS SLIGHTLY took me off course until I reset my phone, then all was fine. Wasted about 10 minutes of my time because of it. Not a big deal, but still relevant. Maybe had I already had that fix back then that wouldn't have happened? I mean, u still should reset your phone once or twice a week anyway I think, but these fixes help increase the chance of success w/o HAVING to reboot.
RockStar2005
RockStar2005 said:
I see. But what's EPSM though? And WWE? Not sure I'm following on the "day one update"......do u mean the non-carrier devices got EPSM on the same day it was set to be released?
Yeah........ I mean, the carriers deploy the updates by regions over a set period of time. And note that it was APPROVED on August 18th by T-Mobile. I don't know if that was the same date they started deploying or not too. And since their description is so vague, I again can't say if that GPS fix was included or not. To me, the GPS on phones still aren't 100% perfect, so ANY fix that a company (phone maker or even carrier) can put out there that improves GPS quality is important. Just 2 weeks ago my GPS SLIGHTLY took me off course until I reset my phone, then all was fine. Wasted about 10 minutes of my time because of it. Not a big deal, but still relevant. Maybe had I already had that fix back then that wouldn't have happened? I mean, u still should reset your phone once or twice a week anyway I think, but these fixes help increase the chance of success w/o HAVING to reboot.
RockStar2005
Click to expand...
Click to collapse
EPSM is the ExtremePowerSavingMode introduced by HTC and yes the update came out on the day the One M8 got released. At least it did for the WWE (World Wide English) variants of the HTC - which are the official HTC variants without any - if just like here - software branding by the providers.
In my opinion that's what leeds to long period between HTC own OTAs and carrier OTAs of any smartphone. The carriers - be it T-Mobile, Vodafone or some others - try to integrate their own bloatware into those updates. T-Mob e.g. says there are still issues with the EPSM, but asking me those problems are likely to be triggered by T-Mobiles own bloatware.
And well fixes for e.g. GPS just arrive much later on carrier-branded devices ....
RockStar2005 said:
Smokin,
is there any gain or loss of quality etc in downloading a carrier-specific firmware or OTA, or no difference at all?
Click to expand...
Click to collapse
Quality of what? It seems like a very subjective question. Fixes and other updates are almost always going to come out sooner on the "international" unbranded version. That much is "better". But some folks like carrier-specific features. For example, doesn't T-Mob have WiFi calling? Some AT&T folks like Visual Voicemail and ISIS (payment system), while I (just personally) can care less for such things.
As far as band support, having your carrier's radio (or one that is at least compatible with your carrier) plus the custom ROM of your choice should take care of any band compatibility issues.
HTCNerdYoda said:
EPSM is the ExtremePowerSavingMode introduced by HTC and yes the update came out on the day the One M8 got released. At least it did for the WWE (World Wide English) variants of the HTC - which are the official HTC variants without any - if just like here - software branding by the providers.
In my opinion that's what leeds to long period between HTC own OTAs and carrier OTAs of any smartphone. The carriers - be it T-Mobile, Vodafone or some others - try to integrate their own bloatware into those updates. T-Mob e.g. says there are still issues with the EPSM, but asking me those problems are likely to be triggered by T-Mobiles own bloatware.
And well fixes for e.g. GPS just arrive much later on carrier-branded devices ....
Click to expand...
Click to collapse
Yoda,
Oh yeah........ ok, EPSM. Got it. Yeah that came out weeks later on T-Mobile, but ok that's cool that HTC released it the same day the M8 was released. Yeah, I guess that makes sense b/c they're adding more into it, but not anything important. But I'm still not getting how bloatware fits in to the firmware? I understand bloatware like all the T-Mobile-specific apps that come with the phone, but what bloatware comes in the updates??
Yeah that's definitely a possibility........... like perhaps certain parts of their "firmware bloatware" are interfering or not compatible with the EPSM.
Well that's not good. Those fixes should be deployed before anything else. Google Maps is only as good as the phone's GPS capabilities.
Thanks,
RockStar2005
RockStar2005 said:
Yoda,
Oh yeah........ ok, EPSM. Got it. Yeah that came out weeks later on T-Mobile, but ok that's cool that HTC released it the same day the M8 was released. Yeah, I guess that makes sense b/c they're adding more into it, but not anything important. But I'm still not getting how bloatware fits in to the firmware? I understand bloatware like all the T-Mobile-specific apps that come with the phone, but what bloatware comes in the updates??
Yeah that's definitely a possibility........... like perhaps certain parts of their "firmware bloatware" are interfering or not compatible with the EPSM.
Well that's not good. Those fixes should be deployed before anything else. Google Maps is only as good as the phone's GPS capabilities.
Thanks,
RockStar2005
Click to expand...
Click to collapse
You're welcome RockStar!
Firmware (such as ICS, Jelly Bean, KitKat) on your phone is the core system. The ROM IS just the OS on top of it. But the OS is configured to perform with a specific core, meaning that a carrier OS version is programmed to work with a specially designed firmware. Thus firmware for e.g. a T-Mobile ROM (OS) is a little bit altered compared to the one for a pure HTC ROM, as it has to fit the ROM altered by T-Mobile.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
You're welcome RockStar!
Firmware (such as ICS, Jelly Bean, KitKat) on your phone is the core system. The ROM IS just the OS on top of it. But the OS is configured to perform with a specific core, meaning that a carrier OS version is programmed to work with a specially designed firmware. Thus firmware for e.g. a T-Mobile ROM (OS) is a little bit altered compared to the one for a pure HTC ROM, as it has to fit the ROM altered by T-Mobile.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yoda,
I see. Well right now I use ViperOne M8, and although the last firmware was from T-Mo, the one I just got (2.22) was not carrier-specific (http://www.renovate-themes.de/index.php?s=firmware). Though I believe ViperOne M8 is designed to be compatible with all variants?
I see what you're saying better now, but I don't know if I'd call the T-Mobile firmware & ROM "bloatware". But I guess to really know how to refer to it, I'd have to ask: What kind of changes do they make to the carrier one?
Thanks,
RockStar2005
RockStar2005 said:
Yoda,
I see. Well right now I use ViperOne M8, and although the last firmware was from T-Mo, the one I just got (2.22) was not carrier-specific (http://www.renovate-themes.de/index.php?s=firmware). Though I believe ViperOne M8 is designed to be compatible with all variants?
I see what you're saying better now, but I don't know if I'd call the T-Mobile firmware & ROM "bloatware". But I guess to really know how to refer to it, I'd have to ask: What kind of changes do they make to the carrier one?
Thanks,
RockStar2005
Click to expand...
Click to collapse
Yes, the one you got is the WWE firmware. And yes again, ViperOne works with most 2.22.xxx.x firmwares, but is build upon 2.22.401.5.
Changes are as @redpoint73 already said e.g. Wifi calling in case of the T-Mobile firmware.
redpoint73 said:
Quality of what? It seems like a very subjective question. Fixes and other updates are almost always going to come out sooner on the "international" unbranded version. That much is "better". But some folks like carrier-specific features. For example, doesn't T-Mob have WiFi calling? Some AT&T folks like Visual Voicemail and ISIS (payment system), while I (just personally) can care less for such things.
As far as band support, having your carrier's radio (or one that is at least compatible with your carrier) plus the custom ROM of your choice should take care of any band compatibility issues.
Click to expand...
Click to collapse
Red,
I just meant quality of how the phone interacts with the network, etc.
Yes that is true. Though ROMs like the one I have, ViperOne M8, have managed to include things like Wi-Fi Calling in their options. Since ViperOne is fully compatible with T-Mobile M8s, and they have been good about offering the same things T-Mo does, then it seems to be all good. I think Six was just saying it's really only an issue when you use one carrier's phone on another carrier's network.
Thanks,
RockStar2005
HTCNerdYoda said:
Yes, the one you got is the WWE firmware. And yes again, ViperOne works with most 2.22.xxx.x firmwares, but is build upon 2.22.401.5.
Changes are as @redpoint73 already said e.g. Wifi calling in case of the T-Mobile firmware.
Click to expand...
Click to collapse
Yoda,
Ok. I just said int'l, but I guess WWE is the same thing. Good to know.
Yeah. ViperOne didn't have Wi-Fi Calling for a lil while but as of last week the most recent update re-enabled it on my M8. I never use it though b/c it totally blocks incoming/outgoing MMS (though not regular SMS) messages. Even one customer service rep lady at T-Mobile told me she has the same issue, and has for years. I would only use it if I was in another country and wanted to make a free call and had access to Wi-Fi. But I'd shut it off the second I was done with that call. lol
Thanks,
RockStar2005
RockStar2005 said:
Red,
I just meant quality of how the phone interacts with the network, etc.
Click to expand...
Click to collapse
Its not normally a function of the ROM. As long as you are on a T-Mob compatible radio, it shouldn't matter what ROM you are on.
Although there is the other complication that has been mentioned: with any 2.xx based custom ROM (ViperOne included) you need to be using updated firmware (not to be confused with the ROM). So you will want a firmware that plays well with the 2.xx ROM, and one that plays well with T-Mobile's network.
---------- Post added at 03:33 PM ---------- Previous post was at 03:26 PM ----------
RockStar2005 said:
the one I just got (2.22) was not carrier-specific (http://www.renovate-themes.de/index.php?s=firmware). Though I believe ViperOne M8 is designed to be compatible with all variants?
Click to expand...
Click to collapse
2.22.401 firmware is for the unbranded "international" variant. Its not specifically designed for use in the US, and at least for AT&T, it has caused reception issues from dodgy reception, to no service whatsoever (solution was to flash 2.22.1540 firmware). So not sure how this will play out on the T-Mob network.
Best bet would be to flash the firmware from the new T-Mob OTA rolling out, but I don't think its been posted here yet.
Yeah, though I was referring more to the firmware than the ROM.
Yes..... true. Yeah the firmware is just the various data and ROM is like the interface. I believe the 2.22.401.5 firmware is fully compatible. If you believe it's not, please let me know.
---------- Post added at 03:33 PM ---------- Previous post was at 03:26 PM ----------
[/COLOR]
2.22.401 firmware is for the unbranded "international" variant. Its not specifically designed for use in the US, and at least for AT&T, it has caused reception issues from dodgy reception, to no service whatsoever (solution was to flash 2.22.1540 firmware). So not sure how this will play out on the T-Mob network.
Best bet would be to flash the firmware from the new T-Mob OTA rolling out, but I don't think its been posted here yet.[/QUOTE]
The firmware I have is 2.22.401.5. And ViperOne M8 offers (using 2.22.401.5 as a base) full T-Mo functionality:
ViperOneM8 2.2.0 (August 19)
ADDED full T-Mobile carrier support
FIXED T-Mobile WIFI calling
FIXED Locked IPV4/6 Settings
FIXED AOSP incoming call workaround not working
ViperOneM8 2.1.0 (August 16)
Merged with HTC OTA 2.22.401.5
Added new stock kernel from OTA (Only full ROM)
GPS improvements and fixes from HTC
Workaround white gap in dialer when having custom stock navbar size
Fixed Notification icon color
Added longpress power custom actions
So after reading that, would you say I'm at the equivalent of T-Mo's OTA, or T-Mo's is still better? I just hate waiting on T-Mo, esp if their OTAs are not perfect either (see Yoda's posts in this thread). Team Venom (who makes ViperOne) has told me they base their updates on T-Mobile's, but tweak them to work better with ViperOne. So I guess their's aren't pure HTC either. lol
Thank You,
RockStar2005
My nexus 6P has become my daily driver since I got it, but I still use my note 4 daily for a lot of stuff via WiFi (6P has Sim)
I saw the MM Ota should be rolling out over Verizon soon and was wondering if it was possible to update without Sim? Or is it likely someone will upload the Ota here?
Don't get your hops up... Verizon is the last one in this planet to release updates.
Normally you won't be able to get OTA without sim card... But you can always use the verizon software assistant on pc to update
Sent from my SM-N910V using XDA-Developers mobile app
I mean I've seen screens of Verizon note 4's with the update so I think it's gotta be coming soon at the least but thanks a ton for the software assistant tip, I forgot about that
I believe the Verizon Assistant will not work on bad ESN, black listed EMEI or phones not activated with a SIM.
Sent from my SM-N910V using Tapatalk
Degenerator9000 said:
I mean I've seen screens of Verizon note 4's with the update so I think it's gotta be coming soon at the least but thanks a ton for the software assistant tip, I forgot about that
Click to expand...
Click to collapse
You've seen screens of a VZ Note 4 with MM?
IndyRoadie said:
You've seen screens of a VZ Note 4 with MM?
Click to expand...
Click to collapse
I thought I had but I just checked and they weren't Verizon
Whoopsies
I'll probably end up waiting a but anyway to see if the developer edition conversion pans out
Degenerator9000 said:
I thought I had but I just checked and they weren't Verizon
Whoopsies[emoji14]
I'll probably end up waiting a but anyway to see if the developer edition conversion pans out
Click to expand...
Click to collapse
The international version just went out no more than a week or two ago. If past patterns hold, we have at least several more months of waiting. Here's to hoping it'll be better this time around though.
Sent from my SM-N910V using XDA-Developers mobile app
I was curious what build numbers you all have received! I heard there are different build numbers based on where you are located in the world. I personally received one with the build number NDE63L being here in the US.
NDE63P. I'm in Florida.
Sent from my Pixel XL using Tapatalk
NDE63P in mn
Sent from my Pixel XL using XDA-Developers mobile app
NDE63H in Germany
NDE63P. Also in Florida.
NDE63H in the UK (EE network)
Odd that I'm seeing most US (so far) have the P variant when I received one with the L variant. I've been having issues with receiving calls on Sprint network as well as data connection (at times). I just flashed the P variant onto my phone from Google's factory images. Hopefully that'll sort out my issue as the baseband versions are different but bootloaders are identical.
blaz4710 said:
Odd that I'm seeing most US (so far) have the P variant when I received one with the L variant. I've been having issues with receiving calls on Sprint network as well as data connection (at times). I just flashed the P variant onto my phone from Google's factory images. Hopefully that'll sort out my issue as the baseband versions are different but bootloaders are identical.
Click to expand...
Click to collapse
Interesting. I have the L variant as well and I'm in NJ on AT&T. I have noticed that sometimes my txt's don't come in. Then all of a sudden I get 2 or 3 in a row as if they were backed up.
NDE63L in Colorado on Google Fi purchased from the Google Store
mdecker79 said:
Interesting. I have the L variant as well and I'm in NJ on AT&T. I have noticed that sometimes my txt's don't come in. Then all of a sudden I get 2 or 3 in a row as if they were backed up.
Click to expand...
Click to collapse
Although sad to hear you are having issues, I am also glad I am no the only one. I wonder if it has something to do with the new Doze as I've noticed the phone call issue is when the phone as been idle for awhile.
NDE63P uk ee
blaz4710 said:
Although sad to hear you are having issues, I am also glad I am no the only one. I wonder if it has something to do with the new Doze as I've noticed the phone call issue is when the phone as been idle for awhile.
Click to expand...
Click to collapse
Yes I can agree with the Doze on the go "issue". Some of my push emails using Nine or Gmail don't come in right away. I'm ok with this because of the extra battery life. It's really only a few minutes delayed so its not that bad.
Anybody have NDE63P on tmo in the us?
mcrumps said:
Anybody have NDE63P on tmo in the us?
Click to expand...
Click to collapse
I believe P is Verizon build. It's not just location US vs international but carrier with Vzw's exclusivity and custom build
NDE63L FL as well
NDE63L, PR
mcrumps said:
Anybody have NDE63P on tmo in the us?
Click to expand...
Click to collapse
Yes
NDE63L. California, purchased from the Google Store.
XX63L. T-Mobile. California. First batch
All the builds are the same from the looks of the kernel date, so might just be region based. We'll find out when the next release hits
P on Google Store purchased phone with Verizon service. VA
So I got my phone yesterday and it did some updating while I was setting it up and noticed that the latest firmware it installed was NDE63X not V. I bought this from Google not Verizon paid all the money up front so it is fully mine. I have Verizon service, did they just hijack my phone? I have Googled a bit on it and can't find an answer. This worries me since I avoided buying from Verizon so they had no say on updates. I have not gotten any of the Verizon apps automatically added toy phone yet. Thanks for any answer.
Sent from my Pixel XL using Tapatalk
If you have a Verizon SIM in the phone, it will get Verizon firmware images regardless of where you bought the phone.
I would recommend flashing the Google OTA's yourself when they release.
Don't worry. You got the verizon firmware because you have a verizon sim. The reverse is true for people who bought their phones from verizon and went to another carrier. Their phones updated to the US firmware automatically.
Verizon bootloaders cannot be unlocked. That is the only difference. Firmware versions are completely independent of this fact.
ahent said:
So I got my phone yesterday and it did some updating while I was setting it up and noticed that the latest firmware it installed was NDE63X not V. I bought this from Google not Verizon paid all the money up front so it is fully mine. I have Verizon service, did they just hijack my phone? I have Googled a bit on it and can't find an answer. This worries me since I avoided buying from Verizon so they had no say on updates. I have not gotten any of the Verizon apps automatically added toy phone yet. Thanks for any answer.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No. The software sees that you are using a Verizon sim and downloads the version that is optimized for Verizon networks.
Makes the radio work more efficiently with the bands Verizon uses and such things like that. Maybe downloads a set of unique Verizon apps you may want to use for your convenience. You can dismiss these apps or run some other firmware if you wish. It is not hijacking your phone and turning it into an evil, screwed up monster with a locked bootloader or rendering it unrootable.
Sent from my Nexus 7 using Tapatalk
Thanks, just the info I needed. If I switched carriers or traveled internationally and switched sim cards would this cause the phone issues?
Sent from my Pixel XL using Tapatalk
ahent said:
Thanks, just the info I needed. If I switched carriers or traveled internationally and switched sim cards would this cause the phone issues?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No.
Thanks again, I love XDA.
Sent from my Pixel XL using Tapatalk
You may get slightly better performance overseas or on another carrier with different firmware due to the slight differences in the radio, but it will function the same otherwise.
Sent from my Pixel XL
If I have a Verizon version unlocked and take the Verizon firmware update is it possible for them to relock the bootloader? UPDATE - I looked on the forum and it seems like every agrees that it isn't possible for VZ to relock bootloader with firmware updates. Just want to confirm this is correct.
So I just purchased a new pixel 2 XL, an I'm getting ready to update my phone to the latest 8.1 OTA firmware from Google developer section (pie looks to have too many problems that are unacceptable to me), and I'm seeing T-Mobile firmware. I am on T-Mobile in the US, but I'm wondering if this is firmware for European market or something weird.
Should I use the T-Mobile firmware, or the non-specified OTA?
Soured Lie said:
So I just purchased a new pixel 2 XL, an I'm getting ready to update my phone to the latest 8.1 OTA firmware from Google developer section (pie looks to have too many problems that are unacceptable to me), and I'm seeing T-Mobile firmware. I am on T-Mobile in the US, but I'm wondering if this is firmware for European market or something weird.
Should I use the T-Mobile firmware, or the non-specified OTA?
Click to expand...
Click to collapse
Go into settings/system/about phone. Look at the build number at the bottom. Choose the firmware that correspond with that number.
Eg: OPM2.
Chance Ill said:
Go into settings/system/about phone. Look at the build number at the bottom. Choose the firmware that correspond with that number.
Eg: OPM2.
Click to expand...
Click to collapse
Thank you for answering, unfortunately the only update that corresponds with OPD1 for my device is the firmware I am currently on. There are also multiple firmwares with the same date for other similar numbers (there is an OPD1 for Rogers, as well as one for Telstra and another with no signifier and so on). I'm not seeing anything that really correlates to my device in particular. Not for updates anyways. The build numbers have changed.
In my mind it is only logical that they have Google images and Verizon images as they never released model that was carrier specific outside of those two.
Soured Lie said:
Thank you for answering, unfortunately the only update that corresponds with OPD1 for my device is the firmware I am currently on. There are also multiple firmwares with the same date for other similar numbers (there is an OPD1 for Rogers, as well as one for Telstra and another with no signifier and so on). I'm not seeing anything that really correlates to my device in particular. Not for updates anyways. The build numbers have changed.
In my mind it is only logical that they have Google images and Verizon images as they never released model that was carrier specific outside of those two.
Click to expand...
Click to collapse
What model do you have? Verizon, Telstra, Rogers, etc
Chance Ill said:
What model do you have? Verizon, Telstra, Rogers, etc
Click to expand...
Click to collapse
I have an unlocked Google edition 2xl running on t-mobile network.
When did they ever make a Rogers or T-Mobile version?
Soured Lie said:
I have an unlocked Google edition 2xl running on t-mobile network.
When did they ever make a Rogers or T-Mobile version?
Click to expand...
Click to collapse
Some carriers like Verizon sell (not make) the Pixel thus the .img files correlates with that network for compatibility. I also use my device on T-Mobile US but us the OPM2 firmware because TMobile firmware (OPM4) caused modem issues
Chance Ill said:
Some carriers like Verizon sell (not make) the Pixel thus the .img files correlates with that network for compatibility. I also use my device on T-Mobile US but us the OPM2 firmware because TMobile firmware (OPM4) caused modem issues
Click to expand...
Click to collapse
I really appreciate your help. I am on stock firmware and have really good connectivity, so I think I'll do what you have done and stick to similar firmware.
I have one last question. I'm about to sideloaded this, the instructions say to make sure there are no pending updates before proceeding. I have pending pie update which I have not downloaded, is this going to cause issues? I can't see why it would. I guess at worst it will reject my sideloaded at worst if it was expecting something else?
Soured Lie said:
I really appreciate your help. I am on stock firmware and have really good connectivity, so I think I'll do what you have done and stick to similar firmware.
I have one last question. I'm about to sideloaded this, the instructions say to make sure there are no pending updates before proceeding. I have pending pie update which I have not downloaded, is this going to cause issues? I can't see why it would. I guess at worst it will reject my sideloaded at worst if it was expecting something else?
Click to expand...
Click to collapse
As long as you haven't downloaded the ota, you should be fine.
Chance Ill said:
As long as you haven't downloaded the ota, you should be fine.
Click to expand...
Click to collapse
Already updated. Everything is smooth so far. Thank you for taking the time to help. I used to make ROMs when ICS was out, but everything has changed. Partition scheming and the whole 9. I'm a newbie all over again. I forgot how much I enjoyed Android. Very liberating after being on iOS for so long. Anyhow, have a good day.
Soured Lie said:
Already updated. Everything is smooth so far. Thank you for taking the time to help. I used to make ROMs when ICS was out, but everything has changed. Partition scheming and the whole 9. I'm a newbie all over again. I forgot how much I enjoyed Android. Very liberating after being on iOS for so long. Anyhow, have a good day.
Click to expand...
Click to collapse
Lol. Yeah, much has changed since the good ole days. Welcome home! ?
Can some one confirm what OTA should I download for T-Mobile US on Pixel XL 2 for 9.0 ? Thank you
The one NOT for Telstra.
I'm hoping they release an update for TMobile. I'm having serious signal issues since moving to Pie... Once the signal drops a bit I immediately drop to 3G or even H+... Never had that issue with the TMobile release for Oreo.