Android-x86 64 and magisk

[Jose Luis s]

Hi all.

I know this is more related to Magisk than A-x86 (probably) but maybe someone faced the same issues here.

I installed Magisk 20.3 in 9.0 rc2 x86-64 Magisk self reported as installed and updated. Seems ok till this point, but tried to install riru Core to install edxposed (and other modules) but although the installation finishes ok the module does not load at all (any of them).

Does anybody faced same issues?

Thanks

[Jose Luis s]

No one?

[Huy Minh Bui]

I remembered that youling257 used to fix the problem. I wonder that if that fix still work.........

Hope that he can figure this out again.

[youling 257]

first, you need know /sbin/.magisk/mirror/system, /sbin/.magisk/mirror/data , /sbin/.magisk/modules

then, you need know /data/adb/modules/$MODID/system

[Jose Luis s]

Hi Youling.

/sbin/.magisk/mirror  exist in my installation

It contains 2 dirs cache and persist, but system data are not present

also /sbin/.magisk/modules does not exist

/data/adb/modules/$MODID/  are present (modules I've tried to install) some of them does not have any system subdir inside and riru-core has a system_x86 inside.

It's weird because Magisk self reported as installed and updated.

What can I do to fix this? must I create the dirs not present?

Thanks

[Jose Luis s]

Hello.

I've found info about how to make Magisk work in BlissOS Provided by Youling.

Is it possible to apply same solution to Android-X86?

[youling 257]

you have to use system.img and data.img, symlink /dev/loop* to /dev/block/loop*, then will mount /dev/block/loop0 on /sbin/.magisk/mirror/system, mount /dev/block/loop1 on /sbin/.magisk/mirror/data

edit /system/etc/init.sh

function init_misc()

{

 # device information

 setprop ro.product.manufacturer "$(cat $DMIPATH/sys_vendor)"

 setprop ro.product.model "$PRODUCT"

 ln -s /dev/block/loop* /dev

[youling 257]

a magisk module file list should be these

├── riru-core

│   ├── module.prop

│   ├── post-fs-data.sh

│   └── system

│       ├── lib

│       │   ├── libmemtrack_real.so

│       │   └── libmemtrack.so

│       └── lib64

│           ├── libmemtrack_real.so

│           └── libmemtrack.so

└── riru_edxposed

    ├── module.prop

    ├── post-fs-data.sh

    ├── service.sh

    ├── system

    │   ├── framework

    │   │   ├── edconfig.jar

    │   │   ├── eddalvikdx.jar

    │   │   ├── eddexmaker.jar

    │   │   └── edxp.jar

    │   ├── lib

    │   │   ├── libriru_edxp.so

    │   │   └── libwhale.edxp.so

    │   └── lib64

    │       ├── libriru_edxp.so

    │       └── libwhale.edxp.so

    ├── system.prop

    └── util_functions.sh

[youling 257]

magisk put lib* to system/lib by use mount bind bad way.

/dev/mmcblk1p3 on /android/system/lib/libmemtrack.so type ext4 (rw,seclabel,noatime)

/dev/mmcblk1p3 on /android/system/lib/libmemtrack_real.so type ext4 (rw,seclabel,noatime)

/dev/mmcblk1p3 on /android/system/lib/libriru_edxp.so type ext4 (rw,seclabel,noatime)

/dev/mmcblk1p3 on /android/system/lib/libwhale.edxp.so type ext4 (rw,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libstagefright_bufferqueue_helper.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libgraphicsenv.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libandroidfw.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libbinder.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/android.hard...@1.0.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/android.sys...@1.0.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libkeymaster4support.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libstagefright_enc_common.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libbootanimation.so type ext4 (ro,seclabel,noatime)

......

......

......

/sbin/.magisk/block/system on /android/system/lib/libadbconnection.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libRSDriver.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libprotoutil.so type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/lib/libsync.so type ext4 (ro,seclabel,noatime)

tmpfs on /android/system/framework type tmpfs (rw,seclabel,relatime)

/dev/mmcblk1p3 on /android/system/framework/services.jar type ext4 (rw,seclabel,noatime)

/dev/mmcblk1p3 on /android/system/framework/edconfig.jar type ext4 (rw,seclabel,noatime)

/dev/mmcblk1p3 on /android/system/framework/eddalvikdx.jar type ext4 (rw,seclabel,noatime)

/dev/mmcblk1p3 on /android/system/framework/eddexmaker.jar type ext4 (rw,seclabel,noatime)

/dev/mmcblk1p3 on /android/system/framework/edxp.jar type ext4 (rw,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/framework/ims-common.jar type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/framework/com.android.future.usb.accessory.jar type ext4 (ro,seclabel,noatime)

/sbin/.magisk/block/system on /android/system/framework/core-oj.jar type ext4 (ro,seclabel,noatime)

a easy way is use mount overlay, upperdir file list is libmemtrack and other files.

mount -t overlay overlay -o ro,'context="u:object_r:system_file:s0"',noatime,lowerdir=/system/lib,upperdir=/data/adb/upper/lib,workdir=/data/adb/work /system/lib

overlay on /android/system/lib type overlay (ro,context=u:object_r:system_file:s0,noatime,lowerdir=/system/lib,upperdir=/data/adb/upper/lib,workdir=/data/adb/work)

[Jose Luis s]

Thanks Youling

Seems to be different guide for Bliss.

So Android-x86 use by default if installed over ext4, system.img and Data dir (not data.img) so must I modify the Data dir to data.img?

And what about the rest of the guide in Bliss forum? I use the patching method from magisk.apk but I do not decomres any file from magisk.zip.......

Honestly I have a great mess with the process........

[youling 257]

you can use other one ext4 partition as Android data, command line DATA=/dev/block/XXX, magisk can mount /dev/block/XXX on /sbin/.magisk/mirror/data no problem.

在 2020年2月26日星期三 UTC+8上午12:12:39，Jose Luis s写道：

[Jose Luis s]

Great.

So I I use a separate partition for data it will work. And what if I use a separate partition for System and Data (leaving kernel and stages files in the installed one) will it work? What kernel parameter must I use to use the system partition?

Thanks for your help.

[youling 257]

http://git.osdn.net/view?p=android-x86/bootable-newinstaller.git;a=blob;f=initrd/init;h=af139aa61c6e7073efccf3f3521da36e360a12f3;hb=HEAD#l119

  119         elif [ -z "$SRC" -a -e /mnt/build.prop ]; then

120                 mount --bind /mnt system

if kernel initrd.img ramdisk.img installed on /dev/block/sda5, copy system files to this sda5 root directory, sda5 root directory has app priv-app bin lib build.prop...files,

will mount /dev/block/sda5 on /sbin/.magisk/mirror/system, copy system files must keep selinux context.

initrd.img kernel ramdisk.img system files must on the same partition, ROOT=/dev/block/sda3 DATA=/dev/block/sda4

not support SYSTEM=/dev/block/xxx command line.

在 2020年2月27日星期四 UTC+8上午4:34:54，Jose Luis s写道：