Have you option.ko and usb_wwan.ko modules for this 3.4.5 kernel? For modem 3g huawei...
Added option.ko and usb_wwan.ko, also usbserial.ko that seems to be needed.
insmod usbseria.ko then usb_wwan.ko and option.ko last
Thank you. After insmod, if i reboot tablet is necesary repeat the proceso? Or only once. Changes any system file and i Will have problems With OTA?
Quick question all - (sorry an Android Noob here who's spent way too many hours reading through XDA since the Nexus 10 Purchase!
Mounting CIFs shares in this manner are you then seeing transfer speeds that the nexus 10 is capable of over Wifi? I've been trying to get the 80-90mbps through CIFs shares that I get from Iperf tests but all File Explorers only give me 20mbps which obviously isn't great for HD Video.
Just wanted to throw it out there to see what kind of bandwidth people are getting using this solution. Cheers!
Hi all !
I've a problem...
I mounted it correctly (i think...), i mean i can see my files/folders under my mount point in connecbot.
But i don't see anything with solid explorer or es file explorer...
I tried to mount it in different places...same...
I don't understand why !
So it's unusable by third party apps
Did i miss something ??
Thanks for your help !
I get an error with the shell script you posted. Line 54; syntax error: 'if' unmatched'
i used the script method...
other thing....
under cm 10, i get this error when i load modules :
u0_a69@android:/ # insmod /system/lib/modules/cifs.ko
insmod: init_module '/system/lib/modules/cifs.ko' failed (Exec format error)
255|u0_a69@android:/ #
I;m getting the same exact error. I copied the script to notepad, modified the parameters, saved as mountcifs.sh and tried to run it from terminal emulator and got the same errors. When I vi my script it has all these ^M carriage return characters that I think Windows/Notepad adds to the file. Whats the proper way to copy the script and get in on the device to avoid these errors?
CyanogenMod 10? These modules are specific for the kernel version that ships with the stock Nexus 10 JellyBean 4.2.x. You will need to find CIFS modules for your CM10 kernel. It would be nice if the CyanogenMod guys compiled cifs modules by default but for some reason they don't.
[cut]
Interesting. I'm following this thread as a Nexus 7 user. I'm wondering if it's worth trying this on a Nexus 7 running the stock ROM. The only thing I can think of that might cause it to not work is the patched /system/lib/libdvm.so. Any thoughts on that? If it's not a show stopper, then I'm willing to try and report my results. I'll never use the multi-user aspect of 4.2.x, so I don't care about losing that either. And it's easy enough to go back to 4.1.2 and bide my time, if this fails. Just don't want to waste my time if the patched library won't work on a Nexus 7.Okay, here's an experiment...
Attached is a flashable zip that does the following:
1) replaces /system/xbin/busybox with a version that has the unc fixup patch (for roms that don't already include it).
2) removes existing symlink /system/bin/mount and recreates it pointing to /system/xbin/mount so that the default "mount" uses the fixed version.
3) installs a patched /system/lib/libdvm.so dalvik library that has had removed the unshare() call that is partitioning the mount namespace and making cifs mounts invisible to other processes (unless you do hack around adb shell etc).
Use at your own risk and I'd certainly recommend ensuring you have your current rom available for reflashing if anything goes wrong... However, for me, with stock cm I can now simply flash this and then cifsmanager works as it always did previously without any other hackery whatsoever.
I can't see why this wouldn't work for any rom (certainly stock and cm should be good). The only thing you need to ensure is that you have the cifs module for your rom already installed.
Final note: this is a dirty hack because it entirely destroys the per user mount namespace separation feature. That said, I only have one user account on my tablet so my personal care level is zero.
Let me know if it works for you.
#!/system/bin/sh
# Your settings here
USERNAME="USERNAME"
PASSWORD="PASSWORD"
IPADDRESS="192.168.1.1"
SHARE="storage"
MOUNT_POINT="/data/media/0/cifs/Storage"
# If you need to change the mount command edit this
MOUNT_CMD="\
mount -t cifs \
\
-o \
user=$USERNAME,\
password=$PASSWORD,\
unc=\\\\\\\\\\\\\\\\$IPADDRESS\\\\\\\\$SHARE \
\
//$IPADDRESS/$SHARE \
$MOUNT_POINT"
COMMANDS="\
insmod /system/lib/modules/md4.ko; \
insmod /system/lib/modules/nls_utf8.ko; \
insmod /system/lib/modules/cifs.ko; \
$MOUNT_CMD
"
# Starting ADB...
PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port 5555
adb kill-server
adb start-server
stop adbd
start adbd
adb connect localhost
# Make sure we only use the first device (sometimes there is more than one)
SERIAL=`adb devices | head -n2 | tail -n1 | cut -f1`
if [ "$SERIAL" = "" ] ; then
echo "ERROR: Could not find ADB device.";
fi
echo Mounting share via adb...
adb -s $SERIAL shell su root -c "$COMMANDS"
# If you started adb, then stop it here for security:
adb disconnect localhost
stop adbd
setprop service.adb.tcp.port $PORT
start adbd
RESULT=`mount | grep $MOUNT_POINT`
if [ "$RESULT" = "" ] ; then
echo "Mounting failed..."
else
echo "Mounting sucess!"
fi
echo Done... You may close this script window.
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
Quick question all - (sorry an Android Noob here who's spent way too many hours reading through XDA since the Nexus 10 Purchase!
Mounting CIFs shares in this manner are you then seeing transfer speeds that the nexus 10 is capable of over Wifi? I've been trying to get the 80-90mbps through CIFs shares that I get from Iperf tests but all File Explorers only give me 20mbps which obviously isn't great for HD Video.
Just wanted to throw it out there to see what kind of bandwidth people are getting using this solution. Cheers!
Remove the word "root" from line: adb -s $SERIAL shell su root -c "$COMMANDS"
I also changed the "mount" command by "busybox mount" (I didn't make the hardlink as recommended in some posts)
That was driving me nuts. Everytime I executed the script I saw "SuperSU - Copyright [...] Chainfire" message until I removed the "root". Now it all works flawlessly. I guess this may be happening because of the superuser binary version I have installed.
Merry Xmas.