Develop Bugs

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.

[ASHB] OTA Firmware + September security patch download available

Enjoy

hayabusa1300cc said:
Enjoy
Click to expand...
Click to collapse
It's not available for my us unlocked version yet

Sent from my SM-N975U using Tapatalk

my370z said:
It's not available for my us unlocked version yet
Click to expand...
Click to collapse
Unlocked typically gets the update after all the carriers push out their update. It's the downside of buying the unlocked version.

I kinda don't understand this. How are these updates linked to carriers? I thought these updates are made available over the internet, so if I am on wifi internet, with no sim inside my phone, what any carrier has to do with this update? What am I missing here? These updates are not available on samsung servers?
I recently bought a Nokia 8110 4g phone. Tried to update its firmware with no success over wifi (KaiOS). As soon as I took out the SIM, it found the update and updated with no problem.
Why my Note 10+ would be linked to any carrier? I did not bought it through a carrier and it is not unlocked. It is bought from Singapore and it is SM-N975F/DS (Global) version, while I am being in Europe.
Can someone shed some light into this?

Samsung holds on the Unlocked firmware update until the carrier's start pushing. At least in the USA.

Yeah, but it is unclear to my what is "carrier pushing" and why it is needed. Over the internet, Samsung servers could do this w/o any form of carrier involvement or knowledge. Why "carrier" is in in this chain?!? It is like my Windows would be updated only when my internet service provider wants it.

big_ipaq said:
Yeah, but it is unclear to my what is "carrier pushing" and why it is needed. Over the internet, Samsung servers could do this w/o any form of carrier involvement or knowledge. Why "carrier" is in in this chain?!? It is like my Windows would be updated only when my internet service provider wants it.
Click to expand...
Click to collapse
Exactly, Google and handset manufacturers need to step in! Imagine if Apple let carriers modify iOS! That would never happen! That was a good analogy by the way! :good:

big_ipaq said:
I kinda don't understand this. How are these updates linked to carriers? I thought these updates are made available over the internet, so if I am on wifi internet, with no sim inside my phone, what any carrier has to do with this update? What am I missing here? These updates are not available on samsung servers?
I recently bought a Nokia 8110 4g phone. Tried to update its firmware with no success over wifi (KaiOS). As soon as I took out the SIM, it found the update and updated with no problem.
Why my Note 10+ would be linked to any carrier? I did not bought it through a carrier and it is not unlocked. It is bought from Singapore and it is SM-N975F/DS (Global) version, while I am being in Europe.
Can someone shed some light into this?
Click to expand...
Click to collapse
Same thought. I stay here in Singapore & I bought it directly from Samsung, until now no OTA update. In Singapore, network providers never lock any smartphone, but 3 major networks here have different CSC (SIN/STH/MM1), mine was the non-network Singapore CSC which is XSP, still to no avail. I am forced to update via odin because of this.

big_ipaq said:
Yeah, but it is unclear to my what is "carrier pushing" and why it is needed. Over the internet, Samsung servers could do this w/o any form of carrier involvement or knowledge. Why "carrier" is in in this chain?!? It is like my Windows would be updated only when my internet service provider wants it.
Click to expand...
Click to collapse
This is because the carriers can customise the firmwares for their network. (add in extra apps; turn options on or off etc.) so therefore the carriers have to approve each and every new firmware that's developed by Samsung.
Samsung will do the actual "pushing" of the carrier-cusomised firmware, but only once the carrier gives them permission to do so.

stuclark said:
This is because the carriers can customise the firmwares for their network. (add in extra apps; turn options on or off etc.) so therefore the carriers have to approve each and every new firmware that's developed by Samsung.
[...]
.
Click to expand...
Click to collapse
This is most probably stupid and needs to stop.

big_ipaq said:
This is most probably stupid and needs to stop.
Click to expand...
Click to collapse
That's highly unlikely to happen.
Carrier customisations are fundamental to how the industry is currently working

Can you give me a sample of this "carrier customization"? Fundamental to carriers or to us the customers?

It's most likely contractual.

So essentially, Samsung waits for the carriers to modify their firmware, release that first then release their UNCHANGED firmware/security patch to the unlocked devices...
That is such a crap model. Common sense would say to release what you can first... This would also push the carriers to release these updates in a much timelier manner as there is no benefit to be on carrier software if the patches are months behind the unlocked devices...

ultramag69 said:
So essentially, Samsung waits for the carriers to modify their firmware, release that first then release their UNCHANGED firmware/security patch to the unlocked devices...
That is such a crap model. Common sense would say to release what you can first... This would also push the carriers to release these updates in a much timelier manner as there is no benefit to be on carrier software if the patches are months behind the unlocked devices...
Click to expand...
Click to collapse
LOL, you must be new to Samsung devices!
I kid, I kid. But seriously. It sucks, but it's reality. Benn that way since at least the S8.

