yashsingh1/xdaforums huggingface dataset:
[Magisk] DrPglixq:
Does anyone could help me with the app_data, I am lost there.

Do I need to partition my sdcard ? Fat32 (where my files are located), Ext4 (for app_data)?
[Magisk] VR25:
app_data works with either a separate partition or the main with a Linux file system. So, you can format your entire SD card to F2FS (fast) or EXT4 (may take a LONG time). The config syntax is "app_data pkg_name". Next build will have the option to mount app data to an EXT4 image file instead.
[Magisk] Shikhs:
Just wanted to know if this will updated to work on 8.1?
[Magisk] zdoe:
ok - looks like what i need. but please guide me - i didn't even find an installable ZIP on the 1st page...! is the module going to work on moto 5G (stock, magisk 11.6)?
[Magisk] elzafir:
Guys, what am I missing?

I have installed Magic Folder Binder and rebooted (with empty config.txt). Now I have set up my config.txt, went into Termux, input the command, and nothing. The command 'fbind -mb' in Termux doesn't return anything (see attached screenshot).

I'm on Redmi Note 3 (kenzo), using Xiaomi.eu ROM (v7.12.14), with MagiskSU 14.0, Stericson Busybox, and Magic Folder Binder v2017.12.4.

This is my config.txt:

EDIT: I rebooted and I see in the log that the folders are bound! (see attached screenshot)

EDIT 2: What does it mean that fbind doesn't support loopback devices? What constitute a loopback devices? How to check if mine is one?
[Magisk] pat357:
Did you type

su

before you typed fbind -mb ?

If you did, try again with "su -mm" (without the quotes!) instead of just "su", and then "fbind -mb"
[Magisk] elzafir:
Thanks for your reply. Yes I did type su before fbind -mb, as shown in my screenshot. I will try "su -mm" once I get home. Do you mind explaining what is the -mm command stands for and why do I need it?
[Magisk] pat357:
"su -mm" is the same as just "su" with the addition to launch su (root) in a "global name space", independent of of what you have setup in Magic Manager -> settings -> namespace-mount modus.

Mount/Unmount operations often require a global name-space, so with "su -mm", you'll always have root in global-namespace.

Check in a terminal for other su options :

su --help
[Magisk] VR25:
Issues could be resulting from recent Magisk versions as opposed to Android 8.1 itself.

An update is in the works and should be available in a few days.

You're supposed to download the zip from Magisk Manager.

There are a few bugs in the current version (including mount namespace handling). An update will be up soon.

Loopback device is an .img files mounted as if it were an actual (physical) drive. An example of that is magisk.img. The upcoming fbind version will allow you to handle that.

With such a feature, you can emulated storage device (i.e., create a fake SD card or a hidden/reserved space for nasty secrets you may have).
[Magisk] elzafir:
Thank you for your reply. I can't wait to try the update.

As for WhatsApp media, I get "Sorry the media doesn't exist on your internal storage" whenever I click on a received picture. But If I send an image, it put the picture into Media/WhatsApp Images/Sent folder and correctly bound to SD Card.

Do you get the same WhatsApp behaviour as me? I'm afraid this will break my current WhatsApp back up, so should I unbind for now and wait for the update?
[Magisk] _Tille_:
Path containing Blanks/Spaces

Hi,

I seem to have run into some difficulties, perhaps just a silly question but I did not find any sample or hint in the existing posts.

How do I specify a path containing spaces/blanks in the config.txt i.e. assuming I just want to mount .../WhatsApp/Media/WhatsApp Video? I tried these two possibilities:

- from_to WhatsApp/Media/WhatsApp\ Video WhatsApp/Media/WhatsApp\ Video

- from_to "WhatsApp/Media/WhatsApp Video" "WhatsApp/Media/WhatsApp Video"

Both give me No File or Directory found error in the debug log.

Thank you
[Magisk] VR25:
If your scenario is the same as _Tille_'s, read the response below. Otherwise, that's the classic storage permission issue -- add the word "perms" to your config, reboot, wait about 2.5 minutes after boot -- or until you see WhatsApp in one of the last lines of /data/media/fbind/debug.log -- and see if that helps.

Quote the paths. ;)
[Magisk] _Tille_:
Okay, I must assume I have not understood the given examples, as it still seems I'm doing something wrong.

Any help is appreciated

- I'm running a Samsung A3 (2017) on Nougat.

- TWRP + Magisk

My current config.txt

intsd_path /storage/emulated/0
from_to "WhatsApp/Media/WhatsApp Video" "WhatsApp/Media/WhatsApp Video"

