Develop Bugs

T-mobile UK Firmware upgrade

Can anyone share there firmware version for a stock UK T-mobile HOX. Not only do I not get the 1.28 upgrade (surprise surprise) but I seem to be on a version no-one else seems to mention 1.26.110.5. Can anyone help me confirm this is the standard t-mobile version. Cheers.

it's mentioned a few times in the HOX branch - think it's one of the first impressions threads. I did a thread search on your version and found a few mentions.

joll200x said:
it's mentioned a few times in the HOX branch - think it's one of the first impressions threads. I did a thread search on your version and found a few mentions.
Click to expand...
Click to collapse
Thanks for the reply. I did search but didn't really find the answer to my question. I will try putting it another way.
Does anyone have a STOCK UK T-MOBILE HOX that has a firmware version different to 1.26.110.5 or are we always going to be massively behind even the other carrier branded phones with updates.
Didn't really want to root yet but it is looking more like the only answer.

110 is the standard code for T-mobile UK, so yes, you seem to have the correct T-Mobile UK ROM.
Yes, it'll probably be a while till you get the 1.28 update as t-mobile are especially thorough in their testing before they release a ROM update. However, they're no worse than orange since they joined together.

I can confirm i'm on the same software and on T-mobile UK. I rooted because in the 4 years of being with t-mobile they never release a software update anywhere close to an expected date.
Some folk are still waiting for updates to Froyo on phones apparently.

Paulst30 said:
I can confirm i'm on the same software and on T-mobile UK. I rooted because in the 4 years of being with t-mobile they never release a software update anywhere close to an expected date.
Some folk are still waiting for updates to Froyo on phones apparently.
Click to expand...
Click to collapse
hey guys i have a problem with my ONE X! it wont UPDATE from 1.26!! i asked the HTC guys and they said its a T-MOBILE UK variant..its upto them.. but ive heard people getting updates on t mobile... what should be done? any ideas? i tried to root the phone via htc dev.. i get the token bu then at the last step when i put in the flash command.. nothing happens!!

Why don't you look for a T-Mobile ruu and use that.
Sent from my GT-I9300 using xda app-developers app

[Q] Firmware versions

I have a TMO version of the M8 and was curious about the importance of firmware versions when using custom ROMs. I notice that all the ROMs are based on firmware version 3.28.401.9, but the latest TMO version is 3.32.531.2. Am I correct in assuming that the TMO, being that it has a higher number, contains the same, or newer, changes/fixes that the other firmware contains? If so, why don't they base it on the higher one instead? Also, is there any benefit for me to use the firmware that the ROMs are based on?

There isn't a clear cut answer on this. Yes, technically the higher software/firmware number (firmware itself does not really have a "number" but we merely associate it with the software that it deployed with) the "newer" it is. But it just might be carrier specific changes, and often there are no significant upgrades beyond that (for versions numbers that are close together). I'm no dev, and can't really speak for them. But my hunch would be that its usually preferable to base a custom ROM on an unbranded base, as too much carrier meddling can cause some issues and headaches (and I've seen this problem rear its head on previous devices).
I'd tend to suggest that using the firmware for your carrier/region is best. But this might not be the best for everyone, everywhere. And there is even some trial and error involved.

redpoint73 said:
There isn't a clear cut answer on this. Yes, technically the higher software/firmware number (firmware itself does not really have a "number" but we merely associate it with the software that it deployed with) the "newer" it is. But it just might be carrier specific changes, and often there are no significant upgrades beyond that (for versions numbers that are close together). I'm no dev, and can't really speak for them. But my hunch would be that its usually preferable to base a custom ROM on an unbranded base, as too much carrier meddling can cause some issues and headaches (and I've seen this problem rear its head on previous devices).
I'd tend to suggest that using the firmware for your carrier/region is best. But this might not be the best for everyone, everywhere. And there is even some trial and error involved.
Click to expand...
Click to collapse
@tkoreaper
The different numbers are a CDMA vs GSM thing.
The 328 is GSM, 332 is CDMA.
T-Mo is CDMA.

