IIRC from going through a bit this forum, extracting the iso to a partition -if-I-could-point-to-that-partition-at-boot- should trigger the installation (If that is not the way I could install android to usb using another computer -skipping-grub-during-install- and copy the contents to my desired partition). I can't point to android without grub. So what I need to do is install grub to-only-android's-partition, and show windows boot manager the way to grub. Android installation doesn't give me an option to install grub to a partition. Let's say I'm not wrong this far. On Wed, Jan 7, 2015 at 12:26 PM, hashirt wrote: > I can't point to android without grub.
GRLDR.MBR is unknown, probably legitimate. If the file GRLDR.MBR is located on your computer, download UnHackMe for free to fix the problem with GRLDR.MBR. Browse files . 修正 grldr.mbr。 Loading branch information. 1 parent 4bf9ee3 commit c59cb7df7c6aeb938b62bb5d686badce4869bd9c yaya committed.
It doesn't have to be grub. Any other boot manager that can load linux will also do.
> > > If the fellow at link above is right, If I could install grub to a partition > via an emulator, I could copy first 512 bytes of that partition using dd or > dd for windows, with that 512 bytes I could point windows boot manager via > bcdedit to android partition. > It appears what I only need is a way to install grub to that partition under > windows. Grub4dos should be easier to install since it already includes grldr.mbr. Search 'grub4dos' in the comment of section of the link you posted. -- Fajar Miker1029 07:05.
Just finished up the move the hard drive test and it worked fine with one little step that I didn't think of. The rootnoverify will be wrong under the Windows title in menu.lst and should be changed to: rootnoverify (hda0,0) I used an old Toshiba Satellite A75-S231. Installed Windows XP to it. Removed the hard drive and put it in a USB enclosure.
Plugged it into to a Dell Dimension 9100 and booted up an android-x86 4.4-r2 CD. Installed to the USB hard drive (/dev/sdf1) in my case. Entered No to format, Yes to install grub. It saw Windows and asked if I wanted a Title entry.
The rootnoverify it generated was hd5,0. Once I changed that I put the hard drive back in the laptop and both android and Windows were able to boot. On Fri, Jan 9, 2015 at 9:41 AM, George Turner wrote: > I suppose I could try the move the hard drive approach.
I think I have > everything except Win 7. I would have to use Win XP. There is a good chance > that when the hard drive goes back into the laptop that nothing will boot.
> Getting Win 7 back should not be too hard, but a pain nevertheless. > Installing grub will wipe out the Window boot loader in the MBR. > > On Thu, Jan 8, 2015 at 9:14 PM, George Turner wrote: >> >> Yes, you can't usually do that with Windows because they want you to buy >> another copy.
Linux on the other hand is very good at having a look at the >> hardware at boot time and doing the right thing. I didn't mean to discourage >> you from trying, but I think the outcome is bleak.I have many old computers >> and always try when there is a new version. Those old nvidia cards seem to >> be a major problem. UEFI is certainly not an issue for you, at least not on >> the laptop. >> >> On Thu, Jan 8, 2015 at 8:33 PM, David A wrote: >>> >>> sorry for the late response, didn't expect this place to be so active. >>> >>> the way i attempted installing android was like this: >>> >>> >>> >>> Instead of using windows disc I used the android.iso file, i'm assuming >>> based on what i've read here that simply does not work >>> >>> If someone could point me to a proper guide or tutorial to learn the >>> basics from that would be much appriciated.
I'm an advanced computer user >>> but no absolutely nothing about linux/android, so it'll be a good read >>> >>> also, in response to everyone: >>> >>> George Turner: Your suggestion of sticking the hdd into another computer >>> and installing android on, then swapping it back.with windows that would >>> not work due to various (chipset normally) drivers, is that doable with >>> linux/android? I can just install the OS on the hdd while its in another >>> machine and it'll work when re-installed to the original laptop? >>> >>> And yes I'm aware this system is old, but It is a project I'm currently >>> tinkering with just for fun.
>>> >>> >>> Miker1029: I dont know what either UEFI or GRUB is short of 'theyre >>> bootloaders', i assumed I could treat linux/android installs like windows >>> installs (ie shove iso's files into a bootable partition and reboot) but i >>> guess not? >>> >>> -- >>> 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. >>> To post to this group, send email to. >>> Visit this group. >>> For more options, visit.
>> >> > > -- > 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. > To post to this group, send email to. > Visit this group. > For more options, visit.
-- 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. To post to this group, send email to. Visit this group.
For more options, visit. David A 22:33. What is your complete grub entry for 'Install Android-x86 to harddisk'? Is the harddisk listed the right one for android instaler? (hd0,0) -> 1st partition of your harddisk.
Note that 1st partition is not always C drive, it can be a hidden system partition. Do you put the installer files (i.e. Content of android ISO) on the root of the disk, or inside a path? 'kernel /kernel' and 'Error 15: File not Found' means grub looks for 'kernel' on the root of the partition you specify, but couldn't find it.
If your specify (hd0,0), and first partition is C in windows, then grub can't find 'C: kernel' -- Fajar David A 23:45. I suspect he won't even see hd1, since grub only shows whatever the BIOS sees. In other words, if he can't boot from usb disk (which is what started this thread), grub won't even see the usb disk. The easy workaround is to make sure that grub can see the internal disk, and find out exactly the numbers (e.g.
Partition numbers are not always the same as order on disk). If he can find where windows drive (C) is detcted as (e.g. Hd0,2 or whatever), then simply copy grub's installer there and adjust grub's menu accordingly. No need to use external drive. -- Fajar Fajar A. Nugraha 00:22.
Try tab completion:) You should be able to see whether fd0 has any partitions, and what files are there. See my previous reply, you probably won't be able to get grub to see the usb disk. In any case, check what files are on partitions 0, 1, and 4 (again, using tab completion), map the numbers to the drive letters you see in windows, just for your reference. Copy android installer to whichever one that: - has enough space - is not the destination drive for installation - won't be formatted.
-- Fajar David A 00:36. On Fri, Jan 9, 2015 at 3:36 PM, David A wrote: > fajar, can you expand on your comment 'copy grub's [Androids] installer > there and adjust grub's menu accordingly' copy whatever is in android iso (kernel, initrd.img, system.sfs, whatever) to your install drive (C?) > > more specifically, what/how do i adjust grubs menu? Thats the menu.lst that > i've been playing with yes? > Yes > > Before i put this into effect on the system let me run this by you: > > with this setup: > > > lets say I put the android.iso files into C: directory, that should be > (hd0,2) > No. Check again what grub sees in the command line.
It's either (hd0,0), (hd0,1), or (hd0,4) > i would then edit menu.lst and change the various install paths to: > > root (hd0,01) > > if i wanted to overwright the first partition (D drive), Does this sound > correct to you? Same as above. See whatever grub detects. -- Fajar David A 00:58. On Fri, Jan 9, 2015 at 4:35 PM, David A wrote: > well, i think i've just had a nice wave of unfortunate luck. > > firstly, I was able to install android by accepting a current partition > instead of trying to modify partitions.
This allowed me to install android > on a pre-existing partition There are tools that let you format non-ntfs partitions from windows. IIRC lets you do that.
> > then.i installed grub by mistake.so now I have no access to my windows > install (unless someone can help me out here.) Press 'c' at grub menu, then try typing in manually what George wrote: rootnoverify (hd0,X) chainloader +1 in your case it's probably hd0,4 After that you need to find a way to either access android's partition and edit menu.lst, or reinstall windows mbr (e.g. Bootrec, ) > > and whats worse, when i run android, it just hangs at a blinking cursor > before even reaching the ANDROID splash logo your system might not be compatible with android-x86.
Try vesa mode, to isolate whether it's graphics problem. -- Fajar George Turner 02:52.
How to Boot Android x86 from BOOTMGR ***tested on Win10 x64 1. Edit BOOTMGR 'BCD' file using BOOTICEx86.exe (in the attached zip file) to chainload 'grldr.mbr' (in the attached zip file) (see picture attached) 2. As for me, i create it my self. Here is the log steps to create ext4 formatted data.img using command prompt in Win10 x64: ------------start------------ Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C: Windows system32>d: D: >cd ddwin D: ddwin> D: ddwin>dd bs=10M count=1 if=/dev/zero --progress of=data.img rawwrite dd for windows version 0.5. Written by John Newbigin This program is covered by the GPL.
See copying.txt for details 10,485,760 100% 1+0 records in 1+0 records out D: ddwin>mke2fs -t ext4 -F d: ddwin data.img mke2fs 1.42.13 (17-May-2015) cygwin warning: MS-DOS style path detected: d: ddwin data.img Preferred POSIX equivalent is: /ddwin/data.img CYGWIN environment variable option 'nodosfilewarning' turns off this warning.