OS X El Capitan on Unsupported Macs

[TMRJIJ]

Yes, I'm still alive. Heartbroken from my gf leaving me, but still alive.
OSXH site is currently under backend construction but downloads should be unaffected. I am going to try to brush off this dust on OSXE with a small update (1.31.1). It is available now in post 1 and only really applies to Mavericks users.
I haven't got in contact with MLforAll about his scripts, MCPF 2.0, and Bootloader builds since Exams so I am just going to test mine. I can finally compile my own solutions without Build errors so more builds are to come.

EFI32 Bootloader with System Integrity Protection disabled by default
(iMac, Mac Mini, Mac Pro testing only)
Build 1 (Tested: Not Working - 11 reports)
Build 2 (Tested: Working - 19 reports)

rename this file to 'boot.efi' and follow post 1 guide to replace this in the OS X Installer. Developers are to test to make sure they are able to boot to the installer or system successfully with SIP disabled by default in NVRAM.

Remember all credits go the Pike everything else this build does.

 

[Riwam]

Yes, I'm still alive. Heartbroken from my gf leaving me, but still alive.
OSXH site is currently under backend construction but downloads should be unaffected. I am going to try to brush off this dust on OSXE with a small update (1.31.1). It is available now in post 1 and only really applies to Mavericks users.
I haven't got in contact with MLforAll about his scripts, MCPF 2.0, and Bootloader builds since Exams so I am just going to test mine. I can finally compile my own solutions without Build errors so more builds are to come.

EFI32 Bootloader with System Integrity Protection disabled by default
(iMac, Mac Mini, Mac Pro testing only)
Build 1 (Tested: Not Working - 6 reports)
Build 2 (Tested: Working - 3 reports)

rename this file to 'boot.efi' and follow post 1 guide to replace this in the OS X Installer. Developers are to test to make sure they are able to boot to the installer or system successfully with SIP disabled by default in NVRAM.

Remember all credits go the Pike everything else this build does.

***********
I am sorry about your feelings.
In my faith we believe that before a child is born a decision is made by the Highest as to who will be the companion in life for that child when grown up.
The right companion.
At least in my own life it took much time... but I finally found her.
That gf might not have been the right one to make your whole life a happy one. Who can know it for sure in advance?
Have confidence that the right one will soon come to your life and cheer up!

Thank you for your update concerning tools for unsupported macs.
However I do not quite seize what is going to happen to MCPF or to what you will make to improve/replace it.
The Extractor proved to be a too risky way for my old MB 4.1.
It made a mess of it (or I made it...) and I don't dare try it again.
My hope is therefore of an improved "MCPF" or whatever the name of such a foolproof tool might be.
Thank you in advance for a more detailed info!
Ed

 

[danwelsh]

Hi guys, could someone tell me if theres a fix for touchpad and keyboard to get working for a macbook 4.1, I'm trying to install El Capitan on my sisters Macbook and got to the installer screen but no mouse or kb

 

[Zacharybinx34]

Yes, I'm still alive. Heartbroken from my gf leaving me, but still alive.
OSXH site is currently under backend construction but downloads should be unaffected. I am going to try to brush off this dust on OSXE with a small update (1.31.1). It is available now in post 1 and only really applies to Mavericks users.
I haven't got in contact with MLforAll about his scripts, MCPF 2.0, and Bootloader builds since Exams so I am just going to test mine. I can finally compile my own solutions without Build errors so more builds are to come.

EFI32 Bootloader with System Integrity Protection disabled by default
(iMac, Mac Mini, Mac Pro testing only)
Build 1 (Tested: Not Working - 6 reports)
Build 2 (Tested: Working - 3 reports)

rename this file to 'boot.efi' and follow post 1 guide to replace this in the OS X Installer. Developers are to test to make sure they are able to boot to the installer or system successfully with SIP disabled by default in NVRAM.

Remember all credits go the Pike everything else this build does.

