[Magisk] manos78:
Hi [MENTION=4470081]topjohnwu[/MENTION] (and others),

Regarding my MotoG5+ and the new v14.0, the same problem continues (mount of "/magisk" fails).This is the log of the Beta 1400:

--------- beginning of main
D( 460: 460) client: connect fail, try launching new daemon process
D( 471: 472) sepol: Starting large patch thread
I( 471: 471) Magisk v14.0(1400) daemon started
I( 471: 473) ** post-fs mode running
--------- beginning of system
I( 471: 512) ** post-fs-data mode running
I( 471: 512) * Mounting mirrors
I( 471: 512) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system
I( 471: 512) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
D( 471: 512) bind_mount: /data/magisk -> /dev/magisk/mirror/bin
D( 471: 512) magisk_img: e2fsck 1.42.9 (28-Dec-2013)
D( 471: 512) magisk_img: Pass 1: Checking inodes, blocks, and sizes
D( 471: 512) magisk_img: Pass 2: Checking directory structure
D( 471: 512) magisk_img: Pass 3: Checking directory connectivity
D( 471: 512) magisk_img: Pass 4: Checking reference counts
D( 471: 512) magisk_img: Pass 5: Checking group summary information
D( 471: 512) magisk_img: /data/magisk_merge.img: 11/4096 files (0.0% non-contiguous), 1294/16384 blocks
E( 471: 512) mount /dev/block/loop1->/dev/source failed with 13: Permission denied
D( 471: 472) sepol: Large patch done
I( 471: 770) ** late_start service mode running
I( 471: 770) * Running service.d scripts
I( 471: 770) * Running module service scripts
D( 471: 3926) su: request from client: 6
D( 471: 3926) su: request from uid=[10130] (#1)
D( 471: 3927) su: collector started
D( 471: 3926) su: waiting child: [3928]
D( 3928: 3928) su: child process started
D( 3928: 3928) su: argc=[2]
D( 3928: 3928) su: argv[0]=[su]
D( 3928: 3928) su: argv[1]=[--mount-master]
D( 3928: 3928) su: cwd=[/]
D( 3928: 3928) su: pts_slave=[]
D( 3928: 3928) su: use global namespace
D( 471: 3934) su: request from client: 7
D( 471: 3934) su: request from uid=[0] (#1)
D( 471: 3934) su: waiting child: [3935]
D( 3935: 3935) su: child process started
D( 3935: 3935) su: argc=[2]
D( 3935: 3935) su: argv[0]=[su]
D( 3935: 3935) su: argv[1]=[-v]
D( 3935: 3935) su: cwd=[/]
D( 3935: 3935) su: pts_slave=[]
D( 471: 3934) su: return code: [0]
D( 471: 4835) su: request from client: 8
D( 471: 4835) su: request from uid=[2000] (#1)
D( 471: 4835) su_db: query policy=[2]
D( 471: 4835) su: waiting child: [4836]
D( 4836: 4836) su: child process started
D( 4836: 4836) su: argc=[1]
D( 4836: 4836) su: argv[0]=[su]
D( 4836: 4836) su: cwd=[/]
D( 4836: 4836) su: pts_slave=[/dev/pts/1]
D( 4836: 4836) su: stdin using PTY
D( 4836: 4836) su: stdout using PTY
D( 4836: 4836) su: stderr using PTY
D( 4836: 4836) su: use namespace of pid=[4833]

However, I do some tests by hand when the device is running (the regular MagiskRoot works, the problem is that modules doesn't install):

In the Shell, after call to su, I execute: "mount /data/magisk.img /magisk" and it fails with "mount: losetup failed 1"

Then in the Shell I try "losetup -f" and it responds with "losetup: /dev/loop3: No such file or directory"

However, the path seems to be incorrect (not "/dev/loop3", but "/dev/block/loop3" exists). So I execute "mount /dev/block/loop3 /magisk" and it works!

With "mount" I see "/dev/block/loop3 on /magisk type ext4 (rw,seclabel,relatime,data=ordered)"

So, I feel the problem can be a simple incorrect path ("/dev/block/*" instead of "/dev/*"). I know that Magisk is using the correct path as the log shows "/dev/block/loop1". But, perhaps the problem is with the losetup call... Can be that you need to call to the tool with the full path?

If you need I can do more tests.

Thank you!