Related
as you read the title when i try to use glossy themed version and the xdandroid version but i still get failed to mount sd card!
Try This: http://groups.google.com/group/beagleboard/browse_thread/thread/ef88a97aaef9116b?pli=1
hi everyone,I have the same problem that it can not "mount the sdcard"
then i search ,and found this :
"Add androidboot.console=ttySn to your kernel commandline, where n is
the number of your console serial port"
Could anyone plz tell me add it to where?
thanks a lot!!
help plzzzzzzzz
I read that ,but I can not understand it at all
"Add androidboot.console=ttySn to your kernel commandline, where n is
the number of your console serial port"
it is too difficult to fllow.add to where,and what is "n"???
Plz help!!
Mine is HTC Touch Pro/Raph with Android FRX04.
-> To add paramters to kernel I guess you would use the STARTUP.TXT and just add to the set cmdline " string.
Formatting with this util sdcard.org/consumers/formatter_3/ enabled my microSD card to be mounted in Android FRX04.
Thank you.
it seems you need to at.abraxas.mountusb to allow you to perform mount the sdcard...
im a noob so i dont get how to do this? I did search but nothing really answers my question?
savathtiv said:
im a noob so i dont get how to do this? I did search but nothing really answers my question?
Click to expand...
Click to collapse
You should be able to partition it in your custom recovery.
OR
Try using Ubuntu live CD and mount your sdcard.
Then partition it using GNOME Partition Editor.
Click me.
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.
Been trying to get this to work for hours, followed endless amounts of tutorials, I've hit a brick wall and am finally at the point I need to ask for more specific help.
I have 32gb Nexus 7 wifi only
Version: 4.2.1
Kernal: Motley's kernal 3.1.10-motley-v3+
Build Number:JOP40D
I started with CifsManager, couldn't get it to work because of no/wrong modules, tried many I found in tutorials around the net, eventually found I needed a new kernal, settled on Motley's, this finally allowed cifs to mount the folder, but the folder is always empty.
Came across Mount Manager, set it up, same problem.
Here's what my settings look like:
CifsManager:
Share Path: 192.168.1.18/y
Mount Point: /mnt/sdcard/cifs/pcY
Username: Comp1
Password: Password
Options: iocharset=utf8
I have tried it with options blank, same thing, yes my share is called y, Comp1 is the account I set up to access shares, no my password is not really password but you get the idea. I can access this share fine from other devices including my wii using the same settings.
Mount manager is basically the same except I made the mount point /compY because I didn't know if it would conflict, and it has file_mode and dir_mode = 0777.
Thank you for your time and any help is greatly appreciated.
Still searching for a solution, even a nudge in the right direction would help a lot right now.
I found out how chainfire solved this problem. (And did not said how ) I think my thread got lost ist the Android General section.... I should have posted it in the Nexus 7 General. (I tested it on my Nexus 7)
http://forum.xda-developers.com/showthread.php?t=2062768
vorcers said:
I found out how chainfire solved this problem. (And did not said how ) I think my thread got lost ist the Android General section.... I should have posted it in the Nexus 7 General. (I tested it on my Nexus 7)
http://forum.xda-developers.com/showthread.php?t=2062768
Click to expand...
Click to collapse
Thank you very much for your reply.
I am very new to this, I can't quite follow what I am supposed to do, I think start the file debuggerd as a system service? I can find the file, but I can't find out how to start it, I've done a few searches on this site and google but have come up empty, could you please explain exactly what I need to do to make this solution work?
Thanks again for your help
(For germans: "Bitte nagelt mich nicht darauf fest" (Auf die Informationen) Sorry, I don't know the english phrase for this...)
The "debuggerd" is an "debugger daemon". It can be started with "start debuggerd" and stopped with "stop debuggerd". I think errors at excecution are posted in dmesg or logcat.
The main thought behind this, that the debuggerd is started by "start" with higher privileges even then our normal su. (Or it does mount something, I don't know) So, if you backup the original /system/bin/debuggerd and write your own commands into that file and start it via "start debuggerd" these commands are executed with these "high privileges". For example, if you write these content in debuggerd and start it, the share should be available for all apps. (Well, only if "others" have r (? wx ?) permissions on server...)
/system/bin/debuggerd
Code:
#!/bin/sh
busybox mount -t cifs //server/share /mnt/sdcard/mnt -o username=max,password=mustermann)
You can also mount devices with this method...
Well, you can't use this with the manager, because the manager needs to be changed to support this.
I hope this helps you.
You can turn on your "ADB over network".Then you con connect from your device with
adb connect 127.0.0.1:5555
Click to expand...
Click to collapse
now youre ready to mount but the foders are visable only in the apps that are been started befour mount can see the folder.
Tornadough said:
Still searching for a solution, even a nudge in the right direction would help a lot right now.
Click to expand...
Click to collapse
Here's a solution that can be implemented by ROMs or kernels to fix app mount support in Android 4.2 without requiring modifications to CifsManager or other apps.
I'd recommend asking your favorite ROM to incorporate the dalvik/init.rc patches.
vorcers said:
The main thought behind this, that the debuggerd is started by "start" with higher privileges even then our normal su.
Click to expand...
Click to collapse
What's happening is that the debuggerd process is spawned directly by init, which uses the default mount namespace, so any mount operations are shared with/visible to all other processes.
The problem is that when an app calls "su" to mount a file system, it's already walled off in a separate mount namespace by virtue of the app itself having been spawned from zygote. Basically, any process whose ancestry can be traced back to zygote can't mount file systems visible to other apps. Those whose process ancestry don't include zygote can. Which is why manually mounting file systems from adb (with either "su" or "adb root") also works.
After all this time nobody has updated any app to fix this problem?