yashsingh1/xdaforums huggingface dataset:
[Magisk] Wolfcity:
When you say you are on stock Oreo you must be member of a soak test?

As Oreo isn't official atm [MENTION=5228676]VR25[/MENTION] , the developer of this module isn't able to test it. But you could help to find the reason why it's not working on stock Oreo. First of all a recovery log of the flashing procedure would be helpful. Maybe [MENTION=5228676]VR25[/MENTION] is reading this and can guide you better than I can.

If it's a Oreo related issue a lot of users will run into this problem.
[Magisk] freeZbies:
No, I didn't know it was meant to be used with the G5+, especially because in the magisk repos it doesn't state anything at all.

I'll try get the recovery logs and post them here. By the way, I edited my last post so as to show what I've done so far.

Thanks.
[Magisk] freeZbies:
Here are the logs. Couldn't include them in the previous post.

Ps: by not adding the /data/.magisk the results are the same
[Magisk] Wolfcity:
No, it's not just for the Moto G5+, my fault. I was thinking that I was posting in another thread. I'll edit my post.

It's for several Motorola devices that suffer from that loopback bug. These devices have a F2FS formatted data partition and aren't able to mount images r/w.
[Magisk] freeZbies:
No problem. If you get any updates, please mention me and I'll be notified.

I think unlocking Cedric's bootloader was a mistake, even because I got the soak test Oreo without unlocking bootloader (Ota files are signed)

Now I lost my warrant and can't use magisk, which was my only goal at first.
[Magisk] Wolfcity:
Maybe you're right. If there's any further soak update to come you will have a problem, maybe you're lucky and the build you're on becomes the official one.

But I think this module isn't working for you because you are on Oreo, I'm using it on 7.0 since the day I rooted my potter and magisk is working well with all installed modules. Motorola may have changed something in 8.1 what makes this module fail but I'm pretty sure that [MENTION=5228676]VR25[/MENTION] is able to fix it.

Btw, have you checked if your data partition is still F2FS and the cache partition is not?

Edit: Ok, your recovery log states that data is still F2FS and cache ext4.
[Magisk] freeZbies:
Well, I'm not sure how to check that, but given I never formatted my data partition, it must still be f2fs (I just sideloaded the soak test with locked bootloader and unlocked it afterwards).

By the way, the partition is still encrypted, as I can't use twrp if I don't decrypt it.

However, the cache partition is really ext4
[Magisk] gkornaks:
Moto G5 Oreo 8.1

Hi,

Any update on this? I've got an exact issue with my Moto G5 soak Oreo 8.1

Thanks!
[Magisk] Wolfcity:
The developer [MENTION=5228676]VR25[/MENTION] has some problems with his internet connection at the moment:

https://xdaforums.com/apps/magisk/module-magic-folder-binder-t3621814/post77155703

But he will for sure check this if he has access.
[Magisk] zahna:
I did a little further digging and discovered that my issue might not be the f2fs module. When I apply the f2fs module, the links in /data/adb are created to magisk.img and magisk_merge.img in /cache, but when I reboot, something is overwriting those symlinks with actual files, which I then don't have permission to read. Any ideas what's going on?
[Magisk] Wolfcity:
Maybe that's magisk related. Post it in the magisk main thread (if you're using magisk 16) or in the beta thread if you're on 16.7. Maybe it's a magisk bug. Provide a TWRP log. [MENTION=4667597]Didgeridoohan[/MENTION] may know something more about it.
[Magisk] Didgeridoohan:
I do not know what's going on. Recovery log from installation, a logcat from boot and the Magisk log (if existing) might help.
[Magisk] VR25:
Update coming within a few days.
[Magisk] freeZbies:
No, so far it just doesn't work on stock 8.1

Enviado de meu Moto G (5) usando o Tapatalk
[Magisk] Wolfcity:
Good news! :good:
[Magisk] freeZbies:
I found a way to make it work.

