Database Info

[Q] Accidentally set radio to USA band

Hey Folks,
normally I'm a silent reader. Till now I could solve any problems but right now I'm facing a problem which I can't get rid of.
I did the Sim Mod on my Photon q and while trying to get the mobile data working I accidentally set the radio band to "USA band". So now I can't get any connection to a german provider.
I tried to fix this problem with QPST. But failed in the beginning. I downloaded QPST 2.7 Build 378 and tried to get a connection between the phone and QPST with no sucess.
Could anybody help me with aome detailed instructions? Would appreciate it!
Thanks!

You made the same mistake I made.
I solved it by modifying my Photon Q with QPST, I changed the "UMTS System" and selected every Band by "Prefered Band".
Now I would only select those bands which are used in germany.
PS: If you need help in german, ask here for help -> http://www.android-hilfe.de/motorola-photon-q-forum/

HeliPilotMech said:
Hey Folks,
normally I'm a silent reader. Till now I could solve any problems but right now I'm facing a problem which I can't get rid of.
I did the Sim Mod on my Photon q and while trying to get the mobile data working I accidentally set the radio band to "USA band". So now I can't get any connection to a german provider.
I tried to fix this problem with QPST. But failed in the beginning. I downloaded QPST 2.7 Build 378 and tried to get a connection between the phone and QPST with no sucess.
Could anybody help me with aome detailed instructions? Would appreciate it!
Thanks!
Click to expand...
Click to collapse
Download the newest QPST. This is important. Follow this guide to set up QPST http://www.cricketusers.com/sprint-...-q-4g-lte-cricket-talk-text-mms-internet.html. From there, just select all the bands under UMTS (i am not sure on this one, but look through the menus). Selct all the bands and flash. Your phone should be good as new.

amrewsl Systeme
zodiac12345 said:
Download the newest QPST. This is important. Follow this guide to set up QPST http://www.cricketusers.com/sprint-...-q-4g-lte-cricket-talk-text-mms-internet.html. From there, just select all the bands under UMTS (i am not sure on this one, but look through the menus). Selct all the bands and flash. Your phone should be good as new.
Click to expand...
Click to collapse
Thanks zodiac, that helped a lot!
But I'm having trouble with getting my MSL/SPC. I tried to get it with this method: http://forum.xda-developers.com/showthread.php?t=1894038
But the only thing I get is: ~1,1~3,1~5,1~7,1~9,1~11,1
And I also tried this method: http://forum.xda-developers.com/showthread.php?t=1365058
But there I get this message:
Sending 'RDELEM' command with data '278600010000000E' to the radio...
Sent to radio:
TC Send Header: 000800200000000000000008
TC Send Data: 278600010000000E
Returned from radio:
TC Receive Header: 860800200087000000000070
TC Receive Data: 46544D20636F6D6D616E64206661696C65642C2064726976657220657272203D20302C20737461747573203D20313B206661696C656420746F206F70656E2046544D206465766963652C206572726F72203D2032284E6F20737563682066696C65206F72206469726563746F72792900
TC ASCII Error: FTM command failed, driver err = 0, status = 1; failed to open FTM device, error = 2(No such file or directory)
RDELEM ==>FAILED
Driver answer ==> -4
Error Description ==> Unknown Error
Time to execute command: 0 seconds.
Command timeout set to : 15 seconds.
Any ideas how to get my MSL/SPC?

Sent from my Nexus 7 using xda app-developers app

A User in the german Android-Hilfe.de forum have pointed at this two posts:
parin11 said:
ON Jellybean it not working
On ICS Its reading SPC perfectly
Click to expand...
Click to collapse
x86Daddy said:
I was receiving the same wrong number many have posted (~1,1~3,1~5,1~7,1~9,1~11,1)... because my used Photon Q arrived with 4.1.2 already installed. Here's the high level steps I took to get my MSL:
I unlocked the bootloader through Motorola
I installed the latest TWRP recovery for the Photon Q (2.6.0.0 in my case), using the fastboot method described here
I installed the ICS stock rom from this XDA thread
I tried the MSL retrieval batch file tool again. I had to click the OK after verifying the empty code for the batch tool to work.
I have a working MSL code now.
I then wiped the OS again and installed the latest Cyanogenmod nightly.
Thanks to this community and to the author of this batch from the CricketUsers site!!!
Click to expand...
Click to collapse
Maybe it will be helpful.

