Database Info

Carrier Unlocking Sprints Photon Q

Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one

Morecrabs said:
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Click to expand...
Click to collapse
1. No
2. Yes
You need to be on stock ics firmware for the NV edit to succeed and stick.
Use Android 4.0.4 Blur_Version.77.8.14.XT897.Sprint.en.US - http://sbf.droid-developers.org/phone.php?device=3
If you're downgrading from jellybean, you have to remove the line with flash gpt_main0.bin from the xml file, otherwise the flashing via rsdlite will fail.
Code:
[STRIKE]<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="6C05E70F1DCC59AD92B0BBEC4E6100ED" />[/STRIKE]
The firmware thread is here: http://forum.xda-developers.com/showthread.php?t=2095536
Then you can follow this (RadioComm):
http://forum.xda-developers.com/showthread.php?t=2166542
or this (CDMA WS) guide:
http://forum.xda-developers.com/showthread.php?t=2386871
After it's done, you should flash the stock Android 4.1.2 via rsdlite, then install CM10.2 (or any other custom ROM) again.

soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?

Morecrabs said:
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Click to expand...
Click to collapse
That development ID is simply for identifying your device under debugging circumstances like ADB, every device has them. Also, flashing another ROM changes this value.
Sent from Google Nexus 4 @ CM11

ok so that was a dumb decision to come to, but its not something id ever seen on any of my other android devices, Droid 1,2,4 samsung captivate glide, so i figured it was related to the developer Models
Do I need to run my copy of radio Comm on a 32 bit machine to accomplish this hacking?
my 64 bit machines seem to have driver related issues with the software

was wondering if anyone could help me setup the drivers, I keep getting errors with Radio comm and cdma workshop, and it all boils down to driver issues, with cdma workshop i cant get the QC port setup because IM missing a driver, and with radio comm, I cant get it to communicate properly with the phone once i boot into fastboot any help suggestions? ive installed the moto drivers and setup on a PC with a 32 bit version of win7 starter to allow radio comm to setup properly
In radio comm it will ID the phone as xt897 and i can get software version if its booted into OS, but it will do nothing else

Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http://bork.cs.fau.de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
Code:
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https://github.com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
EDIT2: This is now included as "unlock-us-gsm" in CM12.0 and up on XT897, XT907 and XT926. To use it run "unlock-us-gsm" in a root shell:
Code:
[email protected]_c:/ # unlock-us-gsm
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Reading value of NV-item 8322...
GSM locked in the US: 1
Setting value of NV-item 8322 to 0...
Reading value of NV-item 8322...
GSM locked in the US: 0
Setting logging_mode to usb...
Regards,
Michael

stargo said:
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer
Click to expand...
Click to collapse
Excellent! I picked a good day to try to figure out how to do this, I was making notes of all the various steps (install ics on phone, use radiocomm on pc, install jb on phone, then cm on phone) when I got to this post and realized I won't need to do any of that, thanks much!