Looks it up here
[Magisk] VR25:
Update will be up within a day or two.

Just wanted to let you all know that reported issues are caused by recent versions of Magisk and Android. The upcoming update will support Magisk 15-16.6 and Android P.

Why not Magisk 16.7 as well?

I found two big and deal-breaking bugs on it. One of the debugging tools I use (set -x) outputs nothing; post-fs-data.d and modules' post-fs-data scripts are not executed.
[Magisk] Wolfcity:
Seems to be that there are known bugs in 16.7. There are some unofficial builds like the ones from [MENTION=3306843]kantjer[/MENTION] with fixes in them but I'm sure [MENTION=4470081]topjohnwu[/MENTION] will release another beta soon. It's great that you update your module for the last official (16.0) .
[Magisk] Wolfcity:
Edit: v.17.0 stable has been released. If you want to have a look into it.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post77496559
[Magisk] DS-1:
I can't install this: https://xdaforums.com/showpost.php?p=75242358&postcount=1

I have a Lenovo P2 with lineageos 15.1 official and magisk 17.1.

It tells that magisk 14.0+ is required...
[Magisk] Wolfcity:
You´re in the wrong thread here, it´s just for the loopback bug module.

You should head over to the Magisk thread: https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[Magisk] VR25:
Build 2018.9.2 is up!

Can't upload the new zip now. Get it from Magisk Manager.
[Magisk] Lucuitas:
How could I open Magisk Manager if I can't event boot into my device because of this loopback bug? :|
[Magisk] VR25:
[MENTION=4932555]Lucuitas[/MENTION], here's the zip.

Edit: added to the OP.
[Magisk] woozie.2007:
is not working, i flash it from twrp and if i dont install any module is still there, but if I install one module, all of them will disappear, magisk 17.1
[Magisk] VR25:
[MENTION=1284298]woozie.2007[/MENTION], which device and ROM are you using?

How big are your cache partition and the module you're trying to install?

P.S., the lastest and only Magisk version I tested this on is 16.6, and everything works fine (multiple modules installed).
[Magisk] woozie.2007:
I have moto g5, but until magiks was updated to 17, everything works fine. Now, like i said if i restart the phone all modules disappear and i have to reboot to twrp and flash only your module and modules appear again until next restart. But with the last update from you i have no module in folder. If i not install nothing, your module remain there even after restart, but if i install viper or something else, all disappear. Sorry for my english

Ihave only your module installed and v4a, not many module only two, and i have stock 7.0 rooted
[Magisk] VR25:
[MENTION=1284298]woozie.2007[/MENTION], your English is fine. Don't worry too much about it.

What's your native language?

Try the following:

1. Rename or remove /sbin/.core/img/f2fs-loopback-bug-workaround/service.sh

2. Remove /data/adb/magisk_merge.img and /cache/magisk_merge_.img

3. Reboot into TWRP, install a module, reboot

Note: after the above, you must install modules from TWRP only.
[Magisk] Wolfcity:
This seems to be a bug of magisk 17/17.1 itself. My modules (especially the ones that mount APK's) disappear on other devices without the loopback bug too. As [MENTION=5228676]VR25[/MENTION] posted the updated loopback bug module is tested up to v16.6.
[Magisk] woozie.2007:
Better to wait to topjohnwoo maybe will update the magisk...for the moment i will not restart the phone anymore :)
[Magisk] Natan_Gameron:
Does not work on Magisk 17.1

In version 17.1 of Magisk when trying to install "F2FS Build 2018.9.2" I get the error message: 1, but when installing "F2FS Build 2018.8.1" no error occurs but I can not install any modules.

Build 2018.9.2:

(Updater error: 1)

Build 2018.8.1:

(Without any error but it is not possible to install any module.)
[Magisk] VR25:
NOTICE

