Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Houpla

macrumors member
Jan 1, 2018
73
94
Success!

Got it working on Mac Mini 1,1 flashed to 2,1 and CPU upgraded:

Screen_Shot_El_Cap.png

Tried every combination of El Capitan updates and for some reason if I apply "Security Update 2018-004", the resulting system can't be hacked to run Mac Mini, tried several times (acts like I described in the previous post). All other updates worked fine, so updated an external disk attached to an El Capitan compatible Mac to 10.11.6, Safari 11.1.2 etc, then applied method 3, cloned to Mac Mini's internal disk and it works!

Speed is acceptable, lightweight apps fork fine, heavy webpages are laggy, but at least they work, on 10.6.8 I got "connection refused" from github, my bank and many other websites.

Youtube videos work up to 720p, if I go higher than that, frames start to drop.
 

TMRJIJ

macrumors 68040
Original poster
Dec 12, 2011
3,530
6,713
South Carolina, United States
macOS Extractor v1.44
An update to the macOS Extractor was released on May 29, 2019.

A macOSE update is recommended to assist you in installing macOS Sierra, El Capitan, Yosemite, Mavericks, and Mountain Lion on your old Mac. Also, by updating the patching software on your Mac, you can enjoy various additional features and enhanced security. Always use to the latest version.
Never download this from any other provider. All links must link to this page or directly from our server. This is to ensure that nothing was tampered with and that you have the most reliable and tested software.

This update includes:
◦ Small Update to El Capitan and Sierra Specific Kexts
◦ Addressed Issue where AutoPatch would download El Capitan Kexts for Sierra
◦ Added Prelinked Kernels for macOS Sierra Patching
◦ Fixed missing El Capitan Prelinked Kernel that could result in AutoPatch Installation Failure
◦ New SIP Manager Kext added


Other Features in Previous Versions:
◦ Performance and Stability Improvements to the Installer
◦ Graphical Kext Installers now remove Unsupported Screen Savers
◦ El Captain and Sierra Patches now include SIP Check Detection
◦ Maintenance script now compresses Dock app resources
◦ [dev] AutoPatch main script now includes variables for each OS and steps required
◦ [dev] Graphical Kexts Web Installers now addresses changes in version control
◦ Address differences between Mountain Lion and other OSs’ BaseSystem
◦ Hides Framework error from installer logs (Not Important)
◦ Address Issue that would cause Mountain Lion Patching to fail due to file name errors.
◦ Adds an PostInst script within the AutoPatch that can be addressed through the Installer’s terminal
◦ Graphical Kexts are automatically downloaded to the Installer for use during patching.
◦ AutoPatch now verifies that the Installer is ‘bless’ to boot.
◦ Maintenance Script is now fully executable and includes more optimizations.
◦ Address issue where Graphics Kext Installer fails even when the kexts are installed.
◦ Addresses Rich Text Formatting that causes some scripts to not finish
◦ Fixed issue where the Graphical Installer fails after clearing kernel cache
◦ Addresses issue where the AutoPatch refuses to complete all of its tasks within the Target Partition/Image
◦ Fixes issue where some scripts are in rich text formatting
◦ Replaces brightness app with a new app recommended by a member is the Yosemite thread.
◦ Smart OS detection
◦ Installer Logs now echo its current process to help diagnose where more issues may occur.




Web Installer Size: 4 MB
Download Size: 70 - 170 MB
The Installer reads and downloads needed patches from our servers. You must have at least 180 MB of space for installation

Prerequisites

Tested Macs listed below. Here are the minimum requirements:

- Running 10.7 Lion
- At least 2GB of RAM.
- A copy of Yosemite or Mavericks in Applications Folder (.app file preferred)
- 15 GB of free space from USB or HDD Partition.

-MacBook2,x
-MacBook3,x
-MacBook4,x
-MacBookPro2,x
-MacBookAir1,1
-MacMini1,x (C2D upgraded)
-MacMini2,x
-iMac4,x (C2D can be upgraded)
-iMac5,x


We DON'T assist with Hackintosh. All private messages/emails involving installing OS X on non-Apple hardware will be redirected to another support team.