So I have a macbook a1181 (MacBook "Core 2 Duo" 2.4 13" (Black-08)
I have mountain lion installed from the old mlpostfactor. Will this work to install OS X El Capitan?

Sorry if this is a noob question.

I'm trying to figure out if I should wait for this/try this, or just go with Windows 10 since I'll have Graphics acceleration, etc.

Thanks!

 

[RV-ABZ]

Nope, MLPF was only for Mountain Lion (hence the name) to run ML in 32bit kernel mode and use older 32bit graphics kexts (among other things) to retain full QE/CI. 'afraid you can't use MLPF for anything else.

There is no support for graphics acceleration for obsolete Intel GMA chips such as GMA950 and/or GMA X3100. I'm pretty sure this applies to Windows 10 too (I don't think there are drivers for this kind of old drivers beyond Win7), but don't quote me on that...

 

[Zacharybinx34]

Nope, MLPF was only for Mountain Lion (hence the name) to run ML in 32bit kernel mode and use older 32bit graphics kexts (among other things) to retain full QE/CI. 'afraid you can't use MLPF for anything else.

There is no support for graphics acceleration for obsolete Intel GMA chips such as GMA950 and/or GMA X3100. I'm pretty sure this applies to Windows 10 too (I don't think there are drivers for this kind of old drivers beyond Win7), but don't quote me on that...

Then why does the original post say,
"-MacBook4,x (TMRJIJ testing Kexts - working on Kernel Exploit / kextcache error)"

 

[TMRJIJ]

Nope, MLPF was only for Mountain Lion (hence the name) to run ML in 32bit kernel mode and use older 32bit graphics kexts (among other things) to retain full QE/CI. 'afraid you can't use MLPF for anything else.

There is no support for graphics acceleration for obsolete Intel GMA chips such as GMA950 and/or GMA X3100. I'm pretty sure this applies to Windows 10 too (I don't think there are drivers for this kind of old drivers beyond Win7), but don't quote me on that...

Then why does the original post say,
"-MacBook4,x (TMRJIJ testing Kexts - working on Kernel Exploit / kextcache error)"

