Database Users

[Q] ADB not showing device

Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.

akrabi said:
Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.
Click to expand...
Click to collapse
Did you enable usb debugging?

Also check that you have an option selected under Settings>Storage>USB Computer connection, not having either MTP or PTP selected there will also bork adb.

If you still can't get it to work, try Koush's universal drivers: Link

still not working...
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???

akrabi said:
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???
Click to expand...
Click to collapse
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.

taodan said:
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.
Click to expand...
Click to collapse
Ok, so I'm with my Nexus connected as an MTP device, with the driver from XDA installed (see attached image), USB Debugging enabled:
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
C:\>

Any advice???
Anyone has any advice??
I really have not idea what to do. Tried everything...
Thanks

Works on a different computer
I've connected the phone to my borther's PC and installed the drivers from the SDK. It worked without any problem.
I really can't figure out why it's not working on my laptop.

[Solved]
OK...
So as I said before I tried connecting when PTP is checked and when neither PTP nor MTP are checked and on both couldn't install the drivers properly (neither from xda nor from sdk).
What worked for me:
1. Uncheck both PTP & MTP
2. Device Manager -> Nexus 4 -> Update Driver Software -> Browse my computer for driver software
3. Now instead of browsing to the location I went to "Let me pick from a list..."
4. It should show a list of devices/manufacturers. Clicked "Show All Devices"
5. On the bottom right click "Have a disk"
6. Point to the android_winusb.inf file from Android SDK
7. Choose Android ADB Interface from the list
8. Let driver install
Click to expand...
Click to collapse
Hoped it will help someone.
Thanks to everyone that tried to help. :good:

delete OnePlus drivers

hello,
since i have installed the OnePlus Drivers i have no MTP, no RNDIS (Thethering) Windows can't reconize the phone connected, and there no item in device manager !
i've tried to install the drivers in another PC and the same thing happens !
and when the device is connectet a least once i can't reboot propely the pc.
so i tried to delete the drivers by clicking on Uninstall.exe on the following directory: C:\Program Files (x86)\OnePlus USB Drivers and reboot and i can't still reconize the phone ....
so how to delete them ?

Nevermind, i found the solution
juste one words:
DONT INSTALL ONEPLUS DRIVERS
remove the drivers via the Uninstall.exe or program manager
then remove the Qualcomm HS-USB Diagnostics 900E drivers on ports (COM and LPT section ) in device manager ( you have to check hidden drives)
reboot.
and voila problem fixed
source: https://forums.oneplus.net/threads/oneplus-5-windows-10-no-usb-connections.554305/page-3

johnstinks said:
Nevermind, i found the solution
juste one words:
DONT INSTALL ONEPLUS DRIVERS
remove the drivers via the Uninstall.exe or program manager
then remove the Qualcomm HS-USB Diagnostics 900E drivers on ports (COM and LPT section ) in device manager ( you have to check hidden drives)
reboot.
and voila problem fixed
source: https://forums.oneplus.net/threads/oneplus-5-windows-10-no-usb-connections.554305/page-3
Click to expand...
Click to collapse
Sorry but lmao. You must be using Windows 10? Silly, they have to pry Windows 7 from my cold dead hands. It's bullet proof

yes i'm using Windows 10
sadly my solution didn't work
i even deleted the drivers from C:\Windows\System32\drivers folder and C:\Windows\System32\DriverStore\FileRepository folder and when i reboot the drivers come back ....

johnstinks said:
yes i'm using Windows 10
sadly my solution didn't work
i even deleted the drivers from C:\Windows\System32\drivers folder and C:\Windows\System32\DriverStore\FileRepository folder and when i reboot the drivers come back ....
Click to expand...
Click to collapse
had that problem 10 mins ago, because I want to unlock my bootloader. Here you go!
https://www.youtube.com/watch?v=eNG6tKag49U&t=13s

[Guide] Enable Volte on custom rom (Android 10) (Rooted)

Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97

Got stuck at PDC
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.

aperture22 said:
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.
Click to expand...
Click to collapse
Did you install the Qualcomm usb driver which came included in the QPST zip file.
I'm not sure if it is a problem with the qpst version ,I'm using QPST 2.7.480.
And once I run the command in adb shell I get my device to show up as Qualcomm USB Composite Device in device manager under the universal serial bus controllers category.
And if everything is working well , the pdc will not show anything when it opens up but you'll find your device in the drop down menu.