Current debug.log

Thu Dec 28 08:18:59 GMT 2017

<Config Update>
- Done.

<SD Card Information>
/dev/block/vold/public:179,33 /mnt/media_rw/32F7-DF7F sdfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,utf8,namecase=0,adj_req,symlink=0,bps=512,errors=remount-ro 0 0
/dev/fuse /mnt/runtime/default/32F7-DF7F fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/32F7-DF7F fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/32F7-DF7F fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/32F7-DF7F fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

<Bind Folders>
mkdir: can't create directory '/mnt/media_rw/32F7-DF7F/WhatsApp/Media/WhatsApp Video
': Invalid argument
[intsd/WhatsApp/Media/WhatsApp Video] <--> [extsd/WhatsApp/Media/WhatsApp Video
]
mount: mounting /mnt/media_rw/32F7-DF7F/WhatsApp/Media/WhatsApp Video
on /storage/emulated/0
/WhatsApp/Media/WhatsApp Video failed: No such file or directory
- Done.

<Cleanup>
- Done.

In addition it seems it created a new additional folder "0/WhatsApp/Media/WhatsApp Video" within "/data/media". Not sure why that is? I have now basically two folders ./0 within /data/media.
[Magisk] zdoe:
ok - got that, thanx.

download ok, install completes with error. how to troubleshoot? or - could the zip be installed from recovery?
[Magisk] elzafir:
Thanks [MENTION=5228676]VR25[/MENTION] for your reply. It turns out the problem with WhatsApp received pictures problem was Magisk' doing. Updating tp v15.1 solves it.

Thank you for this awesome app!!! Can't wait for the GUI.
[Magisk] DrPglixq:
Any help on this one?

should I replace the mmcblk1 with my desired partition?

like mmcblk1p3?
[Magisk] RokCruz:
Sorry for the question, there's a way to bind all folders on emulated/0 to sdcard? Like Xposed module Xinternal??
[Magisk] VR25:
Yes

Put int_extf in your config. This binds all internal_storage folders to external_storage/.fbind/FolderName.

Everyone else who's stuck somewhere, please wait for the next release -- thanks.
[Magisk] zdoe:
no jive.
[Magisk] Didgeridoohan:
That looks like you're trying to install a template 1500 module on a v14.x Magisk installation or something along those lines.

Scratch that... This is a 1400 module. Try installing from the Manager instead.
[Magisk] VR25:
That seems to be a zip integrity issue. Re-download the module and try again.

I wonder what the "Please install Magisk v14+!" is coming from, though...

Don't you have Magisk installed already?

Edit: [MENTION=4667597]Didgeridoohan[/MENTION], nice posting speed! ;)

The latest repo version uses template 1400.
[Magisk] Didgeridoohan:
Yeah... Saw that right after posting. Even had time to edit before you I believe. :p
[Magisk] _Tille_:
Made some progress with WhatsApp Video

- Had to change the internal SD to /data/media/0 on my Samsung A3.

- Quoting the path did not work for me, the blanks did mess the path Up. Instead I escaped the blank with \

Debug Log contains no errors. Looks fine to me. But WhatsApp behaves strange. Taking a Video works, it shows up in both locations. But it does not sent, the status in WhatsApp does not update. Also, cannot receive videos.

Strange, did anybody get WhatsApp moved? I wonder if I should try to move the whole thing instead of just one subfolder.
[Magisk] VR25:
Interesting...

Now that you pointed that out, I never actually tried bind mounting WhatsApp Video folder itself. Instead, I always target the whole WhatsApp directory.

A note: I saw you using "from_to WhatsApp/* Whatsapp/*." That's not a good idea -- you'll end up with duplicates. When bind mounting media directories, the destination folder's name must always start with a dot. A traditional practice, in particular with "from_to" is starting the destination path with ".fbind/".
[Magisk] DrPglixq:
Is it possible to mount my 3rd partition of my sdcard without moving any data to it?

This is my config:

I just want to mount my 3rd partition, but I don't want to put anything on it.

I already added the extsd_path , but it still binding everything to the 3rd partition
[Magisk] VR25:
"part" replaces the sdcard path used by fbind. You can't override it. I can however take you inquiry as a suggestion for a new feature -- and I actually like the idea.
[Magisk] RokCruz:
no luck for me, after run command on termux nothing happen and directories not binded
[Magisk] VR25:
[MENTION=8353427]miadevice[/MENTION], it seems you didn't move the files prior to rebooting. Have you read the entire OP? :p
[Magisk] VR25:
Strange... did you install the actual game before trying to bind? V2017.6.19-1 is up. See if that fixes WhatsApp issue.