Do not use Magisk versions 16.7, 17.0, or 17.1. Recent user reports suggest these have major bugs which prevent several modules from working properly. Stay on 16.6 for now and you'll be fine.
[Magisk] Natan_Gameron:
Ok thanks I decided to use version 16.0 even though everything is working perfectly.
[Magisk] vrmay83:
Old version of magisk don't show some modules

I am using magisk v16 because f2fs loopback bug module do not installs in magisk v17.1 but in old versions some modules like vanced YouTube do not shows in download menu even any old version also not shown so please fix v17.1 I think there is some issue in v 17.1 not in f2fs loopback module update 2018.9.2

Thanks
[Magisk] Wolfcity:
This belongs in the Magisk general thread. [MENTION=5228676]VR25[/MENTION] develops the loopback bug module, not Magisk.
[Magisk] xeropressence:
Moto e4 stock 7.1.1 rom, magisk 16.6 the latest version doesn't survive a reboot. Flash from twrp, it shows up in modules, reboot and its gone.
[Magisk] Natan_Gameron:
The update 2018.9.2 only works in Magisk 17.1 use the old version.
[Magisk] Wolfcity:
That build is named f2fsfix in the OP, the release notes say "Improved compatibility" but I can't find any further information that it's especially for magisk 17.1, even if it makes sense. May I ask where the info comes from ?
[Magisk] zahna:
I have the same thing on my Moto E4 as well. They're asking for logs, but I'm not sure how to get logs to them, and don't currently have time to figure it out. If you have the time to submit logs on both of our behalf, I'd be grateful.
[Magisk] Wolfcity:
2 posts above: The latest build seems to be only for magisk 17.1. Roll back to the previous f2fs loopback bug module (2018.8.1).
[Magisk] xeropressence:
2018.8.1 also failed on 16.6

Rolled back to magisk 16.0 used 2018.8.1 and it worked fine.
[Magisk] VR25:
The latest build is for Magisk versions 15 to 16.6.

The log is stored at /sbin/.core/img/fs2fs-loo*/ as "f2fsfix.log".

"f2fsfix-$version.zip" is just a simpler and shorter nickname for the module.

I'm not having much free time these days to update all my modules. But I'll look into the reported issues further once I get an extra second. Thanks.
[Magisk] AMShiech:
Same issue here. I'm on v17.1 and Not only does f2fs fix not survive reboot but all modules disappear upon reboot. And reappear after reflashing f2fs fix in TWRP.

Im gonna flash 16 again for now and see if that fixes it.

---------- Post added at 12:49 AM ---------- Previous post was at 12:26 AM ----------

Nevermind I guess I can no longer get root with anything but the newest version of magisk. I'm pretty new to magisk root and it's had me scratching my head for quite some time. If I ignore the update notification for too long i randomly lose root and am forced to update which seems to happen very frequently compared to other root solutions (namely SuperSU). So until there's an updated module I guess I'll have to reflash the f2fs fix when I want my modules. Not a huge deal.

Before this started happening though I also updated the apk for the first time since I got this phone so I'm gonna see if reinstalling the older apk version works.
[Magisk] madbat99:
Yes, use the APK you had previously, also magisk 16. If all is working, don't update. The reason SuperSU doesn't prompt an update is because it's dead and sold to a Chinese company that has not updated or announced anything in over a year
[Magisk] VR25:
That's bad, but interesting nonetheless... I've seen a couple of reports on this... ?

Something (not f2fsfix) might be wiping your cache partition on boot or before system shutdown!

Could you check that? If there's no magisk_.img file in there when all modules are missing, that means it's really happening. Thanks.
[Magisk] nshimose:
Hello guys, how I'm not an advanced user, someone could me explain the step by step to install the module?

I'd already see that the modulo not is workin in Magisk 17.1, so I'll use the version 16.0...

