yashsingh1/xdaforums huggingface dataset:
[Magisk] pat357:
I guess I found a major problem : this causes fbind to fail to make any working binds.

By looking here in this log, one can tell that your phone is still using sdcardfs for the external SD,

while it should be FUSE to make fbind work.

Now, fbind normally disables sdcardfs , but for some unknown reason, it did not work in your case; very strange !

About your config.txt:

drop the line to set to permissive, will not help you and can cause further problems

if OGMods will never contain any media, the from_to is ok, but better is to use target (shorter)

target OGMods
obb

You could try to remove the module and start with a fresh install from the latest fbind-version.

Then re-post the output from

mount | grep -E '[0-9A-F]{4}-[0-9A-F]{4}'

Some other related questions

Are you on Magisk 15.3 ?

Do you have any other modules installed ? if so, which modules ? Are these working ok ?

Do you happen to have the battery related CS (also from VR25) installed ? If so, disable this module in Magic Manager for testing the fbind module.
[Magisk] sdz2:
How do you mount a LUKS volume in fbind?

The README is quite vague. The config_examples.txt file does not have any LUKS examples.

In my case, I have an encrypted FAT32 partition on the OTG (/dev/sda1).

Question: How do you specify the passphrase or key file?

EDIT Configuration and error message

I created an empty directory /mnt/ext

When I run fbind -b, it hangs after <Partition Information> for about a minute then continues with the error message.

shell@quark:/data/media/fbind # cat config.txt
part /dev/sda1--L /mnt/ext vfat
shell@quark:/data/media/fbind # fbind -b

<Partition Information>
Device /dev/sda1 doesn't exist or access denied.
***
mount: mounting /dev/mapper/sda1 on /mnt/ext failed: No such device
***
(!) sda1 mount failed
1|shell@quark:/data/media/fbind #

EDIT 2: Ask for assistance

Would you please provide your config.txt and fbind command(s) which mounted your LUKS partition successfully?
[Magisk] aseferfan:
I am on Magisk 15.3 with latest magisk manager, i only have ExSDCard Write Access Enabler module other than magic folder binder, and yes ExSDCard Write Access Enabler v2 seems to do its job right(v3 makes the device bootloop)

I have reinstalled this module 3 times now including 2 times with a complete ROM flash(I always install magisk module from recovery by flashing them because installing it in manager causes the app to crash)

Everytime same results with bound folders becoming file. and FYI link to my ROM which use a systemless devbase : DevBase v4.6

Is there any way to enable FUSE manually?
[Magisk] pat357:
About Magisk Manager crashing : did you try already the classic trick with cleaning the app cache & data ?

What about uninstall and clearing cache & dalvik in TWRP and then reinstall ?

Do you have any errors in the Magisk log ?

About sdcardfs :

It could be that this systemless implemented devbase is somehow overwriting the changes done by fbind.

