I am on a rooted Android 12 device (Orange Pi 5 Plus) and I have managed to setup and mount a samba share to a local directory using the following commands: su export PATH="/data/data/com.termux/files/usr/bin:$PATH" rclone mount rpi4:/raspberrypidocker/shared /data/media/0/rpi4 --allow-other --config="/sdcard/.rclone/rclone.conf" This works and it looks like all apps are able to read the contents of that directory. The problem is that no app can write to this directory. I receive: /storage/emulated/0: read-only filesystem However I am able to write to that directory before I mount it with rclone. Am I missing something here?

currently I don’t have both devices at the same place to test this, but maybe someone uses a similar setup. So I’d like to use an android tv box with a NAS device connected directly to the ethernet port of the android device. So there is no router in between. I can set a fixed ip address on the NAS, I guess the same can be done on the device running android. And android should immediately detect the SMB share on the NAS when connected this way, right? Currently I have the NAS connected to an old samsung tv this way and it works as a media server for the tv. But I lose internet on the tv, because wifi can’t be used at the same time when the NAS is connected. What would be really cool is if I could use android’s wifi connection while the NAS is connected to ethernet, and if android was able to somehow passthrough the NAS’ SMB share to the rest of the local network devices, so they could also read/write to the NAS. Any thoughts if something like this could be done? Connecting the NAS to the router doesn’t work for me, because LAN cable doesn’t reach the place where the tv is and wifi is too slow for video.

I use the latest version of Nox Player (android emulator) on Mac OS Catalina. I would like to mount my AFP or SMB drive to Nox Player. I've connected to Nox Player thru ADB: adb connect 127.0.0.1:62001 Now I am trying to mount the drive: mount -t afp afp://login:pass@192.168.1.5/photo /sdcard/DCIM (/sdcard/DCIM folder exists) But it returns the error No such device. I tried to su before executing the command. I tried to mount to another folder (/mnt/sdcard/xyz, /storage/self/primary/DCIM), but it doesn't help. The command given above works well if executed directly on my Mac. I've tried to ping 192.168.1.5 from Nox player and it works well. I've tried to open the same storage within Nox Player built-in Amaze file browser as SMB share and it also works. I've read https://android.stackexchange.com/questions/200867/how-to-mount-nfs-on-android-with-correct-permissions/201191#201191 , but it is not quite clear for me what else could be tried. What should I try?

I have a handful of apps that have file pickers, but they only show me what is in /storage/emulated/0 (also shown on my phone as "Internal Storage") and below. I want to mount a NAS so that i can access the files through these other apps but I can't figure out how. Mounting the network drive with Cx File Explorer or SolidExplorer does not seem to make the drive accessible to other apps. Is there a way to mount the NAS as a subdirectory of the internal storage? Or create a symbolic link to the mounted network drive? EDIT: From searching more it seems that SolidExplorer/CxFileManager do not mount the network drive as a "system wide" drive. Nor does it seem that stock Pixel 6/6 Pro kernels support CIFS. Not sure what to do as i'm not looking to flash a new kernel or rom.

All of a sudden, my VLC for Android app just up and stopped showing the local LAN network shares which are Samba running on a Xubuntu 20.04 host. I have no clue to what caused this. I have verified that the share is indeed shared via this on that Linux host that has the samba service activated: $ smbclient -L wilddog Enter WORKGROUP\XXXX's password: Sharename Type Comment --------- ---- ------- samba_share Disk Shared Folder print$ Disk Printer Drivers IPC$ IPC IPC Service (XXXXX server (Samba, Ubuntu)) testprinter Printer SMB1 disabled -- no workgroup available $ From the VLC For Android app, all I see now is this: EDIT: I have rebooted both the phone, and the Linux server, to no avail. I've also restarted the samba server on the Linux server, also to no avail. What do I need to do to diagnose this?

