Hello,
Just got my new TF and thanks to XDA I've already rooted it and installed rom Prime 1.4 to get a rooted 3.1 android version.
Everything goes fine except for mapping network shares. Mounting network shares with cifs manager is ok except that I'm French so some directories in my network got unicode characters and I can't mount them.
Does anyone know how to bypass this limitation ?
On my understanding, I should install a cifs.ko module compiled for the TF and the 3.1 Android version in /system/lib/modules but I don't know where to find such module.
Thanks in advance
Try es strongs file explorer. It allows you to add network shares.
Sent from my Transformer TF101 using XDA Premium App
Thanks, but I've already done it without success.
The issue is not to map a share, this is working. The real issue is that share with unicode characters (like é, è, à...) are not working.
Thanks anyway
Im also rooted with prime 1.4 buf cant get any shared volume to mount via cifs manager. What am i missing here?
Have you tried adding 'iocharset=utf8' to the mount point options?
Don't know if this can help you or not, but my 1st mistake with cifs manager when I tried it fist time was that I haven't put anything on mount point.
What you need on the fields of cifs manager is:
Share Path: The path to your share ==> ex: 192.168.1.5/share (this is the shared dir on your server)
Mount point: The name of the "false" directory that will simulate that your share is on your tablet ==> ex: /sdcard/cifs/share (this is up to you but keep close to this)
Plus of course username and password (I thinks that anonymous connection is not allowed anyway)
Hope this help
Tortel1210 said:
Have you tried adding 'iocharset=utf8' to the mount point options?
Click to expand...
Click to collapse
I don't know how I can do that. Is it an argument to parse in a field of cifs manager ? If so how should I do that ?
Can you help me with this please.
XPNect said:
I don't know how I can do that. Is it an argument to parse in a field of cifs manager ? If so how should I do that ?
Can you help me with this please.
Click to expand...
Click to collapse
If you edit the settings for a mount point (Long press on it, then choose edit), there is an options text field at the bottom. Put it in there, save, and try mounting it.
XPNect said:
Don't know if this can help you or not, but my 1st mistake with cifs manager when I tried it fist time was that I haven't put anything on mount point.
What you need on the fields of cifs manager is:
Share Path: The path to your share ==> ex: 192.168.1.5/share (this is the shared dir on your server)
Mount point: The name of the "false" directory that will simulate that your share is on your tablet ==> ex: /sdcard/cifs/share (this is up to you but keep close to this)
Plus of course username and password (I thinks that anonymous connection is not allowed anyway)
Hope this help
Click to expand...
Click to collapse
Thanks!!! Dont know how or why but now it works!
Tortel1210 said:
If you edit the settings for a mount point (Long press on it, then choose edit), there is an options text field at the bottom. Put it in there, save, and try mounting it.
Click to expand...
Click to collapse
It works fine a big thanks.
I've been abused by the comment and I was thinking that this box was only for a domain name... feel stupid sometime
Is it possible for someone with Linux experience to compile a cifs kernel module for use with the stock 4.0.3 kernel? I would like to be able to mount smb shares and know nothing of Linux compilation ...obviously I am rooted......and also, why doesn't a business class device come with cifs support? Lenovo...I'm looking at you....
Thanks to anyone who may help our with insight on this issue.
lmbea4 said:
Is it possible for someone with Linux experience to compile a cifs kernel module for use with the stock 4.0.3 kernel? I would like to be able to mount smb shares and know nothing of Linux compilation ...obviously I am rooted......and also, why doesn't a business class device come with cifs support? Lenovo...I'm looking at you....
Thanks to anyone who may help our with insight on this issue.
Click to expand...
Click to collapse
Here it is. Compiled from the official Lenovo ICS sources. Needed to setup my build system anyway.
Edit:
If it doesn't work please post your precise kernel-version (setting->info) with all the characters and numbers and everything.
(exec format error)
I tried the file you made, placed it in the /system/lib/modules directory...Insmod /system/lib/modules/cifs.ko and got the (exec format error) ...am I doing something wrong...and also, thank you so much for helping! Awesome work
2.6.39.4-g9b8008b-dirty
[email protected]#1
lmbea4 said:
I tried the file you made, placed it in the /system/lib/modules directory...Insmod /system/lib/modules/cifs.ko and got the (exec format error) ...am I doing something wrong...and also, thank you so much for helping! Awesome work
2.6.39.4-g9b8008b-dirty
[email protected]#1
Click to expand...
Click to collapse
Next try. If it doesn't work this time please post the last lines of dmesg
yes...but
Yes! the new module loads wonderfully ....now as for getting cifs manager to work,I keep getting "mount: no such file or directory" ...and yes I have the latest busybox, and yes I made the mount point rw...strange....also I noticed that other kernel modules have the cifs.ko and a md4.ko...could the problem lie in not having a md4.ko? Also, you are awesome at this, thank you so much for your continued help!
What I'm trying to accomplish
I'm trying to get the Cifs Manager application to function on my thinkpad tablet. I thought it might help to give out that information so you can see where I'm heading with all of this. Thanks again
lmbea4 said:
I'm trying to get the Cifs Manager application to function on my thinkpad tablet. I thought it might help to give out that information so you can see where I'm heading with all of this. Thanks again
Click to expand...
Click to collapse
A logcat might tell you whats wrong. Try to start searching there, most times its something simple.
Edit: You might be right, a md4.ko seems to be necessary. Will build it as soon as i find out what md4 exactly is.
Edit2: And here it is. Its a crypto module.
awesome!!
That did the trick, cifs manager works great now!! Thank you so much!
lmbea4 said:
That did the trick, cifs manager works great now!! Thank you so much!
Click to expand...
Click to collapse
Hi, could you share your process to mount cifs on thinkpad tablet? I have followed on one tutorial on thinkpadtabletforums. But failed unfortunately. Could you give me a hint? Thanks in advance!
cifs manager
kpf190 said:
Hi, could you share your process to mount cifs on thinkpad tablet? I have followed on one tutorial on thinkpadtabletforums. But failed unfortunately. Could you give me a hint? Thanks in advance!
Click to expand...
Click to collapse
Sure, first download the cifs manager from the play store. (none of this works of you don't have root). then download the two files (in one zip file,2 posts up) and place the two files in the system/lib/modules/ directory. now, open the cifs manager app and go to settings. you need to check the "use insmod" and then in the option below that you need to put /system/lib/modules/cifs.ko:/system/lib/modules/md4.ko that whole thing, no spaces, the : will make it run the second command which is a required modules for the cifs one to work.
good luck
lmbea4 said:
Sure, first download the cifs manager from the play store. (none of this works of you don't have root). then download the two files (in one zip file,2 posts up) and place the two files in the system/lib/modules/ directory. now, open the cifs manager app and go to settings. you need to check the "use insmod" and then in the option below that you need to put /system/lib/modules/cifs.ko:/system/lib/modules/md4.ko that whole thing, no spaces, the : will make it run the second command which is a required modules for the cifs one to work.
good luck
Click to expand...
Click to collapse
Noted and tried but still get msg as "mount: No such device".
I think I have no luck with CIFS...
Thanks Koshu and all. Mounted my NAS shares with no problems.
Hi guys,
Do any of you have successful solution to mount cifs shares with ANY kernel available? I've tried to do it with Project Flaming Monkey kernel, but had no luck. Most of the time I got "device not authorized" error when tried to mount via adb shell. But even if I could overcome this error (didn't figure out exact sequence of steps) it always says that mounting failed or even gets segfault.
With KTmanta kernel device is always authorized, I get root credentials immediately, but mounting also fails. Later I discovered that mounting actually happens and I can see it via adb shell, but it's invisible for all other users including root. Does it mean that 'mount using adb shell' trick doesn't work anymore?
Anyway I'll be very grateful for any kind of working solution or direction where to get it. Thanks in advance.
P.S. interesting but StickMount just works even on stock kernel that is said to have module loading disabled.
Sent from my Nexus 10 using xda app-developers app
uentity said:
Hi guys,
Do any of you have successful solution to mount cifs shares with ANY kernel available? I've tried to do it with Project Flaming Monkey kernel, but had no luck. Most of the time I got "device not authorized" error when tried to mount via adb shell. But even if I could overcome this error (didn't figure out exact sequence of steps) it always says that mounting failed or even gets segfault.
With KTmanta kernel device is always authorized, I get root credentials immediately, but mounting also fails. Later I discovered that mounting actually happens and I can see it via adb shell, but it's invisible for all other users including root. Does it mean that 'mount using adb shell' trick doesn't work anymore?
Anyway I'll be very grateful for any kind of working solution or direction where to get it. Thanks in advance.
P.S. interesting but StickMount just works even on stock kernel that is said to have module loading disabled.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
CM 10.2 plus Trinity Kernel plus Mount Manager works
I didn't yet tried trinity kernel
Thanks for the reply!
I think that kernel actually affects mounting process and not the ROM. Didn't tried trinity kernel yet, because author said that it's not feature complete for 4.3.
Do you have any issues with it? Everything works fine?
Sent from my Nexus 10 using xda app-developers app
uentity said:
I didn't yet tried trinity kernel
Thanks for the reply!
I think that kernel actually affects mounting process and not the ROM. Didn't tried trinity kernel yet, because author said that it's not feature complete for 4.3.
Do you have any issues with it? Everything works fine?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Running the kernel version TX10, I have had some rare forced close issues, but i have no idea if it is kernel- or rom-related, propably the latter. Other than that it works just as well as any 4.2 combo I had before. Some kinks here and there, but perfectly usable.
I use Trinity with any 4.3 ROM and a script to mount my home file share. Works great.
I'm running 4.3 and Trinity kernel (tx17), I'm able to mount the cifs share from adb shell, I see the data there, but it's not available for the apps on the tablet. I also tried mounting the share using mount manager but it didn't help. I see it as a mounted, but no apps can see the data.
Where (mountpoint) and how should you mount the cifs share so it's visible for the rest of apps as well? Thx.
slano said:
I'm running 4.3 and Trinity kernel (tx17), I'm able to mount the cifs share from adb shell, I see the data there, but it's not available for the apps on the tablet. I also tried mounting the share using mount manager but it didn't help. I see it as a mounted, but no apps can see the data.
Where (mountpoint) and how should you mount the cifs share so it's visible for the rest of apps as well? Thx.
Click to expand...
Click to collapse
I remember having this problem, but I don't remember how I fixed it. Here's my script, compare it to yours to see if there's any difference. The below is all one line;
busybox mount -t cifs -o username=tv,password=<your_password>,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.1.101\\files //192.168.1.101/files /data/media/0/TV-PC
I seem to remember it having something to do with mounting to /data/media/(whatever) or the uid/gid.
sttovo said:
I remember having this problem, but I don't remember how I fixed it. Here's my script, compare it to yours to see if there's any difference. The below is all one line;
busybox mount -t cifs -o username=tv,password=<your_password>,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.1.101\\files //192.168.1.101/files /data/media/0/TV-PC
I seem to remember it having something to do with mounting to /data/media/(whatever) or the uid/gid.
Click to expand...
Click to collapse
Did try all possible combinations but still no luck. I've changed rom to Flaming Monkey and everything works like a charm there, so I'll probably stick with it for a while.
slano said:
Did try all possible combinations but still no luck. I've changed rom to Flaming Monkey and everything works like a charm there, so I'll probably stick with it for a while.
Click to expand...
Click to collapse
So to confirm, you did get cifs working with project flaming monkey rom or that's just the Rom you settled with since cifs never worked anyway? Did you use trinity kernel tx17? That's currently the combo I have and for the life of me cannot get it to work..... I am just learning about this so I'm sure it's me but if I know I have the same combo as someone who got it working, I will keep trying.
c683 said:
So to confirm, you did get cifs working with project flaming monkey rom or that's just the Rom you settled with since cifs never worked anyway? Did you use trinity kernel tx17? That's currently the combo I have and for the life of me cannot get it to work..... I am just learning about this so I'm sure it's me but if I know I have the same combo as someone who got it working, I will keep trying.
Click to expand...
Click to collapse
I've tried stock ROM with the Trinity kernel but no luck. I was able to mount the cifs filesystem, but it was not accessible for other apps. I've switched to Flaming monkey and everything mounted and was available just fine.
What is your problem with the current set-up? Will the share mount ok but it's not accessible from other apps or are you not able to perform the mount at all?
slano said:
I've tried stock ROM with the Trinity kernel but no luck. I was able to mount the cifs filesystem, but it was not accessible for other apps. I've switched to Flaming monkey and everything mounted and was available just fine.
What is your problem with the current set-up? Will the share mount ok but it's not accessible from other apps or are you not able to perform the mount at all?
Click to expand...
Click to collapse
Thanks for the reply. I have tried to use 3 different ways, below is a brief summary:
- CIFS Manager - No matter what I do, I get an "Invalid Argument" or "directory cant be found" error. Read and tried what is listed in CIFS FAQ to no avail.
- Mount Manger - Shows as connected, but there are no files; not in any apps or in the directory when using a file browser (root explorer or ES)
- Script - Yeah, just copied the script a few posts back and modified based on what I thought I needed to and used terminal emulator, gave it a go but nothing happens. Really don't know what I am doing with regard to script, over my head...
I also read that modules are needed but I thought the the trinity kernel already had them...
I am running the latest flaming monkey rom and trinity kernel on my nexus 10. So in short I really don't know exactly what I am doing but I will keep trying since I know you got it working with the same ROM and kernel setup. I can also access the files on my shared files through ES file explorer when I use the LAN or server feature so I know the PC is at least setup correctly, I think...
I haven't tried it on 4.3 yet. But the "Invalid argument" error is a problem in Linux kernels 3.4 in general. Take a look here:
How to Troubleshoot CIFS Problems on Android and Linux in General
I encountered that problem ever since JB. The problem is that mount is usually used in this way:
Code:
mount -o username=youruser,password=yourpasswd -t cifs //ipofpc/shareonpc dironphone
But that does not work in kernel 3.4. The share-directory as a device name is ignored. It has to be specified with argument unc. Like this:
Code:
mount -o unc=\\\\ipofpc\\shareonpc,username=youruser,password=yourpasswd -t cifs none dironphone
Note: since backslash is an escape character the double \\ is needed instead of \. It's also a good idea to specify noperm if you want the mounted directory to be accessible by all apps. Otherwise the mounted directory might only be accessible by root on the phone.
So a working example looks like this:
Code:
mount -o noperm,unc=\\\\10.0.0.200\\Public,username=guest,password=secret -t cifs none /sdcard/shares/nas
You have to work around that problem in CifsManager. Enter it like this:
Share Path: Enter anything. It will be ignored.
Mount Point: directory on phone: e.g. /sdcard/shares/nas
Username: enter user name
Password: leave empty
Options: e.g. noperm,unc=\\\\10.0.0.200\\Public,password=secret
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gwodus said:
I haven't tried it on 4.3 yet. But the "Invalid argument" error is a problem in Linux kernels 3.4 in general. Take a look here:
How to Troubleshoot CIFS Problems on Android and Linux in General
I encountered that problem ever since JB. The problem is that mount is usually used in this way:
Code:
mount -o username=youruser,password=yourpasswd -t cifs //ipofpc/shareonpc dironphone
But that does not work in kernel 3.4. The share-directory as a device name is ignored. It has to be specified with argument unc. Like this:
Code:
mount -o unc=\\\\ipofpc\\shareonpc,username=youruser,password=yourpasswd -t cifs none dironphone
Note: since backslash is an escape character the double \\ is needed instead of \. It's also a good idea to specify noperm if you want the mounted directory to be accessible by all apps. Otherwise the mounted directory might only be accessible by root on the phone.
So a working example looks like this:
Code:
mount -o noperm,unc=\\\\10.0.0.200\\Public,username=guest,password=secret -t cifs none /sdcard/shares/nas
You have to work around that problem in CifsManager. Enter it like this:
Share Path: Enter anything. It will be ignored.
Mount Point: directory on phone: e.g. /sdcard/shares/nas
Username: enter user name
Password: leave empty
Options: e.g. noperm,unc=\\\\10.0.0.200\\Public,password=secret
Click to expand...
Click to collapse
Thank you for the detailed response, I will give that a try.
Sent from my Nexus 10 using xda app-developers app
c683 said:
Thank you for the detailed response, I will give that a try.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
BTW. I forgot. Before you try anything. Check if the directory /proc/fs/cifs exists. If it doesn't, then you are missing the required cifs kernel module. But more often then not, the kernel module is there and the problem is elsewhere.
gwodus said:
BTW. I forgot. Before you try anything. Check if the directory /proc/fs/cifs exists. If it doesn't, then you are missing the required cifs kernel module. But more often then not, the kernel module is there and the problem is elsewhere.
Click to expand...
Click to collapse
Thank you for your help. I thought for sure I tried what you said in your last post before as I read something similar. However, the info was wrong or I screwed up because when I followed your detailed description, it worked! The weird thing is some files open and others I'll get "the file doesn't exist error" but I am not concerned with it since I can get what I need. Thanks again.
c683 said:
Thank you for your help. I thought for sure I tried what you said in your last post before as I read something similar. However, the info was wrong or I screwed up because when I followed your detailed description, it worked! The weird thing is some files open and others I'll get "the file doesn't exist error" but I am not concerned with it since I can get what I need. Thanks again.
Click to expand...
Click to collapse
Awesome. You got it working!
I never ran across the "file doesn't exist" error. But I read around here that other people have such troubles too. It's probably a permission problem. Maybe try to play around with options like gid, forceuid, file_mode and dir_mode. A complete list of options is here: mount.cifs man page
gwodus said:
I haven't tried it on 4.3 yet. But the "Invalid argument" error is a problem in Linux kernels 3.4 in general. Take a look here:
How to Troubleshoot CIFS Problems on Android and Linux in General
I encountered that problem ever since JB. The problem is that mount is usually used in this way:
Code:
mount -o username=youruser,password=yourpasswd -t cifs //ipofpc/shareonpc dironphone
But that does not work in kernel 3.4. The share-directory as a device name is ignored. It has to be specified with argument unc. Like this:
Code:
mount -o unc=\\\\ipofpc\\shareonpc,username=youruser,password=yourpasswd -t cifs none dironphone
Note: since backslash is an escape character the double \\ is needed instead of \. It's also a good idea to specify noperm if you want the mounted directory to be accessible by all apps. Otherwise the mounted directory might only be accessible by root on the phone.
So a working example looks like this:
Code:
mount -o noperm,unc=\\\\10.0.0.200\\Public,username=guest,password=secret -t cifs none /sdcard/shares/nas
You have to work around that problem in CifsManager. Enter it like this:
Share Path: Enter anything. It will be ignored.
Mount Point: directory on phone: e.g. /sdcard/shares/nas
Username: enter user name
Password: leave empty
Options: e.g. noperm,unc=\\\\10.0.0.200\\Public,password=secret
Click to expand...
Click to collapse
I tried your solution (4.4, Nexus 5) and it actually mounts the volume correctly. The only problem is that mounted content is visibile only if you're root: i can't see the folders mounted from the applications even if the cifsmanager say it has been mounted.
I verified by mounting the volume via ADB and navigated to the mounted folder -> root can see the folder and normal user can't.
I also tried adding the parameters "rw,file_mode=0777,dir_mode=0777,nounix,iocharset=utf8", nothing.
Do you know something about this?
Same problem here on 4.4 N4
Sent from my Nexus 4 using Tapatalk 2
root only problem
ludalex07 said:
I tried your solution (4.4, Nexus 5) and it actually mounts the volume correctly. The only problem is that mounted content is visibile only if you're root: i can't see the folders mounted from the applications even if the cifsmanager say it has been mounted.
Click to expand...
Click to collapse
i've got the same issue on nexus 7 (new) running 4.3
here is my mount command:
mount -o noperm,unc=\\\\192.168.2.16\\Volume_2,username=guest,password=guest -t cifs musiq /sdcard/NAS
root only can see it.
from google groups, someone seems to have a workaraound, but i can not firgure out excactly what he means:
"when I mount using a shell-script (masked as a system-service like /system/bin/debuggerd) with "/system/bin/start" the mount is visible systemwide"
i tried replacing debuggerd with a script, but it is not part of the start-up services, so i am guessing /system/bin/start has to be invoked somehow?
noktilux said:
i've got the same issue on nexus 7 (new) running 4.3
here is my mount command:
mount -o noperm,unc=\\\\192.168.2.16\\Volume_2,username=guest,password=guest -t cifs musiq /sdcard/NAS
root only can see it.
from google groups, someone seems to have a workaraound, but i can not firgure out excactly what he means:
"when I mount using a shell-script (masked as a system-service like /system/bin/debuggerd) with "/system/bin/start" the mount is visible systemwide"
i tried replacing debuggerd with a script, but it is not part of the start-up services, so i am guessing /system/bin/start has to be invoked somehow?
Click to expand...
Click to collapse
The debugger method is described here: http://forum.xda-developers.com/showpost.php?p=37751808&postcount=55
Not sure it will work on 4.3, but you can give it a try.