Do you happen to have any .prop files in /data/devbase/system/*.prop ? or in /data/devbase/*.prop ?

Could you give me the output from

cd /data/devbase &&
grep -i -r -H sdcardfs *.prop
[Magisk] aseferfan:
I don't see any errors in magisk log while installing modules from within app, but the manager crashes anyways so i just install modules from recovery.

anyways here is the result after running

cd /data/devbase &&
grep -i -r -H sdcardfs *.prop

u0_a189@klte:/ $ cd /data/devbase &&
> grep -i -r -H sdcardfs *.prop
grep: *.prop: No such file or directory
2|u0_a189@klte:/data/devbase $ cd /data/devbase/system &&
> grep -i -r -H sdcardfs *.prop
1|u0_a189@klte:/data/devbase/system $

there is a build.prop under /data/devbase/system/ and here is the contents of that prop file

#
# BUILD_PROP_OVERRIDES_AND_ADDITIONS
#
wlan.wfd.hdcp=disable
ro.config.tima=0
[Magisk] ohtoulouz:
Help needed please

Hi everyone!

As strange as it seems, some folders are properly bound... and others are not.

I made a very simple config.txt file for test:

from_to "Music" ".fbind/Music"

from_to "Android/obb/com.FireproofStudios.TheRoom3" ".fbind/Android/obbTheRoom3"

fbind -m says it moves files but he does not move the .obb file (I checked and .fbind/Android/obbTheRoom3 was even not created)

fbind -b says it binds folders but it does not (for obb folder)

After reboot, .fbind/Android/obbTheRoom3 appears, but it was still impossible to move files with fbind -m (before or after fbind -u)

Even if I moves files manually and type fbind -b, the obb folder in not bound.

After reboot, the debug.log is:

Mon Sep 7 03:15:47 GMT 1970

<SD Card Information>

/dev/block/vold/public:179_65 /mnt/media_rw/A81A-0F17 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /mnt/runtime/default/A81A-0F17 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/fuse /storage/A81A-0F17 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/fuse /mnt/runtime/read/A81A-0F17 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/fuse /mnt/runtime/write/A81A-0F17 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

<Bind Folders>

[/data/media/0/Music] <--> [/mnt/media_rw/A81A-0F17/.fbind/Music]

[/data/media/0/Android/obb/com.FireproofStudios.TheRoom3] <--> [/mnt/media_rw/A81A-0F17/.fbind/Android/obbTheRoom3]

- Done.

(i) Nothing to clean

Music is properly bound: everything went fine (files were moved with fbind -m)

Android/obb/com.FireproofStudios.TheRoom3 cannot be bound. I have tried rebooting, moving files manually (because fbind -m does not move files and fbind -b does not even create .fbind/Android/obbTheRoom3 without a reboot). Could it be a problem with folders names containing "." ? What do I do wrong ?

Thanks for you help.
[Magisk] pat357:
Make a backup from this file (adding .bak extension) and add the following line to the build.prop it :

persist.sys.sdcardfs=force_off

and reboot the phone.

After booting up, then again, give me output from

mount | grep -E '[0-9A-F]{4}-[0-9A-F]{4}'

and from :

getprop persist.sys.sdcardfs

---------- Post added at 06:56 PM ---------- Previous post was at 05:58 PM ----------

Your syntax for the binding the obb file is not correct. Have you seen such things in the "example file" ??

try this config.txt

from_to "Music" ".fbind/Music"
obbf com.FireproofStudios.TheRoom3
[Magisk] ohtoulouz:
Hi [MENTION=4970217]pat357[/MENTION]

I saw obb, but not obbf in config_sample (didn't want to bind the whole obb folder).

Thanks for your help, will follow your advice.

Cheers

Edit: It worked, thanks again.
[Magisk] anonymvs_xda:
... awesome !

Everything worked like a charm. Just followed a tutorial ... :D:good::cool:

Samsung Galaxy J5 2015 (SM-J500FN), ROM OdysseyNote8-v1, Quasar_Kernel-v1.6, Android 7.1.1, Magisk 15.3 ...
[Magisk] shukla._:
How can I bind the whole Internal and External memories?

And if done so, will there be any problem?
[Magisk] rovingthief:
Nothing happens when I try to use 'su' then 'fbind -mb'

I try this on 2017.12.4, since the new version gives me an error "fbinds need a root" even though it is rooted. Can anyone help?
[Magisk] FHC1998:
Same problem here, I have to reboot my phone to make any changes in fbind effective, since any fbind command results in "(!) Fbind must run as Root" even though I am rooted and run "su" command before running fbind.

Android 8.1

Atomic OS Plasma 2.3

Magisk 15.4

Fbind 31.01.2018
[Magisk] VR25:
Been out for a while due to random internet access issues.

I didn't stop working during that time, though.

Can't thoroughly read all recent posts now, but I'll do it as soon as I get some free time -- and of course, push the new version.

Below are the current changelog and a few screenshots.

- Automatically disable ESDFS and SDCARDFS & enable FUSE

- "fbind" (no args) command now leads to a quick on-terminal reference; -h/--help added

- Log additional storage info

- Misc optimizations

- Optional SELinux mode handling (config lines: setenforce auto, setenforce 0)

- [TEST] Universal full external SD card access (new platform.xml workaround) -- some [or all] users may need to set SELinux mode to permissive to actually benefit from this (config line: setenforce 0)

- The `-l` (list config lines) option now shows each config lines & corresponding mount status

- Updated reference

The new storage permissions fix works fine for me. All apps have full/unrestricted read & write access to /mnt/media_rw/...

In addition, this appears to unlock "some" of the features of a native file system. In Oreo, for instance, symlinks on SD card seem to work.
[Magisk] pat357:
To bind-mount the entire intsd to extsd/.fbind (includes obb) ,

your config.txt located in /data/media/fbind/ is just one line :

int_extf

---------- Post added at 10:34 PM ---------- Previous post was at 10:14 PM ----------

I see you running Andoid 8.1 with Magisk 15.4.

There are some important changes in Magisk 15.4.

I suppose Atomic OS Plasma 2.3 is a custom ROM ?

Just a wild guess : run su -mm instead of just su.

su -mm is similar to running just su, but forced in global namespace mode, which is needed for fbind.
[Magisk] pat357:
It looks very promising !

I almost can't wait to see how you've solved the long hanging issue with SD-card permissions ....

Anyway, already looking forward to your next release !
[Magisk] sdz2:
How do you specify the key file or password for mounting a LUKS volume?
[Magisk] FHC1998:
Yes its a custom ROM.

Running su -mm gives the same problem. (Screenshot attached)

I'll try using magisk 15.3 and report back.

Thanks for trying to help.
[Magisk] FHC1998:
Update: Reverting to magisk 15.3 Solved the problem. Thanks!
[Magisk] FHC1998:
Thanks!
[Magisk] pat357:
Good to see you've fbind up and running !
[Magisk] y2klol:
Hey, I was wondering what tutorial you used? I want to use this but it's a bit overwhelming.
[Magisk] y2klol:
Alright, so I downloaded the magisk module and uses terminal emulator, granted it root, and typed "fbind -help" "fbind -u" "fbind -a" and "fbind" all these commands do nothing because "/system/bin/sh: fbind: not found". How do I get the commands working in the terminal?
[Magisk] godofsalt:
Hey there. MIGHT want to read the Opening Page. Gives details on how to use.
[Magisk] pat357:
Were there any errors during the install from the fbind module ?

Have you installed any busybox ? If not, install the one from the Magisk module repo (osmosis) : will be installed systemless.

Can you check, using a file-manager with root permissions, if you have the fbind directory in /data/media/fbind/.

Also check your the fbind script itself is in /system/xbin/fbind or in /system/bin/fbind.

If any of the above is not there, the fbind-module was not properly installed.

You've Magisk v15.3, right ?

---------- Post added at 05:46 PM ---------- Previous post was at 05:30 PM ----------

The one in the directory /data/media/fbind & /data/media/fbind/info

You could also just tell me what you want to accomplish, maybe I can give you a solution that will work.

Also, I've help people from starting zero in the past, read those posts too.
[Magisk] y2klol:
Thanks! I was looking only at the front page, didn't realise that the config_samples.txt had more info.
[Magisk] pat357:
Also the README.TXT has all the possible commands explained.

The install seems ok, but the debug shows something is not ok.

Fbind seems to fail to detect your extSD card.

What phone do you have ?

Can you also give me the output from this (run in a terminal window) :

mount | grep -E '[0-9A-F]{4}-[0-9A-F]{4}'
[Magisk] anonymvs_xda:
Hi everyone,

I have the from_to "viber" ".fbind/viber" line in config.txt, now I can make a photo inside the viber, but when I tap to "send", Viber is always say "This photo is no longer available.", and /storage/xxxx-yyyy/.fbind/viber/media/Viber Images/ is empty. When I make a photo with camera and share it with Viber from Gallery, that is working. When setting up the .fbind I was on : Samsung Galaxy J5 2015 (SM-J500FN), ROM OdysseyNote8-v1, Quasar_Kernel-v1.6, Android 7.1.1, Magisk 15.3. Since then, I updated to Quasar_Kernel-v2.0, Magisk 16.0, but I didn't try this with old Kernel, and Magisk.

EDIT:

When I execute fbind --rollback everything is working with Viber. Is it some bug in module, or I messed something up ?
[Magisk] pat357:
No, you didn't mess up anything !

The likely problem is that Viper can not write to your extSD card due missing permissions : this is also the reason why the photo doesn't show up on SD card.

There is ATM no fix for this AFAIK, but VR25 (developer from the module) has let us know recently he found a way to give every app r+w access to extSD card.

I expect we will see more about this when he releases an update for the module.

So hold on a little for now till the next release of fbind !
[Magisk] MrMmmkay:
Hi there,

I just can´t get it to work :(. I try to move my WhatsApp Folder from internal to external memory, here is my config.txt:

intsd_path /storage/emulated/0
extsd_path /storage/44D6-D880

from_to WhatsApp .fbind/WhatsApp

and debug.log

Sat Feb 24 14:21:10 GMT 2018

<SD Card Information>

mv: can't rename '/storage/44D6-D880
/.fbind_bkp/config.txt': No such file or directory

<Bind Folders>
[/storage/emulated/0
/WhatsApp] <--> [/storage/44D6-D880
/.WhatsApp
]
- Done.

(i) Nothing to clean

than I run fbind -mb, it takes about 2 minutes and finish with success, but nothing changed, no data in .fbin/WhatsApp

What do I wrong?
[Magisk] rovingthief:
Hello, Can I make my external SD partitioned with fat 32 and ext4? So I can backup my app data on the ext4 partition.
[Magisk] pat357:
Why did you specify these special values for intsd_path & extsd_path ?

These should not be used unless you have problems with the default values.

Did you try the default values ? I thought so.

The defaults are used if you don't specify any intsd_path or extsd_path

Try this config.txt :

from_to WhatsApp .fbind/WhatsApp

---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------

1. Yes, you can partition every SD like this.

2. Yes, if you have the extSD card with 2 partitions (fat32 and ext4), you can backup all your app-data.
[Magisk] MrMmmkay:
Hi,

Thanks for your answer. Here is the new debug.log :

<SD Card Information>
/dev/block/vold/public:179,1 /mnt/media_rw/44D6-D880 vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /mnt/runtime/default/44D6-D880 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/44D6-D880 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /mnt/runtime/read/44D6-D880 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /mnt/runtime/write/44D6-D880 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0

<Bind Folders>
mkdir: can't create directory '/mnt/media_rw/44D6-D880/.fbind/WhatsApp
': Invalid argument
mkdir: can't create directory '/data/media/0/WhatsApp': Operation not permitted
[/data/media/0/WhatsApp] <--> [/mnt/media_rw/44D6-D880/.fbind/WhatsApp
]
mount: mounting /mnt/media_rw/44D6-D880/.fbind/WhatsApp
on /data/media/0/WhatsApp failed: No such file or directory
- Done.

(i) Nothing to clean
[Magisk] pat357:
Did you reboot your phone ?
[Magisk] MrMmmkay:
Yes I did, several times ?
[Magisk] pat357:
You did run su before running fbind -mb, did you ? Next time try with su -mm instead of just su.

What phone do you have ? Made and model please.

What android version ? (5, 6, 7.0, 7.1.x, 8.0, 8.1)

What version of magisk are you using ?

v15.3 should be OK

v16.0 there have been reports of fbind not working on v16.0. After going back to v15.3 fbind was working.

Are you running stock or a custom ROM ? Any links ? Custom kernel ? links ?

To be sure, can you give me the out from this, running in a terminal :

mount | grep -E '[0-9A-F]{4}-[0-9A-F]{4}'
[Magisk] MrMmmkay:
- Sony Xperia XZ1 Compact

- Android 8.0

- magisk v16.0

- stock ROM 47.1.A.12.75

- kernel: https://xdaforums.com/xperia-xz1-co...nel-sony-xz1-compact-16-january-2018-t3736068

-

mount | grep -E '[0-9A-F]{4}-[0-9A-F]{4}' (su)
=======================
/dev/block/vold/public:179,1 on /mnt/media_rw/44D6-D880 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/44D6-D880 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp)
/dev/fuse on /storage/44D6-D880 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp)
/dev/fuse on /mnt/runtime/read/44D6-D880 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp)
/dev/fuse on /mnt/runtime/write/44D6-D880 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp)

Magisk 15.3 does not work with the XZ1 Compact :crying:
[Magisk] aseferfan:
Oki thanks for removing Termux but it seems almost any module is tripping safety net with v13 of magisk XD

so unless magisk is update and fixed to acutally hide the modules properly can't exactly report your module is tripping safetynet

I also have the problem of the mounted folder being displayed as a file in ES file manager,but i moved the contents beforehand to externel sd card and app detects that externel as internel folder so i'm not really complaining :D

also here is a log of magisk(if it helps) when your module and sd card enabler is enabled(SD card enabler is the only module i found to be keeping safetynet green atm XD)
[Magisk] cantenna:
im using a number of modules, safteynet check passed.
[Magisk] VR25:
You see, by "device specific" I mean it may affect all ROMs/Kernels available for that device, since all of those use part of code from the device's original software sources. I know I said the module is not the issue. Still, workarounds "may" be implemented on it to get over the issue. It's just that those have nothing to do with the way the module works at its core level.

"SELinux contexts" is the boss in this game. I've been digging into it these days.
[Magisk] p50kombi:
yeah, I have tried several mouning scripts and programs, none really seem to work.

I guess maybe mounting is just a thing of the past with my 10 :(

Still kudos for all your hard work mate.....
[Magisk] VR25:
Oh, the SafetyNet war... I see what's happening XD

First of, that's a Magisk issue. Well, Magisk is failing to umount many components, not limited to this module's. I see that "fbind_move" from this module is on the list. Try deleting that from the zip and reinstall the module. You'll have to move your files manually if that script is missing. It's the only part of this module that goes into system.
[Magisk] VR25:
Thanks, but don't rest yet. I'll build a version with its own, "standalone-separated-from-system" busybox binary. That may work, who knows... ;)
[Magisk] p50kombi:
I'll happily test it out for you... :svetius:
[Magisk] American_Jesus:
I've the same problem, manual mounting show up as file

# mount -o bind /mnt/media_rw/7E0A-14F3/Test /data/media/0/Test

# mount | grep Test
/dev/block/vold/public:179_65 on /data/media/0/Test type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

However using Apps2SD mount folder, that doesn't happen

# mount | grep Download
/mnt/media_rw/7E0A-14F3/Download on /mnt/runtime/default/emulated/0/Download type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=6)
/mnt/media_rw/7E0A-14F3/Download on /storage/emulated/0/Download type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=6)
/mnt/media_rw/7E0A-14F3/Download on /mnt/runtime/read/emulated/0/Download type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=23)
/mnt/media_rw/7E0A-14F3/Download on /mnt/runtime/write/emulated/0/Download type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=7)
[Magisk] VR25:
Yes, that's what I'll test further by implementing a standalone busybox into the module and use it instead of the system busybox. I'm sure Apps2SD uses the same command to bind folders. Perhaps it just does it with a separate busybox. That way, SELinux contexts we're talking about might not apply. I need to confirm just that. Thanks for your tests and report, man! :)
[Magisk] TopperBG:
That's App2sd option.

Изпратено от моят HUAWEI GRA-L09 с помощта на Tapatalk
[Magisk] VR25:
Well, yes... but the app might just as well copy your system busybox to its home and execute it from there, instead of using it from the standard location. So, it's about the location of busybox, not the version/type.
[Magisk] TopperBG:
Yeah, that means that option.

And it works.

Изпратено от моят HUAWEI GRA-L09 с помощта на Tapatalk
[Magisk] aseferfan:
WAIT,more than 1 module works in magisk WITHOUT tripping safetynet?

WHAT SORCERY IS THIS??? XD

but could you please tell me which version of magisk you are using and which modules? ill be grateful for that :)

Edit : Sorry op i know this is definitely not the place for magisk module discussion but i have to know :D
[Magisk] cantenna:
commit 8b6, the changelog for this commit was to allow for safteynet to pass wifh modules.
[Magisk] Captain_Throwback:
I'm watching this thread with keen anticipation, as I also have an HTC 10 and have the issue where bind mounts are working to /data/media/0 but the folders are showing up as zero byte files in /sdcard. If this is indeed a kernel issue, do we have any idea what the cause in the source might be? I could build a modified kernel for my device if I had a clue what to change. Since this issue persists even with SELinux set to permissive, that suggests that SELinux isn't the problem, though I suppose it could still be related to file context, somehow. When I do an ls -laZ of /sdcard/ the error I get on those files is "Cross-device link." Does that mean anything to you?

EDIT: Note the context of the other folders in the root of /sdcard - perhaps the issue is related to sdcardfs?

EDIT 2: Added another screenshot. Note the context on those same folders in /data/media/0 - it's showing sdcardfs when it should be media_rw. That must be why they don't show up. Can the proper context be set on those folders somehow?

EDIT 3: I just noticed the double slashes in the first screenshot - any idea where those came from?

EDIT 4: Just checked another device where it's working, and the second screenshot looks the same. So I'm not sure if that's at all related now :/.

EDIT 5: Guess that makes sense, since we're bind mounting from the sd card, it should be sdcardfs. This seems to be a limitation of the emmc driver on the HTC 10. I'm not sure why other devices have similar issues. Maybe that gives me somewhere to start looking in the source, though (not sure when I'll have a chance to do that).
[Magisk] p50kombi:
Welcome aboard cap'n
[Magisk] Captain_Throwback:
Also, for the sake of being thorough, I'm not using any busybox on my system; toybox is installed by default. According to the help output of the mount command, there's no need to "mount -o bind." See screenshot.