Terminal Emulator Question
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http //bork cs fau de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
[CODE
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
[/CODE]
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https //github com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
Regards,
Michael
Click to expand...
Click to collapse
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.

DroidRazrMv said:
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
Click to expand...
Click to collapse
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.

arrrghhh said:
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
Click to expand...
Click to collapse
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.

DroidRazrMv said:
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
Click to expand...
Click to collapse
Still confused as to where you're having issues - we are both talking about the same post. If you look, kabaldan's post redirects to the one I am referencing....

So once these steps are used to unlock the phone, which carriers can be used and how does flashing of carrier info occur?

Just want to say thanks again Michael. I just got my new Photon Q back from having sim card slot installed, ran your program and it worked perfectly on 21OCT2014 CM nightly.
I did also change a couple settings in the phone menu too, cuz I put an AT&T sim card in it, but sprint kept calling me to activate. Seems to be working well now, but not sure I understand everything, does this seem right - in regular CM11 settings menu under Mobile network settings, I set Preferred network type to "GSM/WCDMA Auto".
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
Click to expand...
Click to collapse

VoLTE - i9505 International for Jio - Easy way.

I am not a developer but a HW guy.
This applies only to i9505 international version with Qualcomm processor as tested.
Please note that whoever tries the following, upon failure and/or ending up with bricked phone(s), incurring any loss, implied or direct, resulting from the application of what is described in this post, including but not limited to time, warranty, update from Samsung including security updates, resources, financial or otherwise,etc., does not point a finger in my direction but, does so at his/her own risk.
(Hope I scared a few).
The unit that I used originally had XXUHPK2 - XST firmware.
Whatever given below are personally experienced after quite a bit of searching, testing and few near misses including SIM not being detected or infinite loops when searching for network to register due to my own experimentation with Modem and NON-HLOS files.
But I never once lost my IMEI as the method is fairly straightforward. Always God "ODIN" is there to the rescue.
This applies to those who do not want an "always on" Jio4GVoice app and prefer to stay with stock recovery. Of course custom recovery can always be installed.
I have used PI1_VOLTE_JIO FW available on this forum but had faced few issues related to calling out at times, more so when I travel long distance. If I stay put at certain places it always worked.
Now to the works:
1. Using ODIN install I9505XXUPOL1_I9505PHNPOL1_PHN FW. - Search to download FW.
Nordic version of FW with PI1 modem "may" be used but I found network search for registering yields less number of networks. I have not tried using the Nordic FW.
2. Root the device using CF-Auto-Root.
3. Search for "Volte fix.zip" and download. Easiest way to get links to download is YouTube. In the zip file I used all files have 07-11-2016 as creation date. I found VoLTEFiles zip too with the same dates but did not try it so far.
4. Watch the YouTube, say, at "watch?v=MlkaziK6AkY" or any other relevant VoLTE zip file installation video to get the gist of the method before attempting.
5. The zip contains an Apks folder and a Files folder. Extract APK, csc folder, CSCVersion.txt and SW_Confgiuration.xml to a known folder preferably in ext-sd if available.
6. Install root explorer. It is under extracted Apks folder. Allow for installation of app from unknown sources.
7. Open Root Explorer browse to /system directory. Rename existing csc folder, CscVersion.txt and SW_Configuration.xml with some leading characters as fall back. The csc folder and the files can optionally be deleted as well.
Root Explorer will require the patition to be mounted as RW saying it is Read Only. Say OK to proceed.
8. Copy and paste the above folder and files obtained from zip to /system.
9. Change permissions via Root Explorer as below:
Touch the folder or file under Root Explorer. Once selected touch 3 dots on top right and select permissions. Given numbers can be directly entered using Octal button.
csc folder - 755 octal
CscVersion.txt - 644 octal
SW_Configuration.xml - 644 octal
10. Exit Root Explorer and Reboot. And wait patiently for a while until the two way sign appears on status bar. It really takes a while.
Call Settings - "Outgoing voice call settings" automatically shows "Use VoLTE when available".
Factory reset does not restore VoLTE icon on status bar and calling is not possible as well. Wait for a while for the phone to complete all processes after setting up. Reboot to get VoLTE back.
It seems to take a while and the Sammy phone will show a report being sent when connected to WiFi... to inform you later when you select "Software Update" that the phone has modified in an un-authorized way, etc.
Calling and messaging works even with WiFi ON.
I have not provided any link as the credit should go where it belongs.
See screenshots in the attached thumbnails.
ODIN Version used 3.12.7
CF-Auto-Root available on this forum.
And most importantly thanks to the developer who created the VoLTE fix files. And a special thanks to @dhiru1602 with his PI1-VOLTE-JIO ROM as it was instrumental in making me search and test.

Does this work on other S4 not for JIO and on other networks?

treysis said:
Does this work on other S4 not for JIO and on other networks?
Click to expand...
Click to collapse
Sorry for the belated reply. I was using it on Jio only as no other nw providers were offering VoLTE at that time. Now the unit is with someone else in another country. I learnt VoLTE is available in that country and will request to get it checked. Will revert with results.

hey, no problem and thanks for the help! Have you heard back from your friend yet?

treysis said:
hey, no problem and thanks for the help! Have you heard back from your friend yet?
Click to expand...
Click to collapse
Yes and a No - On one network it does not show the icon. He is not sure if the ISP actually implemented VoLTE though announced last year. On the other he has not tested as yet. Says needs to get the 4G SIM. Will wait for some more time and revert again.

Ok. I know for sure that my network and my SIM support VoLTE, cause I am using it on another Samsung handset and it's working fine. But on the S4 no luck yet.

Btw. I just put a Malaysian SIM and this enabled VoWiFi in the settings. But couldn't try it as the card is not fully active anymore.

[GUIDE] Enabling LTE on China Telecom (and others) on Pixel 3 XL (Android 10)

Being a huge fan of the Pixel series and living in China is not easy. Just upgraded my XL to 3 XL and naturally I had to enable the LTE to work in China. Regardless what you may see on the Chinese forums (gfan), all the files you need are already present on the phone.
Files you need:
1) The ADB bridge for Windows
2) The most recent factory image
3) Magisk Manager
4) Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (Magisk Manager module) - Github direct: https://github.com/wangdaning/Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (big thank you to wangdaning for allowing me to publish it.) Also attached as a zip file to this post.
If you don't understand what these files are for or where to find them, perhaps you should ask a friend to help you. Flashing anything wrong could result in an expensive brick. Always backup your data, never blindly trust a post, and do your research. This post is in good faith and I am not liable for your actions.
Now, I don't have any of the variants of 3 (Pixel 3, 3a, 3a XL) but I would assume it would work in a similar fashion; however, see above and do your research. Check file structures, read some posts, backup data, etc. If someone does try it, please report both success and failure to build the knowledge.
1) We need to ensure our phone has an unlocked bootloader. If your bootloader is locked, you WILL lose all your data. Ensure you backup everything you want to keep. There is no getting around this step. We need to be a developer first. Go to Setting->About Phone->Build number (tap it until it says you are a developer). Then go to System-> Developer options -> OEM unlocking: turn it on. Next we need to reboot to the bootloader by resetting the phone and hold the down volume key as it reboots. In the bootloader, first use the volume keys to find and select the unlock the bootloader command with the power key. Then, we need to send the following command:
Code:
fastboot flashing unlock
You will receive a wipe and security warning. Accept and reboot the phone. It will wipe and reset your phone to factory.
2) I started from a stock image (May update; QQ2A.200501.001.B2). I suggest you start from there.
3) While we have the May update in front of us, we need to extract the boot.img so it can be patched to root the phone. TWRP doesn't support us at the time of writing on Android 10. (Hope that new baby is healthy!) The boot image can be found in the zip image-crosshatch-*release code*.zip/boot.img. Transfer this boot.img to the phone to be modded to enable root.
4) Next the phone needs to be rooted. You need to download the most recent version of Magisk Manager. Once installed, open up Magisk Manager. It will report no Magisk and that's ok, we are installing it now.
5) Tap install on Magisk and it will ask if you want to install, so install. Then you need to select the method. We will choose "Select and patch a file." Tell it where you saved your boot.img and it will patch it to allow us to root the phone. The output file we need is called magisk_patched.img is on the phone. Move it back to your directory with your ADB bridge.
6) Next we need to flash this patched boot file to our phone to complete the rooting process. Reboot to the bootloader and send the two commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Reboot the phone and congrats, you are rooted with an unlocked bootloader.
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
8) Download the LTE_enabler from Github or the zip file here. Open Magisk Manager and open the menu -> Modules -> "Yellow Plus" to add. Point it to the zip file.
9) Reboot and enjoy using your phone as intended.
I tried to be as detailed as I could but not be over verbose either. If any step is unclear, there are more detailed guides on this forum concerning bootloader unlocking and Magisk rooting on Android 10. As a bonus tip, does the "x" showing no data bother you and stop some services from working? If so, this can be fixed by re-pointing your captive portal to something inside the firewall. This can be accomplished with one line of code:
Code:
adb shell "settings put global captive_portal_https_url https://developers.google.cn/generate_204"
Enjoy and if you have questions about Pixel and China, feel free to post them. Support right to repair!

