[GUIDE][WIFICalling][VoLTE][T-Mobile.pl] Getting VoWiFi/VoLTE working in Poland

solk2

Senior Member
Jun 1, 2013
500
611
0
/* Disclaimer */
Do this on your own risk. I am not responsible for broken phones, lost imei, corrupted EFS partition, whatever.

!!!!BACKUP YOUR EFS PARTITION FIRST!!!!

/* Prerequisites */
- Oneplus 3/3T (in theory this can work for any other QC phone supporting VoLTE/VoWIFI)
- T-Mobile.pl SIM card with activated VoLTE/VoWiFi. You need send free SMS for this. Details here in regulamins.
- QPST with EFS file manager and diag drivers. Google for it.
- Root or at least rooted recovery.
- Attached ZIP file.

/* Preparation */
You need switch to diag mode first. To do this you need to set sys.usb.config property to diag,qdss,rmnet_qti_bam,adb . If you don't have root but you have rooted recovery you can do this by placing persist.sys.usb.config to /data/property with 600 permission and root:root owner with this contents: diag,qdss,rmnet_qti_bam,adb, but double check this file it should not contain any EOL chars, better to create it with some HEX editor.

/* Actual hacking */
After you are in diag mode and have drivers installed you can proceed with instructions located in README file inside attached zip file.
 

Attachments

Last edited:

solk2

Senior Member
Jun 1, 2013
500
611
0
It should work on any ROM where volte and vowifi works. At least on my LAOS it works. But it may require properties override (persist.dbg.volte_avail_ovr, persist.dbg.wfc_avail_ovr). But not sure about that as I have my own LAOS builds with carrier_config_26002.xml and I am too lazy to make new builds just to test it.
And this settings may be overridden by mcfg_sw update process which can happen while you updating ROM for example.
 
  • Like
Reactions: MrWilsonxD

meiser

Senior Member
Nov 6, 2010
356
121
63
H,

this sounds very interesting. I'd like to try it for T-Mobile Germany, but I have some questions to understand it properly.