[Q] [HELP NEEDED BADLY] XPERIA Z ULTRA (SOL24) - Unlock

Hello XDA Members,
I recently obtained an Xperia Z Ultra from Japan - AU KDDI with model name SOL24 (32GB). I was eager to have it unlocked so I tried flashing the C6833 (Global Xperia Z Ultra) latest Kitkat ROM to it.
It was a success, however, later did I found out that I should have excluded the partition as it is now reporting only 16GB of usable space. I then decided to go back to SOL24's original stock rom (4.1) but I keep on encountering error message - to follow.
I hope someone out there can share his thoughts or tips on this matter.
Issues:
1. SOL24 not able to unlock / use with other SIM Cards
2. SOL24 not able to recognize 32GB and unable to return to STOCK AU KDDI ROM as well.
*Unable to unlock via NCK Code since phone is not requesting for any unlock pin when a different SIM is inserted.
*Also tried procedure from htsoku.info but it was not applicable to me
*Tried rolling back Android 4.4 to original SOL24 AU KDDI ROM but encountered this error:
12/018/2014 13:18:50 - INFO - Start Flashing
12/018/2014 13:18:50 - INFO - Processing loader.sin
12/018/2014 13:18:50 - INFO - Checking header
12/018/2014 13:18:50 - ERROR - Processing of loader.sin finished with errors.
12/018/2014 13:18:50 - INFO - Ending flash session
12/018/2014 13:18:50 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80060011 ";
Thanks for reading.

franceiam said:
Hello XDA Members,
I recently obtained an Xperia Z Ultra from Japan - AU KDDI with model name SOL24 (32GB). I was eager to have it unlocked so I tried flashing the C6833 (Global Xperia Z Ultra) latest Kitkat ROM to it.
It was a success, however, later did I found out that I should have excluded the partition as it is now reporting only 16GB of usable space. I then decided to go back to SOL24's original stock rom (4.1) but I keep on encountering error message - to follow.
I hope someone out there can share his thoughts or tips on this matter.
Issues:
1. SOL24 not able to unlock / use with other SIM Cards
2. SOL24 not able to recognize 32GB and unable to return to STOCK AU KDDI ROM as well.
*Unable to unlock via NCK Code since phone is not requesting for any unlock pin when a different SIM is inserted.
*Also tried procedure from htsoku.info but it was not applicable to me
*Tried rolling back Android 4.4 to original SOL24 AU KDDI ROM but encountered this error:
12/018/2014 13:18:50 - INFO - Start Flashing
12/018/2014 13:18:50 - INFO - Processing loader.sin
12/018/2014 13:18:50 - INFO - Checking header
12/018/2014 13:18:50 - ERROR - Processing of loader.sin finished with errors.
12/018/2014 13:18:50 - INFO - Ending flash session
12/018/2014 13:18:50 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80060011 ";
Thanks for reading.
Click to expand...
Click to collapse
Hey I'm planning to get a SOL24 as well so I might be able to help you. Just to check - when the phone is started up is there an English language option? I can't read kanji ...

christcentric said:
Hey I'm planning to get a SOL24 as well so I might be able to help you. Just to check - when the phone is started up is there an English language option? I can't read kanji ...
Click to expand...
Click to collapse
Yes there is a language selection screen. Only some apps will be left in Kanji since most of them are native japanese apps.

franceiam said:
Yes there is a language selection screen. Only some apps will be left in Kanji since most of them are native japanese apps.
Click to expand...
Click to collapse
anu update on this? I have my sol24 with same issue. sim unlock code does not prompt.