How to Use It:
1. Download macOS Extractor
2. Install it. Choose a version of macOS/OS X to get the correct patches.
3. Open the AutoPatch in your Applications and view to corresponding guide for the OS you choose.

Download (Web Installer)
Download (Mega)
[doublepost=1559157371][/doublepost]Hey Guys, I'm alive.

If you are still having issues with the AutoPatch installation, please send me your full Installer Logs.
I'm going to spend the next month beta testing to fix these lingering issues and then see if I can get a few of these models up to Mojave.
 

Yojx21

macrumors member
Dec 26, 2017
50
24
Dijon, France
macOS Extractor v1.44
An update to the macOS Extractor was released on May 29, 2019.

A macOSE update is recommended to assist you in installing macOS Sierra, El Capitan, Yosemite, Mavericks, and Mountain Lion on your old Mac. Also, by updating the patching software on your Mac, you can enjoy various additional features and enhanced security. Always use to the latest version.
Never download this from any other provider. All links must link to this page or directly from our server. This is to ensure that nothing was tampered with and that you have the most reliable and tested software.

This update includes:
◦ Small Update to El Capitan and Sierra Specific Kexts
◦ Addressed Issue where AutoPatch would download El Capitan Kexts for Sierra
◦ Added Prelinked Kernels for macOS Sierra Patching
◦ Fixed missing El Capitan Prelinked Kernel that could result in AutoPatch Installation Failure
◦ New SIP Manager Kext added


Other Features in Previous Versions:
◦ Performance and Stability Improvements to the Installer
◦ Graphical Kext Installers now remove Unsupported Screen Savers
◦ El Captain and Sierra Patches now include SIP Check Detection
◦ Maintenance script now compresses Dock app resources
◦ [dev] AutoPatch main script now includes variables for each OS and steps required
◦ [dev] Graphical Kexts Web Installers now addresses changes in version control
◦ Address differences between Mountain Lion and other OSs’ BaseSystem
◦ Hides Framework error from installer logs (Not Important)
◦ Address Issue that would cause Mountain Lion Patching to fail due to file name errors.
◦ Adds an PostInst script within the AutoPatch that can be addressed through the Installer’s terminal
◦ Graphical Kexts are automatically downloaded to the Installer for use during patching.
◦ AutoPatch now verifies that the Installer is ‘bless’ to boot.
◦ Maintenance Script is now fully executable and includes more optimizations.
◦ Address issue where Graphics Kext Installer fails even when the kexts are installed.
◦ Addresses Rich Text Formatting that causes some scripts to not finish
◦ Fixed issue where the Graphical Installer fails after clearing kernel cache
◦ Addresses issue where the AutoPatch refuses to complete all of its tasks within the Target Partition/Image
◦ Fixes issue where some scripts are in rich text formatting
◦ Replaces brightness app with a new app recommended by a member is the Yosemite thread.
◦ Smart OS detection
◦ Installer Logs now echo its current process to help diagnose where more issues may occur.




Web Installer Size: 4 MB
Download Size: 70 - 170 MB
The Installer reads and downloads needed patches from our servers. You must have at least 180 MB of space for installation

Prerequisites

Tested Macs listed below. Here are the minimum requirements:

- Running 10.7 Lion
- At least 2GB of RAM.
- A copy of Yosemite or Mavericks in Applications Folder (.app file preferred)
- 15 GB of free space from USB or HDD Partition.

-MacBook2,x
-MacBook3,x
-MacBook4,x
-MacBookPro2,x
-MacBookAir1,1
-MacMini1,x (C2D upgraded)
-MacMini2,x
-iMac4,x (C2D can be upgraded)
-iMac5,x


We DON'T assist with Hackintosh. All private messages/emails involving installing OS X on non-Apple hardware will be redirected to another support team.


How to Use It:
1. Download macOS Extractor
2. Install it. Choose a version of macOS/OS X to get the correct patches.
3. Open the AutoPatch in your Applications and view to corresponding guide for the OS you choose.