1. What ROM do you use exactly? You mention LAOS, but is it LAOS 13.0 or 14.1?
2. What exactly did you change in your self-built ROM?
3. I guess that I have to use the "Telekom.de DE" branded ROM to extract the system files (https://xpericheck.com/device/F8331). Is that right?
4. Currently, I'm running self-built LAOS 13.0 nightly which should have VoLTE integrated. Should the settings options for VoLTE already be shown? Or only after the modification?
5. Could you maybe point to a download location for QPST and the diag drivers? Or which version did you use?

Many thanks in advance,
meiser
 

solk2

Senior Member
Jun 1, 2013
500
611
0
H,

this sounds very interesting. I'd like to try it for T-Mobile Germany, but I have some questions to understand it properly.

1. What ROM do you use exactly? You mention LAOS, but is it LAOS 13.0 or 14.1?
2. What exactly did you change in your self-built ROM?
3. I guess that I have to use the "Telekom.de DE" branded ROM to extract the system files (https://xpericheck.com/device/F8331). Is that right?
4. Currently, I'm running self-built LAOS 13.0 nightly which should have VoLTE integrated. Should the settings options for VoLTE already be shown? Or only after the modification?
5. Could you maybe point to a download location for QPST and the diag drivers? Or which version did you use?

Many thanks in advance,
meiser
1. and 2. I am using LAOS 14.1 with some my own modifications. But they aren't related to volte, vowifi or ril. Maybe only carrier_config_26002.XML in CarrierConfig but this can be achieved by system props. This method should work on any ROM. This is modem config so ROM should not matter.
3. Model is correct and I don't think that branding matters much. Looks like they are shipping all modem configs in all variants.
4. Settings will be show after you will add properties despite if modification was done right or not.
Or (but this is not tested) they will appear if modem config is correct and right apns added.
5. QPST is proprietary QC software so links to it here is forbidden. I was using 2.7.429.
 

meiser

Senior Member
Nov 6, 2010
356
121
63
3. Model is correct and I don't think that branding matters much. Looks like they are shipping all modem configs in all variants.
Does this mean that I can already use your zip file as it also includes the modem config for T-Mobile Germany?
 

solk2

Senior Member
Jun 1, 2013
500
611
0
Does this mean that I can already use your zip file as it also includes the modem config for T-Mobile Germany?
No. I've meant that you can find all configs in Sony ROM image for all regions despite which branding. But this config is made out of amss_fsg_kagura_telekom_poland_volte_vowifi.tar.mbn and you need something like amss_fsg_kagura_telekom_germany_volte_vowifi.tar.mbn
 

meiser

Senior Member
Nov 6, 2010
356
121
63
OK, so I downloaded the FW with XperiFirm, extracted it with FlashTool and mounted the system.ext4 to get the modem config "amss_fsg_kagura_telekom_germany_volte_vowifi_tar.mbn". I stripped the 552 bytes header and extraced the tar file.

But now I'm hanging at the next step. The nvpreload folder includes 3 files, but these are no tar files, just compressed data.

Code:
[email protected]:/tmp/modem$ ll nvpreload/
insgesamt 72
-rw-r--r-- 1 meiser meiser   353 Jan  1  1970 band_mapping_override.txt
-rw-r--r-- 1 meiser meiser 50650 Jan  1  1970 nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41.bin.gz
-rw-r--r-- 1 meiser meiser   115 Jan  1  1970 nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41_cal_true.bin.gz
-rw-r--r-- 1 meiser meiser  9163 Jan  1  1970 nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41_ets.bin.gz
Could you describe the next steps a bit more in detail? Right now, if I just uncompress the largest file, place the nvitems_list.csv in the root folder of the extracted modem config and run the jar file, I get the following error:

Code:
[email protected]:/tmp/modem$ java -jar cnvparse.jar 
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0
	at ua.org.solk.qc.CNVParse.main(CNVParse.java:37)
At the end, VoLTE and VoWifi should work for both SIM slots as both have a T-Mobile SIM card (private and business). Does this work like this?

Thanks for your help,
meiser
 
Last edited:

solk2

Senior Member
Jun 1, 2013
500
611
0
OK, so I downloaded the FW with XperiFirm, extracted it with FlashTool and mounted the system.ext4 to get the modem config "amss_fsg_kagura_telekom_germany_volte_vowifi_tar.mbn". I stripped the 552 bytes header and extraced the tar file.

But now I'm hanging at the next step. The nvpreload folder includes 3 files, but these are no tar files, just compressed data.

Code:
[email protected]:/tmp/modem$ ll nvpreload/
insgesamt 72
-rw-r--r-- 1 meiser meiser   353 Jan  1  1970 band_mapping_override.txt
-rw-r--r-- 1 meiser meiser 50650 Jan  1  1970 nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41.bin.gz
-rw-r--r-- 1 meiser meiser   115 Jan  1  1970 nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41_cal_true.bin.gz
-rw-r--r-- 1 meiser meiser  9163 Jan  1  1970 nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41_ets.bin.gz
Could you describe the next steps a bit more in detail? Right now, if I just uncompress the largest file, place the nvitems_list.csv in the root folder of the extracted modem config and run the jar file, I get the following error:

Code:
[email protected]:/tmp/modem$ java -jar cnvparse.jar 
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0
	at ua.org.solk.qc.CNVParse.main(CNVParse.java:37)
At the end, VoLTE and VoWifi should work for both SIM slots as both have a T-Mobile SIM card (private and business). Does this work like this?

Thanks for your help,
meiser
Oops. My mistake. Not tar. You just need to run gzip -d nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41.bin.gz to uncompress it. And then you need to run java -jar cnvparse.jar /tmp/modem/nvpreload/nv_L1234578_12_13_17_19_20_26_28_29_32_38_39_40_41.bin .
nvitems_list.csv should be in same folder where cnvparse.jar and to that folder everything will be unpacked.

You will need to apply this config for both subscriptions to get both SIM cards working. So you will need to copy file to EFS twice. For first SIM copy them like it is. For second SIM you need to rename all files by appending _Subscription01.
 
Last edited:

meiser

Senior Member
Nov 6, 2010
356
121
63
OK, we're getting closer. :) What am I supposed to do with the out.xml file?

So I deleted all folders which are also not in your zip file. The folder structure is now as follows:

Code:
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 data
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 Data_Profiles
drwxr-xr-x 3 meiser meiser    4096 Jan  1  1970 ds
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 efsprofiles
drwxr-xr-x 3 meiser meiser    4096 Jan  1  1970 nv
-rw-rw-r-- 1 meiser meiser 1211544 Apr 27 21:53 out.xml
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 policyman
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 sd
Do I have to rename really all files to name_Subscription01 or only the files in the nv folder?
 

solk2

Senior Member
Jun 1, 2013
500
611
0
OK, we're getting closer. :) What am I supposed to do with the out.xml file?

So I deleted all folders which are also not in your zip file. The folder structure is now as follows:

Code:
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 data
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 Data_Profiles
drwxr-xr-x 3 meiser meiser    4096 Jan  1  1970 ds
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 efsprofiles
drwxr-xr-x 3 meiser meiser    4096 Jan  1  1970 nv
-rw-rw-r-- 1 meiser meiser 1211544 Apr 27 21:53 out.xml
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 policyman
drwxr-xr-x 2 meiser meiser    4096 Jan  1  1970 sd
Do I have to rename really all files to name_Subscription01 or only the files in the nv folder?
Yes, looks good.
Probably not all. I think there no need to rename gps related files, they somewhere in nv folder. Maybe some other. But in any case it won't make worse. If they aren't used they will be just ignored. So just to be on a safe side rename all and copy them.

out.xml is NVItems file suitable for qxdm. It mostly contains bands settings and things like that. And we don't need to change that, so just ignore it.

EDIT: And delete nv/item_files/rfnv as that also bands related changes.
And you need to hexedit nv/item_files/ims/qp_ims_ut_config and add "internet.telekom" starting from second byte: So the beginning of file will look like this:
Code:
00000000: 0869 6e74 6572 6e65 742e 7465 6c65 6b6f  .internet.teleko
00000010: 6d00 0000 0000 0000 0000 0000 0000 0000  m...............
 
Last edited:

solk2

Senior Member
Jun 1, 2013
500
611
0
Sony devices are not support Vodafone TR VoLTE? Can I take from Samsung Galaxy S7 firmware? Can anyone help me? :))
Nope. But if it's just VoLTE without VoWiFi you can try to copy /nv/item_files/ims files, /efsprofiles/imshandover and /Data_Profies/Profile8 from attached zip in first post. And then just add this APN:
Code:
 <apn carrier="IMS"
      mcc="286"
      mnc="02"
      apn="ims"
      type="ims"
      protocol="IPV4V6"
      roaming_protocol="IPV4V6"
  />
