[Guide] Mount Internal Storage in Ubuntu

[Crimton]

I keep gettting a "Transport endpoint is not connected" error when I try this. I am using 10.04 64-bit. Does anyone know how to resolve this?

this was another error i kept getting. i actually emailed motorola demanding a fix for this as its not fair that only mac and windows users are able to mount storage, we'll see if they reply....

 

[timrock]

this is what i get in my fstab

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdc1 during installation
UUID=b84cb6ae-d386-4791-b9f6-556ae47ccd95 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdc5 during installation
UUID=2369430c-0a78-42b3-803a-ba5175d1164b none            swap    sw              0       0
/dev/sdd        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
/dev/scd1       /media/floppy1  auto    rw,user,noauto,exec,utf8 0       0

exactly where am i supposed to type "# mount point for moto xoom" and "mtpfs /media/xoom fuse user,noauto,allow_other 0 0"? do i press enter after entering the first line? and do i put the "#" at the beginning of that second line?

 

[willverduzco]

Title edited to reflect that this is in fact a guide. Thanks for the useful post.

 

[Crimton]

this is what i get in my fstab

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdc1 during installation
UUID=b84cb6ae-d386-4791-b9f6-556ae47ccd95 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdc5 during installation
UUID=2369430c-0a78-42b3-803a-ba5175d1164b none            swap    sw              0       0
/dev/sdd        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
/dev/scd1       /media/floppy1  auto    rw,user,noauto,exec,utf8 0       0

exactly where am i supposed to type "# mount point for moto xoom" and "mtpfs /media/xoom fuse user,noauto,allow_other 0 0"? do i press enter after entering the first line? and do i put the "#" at the beginning of that second line?

i put both lines at the bottom, and it was not working. also i think i messed up my fstab and i didn't back it up so now i'm getting mount errors at boot up

 

[timrock]

i put both lines at the bottom, and it was not working. also i think i messed up my fstab and i didn't back it up so now i'm getting mount errors at boot up

i copied and pasted what was originally there, to another note, before making any changes to it. i hope a fix for this comes soon. i dont want to have to dual boot with windows.

 

[roberj13]

Hey guys, just wanted to pop in because I heard some people were having some trouble with this. First I wanted to test this set of instructions out and make sure I copied them right myself. I started on Maverick, Clean upgraded to Natty beta 2 and both times it worked.

Here are some steps that I am seeing alot of people get wrong.

If you copy and paste the code boxes, you still need to read the instructions. All three of these things will break this and they are easy to miss.

- Copying and pasting 'sudo chmod user:user /media/xoom' when 'user' should be your actual username
- Not uncommenting allow_other in fuse.conf by removing the '#' sign, because that's not clear in the code box.
- not adding your user name to etc/groups under the fuse listing because that's not clear on the code box either.

All of these things have to be done right or none of it will work at all. I have seen all the errors you guys are getting now so you are getting close if you are getting them but you need to check through your work. Stuff like transport not connected, bad mount point, etc. will all go away when everything is good.

This sucks, I wish the guide wouldn't have to be so complicated. Maybe we can hack up a way to allow ums mounting booted but until then we are stuck with this.

OH. I forgot to mention a nice light at the end of the tunnel. Since SDCard2's mount point is within SDCard on Tiamat's kernel. You will have access to that as well~!

Also note, if you are on Lucid, apparently as mentioned before the mtpfs package is broken and you will likely have to search for another package for this.

 

[grenness]

I am pretty sure I have done everything by the letters, and I'm able to mount and browse the Xoom.
However, when trying to transfer files from my Ubuntu 10.10 they appear to be copied over but then just disappears. No error messages.
Am I the only one? I noticed someone else said it appeared that the transferred files didn't transfer - I took that as they in fact were transferred, but mine are gone.

~Christopher