I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.

aperture22 said:
I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.
Click to expand...
Click to collapse
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg

activate button is disabled even after running as admin

Gauravlonkar said:
activate button is disabled even after running as admin
Click to expand...
Click to collapse
To activate a profile: Right click on it and under setselectedconfig select sub0/sub1/both (try and check what works for you) and then you'll be able to click the activate button.
To deactivate select the sub under deactivate in the right click menu (or) just activate some other profile .
Do check the other xda forum posts related to this which i've provided links under reference, it might be helpful when you're stuck with something related to this .

the command after su doesn't do anything to my custom rom ....

prokiller1199 said:
the command after su doesn't do anything to my custom rom ....
Click to expand...
Click to collapse
I've tested it to work with luisrom,Havocos and some other rom I don't remember which one.
Running the command doesn't bring any popup or open up anything on the phone but you'll be able to see the change in the device manager of your pc.
The change caused by the command only persists till it is connected (ie. if you unplug nd replug the usb cable it will revert to the default state), until you change the state from the option provided in your notification (ie . something like from charging only to file transfer or tethering ect) and restart of the device.
Do also check if you have the correct drivers installed.

*deleted*

Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.

aperture22 said:
Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.
Click to expand...
Click to collapse
hello,
why in PDC shows no devices (even when run as Admin)? I have the same problem.

gammerboy said:
Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97
Click to expand...
Click to collapse
Sir can u make a total video tutorials so that we can easly understand because i just confuse what shuld i insta 8n pc and what shuld instal in mobile
---------- Post added at 07:55 AM ---------- Previous post was at 07:52 AM ----------
ronaksworld said:
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg
Click to expand...
Click to collapse
Sir in this zip file their two apk file but that not installed in my phone can u tell me which one shuld i instal in pc and phone step by step plz

Tried to enable VoLTE & VoWIFI on my Redme 9 Pro, using the PDC and can actually get the VoWIFI works. However, once the device reboot, it just fall back to the ROW_Commercial profile and have to redo again to get it work.
Can anyone help with this issue?

Thans for your support

I'm also trying to activate VoLTE on my oneplus3t. But stuck in loading a .MBN file in the PDC tool. When I click the load button and select the .MBN file to open nothing happens.

[Guide] VoLTE/VoWiFi/ViLTE/EVS HD+ codec [no root] latest OOS 11.0.7.7

To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “qud.win.1.1_installer_10061.1.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
You should see some Chinese characters on display
8) Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6"
9) In CMD:
ADB shell
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
10) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator”, select device with filled "EFS" and "Banner" fields and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps in PDC.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
11) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
12) In ADB:
ADB reboot
13) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
14) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
15) Disable USB Debugging if necessary.
16) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
After update to latest version VoLTE was not working again. I think we should repeats this step after every update, until OnePlus (if) fixed this issue.

Hello.
Does the step 9 has to be done , becouse i cant get a connection with efs explorer. Its just blank. I ask becouse i have volte and vowifi activated but my phone wont turn automatic to vowifi when i get a wifi connection. i have to first turn off volte and reboot that the phone connects to vowifi

zorantoma
Hi. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?

vip77 said:
To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “QUD.WIN.1.1+Installer-10037.3+Setup.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
ADB shell
setprop sys.usb.config diag,serial_cdev,rmnet,adb
You should see some Chinese characters on display
8) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator” and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
9) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
10) In ADB:
ADB reboot
11) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
12) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
13) Disable USB Debugging if necessary.
14) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
View attachment 5202729View attachment 5202731View attachment 5202727View attachment 5202725
Click to expand...
Click to collapse
hi i have a problem, i can't connect my op8 to efs file explore, it tells me it is not supported

Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot

vip77 said:
Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot
Click to expand...
Click to collapse
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator

this is what i get when i run efs explorer

patonovich said:
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator
Click to expand...
Click to collapse
zorantoma said:
this is what i get when i run efs explorer
Click to expand...
Click to collapse
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.

