I rooted my TN7(Xolo). Now I want to mount my windows shared folders. Is it possible with stock kernel. Does shaky's kernel have this facility?
I've rooted my Tegra Note 7 too but haven't been able to mount my Windows Network Shares either. I'd like to compile the modules but I don't have the time. If anyone does have the time or has succeeded in compiling the relevant modules for the default kernel I'd appreciate being able to make use of them too. Thanks.
I compiled and it was a success. I also loaded 2 modules cifs.ko and md4.ko using insmod command, it was successfully loaded. Also checked using lsmod command, it showed modules loaded and live as a status. But when I mounted using "mount" or "busybox mount" command I got various error like "No such device", "unc path does not begin with // or ". After, I came to know that there is problem with android 4.2+ kernels. ... ... I will post the modules later today when I am at home, in case if you get succees then tell me which command you used.
asratxda said:
I compiled and it was a success. I also loaded 2 modules cifs.ko and md4.ko using insmod command, it was successfully loaded. Also checked using lsmod command, it showed modules loaded and live as a status. But when I mounted using "mount" or "busybox mount" command I got various error like "No such device", "unc path does not begin with // or ". After, I came to know that there is problem with android 4.2+ kernels. ... ... I will post the modules later today when I am at home, in case if you get succees then tell me which command you used.
Click to expand...
Click to collapse
Hello, can You please Upload those modules. I am in need of them. Tried alot with mount manager. But no success :'(
Related
Im working with Andrizoid atm at seeing if we can get some progress on his Ubuntu project. Heres the issue.
Code:
busybox mount -o --bind ./dev/pts /data/local/ubuntu/dev/pts
mount: cannot read /etc/fstab: No such file or directory
In doing a little research I came across this
If there is no entry for /dev/fd0 in my fstab when I issue the command above, mount gets very confused because it doesn't know where to mount the floppy.
Click to expand...
Click to collapse
This come from http://www.tuxfiles.org/linuxhelp/fstab.html which gives a quick breakdown of what the etc/fstab file is. When i went exploring I couldnt find an etc/fstab
Code:
[B]
mount: cannot read /etc/fstab: No such file or directory
[/B]
The thing about Android though...there IS NO /ETC/FSTAB file because its become obsolete.
The init program directly mounts all filesystems and devices using either hard-coded file names or device names generated by probing the sysfs filesystem (thereby eliminating the need for a /etc/fstab file in Android). After device/system files are mounted, init reads /etc/init.rc and invokes the programs listed there (one of the first of which is the console shell).
Click to expand...
Click to collapse
EDIT: Conclusion
After bouncing some ideas around, I've come to the conclusion that it HAS to be a Busybox issue.
An Android specific variation of Busybox should take into account the fact that there isnt an etc/fstab file. The fact that these commands work on other phones leads me to think that its an Eris specific issue. If anyone remembers there were issues when using the Busybox available on the market on the Eris.
Looks like we need a Busybox update
es0tericcha0s said:
Or is there something else I can do?
Click to expand...
Click to collapse
Modify the mount command.
If the version of BusyBox is the Android version, report this issue (as a bug?). If it's the standard Linux BusyBox, the devs may not be interested. Or, if BusyBox is just calling the standard mount command, then it's not a BusyBox issue for them to worry about.
hallstevenson said:
Modify the mount command.
If the version of BusyBox is the Android version, report this issue (as a bug?). If it's the standard Linux BusyBox, the devs may not be interested. Or, if BusyBox is just calling the standard mount command, then it's not a BusyBox issue for them to worry about.
Click to expand...
Click to collapse
I'm using the Android Busybox, and those commands are being executed in an adb shell so I doubt that its calling the standard mount command-it should be calling the (hopefully) Android specific mount command. The things thats confusing me is that those same commands worked just fine for other phones. I dont see why I would get an error and others would have no issue with it?
EDIT:
And if you ave any recommendations for what I should modify the mount command to, let me know.
You mention a reference to /dev/fd0 but I'm 99.9% that's referring to the *nix mount command. The Android/BusyBox version should know better than to look for a floppy drive.
Where is BusyBox maintained ?
I did find a page about an Android ROM from Nov 2008 that mentions
- changed the "mount" symlink to be busybox's mount instead of toolbox's mount
- added an /etc/fstab file that busybox's mount can use, that lists the standard system partitions.
Click to expand...
Click to collapse
Is "mount" in fact an internal adb command ?
hallstevenson said:
You mention a reference to /dev/fd0 but I'm 99.9% that's referring to the *nix mount command. The Android/BusyBox version should know better than to look for a floppy drive.
Where is BusyBox maintained ?
I did find a page about an Android ROM from Nov 2008 that mentions Is "mount" in fact an internal adb command ?
Click to expand...
Click to collapse
The floppy drive reference was just from some background info I pulled on the etc/fstab file. I wasnt actually trying to mount a floppy disk
I have no idea where I would put in a bug report or anything. I know Stericson was the publisher of the BusyBox app thats avaiable on the market, but the one for the Eris is different anyways so idk if he could help.
Im not sure what you mean by your last statement, but mount is not a command that you can use in a shell on its own. You have to use busybox mount ...
If you can show me where you found that rom from I may be able to finish this. I was just talking to a buddy of mine about making my own /etc/fstab and slipping it in just so that the mount command would work. If theres already one put together then thats way less work for me
What I meant by referring to that info you found was that person couldn't have been talking about the Android version. I didn't think you were trying to mount a floppy.
You sure that there's no "adb mount" ? Look here, http://forum.xda-developers.com/showthread.php?t=517874. They refer to "adb shell mount".
Personally, I would just create an /etc/fstab file (I believe it can be empty) and see what happens.
hallstevenson said:
What I meant by referring to that info you found was that person couldn't have been talking about the Android version. I didn't think you were trying to mount a floppy.
You sure that there's no "adb mount" ? Look here, http://forum.xda-developers.com/showthread.php?t=517874. They refer to "adb shell mount".
Personally, I would just create an /etc/fstab file (I believe it can be empty) and see what happens.
Click to expand...
Click to collapse
well ive got an /ect/fstab file that i took from here http://www.android-devs.com/?p=152
Code:
# /etc/fstab: static file system information
#
# file system mount point type options dump pass
/dev/block/mmcblk0p2 / ext2 defaults 1 1
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /media/sdcard vfat defaults 0 0
But thats from a guide about debian on the N1 and the way they are doing it is much different from the method I'm using.
adb shell mount give the error that mount isnt found. it has to be called through busybox-at least in the instance that im using it in
Code:
busybox mount -o --bind /dev/pts /data/local/ubuntu/dev/pts
Solved: See post #4
Obviously for those with a modded kernel and broken MAC.
If we knew the real MAC address for the specific device, couldn't we set the module's MAC to our real one?
Or just a MAC spoofer? But more like an un-spoofer..
Im looking for the answer as well...
I have been through every oc kernel so far, only stock/insmod seems to keep the mac addy. This might be the best option until a proper solution is found, if anyone has an idea on how to insmod on startup that would be good.
I also tried ipconfig eth0 hw ether, but got an invalid argument.
tijuanacartel said:
Im looking for the answer as well...
I have been through every oc kernel so far, only stock/insmod seems to keep the mac addy. This might be the best option until a proper solution is found, if anyone has an idea on how to insmod on startup that would be good.
I also tried ipconfig eth0 hw ether, but got an invalid argument.
Click to expand...
Click to collapse
Can't you setup a script that insmod's and set that up to run on startup?
I'm sure there is somewhere in the ROM where a script can be added for it to run on boot, or at least a boot time Android one...
init.rc perhaps?
Okay i found it... there is a file called /bootcomplete.rc that calls
/system/xbin/busybox run-parts /system/etc/init.d
so, on stock kernel with oc-dz.ko:
Code:
# cd /system/etc/
# mkdir init.d
# cd init.d
# echo insmod /system/lib/modules/oc-dz.ko pll2_l_val=74 > overclock
# chmod 0755 overclock
will load the module at boot. wifi mac is correct
Okay I've been using this for most of the day and just had a hard crash on level 99 of robo defence(F7U13!) Looking into it, it seems this kernel module only seems to step up from 700 straight to 1497! I'm disabling it for now.
Apparently cyanogen is quite a lot faster than the stock Sense, even without overclock. As soon as it hits RC2, I'm gonna give it a shot.
tijuanacartel said:
Okay i found it... there is a file called /bootcomplete.rc that calls
/system/xbin/busybox run-parts /system/etc/init.d
so, on stock kernel with oc-dz.ko:
Code:
# cd /system/etc/
# mkdir init.d
# cd init.d
# echo insmod /system/lib/modules/oc-dz.ko pll2_l_val=74 > overclock
# chmod 0755 overclock
will load the module at boot. wifi mac is correct
Click to expand...
Click to collapse
EDIT
Trying from a Terminal I get: "undable to chmod overclock: Read-only file system"
I tryed from ADB and all commands were accepted, file was created and chmod processed, but after reboot the OC module is not loaded
What ROM are your using ??
Obviously you should remount your system partition rw
tijuanacartel said:
Obviously you should remount your system partition rw
Click to expand...
Click to collapse
OMFG I really need to sleep a little
What ROM are you using ?? Have you changed the Kernel ??
at the time i was using stock.. currently using virtuous from rom manager
I've been strugglin with that command line for days, trying to find a way t make it stick from boot (and not typing it from a console), I finaly made it today via updater script (update.zip).
I also included the stock radio module and the stock kernel (rooted) to the package, so it can serve as a "rescue kit" for other users stuck with the MAC WiFi shizz. I shared it @ devs forum.
I copied over the debian image i made for my sgs i9000 to try and run on my galaxy tab since i think the much larger screen, double RAM and faster cpu would make the image run smoother. I hoped the p7510 might be able to replace my laptop for word processing by running openoffice in chroot. I remembed to set the path, user and home variables. After mounting the image i go to chroot but i get the error
"chroot: can't execute /system/bin/sh"
I tried installing 10 other versions of busybox from the market. I am currently using the latest bindroid rom and pershoot kernel. The image worked on my sgs when it ran stock roms and now cm7.1. Is it the bindroid rom? I also tried to use apk manage 4.9 to decompile the rom's framework-res to enable crt off but it always errors out recompiling.
I realize that /system/bin/sh is where android has sh but i thought busybox would be smart enough to know that normal linux like my laptop has it in /bin/sh. My sgs seemed to know its directory of sh was not normal.
i'm having the same problem as well setting up debian to my galaxy tab, same model as you. when i mounted debian, it doesn't have /system/bin/sh, it's just /bin/sh. maybe you should try to specify /bin/sh at the end of the command, if you don't, it will default to /system/bin/sh. maybe you'll have more luck than me. i mounted debian in /data/local/debian and typed chroot /data/local/debian /bin/sh but it says "/bin/sh: precmd: not found". if you or anybody else figures out how to get past that, that would be awesome! thanks!
EDIT: look at the directory structure and see if it's /bin/sh instead of /system/bin/sh and if it is, specify /bin/sh at the end of the chroot command then hit enter and you might get an error, if you do, type: unset PS1 PROMPT_COMMAND .. that worked for me and then you'll get a command prompt and you'll be in linux now and not android. i hope i helped
I've been trying to get my NAS drive mounted into my file system on my S4, but haven't had any success. I've tried using a combination of Mount Manager and CIFS Manager, but I always seem to get one error or another.
Every time I think I have it setup right I get an error about not being able to chmod the directory where I'm trying to mount it to. I've tried many other directories but nothing as seemed to work.
Any solutions?
I have the cifs.ko loaded, but is it possible that my kernel simply just doesn't support the action I'm trying to perform?
hello guys sorry for my english, but at the time is possibile to have kali linux on android 4.4.2 of galaxy s5??? i try a lot of guide but nothing, thanks
Yes there is a way. I am running Kali Linux on my Galaxy s5 now!!
Download linux deploy and install Kali linux from there.
GL!
la2o said:
Yes there is a way. I am running Kali Linux on my Galaxy s5 now!!
Download linux deploy and install Kali linux from there.
GL!
Click to expand...
Click to collapse
i've already tried but nothing , maybe can you send me a pvt message with a little guide for the installation?? p.s. i have a sdcard of 8 gb
I tried Linux on Android but it gives invalid argument mounting the loop device. Linux Deploy has an option to not use a loop device and install to a folder I think. Not positive. Try Advanced Linux Installer. That might work. It costs but it's way better than the free version. Try Standard Linux Installer first if you like.
Could you please add some note on how you managed to install?
I am trying with several options, but always get stuck on a "dd: permission denied" creating the volume
Z
I'll try to provide that info. What you're seeing likely means where it's trying to write isn't allowed. Try changing the install location to somewhere safe like /data/kali or something. Also I just found out the S5 won't do ext2 so if you're trying to do a loop device use ext4 if possible. Sorry I don't have more info at the moment.
I am having the same issue. What SU app are you using? I am using SuperSU, I read that SuperSU might be the problem but I do not know the conditions on how to switch SU apps. Hopefully we can find a solution.
Just got running.
use a terminal emulator as root
cd /data/data/ru.meefik.linuxdeploy/linux/bin
rm sh chroot
ln -s /system/bin/mksh sh
ln -s /system/xbin/busybox chroot
make sure your file location is on your sd card
change image size to appropriate size.
also change to ext4 file system
DipSprayArc said:
Just got running.
use a terminal emulator as root
cd /data/data/ru.meefik.linuxdeploy/linux/bin
rm sh chroot
ln -s /system/bin/mksh sh
ln -s /system/xbin/busybox chroot
make sure your file location is on your sd card
change image size to appropriate size.
also change to ext4 file system
Click to expand...
Click to collapse
Can you explain this deeper? I typed that in an emulater but no luck
DipSprayArc said:
Just got running.
use a terminal emulator as root
cd /data/data/ru.meefik.linuxdeploy/linux/bin
rm sh chroot
ln -s /system/bin/mksh sh
ln -s /system/xbin/busybox chroot
make sure your file location is on your sd card
change image size to appropriate size.
also change to ext4 file system
Click to expand...
Click to collapse
Also here are screen shots of my errors, settings, and anything else I figured might be useful to you. Thanks for help in advance.
I think it's long overdue for a Galaxy S4/5 guide. I know tinkering must be done and there are several issues to negotiate. I've found scattered info here and there but nothing definitive. Complete Linux Installer or Linux Deploy. Either/or. The only way I've ever got Linux to work is by installing to a directory and doing a chroot into it and doing a debootstrap.
Please&ty.
Is the stock WiFi radio compatible with packet injection or monitor mode on the S5 that you know of? I never put much effort into the install after I had such as hard time initially, attempting to install it to my extSdCard.
Solution
Hi there, I tried to install the kali distro in a s5 (g900f) with de Linux Deploy v 1.5.5 and I couldnt, i downloaded the 1.4 and neither but with de v 1.3 I could make it!
So if you are having any troubles with the installation, just download a previous version from the project's github (here)
Hope it helps!
su error
[email protected]:~$ su
Password:
su: Authentication failure
[email protected]:~$ sudo -i
sudo: PERM_ROOT: setresuid(0, -1, -1): Permission denied
[email protected]:~$
And now ?
plz help bro