(Why, Google, did you drop the simple and brilliant Mass Storage feature in 3.0? MTP, isn't that some sort of Microsoft "standard"?)

 

[roberj13]

Yeah MTP is a Microsoft standard, I would guess they are trying to show people it is actually easier to sync music, pictures, etc. on Android, since that's what I hear a lot of new users complain about. On Windows it is actually easier once you get it setup..sigh

Anyhow, yeah seems I lied. This used to work...I don't know if it was the update that made it to where the files don't update or if recent changes in the kernel. I am going to be looking into this today again and running some tests.

Linux users deserve to be able to transfer files to :/

 

[Crimton]

Linux users deserve to be able to transfer files to :/

THIS ^^^

Sent from my ADR6400L using XDA App

 

[kcrudup]

(Why, Google, did you drop the simple and brilliant Mass Storage feature in 3.0? MTP, isn't that some sort of Microsoft "standard"?)

It's tied to the same reason we don't have official SD-Card support. When you needed to access your files with USB Mass Storage, you had to disconnect your SD-Card from the rest of the Android system first. Since in the latest crop of HC devices, "/sdcard" is really just a mount-point on the internal storage (and presumably some apps/services require it to be there at all times) they aren't just disconnecting it any more. Since MTP works on the file-level, you can have simultaneous access and no disconnection of the storage is necessary.

I don't like it either (esp. since MTP hasn't ever worked reliably for me on Linux, so I use "adb push/pull") but I can understand the reasoning behind it.

 

[Crimton]

i think mass storage is coming soon in a kernel update so that may solve all our problems.

 

[kcrudup]

i think mass storage is coming soon in a kernel update so that may solve all our problems.

Maybe, maybe not. I've built a kernel with USB Mass Storage (preliminary) support, but I had to let it go as the "vold" storage manager in HC doesn't seem to be able to handle it (... properly?)

It'd be nice to have, but there's just no easy way to do it w/o disconnecting whereever the backing store is from the rest of Android, as USB MS can't do accesses at the file level.

 

[Crimton]

Maybe, maybe not. I've built a kernel with USB Mass Storage (preliminary) support, but I had to let it go as the "vold" storage manager in HC doesn't seem to be able to handle it (... properly?)

It'd be nice to have, but there's just no easy way to do it w/o disconnecting whereever the backing store is from the rest of Android, as USB MS can't do accesses at the file level.

Hmm, I was just going off of a comment bigrushdog made. I can at least mount my SD card in recovery, which for me is easier than booting into Windows. I will try this method again in 11.04 on a clean install.
Sent from my ADR6400L using XDA App

 

[kcrudup]

"adb" has recursive modes in push/pull- that's not good enough (for now, anyway)?

 

[Crimton]

"adb" has recursive modes in push/pull- that's not good enough (for now, anyway)?

theres a few other options including adb, but the simplicity of just using nautilus or a file manager is missed.

 

[dro1dfan]

Thanks so much for the guide. Hated having to boot into windows just to copy past files.

BTW, does the linux honeycomb sdk not include fastboot? (i thought it did)

 

[roberj13]

Yeah, I don't know why fastboot isn't included in the linux sdk when it is in the windows one.

Here is a link to one I made for me.

Ok, so it does still work on the internal storage to add and remove files, just make sure you unmount it when you disconnect otherwise Ubuntu gets confused what state it should be in when you plug it back in and you will have to restart. Still haven't figured out the external storage issue with not being able to change files, even though you can't see them.

 

[robcoch]

Ubuntu in a VM to solve Calibre sync issue?

Hi,
Currently Calibre cannot sync my ebooks from my Win 7 machine to the Xoom because there seems to be no way for it to access the Xoom.

I wonder if it might be possible to get around this issue by running a copy of Ubuntu in a virtual machine (virtualbox or Windows Virtual PC) and using virtualbox or VPC to create a UNC path/drive letter to the Xoom's file system -- or maybe I should just run a copy of Ubuntu under either of these VMs and install Calibre on Ubuntu and use the solution offered here so Calibre can access it. Seems like the latter might have fewer moving parts so perhaps a better chance of actually working...

Anyone have any thoughts about this and/or have you found anything that works? I figure either something will change on HC or the Xoom in upcoming months or the very clever developers of Calibre may have their own solution to the problem but would like to get this working better in the meantime.

Thanks,
rob

 

[sogrady]

Same problem here. This was working here, but an update seems to have broken it as I'm now getting the "Transport endpoint is not connected" error. Went back through all of it from the fstab to the udev rules and none of my changes had been backed out, so it has to be a changed/bad package.

 

[radiomike]

Same problem here. This was working here, but an update seems to have broken it as I'm now getting the "Transport endpoint is not connected" error. Went back through all of it from the fstab to the udev rules and none of my changes had been backed out, so it has to be a changed/bad package.

I was just having the same issue here. Checked all settings on ubuntu and all appeared fine.
Tried rythmbox - it was able to see device and access media on it.
Tried Banshee - unable to see device or access media.

I'm running Natty and Xoom Wifi (mz604) having done an update from Maverick.

Did an lsusb and device was coming back with an id of 18d1. Which I believe is the bootloader id?

After some trial and error eventually turned on usb debugging and lsusb returned correct id. Plus mounted correctly at /media/xoom with no errors