[WFX] Android ADB 8.8

[AntonyD]

Yes, there is a problem, but for an example it would be better and easier to show a folder with the WhatsApp database -
all the subfolders are in English and it's immediately clear what is being transferred incorrectly and where.
And in your photo, we still have to think very hard and try to understand what it's about...

[Mapaler]

Yes, there is a problem, but for an example it would be better and easier to show a folder with the WhatsApp database -
all the subfolders are in English and it's immediately clear what is being transferred incorrectly and where.
And in your photo, we still have to think very hard and try to understand what it's about...

I use FTP connection for comparison:
Image: https://i.ibb.co/Tp5X0D8/3160-TOTALCMD64-Total-Commander-x64-11-56-User.png
Image: https://i.ibb.co/Z1hJC4FZ/3161-TOTALCMD64-Total-Commander-x64-11-56-User.png
Image: https://i.ibb.co/Vch8WTzQ/3159-TOTALCMD64-Total-Commander-x64-11-56-User.png

ADB outputs spaces as " ", which Windows interprets as a folder path separator, thus leading to the wrong path.

The output results differ depending on the way the commands are used.
Image: https://i.ibb.co/wh9Sq2t2/3162-Windows-Terminal-Windows-Power-Shell.png

[AntonyD]

jakub [at} icewarp {dot] com
this is the real address of the plug-developer - there he will read and respond faster and more productively,
and here we will probably never get the proper reaction. Therefore, I suggest "calling" via email and put
the link to this topic in a email...
This is a definitely problem on the plugin side, when it incorrectly passes strings to Total.

The file manager is clearly expected to provide straightforward lines describing paths/file/folder names
in strict accordance with Windows requirements. Despite the fact that it works with objects from a different OS/FS.
However, the plugin is designed to act as a necessary layer between these different environments, ensuring native
and seamless interaction. Unfortunately, it does not perform as well as we would like.

[JPCoetzee]

The requirements say that a rooted device + Wifi ADB is needed. Is this still necessary in 2025?
Can this plugin be made to work on a non-rooted phone via Wireless Debugging?
many thanks

[JPCoetzee]

The requirements say that a rooted device + Wifi ADB is needed. Is this still necessary in 2025?
Can this plugin be made to work on a non-rooted phone via Wireless Debugging?

Answering my own question: yes it is possible.

Once I had added the plugin (Configuration → Options → Plugins) I opened the "Network" pseudo-folder to see new icon labeled "ADB". I clicked "Connect to device" and entered the Wireless Debugging PHONE_IP:PORT enabled on the phone (for example 192.168.1.50:36735).

However TC freezes and nothing is returned **UNLESS** I first start a different ADB app on my laptop - in my case ADB Explorer. Then the TC ADB plugin can read and write my phone. I guess ADB Explorer starts a daemon using a more compatible version of ADB.EXE, which is then used by the TC plugin..? So yes it is possible to use this on an unrooted phone using Wireless Debugging, but with some difficulty.

Updating these three ADB files in the plugin directory fixed the problem above - adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll
Latest version can be found here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

So yes it IS possible to use this plugin on a non-rooted phone via Wireless Debugging.

[BudCord]

I clicked "Connect to device" and entered the Wireless Debugging PHONE_IP:PORT enabled on the phone (for example 192.168.1.50:36735).

Where can I find the port number I need to access the Fon via Wireless Debugging?

[JPCoetzee]

Where can I find the port number I need to access the Fon via Wireless Debugging?

I'm assuming you know how to make yourself a developer on an Android phone. You can do that without root. Once you're a developer you can enable USB debugging and Wireless debugging.

On the Wireless debugging settings page you will find the IP address & Port of the phone. The settings page typically looks like this: https://commonsware.com/R/pages/OtherChanges-04.png

Note that in my Xiaomi phone the port changes every time Wireless debugging is enabled.

To make this much quicker you can create a Quick Settings Developer tile to access the Wireless debugging menu from the top of the phone with one swipe. The settings for that are also under Developer Options.

[BudCord]

Thanks for pointing me in the right direction!

My current phone is the first one since 2012 that doesn't have root access.
With root, I always had a fixed port thanks to the ‘WiFi ADB - Debug Over Air’ app (by MetaCtrl).

The constantly changing port makes access via wireless debugging uninteresting, especially since I can exchange data at 4x speed with a Thunderbolt 4 cable.

[beb]

2JPCoetzee

My experience:
Google Pixel 9 Pro @ Android 16 (No root) vs TC 64-bit @ Windows 10
Phone - Settings - System - Developer options - Wireless debugging > ON >
Device name: Pixel
IP address & port: 192.168.1.123:12345

Way 1 (failed):
Phone: ... Wireless debugging > ON > IP address & port: 192.168.1.123:12345
PC: Using ADB plugin at a glance:
step 1 (TC): \\\ADB\Connect To Device
step 2 (enter upon request): 192.168.1.123:12345
step 3: waiting...
result: nothing happens

Way 2 (failed):
Phone: ... Wireless debugging > ON > Pair device with pairing code >
WiFi pairing code: 123456
IP address & port: 192.168.1.123:12345
PC: Using ADB plugin at a glance:
step 1 (TC) \\\ADB\Connect To Device
step 2 (enter upon request): 192.168.1.123:12345
step 3: waiting...
result:
PC: nothing happens
Phone: reports "Pairing unsuccessful..."

