Database Info

Enable bands 2,3,4,7,12 and 17 lte

I can confirm using the link below in a forum in the m9 section, I've been able to unlock bands 2,3,4,7,12 and 17 lte for a verizon build phone that is using tmobile service now. There are also instructions for other bands for other provides in the op. Used DFS tool, diag adb commands to enable diag.
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401

can you help me out with adding band 40 lte 2300mhz for indian gsm network
Casetheace said:
I can confirm using the link below in a forum in the m9 section, I've been able to unlock bands 2,3,4,7,12 and 17 lte for a verizon build phone that is using tmobile service now. There are also instructions for other bands for other provides in the op. Used DFS tool, diag adb commands to enable diag.
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401
Click to expand...
Click to collapse
hi i have been using Verizon htc one m8 in india on gsm network for an year now. As the 4g Lte services are launched in my country i got to know my phone does not support the required band. I just want to know the process to add Lte band 40 2300MHz to verizon htc one m8. my htc m8 is S-0ff on SD V10.1 rom thanks in advance.

I would believe that it would work using those links and the guide in it. Concern would be is the author of it clearly States enabling extra bands may break phone to point of RUU won't fix it. I can tell you on my Verizon m8 when I first used the DFS tool I had 4 Lt bands enabled, believe is was 2,4, 12 and maybe one more. So 3 or 4. I have it on T-Mobile sim, so. Was enabling 6 bands, at least 2 more then before. My first try I accidentally hit band 40 also so I was turning all T-Mobile bands on and a extra one. Now that didnt fry my radios. Noticed it on the first text to check if it worked. I'll write why I did, I think enabling just that one band won't kill it. Also if a band is active and you don't use it, maybe turn that off and 40 on. Okay heres my step by step guide it did.:
1. Downloaded DFS TOOl , free version is fine just takes extra time that's all.
2. Using command prompt., did the adb shell, then su, phone will ask for approval for supersu access. Then enter the code to turn hdiag on. You want to use the one for m8, first codes are for m9 , the m8 is clearly said in bold. Once entered to turn in on. Plug in your phone. Now run DFS with administrative rights, can't remember what the exact steps for the next things but just follow the guide. In DFS tool you should see your phone connect , not in usb mode, but cm 8 port, cm 7port. Now for the computer to read the phone in DIAG you need the driver, its in the m8 HTC sync manager thing. So if that's installed you have it already. Now if it's installed and you don't see it recognised in diag mode using device manager option your PC (by the way I'm running WIN 10 on my PC) I had read that I'm windows 8 it would not accept drivers without signatures. There is a guide in there explaining how to install under that. My phone was not picked up in DIAG mode, had sync manager , driver installed from DFS tool, then used a zip I'm authors guide. Unzipped folder and it was broken into folders. Have to find folder with exe to run it. After all this still no dice. Then went to device manager , went to phone where it stated driver missing. Douple clicked on it. Chose option to update driver, selected in there a option that will show you all the drivers installed on the device. Chose the HTCDIAGDRIVER. It installed it and had to reboot comp.
3. Now go back to DFS TOOL., follow the authors guide to the T in this process. You pick the last tab , LTE , I believe. Following guide, I let it read all my lte bands, wrote down all the current ones in case I needed to change it in time. Then chose to read again and write down LTE bands using authors guide, of the selection in bottom right of screen u need to chose. In guide it States the name of it, and to choose that and read. In that option In bottom right, there is another selection next to it, 3 of 4 same words can't remember the word but its in Authors guide. Now your gonna want to have what bands are currently enabled, in authors guide is what LTE bands should be choose by manufacturers default. I then choose the bands it had listed that should be, and deselected any bands that where not being used on current provider. Now you want to hit write after choosing your bands. Now after that you want to write the bands in next mode that author says to change just in case. OK, now you can't do both writes at same time. If you do, first write won't stick and only second. I tried and can tell you that. So write , reboot, write, reboot. Now after that, reconnect phone to PC and read both things you just changed to make sure they stuck.
4. Using command prompt on PC, adb shell, su , then code to turn the hdiag mode off. If you don't PC won't recognize the phone as prober driver and a DIAG mode. Make sure to do this.
That's what I did. I would advise to read all ten pages of former questions, lost of newer information that will only help you understand it more.
I'm far from a expert, I just know the adb commamd process, how to flash ROMs, mostly basic things. 4 Years ago I knew nothing. So I'm sure u can do it. Author will answer questions, mostly every question you can think of has been asked in those ten oahes and you will learn it from there. So i would read all posts so you have a good feel of it. Anything I can help you with write back. Havent been on in two weeks. Stock market has my attention 18hrs a day

mediapad x2 (702) h+ T-Mobile only works while you are on a phone call. (help) ?

Help I have a 702 model of this phone. I have T-Mobile and cannot connect to h+ or 3g only 2g works but what's strange is that when you make a call and remain on the line the h+ will work and its fast. If anyone can help or suggest of maybe give me there APN setting I would appreciate it. I don't see what I'm doing wrong everything is good. Also I did try and search and search for a answer but all I can find is the question being asked but never a answer. Thanks a lot.

bosnia8659 said:
Help I have a 702 model of this phone. I have T-Mobile and cannot connect to h+ or 3g only 2g works but what's strange is that when you make a call and remain on the line the h+ will work and its fast. If anyone can help or suggest of maybe give me there APN setting I would appreciate it. I don't see what I'm doing wrong everything is good. Also I did try and search and search for a answer but all I can find is the question being asked but never a answer. Thanks a lot.
Click to expand...
Click to collapse
Your SIM should have automatically put in your APN settings. Send me a screenshot of your Mobile Network screen in Settings.

Phone won't let me upload. But if you can give your input on APN it would be great. I know mine are right I have fast T-Mobile and also epc T-Mobile. . if you let me know how to upload the pics I'll be more than happy to. Thanks. I don't understand. 2 gworks. But 4g 3g h,,+ only works when I'm litteraly on the phone. Best way to say it is to make a call and answer the line put phone in munte and use the net. Just strange.

bosnia8659 said:
Phone won't let me upload. But if you can give your input on APN it would be great. I know mine are right I have fast T-Mobile and also epc T-Mobile. . if you let me know how to upload the pics I'll be more than happy to. Thanks. I don't understand. 2 gworks. But 4g 3g h,,+ only works when I'm litteraly on the phone. Best way to say it is to make a call and answer the line put phone in munte and use the net. Just strange.
Click to expand...
Click to collapse
Any advice or a screen shot of APN will be greatly appreciated. Thanks

Did you find apn?
Hi,
I have same device and am running into no data issue too. Did you ever get the apn?
Robbie

On my 702L with T-Mobile I had to go into Settings--->More--->Mobile Network and set the Preferred network type to WCDMA only (for some reason.) Then I had HSPA+.

No WCDMA
ajsmsg78 said:
On my 702L with T-Mobile I had to go into Settings--->More--->Mobile Network and set the Preferred network type to WCDMA only (for some reason.) Then I had HSPA+.
Click to expand...
Click to collapse
Hi,
Thanks for taking time to respond. Did you do any additional steps to activate additional preferred network types? I have 4g, 3g, 2g, 4g/3g/2g auto, and automatic (3g/2g). Rob

AzRob82 said:
Hi,
Thanks for taking time to respond. Did you do any additional steps to activate additional preferred network types? I have 4g, 3g, 2g, 4g/3g/2g auto, and automatic (3g/2g). Rob
Click to expand...
Click to collapse
The only thing I can think of is I flashed the B111 cust mod.

ajsmsg78 said:
The only thing I can think of is I flashed the B111 cust mod.
Click to expand...
Click to collapse
Is yours the 702l? I love the device but had planned on returning tomorrow since I couldn't get it going. I will root and flash rom if yours is the 702l. Would hate to do all that if I have different model.

AzRob82 said:
Is yours the 702l? I love the device but had planned on returning tomorrow since I couldn't get it going. I will root and flash rom if yours is the 702l. Would hate to do all that if I have different model.
Click to expand...
Click to collapse
Yeah it's a 702L. This is what I have in mobile networks. On my 703L I only have 3 options. (4G/3G/2G Auto, 3G/2G Auto and 2G only)

ajsmsg78 said:
Yeah it's a 702L. This is what I have in mobile networks. On my 703L I only have 3 options. (4G/3G/2G Auto, 3G/2G Auto and 2G only)
Click to expand...
Click to collapse
Sorry if this is wrong place to post this question I was unable to in your thread [RECOVERY] [5.1.1] TWRP for Mediapad X2 **UPDATE 12/5/15**.
I have 702L with B006. When I run "fastboot flash recovery twrp_cn.img" from the cmnd prompt I opened in the folder located on desktop with twrp I get an error message 'fastboot' is not recognized as an internal or external command, operable program or batch file. The twrp file is named twrp-eng-5.1.1 I tried "fastboot flash recovery twrp-eng-5.1.1.img" and receive the same message. Any help would be appreciated. I have been trying since you answered my first questions. I am a novice I have successfully rooted several phones in the past by following the XDA instructions.
Forgot to mention I did unlock bootloader or at least I think I did. Fastboot screen shows phone unlocked now.

AzRob82 said:
Sorry if this is wrong place to post this question I was unable to in your thread [RECOVERY] [5.1.1] TWRP for Mediapad X2 **UPDATE 12/5/15**.
I have 702L with B006. When I run "fastboot flash recovery twrp_cn.img" from the cmnd prompt I opened in the folder located on desktop with twrp I get an error message 'fastboot' is not recognized as an internal or external command, operable program or batch file. The twrp file is named twrp-eng-5.1.1 I tried "fastboot flash recovery twrp-eng-5.1.1.img" and receive the same message. Any help would be appreciated. I have been trying since you answered my first questions. I am a novice I have successfully rooted several phones in the past by following the XDA instructions.
Forgot to mention I did unlock bootloader or at least I think I did. Fastboot screen shows phone unlocked now.
Click to expand...
Click to collapse
Do you have the Andoid Tools in the same folder as the TWRP File? Download this and extract it to your desktop and put the TWRP file in with the extracted folder then it should work.
https://docviewer.yandex.com/?url=ya-disk-public%3A%2F%2FvI5Y3Obeku4qzIrtHfPviJPL3yhTpSABBi9V4fM0UpU%3D%3A%2Fadb%2Bfastboot%2Fplatform-tools.zip&name=platform-tools.zip&c=5688b1f6cdb7

new error
Thanks for getting back to me. I didn't realize they had to be in the same folder. I am getting a new message now:
target reported max download size of 471059200 bytes
sending 'recovery'...
FAILED <remote: Command not allowed>
finished. total time : 0.899s
When I unlocked bootloader is said something like status bootloader unlocked. it does show phone unlocked in fastboot. Not sure if i need to go through steps again to unlock bootloader.

AzRob82 said:
Thanks for getting back to me. I didn't realize they had to be in the same folder. I am getting a new message now:
target reported max download size of 471059200 bytes
sending 'recovery'...
FAILED <remote: Command not allowed>
finished. total time : 0.899s
When I unlocked bootloader is said something like status bootloader unlocked. it does show phone unlocked in fastboot. Not sure if i need to go through steps again to unlock bootloader.
Click to expand...
Click to collapse
Yeah unlock it again, sometimes this happens and it says it's unlocked when it isn't.

still at it.
ajsmsg78 said:
Yeah unlock it again, sometimes this happens and it says it's unlocked when it isn't.
Click to expand...
Click to collapse
I am stuck in a boot loop of the hauwei logo when I hold volume up and power. If phone is plugged into pc it goes to stock recovery. I received confirmation that twrp installed from cmd. I tried to download the twrp img again and go through steps before writing you but I get a message error cannot load twrp-eng-5.1.1.img. I cant thank you enough for trying to help me. I plan to formally "thank you" once I get this going. Do you have any suggestions?

AzRob82 said:
I am stuck in a boot loop of the hauwei logo when I hold volume up and power. If phone is plugged into pc it goes to stock recovery. I received confirmation that twrp installed from cmd. I tried to download the twrp img again and go through steps before writing you but I get a message error cannot load twrp-eng-5.1.1.img. I cant thank you enough for trying to help me. I plan to formally "thank you" once I get this going. Do you have any suggestions?
Click to expand...
Click to collapse
Hold in volume down and power when the phone is plugged into the computer to get into fastboot, then you can do a fastboot oem unlock xxxxxxxxxxxxxx. Then boot into fastboot again and flash TWRP. Download the first TWRP if your're already on Android 5.1.1. If not you need do download the one for Android 5.0 from the 2nd link. I think you said you were on B006 so you need to use the TWRP for Android 5.0. When you get to B106 then flash and use the TWRP for 5.1.1.
5.1.1: https://drive.google.com/file/d/0B5I_q70mNuR4Uy1XdXVoSG1SMXc/view
5.0: https://drive.google.com/file/d/0B5I_q70mNuR4R0hHNzRRVXhlQWs/view

still at it
ajsmsg78 said:
Hold in volume down and power when the phone is plugged into the computer to get into fastboot, then you can do a fastboot oem unlock xxxxxxxxxxxxxx. Then boot into fastboot again and flash TWRP. Download the first TWRP if your're already on Android 5.1.1. If not you need do download the one for Android 5.0 from the 2nd link. I think you said you were on B006 so you need to use the TWRP for Android 5.0. When you get to B106 then flash and use the TWRP for 5.1.1.
Thanks for all your help. I am at a loss. I think I just purchased an expensive wifi only tab now that makes calls. I successfully rooted and flashed your CUST MOD B111. I still dont have WCDMA as an option. I am unsure with root access if there is an app or file that will force WCDMA.
I updated my apn settings again per tmobile website. I am able to make calls and can use internet only when on a phone call. if you know of any other options I would really appreciate it.
Click to expand...
Click to collapse

AzRob82 said:
ajsmsg78 said:
Hold in volume down and power when the phone is plugged into the computer to get into fastboot, then you can do a fastboot oem unlock xxxxxxxxxxxxxx. Then boot into fastboot again and flash TWRP. Download the first TWRP if your're already on Android 5.1.1. If not you need do download the one for Android 5.0 from the 2nd link. I think you said you were on B006 so you need to use the TWRP for Android 5.0. When you get to B106 then flash and use the TWRP for 5.1.1.
Thanks for all your help. I am at a loss. I think I just purchased an expensive wifi only tab now that makes calls. I successfully rooted and flashed your CUST MOD B111. I still dont have WCDMA as an option. I am unsure with root access if there is an app or file that will force WCDMA.
I updated my apn settings again per tmobile website. I am able to make calls and can use internet only when on a phone call. if you know of any other options I would really appreciate it.
Click to expand...
Click to collapse
What options do you have? What cell service are you using?
Click to expand...
Click to collapse

I have tmobile with data plan. I am using my note 4 at this time without a problem. I have tried several family members sim cards and went to tmobile to get a new sim card. Only get Internet if I am on a call. It's really weird. I would think it is some setting.

Hi ajsmsg78, I gave up on device for awhile and started messing with it again. After doing a factory reset I have all the preferred network connections you have. The only one that allows me to get internet when I am not on a phone call is GSM which only gives me 2g. I tried WCDMA and internet will not work. Would flashing a different rom possibly help?

VoLTE T-Mobile USA Working on H8324 Xperia XZ2 Compact Dual Stock

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.

TMO 10.5.17.IN55CB installation problem? rooted

is there any way to install this update? every time i try i get an error message that only says "Installation Problem".

eisawi99 said:
is there any way to install this update? every time i try i get an error message that only says "Installation Problem".
Click to expand...
Click to collapse
You can't install updates while rooted. You would need to use MSM tool to go back to stock and then upgrade, afterwards you can root again. T mobile disables the local update option in system update and also only sends out the ota package and not the full system firmware. Just make sure you backup your persist partition before using MSM (recommend using the readback feature F8 of the MSM tool to back it up and then restore persist using fastbootd if it breaks fingerprint).

jeffsga88 said:
You can't install updates while rooted. You would need to use MSM tool to go back to stock and then upgrade, afterwards you can root again. T mobile disables the local update option in system update and also only sends out the ota package and not the full system firmware. Just make sure you backup your persist partition before using MSM (recommend using the readback feature F8 of the MSM tool to back it up and then restore persist using fastbootd if it breaks fingerprint).
Click to expand...
Click to collapse
Is there a guide for doing this using the MSM tool? I'm sure I could figure it out eventually but I'd probably also break something in the process lol.

eisawi99 said:
Is there a guide for doing this using the MSM tool? I'm sure I could figure it out eventually but I'd probably also break something in the process lol.
Click to expand...
Click to collapse
Here's the link to MSM tool:
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
It has a guide in the OP of how to use it. Again, I highly recommend backing up your persist partition using the tool first. Just open tool, press F8, select persist, password is oneplus, connect phone in edl mode, click readback. It will copy your persist to root of your hard drive. Disconnect phone, close and reopen MSM, reconnect phone in edl mode and run MSM tool. Completely restores phone. Update to newest 10.5.17, then if you lost fingerprint, unlock bootloader, then from fastboot type:
Code:
fastboot reboot fastboot
Brings you to a screen with Chinese and English on it, type the following:
Code:
fastboot flash persist persist.img
Replace persist.img with location of your backed up persist. Then you can boot or install TWRP and flash magisk for root.
I had rooted my op8 and wanted the update so did exactly the above, used MSM, lost fingerprint so flashed my backed up persist and everything works great.

jeffsga88 said:
Here's the link to MSM tool:
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
It has a guide in the OP of how to use it. Again, I highly recommend backing up your persist partition using the tool first. Just open tool, press F8, select persist, password is oneplus, connect phone in edl mode, click readback. It will copy your persist to root of your hard drive. Disconnect phone, close and reopen MSM, reconnect phone in edl mode and run MSM tool. Completely restores phone. Update to newest 10.5.17, then if you lost fingerprint, unlock bootloader, then from fastboot type:
Code:
fastboot reboot fastboot
Brings you to a screen with Chinese and English on it, type the following:
Code:
fastboot flash persist persist.img
Replace persist.img with location of your backed up persist. Then you can boot or install TWRP and flash magisk for root.
I had rooted my op8 and wanted the update so did exactly the above, used MSM, lost fingerprint so flashed my backed up persist and everything works great.
Click to expand...
Click to collapse
By completely restores phone, you mean I'll lose all my data? If so it's fine but is there an easy way to back up and restore the data?

eisawi99 said:
By completely restores phone, you mean I'll lose all my data? If so it's fine but is there an easy way to back up and restore the data?
Click to expand...
Click to collapse
Sorry, meant to put that on that reply before. It completely erases your phone. They have the OnePlus switch app, not sure how it is as I've never used it. I use Swift backup from the play store, but it's not completely free (i.e. batch backup and restore isn't free), also know others use titanium backup as well.

Got my update so far pretty unimpressed. Maybe I don't know what I'm doing should it show NR or 5G? Cell mapper will show NR at times, but my phone says 5G. Coverage might have improved some, but not much Decent download speeds, but upload is horrible almost always, sometimes it just errors out,

Christobal34 said:
Got my update so far pretty unimpressed. Maybe I don't know what I'm doing should it show NR or 5G? Cell mapper will show NR at times, but my phone says 5G. Coverage might have improved some, but not much Decent download speeds, but upload is horrible almost always, sometimes it just errors out,
Click to expand...
Click to collapse
Overall, it will not put you on SA (NR only) mode by default. The network will still keep you on NSA (LTE + NR) at most times. Generally, your speeds on NSA will be faster than on SA. The benefit of SA is that you don't need to have good LTE signal to connect to 5G. The issue, current 5G phones can't do calls over NR (VoNR) which means if you force SA mode, you won't be able to make our receive calls. Next year's phones will have VoNR, so SA will matter more then. By the way, cell mapper won't show you much information, the only useful thing to look for on cell mapper regarding 5g right now is the:
Code:
5G State: Connected
If it says that, you're Connected to 5g. If you're Connected to 5g and it gives you no LTE cell information, you should be on SA. There's only 1 app that correctly shows everything for 5g and it's Network Signal Guru, but it requires root and to see 5g info requires the beta version and a license. By the way, phone will show 5g. Another way to tell if on SA, pull down the quick settings and it will say TMO instead of T-Mobile and you can go to the phone dialer and type the following:
Code:
*#*#4636#*#*
Click on phone information and see what it says for data network and voice network, it will say NR if on SA or say LTE if on NSA. You can also force it to NR only with that menu, but again you won't be able to make or receive calls if you do that.

jeffsga88 said:
Overall, it will not put you on SA (NR only) mode by default. The network will still keep you on NSA (LTE + NR) at most times. Generally, your speeds on NSA will be faster than on SA. The benefit of SA is that you don't need to have good LTE signal to connect to 5G. The issue, current 5G phones can't do calls over NR (VoNR) which means if you force SA mode, you won't be able to make our receive calls. Next year's phones will have VoNR, so SA will matter more then. By the way, cell mapper won't show you much information, the only useful thing to look for on cell mapper regarding 5g right now is the:
Code:
5G State: Connected
If it says that, you're Connected to 5g. If you're Connected to 5g and it gives you no LTE cell information, you should be on SA. There's only 1 app that correctly shows everything for 5g and it's Network Signal Guru, but it requires root and to see 5g info requires the beta version and a license. By the way, phone will show 5g. Another way to tell if on SA, pull down the quick settings and it will say TMO instead of T-Mobile and you can go to the phone dialer and type the following:
Code:
*#*#4636#*#*
Click on phone information and see what it says for data network and voice network, it will say NR if on SA or say LTE if on NSA. You can also force it to NR only with that menu, but again you won't be able to make or receive calls if you do that.
Click to expand...
Click to collapse
Thanks for the info. I did force it to NR to test. I personally don't care about speed, but was hoping for better coverage. So do you need the x60 modem to use VoNR?

Christobal34 said:
Thanks for the info. I did force it to NR to test. I personally don't care about speed, but was hoping for better coverage. So do you need the x60 modem to use VoNR?
Click to expand...
Click to collapse
Yeah unfortunately still need to wait for x60 for VoNR (at least that's my understanding is that x50 and x55 don't support VoNR). I wouldn't be surprised if OnePlus patched the modem in the future so even if you force NR that it still detects when you place a call or get a call to drop to LTE for phone call. Samsung appears to have done this with the s20s.

t-mobile and betas

So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3

goast said:
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
Click to expand...
Click to collapse
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.

Global Version
stompysan said:
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Click to expand...
Click to collapse
Do you have a link as to where i can get Global version or steps for getting it ?

j1232 said:
Do you have a link as to where i can get Global version or steps for getting it ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.

stompysan said:
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
Click to expand...
Click to collapse
How can one tell of phone is using 5g SA on OB3?

crazynapkinman said:
How can one tell of phone is using 5g SA on OB3?
Click to expand...
Click to collapse
Using a program like LTE Discovery will tell you. In my case, it indicates I am connected to NR NSA 5G. I have not ever seen my phone go to SA 5G since converting, and I do live in an SA location and have connected while on T-Mobile software. See screenshot.

Mine says 5G NR

crazynapkinman said:
Mine says 5G NR
Click to expand...
Click to collapse
I have noticed it takes some fiddling with WiFi to get it to display network type. The 5G detection is still a WIP. There are probably other apps that may work better, but I am just used to using LTE Discovery over the years.

I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!

xxBrun0xx said:
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
Click to expand...
Click to collapse
I have Sprint sim and this is not happening.