General [NO ROOT]SercrtCode to unlock all country 5G and VoLTE!!!

Search This thread

HSOC

Senior Member
Oct 24, 2007
68
5
Thessaloniki
Hey,

I've made some tests and...

Go to *#*#0702#*#* -> Common settings. There is UPDATE_IMSCONFIG_BY_CARRIERCONFIG value with default value 1. After changing it to 0, it stays same after reboot.

So I copied two xml files to local directory and then changed values of:
  1. CONFIG_XML to local path /storage/emulated/0/imssetting/sim_configuration.xml
  2. UT_XML to local path /storage/emulated/0/imssetting/ut_default_setting.xml
It also stays after reboot.

But... nothing happens. SIM 2 Provisioned and SIM 2 Policy (testing it on my SIM2) settings are diffrent than these in xml files. It's weird that it correctly sets XCAP_APN_NAME to T-Mobile XCAP (my carrier is T-Mobile PL), but a few of settings are diffrent...

Additionaly, Setting VOWIFI_ENABLED_BY_PLATFORM to 1 in sim_configuration.xml doesn't sets it in ImsSetting app. Also, Provisioned and Policy setting always returns to default after reboot. Only Common settings are saved and surviving device reboot.

I think that it can somehow work, but we need find out how :cool:

I confirm your results. What did you change on ut_default_setting.xml ? I couldn't find any related option so I didn't change the path. I think we are really close, we just need to find the correct setting.
 
On mine, using the 4646 code, it shows VoLTE provisioned on (gray)
VoLTE calling provisioned off (gray)
Wifi calling provisioned on (gray)
EAB/presence provisioned on (gray)
So, with the VoLTE calling provisioned off and gray, does that mean VoLTE isn't
supported by my carrier? At&t prepay. It was on my older A71 Samsung, or, at least
it showed that on the screen in the top corner.
I have a Pixel 6 I got direct from Google and use it on TMO. I see the same thing you see when in that dial code. I looked on one of TMO's pages for the product and it says

Turn on / off VoLTE​

Although this device does have VoLTE, it can't be turned on or off in the settings

Here is the link, it's at the bottom of the page, so I would suspect its the same for your provider.

https://www.t-mobile.com/support/de...-6-5g/network-apn-and-volte-google-pixel-6-5g
 
Hey,

I've made some tests and...

Go to *#*#0702#*#* -> Common settings. There is UPDATE_IMSCONFIG_BY_CARRIERCONFIG value with default value 1. After changing it to 0, it stays same after reboot.

So I copied two xml files to local directory and then changed values of:
  1. CONFIG_XML to local path /storage/emulated/0/imssetting/sim_configuration.xml
  2. UT_XML to local path /storage/emulated/0/imssetting/ut_default_setting.xml
It also stays after reboot.

But... nothing happens. SIM 2 Provisioned and SIM 2 Policy (testing it on my SIM2) settings are diffrent than these in xml files. It's weird that it correctly sets XCAP_APN_NAME to T-Mobile XCAP (my carrier is T-Mobile PL), but a few of settings are diffrent...

Additionaly, Setting VOWIFI_ENABLED_BY_PLATFORM to 1 in sim_configuration.xml doesn't sets it in ImsSetting app. Also, Provisioned and Policy setting always returns to default after reboot. Only Common settings are saved and surviving device reboot.