Way 3 (failed, incomplete):
Phone: ... Wireless debugging > ON > IP address & port: 192.168.1.123:12345
PC: running adb.exe in the Window mode (Sift+Enter on adb.exe)
step 1 (enter command): $TC\Plugins\wfx\ADB\bin>adb pair 192.168.1.123:12345
step 2 (get the request): Enter pairing code:
result: since no pairing code for this way, am better going to way 4.

Way 4 (succeed):
Phone: ... Wireless debugging > ON > Pair device with pairing code >
WiFi pairing code: 123456
IP address & port: 192.168.1.123:12345
PC: running adb.exe in the Window mode (Sift+Enter on adb.exe)
step 1 (enter command): $TC\Plugins\wfx\ADB\bin>adb pair 192.168.1.123:12345
step 2 (get the request): Enter pairing code:
step 3 (enter pairing code): Enter pairing code: 123456
stet 4 (get a message): Successfully paired to 192.168.1.123:12345 [guid=adb-xyz...bla-bla-bla]
Now we are ready to proceed with ADB plugin
step 5 (TC, enter the plugin): \\\ADB\
As soon as step 5 is done, we can see "adb-xyz...bla-bla-bla" entry there
step 6 (TC, enter the entry): \\\ADB\adb-xyz...bla-bla-bla
setp 7 = result = we've got access to the phone.

Conclusion:
- my phone requires at least the "Pair device with pairing code" mode for the "Wireless debugging", which apparently the ADB plugin cannot process.
- however, upon running adb.exe at first, using "adb pair IP:PORT*" and entering "Enter pairing code: PRCODE*", we are getting (if the command succeed) some "guid=adb-xyz...bla-bla-bla", and then the phone becomes available in "\\\ADB\" plugin via said "adb-xyz...bla-bla-bla" guid entry.

* "IP:PORT", and "PRCODE" are obtained via the "Phone: Settings - System - Developer options - Wireless debugging > ON > Pair device with pairing code >" menu.

[JPCoetzee]

My experience:
Google Pixel 9 Pro @ Android 16 (No root) vs TC 64-bit @ Windows 10
...

Did you also do this? →

Updating these three ADB files in the plugin directory fixed the problem above - adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll
Latest version can be found here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

This fixed everything for me, now I don't have to start adb manually (using ADB Explorer in my case, Way 4 in your case).

[B. Radji]

Hello!
Is it possible to create ZIP files and make them save directly in PC's internal storage... using this plugin?

It is working fine for me via ADB usb after installing SDK platforms, but the folders I'm trying to copy are too big with too many small size photos (+6000 file)... At the beginning it copies with fast speed but after a while it starts getting very critical and slow, speed becomes extremely instable, so that's why I'm asking if Total Commander can create ZIP file from phone storage and save them to PC's storage.

Sorry for my bad english, and I'm new here.
Thanks everyone.

[Mapaler]

Hello!
Is it possible to create ZIP files and make them save directly in PC's internal storage... using this plugin?

It is working fine for me via ADB usb after installing SDK platforms, but the folders I'm trying to copy are too big with too many small size photos (+6000 file)... At the beginning it copies with fast speed but after a while it starts getting very critical and slow, speed becomes extremely instable, so that's why I'm asking if Total Commander can create ZIP file from phone storage and save them to PC's storage.

Sorry for my bad english, and I'm new here.
Thanks everyone.

adb can use the shell, but it requires a zip command that supports shell, and you need to generate the package on your phone before you can achieve the subsequent steps. Rather than doing this, you might as well manage it directly using FTP service software in a Wi-Fi environment.


I recommend MixPlorer
https://xdaforums.com/t/app-2-2-mixplorer-v6-x-released-fully-featured-file-manager.1523691/

[dziubek]

Hi,
Just to let you know, the author has updated the plugin’s binary files, as mentioned in the discussion, which has resolved the reported issues.

8.11
- New DebugLogDir ini setting
- Latest Windows adb binaries

8.10
- Screenshot uses native Android instead of framebuffer

8.9
- Linux - Dialogs removed, ini file comments and examples
- Linux - Custom columns, owner and string attributes

8.8
- Native ls - --full-time support (with TZ)
- Native ls - append indicator removed (only used for busybox ls)

[WindR]

The application successfully connects via ADB and reads root directories using su -c, but fails immediately when attempting to write/delete files within those directories due to inconsistent privilege escalation (permission denied).

2026-05-17 07:16:39 [1AE0] ADB Read Data (1097): ... ls: total 4212 ... (SUCCESS with su)
2026-05-17 07:16:42 [1AE0] ADB Write (63): shell:rm "/data/adb/HMA/..."
2026-05-17 07:16:42 [1AE0] ADB Read Data (76): rm: /data/adb/HMA/...: Permission denied

The tool attempts to use busybox for file operations when standard commands fail, but BusyBox is not present on the device. The tool does not appear to fall back gracefully.

2026-05-17 07:16:42 [1AE0] ADB Write (74): shell:busybox rm -f "/data/adb/HMA/..."
2026-05-17 07:16:42 [1AE0] ADB Read Data (51): /system/bin/sh: busybox: inaccessible or not found

Additionally, the installation of the internal adbhelper.apk fails because the bundled APK targets an obsolete SDK version compared to current Android security requirements.

2026-05-17 07:26:27 [2844] ADB Read Data (111): Failure [INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 24, but found 17]