I don't show any updates available for my Korean 10+ 5g yet either

Mr. Orange 645 said:
LOL, you must be new to Samsung devices!
I kid, I kid. But seriously. It sucks, but it's reality. Benn that way since at least the S8.
Click to expand...
Click to collapse
This has been the case since the Galaxy S2, if not earlier.
I suspect (but don't know) that Samsung have some form of contractual obligation to the networks to not release any new features etc. until the network devices (don't forget some networks may have paid a lot to Samsung to have an "exclusive" on the handset when it was released) have had a chance to get said feature.

stuclark said:
This has been the case since the Galaxy S2, if not earlier.
I suspect (but don't know) that Samsung have some form of contractual obligation to the networks to not release any new features etc. until the network devices (don't forget some networks may have paid a lot to Samsung to have an "exclusive" on the handset when it was released) have had a chance to get said feature.
Click to expand...
Click to collapse
Didn't even realize they had unlocked models going back that far. I has an S3 and a Note 2, but back then I was on Verizon so there was no thought of carrier unlocked models. It was a V model or nothing, LOL. My next Galaxy after those was an S7Edge, but they were all still carrier exclusive models. I had T-Mobile by them, so I had a G935T. They eventually came out with a G935U, I think, but I never had one.
It wasn't until the S8/+ they had the universal hardware for all carriers, and that's also when I really got back into the Samsung devices and started flashing U1 and U firmware. That was my first experience with unlocked vs carrier model updates. I didn't realize the update situation had been that way since nlthr S2, other than Samsung has always been slow with updates.
Yeah, I said earlier it was likely contractual. Like you I don't know that for sure, but that's the only thing I can think of.

big_ipaq said:
Yeah, but it is unclear to my what is "carrier pushing" and why it is needed. Over the internet, Samsung servers could do this w/o any form of carrier involvement or knowledge. Why "carrier" is in in this chain?!? It is like my Windows would be updated only when my internet service provider wants it.
Click to expand...
Click to collapse
because some carriers like to test the updates and ensure their services andbloatware are working before pushing an update.. last i checked tho sprint and tmobile use Samsung fota servers.. vzw of course just has to use their own servers.. att does as well..
even if u sign up to use samsungs efota advanced it clearly indicates will not work with vzw or att devices...
as far as the rest of the world i have no idea lol

GWA2 LTE Unlocked Variant updates

So I got a GWA2 LTE Unlocked variant. I used it on AT&T for about a month or two before I took it off of my mobile plan. After I did that I had to fully reset the watch which ended up seemingly downgrading its firmware to out of the box status. Every time I try to check for an update it tells me that my watch is in fact up-to-date which I honestly don't believe it really is. I've seen a few different firmware versions around the net that's seem to surpass my own. if anyone could help with actually finding the real latest software or explain to me why my watch won't update just as if it was a Bluetooth model now. Screenshots will be attached to show what firmware version and such that I'm on.
I have an SM-R825U btw.

IMHO this is correct... you have the US device...
http://fota-cloud-dn.ospserver.net/firmware/ATT/SM-R825U/version.xml
https://doc.samsungmobile.com/SM-R825U/ATT/doc.html
Code:
R825USQU1[B]ASI1[/B]/R825UOYN1ASI1/R825USQU1ASI1
Best Regards

adfree said:
IMHO this is correct... you have the US device...
http://fota-cloud-dn.ospserver.net/firmware/ATT/SM-R825U/version.xml
https://doc.samsungmobile.com/SM-R825U/ATT/doc.html
Best Regards
Click to expand...
Click to collapse
So I actually do have the latest? How about that.
So does this mean I should still receive updates in the future without it being on a mobile network?

yes, through your Galaxy Gear app

Trying to get samsung pay on a device (s20+) without it - maybe changing CSC?

