Jump to content

Clover, Yosemite & Custom Entries


v.kouk
 Share

19 posts in this topic

Recommended Posts

Hello , i was trying to make custom entries just to use the osx i use,so i decided to do that thing with custom entries . All was good with my yosemite upgradation from mavericks but now in my boot menu i got 1 windows icon in which i can't boot cause it says my pc need repair although when i remove the custom entries thing it boots fine . I did that EFI thing with microsoft boot also . And about osx it shows 1 partition that i boot from and 2 recovery partitions which is the same exactly. So what i am trying to fix is my windows + remove  1 useless partition . 

Thanks in advance

 

 

/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:       Microsoft Basic Data                         250.0 GB   disk0s2
   3:                  Apple_HFS Mac                     249.2 GB   disk0s3
   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4

 

k1fms7.jpg

Link to comment
Share on other sites

As you can see the 5th (Clover EFI) and 6th (Windows) entries have both legacy and UEFI code:

 

1:148  0:000  Scanning legacy ...

1:148  0:000   5: 'EFI' (clover) add legacy

1:165  0:016   added 'Boot Clover from EFI' OSType=3 Icon=clover

1:165  0:000   6: '' (vista,win) add legacy

1:166  0:001   added 'Boot Windows from ' OSType=2 Icon=vista,win

 
1:166  0:000  Scanning loaders...

1:225  0:000   5: 'EFI'

1:278  0:053  found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,3AB35F97-B3E6-4710-A536-69D85E426212,0x28,0x64000)\EFI\Microsoft\Boot\bootmgfw-orig.efi

1:279  0:000  skipped because path `PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,3AB35F97-B3E6-4710-A536-69D85E426212,0x28,0x64000)\EFI\Microsoft\Boot\bootmgfw.efi` is self path!

2:275  0:996    hiding entry: \EFI\BOOT\BOOTX64.efi

2:275  0:000   6: ''

2:316  0:040  found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,9E827C3A-2238-416F-BB4A-103D74D8B827,0x64800,0x1D1C1000)\EFI\Microsoft\Boot\bootmgfw.efi

2:362  0:045    hiding entry: \EFI\BOOT\BOOTX64.efi

2:362  0:000   7: 'Mac'

2:563  0:051  found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(3,GPT,32419BFA-4205-4148-AFA1-87B00A38F2C2,0x1D225800,0x1D02A8E8)\System\Library\CoreServices\boot.efi

2:696  0:133   8: 'Recovery HD'

2:747  0:050  found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(4,GPT,8A7D1B88-9B5C-4644-A8AC-2352B96E8DA2,0x3A2500E8,0x135F20)\com.apple.recovery.boot\boot.efi

 
Do you need the legacy ones? If you don't, disable it and try again to see if that extra entry is still visible. This might just solve your problem without the need of custom entries.
<key>Scan</key>
<dict>
   <key>Legacy</key>
   <false/>
</dict>

If you still want the custom entries, tell me which loaders from the above list you need and I'll help you create the custom entries. Or you can also upload the config.plist with the custom entries so I can use those are reference.

Link to comment
Share on other sites

So none of those windows entries worked but the rest did? How is the working Windows entry called when you delete the custom ones? Is it "Boot Windows from "?

 

Does the working entry appear if you turn off legacy detection like I suggested before? Try it please. I wanna make sure it's not a legacy windows setup.

 

And why do you have bootmgfw.efi and bootmgfw-orig.efi? I linked the new custom Windows entry to bootmgfw-orig.efi, but that may not be the right one, try changing the Path to bootmgfw.efi instead.

 

Did you follow a multiboot tutorial or something? If you did, then post the link please.

Link to comment
Share on other sites

Yeah it says boot windows from

Its legacy install , cause when i delete all entries boots fine .. I followed poken's guide somehow although now what i want to do is install windows UEFI .

Link to comment
Share on other sites

No, but a quick google will point you to many guides, like this one: link. Read the comments too, people suggest doing a backup, then repartitioning and restoring to it as a "quicker" solution. I think the best way would be to repartition the disk as GPT and reinstall Windows altogether but the restore option might work as well.

Link to comment
Share on other sites

 Share

×
×
  • Create New...