movievova.blogg.se - Phoenix os virtualbox install

#Phoenix os virtualbox install install
#Phoenix os virtualbox install Pc
#Phoenix os virtualbox install zip

I don't guarantee this solution will work on your Android x86 distribution but this is the only solution I found after weeks of nightmare!Į : mount /sbin/.magisk/block/system->/sbin/. Step 1: Install VM VirtualBox on your Computer/Laptop Step 2: Create Virtual Machine using VirtualBox Step 3: Run Remix OS using ISO file Download link. You can start module just by typing props from Terminal Emulator or find it in /data/adb/modules/MagiskHidePropsConf/system/(x)bin folder. But after second reboot somehow I repeated the operation and now module (for example: MagiskHide Props Config) worked well!

#Phoenix os virtualbox install zip

Notice: first time I installed ZIP module through CLI, I didn't see any output and module was not installed. Then, install module ZIP by typing # magisk -install-module /path/to/your-module.zip.while opening Magisk app after reboot you will see this error:īut don't worry! You can always use Command Line Interface instead of GUI, just open Terminal Emulator or adb shell and type su and then check that magisk was successfully installed by typing # magisk -c Those who would like a single Linux-based operating system to run on all of their devices will find that Android-x86 is a solid alternative. If you have previously Magisk version installed, then after installation Magisk Canary with steps described in 4.Git clone shakalaca scripts and follow steps described in (don't forget to rename app-debug.apk to magisk.zip).Download latest canary Magisk build from (app-debug.apk).

#Phoenix os virtualbox install Pc

Established ADB connection with PC via adb connect Android-x86 IP address.

Enabled ADB debugging through developer options (5 tap click on build number in Android Settings).

Installed a system from ISO with /system read-write

Assuming I use Android x86_64 (AOSP) 8.1.0 on top of VirtualBox.

Whoa! I installed last canary version of Magisk and somehow modules worked! Tested on MagiskHide Props Config module. Either modifying Magisk init script or Android x86 init ramdisk? But somehow we need to find a way to solve this issue. I don't think topjohnwu is going to solve our issue because he thinks this is a Android x86 architecture issue, not Magisk itself. I think we should somehow avoid /dev/loop0 (system.sfs image) and /dev/block/sda1 from mounting as Magisk mirrors in order to allow Magisk to mount mirrors from /sbin/.magisk/block/. So, the devices are becoming busy after Android has booted so Magisk cannot remount them. Output cat /proc/mounts shows me the following output: it seems I found the reason of this problem (assuming I use Android x86 8.1.0 VirtualBox): You can also install HDP on other virtualization platforms such as kvm or VMware. Tried installing Android x86 with both /system read-write and read-only.Īll versions of Magisk started from 20.4 to 22.0 have these Errors in log:Īnd moreover. Here we use Oracle's open source VirtualBox. I don't know about PhoenixOS, but I use Android x86_64 8.1.0 on top of VirtualBox and I can confirm that Error 16: Device or resource busy is present here.