Hello.
Here's the back story. Bought my phone from Egypt unlocked s20 plus. Recently moved to canada and trying to get samsung pay to work. Downloaded the app from google play canada but it says that device is not supported. Downloaded it from APK mirror but it just says it needs to update, even though this is the last version.
I was told that getting the BTU or DBT CSC might fix this, since they come preinstalled with samsung pay.
First of all, can I do this by just flashing the firmware (not changing CSC)? Or do I need to change the CSC using samkey? I don't mind flashing first, if that didn't work then using samkey. But would rather go with the route that people think will work straight away.
I'll write all my device's info that I think might be needed to make this as complete as possible. Then I'll put some questions that are confusing me.
So to start this, I bought my phone from Egypt and I'm currently in Canada. Since it's a dual sim model, I have a Canadian SIM as my primary and Egyptian as my secondary. Currently, I'm getting wifi calling but not VoLTE. Reading a bit on this, some people are saying that my network intentionally locked people out of this option if they didn't buy the phone from them. My network is Fido btw.
Model: SM-G985F/DS (4G)
Product Code: SM-G985FZADEGY
PDA: G985FXXU4BTIB
CSC: G985FOXM4BTID
Basebad: G985FXXU4BTI6
Bootloader: G985FXXU4BTIB
September Security Patch.
One thing I'd like to point out is typing "*#243203855#" in the dialer does nothing. Maybe it's because it's not supported? Or the fact that I have dual IMEI?
Questions:
1. Is there benefit of using DBT over BTU?
2. With my bootloader being BIT 4 (I think?), can I use samkey? When I checked it, it said that they only support BIT 1 and 2 on their website. I could be wrong.
3. Is it safe to purchase samkey credits off ebay?
4. Is samkey itself safe? It showed up as a trojen when I installed it. Could be a false positive? Downloaded from the official site btw.
5. Is flashing BTU enough for this to work or do I need to change the CSC?
6. Can I revert any changes that I've done to restore the device in its original state? If I change the CSC, can I revert it back to EGY?
7. Will I get normal OTA updates while I'm here in canada? This applies to both flashing and/or changing my CSC?
8. I would love to keep wifi calling, call HD, and hopefully get VoLTE (but I understand that this might work). And obviously the main reason for this whole thing is getting Samsung Pay to work.
Sorry if these questions might be obvious, I'm really trying to understand this so I don't ruin anything and don't regret anything.
If someone is willing to help me further, I would greatly appreciate it.

I am unsure about majority of the things you have question about, but one thing i know for sure - samsung pay on my s20+ was rarely working making me look stupid at the shops - since i switched to google pay all issues are gone and payment is going through everywhere

Klopers33 said:
I am unsure about majority of the things you have question about, but one thing i know for sure - samsung pay on my s20+ was rarely working making me look stupid at the shops - since i switched to google pay all issues are gone and payment is going through everywhere
Click to expand...
Click to collapse
The one thing that I care about with samsung pay is the magnetic card replication. I forgot what it was called MTP, or something? This is something that doesn't work with google pay.

krusion said:
The one thing that I care about with samsung pay is the magnetic card replication. I forgot what it was called MTP, or something? This is something that doesn't work with google pay.
Click to expand...
Click to collapse
The MST function was disabled in 2019 for all the smartphones sold within the EU (at least) due to a new regulation regarding MST technology.
I don't know if it's working elsewhere.
Still, for me SPAY has been working flawlessly for over an year or two, never had any problem, with or without MST

phrancini said:
The MST function was disabled in 2019 for all the smartphones sold within the EU (at least) due to a new regulation regarding MST technology.
I don't know if it's working elsewhere.
Still, for me SPAY has been working flawlessly for over an year or two, never had any problem, with or without MST
Click to expand...
Click to collapse
Oh? This might actually be useless than. So this is a hardware change or a software one? Since mine was bought from Egypt. I plan to flash the UK software on there. I'm not sure if it'll have it or not in this case. I guess without MST, what's the point of using samsung pay over google pay?

Question Flashed ATT firmware to VZW S22 901U - Still has VZW splash screen and software?

So I flashed the ATT firmware S901USQU1AVC8 to my Verizon S22 901U and the starting splash screen is still the Verizon logo and when I start the setup process it still requires Verizon activation via wifi and asks to login to Verizon account to use their "My Verizon" app.
I flash BL, AP, CP, CSC via Odin
Any way to get all ATT branding, splash screen, and apps?

The U vs the U1 variant may use different hardware... be warned. This is true with N10+ N975U vs N975U1. The C post pcb is completely incompatible between them. You see where this is going if the firmware controlling the hardware is different.

blackhawk said:
The U vs the U1 variant may use different hardware... be warned. This is true with N10+ N975U vs N975U1. The C post pcb is completely incompatible between them. You see where this is going if the firmware controlling the hardware is different.
Click to expand...
Click to collapse
I'm not using a U1, just a U and U firmware.

MrBaltazar said:
I'm not using a U1, just a U and U firmware.
Click to expand...
Click to collapse
Just be careful as AT&T is partnered with Samsung and actually influence the software and hardware used in many cases.
I'm not familiar with Verizon's practices.
Personally I leave the firmware alone; I don't upgrade or update if the phone is running well.
This N10+ in my hand is still running well on Pie.

