Not booting after installing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install android-x86-4.0-eeepc-20120101.iso to USB device (or SD Card) via 
USB formatted using unetbootin.
2. Installed with (and without) RW permissions for the file system, used ext3, 
and installed GRUB when prompted.
3. Boot the USB or SD Card.

What is the expected output? What do you see instead?
Android to boot, instead a black screen appears with blinking underscore. 
Tested on mulitple USB/SD card devices, sometimes the message 'MISSING 
OPERATING SYSTEM' occurs instead.

What version of the product are you using? On what operating system?
android-x86-4.0-eeepc-20120101

Please provide any additional information below.
PC used was an Asus eeePC 1000HE.

After installation, booting straight into the Android OS will work but when you 
reboot the system the problem occurs. I'm lead to believe it has something to 
do with the GRUB bootloader, but I am unsure.

Original issue reported on code.google.com by ddtran74 on 8 Feb 2012 at 10:36

[GoogleCodeExporter]

I'm getting a similar issue, but on my 1201N model. I used the same flash drive 
in a 1000H model and it works perfectly. It won't run LiveCD or run after 
installation on the 1201N. I've tried the 3.2 and 4.0 releases, as well as the 
4.0 Asus Laptop release, nothing.

Original comment by bwi...@gmail.com on 17 Mar 2012 at 12:45

[GoogleCodeExporter]

I went through this same issue on an 1000h, I created my install media with 
unetbootin. I found that the lili (linux live) media creation tool solved the 
issue, and I believe (for me at least) the issue was with unetbootin.

Original comment by sagef...@gmail.com on 17 Mar 2012 at 8:33

[GoogleCodeExporter]

Sage, I've tried both with no luck, sadly. I've been using LiLi mostly and also 
tried unetbootin and neither gave any results.

Original comment by bwi...@gmail.com on 17 Mar 2012 at 9:50

[GoogleCodeExporter]

did you ever solve the problem... mine sounds the same . except i always get 
boot partition not found.

Original comment by albertah...@gmail.com on 21 Aug 2012 at 3:09

[GoogleCodeExporter]

I've read somewhere else that it's the graphics chip, apparently the Android 
port was not compatible. I don't know if it's been solved in the mean time.

Original comment by bwi...@gmail.com on 21 Aug 2012 at 3:11

[GoogleCodeExporter]

strange thing is running on usb not installing works perfect but as soon as i 
install thats the problem i get... ah well guess i have to wait.

thanks for your quick response

Original comment by albertah...@gmail.com on 21 Aug 2012 at 3:15

[GoogleCodeExporter]

I got it working several months ago. I used a 8GB USB stick and formatted it 
with NTFS during the installation process. For whatever reason, that seem to 
had worked when booting via the USB stick.

You might need to try it with a USB/SD card larger than 8GB for it to work.

I have not tried this with any other build.

Original comment by ddtran74 on 21 Aug 2012 at 3:22

[GoogleCodeExporter]

like dd said, try an ntfs format before creating the bootable media, i went 
through plenty of trial and error before mine booted up correctly.

Original comment by sagef...@gmail.com on 21 Aug 2012 at 3:49

[GoogleCodeExporter]

I have a Lenovo s10-3t and have the same issue with a 2GB SD card. I can 
install android and boot normally in fat32 but in any other type (ext3, ntfs) I 
get the blank screen with the blinking cursor. The problem is that I cannot 
install androis as read/write in fat32... Any syggestions anyone?

Original comment by panagpa...@gmail.com on 24 Aug 2012 at 4:59

[GoogleCodeExporter]

i installed android 4.2 from androidx86, and the boot goes good until the 
android loading screen, then when that is done, my moniter is clicking (old 
crt) the way it does when i change screen resolutions, and nothing happens 
after that

Original comment by daniel.stalnaker.10 on 3 May 2013 at 1:39

[GoogleCodeExporter]

on my eee pc 900 i use live boot of partedmagic and formatted my drive to ext3. 
then ran the Android installation and picked do not format

Original comment by warman...@gmail.com on 22 Jul 2013 at 4:43

[GoogleCodeExporter]

Same issue in DELL D620 using android-x86-4.3-20130725.iso
Not sure partition is formated anyway. 

Original comment by evilz...@gmail.com on 22 Dec 2013 at 11:25

[GoogleCodeExporter]

Solving for blank screen after reboot : After clean install, go to settings -> 
security -> disable lock screen..
Work for me..

Original comment by hando...@gmail.com on 13 Jan 2014 at 12:57

[GoogleCodeExporter]

I have tried unebootin and lili and 
android-x86-4.0-r1.1-asus_laptop,android-x86-4.2-20130228,android-x86-4.3-201307
25. originally I got failed image,followed by installed correctly. then after 
formatting to ext3 (with parted magic) before attempting to install.
looked like it had worked but I still get blank screen and cursor. It is 
possible to type and pressing enter gets; 
r
root@x86:/ #
quite possibly a graphics thing as sometimes all text is in top left of the 
screen
and it says ANDROID root@x86:/ # then goes blank with cursor

Original comment by vwil...@gmail.com on 5 Feb 2014 at 10:58

[GoogleCodeExporter]

i tried a lot of version of x86android, and all of them run perfectly on 
usblive mode (unetbootin on 8gb fat32 pendrive) but after install on hdd with 
format and no format mode (sata 160gb) on reboot stay screen on No Proper boot 
device.....

anyone solve this?? (lili may be a solution?? i didnt try)

Original comment by fernando...@gmail.com on 22 Aug 2014 at 3:29