Download (Web Installer)
Download (Mega)
[doublepost=1559157371][/doublepost]Hey Guys, I'm alive.

If you are still having issues with the AutoPatch installation, please send me your full Installer Logs.
I'm going to spend the next month beta testing to fix these lingering issues and then see if I can get a few of these models up to Mojave.
Nice thanks ! But we agree that these modei in the list can't go higher than El Capitan?
 

TMRJIJ

macrumors 68040
Original poster
Dec 12, 2011
3,530
6,713
South Carolina, United States
Nice thanks ! But we agree that these modei in the list can't go higher than El Capitan?
A Developer in the RMC team managed to get macOS Mojave running on a MacBook 4,1 with Input Devices functional to a certain extent (Limited Trackpad obviously). He made changes to our Kexts and got performance relatively close to Yosemite from the looks of it. To my knowledge, that may be the only model that has the ability to go that far but I will be sure to check after I fully fix this SIP hiccup. I just need to study his script and changes to determine if it's even worth the thought and hassle.
No doubt, my focus is on El Capitan and weeding out all the issues OSXE and MacPostFactor are facing.
 

TMRJIJ

macrumors 68040
Original poster
Dec 12, 2011
3,530
6,713
South Carolina, United States
Nice! Is there a way to upgrade to these modified kexts for those of us who installed El Capitan "manually" using method 3?
Since these Kexts are not contained in package installers, you would probably have to install them manually via Kext Utility or another partition. Of course, make sure you back up the originals if you encounter issues.
 
macOS Extractor v1.44
An update to the macOS Extractor was released on May 29, 2019.

A macOSE update is recommended to assist you in installing macOS Sierra, El Capitan, Yosemite, Mavericks, and Mountain Lion on your old Mac. Also, by updating the patching software on your Mac, you can enjoy various additional features and enhanced security. Always use to the latest version.
Never download this from any other provider. All links must link to this page or directly from our server. This is to ensure that nothing was tampered with and that you have the most reliable and tested software.

This update includes:
◦ Small Update to El Capitan and Sierra Specific Kexts
◦ Addressed Issue where AutoPatch would download El Capitan Kexts for Sierra
◦ Added Prelinked Kernels for macOS Sierra Patching
◦ Fixed missing El Capitan Prelinked Kernel that could result in AutoPatch Installation Failure
◦ New SIP Manager Kext added


Other Features in Previous Versions:
◦ Performance and Stability Improvements to the Installer
◦ Graphical Kext Installers now remove Unsupported Screen Savers
◦ El Captain and Sierra Patches now include SIP Check Detection
◦ Maintenance script now compresses Dock app resources
◦ [dev] AutoPatch main script now includes variables for each OS and steps required
◦ [dev] Graphical Kexts Web Installers now addresses changes in version control
◦ Address differences between Mountain Lion and other OSs’ BaseSystem
◦ Hides Framework error from installer logs (Not Important)
◦ Address Issue that would cause Mountain Lion Patching to fail due to file name errors.
◦ Adds an PostInst script within the AutoPatch that can be addressed through the Installer’s terminal
◦ Graphical Kexts are automatically downloaded to the Installer for use during patching.
◦ AutoPatch now verifies that the Installer is ‘bless’ to boot.
◦ Maintenance Script is now fully executable and includes more optimizations.
◦ Address issue where Graphics Kext Installer fails even when the kexts are installed.
◦ Addresses Rich Text Formatting that causes some scripts to not finish
◦ Fixed issue where the Graphical Installer fails after clearing kernel cache
◦ Addresses issue where the AutoPatch refuses to complete all of its tasks within the Target Partition/Image
◦ Fixes issue where some scripts are in rich text formatting
◦ Replaces brightness app with a new app recommended by a member is the Yosemite thread.
◦ Smart OS detection
◦ Installer Logs now echo its current process to help diagnose where more issues may occur.




Web Installer Size: 4 MB
Download Size: 70 - 170 MB
The Installer reads and downloads needed patches from our servers. You must have at least 180 MB of space for installation

Prerequisites

Tested Macs listed below. Here are the minimum requirements:

