Database Develop

How To Guide Enable VOLTE/VOWIFI in settings

Hey everybody,
the commands to make the volte/vowifi option in settings show permanently across reboots on asus phones has changed from previous years on the zenfone 8.
The setprop commands linked in this guide will no longer work on the zf8.
To temporarily enable the toggles in setting type the following sequence into your current default dialer:
*#*#3642623344#*#*
Afterwards you should be able to check for volte/vowifi functionality. However these settings will not persist across a reboot.
On the Zenfone 8 the following commands can be used after obtaining su elevation in an adb shell or in terminal on the phone to make the options permanently visible across reboots:
Code:
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.dbg.wfc_avail_ovr 1
after setting the props do a full reboot. You should be able to see the settings now.
Please note that this will enable only the option in settings in case it is hidden. It will not make volte/vowifi work, if the phone does not support it.
Asus can´t enable the option if the carrier doesn´t verifiy/grant asus permission to do so. Testing this is a very tedious process.
If volte/vowifi is not working for you after toggling it on in settings, this means there´s no config file for your carrier yet.
In my case volte was already supported by default. I could enable vowifi with the third prop, because asus already has the correct config in the modem. Lucky for me it works and it was only a matter of making the option visible.
It might be enabled by default in the future if the carrier agrees.
Happy Testing everybody.

mine too

How did you get root to apply these commands?

Puksom said:
How did you get root to apply these commands?
Click to expand...
Click to collapse
Unlocking the bootloader and rooting the phone via magisk.

Hey @Freak07
I'm struggling on my ROG 5 trying to enable the DIAG mode as I do not have VoLTE and 5G.
I have my carriers MBN file, and there is no way to PDC or DIAG to use the EFS Tools on this phone. I guess Android 11 has blocked this function, yet I saw a successful attempt here on Zenfone 7
The following codes have no effect on the device, tried them using an elevated command prompt and with SU
Code:
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
I do not see any prompts for new hardware devices.
Then I tried using the New ASUS VoLTE app.
This enables PDC mode, I have the drivers installed (Correctly detected) however my device manager keeps refreshing every 2 seconds and EFSTools only throws the below error.
{
"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"
}
Same cables, Same commands works perfectly on my ROG II, and I have access to PDC as well as EFS tools without any issue - assuming its because its still on Android 10.
Any clue, Ideas on how to get DIAG enabled on the ROG 5 (Android 11) ?

@JazonX ... Are mbn file device specific or are they like files containing info like this is the so and so server to connect to with so and so creds like a openvpn config file ?
Just asking to know if a mbn file from one phone be used with some other phone model.

gammerboy said:
@JazonX ... Are mbn file device specific or are they like files containing info like this is the so and so server to connect to with so and so creds like a openvpn config file ?
Just asking to know if a mbn file from one phone be used with some other phone model.
Click to expand...
Click to collapse
Yes, Correct - MBN files are carrier configuration specific.
I believe only Qualcomm devices use this method, and these files are intercompatible.
I'm using the Xiaomi MBN in my Asus ROG. It worked well in ROG II, but got trouble pushing it to the phone on ROG 5 due to Android 11 restrictions.