I downloaded the zip file but it tells me it's not a module.

jifengSherry said:
I downloaded the zip file but it tells me it's not a module.
Click to expand...
Click to collapse
Could use more details, otherwise it is hard to help. It definitely is a module and installs fine. Something else is going on.

is this for china only? I have a Canadian 3 XL and moved to Bucharest, need to enable VOLTE on Orange Romania. I'm also on Android 11

It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?

wangdaning said:
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
Click to expand...
Click to collapse
I contacted Orange and they say VOLTE should be working, that the issue is my device not being compatible with their network. I also bought a Samsung watch 3 with LTE and can't activate LTE through my phone, i assume it's due to the same issue.
I'll follow your guide and report back.
Should be no issue if i am using Android 11 instead of 10 right?

Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
Click to expand...
Click to collapse
If that does not work then you need to modify the module to include the romania mbn.

wangdaning said:
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
If that does not work then you need to modify the module to include the romania mbn.
Click to expand...
Click to collapse
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!

angeluszero said:
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
Click to expand...
Click to collapse
ok i spoke too fast, while VOLTE is enabled now in the settings, when i make a call, it switches to H+ which means its not using VOLTE. any idea? I modified the .txt file to include the location of the romania .mbn file, i modified the file directly on the phone though, after installing the module with magisk manager

Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.

