Tutorial initrd-magisk - Magisk for Android x86 project

MrMiy4mo

Well-known member
After I installed initrd-mangisk, the mount partition got errors like this:
in terminal:
#su
#mount.ntfs /dev/block/sdc5 /mnt/sdc5
ntfs-3g-mount:mount failed:Device or resource busy


Everything worked fine before installation! my system is android x86_64 9.0 r2
It is probably already mounted, i guess you are trying to mount partition where your system is installed.
 

supertc

New member
VC
64
It is probably already mounted, i guess you are trying to mount partition where your system is installed.
There is a line of information in df -h as follows:
#df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 7.7G 4.4M 7.7G 1% /
tmpfs 7.7G 0 7.7G 0% /system/bin
/dev/z00IUN4Siy/.magisk/block/system 4.8G 3.1G 1.6G 67% /system/bin/adbd
tmpfs 7.7G 7.4M 7.7G 1% /system/bin/magisk
tmpfs 7.7G 0 7.7G 0% /system/xbin
tmpfs 7.7G 58M 7.7G 1% /gearlock
tmpfs 7.7G 332K 7.7G 1% /dev
/dev/z00IUN4Siy/.magisk/block/sda1 499M 30M 469M 7% /dev/z00IUN4Siy/.magisk/mirror/sda1
/dev/z00IUN4Siy/.magisk/block/sda2 100G 38G 62G 39% /dev/z00IUN4Siy/.magisk/mirror/sda2
/dev/z00IUN4Siy/.magisk/block/sda3 92G 7.9G 84G 9% /dev/z00IUN4Siy/.magisk/mirror/sda3
/dev/z00IUN4Siy/.magisk/block/sda4 30G 11G 19G 37% /dev/z00IUN4Siy/.magisk/mirror/sda4
/dev/z00IUN4Siy/.magisk/block/sdb1 499M 37M 462M 8% /dev/z00IUN4Siy/.magisk/mirror/sdb1
/dev/z00IUN4Siy/.magisk/block/sdb2 40G 15G 25G 37% /dev/z00IUN4Siy/.magisk/mirror/sdb2
/dev/z00IUN4Siy/.magisk/block/sdc1 499M 5.2M 494M 2% /dev/z00IUN4Siy/.magisk/mirror/sdc1
/dev/z00IUN4Siy/.magisk/block/sdc2 41G 10G 31G 25% /dev/z00IUN4Siy/.magisk/mirror/sdc2
/dev/z00IUN4Siy/.magisk/block/sdc4 140G 105G 35G 76% /dev/z00IUN4Siy/.magisk/mirror/sdc4
/dev/z00IUN4Siy/.magisk/block/sdc5 120G 86G 34G 72% /dev/z00IUN4Siy/.magisk/mirror/sdc5
/dev/z00IUN4Siy/.magisk/block/sdc6 120G 107G 13G 90% /dev/z00IUN4Siy/.magisk/mirror/sdc6
/dev/z00IUN4Siy/.magisk/block/sdc7 35G 88M 35G 1% /dev/z00IUN4Siy/.magisk/mirror/sdc7
tmpfs 7.7G 0 7.7G 0% /mnt
/data/media 40G 15G 25G 37% /mnt/runtime/default/emulated
none 7.7G 4.0K 7.7G 1% /cache

sdb2 The partition is android x86 9.0 r2 partition
sda and sdc The partition is a WINDOWS NTFS partition

#mount.ntfs /dev/block/sdc5 /mnt/sdc5
ntfs-3g-mount:mount failed : Device or resource busy

Before installing magisk, i can mount the hard disk with gearlock, and the mount.ntfs command also works!
 
Last edited:

MrMiy4mo

Well-known member
@supertc
See the line;
Code:
/dev/{Random.String}/.magisk/block/sdc5 120G 86G 34G 72% /dev/{Random.String}/.magisk/mirror/sdc5

It is the directory where magisk daemon mounts partitions to allow magisk modules to work systemlessly

There is no guarranty that these will work but give them a try;
1. Unmount and remount sdc5
Code:
umount /dev/block/sdc5

2. Bind mount from magisk mount directory to your destination directory
Code:
mount -o bind /dev/{Random.String}/.magisk/mirror/sdc5 /mnt/{Dest.Directory}
 