With ES Explorer not to be trusted any more, I needed another solution for easy access to my SMB/CIFS network shares. Mounting a SMB/CIFS network share in Android-x86 (version 9 R2) turned out to be a lot easier than any of the solutions I found on StackExchange. I did not need to install any software or app, mount -t cifs works just out of the box. The problem is that I cannot make this mount visible for normal user. Only root or superuser, whatever it is called in Android, sees and can use the mounted file system, whereas the normal user keeps seeing the mountpoint as a directory of Android's own filesystem. To clarify, have a look at this terminal session. In this example, Android is running in a Virtual Box VM, the IP address is that of the host itself. I make a subdirectory in /sdcard/Download/ to mount on, with the intent of easily moving files from Download to the share mounted on that subdirectory. I mount the share as superuser, with appropriate options, and then, both as normal and as super user, list the subdirectory contents and stat the subdirectory : $ cd "/$EXTERNAL_STORAGE"/Download/ # i.e. /sdcard/Download/ $ mkdir SERVER_SHARE $ touch SERVER_SHARE/"NOT THE MOUNTED SHARE" # a marker for the base directory $ su -c "mount -v -o username=guest,rw,noperm,iocharset=utf8 -t cifs //192.168.1.10/SHARE $PWD/SERVER_SHARE" $ ls SERVER_SHARE/ 'NOT THE MOUNTED SHARE' $ su -c "ls SERVER_SHARE" ... lists all the files on the share ... $ stat SERVER_SHARE Size: 4096 Blocks: 0 IO Block: 512 directory Device: 1dh/29d Inode: 409629 Links: 2 Access: (0770/drwxrwx---) Uid: ( 0/ root) Gid: ( 9997/everybody) ... $ su -c "stat SERVER_SHARE" Size: 0 Blocks: 0 IO Block: 512 directory Device: 1eh/30d Inode: 217 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) ... You see the difference between normal and super user: ls shows different directory contents because stat says they see the subdirectory on a different Device. A possible explanation could be that the normal user has the file descriptor for the directory open, and keeps using that file descriptor and the contents it points to, even after some other file system is mounted over it. But that would probably not explain why exactly the same thing happens if I put the mkdir inside the su command for the mount. For the time being, I can only access the mounted samba share of the VM host from the terminal, as super user, to copy files between the share and the Download folder. I have put the mkdir and mount commands in a script, and added the touch command to mount the directory under the mountpoint as 'not the network share'. **My question is this**: how do I make the mounted share visible to the normal user, so that I can use the Android apps like "Files" and other file managers to access it in a GUI.

I tried a couple of Android file explorer apps to mount an (SMB3) Azure file share, but I got an "Access Denied" error with each of them. Does anyone know a solution? I tried the most common File-Apps on PlayStore: - Cx File Explorer - File Manager - X-plore - AndSMB - CIFS Documents Provider Authentication is with username and Azure storage account key based on the snippet provided by azure for Linux: sudo mkdir /mnt/fileshare1 if [ ! -d "/etc/smbcredentials" ]; then sudo mkdir /etc/smbcredentials fi if [ ! -f "/etc/smbcredentials/aname.cred" ]; then sudo bash -c 'echo "username=aname" >> /etc/smbcredentials/aname.cred' sudo bash -c 'echo "password=akey" >> /etc/smbcredentials/aname.cred' fi sudo chmod 600 /etc/smbcredentials/aname.cred sudo bash -c 'echo "//aname.file.core.windows.net/fileshare1 /mnt/fileshare1 cifs nofail,vers=3.0,credentials=/etc/smbcredentials/aname.cred,dir_mode=0777,file_mode=0777,serverino" >> /etc/fstab' sudo mount -t cifs //aname.file.core.windows.net/fileshare1 /mnt/fileshare1 -o vers=3.0,credentials=/etc/smbcredentials/aname.cred,dir_mode=0777,file_mode=0777,serverino

I want to backup as much as possible from a rooted Android phone(user-data, app-data, etc) on a daily basis to a Synology NAS. I've found this tutorial: Automatic Nightly Backups for Your Android Device to Your Computer | Guysoft's Weblog https://guysoft.wordpress.com/2012/11/01/android-nightly-backups/ The only problem remaining is that Titanium Backup performs the backup image on the phone, which is then copied to the NAS via rsync. I cannot afford this, since I don't have an SD card slot, nor much space left on the phone. Any ideas on how to save directly to NAS(smb share) instead? On the other hand, I was thinking at adb, as an alternative way to do a backup, but I haven't seen anyone installing it on a NAS. Besides installing, there should be some scripting involved, in order to detect the connection to the phone via USB or WiFi, and then the backup process.

With a Windows machine, I can connect with IP, user, and password to some Linux shares. With ES File Explorer Pro, I get strange "server not found" messages. This is what I do: 1. Open ES File Explorer Pro 2. Search the LAN (the machine is listed) 3. Access the machine (I notice it's getting all the shares listed) 4. Entering a folder gives a permission error. So I add the folder to ES File Explorer server bookmarks and try to access it again, but I get a "server not found" error. 5. Then I edit the bookmark (and notice it's logging as an anonymous user) so I set the domain with the machine name, server adding smb://ip/share/ to the address, user, and password. And still, I get "server not found". All the other machines, some Linux and some Windows are accessing Just fine. Except for the Android devices with ES File Explorer Pro. What am I missing?

I am not able to mount an image over a network onto my Android device. I tried to pull the userdata partition onto my Windows using: adb pull /dev/block/mm..0p29 userdata.img Now, I am trying to mount this image on some other Android device over network using Samba/CIFS: busybox mount -t cifs -o vers=1.0,username=...,pass=..."//ipaddr/folder" /mnt/folder to mention I don't see the CIFS in my filesystems, so I tried to build a kernel with CIFS support but failed to have one. I tried to push an already built cifs.ko into system/bin/modules and load it, but it still doesn't show up in /proc/filesystems. My device is rooted, I have tried using SambaDocumentsProvider/CIFSManager but even after clicking on mount option, I don't find any files shown via the file explorers. I can't even see any mountpoint being shown. I have set my device to permissive to get rid of any SELinux issues. if anyone knows how to fix it, please share it with me.

