Slackware mount MTP as a non-root user

gonny95 · 02-19-2014, 10:05 PM

Code:

Failed to mount "SHV-E210L"
Unable to open MTP device '[usb:001,019]'

These messages appear when I try to mount MTP as a non-root user
Other USB devices or hard disks that are not MTP can be mounted with no problems by any user
How can I mount this without logging into root?

gonny95 · 02-20-2014, 05:58 PM

I'm really desperate... I would really appreciate if you help me...

frankbell · 02-20-2014, 06:42 PM

Posting to your own thread (or "bumping" as it is sometimes called) is not a good idea at LQ. LQ automatically "bumps" zero reply threads, and posting to it takes it out of the zero-reply list, where persons who might be able to help might miss seeing it.

You might take a look at installing mtpfs: http://slackbuilds.org/repository/13...timedia/mtpfs/ I've never had to use it, but that's what I would try.

If you've already done that, please post the output of these two commands, being sure to surround it with "code" tags, which become available when you click the "Go Advanced" button to the right of the "Post Quick Reply" button at the bottom of the reply window.

Code:

cat /etc/fstab
cat /etc/mtab    <---------with the device unmounted and with it mounted

gonny95 · 02-20-2014, 07:01 PM

Thanks for your replying
I did as you said

Code:

cat /etc/fstab
cat /etc/mtab    <---------with the device unmounted and with it mounted

The results are

Code:

bash-4.2# cat /etc/fstab
/dev/sdc5        swap             swap        defaults         0   0
/dev/sdc2        /                ext4        defaults         1   1
#/dev/cdrom      /mnt/cdrom       auto        defaults 0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0

/dev/sda5        /.1C             ntfs        rw,noauto,user,umask=000   1   0
/dev/sdb1        /.2D             ntfs        rw,noauto,user,umask=000   1   0

Code:

bash-4.2# cat /etc/mtab
/dev/sdc2 / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
gvfsd-fuse /home/guest/.gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=guest 0 0

Well it's first time I've ever seen /etc/mtab
I didn't know that file even exist
What's the difference between /etc/fstab/ and /etc/mtab?

And I installed mtpfs but seems that some errors happened

Code:

bash-4.2# mtpfs
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 6
Attempting to connect device

For your information, the following error was happend when I tried to mount MTP device in Thunar as a non-root user

Code:

Failed to mount "SHV-E210L"
Unable to open MTP device '[usb:001,019]'

frankbell · 02-20-2014, 07:09 PM

Fstab is the File System Table. It lists the partitions that the computer is aware of. Before automount came along, the easiest way to mount a new partition repeatedly was to enter it in fstab.

Mtab is the Mount table; it shows what partitions are actually mounted.

Here's a good article: http://www.linuxchix.org/content/cou...m/Lesson5.html

What is the precise device you are attempting to mount? I think that information would help a lot.

gonny95 · 02-20-2014, 07:13 PM

I'm using 32-bit Slackware 14.1

And my phone is Galaxy S3 4.3 JellyBean

frankbell · 02-20-2014, 08:01 PM

I have an HTC One running Android 4.3, and I haven't been able to get it to mount.

My workaround was to install the ES File Explorer app, free in the Play Store, which is capable of browsing network shares. Since I installed that, I've stopped exploring ways to mount the device, because I could accomplish my larger purpose--to copy files to and from my phone.

Googling around, I find that it appears that mounting Android 4.3 devices to Linux is not as easy as (I think) it should be.

In other words, I gave up, because I have other brick walls to pound my head against.

Maybe someone who has succeeded will stumble over this thread and help both of us out.

gonny95 · 02-21-2014, 05:55 AM

Thanks but I gotta solve this problem completely.

Looks like something's wrong with 'libusb_open()'

It happens only when I logged-on as a non-root

Code:

bash-4.2$ mtpfs /PHONE
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 2, dev 4
Attempting to connect device
libusb_open() failed!: Permission denied
LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0

That had nothing to do with the permission of the mount point directory

gonny95 · 02-21-2014, 06:24 AM

Quote:

Originally Posted by gonny95

Thanks but I gotta solve this problem completely.

Looks like something's wrong with 'libusb_open()'

It happens only when I logged-on as a non-root

Code:

bash-4.2$ mtpfs /PHONE
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 2, dev 4
Attempting to connect device
libusb_open() failed!: Permission denied
LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0

That had nothing to do with the permission of the mount point directory

Guess I found the cause
that's because I didn't specify /etc/udev/rules.d/51-android.rules

So I made /etc/udev/rules.d/51-android.rules

and specified as following:
(I don't know exactly what is udevrules,though...)

Code:

SUBSYSTEM=="usb",

ATTR{idVendor}=="04e8",

ATTR{idProduct}=="6860", MODE="0666"

Then it works partially

When I tried to mount through Thunar It was mounted very well

But When I used mtpfs command, it just freezes... very weird

frankbell · 02-21-2014, 07:17 PM

Cool. I'll have to try this out, but I probably won't get to it until next week.

Regnad Kcin · 04-20-2014, 01:55 AM

the MTP mount thing is a real P.I.A.

The android rules setting fixed it.

How did you find this out?

ckuttruff · 08-02-2014, 01:48 PM

It looks like arch linux has some excellent info about android-related issues (and this is where I'm assuming that these udev rules came from):
https://wiki.archlinux.org/index.php/android

To find the vendor / product IDs:
https://wiki.archlinux.org/index.php...our_Device_Ids

When adding the rules file, reloading the udev rules (as specified in the aforementioned arch documentation), and then running mtpfs, I can confirm that things show up perfectly fine now in my file manager.

Thanks Arch folks!! <3