Edit: have you moved GTA VC folder over without leaving the same folder (empty) in the origin? You could have run fbind_move as root to move your data. You're supposed to move the data, but leave the source folder there (empty). fbind_move does that for you easily.
[Magisk] VR25:
[MENTION=271041]p50kombi[/MENTION], [MENTION=5263982]aseferfan[/MENTION], v2017.6.19-1 is up. You should be good now. [MENTION=4778658]cantenna[/MENTION], [MENTION=4075919]vikasb32[/MENTION], you guys should try it too.
[Magisk] p50kombi:
Nope, I always just move the files inside the folder, the actual folder is empty on internal sd and populated in the external sd.

So how does the move command work?

You set the find txt file and without rebooting then do the move command?

You see, that wasn't entirely clear for me.

Also, if you have to do it that way, when does it create the folder?
[Magisk] VR25:
Quick Anouncement

First of, thank you for so many reports! That makes the development much easier as I have just a single device to test the module on.

I noticed that some folks don't even bother to read the ENTIRE OP before asking questions/reporting things. Well, if you don't want to be helped, I won't be able to help you either. :(

Some of the issues might have been avoided in the first place if you have actually taken the time to read and understand the documentation.

Moving on to another topic...

Just to prove that obb binding is really working for me and others... check the screenshots! No game crashes or missing folders.

That is not to say I'm giving up on those who can't get it to work though. I'll keep working to the best of my abilities, until I can't do no more. ;)
[Magisk] VR25:
You simply run fbind_move as root and that's it. No parameters, no hassle. It will move and OVERWRITE files of currently not bound folders present in your bind list. Basically, every time you make changes to the list, you should run that command to ease your life BEFORE rebooting to apply changes. Notice the OVERWRITE part -- any existing files in the destination folder will be overwritten.

I didn't implement that to run on boot since it would break things -- i.e., the actual bind process would be significantly delayed. I'm sure I don't need to explain why that's a big no no.

Sorry if I wasn't specific enough in the OP.
[Magisk] p50kombi:
I get that, but how can it move files into a new folder if it hadn't created that folder yet is my point. :)

And I just tried fbind_move and it is just bit moving the files, got this error as per attached and it is not moving any of the files.

Selinux is permissive.

Could it be that I'm using magisk hide in magisk v12?

Also, did you check the log in attached to my post re the obb binding?

It's trying to bind to a folder that isn't there on my device.
[Magisk] cantenna:
same result as before.
[Magisk] p50kombi:
Some additional info,

After binding the WhatsApp folder, my internal storage looks like this, WhatsApp showing as file. Also added the log for extra info.

So something somehow isn't working yet for me on the htc 10

Only trying to help.. :)
[Magisk] VR25:
Oh, I see... well, since fbind_move does what it does, I built it so that it creates the necessary folders automatically. Otherwise it would fail miserably. :D

I checked the log, yes. That's the classic issue with obb binding I'm trying to solve. In your case though, it shows something curious, "No such file or directory." At this point I'm not sure what that is, given that you have everything set up correctly... but stay tuned for the next version.

About Magisk Hide, hmm, I'm unsure, but it may not have anything to do with that.

Finally, that error... I forgot something, goddammit! :laugh:

I'll fix it right away! Expect v2017.6.19-2 to be up in a few minutes.
[Magisk] VR25:
Gooddamit! :D At least now I'm sure enforcing SELinux is not exactly the issue here.

So, now you just confirmed you're in the same boat as [MENTION=4075919]vikasb32[/MENTION].

I'm betting my 2 cents that's a Kernel issue (for the 3 of you). As osm0sis mentioned a few posts back, some device specific ROMs don't allow "mount -o bind" command to work the way we want here.

p50kombi, try this to check whether your mount command is doing its job as desired:

Run the following two commands in sequence as root:

1.

umount /data/media/0/Whatsapp

Check whether WhatsApp folder is still displayed as a file. If so, remove it and create a new one.

2.

mount -o bind /mnt/media_rw/1A0B-2E6A/.fbind/WhatsApp /data/media/0/Whatsapp

See if it still shows up as a file and report back.

Edit: every bit of help gives me strength! You help me with reports I provide you with functional stuff. Win-win. Thanks!
[Magisk] miadevice:
Hm no, fresh phone, no files exist in download or dcim. Cam an downloadmanager should put fresh ones in her folders but they cant.

