- #CLOVER EFI FOR MAC OS SIERRA HOW TO#
- #CLOVER EFI FOR MAC OS SIERRA INSTALL#
- #CLOVER EFI FOR MAC OS SIERRA FULL#
- #CLOVER EFI FOR MAC OS SIERRA SERIES#
I attach an image: it's using the Pike El Cap boot.efi, modified as I've explained in point 2, just before the KP, having booted it in single user mode.
#CLOVER EFI FOR MAC OS SIERRA HOW TO#
This is the only thing that doesn't let us to have a good El Cap in our old Macbooks and MBPs.Īnd I don't know how to do that, so, I have installed again Yosemite on my old MB2,1. So, one year later of creating the "method 3", we are stuck in the same point we were: we need a boot.efi that we don't have, and it seems nobody knows how to modify Pike El Cap boot.efi to get it running without KPs.
#CLOVER EFI FOR MAC OS SIERRA FULL#
Smith, creator of rEFInd, who has helped me answering an e-mail full of questions, I'm very grateful to him for his help. If you have an unsupported EFI64 Mac, and you can use the default El Cap boot.efi (for example, MACBOOK 4,1), you can disable SIP installing rEFInd. I don't attach the "new" boot.efi", because it doesn't work. One this is done, you simply delete lines from 277 to 283.
We invent a board-id that doesn't exist (Mac-F32487Z7) and we say to the compiler that every mac with a board-id different to that fake Mac-F32487Z7 has to be redefined to a MACBOOKPRO_31 (this happens in line 275). I've done that, modifying the code, just to have every macbook or mbp recognised as it was a MBP 3,1. The reality, in 3 facts, all related to rEFInd:ġ- With EFI 32 from Yosemite, you cannot disable SIP with rEFInd.Ģ- With EFI 32 from Pike Capitan, you can disable SIP with rEFInd, but, 30 seconds later, you get a KP. The third step would be to check if our yosemite-pike's-boot.efi let us to boot Sierra from it.
#CLOVER EFI FOR MAC OS SIERRA SERIES#
I hope AMD people, who build kernels for their AMDs hackintoshes, can finally create that kernel: it would serve for their old AMDs and for our Core2Duo T7000 series CPUs, too.
#CLOVER EFI FOR MAC OS SIERRA INSTALL#
If someone has a non-SSE-4 kernel, please tell it to me, because if rEFInd disables SIP in El Cap, this is the first step to install Sierra on our EFI 32 MB 2,1-3,1-4,1 and MBP 2,1-3,1. If you have time, you know the idea, check it, too Maybe you can be the creator of the "new method 3". I will inform you in a few days if a "new method 3" can be created or not, with rEFInd and El Cap 10.11.6 It seems the actual version lets us to do that. When I discovered method 3, the version of rEFInd of that moment didn't let us to disable SIP (that was one of the things I tried to do when I was creating the method, and it failed). I hope that will let us to be able to:ġ- Have SIP disabled, so no more problems with the kext caches and so on I'm supposed to have 2 or 3 days to spend some time with my unsupported macs, and I'll try to get SIP disabled using the last version of rEFInd, because it's the base of Clover bootloader, which has let me to install El Cap (and Sierra, too) on my old 2007 Acer hackintosh. So, in brief, I remember method 3 was developed when El Cap 10.11.5 had just been released, it seems Apple decided to make some changes when realeasing 10.11.6 that "destroy" our "method 3". And that the kexts and all the terminal steps of the method 3 could be done with a Yosemite machine, but not with a El Cap 10.11.6 machine, because, although SIP was disabled, the El Cap 10.11.6 machine said all the time "Permissions wrong, omitting kexts." and this type of messages and it didn't obey me when I tried to do some "chown" and "chmod" to modify owner and permissions of the kexts. I could see, too, when cloning from a 10.11.0 backup, that the the boot.efi from didn't disable SIP. Other way, and talking about Capitan, I realised yesterday method 3 doesn't work with 10.11.6, but it works from 10.11.0 to 10.11.5
No, my idea is not talking about it, but just stating the GMA X3100 kexts from OS X Hackers work like a charm with Sierra 10.12.4.
0 kommentar(er)