I think that it can somehow work, but we need find out how :cool:
Hope you'll find out how to make it work.
I'm worried because in the future without VoLTE I won't be able to use the phone :(
 

mightyvenom

Senior Member
Jul 7, 2011
100
44
Google Pixel 5
If someone manages to unlock VoLTE/VoWifi via this method it will trully be a game changer. There are a lot of people owning this phone outside of the supported countries that are flooding the Pixel Support forums regarding this issue.

I, for one, am willing to also donate for the person who manages this. Let's hope it can be done, thanks!
 

Cyndaquissshhh

Senior Member
Dec 25, 2021
64
34
This all started as a joke and suddenly everything blew up.

Anyway... sir when VoLTE for Pixel LineageOS sir 🥺
 
My girlfriend is from Germany with a Pixel 5. Google sells it there officially. I am from Austria with a P6P (not sold officially in my country).

We are currently on a trip through Europe and she frequently gets 5G in all kind of countries while I only get 4G. I have a 5G plan and get 5G in my home country.

Also she always gets 4G+ where I only have 4G.

Not sure if this helps. But it seems like you are ****ed world wide if the carrier/plan in your home country doesn't officially support the Pixel.
 
  • Like
Reactions: mightyvenom

tschaad

Member
Feb 4, 2022
15
4
My girlfriend is from Germany with a Pixel 5. Google sells it there officially. I am from Austria with a P6P (not sold officially in my country).

We are currently on a trip through Europe and she frequently gets 5G in all kind of countries while I only get 4G. I have a 5G plan and get 5G in my home country.

Also she always gets 4G+ where I only have 4G.

Not sure if this helps. But it seems like you are ****ed world wide if the carrier/plan in your home country doesn't officially support the Pixel.
jup, I love the phone but I gave up... I just bought a S22 Ultra... sadly but I see no other choises ..
 
  • Like
Reactions: Sigray

mightyvenom

Senior Member
Jul 7, 2011
100
44
Google Pixel 5
So, did anyone tested if the latest builds Android 12 QPR3 Beta 1 or Android 13 DP1 in any unsupported (european) countries have active VoLTE / VoWiFi / 5G support ?

Thanks!
 

LLStarks

Senior Member
Jun 1, 2012
2,068
1,354
With respect to Vo5G, it looks that's controlled by the vonr_enabled_bool flag in the carrier setting pb file.

For T-Mobile, this was present in DP1 but is absent in most other builds, including DP2.

Still not clear whether Google can update these configs between OTAs.
 
Last edited:
  • Like
Reactions: mightyvenom

swimtw

Member
May 20, 2014
11
0
So I tried enabling VoLTE in my country by adding some lines in build.prop file and using the methods written here. Well, the result was disappointing in both ways. When I try to call someone, it somehow ends the call before any beep sounds, basically it just hangs up right after I press the call button. I analyzed the logcat when calling, and here is the result.

ims_logcat.png


Any ideas about this?? I am supposing that it has to do something about the SIP timer settings and other settings that were in the *#*#0702#*#*. Well, I can't get any values from my carrier so bummer

+ Disabling VoLTE works great, no auto hanging up.

Country: South Korea
Carrier: SK Telecom
IMS: Definitely supported, all other phones in Korea support VoLTE + Video calling + 5G support.
 
So I tried enabling VoLTE in my country by adding some lines in build.prop file and using the methods written here. Well, the result was disappointing in both ways. When I try to call someone, it somehow ends the call before any beep sounds, basically it just hangs up right after I press the call button. I analyzed the logcat when calling, and here is the result.

View attachment 5568607

Any ideas about this?? I am supposing that it has to do something about the SIP timer settings and other settings that were in the *#*#0702#*#*. Well, I can't get any values from my carrier so bummer

+ Disabling VoLTE works great, no auto hanging up.

Country: South Korea
Carrier: SK Telecom
IMS: Definitely supported, all other phones in Korea support VoLTE + Video calling + 5G support.

I faced similiar issues when disabling VoLTE and/or disabling 2G.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    What should we do with this file?

    Seeing that this user has only posted 12 messages, I'm guessing this was among their first 10. Last I remember, XDA requires 10 messages to be posted by a user in order to get some kind of further permissions, although I don't remember what, although that was back on the old forum software. These days there are also achievements to get "XP" and "levels", and that might've been one.

    Long story medium, the user likely posted nearly useless information to get their post-count up to 10. As his only useful comment says in the OP "no thanks". :) I'm not even downloading something that I don't know what I'm expecting, much less looking in the zip or doing anything else, and some of the settings accessible via the dialer code are likely dangerous unless you know exactly what you're doing, so without actual instructions detailing what the code has to do with the title of the thread, I wouldn't bother.

    I'm tempted to report the thread. Normally I wouldn't bother as this kind of thread from new users is a dime a dozen but it's pretty blatantly a misleading thread title without more information, and with no description of what the file is supposed to be, and the only words in the OP being "no thanks" just screams "what the bloody hell" to me.

    [/rant] :D

    *#*#0702#*#*

    no thanks
    11
    I found some other stuff. But it's not for the fainth of heart ;-)

    In /product/etc/CarrierSettings directory you have .pb (protobuf) files which contain carrier info (read: https://source.android.com/devices/tech/config/carrierid). For example there are specific files for US networks (e.g. sprint_us.pb), networks in France (e.g. bouygues_fr.pb), networks in UK (e.g. ee_gb.pb). I would say these will be "fully" supported by Google. There are 130 files there.

    Just as an example, here is the config for the bouygues_fr.pb (Bouygues network in France):

    Code:
    canonicalName: "bouygues_fr"
    version: 30000000317
    apns {
      apn {
        name: "Bouygues Telecom"
        value: "mmsbouygtel.com"
        type: DEFAULT
        type: SUPL
        type: MMS
        authtype: 1
        mmsc: "http://mms.bouyguestelecom.fr/mms/wapenc"
        protocol: IPV6
      }
      apn {
        name: "Bouygues Telecom IMS"
        value: "ims"
        type: IMS
        protocol: IPV4V6
        userVisible: false
      }
      apn {
        name: "Bouygues XCAP"
        value: "mmsbouygtel.com"
        type: XCAP
        bearerBitmask: "3|9|10|11|14|15|20"
        authtype: 1
        protocol: IPV6
      }
    }
    configs {
      config {
        key: "carrier_certificate_string_array"
        textArray {
          item: "A0058F6467628EA2031C4C9D8519ABECB2671F6A1752B15A89369CDCB8D2952B"
        }
      }
      config {
        key: "carrier_cross_sim_ims_available_bool"
        boolValue: false
      }
      config {
        key: "carrier_default_wfc_ims_mode_int"
        intValue: 1
      }
      config {
        key: "carrier_supports_ss_over_ut_bool"
        boolValue: true
      }
      config {
        key: "carrier_ussd_method_int"
        intValue: 2
      }
      config {
        key: "carrier_volte_available_bool"
        boolValue: true
      }
      config {
        key: "carrier_wfc_ims_available_bool"
        boolValue: true
      }
      config {
        key: "editable_wfc_mode_bool"
        boolValue: false
      }
      config {
        key: "iwlan.child_sa_rekey_hard_timer_sec_int"
        intValue: 7400
      }
      config {
        key: "iwlan.child_sa_rekey_soft_timer_sec_int"
        intValue: 7300
      }
      config {
        key: "iwlan.diffie_hellman_groups_int_array"
        intArray {
          item: 14
        }
      }
      config {
        key: "iwlan.ike_rekey_hard_timer_in_sec"
        intValue: 14800
      }
      config {
        key: "iwlan.ike_rekey_soft_timer_sec_int"
        intValue: 14700
      }
      config {
        key: "iwlan.key_error_policy_config_string"
        textValue: "[{\"ApnName\": \"*\",\"ErrorTypes\": [{\"ErrorType\": \"IKE_PROTOCOL_ERROR_TYPE\",\"ErrorDetails\": [\"9000\", \"10000\"],\"RetryArray\": [\"0\", \"0\"],\"UnthrottlingEv
    ents\": [\"APM_ENABLE_EVENT\", \"WIFI_DISABLE_EVENT\", \"WIFI_AP_CHANGED_EVENT\", \"WIFI_CALLING_DISABLE_EVENT\"]}, {\"ErrorType\": \"IKE_PROTOCOL_ERROR_TYPE\",\"ErrorDetails\": [\"1050
    0\"],\"RetryArray\": [\"3600\", \"-1\"],\"UnthrottlingEvents\": [\"APM_ENABLE_EVENT\", \"WIFI_DISABLE_EVENT\", \"WIFI_AP_CHANGED_EVENT\", \"WIFI_CALLING_DISABLE_EVENT\"]}, {\"ErrorType\
    ": \"IKE_PROTOCOL_ERROR_TYPE\",\"ErrorDetails\": [\"11002\", \"11003\"],\"RetryArray\": [],\"UnthrottlingEvents\": [\"APM_ENABLE_EVENT\", \"WIFI_DISABLE_EVENT\", \"WIFI_AP_CHANGED_EVENT
    \", \"WIFI_CALLING_DISABLE_EVENT\"]}]}]"
      }
      config {
        key: "maxImageHeight"
        intValue: 1944
      }
      config {
        key: "maxImageWidth"
        intValue: 2592
      }
      config {
        key: "maxMessageSize"
        intValue: 614400
      }
      config {
        key: "show_4g_for_lte_data_icon_bool"
        boolValue: true
      }
      config {
        key: "supportHttpCharsetHeader"
        boolValue: false
      }
    }

    As you can see in the config part, it has an indication that VoLTE is available. And when it is available, it will show the 4G icon in the status bar (instead of the LTE icon). I know that this works, because I tested with my brother's SIM card which is on that exact network.

    There is one file, called '/product/etc/CarrierSettings/others.pb' (on the phone) which has carrier specs for ALL other networks in the world. However, these specs seem to be rather minimal. Not all networks are even there (I am currently on Belgian Youfone which is missing from that file). I checked, for example, for the Proximus network in Belgium and there very little configuration, e.g. no indication of VoLTE (which I know is there).

    Maybe - but I'm not 100% sure - network info can be added via these files.

    I fiddled around with this others.pb file. First, decompile the .pb (protobuf) into text, then modify test, then recompile the text into pb (protobuf) format, then (using a Magisk bind mount) overwrite /etc/product/CarrierSettings/others.pb on the phone.

    And tada, when I refreshed the APN info, my Youfone network and APN spec were there, automatically selected by the phone.

    I'm not 100% sure, but maybe VoLTE/5G can be added as well through these files.

    You need to do some research. First read the article: https://source.android.com/devices/tech/config/carrierid, this explains a bit how the Carrier pb files are

    You will need the protoc tool (see https://github.com/protocolbuffers/protobuf). I downloaded the source and built it from source. It allows you to decompile/recompile the pb files, e.g. on Linux:

    Code:
    Decompile pb file into text:
    
    > protoc -I. --decode=MultiCarrierSettings carriersettings.proto < ~/pixel/raven-sd1a.210817.037/mnt/product/etc/CarrierSettings/others.pb > out.txt

    The carriersettings.proto file can be downloaded from: https://github.com/daradib/carriersettings-extractor

    Then edit the out.txt file, modify/add your network details, remove the last 3 lines of the file (some sort of version indicator I'm guessing), finally recompile into protobuf using:

    Code:
    Recompile text file into protobuf:
    
    > cat out.txt | protoc --encode=MultiCarrierSettings carriersettings.proto > others.pb

    You will need a Magisk module to 'replace' the others.pb file on your phone. Module is attached, download it (the original phone's 'other.pb' file is in there).

    First, unzip it, then copy YOUR modified pb file, then re-zip it.

    Code:
    > cd temp
    > unzip ~/replaceotherspb.zip
    > cp mymodifiedpbfile.pb system/product/etc/CarrierSettings/others.pb
    > zip -r ~/mymagisk.zip .
    > adb push ~/mymagisk.zip /sdcard/

    Then install the module mymagisk.zip using the Magisk app. Go to settings > network > your SIM > access points, tap the 3 dots and 'refresh'. Your modified carrier details should be loaded now.

    Again, I'm absolutely not an expert in this ... so can't really support ... I'm not even sure if this will allow you to activate VoLTE/5G, but worth a try. Good luck.
    10
    *#*#0702#*#*

    no thanks
    8
    If someone manages to unlock VoLTE/VoWifi via this method it will trully be a game changer. There are a lot of people owning this phone outside of the supported countries that are flooding the Pixel Support forums regarding this issue.

    I, for one, am willing to also donate for the person who manages this. Let's hope it can be done, thanks!
    6
    Hey,

    I've made some tests and...

    Go to *#*#0702#*#* -> Common settings. There is UPDATE_IMSCONFIG_BY_CARRIERCONFIG value with default value 1. After changing it to 0, it stays same after reboot.

    So I copied two xml files to local directory and then changed values of:
    1. CONFIG_XML to local path /storage/emulated/0/imssetting/sim_configuration.xml
    2. UT_XML to local path /storage/emulated/0/imssetting/ut_default_setting.xml
    It also stays after reboot.

    But... nothing happens. SIM 2 Provisioned and SIM 2 Policy (testing it on my SIM2) settings are diffrent than these in xml files. It's weird that it correctly sets XCAP_APN_NAME to T-Mobile XCAP (my carrier is T-Mobile PL), but a few of settings are diffrent...

    Additionaly, Setting VOWIFI_ENABLED_BY_PLATFORM to 1 in sim_configuration.xml doesn't sets it in ImsSetting app. Also, Provisioned and Policy setting always returns to default after reboot. Only Common settings are saved and surviving device reboot.

    I think that it can somehow work, but we need find out how :cool: