I had rclone mount my Google Drive on my Android 7 box with the Magisk module and Termux. But it has stopped working and now there's only an empty folder. This is the rclone log:

2020/06/03 07:33:54 mount helper error: CANNOT LINK EXECUTABLE "fusermount": library "libandroid-support.so" not found
2020/06/03 07:33:54 Fatal error: failed to mount FUSE fs: fusermount: signal: aborted.

I just want to mount rclone on my rooted HiMedia Q10 Pro Android TV box so that I can view my GDrive as a permanent folder on my file system.


1 Answer 1


The Magisk module you linked is using fusermount binary from this thread which is built for Termux environment. But LD_LIBRARY_PATH environment variable is not being set properly in the module, so the error occurs. A simple approach is to use static fusermount binary, I already posted in the same thread.

rclone uses FUSE which you can mount manually from CLI without relying on Magisk module. I have explained in detail How to bind mount a folder inside /sdcard with correct permissions?. Some issues related to using FUSE on Android are explained in this post. Here I'm describing steps briefly related to rclone only. I'm using Termux for explanation. You can use some other terminal emulator app or adb shell with differences in paths.

Instructions below require that you have a rooted device.

  • Install rclone binary available in Termux repos (by running pkg install rclone) or download from official website official website. Download static fusermount binary from here (available for both aarch64 and armeabi-v7a). Extract the downloaded archive files. I assume that downloaded files are placed in /sdcard/Download/.

  • For ease of repeated use create a shell script /sdcard/Download/rclone_mount.sh using any text editor. Copy/paste the following lines:

    #!/data/data/com.termux/files/usr/bin/bash -e
    # must be run with root privileges
    [ $(id -u) -eq 0 ] || exec su --mount-master -c "LD_LIBRARY_PATH=$LD_LIBRARY_PATH HOME=$HOME PATH=$PATH:$HOME/bin $0"
    # make sure to be in root mount namespace
    [ $(readlink /proc/1/ns/mnt) = $(readlink /proc/self/ns/mnt) ] || nsenter -t 1 -m -- "$0"
    Unmount() {
        fusermount -u /mnt/runtime/write/emulated/0/GDrive 2>/dev/null || :
    # make sure it's not already mounted
    # make sure it's unmounted after rclone is killed
    trap 'sleep 1; Unmount' EXIT
    # mount remote in /sdcard/
    rclone -v mount GDrive: /mnt/runtime/write/emulated/0/GDrive --gid 9997 --dir-perms 0771 --file-perms 0660 --umask=0 --allow-other

    See rclone mount manual for explanation on commandline options. Some options may impact the performance.

  • Make sure Termux is granted Storage permission and execute following commands:

    ~$ cd
    ~$ pkg install -y util-linux
    ~$ mkdir -p bin /sdcard/GDrive
    ~$ cp /sdcard/Download/{fusermount,rclone,rclone_mount.sh} bin/
    ~$ chmod -R 0755 bin
    ~$ dos2unix bin/rclone_mount.sh
    ~$ bin/rclone config

    Follow the instruction on screen (see rclone config manual for details) to create configuration file (~/.config/rclone/rclone.conf) for Google Drive (or whatever remote service you want to use). I assume you chose the remote name GDrive (as used in above script).

Whenever you need to mount rclone, open Termux and run bin/rclone_mount.sh (or create Termux Widget to run the script from home screen conveniently).

  • All apps with Storage permissions should be able to explore GDrive folder (bind mounting to read and default views isn't necessarily required). But some apps may crash due to slow network activity, others may require more caching (see options) etc.
  • Trigger a Media Scan if e.g. pictures on remote don't appear in gallery app.
  • When done press Ctrl ^C to stop rclone process and mount.
  • Thanks for your detailed answer. You answered about 16 months ago. Is it still the case that the fusermount binary needs to be changed? I'm using rclone-mount 1.16 Magisk module which comes from github.com/Magisk-Modules-Repo/com.piyushgarg.rclone. I'm not using Termux and I would prefer a fully automatic full-time mount (which I assume the Magisk module provides). My question is, after 16 months, do you still recommend the Termux approach as described in your answer instead of Magisk module?
    – MountainX
    Commented Oct 12, 2021 at 21:58
  • 1
    @MountainX I don't use Magisk module, so can't say how well it works. But the manual method I explained should always work. This is how it'll work on any UNIX-like operating system including Android. Commented Oct 13, 2021 at 1:29
  • So... I have the Magisk module installed. I did a good bit of troubleshooting & it still is not working. Now I tried running your mount command rclone -v mount MYMOUNT: /mnt/runtime/write/emulated/0/MYMOUNT --gid 9997 --dir-perms 0771 --file-perms 0660 --umask=0 --allow-other and it works as expected. I did not change my binaries or use Termux or run your script. I just ran the mount cmd as root. Curious why the the Magisk module mounts are failing when clearly my config and my binaries are capable of working. But I do plan to use your approach. I like that it is clear. Thanks!
    – MountainX
    Commented Oct 14, 2021 at 2:54
  • I posted a related question here: scripts - How to use rclone-mount with Termux:Boot? - Android Enthusiasts Stack Exchange. I'm not having success with Termux:Boot yet.
    – MountainX
    Commented Oct 21, 2021 at 4:47
  • I posted two more related questions: Termux: bad interpreter: Permission denied and permission denied only AFTER becoming root in Termux
    – MountainX
    Commented Oct 23, 2021 at 4:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .