Results 1 to 3 of 3
  1. #1

    Question problem mounting Android phone as filesystem on Debian laptop via USB

    summary: When I connect my Android version=4.4.2 phone to my Debian laptop, the laptop detects the phone via both `nautilus` and `jmtpfs -l`. However my attempt to mount the phone's storage with `jmtpfs` fails with
    Code:
    -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
    details:

    I have a Debian laptop with

    Code:
    $ cat /etc/debian_version
    jessie/sid
    $ uname -rv
    3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13)
    $ gcc --version | head -n 1
    gcc (Debian 4.8.2-1) 4.8.2
    $ aptitude versions --disable-columns mtp | grep -e '^Package\|^i' | grep -vie 'dovecot\|mtpaint\|smtp'
    Package gmtp:
    Package gmtp:i386:
    Package jmtpfs:
    i  0.5-2  100
    Package kio-mtp:
    Package kio-mtp-dbg:
    Package kio-mtp-dbg:i386:
    Package kio-mtp:i386:
    Package libmtp-common:
    i  1.1.8-1  100
    Package libmtp-dbg:
    Package libmtp-dbg:i386:
    Package libmtp-dev:
    Package libmtp-dev:i386:
    Package libmtp-doc:
    i  1.1.8-1  100
    Package libmtp-runtime:
    i  1.1.8-1+b1  100
    Package libmtp-runtime:i386:
    Package libmtp9:
    i  1.1.8-1+b1  100
    Package libmtp9:i386:
    i  1.01-3 testing 500
    Package mtp-tools:
    i  1.1.6-20-g1b9f164-1 testing 500
    Package mtp-tools:i386:
    Package python-pymtp:
    Package uucp-lmtp:
    I also have a (working) Motorola Moto G running Android version=4.4.2. With no MTP devices connected to the Debian box, I see

    Code:
    $ date ; jmtpfs -l
    Sun Apr  5 20:08:46 EDT 2015
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.
    Available devices (busLocation, devNum, productId, vendorId, product, vendor):
    I then connected the MotoG to the laptop with a USB cable. A `nautilus` window opened showing the (browsable) contents of location='mtp://[usb:001,040]/' with device name='XT1028'. I can also see

    Code:
    $ date ; jmtpfs -l
    Sun Apr  5 20:09:06 EDT 2015
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.
    Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
    Available devices (busLocation, devNum, productId, vendorId, product, vendor):
    1, 41, 0x2e82, 0x22b8, Moto G (ID2), Motorola
    However, I am unable to mount the device with

    Code:
    $ mkdir -p ~/Android_transfer/
    $ sudo jmtpfs ~/Android_transfer/
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.
    Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
    ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
    LIBMTP libusb: Attempt to reset device
    Android device detected, assigning default bug flags
    $ ls -al ~/Android_transfer/
    ls: cannot access /home/me/Android_transfer/: Permission denied
    $ sudo fusermount -u /home/me/Android_transfer
    Should I use something other than `jmtpfs` to mount the MotoG's storage? If so, what do you advise?

    If not, how to fix or further debug?
    Last edited by TomRoche; 04-05-2015 at 09:57 PM. Reason: solved

  2. #2

    solved: don't use `sudo`

    Quote Originally Posted by TomRoche View Post
    summary: When I connect my Android version=4.4.2 phone to my Debian laptop, the laptop detects the phone via both `nautilus` and `jmtpfs -l`. However my attempt to mount the phone's storage with `jmtpfs` fails with
    Code:
    -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
    solution: don't use `sudo`!

    Code:
    me@it:~$ fusermount -u /home/me/Android_transfer
    me@it:~$ ls -al ~/Android_transfer/
    total 8
    drwxr-xr-x  2 me me 4096 Apr  5 20:08 .
    drwxr-xr-x 50 me me 4096 Apr  5 21:09 ..
    
    me@it:~$ jmtpfs ~/Android_transfer/
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.
    Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
    Android device detected, assigning default bug flags
    me@it:~$ ls -al ~/Android_transfer/
    total 4
    drwxr-xr-x  3 me me    0 Dec 31  1969 .
    drwxr-xr-x 50 me me 4096 Apr  5 21:09 ..
    drwxr-xr-x 12 me me    0 Oct  2  4448648 Internal storage
    me@it:~$ ls -al ~/Android_transfer/Internal\ storage/
    total 0
    drwxr-xr-x 12 me me 0 Oct  2  4448648 .
    drwxr-xr-x  3 me me 0 Dec 31  1969 ..
    drwxr-xr-x  2 me me 0 Aug 31  2024 Alarms
    drwxr-xr-x  3 me me 0 Aug 26  2014 Android
    drwxr-xr-x  3 me me 0 Feb 13 19:50 DCIM
    drwxr-xr-x  2 me me 0 Aug 31  2024 Download
    drwxr-xr-x  2 me me 0 Aug 31  2024 Movies
    drwxr-xr-x  2 me me 0 Aug 31  2024 Music
    drwxr-xr-x  2 me me 0 Aug 31  2024 Notifications
    drwxr-xr-x  2 me me 0 Aug 31  2024 Pictures
    drwxr-xr-x  2 me me 0 Aug 31  2024 Podcasts
    drwxr-xr-x  2 me me 0 Aug 31  2024 Ringtones
    
    me@it:~$ fusermount -u /home/me/Android_transfer
    me@it:~$ ls -al ~/Android_transfer/Internal\ storage/
    ls: cannot access /home/me/Android_transfer/Internal storage/: No such file or directory



  3. #3
    Unfortunately the issue isn’t solved for me. Solution doesn’t work with Samsung Galaxy 2



Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •