After the install you will boot and will stuck into Android command prompt.
I also met this error and full reinstall helped, so I assume this error is somehow connected with the Run option, 'cause when I selected Reboot I didn't face the error. Is not related to VGA issue and should be dealt separately. The big drawback of this approach is that the next time you try toīoot from the hard drive, GRUB will not be able to find the image Do not use immediate Run Android_x86 option, instead select Reboot and eject the iso.First of all, install the Android from iso image correctly through the wizard steps.It can be made persistent, and should be! And I show you how:)
He is right in the core thing that the cause of the issue is VGA resolution used by Android, but he is wrong in his assumption it is disposable fix and should be typed at each boot. I'd like to extend and improve Smith answer based on personal experience. You can find all the VESA modes when you use the iso file and pick the boot option to boot in VESA mode - it will show the list with all modes (numbers are in hex and there is also a redundant letter in front of some modes - ignore it) and you can test them there immediately to see if it works and is good to use in this menu.lst fix, but you have to convert it from hex to dec first using any hex->dec converter. You can replace the vga=xxx by any number you want for your screen resolution.Īlso tested that 832 works fine (gives 800圆00 resolution).
This will enforces to use the VESA driver for X. Now the system should reboot in the VESA mode of your choice. press ESC then :wq - these commands will save the file and quit vi.at the end of the line type vga=834 nomodeset xforcevesa.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).when booting stops (for me it just hangs there with flashing cursor and without any prompt) enter mount -o remount,rw /mnt.boot in debug mode (usually the second option in boot menu).
I have a feeling that the solution might be something linked to the graphics settings but i'm not exactly sure. iso does boot up though all the way to the GUI in Live mode (LiveCD).Īny assistance would be greatly appreciated. I've tried nomodeset and xforcevesa in the Grub boot parameters but nothing seems to work. The VMs in both VMware and Virtualbox have: HDD=4GB(IDE), RAM=2GB, 2 CPUs and they boot through EFI. I've seen somehow similar questions on Android-SE ( here and here), but they use older versions of Android x86 and don't seem to have solutions that work for me. I get the result seen in the screenshot below and then a blank screen with a blinking cursor. However when I reboot it passes GRUB, picks the correct Android installation, but it does not boot. The installation seems to proceed properly (using EXT4, and EFI Grub) and i get a message that it has installed successfully. I've downloaded the latest Android x86 (android-x86-6.0_20160129.iso) from here and tried to install it to the HDD on a VM in VMware Workstation and in Virtualbox.