How to solve mount helper error:CANOT LINK EXECUTABLE "fusermount":library "libandroid-support.so" not found ?

[themanyourmancouldbe]

trafficstars

I've tried this on Samsung J7 Prime, J1 Ace, and the rclone log output the above message followed by

Fatal error: failed to mount FUSE fs:fusermount: signal aborted

Now I begin to wonder if this problem is specific to Samsung devices..

[piyushgarg]

@themanyourmancouldbe No idea about this.

[themanyourmancouldbe]

I see, thx for the swift reply, I have given up on Samsung, may I know what are some of the successful model+firmware+magisk version combo so far? I'mma try my luck with Xiaomi

[piyushgarg]

I am not sure about Samsung, if you could install custom ROM it might work. I mostly use LineageOS on Xiaomi and Motorola devices. Currently LineageOS 16.0/17.1 + Magisk stable 20.4 does not have any issues.

[themanyourmancouldbe]

Thx for the heads up, appreciate it 👍

[ioogithub]

I have a similar error message regarding the inotify part of the syncd.sh script. I am not sure it is woking. When I try to execute inotifywait I get

CANNOT LINK EXECUTABLE "inotifywait": library "libnotifytools.so" not found.

The although it is a different library, the message looks quite similar to the issue you reported. I wonder, do we need to install a missing library to get these script working?

[sotitrox]

All right I solved this with a symbolic link to the libandroid-support.so in the module folder to the system lib folder. In my device I had to do this: ln -s /data/adb/modules/com.piyushgarg.rclone/libandroid-support.so /system/lib/libandroid-support.so

But that failed to me, the system folder is mount in read mode only, so I made the symbolic link in the same folder, and mount the system folder in write mode in the filemanager, then just move the symbolic link to /system/lib/ and rename back to the correct name:

ln -s /data/adb/modules/com.piyushgarg.rclone/libandroid-support.so /data/adb/modules/com.piyushgarg.rclone/libandroid-support.so.2

1. mount system in write mode in the file manager
2. move the libandroid-support.so.2 to the /system/lib dir
3. rename back to libandroid-support.so

remember that the rclone bin for the magisk module is "reclonew", for config remotes is "rclonew config" and for mount just like the system module do is "rclonew remount"

sorry my bad english.

[micahriley88]

All right I solved this with a symbolic link to the libandroid-support.so in the module folder to the system lib folder. In my device I had to do this: ln -s /data/adb/modules/com.piyushgarg.rclone/libandroid-support.so /system/lib/libandroid-support.so

But that failed to me, the system folder is mount in read mode only, so I made the symbolic link in the same folder, and mount the system folder in write mode in the filemanager, then just move the symbolic link to /system/lib/ and rename back to the correct name:

ln -s /data/adb/modules/com.piyushgarg.rclone/libandroid-support.so /data/adb/modules/com.piyushgarg.rclone/libandroid-support.so.2

1. mount system in write mode in the file manager
2. move the libandroid-support.so.2 to the /system/lib dir
3. rename back to libandroid-support.so

remember that the rclone bin for the magisk module is "reclonew", for config remotes is "rclonew config" and for mount just like the system module do is "rclonew remount"

sorry my bad english.

You are awesome!!! I've been stuck on this issue all night! Thanks!