[android-x86] 4.2 runs from live cd, but bootloops on android logo when installed to HDD

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Search Discussions

Electrik jesusI am having this same issue with the 2/27 build as well on my Acer w500, I will post back how I fix it if I can ;) On Wednesday, February 20, 2013 9:58:43 AM UTC-5, thewoun...@gmail.com wrote: -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to android-x86@googlegroups.com. Visit this group

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Electrik jesusI was able to fix this by reinstalling as normal, not read/write ;) On Wednesday, February 20, 2013 9:58:43 AM UTC-5, thewoun...@gmail.com wrote: -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to android-x86@googlegroups.com. Visit this group at

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Erik JohansenChoosing not read/write resolved it on my Acer Aspire One. -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to android-x86@googlegroups.com. Visit this group at http://groups.google.com/group/android-x86?hl=en. For more options, visit https://groups.google.com/groups/opt_out.

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump toinstall to hard disk, alongside my fresh windows 7 install. There is only asingle NTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Thanos PapoutsisI have exactly the same issue. When i install it as read/write and run the android right after installation without rebooting everything is ok, but when i reboot the system makes it as far as the android graphic screen and basically bootloops there. If reinstall it as normal no read/write its ok but i need the read/write option cause i want to do some changes in the system folder. I tryied everything any suggestion? On Wednesday, February 20, 2013 4:58:43 PM UTC+2, thewoun...@gmail.com wrote

