Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Using ADB shell to view my Samsung Galaxy Tab 7+, I see a /mnt but no /mnt/sdcard/ where according to fable the photos taken by the camera should reside. Why would the sdcard directory not be there?

Does the Tab need to be in some special mode or adb need some special incantation?

I'm doing this from an Ubuntu 11.something Linux machine.

UPDATE: got a new clue. Normally adb works only when the tablet is off, but has USB plugged in. When I hold down the power button, the tablet starts up. First there's a Samsung logo. Eventually the splashy orange screen with the lock-circle thing appears.

During the Samsung logo phase, adb shell will show stuff in /mnt, including the lusted-for /mnt/sdcard. But as soon as the orange lock screen appears (maybe slight sooner) adb is booted out, suddenly exiting to the xterm command line, and adb devices shows question marks instead of the device number.

So maybe all I need to do is find a way to make the tablet stay in Samsung-logo mode indefinitely, long enough for me to do my transfer.

share|improve this question
Isn't it mounted at sdcard/external- sd? Can you do an ls-l in /mnt in /sdcard and in / (the root)? – Richard Borcsik May 2 '12 at 6:53
Maybe it's just /sdcard – Flow May 2 '12 at 7:00
From what I read, external-sd is for actual physical sd cards. I don't have one. For the Galaxy Tab, /mnt/sdcard is a virtual card. My understanding is probably faulty, though. – DarenW May 2 '12 at 7:21
/sdcard is just a symlink to /mnt/sdcard, prolly as a convenience. – DarenW May 2 '12 at 7:22
It seems like the actual problem here has nothing to do with /mnt/sdcard not being there and everything to do with the fact that adb isn't seeing your device at all. The ?????? status usually implies you don't have udev rules set (or, generically, proper permissions for the usb device). I'd start with this Stack Overflow answer and see if that helps. – eldarerathis May 2 '12 at 13:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.