Edit: jep, reading entire thread before
[Magisk] VR25:
You may be facing the same SELinux contexts issue others are dealing with. A solution is yet to be found.
[Magisk] VR25:
Those who installed v2017.6.19-2, please re-download it. Something was missing.
[Magisk] koko115:
I download this version. And my apps like dentex youtube downloader "Acces danied for Download folder" in /data/media/0 and i dont see Download folder in /storage/emulated/0

I think problem is in /data/media/0 and /storage/emulated/0

Because when i change in /magisk/fbind/service.sh intsd=/data/media/0 to instd=/storage/emulated/0 bind works, but apps like dentex youtube downloader download to /data/media/0/Download and i dont see downloaded file in /storage/emulated/0/Download

And then Download folder in /data/media/0 and /storage/emulated/0 is difrent folder.

Galaxy s8+
[Magisk] cantenna:
S8+ here too, no go, yet.

Just seems like to me that this is a permission problem. Are we dealing with symbolic links or bind?

It miggt be worth noting i face a simular issue with sshfs, i could only mount over wifito specific locations onvthe S8+., perhaps those same locations would work here? Issue would still be how do we change the default path for obb directory?
[Magisk] VR25:
I don't think obb's path is the issue. I've looked into that already. Also, permissions don't seem to be the problem either. If one of those were to blame, I wouldn't be able to bind obb in my device. It has the same exact paths as yours.

FAT32 & exFAT, the two commonly used file systems for SD cards don't support symbolic links nor file permissions.

Days before having the idea to build this module, I've tried formating my card to f2fs and ext2 -- symlinks worked but the system recognized them all as files. So, they're of no use in this case. If they fully worked, no such module would be needed, as symlinks are way superior to what we're trying too accomplish here.

So, the verdict is, we're dealing with ROM/kernel specific issues. The module itself has nothing to do with the problem.
[Magisk] cantenna:
sadly I've tried all available kernels and roms so this means that this is baked into the source.. too bad we dont know what needs to be changed.
[Magisk] p50kombi:
All a no go unfortunately.. See attached screenshots
[Magisk] vikasb32:
I am using aosp extented in my Redmi note 4 and this module is working fine but same in my yureka this module didn't working (mounted folder work in data/media/0 but not in internal memory) so i don't think its Rom problem but yea may be kernel problem?
[Magisk] zdoe:
as you guessed i've redownloaded a few times. many many from tha magisk manager ("installation error!), but a few times also to install with TWRP.

i think the "Please install Magisk v14+!" is coming from another module i've tried to install. i'm on magisk 11.6. according to the threads about my gadget (moto G5 stock), i should not update to keep root. am i running to compatibility issues here? can your module work with 11.6?
[Magisk] DrPglixq:
This module is a must for miui users haha,

I've been using miui and this magisk module, Everytime I format I update my device or change miui flavor, I always install magisk because of this Magic Folder , and it always do the job done :)

Thank You
[Magisk] VR25:
**2018.1.2 (201801020)**

- Added wildcards support to `fbind -as`

- Automatically restore config backup upon installation if current config is missing or empty

- Automatically set/reset `Mount Namespace Mode` to Global

- Backwards compatible with Magisk versions older than 15, suporting template v4+

- Fixed a critical bug that caused absurd delays in the folder binding process

- Major optimizations

- Major reference updates, especially config_samples.txt -- definitely worth checking that out

- Smart SELinux mode handling -- "if enforcing; then set to permissive; do fbind stuff; set back to enforcing; fi" ;)

- [TEST] New storage permissions workaround

From now on, I'll be pushing smaller updates more frequently as opposed to larger ones every two centuries. Requested/suggested features will come one by one.

[MENTION=3644193]zdoe[/MENTION], 11.6 is too old. You can still try the latest module build, though.

- Replace /data/magisk/util_functions.sh with this from the latest Magisk version. You may want to backup the current file before proceeding.

- After that, you may be able to install the new fbind version.
[Magisk] khnoizer:
updated from magisk manager, and go straight to bootloop after reboot.

EDIT: uninstalled magisk, and reinstall latest version of the module (this module are just really important for me), and now it's working. So, it's can only flashed through twrp now?
[Magisk] PalychUA:
Invalid packed archive! Not Installed.
[Magisk] santo_007:
Can you please explain how you successfully achieved to move folder containing space
[Magisk] _Tille_:
Dear Santo_007,

I was able to get a working mount by escaping the blank with a backslash i.e.

- from_to WhatsApp/Media/WhatsApp\ Video WhatsApp/Media/WhatsApp\ Video

No other quote or measures taken. The mount itself that was created looks successful and works fine, just not together with WhatsApp, but that might very well be a limitation of WhatsApp or something strange with the way how the Samsung Devices handles/binds storage.

