huskydg / magic_overlayfs Goto Github PK

one plus 8t，HOS 11.0.14.14，magisk versionV26.1,overlayfs version 3.2.1
installed mobile don't boot

I tried to add service which should start at the beginning but it do not

the service works well in other read / write system

android version : 13

Env:
KernelSU: v0.5.7
magic_overlayfs: v3.0.3
OS: ColorOS 13 (Android 12)

The fault has been identified as this module by loading modules one by one.

The Bluetooth headset connects normally, but it doesn't sound.

如题，ksu刷入后nfc会失效，处于无法启动状态

Trên Kernel v10753 mới nhất
_ magisk_overlayfs v2.20 thì module "Zygisk On KernelSU" không load được
_ magisk_overlayfs v2.11 thì module "Zygisk On KernelSU" load bình thường

After installation and reboot the module is off.
Module again in Magisk on, then restart. There is a 2nd restart and the module is off again.

There were no problems with magisk-overlayfs-release_2.29.1.

Edit: An update did not work anymore.
Removed and reinstalled, works.

Hi, I'm trying to hide system/addon.d from my banking app, I think i should be able to do that with this module but I've never used OverlayFS before.

I've installed the module and I think it's running OK, but which folder do I make the change I need?

I think I need to make an 'opaque directory' in the 'upper' folder but I can't figure out where that is?

Any help to point me on my way would be appreciated

Thanks!

overlay.log

