Android doesn’t boot on virtualbox and VMware

This problem can be meeting on every version android OS, if we want to install on virtual machine

What can we doing for solution?


You have to edit menu.lst file. Here is how:

  1. boot in debug mode (usually the second option in boot menu)
  2. when booting stops (for me it just hangs there with flashing cursor and without any prompt) enter mount -o remount,rw /mnt
  3. enter cd /mnt/grub
  4. enter vi menu.lst
  5. press Shift+a
  6. right under the first boot entry find the line starting with kernel initrd=/in (your line might look different; it depends on Android version; in general just find the line that starts with kernel)
  7. at the end of the line type vga=834 nomodeset xforcevesa
  8. press ESC then :wq – these commands will save the file and quit vi
  9. enter cd /
  10. enter umount /mnt
  11. enter reboot -f

Now the system should reboot in the VESA mode of your choice.

This will enforces to use the VESA driver for X.

You can replace the vga=xxx by any number you want for your screen resolution. Also tested that 832 works fine (gives 800×600 resolution).

exemple :

Windows 10 does’t load after migration image on SSD

  1. We must to load from usb or dvd disk image Windows 10 or LiveCd where is repair windows tool
  2. Open command line and enter commands one by one. You may see error sample “access denied” ignore this message
  • bootrec.exe /fixmbr
  • bootrec.exe /fixboot
  • bootrec.exe /ScanOs
  • bootrec.exe /RebuildBcd

3. Now, without fail, using “Disk Part”

  • diskpart
  • list volume
  • select volume where installed Windows sample “sel volume 0”
  • list partition
  • sel partition 0 (where installed windows!!!)
  • active

WELL DONE , NOW Windows must load normal

Resolutions like 1680×1050 and 1440×900 are not available in graphics properties

On some monitors, when using the Intel graphics chipset, users may experience the problem of not being able to set their own display resolution. Resolutions such as 1680×1050 and 1440×900 are not available in graphics properties.


Intel has released a driver specifically for this problem, however, there is a probability of occurrence of such side effects, as longer than normal resume times from standby.

Download the driver and see the problem in more detail at this link