I need install firt the F2FS or Magisk?
[Magisk] Natan_Gameron:
You first install Magisk 16.0 (I recommend it because the 17 is with many bugs) after this the F2FS Bug Fix, I recommend the version v2018.8.1, the 2018.9.2 is not surviving the reboots if I want I can send you a video but it is in Portuguese. :good:
[Magisk] nshimose:
No problem Natan, I'm Brazillian too.

I had already tried to install in version 16.0 but had not got it, I will try again but now with the F2FS v2018.8.1.

And I need to delete which files? I found only /data/adb/magisk.img in my device

---------- Post added at 08:34 PM ---------- Previous post was at 08:00 PM ----------

I installed Magisk v16.0 and F2FS v2018.8.1 but now the module I need to install no longer appears in the list of modules within Magisk :(

I need to install the Sony Framework
[Magisk] Wolfcity:
Which version of the Magisk Manager have you installed? It should always be the build fitting to the magisk.zip, in case of magisk 16 it is MM 5.7.0.
[Magisk] Natan_Gameron:
Só instalar o F2FS Bug Fix que já vai resolver.
[Magisk] VR25:
Eu também falo português, mas só ofereço suporte nesse idioma pelo Facebook ou mensagem privada aqui no fórum.

I speak Portuguese as well, but I only offer support in this language through Facebook or PM here on XDA.

Will push a quick update soon to support Magisk 17.
[Magisk] nshimose:
I have installed the latest version MM 6.0.0... Can I downgrade for 5.70 version or I need to reinstall the Magisk?

Edit: I re-installed Magisk v16 but I ca'nt pass in Safety Net Test neither MM 5.70.0 nor 5.80.2, so I installed MM 6.00 again... :(

I installed the F2FS too....

But, after I installed the Magisk v16 the module that I need install didn't appear from module list anymore...
[Magisk] nshimose:
I'm confused...

How my goal was to install the module Sony Framework, I don't not why but when I did the downgrade for the versions below Magisk v17 I can't find the module on field download from Magisk.

So, different that you told me I installed the F2FS version 2018.8.1 in Magisk v17 and MM v6.0 and I didn't have problems with this.

Even so, after I installed the F2FS, I can install the Sony Framework, but when I reboot my device both modules F2FS and Sony Framework disappeared.

I was about to give up, but I tried one last chance to do the installation at the same time, both the Sony Framework and F2FS via TRWP Recovery, and after I rebooted my device, both modules were installed in Magisk. And all it was working for me :laugh:

But how always, I have a new problem here... When I reboot again my device both modules disappears again, and for use the apps I need to re-install all again and cannot reboot my device. :(

Does anyone have an idea of what to do so that these modules do not "disappear"?
[Magisk] madbat99:
Wait for an update to this module like the developer said to do.

Or learn how to build a kernel for your device with a loop-back bug fixed. or ask in your device's Forum if anyone has compiled a kernel with the loop-back bug fixed
[Magisk] AMShiech:
Do you happen to know which apk version is compatible with 16.00? Right now i have v6.00 but i cant remember exactly which version i had before the update. I apologize if this is a stupid question. Im just very busy working and havent been able to find the time to do the necessary searches lol. I manage data for a call center so im literally on the clock morning day and night, married to my phone.

If anyone can provide a download link to the proper apk it would be much appreciated. I suppose in the time it took me to type this post i could have found it on my own hindsight being 20 20 lol. :eek:

---------- Post added at 02:39 AM ---------- Previous post was at 02:31 AM ----------

Where exactly should this magisk_img be located? Not entirely sure where to look.

You say something might be wiping my cache partition on boot. The only app that comes to mind is the boot manager xposed module.
[Magisk] VR25:
The path is /cache/magisk_.img.
[Magisk] madbat99:
I think APK version 5.6.1 was in magisk 16. That's the one that's in the zip anyways. I just extracted it and took a look.
[Magisk] madbat99:
That's the APK that's inside the magisk 16 zip
[Magisk] VR25:
**2018.10.9 (201810090)**

- Bug fixes

- Latest module template, with added sugar.

- Magisk 15-17.2 support

- Updated documentation

Notes

I'm on Magisk 17.2 and it's not executing this module's service.sh script.

How do I know this service.sh thing isn't broken?

- It does everything it's expected to when executed manually!

So, until I find out why Magisk isn't working properly (for me at least), install ALL Magisk stuff from custom recovery only!

Latest systemless Xposed is also misbehaving on Magisk 17.2, whether or not this module is installed.

I don't need an F2FS-patched kernel, nor this module, BTW. Doing this purely for you guys out there who do. Thanks.
[Magisk] daniel_m:
Thanks a lot!

I hate to see how people like you spend time on fixing things that phone manufacturers broke and don't give a damn about :mad:
[Magisk] eliaferri:
I tried f2fs on the s8 it doesn't start

could this module work?

or I did something wrong in setting up the f2fs
[Magisk] Wolfcity:
Is your data partition F2FS formatted?
[Magisk] VR25:
I though I would ask... why do you want to install this on S8?
[Magisk] Thanostsak:
For some reason the new update seems to have a conflict on my device (AGS-W09). When it boots everything seems to be working fine until a second consecutive reboot breaks everything. The previous version (9.2) works fine though, so I guess if it ain't broken no need to fix it.

You working on something that you don't actually need is the most altruistic thing I have seen in a while. Thanks a lot!
[Magisk] nshimose:
The same happening with me, but in my case, this also occurred with versions 8.1 and 9.2 ( I didn't try others versions). My device is a Moto G5 Plus...

Always that I reboot my device I need to install the modules again by TRW Recovery...
[Magisk] Thanostsak:
In your case it seems that something wipes the cache during or after the reboot. You should look into it.
[Magisk] nshimose:
Hum...

Could you help me with this?

I have no idea what can be...
[Magisk] eliaferri:
yes

---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------

i was looking for a way to boot in f2fs, i found this module, this doesn't work?
[Magisk] VR25:
Those getting everything broken after a second reboot, try the following workaround...

After the first reboot (right after installing), remove </sbin/.core/img/f2fs*bla*bla/service.sh>, </data/adb/magisk_merge.img> and </cache/magisk_merge_.img>.

Note that after doing this, you'll only be able to install modules and update Magisk from TWRP.

Uh... ? nah...

I still think this module is not for you.
[Magisk] mmephisto:
I'm using a Motorola Moto G5s plus, Android 7.1.1, with Magisk 16.0 in place - and each version of f2fsfix is working (2018.10.9, 2018.9.2 and 2018.3.6).

But when upgrading to Magisk 17.x (no matter if 17.0, 17.1, 17.2) I always get following error message showing up in Magisk Log Window:

mount /sbin/.core/block/loop10->/dev/.img_mrg failed with 13:Permission denied
and
mount /sbin/.core/block/loop08->/sbin/.core/img failed with 13:Permission denied

Reverting back to Magisk 16.0 solves the issue, all back to normal.

What am I doing wrong ?
[Magisk] madbat99:
Try using the uninstall zip and uninstall 16 then install 17
[Magisk] mmephisto:
Sorry, I forgot to mention this, I'm doing it this way.

I'm always using the newest version of Magis-uninstaller-yyyymmdd.zip (here Magisk-uninstaller-20180921.zip), then I do the installation. I'm rebooting as well between these steps.

But I got no clue why all versions of f2fsfix are working fine with Magisk 16.0, but starting with 17.x it fails to work. Installation works fine, it seems(!) to work, and setting Applications in Magisk-Hide is working as well for the time until I reboot the phone. But when rebooting, all magisk-hide settings are gone due the failing mount (see my previous post)

Justz to note - no errors during installation, only Magisk-Hide settings are not saved due to failing mount !

Any recommendations/ideas ? Something must have changed in magsik from 16 to 17 ?

Edit:

I completely removed Magisk 16 (Magisk uninstaller) and installed 17.2 without any issues. Then I rebooted the phone and installed f2fsfix-2018.10.9.zip with TWRP.

All working fine, checking Magisk-Hide, added Apps, still all ok, no error messages in Magisk Log.

Then I rebooted the phone and got these "Permission denied" errors again, all Magisk-Hide settings are lost.

This is the only issue I have, Magisk Hide Settings lost due to failing mount :(

Strange, no idea why this happens
[Magisk] AMShiech:
So I was delighted to see a new version of the f2fs bug fix up that claims to be compatible with v17. I flashed it hoping to get all my modules back and have everything survive reboot finally but I installed it in TWRp, rebooted and the fix was listed in modules but none of my other modules were there so I tried to reinstall YouTube vanced module and both modules disappeared after reboot.

I tried reflashing the old version of f2fs fix hoping it would bring my modules back but no dice. The only module listed was the f2fs fix but none of my other modules. It seems my modules are now unrecoverable after flashing the new version of f2fs fix. At a loss here.

Also tried installing the older magisk manager apk and it says the file is corrupt even though I redownloaded it several times.

---++-++update++-++---

I just uninstalled magisk altogether in twrp and flashed back to v16. Currently reinstalling all my modules. Hopefully v17 becomes more stable for my device in the future.
[Magisk] mmephisto:
I found another fix to solve the issue with MagiskHide on v17.x

- Moto G5s Plus, Stock ROM 7.1.1, Stock kernel

- install Resurrected Kernel (https://xdaforums.com/moto-g5s-plus/development/kernel-resurrected-kernel-t3716267)

- install Magisk v17.2 (maybe 17.1 will work as well)

- enable MagiskHide, select apps you want to hide - and they are still there after phone rebooted !

- NO need to install f2fsfix (unfortunately I did not succeed to make MagiskHide settings permanent with it on my Moto g5s plus)

This is the solution how I succeeded to make MagiskHide work on my phone :)

Maybe it is going to help another Moto G5s plus owner as f2fsfix seems to work on many other phones in an appropriate way

THX :good:
[Magisk] madbat99:
Of course a kernel with the loop-back bug patch in it will work perfectly. That's the first suggestion when you have a moto device with the loop-back bug in it to find a custom kernel with it patched. This module is for those who have no such custom kernel.
[Magisk] mmephisto:
Sure, you are completely right.

But nevertheless I would really appreciate having a working solution without a custom kernel - means a f2fsfix only solution without custom kernel, because it's sometimes hard to find a good-working custom kernel, being sure it is working in the next OS (or patch) release as well.

Hope you guys will succeed making it work on stock-only kernel as well (for Moto G5s plus), many thanks for your effort you already spent on this !!!
[Magisk] omino:
Using F2FS_Loopback_Bug_Workaround-2018.9.2 fixes the issue on Moto G5 Plus with Magisk 17.1

Modules are still there after the second reboot.
[Magisk] VR25:
So, it seems there's something else causing modules to disappear! I've seen this report many times already. How come this module works for some (inc. myself) and not for others?

Do you use MagiskHide?
[Magisk] omino:
I did have a few apps selected in MagiskHide when I experienced the issue with the latest version.

After switching back to F2FS_Loopback_Bug_Workaround-2018.9.2, I had to reinstall all modules and I noticed that no apps were selected in MagiskHide.
[Magisk] VR25:
For the record, I'm using the latest version and Magisk 17.2. MagiskHide is enabled, but in default state (no custom apps added). It's been like that since the latest f2fsfix release day. Never had the <modules disappearing> issue.

My first recommendation was to check whether /cache is being whipped out on boot.
[Magisk] omino:
I thought about the cache being wipe out on boot, but I struggled to figure out what. Moreover, why wouldn't it happen with the previous version of f2fsfix?

So, I am with you that something else may be interfering.