[GoogleCodeExporter]

I also am getting the issue with no operating system found. Installed to hard 
drive, installed Grub, on reboot grub does not come up and no operating system 
is found.

Original comment by dfo...@gmail.com on 17 Sep 2014 at 12:54

[GoogleCodeExporter]

After partitioning with gparted before installing (instead of partitioning with 
the tool provided by the installer) it worked just fine. 
I just selected the partition and formatted with ext3 during the installation 
process. 

Original comment by jorge...@gmail.com on 17 Sep 2014 at 12:58

[GoogleCodeExporter]

Thats actually exactly what i did. I wiped my drive and created one ext3 
partition using gparted, booted to the live usb and ran the install. I believe 
i may have wiped the boot partition when doing that, so I'm trying a grub 
rebuilder / recovery. I assumed the Android install would have created a new 
boot record.

Original comment by dfo...@gmail.com on 17 Sep 2014 at 1:07

[GoogleCodeExporter]

Remember to check the boot flag. Also the partition must be primary type. 
When prompted select yes to install grub. 

Original comment by jorge...@gmail.com on 17 Sep 2014 at 1:11

[GoogleCodeExporter]

guys found out the solution shut down ur android go to settings and then 
storage and remove the iso from there

Original comment by mprajay...@gmail.com on 20 Sep 2014 at 9:14

[GoogleCodeExporter]

I did not install it on a virtual machine. But as I said before, it is already 
working for me.

Original comment by jorge...@gmail.com on 21 Sep 2014 at 2:41

[GoogleCodeExporter]

Installed Android-x86-4.4-r1 on a 16 Gb USB stick with Grub. Boots into Grub 
then shows a few lines then the word A N D R O I D.  Stops there...  Does the 
same using Live CD on a USB Stick.   Installed on a Eee PC 900D. Win XP 
installed on 8Gb SSD, BIOS set to boot from USB first.  Any suggestions???

Original comment by skipmcw...@gmail.com on 30 Oct 2014 at 1:08

[GoogleCodeExporter]

Here's what worked for me on my Dell Latitude E5400, Intel Core2Duo Laptop.

- Boot to the USB with Android (I used unetbootin-windows-608 to create the 
bootable usb - Used a 4GB stick) 
- Insert stick, boot to usb
- Select install to HDD
- At the select a partition screen, select "C"reate/Modify partitions
- I selected my partition, then Delete
- Then New (this changed the FS Type to Linux, I did not see this FS Type on my 
previous failed attempts to install)
- Then Bootable
- Then Write, type "yes" to confirm
- Then Quit
- Back at the select a partition, I selected DO NOT FORMAT
- Installed Grub, etc.
- Then rebooted
- Success, Android 4.4r1 running on my laptop!

Hope that helps!

Original comment by 808hamil...@gmail.com on 30 Oct 2014 at 4:00

[GoogleCodeExporter]

Using your steps, I get the following...
Tries to boot... Gets to the point where it says
A N D R O I D root@x86:/ #
With a flashing cursor. What can I type to get the process to continue? It 
seems like the command to load the GUI is just not there. 

Original comment by skipmcw...@gmail.com on 31 Oct 2014 at 3:24

[GoogleCodeExporter]

Something's hanging up (obviously). The only thing I could tell you is to keep 
trying the install using different variables.  Maybe try to format to ext2 or 
don't install GRUB.

Original comment by 808hamil...@gmail.com on 6 Nov 2014 at 8:08

[GoogleCodeExporter]

well, the same thing happened to me and i am still stumped.

Original comment by jessepet...@gmail.com on 9 Feb 2015 at 10:46

[GoogleCodeExporter]

I have a similar problem on android-x86-4.4-r2.img 

I am installing on a pendrive from another pendrive. And if I boot to android 
x86 instead of rebooting at the end of installation it starts all right. But 
when I reboot the system, it doesnt boot anymore and stays stuck at blinking 
cursor. Then I reboot to restart the system.

System boots OK with android_x86-5.0.2.iso with the same process but without 
openGL and ability to install/update apps

Original comment by shovan.k...@gmail.com on 21 Mar 2015 at 4:05

[GoogleCodeExporter]

Android OS not supported by AMD CPU so if your PC had AMD CPU Android OS will 
not work.

Android OS is only working on Intel CPU PCs.

by*emoboy* :)

Original comment by emoboy12...@gmail.com on 24 Mar 2015 at 6:14

[GoogleCodeExporter]

Mmm, booting from the flash drive, when I pick VESA mode I can boot on an AMD 
CPU. However, after installing, or booting normally, I see the same issue as 
everyone else here.

Original comment by zeq...@gmail.com on 29 Mar 2015 at 9:20

[GoogleCodeExporter]

pls help me as well with the same problem

Original comment by sandyo...@gmail.com on 13 Jul 2015 at 11:18

[GoogleCodeExporter]

I had the same problem. I had installed 4.4-r2 and it would not boot. Turns out 
it is in fact a broken GRUB bootloader. I used a Gentoo LiveDVD in the 
VirtualBox machine and set up the bootloader, rebooted into the GRUB shell, 
loaded the kernel and initrd with commands and wallah! It booted.

So it is a broken bootloader. I think the problem was that the version of GRUB 
included does not support ext4. So if you want to use ext4 or any other problem 
FS, you'll have to install GRUB2 from a Linux CD. I used the Gentoo Live DVD, 
btw.

Original comment by luckyp3...@gmail.com on 15 Jul 2015 at 5:24