- Running 10.7 Lion
- At least 2GB of RAM.
- A copy of Yosemite or Mavericks in Applications Folder (.app file preferred)
- 15 GB of free space from USB or HDD Partition.

-MacBook2,x
-MacBook3,x
-MacBook4,x
-MacBookPro2,x
-MacBookAir1,1
-MacMini1,x (C2D upgraded)
-MacMini2,x
-iMac4,x (C2D can be upgraded)
-iMac5,x


We DON'T assist with Hackintosh. All private messages/emails involving installing OS X on non-Apple hardware will be redirected to another support team.


How to Use It:
1. Download macOS Extractor
2. Install it. Choose a version of macOS/OS X to get the correct patches.
3. Open the AutoPatch in your Applications and view to corresponding guide for the OS you choose.

Download (Web Installer)
Download (Mega)
[doublepost=1559157371][/doublepost]Hey Guys, I'm alive.

If you are still having issues with the AutoPatch installation, please send me your full Installer Logs.
I'm going to spend the next month beta testing to fix these lingering issues and then see if I can get a few of these models up to Mojave.


A couple of remarks:

  1. The pair of links here still point to 1.43, not 1.44.
  2. Based on @dosdude1’s past instruction guides, my understanding is MacBook4,1 models simply won’t work beyond 10.8.5 due to EFI-based constraints. Is this to say that running MacOS Extractor 1.44 on a MacBook4,1 (currently running a clean, new install of OS X 10.7.5 as a base), will enable the successful installation and boot of, say, Mavericks, Yosemite, El Capitan, and/or Sierra on said MacBook4,1? Or is there more to this which I have overlooked?
 

TMRJIJ

macrumors 68040
Original poster
Dec 12, 2011
3,530
6,713
South Carolina, United States
A couple of remarks:

  1. The pair of links here still point to 1.43, not 1.44.
  2. Based on @dosdude1’s past instruction guides, my understanding is MacBook4,1 models simply won’t work beyond 10.8.5 due to EFI-based constraints. Is this to say that running MacOS Extractor 1.44 on a MacBook4,1 (currently running a clean, new install of OS X 10.7.5 as a base), will enable the successful installation and boot of, say, Mavericks, Yosemite, El Capitan, and/or Sierra on said MacBook4,1? Or is there more to this which I have overlooked?

  1. Oof..I'll fix that tomorrow. The v1.43 Web Installer should still point to the updated packages though
  2. MacBook 4,1 can at least run up to El Capitan at this point (A developer managed to get it running Mojave). Dosdude1 and many of the other developers in the newer Unsupported Threads don't like the idea of 'Headless Macs': meaning these particular models don't have Full Graphics Acceleration (OpenGL support / 64bit) leading to graphical limitations, slower performance, no video playback in stock applications, and limited animations/transparency. Some models in the list do require modified Bootloaders since they are in 32bit EFI but thanks to Pike Alpha, we have them.
macOS Extractor and Method 3 in the Guide Post 1 will indeed help enable the successful installation of macOS 10.8-10.11.
If you are willing to deal with the lack of Graphics Acceleration on Mavericks and newer, you should be fine. Please keep up to date with this thread as El Capitan is a troublesome one due to certain kexts not playing nice.
 
  • Like
Reactions: B S Magnet

Sir Charles82

macrumors newbie
May 10, 2019
5
0
Vienna
Hey,

first of all, thank you for working on this program.

as stated above, I'm having troubles getting El Capitan to work on my modded iMac 4,1 (upgraded CPU, RAM, SSD, Firmware flash to iMac 5,1) but with 32bit EFI, nearly giving up. I will try with the new update soon, but do you think it's possible to get Capitan running on a modified iMac WITHOUT Method 3?

Thank you for your work!

Edit: so, I've tried the new version, got further as before (found boot.efi-Files in the folder, which weren't there with the last version) but rebooting from USB-drive won't work. Choosing booting from USB, grey apple logo with running circle appears, screen went black, went white and reboots into Lion.

Perhaps the mistake is, it is the last available El Capitan installer?
 
Last edited:

mshoestrng

