fbind

[sjevtic]

I should've clarified. Fbind does this, but only for bind-mounts. Here's how your setup would look like:

1. Mount the EXT4 partition the usual way:


2. Overlay the mount point with a bind-mount (works like sdcardfs, but better):

How does a bind mount achieve the emulation of having no filesystem permissions? I must be missing something here.

 

[Shihabus Sakib Rad]

@VR25 I installed this module today and it's working great so far on android 11.

I am not sure how to use cryptsetup. I want something like "target Pictures" BUT with encryption like EncFS or rclone-crypt. So that, if put a file in $intsd/Pictures, the file will be encrypted $extsd/Pictures.

With Rclone Remount & ExSDCard Write Access Enabler magisk modules, I could somewhat achieve this on previous android versions.

Can I do this with fbind module? if so, what line do i write in config,txt.

 

[K0rgar]

@VR25 Can you please check if /data/media/0/.fbind does exist or not?
Because if it's there, then it goes into loop, can't mount, I had to reboot, manually delete such folder and finally termux, su, fbind -m

 

[VR25]

Yes but if bindfs wont work in enforced env. How can we expect fbind to work. Does it work ( after binds integration ) and grant RW access to underlying dir - if so what bindfs ops are used in fbind

nsenter -t 1 -m bindfs -o nosuid,nodev,noexec,noatime,nonempty -u 0 -g 9997 -p a-rwx,ug+rw,ugo+X --create-with-perms=a-rwx,ug+rw,ugo+X --xattr-none --chown-ignore --chgrp-ignore --chmod-ignore

 

[VR25]

Thanks. I was using a root explorer but didn't erase from internal storage. Only from microsd was erasing.. Anyway i solve it the hard way. Uninstall fbind magisk plugin. Then i could erase the fold. Reinstall fbind and start again.. It worked.

You have to unmout first, to be able to delete.

 

[VR25]

If i remove microsd, and inserted it back, will the symbolic link in internal still works?
Thanks,

Mount point != symbolic link.
You have to unmount before removing the sdcard, and remount after reinserting inserting it.

 

[VR25]

@VR25 I installed this module today and it's working great so far on android 11.

I am not sure how to use cryptsetup. I want something like "target Pictures" BUT with encryption like EncFS or rclone-crypt. So that, if put a file in $intsd/Pictures, the file will be encrypted $extsd/Pictures.

With Rclone Remount & ExSDCard Write Access Enabler magisk modules, I could somewhat achieve this on previous android versions.

Can I do this with fbind module? if so, what line do i write in config,txt.

Cryptsetup is used by fbind for disk encryption.
You need an encrypted partition. Once mounted, the syntax for folders is the same.