blackhawk said:
Just be careful as AT&T is partnered with Samsung and actually influence the software and hardware used in many cases.
I'm not familiar with Verizon's practices.
Personally I leave the firmware alone; I don't upgrade or update if the phone is running well.
This N10+ in my hand is still running well on Pie.
Click to expand...
Click to collapse
I'm just trying to get all carrier services and branding from ATT working on the phone. Flashed the ATT firmware, not sure why or how Verizon branding is even still there?

MrBaltazar said:
I'm just trying to get all carrier services and branding from ATT working on the phone. Flashed the ATT firmware, not sure why or how Verizon branding is even still there?
Click to expand...
Click to collapse
Unless you want vid calling, the wifi stuff or maybe tethering (not sure if needed), I wouldn't worry about it. On my AT&T N10+ all AT&T apps and services are disabled. It runs fine.
My unlocked N10+ runs the same. I don't use vid calling or wifi.

Holy **** there's a ton of misinformation on here.
You need to flash the U1 software FIRST, then flash the AT&T software after that. You can't flash from carrier straight to another carrier. It even says this in the U1 firmware thread, in the very first post.
Personally, I'd just leave it as the U1 version.

entropism said:
Holy **** there's a ton of misinformation on here.
You need to flash the U1 software FIRST, then flash the AT&T software after that. You can't flash from carrier straight to another carrier. It even says this in the U1 firmware thread, in the very first post.
Personally, I'd just leave it as the U1 version.
Click to expand...
Click to collapse
I really don't know but do know that hardware is different on the AT&T Snapdragon from the unlocked variant. Is the Verizon using the same C port PCB as AT&T? Probably not.
Who knows unless you check the PN, if not the same it will puke on you... cam module may be a different PN too another member said. The C port PCB definitely is; apart and verified. The C port pcb is tied into phone and internet access
My unlocked N10+ has just about the same amount of bloatware as my AT&T variant*, all which is useless and package disable. As long as it has VoLTE and internet there's no point as to which version you use... pretty much same-same.
Lol, I hate the AT&T splash screen.
*the disable list is nearly identical less AT&T apps. Actually used the disable list imported from the N975U to set up the N975U1 Package Disabler

You’re 100% wrong here. All US models are absolutely identical hardware wise. Has been for years. If you have proof otherwise, please feel free to link it here.

entropism said:
You’re 100% wrong here. All US models are absolutely identical hardware wise. Has been for years. If you have proof otherwise, please feel free to link it here.
Click to expand...
Click to collapse
WRONG... maybe. I'll find out in a few months when I replace the battery again.
*Unfortunately I don't have images of the two different c port pcbs as the phone was apart.
I wish I did have the P/N to avoid getting the wrong part without pulling the rear cover first.
It was a repair shop and I really wish I had wrote down both numbers now. Ended up putting the old one back in.

entropism said:
Holy **** there's a ton of misinformation on here.
You need to flash the U1 software FIRST, then flash the AT&T software after that. You can't flash from carrier straight to another carrier. It even says this in the U1 firmware thread, in the very first post.
Personally, I'd just leave it as the U1 version.
Click to expand...
Click to collapse
Even though I don't have a U1 model? I have a regular S22 U model.

Correct. To flash from carrier to carrier, you need to go to U1 first. Personally I’d just stay on U1.

I have an unlocked S22 ultra....I tried to ODIN newer software a few months ago and I didn't put the HOME CSC in there and left it blank. Well, it completely erased everything (stupid me) and I had to start from scratch all over again. I was so mad at myself for not doing a backup before I tried to flash. Can the experts who have been doing this longer than I have tell me exactly what I need to do to make sure nothing gets erased and all of the settings stay in tact? I downloaded the newest S908USQS2AVDC TMB version. Is this going to put TMobile on my phone where I need to freeze apps I don't want or how do I carry over from the version I have now (S908U1UEUAVC8)? Or do I need to specifically wait for the unlocked version of the software?

phillthedrill said:
I have an unlocked S22 ultra....I tried to ODIN newer software a few months ago and I didn't put the HOME CSC in there and left it blank. Well, it completely erased everything (stupid me) and I had to start from scratch all over again. I was so mad at myself for not doing a backup before I tried to flash. Can the experts who have been doing this longer than I have tell me exactly what I need to do to make sure nothing gets erased and all of the settings stay in tact? I downloaded the newest S908USQS2AVDC TMB version. Is this going to put TMobile on my phone where I need to freeze apps I don't want or how do I carry over from the version I have now (S908U1UEUAVC8)? Or do I need to specifically wait for the unlocked version of the software?
Click to expand...
Click to collapse
Too bad about not having backed up first. But in some ways, you might be better off not having attempted to transfer all your personal data along with the new firmware. I have read here and elsewhere that the process is more likely to fail when attempting to transfer the personal data concurrently.
Hope everything worked out to your satisfaction.