xunholyx said:
@tkoreaper
The different numbers are a CDMA vs GSM thing.
The 328 is GSM, 332 is CDMA.
T-Mo is CDMA.
Click to expand...
Click to collapse
Ummm, no... TMO and AT&T are GSM. Sprint and VZ are CDMA. TMO is the only one with 3.32 I believe.

tkoreaper said:
Ummm, no... TMO and AT&T are GSM. Sprint and VZ are CDMA. TMO is the only one with 3.32 I believe.
Click to expand...
Click to collapse
Okay. I'm mistaken. I'm not American. But, the latest GSM firmware is the .9
Americans are weird.
I knew AT&T was GSM, but always thought T-mo wasn't. Thanks for correcting me.
Perhaps it's a WWE thing? I'm newish to HTC. Well......maybe 5 months isn't exactly new, but HTC is sure a lot different than Samsung.
EDIT: If you can wait till tomorrow, I can get a solid answer to this. My HTC firmware expert guy is in Germany and probably sleeping right now.
He'll have a definitive answer that I can pass along.

xunholyx said:
Okay. I'm mistaken. I'm not American. But, the latest GSM firmware is the .9
Americans are weird.
Click to expand...
Click to collapse
Firmware/software numbers are always chronological. 3.32.531.2 is newer than 3.28.401.9. But whether there are any significant software changes beyond carrier customizations, is the question. Or for that matter, if the firmware is even different.

redpoint73 said:
Firmware/software numbers are always chronological. 3.32.531.2 is newer than 3.28.401.9. But whether there are any significant software changes beyond carrier customizations, is the question. Or for that matter, if the firmware is even different.
Click to expand...
Click to collapse
But that wasn't the case with the WWE vs T-Mobile(Poland). WWE International was 1.54.401.x T-Mobile was 1.57.118.x <But didn't even have the extreme power saving mode.
It could probably be argued that carriers add their own number there for their changes, then again, the unbranded Asian(Hong Kong) variant also uses 3.32.xxx.x . Don't know why they number it that way, but it doesn't necessarily mean it's "newer" or "better" (Like the T-Mobile vs WWE example).
O2, 3, T-Mobile, AT&T, Bell, Telus/Rogers they all use different numbers there.

BerndM14 said:
But that wasn't the case with the WWE vs T-Mobile(Poland). WWE International was 1.54.401.x T-Mobile was 1.57.118.x <But didn't even have the extreme power saving mode.
Click to expand...
Click to collapse
Are you saying that 1.57 came out before 1.54?
BerndM14 said:
It could probably be argued that carriers add their own number there for their changes, then again, the unbranded Asian(Hong Kong) variant also uses 3.32.xxx.x .
Click to expand...
Click to collapse
Carriers don't make any of the updates. They all come from HTC, based on customizations directed by the carrier.

redpoint73 said:
Are you saying that 1.57 came out before 1.54?
Click to expand...
Click to collapse
Of course not. But what exactly about that update was newer/better than what we got from the 1.54 ?
That's what makes the way they number these software versions so strange. Even though it's logical that a move from 3.28 to 3.57(For example) would mean a newer version with improvements, it was definitely not the case for T-Mobile(Poland) by being on 1.57 vs our 1.54.
Then of course the International Version got the 3.28 much sooner than the Dev edition yet the Dev edition is also 3.28 where as the Bell release that came out recently is 3.34 yet the update is the same as the one we got on International/Dev Edition with the exception of carrier bloated nonsense and changes.
That's why I say it's a weird way to number the software, they could all have rolled out as 3.28 and just have the x.xx.region-code.x be different.
Carriers don't make any of the updates. They all come from HTC, based on customizations directed by the carrier.
Click to expand...
Click to collapse
Oh ok, I figured that HTC creates the package for the carrier, sends it over to them, they make any local changes they want and then roll out the package to their customers. Thought that they would then "change" the software number based on their own structure/build.