JazonX said:
Yes, Correct - MBN files are carrier configuration specific.
I believe only Qualcomm devices use this method, and these files are intercompatible.
I'm using the Xiaomi MBN in my Asus ROG. It worked well in ROG II, but got trouble pushing it to the phone on ROG 5 due to Android 11 restrictions.
Click to expand...
Click to collapse
Have a look at this. This seems to work for oneplus devices.
1.adb reboot ftm 2.adb shell 3.setprop sys.usb.config diag, diag_mdm, qdss, qdss_mdm, serial_cdev, dpl, rmnet, adb 4.register the new profile in QPST PDC 5.adb reboot
Source:
But I think the factory test mode (ftm) might not be available on devices from other vendors.
As for something else have a look at
Maybe might work.
(or)
at https://forum.xda-developers.com/t/activate-volte-om-pixel-4xl-android-11-r.4163217/ -- but this seems to work only if the device is kept in permissive mode which is not a good thing afaik.
Edit: Just looked at the other thread (https://forum.xda-developers.com/t/mod-ish-asusvolte-w-root-fix.4322877/) guess most of the above is just repeat info to what you already know.

gammerboy said:
Have a look at this. This seems to work for oneplus devices.
1.adb reboot ftm 2.adb shell 3.setprop sys.usb.config diag, diag_mdm, qdss, qdss_mdm, serial_cdev, dpl, rmnet, adb 4.register the new profile in QPST PDC 5.adb reboot
Source:
But I think the factory test mode (ftm) might not be available on devices from other vendors.
As for something else have a look at
Maybe might work.
(or)
at https://forum.xda-developers.com/t/activate-volte-om-pixel-4xl-android-11-r.4163217/ -- but this seems to work only if the device is kept in permissive mode which is not a good thing afaik.
Edit: Just looked at the other thread (https://forum.xda-developers.com/t/mod-ish-asusvolte-w-root-fix.4322877/) guess most of the above is just repeat info to what you already know.
Click to expand...
Click to collapse
My progress made so far is here

JazonX said:
My progress made so far is here
Click to expand...
Click to collapse
any luck so far? need volte for my area as i am intending to buy one

Got the latest Qualcomm 888 (Lahaina) MBN's uploaded here.
If anyone figures out a way to push them on Android 11 - Please share.

Question HELP needed for unlocking the Mi ultra

HI
I tried to unlock my MI ultra ... but the unlock tool doesnt see my phone
I did .. developper option ... the OEM unlocking , USB debugging and the Mi unlock add account
I signed into same account on the latest unlock tool
fastboot mode
but nothing appear on the unlock tool screen
what did I miss ?

You have to install the Fastboot drivers on your Windows.

Afg Playa said:
You have to install the Fastboot drivers on your Windows.
Click to expand...
Click to collapse
I DID
But same issue .. I will try to use different PC

Anesthetist said:
HI
I tried to unlock my MI ultra ... but the unlock tool doesnt see my phone
I did .. developper option ... the OEM unlocking , USB debugging and the Mi unlock add account
I signed into same account on the latest unlock tool
fastboot mode
but nothing appear on the unlock tool screen
what did I miss ?
Click to expand...
Click to collapse
On Windows 10 with your phone plugged in just go to windows update and you'll find a driver install request

Anesthetist said:
HI
I tried to unlock my MI ultra ... but the unlock tool doesnt see my phone
I did .. developper option ... the OEM unlocking , USB debugging and the Mi unlock add account
I signed into same account on the latest unlock tool
fastboot mode
but nothing appear on the unlock tool screen
what did I miss ?
Click to expand...
Click to collapse
Did you do the unlocking in fastboot mode? Try another usb cable, some people are having issues with some.

Run the unlock tool as an administrator - the only thing which solved it for me under Windows 10.

Send me a private message with teamviewer details. I can help

Make sure the following is done prior to booting into fastboot:
Make sure that developer options is enable.
Make sure Unlock OEM is enabled
Make sure you have linked your MI account to your phone
Make sure USB debugging is enabled
Step 1: Place the phone in fastboot and plug it into your PC.
Step 2: Navigate to your windows search bar, enter "device manager" and open the top result. It should now show you several different drivers. You should see one named Android under "Other Devices."
{
"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"
}
If you see a little triangle, then you just need to download the driver for it.
I downloaded these driver
Step 3: Uncompress the files and open the folder up. You should see a file called Mi USB Driver. Run that file.
Step 4: A window will pop up asking you to unplug your Phone. Unplug it from the USB and replug it back in. It should then change the message to "Installing Drivers"
Step 5: Open the MI Unlock Tool and refresh. You should now have the ability to unlock the phone.
Let me know if that helped, or if you need additional assistance.

panda24z said:
Make sure the following is done prior to booting into fastboot:
Make sure that developer options is enable.
Make sure Unlock OEM is enabled
Make sure you have linked your MI account to your phone
Make sure USB debugging is enabled
Step 1: Place the phone in fastboot and plug it into your PC.
Step 2: Navigate to your windows search bar, enter "device manager" and open the top result. It should now show you several different drivers. You should see one named Android under "Other Devices."
View attachment 5329617
If you see a little triangle, then you just need to download the driver for it.
I downloaded these driver
Step 3: Uncompress the files and open the folder up. You should see a file called Mi USB Driver. Run that file.
View attachment 5329623
Step 4: A window will pop up asking you to unplug your Phone. Unplug it from the USB and replug it back in. It should then change the message to "Installing Drivers"
View attachment 5329625
View attachment 5329627
Step 5: Open the MI Unlock Tool and refresh. You should now have the ability to unlock the phone.
View attachment 5329629
Let me know if that helped, or if you need additional assistance.
Click to expand...
Click to collapse
Thank you so much
I have been very busy lately with covid 19 pts and Urgent operations ... I will follow your instructions as soon as I can
Thank you so so much

Anesthetist said:
Thank you so much
I have been very busy lately with covid 19 pts and Urgent operations ... I will follow your instructions as soon as I can
Thank you so so much
Click to expand...
Click to collapse
Please let me know if it worked for you.
I'll have to do the same procedure soon.

Question My computer doesn't recognize the phone in fastboot even with drivers installed

Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.

Check in another USB Port, use original xiaomi's wire...and install latest USB drivers

I have the same problem, i'm using the original xiaomi wire and already installed lastest usb drivers.. the fact is that when I plug in the cell phone in fastboot mode the computer keeps sounds as connecting and disconnecting the device (I used two wires and two different computers)

Yup exact same thing, I hope somebody knows how to fix it and help us out.

Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem

Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
I'll try that, thanks for the help.

I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.

seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
Can you please tell me how do I do that?

Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
Tried that but still don't recognize the phone

seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
worked perfect for me! thank you!

liam_lost said:
Can you please tell me how do I do that?
Click to expand...
Click to collapse
{
"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"
}

seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
Thanks I tried but not sure why it shows this android one

liam_lost said:
Thanks I tried but not sure why it shows this android oneView attachment 5366067
Click to expand...
Click to collapse
Thats it bro, change that to Xiaomi Composite MDB interface, the first time my cellphone showed the same.

Ricardo 182 said:
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
Click to expand...
Click to collapse
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.

Pino76 said:
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Click to expand...
Click to collapse
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.

seyren00 said:
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
Click to expand...
Click to collapse
Thank you, unfortunately, it didn't work for me. My device is still not showing up.

liam_lost said:
Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Click to expand...
Click to collapse
Hi, after almost 2 days of constant researching and trying and failing and testing, I have finally figured it out! You need two things: MediaTek Driver and disabling Driver Signature Enforcement in Windows 10. It's because normally, the (64-bit) Windows 10 system won't allow you to install an unsigned driver and the Mediatek Driver is unsigned.
Here are the steps:
1. Press the Windows key on your keyboard, open PC settings
2. Go to Update & Security
3. Go to Recovery tab
4. Press & hold Shift key on your keyboard and click the Restart now button (in the Advanced startup section)
5. Select Troubleshoot ->Advanced setup -> Startup Settings and press Restart
6. Press 7 number key corresponding to "Disable driver signature enforcement" entry.
The system will now boot with the Driver Signature Enforcement disabled (it's going to be automatically enabled with the next restart). Download the Mediatek Driver (official source), unzip the file. Here's how I installed the driver:
1. Press the Windows key, type Device Manager and open the utility program
2. Click the top item in the list (your PC's name) and click Action in the menu and select Add Legacy Hardware.
3. Click Next in the Wizard, select Install hardware manually, and again Next and Next again.
4. Click Have Disk, Browse, navigate to the unzipped folder: SmartPhoneDriver > x64 > Unsigned infs and select the file android_winusb.inf. Click OK and select Media Tek Inc. in the left pane and then Next and Finish.
Your phone will now finally appear in the Unlock Tool.
This should work for all Note 10s users who also happen to have a 64-bit Windows 10 machine. Let me know how it went for you.

hey Guys, i´m new in the forum. But i had the same problem and i´m bringing the solution.
This error happens because Windows doesn´t recognize the bootloader, then you must install manually the bootloader´s driver and connect again your phone, so simple. I´m attaching the driver in this post.
Cheers.

download google usb driver: https://developer.android.com/studio/run/win-usb
connect phone to pc in fastboot mode. then go to device manager and update related driver named: android.
choose have disk and select Android_USB.inf file. then highlight Android bootloader interface and install driver. in win 10 must disable driver signature verification

seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
After searching for a long time, I found that this is the solution that works 100%. At last I was able to register the unlock of the bootloader today after a week of searching how to do it, since the driver did not work, thank you.

[WORKING] Force enable VOLTE - VOWIFI on OxygenOS Beta 11

Hello! This is my guide to enable or activate VoLTE/VoWIFI on Oneplus 6T OxygenOS 11 Beta
Before I install OSS 11 Beta, my VoLTE is working fine and I used this method to enable it but after I upgrade it to OSS 11 beta, The VoLTE is not working anymore so after much research I found the solution.
Tools to be needed:
ADB
Oneplus Drivers
Qualcom Drivers
QSPT Software
1st - Connect your phone and run adb on administrator mode and type this command:
adb devices - make sure that your device is working on adb
adb reboot ftm - this will reboot your phone into diagnostic mode and you can see Chinese characters there
adb shell
then type this command
setprop sys.usb.config diag,serial_cdev,rmnet,adb then enter
after that, don't close the command prompt
2nd - open device manager and make sure on the com port tab, you can see the Qualcomm HS something like that.
if you can see that the driver is installed, next is
3rd - open PDC as administrator
4th -Select your device on the drop-down menu then if you see your device select it and right-click on "Oversea-Commercial_DS" and deactivate Sub0 and Sub1
Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)
5th - Close the app and reopen it
6th - Select India-VoLTE-Vodafone or Telefonica_UK_Commercial, right-click and SetSelectedConfig for both Sub0 and Sub1
7th - Click on the profile you selected (India) again and click on Activate
Yes, select UK/India even if you are located in another region (see above for confirmed locations + carriers)
8th -Close the PDC and go back to cmd/adb then type
adb reboot
and Boom! VoLTE is Working
I combined the tutorial on this forum https://forum.xda-developers.com/t/guide-volte-vowifi-working-for-german-carriers.3817542/ and my own research.

Hi does this method need a "root"???

mrgibss said:
Hi does this method need a "root"???
Click to expand...
Click to collapse
no need.

lockmunk said:
no need.
Click to expand...
Click to collapse
Generally I managed to enable VoLTE & VoWifi without PDC tool (only via EFStool), but in OOS 11 Beta for Oneplus 6T I have lost HD+ (EVS Codec) quality. Now I have only HD calls. I just want to try to do it via PDC tool. maybe some codec will be loaded by PDC - does somebody has an idea if this will do not work (HD+) ???
Thanks in advance for any feedback or tip in this matter.

mrgibss said:
Hi does this method need a "root"???
Click to expand...
Click to collapse
No my friend. It doesn't required root.

mrgibss said:
Generally I managed to enable VoLTE & VoWifi without PDC tool (only via EFStool), but in OOS 11 Beta for Oneplus 6T I have lost HD+ (EVS Codec) quality. No I have only HD calls. I just want to try to do it via PDC tool. maybe some codec will be loaded by PDC - does somebody has an idea if this will do not work (HD+) ???
Thanks in advance for any feedback or tip in this matter.
Click to expand...
Click to collapse
Just try this method if it's going to work.

blackjack1942 said:
Just try this method if it's going to work.
Click to expand...
Click to collapse
So this method works for PDC tool, I was able to see MBN profiles. I have loaded different one and VoLTE & VoWIFI works as previous, but still only in HD, no in HD+ (EVS codec). So maybe some other tips??? (small remark today I have update to OOS11 Open Beta 2 without change).

mrgibss said:
So this method works for PDC tool, I was able to see MBN profiles. I have loaded different one and VoLTE & VoWIFI works as previous, but still only in HD, no in HD+ (EVS codec). So maybe some other tips??? (small remark today I have update to OOS11 Open Beta 2 without change).
Click to expand...
Click to collapse
UPDATE: it works !!! I have uploaded by PDC tool mbn profiles, then I repeat process via EFS Tools and it start to work (HD+) EVS Codec, thanks for PDC tutorial.

mrgibss said:
UPDATE: it works !!! I have uploaded by PDC tool mbn profiles, then I repeat process via EFS Tools and it start to work (HD+) EVS Codec, thanks for PDC tutorial.
Click to expand...
Click to collapse
Could you share these profiles?

ppajdek said:
Could you share these profiles?
Click to expand...
Click to collapse
Of course, soon I will upload them.

These MBN files are from PIXEL3 which are suitable for OP6/6T (probably for others OP also but I did not test them). Generally I have checked only one profile for Orange (PL), but the are also for other carries (T-Mobile PL and probably Plus GSM).

mrgibss said:
These MBN files are from PIXEL3 which are suitable for OP6/6T (probably for others OP also but I did not test them). Generally I have checked only one profile for Orange (PL), but the are also for other carries (T-Mobile PL and probably Plus GSM).
Click to expand...
Click to collapse
Thanks, im on Play PL, will check it out.

ppajdek said:
Thanks, im on Play PL, will check it out.
Click to expand...
Click to collapse
Choose this profile for Play, if You will have any problems, write to me PM (better speak in Polish)
{
"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"
}

i have tried the instructions above but it keeps getting back to default, until i tried to remove the overseascommercial ds, and avtivate the india volte, it is now working fine as of now. thanks!

blackjack1942 said:
Hello! This is my guide to enable or activate VoLTE/VoWIFI on Oneplus 6T OxygenOS 11 Beta
Before I install OSS 11 Beta, my VoLTE is working fine and I used this method to enable it but after I upgrade it to OSS 11 beta, The VoLTE is not working anymore so after much research I found the solution.
Tools to be needed:
ADB
Oneplus Drivers
Qualcom Drivers
QSPT Software
1st - Connect your phone and run adb on administrator mode and type this command:
adb devices - make sure that your device is working on adb
adb reboot ftm - this will reboot your phone into diagnostic mode and you can see Chinese characters there
adb shell
then type this command
setprop sys.usb.config diag,serial_cdev,rmnet,adb then enter
after that, don't close the command prompt
2nd - open device manager and make sure on the com port tab, you can see the Qualcomm HS something like that.
if you can see that the driver is installed, next is
3rd - open PDC as administrator
4th -Select your device on the drop-down menu then if you see your device select it and right-click on "Oversea-Commercial_DS" and deactivate Sub0 and Sub1
Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)
5th - Close the app and reopen it
6th - Select India-VoLTE-Vodafone or Telefonica_UK_Commercial, right-click and SetSelectedConfig for both Sub0 and Sub1
7th - Click on the profile you selected (India) again and click on Activate
Yes, select UK/India even if you are located in another region (see above for confirmed locations + carriers)
8th -Close the PDC and go back to cmd/adb then type
adb reboot
and Boom! VoLTE is Working
I combined the tutorial on this forum https://forum.xda-developers.com/t/guide-volte-vowifi-working-for-german-carriers.3817542/ and my own research.
Click to expand...
Click to collapse
Thanks for this tutotrial. wotks perfect. very Happy!

mrgibss said:
Generally I managed to enable VoLTE & VoWifi without PDC tool (only via EFStool), but in OOS 11 Beta for Oneplus 6T I have lost HD+ (EVS Codec) quality. Now I have only HD calls. I just want to try to do it via PDC tool. maybe some codec will be loaded by PDC - does somebody has an idea if this will do not work (HD+) ???
Thanks in advance for any feedback or tip in this matter.
Click to expand...
Click to collapse
Please share the tutorial of this method so we can compike the tutorials. Thank you

@blackjack1942
I've tested your method on latest stable OOS11, and I had to do few extra steps to get the VoLTE/VoWiFI on my 6T.
Before step No.1 - enable USB debugging
After the step No. 8 download older 1+ OEM Logkit 1.0-1, install it, open dialer (Google Dialer also works), enter *#800# and LogKit app should open, then:
Oneplus Logkit-> Function Switch
Enable VoLTE switch, VoWifi switch and VT Switch
Done.

blackjack1942 said:
Please share the tutorial of this method so we can compike the tutorials. Thank you
Click to expand...
Click to collapse
Will do, just need a bit of time

I had to combine this with https://forum.xda-developers.com/t/guide-activate-volte-vowifi-oos-11-ob1-ob2.4223967/ to get it to work - EFS on it's own didn't, nor did PDC. PDC, followed by reboot, followed by EFS did the trick - OP6T on Telstra (Boost) AU - used the AUNZ\Telstra\Commercial mcfg_sw.mbm from the pixel3 dump after setting to Telefonica_UK_Commercial.

Cannot for the life of me get PDC to work, it just says connect to device failed, even if I load up efs first or not
Any idea why? Oneplus 8T kb2020

How To Guide [NE2213] How to enable VoLTE (OnePlus 10 Pro 5G)

A lot of things changed with OnePlus brand, now they are exactly same as Oppo (OxygenOS 13 and ColorOS 13 are exactly same)
I believe OnePlus 9 Pro was the last real OnePlus smartphone.
R.I.P. OnePlus and OxygenOS !!
By the way this isn't the point of this thread, so let's start the process:
Unfortunately you need root access to enable VoLTE, also you need a windows PC for this.
Warning: do it at your own risk, I'm not responsible if somethings goes wrong for you !!
In my opinion, OnePlus created a whitelist for carriers and if your carrier is not on the list, you can't use VoLTE, even though it fully supports it !! WTF OnePlus ?!!
Before with OnePlus 9 Pro we could enable VoLTE by LogKit and EngineerMode
Now with OnePlus 10 Pro you are out of luck because LogKit doesn't work at all and you can't easily access to EngineerMode !!
Fortunately, still we can enable it
Note: If your phone model is NE2215 i recommend you to convert it to NE2213 with OPLocalUpdate app as NE2213 supports more 4G bands
0- Extract stock boot.img from payload.bin
Download one of below Full ROMs:
[NE2213] OxygenOS 13.1.0.522(EX01)
[NE2213] OxygenOS 13.1.0.521(EX01)
[NE2213] OxygenOS 13.1.0.520(EX01)
[NE2213] OxygenOS 13 C.30
[NE2213] OxygenOS 13 C.26
[NE2213] OxygenOS 13 C.22
[NE2213] OxygenOS 13 C.21
[NE2213] OxygenOS 13 C.20
[NE2213] OxygenOS 13 C.19
[NE2213] OxygenOS 13 C.17 (Android 13 Beta 2)
[NE2213] OxygenOS 12 A.15
[NE2213] OxygenOS 12 A.12 (Android 12 Rollback)
You can find payload.bin in Full ROM zip file
Use payload_dumper to extract boot.img
Code:
python3 payload_dumper.py --images boot payload.bin
Another option to doing this is FastbootEnhance which is a windows GUI app
1- Prepare your PC
Unzip Platform-Tools (You should add the directory path to "Environment Variables > System variables > Path")
Spoiler: Verify "Platform-Tools" installation
Check if you installed platform tools correctly:
Search for cmd, right click on it and select "Run as administrator"
Type "adb --version" and hit the enter button
If the output shows adb version that means you installed platform tools correctly
Install Qualcomm USB Drivers
Install QPST
2- Prepare your phone
Enable "Developer options" (click on "Settings > About device > Version > Build number" several times)
Go to "Settings > System settings > Developer options" and enable "OEM unlocking" + "USB debugging"
Spoiler: Unlock bootloader
Connect your phone to PC in MTP mode (File Transfer)
Open cmd (Run as administrator) and type "adb reboot bootloader"
Allow USB Debugging for your PC in the phone
Now type "fastboot flashing unlock"
On your phone you should see a message about unlocking the bootloader
With volume up/down you can move between options
Select Unlock boot loader option with power button (It will wipe your data)
Done, the phone bootloader is unlock now.
Spoiler: Root access
Since you unlocked the bootloader you should enable developer options again
Install latest version of Magisk (Download apk from here)
Patch stock boot.img:
Transfer stock boot.img to your phone
Open Magisk and select install
Choose "Select and Patch a File" then click on "LET'S GO"
You can find the patched boot in "Download" directory
Transfer it to your PC
Temporary root access:
Open cmd (Run as administrator) and type "adb reboot bootloader"
Allow USB Debugging for your PC in the phone
Type "fastboot boot patched_boot.img" (change patched_boot.img to whatever your filename is)
Permanent root access:
After booting, Open Magisk and click on install again
Now select "Direct Install (Recommended)" then click on "LET'S GO"
Done, you have a permanent root access now
Note: There are some guides that suggest you a way to update with OTA when you have root access
But i don't recommend it, because it's risky and you may get into bootloop
** IGNORE OTA UPDATE while you have root access **
3- LogKit alternative
With LogKit you could bring back "VoLTE calls" and "Wi-Fi calling" to sim settings
As i mentioned before LogKit no longer works on OnePlus 10 Pro
To achieve this:
Install "VoLTEEnabler" magisk module and reboot
Now you should see the options in "Settings > Mobile network > SIM 1"
4- EngineerMode alternative
With EngineerMode we could enable "Full-port switch" to working with PDC
By root access you can achieve this easily:
1- Connect your phone to PC in MTP mode
2- Open cmd and type:
Code:
adb shell
3- Switch to root user (For first time you need to grant root access to adb on your phone) :
Code:
su
4- Enable Full-port switch:
Code:
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
5- Last step
Open PDC app (It's included in QPST)
Open device dropdown and select your phone
Spoiler: Skip this if you can find "Commercial-DT-VOLTE"
Find "Oversea-Commercial_DS" or "Common-Commercial" and make sure both Sub0 and Sub1 are Inactive (for me both were Inactive by default)
Find "Commercial-DT-VOLTE" and Active it for both Sub0 and Sub1 (right click on it > SetSelectedConfig > click on Sub0 ... do the same for Sub1 ... now both are Pending, click on Activate)
BOOM! you can see "VoLTE" icon on your status bar
{
"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"
}
Note: You should repeat steps 4 and 5 after each reboot
Anyway, it's better than nothing
If someone found a permanent way please share it with the community
[Edit] Just one more step:
Remove the default profile ("Oversea-Commercial_DS" or "Common-Commercial") to keep VoLTE active after device reboot
(Thanks to @ash083)
>> Final word
This is my first and last OnePlus phone!
OnePlus completely destroyed OxygenOS (Say hi to MiUi [ColorOS] by OnePlus [OPPO] !!!)
Almost 99% people buy OnePlus to enjoy stock android experience with a bunch of customization options.
For me OnePlus is dead.
I will buy google pixel 7 pro next year and don't let any of my family member or my friends buy from this FAKE BRAND (OnePlus) !!!
If this topic was useful for you press the thanks button

Hi
Followed everything but never got the voLTE icon on the statusbar

Gunsmoke_79 said:
Hi
Followed everything but never got the voLTE icon on the statusbar
Click to expand...
Click to collapse
Dude, first make sure your carrier supports VoLTE ...
Install "5G Only" app:
5G Only - Android 11 Compatibl - Apps on Google Play
Change your network mode to 5G only (NR only)
play.google.com
You need to check "Voice Service" and "Voice Network Type" values.
Here is mine
As you can see:
Code:
Voice Service: In Service
Voice Network Type: LTE

Guys, I have bad news, since "1 September" SecrecyAutoUnlocker stopped working as other users reported here
I just do a reboot today and damn !! No VoLTE again !!
SecrecyAutoUnlocker no longger works for me too
Nice job OPPO (OnePlus) !!!

No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#

6addri said:
No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#
Click to expand...
Click to collapse
Thanks!
With root access we don't need EngineerMode at all

6addri said:
No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#
Click to expand...
Click to collapse
Hey 6addri yes please share your method!
Thanks

Gunsmoke_79 said:
Hey 6addri yes please share your method!
Thanks
Click to expand...
Click to collapse
OP edited
Check it again
I managed to enable VoLTE on OOS13 OB 2
Thanks to @6addri

Is this working for 9 pro?

vigorito said:
Is this working for 9 pro?
Click to expand...
Click to collapse
Probably yes

On 9pro with a familiar dial code there is no logkit and engeer. mode too,they remove it ,so what are the steps then for 9pro (LE2123)

vigorito said:
On 9pro with a familiar dial code there is no logkit and engeer. mode too,they remove it ,so what are the steps then for 9pro (LE2123)
Click to expand...
Click to collapse
You need unlocked bootloader + root access (check 9 Pro forum)
Other steps should be same as 10 Pro

Already start to working on that,so after i finish unlock b./root access, i should skip rom flashing and start from step prepare your pc i mean its allready prerared skipping flashing rom step 0,i just dont get this step for "Environment Variables > System variables > Path") do i have to unzip platform tools to the path you wrote or i have to do something else

vigorito said:
Already start to working on that,so after i finish unlock b./root access, i should skip rom flashing and start from step prepare your pc i mean its allready prerared skipping flashing rom step 0,i just dont get this step for "Environment Variables > System variables > Path") do i have to unzip platform tools to the path you wrote or i have to do something else
Click to expand...
Click to collapse
You need "adb" + "fastboot" and both are required for rooting
So i think you already have these (if you didn't use a wrapped tool for rooting)
To confirm this type:
"adb --version"
"fastboot --version"
In cmd, you should see adb and fastboot version.

i figure out variable settings path,i have working adb,and i can boot into bootloader with "adb reboot bootloader" command (locked) but im having problem after i type "fastboot devices" in cmd not showing device id,but command "adb devices" showing device id hm

vigorito said:
i figure out variable settings path,i have working adb,and i can boot into bootloader with "adb reboot bootloader" command (locked) but im having problem after i type "fastboot devices" in cmd not showing device id,but command "adb devices" showing device id hm
Click to expand...
Click to collapse
You should open cmd with admin access (Run as administrator)

i always do that

i use command adb reboot bootloader,phone get into fastboot mode and when i send command fastboot oem unlock its just says waithing for any device,usb debb. is ON and oem unlcok is ON,qualcom drivers are installed its all good

I tried using the magisk module, and in the SIM1 settings I have VoWifi enabled (with preference), but it does not work at all. The icon does not show in the status bar, and when I turn off VoLTE, calls do not work. Is this module known to not work on A13?
EDIT: In the 5G Only app, under IMS status I see that Voiceover WiFi is unavailable (LTE is available). How do I enable it? Contact my carrier?

Arnav74 said:
I tried using the magisk module, and in the SIM1 settings I have VoWifi enabled (with preference), but it does not work at all. The icon does not show in the status bar, and when I turn off VoLTE, calls do not work. Is this module known to not work on A13?
EDIT: In the 5G Only app, under IMS status I see that Voiceover WiFi is unavailable (LTE is available). How do I enable it? Contact my carrier?
Click to expand...
Click to collapse
This topic isn't about VoWiFi
Also my carrier doesn't support VoWiFi, so i can't test it, sorry!