Boot Android_X86 4.4 from Grub2

Asked by Peter Dupler

I am trying to add an entry into Grub2 to boot Android_X86 but nothing seems to work. Android's default Grub Legacy boots it just fine, but I can't seem to either boot directly or to chainload into Android's Grub Legacy.
I realize this is technically a Grub Customizer question, but I AM using Grub Customizer to add the entry so... If it needs to be moved let me know, sorry!
- Peter

Question information

Language:
English Edit question
Status:
Expired
For:
Grub Customizer Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Daniel Richter (danielrichter2007) said :
#1

As there's a separate bootloader, chainloading is a good idea. However chainloading needs a boot sector of the destination bootloader (grub 1 in this case). The boot sector code can be installed to mbr of an entire device (eg. /dev/sda) or to each partition (eg. /dev/sda1). When chainloading, the second way is the better one as you will have to overwrite your grub 2 otherwise if there's one hdd only.

How did you start android before? If it's still possible, start it and run grub-install /dev/[your android device]. If it isn't startable, you'll have to use a live system containing grub 1 and install with --root-directory after mounting the android partition.

After doing this, you'll be able to chainload to your android partition.

Revision history for this message
Peter Dupler (mr-chili) said :
#2

Sorry for the slow response, other computer problems...

Okay, so typically when I write an entry in Customizer for Linux I have a initrd line and a linux line. In the Android version of Grub I see it has a kernel line instead. Leaving that in, I get an error that it doesn't know what the command kernel means. If I change the "kernel" to "linux" it doesn't work either, but I don't remember the exact error I got. Chain loading to the Android Grub would be a great idea but I can't seem to get that to work either. Asked a separate question about the chainloading aspect:

https://answers.launchpad.net/grub-customizer/+question/269564

Not sure what I am doing wrong, but trying to learn.... I have been trying to chain load a USB flash drive, a USB HD, an internal HD, a partition on an internal HD, Just can't seem to get anything to work. The Grub1 menu.lst is installed in the Android directory but each install was "overwritten" with my basic Grub2 install and Grub-Customizer since Android's Grub1 only recognizes Android and Windows, and that's it. As to how I could ever get it to run at all, I either use the live iso file or hit boot selection at BIOS and tell it to boot from HD#2 instead of my main drive. I have 3 internal drives and 1 USB drive constantly hooked up. I have tried installing it on all the drives but my experiment partition is on drive #2 which is where I left its bootloader set up. I can of course just keep using boot selection at BIOS when I want to play with it, but if I can, I would still really like to figure this out!

Thank you so much for your time! I know getting Android up & running is NOT necessary, it's just something I am trying to figure out. I know there are a lot of people with a lot more pressing and important problems that need attention, so thanks again for responding!

- Peter

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Daniel Richter (danielrichter2007) said :
#4

back to status "open"

Revision history for this message
Launchpad Janitor (janitor) said :
#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Daniel Richter (danielrichter2007) said :
#6

back to status "open"

Revision history for this message
Daniel Richter (danielrichter2007) said :
#7

I think I cannot help you, sorry :-(

Revision history for this message
Launchpad Janitor (janitor) said :
#8

This question was expired because it remained in the 'Open' state without activity for the last 15 days.