I just switched over from AT&T to T-Mobile. My Z2 force is AT&T version so it is loaded with AT&T SW and Security patch. Can I switch the SW & security patch to T-Mobile specific ?
Thanks,
Ching-Ho Cheng
ditto
My understanding of this is that you can only use offline tools (LMSA) to update Android Security Patches. And of course, you can't get to Pie, because Motorola hung us out to dry.
Thanks for the response. I bought an unlocked Z4 (non carrier specific) now. The AT&T specific z2 force had difficulty to make call, not even WiFi calling (AT&T disabled WiFi calling in z2 force); only data/wifi worked fine. With Z4, I have no problem to make call or WiFi call.
Related
Hello everyone,
Yes, I'm a noob here but online research, etc. tells me that XDA is the place for me. I am a IT tech, just not a programmer nor have I done a lot with flashing phones, etc.
based on some basic searching my issues seems to be common.
I am a T-Mobile user and I now have a new AT&T Branded Galaxy S9 SM-G960U. I paid a third party to provide me with a Samsung unlock code. I unlocked the phone last night, had T-Mobile update my account with my new Nano Sim, etc.
All is working except I can not enable WiFi Calling and of course there are some advanced text messaging features that I can not enable, i.e. sent receipts, etc. I tested the phone with a active AT&T sim and the features work fine.
Does anyone have a work around for getting WiFi calling and text features to work using the T-Mobile Sim?
Do I need to some how flash a T-Mobile ROM to the phone?
Any help and guidance would be greatly appreciated
it will never work because is att brand. you needed to get international model.
I'm not so sure.......... I have the SM-960u1 and have flashed various AT&T FW to it at least 50 times and cannot get any IMS features to work. I get get the ATT bloatware, software,splash screen. But no VoLTE, WiFi Calling etc. I am tired of flashing. Back to Stock U1 for me.
AT&T is the same. They keep promising wifi calling for unlocked phones but I can't get it and neither can 2 others I know with unlocked phones.
This sounds normal. I have an AT&T branded Galaxy S6, which has wifi calling, but I'm using a MintMobile (T-Mobile) SIM. Wifi Calling is grayed out. There's probably some sort of check in the software that only enables the wifi calling if you are using an AT&T sim.
Yes, you have to flash the T-Mobile firmware with the latest modded Odin, or the unlocked U1 variant firmware (for which TMO's RCS messaging and video calling won't work-with U1 firmware, I mean). If you flash the TMO firmware, it's for all intents and purposes turning the phone into aTMO phone, with bootscreen, bloat and all.
jrockz5000 said:
Hello everyone,
Yes, I'm a noob here but online research, etc. tells me that XDA is the place for me. I am a IT tech, just not a programmer nor have I done a lot with flashing phones, etc.
based on some basic searching my issues seems to be common.
I am a T-Mobile user and I now have a new AT&T Branded Galaxy S9 SM-G960U. I paid a third party to provide me with a Samsung unlock code. I unlocked the phone last night, had T-Mobile update my account with my new Nano Sim, etc.
All is working except I can not enable WiFi Calling and of course there are some advanced text messaging features that I can not enable, i.e. sent receipts, etc. I tested the phone with a active AT&T sim and the features work fine.
Does anyone have a work around for getting WiFi calling and text features to work using the T-Mobile Sim?
Do I need to some how flash a T-Mobile ROM to the phone?
Any help and guidance would be greatly appreciated
Click to expand...
Click to collapse
i think your own question just answered you:
tmobile sim on a branded phone (att)
jrockz5000 said:
Hello everyone,
Yes, I'm a noob here but online research, etc. tells me that XDA is the place for me. I am a IT tech, just not a programmer nor have I done a lot with flashing phones, etc.
based on some basic searching my issues seems to be common.
I am a T-Mobile user and I now have a new AT&T Branded Galaxy S9 SM-G960U. I paid a third party to provide me with a Samsung unlock code. I unlocked the phone last night, had T-Mobile update my account with my new Nano Sim, etc.
All is working except I can not enable WiFi Calling and of course there are some advanced text messaging features that I can not enable, i.e. sent receipts, etc. I tested the phone with a active AT&T sim and the features work fine.
Does anyone have a work around for getting WiFi calling and text features to work using the T-Mobile Sim?
Do I need to some how flash a T-Mobile ROM to the phone?
Any help and guidance would be greatly appreciated
Click to expand...
Click to collapse
You will need to flash to the U1 Firmware then Flash the T-Mobile firmware. AT&T's Wifi Calling is proprietary and thus their phones software won't work with other Carrier's Wifi Calling.
Hi all, I switched providers today from Verizon to AT&T and my S9 is working fine with voice, data and TXT however voice mails is messed up, I had to get AT&T Visual Voice Mail from APK mirror because my voice mail wasn't working and still not dialing from the dial pad when I press and hold 1 as in the AT&T native phones.
Anyways I would like to use WiFi calls and other native AT&T features, so is it possible to flash AT&T firmware on my Verizon S9 via Odin or so???
Can anyone please direct me to the process/firmware? I am also concerned about the firmware updates that I might not get from AT&T if my S9 remains on VZW firmware.
Thank you in advance!!
Flash this OTA https://firmware.science/download?url=52758/1488/SS-G960USQU3ARG7-to-U3BRH6-UP and you'll have the BYOD update. Another thing, wifi calling on AT&T will not work at all because your IMEI is not part of the whitelist in their system to use it. I think the same goes for VoLTE but I'm not sure.
FatalONEM8 said:
Flash this OTA https://firmware.science/download?url=52758/1488/SS-G960USQU3ARG7-to-U3BRH6-UP and you'll have the BYOD update. Another thing, wifi calling on AT&T will not work at all because your IMEI is not part of the whitelist in their system to use it. I think the same goes for VoLTE but I'm not sure.
Click to expand...
Click to collapse
Thank you for the feedback FatalONEM8.
After I manually flash, do you know if the next OTAs will come automatically or I will have to manually flash them forever?
Not having access to WiFi calling is a bummer but well, if everything else works I will have to leave with
By the way my current firmware is G960USQS3ARG8, I checked and the upgrades available are G960USQU3BRH6 and G960USQS3ARH7. The later seems to be an add on by the size of it, should I apply both?
Thanks again!!
I have a Galaxy S9 (SM-960U) purchased from T-Mobile, but unlocked and running with an AT&T SIM (among others, at times). Up until today, the phone was running the stock T-Mobile ROM which received various software updates on a monthly or every two month interval. I've installed them as they were released (while running various non-T-Mo SIM cards) and the latest was October 1, 2018. Today, I clicked the "Software Update" function and saw that a new update was available. When it installed and restarted, I noticed that the phone was running an AT&T branded ROM, along with the typical AT&T bloatware (e.g., CNN, Groupon, Amazon, AT&T-specific apps) that was not previously installed.
The other thing I noticed was that the phone now is only connecting to HSPA and HPSA+ networks, whereas before it would also connect to LTE.
I'm not sure why I suddenly received and installed an AT&T-branded ROM today when my S9 and all of my previous devices were fine running the T-Mo ROM and receiving updates as they were released. Does anyone have any insights as to what caused this change and whether future ROM updates will be carrier-specific based on the inserted SIM? In the past month I've used SIMs in Vietnam and Japan and it seems odd that ROMs would suddenly be based on the carrier of the day.
Also, any ideas about restoring LTE service? I've tried removing the SIM and powering off the device a few times, but no dice. This was a network/account-problem when I initially ported over to AT&T from T-Mo which took a lot of troubleshooting at the store (unsure of actual root cause), but it seems odd that a software update on the device would undo that.
The latest update (3BRJ5) is BYOD firmware. With B firmware, a carrier sim will change the csc of your phone to match the network you are connected on. Good luck getting LTE back, I have no idea on that.
*#*#4636#*#* entered into phone dial. That will allow to select preferred network type in device information.
jasonw3 said:
I have a Galaxy S9 (SM-960U) purchased from T-Mobile, but unlocked and running with an AT&T SIM (among others, at times). Up until today, the phone was running the stock T-Mobile ROM which received various software updates on a monthly or every two month interval. I've installed them as they were released (while running various non-T-Mo SIM cards) and the latest was October 1, 2018. Today, I clicked the "Software Update" function and saw that a new update was available. When it installed and restarted, I noticed that the phone was running an AT&T branded ROM, along with the typical AT&T bloatware (e.g., CNN, Groupon, Amazon, AT&T-specific apps) that was not previously installed.
The other thing I noticed was that the phone now is only connecting to HSPA and HPSA+ networks, whereas before it would also connect to LTE.
I'm not sure why I suddenly received and installed an AT&T-branded ROM today when my S9 and all of my previous devices were fine running the T-Mo ROM and receiving updates as they were released. Does anyone have any insights as to what caused this change and whether future ROM updates will be carrier-specific based on the inserted SIM? In the past month I've used SIMs in Vietnam and Japan and it seems odd that ROMs would suddenly be based on the carrier of the day.
Also, any ideas about restoring LTE service? I've tried removing the SIM and powering off the device a few times, but no dice. This was a network/account-problem when I initially ported over to AT&T from T-Mo which took a lot of troubleshooting at the store (unsure of actual root cause), but it seems odd that a software update on the device would undo that.
Click to expand...
Click to collapse
you have to change APN setting on the menu to reflect AT&T network. let me know if it works by changing APN.. I used to have S9+ tmobile and I was waiting for this BYOD update but i traded in my s9+ already =/ i have note 9 unlocked now..
skyethur said:
you have to change APN setting on the menu to reflect AT&T network. let me know if it works by changing APN.. I used to have S9+ tmobile and I was waiting for this BYOD update but i traded in my s9+ already =/ i have note 9 unlocked now..
Click to expand...
Click to collapse
The issue required a visit to the AT&T store, where they replaced the SIM and reset some of the network features on the back end of my account. This required a call to the retail technical support team and about 45 min. No settings were changed on the phone. The APN settings were already configured correctly (which I had confirmed as a part of initial troubleshooting).
The phone works fine now, though some features like AT&T HD Voice and the AT&T Call Protect app still don't work. I've tried contacting them twice about it and they opened a ticket but it hasn't helped. These aren't features I used before so I don't really care.
jasonw3 said:
The issue required a visit to the AT&T store, where they replaced the SIM and reset some of the network features on the back end of my account. This required a call to the retail technical support team and about 45 min. No settings were changed on the phone. The APN settings were already configured correctly (which I had confirmed as a part of initial troubleshooting).
The phone works fine now, though some features like AT&T HD Voice and the AT&T Call Protect app still don't work. I've tried contacting them twice about it and they opened a ticket but it hasn't helped. These aren't features I used before so I don't really care.
Click to expand...
Click to collapse
Keep in mind though that HD voice only available to postpaid At&t only not prepaid and they do required special sim card for hd voice but since you already changed sim card then the problem is not the sim card. You can try and dial #*#*4636*#*# and see if Volte is provisioned.. I wish i had my s9+ from tmobile but i dont have it anymore i was waiting for that byod software update.. Hd voice should work on BYOD custimization update on at&t
Hi there, greetings from Brazil. I just purchased a Samsung S9 SM-960F (XEF) from France, running Exynos. I am being able to use it here (Brazil) with 4G, both sim cards, however VoLTE calls are not active. I have it selected on networks settings and my sim card activates it on my wife's S10e. It seems that the issue is somehow related to the device. Is there any setting or procedure that needs to be done in order to activate it? I have already hard reseted the device and it is still not working.
Marciocons77 said:
Hi there, greetings from Brazil. I just purchased a Samsung S9 SM-960F (XEF) from France, running Exynos. I am being able to use it here (Brazil) with 4G, both sim cards, however VoLTE calls are not active. I have it selected on networks settings and my sim card activates it on my wife's S10e. It seems that the issue is somehow related to the device. Is there any setting or procedure that needs to be done in order to activate it? I have already hard reseted the device and it is still not working.
Click to expand...
Click to collapse
voLTE is something that is carrier dependent and can sometimes need provisioning in the telephony switch. Could be as simple as that particular line not having it enabled on an account level. It could very easily be a firmware thing too. My carrier offers voLTE but i lost that option in my settings menu when i flashed the U1 firmware. I bet it would come back if i flashed an at&t firmware set tho even tho im using an at&t mvno
It is carrier dependent. I have a dual SIM Exynos S9 here in the US. I have a Mint SIM (T-Mobile MVNO) in one slot and VoLTE & Wi-Fi calling work just fine. The other SIM is a Cricket SIM (AT&T MVNO) and, of course, there is no VoLTE or Wi-Fi calling on that line. Cricket only supports those features in phones they sell and, of course, iPhones.
Yeap, I got the point that VoLTE is carrier dependent. The issue is that my Brazilian Carrier (VIVO) does support VoLTE in my region and I was able to confirm it by inserting my simcard in my wife´s smartphone (Samsung S10e). I have been reading some articles and threads about CSC and other stuff, like firmware flashing. As I told, my device is a S9 SM-G960, with XEF (France) firmware version installed on it.
Marciocons77 said:
Yeap, I got the point that VoLTE is carrier dependent. The issue is that my Brazilian Carrier (VIVO) does support VoLTE in my region and I was able to confirm it by inserting my simcard in my wife´s smartphone (Samsung S10e). I have been reading some articles and threads about CSC and other stuff, like firmware flashing. As I told, my device is a S9 SM-G960, with XEF (France) firmware version installed on it.
Click to expand...
Click to collapse
if the S10e is allowing voLTE, then it has the firmware built in for voLTE which might be particular to the the S10's, but thats something for the S10 forums. Regarding the S9, it needs the carriers firmware in order to utilize the voLTE feature
I have a new Galaxy S22 (SM-S901U1 - USA factory unlocked), purchased and placed into service on October 29 (as an upgrade from an S21). While using the One UI 4.1 firmware (AVI5), Wi-Fi calling worked flawlessly (both making and receiving calls), as it did on the S21 (One UI 4.0) prior to that.
On November 15, I installed One UI 5 (Android 13); BVK1, and have found that Wi-Fi calling no longer works. When I try to make a call, I receive an error message "Turn off Airplane Mode to make this call"; and calls made to me don't ring on the phone.
Wi-Fi calling is, of course, enabled at both my carrier (a T-Mobile MVNO) and on my phone. FYI, the SIM is in SIM2 (eSIM), though I am not sure that is relevant to Wi-Fi calling.
Does anyone know how to fix this or is it a bug in the firmware? I need Wi-Fi calling.
UPDATE: The OTA update from Android 12 to Android 13 revoked all of the permissions for the app "Carrier Services" ; once these permissions were restored (followed by a reboot), Wi-Fi calling became fully functional again.
Droiderat said:
I have a new Galaxy S22 (SM-S901U1 - USA factory unlocked), purchased and placed into service on October 29 (as an upgrade from an S21). While using the One UI 4.1 firmware (AVI5), Wi-Fi calling worked flawlessly (both making and receiving calls), as it did on the S21 (One UI 4.0) prior to that.
On November 15, I installed One UI 5 (Android 13); BVK1, and have found that Wi-Fi calling no longer works. When I try to make a call, I receive an error message "Turn off Airplane Mode to make this call"; and calls made to me don't ring on the phone.
Wi-Fi calling is, of course, enabled at both my carrier (a T-Mobile MVNO) and on my phone. FYI, the SIM is in SIM2 (eSIM), though I am not sure that is relevant to Wi-Fi calling.
Does anyone know how to fix this or is it a bug in the firmware? I need Wi-Fi calling.
UPDATE: The OTA update from Android 12 to Android 13 revoked all of the permissions for the app "Carrier Services" ; once these permissions were restored (followed by a reboot), Wi-Fi calling became fully functional again.
Click to expand...
Click to collapse
I have same issue, how do i restore carrier Services permissions
Go to Apps ; enable "Show system apps" and you will see Carrier Services.
Droiderat said:
Go to Apps ; enable "Show system apps" and you will see Carrier Services.
Click to expand...
Click to collapse
Thanks, but it is all there i can see it with all permissions allowed, still not working with me.