After flashing magisk_overlayfs，my oneplus 9 with lineageos20 can not boot normally，the screen shows qualcomm crashdump mode。
Then i reflash boot and lineageos20，it can boot（without magisk），but when i reflash magisk in recovery mode，it boot into qualcomm crashdump mode again。

          ![Screenshot_2023-04-10-17-41-08-406_bin mt plus](https://user-images.githubusercontent.com/103242499/230877271-db9cdb10-3347-4d67-9f29-e792633a43b0.jpg)

Miui14 mounts nfc to /system/product through this folder /product/pangu/, so it should not be moved.

Originally posted by @cy12300 in #8 (comment)

log as attatchment
lose after reboot and module become disabled, re-enable module and overlay come back
v2.24
android 12
F2FS
overlayfs.log

Ok so I just installed it on KSU. I set overlay mode to 1. After reboot I tried to remove some apps from system but root explorer says no access as it seems system still RO. Any ideas
Android 13
Redmi Note 10 Pro

When module installed, all Bluetooth parings disappears every time, phone restarting. Also configuration change system app trying apply and can not do it something.
After disabling the module in magisk, old bluetooth config, that was before module
overlayfs.zip
overlayfs.zip
installation, exists.

Hello, i'm using magical_overlayfs module on ksu. But there is a problem that sometimes this module causes bootloop (like screen blanking) and when i try to force reboot, KernelSU will disable this module so i can't enable this module. How i can fix this or i should to wait new release? Thanks for this module and reading my issue!
KernelSU_bugreport_2023-08-19_17_39.tar.gz

Mod looks really promising!

Installed on my rooted device (Lenovo smart clock 2, Android 10) using built magisk mod.

But fs is still not writable after reboot 😢

# cat /cache/overlayfs.log                                                                                                            
--- Start debugging log ---
mount: tmpfs -> /mnt/overlayfs_irgcftsbdmzslhcogtug
mount: overlay -> /mnt/overlayfs_irgcftsbdmzslhcogtug/system [lowerdir=/system,upperdir=/mnt/overlay_system/upper/system,workdir=/mnt/overlay_system/worker/system]
mount failed, try read-only overlayfs...
mount: overlay -> /mnt/overlayfs_irgcftsbdmzslhcogtug/system [lowerdir=/mnt/overlay_system/upper/system:/system]
mount: overlay -> /mnt/overlayfs_irgcftsbdmzslhcogtug/vendor [lowerdir=/vendor,upperdir=/mnt/overlay_system/upper/vendor,workdir=/mnt/overlay_system/worker/vendor]
mount failed, try read-only overlayfs...
mount: overlay -> /mnt/overlayfs_irgcftsbdmzslhcogtug/vendor [lowerdir=/mnt/overlay_system/upper/vendor:/vendor]
mount: overlay -> /mnt/overlayfs_irgcftsbdmzslhcogtug/product [lowerdir=/product,upperdir=/mnt/overlay_system/upper/product,workdir=/mnt/overlay_system/worker/product]
mount failed, try read-only overlayfs...
mount: overlay -> /mnt/overlayfs_irgcftsbdmzslhcogtug/product [lowerdir=/mnt/overlay_system/upper/product:/product]
mount: /mnt/overlayfs_irgcftsbdmzslhcogtug/system -> /system
mount: /mnt/overlayfs_irgcftsbdmzslhcogtug/system -> /sbin/.magisk/mirror/system
mount:  -> /sbin/.magisk/mirror/system
mount:  -> /sbin/.magisk/mirror/system
mount: /mnt/overlayfs_irgcftsbdmzslhcogtug/vendor -> /vendor
mount: /mnt/overlayfs_irgcftsbdmzslhcogtug/vendor -> /sbin/.magisk/mirror/vendor
mount:  -> /sbin/.magisk/mirror/vendor
mount:  -> /sbin/.magisk/mirror/vendor
mount: /mnt/overlayfs_irgcftsbdmzslhcogtug/product -> /product
mount: /mnt/overlayfs_irgcftsbdmzslhcogtug/product -> /sbin/.magisk/mirror/product
mount:  -> /sbin/.magisk/mirror/product
mount:  -> /sbin/.magisk/mirror/product
mount done!
clean up
umount: /mnt/overlayfs_irgcftsbdmzslhcogtug

cheers!

My device is Galaxy Tab S7+, model SM-T976N. I'm running an Android 13 AOSP gsi ROM by phhusson. My kernel is unmodified stock, but my boot.img is patched with Magisk Delta stable 26.1.

After flashing your module zip, my device gets stuck in an endless bootloop. I am able to boot back into Android, but only by going into TWRP and deleting your module. I haven't made any changes, only flashed the zip. My data partition is f2fs, cache partition is ext4. And my data partition isn't encrypted, I disabled that.

Months ago, your module worked for me, before you switched to mounting an img file at boot. But that old zip release is gone. Your module hasn't worked for me since then, always a bootloop.

I don't think it's a corrupted img issue, since I haven't manually modified it in any way. If it is corrupt, then your module is causing it.

I can't even give logs, they are all zero bytes in size (magisk.log and overlays.log)

Hello, today I saw sn-o-w/WSA-Magisk#1 that support OverlayFS. And I would want to test it. So I want to asked about the method to add it to Windows Subsystem for Android

Do i need to uninstall to remove upperdir files in android/data folder. One more questing after installing overlayfs module storage space used in root directory is reduced to 1% how is this possible, before module installation it was 99%.

KernelSU Manager version 0.6.1 and kernel version 5.10.177, as well as LSPosed version 1.8.6 (6712).

KernelSU_bugreport_2023-07-05_17_47.tar.gz

When OVERLAY_MODE=0 and OVERLAY_LEGACY_MOUNT=false, NFC stops working.

When OVERLAY_MODE=1 and OVERLAY_LEGACY_MOUNT=true, LSPosed cannot be opened and conflicts with the Clipboard Whitelist module.

What configuration is needed to make this folder writable?

When I flash this using Magisk after the reboot, Magisk app can't detect root boot image, but when I remove the module from TWRP and reboot Magisk app detect root.

When I installed the magic overlayfs module using KernelSU, the Bluetooth headset stopped making sound, and it only worked when the module was disabled. At present, this problem appears in the test of OnePlus 11 and oppo find x6 pro. Hope to fix this bug.

v3.1.3 work well

A12 F2FS

no log cause cant boot :(

Sorry for bad english.
So I deleted the xiaomi FindDevice.apk in system/priv-app. I had to delete the apk because disabling or uninstalling bootloops the device.
But if I disable the module and restart the deivce the app somehow is back in "system/priv-app/FindDevice".
If I keep the module enable the app reamins deleted, even on restart.

Hello just found your work, and nicely done it works like a charm.
I saw you pushed a version where you can dynamically add partitions, using partition.hpp as a list.
I wanted to try adding the /sys/class/qcom-battery folder and compiling it.
But you recently changed the way. Is there any possibility to manually do it now or could you add it eventually to the list ?

When i flashing module, i cant use internet how to fix?

I installed the module from the latest ZIP file here (v2.3), and now my LineageOS (with microG services) is in an infinite wait at the start-up animation. I'm using the latest official version of Magisk. Any idea on how to fix this?

This module is tested on OnePlus 6T Android 10 version, it will cause boot delay and baseband stop working, which is a very troublesome problem.

Hey brother.
I want to make chages made by module(deleting something) permanent even after disabling module. How would I do that?

2 of my bank apps start to complain root after update OverlayFS 2.12

once back to 2.11 they chill again

overlayfs.log

No sound at all after loading overlayfs.
Device Xperia 1 V DQ-72
Evolution X 7.9.8
Kernel Hellscape 5.15.41
KernelSU 0.6.8

Logcat attached only has "audio" search term, can get a full logcat if needed.

Log_2023-9-22_04-52-24.txt

overlayfs.log

Im running Android 13 (API 33) rooted with magisk in android emulator (NOT debug).
In magisk when I try to install the .zip of the release (2.3) i get the error:

Error in mirpay (nfc pay application on Russia) application if export DO_UNMOUNT_KSU=true

can not be installed on android11 MIUI13.

The README for this project includes the following:

Build
There is two way:
Fork this repo and run github actions

I know how to fork a repo, but would someone please provide more specific instructions for 'run github actions'.
Thank you.

When using this module under kernelksu, the system camera app will flash back. One plus 11 coloros13
overlayfs.log :
https://drive.google.com/file/d/1Bsc-xKT5Js7NIVmldfigbdGEwN0laQzq/view?usp=sharing

KernelSU: v0.6.6
magic_overlayfs: v3.2.1
Redmi Note 12 4g with Android 13(MIUI 14)

After installing the module and restarting, no sound is played. No music, no video, no alarm, notification sound, ringtone, etc.
...
It will be fixed as soon as the module is deactivated and restarted.
overlayfs.log

boot_log_with_overlayfs.zip
boot_log_without_overlayfs.zip

After Install, or any time the module is enabled, the Cameras, both front and rear, fail with a popup of "Camera Failed". I was not able to get alot of meaningful info via logcat, but i did see "cameraxservice" log something close to "Camera failed due to serious error!" and another entry talking about "Camera has run out of memory" which i found strange, ill attempt to find better logs for this issue.
Interestingly enough, the issue goes away when module is disabled and device reboot so unsure if this is security related or error
Any ideas on your end wth is going on?
No other Modules are installed aside from systemless hosts and SELinux set to permissive everything else is stock
Device does use F2FS for /system. (and others)

Otherwise module works as expected.

After installing your module, some apps (like Turkish Oldubil) begin to detect root, regardless of whether they are listed in "unmounted modules" in Magisk Delta.

line deleted

but cause random bootloop (when torch disable condition about to happened, i gusess)

          Delete this line in `service.sh`

https://github.com/HuskyDG/magisk_overlayfs/blob/4188be9718f79598a851dde34628e5a82eb891e1/magisk-module/service.sh#L1

Originally posted by @HuskyDG in #14 (comment)

Doesn't work on Android 14
set ext4 image failed,abort

environment:
magisk delta26.1
coloros14
android 14
oneplus11 and oppo find x6 pro
overlayfs latest

I am trying to run magic_overlayfs in a temp-root environment that utilizes magisk running in /dev/.magisk on a Samsung Galaxy Z Fold 3. After running from root terminal: /data/local/tmp/overlayfs_system /data/overlayfs, I get no functioning overlay and the following /cache/overlayfs.log:

07-28 03:07:13.944  8286  8286 I : * Mount OverlayFS started
07-28 03:07:13.946  8286  8286 I : Switched to init mount namespace
07-28 03:07:13.950  8286  8286 D : mountinfo: device (253:4)/system/carrier/VZW on /system/carrier type ext4 (ro,seclabel,i_version)
07-28 03:07:13.951  8286  8286 D : mountinfo: device (259:1) on /vendor/dsp type ext4 (ro,seclabel,i_version)
07-28 03:07:13.951  8286  8286 D : mountinfo: device (259:2) on /vendor/firmware-modem type vfat (ro,context=u:object_r:firmware_file:s0,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
07-28 03:07:13.952  8286  8286 D : mountinfo: device (259:7) on /vendor/firmware_mnt type vfat (ro,context=u:object_r:firmware_file:s0,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
07-28 03:07:13.952  8286  8286 D : mountinfo: device (253:9) on /optics type ext4 (ro,seclabel,i_version)
07-28 03:07:13.952  8286  8286 D : mountinfo: device (253:8) on /prism type ext4 (ro,seclabel,i_version)
07-28 03:07:13.952  8286  8286 D : mountinfo: device (253:7) on /odm type ext4 (ro,seclabel,i_version)
07-28 03:07:13.952  8286  8286 D : mountinfo: device (253:6) on /product type ext4 (ro,seclabel,i_version)
07-28 03:07:13.952  8286  8286 D : mountinfo: device (253:5) on /vendor type ext4 (ro,seclabel,i_version)
07-28 03:07:13.953  8286  8286 D : getenv: [OVERLAY_MODE]=[2]
07-28 03:07:13.953  8286  8286 D : getenv: [OVERLAY_LEGACY_MOUNT]=[false]
07-28 03:07:13.953  8286  8286 D : getenv: [OVERLAYLIST]=[/dev/.magisk/.magisk/modules/module_a:/dev/.magisk/.magisk/modules/module_b]
07-28 03:07:13.953  8286  8286 D : getenv: [MAGISKTMP]=[/dev/.magisk]
07-28 03:07:13.953  8286  8286 D : Kernel version: 5.4
07-28 03:07:13.953  8286  8286 D : Magisk mirrors path is /dev/.magisk/.magisk/mirror
07-28 03:07:13.956  8286  8286 D : mount: /dev/.worker_pvqylujhqjrcrykjbnhq <- tmpfs (tmpfs) [rw]
07-28 03:07:13.956  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/master failed with 2: No such file or directory
07-28 03:07:13.956  8286  8286 I : ** Prepare mounts
07-28 03:07:13.957  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/system failed with 22: Invalid argument
07-28 03:07:13.957  8286  8286 W : Unable to add [/system], ignore!
07-28 03:07:13.957  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/vendor failed with 22: Invalid argument
07-28 03:07:13.958  8286  8286 W : Unable to add [/vendor], ignore!
07-28 03:07:13.958  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/product failed with 22: Invalid argument
07-28 03:07:13.958  8286  8286 W : Unable to add [/product], ignore!
07-28 03:07:13.959  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/odm failed with 22: Invalid argument
07-28 03:07:13.959  8286  8286 W : Unable to add [/odm], ignore!
07-28 03:07:13.959  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/vendor_dlkm failed with 22: Invalid argument
07-28 03:07:13.959  8286  8286 W : Unable to add [/vendor_dlkm], ignore!
07-28 03:07:13.960  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/odm_dlkm failed with 22: Invalid argument
07-28 03:07:13.960  8286  8286 W : Unable to add [/odm_dlkm], ignore!
07-28 03:07:13.960  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/prism failed with 22: Invalid argument
07-28 03:07:13.960  8286  8286 W : Unable to add [/prism], ignore!
07-28 03:07:13.961  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/optics failed with 22: Invalid argument
07-28 03:07:13.961  8286  8286 W : Unable to add [/optics], ignore!
07-28 03:07:13.961  8286  8286 E : mount: overlay -> /dev/.worker_pvqylujhqjrcrykjbnhq/oem failed with 22: Invalid argument
07-28 03:07:13.961  8286  8286 W : Unable to add [/oem], ignore!
07-28 03:07:13.963  8286  8286 I : ** Loading overlayfs
07-28 03:07:13.963  8286  8286 I : ** Loading overlayfs mirrors
07-28 03:07:13.963  8286  8286 I : mount done!
07-28 03:07:13.963  8286  8286 I : clean up
07-28 03:07:13.963  8286  8286 D : umount: /dev/.worker_pvqylujhqjrcrykjbnhq

dmesg output:

[15940.494740] [0:overlayfs_syste: 9908]  overlayfs: failed to resolve '/dev/.magisk/.magisk/modules/module_a': -2
[15940.495698] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/system' not supported
[15940.496226] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/vendor' not supported
[15940.496793] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/product' not supported
[15940.497359] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/odm' not supported
[15940.497875] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/vendor_dlkm' not supported
[15940.498399] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/odm_dlkm' not supported
[15940.499065] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/prism' not supported
[15940.499606] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/optics' not supported
[15940.500127] [0:overlayfs_syste: 9908]  overlayfs: filesystem on '/data/overlayfs/upper/oem' not supported

overlayfs.log
This log is from 3.1.3
My kernel is 5.10.66
Kernelsu version 11041 kernel
Manager 11070

is this "! Setup failed" normal?

still can use overlay, but sometimes overlay failed to apply, after reboot it back again (edit v2.20 trick not working)

/ # mount -o rw,remount /system
/ # touch /system/test
/ # ls /system/test
/system/test
/ # touch /system/etc/test
touch: cannot touch '/system/etc/test': Directory not empty
/ # touch /system/etc/test1
touch: cannot touch '/system/etc/test1': Directory not empty
/ # touch /system/etc/test2
touch: cannot touch '/system/etc/test2': Directory not empty
/ # ls /system/etc/test
ls: cannot access '/system/etc/test': No such file or directory

/ # mount |grep system |grep overlay
overlay on /system/app type overlay (ro,relatime,seclabel,lowerdir=/mnt/vendor/mi_ext/system/app/:/product/pangu/system/app/:/system/app)
overlay on /system/priv-app type overlay (ro,relatime,seclabel,lowerdir=/mnt/vendor/mi_ext/system/priv-app/:/product/pangu/system/priv-app/:/system/priv-app)
overlay on /system/framework type overlay (ro,relatime,seclabel,lowerdir=/product/pangu/system/framework/:/system/framework)
overlay on /system/etc/sysconfig type overlay (ro,relatime,seclabel,lowerdir=/mnt/vendor/mi_ext/system/etc/sysconfig/:/system/etc/sysconfig)
overlay on /system/etc/permissions type overlay (ro,relatime,seclabel,lowerdir=/mnt/vendor/mi_ext/system/etc/permissions/:/product/pangu/system/etc/permissions/:/system/etc/permissions)
overlay on /system type overlay (rw,relatime,seclabel,lowerdir=/dev/mount_loop/9/system:/dev/mount_loop/7/system:/dev/mount_loop/5/system:/dev/mount_loop/2/system:/dev/mount_loop/13/system:/dev/mount_loop/1/system:/dev/mount_loop/0/system:/system,upperdir=/dev/mount_overlayfs/upper/system,workdir=/dev/mount_overlayfs/worker/65027/55)
overlay on /system/app type overlay (rw,relatime,seclabel,lowerdir=/dev/mount_loop/1/system/app:/system/app,upperdir=/dev/mount_overlayfs/upper/system/app,workdir=/dev/mount_overlayfs/worker/74/2)
overlay on /system/priv-app type overlay (rw,relatime,seclabel,lowerdir=/system/priv-app,upperdir=/dev/mount_overlayfs/upper/system/priv-app,workdir=/dev/mount_overlayfs/worker/79/2)
overlay on /system/framework type overlay (ro,relatime,seclabel,lowerdir=/system/framework,upperdir=/dev/mount_overlayfs/upper/system/framework,workdir=/dev/mount_overlayfs/worker/84/2)
overlay on /system/etc/sysconfig type overlay (ro,relatime,seclabel,lowerdir=/system/etc/sysconfig,upperdir=/dev/mount_overlayfs/upper/system/etc/sysconfig,workdir=/dev/mount_overlayfs/worker/88/2)
overlay on /system/etc/permissions type overlay (ro,relatime,seclabel,lowerdir=/system/etc/permissions,upperdir=/dev/mount_overlayfs/upper/system/etc/permissions,workdir=/dev/mount_overlayfs/worker/92/2)
overlay on /vendor/vm-system type overlay (ro,nosuid,nodev,relatime,seclabel,lowerdir=/vendor/vm-system,upperdir=/dev/mount_overlayfs/upper/vendor/vm-system,workdir=/dev/mount_overlayfs/worker/66331/2)
overlay on /system_ext type overlay (ro,relatime,seclabel,lowerdir=/dev/mount_loop/0/system_ext:/system_ext,upperdir=/dev/mount_overlayfs/upper/system_ext,workdir=/dev/mount_overlayfs/worker/65028/2)

kernelsu 0.6.7
magic_overlayfs: 3.2.1