The process for the mtp protocol died unexpectedly

keefaz · 12-16-2017, 04:48 AM

Quote:

Originally Posted by mfoley

I'll probably continue to explore gmgf's suggestion for getting a current version of libmtp. keefaz's suggestion about Thunar is also something to try. I've used Thundar on Ubuntu/Cinnamon and it was my favorite file manager, but apparently it's not an available package for Slackware or Slackbuilds.

Yes Thunar is available on Slackware, it's Thunar package (please note the first letter is uppercase in package name). No need for slackbuild as it is in official release

mfoley · 12-16-2017, 12:34 PM

Quote:

Originally Posted by keefaz

Yes Thunar is available on Slackware, it's Thunar package (please note the first letter is uppercase in package name). No need for slackbuild as it is in official release

You're right! I'm going to download that now.

bassmadrigal: the adb worked great yesterday. I downloaded about 4.5G of photos from my Android. However, today I downloaded android-tools on a different system and went to get some other files and got:

Code:

# adb pull "/mnt/sdcard/viber/media/Viber Images/"
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
adb: error: connect failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

Apparently, there was an update to the SlackBuilds repository from adb 1.0.36 to adb 1.0.39. So, I went back to the other system and ran the 1.0.36 version and got:

Code:

# adb pull "/mnt/sdcard/viber/media/Viber Images/"
adb: error: connect failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I did run 'adb kill-server', but still go the same "This adb server's $ADB_VENDOR_KEYS is not set". Any idea what's up?

Later:

OK, found the answer here: http://www.tomshardware.com/answers/...ndor-keys.html. I had to "Revoke USB debugging authorizations", then unplug and replug the USB from phone to Computer. Sheesh! This adb stuff is not for the faint-of-heart!

bassmadrigal · 12-16-2017, 02:22 PM

Quote:

Originally Posted by mfoley

OK, found the answer here: http://www.tomshardware.com/answers/...ndor-keys.html. I had to "Revoke USB debugging authorizations", then unplug and replug the USB from phone to Computer. Sheesh! This adb stuff is not for the faint-of-heart!

Glad you found the answer! And you're right, adb is not for the faint of heart. It stands for Android Debug Bridge, so it isn't really designed for normal users to use it. I've just had a lot of experience with it over the years due to enjoying rooting and installing 3rd-party ROMs on my Android devices. But, I'm pretty sure I'm barely scraping the surface on what adb is capable of doing.

DJOtaku · 06-19-2018, 06:14 PM

Quote:

Originally Posted by Diantre

Have you set up udev rules for your devices? Most of the time this type of problems happen because the user doesn't have the correct permissions to access the device.

Add the user to the plugdev group, and set up rules for each device you want to connect. Make sure MTP is enabled on the device (USB for file transfer, or something to that effect). As an example, these are the rules I use for my devices:

/etc/udev/rules.d/51-android.rules

Code:

# MSI tablet
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", OWNER="root", GROUP="plugdev"
# Sony
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0664", OWNER="root", GROUP="plugdev"
# Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0664", OWNER="root", GROUP="plugdev"
# Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0664", OWNER="root", GROUP="plugdev"
# HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0664", OWNER="root", GROUP="plugdev"
# LGE
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0664", OWNER="root", GROUP="plugdev"

With only this setup I'm able to use dolphin, thunar, pcmanfm and jmtpfs to browse the files on my phone. YMMV.

I came to tell you THANK YOU SO MUCH FOR THIS! I've been dealing with this issue for months and months now and just happened across this post by random after my months of googling. Thanks!