Magisk: Intalling Magisk to an Android emulator is being solved?

Created on 28 Mar 2019 · 8Comments · Source: topjohnwu/Magisk

I saw a post https://github.com/topjohnwu/Magisk/issues/732
@topjohnwu says
“I run Magisk in emulators. Might release documentations on how to do it soon.” on 26.Feb,
But I didn't find how to install Magisk to emulator on documentations..
I love magisk and can't wait play fgo and pokemon go on My PC..

Source

MAYBreath

All 8 comments

The basic idea is to find a way to replace init to magiskinit. There will not be a general guide for that since emulators does not have a clear standard.

topjohnwu on 23 Apr 2019

I have successfully installed Magisk 20.1 on an Android Q Google Play x86_64 AVD (the emulator provided by Android Studio).

Update: it had some problems: #2112

I found no boot.img on this kind of AVD. I found ramdisk.img in [Android SDK Path]/system-images/android-29/google_apis_playstore/x86_64, which is in cpio.gz format.

I followed the hints of boot_patch.sh to patch this ramdisk.img file. (I didn't execute this file directly.) It turned out to be working.

I then abootimg-unpack-initrded the patched file out of curiosity (a fakeroot environment would be nice to do this job). I found that /init was replaced by magiskinit64, meanwhile, the original /init (together with /fstab.ranchu was moved into /.backup/. A config file (which described KEEPVERITY, KEEPFORCEENCRYPT etc) was also placed into /.backup with a new filename of .magisk.

andronoob on 29 Nov 2019

👍1

I didn't patch the kernel, since it's not ARM at all, while the original patch pattern seemed to be ARM.

I then tried to install magisk on an Android 8.0 x86 AVD, which was unfortunately failed. The system didn't start at all, almost no I/O activity was observed.

Also, there was something wrong around "KEEPFORCEENCRYPT=false".

/fstab.ranchu of this Android 8.0 x86 AVD contains the following line:

/dev/block/vdc                                          /data               ext4      noatime,nosuid,nodev,nomblk_io_submit,errors=panic   wait,check,quota,forceencrypt=/dev/block/vdd

which was (erroneously) modified into this, by magiskboot:

/dev/block/vdc                                          /data               ext4      noatime,nosuid,nodev,nomblk_io_submit,errors=panic   wait,check,quota,=/dev/block/vdd

andronoob on 29 Nov 2019

Android 7.0 x86 AVD seemed to be working fine with Magisk. The official Magisk module of Xposed worked fine with it, too.

andronoob on 1 Dec 2019

👍1

Hi @andronoob ,
Could you share the patched ramdisk.img you created? I would really like to have root in my virtual device, but how to do this goes over my head.

WilkoPebesma on 8 May 2020

@JudgeDread11 Sorry, but I didn't keep that file. I had deleted such patched ramdisk.img. You may follow these steps:
https://github.com/topjohnwu/Magisk/issues/2112#issuecomment-565340950

andronoob on 8 May 2020

I have successfully installed Magisk 20.1 on an Android Q Google Play x86_64 AVD (the emulator provided by Android Studio).

Update: it had some problems: #2112

I found no boot.img on this kind of AVD. I found ramdisk.img in [Android SDK Path]/system-images/android-29/google_apis_playstore/x86_64, which is in cpio.gz format.

I followed the hints of boot_patch.sh to patch this ramdisk.img file. (I didn't execute this file directly.) It turned out to be working.

I then abootimg-unpack-initrded the patched file out of curiosity (a fakeroot environment would be nice to do this job). I found that /init was replaced by magiskinit64, meanwhile, the original /init (together with /fstab.ranchu was moved into /.backup/. A config file (which described KEEPVERITY, KEEPFORCEENCRYPT etc) was also placed into /.backup with a new filename of .magisk.