[GUIDE]Magisk, SuperSU and Xposed for MEmu 7.3.2 or LDPlayer 4.0.45

[evildog1]

If you use Magisk, you should install it as Magisk module

tried it, gets stuck on boot. i'm using latest Magisk canary from you

 

[huskydg]

tried it, gets stuck on boot. i'm using latest Magisk canary from you

try this

https://github.com/HuskyDG/magisk-xposed/releases/download/latest/xposed-sdk25.zip

 

[evildog1]

try this

https://github.com/HuskyDG/magisk-xposed/releases/download/latest/xposed-sdk25.zip

Still stuck. I had bootloop enabled so it disables once I reboot again

 

[kyleofbennett]

Hello.

I was able to edit, add, and remove apps directly on BlueStacks disks, even before installation.

At end, I got an updated Play Store, Google Services Framework and Play Games. I removed the default launcher and added Nova Launcher. Also, removed the pre-installed apps, like the built-in games.

Maybe this is a more effective way to install Magisk, and/or updated Google apps like GApps. My aim is to have a certified device on Play Store.

If anyone is interested, I'll show how I did.

Hey mate, I'd love to see how you did this as I'm trying to achieve the same thing at the moment!

Many thanks in advance

 

[romulocarlos]

Hey mate, I'd love to see how you did this as I'm trying to achieve the same thing at the moment!

Many thanks in advance

Hello!

I abandoned this "project", as I was unable to get a certified device, but isn't a complicated process. You will need a computer or a virtual machine with a Linux distro (like Ubuntu) to preserve the files attributes (Windows can't handle Linux attributes). I've used a Ubuntu distro on VirtualBox, as VirtualBox can work well with the needed files, so I'll show you with this way.

So, at first, do a backup for your c:\programdata\Bluestacks_nxt folder and close any instance!

Now you'll need to convert the BlueStacks's virtual disks to VDI format. Use these commands:

vboxmanage clonehd "path_to_original_data.vhdx" "path_to_converted_original_data.vdi" --format vdi

and

vboxmanage clonehd "path_to_original_root.vhd" "path_to_converted_root.vdi" --format vdi

Once converted, VirtualBox will list these virtual disks on Tools tab. Go there, select the VDI files you just converted, and copy the UUID for each disk. You'll need to edit a file with same name as your's BlueStacks instances (I use only one, named Pie64, so my file is Pie64.bstk). It is located at Bluestacks_nxt folder, at subfolder "Engine". This file is like a XML file, so, I recommend you to use Notepad++ instead default Windows notepad.

There are some lines to edit. Look at lines starting with "HardDisk uuid" at top of the file. You do not need to edit the line with "fastboot.vdi", but edit the others to match the UUIDs and the converted VDIs filenames.

At bottom of the file, look for lines starting with "StorageControler". Inside these groups, change the UUID to match the converted VDIs, again. Close the file and start BlueStacks. If you did all correctly, everything will work as expected. Update/install any app you want, and close the instance.

Fire up your VirtualBox, attach the VDIs to the Ubuntu virtual machine as secondary disks, and start it. Inside the machine, open the root.vdi, and do the "mods" you want, like delete default apps. You can also open original_data.vdi, and delete the BlueStacks default app updates, and move the apps you installed/updated to root.vdi. I don't remember exactly where the apps folders are located, but isn't hard to find.

Once you finish, unmount the VDIs inside the virtual machine, and close it. Dettach the VDIs from the virtual machine, and start BlueStacks.

You're done! Good luck!

 

[kyleofbennett]

Hello!

I abandoned this "project", as I was unable to get a certified device, but isn't a complicated process. You will need a computer or a virtual machine with a Linux distro (like Ubuntu) to preserve the files attributes (Windows can't handle Linux attributes). I've used a Ubuntu distro on VirtualBox, as VirtualBox can work well with the needed files, so I'll show you with this way.

So, at first, do a backup for your c:\programdata\Bluestacks_nxt folder and close any instance!

Now you'll need to convert the BlueStacks's virtual disks to VDI format. Use these commands:

vboxmanage clonehd "path_to_original_data.vhdx" "path_to_converted_original_data.vdi" --format vdi

and

vboxmanage clonehd "path_to_original_root.vhd" "path_to_converted_root.vdi" --format vdi

Once converted, VirtualBox will list these virtual disks on Tools tab. Go there, select the VDI files you just converted, and copy the UUID for each disk. You'll need to edit a file with same name as your's BlueStacks instances (I use only one, named Pie64, so my file is Pie64.bstk). It is located at Bluestacks_nxt folder, at subfolder "Engine". This file is like a XML file, so, I recommend you to use Notepad++ instead default Windows notepad.

There are some lines to edit. Look at lines starting with "HardDisk uuid" at top of the file. You do not need to edit the line with "fastboot.vdi", but edit the others to match the UUIDs and the converted VDIs filenames.

At bottom of the file, look for lines starting with "StorageControler". Inside these groups, change the UUID to match the converted VDIs, again. Close the file and start BlueStacks. If you did all correctly, everything will work as expected. Update/install any app you want, and close the instance.

Fire up your VirtualBox, attach the VDIs to the Ubuntu virtual machine as secondary disks, and start it. Inside the machine, open the root.vdi, and do the "mods" you want, like delete default apps. You can also open original_data.vdi, and delete the BlueStacks default app updates, and move the apps you installed/updated to root.vdi. I don't remember exactly where the apps folders are located, but isn't hard to find.

Once you finish, unmount the VDIs inside the virtual machine, and close it. Dettach the VDIs from the virtual machine, and start BlueStacks.

You're done! Good luck!

Thank you so much for putting this guide together buddy! I'll give it a go and update this thread with the result in case anyone might be interested.

 

[rafaz182]

The script prints nothing for me. I'm using MEMu player

 

[aikostes]

please give me instructions on how to install magisk on memu android 9, I've tried everything( it doesn 't work

 

[tech128]

Well currently kitsune magisk has some bugs that do not allow it to start properly on memu. You have to use the slightly older 26105 delta magisk to get it to work. Why they have removed this version even though its needed for memu is beyond me. Luckily archive.org has a copy.

Release d2a66567-delta(26105) · HuskyDG/magisk-files

Contribute to HuskyDG/magisk-files development by creating an account on GitHub.

web.archive.org

After you grab a copy, follow the instructions here:

Kitsune Magisk

With the exception of you do need to disable root access after you install magisk to the system partition. Why they tell you not to disable it for other emulators besides ldplayer is also beyond me.

Lastly, you probably want to debloat it since memu pushes so much ads and junkware its ridiculous.

Debloating & Optimizing MEmu

Debloating & Optimizing MEmu. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

 

[neerbiqs]

...

 

[neerbiqs]

Already got it work hehe

Btw, the boot.img of LDPlayer can be found in \system.vmdk\0.img\ if i'm right

View attachment 5260677

And Memu, *disk1.vmdk\2.img\. Only if you installed the instance

View attachment 5260679

I can't find boot.img (kernel,ramdisk) in latest Memu Android 9.
Was anyone able to find it?