My Nord 2 isnt using VOLTE or VOWIFI with Sunrise. Is there a way to enable it like with older models?
*#800# does not work
No, we still need to wait for future OTA to resolve this
skyzonemc said:
My Nord 2 isnt using VOLTE or VOWIFI with Sunrise. Is there a way to enable it like with older models?
Click to expand...
Click to collapse
Hey,
If you go on the digitec website and search for your phone, you get a disclairmer about 5G and Sunrise. This isn't strictly related to your issue, but I was wondering if you were able to use the Swiss 5G network with your phone. Maybe you can try calling sunrise directly ?
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Worked! Thank you
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Do you know how to enable 5g? my phone doesn't seem to connect to any 5g network. 5g is not shown as an option in sim settings.
Sorry, I don’t know.
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Thanks for the info. Do you know how to enable voWifi (WiFi Calling) for Vodafone UK?
aathi1 said:
Do you know how to enable 5g? my phone doesn't seem to connect to any 5g network. 5g is not shown as an option in sim settings.
Click to expand...
Click to collapse
Hi, I had the same problem. Usually you can do this with *#*#4636#*#* to access the phone info but those codes don't work on this phone.
I installed an app called "5G switch" (not sponsored by any means), then you can access the menu, and selected NR/LTE/TDSCDMA/GSM/WCDMA, which makes 5G appear in the settings, and works with Yallo (Sunrise) as a carrier. Hope it helps!
DerSandmann said:
Hi, I had the same problem. Usually you can do this with *#*#4636#*#* to access the phone info but those codes don't work on this phone.
I installed an app called "5G switch" (not sponsored by any means), then you can access the menu, and selected NR/LTE/TDSCDMA/GSM/WCDMA, which makes 5G appear in the settings, and works with Yallo (Sunrise) as a carrier. Hope it helps!
Click to expand...
Click to collapse
I have tried that but it does not work for me. Even though I selected the NR/LTE.. it still hooks onto 4g. are you aware of any methods to modify the radio files.. Thnx.
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Hi,
This method didn't work for me (although I have to mention that the VoLTE toggle was present in the SIM settings since first use).
I'm currently on a Dutch provider called hollandsenieuwe which operates on Vodafone NL network.
The strange thing is that VoWiFi just works fine since first use.
I checked all the settings for VoLTE (even the one for the icon to appear in the top bar which is disabled by default but nothing).
Asked support to the provider but they just say that the issue is with the device.
I tested with the previous model Oneplus Nord 5G and VoLTE and VoWIFI both work fine, with Oneplus Nord 2 only VoWiFI is working.
Any suggestion?
Up.
Up.
No solution for now, we need to wait for oneplus to add the missing 5g/volte profiles in a next OTA... it could take a while or simply never arrive .
What commands should be entered instead of these to
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
everything as it was? I think the reason they lost wifi and bluetooth. They don't turn on at all...
A.15 update finally did it, since this morning I have 5G and VolTE working on my phone on swiss networks!
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Hi master, greetings from Chile. Sorry for my ignorance. I don't understand step 2. Would you please explain to me. I'm a dumb. Sorry
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Has there been any recent updates that could have broken step 3? Tested on both Windows and Linux but whenever it reboots into recovery mode, ADB never reconnects. Is there something else I'm missing?
McGinsky said:
Has there been any recent updates that could have broken step 3? Tested on both Windows and Linux but whenever it reboots into recovery mode, ADB never reconnects. Is there something else I'm missing?
Click to expand...
Click to collapse
Since A14 or A15 update, ADB is not available in recovery mode...
Related
Dear all
I try use miui and custom ROM, I used Cardinal ROM now, I tried to enable RNDIS + DM + Modem USB mode, but I failed many times,
I got the help from https://forum.xda-developers.com/lg-g2/help/tried-unlocking-basebands-guide-t3180317
and used those command just enable the diagnosis mode.
$adb shell
#su
#setprop sys.usb.config diag,adb
so can some one give me some suggestion or which ROM to enable RNDIS + DM + Modem USB mode in some rom?
this made me crazy. thanks to every one frist!!!
Try
setprop persist.sys.usb.config diag,adb
LiQuiD_FeAR said:
Try
setprop persist.sys.usb.config diag,adb
Click to expand...
Click to collapse
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
mido:/ $ su
su
mido:/ # setprop persist.sys.usb.config diag,adb
setprop persist.sys.usb.config diag,adb
mido:/ #
I try that, that just shown like this, I think this ROM can't use this command.
this one just enable diag mode:
mido:/ # setprop sys.usb.config diag,adb
setprop sys.usb.config diag,adb
I found I can use these ADB commands to turn on and of the WiFi of a rooted phone:
Code:
adb shell su -c 'svc wifi enable'
adb shell su -c 'svc wifi disable'
However, I'm interested in doing it without having to root the phone for an automatic testing I'm doing. Do you guys know if this is possible?
I found this project which allows me to connect to a WiFi through ADB commands not being a root user. I was wondering if anyone knows how to disconnect also from ADB and not being a root user.
UPDATE:
I've been recently trying:
Code:
C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb server is out of date. killing...
* daemon started successfully *
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
and
Code:
C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
I also found doing this type of command:
Code:
adb shell input keyevent 20 & adb shell input keyevent 23
I can navigate and click. The problem seems to be that I always finish in a different state so the next time I input the command
Code:
adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
I start in a different place and start clicking elsewhere. I've tried returning home, but that doesn't fix the issue. Is there any way to start always from the same point inside the WiFi settings?
Thanks!
natiya said:
I found I can use these ADB commands to turn on and of the WiFi of a rooted phone:
Code:
adb shell su -c 'svc wifi enable'
adb shell su -c 'svc wifi disable'
However, I'm interested in doing it without having to root the phone for an automatic testing I'm doing. Do you guys know if this is possible?
Click to expand...
Click to collapse
Turn WiFi off
Code:
adb shell settings put global airplane_mode_on 1
adb shell settings put global wifi_on 0
adb shell settings put global wifi_scan_always_enabled 0
Afterwards you've to re-boot the device.
Turn WiFi on
Code:
adb shell settings put global airplane_mode 0
adb shell settings put global wifi_on 1
adb shell settings put global wifi_scan_always_enabled 1
jwoegerbauer said:
Turn WiFi off
Code:
adb shell settings put global airplane_mode_on 1
adb shell settings put global wifi_on 0
adb shell settings put global wifi_scan_always_enabled 0
Afterwards you've to re-boot the device.
Turn WiFi on
Code:
adb shell settings put global airplane_mode 0
adb shell settings put global wifi_on 1
adb shell settings put global wifi_scan_always_enabled 1
Click to expand...
Click to collapse
Thank you, but those don't produce any change on my device. Actually, if I put the first two commands without doing "adb kill-server" in between, I get this message:
error: more than one device/emulator
Click to expand...
Click to collapse
But the output when they work is:
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
and nothing happens.
I've been recently trying:
Code:
C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb server is out of date. killing...
* daemon started successfully *
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
and
Code:
C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
This opens the screen where you can turn on and off the WiFi but it doesn't do it...not sure if I'm missing something!
Just to be shure, make shure your using the latest version of ADB offered by google here:
https://developer.android.com/studio/releases/platform-tools
You could use adb wifi
After activating when using usb it and connecting through the same wifi:
svc wifi enable
works without root
I'm a little late to this thread, but if it still helps the OP, non-rooted Android 10 and below allowed wireless adb connections AFTER a USB connection was first established (adb start-server && adb tcpip 5555 && adb connect [IP]:5555), but that changed (for the better) in Android 11 and above with the new new Developer options Wireless debugging random port assignments (adb connect [IP]:[PORT] or adb pair [IP]:[PORT] [PIN]) such that the adb wireless connection never needs USB cable ever again.
Given Android 11 allows Developer options Wireless debugging via a random port, and Android 12 new Developer options Wireless debugging allows that to be accessed even easier with a new Developer options Wireless debugging tile, the only thing missing is a way to turn the non-rooted Android Wi-Fi on or off via adb (which was the OP's original question after all).
Maybe this will work if we can figure out how to tap the buttons?
adb shell "am start -a android.settings.WIFI_SETTINGS"
Click to expand...
Click to collapse
For swiping on the phone from adb this works...
C:\> adb shell input swipe 500 1000 500 100
This will instantly swipe from center to the top of the screen.
You can add a time period, e.g., take 3 seconds to swipe that.
C:\> adb shell input swipe 500 1000 500 100 3000
Click to expand...
Click to collapse
But you want to tap the buttons, right?
If we can figure out the positions, maybe this would work?
C:\> adb shell am start -n com.google.android.gms/.ads.settings.AdsSettingsActivity
That should pop up an Android "Reset Advertising ID" settings page.
C:\> adb shell input tap 500 400
If run after the command above, that will tap the button to
asking to "Opt out of Ads Personalization" in that Activity
if that button is like mine, at the X=500 & Y=400 location.
On my phone, this is the "Reset advertising ID" button location:
adb shell input tap 500 200
On my phone, this is the "OK" button on that GUI above.
adb shell input tap 700 1000
C:\> adb shell am force-stop com.google.android.gms
If run after bringing up the advertising-id reset Activity,
it will close the activity without doing anything else.
Click to expand...
Click to collapse
Here is a somewhat related post...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Type adb tcpip 5555 in the command line or Terminal and press Enter.
Find your phone's IP address in Settings > About Phone > Status > IP Address.
Back in the command line or Terminal, type adb connect [your Android's IP address].
Finally, press Enter again.
Regards,
J Wick
Hi,
I read some information from users who do not have 5G available and Volte on calls.
Is this a problem that phone operators can fix or will a OnePlus fix be needed?
Thanks
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Pouic said:
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Click to expand...
Click to collapse
Any idea when it is going to happen?
Pouic said:
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Click to expand...
Click to collapse
Is there a way to fix this now?
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
I have volte calls enabled by default but still doesnt work. Probably you also need support from your carrier and one plus will never exist for my carrier.
Hey,
whenever I issue a reboot command via adb to a device that is connected via network / tcp, adb freezes (I guess because it waits for the response to the command that never arrives because the device is offline). Regardless if I use "adb reboot" or "adb shell reboot" ... I tried delaying the reboot with sleep and spawning it separately with & but nothing worked...
Code:
adb shell "sleep 5 &"
adb shell "(sleep 5) &"
adb shell "(sleep 5 &)"
It always waits until execution finished...
Any ideas?
If you invoke the SLEEP command it gets processed - even if forced to get processed in background.
FYI: Running a command in background simply means a user-interaction isn't possible.
jwoegerbauer said:
If you invoke the SLEEP command it gets processed - even if forced to get processed in background.
FYI: Running a command in background simply means a user-interaction isn't possible.
Click to expand...
Click to collapse
Yeah, but when I execute "sleep 5" within the shell, I cannot do anything until sleep finished. When I execute "sleep 5 &" within the sell, I can immediately enter the next command.
Same is NOT true with adb shell. Both "adb shell sleep 5" and "adb shell sleep 5 &" wait until sleep finish.
Of course I want "sleep" to execute in background. I want to execute "sleep 5 && reboot &" so adb has time to read the response and I can execute "adb disconnect" on the host before the device reboots.
Each
Code:
adb [-d|-e|-s <serialNumber>] shell "<shell_command>"
invokes a separate ( new ) terminal session and waits for this session has finished
To get around this open a remote shell, means invoke a terminal session only once and execute the commands desired
Code:
adb [-d|-e|-s <serialNumber>] shell
<shell_command>
exit
I'm sorry but I don't understand what u mean by that :/
I want to run this on my host:
Code:
adb command_that_will_reboot_connected_device_in_5_sec_without_blocking
adb disconnect
...
Any solutions for that?
If BusyBox is installed on device's Android, and if BusyBox has commands crond & crontab & reboot implemented, then you can create on Android a scheduled task to reboot Android by means of crontab
Example ( untested ) what re-boots Android in 1 minute:
Code:
adb shell
mkdir -p '/data/local/tmp/cron'
echo */1 * * * * reboot > /data/local/tmp/cron/crontab
busybox crond -c /data/local/tmp/cron
busybox crontab -c '/data/local/tmp/cron/' '/data/local/tmp/cron/crontab'
exit
Well, that sounds pretty overkill...
Found a solution... I moved the problem to the host by spawning the "hanging" adb process seperately (using windows in this case):
Code:
start adb reboot
timeout /t 3
adb disconnect
...
My phone is SONY Xperia XZ1 G8341, I installed LineageOS 17.1 yesterday, I installed sony-diag module on Magisk and QPST, QPST Drivers on PC, I opening adb shell and writing
su
setprop persist.usb.eng 1
but doesn't working, I tried again adb shell
su
setprop sys.usb.config diag,adb
doesn't working again, i can't see my phone in device manager -> other devices
when I see, I will install mi5 qualcomm drivers for qualcomm android modem 9018 and I will see on QPST
but doesn't working...
I tried like this
Can anyone help me?