I've tried these commands with root access mount -t fifs //192.168.62.118/xyz -o username=user,password=pw /mnt/sdcard/xyz mount -t cifs //192.168.62.118/xyz -o username=user,password=pw /mnt/sdcard/xyz mount iocharset=utf8 -t cifs -o username=user,password=pw,rw,noperm,iocharset=utf8 //192.168.62.118/xyz /mnt/sdcard/xyz mount -o username=user,password=pw,nodfs,rw,iocharset=utf8,noperm,dir_mode=0777,file_mode=0777 -t cifs //192.168.62.118/xyz /storage/self/primary/xyz all of them results in "no such device". Googling around, it seems its due to the kernel not supporting CIFS. But this also happen in LineageOS 17.1 where other people reports able to mount cifs, albeit on a different device. WHat I could do to get cifs smb mount working?

I have shared a folder named myfolder in Windows, the computer name is MYPC. I installed FolderSync on Android and I would like to connect to this shared folder via SMB. **What's the relevant share address with smb:... ?** smb://MYPC/myfolder or smb:///MYPC/myfolder or smb:\\\MYPC\myfolder I tried all these options, but it did not work.

My phone is not rooted. I have shared folders on a Synology drive which I can mount on a couple of different Macs running different versions of Mac OSX. I am assuming the folders are published using CIFS/SMB but I cannot mount them on my Android phone using file manager type applications. So far I have tried "ES File Explorer", "Network Browser" and "File Commander" none of which are able to connect. I can connect to the Synology home page using a browser on the phone so network connectivity is OK. Do I need to disable/enable firewall/sharing settings on the phone?

Im trying to mount cifs share to android 10 rooted phone and i already mount it but i cant see files in folder in other apps only in rooted one. It is possible to do something like that to get access from all apps to cifs share?

I want my hone to be used as network drive, by sharing folders over network. So that I can access it from My windows PC. I want to use SMA protocol for that. I am using OnePlus One, CM12.1 OS with ES file explorer.

I used 2 apps that can connect from Android (Nougat) to PC (Windows 7). Hitherto that worked perfect. Now I get user authentication problem when I try to connect from Android to PC with "username" credentials. But I can connect without issues using administrator. It tells me that there is a user specific setting that changed. I didnt change anything. What setting is this? Any idea?

I'm looking for a way for my HTC Hero (Android 2.1) so I can share the contents of my SD card and phone memory over the WiFi network like a regular Windows file share. I'd like one that does not require me to root my phone, and am willing to pay for the right app so it doesn't have to be free. I'm thinking of using SMB server and all I've found so far are: 1. SambaAndroid which requires root access. 2. androidsmb which is a "Java implementation of the SMB/CIFS network file and printer share server for Android devices" hosted on Google Code that has no documentation and has not released any files. Is it even technically possible to develop an SMB Server on Android that can be installed without root access?

I have a setup like this : [Shield TV 2015] 10.10.2.112 [OpenWRT Router] [Synology SMB Share] 10.10.3.11 I want to be able to access all my NAS files with any apps on the shield TV, so, I want to mount permanantly the SMB share on the Shield. So after confirming the connection was router correctly usig solid explorer integrated smb client, I went into the shield settings > Storage > add new network storage and inputed the NAS path (\\10.10.3.11\Public) and the associated credentials. However, it can't mount it, and according to logcat, it can't find the NAS netbios name locally, which is normal as it's in another subnet, but abnormal as I inputed it by IP. Moving the nas to the main subnet is out of the question for multiple reason. In the end, is there a way to force the mount with just the IP ? I'm open to all suggestion, even root or scripts ones.

Is it possible to scan specific folders for music files and import them to some android media player app, which could then stream the music to a DLNA device? Another challenge is that the music files are on a NAS device, so they would be accessed through an SMB share (or AFP, or NFS share, if that changes anything). I found a way to mount it to android's filesystem (using command busybox mount iocharset=utf8 -t cifs -o username=guest,rw,noperm,iocharset=utf8 //192.168.0.106/xxx /data/media/0/xxx), so apps see it as a local folder (you must have root for that I think, also the kernel should support cifs filesystem, and apparently the android device should not be in battery saving state and iocharset=utf8 is important if you have file or folder names with special characters), but the problem is that many apps rely on android's media scanner service to find music, which probably has trouble scanning the whole mounted folder and the apps do not see all the music files.

Is it possible to mount an SMB share to a folder that Android thinks is a removable media (external SD card or USB storage)? Currently. I am using the following command to mount the share to Android's filesystem (I should mention that it doesn't work if the android device is in battery saving mode - took me a while to figure this out): busybox mount iocharset=utf8 -t cifs -o username=guest,rw,noperm,iocharset=utf8 //192.168.0.11/xxx /data/media/0/xxx But, I don't think it's the best way, because I had some media scanner crashes, random reboots and notifications about low internal memory, which I think are related to the mount I performed.