thor0002 said:
anu update on this? I have my sol24 with same issue. sim unlock code does not prompt.
Click to expand...
Click to collapse
What I did to enable the Unlock Code Prompt was flashed it with a ROM for the international version of Xperia Z Ultra. PLEASE BE WARNED, exclude the PARTITION part to prevent your 32GB Internal Memory from being just 16GB. It happened to me and now I am still looking for ways on how to restore that missing 16GB.
BTW, Unlock Code worked fine and I was able to use the Phone with three (3) different carriers so far (PH: SMART, PH: GLOBE & JP: Softbank). Originally it was just AU.
Hope someone can help us.

franceiam said:
What I did to enable the Unlock Code Prompt was flashed it with a ROM for the international version of Xperia Z Ultra. PLEASE BE WARNED, exclude the PARTITION part to prevent your 32GB Internal Memory from being just 16GB. It happened to me and now I am still looking for ways on how to restore that missing 16GB.
BTW, Unlock Code worked fine and I was able to use the Phone with three (3) different carriers so far (PH: SMART, PH: GLOBE & JP: Softbank). Originally it was just AU.
Hope someone can help us.
Click to expand...
Click to collapse
Thanks for the information but kinda newbie here. Is there any reliable source\link that can help me to this procedure of enabling the Unlock Code prompt? What particular ROM int'l version of Xperia Z ultra that I can use? How to flash? Please help me

franceiam said:
What I did to enable the Unlock Code Prompt was flashed it with a ROM for the international version of Xperia Z Ultra. PLEASE BE WARNED, exclude the PARTITION part to prevent your 32GB Internal Memory from being just 16GB. It happened to me and now I am still looking for ways on how to restore that missing 16GB.
BTW, Unlock Code worked fine and I was able to use the Phone with three (3) different carriers so far (PH: SMART, PH: GLOBE & JP: Softbank). Originally it was just AU.
Hope someone can help us.
Click to expand...
Click to collapse
In the AU SOL24 ROM- It does not have the regular APN settings Instead it has something similar settings - CPA settings. I input all details for AU iPhone sim detail (I have an AU iPhone sim)
Cannot save the settings - gives me some error.
My case is worse - I have an AU iPhone sim and yet I cannot use the AU SOL24 handset.
How did you input the 3 carrier settings in your handset.
Any help can be appreciated.
Cheers
Roy

Unlocking sol24
Bossing,pede malaman saan mo nakuha unlocking code mo at magkano?
(May I please ask where you got your unlocking code and how much?)

Flashing unbranded ROM

I reently became a happy owner of black XZP and i love it but there is one thing that irritates me, it came with Orange branded software. My question is, can i flash original unbranded software (when flashtool will provide this option) without loosing IMEI,DRM keys, bravia engine and such ? And where can i find this kind of software ?
Also i heard from SONY centre Poland, that even if i do this myself somehow, it will return to the branded software with next software update as the software is tied to phones IMEI...
Would be gratefull for some extended explanation on this. Thanks.

Probably not since it probably locked to the Orange. You will need to get the network unlock code first before flashing a generic firmware.

Well I know that the XZ Premiums in Australia aren't locked, my friend got one from Telstra and then uses an Optus SIM in it.
Flashing generic FW won't cause you to lose DRM keys, etc, since only unlocking the bootloader will cause that stuff to be affected.
Also, even if the phone is network locked, I don't see why generic FW would affect that - That should only impact what carrier SIM you can use on the phone.

I used newflasher to flash customized UK version on my Vodafone branded version a couple of days ago, and received update for customized UK version this morning, updated ok, no probs.

