Has anyone managed to connect their S2 using MTP when running Ubuntu? Obviously I know that it's a very simple tast to just connect via mass storage instead, but I'm interested to know.
I think that Samsung have some weird implementation of MTP because I was able to connect and copy files when I was running CM9 but not on stock ICS. I always get the error message:
Unable to mount SAMSUNG_Android
Error initialising camera: -60: Could not lock the device
Though it does mount and I can see the root of both SDCards, all the folders are empty and I can't copy any files to the cards from the computer as I get a error message reading:
There was an error copying the file into gphoto2://[usb:001,010]/store_00020002.
The same happens whether I try to use MTP or PTP.
I think the problem lies in that libmtp-1.1.3 contains fixes for the S2 but that version isn't included with 11.10 or 12.04
hint
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
alpike said:
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
Click to expand...
Click to collapse
That's connecting via USB mass storage, not mtp. But thanks for trying.
Sent from my GT-I9100 using XDA
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
what I have found out that mtpfs is unable to preserve timestamps of the files at least on my install.
gphoto2 backend worked fine on CM9 now wile testing CM10 its a bit buggy, I can get the list of files but I am unable to read or rename them.
Most likelly it will improve as development of CM10 progresses rapidly.
Mounting my Galaxy S3 when connected via USB to my Ubuntu computer
D4rKn3sSyS said:
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
Click to expand...
Click to collapse
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
slubkin said:
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
Click to expand...
Click to collapse
Ubuntu 13.04 is a drastic improvement for MTP support. I have not got around to trying my S II but I successfully managed a family friends Galaxy TAB 2 with MTP with zero manual modifications to Ubuntu. Everything worked perfect plug and play out of the box.
I have also tried old versions to know how bad they were compared to 13.04.
No luck with S2 and Ubuntu 13.04
I'm on Android 4.1.2 and trying to connect via USB to Ubuntu 13.04. Error I get is that my device is not an MTP device, which it's not as its using USB
Issue is that I don't see the mounted android partitions. To make this worse, it works every now and then. Following is the syslog and the outpu of lsusb
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aug 26 23:04:00 ml kernel: [134718.425536] usb 1-5: new high-speed USB device number 11 using ehci-pci
Aug 26 23:04:00 ml kernel: [134718.558636] usb 1-5: New USB device found, idVendor=04e8, idProduct=685b
Aug 26 23:04:00 ml kernel: [134718.558647] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 26 23:04:00 ml kernel: [134718.558655] usb 1-5: Product: SAMSUNG_Android
Aug 26 23:04:00 ml kernel: [134718.558661] usb 1-5: Manufacturer: SAMSUNG
Aug 26 23:04:00 ml kernel: [134718.558666] usb 1-5: SerialNumber: 001964815b817e
Aug 26 23:04:05 ml kernel: [134723.546077] usb 1-5: can't set config #1, error -110
Aug 26 23:04:05 ml mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5"
Aug 26 23:04:05 ml mtp-probe: bus: 1, device: 11 was not an MTP device
[email protected]:~$ lsusb
Bus 001 Device 011: ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (mass storage mode)
Bus 003 Device 002: ID 046d:c52e Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Hi Guys, I'm Running FreeBSD On my Android using Limbo PC Emulator App, Which is Based on QEMU:laugh:
i'd like to Mount Devices into FreeBSD that is Connected over USB Host..
There's "QEMU Console" which i can add from USB Devices, Remove the, etc.:silly:
The thing is that it says that the syntax of adding a device:
HTML:
usb_add device -- add USB device (e.g. 'host:bus.addr' or 'host:vendor_id:product_id')
What does it Mean? i Will be Mounting ALFA AWU0356H which it's chipset is RTL8187:victory:
i opened terminal and typed:
HTML:
lsusb
and i gotthe following:
HTML:
/dev/bus/usb/001/061: 0bda:8187 (null) (null) (null)
there's another line which is for the USB Hub i connected..:fingers-crossed:
now how can i apply this Information to the Console?:cyclops:
i could get all the required information just tell me..
I came across this post because I was looking to do the exact same thing. How did you make out?
Hi, suddenly (without any ROM flash attempt) my IAIWAI AW920 tablet got in a bootloop.
IIRC it's a RK3066 but the RKAndroidTool/Finn Flash Tool didn't recognized the tablet with either PWR Vol+ or PWR Vol- boot modes.
In the past I got the tablet successfully rooted through some tools, so in some past era I was able to communicate with ADB from the Android SDK (Linux Mint Kernel +3.10) but before it got soft-bricked I had not the USB debugging bridge set and due a failing HDD I lost that environment setup.
While being connected to my laptop through USB cable I can access two modes:
USB + PWR + Vol+: Blank black screen but I detect a USB device with VID: 10d6 PID: 10d6 that doesn't seems to be an adb client.
USB + PWR + Vol-: Appears a Fastboot kind of picture (Android mascot laying in the floor with his chest open and a Red Warning Symbol ) but no output whatsoever in [dmesg] or [udev monitor]
In neither these modes adb or fastboot detect something
---- For the Vol+ mode with the 10d6:10d6 device ----
I can't get adb or fastboot to work, even with adb_usb.ini edited in windows or linux or several different udev rules
The only udev rule I could trigger was
#IAIWAI
SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="10d6", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
Click to expand...
Click to collapse
But it seems android_usb is not a link to a proper block device (the last number increases on each test)
ls -l /dev/
android_adb -> bus/usb/001/010
Click to expand...
Click to collapse
Or at least I can't make it work with
adb -p /dev/android_adb devices
or
fastboot -s /dev/android_adb devices
Extra information of the device found in Vol+ mode
lsusb:
Bus 001 Device 003: ID 10d6:10d6 Actions Semiconductor Co., Ltd
dmesg:
[11102.331560] usb 1-2: new high-speed USB device number 10 using ehci-pci
[11102.464620] usb 1-2: New USB device found, idVendor=10d6, idProduct=10d6
[11102.464633] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
udevadm monitor:
KERNEL[8596.157794] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
KERNEL[8596.158995] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
UDEV [8596.167280] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
UDEV [8596.171388] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
P: /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVTYPE=usb_interface
E: ID_VENDOR_FROM_DATABASE=Actions Semiconductor Co., Ltd
E: INTERFACE=255/255/255
E: MODALIAS=usb:v10D6p10D6d0100dc00dsc00dp00icFFiscFFipFFin00
E: PRODUCT=10d6/10d6/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: USEC_INITIALIZED=434099056
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 --attribute-walk:
looking at device '/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0':
KERNEL=="1-2:1.0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{bInterfaceClass}=="ff"
ATTR{bInterfaceSubClass}=="ff"
ATTR{bInterfaceProtocol}=="ff"
ATTR{bNumEndpoints}=="02"
ATTR{supports_autosuspend}=="1"
ATTR{bAlternateSetting}==" 0"
ATTR{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1/1-2':
KERNELS=="1-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="2"
ATTRS{idVendor}=="10d6"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="128mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="6"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="10d6"
ATTRS{bDeviceClass}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="5"
ATTRS{bcdDevice}=="0313"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:12.2"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="91"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.13.0-37-generic ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:12.2':
KERNELS=="0000:00:12.2"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="17"
ATTRS{subsystem_vendor}=="0x1179"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{enabled}=="1"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
ATTRS{device}=="0x4396"
ATTRS{uframe_periodic_max}=="100"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-1"
ATTRS{vendor}=="0x1002"
ATTRS{subsystem_device}=="0xff1e"
ATTRS{numa_node}=="0"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Click to expand...
Click to collapse
After connecting the phone via usb cable, "adb devices" command lists :
$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA3BSWG00401 offline
1) First time it asked whether to trust this computer and I checked 'always trust this computer'. Is there a way to untrust a specific computer / make it ask again ?
2) plugging the cable to my older SGS3 works fine :
$ adb devices
List of devices attached
4df1d4650790afdf device
Has anybody encountered this before ?
Additional info :
$ adb version
Android Debug Bridge version 1.0.32
Revision 57224c5cff69-android
I'm using Linux Mint 17.2, NuSense 6 (Lolipop)
hey i try to get the ADB things to work. i was albe to make myself a developer and all i want to do its to change the resolution of my display from 2k to 1080.
if its to hard and i need to root i will wait for i want to damage my worrenty or anything leik that due to it costed to much.
i use a Huawei Mediapad M5 LTE 64Gb tablet.
i use windows 10 pro x64
the error i get when i type ADB this is
Code:
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
it seems its not installed but i dont know i tryed some problems from the site and even puged my tablet and put on usb debugging but it dont get up on any list or anything.
thanks for the help.