Develop Bugs

HTC u12+ VOLTE activation method in non-released countries

Hello, I am a Korean user who likes htc very much. I have shared how to activate tta-volte volte to the developer of gsi Viper, who develops a lot for htc products, although my English is not good enough, and I'll give you some information now.
It has been 10 years since HTC already closed its business in Korea, so there is no Korean telecommunications company or supplier file, and it does not sell. It's sad. Anyway, let me explain. Originally, HTC products were not allowed to open Qualcomm ports, but only U12+ can open Qualcomm ports
(adb shell - su - setprop sys.usb.config rndis,diag,adb)
Volte in Korea is an independent tta-volte method, so I have the same Qualcomm Snapdragon 845 and I extracted efs files and mbn from Sony Xperia xz2 Korean version firmware, which was officially released in Korea, and pasted them using Qualcomm epsproler.
If the communication company you are using has its own standard like Korea, you can replace the efs file in the same way as I do, and if that doesn't matter, please read the following immediately.
Note the HTC system folder. There is a secret in the system custom folder. First, if you look at customize - MNS folder, it's a number.I see xml. There is a secret in that number. The number is the carrier code. It's very simple. I found this. It was such a pleasure. Please correct the xml title. For example, it is 45008 because it is KT(koreatelecom) mcc:450 mnc:08 You can check the carrier's mcc, mnc(apn) and modify it to 45008.xml and if you look in the custom folder, there is mns_map.xml. Edit the file as text If you enter the 45008th place you changed earlier and reboot, you will be able to create a volte active menu on the existing phone app setup screen.
This is all, simple. When you add an xml (app:mcc+mnc) title in the mns folder, write and save the number that was just added in the custom folder-mns_map_xml text editor, and reboot, the htc phone app settings show the volte activation menu, and there are no other changes to the build-prop In the case of Korea, it was necessary to modify the efs file because it is volte in a nonstandard way.
Modifying directly to root file editor without module It's very simple. My last hope is that volte is possible at gsi and that htc will continue to announce new flagships and that htc users are all healthy, thank you.
*To you in Seoul*

htcmage said:
Hello, I am a Korean user who likes htc very much. I have shared how to activate tta-volte volte to the developer of gsi Viper, who develops a lot for htc products, although my English is not good enough, and I'll give you some information now.
It has been 10 years since HTC already closed its business in Korea, so there is no Korean telecommunications company or supplier file, and it does not sell. It's sad. Anyway, let me explain. Originally, HTC products were not allowed to open Qualcomm ports, but only U12+ can open Qualcomm ports
(adb shell - su - setprop sys.usb.config rndis,diag,adb)
Volte in Korea is an independent tta-volte method, so I have the same Qualcomm Snapdragon 845 and I extracted efs files and mbn from Sony Xperia xz2 Korean version firmware, which was officially released in Korea, and pasted them using Qualcomm epsproler.
If the communication company you are using has its own standard like Korea, you can replace the efs file in the same way as I do, and if that doesn't matter, please read the following immediately.
Note the HTC system folder. There is a secret in the system custom folder. First, if you look at customize - MNS folder, it's a number.I see xml. There is a secret in that number. The number is the carrier code. It's very simple. I found this. It was such a pleasure. Please correct the xml title. For example, it is 45008 because it is KT(koreatelecom) mcc:450 mnc:08 You can check the carrier's mcc, mnc(apn) and modify it to 45008.xml and if you look in the custom folder, there is mns_map.xml. Edit the file as text If you enter the 45008th place you changed earlier and reboot, you will be able to create a volte active menu on the existing phone app setup screen.
This is all, simple. When you add an xml (app:mcc+mnc) title in the mns folder, write and save the number that was just added in the custom folder-mns_map_xml text editor, and reboot, the htc phone app settings show the volte activation menu, and there are no other changes to the build-prop In the case of Korea, it was necessary to modify the efs file because it is volte in a nonstandard way.
Modifying directly to root file editor without module It's very simple. My last hope is that volte is possible at gsi and that htc will continue to announce new flagships and that htc users are all healthy, thank you.
*To you in Seoul*
Click to expand...
Click to collapse
What is the firmware version for your phone, can you support your explanation by images?

htcmage said:
Hello, I am a Korean user who likes htc very much. I have shared how to activate tta-volte volte to the developer of gsi Viper, who develops a lot for htc products, although my English is not good enough, and I'll give you some information now.
It has been 10 years since HTC already closed its business in Korea, so there is no Korean telecommunications company or supplier file, and it does not sell. It's sad. Anyway, let me explain. Originally, HTC products were not allowed to open Qualcomm ports, but only U12+ can open Qualcomm ports
(adb shell - su - setprop sys.usb.config rndis,diag,adb)
Volte in Korea is an independent tta-volte method, so I have the same Qualcomm Snapdragon 845 and I extracted efs files and mbn from Sony Xperia xz2 Korean version firmware, which was officially released in Korea, and pasted them using Qualcomm epsproler.
If the communication company you are using has its own standard like Korea, you can replace the efs file in the same way as I do, and if that doesn't matter, please read the following immediately.
Note the HTC system folder. There is a secret in the system custom folder. First, if you look at customize - MNS folder, it's a number.I see xml. There is a secret in that number. The number is the carrier code. It's very simple. I found this. It was such a pleasure. Please correct the xml title. For example, it is 45008 because it is KT(koreatelecom) mcc:450 mnc:08 You can check the carrier's mcc, mnc(apn) and modify it to 45008.xml and if you look in the custom folder, there is mns_map.xml. Edit the file as text If you enter the 45008th place you changed earlier and reboot, you will be able to create a volte active menu on the existing phone app setup screen.
This is all, simple. When you add an xml (app:mcc+mnc) title in the mns folder, write and save the number that was just added in the custom folder-mns_map_xml text editor, and reboot, the htc phone app settings show the volte activation menu, and there are no other changes to the build-prop In the case of Korea, it was necessary to modify the efs file because it is volte in a nonstandard way.
Modifying directly to root file editor without module It's very simple. My last hope is that volte is possible at gsi and that htc will continue to announce new flagships and that htc users are all healthy, thank you.
*To you in Seoul*
Click to expand...
Click to collapse
Dear htcmage,
Can you post the detailed step by step on how to do this?
Regards,
Brian

Carrier Aggregation

Does realme X support carrier aggregation?

I think this device support 2CA but i don't combinations so then i can't confirm network support. Someone who have this device please get logs https://mt-tech.fi/en/how-to-get-4g...droid-phone/#OnePlus,_Oppo_and_RealMe_devices and send these to so i can add this device to my site: https://cacombos.com/contribute
I have few Oppo devices listed already: https://cacombos.com/search?key=Oppo

U want this log?
https://drive.google.com/file/d/1Ggn5S-fiHAOXk7km7ysgH6Szff019QrH/view?usp=drivesdk

rupeshmaurya35 said:
U want this log?
https://drive.google.com/file/d/1Ggn5S-fiHAOXk7km7ysgH6Szff019QrH/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you for the log but there missing some information. Can you test again but wait little bit longer so your device connect to 4G back. Also i need your device model number, you can find it on Android Settings -> About so then i can add it to my site.

Ok, here is the log
And my device is RMX1901 Global variant
And please let me know about the process if it supports 2CA .
And by the way I am using NSG but i don't have Premium licences ,so i can't load log file from NSG. I use it for band locking only.
https://drive.google.com/file/d/1HNVJ8j7JNzoy94cXSMRGLyU7jBHPyItd/view?usp=drivesdk

rupeshmaurya35 said:
Ok, here is the log
And my device is RMX1901 Global variant
And please let me know about the process if it supports 2CA .
And by the way I am using NSG but i don't have Premium licences ,so i can't load log file from NSG. I use it for band locking only.
https://drive.google.com/file/d/1HNVJ8j7JNzoy94cXSMRGLyU7jBHPyItd/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry again but this log file did not again include any combos. So you have to first start log recording on Get QXDM log -> open device log. Then put your phone Airplane mode on and off. Wait minute to get your phone connected to 4G-network. Then repeat this step few times. Then you can close log and share log file.
Oh yes NSG Premium only allow reading logs and Signaling data.

I have done the same last time , check screenshot for values may be something wrong there.

rupeshmaurya35 said:
I have done the same last time , check screenshot for values may be something wrong there.
Click to expand...
Click to collapse
Looks like your settings are fine. Open logging, then put your device to Airplane mode on, wait your phone connect to 4G (1min), then put your phone back to Airplane and repeat step. This should include all data in log.

I have tried every possible band and CA is not supported in Realme X

rupeshmaurya35 said:
I have tried every possible band and CA is not supported in Realme X
Click to expand...
Click to collapse
I think Realme support only Contiguous CA but without modem log impossible verify. in cacombos.com/contribute there is instructions how to get log.

olkitu said:
I think this device support 2CA but i don't combinations so then i can't confirm network support. Someone who have this device please get logs https://mt-tech.fi/en/how-to-get-4g...droid-phone/#OnePlus,_Oppo_and_RealMe_devices and send these to so i can add this device to my site: https://cacombos.com/contribute
I have few Oppo devices listed already: https://cacombos.com/search?key=Oppo
Click to expand...
Click to collapse
LTE RRC OTA Packet
version : 20
phyCellId : 231
freq : 1251
sfn : 0
Channel : 8
ul-dcch
message -> c1 -> ueCapabilityInformation
rrc-TransactionIdentifier : 2
criticalExtensions -> c1 -> ueCapabilityInformation-r8
ue-CapabilityRAT-ContainerList
[0]
rat-Type : eutra
ueCapabilityRAT-Container
accessStratumRelease : rel12
ue-Category : 4
pdcp-Parameters
supportedROHC-Profiles
profile0x0001-r15 : true
profile0x0002-r15 : true

How To Guide VoLTE, VoWIFI, and 5G in AUS