It may work.
 

meiser

Senior Member
Nov 6, 2010
356
121
63
I just finished copying all the approx. 1700 files to the EFS from my created package.

I couldn't copy some files because of file length or file size.

After a reboot, I can't attach to the LTE network and I also don't see new VoLTE settings.

Any ideas?
 
Last edited:

solk2

Senior Member
Jun 1, 2013
500
611
0
I just finished copying all the approx. 1700 files to the EFS from my created package, see attachment.

I couldn't copy some files because of file length or file size.

After a reboot, I can't attach to the LTE network and I also don't see new VoLTE settings.

Any ideas?
Looks like you've missed this part:
EDIT: And delete nv/item_files/rfnv as that also bands related changes.
And you need to hexedit nv/item_files/ims/qp_ims_ut_config and add "internet.telekom" starting from second byte: So the beginning of file will look like this:
Code:
00000000: 0869 6e74 6572 6e65 742e 7465 6c65 6b6f  .internet.teleko
00000010: 6d00 0000 0000 0000 0000 0000 0000 0000  m...............
RFNV files are related to bands. So restore EFS from backup and try again.
And yes, I forgot about some uim files. That ones are secured so you can't replace them and EFS manager just crashes. But they are not needed for VoLTE, that is related to sim card. So just skip them.

EDIT: And you need APNs for VoLTE to appear. Most important is apn="ims" type="ims".

EDIT2: And it looks like /nv/item_files/modem/data/3gpp/lteps/disable_apn_matching is missing in your config and it's quite important as it disables override of Data_Profiles by userspace APNs.
 
Last edited:

ByKatre

Member
Jul 15, 2015
28
14
0
İstanbul
Nope. But if it's just VoLTE without VoWiFi you can try to copy /nv/item_files/ims files, /efsprofiles/imshandover and /Data_Profies/Profile8 from attached zip in first post. And then just add this APN:
Code:
 <apn carrier="IMS"
      mcc="286"
      mnc="02"
      apn="ims"
      type="ims"
      protocol="IPV4V6"
      roaming_protocol="IPV4V6"
  />
It may work.
It hasn't worked bro. :(