Renesco said:
I reently became a happy owner of black XZP and i love it but there is one thing that irritates me, it came with Orange branded software. My question is, can i flash original unbranded software (when flashtool will provide this option) without loosing IMEI,DRM keys, bravia engine and such ? And where can i find this kind of software ?
Also i heard from SONY centre Poland, that even if i do this myself somehow, it will return to the branded software with next software update as the software is tied to phones IMEI...
Would be gratefull for some extended explanation on this. Thanks.
Click to expand...
Click to collapse
I got a happy owner too, yesterday :highfive: , Wanted to flash EU firmware but flashtool is not working, found newflasher thread but have no idea how to use it, anybody point me to the instructions? Also it would be great if somebody give me a link for download, found this https://forum.xda-developers.com/cr...ewflasher-xperia-command-line-t3619426/page33 but booth files contain malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/

pawnstar said:
I got a happy owner too, yesterday :highfive: , Wanted to flash EU firmware but flashtool is not working, found newflasher thread but have no idea how to use it, anybody point me to the instructions? Also it would be great if somebody give me a link for download, found this https://forum.xda-developers.com/cr...ewflasher-xperia-command-line-t3619426/page33 but booth files contain malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/
Click to expand...
Click to collapse
I flashed mine two days ago on Windows 10 v1607.
I used the "old" version linked in the other thread. It is right that virus total show that there is some malware but only 2 of 64 AV product say that, I think that is a false positive.
First download your firmware with XperiFirm, pay attention on device version (single or dual sim)
Download Sony companion app and try to make a software repair (until it ask you to shutdown the phone and connect it with volume down button pressed), it will download and install Sony official flash driver (needed for flash the firmware with newflasher).
After that abort Sony software repair and download newflasher.
Go to the firmware folder extract partition.zip (this will allow new flasher to flash partition layout)
Also move away from the folder sim-lock.ta for security purpose (new flasher should have a check but bug can exist)
Copy newflasher.exe to the firmware folder
Shutdown the phone, press volume down button and plug-in the usb cable (Same instruction of Sony companion app), you should see windows driver configuration.
Wait driver configuration to finish and then run newflasher.exe as administrator
Wait until it finish (some system files flash can take minutes to flash don't worry) and check if there are errors in log.

Had problems with yellow triangle in driver but after using companion software per your instruction drivers got installed and everything went ok, flashed central eu version 1 and I'm happy now Many thanks!

Trout777 said:
I used newflasher to flash customized UK version on my Vodafone branded version a couple of days ago, and received update for customized UK version this morning, updated ok, no probs.
Click to expand...
Click to collapse
im on three and want to flash to uk customised ?
got sorted guys well pleased

Need Help with IMEI fix for Asus Zenfone 3 Max

Hello all
in need of some urgent but easy help fixing the IMEI invalid / null issue with the phone i recently had to flash a Rom on
details of phone:
Asus Zenfone 3 Max
model ZC520TL or as seen in screenshot X008D
chipset MT6737M
Current Android Version 7.0 original version out of box was 6.0
the situation
i recently was forced to flash the phone due to it being completely dead had contacted Asus support they gave me the current version of the firmware i am using now ( Android 7.0 ) the original out of the box was ( Android 6.0 ).... the phone has now finally fired up and is operational as far as being able to access menus and connecting to my Wi-Fi
the issue i am faced with is invalid IMEI number as can be seen in screenshot had a look around the web and there seems to be a number of tools to deal with this issue but sadly none have helped me i have tried using MTK Engineering mode but when it comes to following the instructions given by some forums i get stuck at the point where it states CDS as this option is missing from the list
other tools require the AP BP database files and i cannot seem to find them online ones i can find don't match my chipset version... i also cannot pull files from the phone as the phone is not rooted and phone either fails to root or has some permission issue and says contact your IT administrator
bottom line is i would really like to get the phone to do what a mobile phone was designed for so does anyone have a simple solution
i should also note i spotted in my Wi-Fi list an error it reads NVRAM WARNING: Err = 0x10 but my Wi-Fi is working
please see screenshots for more info
thank you all

Same problem

fix imei with maui meta
easy way with maui meta

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.