So I have a macbook a1181 (MacBook "Core 2 Duo" 2.4 13" (Black-08)
I have mountain lion installed from the old mlpostfactor. Will this work to install OS X El Capitan?

Sorry if this is a noob question.

I'm trying to figure out if I should wait for this/try this, or just go with Windows 10 since I'll have Graphics acceleration, etc.

Thanks!

MLPostFactor is only for Mountain Lion.
MacPostFactor 1.0.1 works with OS X Mountain Lion, Mavericks and Yosemite.
El Capitan Support for both MacPostFactor and OS X Extractor is still in development due to KernelCache issues with the modified USB Kexts (available in OS X Extractor 1.31 or later) and compiling issue with the 64bit EFI Bootloaders.

You will not get Graphics Acceleration regardless after OS X Mountain Lion. We still haven't figured it out yet. The OpenGL Frameworks (in OS X Extractor 1.2 or later; MacPostFactor 1.0 or later) work well when Graphics Acceleration turned off only. When on, your Mac will experience a WindowServer crash immediately upon loading the login screen. This will likely require complete recoding of the Kernel.
I haven't tested Windows 10 BootCamp on all unsupported Hardware yet but if Windows 8 worked fine which it did actually. Windows 10 may work as well.

 

[atvusr]

EFI32 Bootloader with System Integrity Protection disabled by default
(iMac, Mac Mini, Mac Pro testing only)
Build 1 (Tested: Not Working - 11 reports)
Build 2 (Tested: Working - 19 reports)

Yes, Build 2 works (Build 1 not) on a MBP2,2 too - SIP is disabled and I can rename/replace Kexts although the bootline below 'bootargs =' says 'System Integrity Protection is engaged'.

But it's not quite reliable - the Boot.efi sometimes doesn't load the Kernel if the System/Library/Extensions folder was modified (gets stuck with a underscore). Furthermore very often Kernel Panics or sudden restarts, but this happens with Pike's original Boot.efi too. It's a transferred OSX 10.11.2, installed on a SSD connected to a supported Mac via FireWire, then only both Boot.efi replaced and connected via FireWire to the MBP2,2.

The USB-Inject-All Kext seems to be a solution for the USB issue. I got the internal Input-devices working too on the MBP2,2 - but due to the Kernel Panics / sudden restarts only for a short moment as described in Post #349.

 

[Riwam]

MLPostFactor is only for Mountain Lion.
MacPostFactor 1.0.1 works with OS X Mountain Lion, Mavericks and Yosemite.
El Capitan Support for both MacPostFactor and OS X Extractor is still in development due to KernelCache issues with the modified USB Kexts (available in OS X Extractor 1.31 or later) and compiling issue with the 64bit EFI Bootloaders.

You will not get Graphics Acceleration regardless after OS X Mountain Lion. We still haven't figured it out yet. The OpenGL Frameworks (in OS X Extractor 1.2 or later; MacPostFactor 1.0 or later) work well when Graphics Acceleration turned off only. When on, your Mac will experience a WindowServer crash immediately upon loading the login screen. This will likely require complete recoding of the Kernel.
I haven't tested Windows 10 BootCamp on all unsupported Hardware yet but if Windows 8 worked fine which it did actually. Windows 10 may work as well.

*******
Again thank you very much for all your efforts.
In advance have a very happy 2016 with a very successful relationship life.
We are all very grateful for what you did, do and will continue to do to help us to use old hardware.
Ed

 

[PythonFreak12]

I've managed to partially decompile the GMAX3100 kexts. If anyone needs the files, skype me at myallsocial and I will give them. I tried to skype TMRJIJ but he didn't respond. If any coder wants the files to give reverse engineering them a shot, skype me.

If we can reconstruct these kexts with the pseudocode that I currently have into working, compilable kexts we might achieve QE/CI on GMA965 and 950 cards. It will take a lot of effort but it is doable. We might as well take examples from Linux drivers as reference to fill in the gaps in the pseudocode.

A limitation could be that El Capitan and Yosemite do not support OpenGL 2.1 but maybe we can achieve something.

Proof:

 

[Riwam]

I've managed to partially decompile the GMAX3100 kexts. If anyone needs the files, skype me at myallsocial and I will give them. I tried to skype TMRJIJ but he didn't respond.

**********
Hello PhytonFreak12
Thank you very much for your efforts and hurrah for your achievements.
Please be so kind to insist again and again to contact TMRJIJ until you finally get in touch with him.
He seems to be the only one developer who still tries to solve this matter in a systematic and continuous way while others, who were at work in the past, have presently unfortunately "disappeared".
Maybe he might be non reachable because of the end of the year/new year turmoil.
However please continue to try to reach him until you succeed.
Thank you very much again and have a very happy 2016.
Ed

 

[PythonFreak12]

**********
Hello PhytonFreak12
Thank you very much for your efforts and hurrah for your achievements.
Please be so kind to insist again and again to contact TMRJIJ until you finally get in touch with him.
He seems to be the only one developer who still tries to solve this matter in a systematic and continuous way while others, who were at work in the past, have presently unfortunately "disappeared".
Maybe he might be non reachable because of the end of the year/new year turmoil.
However please continue to try to reach him until you succeed.
Thank you very much again and have a very happy 2016.
Ed

I have managed to contact TMRJIJ and we're working with this. I decompiled all the GMAX3100 kexts and I believe we can decompile the GMA950 kexts too.

 

[Riwam]

I have managed to contact TMRJIJ and we're working with this. I decompiled all the GMAX3100 kexts and I believe we can decompile the GMA950 kexts too.

*****
My compliments!
Thank you very much.
That gives me renewed hope regarding my old MacBook 4.1 with 3100 Graphics.
Thank you again and a happy New Year!
Ed

 

[Sventroy]

*****
My compliments!
Thank you very much.
That gives me renewed hope regarding my old MacBook 4.1 with 3100 Graphics.
Thank you again and a happy New Year!
Ed

I am anxiously awaiting this as well. My MB 4,1 is staring me in the face hoping to get El Capitan.
Anyone else hack a 4,1 and have a best case suggestion for now?

 

[Riwam]

I am anxiously awaiting this as well. My MB 4,1 is staring me in the face hoping to get El Capitan.
Anyone else hack a 4,1 and have a best case suggestion for now?

*******
They say that hope is the last thing one loses.
I very much hope that our talented creators of wonderful tools make it possible soon.
My MB 4.1 stares me no less than yours.
However...it is much worse when my faithful dog stares at me...
Then it means I must take it out in the cold and rain...
From both kinds of staring...at least the MB 4.1 let's me keep warm
Ed

 

[whathemac]

Hi community, any chance that someone could point me to an easy way to upgrade my unsupported Mac Pro 2,1 Yosemite to El-Capitan ? Just recently finished my final installation steps for Yosemite, and all the software i need, so i am really very reluctant to start from scratch again, installing and updating all the stuff i have....

Would be really happy if there would be a simple way to update the current installation...

Thanks,
L.

 

[atvusr]

Hi community, any chance that someone could point me to an easy way to upgrade my unsupported Mac Pro 2,1 Yosemite to El-Capitan ?

Have a look into the Mac-Pro-Thread: https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2-1-and-os-x-el-capitan.1890435/ .

 

[Riwam]

MLPostFactor is only for Mountain Lion.
MacPostFactor 1.0.1 works with OS X Mountain Lion, Mavericks and Yosemite.
El Capitan Support for both MacPostFactor and OS X Extractor is still in development due to KernelCache issues with the modified USB Kexts (available in OS X Extractor 1.31 or later) and compiling issue with the 64bit EFI Bootloaders.

You will not get Graphics Acceleration regardless after OS X Mountain Lion. We still haven't figured it out yet. The OpenGL Frameworks (in OS X Extractor 1.2 or later; MacPostFactor 1.0 or later) work well when Graphics Acceleration turned off only. When on, your Mac will experience a WindowServer crash immediately upon loading the login screen. This will likely require complete recoding of the Kernel.
I haven't tested Windows 10 BootCamp on all unsupported Hardware yet but if Windows 8 worked fine which it did actually. Windows 10 may work as well.

******
Hello TMRJIJ
Hope you are fine.
Haven't heard anything about your development for quite a while.
Is "no news, good news" valid for this matter... or the opposite?
Thank you in advance for your feed back.
All the best to you!
Ed

 

[brunop]

Hello,
I'm trying to install ElCap on late 2006 imac. (5,1)

I managed to boot on the installer partition, but the mouse and the keyboard are not working.
It seems that other people have the same problem.

I installed USBInjectAll.kext in the installer /S/L/E with kextwizard, but now the installer partition does not even boot anymore (in verbose mode, I just have a dash on the screen and it doesn't go further)

What should I do to boot the installer with USB?

I tried:
pikeralpha boot.efi (md5= 036476dc081da904f50736eb56acbcfa)
and also TMRJIJ's latest boot.efi (TMRJIJ-32bootB2.efi, md5=23348e2baff575405f527cf0a26e2838) with the same result.

By the way, I have 2 other questions:
- I don't understand what I have to do with /S/L/CoreServices/bootbase.efi. Should it be a copy of 32bit boot.efi ? Should I remove it ?

- when the boot does not even start (blocked on the dash in verbose mode) what does it mean? Did the boot.efi started being executed ?
[doublepost=1452635389][/doublepost]I just tried editing Info.plist inside USBInjectAll.kext by adding a configuration for iMac5,1 inside
but it is not working better.
Still can't boot the installer with USB support.

 

[TMRJIJ]

******
Hello TMRJIJ
Hope you are fine.
Haven't heard anything about your development for quite a while.
Is "no news, good news" valid for this matter... or the opposite?
Thank you in advance for your feed back.
All the best to you!
Ed

Not so much. I don't really want to upload a beta that doesn't work at all.

Current progress:
Working on 64bit Bootloader with Rootless off.
OS X Patcher right now creates the installer partition perfectly but ends up with "already installed on this Mac" error.

I'm working git repositories for each project to work on with developers. I can't keep creating hundreds of builds for every little change. Everyone's scripts are counteracting each other's. Version Control is needed now.

 

[renaissance18]

im trying 2 install the os x extractor 1.31 but the el captian is grey out, i put the app in the app folder still the same

 

[Fred57]

Hello,

I installed USBInjectAll.kext in the installer /S/L/E with kextwizard, but now the installer partition does not even boot anymore (in verbose mode, I just have a dash on the screen and it doesn't go further)
(...)
Still can't boot the installer with USB support.

Try and reset your PRAM (Command, Option, P & R keys at boot). it should allow your Mac to boot again.

If we could have a mapping of the USB ports used in El Capitan thanks to something like IOJones (?), it would allow us to inject only the needed ports for KB & Mouse thanks to USBInjectAll for the time being. Rehabman has developed exclusions that can be added to com.apple.boot

For a Mac mini 2,1, as far as I know, only MacVidCards could help us as he has a running mac under EC. For other Macs, TMRJIJ ?

My guess is USBInjectAll injects too much & that leads to the reboot.

I am not 100% sure of the above though, of course

 

[Riwam]

Not so much. I don't really want to upload a beta that doesn't work at all.

Current progress:
Working on 64bit Bootloader with Rootless off.
OS X Patcher right now creates the installer partition perfectly but ends up with "already installed on this Mac" error.

I'm working git repositories for each project to work on with developers. I can't keep creating hundreds of builds for every little change. Everyone's scripts are counteracting each other's. Version Control is needed now.

*********
TO TMRJIJ (sorry for the somehow merged posts I don't know why!)
Thank you very much for your info, Isiah!

Kindly allow me to put one question in two parts:
Let's leave for a moment aside a tool allowing to get to successfully install El Capitan in natively unsupported Macs, which, as you write, you haven't still managed to create,
1) is with your present "work" possible to install Yosemite (in unsupported Macs) with a somehow "better" result than with MCPF 1.01 ?
2) is with your present "work" possible to install Mavericks (again in unsupported Macs) with a somehow "better" result than with MCPF 1.01 ?
If one of those questions gets a "yes", I would be very much interested in it, even if El Capitan is yet not possible (and I believe many others owners of old Macs might be as well).
Thank you very much in advance for answering!
Ed
===========================================================
===========================================================
[doublepost=1452695107][/doublepost]

im trying 2 install the os x extractor 1.31 but the el captian is grey out, i put the app in the app folder still the same

******
(SORRY FOR THE MERGED POSTS!)
TO RENAISSANCE18

Unfortunately my answer is no help for you...but just for info purposes.
When I tried several times the other tool MCPF 1.0.1 in an old unsupported MacBook 4.1...even Yosemite (which should be possible according to the info of that tool) was always grayed out.
I now believe that Mac models have "ways" to show their "willingness" or "capabilities"...although of course I have not the slightest idea how this happens.
Ed

 

[Fred57]

*********

1) is with your present "work" possible to install Yosemite (in unsupported Macs) with a somehow "better" result than with MCPF 1.01 ?

You can try SFOTT. Pretty straightforward to get Yosemite working.

 

[renaissance18]

*********
TO TMRJIJ (sorry for the somehow merged posts I don't know why!)
Thank you very much for your info, Isiah!

Kindly allow me to put one question in two parts:
Let's leave for a moment aside a tool allowing to get to successfully install El Capitan in natively unsupported Macs, which, as you write, you haven't still managed to create,
1) is with your present "work" possible to install Yosemite (in unsupported Macs) with a somehow "better" result than with MCPF 1.01 ?
2) is with your present "work" possible to install Mavericks (again in unsupported Macs) with a somehow "better" result than with MCPF 1.01 ?
If one of those questions gets a "yes", I would be very much interested in it, even if El Capitan is yet not possible (and I believe many others owners of old Macs might be as well).
Thank you very much in advance for answering!
Ed
===========================================================
===========================================================
[doublepost=1452695107][/doublepost]
******
(SORRY FOR THE MERGED POSTS!)
TO RENAISSANCE18

Unfortunately my answer is no help for you...but just for info purposes.
When I tried several times the other tool MCPF 1.0.1 in an old unsupported MacBook 4.1...even Yosemite (which should be possible according to the info of that tool) was always grayed out.
I now believe that Mac models have "ways" to show their "willingness" or "capabilities"...although of course I have not the slightest idea how this happens.
Ed

[doublepost=1452695749][/doublepost]ok thnks 4 the info Riwam