How to Recover Broken VMs and Data in MEmu

#How to recover your virtual machine in Android Emulator?#

If you want to recover from the original vmdk file, please follow the below steps. This is not recommended, but a repair method when you forget to backup properly with ova file.

Let’s take MEmu_1 as an example.
memu1vmdk

1. Run MemuHyperv.exe with admin privilege (Where can I get it? Click here)

2. Click Add in MemuHyperv
faq-reg-vm-6

3. Select MEmu_1.memu to add.
faq-reg-vm-7

4. Click Settings for MEmu_1 and check the sequence of 3 disks. The correct sequence is “system(540MB) –> data(16GB) –> sd card(32GB)”. If they are not in order, please remove and attach again. faq-reg-vm-8

5. Open MEmu Multiple Instances Manager and run MEmu_1. If you can not find MEmu_1 in it, please close all MEmu* processes in Windows Task Manager and open it again.
faq-reg-vm-9

Note: If you still can not run MEmu_1 correctly or get below error message, faq-reg-vm-1

please make sure the two VM uuid strings in .MemuHyperv.xml and Memu.memu.xml are exactly same. In addition, double confirm the VM path in MemuHyperv.xml is correct.faq-reg-vm-2
MemuHyperv.xml:
faq-reg-vm-3
MEmu.memu.xml:
faq-reg-vm-4

 

#How to Recover Data from Broken VM#

If your VM is broken to boot somehow, I suggest you try to export this VM and then import it again.

However, if unfortunately it still fails, here is the final recovery method you can take a shot.

1. You need to download MEmuHyperv tool first. There are two versions, 32-bit, and 64-bit, which depends on your Operation System. If you have no idea which is suitable, Click Control Panel> System and Security > System and check it out.

2. Download and extract MEmuHyperv files into MEmuHyperv directory, which depends on your MEmu installation path.

Exported Files

hyperv

3. Run MemuHyperv.exe as Admin. Please make sure all MEmu processes are closed in Task Manager. Let’s take an example. MEmu_1 is broken and MEmu_2 is good. We will guide you on how to recover your data in MEmu_1 and attach to MEmu_2. In the MEmu Manager,  every instance(VM) have three partitions: Primary Master is system volume, Primary Slave is data volume, Secondary Master is SD Card. (Remember the file name, but don’t get mislead by disk1, disk2, and disk3, sometimes it’s randomly ordered).

MEmuHyperv

 

4. Choose MEmu_1(Broken), Click Settings > Storage, Choose Primary Slave Storage and right-click, Remove Attachment and Click OK. Then we will see it removed

Pic 1

Pic 2

Pic 3

5. Repeat the same operation to MEmu_2(Good). Remove Attachment Primary Slave Storage from MEmu_2.

Pic 4

6. Click File and Enter into Virtual Media Manager, find Primary Slave Storage VMfiles of MEmu_1 and MEmu_2, which are both not attached, then remove but keep the two files (NOT delete).

Pic 5

Pic 6

Pic 7

Pic 8

7. Find the directory of MEmu_1 and MEmu_2, which depends on your installation path. Copy the Primary Slave Storage VMfile from MEmu_1 to MEmu_2 folder.

hyper1

hyperv2

8. Enter into MEmu_2(Good) Settings and Choose Storage. Click the circled button to add Hard Disk, then Click choose an existing disk, find the MEmu_1(Broken) directory, choose the Primary Slave Storage vmdk file (your original data volume) to add.

Pic 9

Pic 10

Pic11

9. Now you have inserted your data volume into a good/new VM. Suggest you do the same thing to the Secondary Master Storage (SD Card Volume) if you have data on it.


> Back to MEmu 101, everything you need to know about MEmu <<