wangdaning said:
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
Click to expand...
Click to collapse
I did that, both VOLTE and Wifi calling say provisioned. I guess it might be something on Orange's end.
I saw a reddit post for a Pixel 3 having the same issue and the carrier ended up doing something on their side.

Confirmed working on Pixel 3 w/ Android 11!

Can this patch work on Pixel 4 as well? Thank you

duffercn said:
Can this patch work on Pixel 4 as well? Thank you
Click to expand...
Click to collapse
You would have to find the location of the files on the Pixel 4 as I am not sure where they are. Then modify the module to point to the correct location.

Mmw_rf_card removed

This setting has to have a reverse right? Anyone samsung service menu savvy?
What happened is Mmwave was disabled and a factory reset didn't fix

Hey, If! are you familiar with the efs file explorer...? Or QPST. I found out how to get it mmWave back working
Remove mmWave RF Card - Shared with pCloud
Keep all your files safe, access them on any device you own and share with just the right people. Create a free pCloud account!
u.pcloud.link
Use this file... Save it to your phone... Remove the (.bin)... Transfer to your computer... Use efs... Go to /nv/item_files/rfnv/
Copy the file here
When you download the file it comes with (.bin)... Remove that from the name
Then save it to your computer
Once you save it to your phone using efs explorer, power down your phone and then go to the Samsung secret menu and enable all the bands like normal,
***
That might only work for Galaxy Z Fold 2.
If that is not working for your particular phone, You'll have to contact someone that has the same you like you and extract the files with QPST from: /nv/item_files/rfnv/* and copy it to your phone with QPST
***
Thank u/VincentMartel007 from Reddit!

I did the same thing by accident… I am trying to get QPST to work with my S22 Ultra but it is saying that the file system does not exist. Does my phone need to be rooted? I tried the “NV REBUILD ALL” but mmWave still doesn’t show up in the menu

Keltonb said:
I did the same thing by accident… I am trying to get QPST to work with my S22 Ultra but it is saying that the file system does not exist. Does my phone need to be rooted? I tried the “NV REBUILD ALL” but mmWave still doesn’t show up in the menu
Click to expand...
Click to collapse
Which version of QPST?
(No root needed)
Note: You have to connect first ( Sometimes search to find and add the port) with QPST Configuration and then start the client from there.
Also, make sure your Samsung driver is updated

Dude you are a godsend my mmwave is BACK! thank you so much this work for the s20 ultra I think it'll work for whatever phone as long as it has the same modem the x55 modem you are a godsend can you tell me how you found out exactly what this file was?
Because if you know that then you know exactly what files are the 5G bands with hex coding and so on and and I would like to talk to you please

Adding the file for S21+ device if anybody need it in future .

US Verizon provisioning on a XZ2