macrumors newbie
Jun 10, 2019
1
1
Hi everyone,
I’m trying to install El Captain via MPF 2.0.1 on an iMac 5.1 with Mac OS 10.7.5.

After multiple tries I managed to create a clean-install-package for MPF/El Captain on my flash drive. When I boot from the USB the install starts just fine, but after 1/3 to 1/2 of the progress bar the computer reboots and then shows me the usual "OS X Utilities" install screen again with the four options: XY, „(re-)install Mac OS Lion“, „Help someting…“, Disk Utility.

When I reboot again I still only get to the install screen. When I reboot and choose the MPF-USB it just shows the apple logo on grey background and nothing seems to happen.

Sometimes after restarting multiple times and booting the MPF-USB, I get back into the MPF-Install menu. However, it seems the installation starts over again and again aborts through reboot after about 10 % progress.

Is there any install logs anywhere which I could check for clues? Or do you have any other hints for me?

In my setup MPF seems very unpredictive with varying results despite identical input?! So logs would be great to find out what's happening. Thanks!
 
  • Like
Reactions: Sir Charles82

Yojx21

macrumors member
Dec 26, 2017
50
24
Dijon, France
A Developer in the RMC team managed to get macOS Mojave running on a MacBook 4,1 with Input Devices functional to a certain extent (Limited Trackpad obviously). He made changes to our Kexts and got performance relatively close to Yosemite from the looks of it. To my knowledge, that may be the only model that has the ability to go that far but I will be sure to check after I fully fix this SIP hiccup. I just need to study his script and changes to determine if it's even worth the thought and hassle.
No doubt, my focus is on El Capitan and weeding out all the issues OSXE and MacPostFactor are facing.

If i am not mistaken, i was the first to ask on the unsupported mojave thread if we can run macOS Mojave on the MacBook4,1. ;)

This is the only model which can run higher OS than El Capitan because Sierra (and higher) request SSE4.2 and the other model don't have this instruction set. To have SSE4.2 you need at least a Penryn based core 2 duo which arrived on our macs in 2008.

If i check the list of compatible mac (with patches) for Mac OS X El Capitan, no any would have full QE/CI (except MacPro1,1 and Xserve1,1) ?

I know that i have already asked but do you know why iMac6,1 isn't in the list ? It's GPU is upgradable and can support full acceleration on el capitan.
 

TMRJIJ

macrumors 68040
Original poster
Dec 12, 2011
3,530
6,713
South Carolina, United States
If i am not mistaken, i was the first to ask on the unsupported mojave thread if we can run macOS Mojave on the MacBook4,1. ;)

This is the only model which can run higher OS than El Capitan because Sierra (and higher) request SSE4.2 and the other model don't have this instruction set. To have SSE4.2 you need at least a Penryn based core 2 duo which arrived on our macs in 2008.

If i check the list of compatible mac (with patches) for Mac OS X El Capitan, no any would have full QE/CI (except MacPro1,1 and Xserve1,1) ?

I know that i have already asked but do you know why iMac6,1 isn't in the list ? It's GPU is upgradable and can support full acceleration on el capitan.
If the GPU is upgraded to a Metal Supported Configuration then you can possibly use Dosdude1 Patcher to upgrade to Mojave
[doublepost=1561749513][/doublepost]macOS Extractor 1.45 is currently in production. macOS Extractor 1.45 Beta testing will start late July with Major Performance Changes, Bug Fixes, and maybe a surprise.
 

sebicologne

macrumors newbie
Jul 4, 2019
1
0
Hi there,

i´ve followed the instructions for patching with macOS X Extractor (latest version) and get stuck at Installation with this case:
"If the Installation Drive boots you back to the main partition, try blessing the drive from your terminal app:
Code:
sudo bless --folder /Volumes/[Installation Drive Name] --file /Volumes/[Installation Drive Name]/boot --setBoot"


I´ve tried the following command but get an error message.

sudo bless --folder /Volumes/OS\ X\ Base\ System\ 1 --file /Volumes/OS\ X\ Base\ System\ 1/boot --setBoot
Error while getting file ID of /Volumes/OS X Base System 1/boot. Ignoring…