vip77 said:
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.
Click to expand...
Click to collapse
WOW thanks

patonovich said:
WOW thanks
Click to expand...
Click to collapse
Please report if everything went well. Good luck.

del

Thank you, it worked.
BR

Working great on OP8T,
Before this guide the Volte profile was change to the default oversea profile.
Thanl you.
UPDATE -
for some reason the OVERSEA profile is active , and volte is lost.
after that i change overideconfig files to Read only after
i copy the file to efsprofiles ,
its work for now for two days in row ,
before that the phone change to ovesea profile in half day.

not working :/
i tried exactly this and not working op8t

Grigiac said:
not working :/
i tried exactly this and not working op8t
Click to expand...
Click to collapse
What exactly "not working" which step?

vip77 said:
What exactly "not working" which step?
Click to expand...
Click to collapse
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t

Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.

vip77 said:
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.
Click to expand...
Click to collapse
yes, i did it with pdc on my last device op6 with other guide and work great
but now i have new device and tried with this guide..
and im using slot 1
i have no idea why its not working :/

Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
On which country are you?

Dreamelba said:
On which country are you?
Click to expand...
Click to collapse
Israel
tried India & telfonica uk
Nothing work

OP8 PRO 11.0.6.6 VOLTE/VOWIFI PDC MODEM CHANGE PROBLEM

Hi,
Has any of you found out how to change PDC modem profile in latest OxygenOS 11.0.6.6 ??
All the previous method does not work since the equipment devices has changed in Windows Device Manager (IN2020, RMnet, SMS). When I use for IN2020 driver Qualcomm HS-USB ethernet adapter 9091, it shows modem in PDC but then when trying to connect it gives failure - Connection failed
Previously, in 10.0.5.5 I was able to resolve it
[GUIDE] VoLTE & VoWIFI on 11.0.5.5 Oneplus 8 PRO
Hi, I've recently upgraded my phone from version 11.0.4.4 to 11.0.5.5 and after upgrade all my modem configs were reverted to the default ones. I was not able to use VoLTE & VoWIFI as before. Previous guides to run PDC tool didn't want to work...
forum.xda-developers.com

@mxtuu222
I now try update, and no problem with turn on vowifi/lte, works. No instal new driver, only open PDC and active again.

Youre saying that you're able to open PDC to choose profile?
My VoLTE and VoWifi toggles are enabled but the modem profile was reverted to the default one in PDC, which not gives me an option for VoWifi to work with my carrier.

mxtuu222 said:
Youre saying that you're able to open PDC to choose profile?
My VoLTE and VoWifi toggles are enabled but the modem profile was reverted to the default one in PDC, which not gives me an option for VoWifi to work with my carrier.
Click to expand...
Click to collapse
Yes after update, use app engineer mode toogle (*#801#) turn on engineer mode toggle,
adb reboot ftm, waiting,
adb shell # setprop sys.usb.config diag,serial_cdev,rmnet,adb
open PDC, and active sub 0 i sub 1 for my country.
adb shell,
reboot, and works.

Can you please share the Qualcomm driver that you used for IN2020 and Rmnet? Thanks

mxtuu222 said:
Can you please share the Qualcomm driver that you used for IN2020 and Rmnet? Thanks
Click to expand...
Click to collapse
I instal the driver when phone is adb reboot ftm and chinese sign disappear.

zioloiso said:
I instal the driver when phone is adb reboot ftm and chinese sign disappear.
Click to expand...
Click to collapse
Hi,
It seems that after uninstalling all Qualcomm Tools and installing them again, the IN2020 is now set as Qualcomm HS-USB WWAN adapter 9091 and PDC launches without fail.
I think it helps to clear drivers on Windows.
@zioloiso thank you for help

mxtuu222 said:
Hi,
It seems that after uninstalling all Qualcomm Tools and installing them again, the IN2020 is now set as Qualcomm HS-USB WWAN adapter 9091 and PDC launches without fail.
I think it helps to clear drivers on Windows.
@zioloiso thank you for help
Click to expand...
Click to collapse
Works, nice.

Was your phone rooted? I couldn't get the PDC connect to my unrooted OP 8 Pro.
A pop up message said: "connection fail!".