14.04 Cannot create/delete/manipulate files on my Android device via USB
I've always had issues with compatibility between my Android phone and Ubuntu, but now it's gotten to the point that I can't do anything with it over USB. It's always been that when I plug in my device, an error message appear:
"Unable to mount Android phone
"Unable to open MTP device '[usb:001,035]'"
Regardless, I was able to manage my files as long as the phone was unlocked when I plugged it in. However, I now seem to get a new error message (or at least one that I don't recall getting before), which reads:
Unhandled error message: No such interface 'org.gtk.vfs.Mount' on object at path/org/gtk/vfs/mount/1
I'm not sure if this is the root of my problem. I can view all of the files on my Android device, but when I try to do anything like creating/deleting files, I receive a message saying something like:
Error while creating directory Untitled Folder.
There was an error creating the directory in mtp://[usb001,037]/Internal%20storage.
Under "Show more details", I receive the error:
libmtp error: Could not send object info.
I can do everything I need to over FTP, but it ridiculously slow for large files. Any help getting my Android and PC to talk to each other is greatly appreciated.
14.04 usb android
add a comment |
I've always had issues with compatibility between my Android phone and Ubuntu, but now it's gotten to the point that I can't do anything with it over USB. It's always been that when I plug in my device, an error message appear:
"Unable to mount Android phone
"Unable to open MTP device '[usb:001,035]'"
Regardless, I was able to manage my files as long as the phone was unlocked when I plugged it in. However, I now seem to get a new error message (or at least one that I don't recall getting before), which reads:
Unhandled error message: No such interface 'org.gtk.vfs.Mount' on object at path/org/gtk/vfs/mount/1
I'm not sure if this is the root of my problem. I can view all of the files on my Android device, but when I try to do anything like creating/deleting files, I receive a message saying something like:
Error while creating directory Untitled Folder.
There was an error creating the directory in mtp://[usb001,037]/Internal%20storage.
Under "Show more details", I receive the error:
libmtp error: Could not send object info.
I can do everything I need to over FTP, but it ridiculously slow for large files. Any help getting my Android and PC to talk to each other is greatly appreciated.
14.04 usb android
Make sure the device is connected in Mass storage mode (MSC) and not in Media transfer mode (MTP).
– user457885
Jun 14 '16 at 3:50
add a comment |
I've always had issues with compatibility between my Android phone and Ubuntu, but now it's gotten to the point that I can't do anything with it over USB. It's always been that when I plug in my device, an error message appear:
"Unable to mount Android phone
"Unable to open MTP device '[usb:001,035]'"
Regardless, I was able to manage my files as long as the phone was unlocked when I plugged it in. However, I now seem to get a new error message (or at least one that I don't recall getting before), which reads:
Unhandled error message: No such interface 'org.gtk.vfs.Mount' on object at path/org/gtk/vfs/mount/1
I'm not sure if this is the root of my problem. I can view all of the files on my Android device, but when I try to do anything like creating/deleting files, I receive a message saying something like:
Error while creating directory Untitled Folder.
There was an error creating the directory in mtp://[usb001,037]/Internal%20storage.
Under "Show more details", I receive the error:
libmtp error: Could not send object info.
I can do everything I need to over FTP, but it ridiculously slow for large files. Any help getting my Android and PC to talk to each other is greatly appreciated.
14.04 usb android
I've always had issues with compatibility between my Android phone and Ubuntu, but now it's gotten to the point that I can't do anything with it over USB. It's always been that when I plug in my device, an error message appear:
"Unable to mount Android phone
"Unable to open MTP device '[usb:001,035]'"
Regardless, I was able to manage my files as long as the phone was unlocked when I plugged it in. However, I now seem to get a new error message (or at least one that I don't recall getting before), which reads:
Unhandled error message: No such interface 'org.gtk.vfs.Mount' on object at path/org/gtk/vfs/mount/1
I'm not sure if this is the root of my problem. I can view all of the files on my Android device, but when I try to do anything like creating/deleting files, I receive a message saying something like:
Error while creating directory Untitled Folder.
There was an error creating the directory in mtp://[usb001,037]/Internal%20storage.
Under "Show more details", I receive the error:
libmtp error: Could not send object info.
I can do everything I need to over FTP, but it ridiculously slow for large files. Any help getting my Android and PC to talk to each other is greatly appreciated.
14.04 usb android
14.04 usb android
asked Sep 28 '14 at 2:22
user154885user154885
111113
111113
Make sure the device is connected in Mass storage mode (MSC) and not in Media transfer mode (MTP).
– user457885
Jun 14 '16 at 3:50
add a comment |
Make sure the device is connected in Mass storage mode (MSC) and not in Media transfer mode (MTP).
– user457885
Jun 14 '16 at 3:50
Make sure the device is connected in Mass storage mode (MSC) and not in Media transfer mode (MTP).
– user457885
Jun 14 '16 at 3:50
Make sure the device is connected in Mass storage mode (MSC) and not in Media transfer mode (MTP).
– user457885
Jun 14 '16 at 3:50
add a comment |
9 Answers
9
active
oldest
votes
The conflict is between Banshee and the file manager (Nautilus), both are trying to access the device. So if you want to copy the playlist to the device, you must deactivate all the extensions that access your device, in Banshee's Preferences.
Then open your device's music folder in Nautilus, and copy/paste your playlists from Banshee to the Nautilus' window.
This worked for me with Ubuntu 14.04 + Jolla phone with Sailfish OS.
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:09
Just want to note that this solved my problem as well -- make sure Banshee is not running in the background
– mb7744
Apr 13 '16 at 15:06
add a comment |
Try this
sudo apt-get install mtpfs
Then reconnect phone. This works for me. Samsung Note 2 Android 4.4.2
I have same problem as OP, and installing mtpfs did not solve the issue. I still get the same error when connecting my phone via USB, which worked perfectly fine in 12.04, 12.10, 13.04, and 13.10. Now with 14.04 upgrade, I cant seem to connect my phone at all.
– Todd
Oct 13 '14 at 19:11
1
im passed the 5 min comment edit window... but apparently my phone (Samsung S5) will connect if i leave the usb plugged in for about 10 mins or so. I was browsing the web for bug reports/solutions on this, then all the sudden was able to click into the phone via nautilus and find my SD card and data i wanted...
– Todd
Oct 13 '14 at 19:31
1
also wanted to note - i have a second 14.04 machine that had this same problem, and simply installing 'mtpfs' fixed this, though again it took about 10 minutes after the install for it to start working. i also noticed that if i turned banshee media player on, i couldnt access data in my phone, and turning banshee off immediately restored access to the SD card.
– Todd
Oct 13 '14 at 23:54
From insane comments and "nothing will work, trust me Linux doesn't work that way" advices. I salute you :) 1 seconds job solved my 20 day problem.
– user3041058
Jul 11 '15 at 17:32
1
Doesnt work even after I rebooted my system... I'm using Galaxy Grand
– abhishah901
Dec 10 '15 at 10:07
|
show 1 more comment
I had the same problem, but simply closing Banshee solved it. Make sure you don't have any other programs currently accessing the device.
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:08
add a comment |
You could also use:
adb push /path/to/file /path/to/phonestorage
you need the ADB
drivers installed on your computer.
You also have to enable USB debugging
in developer options
on your device.
To enable developer options,
go to: Settings>About Phone> Tap Build-number 7 times. (Enabled)
Then go back to settings, you'll find developer options right above About Phone. In here you'll find USB debugging.
When you enable this and connect your device to your computer, it will ask you to give your computer permission with the RSA
key (tick the box before accepting it to let the permission stick).
This is for me even quicker then just copying files over like we normally do.
Same problem over adb on Samsung S5 running cyanogenmod 13.1
– Tony Martin
Dec 4 '16 at 19:41
add a comment |
I had the following error:
libmtp error: Could not send object info.
error message due to a :
in the file name. I renamed the file, and the problem was solved.
Similar issue due to either an emoji or an ampersand in the file name (or possibly some other weird zero-width character or something.)
– MalcolmOcean
Jan 23 at 23:36
add a comment |
I had a similar problem, which was not fixed by the various answer given above. The directory would mount and I could see files, but after a few seconds it would not work anymore. The quick fix solution was: I noticed that the connection breaks everytime the phone goes into "screen lock" mode. So I started swiping the phone screen continuously with one hand while I copied files with the other hand, and that actually worked. I don't know the "correct" fix for this though.
If the screen lock was the problem you can disable it or set its timer to a much longer period in the phone configuration.
– David Foerster
Dec 23 '16 at 11:29
add a comment |
Same problem. Thousands of popups and file explorer windows would keep coming as soon as I connect my phone. I solved it by choosing "Camera (PTP)" in my phone instead of "Media device (MTP)" by clicking the usb notification.
add a comment |
Buongiorno, uso ubuntu 18.10 e mi si è presentato lo stesso problema con un file mp3. Ho risolto cambiando il protocollo del file (ľho rinominato togliendo un asterisco * che secondo me non tornava).
New contributor
add a comment |
I had encounter the same problem after a period when the files transfer worked well.
But, after some tries, I've got the cause; that the device's file system showed by the mtp protocol on the computer is not correctly synced by the real one: it not show a file/dir that is physically exist on the device, and a creation/renaming of the same entity on the file system occur this error.
Solution: keep manually (explorer app) the file system to the same state of the presented one.
I don't know the cause of this mistake.
I hope that can be useful for someone.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f529477%2f14-04-cannot-create-delete-manipulate-files-on-my-android-device-via-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
The conflict is between Banshee and the file manager (Nautilus), both are trying to access the device. So if you want to copy the playlist to the device, you must deactivate all the extensions that access your device, in Banshee's Preferences.
Then open your device's music folder in Nautilus, and copy/paste your playlists from Banshee to the Nautilus' window.
This worked for me with Ubuntu 14.04 + Jolla phone with Sailfish OS.
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:09
Just want to note that this solved my problem as well -- make sure Banshee is not running in the background
– mb7744
Apr 13 '16 at 15:06
add a comment |
The conflict is between Banshee and the file manager (Nautilus), both are trying to access the device. So if you want to copy the playlist to the device, you must deactivate all the extensions that access your device, in Banshee's Preferences.
Then open your device's music folder in Nautilus, and copy/paste your playlists from Banshee to the Nautilus' window.
This worked for me with Ubuntu 14.04 + Jolla phone with Sailfish OS.
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:09
Just want to note that this solved my problem as well -- make sure Banshee is not running in the background
– mb7744
Apr 13 '16 at 15:06
add a comment |
The conflict is between Banshee and the file manager (Nautilus), both are trying to access the device. So if you want to copy the playlist to the device, you must deactivate all the extensions that access your device, in Banshee's Preferences.
Then open your device's music folder in Nautilus, and copy/paste your playlists from Banshee to the Nautilus' window.
This worked for me with Ubuntu 14.04 + Jolla phone with Sailfish OS.
The conflict is between Banshee and the file manager (Nautilus), both are trying to access the device. So if you want to copy the playlist to the device, you must deactivate all the extensions that access your device, in Banshee's Preferences.
Then open your device's music folder in Nautilus, and copy/paste your playlists from Banshee to the Nautilus' window.
This worked for me with Ubuntu 14.04 + Jolla phone with Sailfish OS.
answered Dec 22 '14 at 21:33
Lucien P.Lucien P.
12113
12113
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:09
Just want to note that this solved my problem as well -- make sure Banshee is not running in the background
– mb7744
Apr 13 '16 at 15:06
add a comment |
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:09
Just want to note that this solved my problem as well -- make sure Banshee is not running in the background
– mb7744
Apr 13 '16 at 15:06
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:09
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:09
Just want to note that this solved my problem as well -- make sure Banshee is not running in the background
– mb7744
Apr 13 '16 at 15:06
Just want to note that this solved my problem as well -- make sure Banshee is not running in the background
– mb7744
Apr 13 '16 at 15:06
add a comment |
Try this
sudo apt-get install mtpfs
Then reconnect phone. This works for me. Samsung Note 2 Android 4.4.2
I have same problem as OP, and installing mtpfs did not solve the issue. I still get the same error when connecting my phone via USB, which worked perfectly fine in 12.04, 12.10, 13.04, and 13.10. Now with 14.04 upgrade, I cant seem to connect my phone at all.
– Todd
Oct 13 '14 at 19:11
1
im passed the 5 min comment edit window... but apparently my phone (Samsung S5) will connect if i leave the usb plugged in for about 10 mins or so. I was browsing the web for bug reports/solutions on this, then all the sudden was able to click into the phone via nautilus and find my SD card and data i wanted...
– Todd
Oct 13 '14 at 19:31
1
also wanted to note - i have a second 14.04 machine that had this same problem, and simply installing 'mtpfs' fixed this, though again it took about 10 minutes after the install for it to start working. i also noticed that if i turned banshee media player on, i couldnt access data in my phone, and turning banshee off immediately restored access to the SD card.
– Todd
Oct 13 '14 at 23:54
From insane comments and "nothing will work, trust me Linux doesn't work that way" advices. I salute you :) 1 seconds job solved my 20 day problem.
– user3041058
Jul 11 '15 at 17:32
1
Doesnt work even after I rebooted my system... I'm using Galaxy Grand
– abhishah901
Dec 10 '15 at 10:07
|
show 1 more comment
Try this
sudo apt-get install mtpfs
Then reconnect phone. This works for me. Samsung Note 2 Android 4.4.2
I have same problem as OP, and installing mtpfs did not solve the issue. I still get the same error when connecting my phone via USB, which worked perfectly fine in 12.04, 12.10, 13.04, and 13.10. Now with 14.04 upgrade, I cant seem to connect my phone at all.
– Todd
Oct 13 '14 at 19:11
1
im passed the 5 min comment edit window... but apparently my phone (Samsung S5) will connect if i leave the usb plugged in for about 10 mins or so. I was browsing the web for bug reports/solutions on this, then all the sudden was able to click into the phone via nautilus and find my SD card and data i wanted...
– Todd
Oct 13 '14 at 19:31
1
also wanted to note - i have a second 14.04 machine that had this same problem, and simply installing 'mtpfs' fixed this, though again it took about 10 minutes after the install for it to start working. i also noticed that if i turned banshee media player on, i couldnt access data in my phone, and turning banshee off immediately restored access to the SD card.
– Todd
Oct 13 '14 at 23:54
From insane comments and "nothing will work, trust me Linux doesn't work that way" advices. I salute you :) 1 seconds job solved my 20 day problem.
– user3041058
Jul 11 '15 at 17:32
1
Doesnt work even after I rebooted my system... I'm using Galaxy Grand
– abhishah901
Dec 10 '15 at 10:07
|
show 1 more comment
Try this
sudo apt-get install mtpfs
Then reconnect phone. This works for me. Samsung Note 2 Android 4.4.2
Try this
sudo apt-get install mtpfs
Then reconnect phone. This works for me. Samsung Note 2 Android 4.4.2
answered Sep 28 '14 at 2:38
branch.lizardbranch.lizard
32114
32114
I have same problem as OP, and installing mtpfs did not solve the issue. I still get the same error when connecting my phone via USB, which worked perfectly fine in 12.04, 12.10, 13.04, and 13.10. Now with 14.04 upgrade, I cant seem to connect my phone at all.
– Todd
Oct 13 '14 at 19:11
1
im passed the 5 min comment edit window... but apparently my phone (Samsung S5) will connect if i leave the usb plugged in for about 10 mins or so. I was browsing the web for bug reports/solutions on this, then all the sudden was able to click into the phone via nautilus and find my SD card and data i wanted...
– Todd
Oct 13 '14 at 19:31
1
also wanted to note - i have a second 14.04 machine that had this same problem, and simply installing 'mtpfs' fixed this, though again it took about 10 minutes after the install for it to start working. i also noticed that if i turned banshee media player on, i couldnt access data in my phone, and turning banshee off immediately restored access to the SD card.
– Todd
Oct 13 '14 at 23:54
From insane comments and "nothing will work, trust me Linux doesn't work that way" advices. I salute you :) 1 seconds job solved my 20 day problem.
– user3041058
Jul 11 '15 at 17:32
1
Doesnt work even after I rebooted my system... I'm using Galaxy Grand
– abhishah901
Dec 10 '15 at 10:07
|
show 1 more comment
I have same problem as OP, and installing mtpfs did not solve the issue. I still get the same error when connecting my phone via USB, which worked perfectly fine in 12.04, 12.10, 13.04, and 13.10. Now with 14.04 upgrade, I cant seem to connect my phone at all.
– Todd
Oct 13 '14 at 19:11
1
im passed the 5 min comment edit window... but apparently my phone (Samsung S5) will connect if i leave the usb plugged in for about 10 mins or so. I was browsing the web for bug reports/solutions on this, then all the sudden was able to click into the phone via nautilus and find my SD card and data i wanted...
– Todd
Oct 13 '14 at 19:31
1
also wanted to note - i have a second 14.04 machine that had this same problem, and simply installing 'mtpfs' fixed this, though again it took about 10 minutes after the install for it to start working. i also noticed that if i turned banshee media player on, i couldnt access data in my phone, and turning banshee off immediately restored access to the SD card.
– Todd
Oct 13 '14 at 23:54
From insane comments and "nothing will work, trust me Linux doesn't work that way" advices. I salute you :) 1 seconds job solved my 20 day problem.
– user3041058
Jul 11 '15 at 17:32
1
Doesnt work even after I rebooted my system... I'm using Galaxy Grand
– abhishah901
Dec 10 '15 at 10:07
I have same problem as OP, and installing mtpfs did not solve the issue. I still get the same error when connecting my phone via USB, which worked perfectly fine in 12.04, 12.10, 13.04, and 13.10. Now with 14.04 upgrade, I cant seem to connect my phone at all.
– Todd
Oct 13 '14 at 19:11
I have same problem as OP, and installing mtpfs did not solve the issue. I still get the same error when connecting my phone via USB, which worked perfectly fine in 12.04, 12.10, 13.04, and 13.10. Now with 14.04 upgrade, I cant seem to connect my phone at all.
– Todd
Oct 13 '14 at 19:11
1
1
im passed the 5 min comment edit window... but apparently my phone (Samsung S5) will connect if i leave the usb plugged in for about 10 mins or so. I was browsing the web for bug reports/solutions on this, then all the sudden was able to click into the phone via nautilus and find my SD card and data i wanted...
– Todd
Oct 13 '14 at 19:31
im passed the 5 min comment edit window... but apparently my phone (Samsung S5) will connect if i leave the usb plugged in for about 10 mins or so. I was browsing the web for bug reports/solutions on this, then all the sudden was able to click into the phone via nautilus and find my SD card and data i wanted...
– Todd
Oct 13 '14 at 19:31
1
1
also wanted to note - i have a second 14.04 machine that had this same problem, and simply installing 'mtpfs' fixed this, though again it took about 10 minutes after the install for it to start working. i also noticed that if i turned banshee media player on, i couldnt access data in my phone, and turning banshee off immediately restored access to the SD card.
– Todd
Oct 13 '14 at 23:54
also wanted to note - i have a second 14.04 machine that had this same problem, and simply installing 'mtpfs' fixed this, though again it took about 10 minutes after the install for it to start working. i also noticed that if i turned banshee media player on, i couldnt access data in my phone, and turning banshee off immediately restored access to the SD card.
– Todd
Oct 13 '14 at 23:54
From insane comments and "nothing will work, trust me Linux doesn't work that way" advices. I salute you :) 1 seconds job solved my 20 day problem.
– user3041058
Jul 11 '15 at 17:32
From insane comments and "nothing will work, trust me Linux doesn't work that way" advices. I salute you :) 1 seconds job solved my 20 day problem.
– user3041058
Jul 11 '15 at 17:32
1
1
Doesnt work even after I rebooted my system... I'm using Galaxy Grand
– abhishah901
Dec 10 '15 at 10:07
Doesnt work even after I rebooted my system... I'm using Galaxy Grand
– abhishah901
Dec 10 '15 at 10:07
|
show 1 more comment
I had the same problem, but simply closing Banshee solved it. Make sure you don't have any other programs currently accessing the device.
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:08
add a comment |
I had the same problem, but simply closing Banshee solved it. Make sure you don't have any other programs currently accessing the device.
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:08
add a comment |
I had the same problem, but simply closing Banshee solved it. Make sure you don't have any other programs currently accessing the device.
I had the same problem, but simply closing Banshee solved it. Make sure you don't have any other programs currently accessing the device.
answered Nov 25 '14 at 14:48
Július RetzerJúlius Retzer
1393
1393
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:08
add a comment |
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:08
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:08
I don't use Banshee but the problem still persists
– abhishah901
Dec 10 '15 at 10:08
add a comment |
You could also use:
adb push /path/to/file /path/to/phonestorage
you need the ADB
drivers installed on your computer.
You also have to enable USB debugging
in developer options
on your device.
To enable developer options,
go to: Settings>About Phone> Tap Build-number 7 times. (Enabled)
Then go back to settings, you'll find developer options right above About Phone. In here you'll find USB debugging.
When you enable this and connect your device to your computer, it will ask you to give your computer permission with the RSA
key (tick the box before accepting it to let the permission stick).
This is for me even quicker then just copying files over like we normally do.
Same problem over adb on Samsung S5 running cyanogenmod 13.1
– Tony Martin
Dec 4 '16 at 19:41
add a comment |
You could also use:
adb push /path/to/file /path/to/phonestorage
you need the ADB
drivers installed on your computer.
You also have to enable USB debugging
in developer options
on your device.
To enable developer options,
go to: Settings>About Phone> Tap Build-number 7 times. (Enabled)
Then go back to settings, you'll find developer options right above About Phone. In here you'll find USB debugging.
When you enable this and connect your device to your computer, it will ask you to give your computer permission with the RSA
key (tick the box before accepting it to let the permission stick).
This is for me even quicker then just copying files over like we normally do.
Same problem over adb on Samsung S5 running cyanogenmod 13.1
– Tony Martin
Dec 4 '16 at 19:41
add a comment |
You could also use:
adb push /path/to/file /path/to/phonestorage
you need the ADB
drivers installed on your computer.
You also have to enable USB debugging
in developer options
on your device.
To enable developer options,
go to: Settings>About Phone> Tap Build-number 7 times. (Enabled)
Then go back to settings, you'll find developer options right above About Phone. In here you'll find USB debugging.
When you enable this and connect your device to your computer, it will ask you to give your computer permission with the RSA
key (tick the box before accepting it to let the permission stick).
This is for me even quicker then just copying files over like we normally do.
You could also use:
adb push /path/to/file /path/to/phonestorage
you need the ADB
drivers installed on your computer.
You also have to enable USB debugging
in developer options
on your device.
To enable developer options,
go to: Settings>About Phone> Tap Build-number 7 times. (Enabled)
Then go back to settings, you'll find developer options right above About Phone. In here you'll find USB debugging.
When you enable this and connect your device to your computer, it will ask you to give your computer permission with the RSA
key (tick the box before accepting it to let the permission stick).
This is for me even quicker then just copying files over like we normally do.
edited Jun 14 '16 at 5:28
Mahesh
10.3k43754
10.3k43754
answered Jan 21 '16 at 22:55
MrMaddTraxxMrMaddTraxx
111
111
Same problem over adb on Samsung S5 running cyanogenmod 13.1
– Tony Martin
Dec 4 '16 at 19:41
add a comment |
Same problem over adb on Samsung S5 running cyanogenmod 13.1
– Tony Martin
Dec 4 '16 at 19:41
Same problem over adb on Samsung S5 running cyanogenmod 13.1
– Tony Martin
Dec 4 '16 at 19:41
Same problem over adb on Samsung S5 running cyanogenmod 13.1
– Tony Martin
Dec 4 '16 at 19:41
add a comment |
I had the following error:
libmtp error: Could not send object info.
error message due to a :
in the file name. I renamed the file, and the problem was solved.
Similar issue due to either an emoji or an ampersand in the file name (or possibly some other weird zero-width character or something.)
– MalcolmOcean
Jan 23 at 23:36
add a comment |
I had the following error:
libmtp error: Could not send object info.
error message due to a :
in the file name. I renamed the file, and the problem was solved.
Similar issue due to either an emoji or an ampersand in the file name (or possibly some other weird zero-width character or something.)
– MalcolmOcean
Jan 23 at 23:36
add a comment |
I had the following error:
libmtp error: Could not send object info.
error message due to a :
in the file name. I renamed the file, and the problem was solved.
I had the following error:
libmtp error: Could not send object info.
error message due to a :
in the file name. I renamed the file, and the problem was solved.
edited May 28 '18 at 19:43
Fabby
26.8k1360161
26.8k1360161
answered May 28 '18 at 19:23
BenBen
111
111
Similar issue due to either an emoji or an ampersand in the file name (or possibly some other weird zero-width character or something.)
– MalcolmOcean
Jan 23 at 23:36
add a comment |
Similar issue due to either an emoji or an ampersand in the file name (or possibly some other weird zero-width character or something.)
– MalcolmOcean
Jan 23 at 23:36
Similar issue due to either an emoji or an ampersand in the file name (or possibly some other weird zero-width character or something.)
– MalcolmOcean
Jan 23 at 23:36
Similar issue due to either an emoji or an ampersand in the file name (or possibly some other weird zero-width character or something.)
– MalcolmOcean
Jan 23 at 23:36
add a comment |
I had a similar problem, which was not fixed by the various answer given above. The directory would mount and I could see files, but after a few seconds it would not work anymore. The quick fix solution was: I noticed that the connection breaks everytime the phone goes into "screen lock" mode. So I started swiping the phone screen continuously with one hand while I copied files with the other hand, and that actually worked. I don't know the "correct" fix for this though.
If the screen lock was the problem you can disable it or set its timer to a much longer period in the phone configuration.
– David Foerster
Dec 23 '16 at 11:29
add a comment |
I had a similar problem, which was not fixed by the various answer given above. The directory would mount and I could see files, but after a few seconds it would not work anymore. The quick fix solution was: I noticed that the connection breaks everytime the phone goes into "screen lock" mode. So I started swiping the phone screen continuously with one hand while I copied files with the other hand, and that actually worked. I don't know the "correct" fix for this though.
If the screen lock was the problem you can disable it or set its timer to a much longer period in the phone configuration.
– David Foerster
Dec 23 '16 at 11:29
add a comment |
I had a similar problem, which was not fixed by the various answer given above. The directory would mount and I could see files, but after a few seconds it would not work anymore. The quick fix solution was: I noticed that the connection breaks everytime the phone goes into "screen lock" mode. So I started swiping the phone screen continuously with one hand while I copied files with the other hand, and that actually worked. I don't know the "correct" fix for this though.
I had a similar problem, which was not fixed by the various answer given above. The directory would mount and I could see files, but after a few seconds it would not work anymore. The quick fix solution was: I noticed that the connection breaks everytime the phone goes into "screen lock" mode. So I started swiping the phone screen continuously with one hand while I copied files with the other hand, and that actually worked. I don't know the "correct" fix for this though.
answered Dec 23 '16 at 8:13
Jérôme KunegisJérôme Kunegis
12
12
If the screen lock was the problem you can disable it or set its timer to a much longer period in the phone configuration.
– David Foerster
Dec 23 '16 at 11:29
add a comment |
If the screen lock was the problem you can disable it or set its timer to a much longer period in the phone configuration.
– David Foerster
Dec 23 '16 at 11:29
If the screen lock was the problem you can disable it or set its timer to a much longer period in the phone configuration.
– David Foerster
Dec 23 '16 at 11:29
If the screen lock was the problem you can disable it or set its timer to a much longer period in the phone configuration.
– David Foerster
Dec 23 '16 at 11:29
add a comment |
Same problem. Thousands of popups and file explorer windows would keep coming as soon as I connect my phone. I solved it by choosing "Camera (PTP)" in my phone instead of "Media device (MTP)" by clicking the usb notification.
add a comment |
Same problem. Thousands of popups and file explorer windows would keep coming as soon as I connect my phone. I solved it by choosing "Camera (PTP)" in my phone instead of "Media device (MTP)" by clicking the usb notification.
add a comment |
Same problem. Thousands of popups and file explorer windows would keep coming as soon as I connect my phone. I solved it by choosing "Camera (PTP)" in my phone instead of "Media device (MTP)" by clicking the usb notification.
Same problem. Thousands of popups and file explorer windows would keep coming as soon as I connect my phone. I solved it by choosing "Camera (PTP)" in my phone instead of "Media device (MTP)" by clicking the usb notification.
answered Jun 30 '18 at 13:29
raghavsood33raghavsood33
1314
1314
add a comment |
add a comment |
Buongiorno, uso ubuntu 18.10 e mi si è presentato lo stesso problema con un file mp3. Ho risolto cambiando il protocollo del file (ľho rinominato togliendo un asterisco * che secondo me non tornava).
New contributor
add a comment |
Buongiorno, uso ubuntu 18.10 e mi si è presentato lo stesso problema con un file mp3. Ho risolto cambiando il protocollo del file (ľho rinominato togliendo un asterisco * che secondo me non tornava).
New contributor
add a comment |
Buongiorno, uso ubuntu 18.10 e mi si è presentato lo stesso problema con un file mp3. Ho risolto cambiando il protocollo del file (ľho rinominato togliendo un asterisco * che secondo me non tornava).
New contributor
Buongiorno, uso ubuntu 18.10 e mi si è presentato lo stesso problema con un file mp3. Ho risolto cambiando il protocollo del file (ľho rinominato togliendo un asterisco * che secondo me non tornava).
New contributor
New contributor
answered 58 mins ago
Marco4931Marco4931
1
1
New contributor
New contributor
add a comment |
add a comment |
I had encounter the same problem after a period when the files transfer worked well.
But, after some tries, I've got the cause; that the device's file system showed by the mtp protocol on the computer is not correctly synced by the real one: it not show a file/dir that is physically exist on the device, and a creation/renaming of the same entity on the file system occur this error.
Solution: keep manually (explorer app) the file system to the same state of the presented one.
I don't know the cause of this mistake.
I hope that can be useful for someone.
add a comment |
I had encounter the same problem after a period when the files transfer worked well.
But, after some tries, I've got the cause; that the device's file system showed by the mtp protocol on the computer is not correctly synced by the real one: it not show a file/dir that is physically exist on the device, and a creation/renaming of the same entity on the file system occur this error.
Solution: keep manually (explorer app) the file system to the same state of the presented one.
I don't know the cause of this mistake.
I hope that can be useful for someone.
add a comment |
I had encounter the same problem after a period when the files transfer worked well.
But, after some tries, I've got the cause; that the device's file system showed by the mtp protocol on the computer is not correctly synced by the real one: it not show a file/dir that is physically exist on the device, and a creation/renaming of the same entity on the file system occur this error.
Solution: keep manually (explorer app) the file system to the same state of the presented one.
I don't know the cause of this mistake.
I hope that can be useful for someone.
I had encounter the same problem after a period when the files transfer worked well.
But, after some tries, I've got the cause; that the device's file system showed by the mtp protocol on the computer is not correctly synced by the real one: it not show a file/dir that is physically exist on the device, and a creation/renaming of the same entity on the file system occur this error.
Solution: keep manually (explorer app) the file system to the same state of the presented one.
I don't know the cause of this mistake.
I hope that can be useful for someone.
answered Oct 8 '15 at 15:02
Alessandro BorileAlessandro Borile
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f529477%2f14-04-cannot-create-delete-manipulate-files-on-my-android-device-via-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Make sure the device is connected in Mass storage mode (MSC) and not in Media transfer mode (MTP).
– user457885
Jun 14 '16 at 3:50