Does anybody knows, what i´am doing wrong?

Many thanks!

Best
Sebastian
 

ils4nt0

macrumors newbie
Oct 29, 2018
17
0
Success!

Got it working on Mac Mini 1,1 flashed to 2,1 and CPU upgraded:

View attachment 839435
Tried every combination of El Capitan updates and for some reason if I apply "Security Update 2018-004", the resulting system can't be hacked to run Mac Mini, tried several times (acts like I described in the previous post). All other updates worked fine, so updated an external disk attached to an El Capitan compatible Mac to 10.11.6, Safari 11.1.2 etc, then applied method 3, cloned to Mac Mini's internal disk and it works!

Speed is acceptable, lightweight apps fork fine, heavy webpages are laggy, but at least they work, on 10.6.8 I got "connection refused" from github, my bank and many other websites.

Youtube videos work up to 720p, if I go higher than that, frames start to drop.

Hi dear, I have had a similar problem for months... with a MB 2,1... I've used the 3th method and I'm stucked on the loading desktop with the coloured wheel. I think the extension instruction are non perfectly clear. Can you explain what you have done?
any kind of suggestion is well appreciated

ps: i've installed on a clean external drive from a mb 5,1 a 10.11.6, patched with efi no sip and basi kext plus intel 950.
 

steinbeq

macrumors newbie
Jul 8, 2019
17
6
UK
Hi All,

Method 3 still works well on a MB2.1 but not with the latest installer. The latest version of the 10.11.6 installer looks as though it has CPU instructions which the MB2.1 doesn't understand. I tried a 10.11.1 installer and was able to get 2006 MB running El Capitan. Was quite a bit of back and forth between a supported mac and the MB2.1 but works pretty well. Things to note:

10.11.1 installer is now quite old so you have to set your system clock to something like Jan 2016 for it to run.

USB kexts had to be quite close in date to the installer ( I found some from 2016 ).

Pretty much everything else is in accordance with method 3.

If anyone is interested in more specific details let me know.

Cheers

S
 
  • Like
Reactions: pippox0 and ils4nt0

Gregorex

macrumors newbie
Jun 26, 2019
3
0
Hi All,

Method 3 still works well on a MB2.1 but not with the latest installer. The latest version of the 10.11.6 installer looks as though it has CPU instructions which the MB2.1 doesn't understand. I tried a 10.11.1 installer and was able to get 2006 MB running El Capitan. Was quite a bit of back and forth between a supported mac and the MB2.1 but works pretty well. Things to note:

10.11.1 installer is now quite old so you have to set your system clock to something like Jan 2016 for it to run.

USB kexts had to be quite close in date to the installer ( I found some from 2016 ).

Pretty much everything else is in accordance with method 3.

If anyone is interested in more specific details let me know.

Cheers

S



Hello,

I'm very interested on this, I Have a macbook 2.1 late 2006 and I've been trying to get el capitan run on this laptop, I'm stuck currently on the step 10 of the guide method #3 , I'm having this issue below

upload_2019-7-9_11-28-54.png


if someone can help me or explain me how to get this work I Will appreciate, I'm a new on mac and I'm trying to get the capitan works, so if someone can explain me as dummies like the guide of method #3 I Will appreciate. Thanks for this amazing blog of collaboration and help across Mac OS Environments!

Regards from Costa Rica!

Greg.
 

Gregorex

macrumors newbie
Jun 26, 2019
3
0
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


Hello there,

Just to let you know, this link :https://www.dropbox.com/s/oqtz4ozluwb6xx5/all-kexts.zip?dl=1. is not working at this date.
 

steinbeq

macrumors newbie
Jul 8, 2019
17
6
UK
Hey @Gregorex ,

I think you need SIP disabled to be able to run kextcache.

To disable SIP you need to boot into recovery ( on your supported machine ) and then run this from a terminal:

csrutil disable

Some useful kexts are available here.

Cheers

S
 

ils4nt0

macrumors newbie
Oct 29, 2018
17
0
Hi All,

