Hello Mac Rumors. I am trying to install El Capitan on a late 2006 MBP (2,2, 2.33GHZ Core 2 Duo) using MacPostFactor. I have a dmg installer for El Capitan that worked flawless on a 2008 MBP (direct upgrade), but MacPostFactor cannot find the dmg installer...it seems it needs a .app installer?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OS X El Capitan on Unsupported Macs
- Thread starter TMRJIJ
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
OK, so I replaced the core duo processor in my iMac 4,1 (early 2006) with a core 2 duo, and using a firmware upgrade, the iMac "officially" became an iMac 5,1 (late 2006) capable of taking 4GB ram (though understandably the iMac can utilize only 3GB ram).
The good news is that using one or the other of the three methods listed in the first post, I was able to run Mountain, Mountain lion, Mavericks and El Capitan (tried them all).
The bad news (and I have read several posts on the issue with no answers) is that while Lion and Mountain lion would run perfectly with 4GB ram installed; Mavericks, Yosemite or El Capitan would not! Anything above 2GB ram, like 3GB or 4GB will get the iMac either hung at booting or a kernel panic.
I absolutely and already tried ram from PNY, Kingston, Micron, Samsung and Crucial, so it is definitely not the ram per se!
Having a love-hate relation with El Capitan running with only 2GB ram.
Any of you gurus can explain this frustrating mystery?
The good news is that using one or the other of the three methods listed in the first post, I was able to run Mountain, Mountain lion, Mavericks and El Capitan (tried them all).
The bad news (and I have read several posts on the issue with no answers) is that while Lion and Mountain lion would run perfectly with 4GB ram installed; Mavericks, Yosemite or El Capitan would not! Anything above 2GB ram, like 3GB or 4GB will get the iMac either hung at booting or a kernel panic.
I absolutely and already tried ram from PNY, Kingston, Micron, Samsung and Crucial, so it is definitely not the ram per se!
Having a love-hate relation with El Capitan running with only 2GB ram.
Any of you gurus can explain this frustrating mystery?
Last edited:
Hello! Sorry, if my question seems stupid, but I haven't found an answer to it here yet.
I have a macbook 4.1 (white, early 2008)
It is running on Yosemite, thanks to your soft guys. If I would want to update to El Capitan - can I do so straight ahead, or should I patch it once again first?
Thank you!
I have a macbook 4.1 (white, early 2008)
It is running on Yosemite, thanks to your soft guys. If I would want to update to El Capitan - can I do so straight ahead, or should I patch it once again first?
Thank you!
Hey everyone, I have an iMac late 2006 (5,1) that I'm trying to install El Capitan on. I know there has been a lot of trouble with these units and installing newer software, but nothing seems to be working. Since this mac was not mine initially, it seems that the RAM inside is from a 3rd party. There was also 3GB installed, but have knocked it down to 2 as I'm aware that the iMac 5,1 cannot boot to El Capitan, Yosemite, and Mavericks at more than 2GB of RAM. Could the fact that the RAM in the machine is not from apple cause my bootable USB made from macOS Extractor to just hang at the apple logo? I've tried replacing the boot.efi in the install drive with the boot.efi from macOS Extractor, and even tried boot32.efi. Stuck at the grey apple logo every time. Any suggestions? I've been at this for a long while but to no avail.
Hi!
[doublepost=1504487070][/doublepost]
Yes, MacPostFactor needs the original app installer from the Mac App Store
cordial saludo tengo un problema teno un imac de 2006 core 2 duo me dice que puedo actualizar hasta lion pero no meda la oppcion de actualizar por ende quiero correr un yosemite o otro sistema operativo mas actual actualmente tengo snow leopard 10.6.8 y muchas aplicaciones no me corren pero MacPostFactor no corre en snow leopard solo en lion hacia arriba que puedo hacer compañeros ya me urge cambiar de sistema operativo , muchas gracias por cualquier ayuda
i Have a trouble.. got error MacBook 4.1
"Error while getting file ID of /volumes/OS X Base System/boot. Ignoring.
I do everything, when i choose OS X Base System partition to boot its booting to OS X Lion again..
I try bless only partion but with no succes.
"Error while getting file ID of /volumes/OS X Base System/boot. Ignoring.
I do everything, when i choose OS X Base System partition to boot its booting to OS X Lion again..
I try bless only partion but with no succes.
I have a MacBook 2,1 late 2006.
I have succesfully installed El Capitan by following the Method 3 v3 - @skyfly555's method but I have updated the system directly on my external HDD and cannot boot again on it.
So I have deleted all the HDD and did the same method again.
This time it does not work at step 9.
The command "sudo kextcache..." returns the following error message (and a lot more after this one)
Kernel file /Volumes/Capitann/System/Library/Kernels/kernel does not contain requested arch: i386
Can you help me please ?
Best regards
I have succesfully installed El Capitan by following the Method 3 v3 - @skyfly555's method but I have updated the system directly on my external HDD and cannot boot again on it.
So I have deleted all the HDD and did the same method again.
This time it does not work at step 9.
The command "sudo kextcache..." returns the following error message (and a lot more after this one)
Kernel file /Volumes/Capitann/System/Library/Kernels/kernel does not contain requested arch: i386
Can you help me please ?
Best regards
Hello OS X Hackers! First of all, I want to tell you that I very much respect your work, passion and dedication. You truly bring old macs to life! I want to ask you a question though: I have a Macbook 3,1 (Late 2007) on El Capitan. Built-in Output, Microphone and Line-In work great. My problem is that I have a USB Audio Interface that worked just fine under Yosemite, but it doesn't get recognized in System Preferences. If I do the ioreg usb command in Terminal, it's there. I can even change settings on it through the special program that comes with it.
Bottom line: It shows up as a USB Device, but not as an audio device... I know that you probably did not engineer the kexts with usb audio functionality in mind, but could you please suggest an idea? It would mean a lot to me... Thank you!
[doublepost=1505413264][/doublepost]
Bottom line: It shows up as a USB Device, but not as an audio device... I know that you probably did not engineer the kexts with usb audio functionality in mind, but could you please suggest an idea? It would mean a lot to me... Thank you!
[doublepost=1505413264][/doublepost]
So I checked EC-Base Kexts from your files and APPLEUSBAUDIO is not included... That must be the problem. You guys are great anyway, thanks a lot. El Capitan runs flawlessly and the new graphics kexts are great... Do you think something can be done about the usbaudio kext?
Hey guys! Thank you for whatever help you may have been preparing to give me, but I solved it myself - installed appleusbaudio from Yosemite!Hello OS X Hackers! First of all, I want to tell you that I very much respect your work, passion and dedication. You truly bring old macs to life! I want to ask you a question though: I have a Macbook 3,1 (Late 2007) on El Capitan. Built-in Output, Microphone and Line-In work great. My problem is that I have a USB Audio Interface that worked just fine under Yosemite, but it doesn't get recognized in System Preferences. If I do the ioreg usb command in Terminal, it's there. I can even change settings on it through the special program that comes with it.
Bottom line: It shows up as a USB Device, but not as an audio device... I know that you probably did not engineer the kexts with usb audio functionality in mind, but could you please suggest an idea? It would mean a lot to me... Thank you!
[doublepost=1505413264][/doublepost]
So I checked EC-Base Kexts from your files and APPLEUSBAUDIO is not included... That must be the problem. You guys are great anyway, thanks a lot. El Capitan runs flawlessly and the new graphics kexts are great... Do you think something can be done about the usbaudio kext?
Just picked up a 2.16ghz black 2.2 macbook with 3gb RAM and for the life of me can't get this to work.
MacPostFactor results in an unbootable drive that no longer shows up under bootable disks after an "Option" boot, and macOS Extractor makes a USB drive or 2nd partition that only boots to the Apple logo and then hangs there. Have tried both the normal and 32bit boot efi's and with/without the optional video support with no luck on ether, and after 9 reinstalls of Lion I'm starting to get frustrated.
Can anyone confirm what steps/options they did to get 10.11 on a 2.2? Also if possible what versions of Macpostfactor or Macos_extractor were used? Bout ready just to install Windows and call it a day.
MacPostFactor results in an unbootable drive that no longer shows up under bootable disks after an "Option" boot, and macOS Extractor makes a USB drive or 2nd partition that only boots to the Apple logo and then hangs there. Have tried both the normal and 32bit boot efi's and with/without the optional video support with no luck on ether, and after 9 reinstalls of Lion I'm starting to get frustrated.
Can anyone confirm what steps/options they did to get 10.11 on a 2.2? Also if possible what versions of Macpostfactor or Macos_extractor were used? Bout ready just to install Windows and call it a day.
@Mathewww I'm not really active with this anymore, but when I did this multiple times before it is successful about 50% only. The step that seems to cause the problems is copying the kexts, it always looks like it works but doesn't actually copy them over sometimes.
It seems to only work reliably if you delete the existing kext ("rm -R kext.old") and then copy ("cp -R kext.new"). I do this one kext at a time so it requires a lot of careful typing. After that the kextcache bits should work. No guarantees though. My machine is also MacBook 2,1. Good luck!
It seems to only work reliably if you delete the existing kext ("rm -R kext.old") and then copy ("cp -R kext.new"). I do this one kext at a time so it requires a lot of careful typing. After that the kextcache bits should work. No guarantees though. My machine is also MacBook 2,1. Good luck!
Last edited:
HOW TO INSTALL EL CAPITAN ON AN UNSUPPORTED MACBOOK 2,1
Update (27th November 2016): This method has been updated on post #1 of this thread. But in this post you can find some explanations that aren't on post #1.
Note: This should work well with other EFI32 non-Mac-Pros Macs as iMac or whatever, but I haven't tested it because I don't have these computers.
CREDITS
- Thanks to atvusr, who confirmed me that it should be technically possible to install El Capitan cloning the hard disk from a machine running El Capitan, and gave me very valuable advices: After many hours of work, I can say that it’s true: you can have El Capitan into your old EFI32 non-Mac-Pro machine in this way.
- OS X Hackers work has been very helpful: their distros, their kexts… all the kexts used come from TRMJIJ and OS X Hackers.
- Pike’s work has been of an invaluable value: Pike's yosemite boot.efi works with El Capitan with my computer; Pike's Capitan boot.efi doesn't.
- Hackintosh Clover and kexts used by Hackintosh Community have a part into this story.
- The @parrotgeek1's script to boot Sierra on unsupported Macs (he uses a method that is very similar to the one I'm using here). This script gave me two important keys I added to the steps 9 and 10 (how to rebuild kernel and some boot flags).
A SMALL INTRO
With these old machines, the trouble is related to USB El Capitan kexts for these machines. To install El Capitan from an USB stick, you need to have USB supported, and, as you need some USB kexts than cannot be installed into the USB stick with which you are going to install El Capitan into your machine, you cannot do that.
So, the idea is cloning the hard disk with El Capitan from a machine running it. After that, you add some kexts to System/Library/Extensions, change the boot.efi to a Pike’s Yosemite EFI32 boot.efi (included in MacPostFactor), repair some permissions, caches… and it works.
After several attempts from my Hackintosh and from my MacBook Pro, both of them running El Capitan, I can say this process works... from both of them!
HOW I DID IT AND YOU CAN DO IT: THE TUTORIAL
1- First of all, you need an external 2,5” HDD or SSD. It has to be GUID HFS+ formatted. If you format it from El Capitan, it formats the hard disk in this way by default. I will suppose its name is "Capitann". This will create a HFS+ partition and an EFI partition automatically.
2- Clone the partition where you have El Capitan. It can be a real Mac, or even a Hackintosh. You can use Carbon Copy Clone (CCC) or SuperDuper! I have used both of them and they worked well. I cloned the disk having SIP disabled. To do that, boot from your El Capitan Mac from Recovery Partition, go to utilities, open a terminal, and write csrutil disable and reboot. You need to do all the steps from a El Capitan with SIP disabled.
3- The EFI partition should be a real Mac one. Two possibilities: it’s blank or it has only one file: /EFI/APPLE/EXTENSIONS/Firmware.scap. We may come from three scenarios.
a) If you have cloned from a real Mac, EFI could have some firmware from your source machine, which is different than your machine. CCC and SuperDuper clone the EFI partition automatically, so you have it.
b) If you have cloned from a Hackintosh with Legacy Clover, you should have the EFI partition empty.
c) If you have cloned from a Hackintosh with UEFI Clover, you have Clover into the EFI Partition. We want to delete it.
We want to be sure the EFI partition is empty.
4- You need to mount the EFI partition to be sure it's blank. You can use an app called “Clover configurator”, for example (http://mackie100projects.altervista.org/download-clover-configurator/). Go to “TOOLS/Mount EFI”. Click “Check partition”. Locate your external hard drive (disk0, disk1, disk2…). Click “Mount EFI partition” and select our cloned hard drive by its name (its name will be disk0s1 or disk1s1 or similar). Click “Open Partition”. Finder will open the EFI Partition of your hard drive.
If there’s something there, delete it and leave it blank. Unmount the partition.
5- Now we need to change the boot.efi so we will use the one I've attached. First, we need to change flags. From terminal (I'm supposing your Capitan partition is called "Capitann"):
cd /Volumes/Capitann/System/Library/CoreServices/
sudo chflags nouchg boot.efi
cd /Volumes/Capitann/usr/standalone/i386/
sudo chflags nouchg boot.efi
6- From Finder, use the "Go" menu and select "Go to folder..."
Open /Volumes/Capitann/System/Library/CoreServices/ and copy there the new boot.efi from where you have it (probably your Downloads folder).
Open /Volumes/Capitann/usr/standalone/i386/ and do the same.
We will assign the correct owner to them. From terminal:
cd /Volumes/Capitann/System/Library/CoreServices/
sudo chown root:wheel boot.efi
cd /Volumes/Capitann/usr/standalone/i386/
sudo chown root:wheel boot.efi
7- We need kexts. We are using tones of kext from TRMJIJ - OS X Hackers (for example, Beta-USB-Kexts). To make the things easy, you have them all zipped in this link:https://www.dropbox.com/s/oqtz4ozluwb6xx5/all-kexts.zip?dl=1. Download, unzip and copy them into /Volumes/Capitann/System/Library/Extensions/.
There are two more kexts, attached (more-kexts.zip), that come from Hackintoshes. You only need them if you are cloning from your hackintosh. Without them, El Capitan won't boot.
Note: If you have cloned from a hackintosh, check your kexts into /Volumes/Capitann/System/Library/Extensions/ and /Volumes/Capitann/Library/Extensions/. Maybe you have things you don't need. Some of them can give you problems, for example, AppleACPIPS2Nub.kext or ApplePS2Controller.kext. I can say the same if you have some HDAEnablerx.kext or whatever that is "very hackintosh".
If you have in these folders kexts like FakeSMC.kext and/or NullCPUPowerManagement.kext, remove them and change them by the ones I'm providing into the attached file, more-kexts.zip. These two kexts have to be into /Volumes/Capitann/System/Library/Extensions/. If they are in /Volumes/Capitann/Library/Extensions/, delete them: they have to be only in one place and its place is /Volumes/Capitann/System/Library/Extensions/.
8a- Before doing 8b, you need to be sure you have an important folder, which is not usually cloned.
Open in Finder /Volumes/Capitann/System/Library/Caches/ Do you have com.apple.kext.caches/ folder?
If not, open in another window of the finder /System/Library/Caches/, and drag and drop com.apple.kext.caches/ from /System/Library/Caches/ to /Volumes/Capitann/System/Library/Caches/.
After that, open a terminal and:
cd /Volumes/Capitann/System/Library/Caches/
sudo chown -R root:wheel *.*
Note: If you don't have com.apple.kext.caches/, in step 8b you can get a message like:
or Can't create /Volumes/Capitann/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext.JzU7 - No such file or directory. Or, in step 10, you can get a message like:
Can't create /Volumes/Capitann/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.l9a9 - No such file or directory and El Capitan won't boot.
8b- Now we need to rebuild permissions in the cloned disk. From terminal:
sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /Volumes/Capitann/
9- Now we will set boot flags and use them every time we boot. From terminal:
cd /Volumes/Capitann//Library/Preferences/SystemConfiguration/
sudo nano com.apple.Boot.plist
You will see:
<key>Kernel Flags</key>
<string></string>
You want to have:
<key>Kernel Flags</key>
<string>-no_compat_check kext-dev-mode=1 mbasd=1</string>
Or, if you want verbose mode, too, add -v flag:
<key>Kernel Flags</key>
<string>-no_compat_check kext-dev-mode=1 mbasd=1 -v</string>
Note: we need these flags, they are mandatory to have all the kexts loaded.
To go out from nano editor, Ctrl+X and say "y".
10- Now we want to have permissions in good condition, and rebuilding kext cache. From terminal:
cd /Volumes/Capitann/System/Library/Extensions/
sudo chown -R root:wheel *.*
sudo chmod -R 755 *.*
sudo kextcache -v 1 -a x86_64 -m /Volumes/Capitann/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /Volumes/Capitann/System/Library/Extensions
The terminal shoud give you messages like these:
/Volumes/Capitann locked; waiting for lock.
Lock acquired; proceeding.
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext IOUSBHostFamily.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOUSBHIDDriverSafeBoot.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext IOUSBHIDDriverPM.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext IOUSBFamily.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleWWANSupport.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOHIDUserClient.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOHIDSystem.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOHIDEventDriverSafeBoot.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOHIDEventDriver.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext IOBluetoothUSBDFU.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleUSBTopCase.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleTopCase.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleStorageDrivers.kext
kext-dev-mode allowing invalid signature -67050 0xFFFFFFFFFFFEFA16 for kext AppleIntelIntegratedFramebuffer.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleIntelGMA950.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOHDAFamily.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext DspFuncLib.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleMikeyDriver.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDAController.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
AppleDataSetManagement.kext - dependency for com.apple.iokit.IOAHCIBlockStorage lacks valid OSBundleCompatibleVersion.
AppleDataSetManagement.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
Created mkext archive /Volumes/Capitann/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext.
Note 1: AppleDataSetManagement.kext messages will be shown if you have an SSD and TRIM enabled.
Note 2: If you get messages saying permissions are not correct, or omitting... repeat steps 7, 8 and 10, until you get these messages saying "kext-dev-mode allowing invalid signature..". Be sure you are doing all the steps (especially the terminal commands) correct, and in the correct order.
Note 3: If you get a message saying "Can't create...", do the step 8a again, it hasn't been done.
11- Now we are going to build the prelinked kernel and kernelcache:
sudo kextcache -prelinked-kernel /Volumes/Capitann/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache -K /Volumes/Capitann/System/Library/Kernels/kernel /Volumes/Capitann/System/Library/Extensions /Volumes/Capitann/Library/Extensions
The output of the terminal should be similar to the prior one, because we are rebuilding kernel, but rebuilding caches, too.
Note: if you are on a hackintosh, you can get messages like:
SoftRAID.kext has incorrect permissions; omitting.
PromiseSTEX.kext has incorrect permissions; omitting.
hp_io_enabler_compound.kext has incorrect permissions; omitting.
HighPointRR.kext has incorrect permissions; omitting.
HighPointIOP.kext has incorrect permissions; omitting.
HandsOff.kext has incorrect permissions; omitting.
CalDigitHDProDrv.kext has incorrect permissions; omitting.
ATTOExpressSASRAID2.kext has incorrect permissions; omitting.
ATTOExpressSASHBA2.kext has incorrect permissions; omitting.
ATTOCelerityFC8.kext has incorrect permissions; omitting.
ArcMSR.kext has incorrect permissions; omitting.
ACS6x.kext has incorrect permissions; omitting.
Some of these kexts are from hackintosh and will not be needed. Other ones, like HandsOff.kext, can be from some app you have installed. Be sure you are not omitting something important, as the kexts the prior command has loaded (AppleHDA.kext or similar), and don't care for the rest.
12- Now we can change flags to boot.efi, and protect it again. From terminal:
cd /Volumes/Capitann/System/Library/CoreServices/
sudo chflags uchg boot.efi
cd /Volumes/Capitann/usr/standalone/i386/
sudo chflags uchg boot.efi
13- Unmount the USB external drive, and connect it to your unsupported EFI32 Mac.
14- Boot you unsupported Mac as the external drive wasn't there. When I boot, I have OS X Hackers Yosemite. Once booted, go to System Preferences/Startup Disk. Select "El Capitann" and click "Restart...". You will be asked. Confirm you want to restart and... wait and be patient
15- If El Capitan boots, you have to decide what to do. Maybe you want to clone the external HDD to your internal hard disk/SSD using CCC or SuperDuper!, or having El Capitan where it is. It's your decision.
IMPORTANT: After cloning from your external drive to the internal one, if you use Carbon Copy Cloner or SuperDuper!, you need to do step 8a. If you not, El Capitan won't boot. If you have used "Stellar Drive Clone" you don't need step 8a. This is because CCC and SuperDuper doesn't clone the folder /System/Library/Caches/com.apple.kext.caches/ and we need this folder to boot El Capitan. What happens if you don't have it? El Capitan will try to create the folder and, as it has SIP enabled, it won't load all the kexts we need, and, hence, El Capitan won't boot because the internal HDD/SSD will not be recognized.
ISSUES THAT COULD BE IMPROVED
SIP: When you boot El Capitan and go to terminal, if you write csrutil status, it says "enabled".
GMA950 KEXTS: They could be more El Capitan-adapted; TRMJIJ has said that, if he and another developer have time, they will do that. Thank you!
So, everything is working, all the needed kexts loaded, but, remember, you don't have QE/CI on GMA950 from Mavericks to El Capitan, and you will have the same issues you'd have using MacPostFactor to install Yosemite on this machine (machine can not wake up from sleep due to the lack of QE/CI, you may want to install nosleep extension, VLC not working, and so on). Remember, last officially supported OS X version with QE/CI is Lion; and Mountain Lion, this last one thanks to OS X Hackers. For this reason, I highly recommend an SSD and 4 GB of RAM.
For watching HD videos, you can use MPEG Streamclip or the HD player included in Vuze (VLC doesn't work). You can, too, disable animations (look at the post #1 of this thread, or look at the Yosemite on Unsupported Macs thread: https://forums.macrumors.com/threads/os-x-yosemite-on-unsupported-macs-guide.1761432/ ).
I've tried to describe all the issues you could have during the process, so I think you shoud not have any problems following this tutorial.
That's all! Thank you very much.
View attachment 640466
Hi,
I wanna ask you if this can be done on MBP2,2?
Actually, I have tried but it didn't succeed.
I did everything follow from post #1 and the one I quoted.
I'm stuck with prelinking kernel command.
I always get a message "xxxxx.kext has incorrect permissions; omitting." and kernel file is not created.
Gonna say that EVERY kexts are saying this and I'm sure that my hackintosh is indeed SIP disabled.
I thought because I'm running Sierra so, I install El Capitan. Finally, just got the same thing.
I tried both El Capitan with 10.11 and 10.11.6(Official App Store one). Nothing is different.
Moreover, I got an El Capitan clone in dmg from online (10.11) and I tried with modded boot.efi and install your kexts.
It worked and finally booted up! but it worked for a few minutes on Desktop just and restart.
I haven't tried your boot-vs-67.efi because while I'm writing this, I decided to go back to Yosemite.
MacPostFactor gave me an error 1 with El Capitan too.
I'm so frustrated right now.
Any workaround?
Or anyone with MBP2,x with El Capitan works, pls tell me. I have been trying to install El Capitan for almost a week now.
When you say it worked for a few minutes and then restarted, you mean you got a kernel panic/crash right? Using wrong boot.efi is likely cause of this. The one done by pikeralpha for Yosemite does boot ElCapitan, but then it crashes shortly thereafter on the desktop.
I don't have a Pro and neither many people here since this thread is primarily intended for non-Pro systems, so this advice is admittedly uninformed. Maybe try using one of @skyfly555 boot.efi from method3? Just an educated guess though.
Also please see my comment in post #966 about overwriting/copying kext. You need to be sure you actually replace the old ones. Sometimes it fails to overwrite depending how you try to do it.
Last edited:
So I will try again.
Regarding kexts, there is an AppleHDA.kext in EC-Base-kexts directory and one in EC-GMA950-kexts directory. Which one should I copy ? Both ? Is there a particular order to do so ?
Thank you.
[doublepost=1505935908][/doublepost]
I have noticed that the command "chown -R root:wheel" does nothing. To actually change file owner I have untick the option "Ignore ownership on this volume" (Right click on volume > Read info > Option below permissions)
Depending on your actual configuration, some of the commands may not succeed. You have to verify every step along the way. Thanks for your suggested solution.
Regarding AppleHDA.kext they are just duplicates. Check the files and they are same. I asked this exact same question in post #944. @skyfly555 answered it in post #946.
I searched this thread for "MacBook4" but it would seem all of the posts are just of failures or partial failures.
I didn't scour every single post individually. Has anyone been able to get an problem-free install of El Capitan on MacBook4,1?
In the meantime, I've retired the MacBook4,1. I've replaced it with a MacBook5,1 and installed Higher Sierra on it (which is super easy BTW), but it'd be nice to be able to get El Capitan on the MacBook4,1 too.
I didn't scour every single post individually. Has anyone been able to get an problem-free install of El Capitan on MacBook4,1?
In the meantime, I've retired the MacBook4,1. I've replaced it with a MacBook5,1 and installed Higher Sierra on it (which is super easy BTW), but it'd be nice to be able to get El Capitan on the MacBook4,1 too.
I got it to work on my 4,1. I used my 2009 Macbook Pro to install El Cap onto the drive, then hooked it up to my Mac Pro (which is a 2,1 running El Cap unsupported) to do all of the command line fu and file moving. I initially had trouble with getting it to boot from refind, but I downloaded the refind usb image, installed it to usb and booted from it, removed SIP, booted my el cap install, and found firmware.scap in the standalone/i386 directory and the APPLE directory had returned in the EFI partition. I deleted these, reblessed the refind x64 efi, rebuilt the kext cache, and everything works. Now I just need to figure out why my graphics memory only reports 6mb, but that's a kext issue I'm sure I can fix after I get some sleep...
EDIT: Doh! I installed the x1300 kexts by mistake. Installing the x3100 kexts, changing their permissions to root:wheel, and rebuilding the kext cache fixed the video problem.
As far as how it runs... pretty darn good. Some choppiness, but it's reasonable. DVD Player and Maps don't work, but there are other apps (VLC, Google Maps, Movist) that can take their place. 720p videos play fine on YouTube; 720p60 videos are choppy. Grid stack view is really slow, so I changed it to List view instead. Launchpad is decent and not too slow; just a bit choppy. No transparency anywhere. cDock2 can be used to theme the dock to not be blasting white. And of course, brightness controls and wake from sleep don't work. Shady can be used for brightness controlling, and NoSleep can be used to keep the Macbook from sleeping, but you'll have to shut it down if you want to be mobile. Overall, it runs better than Yosemite did on this Macbook.
Now, to get it to work on my 3,1...
EDIT: With a quick disk clone and some editing to boot 32-bit EFI and GMA950 kexts, it's now also running on my 2,1 Blackbook (see photo)...
EDIT #3: ... and now on my 3,1. That's all of them!
Attachments
Last edited:
Finally it is working on a Macmini2,1 (Intel Core2Duo 1,83 Ghz / 2Go RAM / GMA950)
I will also try on my MacBook 2,1, there is no reason (same proc, same graphic card, better freq (2Ghz), more RAM, SSHD)