Temp Root about magic_overlayfs HOT 3 CLOSED

1. Overlayfs must be mounted before zygote start so system modifications can have effect, overwise it is meanless. Unless you restart zygote again after mounting.
2. /data f2fs is not allowed to be used directly on some Kernel

Please try:

dd if=/dev/zero of=/data/adb/overlay bs=1024 count=100
mkfs.ext4 /data/adb/overlay
e2fsck -pf /data/adb/overlay
resize2fs /data/adb/overlay 2000M
mkdir /mnt/overlayfs
mount -o rw -t ext4 /data/adb/overlay /mnt/overlayfs
/data/local/tmp/overlayfs_system /mnt/overlayfs
stop; start

from magic_overlayfs.

mount -o rw -t ext4 /data/adb/overlay /mnt/overlayfs

@HuskyDG , thank you for your assistance

yes, restarting zygote was the plan, although I am sure that will come with more issues to be solved, I will have to take it one step at a time.

running your commands, the mount -o rw -t ext4 /data/adb/overlay /mnt/overlayfs results in:

mount: can't setup loop device: No such file or directory

EDIT: I apologize , it was a busybox mount issue, let me continue now that i used the proper mount binary

The test mount command runs fine, but running overlayfs_system mounting to /mnt/overlayfs results in the device locking up and rebooting

I tried

setprop ctl.stop media
setprop ctl.stop zygote

before running the command, but that did not result in any difference. The system freezes before there is any meaningful output in dmesg or logcat

from magic_overlayfs.

is there a reason why this is closed? whether it is believed to be useful or not after android boot i dont believe should be the reason. if it just not possible under this environment, that would be a good reason, but im not sure we've proven that

from magic_overlayfs.