[GUIDE] [NO ROOT REQUIRED] [EPIC UPDATE] How to add VoLTE support for other carriers to the G8 (and other Qualcomm powered LG devices too!)

Search This thread

surgemanx

Senior Member
Jan 29, 2022
172
31
Try this:
1. Create a new folder in your internal storage named "enable_ue"
2. Dial #546368#*820
3. Go into field test==>universal enabler
4. Click "Create New Config"
5. Then enable all 4 boxes and see if VoLTE will work

If this doesn't work then flashing Open US G820QM firmware is the only solution for you to get T-Mobile VoLTE support.

Saw your reddit post, for the Mint APN leave the MNC as 240, Mint sim cards are MCC 310 MNC 240, not 310 260 like actual T-Mobile sim cards. This is why it disappears when you try to save it with the MNC as 260.
The 820QM firmware will solve his issues with nothing else being done except fixing the NT Code error.I have done this already myself,and all works except wifi calling of course.
 

surgemanx

Senior Member
Jan 29, 2022
172
31
He's trying to get T-Mobile to work, so he will probably have wifi calling on the QM firmware
Yes,I have a T-Mobile sim in my G850(Sprint),and it's crossflashed to the QM firmware.All works on my end but the WIFI calling.It's a hit and miss I guess with certain models maybe?I knew it did work with the Sprint firmware,but stuck at A10 because that was the last update that was pushed to those models.
 

tlogan23

New member
Jan 24, 2008
4
0
BLU R1 HD
Actually I spoke too soon. I tested my phone while I was still home. I could call and receive and with my WiFi turned off, I had 4Glte icon and I could surf. Yesterday, I was out and about. My phone behaved the same way after cut off by ATT network. CC was able to get my phone back by resetting my network, but no data service. Providing an APN with CC settings got my data service back. But I can't have both. Either one or the other.
I just tried once again try to load GSM for ATT, ATT_Open, and Tmobile_Open. But still have the same results. Even using the enable_er, checking all 4, did not change the behavior.
I think I might have to try cross/flashing to see if this beast can be tamed, without me having to buy a new phone.
Thanks for the input! -tim
 

7roots

New member
May 26, 2022
2
0
LG G8
LG V50 ThinQ
Hi Bro, v50 skt how to make it work in mode pdc.

lm-v500.jpg
 
Last edited by a moderator:

surgemanx

