Related
This is a patch to fully enable the GSM on CDMA Global phones.
The Global Phones are phones with CDMA and GSM modems but that are usually configured to primarly work on CDMA network and at least to be able to call on GSM network.
The patch is working on every Stock Rom, on every AOSP Rom and on every Android version.
If you are successfully using this patch please comment the thread with your phone model.
This patch will enable:
- GSM/UMTS -> [GSM auto (PRL)] in Testing menù
- SMS
- MMS
- 3G Data
- USSD Code
- Call Forwarding
- Testing menù to manage the baseband accessible dialing the code *#*#4636#*#* (locked on Verizon Phones)
How to install:
- Copy the .zip file to the external memory or memory card
- Reboot your phone and enter on your custom recovery
- From the Install menu select the .zip file and instal withotut signature verification on your Rom
Risk of briking:
- no one: during installation the installer checks everything is ok and stop installation in case of problem; in case of problems after installation the old settings can be restored by simply installing the patch a second time. In this way you can test the gsm settings without any risk.
Advice post-installation:
- If the patch has not been installed on a clean system then you have to do a factory reset
- On the AOSP Roms the Patch is persistent, when you will update your rom you do not have to reinstall the patch
- *#*#4636#*#* -> Phone info -> Set prefered network type -> GSM auto (PRL)
How to uninstall:
- To uninstall the patch you have to reinstall it a second time from the custom recovery
The patch should work on every CDMA Global Phone.
The patch should work on every Rom.
Download the patch here
If someone successfully use this patch on some other model please leave a comment in this page, so I will be able to update the above list.
If someone has edited this patch to support some other phone please inform me so as not to waste information and in this way I can update the patch.
Any help is precious.
HOW TO POST REQUEST FOR HELP:
You have to entirely read this thread, I do NOT answer redundant question.
If you want to know if the patch is compatible with a phone then you have to attach the /system/build.prop in your post in this thread because i don't know all phones. (You can also send me the build.prop as attachment via the contact section of my site.)
If you installed the patch and there are problems you have to attach (and do not post) your /system/build.prop and your /system/build.prop.bak.
I do not answer to requests for help in private, I have neither the time nor the interest in doing so.
Any doubts, questions or requests must be posted in this thread in order to answer a single time and help everyone.
XDA:DevDB Information
Patch CDMA to GSM for Android Global Phones, Tool/Utility for the Android General
Contributors
Mentor.37
Version Information
Status: Stable
Current Stable Version: 4.2.7
Stable Release Date: 2016-04-25
Created 2014-12-04
Last Updated 2016-04-25
The patch has been updated.
The patch has been update.
Everyone can help me to extend support for more phones.
Thanks.
Patch updated for better GSM support.
works flawless on my Razr xt912 in Pakistan using Gsm network.
Thanks a lot man.:good:
Available a new update to solve problems with apns on 4.3.x roms.
It works on my Droid razr Maxx xt912 with CM10.2-20131020-NIGHTLY-spyder ROM, my phone is using GSM carrier
New version working well on Vodafone Ireland with cyanogenmod 10.1.3 on XT912.
This version also leaves the ROM version intact - older version for 10.1.2 seemed to update the string.
The version that changed the string was only for the xt894 with cm 10.1.2, that was the first version.
Works great on my XT912 with MIUI v5. Thanks.
Mentor.37 said:
This is a patch to fully enable GSM on every Stock Rom, on every AOSP Rom and on every Android version.
This in not for US users, in US the GSM is locked in RIL.
Release 1.6 - 20/10/2013
Click to expand...
Click to collapse
I may have misinterpreted the topic I guess, but did install this while I was overseas with my Verizon phone, everything was fine but now it seems as I am unable to find 3G network back in the US. I have changed the specs from GMS/CDMA , etc on the settings but no signal of 3G/LTE.
Anyone has had this issue before? Any way to turn it back to normal so that I can get data here in the US?
blustosa said:
I may have misinterpreted the topic I guess, but did install this while I was overseas with my Verizon phone, everything was fine but now it seems as I am unable to find 3G network back in the US. I have changed the specs from GMS/CDMA , etc on the settings but no signal of 3G/LTE.
Anyone has had this issue before? Any way to turn it back to normal so that I can get data here in the US?
Click to expand...
Click to collapse
In US you can not use the GSM on many Verizon phones, you have to use the CDMA and you have to restore build.props and apns list.
The patch has been successfully tested on droid bionic xt875 in and outside the US and on droid 3 xt862.
Mentor.37 said:
The patch has been successfully tested on droid bionic xt875 in and outside the US and on droid 3 xt862.
Click to expand...
Click to collapse
Mentor.37 said:
I need your build.prop.
Click to expand...
Click to collapse
Mentor I have a question.
I flashed on XT912-Spyder CM 10.1.3 but even before I did flash I would have no service at all , I have Euorpean sim card which has active roaming.
When I put it into iPhone 4S it shows T-Mobile USA but in settings T-Mobile.Poland settings so it roams, it gets signal,receivies texts.
IN XT912 it only shows phone number in settings that is all , i flashed your patch.. I will do it again maybe it will help I don't know.
Can you help me? if I get sim to work I will have my buddy replace screen,battery everything and put this phone into use for someone.
You could try installing the patch on clean system before first boot without restore any backup.
Let's me know.
Mentor.37 said:
You could try installing the patch on clean system before first boot without restore any backup.
Let's me know.
Click to expand...
Click to collapse
EDIT:
Same thing I just did what you told me it instantly showed the European phone number Poland area code +48.
Signal Strength : 0 dBm 99asu
I can't understand how when I put it in Verizon 4S which was Unlocked by VZW it shows signal,receives texts etc.. the droid razr after JB update was suppsed to be unlocked for European use for example.
It even synced local time in Poland which is +6 hours! it seems to pull up number and time but no signal
Is there anything else I can try?
In your recovery: factory reset, wipes, install patch and then reboot phone.
Mentor.37 said:
In your recovery: factory reset, wipes, install patch and then reboot phone.
Click to expand...
Click to collapse
Yep did that and still no ago same thing.
Before I got the phone (Got it for free)
when I first put AT&T simcard it showed me roaming triangle for few seconds ever since that time the signal just does not work.. at all.
The xt 912 is GSM locked in the US and could be locked for AT&T sim outside US too, you could try with another sim.
Mentor.37 said:
The xt 912 is GSM locked in the US and could be locked for AT&T sim outside US too, you could try with another sim.
Click to expand...
Click to collapse
Well yes I know so why when I put in T-Mobile Poland sim card which roams on T-Mobile USA it shows nothing but only phone number? it's weird.
Works fine in 4S unlocked by Verizon.
I have a Samsung Galaxy S3 SCH-I535 CDMA Verizon & GSM phone. Originally it was on android 4.1.2 and working fine for both CDMA and GSM (one at a time). CDMA EVDO Rev A data service was working fine.
I am using this phone in Nepal (not in USA). It was carrier unlocked for both CDMA & GSM when I purchased from Amazon. (so, I guess, Originally it may had some customized firmware/ROM for International use, I don’t have much idea).
I was asked for firmware upgrade every time when I run Samsung Kies. One day I clicked to upgrade the firmware. The upgrade was over successfully. But the new android version I found on my phone was 4.4.2.
In this version /new upgrade, I was unable to use CDMA data (EVDO-rev A). So I wanted to reverse back to old version. I search the process in Google and tried to load firmware with the help of Odin3 using this file:- “I535VRBMF1_I535VZWBMF1_VZW.zip”, but it was not successful. Result: Fail(Auth)
Then I loaded firmware for 4.4.2 using Odin3.09 (AP: “I535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5”) and now the phone is working.
• If I use GSM SIM I can make call and use HSPA data service as well by adding new APN.
• If I use CDMA RUIM I can make call, BUT DATA SEVRICE using CDMA EVDO Rev A is NOT WORKING!! (I can not save APN in this case).
Now my issue is how to make CDMA EVDO data service working in my phone, because my basic requirement is to use this phone for CDMA service (voice + data).
I can edit the APN but when I click “Save”, nothing was saved. So I can not select APN for my carrier. I tried using APN Manager Pro too, here I can enter & enable the APN, but did not work. The phone is not able to dial the data access code #777 (verified from CDMA service provider side trace).
Can someone help me what I should do to make my phone working for CDMA data. My phone is rooted.
I guess it may work for CDMA data if I downgrade it to 4.3 or 4.1.2,
Can I do that. If so what are the procedures / steps. Any help in this regard would be highly appreciable.
My data worked this way
kkafle said:
I have a Samsung Galaxy S3 SCH-I535 CDMA Verizon & GSM phone. Originally it was on android 4.1.2 and working fine for both CDMA and GSM (one at a time). CDMA EVDO Rev A data service was working fine.
I am using this phone in Nepal (not in USA). It was carrier unlocked for both CDMA & GSM when I purchased from Amazon. (so, I guess, Originally it may had some customized firmware/ROM for International use, I don’t have much idea).
I was asked for firmware upgrade every time when I run Samsung Kies. One day I clicked to upgrade the firmware. The upgrade was over successfully. But the new android version I found on my phone was 4.4.2.
In this version /new upgrade, I was unable to use CDMA data (EVDO-rev A). So I wanted to reverse back to old version. I search the process in Google and tried to load firmware with the help of Odin3 using this file:- “I535VRBMF1_I535VZWBMF1_VZW.zip”, but it was not successful. Result: Fail(Auth)
Then I loaded firmware for 4.4.2 using Odin3.09 (AP: “I535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5”) and now the phone is working.
• If I use GSM SIM I can make call and use HSPA data service as well by adding new APN.
• If I use CDMA RUIM I can make call, BUT DATA SEVRICE using CDMA EVDO Rev A is NOT WORKING!! (I can not save APN in this case).
Now my issue is how to make CDMA EVDO data service working in my phone, because my basic requirement is to use this phone for CDMA service (voice + data).
I can edit the APN but when I click “Save”, nothing was saved. So I can not select APN for my carrier. I tried using APN Manager Pro too, here I can enter & enable the APN, but did not work. The phone is not able to dial the data access code #777 (verified from CDMA service provider side trace).
Can someone help me what I should do to make my phone working for CDMA data. My phone is rooted.
I guess it may work for CDMA data if I downgrade it to 4.3 or 4.1.2,
Can I do that. If so what are the procedures / steps. Any help in this regard would be highly appreciable.
Click to expand...
Click to collapse
I think your problem is the region is not set Nepal...I installed dark jb rom in my phone and data was gone since then. Then I manually downloaded stock firmware and flashed through odin but still data wasnt working,nd while in recovery mode i saw region INS ie India. then something came in my mind and.. .I changed it to NPL and now i can use data in only sim 1 only not in both sims. So i also may need some help.
For you *#272*IMEI# . Use your phones IMEI number there (*#06#) . Select NPL region.
NOTE: It will hard format your phone installing required carrier apps, aps, bla bla and hope work on your phone
Pujan Shrestha said:
I think your problem is the region is not set Nepal...I installed dark jb rom in my phone and data was gone since then. Then I manually downloaded stock firmware and flashed through odin but still data wasnt working,nd while in recovery mode i saw region INS ie India. then something came in my mind and.. .I changed it to NPL and now i can use data in only sim 1 only not in both sims. So i also may need some help.
For you *#272*IMEI# . Use your phones IMEI number there (*#06#) . Select NPL region.
NOTE: It will hard format your phone installing required carrier apps, aps, bla bla and hope work on your phone
Click to expand...
Click to collapse
I found that the hidden menu (& hence secret code dialing) was disabled in my phone. Following guides from Google search I enabled it. Now codes likes "*#06#",*#1111#", "*#0228#" etc are working, but "*#272*IMEI#" is not working. Any idea, why it is not working?
kkafle said:
I have a Samsung Galaxy S3 SCH-I535 CDMA Verizon & GSM phone. Originally it was on android 4.1.2 and working fine for both CDMA and GSM (one at a time). CDMA EVDO Rev A data service was working fine.
I am using this phone in Nepal (not in USA). It was carrier unlocked for both CDMA & GSM when I purchased from Amazon. (so, I guess, Originally it may had some customized firmware/ROM for International use, I don’t have much idea).
I was asked for firmware upgrade every time when I run Samsung Kies. One day I clicked to upgrade the firmware. The upgrade was over successfully. But the new android version I found on my phone was 4.4.2.
In this version /new upgrade, I was unable to use CDMA data (EVDO-rev A). So I wanted to reverse back to old version. I search the process in Google and tried to load firmware with the help of Odin3 using this file:- “I535VRBMF1_I535VZWBMF1_VZW.zip”, but it was not successful. Result: Fail(Auth)
Then I loaded firmware for 4.4.2 using Odin3.09 (AP: “I535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5”) and now the phone is working.
• If I use GSM SIM I can make call and use HSPA data service as well by adding new APN.
• If I use CDMA RUIM I can make call, BUT DATA SEVRICE using CDMA EVDO Rev A is NOT WORKING!! (I can not save APN in this case).
Now my issue is how to make CDMA EVDO data service working in my phone, because my basic requirement is to use this phone for CDMA service (voice + data).
I can edit the APN but when I click “Save”, nothing was saved. So I can not select APN for my carrier. I tried using APN Manager Pro too, here I can enter & enable the APN, but did not work. The phone is not able to dial the data access code #777 (verified from CDMA service provider side trace).
Can someone help me what I should do to make my phone working for CDMA data. My phone is rooted.
I guess it may work for CDMA data if I downgrade it to 4.3 or 4.1.2,
Can I do that. If so what are the procedures / steps. Any help in this regard would be highly appreciable.
Click to expand...
Click to collapse
Well, it looks to me as though you've locked your bootloader and are now stuck on 4.4.2. For some reason, Verizon forces Samsung to lock their bootloaders, which means we (the consumers) cannot install "custom" firmware on our devices (or downgrade).
Once you're on 4.4.2 NE1 your stuck with it. No downgrade possible at least not without a Jtag service
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I have faced similar problem I can't create apn I am using it in India . So my data i not working on any sim card but i can make and receive calls . My android version is also 4.3 . So please help me i want to use both hspa and evdo .
Sent from my iPhone using Tapatalk
hey guys sorry to spam if this is being posted in incorrect section.
I live in UAE. I bought used american note 4 sm-n910p unlocked network. the person who sold me this phone already had it unlocked to use GSM sim. UAE sim used to work perfectly untill i flashed lineage rom to it. lineageos is awesome i loved it everything works fine but cannot get any sim to work in lineage. it always says no service. i tried dialing *#*#4636#*#* and changed to gsm only but that was resetting as soon as i reboot so i modified build.prop ro.radio.networkmode=3 to unable GSM on boot but that shows my network name and emergency calls only. i restored my previous backup rom in which GSM sim used to work but now after restoring sim doesn't work in backedup rom too and *#*#4636#*#* is not working in my backup rom :crying:
and if i reinstalling lineageos rom *#*#4636*#*# is not taking any effects
i flashed stock sm-n910p rom from sammobile that locked the network and shows "Hands Free Activation" so i reinstalled my backup rom. in this rom network bar shows but network always shows (searching)
Please Help:crying::crying:
BTW i cam across octoplus on youtube but soon realised it needs dongle or octoplus box to unlock sim. and saw some hacked videos it says octoplus can work without any box or dongle. Is This True or just haox to download their trojan virus?
I managed to get VoLTE working on the xz2cd (H8324) with T-Mobile USA using the xz3 (H8416) USA firmware oem-*.sin files.
Thank you to all the others that figured out the process details so all I had to do was try every combination - see the other VoLTE threads in this forum to guide you on the actual steps. Also thanks to Androxyde and Igoreisberg for the flash & download tools!
I have this working with the H8324_Customized NOBA_1313-6167_52.0.A.8.25_R5B firmware, I happen to choose, replacing only the oem-*.sin files from the XZ3 H8416_Customized US_1316-4522_52.0.A.8.25_R10B firmware. When you set both lines to "LTE (preferred)" and you'll be able to make LTE calls on both lines, however it may only show [HD] calling on the line you configured last I think but it'll be VoLTE on both.
Enjoy and thanks again to all the other threads that guided me through this long but worthwhile trial process. I wish the carriers didn't make LTE VoLTE provisioning difficult, why didn't they just make it universal like 3G.
Note: I was able to separately get Wifi-Calling to appear using the H8276_Freedom CA_1313-8876_52.0.A.8.25_R3B oem-*.sin files but it wasn't functional on T-Mobile USA - I think someone with a little bit more knowledge might be able to get this to work, unless you can point me in the right direction.
Someone please make an open firmware thin/light/compact dual SIM phone with Wifi-Calling/VoLTE (removable battery a bonus)!
Do you think the files would be the same on the H8314 US edition? i'm assuming you need to be rooted for this to work?
Hey Mike, Can you please share(download link) OEM*.sin files of USA firmware for Volte Settings
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
VoLTE provisioned on XZ2 but calls are still made over 3G
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
I just talked to a T-mobile specialist, and he confirmed that my phone should work and no need to register or do anything if it supports all bands!!! As he told me "only check for compatibility" and mine is compatible! ?
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Is there anyway to get volte working for tmobile on the h8314?
XZ2C H8314 VoLTE working on T-Mobile USA
colonelcack said:
Is there anyway to get volte working for tmobile on the h8314?
Click to expand...
Click to collapse
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 4(66) just fine, I cannot confirm band 12 even though the phone spec supports it. It appears only Short range VoLTE is working on the phone unless someone else can confirm with this method, My Band 12 tower is behind a hill and i am 20 miles from it) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
XZ1 oem files on XZ2 for VOLTE and VOWIFI calls.
nicogu said:
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
Click to expand...
Click to collapse
You will need to try this. I was not so brave. The reason is the difference in the build IDs and oem.sin file names between the XZ1 (Old) and XZ2 (Current as of July USA Customized builds).
Mixing and matching files is easier when you are doing so off the same build ID. Thats why V0LTE worked on my XZ2 using XZ3 oem.sin files, they were from the same build ID and had the same names even though the sizes were slightly different.
It may work if the format of the oem.sin file did not change between the XZ1 builds and XZ2 Builds. The more different the builds, the higher the risk of something going wrong.
---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------
gigili said:
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
Click to expand...
Click to collapse
Enter *#*#4636#*#* in your phone dialer app, select phone information, and select LTE only - Reboot, if you cant make calls after that something else is wrong.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
hitemup92 said:
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Click to expand...
Click to collapse
Got this to work, no VoWIFI though - look further down the thread.
depsilon said:
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 12 just fine) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
I made the mistake of calling sony and t-mobile for support and they both kept blaming each other, the reason they don't know why VoLTE does not work on some phones is they really don't know enough about their network or the basebands in the phone or the software build process and details about android sin files - as they should not either cause if the network engineers, device manufacturers and software developers all do their job and stick to industry standard practices, it will just work anyway.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
Click to expand...
Click to collapse
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
H8314 Flash tools
colonelcack said:
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
Click to expand...
Click to collapse
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
depsilon said:
H8314 Flash tools
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
It's been a while but wanted to thank you for taking the time to write out these steps. I finally took a shot with the incoming shutdown of 3g for my XZ2, but unfortunately it did not work. Similar to what gigili said, while VoLTE appears to be provisioned the calls are dropping to 3g/HSPA like they originally were. After setting to "LTE Preferred" and rebooting, calls would not be made at all. I also saw "Unknown" under the Modem Config, and from what you said it should reference T-Mobile after flashing the OEM sin files.
I tried this using the latest firmware available on XperiFirm for the XZ2 (Customized US H8266 - my device is H8276) and the XZ3, which I used to grab the two OEM sin files. The firmware is 52.1.A.3.137.
Using UnSin, I unpacked both "oem_X-FLASH-CUST-B6B5.sin" files in both firmwares, and under modem-config there are a bunch of folders, and each one seems to have a conf files pointing to "mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn."
I read in another thread that T-Mobile maybe has some way of blocking this workaround now, but I'm not entirely sure if that is true? Totally understand if you've moved on from the device as it's been a while, but am admittedly curious if there's a specific firmware version that this works on I could try to salvage the device.
Volte xz2/xz2 p/xz3 solved
Samir solanki said:
Volte xz2/xz2 p/xz3 solved
Click to expand...
Click to collapse
Details on exactly how?
I will create complete guide thread for the same
Samir solanki said:
I will create complete guide thread for the same
Click to expand...
Click to collapse
Thanks I'll watch for it
I am working to bring support for T-Mobile VoLTE on the xz2c to LineageOS 18.1. As of this writing, official LineageOS builds for this device do not support VoLTE unless it was already enabled and working in the stock firmware.
I have submitted some patches which may resolve the issue for TMO and probably other carriers as well. They work for me, but testing has been limited. If you are interested in using LineageOS instead of the stock ROM, and you are willing and able to build LOS yourself on linux, consider giving my patchset a try. Please read the patch description fully before attempting a build: you will need to obtain and mount some additional files first. The LineageOS wiki has additional instructions for creating a build environment.
EDIT: My patch is part of official LOS 18.1 starting with nightly 20220401. There is no need to build it yourself.
cbs228 said:
---
Click to expand...
Click to collapse
You are a saint for working on this. I bought a H8324 XZ2c recently and was super disappointed it didn't work, so I am back to my XZ1c. Super frustrated. If you ever get a pre-compiled ROM, I would love to try. In the meantime I will try to compile it myself in the coming days despite my technical illiteracy.
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage? Considering how old the other solutions for trying to get VoLTE working, I am hesitant to try any especially funny business of switching old firmware files from other phones around.
xperiaperson42069 said:
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage?
Click to expand...
Click to collapse
As far as I am aware there isn't any stock firmware that works "out of the box." The xz2c is listed as "unsupported" by t-mobile, which probably means there isn't any sort of stock ROM out there that works. Sometimes carriers do release "branded" ROMs, but there's nothing like that for this device AFAIK.
LinageOS is designed to be installed "on top" of an existing stock ROM. If you attempt to install it after you have flashed another distro (like an AOSP build), you will likely just make a brick. If you do end up bricking your device, do not despair. You can use Emma to restore your device to factory condition. Emma is available on the Sony Developer World website, and there are many guides available for it.
Has anyone been able to get dual SIM working on their T-Mobile OP8 after flashing to the Global ROM?
I have a dual SIM tray and whenever I insert two SIMs, I get service on the first, and the second is recognized, but refuses to connect to any network. This applies to any second SIM inserted. The IMEI numbers are showing as the same for IMEI1 and IMEI2, but that shouldn't be an issue as far as I can tell.
Thanks!
I have same issue did you find any fix? Please let me know
themoveforward said:
Has anyone been able to get dual SIM working on their T-Mobile OP8 after flashing to the Global ROM?
I have a dual SIM tray and whenever I insert two SIMs, I get service on the first, and the second is recognized, but refuses to connect to any network. This applies to any second SIM inserted. The IMEI numbers are showing as the same for IMEI1 and IMEI2, but that shouldn't be an issue as far as I can tell.
Thanks!
Click to expand...
Click to collapse
I have same issue did you find any fix? Please let me know
i have the same issue
Follow these instructions at your own risk. I am NOT responsible for you bricking your device. If you are new to this I advise you to do it with someone who is experienced and knows what he/she is doing.
I was recently able to "rebrand" my OnePlus 8 T-Mobile 5G phone from the T-Mobile version to the European version using these steps (I tried with the GLOBAL version but it DID NOT work):
1. Unlock the bootloader. Steps given in:
https://www.oneplus.com/support/answer/detail/op588
2. I was able to to use the MSMTool_instantnoodle_tmo_15_O.06_200411.zip to go back to 10.5.7.IN55CB
(OnePlus T-Mobile Android build) using the method given in (GLOBAL version FAILED for me here) :
Instructions: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
Tool: https://androidfilehost.com/?fid=4349826312261823571
3 Repeat Step 1. Go to Step 4.
4. Next, I upgraded to 10.5.9.IN21BA (OnePlus European Android build) by flashing 10.5.9-EUROPE-OnePlus8Oxygen_15.E.18_OTA_018_all_2007160043_913306-FASTBOOT.zip using the method given in:
Instructions: https://forum.xda-developers.com/t/rom-stock-fastboot-op8-stock-fastboot-roms-for-oneplus-8.4084629/
Tool: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8/
5 Repeat Step 1. Go to Step 6.
6. Finally, I upgraded the phone to the latest OnePlus Android version for this phone through System Update to 11.0.9.9.IN21BA (OnePlus European Android build). Now Dual Sim capability is installed but it does NOT show.
7. Relock the bootloader and NOW dual sim capability shows under SIM & Network.
What I don't understand is that the model, IN2017 (T-Mobile), remains the same but when you boot the phone, the T-Mobile logo does NOT show and it boots like a non-T-Mobile OnePlus phone. I expected the model to change to the European model number (IN2013). My goal was to get Dual-Sim working as it has been banned by carriers here in the good ol' USA. My phone now shows 2 sim cards, originally it only showed 1. Now I have to verify what signals it really works with (5G, 4G ?) and if the dual sim capability works.
Cmdr_Colstel said:
Follow these instructions at your own risk. I am NOT responsible for you bricking your device. If you are new to this I advise you to do it with someone who is experienced and knows what he/she is doing.
I was recently able to "rebrand" my OnePlus 8 T-Mobile 5G phone from the T-Mobile version to the European version using these steps (I tried with the GLOBAL version but it DID NOT work):
1. Unlock the bootloader. Steps given in:
https://www.oneplus.com/support/answer/detail/op588
2. I was able to to use the MSMTool_instantnoodle_tmo_15_O.06_200411.zip to go back to 10.5.7.IN55CB
(OnePlus T-Mobile Android build) using the method given in (GLOBAL version FAILED for me here) :
Instructions: https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
Tool: https://androidfilehost.com/?fid=4349826312261823571
2 Repeat Step 1. Go to Step 3.
3. Next, I upgraded to 10.5.9.IN21BA (OnePlus European Android build) by flashing 10.5.9-EUROPE-OnePlus8Oxygen_15.E.18_OTA_018_all_2007160043_913306-FASTBOOT.zip using the method given in:
Instructions: https://forum.xda-developers.com/t/rom-stock-fastboot-op8-stock-fastboot-roms-for-oneplus-8.4084629/
Tool: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8/
4 Repeat Step 1. Go to Step 5.
5. Finally, I upgraded the phone to the latest OnePlus Android version for this phone through System Update to 11.0.9.9.IN21BA (OnePlus European Android build). Now Dual Sim capability is installed but it does NOT show.
6. Relock the bootloader and NOW dual sim capability shows under SIM & Network.
What I don't understand is that the model, IN2017 (T-Mobile), remains the same but when you boot the phone, the T-Mobile logo does NOT show and it boots like a non-T-Mobile OnePlus phone. I expected the model to change to the European model number (IN2013). My goal was to get Dual-Sim working as it has been banned by carriers here in the good ol' USA. My phone now shows 2 sim cards, originally it only showed 1. Now I have to verify what signals it really works with (5G, 4G ?) and if the dual sim capability works.
Click to expand...
Click to collapse
even if the two simcards appear, they won't work for you. the second simcard always says "no service"
acostmisa said:
even if the two simcards appear, they won't work for you. the second simcard always says "no service"
Click to expand...
Click to collapse
I went to Verizon yesterday with the setup written above and the second sim did register as Verizon with the first card in slot 1 as T-Mobile. The problem was that we only tested it with 5G. 5G did NOT work with both sim cards placed. I should have put my phone in 4G to see if THAT works. I will go to another Verizon store later in the week to see if it will work in 4G with both sim cards. Hopefully it will.
I went to the Verizon store yesterday and they said that I needed to open an account and activate my phone with that account in order for the Verizon service to work. I was under the impression that all you needed was a Sim card with an active Verizon account and a phone with a good IMEI. I asked them to use a spare Verizon card at the store to test it just to make sure it would work. He wanted me to sign up first which I wasn't going to do. I will have to find another store. Am I correct in assuming that you can just use the sim card from another phone and the service should automatically work ? Or do I have to "register" that phone with Verizon ? F%^k Verizon. Thank you.
So I went to the Verizon store yesterday and brought my OnePlus 8 (IN2017 updated with Oxygen OS 11.0.9.9IN21BA European version). I brought it in unlocked and the Verizon clerk told me it was "dangerous" to leave it unlocked and advised me to lock it (of course I did not). I had my phone set to LTE (4G) under network settings and the two SIMs slots were showing with the first one occupied by T-Mobile. The clerk placed a Verizon SIM card on the 2nd slot and the phone recognized it but IT DID NOT work (messages nor calls). So apparently, according to other users over the web, the blockage of service is coming from the carriers (T-Mobile, Verizon, etc.) themselves. They frown upon dual sim capability and until there are enough complaints to make them change their stance they will continue to refuse to provide dual sim service. It may work in Europe and Asia, but here in the US, not a chance. Talk about UNFREE market.