Related
While trying to perform a clean installation of MacOS Sierra on a Macbook Pro 2012 (8Gb ram, 250 SSD Crucial Driver and i5 processor) through the boot install option (cmd + r) from the web (Internet install, an this is needed as I just installed the new SSD) the operation always gets stuck at 2 minutes before finishing.
Left it the whole night and in the morning saw the message in the image of this post.
Booted in the new AFP2 filesystem format for the drive as required in the Sierra version. Created the partition and erased the disk without any problem.
Seems the installer is fail fast but not very descriptive, any help would be appreciated otherwise that Mac will likely be a deluxe "cup holder" :(
Thanks a million
sierra boot install failure picture
Solved it myself in the end, for anybody stuck on this in the future.
And the only way I found out to do it is to install the OS that came with the Macbook Pro (2010 Mountain Lion in my case) and then update but from the installed system rather than the boot repair util.
Restart the Macbook and right after you hear the sound hold the option key until you see the spinning globe icon.
Input the WiFi credentials to access the repair util (this is the original util that came with your mac not the one updated that only bounds to install High Sierra OS)
Now install your default OS.
After this, inside the default OS, go to app store and download the High Sierra installer and install from there. Installation seemed to go fine.
Loads of effort but at least does the trick,
Hope it helps.
I am following the instructions given HERE
I can install it to the vmware hard disk fine and get it running, but then it says to open a terminal and execute su
The terminal says that it cannot make me a root and nothing else
I am not able to go any further after this and so the internet isn't working in the virtual machine
Moreover, the internet works if I was just using the live CD version, without me having to do anything else
How do I get root permissions in android x86 on VMware?
--- EDIT---
After playing around some more with this I have noticed another problem: when I try to start the virtual machine, most of the times it reaches the Chrome coloured android startup logo, the logo animates continuously but the screen is sort of stuck at that phase. And if I loose focus to the vmware window and come back, I see that the window is blank and I am not sure if the virtual machine is even further loading or not. How do I properly get Android x86 to work on vmware (with full install on it's virtual hard disk and not just the live CD version? Should I try other virtual machines? I have not been able to get others such as qemu and bochs to work in the past and see that vmware is the easiest and most stable option, so I would like to run this in vmware if possible.
check here www.bitdirect.nl/?p=128
I followed this with a few little tweaks here and there and it worked perfectly.
only downside is transferring data outside of the android os is a pain.
I have successfully downloaded and installed Genymotion and Virtualbox as well as a Virtual Device Image but I am unable to create a virtual device.I get an error message stating
Unable to create Virtual Device:
Failed to import OVA
My laptop Specs
8gb RAM
Intel Core i7 (Sandy Bridge)
Hardware Virtualization is enabled in the BIOS.
Deleting the Genymotion cached .ova file, deleting the corrupted deployed image, redownloading the image, and reinstalling it addressed the issue for me.
Note that the deployed images are under:
~/.Genymobile/Genymotion/deployed
the cached ova files are under:
~/.Genymobile/Genymotion/ova
I solved the problem.It was my mistake.
It works fine by running genymotion with administrative privileges.
I solved the issue deleting the deployed images in
~/.Genymobile/Genymotion/deployed
I didn't touch ova files
I just ran into this problem too, so just in case anyone needs it:
The reason why it needs admin privileges is probably because of your settings on where it store the virtual device..
Go to Settings - Virtual Box - and change your virtual devices storage area. I got mine set to something like \Program Files\Genymotion, that's why it needs Admin privileges. I only blanked the field, clicked ok, and it got set to the default which is in my home directory..
After that no need to run as admin anymore..
(I need 50 reputations to comment, so had to use this answer..)
I solved the issue myself by deleting all old devices (the folders of previously made devices) from my .android/avd folder.
In my case, the DHCP server was missing from Virtual Box's Host Only Adapter. I added a DHCP server at 192.168.56.100 with addresses from 192.168.56.101 - 192.168.56.254 and it came up.
I also had the issue. Had to delete Genymotion cached files/devices then redownload devices and reinstall.
We had the same issues, it was because we had wrong version of Oracle VM Virtual Box. Make sure you uninstall wrong version and re-install Compatible Oracle VM Virtual Box.
just delete the file in your ova and it should fix it, thats what i did, no need to run program under admin or anything. didnt delete my deployed files either. (I was trying to create new virtual machines not open them)
Have a look at this blog.
Genymotion is previously known as AndroidVM.
As the blog stated:
Known bugs (same as 20121119 release) :
Hardware OpenGL/Intel HD/Windows : On most Intel HD drivers running Windows, the AndroVMplayer might crash (in the driver DLL) when starting Android ; you may have to restart AndroVMplayer an important number of times before it suceeds
Hardware OpenGL/WebView : On some GPUs (mostly NVidia ?), the browser and all apps which use the WebView component might show scrambled HTML content
AndroVMplayer now support window resizing, as well as fullscreen mode ; to use AndroVMplayer in fullscreen mode, you have to :
select “manual resolution” and tick the “fullscreen” box
press F11 (Ctrl+F11 on Mac) to switch to fullscreen when the player window has appeared
When starting the virtual machine, AndroVMplayer now check different things :
If your AndroVM virtual machine doesn’t have the “hardware OpenGL” option enabled, it can enable it for you before starting the VM.
If your AndroVM virtual machine first network adapter is not configured, it can configure it for you (as well as create the host-only network for you).
To summarize that, with this new AndroVMplayer, to use OpenGL hardware you just have to :
Import the AndroVM ova in VirtualBox
Start AndroVMplayer, choose your resolution and the virtual machine you’ve just imported
Click “Run” and it should work
You can still use AndroVMplayer with non-VirtualBox systems (e.g VMWare) but, obviously, you won’t benefit from automatic VirtualBox configuration and VM start/stop ; in this case, you have to choose ‘none’ as the VM name and directly type the IP address of your virtual machine.
Please note that, due to the change in communication, old AndroVMplayer won’t work with 20130222 OVAs and old OVAs won’t work with 20130222 AndroVMplayer.
Disadvantage of deleting the deployed and .ova files is obvious i.e. you have to download the massive 200mb image again. A better choice is to :
Open genymotion and open settings --> virtualBox --> virtual devices browse and set the path to a folder which can be completely accessed without administrative pivileges e.g. for ubuntu set virtual devices path to any folder in your home directory for example /home/user/deployed and for windows you can use a folder like C://deployed.
That's it . Now you can use your already existing .ova file again to deploy image to new locatioin without any problem.
I followed following steps
I removed everything under {~/.Genymobile/Genymotion/ova} folder (with only doing this step it works sometimes)
removed everything under {~/.Genymobile/Genymotion/bin} folder
After which I downloaded the fresh copy and it worked like magic.
Hope this helps.
I solved this error message by fixing the path to the virtual machines folder (Setting > VirtualBox - Virtual devices). Yes, I had broken settings...
In case someone is using Mac OSX YOSEMITE or earlier. Follow this post. It worked for me. http://forums.macrumors.com/showthread.php?t=1196027
Run these two command in Terminal:
sudo chmod 755 /Applications
sudo chmod 755 /Applications/Virtualbox.app
Took me hours to get it to work!
Check if you have problem with your virtual device path under
Genymotion > Settings > Virtual Box > Virtual Device >
If it is still an issue remove files under ~/.Genymobile/Genymotion/ova
If it is still an issue remove files under ~/.Genymobile/Genymotion/bin
Remove Genymotion and all files under ~/.Genymobile/ & reinstall
If you have installed the Genymotion plugin without VirtualBox then make sure the version of VBox is compatible with the plugin, otherwise the plugin will not deploy the virtual device regardless of the OVA file.Install the latest versions of both if you are unsure
Once you verified the versions, you may need to either:
a: Give administrative privileges for Genymotion via properties
OR
b: Change the location for the deployed devices via Settings/VirtualBox to somewhere more accessbile like D:/GenyMotion VMs/
If both step 1 and 2 doesnt work for you, sadly you will have to clear the cache via Settings/Misc and reinstall the OVA file.Hopefully your efforts will be worth it. Good Luck.
It works fine by running genymotion with administrative privileges.
I solved it by deleting all of file in Ova,Templates and Deployed folder, I can run download and reinstall again and run without Administrative privileges
I solved this problem on windows setting up sdk path in configuration option.
Double check the virtual device you're trying to create has the same version on Genymotion that you have running.
I just upgraded to 2.1.1 but all the virtual devices I was trying to install were for 2.1.0. Downgrading Genymotion did the trick.
A very simple Solution that i just Tried is:
1) Delete your Instalation Folder at ~/Genymobile
2) Delete the Virtual Device Folder at C:\Users\ your_name\AppData\Local/Genymobile
3) Reinstall
4) Done.
Oracle VM ware has an update for Windows 10. I was getting this error until I installed this update.
I had the same problem because i had an old version of Virtual Box (4.0.0).
So, I uninstalled genymotion and the old version of VB,
and I installed genymotion with virtual box (5.0.28).
And Its worked fine.
This fixed the issue:
Just go to ~/.Genymobile/Genymotion/ova (Either you are on Mac OSX
or Windows, you can find this path by looking for Virtualbox path at
the Genymotion Settings, there is a path to Genymotion/deployed
folder, you should go to Genymotion/ova folder)
Open the ova file with your virtualbox.
At the Virtualbox startup dialog box, Appliance settings, It shows Guest OS type set to Other Linux 64, you should double click and change it to your OS type (e.g Mac OSX El Captain (64-bit)) and Import:
Now launch Genymotion and find the virtual device in the list of already deployed ones ready to run
Run the virtual device, after first run you get a warning saying Genymotion version does not match with Virtualbox version and choose Continue.
I hope it helps future visitors to this page.
Any of above solutions didn't work for me but I finally found it!
You should remove under folders in C:\Users\[your user]\VirtualBox VMs.
I hope it helps you.
First you go to ova inside the folder and delete all files
C:\Users\UserName\AppData\Local\Genymobile\Genymotion\ova
After you uninstall the genymotion and virtual box. next you can do for install of genymotion and virtual box as check your support your OS(windows) capability version install then work fine.
Now you can create virtual device.
This way for work my windows 10 OS.
Solved!!
I am using OS X 10.9 (Mavericks), Genymotion v1.3.1
While adding the device, instead of adding Nexus, I added Galaxy S4/HTC One/Xperia Z - 4.2.2 with Google Apps.
This one just worked.
I bought a new Nexus 7, and Eclipse cannot see it. It is appearing in Device Manager as Android Device ---> Android Composite ADB Interface. There is no other devices category, and I have updated the list.
My SDK Manager has everything except for the obsolete installed and updated. I have also tried reinstalling Eclipse all together.
I have updated the driver via \adt-bundle-windows-x86_64-20130514\sdk\extras\google\usb_driver and it says the best one is already installed. USB-debugging is enabled on the Nexus 7. I am all out of ideas. Please help!
Uninstall and Reinstall Nexus 7
Update:
Plan B:
OK you say it didnt work.... this is kind of a long shot but saved my bacon a lot when I was working as a technician in my past life and had to find unknown device drivers.
Right click your Nexus in device manager , select properties and go to this page
The example shows my radeon card but if you google this hardware ID( the top one in your pc), and check a couple of random sites , you are likely to find it. This method is used for finding unknown drivers, and you may as well give it a shot as you have exhausted most options.
Plan C:
Trying the same nexus on a different windows7 computer to see if it installs . If it does, then you can try to extract it from that computer ( e.g. using driverguide software) and force windows on your main pc to use that.
Plan D:
run sysprep.exe on your PC by typing it in RUN and double clicking the file and clicking Generealize.This prepares your pc for imaging and removes all drivers. Note that you'll have to activate windows again after this.
Plan E:
And lastly, the call center answer , use system restore, although the damned thing fails 90% of the time and install again after a reboot. or a whole scary reinstall of windows :(
//Ignore below now as it didn't work for you
Download this driver http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
You can also check this question for a solution for Nexus and an alternative driver. I had the same problem , although not with a Nexus, but a sony Xperia, and I had to download a generic driver to get it going. The above samsung site has the driver, but the model is called SCH-I515. You should be able to fix it without the generic driver
ADB dosn't recognize my Galaxy Nexus - Win7
I have an issue with my HAXM installation. Here is the thing. I got this error every single time I tried to install HAXM for my computer:
Problem is, that my computer supports Virtualization Technology (see pic below). Any idea how to fix this issue?
Just follows these steps:
Go to Control Panel → Program and Feature.
Click on Turn Window Features on and off. A window opens.
Uncheck Hyper-V and Windows Hypervisor Platform options and restart your system.
Now, you can Start HAXM installation without any error.
Hello and welcome to the 3rd installment of the infamous Android Emulator on Windows saga. Despite the combined 3 trillion dollar market cap of Microsoft and Google, this remains to be a problem harder than going to the moon.
Below is the somewhat comprehensive list for Windows (so far as of circa 11/2022)
First make sure you have the latest version of Windows. As of writing, this is Windows 11 22H2 with all updates installed. If you have an older version of Windows, you'll have to try each one of the below, with possibly different combinations. Otherwise follow from the top until your issue is solved. It is ordered from the easiest/most likely culprit on a decent Windows machine, to the most unlikely cause.
Note that if you're doing below on a corporate machine, some of the below actions may be blocked by your admin, and/or flag your machine as suspicious activity as some actions intentionally turns off some security features. Depending on your situation, you may want to give a heads-up to your IT/security team.
If your Windows device has Bitlocker enabled on your boot drive contact your IT admin first. Messing with virtualization and boot configuration may trigger bitlocker prompts upon reboot. If you're working from home,this may mean taking your laptop to the office to get it unlocked by IT, as Windows may refuse to boot without unlocking BitLocker.
To find what is blocking the emulator launch, the surefire way is to open a terminal (cmd or powershell) and launch to from there as below.
First kill any existing emulator.exe instances, adb.exe instances, java.exe instances, qemu instances, android studio instances. Check in task manager to be sure.
The adb relaunches itself so its ok be running. But make sure android studio is not running. It seems to lock files/cache and not flush emulator configs, that may crash the emulator at launch, without any useful logs.
in a terminal
cd your_sdk_location\emulator
emulator.exe -list-avds
this will list what AVDs you have. Find the one you want
emulator.exe -avd your_avd_name -verbose
This will have a long log, and will have some information on what the failure is. If you see a VM heap size being outside of limits, it may say that it it automatically set to lowest or highest value. This is a lie. Open emulator settings and set it to within the limits manually, usually 550MB works. Launch android studio and edit the emulator instance to be within this limit, then close android studio, then wait about 30 seconds before attempting to launch the emulator. For all attempts of launching the emulator below, do not rely on android studio, launch from command line instead.
Note that the emulator editor UI in android studio can corrupt the config at times. If this happens, I don't know where this is stored, so you may have to delete and re-create the AVD. If this doesn't work, do not change and configs during AVD creation, then launch it from command line.
If the emulator doesn't launch, no useful failure logs, yet the emulator.exe exits after a few minutes, you may have android studio running. Exit/Kill Android studio, wait a minute or so and try again. If still fails, reboot.
Have an Antivirus (other than Microsoft Defender)?
Disable it
Reboot and try to launch the emulator
Disable Hypervisor Boot
open an admin terminal (cmd or powershell)
run bcdedit /set hypervisorlaunchtype off
try to launch the emulator. If still broken, try rebooting.
If your failure is due to install of HAXM/AMD hypervisor driver failing
run systeminfo in a terminal
at the end under Hyper-V Requirements: if it says A hypervisor has been detected this means emulator cannot launch virtualization.
Open Start > Windows Security > Device Security > Core isolation
turn off Core Isolation (previously known as Memory Integrity/Isolated User Mode)
Open Turn Windows features on or off and disable
Hyper-V Platform
Hyper-V Management Tools
Windows Hypervisor Platform
You can enable them after HAXM/AMD Driver install
on an admin prompt run bcdedit /set hypervisorlaunchtype off
reboot
try to launch the emulator
Check BIOS
go into BIOS/UEFI setup and look for settings like
VT-x
VT-d
Virtualization Technology
Hardware Virtualization
Make sure these settings are enabled
try to launch the emulator
Uninstall Docker Desktop
Some users have reported that uninstalling Docker Desktop fixed their issue.
It is unclear as to why docker desktop interferes with haxm installation. The reason is probably that it supports running docker images via a Hyper-V backend, and disabling this feature does not remove the hypervisor completely.
Go to Settings -> Add or remove programs, and uninstall docker desktop
reboot
try to launch the emulator
Nothing works
You shouldn't get here, since Android emulator can now run alongside with Hyper-V if you have 'Windows Hypervisor Platform' enabled.
If nothing above works, as a last resort you can try running Android in a Hyper-V VM and get ADB to connect to it. (Not a solution, but a workaround)
You can also run android using a third-party emulator like Genimotion.
¯\(ツ)/¯
Debug on a physical device
You can also use Wifi debugging via adb pair ip:port and adb connect ip:port commands.
or get a Macbook
After few days of googling I found, that problem was caused by hyperthreading (or hyper - v). I decided to edit my boot.ini file with option to start up windows with hyperthreading turned off.
I followed this tutorial and now everything works perfect
chances are that you have windows 8 with hyper-v installed? if yes remove hyper-v and your problem goes away!
First of all make sure you enabled Virtualization Technology in your BIOS. After restarting your computer press F1-F12 on your keyboard and find this option.
Make sure you disabled Hyper-V in your Windows 7/Windows 8. You can turn it off in Control Panel -> Programs -> Windows functions
You can try to disable your antivirus program for the whole installation process. Remember to restore all antivirus services after installing HAXM.
Some people recommend cold boot which is:
Disabling Virtualization in your BIOS
Restart computer and turn it off
Enable VT in your BIOS
Restart computer, turn it off
It's likely that now might be allowed to install HAXM
Unfortunately this step didn't work for me
Last but not least: try this workaround patch released by Intel.
http://software.intel.com/en-us/blogs/2013/04/25/workaround-patch-for-haxm-installation-error-failed-to-configure-driver-unknown
All you have to do is to download the package, unzip it, put it together with HAXM installator file and run .cmd file included in the package - remember, start it as an Administrator.
I had a lot of problems with installing HAXM and only the last step helped me.
In the "Turn Windows features on or off" window, un-check Hyper-V and also ensure that Windows Hypervisor Platform is unchecked. Windows Hypervisor Platform being enabled can also block the installation of the Intel HaxM
Maybe VT-X is not enabled in your BIOS.
See Intel HAXM documentation here: http://software.intel.com/en-us/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows
Intel VT-x not enabled
In some cases, Intel VT-x may be disabled in the system BIOS and must
be enabled within the BIOS setup utility. To access the BIOS setup
utility, a key must be pressed during the computer’s boot sequence.
This key is dependent on which BIOS is used but it is typically the
F2, Delete, or Esc key. Within the BIOS setup utility, Intel VT may be
identified by the terms "VT", "Virtualization Technology", or "VT-d."
Make sure to enable all of the Virtualization features.
Anti-virus software may interfere with the HAXM installation.
After trying to figure out what went wrong for a few hours I found a strange solution - uninstalling my anti-virus software , installing HAXM (which worked) and then re-installing the anti-virus software (Avast in my case but it could happen with other anti-virus programs as well.
The full check I went through to get this running is:
Check the 'Virtualization' and vt-X feature in the BIOS.
Verifying Hyper-V is not installed.
Checking weather vt-X is enabled in windows with the Intel tool and MS tool (mentioned in previous posts in this thread).
Disabling the anti-virus which didn't help.
Uninstalling the anti-virus (which solved the problem for me).
In Windows 10, Windows Defender has a feature of core isolation which uses virtualisation technology that will also interupt in working of HAXM. Disable it and try again. In my case disabling it solved my issue.
If you have an AMD Ryzen processor in your computer you need the following setup requirements to be in place:
AMD Processor - Recommended: AMD® Ryzen™ processors
Android Studio 3.2 Beta or higher - download via Android Studio
Preview page
Android Emulator v27.3.8+ - download via Android Studio SDK Manager
x86 Android Virtual Device (AVD) - Create AVD
Windows 10 with April 2018 Update
Enable via Windows Features: "Windows Hypervisor Platform"
Note:There is Hyper-V features... You should enable Windows Hypervisor Platform not Hyper-V.
Windows Hypervisor Platform is at the bottom
After conditions done avd x86 work without haxm install
Reference
In many cases some antivirus also start HyperV with window start and does not allow HAXM to install.
I faced this issue because of AVAST antivirus.
So I uninstalled AVAST, then HAXM installed properly after restart.
Then I re-installed AVAST.
So its just a check while installing as now even with AVAST installed back, HAXM works properly with virtual box and android emulators.
After I installed Visual Studio 2013 Update 2, Visual Studio notified me about a Windows Phone emulator update, which I installed (it was really a new component, not an update). It turned out this enabled Hyper-V, which broke HAXM.
The solution was to uninstall the emulator from Programs and Features and to turn off Hyper-V from Windows Features (search for "Windows Features" and click "Turn Windows features on or off").
If you dont find Hyper-V option in control panel as said in other responses here, try entering BIOS setup (restarting and pressing F-12 or ESC or other depending on your PC) and enabling Virtualization, located probably in CPU options.
I'm running Windows 10 and had this problem after I changed my SSD, I fixed it by disabling the VT support on Bios. I got a different error after I ran the installer. I rebooted and enabled VT support again and voila, working now.
If any of the answers doesn't work just remove Android Emulator and reinstall it again. and after that try installing Intel Haxm.
If none of the answers worked out for you, try this,
Hyper-V might not be disabled
If you have windows 10 features such as Device Guard and Credential Guard is enabled, it can prevent Hyper-V from being completely disabled.
The Device Guard and Credential Guard hardware readiness tool released by Microsoft can disable the said Windows 10 features along with Hyper-V:
Download it here, https://www.microsoft.com/en-us/download/details.aspx?id=53337
Download the latest version of the Device Guard and Credential Guard hardware readiness tool.
Unzip
Open the Command Prompt using Run as administrator
#powershell -ExecutionPolicy RemoteSigned -Command "X:\path\to\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1 -Disable"
Reboot.
I already tried all of the possible solutions on stackoverflow and didn't work
What I tried:
Disable Hyper-V in windows feature
Disable Hyper-V with command
Disable Device Guard
etc etc
Above solution still give me information about Hyper-V in System Information and the HAXM still failed to install.
But finally I found the solution, you have to disable Hyper-V from System Configuration:
Open System Configuration
Click Service tab
Uncheck all of Hyper-V related
Check System Information then Hyper-V is off now
Fix the error. follow the following steps
Turn off Hyper-V and Windows Hypervisor Platform
Goto RegEdit "Windows Defender is blocking HAXM."
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard
Set the key EnableVirtualizationBasedSecurity to '0'
if Key is not available create a key
Re-boot the machine
Install the intelhaxm-android.exe