supertc

New member
VC
64
@supertc
See the line;
Code:
/dev/{Random.String}/.magisk/block/sdc5 120G 86G 34G 72% /dev/{Random.String}/.magisk/mirror/sdc5

It is the directory where magisk daemon mounts partitions to allow magisk modules to work systemlessly

There is no guarranty that these will work but give them a try;
1. Unmount and remount sdc5
Code:
umount /dev/block/sdc5

2. Bind mount from magisk mount directory to your destination directory
Code:
mount -o bind /dev/{Random.String}/.magisk/mirror/sdc5 /mnt/{Dest.Directory}
thank you very much!

The value of ramdom.string is different every time Android boots

The SDC5 partition has been loaded in the terminal, and the content of /mnt/sdc5 can be displayed in the terminal. I don’t know why there is no content in /mnt/sdc5 in the ES file manager.
 

MrMiy4mo

Well-known member
thank you very much!

The value of ramdom.string is different every time Android boots

The SDC5 partition has been loaded in the terminal, and the content of /mnt/sdc5 can be displayed in the terminal. I don’t know why there is no content in /mnt/sdc5 in the ES file manager.
Because of the way android isolates each app, you will not able to access to a directory if it is mounted by another process(app)

You must create a script and execute in ES file manager
(if supports, otherwise use another file manager)
 

Xtr

Well-known member
Because of the way android isolates each app, you will not able to access to a directory if it is mounted by another process(app)

You must create a script and execute in ES file manager
(if supports, otherwise use another file manager)
It happens only in Android 11 x86 or newer currently
Might be related to mount namespaces too
 

supertc

New member
VC
64
Because of the way android isolates each app, you will not able to access to a directory if it is mounted by another process(app)

You must create a script and execute in ES file manager
(if supports, otherwise use another file manager)
Can you make such a script? It can automatically read ramdom.string at each boot, and then automatically mount the partition。ramdom.String is only available after installing magisk。

Is the script placed in the post fs data.d or service.d directory?
 

grizz

New member
VC
56
Por favor haz un video hermano
Otra forma fácil y conveniente de integrar Magisk, agregue soporte boot.img para Magisk en el proyecto Android-x86 (BlissOS, PrimeOS, ...).

68747470733a2f2f692e696d6775722e636f6d2f314262537254702e6a7067


Descargue initrd-magisk y boot-magisk desde la página de lanzamiento

Consulte la página Wiki para ver cómo instalarlo.
[combinación automática]1653069061[/combinación automática]
Si desea que los módulos de magisk funcionen correctamente, no use rusty-magisk
Hermano, Bro, I did all the procedures and nothing
 

Attachments

  • IMG_20230405_145432.jpg
    IMG_20230405_145432.jpg
    533.8 KB · Views: 98
  • IMG_20230405_145405.jpg
    IMG_20230405_145405.jpg
    302 KB · Views: 102

grizz

New member
VC
56
you have to extract magiskpatchedxxxx.img and place to primeos partition
Hi, excuse me, where is magisk patched? download one called boot magisk and innitrd
Post automatically merged:

Otra forma fácil y conveniente de integrar Magisk, agregue soporte boot.img para Magisk en el proyecto Android-x86 (BlissOS, PrimeOS, ...).

68747470733a2f2f692e696d6775722e636f6d2f314262537254702e6a7067


Descargue initrd-magisk y boot-magisk desde la página de lanzamiento

Consulte la página Wiki para ver cómo instalarlo.
[combinación automática]1653069061[/combinación automática]
Si desea que los módulos de magisk funcionen correctamente, no use rusty-magisk
B.Bro, don't you have any video tutorial? I did everything that the letter says, the system starts with the innitrd magisk but when I go to the app it does not record the data entered
 
Last edited:

YHR

Active member
Hi, excuse me, where is magisk patched? download one called boot magisk and innitrd
Post automatically merged:


B.Bro, don't you have any video tutorial? I did everything that the letter says, the system starts with the innitrd magisk but when I go to the app it does not record the data entered
inside /storage/emulated/0/Download/
 

Get Connected

Discord Server
Top