Hello Fellow OP9 Pro users
I just wanted to start a thread for anyone interested in a OP9/Pro in australia that wanted to get Volte, VoWIFI, and 5G working.
I have tested this and confirmed that it is 100% working for Telstra & Vodafone, I have good word that this method will also work on Optus but don't actually have an Optus sim to test this with.
Huge shout out to happiboi from the OP8 forums for the methods used to get this all working with A11.
First step is to download the oneplus logkit from this link: https://downloadmirror.co/1MW9/com.oem.oemlogkit_1.0-1.apk
Once this has been installed, open the dialer on the phone and type in *#800#, tap on the "oneplus logkit" button, scroll down and tap on "Function switch", then tap on "VoLTE switch" but do not click restart click cancel. Then Tap on "VoWiFi switch" this time press reboot.
Once the phone has rebooted open settings, Wi-Fi & Network, SIM & network, SIM 1, then enable both the toggles for VoLTE and VoWIFI. This is probably also a good time to ensure 5G is enabled under "Prefer network type".
Now what we have done so far is essentially just enable the toggles for everything to work, what we still need to do is actually configure the phone to work on the Australian mobile networks, this is where the information and hard work from happiboi really comes in. I have quoted the guide from happiboi below as it is very well written anyway.
happiboi said:
Code:
Prerequisites:
* Need ADB suite available on PC & enabled "ADB debugging" on phone via developer options
* When you permit your PC adb access to the phone after first adb command, make sure you tick always permit this device. When the phone boots after "adb reboot ftm", the screen is inactive so you can't authorise the device when you try to adb shell and are stuck
* Need QPST suite of apps installed on PC (needed PDC tools + EFS explorer)
* If on custom firmware - probably a good idea to backup your phone before you do this. On custom firmware after the first "adb reboot ftm" rebooting again puts the device in a boot loop until you format data
Process:
- Open command prompt on PC & navigate to where your ADB suite is located
- Type command without "":
"adb devices" (I like to do this to ensure adb can speak with phone/computer)
- Should display:
List of devices attached
<if working, your device should be listed here (else, it'll be blank)>
- Type command without "":
"adb reboot ftm"
--> This puts phone into field test mode
- Type command without "":
"adb shell"
--> Creates dialogue for shell command on phone
- In the shell (OnePlus8Pro:/ $ ) type command without "":
"setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb"
--> This opens up ports that we used to be able to in Android 10
- Phone Screen is still blank - but it's OK.
- Start up PDC Tool in Admin mode on PC
- Click drop down, select phone connection (there's only 1 in the list)
--> ** If the drop-down box is empty and no phone/device listed, you cannot proceed.
--> ** Other users have foudn this to be related to a Qualcomm driver issue.
--> ** Delete the drivers you have currently installed and get a new one from here:
--> ** https://gsmusbdriver.com/install-qualcomm-usb-driver.
--> ** Also once the device shows up in PDC don't click on it, open efs explorer and let it start searching directories --> ** before going back to PDC and clicking on the device in the drop down.
--> ** The window may say 'not responding' just leave it until the carrier list populates then carry on with below steps
- Do the profile activation stuff for Telefonica_UK_Commercial:
- Look for "Telefonica_UK_Commercial", right click and SetSelectedConfig for both Sub0 and Sub1
- Click on the above profile again and click on Activate
- Do not restart your phone
- Don't close PDC yet (don't know if it make a difference but I didn't close)
- Open EFS Explorer (I opened in Admin mode too)
- Navigate to "\nv\item_files\ims\"
- Replace ims_user_agent file with one supplied
--> The supplied one has Telstra VoLTE Qualcomm as header instead of Telefonica
- Navigate to "\policyman"
- Replace carrier_policy.xml & carrier_policy.xml_Subscription01 with ones supplied.
--> Just take carrier_policy.xml and make a copy named "carrier_policy.xml_Subscription01"
--> ** Caveat, I further modified the carrier_policy.xml file as it wasn't enabling 5G for me on my IN2020 (Android 11) Oneplus 8 Pro.
--> ** I changed the nr5g_sa_bands base & nr5g_nsa_bands base values to be "hardware" rather than specifically band n78.
--> ** This changes config to allow whatever 5G bands the hardware has available rather than specific bands
--> ** You can't enable bands that the hardware doesn't support anyway so makes sense to enable all
--> ** This gave me the needed 5G access with Telstra
- Type command without "":
"adb reboot"
After phone boots back up, 5G + VoLTE + VoWiFi are all intact and in working order!
[/QUOTE]
Click to expand...
Click to collapse
I am extremely interested to see if anyone running the A12 beta would try this and see what sort of results they are able to achieve.
Cheers guys.

Thanks for this. Can confirm that this works for the UK as well. I'm on VOXI (Vodafone) and saw no option for wifi calling. Just followed the first part to download the logkit, enabled switch, wifi calling working

mhall156 said:
Hello Fellow OP9 Pro users
I just wanted to start a thread for anyone interested in a OP9/Pro in australia that wanted to get Volte, VoWIFI, and 5G working.
I have tested this and confirmed that it is 100% working for Telstra & Vodafone, I have good word that this method will also work on Optus but don't actually have an Optus sim to test this with.
Huge shout out to happiboi from the OP8 forums for the methods used to get this all working with A11.
First step is to download the oneplus logkit from this link: https://downloadmirror.co/1MW9/com.oem.oemlogkit_1.0-1.apk
Once this has been installed, open the dialer on the phone and type in *#800#, tap on the "oneplus logkit" button, scroll down and tap on "Function switch", then tap on "VoLTE switch" but do not click restart click cancel. Then Tap on "VoWiFi switch" this time press reboot.
Once the phone has rebooted open settings, Wi-Fi & Network, SIM & network, SIM 1, then enable both the toggles for VoLTE and VoWIFI. This is probably also a good time to ensure 5G is enabled under "Prefer network type".
Now what we have done so far is essentially just enable the toggles for everything to work, what we still need to do is actually configure the phone to work on the Australian mobile networks, this is where the information and hard work from happiboi really comes in. I have quoted the guide from happiboi below as it is very well written anyway.
I am extremely interested to see if anyone running the A12 beta would try this and see what sort of results they are able to achieve.
Cheers guys.
Click to expand...
Click to collapse
Hey there,
I'm glad this is working for you too - the credit really goes back to all the XDA users who have helped to give guidance in creating these steps
For anyone reading and interested, it has now been confiremd working on OP6, 7, 8 and 9 series phones (as well as Nord).
Great way to get features that should be 'enabled' from OP themselves and remember you will need to do this after every system/OTA update to re-enable these functions.
Happy days, cheers all!

Thanks so much! This worked perfectly for me with an 8pro on Telstra. I work in an area with a 4G only tower so haven't been able to make calls for the last 6 months!
Could the same methodology be followed for my colleague's Xiaomi mi 10t pro 5g?
happiboi said:
Hey there,
I'm glad this is working for you too - the credit really goes back to all the XDA users who have helped to give guidance in creating these steps
For anyone reading and interested, it has now been confiremd working on OP6, 7, 8 and 9 series phones (as well as Nord).
Great way to get features that should be 'enabled' from OP themselves and remember you will need to do this after every system/OTA update to re-enable these functions.
Happy days, cheers all!
Click to expand...
Click to collapse

jbell87 said:
Thanks so much! This worked perfectly for me with an 8pro on Telstra. I work in an area with a 4G only tower so haven't been able to make calls for the last 6 months!
Could the same methodology be followed for my colleague's Xiaomi mi 10t pro 5g?
Click to expand...
Click to collapse
There's no harm in trying on the Xiaomi.
The other way to attempt this was the original process outlined here: https://forum.xda-developers.com/t/volte-and-vowifi-in-australia.4095097/post-82847027
The only reason we (OnePlus users) had to change our method was because OP closed off access to the efs ports after the android 11 updates.

Not working whit Ho mobile Italy carrier
Ho can restore the original versione of. com.oem.oemlogkit
Regards

Thanks a lot for this! thought I was being screwed by Telstra the whole time.
Confirmed working on LE2123, Oxygen build 11.2.6.6.LE15BA with Telstra 5G, VoWIFI & VoLTE, though when installing the Qualcomm driver in Device Manager I had to use the "Qualcomm HS-USB WWAN Adapter 9091" option to make my phone show up in QPST.

happiboi said:
Hey there,
I'm glad this is working for you too - the credit really goes back to all the XDA users who have helped to give guidance in creating these steps
For anyone reading and interested, it has now been confiremd working on OP6, 7, 8 and 9 series phones (as well as Nord).
Great way to get features that should be 'enabled' from OP themselves and remember you will need to do this after every system/OTA update to re-enable these functions.
Happy days, cheers all!
Click to expand...
Click to collapse
Hey there! I have a Nord (EU AC2003 model) and I'm in Bulgaria on the Telenor network. I don't care about VoLTE or VoWIFI but I do want to be able to use 5G as my carrier supports it (and should be compatible with the phone as they are using the n78 band according to Wikipedia and the phone supports it).
On the phone Telenor said it needed no special activation on their side so this is an issue with the device. I don't have the 5G option in preferred network selection at all so I thought this guide would help until I saw that the XML files are for Telstra.
You said that it has been confirmed to work on Nord, my question is, would this guide work specifically to force the phone to use 5G (I have already tried enabling it through the engineering menu via dialing *#*#4636#*#* but that doesn't work for me)? My second question is whether it would be possible for someone show me how to modify the XML files for my carrier (Telenor BG)/modify them for me if that's the case?

mhall156 said:
Hello Fellow OP9 Pro users
I just wanted to start a thread for anyone interested in a OP9/Pro in australia that wanted to get Volte, VoWIFI, and 5G working.
I have tested this and confirmed that it is 100% working for Telstra & Vodafone, I have good word that this method will also work on Optus but don't actually have an Optus sim to test this with.
Huge shout out to happiboi from the OP8 forums for the methods used to get this all working with A11.
First step is to download the oneplus logkit from this link: https://downloadmirror.co/1MW9/com.oem.oemlogkit_1.0-1.apk
Once this has been installed, open the dialer on the phone and type in *#800#, tap on the "oneplus logkit" button, scroll down and tap on "Function switch", then tap on "VoLTE switch" but do not click restart click cancel. Then Tap on "VoWiFi switch" this time press reboot.
Once the phone has rebooted open settings, Wi-Fi & Network, SIM & network, SIM 1, then enable both the toggles for VoLTE and VoWIFI. This is probably also a good time to ensure 5G is enabled under "Prefer network type".
Now what we have done so far is essentially just enable the toggles for everything to work, what we still need to do is actually configure the phone to work on the Australian mobile networks, this is where the information and hard work from happiboi really comes in. I have quoted the guide from happiboi below as it is very well written anyway.
I am extremely interested to see if anyone running the A12 beta would try this and see what sort of results they are able to achieve.
Cheers guys.
Click to expand...
Click to collapse
i previously had 5g working and volte but ever since i updated firmware for the 8t i lose it i also did the steps which got me 5g before still with no success hopefully this will help which you editing stuff for telstra. the ims whch you put for telstra do i need it im with optus

Just wanted to say this guide is working with an Optus network sim card in Australia!
Carrier: Moose Mobile (Optus)
Device: One Plus 8 Pro (In2020)
Android version 11
As @LordFigTree mentioned I also had to use the "Qualcomm HS-USB WWAN Adapter 9091" driver.
Other than that flawless guide, thank you very much to everyone who made this possible!

error:S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

By.TRabZonLu™ said:
error:S
View attachment 5405019
Click to expand...
Click to collapse
Might be something to do with the special characters in your user file name? Not sure but it might be worth trying to copy the file from the root of your drive.

Lofty248 said:
Might be something to do with the special characters in your user file name? Not sure but it might be worth trying to copy the file from the root of your drive.
Click to expand...
Click to collapse
Unfortunately it has nothing to do with it. The problem still persists, I couldn't fix it, I gave up.

Lofty248 said:
Just wanted to say this guide is working with an Optus network sim card in Australia!
Carrier: Moose Mobile (Optus)
Device: One Plus 8 Pro (In2020)
Android version 11
As @LordFigTree mentioned I also had to use the "Qualcomm HS-USB WWAN Adapter 9091" driver.
Other than that flawless guide, thank you very much to everyone who made this possible!
Click to expand...
Click to collapse
did you change anything with the carrier policy and carrier_policy.xml_Subscription01? also the ims file? im on optus aswell

Unfortunately this guide doesn't seem to work anymore, the after the last two updates (now on Oxygen OS 11.2.10.10.LE15BA) try the same process but it i don't see it working.

LordFigTree said:
Unfortunately this guide doesn't seem to work anymore, the after the last two updates (now on Oxygen OS 11.2.10.10.LE15BA) try the same process but it i don't see it working.
Click to expand...
Click to collapse
Hey Mate,
I'm running 11.2.10.10.LE15BA and is working flawlessly for me, have tried both Vodafone AU and Telstra sims with no issues.

Damn ok i'm doing something wrong then, i'll try again, thanks for the info.

LordFigTree said:
Damn ok i'm doing something wrong then, i'll try again, thanks for the info.
Click to expand...
Click to collapse
East as mate, let me know how you go!
I'm just here hoping OOS12 doesn't break this method lmao

mhall156 said:
East as mate, let me know how you go!
I'm just here hoping OOS12 doesn't break this method lmao
Click to expand...
Click to collapse
Weird, just did it exactly the same as I did last time but it has now worked, showing i have full 5G connection.
Thanks @mhall156 i wouldn't have tried again if you didn't say it's still working for you, not sure how i screwed it last time but glad i got 5G back.

Awesome, I'm glad it's working! I have had some attempts not work for seemingly unknown reasons. I've just restarted the phone and tried again and have always seemed to make it work.
It's a shame we have to go through this to make our otherwise great phones work properly.

General Sony Xperia 10 iii Additional LTE/5G Band Unlocks

Hi,
The 10 iii uses the Snapdragon X51 Modem. This modem seems to be in very few phones at the moment, however, the modem is the same on the OnePlus Nord N10 5G and Nokia X20 . Both of these devices are available in the US and contain some additional bands that the 10 iii does not.
With the Xperia 10 iii most likely not receiving a US Customized firmware in the future, is there any path forward with modifying the bands that are available on the modem?
Currently, my progress is as follows...
1. Root the 10 iii with Magisk -​
This is easily done by downloading firmware with XperiFirm, extracting the boot.sin, "unsinning" it to get a boot.img, patching the boot.img with Magisk, and then flashing the modified boot.img with fastboot. To do this, the bootloader must be first unlocked. Simply use the factory method of unlocking the bootloader. Generate a code for the Sony Xperia 10 ii (as the 10 iii isn't listed yet, but the codes are interchangeable, this applies to all iii devices like the 5 and 1, just use the ii codes). Unlocking the bootloader will wipe the device and lose the Sony DRM keys.​​2. Qualcomm QPST Connection -​
Most Qualcomm modems support their QPST application. This diagnostic application allows you to interface with the modem on your phone and change it's parameters. The process to connect to that application involves installing their modem drivers, opening the com port on your pc to connect to your phone, and initiating the connection.​​Here is a guide on setting it up that pertains to the 1 ii, but is relevant to most Sony devices. Note that the "enable Qualcomm diag" step contains a correction for us.....​"setprop persistent.sub.eng 1" should be "setprop persist.usb.eng 1" and installing the drivers (9018, not 9020) on the device in device manager should contain the "MI_00" hardware ID instead.​​3. Digging in to the files​
Here is where my roadblock begins and expertise falls off. The modem contains many xml files that can be edited to set bands, enable data features, etc. Most relevant files appear to be in the "policyman" folder. However, my efforts on actually having any edits make any impact have been a zero sum game. Making changes to the band_set_01 and carrier_policy files seems to make no difference on enabled bands, how it connects to my network (Verizon), etc.​​​​Any one have any ideas or thoughts? Is this path forward even possible?
Below are links to the policyman files that I extracted from the modem. Feel free to download them and view/modify. If other modem files would like to be looked at, just let me know. Most other files seem to be an unknown file format and not easily modified xml.
Here is a copy of the stock 10 iii policyman folder (note my carrier_policy is standard Verizon) - Download
Here is a copy of a modified band_set_01. I basically added all Verizon bands to all rf_band_lists that could be US related.
I have tried various carrier_policy changes. Also attempted to use generic/pre-made ones from other devices that contain more defined rules. Here is an example of one I tried from a OnePlus 9
Thanks!
​​​​

Hi, were you really able to root the phone the way you described? Or is this just the theoretical steps? Because currently it's not even possible to unlock the bootloader on this phone (yet, hopefully) which would forbid the flashing of a modified boot.img as far as I know.
Looks like we'll have to wait some more before anything really moves for this phone.

combinedfleet said:
Hi, were you really able to root the phone the way you described? Or is this just the theoretical steps? Because currently it's not even possible to unlock the bootloader on this phone (yet, hopefully) which would forbid the flashing of a modified boot.img as far as I know.
Looks like we'll have to wait some more before anything really moves for this phone.
Click to expand...
Click to collapse
Yes, the device is able to be rooted normally with Magisk. To unlock the bootloader, just generate a code for a Xperia 10 ii, they work just fine. Note that unlocking the bootloader will wipe the device and lose DRM keys. https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code I have edited the OP to include this step.

I can help you to list all devices supported bands and 4G & 5G combinations if you like to contribute log to cacombos.com/contribute. Qualcomm diag option is best for Sony devices when rooted.
You can't edit firmware defined combinations because these are compiled and signed by Qualcomm. To edit these have to recompile from source and sign. And of course the firmware source is not public and signing keys are very secure.

olkitu said:
I can help you to list all devices supported bands and 4G & 5G combinations if you like to contribute log to cacombos.com/contribute. Qualcomm diag option is best for Sony devices when rooted.
You can't edit firmware defined combinations because these are compiled and signed by Qualcomm. To edit these have to recompile from source and sign. And of course the firmware source is not public and signing keys are very secure.
Click to expand...
Click to collapse
I planned on contributing to your website!
I know I stop logging with ctrl+c, but, is there a limit to amount of qmd1 files that are created per proc_type?
The example on ca combos looks like it moves on to the next proc_type automatically? Below is my current terminal.
Code:
XQ-BT52:/sdcard/diag_logs $ su
ogs -f /sdcard/diag_logs/Diag.cfg -m /sdcard/diag_logs/Diag.cfg <
diag_mdlog: command = o
diag_mdlog: command = f
diag_mdlog: command = m
diag:main: kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
diag: No Session is active for the given mask
diag_mdlog: Closing diag_fd_temp
diag_mdlog: Warning output directory already exists: /sdcard/diag_logs
diag_mdlog: Proceeding...
diag_mdlog: Diag_LSM_Init succeeded.
REMOTE PROCESSOR MASK 0
diag:kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
logging switched
Output dirs /sdcard/diag_logs --- /sdcard/diag_logs
diag: check_for_diagid_cmd DIAG_GET_DIAG_ID
diag_mdlog: Reading mask for MSM, proc_type: 0
Reading the mask file: /sdcard/diag_logs/Diag.cfg
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
creating new file /sdcard/diag_logs/diag_log_20210703_1119471625325587206.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1123011625325781935.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1127191625326039079.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1131261625326286642.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1136221625326582083.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1140061625326806999.qmdl

@olkitu I stopped the logging after about 20 minutes. Submitted the logs to cacombos.

Archerpunk said:
@olkitu I stopped the logging after about 20 minutes. Submitted the logs to cacombos.
Click to expand...
Click to collapse
Got it and now supported combinations of this device listed here: https://cacombos.com/device/XQ-BT52 (HW combos).
During logging seems you have only enabled LTE bands 4 and 5.
This device sold in US? This is global model - same sold in Europe too. Device missing US combinations.
Archerpunk said:
I planned on contributing to your website!
I know I stop logging with ctrl+c, but, is there a limit to amount of qmd1 files that are created per proc_type?
The example on ca combos looks like it moves on to the next proc_type automatically? Below is my current terminal.
Code:
XQ-BT52:/sdcard/diag_logs $ su
ogs -f /sdcard/diag_logs/Diag.cfg -m /sdcard/diag_logs/Diag.cfg <
diag_mdlog: command = o
diag_mdlog: command = f
diag_mdlog: command = m
diag:main: kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
diag: No Session is active for the given mask
diag_mdlog: Closing diag_fd_temp
diag_mdlog: Warning output directory already exists: /sdcard/diag_logs
diag_mdlog: Proceeding...
diag_mdlog: Diag_LSM_Init succeeded.
REMOTE PROCESSOR MASK 0
diag:kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
logging switched
Output dirs /sdcard/diag_logs --- /sdcard/diag_logs
diag: check_for_diagid_cmd DIAG_GET_DIAG_ID
diag_mdlog: Reading mask for MSM, proc_type: 0
Reading the mask file: /sdcard/diag_logs/Diag.cfg
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
creating new file /sdcard/diag_logs/diag_log_20210703_1119471625325587206.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1123011625325781935.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1127191625326039079.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1131261625326286642.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1136221625326582083.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1140061625326806999.qmdl
Click to expand...
Click to collapse
No limits but file size by default max 100MB and then create new one automatically.

olkitu said:
Got it and now supported combinations of this device listed here: https://cacombos.com/device/XQ-BT52 (HW combos).
During logging seems you have only enabled LTE bands 4 and 5.
This device sold in US? This is global model - same sold in Europe too. Device missing US combinations.
No limits but file size by default max 100MB and then create new one automatically.
Click to expand...
Click to collapse
Yes, it appears this device only supports bands 4 and 5 for the Verizon Network.
It isn't sold in US, but is sold globally. Most other regions (EU, Asia, Etc) seem to have specific customized firmware with mostly similar bands.
Is there a way to export all the CA combos in a format for the Carrier Policy?

Archerpunk said:
Yes, it appears this device only supports bands 4 and 5 for the Verizon Network.
It isn't sold in US, but is sold globally. Most other regions (EU, Asia, Etc) seem to have specific customized firmware with mostly similar bands.
Is there a way to export all the CA combos in a format for the Carrier Policy?
Click to expand...
Click to collapse
For now there is no tool to export Qualcomm format out.

Was hoping this thread would bear some fruit because if band difference is a solely software matter these days, rooting should allow us full access to all the features of any damn phone.

Archerpunk said:
Hi,
The 10 iii uses the Snapdragon X51 Modem. This modem seems to be in very few phones at the moment, however, the modem is the same on the OnePlus Nord N10 5G and Nokia X20 . Both of these devices are available in the US and contain some additional bands that the 10 iii does not.
With the Xperia 10 iii most likely not receiving a US Customized firmware in the future, is there any path forward with modifying the bands that are available on the modem?
Currently, my progress is as follows...
1. Root the 10 iii with Magisk -​
This is easily done by downloading firmware with XperiFirm, extracting the boot.sin, "unsinning" it to get a boot.img, patching the boot.img with Magisk, and then flashing the modified boot.img with fastboot. To do this, the bootloader must be first unlocked. Simply use the factory method of unlocking the bootloader. Generate a code for the Sony Xperia 10 ii (as the 10 iii isn't listed yet, but the codes are interchangeable, this applies to all iii devices like the 5 and 1, just use the ii codes). Unlocking the bootloader will wipe the device and lose the Sony DRM keys.​​2. Qualcomm QPST Connection -​
Most Qualcomm modems support their QPST application. This diagnostic application allows you to interface with the modem on your phone and change it's parameters. The process to connect to that application involves installing their modem drivers, opening the com port on your pc to connect to your phone, and initiating the connection.​​Here is a guide on setting it up that pertains to the 1 ii, but is relevant to most Sony devices. Note that the "enable Qualcomm diag" step contains a correction for us.....​"setprop persistent.sub.eng 1" should be "setprop persist.usb.eng 1" and installing the drivers (9018, not 9020) on the device in device manager should contain the "MI_00" hardware ID instead.​​3. Digging in to the files​
Here is where my roadblock begins and expertise falls off. The modem contains many xml files that can be edited to set bands, enable data features, etc. Most relevant files appear to be in the "policyman" folder. However, my efforts on actually having any edits make any impact have been a zero sum game. Making changes to the band_set_01 and carrier_policy files seems to make no difference on enabled bands, how it connects to my network (Verizon), etc.​​​​Any one have any ideas or thoughts? Is this path forward even possible?
Below are links to the policyman files that I extracted from the modem. Feel free to download them and view/modify. If other modem files would like to be looked at, just let me know. Most other files seem to be an unknown file format and not easily modified xml.
Here is a copy of the stock 10 iii policyman folder (note my carrier_policy is standard Verizon) - Download
Here is a copy of a modified band_set_01. I basically added all Verizon bands to all rf_band_lists that could be US related.
I have tried various carrier_policy changes. Also attempted to use generic/pre-made ones from other devices that contain more defined rules. Here is an example of one I tried from a OnePlus 9
Thanks!
​​​​
Click to expand...
Click to collapse
In lte_feature_ca_mcc entries of each operator, you need to edit them and add combinations for your operator

Question editing a file /priv-app/imsservice/imsservice.apk for adding a profile IMS For VoLTE

some background,
I am after thorough tests on the topic of how it works VoLTE and VoWiFi And what causes it to be activated in some providers and in some not.
The source from which I drew all a lot of information was: https://volteromania.blogspot.com/p/samsung-voltevowifi-settings.html?m=1
Actually, I followed all the steps but got stuck on the most important part.
In order to start communication for VoLTE It is necessary to define a profile IMS.
Samsung chose - unlike APN Not to allow any user to create such a profile, but the profiles are inside files json in the file /system/priv-app/imsservice/imsservice.apk
I am very interested in trying to edit the files json These, but all my attempts were unsuccessful.
I have a Samsung S21 ultra Rooted, on which I perform the tests.
I can't edit the APK without hurting him. Any change in it causes the application not to load - and completely disables the service IMS and the registration.
The files I want to edit are in
/priv-app/imsservice/imsservice.apk/res/raw
It's files json simple.
Maybe someone can help me?

im curruntly trying to enable Volte on Samsung SM-N920L korean phone in defferent region..no luck..im rooting for you..if any succuss please let we know too..

I gave up.
This is Samsung's behavior on purpose to make consumers have to replace the phones.
Anyway, in the technical part,
In Android 13, in my opinion, this is not completely possible, since every change in the application damages the signature, but even in older versions it is necessary to change the Java code as well, And as you know it is compiled.
I spent many hours on this, with several devices, I purchased a Galaxy 7 for the tests, and I failed.

I do not know if this still works, but on my SM-9700 (HK) with Android 10 I made VoLTE work in Germany by copying the "product/omc/DBT/conf" from a SM-970F to the corresponding TGY directory of the SM-9700.

I was able to run volte on the galaxy s7.
It requires a lot of changes.
Including in the smali files of the application imsservice.apk and it was a nightmare.
In my case I had to add a brand new provider that didn't appear anywhere, maybe that's why everything was complicated and maybe if it's a defined operator and just enabling the option is simpler.
Anyway,
It really wasn't easy, but I had most of the information from the first post I wrote, but I was also able to find a lot on my own.
It is not easy.
Maybe Samsung will release the source code (including java) of the imsservice.apk application and then it will be easier..

Have you ever tried just copying the content of the conf directory from another phone?
This made VoLTE work on my Hong Kong Note10 (Snapdragon) in Germany.

ZXR said:
Have you ever tried just copying the content of the conf directory from another phone?
This made VoLTE work on my Hong Kong Note10 (Snapdragon) in Germany.
Click to expand...
Click to collapse
I have nowhere to copy. I don't have a phone that works with the same carrier I wanted to test. I had to write all the settings myself.

Which carrier do you need? We (the forum) might copy it for you.

shmuel0990 said:
I was able to run volte on the galaxy s7.
It requires a lot of changes.
Including in the smali files of the application imsservice.apk and it was a nightmare.
In my case I had to add a brand new provider that didn't appear anywhere, maybe that's why everything was complicated and maybe if it's a defined operator and just enabling the option is simpler.
Anyway,
It really wasn't easy, but I had most of the information from the first post I wrote, but I was also able to find a lot on my own.
It is not easy.
Maybe Samsung will release the source code (including java) of the imsservice.apk application and then it will be easier..
Click to expand...
Click to collapse
Can you please share knowlage with us..im tring for days now..i tried with csc options..added everything in customer.xml ,others.xml
i read the files inside immservice app..there are lines for my carrier.. cant understand what to add..by the way using a activity manager.. i opened a ims settings page..
Is there something i can change for carrier? Photo attached

prasadmanjulago said:
Can you please share knowlage with us..im tring for days now..i tried with csc options..added everything in customer.xml ,others.xml
i read the files inside immservice app..there are lines for my carrier.. cant understand what to add..by the way using a activity manager.. i opened a ims settings page..
Is there something i can change for carrier? Photo attached
Click to expand...
Click to collapse
t what phone is this
I tried Galaxy S7, Android 8.
I don't think the solution I came up with is suitable for every device.

shmuel0990 said:
t what phone is this
I tried Galaxy S7, Android 8.
I don't think the solution I came up with is suitable for every device.
Click to expand...
Click to collapse
thanks. i succeeded yesterday...i didnt edit imsservice.apk
i found enforceskippingpackages.xml file in system/csc_contents folder
in the only couple of lines
imsservices.apk
imslogger.apk
imssettings.apk etc
i removed those ims lines.. then volte worked.. i already added enable volte lines on csc/others.xml and customer.xml before.
i didnt edit anything on the attached screenshot i sent on above reply
thanks,,,

prasadmanjulago said:
thanks. i succeeded yesterday...i didnt edit imsservice.apk
i found enforceskippingpackages.xml file in system/csc_contents folder
in the only couple of lines
imsservices.apk
imslogger.apk
imssettings.apk etc
i removed those ims lines.. then volte worked.. i already added enable volte lines on csc/others.xml and customer.xml before.
i didnt edit anything on the attached screenshot i sent on above reply
thanks,,,
Click to expand...
Click to collapse
Hello, I don't know how it made to work for you. I have the same problem but the ims lines are already no longer present in the enforceskippingpackages.xml file and the volte does not work...

thib66 said:
Hello, I don't know how it made to work for you. I have the same problem but the ims lines are already no longer present in the enforceskippingpackages.xml file and the volte does not work...
Click to expand...
Click to collapse
i already made some changes to others.xml and customer.xml file also..What country are you? Send me telegram or whatsapp no..ill send my files and figure whays wrong

shmuel0990 said:
t what phone is this
I tried Galaxy S7, Android 8.
I don't think the solution I came up with is suitable for every device.
Click to expand...
Click to collapse
I have an S7 and I need to do exactly what you did - add a brand new provider. Can you share more precise details on how you did it?

prasadmanjulago said:
thanks. i succeeded yesterday...i didnt edit imsservice.apk
i found enforceskippingpackages.xml file in system/csc_contents folder
in the only couple of lines
imsservices.apk
imslogger.apk
imssettings.apk etc
i removed those ims lines.. then volte worked.. i already added enable volte lines on csc/others.xml and customer.xml before.
i didnt edit anything on the attached screenshot i sent on above reply
thanks,,,
Click to expand...
Click to collapse
Hi,
I would like to have your guidance
I have a LG v60 L-51a docomo model where field test option (hidden menu ) is disabled.
I am unable to enable volte in India to use jio.
Searched various options seems no way out. However i was able to locate hidden apps by using 3party launcher app. LG ims. But unable to launch hidden menu to changed ims settings. Help me to by pass this application to enable volte.

I don't know if this will help anyone, or if anyone can help me, but...
SM910v, (verizon wireless) with T-Mobile SIM
6.01 Marshmallow (please read the rest anyway)
4G/LTE Data works.
Voice calls fall back to 2G/Edge, ie no VoLTE.
-------- HOWEVER -------
Changing the sales_code.dat from VZW to TMO enables VoLTE, and it works great.
(it breaks the settings pages, though, so it's not a solution)
When sales_code is VZW, then IMS Settings-->IMS Information:
All are "false", Registration Information is "no profile is registered", although the profile "T-Mobile VoLTE/RCS" is available and status is 'on' in the Manage IMS Profiles page.
I can not find a way to 'register' it.
When sales_code is TMB,
then, in IMS Settings-->IMS Information:
All are "true", Registration Information is "T-Mobile VoLTE/RCS",
And, of course, VoLTE works great.
I mention this in this thread because just having the correct profile present & available may not be enough. At least in my case, it appears that the sales_code (or some other CSC function) flips a flag somewhere that allows the profile to become selected/active. I've been trying to find it for six weeks, with no luck yet. Thanks for reading.