Senior Member
Jan 29, 2022
172
31
it doesn't work for korea lg v50n, and after root, crossflash. There is an opinion that the adb method is needed
i tried this adb shell setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
does not work :(
Okay,try these drivers.These are for v500n,and should work.
 

Attachments

  • LG_Mobile_Driver_v3.6.0.0.zip
    8.8 MB · Views: 8

Sykander

Member
Dec 5, 2020
13
0
I've already mentioned the names of the mbn files that i can see on my G8S, unfortunately i can't see them when i extract files from modem_a using 7z.
I'm hoping you can share the LG default mbn file so that i can try it on the G8.

Regarding how i got VoLTE to work on my G8 phones, it was a long story of trial and error, but what finally works is replacing these files in /product/OP/config with files from the Indian G8S - apns.xml, carrier_code.xml, telephony.xml and vo_config.xml. In the last file, don't change the name of the operator or country,
@mangojain Mate I'd really like to know how you managed to get hold of those files from the indian G8S..

I have a LGv50 (LGU+) flashed with open EU rom. I was really excited when I discovered this thread a week ago and wanted to see if I can get VoLTE to work on Indian carriers.

So far I've not been able to find any KDZ which have the mbn files for Indian carriers - for some strange reason they all contain only Korean and NA ones.

So I would really like to know if anyone has managed to find mbn files for Indian carriers or if there is another workaround.
 

mangojain

Senior Member
Jul 24, 2010
211
20
@mangojain Mate I'd really like to know how you managed to get hold of those files from the indian G8S..

I have a LGv50 (LGU+) flashed with open EU rom. I was really excited when I discovered this thread a week ago and wanted to see if I can get VoLTE to work on Indian carriers.

So far I've not been able to find any KDZ which have the mbn files for Indian carriers - for some strange reason they all contain only Korean and NA ones.

So I would really like to know if anyone has managed to find mbn files for Indian carriers or if there is another workaround.
The Indian G8S doesn't contain any India-specific MBNs either, like you said, they are the Korean or NA versions only.
To get VoLTE to work on the G8 in india you need root to edit some of the files in the OP and OP/config folders, loading MBNs will not help. I have VoLTE & VoWiFi working perfectly on Jio and Airtel and VoLTE on Vodafone.
 

Sykander

Member
Dec 5, 2020
13
0
The Indian G8S doesn't contain any India-specific MBNs either, like you said, they are the Korean or NA versions only.
To get VoLTE to work on the G8 in india you need root to edit some of the files in the OP and OP/config folders, loading MBNs will not help. I have VoLTE & VoWiFi working perfectly on Jio and Airtel and VoLTE on Vodafone.
Thank you for responding!

Please help me with the four files mentioned in your post - apns.xml, carrier_code.xml, telephony.xml and vo_config.xml. I hope these work for my v50 too.

I've never rooted my phone before. But since you've said that you have managed to get it working on airtel & vodafone i'm quite happy to give it a shot!
 

Sykander

Member
Dec 5, 2020
13
0
The Indian G8S doesn't contain any India-specific MBNs either, like you said, they are the Korean or NA versions only.
To get VoLTE to work on the G8 in india you need root to edit some of the files in the OP and OP/config folders, loading MBNs will not help. I have VoLTE & VoWiFi working perfectly on Jio and Airtel and VoLTE on Vodafone.

Sorry, also wanted to know how you managed to get the files onto your phone after root. Did you use something like solid explorer?
 

hypafly

Senior Member
Aug 18, 2013
160
50
Fisrt of all, amazing tutorial and effort on do it, but I have a problem.

I have an Unlocked T-mobile V60, I tried to do the tutorial but when I connect the phone on the QMICM mode, it doesn't even show in the device manager nor make the Windows sound for a new connected device. When i return it to Android mode it pops right up as a "v60" and Windows makes the sound of connected device but on QMICM mode its just like it's not even connected.

Drivers are installed correctly but again, when I connect the phone it just doesn't shows up as nothing at all.

Any ideas?
I noticed this when I upgraded to android 12 EA firmware. The QMICM mode doesn't show up in device manager or show any sign. But I downgraded to TM android 11 Firmware and it works. I don't know if this is a bug or they've patched it on Android 12. If anyone on Android 12 got it to work please let us know.
 

Wish39

Senior Member
Jan 13, 2015
196
48
I noticed this when I upgraded to android 12 EA firmware. The QMICM mode doesn't show up in device manager or show any sign. But I downgraded to TM android 11 Firmware and it works. I don't know if this is a bug or they've patched it on Android 12. If anyone on Android 12 got it to work please let us know.
LG either unintentionally or intentionally broke the QMICM mode in Android 12, need to update the guide to include that info. Same behavior on my AT&T Velvet with Android 12.
 
  • Like
Reactions: hypafly

Sykander

Member
Dec 5, 2020
13
0
Hey, any chance you could help me out with these four files from the Indian
The Indian G8S doesn't contain any India-specific MBNs either, like you said, they are the Korean or NA versions only.
To get VoLTE to work on the G8 in india you need root to edit some of the files in the OP and OP/config folders, loading MBNs will not help. I have VoLTE & VoWiFi working perfectly on Jio and Airtel and VoLTE on Vodafone.

G8X?
 

mangojain

Senior Member
Jul 24, 2010
211
20
Hey, any chance you could help me out with these four files from the Indian


G8X?
In product/OP/cust.prop change the values for these entries -

ro.vendor.lge.build.target_region=ESA
ro.vendor.lge.build.target_operator=OPEN
ro.vendor.lge.build.target_country=ESA
persist.product.lge.ims.volte_open=1

In the product/OP/config folder, replace the attached files
 

Attachments

  • config.zip
    220.5 KB · Views: 4

Sykander

Member
Dec 5, 2020
13
0
Thank you very much for your reply and the files! Really appreciate it mate.. Will give this a shot and give an update.
 

Sykander

Member
Dec 5, 2020
13
0
In product/OP/cust.prop change the values for these entries -

ro.vendor.lge.build.target_region=ESA
ro.vendor.lge.build.target_operator=OPEN
ro.vendor.lge.build.target_country=ESA
persist.product.lge.ims.volte_open=1

In the product/OP/config folder, replace the attached files
Thank you again for the files. I really appreciate it.

I tried replacing these in OP/Config. Unfortunately I still don't have VoLTE or VoWifi. I can see that the profiles for Indian carriers are added in Master Config from Universal Enabler. However the VoLTE doesn't work. I even tried removing SIM and putting it back in.

I hope there are no more steps after replacing the files.
 

Wish39

Senior Member
Jan 13, 2015
196
48
Thank you again for the files. I really appreciate it.

I tried replacing these in OP/Config. Unfortunately I still don't have VoLTE or VoWifi. I can see that the profiles for Indian carriers are added in Master Config from Universal Enabler. However the VoLTE doesn't work. I even tried removing SIM and putting it back in.

I hope there are no more steps after replacing the files.
Did you change the values in the cust.prop file as instructed?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Ok, so I went through all your processes with the same phone as you and used your files for my ATT G8 and it did not work. Like someone else said, it now shows that my TMO is active and says I'm connected, instead of disconnected... but it did nothing to change the fact that I cannot provision my Volte to turn on, I'm guessing due to something in ATT's software. Looks like unless I'm going to try and cross-flash, that there is no actual way to do this easy.

    Wasted a good part of a day on this... so if you have anything else I can try, I'll probably do it.
    Try this:
    1. Create a new folder in your internal storage named "enable_ue"
    2. Dial #546368#*820
    3. Go into field test==>universal enabler
    4. Click "Create New Config"
    5. Then enable all 4 boxes and see if VoLTE will work

    If this doesn't work then flashing Open US G820QM firmware is the only solution for you to get T-Mobile VoLTE support.

    Saw your reddit post, for the Mint APN leave the MNC as 240, Mint sim cards are MCC 310 MNC 240, not 310 260 like actual T-Mobile sim cards. This is why it disappears when you try to save it with the MNC as 260.
    1
    I noticed this when I upgraded to android 12 EA firmware. The QMICM mode doesn't show up in device manager or show any sign. But I downgraded to TM android 11 Firmware and it works. I don't know if this is a bug or they've patched it on Android 12. If anyone on Android 12 got it to work please let us know.
    LG either unintentionally or intentionally broke the QMICM mode in Android 12, need to update the guide to include that info. Same behavior on my AT&T Velvet with Android 12.
  • 9
    This guide will not work if you are running Android 12 :(

    I'm gonna keep the intro simple, been a longtime user here on XDA, and recently I found that my T-Mobile LG G8 only supported VoLTE and VoWifi on, you guessed it, T-Mobile! So I did some research, experimented with my G8 for a bit, and I now have a method that works and does not need root at all. Basically, what we are doing here is just loading carrier profiles into the phone's modem so that the phone is able to complete IMS registration and correctly provision VoLTE when you insert a SIM card from another carrier.

    If you are trying this on a LG V60, please turn off USB debugging before attempting this as multiple V60 owners have had trouble properly installing the modem driver and only resolved the driver issue by turning it off. Also, please try the 90E5 driver if the 9091 driver does not work for you.

    This method does not work on the Sprint G8, any other Sprint LG devices, the Korean G8 and any other Korean LG devices since there is no Field Test option in the HiddenMenu in those devices.


    Follow this post here, and make sure you read the original post in that thread as well. Also should work with other BL unlocked G8 models. Crossflash your G8 to Open US or Open CA firmware using this method! No unlocked bootloader or root needed!

    DO THIS FIRST!!!!!: STEPS TO OBTAIN CARRIER MBN FILES FOR YOUR DEVICE (MBN files for the G8/G8x/G8s provided in Step 11 of the main guide)

    1. Download a KDZ for your device. Sites like lgrom.com or lg-firmwares.com have KDZ's available to download. If you have an AT&T LG device just download a KDZ for another variant of your phone. Ex: If you have the AT&T LG Velvet, just download the Canadian Velvet's KDZ. Same for the AT&T G8, G8x etc.

    2. Download and install
    7zip, and the linked/attached KDZ extractor tool.

    3. Extract the KDZ tool zip file, then place your downloaded KDZ into the same folder as the KDZ tools.
    1646120728815.png

    4. In the KDZ tools folder, find "OneKeyExtraction.bat" and double click on it.

    5. When the CMD windows launches, press Y to start extracting the partitions from the KDZ.

    6. Once it is finished, you should see a new folder in the KDZ tools folder that has the same name as the KDZ that you downloaded. Open up that folder.
    1646121613132.png

    7. As you can see the tool extracted all of the partitions that are contained in the KDZ file. We will need to open up either the modem_a or modem_b partitions to grab the needed MBN files. Scroll down to find those partitions. Doesn't matter which one you choose.

    8. Right click on whichever one you chose, hover over "7zip", then click "Open archive".
    1646122181314.png

    9. 7zip will open up. The folders where the MBN's will be vary by device. Generally you should first look for a folder named "modem_pr", then once in it find the "mcfg_sw" folder. Here are some examples to help you find where the MBN files in your device's modem partition are. The files will be seperated into folders by region and carrier.
    1646122816648.png

    1646122875662.png

    1646122958551.png

    10. Once you find the files, extract them to whichever folder you want to.



    Now here are the steps to load the MBN's:

    1. Download the latest QPST Tools from here. Only runs on Windows. No Linux, sorry.

    2. Extract the zip file you downloaded and open QPST.2.7.496.1.exe to install the QPST tools.

    1633495073816.png

    3. Once that is done, go to the Driver folder and open Qualcomm USB Driver V1.0.exe to install the drivers needed for the tool to communicate with your phone.

    4. After that is done, there should be a QPST folder in your start menu. We'll come back to that later.

    5. On your phone, go to the dialer and enter this code:
    Code:
    *#546368#*xxx# OR #*462633*#xxx# *xxx is the three numbers in your device's model code.

    6. The HiddenMenu should pop up, choose Field Test, then LTE Data Test, and change the Tethering Mode from Android to QMICM. I recommend leaving your phone in this menu so that it is easier to switch back to the normal Android USB connection mode when you are done.

    1633495857477.png
    1633495872107.png
    1633495890722.png

    7. Connect your phone to your computer, it should be detected as "Qualcomm HS-USB Modem 9091". In Device Manager it should show up under the Modems section.

    8. Go to the QPST start menu folder and open the "PDC" application.

    9. Go to the Device dropdown, there should be an item named "Qualcomm Wireless HS-USB Ethernet Adapter 9091". This is your phone, select it.
    1633496853860.png
    10. This is what you should see. Notice how only the original carrier's (T-Mobile) modem profile is loaded into the phone's modem. Pretty lazy if you ask me.
    1633497146862.png
    11. Now you will need some modem profiles to load into your phone! As a little starter pack, here are a few carrier modem profiles for US, Canadian and Korean carriers. Download them here (these are only for the G8/G8x/G8s! Will not work with other devices!!!!!!). I have extracted these from my phone's modem_a partition using QFIL Partition Manager with the LG SD855 firehose, and these are present in the modem_b partition as well. LG left all of these profiles inside the phone but only actually loads one of them into the modem on carrier models....

    These profiles may also work on the G8x, V50, and G8s since those phones have the same SOC as the G8, and by extension the same modem chip.

    12. Once you are ready, press the Load button and navigate to whichever carrier profile you want to add, I will load AT&T as an example. After going inside the folder for the carrier you want to load, there should be a file named "mcfg_sw.mbn". This is the profile. Don't bother adding any profile that has "row" in it's name, those usually don't give you support for VoLTE.
    1633498811451.png
    13. When you are ready, click Open and your carrier profile will be loaded into your phone! You can go and add as many carriers as you want, I loaded all US and Korean, and some Canadian carrier profiles into my G8.

    Do not load the same profile multiple times, this may cause issues with VoLTE and cell connectivity.
    1633501377502.png

    14. When you are done, go back to the LTE Data Test menu and set the tethering mode back to Android. Your phone now has VoLTE support for the carriers that you loaded into it!

    If you have another Qualcomm LG device, you can also follow this guide, you just need to enter the HiddenMenu dialer code specific to your device, and have carrier config files that are either specifically for your device, or from another phone that has the same chipset as your device* (*may or may not work).

    Here's AT&T VoLTE working with a Tracfone AT&T sim card on my previously incompatible T-Mobile G8:
    1633502003068.png
    1633502017259.png

    Hope this guide has helped you guys!
    1
    If it's anything like the Sprint V50, see if 5689#*820# works. But I suspect that even if it works, there won't be a Field Test option.
    Yeah, same result.

    If I use *#*#7262626#*#*, upon pressing the last * the code disappears and I'm still on the dialer.

    1
    Its weird, as far as I can tell... my device has VoLTE enabled on Tmobile, eventhough its DEFINITELY a Sprint model. Aside from that, I use Google Voice, which essentially lets me make calls and use data at the same time anyway.
    1
    On my Sprint G8X on 20p, simply replacing abl_a and abl_b with the special one used for BL unlocking made my phone think it's a T-Mobile one and enabled Field Test in the HiddenMenu. It's not necessary to do the BL unlock itself if you don't need it. Just thought I'd mention it in case anyone wants to try this on a Sprint phone.
    1
    That's too bad, but makes sense since the abl came from an 850.
    I wonder if you can use abl files from a different branded or unbranded V50? I'd think if you're not planning to BL unlock, you wouldn't need it to be an engineering abl.
    Looks like it's unfortunately still a no-go for the Sprint V50.

    Even after putting in the engineering abl file to make it look like an LM-G850, the 546368 dialer code still doesn't work (tried 850, 450, 820, 500 for model numbers) while the Sprint alternative code 5689#*850# still gives the same options as out-of-the-box with no Field Test.

    So I guess unlocking the bootloader and root access (to replace op partition files after which the 546368 code will work) are still needed for this particular model.

    Just to clarify, it's whats in the OP partition that will (or won't) allow those dial codes to work. And yes, the engineering abl, being from a specific model / variant of android, will almost always mean the device won't boot when it's flashed to the abl partition.

    So, if yours booted with it, and it seemed to somehow allow additional dial codes to work, then your OP partition somehow got the message it was a different variant device, and made them available. That's unusual, quite rare. Trying to repeat that with various other abl partitions from other devices / android versions is almost guaranteed to be a futile endeavor.

    The best way to do this, as mentioned, is to use the US open OP partition, and make sure the totc file is set to your specific variant (of course). Then the phone will act / be much like the US Open variant does, have volte and vowifi, less bloat, etc.

    But to get to that point, yes, bl unlocked and root / twrp needed.

    cheers