AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Phoenix os virtualbox install9/28/2023 ![]() ![]() 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/. Click Finish to close the installer and open. Accept the default install options which include network interfaces and USB. You can start module just by typing props from Terminal Emulator or find it in /data/adb/modules/MagiskHidePropsConf/system/(x)bin folder. The Openbox Linux window manager is light on system resources, easy to configure, and a pleasure to use. Download and install Virtualbox to your Windows machine. But after second reboot somehow I repeated the operation and now module (for example: MagiskHide Props Config) worked well! 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 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).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. The main thing I want to achieve is 3d acceleration, so I be able to run games or apps with 3d content. I don't think topjohnwu is going to solve our issue because he thinks this is a Android x86 architecture issue, not Magisk itself. Hi everyone I'm constantly searching for working way to install virtualbox guest addition to PhoenixOS as guest os. 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): 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. 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. ![]()
0 Comments
Read More
Leave a Reply. |