device busy error when running mvt-android check-adb while adb is NOT running in the background

[joeraven01]

I am having issues with an old issue that was already brought up here ( issue #8) and now is closed. It seemed that the issue was triggered by an adb process in the background; unfortunately that is not my case. I used the task manager on the Windows side and "ps aux" on the linux side to ensure that was not the case.

I installed Ubuntu 22.04.1 LTS WSL
Installed usbipd on Windows in order to attach USB devices and added a firewall rule that enables incoming TCP traffic on port 3240.
I set my Pixel to Developer options, USB debugging enabled and set to file transfer

For attaching my Pixel to Ubuntu I run on a Powershell:

+++++++++++++++++
PS C:\Windows\System32> usbipd wsl list
BUSID VID:PID DEVICE STATE
4-2 03f0:522a USB Printing Support, HP LEDM, HP Printer (BIDI), IPP Pri... Not attached
4-4 18d1:4ee2 Pixel 4a, ADB Interface Not attached

PS C:\Windows\System32> usbipd wsl attach --busid 4-4
PS C:\Windows\System32> usbipd wsl list
BUSID VID:PID DEVICE STATE
4-2 03f0:522a USB Printing Support, HP LEDM, HP Printer (BIDI), IPP Pri... Not attached
4-4 18d1:4ee2 Pixel 4a, ADB Interface Attached - Ubuntu
+++++++++++++++++

Then on Ubuntu:
++++++++++++++++++++
joe@DESKTOP-I1KEL90:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

joe@DESKTOP-I1KEL90:~$ ps aux | grep adb
joe 798 0.0 0.0 4020 1988 pts/0 S+ 20:58 0:00 grep --color=auto adb

joe@DESKTOP$ export PATH=$PATH:~/.local/bin
joe@DESKTOP$ mvt-android check-adb --output /path/to/results

    MVT - Mobile Verification Toolkit
            https://mvt.re
            Version: 2.2.1
            Indicators updates checked recently, next automatic check in 8 hours

20:59:47 INFO [mvt.android.cmd_check_adb] Parsing STIX2 indicators file at path
/home/joe/.local/share/mvt/indicators/raw.githubusercontent.com_AssoEchap_stalkerware-indicators_mast
er_generated_stalkerware.stix2
20:59:48 INFO [mvt.android.cmd_check_adb] Extracted 753 indicators for collection with name "TheTruthSpy"
INFO [mvt.android.cmd_check_adb] Extracted 178 indicators for collection with name "HelloSpy"

MORE INFO STUFF

     CRITICAL [mvt.android.modules.adb.chrome_history] Device is busy, maybe run `adb kill-server` and try again.

joe@DESKTOP$ adb kill-server
cannot connect to daemon at tcp:5037: Connection refused
joe@DESKTOP-I1KEL90:~$
++++++++++++++++
I would run the mvt-android command after running the adb kill-server and no change either.
I also tried Pixel developer option: disable adb authorization timeout
without success.
I also notice that in base.py the exception handles two conditions, one a USB access error and the other a USB busy error, but it gets log as a busy error perhaps lumping the condition of timeout for being busy.

Would this be an adb signing issue?
It seems like I ran pretty much out of options here.

[joeraven01]

I tried something different. I made sure ssh server is running on both ends, host machine(wsl) and guest (Ubuntu). The android phone attaches fine on the host machine. When running mvt-android, it is not able to see the device on the host machine.

+++++++++++
CRITICAL [mvt.android.modules.adb.chrome_history] No device found. Make sure it is connected and unlocked.
joe@DESKTOP-I1KEL90:~$ adb devices -l
List of devices attached
15021JEC202607 device product:sunfish model:Pixel_4a device:sunfish transport_id:1
++++++++++++

adb is able to list the device because I have the ADB_SERVER_SOCKET environment variable setup on the guest side.

Is there a way to run mvt-android check-adb so that it can see my device attached?

[joeraven01]

I found the solution. By connecting the phone over Wifi I was able to talk to the phone.