I have ask about USB host made by verygreen, i don t know where can i found the folder of my USB storage .I have try keyboard and mouse It s good.My sdcard reader Light on and a little external hard drive too but i don t know where search the file .
You need to mount it yourself in terminal. Look at the original thread...should have info in there.
I found the command mount dev/block/sda1 /mnt/somewhere but i have no sda in dev/block , should i write something in etc/vold.fstab . Thank for answer me yesterday
bretzelpopo said:
I found the command mount dev/block/sda1 /mnt/somewhere but i have no sda in dev/block , should i write something in etc/vold.fstab . Thank for answer me yesterday
Click to expand...
Click to collapse
it's mount /dev/block/sda1
not necessary sda1 too, do ls in /dev/block and see shad sdX do you have there.
or do dmesg and it'll tell you what device your usb device is known as.
thank for usb key it s good not my card reader .Will try other device thank
Related
I need to find a driver so i can plug my phone into my linux box and access the sd memory card. This is the machine that has all of the mp3 files. I don't need to sync or anything difficult, just transfer files.
Can someone point me to a driver please?
Maybe you just need to update your installation. Mine TP has worked in linux since I bought it a year ago. Using Ubuntu btw
I use Fedora Core 11. It's relatively new release and I keep it updated regularly. I'm not very good with Linux, but I like it better than MS. It's all the dependencies and line commands you have to do. I found this
http://linux.blogs2k.com/2009/02/21/...-ubuntu-linux/
but it doesn't help me at all. none of the commands work in Fedora. It's probably something simple (for linux gurus), but I'm too stupid to know what it is.
if you box will detect a memory stick it should detect the a phone with the usb manager installed on it. I had best luck with fedora as well. A side note is that there is a nice app made by pof on here that you can flash roms on linux as well
be sure you are selecting the usb connection as "data drive", are you on a stock rom?
otherwise
from a terminal do
Code:
lsusb
if you see the drive in the list (sandisk kingston etc..) then u should just need to mount it. i'm not the best on linux either, especially redhat, but i'm sure u can google a method to mount a usb drive. GL
You'll need an app like the built in 'Disk Drive' USB application or WM5torage. Once you have it in that mode, you can do the following:
Check your /dev/ folder for an item along the lines of 'sda1' or 'sdb1' that wasn't there before you plugged in the phone. Once you have it, you can create a folder, then:
sudo mount /dev/sdx1 /path/to/your/folder/
where /dev/sdx1 is your device and /path/to/your/folder is the folder you created.
Google 'mount usb flash drive linux' for more info.
ktemkin said:
Check your /dev/ folder for an item along the lines of 'sda1' or 'sdb1' that wasn't there before you plugged in the phone. Once you have it, you can create a folder, then:
Click to expand...
Click to collapse
or two other ways to find it by comparing output before and after plugin the phone :
fdisk -l
or
cat /proc/partitions
For accessing the storage, by default fedora mounts the device under /media/ I'll assume other "modern" distros are acting at the same way.
But a question regarding your SD card, is it encrypted ?
ubuntu hardy and jaunty working out of the box with storage mode
plug it in via usb and type dmesg at the command line
look for something like /dev/sdb /dev/sdb1 or something similar
this is your memory stick on the fuze make a mount point as root under /media like mkdir /media/fuze then
mount /dev/sdb /media/fuze
bingo bango
G'day folks.
I've edited this post to remove the seemingly unnecessary clutter and to make my question simpler.
Can it please be explained to me exactly how I format my external sdcard as ext2 in such a fashion that the phone recognizes it and mounts it? I've tried using Ubuntu to format it using:
Code:
mkfs.ext2 /dev/sdb
and also the inbuilt package manager, which seems to work fine under Linux and Windows, but the phone barfs with
SD card blank or unsupported file system.
Click to expand...
Click to collapse
I've also tried the busybox method:
Code:
busybox mkfs.ext2 /dev/block/mmcblk01
and get the following error
mke2fs: lseek: Value too large for defined data type
Click to expand...
Click to collapse
I'm running JPK and rooted with the latest Busybox. I have little idea about what I'm doing but am able to follow instructions, and have used Linux on occasions before.
Any help is much appreciated. Cheers !
EXT2 should work fine - you just need to either mount it yourself manually (to /mnt/sdcard/) or you can edit the vold.conf file, and set the filesystem type there. I haven't tried it, but it should work fine.
I'm unsure as to what device it's labelled under; any pointers? Taking a look at it now...
EDIT: Here's the contents of the vold.conf file:
Code:
## vold configuration file for the emulator/SDK
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/s3c-sdhci.0/mmc_host/mmc0
media_type mmc
mount_point /sdcard
## ums_path /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
ums_path /devices/platform/s3c-usbgadget/gadget/lun0
}
Why isn't the mount done automagically when the card is inserted or when the phone boots, like it does with FAT?
jezza333, this thread belongs in the Q&A section, not in development. Take a moment and read the "STOP, READ THIS BEFORE POSTING" thread at the top of both of these sections, it has clear guidelines for proper thread placement.
Whoops, apologies. I wasn't paying attention when I created the thread :/
exFAT might work better if you want to keep it easy to use with windoze base PCs
Yeah, but I don't know of any means to get the phone to read exFAT, apart from recompiling the kernel and including the exFAT driver. I'm happy enough with EXT2, but I need the phone to be able to mount/read it.
Bump, updated first post.
According to the modaco forum, simple
Code:
busybox mkfs.ext2
works. Personally I am waiting for my SGS-2, I'll try it immediately when it arrives.
tamas970 said:
According to the modaco forum, simple
Code:
busybox mkfs.ext2
works. Personally I am waiting for my SGS-2, I'll try it immediately when it arrives.
Click to expand...
Click to collapse
Hey-did you get the sdcard to work with ext2?I tried everything with formatting and such but couldn't get the Samsung galaxy s to recognize it correctly..could you create a step by step tutorial for me please? Thanks in advance!
Holy Thread Rebirthing
sup yall,
busybox mkfs.ext2 /dev/blcok/mmcblk1p1 (nook color) (iknow its wrong thread but only one i could found)
mkfs.ext2: lseek: Value too large for defined data type
what do
Hi, new here and I have a question:
I broke the screen on my Cappy and just got a replacement. The thing is, I hadn't moved all my pictures and movies (and various other things) to the external SD card. I've been searching for a way to retrieve them and it doesn't seem to look good.
I've tried on 2 other phones to get into CWM and mount the USB storage from there (Since hard keys are my only option) and it didn't work there (same model and mod) or when I tried on the bricked phone (6 menu options down, 2 up to mount sd card).
The question is this:
How can I through some way get all this data downloaded to my PC? Boot loader, download mode, recovery... I know just enough to do what I need to do to mod my phone, but not enough to know how to do this.
Any help would be appreciated! You guys have helped me so much by your informative posts I would be humbled for you to help me specifically.
Install adb
If you had usb debugging enabled you cab just boot up, if not recovery will communicate with adb regardless.
Adb pull /mnt/sdcard (where ever you want it to go on your PC)
studacris said:
Install adb
If you had usb debugging enabled you cab just boot up, if not recovery will communicate with adb regardless.
Adb pull /mnt/sdcard (where ever you want it to go on your PC)
Click to expand...
Click to collapse
The following happens when I try:
C:\> adb pull /mnt/sdcard c:/sd/
pull: building file list...
pull: /mnt/sdcard/lost.dir/28 -> c:/sd/lost.dir/28
cannot create 'c:\sd\lost.dir/28': No such file or directory
Nevermind. It should have been:
C:\> adb pull /mnt/sdcard c:\sd\
In windows, file locations use back slashes. you're telling it to go to c:/sd/
Should be c:\sd and no final backslash.
Hey guys I have a question for you all about sd-cards
I sbf'd
Installed ota 5.7.894 (because of no true .906 sbf I won't flash it)
Regained root
Installed busybox 1.20 (figured newer might be better)
Installed safestrap (tweaked of course 1.08f)
Now
My phone see's the internal/external sd-cards fine and mounts/formats/explores just fine
My laptop also see's internal/external sd-cards just fine
However
Rootbrowser cannot see the sd-card
Safestrap cannot find /sdcard
But
Root explorer can see the internal and external just fine
I have tried sbfing several times to see if it will fix it
I have tried not installing the ota,changing versions of busybox ect..
Why can my phone see and work with the sd-cards just fine but programs cannot?
Because safestrap cannot see the sd-card I cannot create backups..
Any help is greatly appreciated
I think Rick#2 acknowledged this in the safestrap 1.08f thread and had this advice for those experiencing the error:
(For the record, this change almost worked for me - safestrap would now access my external sdcard (/sdcard), but when I would select a zip to flash, it would just take me back to the menu. I dropped a reply with my results in that thread.)
Rick#2 said:
While you're in Safestrap, either go into the console or "adb shell" into your phone. (Remember that for adb to work properly in the recovery your phone has to boot up with the USB cable already connected).
If you type:
Code:
ls -l /dev/block | grep mmcblk0
what output does it provide? For me, it spits out "mmcblk0" but... I'm pretty sure that for those that aren't able to mount their external sdcards it will say mmcblk0p1. In which case, the fix is easy; I'll be sure to update my package, obviously, but for those of you who want to try a little DIY, copy the file /systemorig/etc/safestrap/recovery.zip onto your computer and unzip it. Inside, there's be a file called /etc/recovery.fstab; edit this and change the line corresponding to /sdcard (It ought to be on line 3, or the second line of actual text) to the following:
Code:
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
Click to expand...
Click to collapse
At this point, after copying the recovery.fstab back to my phone, I assumed I had to correct the permissions of the file, so I did. If I am wrong, someone please let me know!
continuing his reply...
Doesn't really matter how many spaces you have between; ideally you'll just need to hit tab each time.
Hopefully this is what the issue was. I remembered changing that line because I was getting random error messages about my external /sdcard and since I didn't see /dev/block/mmcblk0p1 in my /dev/block directory I assumed I must have made a typo and changed it... here's one tiny example of how easy it is to completely bork these things. Multiply it by a million and you have kernel development...
Click to expand...
Click to collapse
That might work if it was just safestrap having the issue..but its not
Even cwm cannot backup the apps on the sd-card as it cannot see it as well..
But root explorer and the stock file browser can see the internal/external sd-cards
And write on them just fine..and even mount/unmount and format...arrrggggg
This is killin me
Guys I just picked up one of those SanDisk dual OTG drive (Dual Ultra, 32 GB), and to my sheer shock I see that when I format the drive to FAT32 format the drive isn't being detected by my X, which is running on 4.4.4, rooted of course! If it's formatted in FAT32 it is being detected, but not with exFAT!
Now having a drive formatted in FAT32 is like having no drive for me because of the bloody file size limitation, so is there anything I can do?
I only have tried to mount it with an app called Stick Mount, and if I hit on mount, it's being mounted, but I can't see it via Solid Explorer or ES File Explorer, so I am guessing it's inaccessible somehow.
devilsdouble said:
Guys I just picked up one of those SanDisk dual OTG drive (Dual Ultra, 32 GB), and to my sheer shock I see that when I format the drive to FAT32 format the drive isn't being detected by my X, which is running on 4.4.4, rooted of course! If it's formatted in FAT32 it is being detected, but not with exFAT!
Now having a drive formatted in FAT32 is like having no drive for me because of the bloody file size limitation, so is there anything I can do?
I only have tried to mount it with an app called Stick Mount, and if I hit on mount, it's being mounted, but I can't see it via Solid Explorer or ES File Explorer, so I am guessing it's inaccessible somehow.
Click to expand...
Click to collapse
Using Stick Mount Pro on my X (4.4.2), 8 GB exFAT flash drive, it mounts to /sdcard/usbStorage/sda1 (/storage/sdcard0/usbStorage/sda1)
Did you read the following?
----- Filesystem support -----
The filesystems supported depends on your device firmware. On most devices, at least vfat/fat/fat32 and ext2/3/4 are supported. On the latest Android versions, ntfs is also supported in read-only mode. Some devices also support exfat out the box, but most do not.
StickMount can utilize the "ntfs-3g" and "mount.exfat-fuse" binaries to add support for ntfs (untested) and exfat, but these are not included. If you place the "ntfs-3g" or "mount.exfat-fuse" files in the root of your internal storage ( /sdcard ), StickMount will automatically use them.
You can find the needed files here:
ntfs-3g: http://forum.xda-developers.com/attachment.php?attachmentid=1145436&stc=1&d=1340293802
mount.exfat-fuse: http://forum.xda-developers.com/attachment.php?attachmentid=806200&d=1323109372
Click to expand...
Click to collapse
Check if you have those two files in /data/data/eu.chainfire.stickmount/:
/data/data/eu.chainfire.stickmount/mount.exfat-fuse (rwxr-xr-x)
/data/data/eu.chainfire.stickmount/ntfs-3g (rwxr-xr-x)
If those files do not exist there, download them and put them there or try to put them in /sdcard/:
/sdcard/mount.exfat-fuse
/sdcard/ntfs-3g
BTW, you will see a notification saying "Blank USB storage - USB storage is blank or has unsupported filesystem." However, you should also see a notification for "StickMount - Mass Storage device mounted."
This just means that the Moto X was unable to mount the exFAT drive on it's own, but Stick Mount can and did.
k_t_b said:
Using Stick Mount Pro on my X (4.4.2), 8 GB exFAT flash drive, it mounts to /sdcard/usbStorage/sda1 (/storage/sdcard0/usbStorage/sda1)
Did you read the following?
Check if you have those two files in /data/data/eu.chainfire.stickmount/:
/data/data/eu.chainfire.stickmount/mount.exfat-fuse (rwxr-xw-x)
/data/data/eu.chainfire.stickmount/ntfs-3g (rwxr-xw-x)
If those files do not exist there, download them and put them there or try to put them in /sdcard/:
/sdcard/mount.exfat-fuse
/sdcard/ntfs-3g
BTW, you will see a notification saying "Blank USB storage - USB storage is blank or has unsupported filesystem." However, you should also see a notification for "StickMount - Mass Storage device mounted."
This just means that the Moto X was unable to mount the exFAT drive on it's own, but Stick Mount can and did.
Click to expand...
Click to collapse
Thanks a lot mate. Well I do have those files under /data/data/eu.chainfire.stickmount/ fortunately
But those files are not in same permission like you mentioned, mine is -rwxr-xr-x, (please see the attached screenshot), while you mentioned rwxr-xw-x. So naturally if I am not wrong as mine is set as "r" it's a read-only file, and I can't write anything on it.
And I forgot all the Android things I had in my head, so I am feeling so dumb that I can't even change the permission to make it "w" from "r". So could you kindly remind me how to do that?
Just use that dumb tick / untick format so I can understand, like below
1 2 3
4 5 6
7 8 9
:laugh:
devilsdouble said:
Thanks a lot mate. Well I do have those files under /data/data/eu.chainfire.stickmount/ fortunately
But those files are not in same permission like you mentioned, mine is -rwxr-xr-x, (please see the attached screenshot), while you mentioned rwxr-xw-x. So naturally if I am not wrong as mine is set as "r" it's a read-only file, and I can't write anything on it.
And I forgot all the Android things I had in my head, so I am feeling so dumb that I can't even change the permission to make it "w" from "r". So could you kindly remind me how to do that?
Just use that dumb tick / untick format so I can understand, like below
1 2 3
4 5 6
7 8 9
:laugh:
Click to expand...
Click to collapse
Sorry to cause confusion. The permissions I posted contained typos. Yours look correct " -rwxr-xr-x".
/data/data/eu.chainfire.stickmount/mount.exfat-fuse (rwxr-xr-x)
/data/data/eu.chainfire.stickmount/ntfs-3g (rwxr-xr-x)
Just FYI, from a shell (terminal emulator on the phone):
[email protected]: / $ su
[email protected]: / # chmod 0755 /data/data/eu.chainfire.stickmount/mount.exfat-fuse
k_t_b said:
Sorry to cause confusion. The permissions I posted contained typos. Yours look correct " -rwxr-xr-x".
/data/data/eu.chainfire.stickmount/mount.exfat-fuse (rwxr-xr-x)
/data/data/eu.chainfire.stickmount/ntfs-3g (rwxr-xr-x)
Just FYI, from a shell (terminal emulator on the phone):
[email protected]: / $ su
[email protected]: / # chmod 0755 /data/data/eu.chainfire.stickmount/mount.exfat-fuse
Click to expand...
Click to collapse
Thanks. But this path is read only on my side, I can see stuffs but can't send or create or write anything
devilsdouble said:
Thanks. But this path is read only on my side, I can see stuffs but can't send or create or write anything
Click to expand...
Click to collapse
Interesting. I hadn't tried copying/writing anything to the drive from my phone. That's a bummer. I am using Root Explorer, but it looks like I have the same problem. Root Explorer thinks it has R/W, but fails to write every time. Perhaps there is a solution.
I got it working.
Download this app: https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Set SELinux mode to Permissive. You should then be able to write to the exFAT drive.
I recommend setting it back to Enforcing when you're done (or anytime when you're not needing to write to an exFAT drive).
Paragon NTFS would have worked as well.
nhizzat said:
Paragon NTFS would have worked as well.
Click to expand...
Click to collapse
Really?
"exFAT evaluation mode - for OEMs only"
k_t_b said:
I got it working.
Download this app: https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Set SELinux mode to Permissive. You should then be able to write to the exFAT drive.
I recommend setting it back to Enforcing when you're done (or anytime when you're not needing to write to an exFAT drive).
Click to expand...
Click to collapse
Thanks a lot mate. Finally it's working.
However I have had to format the drive as NTFS for some personal reasons and its working well for the intended purpose.
If I don't change the Linux permission back to Enforcing what problem might I face? I just don't care as long as its not affecting the performance of the device.
devilsdouble said:
Thanks a lot mate. Finally it's working.
However I have had to format the drive as NTFS for some personal reasons and its working well for the intended purpose.
If I don't change the Linux permission back to Enforcing what problem might I face? I just don't care as long as its not affecting the performance of the device.
Click to expand...
Click to collapse
Leaving SELinux set to permissive mode will not necessarily cause a problem for you. SELinux is supposed to enhance/enforce security and was added to Android 4.3 with permissive mode as default, but the default since Android 4.4 is enforcing mode.
You can read a bit more about it here.
http://www.xda-developers.com/android/easily-change-your-android-selinux-mode/
http://source.android.com/devices/tech/security/se-linux.html
k_t_b said:
Really?
"exFAT evaluation mode - for OEMs only"
Click to expand...
Click to collapse
Yup, it'll allow you to set SELinux to permissive within the settings even with that message displayed.
nhizzat said:
Yup, it'll allow you to set SELinux to permissive within the settings even with that message displayed.
Click to expand...
Click to collapse
Oh, I'm aware of that feature. I was just wondering if you found a way to mount exFAT using the Paragon app.
I liked that app when I tried it recently, but given that limitation I will just continue using StickMount.