I have exactly the same issue. When i install it as read/write and run theandroid right after installation without rebooting everything is ok, butwhen i reboot the system makes it as far as the android graphic screen andbasically bootloops there. If reinstall it as normal no read/write its okbut i need the read/write option cause i want to do some changes in thesystem folder. I tryied everything any suggestion?

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Jon WestThe only other option is a straight ext3 install of android ONLY :( no windows :( this way android sees it as the first and only partition. The only other option is finding a way to mount a virtual partition from a .fs file. -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to

The only other option is a straight ext3 install of android ONLY :( nowindows :( this way android sees it as the first and only partition. Theonly other option is finding a way to mount a virtual partition from a .fsfile.

On Monday, March 4, 2013 3:46:03 AM UTC-5, Thanos Papoutsis wrote:

I have exactly the same issue. When i install it as read/write and run theandroid right after installation without rebooting everything is ok, butwhen i reboot the system makes it as far as the android graphic screen andbasically bootloops there. If reinstall it as normal no read/write its okbut i need the read/write option cause i want to do some changes in thesystem folder. I tryied everything any suggestion?

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump toinstall to hard disk, alongside my fresh windows 7 install. There is only asingle NTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Thanos PapoutsisI formatted a usb stick in ext3 i installed only android in rea/write mode but nothing happened. Exactly the same behaviour as before. If not reboot android loads ok after reboot pc cant boot to android. I dont know what to do -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to

I formatted a usb stick in ext3 i installed only android in rea/write modebut nothing happened. Exactly the same behaviour as before. If not rebootandroid loads ok after reboot pc cant boot to android. I dont know what todo

On Tuesday, March 5, 2013 11:34:02 PM UTC+2, Jon West wrote:

The only other option is a straight ext3 install of android ONLY :( nowindows :( this way android sees it as the first and only partition. Theonly other option is finding a way to mount a virtual partition from a .fsfile.

On Monday, March 4, 2013 3:46:03 AM UTC-5, Thanos Papoutsis wrote:

I have exactly the same issue. When i install it as read/write and runthe android right after installation without rebooting everything is ok,but when i reboot the system makes it as far as the android graphic screenand basically bootloops there. If reinstall it as normal no read/write itsok but i need the read/write option cause i want to do some changes in thesystem folder. I tryied everything any suggestion?

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump toinstall to hard disk, alongside my fresh windows 7 install. There is only asingle NTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to methat if I had intended to modify it in any significant way that Id wantthis option. I'd tried setting userdata image size to both the min and maxjust to see about a change, no difference either way.

Jon WestI think that it might be because Grub is written to the boot sector of the HD and Android isn't on the HD, so it cant find it. Try to install Android to the HD and see if it will boot instead of the USB drive. -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to

I think that it might be because Grub is written to the boot sector of theHD and Android isn't on the HD, so it cant find it. Try to install Androidto the HD and see if it will boot instead of the USB drive.

I formatted a usb stick in ext3 i installed only android in rea/write modebut nothing happened. Exactly the same behaviour as before. If not rebootandroid loads ok after reboot pc cant boot to android. I dont know what todo

On Tuesday, March 5, 2013 11:34:02 PM UTC+2, Jon West wrote:

The only other option is a straight ext3 install of android ONLY :( nowindows :( this way android sees it as the first and only partition. Theonly other option is finding a way to mount a virtual partition from a .fsfile.

On Monday, March 4, 2013 3:46:03 AM UTC-5, Thanos Papoutsis wrote:

I have exactly the same issue. When i install it as read/write and runthe android right after installation without rebooting everything is ok,but when i reboot the system makes it as far as the android graphic screenand basically bootloops there. If reinstall it as normal no read/write itsok but i need the read/write option cause i want to do some changes in thesystem folder. I tryied everything any suggestion?

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch driversnot working), the asus ICS build (couln't boot at all), and the 4.2 devbuild all from live CDs. The JB build boots from live cd just fine,multitouch loads up and works, the only issue is it seems to be missingwifi drivers, and thats a seperate and less difficult problem I supposethan this.

I liked the way that JB handled on my machine and made the jump toinstall to hard disk, alongside my fresh windows 7 install. There is only asingle NTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to methat if I had intended to modify it in any significant way that Id wantthis option. I'd tried setting userdata image size to both the min and maxjust to see about a change, no difference either way.

Dscmlocated this...give it a try Partition your USB drive/SDCard, into two partitions, using this EaseUS Partition Master, which is what I used. Partition layout needs to be one with 1GB of space with FAT32 filesystem, that is for the installer. Remaining partition of type ext3 (Linux partition). The installer, when live-booting from the USB Drive/SDCard, will show the just-created partition on the USB/SDCard, just select that partition to install on it and its done. -- You received this message

Partition your USB drive/SDCard, into two partitions, using thisEaseUS Partition Master, which is what I used.

Partition layout needs to be one with 1GB of space with FAT32filesystem, that is for the installer.

Remaining partition of type ext3 (Linux partition).

The installer, when live-booting from the USB Drive/SDCard, will showthe just-created partition on the USB/SDCard, just select thatpartition to install on it and its done.

On Mar 6, 12:38 pm, Thanos Papoutsis wrote:I formatted a usb stick in ext3 i installed only android in rea/write modebut nothing happened. Exactly the same behaviour as before. If not rebootandroid loads ok after reboot pc cant boot to android. I dont know what todo

On Tuesday, March 5, 2013 11:34:02 PM UTC+2, Jon West wrote:

The only other option is a straight ext3 install of android ONLY :( nowindows :( this way android sees it as the first and only partition. Theonly other option is finding a way to mount a virtual partition from a .fsfile.

On Monday, March 4, 2013 3:46:03 AM UTC-5, Thanos Papoutsis wrote:

I have exactly the same issue. When i install it as read/write and runthe android right after installation without rebooting everything is ok,but when i reboot the system makes it as far as the android graphic screenand basically bootloops there. If reinstall it as normal no read/write itsok but i need the read/write option cause i want to do some changes in thesystem folder. I tryied everything any suggestion?

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump toinstall to hard disk, alongside my fresh windows 7 install. There is only asingle NTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to methat if I had intended to modify it in any significant way that Id wantthis option. I'd tried setting userdata image size to both the min and maxjust to see about a change, no difference either way.

Jon WestThe only other option is a straight ext3 install of android ONLY :( no windows :( this way android sees it as the first and only partition. The only other option is finding a way to mount a virtual partition from a .fs file. On Wednesday, February 20, 2013 9:58:43 AM UTC-5, thewoun...@gmail.com wrote: -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to

The only other option is a straight ext3 install of android ONLY :( nowindows :( this way android sees it as the first and only partition. Theonly other option is finding a way to mount a virtual partition from a .fsfile.

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Dscmthese "issues" have been around a while...and been solved by many in these forums 1) shrink your windows partition leaving 2-4GB of free space 2) use gparted(google it) and format your new 2-4GB partition as ext3 3) install whatever flavor of android-x86 from usb flash drive to your new 2-4GB partitioned/formatted space 4) select install grub when asked, also select add windows when asked this method is known to work fine....... can't use fat/ntfs/whatever...good luck -- You received this

On Feb 20, 9:58 am, thewouncebut...@gmail.com wrote:I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Thanos Papoutsisyes in a HD its ok. Did you manage to install androidx86 as read/write in a usb stick? -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to android-x86@googlegroups.com. Visit this group at http://groups.google.com/group/android-x86?hl=en. For more options, visit

On Feb 20, 9:58 am, thewouncebut...@gmail.com wrote:I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Dscmwhy would you want to??? but anyway...I have installed android-x86 onto sd card and it worked fine as I recall..... try this if you must: http://www.austintek.com/dual_boot_usb_flash_drive/ -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to android-x86@googlegroups.com. Visit this group at

On Mar 8, 8:09 am, Thanos Papoutsis wrote:yes in a HD its ok. Did you manage to install androidx86 as read/write in ausb stick?

On Thursday, March 7, 2013 6:40:37 PM UTC+2, dscm wrote:

these "issues" have been around a while...and been solved by many inthese forums 1) shrink your windows partition leaving 2-4GB of free space 2) use gparted(google it) and format your new 2-4GB partition as ext3 3) install whatever flavor of android-x86 from usb flash drive to yournew 2-4GB partitioned/formattedspace 4) select install grub when asked, also select add windows when asked this method is known to work fine....... can't use fat/ntfs/whatever...good luck

On Feb 20, 9:58 am, thewouncebut...@gmail.com wrote:I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.

Christian StarlingI am having the same issue with the Feb build, HP Pavilion G6... On Wednesday, February 20, 2013 8:58:43 AM UTC-6, thewoun...@gmail.com wrote: -- You received this message because you are subscribed to the Google Groups "Android-x86" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com. To post to this group, send email to android-x86@googlegroups.com. Visit this group at

I'm running an HP Tx2z. Have run the tx2500 ICS build (touch drivers notworking), the asus ICS build (couln't boot at all), and the 4.2 dev buildall from live CDs. The JB build boots from live cd just fine, multitouchloads up and works, the only issue is it seems to be missing wifi drivers,and thats a seperate and less difficult problem I suppose than this.

I liked the way that JB handled on my machine and made the jump to installto hard disk, alongside my fresh windows 7 install. There is only a singleNTFS partition on my disk. Grub setup fine, and I can access/boot mywindows 7 install, yet when trying to boot android the system makes it asfar as the android graphic screen and basically bootloops there. The splashscreen flickers constantly and the system never loads, I've let it sit aslong as an hour like this. I had tried a suggestion a few posts below minein another thread, to try ctrl+alt+f1 and look at the log, but the systemseems unresponsive to this command.

The funny thing is, when booting from live CD, and then choosing theinstall to hard disk option, the system seems to install just fine, andwhen presented with the "run android" option at the end of that process, itruns fine. Yet if I shut it down, and start the machine up again, androidsimply cannot finish booting from hard disk.

I'm not really sure where to begin with this one, but I am entirelycomputer literate in that if anyone has any suggestions I don't exactlyneed the laymans version of it.

I had set the system to install as read/rite capable, it seems to me thatif I had intended to modify it in any significant way that Id want thisoption. I'd tried setting userdata image size to both the min and max justto see about a change, no difference either way.