[Moto Z3 Play Questions & Answers] vindicatorr:
After personalizing my Z3 Play, I put in my SD card and went to transfer my media back to it.

When I changed the USB mode to File Transfer, I got no usual notification in KDE.

Watching the linux log, I saw:

Oct 05 21:24:46 computername kernel: usb 2-4: new high-speed USB device number 33 using xhci_hcd
Oct 05 21:24:46 computername kernel: usb 2-4: New USB device found, idVendor=05c6, idProduct=9092, bcdDevice= 4.04
Oct 05 21:24:46 computername kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 05 21:24:46 computername kernel: usb 2-4: Product: Moto Z3 Play
Oct 05 21:24:46 computername kernel: usb 2-4: Manufacturer: motorola
Oct 05 21:24:46 computername kernel: usb 2-4: SerialNumber: <sanitized>
Oct 05 21:24:46 computername mtp-probe[1845138]: checking bus 2, device 33: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4"
Oct 05 21:24:46 computername mtp-probe[1845138]: bus: 2, device: 33 was not an MTP device
Oct 05 21:24:46 computername mtp-probe[1845152]: checking bus 2, device 33: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4"
Oct 05 21:24:46 computername mtp-probe[1845152]: bus: 2, device: 33 was not an MTP device

And that would be the same similar response to selecting PTP or MIDI (which gives some pulseaudio log stuff).

If I select "USB tethering", it DOES come up with a notification, but it's more like a false-positive.

There is no mention of the mtp-probe, but rather:

Oct 05 21:31:12 computername kernel: rndis_host 2-4:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-4, RNDIS device, <sanitized>

and other related stuff.

There was mention of "kf5.kiod.kmtpd: LIBMTP_Open_Raw_Device_Uncached: Could not open MTP device".

This is all after I did a factory reset.

I'll also state that I did unlock the bootloader and sideload Magisk via "fastboot boot" for TWRP.

I've seen topics about this suggesting things like fiddling with the ADB setting in Developer mode, but nothing I've read has resulted in any change.

I was really hoping maybe I messed up with changing permissions, but figured the factory reset would put everything back in place. Nope.

Also, I have no idea if the file transfer mode EVER worked on this device, since I only tried it now after upgrading to pie and patching the boot image with Magisk.

Is anyone with this device able to use the File Transfer mode, and if so, did you also modify things like patching boot with Magisk?

I wouldn't think the two would be related.

EDIT0:

I thought I might add the following as well since it is different, but also maybe not related

05c6:9092 Qualcomm, Inc. Moto Z3 Play

That is what it is now after patching the boot image with Magisk.

The VID used to be 22b8 and I think the PID maybe something like 2e81.

I set the rules in /etc/udev for like 6 different combinations I had seen through my various tests.

EDIT1:

Hmm, looks like the Magisk/VID could very well have been the issue.

I changed to slot b (instead of a), booted that up and right away no problems with File Transfer.

I'll have to look at it more closely. I may just see what happens if I flash the stock boot image back to slot a.

EDIT2:

So the takeaway for anyone else, don't try to be adventurous and deviate from https://topjohnwu.github.io/Magisk/install.html

I had originally sideloaded magisk and I guess somewhere in all of that, things went a little (not completely) awry.

The VID:PID are back to normal and MTP is working right, AND I have magisk installed the way I was originally supposed to.