Method 3 still works well on a MB2.1 but not with the latest installer. The latest version of the 10.11.6 installer looks as though it has CPU instructions which the MB2.1 doesn't understand. I tried a 10.11.1 installer and was able to get 2006 MB running El Capitan. Was quite a bit of back and forth between a supported mac and the MB2.1 but works pretty well. Things to note:

10.11.1 installer is now quite old so you have to set your system clock to something like Jan 2016 for it to run.

USB kexts had to be quite close in date to the installer ( I found some from 2016 ).

Pretty much everything else is in accordance with method 3.

If anyone is interested in more specific details let me know.

Cheers

S
Do you share Kexts working?
 

steinbeq

macrumors newbie
Jul 8, 2019
17
6
UK
Yes I'm using the once in here.

In fact here are my 'Extensions' folders ( /System/Library/Extensions ):

32 bit EFI kexts:

https://drive.google.com/file/d/1gZRpJ6tLMi7zaxMFsnmvY-Kt3NIHXDTs/view?usp=sharing

64 bit EFI kexts:

https://drive.google.com/file/d/1M_dwYnGPxfCW4cUgExyD5X1Ca-MgMYwu/view?usp=sharing

On your machine:

cd /System/Library
mv Extensions Extensions.backup
tar -zxf <path to Extensions.32.tar.gz or Extensions.64.tar.gz

You might need to rebuild the kext cache which is already documented in this thread.

To turn off SIP I used MCPF to create an installation partition and then ran the terminal from the installer.
The installer won't actually install El Capitan but it's very useful for turning off SIP on an EFI 64 unsupported
mac.

So now I have El Capitan on both a macbook 2.1 and also a 4.1

Cheers

S
 

ils4nt0

macrumors newbie
Oct 29, 2018
17
0
In fact here are my 'Extensions' folders ( /System/Library/Extensions ):

32 bit EFI kexts:

https://drive.google.com/file/d/1gZRpJ6tLMi7zaxMFsnmvY-Kt3NIHXDTs/view?usp=sharing

64 bit EFI kexts:

https://drive.google.com/file/d/1M_dwYnGPxfCW4cUgExyD5X1Ca-MgMYwu/view?usp=sharing

On your machine:

cd /System/Library
mv Extensions Extensions.backup
tar -zxf <path to Extensions.32.tar.gz or Extensions.64.tar.gz

You might need to rebuild the kext cache which is already documented in this thread.

To turn off SIP I used MCPF to create an installation partition and then ran the terminal from the installer.
The installer won't actually install El Capitan but it's very useful for turning off SIP on an EFI 64 unsupported
mac.

So now I have El Capitan on both a macbook 2.1 and also a 4.1

Cheers

S
Thank you, tonight I hope to have fun!!!
 

steinbeq

macrumors newbie
Jul 8, 2019
17
6
UK
Thank you, tonight I hope to have fun!!!

If MCPF installer doesn't help with disabling SIP try and boot the installer in single user mode ( CMD+S while booting ). Then you just get a terminal screen and can run 'csruril disable' there and then 'reboot'. I tried it out the other day and had to use single user mode. Goodness knows how I managed to get a terminal via the MCPF installer. csrutil changes nvram so no need to mount files system or anything I don't think.
 

ils4nt0

macrumors newbie
Oct 29, 2018
17
0
If MCPF installer doesn't help with disabling SIP try and boot the installer in single user mode ( CMD+S while booting ). Then you just get a terminal screen and can run 'csruril disable' there and then 'reboot'. I tried it out the other day and had to use single user mode. Goodness knows how I managed to get a terminal via the MCPF installer. csrutil changes nvram so no need to mount files system or anything I don't think.
After installing a fresh el cap on a supported MacBook 5,1 i reboot on recovery for disabiliting the sip. After this i put the efi 32 boot with sip disable (from guide mod 3). all ok since after the kernel injection (I've not tried with yours yet) the Black MacBook 2.1 boots at the desktop and show me the coloured wheely and stop loading to the login user.
I'll try soon. thank's for the interest in this strange case.
18/07... nope to login on desktop. WTF???
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.