I just bought a Xperia XZ2 H8276 since the sim pins finally broke in my Xperia X Performance after about 4 year, word of advice don't make a sim work. Was not finding a Xperia XZ2 compact under $200 and the newer 5's are expensive, so that was the choice I made. It did not dawn on me that the move to volte only would make it hard to get newer unlocked phones on a nework. In trun looking into options pertaining to volte, switching to verizon was the only one that seemed to have a viable path. Talked with at&t where I found them unwilling to add my imei and don"t see a mdn that is clear cut for them, do see a mdn for tmobile but no service by my house. Verizon dose have dmd and they got the XZ2 compact, so there was light at the end of the tunel. So got the cheapest volte phone that I could find to activate a sim on, a moto e5 play is what I found. Will get to aguing with them now to add my imei since it work, unsure how that is going to go.
To get statrted a activated sim is needed and was done using the moto e5. After activation, need to talk with someone and have them check that sim the sim is CDMA-less with HD voice only. Best place I found to do that is start a chat with someone on this page, click chat in bottom right.
Verizon HD voice
For how I got the XZ2 to work on verizon gose like this based on many failed attempts. What I ended up doing is flashing H8216 Vodafone_Global_52.1.A.3.49-R9C firmware with H8314 Customized US_52.1.A.3.137-R7C oem sin files with newflasher, you can get these these off xperiafirm.
NewFlasher
XperiaFirm
Now with that in order, the verizon mbn needs added but need root to do so. If you dont have twrp that need installed and be sure to sideload magisk at the same time, other wise you will have boot loop to deal with.
TWRP
Magisk
After the phone has booted into the os, you need to now install the magisk app. Run this from whre you downloaded the application to your pc or install from the browser on the phone, need to cd to the place of download first if using terminal.
adb install Magisk-v23.0.apk
Magisk app
Here is the verizon mbn I pulled from the XZ2c modem sin.
Verizon mbn
That needs copyed to the phone SD card and use Root explorer to copy the mbn where it gose. I tryed PDC but could not get the drivers to work.
Root Explorer
You can you use this to install it if debug is on or down from the phone browser, cd to where you downloaded the file then...
adb install RootExplorer.apk
Now in root explorer, this is the destination to go and can only go there if root has been granted. If you dont get the promt to grant root go into magisk, click the shield at boot then the slider by the app. To copy the generic folder here from the sd card, click and hold it till hilighted where you can click the two papers stacked at the top. There will now be a clip board icon in the bottom right, do to the destination and click it.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw
The internal and external sd card will be one these two locations, ether use "adb push" or mtp to the put the directory on the sd card.
/storage/*-* *=a string of letters and numbers
/storage/emulated/0
/storage/self/primary
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see this under current modem config
row/verizon/vl/us
Now dial this.
*#*#4636#*#*
Under phone information set network type to lte only and should see voice type lte. If all went well, you should now be able to make phone calls.
I would like to move on to installing lineage-os but volte was not working there. I need to use this phone for work, so am not going to get into debuging that. Be my guess to try but Im not sure what brakes installing that.
I got some help from junkie2100 and give thanks to those that have posted info/software that lead me this far in gettting volte working. Here are some the clues that aided in the journey.
clues
clues
clues
As for tmobile, you might be able to replicate this but intead use oem sin's from the xz3 H8416 US along with pulling its mdn out its modem sin. Not sure what is special in the oem sin that pertains to setting up the given carrier, so unsure what is needed to get at&t to work but you free to experiament if you choise just I will not be much help.

Thanks for taking the time to put this together, the information on getting VoLTE working in the US on the XZ2 seems to be pretty scattered across various threads over the last several years, so I appreciate you placing this here.
I am not on Verizon, but I have been trying to figure out how to get this working on T-Mobile. I have followed some other threads that point to downloading the XZ3 OEM sin files as part of its Customized US Firmware like you mentioned, replacing those in the stack for the XZ2 firmware of a matching/similar version, and flashing to my device. I noticed after doing that VoLTE is provisioned (greyed out but turned "on"), but the modem config when checking my settings is still "Unknown." In addition to that, setting the device to "LTE Only" causes calls to not be placed, and "LTE Preferred" leads to calls dropping down to 3G like they originally were before trying to flash anything.
I could maybe use a little help in understanding what you mean be "pulling the mdn out of the modem sin." Is this an additional step to just flashing the two OEM files mentioned above and if so, where would I find it and go about setting it up?
Appreciate it.

The mbn file you need is in the modem sin from the xz3 firmware and this is the binary you need to extract it, put both the unsin binary and modem_X-FLASH-ALL-B6B5.sin in the same folder. This is the config file used by the oem sin to setup the volte.
unsin binary
Now cd to the folder that has both those and run these commands.
./unsin ./modem_X-FLASH-ALL-B6B5.sin
mkdir ./modem
sudo mount -t vfat -o loop modem_X-FLASH-ALL-B6B5.img modem/
You now have the modem sin extracted and the image mounted in folder modem. From there you need a copy of this tmobile folder and move it to the sd card on the phone.
/image/modem_pr/mcfg/configs/mcfg_sw/generic/row/tmobile
Now you can umount the modem image.
sudo umount -t vfat modem_X-FLASH-ALL-B6B5.img modem/
Now on the phone in root explorer that tmobile folder gets copyed to here.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/row
In this file you will also need to add these two lines so the mbn can be found.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw//mbn_sw.txt
mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn
mcfg_sw/generic/row/tmobile/vlvw/us/mcfg_sw.mbn
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see one these under current modem config
row/tmobie/vl/us
row/tmobile/vlvw/us

Would anyone care to guess if a rooted/ rom'ed 8216 model of the XZ2 will work on T-mobile now that they have declared many older phone models incompatible (perhaps related to VoLTE capability)? 1mouse3 does your phone still work on T-Mobile? Thanks!