part [-o <mount option...>] <[block device[--L[,password]]]> <mount point> ["fsck <option...>"]` Auto-mount a partition.
# The `--L` flag is for LUKS/2 volume, opened manually by running any `fbind` command.
# The filesystem is automatically detected.
# The defaut mount options are `rw` and `noatime`.
# `e2fsck -fy` is always used for supported filesystems.

 

[mashiro2296]

Hello! I Installed this module & it works fine on my J7 (2016) Device running on crDroid 10.
I've use the fbind wizard. done some non-media files (data folders) and it works but once I reboot my device bind doesn't work. I need to go to terminal and once I enter command 'fbind -um' the targeted folder binds again.

tried to add 'permissive' in the config and 'fbind -f' in terminal but same scenario occurs. once I reboot my device the targeted folder not binding.

Hope you may help me. Thanks in advance.

 

[P650SE]

Hi everyone,

I wondered if anyone can help a total beginner? Just recently I purchased a 256GB microSD card for my phone, I would like a way to create an encrypted volume on the SD card that can be mounted onto the device's filesystem so that the files can be freely accessed from within any file manager or gallery app.

As I understand it, I should be able to achieve what I am looking for with this module, but I don't have any knowledge of using terminal so this whole thing is overwhelming to me, I'm rooted with Magisk 25.1 on Android 11, I have the Fbind module installed and Termux from F-Droid. I downloaded the provided cryptsetup binaries and extracted them to /data/adb/vr25/bin/cryptsetup/ with permissions 755 but when I run the command fbind -C it says cryptsetup: can't execute: Is a directory

I can't tell what I'm doing wrong, I wondered if someone with better knowledge could guide me in the right direction, or offer some simplified step-by-step instructions on how to set this up?

Would really appreciate any assistance.

Thanks (and sorry!)

 

[Shihabus Sakib Rad]

You need an encrypted partition. Once mounted, the syntax for folders is the same.

Newb here. Could you explain in non-technical terms if it is possible to achieve what I want to do.
I want a folder, say, $extsd/Diary to be accessible on $intsd/Diary but with encryption. If I put a file firstday.txt on $intsd/Diary, A encrypted file would appear in $extsd/Diary.
Basically, it is similar to how cryptomator, EncFS or rclone-crypt work where encrypted file would be stored on Ext-SD but mounted on Int-SD. This way, I could set this $intsd/Diary path from any App as a Backup folder or Data storage location.

For this use case, could you write me the config file I need for "Diary" folder.

 

[Dark_Phoenix004]

I've been using fbind for long now.
Since Android 6.
Now in my new Android 11( Redmi note 11) it seems fbind is working fine, but after some time, the WhatsApp folder bind just unlinks without any warning. And idea or suggestions about that?

 

[the gladiator]

Using fbind from @VR25 since years with many ROMs and phones, it's more tricky meanwhile to setup the module, but of course not impossible, that's why i thougt i share my experiences with the latest release ( 071221 ) and my new toy ( Xperia XZ2 LOS 18.1, Magisk v23 ) .

I had some trouble to find the path of my intsd, without specify the internal SD in config.txt my binds were mounted, but without write rights, Chrome downloads and the DCIM folder were not accessable.

I installed Kuder Disk Info from APK Mirror, it's not in Play Store anymore, a very helpfull tool to look WHAT is WHERE mounted. Found my intsd under

/mnt/pass_through/0/emulated/0

so i was able to complete my config.txt

So, the first line in your config.txt should be WHERE the intsd is, second line WHERE the extsd is. Sometimes you simple have to try and error, it's all not magic.

Finally, maybe it's usefull for some people, my config.txt, with the device above.

intsd_path /mnt/pass_through/0/emulated/0
extsd_path /storage/xxxx-xxxx
target Android/data
from_to DCIM .fbind/DCIM
from_to Download .fbind/Download
obb


With this config the whole Android/data and Obb folder is on the extsd, DCIM and Download are on extsd too, accessable from the Cam and from Chrome. Media in linked DCIM are visible in gallery, and can be deleted via gallery. All fine.

So - specify the intsd and extsd - that's all.

As 0LDST4R, I'm using fbind since years over many smartphones and I consider it crucial in my digital life (it goes without saying that VR25 is my unparalleled guru). I wanted to install fbind on my daughter's smartphone with Android 9, Magisk 22.1 and fbind v2021.12.7.

It was ok BUT the sd card was disregarded; that means that it binded folders on internal memory. Useless! The trick was to add the "path" in the config file as 0LDST4R was suggesting, as simple as that (once you know) !!!

 

[MarkLev]

@VR25 , also to anyone if you have some answers:
What are the differences between media and non-media in term of fbind's behavior?
Why is there a need to distinguish them?

I am new to fbind, so...

 

[MarkLev]

Ok, here is what I found after playing around with fbind:

** fbind wizard's behavior:
In fbind wizard, there are 3 kinds of binding: Media, Non-media and OBB
There is no difference between Media, Non-media and OBB except the way wizard generates config.txt

Example: When choosing Media, the next prompting will generate the below line in config.txt for user's input "myDir":
from_to "myDir" ".fbind/myDir"
When choosing Non-media, the next prompting will generate the below line in config.txt for user's input "myDir":
target "myDir"
It is equivalent to:
from_to "myDir" "myDir"
When choosing OBB, the next prompting will generate the below line in config.txt for user's input "myDir"
obbf "myDir"
It is equivalent to:
from_to "Android/obb/myDir" "Android/obb/myDir"

** Here is the fbind wizard's behavior in comparison with fbind -m (fbind mount command)
With config from_to "myDir" "myDir":
If there's existing "myDir" in ExternalSD, that "myDir" is renamed to "myDir.old", and then fbind will move intSD-"myDir" to extSD, and mount extSD-"myDir" to intSD-"myDir"

fbind -m (fbind mount command):
With config from_to "myDir" "myDir"
If there's existing "myDir" in InternalSD, that "myDir" is ignored, and then fbind will mount extSD-"myDir" to intSD-"myDir"

 

[AnonVendetta]

Ok, here is what I found after playing around with fbind:

** fbind wizard's behavior:
In fbind wizard, there are 3 kinds of binding: Media, Non-media and OBB
There is no difference between Media, Non-media and OBB except the way wizard generates config.txt

Example: When choosing Media, the next prompting will generate the below line in config.txt for user's input "myDir":
from_to "myDir" ".fbind/myDir"
When choosing Non-media, the next prompting will generate the below line in config.txt for user's input "myDir":
target "myDir"
It is equivalent to:
from_to "myDir" "myDir"
When choosing OBB, the next prompting will generate the below line in config.txt for user's input "myDir"
obbf "myDir"
It is equivalent to:
from_to "Android/obb/myDir" "Android/obb/myDir"

** Here is the fbind wizard's behavior in comparison with fbind -m (fbind mount command)
With config from_to "myDir" "myDir":
If there's existing "myDir" in ExternalSD, that "myDir" is renamed to "myDir.old", and then fbind will move intSD-"myDir" to extSD, and mount extSD-"myDir" to intSD-"myDir"

fbind -m (fbind mount command):
With config from_to "myDir" "myDir"
If there's existing "myDir" in InternalSD, that "myDir" is ignored, and then fbind will mount extSD-"myDir" to intSD-"myDir"

Thx for the info. I've always wondered what the difference is between the 3. Apparently, there are none, except how the configuration file gets written.

 

[kreatifchk]

What to do if fbind -u doesn't work? I did the binding through the terminal with the fbind -b command. Only reboot helps.

 

[MarkLev]

What to do if fbind -u doesn't work? I did the binding through the terminal with the fbind -b command. Only reboot helps.

From github page:

-b|--bind-mount <target> <mount point>
Bind-mount folders not listed in config.txt.

It must be listed in config.txt so that it can be unmount later.

 

[kreatifchk]

From github page:

It must be listed in config.txt so that it can be unmount later.

That is, if it is mounted through the terminal, then the only way to unmount this to restart the device?

 

[MarkLev]

That is, if it is mounted through the terminal, then the only way to unmount this to restart the device?

Run: umount -f <mountpoint>

 

[Teddan Fred]

Noob question here.
In termux when I run fbind (wizard) and press "a" to see all commands.
When I come to END I can no longer execute any new command.
What can I do exit this command list?
Thanks!

edit. Found it! press "q"