My wife (God, I LOVE that lady!) bought me, totally by surprise, the LTE version of the Tab S6 for Christmas. I thought that by putting a T-Mobile SIM in, I would be getting software updates via TMB, but I think I misapprehended that. When I look under settings > software version, I have a CSC that is XEO/XEO/, not the expected TMB and whatnot. I think that's the Polish version, but I don't really know for sure. The whole CSC code thing is not something I'm really familiar with and haven't had to deal with.
Can anyone tell me if I need to go to the TMB version and, if so, point me in the right direction? I am NOT interested in rooting this device. I played the root/ROM in the past and had a good time doing it but I am way too busy now and don't have the time nor the inclination to get involved in it again. Plus, frankly, this thing is flawless as far as I'm concerned and will only get better with the OneUI 2.1 update that's supposedly coming this way.
And one other thing....
I used to be able to designate what bands were used by my device. I have searched all over the place for instructions for this one and nothing works. Or, I haven't been able to make anything work (could be user error, I know). I am really disappointed with the reception that I get on this - it is newer and larger than my Note9 but gets much worse reception. That was NOT the case when I compared my Note4 to my Tab S2 - the S2 had MUCH better reception and I was able to use Google Voice to make calls with my Tab S2 in places where my N4 simply didn't see any service at all.
Any help is appreciated!
TIA!
I'm no expert, but a quick Google shows me XEO/XEO is indeed the Polish model and that it is unbranded - So, you'll just get regular OTA updates direct from Samsung over WIFI - It doesn't matter which SIM you're using, all T-Mobile will provide is service reception. So, no need to change CSC unless there are specific carrier services you need/want to access. The only difference I can imagine you'll experience between an XEO and something like a BTU version is that the default language offered when you set up your Tab may be Polish instead of, in this example English - Rectifying that would be as simple as selecting English from the drop down menu.
I guess worst case scenario if you don't receive updates automatically from Samsung is to download them manually and flash with Odin.
Related
This is more of a general question and not really expecting a true answer from any mobile companies. But why do they insist in either locking their handsets, or preventing them from getting the latest firmware upgrades from the phone manufacturers?
Take the S3 on T-Mobile for example, why have they disabled he update feature? They have put on their own version of the firmware that does nothing different from the official except for disabled updates, no splash screen, no extra apps or other branding, just no official updates? Why?
Why prevent the phone from getting the latest updates from the actual people that made them?
To control content. When you control content, you control the all mighty dollar.
Plus, unless there is a bug that just flat out cripples the device, frequent updates are a bad thing for carriers. Risk of a bad flash, returned merchandise/warranty returns, all hits their bottom line. In other words, they have zero skin in the game to get you the latest/greatest/fastest/most stable ROM. Plus, it's not like they're in the mobile phone branding business, they could care less if your device is a bit slower than a competing carrier's.
For them, a "good enough," bloated/branded ROM with very little updates fits the bill.
eon_designs said:
This is more of a general question and not really expecting a true answer from any mobile companies. But why do they insist in either locking their handsets, or preventing them from getting the latest firmware upgrades from the phone manufacturers?
Take the S3 on T-Mobile for example, why have they disabled he update feature? They have put on their own version of the firmware that does nothing different from the official except for disabled updates, no splash screen, no extra apps or other branding, just no official updates? Why?
Why prevent the phone from getting the latest updates from the actual people that made them?
Click to expand...
Click to collapse
Actually, branded handsets can receive their own official updates. Samsung will distribute them for the carrier. Much of the issue is that people just see a message and accept an OTA update without really thinking about it. I saw a lot of people have to get warranty repairs on HTC desires due to dodgy flashes etc. It probably cost the carriers loads of money with the logisitics of that issue.
Unbranded updates wouldnt work on branded software. Only the correct branded update, modified and created by the carrier would work on the device. Removing the option to check for updates is not stopping you get any updates. The fact that T-mobile aren't sending you any updates is stopping it. The missing option is pretty much a cosmetic issue.
Two seperate questions really.
As for locking the device, like CMD512 said, a lot of it is control. And while pushing their content vs. other or OEM choices is part of the reason, support is the biggest. Returns, exchanges, and contact center support (phone, e-mail, chat, tiered-escalations) eats up profits. The last stat I heard was about 5-7%. Locking the device so the user can't change it reduces returns and exchanges and simplifies support.
Carriers could care less about updates and what happens to a device after they sell it. You're locked in to a 2-year contract whether they update it or not. They all do eventually but it's not a priority. They also skip what they consider minor updates to avoid the hassle and expense all the support contacts updates create.
Well its a known fact that carrier branded phones are destined to get slow updates with added nuisance of preloaded junk along with alteration in FW just to make the phone more carrier obedient.However if someone is having issue with that then there is an alternative known as unlocked international version, buy it and receive prompt OTA's.
*Bites tongue* This is tricky.
.However if someone is having issue with that then there is an alternative known as unlocked international version, buy it and receive prompt OTA's.
Click to expand...
Click to collapse
The carrier-branded phones have the hardware-id i9300 too and often enough have no network lock. So by all definitions they are unlocked international versions but with carrier branding.
Since these are hardware-version including OTA updates.
d4fseeker said:
The carrier-branded phones have the hardware-id i9300 too and often enough have no network lock. So by all definitions they are unlocked international versions but with carrier branding.
Since these are hardware-version including OTA updates.
Click to expand...
Click to collapse
Isn't it also possible to just call your carrier and get a code so that your device is no longer locked to that carrier? Wouldn't that solve the problem?
maggot_ff said:
Isn't it also possible to just call your carrier and get a code so that your device is no longer locked to that carrier? Wouldn't that solve the problem?
Click to expand...
Click to collapse
I'm thinking the OP is talking about locked bootloader preventing the flashing of custom ROMs and not carrier locking.
Afaik noone except Verizon (surprise, surprise) locks the S3's bootloader. And Verizon-devices got their own forum.
The only issue with the international S3 is that carriers often delay updates or refuse to deliver them which can be circumvented with Odin as described above.
d4fseeker said:
Afaik noone except Verizon (surprise, surprise) locks the S3's bootloader. And Verizon-devices got their own forum.
The only issue with the international S3 is that carriers often delay updates or refuse to deliver them which can be circumvented with Odin as described above.
Click to expand...
Click to collapse
But they don't delay them if you just get the code to unlock your phone. No need for Odin. or am i totally off? I usually buy unbranded phones, so not really an issue for me. Just wondering if i got it right or what.
You're talking about network locking, meaning that only the carrier's SIM card will work with the device.
This is about carrier-branded ROM's which has nothing to do with network lock. Basically it's the carrier getting their hands on the ROM and modifying it so it fits their needs (which usually consist of adding the most possible bloatware)
Sometimes they remove the ability for OTA-updates completely during their processing of the ROM, but usually they only cause huge delays and skipped versions due to quality control (testing, ...) and/or laziness (costs)
To get a non-carrier-branded ROM on the phone you'll have to use Odin. Sometimes Kies mistakes the ROM too and flashs a Samsung-provided ROM but that's not a reliable method. Plus depending on your regional location it still takes long until release.
Thanks for all the replies, very interesting. I know of the Odin approach, very scary and not sure I am up to that task, but really we should not have to do that.
I can understand the carrier wanting to control the firmware release when they stick loads of extra bloat ware on it, bit in the case of the S3 there does not seem to be any?
Seems like a waste of time to the carrier IMHO
d4fseeker said:
You're talking about network locking, meaning that only the carrier's SIM card will work with the device.
This is about carrier-branded ROM's which has nothing to do with network lock. Basically it's the carrier getting their hands on the ROM and modifying it so it fits their needs (which usually consist of adding the most possible bloatware)
Sometimes they remove the ability for OTA-updates completely during their processing of the ROM, but usually they only cause huge delays and skipped versions due to quality control (testing, ...) and/or laziness (costs)
To get a non-carrier-branded ROM on the phone you'll have to use Odin. Sometimes Kies mistakes the ROM too and flashs a Samsung-provided ROM but that's not a reliable method. Plus depending on your regional location it still takes long until release.
Click to expand...
Click to collapse
Ahhh.. Ok Thanks a lot. And how exactly would one go about to do that? Just flash a different firmware with odin? I think my GF's S3 is has a carrier branded rom, as my phone got official updates a lot sooner than hers. I have no clue about all this stock stuff. I just always root and update when i feel like it. She doesn't want me to rooth hers, but she wants to get updates quickly, so if you could just send me a link to a guide or quckly explain in PM i would appreciate it. Sorry for going off-topic.
d4fseeker said:
Basically it's the carrier getting their hands on the ROM and modifying it so it fits their needs (which usually consist of adding the most possible bloatware)
Click to expand...
Click to collapse
It's also different between the U.S. carriers and the rest of the world. In the U.S. the phones get specific model numbers, have their physical radios configured differently, have OEM features omitted (h/w and s/w), and are tweaked to perform differently. Elsewhere it's usually a carrier splash screen and some fairly harmless carrier apps. The SGS3 is the closest to unmolested of any phone offered to date by the U.S. carriers. Other than the swap of Exynos for S4 of course. And Verizon locking the bootloader.
Hey guys,
I have a pretty unique problem and im not sure there even is a solution, but here goes.
The story is that I had been living in Canada for the last 7 months or so and bought myself a shiny new Desire 601 from Virgin Mobile (its a zara_ul). Since then, I have managed to brick it hardcore style, but i was able to ressurect it after 4 months of fruitless attempts through various odd files, sheer dumb luck, and the RUU from mrplowdans google drive (super props by the way, you saved my phone good sir!). I had to SuperCID the phone in order for the RUU to stick.
So it goes without saying that im now running the Telus version of KK (i updated through the usual OTA once i had returned it to stock 4.2.2) on a VM phone. All good, no issues there. Ive since returned home to Australia, unlocked the phone so it works with an Australian carrier, also all good. Im able to make calls and send texts no issue.
My problem is with mobile data. It seems to be having an issue connecting to my carriers 3g/4g. Initially, there was nothing at all, just the bars in the notification bar telling me that i had a good connection to cellular. No little superscript 3G though, and in settings, although mobile data is 'On', it is showing connection failed. Adding a custom APN appeared to work slightly, the 3G appeared in the notification bar and in settings, mobile data was shown to be 'connected', but still no dice when i try to connect to the web or download an app.
Now i vaguely understand the principles involved here, I get that North american carriers use a different radio frequency to, say, Europe, and that differs again to Australia. My question is, is it on the software side? Would it be possible to find an Australian Radio.img for a desire 601 (i dont even know if they sell them here), flash it, and all will be fine and dandy? Or is it the physical antenna inside the phone that is set to receive only a certain frequency? Im not expecting someone to go and find me a working file or anything, i know most of you live in Canada anyway, but im looking for someone with a greater knowledge of these things to find a theoretical fix.
I know I rant a lot, but in the scheme of things im willing to let this problem slide considering i only just un-bricked it a few days ago AND managed to root 4.4.2 (a significant achievement given my non-existent knowledge of android), but it is a nuicance and if theres something simple i can do of course i will.
Thanks in advance for any help <3
EDIT: Ive since done some googling and discovered that they do sell these phones in Australia, and that the Network specs for it and the canadian model that i have are almost identical, many of the frequencies are the same on both. Leads me to assume that its software sided, the telus radio.img is telling the phone to not see non-canadian frequencies.
Hi folks,
I'm looking to possibly switch to T-Mobile, but I know that coverage is spotty in my home town. (I don't go home often... Maybe once or twice a month for a weekend)
Because of the spotty coverage, wifi calling is a feature of T-Mobile that is very appealing to me, but I've been hearing rumors that their wifi calling feature doesn't work unless you purchase the phone directly from T-Mobile (which obviously cannot be done).
However, I do remember seeing a screenshot of the Xperia Z5 Compact's wifi calling settings and there was a tab listed for T-Mobile. Now why would a phone include wifi calling options for a specific carrier if that carrier refuses to support that phone?
Now let's say there is no way to trick the Z5 into letting me use wifi calling on T-Mobile... I read an article stating that CM13 will support T-Mobile's wifi calling. If CM13 was developed for the Z5C, would that do the trick?
Praying that someone with some more experience can shed some light on this matter. Is there any hope for me?
T-mobile announced that they'll be giving mini towers to customers for free (that's not wifi calling but an actual LTE tower for your house that uses your internet connection) so you can just call them up and ask when they'll start sending them out.
Does it just generate an LTE signal? That works well if the phone had working T-Mobile voice over LTE; which i'm not sure it would if I purchased an unlocked model. That router would be great for my home, but I'm concerned for other areas of my hometown, where I actually would need service (for example: car accident). If I could connect to a local coffee shop's wifi connection to make calls; that would make my life so much easier. I would hate to only have service in my home because that would make me feel bound to my house.
JGoldz75 said:
Does it just generate an LTE signal? That works well if the phone had working T-Mobile voice over LTE; which i'm not sure it would if I purchased an unlocked model. That router would be great for my home, but I'm concerned for other areas of my hometown, where I actually would need service (for example: car accident). If I could connect to a local coffee shop's wifi connection to make calls; that would make my life so much easier. I would hate to only have service in my home because that would make me feel bound to my house.
Click to expand...
Click to collapse
It's only phone based: https://support.t-mobile.com/docs/DOC-24269
FYI, I did use T-Mobile on an unlocked, unsupported phone last year for few months and I don't recall ever not having phone signal. Data is another story but calls were always available and I do travel a lot across the world. Their international data is pure BS - it just doesn't work.
And finally, the T-Mobile WiFi calling menu you saw is for the old T-Mobile in the UK that has now been merged into EE. You can flash that firmware but it probably won't work with the USA version depending on what moron wrote the integration and how much configuration data they hardcoded in the app or if it works it might be connecting to a UK gateway.
weasal said:
It's only phone based: https://support.t-mobile.com/docs/DOC-24269
FYI, I did use T-Mobile on an unlocked, unsupported phone last year for few months and I don't recall ever not having phone signal. Data is another story but calls were always available and I do travel a lot across the world. Their international data is pure BS - it just doesn't work.
And finally, the T-Mobile WiFi calling menu you saw is for the old T-Mobile in the UK that has now been merged into EE. You can flash that firmware but it probably won't work with the USA version depending on what moron wrote the integration and how much configuration data they hardcoded in the app or if it works it might be connecting to a UK gateway.
Click to expand...
Click to collapse
It's not that I think the phone will not have service because it's unlocked. T-Mobile just doesn't have great coverage in my hometown area at all. I did the Test-Drive a couple months back and remember getting 0-1 bars at all times... never holding on to a signal long enough to make a single phone call or send a text message. Thanks for the insight into the T-Mobile - EE thing. I didn't realize that. It would be lovely if it did work in the USA but I doubt it The T-Mobile Nexus 5 (arguably one of the most modded phones out there) never got t-mo wifi calling so I doubt this will.
Thank you!
Just so you know, I flashed to EE (even though technically I'm on MetroPCS which is a T-Mobile subsidiary), and I couldn't find that screenshot in any of the settings menus, nor could I locate it via "settings, under device, call. UK EE" as someone suggested in that thread. I do have a "Device Connection" menu and a "Call" menu, but they're separate menus not nested in one another. And I can't find any menu or option that says "UK EE".
So, it sounds like no one can find any Wifi calling toggle in any settings menu, correct?
nnotis said:
So, it sounds like no one can find any Wifi calling toggle in any settings menu, correct?
Click to expand...
Click to collapse
A couple people have mentioned seeing it...someplace. One person said he saw it under the pencil looking icon in the drop down shade, but I've never been able to locate it up there no matter what firmware I've flashed too. It appears to be pretty elusive.
Adrift98 said:
A couple people have mentioned seeing it...someplace. One person said he saw it under the pencil looking icon in the drop down shade, but I've never been able to locate it up there no matter what firmware I've flashed too. It appears to be pretty elusive.
Click to expand...
Click to collapse
It's probably checking for some condition to show the menu.
If you extract the EE firmware you would probable be able to do a text search for T-Mobile and find the apps that have that then decompile the one that sounds like the most likely to have the functionality (probably one with the word customization in the name) and check the logic which enables the functionality and even change and re-compile it. You would also be able to see if it connects to a specific gateway for the wifi calling and if so try to change that too..
Theoretically a company won't spend the money to develop different Wifi calling mechanisms for different countries and thus it should work but then again...
weasal said:
It's probably checking for some condition to show the menu.
If you extract the EE firmware you would probable be able to do a text search for T-Mobile and find the apps that have that then decompile the one that sounds like the most likely to have the functionality (probably one with the word customization in the name) and check the logic which enables the functionality and even change and re-compile it. You would also be able to see if it connects to a specific gateway for the wifi calling and if so try to change that too..
Theoretically a company won't spend the money to develop different Wifi calling mechanisms for different countries and thus it should work but then again...
Click to expand...
Click to collapse
I wouldn't know how to begin to do all of that.
Adrift98 said:
I wouldn't know how to begin to do all of that.
Click to expand...
Click to collapse
You can follow this to extract the system partition (system.sln) and get it's contents to your hard drive: http://forum.xda-developers.com/showthread.php?t=1723284
Then you can use your file explorer (on Windows or whatever your OS is) to search for a text string (make sure you tell it to look only inside *.apk to avoid getting too many results). Once you find the apk files that could be what you need you can then use this: http://www.decompileandroid.com/ to decompile the apps so you get source code.
From then on it's a bit trickier, you'll need to make your way trough the configuration and maybe even the code to figure out where they store the connection info or what exactly do they connect to (it looks like the app uses your sim card to authenticate so that shouldn't require any tweaking).
Or you can just wait and hope this is true: https://support.t-mobile.com/thread/81359 or maybe it's already in M : http://www.phone-probe.com/android-m-features-native-wifi-calling/
Oh is that all? Simple.
It might be easier to just locate the apps needed for US T-Mobile wifi calling from another phone and install them on a z5c with EE firmware since the core OS code needed would be provided by the EE firmware and the US specific stuff will come from the apps.
This has a list that might actually be complete: http://forum.xda-developers.com/showthread.php?t=2302313 and you can ignore any jar files that are listed since that should come with the EE firmware.
The fact that there is a z5c firmware that supports Wifi calling is what's important here - you have all the proprietary and OS stuff baked in, you just need the US specific bits/configuration.
So I learned the hard way that you can't have it all.
I travel for work quite a bit and I was in the Middle East working when my Verizon S7 Edge started to have problems. I looked for a replacement in Dubai and was happy to find the S9+ at a reasonable price and with the 256GB option (which I wasn't finding in the US). I popped in my Verizon sim and life was good.
Then I returned to the US and. nothing. worked. I had forgotten that Verizon was strictly CDMA in the US and this phone had no CDMA radio.
I also was noticing that the samsung pay app was locked to the UAE version which was annoying but not a huge issue...I couldn't add American Express credit card which may or may not have been due to that region setting.
So in order to actually get service I switched to T-Mobile and have had decent data rates. However the phone doesn't use volte or wifi calling which is very bad since where I am staying is somewhat of a dead spot for mobile coverage. I basically can't receive phone calls here and making a call requires me to wait about a minute for the phone to figure out what protocol to connect to (dowleveling to either a 3g or H to actually connect and dial).
My initial research tells me that I don't want to root the phone and lose all ability to use samsung pay, but I would love to do as much as I can to the phone to get it working as best as possible.
Can someone chime in here to let me know what's possible? I don't want to experiment too much, and it's been rare over the years for me to keep up with all the root/firmware/rom etc. that has become available. My last real era of rooting phones was many years ago with iPhone and even then it was a lot to keep up with.
thanks in advance!
bump.
Anyone?
I had the same issue. I ended up rooting to get TMobile volte/wifi-calling. Also, by rooting you can also use Verizon Wireless; however, only with LTE.
You could use Google Pay lol.
Furthermore, I suck at giving reasons, but that's what I did.
Don't quote me on this, but from what I understand, you can use the patched ODIN and flash the firmware's CSC outside of it's region and change it to XAA. There is also a guide to changing CSC without root that may work as well.
From what I understand, the G965F is unable to load the XAA csc without root since it is only for the Snapdragon version
I ended up using Tekhd's tmobile detonator after I bricked my G965F/DS atleast 3 times. It works great now.
The way to change csc without root is via a combination rom and using Realterm. Using TMB CSC on a global G965F/DS ROM will end up in a PUK code lock. I tried ALL the US CSC on my G965F to confirm this.
Hey everybody,
So recently i bought this international unlocked Galaxy S9+ (SM-965F/DS Exynos processor) off Amazon and it's great, everything is fine with the one major exception being that at home my signal is pretty poor and i get extremely delayed text messages coming in and calls taking forever to dial out or failing to connect. Not a problem, i'll turn on Wi-Fi calling, right? Wrong, option isn't available, some detail: I'm in the US on T-Mobile, updated to the latest Pie OS update, i'm very tech-capable and used to do tier 2 tech support for Verizon. Long story short, I've tried everything in the book including FDR and fresh setup as well as clearing system cache etc. and it's looking like the ONLY solution to get Wi-Fi calling (and subsequently VoLTE that i didn't realize wasn't enabled until researching and checking myself) enabled is to flash the ROM with a T-Mobile OS. Unfortunately i'm coming up negative trying to find the firmware for this phone. Plenty of resources out there for the SM-965U(Snapdragon), but none for the SM-965F(Exynos) as of yet as far as i can tell (and before any ignorance jumps in here as i've seen on other threads, NO the SM-965U software will NOT work on this model phone as it runs a different processor, non-Snapdragon Exynos chipset)
So, that all being said, is anyone out there working on a fix for this, is it likely i'll ever get a fix for this, and/or is the fix already available and I've just completely missed it? Any information or help would be greatly appreciated. Thank you for your time and consideration.
bahruuk said:
Hey everybody,
So recently i bought this international unlocked Galaxy S9+ (SM-965F/DS Exynos processor) off Amazon and it's great, everything is fine with the one major exception being that at home my signal is pretty poor and i get extremely delayed text messages coming in and calls taking forever to dial out or failing to connect. Not a problem, i'll turn on Wi-Fi calling, right? Wrong, option isn't available, some detail: I'm in the US on T-Mobile, updated to the latest Pie OS update, i'm very tech-capable and used to do tier 2 tech support for Verizon. Long story short, I've tried everything in the book including FDR and fresh setup as well as clearing system cache etc. and it's looking like the ONLY solution to get Wi-Fi calling (and subsequently VoLTE that i didn't realize wasn't enabled until researching and checking myself) enabled is to flash the ROM with a T-Mobile OS. Unfortunately i'm coming up negative trying to find the firmware for this phone. Plenty of resources out there for the SM-965U(Snapdragon), but none for the SM-965F(Exynos) as of yet as far as i can tell (and before any ignorance jumps in here as i've seen on other threads, NO the SM-965U software will NOT work on this model phone as it runs a different processor, non-Snapdragon Exynos chipset)
So, that all being said, is anyone out there working on a fix for this, is it likely i'll ever get a fix for this, and/or is the fix already available and I've just completely missed it? Any information or help would be greatly appreciated. Thank you for your time and consideration.
Click to expand...
Click to collapse
I'm currently researching the very same issue... So far i hypothesize , with no knowledge, that if it is rooted, you can then change the csc settings and configure it for TMO, thus enabling WiFi calling. If someone can confirm, that'd be great, otherwise i'm trudging slowly to verify.
Root and use tekhd detonator.
CynicalHeight00 said:
Root and use tekhd detonator.
Click to expand...
Click to collapse
Well i looked at this and it looks like a non-stock rom i'm sure wrought with problems that unfortunately is not helpful. My goal here is to have my phone work and continue to get standard updates with original and licensed (more or less) software and have it actually work. I'm not interested in a full OS replacement pre-loaded with a bunch of adblockers and other crap the designer thought would be useful, just want my standard features enabled and nothing else to change if at all possible. Also, if you believe my statement here is in error please explain, your one line really isn't very helpful, and nowhere on their website is there any description as to what tekhd detonator does / is supposed to do / what it will break. I'm certainly not risking bricking my phone when their own website says under all of its S9+ related material that it's for Snapdragon which the variant i have again doesn't use Snapdragon.
bahruuk said:
Well i looked at this and it looks like a non-stock rom i'm sure wrought with problems that unfortunately is not helpful. My goal here is to have my phone work and continue to get standard updates with original and licensed (more or less) software and have it actually work. I'm not interested in a full OS replacement pre-loaded with a bunch of adblockers and other crap the designer thought would be useful, just want my standard features enabled and nothing else to change if at all possible. Also, if you believe my statement here is in error please explain, your one line really isn't very helpful, and nowhere on their website is there any description as to what tekhd detonator does / is supposed to do / what it will break. I'm certainly not risking bricking my phone when their own website says under all of its S9+ related material that it's for Snapdragon which the variant i have again doesn't use Snapdragon.
Click to expand...
Click to collapse
This is going to be a hassle trust me. even with the Snapdragon models from different CSCs VoLTE and Wifi Calling do not carry over. An ATT 965U would have to be reflashed with the TMobile CSC and USERDATA files to get access to TMobile features. U are trying to do this with an Exynos model. I think you would have to root and install a custom firmware that has the TMobile USERDATA embedded.
Good luck.
can the U1 be flashed to the verizon u firmware? i thought i read someone tried this, but suspected it didn't work because he had previously used the phone with verizon with the unlocked firmware...
methcat said:
can the U1 be flashed to the verizon u firmware? i thought i read someone tried this, but suspected it didn't work because he had previously used the phone with verizon with the unlocked firmware...
Click to expand...
Click to collapse
You can flash the G965U onto the G965U1 and vice versa. It's been well documented that this will let us go from one carrier firmware to another as well as let us have the unbranded carrier firmware. The only catch to this is the bootloader version of the firmware your wanting to flash. The firmware one wishes to flash must have a bootloader version equal too (or greater then) what is currently on the phone.
If your trying to ask about flashing the U1 onto an exynos variant then the answer is definitely no. You can't flash firmware from a different model onto a different model.