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
Related
The most simple way is this thread. I've done all the editing work for you.
This guide is based on Windows 7 Home Premium. It may be different on your computer. If you are on a Linux build or Mac, you don't need this
Steps: Difficulty: Easy/Medium
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
-Note: If it says not signed, just click next anyway
13. Wait and if it says not signed, click install drivers anyway
14. Wait until it's done, then close all of your programs
15. Press the windows key and R at the same time on your keyboard
16. Type cmd and hit enter (Command prompt will appear)
17. Copy and paste the following code into it:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini
18. Type adb kill-server
19. Type adb devices, and your device should now show up
20. Hit the thanks button below
Thanks to cajl-jbmm from MoDaCo for posting the modification required for the drivers to work
adb devices isn't saying anything.
Good day. I followed your previous steps but when I do "adb devices" I get no response. That is, no message back. When I try it once more this is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Dell>"C:\Program Files\Android\android-sdk\platform-tools\adb.exe">adb
devices
C:\Users\Dell>"C:\Program Files\Android\android-sdk\platform-tools\adb.exe">adb
devices
The process cannot access the file because it is being used by another process.
C:\Users\Dell>
Any help you have is welcomed.
I am having a similar problem.
When I type "adb devices" in command prompt, it returns with:
'adb' is not recognized as an internal or external command, operable program or batch file.
Not sure how to access adb in command prompt.
You need first to install:
Android SDK Tools (can download from archos)
I have sdk installed already
I have sdk installed already. Anymore suggestions? Thanks
baari21 said:
I have sdk installed already. Anymore suggestions? Thanks
Click to expand...
Click to collapse
Is it in your path?
Sent from my ARCHOS 80G9 using XDA Premium HD app
I got it to work. Even though there was no response stating the device was connected I tried "adb reboot" to check if the device was infact working with the adb and it was. So i got it working but perfectly. Only thing is there is no response stating the device is connected but i can live without that. Thanks for the help guys.
adb tool has moved
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK, launch the SDK and AVD Manager (execute the android tool) and install "Android SDK Platform-tools"
Please also update your PATH environment variable to include the platform-tools/ directory, so you can execute adb from any location.
I hope someone is on to help me here, i've done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
BUT... when i click next, it comes up saying....
'the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.
SO WHAT NOW????
MrLarner said:
I hope someone is on to help me here, i've done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
BUT... when i click next, it comes up saying....
'the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.
SO WHAT NOW????
Click to expand...
Click to collapse
You have a 64 bit version of Windows so it's not compatible, sorry
Sent from my HTC Desire HD using XDA
Is there anything i can do about it?
is there something else i can download instead?
or is the only option to use another computer?
MrLarner said:
Is there anything i can do about it?
is there something else i can download instead?
or is the only option to use another computer?
Click to expand...
Click to collapse
adb should perfectly work on 64 bit windows 7. I used it in the past, now I mainly use linux.
Just download the driver from ftp://support.archos.com/ARCHOS it/ADB/adb_winusb_driver.zip
Edit: also look here http://www.archos.com/support/support_tech/updates_adb.html?country=nl&lang=en
divx118
divx118 said:
adb should perfectly work on 64 bit windows 7. I used it in the past, now I mainly use linux.
Just download the driver from ftp://support.archos.com/ARCHOS it/ADB/adb_winusb_driver.zip
Edit: also look here http://www.archos.com/support/support_tech/updates_adb.html?country=nl&lang=en
divx118
Click to expand...
Click to collapse
Is that link for the driver different to the 1 i got from the opening post?
will this 1 work on windows x64?
---------- Post added at 04:20 PM ---------- Previous post was at 04:16 PM ----------
Ignore that last post, i checked it and its exactly the same as the file in the opening post.
I need a file which will work on windows x64
MrLarner said:
Is that link for the driver different to the 1 i got from the opening post?
will this 1 work on windows x64?
Click to expand...
Click to collapse
The link I posted is the original driver provided by archos and works with windows x64. Where the one in the opening post comes from I don't know.
divx118
I'm not to sure why im getting the problem then?
any idea's?
MrLarner said:
I'm not to sure why im getting the problem then?
any idea's?
Click to expand...
Click to collapse
Sorry no idea, I used that driver without problems on windows 7 64 bit.
divx118
Something else i noticed,
when i done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
all went well until i got to 5, it didnt show up unknown devices, it showed up at portable devices and it did not have a yellow ! next to it????
does it mean anything?
Yes, that means you haven't checked USB - Debugging on the device or selected MassStorage in the dropdown.
Sometimes it's not enough that it is selected, so deselect it, leave the menu, get in again and select it.
fzelle said:
Yes, that means you haven't checked USB - Debugging on the device or selected MassStorage in the dropdown.
Click to expand...
Click to collapse
I have, 100% checked usb debugging on.
and where would this mass storage be? i cant find it.
also, for me to enable usb debugging, i have to go to...
{ } Developer options.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
ok think i solved it, i managed to go to storage settings and then had the option once the usb was connected to chose between MTP - Media Device, or, PTP - Camera,
so i changed it from MTP to PTP and now when i go to device manager, its showing up as other devices and then archos has the yellow ! next to it.
does this mean i can continue now?
---------- Post added at 06:37 PM ---------- Previous post was at 06:29 PM ----------
Blimey im hitting problems at every step
i've now got to here...
17. Copy and paste the following code into it:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini
18. Type adb kill-server
19. Type adb devices, and your device should now show up
20. Hit the thanks button below
But when i type adb kill-server it comes up saying....
'adb' is not recognized as an internal or external command, operable program or batch file.
what now???
I've looked into it and everyone says i need to change the path???
i cant find out how to do this, or what to change the path to, someone please help!
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.
Hi. I installed qualcomm drivers and after that QPST and started PDC tool but it doesn't recognize my phone,even tough I activated USB debugging. Any ideas?
Usb port 3.0? Then use then usb 2.0 port, an other port or another usb cable
Sent from my Mi Note 10 using XDA Labs
NatorJ said:
Hi. I installed qualcomm drivers and after that QPST and started PDC tool but it doesn't recognize my phone,even tough I activated USB debugging. Any ideas?
Click to expand...
Click to collapse
The phone need to be switched to diag mode.
Before doing this Mod you should backup EFS-partition !!!
Need to have adb installed and phone rooted. Open cmd window and type:
adb devices (check if phone connected)
adb shell
su (grant root)
setprop sys.usb.config diag,serial_cdev,rmnet,adb
You will find new device in PC device manager "Qualcomm HS-USB WWAN Adapter 9091", then PDC tool will recognize your phone.
More info here: https://forum.xda-developers.com/poco-f1/how-to/guide-activate-vowifi-wlan-call-t3871263
vlouis said:
The phone need to be switched to diag mode.
Before doing this Mod you should backup EFS-partition !!!
Need to have adb installed and phone rooted. Open cmd window and type:
adb devices (check if phone connected)
adb shell
su (grant root)
setprop sys.usb.config diag,serial_cdev,rmnet,adb
You will find new device in PC device manager "Qualcomm HS-USB WWAN Adapter 9091", then PDC tool will recognize your phone.
More info here: https://forum.xda-developers.com/poco-f1/how-to/guide-activate-vowifi-wlan-call-t3871263
Click to expand...
Click to collapse
Qualcomm recognized but PDC tool doesnt recognize it
NatorJ said:
Qualcomm recognized but PDC tool doesnt recognize it
Click to expand...
Click to collapse
https://imgur.com/a/CODbtYN
NatorJ said:
Qualcomm recognized but PDC tool doesnt recognize it
Click to expand...
Click to collapse
In device manager you have "Qualcomm HS-USB Modem 9091" and not "Qualcomm HS-USB WWAN Adapter 9091".
Few weeks ago I changed my modem config using this method. I used Xiaomi.eu 20.7.9 MIUI12 weekly ROM. Or try to change the qualcomm drivers.
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.
Do not know if this happened on other Redmi series?
Can anyone help with this issue?
jengyiing said:
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.
Do not know if this happened on other Redmi series?
Can anyone help with this issue?
Click to expand...
Click to collapse
Delete row_commercial profile with pdc tool.
vlouis said:
Delete row_commercial profile with pdc tool.
Click to expand...
Click to collapse
Yes. it does work! after remove the row_commercial profile in PDC and reboot the phone. The profile now not fall back and VoWIFI is actully working now.
Thanks for your help!
I have the same problem as @NatorJ
Did the "adb shell; su (grant root);setprop sys.usb....." thing. Device get's recoginzed in device manager as "Qualcom USB Composite Device 9091" but NOT PDC tools.
Please Help
hello, how did you put the Row_Commercial profile back in pdc tool?
vlouis said:
The phone need to be switched to diag mode.
Before doing this Mod you should backup EFS-partition !!!
Need to have adb installed and phone rooted. Open cmd window and type:
adb devices (check if phone connected)
adb shell
su (grant root)
setprop sys.usb.config diag,serial_cdev,rmnet,adb
You will find new device in PC device manager "Qualcomm HS-USB WWAN Adapter 9091", then PDC tool will recognize your phone.
More info here: https://forum.xda-developers.com/poco-f1/how-to/guide-activate-vowifi-wlan-call-t3871263
Click to expand...
Click to collapse
Very much thanks for this information
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 on my unit, but after several hours, I've managed to solve how to do this. I'm sharing my method to all who has similar problems.
All the files for procedure are attached to the thread (use GUIDE ONEPLUS8 PDF) to see the procedure with screenshots. There is also guide how to root phone but it's not mandatory for VoLTE, VoWIFI change.
For POLAND PLAY VoLTE & VoWIFI choose DT_COMMERCIAL instead of PLAY_COMMERCIAL
VOLTE & VOWIFI – ACTIVATION & MODEM CHANGE
1. Enable USB debugging and have adb android shell installed
2. Upload to APK from tools folder to phone directory called Download
com.android.engineeringmode_V1.01.0.171117173719.25c8842-26_minAPI26(nodpi)_apkmirror.com.apk
com.oem.oemlogkit_1.0-1.apk
3. Find the apps and install
4. Type code on your phone *#800#
5. Don’t choose any app, stay in OnePlusLogKit
[GUIDE] Magisk for OxygenOS 11
Instructions - Download the magisk_patched.img - Reboot your device in bootloader-fastboot mode - Flash the patched_boot.img in the boot partition: fastboot flash boot boot.img replace "boot.img" with the magisk_patched.img path However, it...
forum.xda-developers.com
6. Go to Function Switch and enable (each time phone reboots)
a. VoLTE switch
b. VoWifi switch
c. VT switch
7. Go to your SIM Card in Settings and enable VoLTE and VoWIFI
8. Install QUD.WIN and QPST from the tools folder on Windows
9. Open CMD
# cd C:/adb
# adb reboot ftm
(this would turn off phone in development mode)
# adb shell
# setprop sys.usb.config diag,serial_cdev,rmnet,adb
(this enables diagnostic port needed for PDC)
10. Open Device Manager in Windows
11. Look for device IN20AA without driver – in the details find one with identifier MM_00 (there will be 3 same names but different identifiers)
12. Pick driver manually from file qqwan0.inf
13. Choose manually Qualcomm HS-USB WWAN adapter and adapt
14. There is gonna both devices visible in the Device Manager after few refreshes
a. Qualcomm HS-USB WWAN adapter
b. Qualcomm HS-USB WWAN adapter 9091
15. Try PDC with WWAN adapter 9091 if it’s working
16. If not, Unplug & plug the device (don’t write once more setprop, just plug it back)
17. In the Device Manager in Windows, delete Qualcomm HS-USB WWAN adapter but leave Qualcomm HS-USB WWAN adapter 9091
18. Open PDC once again and choose the only left Qualcomm HS-USB WWAN adapter 9091
19. The list of configs will be loaded
20. To change the modem config choose desired config ex. Commercial DT_POLAND (OLD ROW_COMMERCIAL NOT WORKING) – choose name, right click, select SUB0, SUB1 and click ACTIVATE. Check if in the row of your new modem config in SUB0 and SUB1 you have active setting
NOTE# For PLAY PL 260-06: DT Poland Commercial has VoLTE & VoWIFI
21. Close PDC. In cmd type command and reboot phone
# adb shell
Oneplus8$ reboot
NOTE!!! PDC MODEM SETTINGS MAY REVERT ONCE YOU TAKE THE SIM CARD OUT OF TRAY. YOU NEED TO MAKE THE CHANGE AGAIN TO DESIRED MODEM CONFIG.
#############################
CHANGE CARRIER POLICIES (UNLOCK BANDS)
Prerequisite is to have engineer apk installed.
1. Plug the phone into PC and dial *#801#
2. Turn on the Engineer Mode Toogle only
BASED ON: https://mt-tech.fi/en/modify-oneplus-7-pro-5g-8-and-8-pro-nr-lte-a-band-combos/
You have to install diag-driver manually if you have Android 11 installed. Check in Device Manager after enabled Engineer Toggle and connected USB to your computer you see two Unknown device labeled your phone model number. I have IN2013 (OnePlus 8 Europe).
Unknown devices in Device Manager
• Download Qualcomm diag-drivers and extract compressed zip-file.
• Right click the device and select Update driver.
• Select Browse my computer for drivers
• Select Let me pick from a list of available drivers on my computer.
• Select All devices.
• Browse drivers in extracted Qualcomm Drivers zip and find qmdm.inf
• Then find Qualcomm HS-USB MDM Diagnostics 90B6 and click Next to install it. You may get warning because hardware id doesn’t match. This driver still works fine.
• Now install same driver to second unknown devices (IN2013 if you have same model).
3. Now you should have driver installed to both interfaces.
4. Open QPST Configuration, Wait for Phone list in the window
5. Then go to Start Clients > QPST EFS EXPLORER
6. It will list all the QUALCOMM directories. Go to policyman directory
7. Copy the carrier_policy.xml (SIM1), carrier_policy.xml_Subscription01(SIM2) and lte_feature_restrictions
8. Modify files accordingly:
Modify OnePlus 7 Pro 5G, 8 and 8 Pro, 9 and 9 Pro NR/LTE-A band combos - MT-TECH.FI
On this instruction we will modify OnePlus 7 Pro 5G, 8 and 8 Pro band combo profiles with Qualcomm software. OnePlus has limited 5G access and 4G+/LTE+ Carrier Aggregation combinations and this instruction help you to unlock. However this instruction doesn’t unlock hardware defined combinations...
mt-tech.fi
or overwrite in QPST files with the modified files for PLMN 26066 with 5G and DSS enabled from folder on Onedrive called policyman (modified)
9. Reboot the phone
10. Dial in *#*#4636#*#*
11. Choose Phone
12. Choose Band config NR/LTE/TDSCDMA/GSM/WCDMA
Now it should work with all 5G bands regardless of some restrictions for not supported PLMNS
thanks. worked like a charm
thanks but after read the guide i think its to hard for me to do.
anyone have easyer method ?
after flash RadioActive kernel i lost VoLTE. (OOS 11.0.9.9.IN11AA)
I was unable to install any of the log kit provided. error given was ' conflicts with an existing package'. Any help?
momiloco said:
I was unable to install any of the log kit provided. error given was ' conflicts with an existing package'. Any help?
Click to expand...
Click to collapse
This is for OOS 11 Android 11
In A12 not is possible install logkit.
any idea what we can do in A12?
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar
fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.