Best regards
[Magisk] zdoe:
there is no util_functions.sh -file at /data/magisk -folder. i can add it, of course. should i? is it gon' get read?
[Magisk] pat357:
It might break the v11.6 Magisk as well, as all the logic has to be present in the different Magisk files (magiskboot, magisk, ..)

Why not just update to the latest Magic v15.2 ? (First make a nandroid-backup with TWRP or similar).

If you're running stock, there could be an issue with updating Magisk because of a faulty f2fs implementation from Moto stock ROM's.

(see here for more info https://xdaforums.com/showpost.php?p=70492947&postcount=8793 )

If you're running a custom kernel/ROM (with the fix or format data to ext4) , you should be OK with updating to 15.2.
[Magisk] pat357:
[MENTION=5228676]VR25[/MENTION]

Please correct me if I'm wrong but I think there is a small mistake in README.md :

Under ### CONFIG SYNTAX it states :

- intobb_path [path] --> i.e., /storage/emulated/0 (ignore for default -- /data/media/0)
- intsd_path [path] --> i.e., /storage/emulated/0/Android/obb (ignore for default -- /data/media/obb)

Should the syntax for these 2 be switched ?
[Magisk] VR25:
I didn't face this issue, but I'll investigate what could've been wrong. -- Thanks

Have you tried redownloading the zip and reinstalling it from MM and TWRP?

Yes, add it and try installing the module.

The logic is only for Magisk itself. I built fbind so that it is able to work with older Magisk versions just as well. Regarding the faulty F2FS, I out together a workaround for that -- [Magisk Module] F2FS Loopback Bug Workaround -- No Custom Kernel Needed.

Oh ***, my bad! You're right. -- Thanks :D
[Magisk] tamjan:
There is a typo in the package in the Magisk repository. A "slee" instead of "sleep", in core.sh I think. Don't know if that's why the latest version works less good than the previous one...
[Magisk] VR25:
Thanks for pointing that out.

... And, yes, that's a major issue, but only for those who have to specify "extsd_path".

The next update will pop up very soon with fixes, optimizations & new features. Stay tuned.
[Magisk] tamjan:
And I did that in the previous version. In an attempt to be able to see and write to the binds, by pointing to the directory created by the extSdCard module. Worked so-so anyway. :)

Thanks for your efforts!
[Magisk] wonkxin473:
I think, I followed the instructions in config_sample.txt, README.md

for my

Samsung Galaxy Note 4 SM-N910F

and changed default folders in

config.txt,

intsd_path /storage/emulated/0

extsd_path /storage/7B61-3E76

intobb_path /storage/emulated/0/Android/obb

from_to test .fbind/test

but after fbind -b, fbind -u intsd_path folder becomes a file until deinstalling the module, extsd_path folder stays as it is and /system/sbin/fsbind[24]: sestatus not found is displayed before done.

debug.log contains:

Thu Jan 4 09:53:38 CET 2018

<Config Update>

- Done.

<SD Card Information>

/sbin/.core/img/fbind/service.sh: /data/media/fbind/.config/debug[2]: slee: not

/sbin/.core/img/fbind/service.sh: /data/media/fbind/.config/debug[2]: slee: not

...

Ask for help
[Magisk] Sebastl:
Read above. Slee should be Sleep
[Magisk] R324D:
I got error fbind must run as root

Running magisk 15.2

Screenshot attached.
[Magisk] VR25:
What's the output of su -c id -un?
[Magisk] R324D:
Result is "root"
[Magisk] zdoe:
i am on rooted stock, and told at the rooting threads that 11.6 magisk is the one that works. have not tried other versions. however, i have thought of formatting data partition to ext4. would that work on rooted stock? they must've had some reason for doing f2fs - if only to make our life more complicated...
[Magisk] zdoe:
yes, once i had util_functions.sh in /data/magisk/ your module installed seemingly ok from the magisk manager. however, after reboot at the modules-tab of magisk there's still nothing showing.

and installing from TWRP, i get error 2, as the screenshot.
[Magisk] R324D:
Well, I install previous version of fbind (2017.12.4)

And it's working fine as expected.

I assume everyone has been updated to latest version of fbind and no issue like this has been reported, which mean this is only happened to me. Any thought?
[Magisk] protechtedd:
Can I use this to bind two internalSD folders together? For instance:

I want this because some apps place their files/photos into the Pictures folder, but I want them to place them all into DCIM. This makes it greatly easier for my syncing method.
[Magisk] Killer7Mod:
In my phone, show this error:

fbind[24]: sestatus not found