Hey Guys,
Just wanted to share with you the CIFS-Module I build some days ago.
Maybe someone can use it.
You can copy the Module wherever you want and then let it load automatically by an APP.
For example with Mount Manager
Or you can load it manually by:
Code:
su
insmod /path/to/module/cifs.ko
Mounting has to be done in Terminal with unc, because the "normal" way isn't working:
Code:
su
mount -t cifs -o unc=\\\\10.0.0.200\\Public,username=guest,password=guest none /sdcard/shares/nas
Unfortunately, since JB Android doesn't make mounts made by root visible for other users.
So even if you mount via Terminal or with Mount Manager, you won't see anything as normal user.
You can see them only as root.
I found a website, where someone is explaining this issue:
http://www.netzgewitter.com/2013/10/troubleshoot-cifs-on-android/
Unforunately, the last Workaround of this Website, which should make mounts visible for normal users, doesn't work for me. Maybe because of some Syntax-Errors I can't find out.
Code:
su -c setenforce 0 && su --mount-master -c mount -o unc=\\\\192.168.1.139\\data,username=kenneth,password=mypassword,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs none /sdcard/cifs/Data
-
Thank you McBane87 ! It worked on my TabletZ
I also managed to make it visible for nonrooted apps.
The (unc=\\\\ ...) part should be enclosed in single quotes for some reason.
Code:
su -c setenforce 0 && su --mount-master -c mount -o 'unc=\\\\192.168.1.139\\data,username=user,password=pass,rw,iocharset=utf8' -t cifs none /sdcard/cifs/Data
onoz1234 said:
Thank you McBane87 ! It worked on my TabletZ
I also managed to make it visible for nonrooted apps.
The (unc=\\\\ ...) part should be enclosed in single quotes for some reason.
Code:
su -c setenforce 0 && su --mount-master -c mount -o 'unc=\\\\192.168.1.139\\data,username=user,password=pass,rw,iocharset=utf8' -t cifs none /sdcard/cifs/Data
Click to expand...
Click to collapse
Thanks.
Tried it with double quotes before and that didn't worked.
But with single quotes it does
@McBane87 could you compile md4 and nls_utf8 ? In polish language many words contains diacritical mark as ą,ć,ź so couldn't be properly mounted.
The best way would be port 'Remote Shares' function from z1-z4 series.
Edit.
Just realised that's working (without nls_utf8.ko) with option iocharset=utf8. Great function for my home network.
Wysłane z mojego C6603 przy użyciu Tapatalka
Hey @McBane87. Maybe some update? Sources for Lollipop .222 released 2 months ago. Could you try compile new one wersion?
EDIT.
Once again I'm surprised!! Attached cifs module for LP .454 working with latest stock firmware .222
So thanks again. [emoji482] [emoji482] [emoji482] [emoji482] [emoji482]
Wysłane z mojego C6603 przy użyciu Tapatalka
Rebooting after mounting
With many hopes I followed the procedure and ... seccesfuly mounted.
But...
After a few seconds device reboots.
There is libc.so mentioned in tombstone.
Any Idea why that happens?
Thanks.
McBane87 said:
Hey Guys,
Just wanted to share with you the CIFS-Module I build some days ago.
Maybe someone can use it.
Click to expand...
Click to collapse
Related
You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /system
exit
adb push bin\sqlite3 /system/bin
adb shell
su
chmod 6755 /system/bin/sqlite3
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
reboot
Ohhhh it's good to see you here in the Iconia section!
I used to be a user of your great Desire Kernels/roms.
Hope to see some work from you soon.
richardtrip said:
You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push bin\sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
adb shell reboot
Click to expand...
Click to collapse
Thank you very much and great to see you here
OT: can you help us with the recovery issues ??
Thanks in advanced. I will try sometime in the near future.
Enviado desde mi GT-I9000B usando XDA Premium App
so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?
lpachuong said:
so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?
Click to expand...
Click to collapse
The rest of the ram is reserved for video on boot.
I thought so, but don't you think that is too much out of 1GB ram? I found the device is laggy if ram goes under 350MB. Hope modded kernel can help optimize ram.
sweet
Nicely done! It works. Yea it is good to see you here' meaning we have somebody who knows a thing or two about android development.
W
Fix worked!
For some strange reason adb remount command didn't worked and adb wasn't able to push sqlite3 file to /system/bin even after remounting /system rw from the device itself. I had to push it to sdcard and then move it to /system/bin.
By the way, channel 13 is working fine now.
Thx
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
EDIT: I can confirm that this works!
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
[Edit: worked with a terminal, but forgot to SU first, and I was typing mmcblkop3, not mmcblk0p3 !!]
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire).
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Try su before the mount command.
Edited the procedure in the first post so try that (should work now).
Sent from my A500 using XDA Premium App
zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Just do
Code:
su
mount -o remount,rw /system
daveba said:
Just do
Code:
su
mount -o remount,rw /system
Click to expand...
Click to collapse
Thanks!
For the beginners (like me): I noticed that /system was set back to read-only on reboot...
Works brilliantly. Thanks.
thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.
hi
can anyone tell me whats this fix for?
is it going to make wifi receiver even better?
thx..
he_stheone64 said:
thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.
Click to expand...
Click to collapse
yes,
add this line
ro.wifi.country=EU
and reboot.
i have this message:
'Unable to detect a device over adb'
I've connected my nexus S via usb cable, i've tryed with the usb usb storage on an off, and i get the same message.
I'm using windows / x64.
Dexter_nlb said:
yes,
add this line
ro.wifi.country=EU
and reboot.
Click to expand...
Click to collapse
i've done that but i canot save the file i get the message that it's a read only file system.
how can i gain write access to that file??
Thanks the fix_wifichannel_EU.bat in the zip worked like a charm. Channel 13 now works on my Asus Eeepad Transformer purchased from the US as well.
How to use Open Vpn
Mahesh
mvgadagi said:
How to use Open Vpn
Mahesh
Click to expand...
Click to collapse
Here you go :http://tinyurl.com/4476rrj
I already have openVPN working in froyo and gingerbread on a i7500, see here: androidforums.com/samsung-i7500/330288-openvpn-gaosp-beta3-i7500.html
Basically you need to copy the key files to a folder, execute some commands from the terminal emulator, and use the "openvpn settings" app to enable it.
Unfortunately, the commands have to be modified for the O1 gingerbread rom.
Anyone help?
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
ln /system/bin/ifconfig /system/xbin/ifconfig
ln /system/bin/route /system/xbin/route
thanks brownsmell for information
Hi,
I'm new to Android, so please bear with me. I just recently picked up a Nexus 4 to play with. It came with 4.2 on it, and I have done the OTA updates to 4.3 and then 4.4. I decided to root the device and followed the instructions here. That all seems to work OK and I can get root using adb.
The first thing I tried to do next was change the hostname from android-something to a hostname that I could remember. I did a bunch of searching here and found the following commands suggested:
Code:
getprop net.hostname
setprop net.hostname
If I run these commands, the hostname changes. The problem is once I reboot, the name is back to what it was originally. I even tried remounting /system as rw, as I saw in some other post, and running the command again like this:
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
setprop net.hostname NEWNAME
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
I tried rebooting after that and the name change still doesn't stick. What am I doing wrong?
bigdweeb said:
Hi,
I'm new to Android, so please bear with me. I just recently picked up a Nexus 4 to play with. It came with 4.2 on it, and I have done the OTA updates to 4.3 and then 4.4. I decided to root the device and followed the instructions here. That all seems to work OK and I can get root using adb.
The first thing I tried to do next was change the hostname from android-something to a hostname that I could remember. I did a bunch of searching here and found the following commands suggested:
Code:
getprop net.hostname
setprop net.hostname
If I run these commands, the hostname changes. The problem is once I reboot, the name is back to what it was originally. I even tried remounting /system as rw, as I saw in some other post, and running the command again like this:
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
setprop net.hostname NEWNAME
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
I tried rebooting after that and the name change still doesn't stick. What am I doing wrong?
Click to expand...
Click to collapse
It shouldn't be changed
Anyway, try this https://play.google.com/store/apps/details?id=com.tiranodroid.change.hostname&hl=es
luiseteyo said:
It shouldn't be changed
Anyway, try this https://play.google.com/store/apps/details?id=com.tiranodroid.change.hostname&hl=es
Click to expand...
Click to collapse
Thanks for the reply. I had seen that there were apps for this, but I figured it would work on the cli if an app could do it.
Why do you say it shouldn't be changed? I've never had a device that you weren't supposed to change the name of.
Project thread created..
http://forum.xda-developers.com/showthread.php?t=2627255
install-or-mount-v0.8-gui.zip
Use this thread for help
Device List
Change Log
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
ONDR4SH3K said:
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
Click to expand...
Click to collapse
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
userdelroot said:
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
Click to expand...
Click to collapse
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
ONDR4SH3K said:
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
Click to expand...
Click to collapse
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
Click to expand...
Click to collapse
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
ONDR4SH3K said:
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
Click to expand...
Click to collapse
Yea, it has to do with the line above I believe.
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
Click to expand...
Click to collapse
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
ONDR4SH3K said:
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
Click to expand...
Click to collapse
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
userdelroot said:
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
Click to expand...
Click to collapse
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
is it normall ubuntu for desktop or Ubuntu phone version?
desktop
JFizDaWiz said:
desktop
Click to expand...
Click to collapse
I'm confused
Does touch work? Or do we need OTG cables
milestoneman said:
I'm confused
Does touch work? Or do we need OTG cables
Click to expand...
Click to collapse
You need root, and an android device.
No OTG cables..
It build's a chroot image on the device, with android running in the background.
You can run X windows (only LXDE currently because it is lightwieght) on the device and then vnc into it from anywhere, even a desktop...
There are other tools out there for this however, they require you to download the images. Which are usually between 1gig - 4gigs.
Instead of downloading the images, this creates the image and only downloads approximately 200megs for the packages.
Thanks for the explanation, sounds great
Sent from my Nexus 7 using Tapatalk
ONDR4SH3K said:
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
Click to expand...
Click to collapse
Yea, crap, that was my bad, I should check where the system busybox is installed. It should default to /system/xbin
But some roms I guess put it in /system/sbin ? Possibly a typo on the rom developers part? LOL
Anyways, I will add code to correct this.
EDIT: How did you fix image 2?, as it should stop at the error in image type every time.
At any rate, image 2 error is because it can't find sh. in the install-or-mount/bin directory type this..
ls -l bin/
Make sure sh is symlinked to /system/bin/sh or /system/xbin/busybox if not that is causing the error in picture 2
it should look like this...
ls -l bin/
sh sh -> /system/xbin/busybox
If you don't see that do the following:
cd /data/local/install-or-mount
busybox touch bin-configs/sh
rm -rf .bin-configs-done
if you have something like that it should be ok, however to be safe since you moved you your busybox
from inside install-or-mount
rm -rf .bin-configs-done
Yes there is a DOT in front of bin-configs-done
I receive a permission denied error with debootstrap as well
Edit: crap I didn't see all the replies up there
Sent from my GT-N7105 using Tapatalk
Will it works on my armv7 single core tablet?
I fix it other way:
mount -o remount,rw /system
cp busybox /sbin /system/xbin
mount -o remount,ro /system
I hope that commands are fine.
I has no solution for fetch Release error, yet. I tried rewrite URL, but unsussesful.
Its in scripts folder line mirror_styles Release
Sent from my Xperia P using xda app-developers app
---------- Post added at 01:06 AM ---------- Previous post was at 01:00 AM ----------
Already testing on armv7 device dual core. OP must fix a few errors but you can try it.
Sent from my Xperia P using xda app-developers app
Hey Guys,
Just wanted to share with you the NFS-Module I build today.
Maybe someone can use it.
You can copy the Modules wherever you want and then let it load automatically by an APP.
For example with Mount Manager
Or you can load them manually in this order by:
Code:
su
insmod /path/to/module/sunrpc.ko
insmod /path/to/module/lockd.ko
insmod /path/to/module/auth_rpcgss.ko
insmod /path/to/module/nfs.ko
Mounting can be done in Terminal, with "busybox mount". Normal mount seems not to work:
Code:
su
busybox mount -t nfs -o hard,intr,nolock,sync,vers=3,exec 192.168.1.1:/path/to/share /path/to/mountpoint
Unfortunately, since JB Android doesn't make mounts made by root visible for other users.
So even if you mount via Terminal or with Mount Manager, you won't see anything as normal user.
You can see them only as root.
If you want to mount shares for normal user, do the following:
Code:
su -c setenforce 0 && su --mount-master -c busybox mount -t nfs -o hard,intr,nolock,sync,vers=3,exec 192.168.1.1:/path/to/share /path/to/mountpoint
-