BerndM14 said:
Of course not. But what exactly about that update was newer/better than what we got from the 1.54 ?
Click to expand...
Click to collapse
I never said anything was "better". Newer doesn't always mean better. The fact the "newer" software is not necessarily better is exactly the point I've been trying to make.
A "newer" software may even be worse. For instance, AT&T released 4.4.3 later than most other versions (version 2.23). But suffered a power drain bug (that I don't believe other versions suffered) and was subsequently pulled.
I still believe that the higher firmware number is "newer". But that "new" may just mean carrier customizations, as I mentioned several times already. If they make any changes, they use a different software number, a number higher than the last one they used. Just normal software version control.
Of course, there are other variables at play that may affect version number vs. release date. A software version might get sent over to the carrier and be delayed in testing for months (AT&T is notorious for this) and other software might get released on other carriers in the meantime.

redpoint73 said:
I never said anything was "better". Newer doesn't always mean better. The fact the "newer" software is not necessarily better is exactly the point I've been trying to make.
I still believe that the higher firmware number is "newer". But that "new" may just mean carrier customizations, as I mentioned several times already. If they make any changes, they use a different software number, a number higher than the last one they used. Just normal software version control.
Of course, there are other variables at play that may affect version number vs. release date. A software version might get sent over to the carrier and be delayed in testing for months (AT&T is notorious for this) and other software might get released on other carriers in the meantime.
Click to expand...
Click to collapse
Exactly, I didn't make my post to argue against your point, I made it to show the OP that a higher number doesn't necessarily mean it's "better" or perhaps, contradictory as it sounds, "newer". Hence why I used the T-Mobile(Poland) roll-out as an example.
It must be carrier specific though(to some extent at least).
20 October , Vodafone roll out 3.29.161.5 342.4 MB
21 October , T-Mobile roll out 3.32.111.3 361.79 MB
The same update, HTC Eye, Face Tracking, Split Capture etc, file sizes differ by a rather big amount and it was only 1 day difference, yet there was a couple of days between International and Dev and it still had the same roll out version 3.28. Which is why I figured that even though the number might be higher it was more to do with carriers. Perhaps it's also linked to something else at HTC's side for releasing builds don't know... Either way though.
Was just trying to point out that it doesn't necessarily mean that his 3.32 is "newer" than the 3.28. Why the developers use the 3.28.401.x as their base is also not known to me, perhaps just easier that way.
Anyways...

BerndM14 said:
It must be carrier specific though(to some extent at least).
Click to expand...
Click to collapse
It seems to me that the number after the second decimal is carrier/region specific. The numbers before that are the main "version" number, and a minor change will increase the last number.
BerndM14 said:
Was just trying to point out that it doesn't necessarily mean that his 3.32 is "newer" than the 3.28.
Click to expand...
Click to collapse
I still think it does (aside from some variables like carrier delay, like I mentioned). Newer, but not by any means necessarily better.
BerndM14 said:
Why the developers use the 3.28.401.x as their base is also not known to me, perhaps just easier that way.
Click to expand...
Click to collapse
Every ROM and situation is different. But unbranded is often the best base for a custom ROM. I've seen carrier customizations cause havoc when used as a base for custom ROMs.

Connectivity Status on 1.53?

Hi all,
I have a VZW 10 running 1.19. I'm interested in knowing if the connectivity issues, specifically Wi-Fi, have been fixed. The patch notes for 1.53 do address it, but has it been fixed.
I know there are workarounds, but this is a $550 phone. Wi-Fi should work out of the box.
Thanks for your help.
Sent from my HTC6545LVW using Tapatalk

dn.lck said:
Hi all,
I have a VZW 10 running 1.19. I'm interested in knowing if the connectivity issues, specifically Wi-Fi, have been fixed. The patch notes for 1.53 do address it, but has it been fixed.
I know there are workarounds, but this is a $550 phone. Wi-Fi should work out of the box.
Thanks for your help.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
1.53 is for general US unlocked and not VZW. 1.53 needs non VZW firmware to work properly.
1.19 is a very old build (US launched with 1.21) so I'd expect a VZW update sometime in the next 30 days.
Sent from my HTC One using Tapatalk

datafoo said:
1.53 is for general US unlocked and not VZW. 1.53 needs non VZW firmware to work properly.
1.19 is a very old build (US launched with 1.21) so I'd expect a VZW update sometime in the next 30 days.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm on 1.19 as well shipped from Verizon. no update was available to 1.21 for me. I'm currently using viper now with 1.19 still, hoping to see something pop up on here :fingers-crossed:
I seem to have wifi issues using standard wifi, but if I use the wifi-5G connection It works flawless

afuller42 said:
I'm on 1.19 as well shipped from Verizon. no update was available to 1.21 for me. I'm currently using viper now with 1.19 still, hoping to see something pop up on here :fingers-crossed:
I seem to have wifi issues using standard wifi, but if I use the wifi-5G connection It works flawless
Click to expand...
Click to collapse
Correct, 1.21 is ONLY for general unlocked versions and not VZW. You won't see a 1.21.617.* or 1.53.617.* update as those are not for your device. In fact you shouldn't use any *.617.* build as the 617 indicates it's not for your carrier but general unlocked.
You must use a VZW build because of firmware and custom VZW settings. Your only choice right now is to wait for VZW to push their build update.
Sent from my HTC One using Tapatalk

My wifi was fine on 1.21, then was horrible with the 1.53 update. It's mostly alright now with a couple tweaks.

datafoo said:
Correct, 1.21 is ONLY for general unlocked versions and not VZW. You won't see a 1.21.617.* or 1.53.617.* update as those are not for your device. In fact you shouldn't use any *.617.* build as the 617 indicates it's not for your carrier but general unlocked.
You must use a VZW build because of firmware and custom VZW settings. Your only choice right now is to wait for VZW to push their build update.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Interesting. How will future firmware updates work? Will we receive the same but with .605 at the end?
regalpimpin said:
My wifi was fine on 1.21, then was horrible with the 1.53 update. It's mostly alright now with a couple tweaks.
Click to expand...
Click to collapse
Sent from my HTC6545LVW using Tapatalk

dn.lck said:
Interesting. How will future firmware updates work? Will we receive the same but with .605 at the end?
Click to expand...
Click to collapse
The build identifiers work like this = 1.53.617.5 <--- current gen unlocked build.
1.53 = primary build ID
.617. = is the carrier specific ID
5 = minor build revision ID
You're partly right. A VZW build would look like (taken from an M9 build) 3.37.605.7 where .605. is the VZW carrier ID. More than likely when they release the update it'll be higher than 1.53.*.*
If you're stock recovery and system then you'll get an OTA notification from VZW whenever their updates are available. There may be an RUU available once the updates are pushed and settled.
The OTA will have a new radio, firmware and system updates for your carrier. You must use matching firmware/system build in order to get the best performance. The firmware is the hardware layer while the system is the software/OS layer.
You should not use new system with old firmware or new firmware with old system files.

Great. Thank you. That helps. I will wait patiently for HTC and Verizon to fix this issue.
Sent from my HTC6545LVW using Tapatalk

dn.lck said:
Great. Thank you. That helps. I will wait patiently for HTC and Verizon to fix this issue.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I know it's a tough spot and being patient can be hard.
I really don't think it'll be long before we see an update for you. The UK and US updates were about 3 weeks apart and we just got our US 1.53.* update a week or so ago. Give it a couple more weeks to pass the carrier approval stage and it'll get pushed out.
For sure, there will be an update. Try to be patient

dn.lck said:
Hi all,
I have a VZW 10 running 1.19. I'm interested in knowing if the connectivity issues, specifically Wi-Fi, have been fixed. The patch notes for 1.53 do address it, but has it been fixed.
I know there are workarounds, but this is a $550 phone. Wi-Fi should work out of the box.
Thanks for your help.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I haven't experienced this exact issue but what I have experienced as a general drop in signal strength on the 10. I have a side-by-side comparison of signal with my m9 versus the 10 and there's a big difference. I'm on prepaid service so I'm planning on switching to AT&T next month just to see if their service is any better. So far no one from T-Mobile has been able to tell me why my service is so bad considering I have two towers less than 1 mile away from where I live, and when I first started service with T-Mobile about five years ago it was fantastic but I would say in the last six months to a year it has started to go downhill
M9
http://dl-1.va.us.xda-developers.co....png?key=SvrxjxJxKPdYWm6IDOupUg&ts=1464048854
10
http://dl-1.va.us.xda-developers.co....png?key=vZKJ8ZMn6jtMzpo2mugVyw&ts=1464049167

Mark112887 said:
I haven't experienced this exact issue but what I have experienced as a general drop in signal strength on the 10. I have a side-by-side comparison of signal with my m9 versus the 10 and there's a big difference. I'm on prepaid service so I'm planning on switching to AT&T next month just to see if their service is any better. So far no one from T-Mobile has been able to tell me why my service is so bad considering I have two towers less than 1 mile away from where I live, and when I first started service with T-Mobile about five years ago it was fantastic but I would say in the last six months to a year it has started to go downhill
M9
http://dl-1.va.us.xda-developers.co....png?key=SvrxjxJxKPdYWm6IDOupUg&ts=1464048854
10
http://dl-1.va.us.xda-developers.co....png?key=vZKJ8ZMn6jtMzpo2mugVyw&ts=1464049167
Click to expand...
Click to collapse
Your answer is simple. It's T-Mobile
Refarmed network and spectrum.

datafoo said:
Your answer is simple. It's T-Mobile
Refarmed network and spectrum.
Click to expand...
Click to collapse
lol

Differences between Verizon and generic factory images?

Using November for example, among others, there is the generic image and Verizon-specific image:
8.0.0 (OPD1.170816.025, Nov 2017)
8.0.0 (OPD3.170816.023, Nov 2017, Verizon)
Note the differences in build numbers. Pixel (1) and Pixel 2s also have similar branches.
I regularly switch SIMs and have always ran the non-Verizon build. In the current case, WiFi calling and enhanced LTE features all work fine.
Question: What do the Verizon builds include, or how are they different than the generic builds?
Also, are they meant for the VZ-branded Pixels or are they meant to be used with VZ SIMs, regardless of VZ-sold or Google-sold?
Lastly, are there differences in the packaged radio? (I can't download them to compare right now.)
Thanks.

That should be the only difference between the generic and the vzw specific images, the radio.

Lawlrus said:
That should be the only difference between the generic and the vzw specific images, the radio.
Click to expand...
Click to collapse
Do you or does anyone know the optimization/differences between the generic and VZ radio?
I wonder if it is better to run the VZ radio w/ other carriers or generic radio w/ VZ? I am running the generic radio w/ VZ now and it seems to work fine (as mentioned in OP). Since I switch to ATT and other carriers and back to VZ, it would be nice to know which radio would work better.

snovvman said:
Do you or does anyone know the optimization/differences between the generic and VZ radio?
I wonder if it is better to run the VZ radio w/ other carriers or generic radio w/ VZ? I am running the generic radio w/ VZ now and it seems to work fine (as mentioned in OP). Since I switch to ATT and other carriers and back to VZ, it would be nice to know which radio would work better.
Click to expand...
Click to collapse
Not sure it's listed anywhere what changes if any they make. I would assume that it would only really matter with their bands, which att does not use as vzw is still currently cdma.
Of all the years of using Nexus devices on vzw, I think an updated radio was an upgrade db wise one time. It's been worse more than better, and I can't remember the last time I updated a radio.
It's rare you can have other system issues from a non updated radio, but unless that happens, I'm a firm believer in not fixing what isn't broken.

I think the other consideration with the Vz version is updates, I wouldn't want Vz getting/delaying updates as you know they will and my understanding is Vz issues the updates for the Vz models.

Delete

SWBgHz said:
I think the other consideration with the Vz version is updates, I wouldn't want Vz getting/delaying updates as you know they will and my understanding is Vz issues the updates for the Vz models.
Click to expand...
Click to collapse
Verizon didn't delay or withhold any update for the original Pixels, what makes you think that they'll do it here? Everyone was delayed for the first update, but I believe Verizon users were the first to start getting the OTA en masse.
Sent from my Pixel 2 XL using Tapatalk

FWIW, I ordered directly from the Google store (the only way to order these devices, lol), and the moment I popped in a VZW SIM I had a 50-some MB update. Afterwards my build number shows the VZW build number per the Google factory images page. So it's clearly tied to SIM cards what it tries to put you on, and although I'm not sure what the difference between the normal and VZW builds are, Verizon delaying updates has nothing to do with it. That's only if you bought your phone through VZW that that would even be a possibility, and honestly they did pretty well with the OG Pixels, afaik

ohlin5 said:
FWIW, I ordered directly from the Google store (the only way to order these devices, lol), and the moment I popped in a VZW SIM I had a 50-some MB update. Afterwards my build number shows the VZW build number per the Google factory images page. So it's clearly tied to SIM cards what it tries to put you on, and although I'm not sure what the difference between the normal and VZW builds are, Verizon delaying updates has nothing to do with it. That's only if you bought your phone through VZW that that would even be a possibility, and honestly they did pretty well with the OG Pixels, afaik
Click to expand...
Click to collapse
I've read the same elsewhere--that the SIM determines the build. I wonder if before the next update, an ATT or TMo SIM is inserted, if the generic build will then be downloaded.
It would be nice to know if the VZ build adds something VZ specific for better support, but still works just the same with other carriers.

imnuts said:
Verizon didn't delay or withhold any update for the original Pixels, what makes you think that they'll do it here? Everyone was delayed for the first update, but I believe Verizon users were the first to start getting the OTA en masse.
Click to expand...
Click to collapse
Don't trust Verizon, plain and simple. 1000 reasons.

snovvman said:
I've read the same elsewhere--that the SIM determines the build. I wonder if before the next update, an ATT or TMo SIM is inserted, if the generic build will then be downloaded.
It would be nice to know if the VZ build adds something VZ specific for better support, but still works just the same with other carriers.
Click to expand...
Click to collapse
My guess would be that (at least Google store ordered devices) start with the generic build, and IF a VZW SIM is inserted then it downloads the differential (~50MB was what mine was) to adjust to the VZW build. I have no way of confirming this as I unfortunately didn't look at the build number prior to SIM insertion and update, but in my simple mind it seems like it could make sense I could be totally off though lol

ohlin5 said:
My guess would be that (at least Google store ordered devices) start with the generic build, and IF a VZW SIM is inserted then it downloads the differential (~50MB was what mine was) to adjust to the VZW build. I have no way of confirming this as I unfortunately didn't look at the build number prior to SIM insertion and update, but in my simple mind it seems like it could make sense I could be totally off though lol
Click to expand...
Click to collapse
Yeah, this is how it works. Multiple people have reported the same. As far as anyone can tell, the only difference between the VZW and the regular firmware is different modem and radio images.

Mine started with OPD1 build. First security update put me at an OPD3 build.

Yeah I don't think any of us are hundred percent sure on this. However I will tell you that I have an unlocked phone from the Google Play Store running on the Verizon network at first I sideload the official Google update and then Just For Kicks When I updated to the November version side-loaded the Verizon specific one. I don't know if it's truly an total but I do think that my network coverage has been maybe just a little bit better than it was previously. Could also be a placebo effect

I wonder if the last 2 Builds, which have separate builds for TMO, contain LTE Band 71...

confused... t-mobile firmware stock OTA???

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.