The Android emulator never finishes booting in Android Studio
Android Studio stops waiting for the emulator and reports a time-out while it waits for the emulator to come onlineShort answer
The emulator process started but Android never reported itself ready to adb, so Studio gave up waiting. The usual causes are a bad Quick Boot snapshot, a graphics mode the machine cannot run, no working hypervisor, or a stale adb server. Start the AVD from the terminal with -verbose to see which.
Fix it fast
1Find out which cause you have
Start the same AVD outside Android Studio with verbose output and a cold boot. If it boots, the saved snapshot was the problem; if it still hangs, the output shows the failing part.
emulator -avd Pixel_8_API_35 -no-snapshot-load -verbose2Match what you see, then jump to its fix
- 1
Earlier runs worked, then the emulator froze after a crash or forced shutdown.Quick Boot restores a broken snapshotFix - 2
The window opens but stays black or crashes, or the log mentions GPU or OpenGL errors.The graphics mode does not work on this machineFix - 3
Booting takes many minutes, or the log says acceleration cannot be used.No usable hypervisor, so the emulator runs without accelerationFix - 4
The emulator looks fine but adb devices does not list it or shows offline, or on Linux and Windows it hangs right at start.The adb server is stale or the audio driver blocks start-upFix
- 1
What does the error look like?
Android Studio stops waiting for the emulator and reports a time-out while it waits for the emulator to come onlineThe emulator window stays on the boot logo or a black or white screen
Cause 1 of 4
Quick Boot restores a broken snapshot
1Check
Quick Boot saves the AVD state on exit and loads it next time. A snapshot saved during a crash can fail to load. The first-step command skips loading it.
emulator -avd Pixel_8_API_35 -no-snapshot-load2Fix
Boot once with the snapshot ignored. If it works, use Cold Boot Now in Device Manager. If it still fails, wipe the AVD data, which deletes apps and settings on it.
emulator -avd Pixel_8_API_35 -wipe-data3Verify
The home screen appears and adb sees the device as ready.
adb devicesConfirmed by developer.android.com
Cause 2 of 4
The graphics mode does not work on this machine
1Check
Automatic graphics lets the emulator choose hardware or software rendering. An unsupported graphics option can give crashes or wrong images, and software mode is the documented fallback.
emulator -avd Pixel_8_API_35 -gpu software2Fix
Set Graphics acceleration to Software in the AVD's advanced settings, or keep -gpu software on the command line. Update your graphics driver afterwards and try Automatic again.
emulator -avd Pixel_8_API_35 -gpu software -no-snapshot-load3Verify
The device finishes booting.
adb wait-for-device shell getprop sys.boot_completedConfirmed by developer.android.com
Cause 3 of 4
No usable hypervisor, so the emulator runs without acceleration
1Check
The emulator relies on KVM on Linux, Windows Hypervisor Platform on Windows and Hypervisor.Framework on macOS. The accel-check option tells you whether one is installed and usable.
emulator -accel-check2Fix
Enable virtualization in the BIOS or UEFI and turn on Windows Hypervisor Platform on Windows, or install KVM and make sure your user may use it on Linux. The emulator cannot run accelerated inside another virtual machine.
# Windows: Turn Windows features on or off > Windows Hypervisor Platform, then reboot
# Ubuntu
sudo apt-get install qemu-kvm3Verify
accel-check reports a hypervisor as installed and usable.
emulator -accel-checkConfirmed by developer.android.com
Cause 4 of 4
The adb server is stale or the audio driver blocks start-up
1Check
adb devices shows the state of each emulator. The state offline means it is not responding. Faulty audio drivers can also stop the emulator from starting.
adb devices -l2Fix
Stop the adb server and let it restart, then start the AVD again. If it still hangs at launch, turn off audio for that run.
adb kill-server
adb start-server
emulator -avd Pixel_8_API_35 -no-audio3Verify
The emulator is listed with the state device.
adb devicesConfirmed by developer.android.com
How do I stop it coming back?
- Close emulators from their own window or Device Manager so Quick Boot can save a clean snapshot.
- Keep the Android Emulator and system image packages up to date in SDK Manager.
- Leave about as much free disk space as the AVD needs; a nearly full disk makes boot very slow.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
The Android Emulator will not start with hardware acceleration (HAXM, Hyper-V, KVM)
KVM acceleration can NOT be used
Intel HAXM is discontinued, and current emulators no longer use it.
4 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fix