OS X El Capitan on Unsupported Macs

[garirry]

Okay, I reached step 16 and I'm confused as heck.

Where do I get the kernel folder? I tried installing the latest version of OS X Hackers you provided, and all it gave me is some kexts and a software that tells me to go read the manual when I open it. It also wouldn't let me select which OS I want to install on the supported Mac during the customisation section of the install, except 10.8, but doing that will result in an installation failed. Also, for some reason, I get this NoSleep warning saying a kernel is missing at the end of each install.

Any help?

 

[atvusr]

Where do I get the kernel folder?

You can find the Kernel also in the OSX 10.11 Installer files, see Post #219.

 

[Riwam]

I'm currently trying to do this on my MacBook Early 2008 just for fun.

Any chance you'll update MacPostFactor to support El Capitan?

*********
Hello garirry
If you are using MCPF 1.0.1, does the installation front page offers you (in the 3 "circles") Yosemite on the right?
In my Early 2008 MB Yosemite is transparent-grayed-out and only Mavericks in the middle and Mountain Lion on the right are offered as possible.
I wonder why.
Thanks for your info.
Regards
Ed

 

[TMRJIJ]

*********
Hello garirry
If you are using MCPF 1.0.1, does the installation front page offers you (in the 3 "circles") Yosemite on the right?
In my Early 2008 MB Yosemite is transparent-grayed-out and only Mavericks in the middle and Mountain Lion on the right are offered as possible.
I wonder why.
Thanks for your info.
Regards
Ed

Is the 'Install OS X Yosemite.app' in your Applications folder?

 

[TMRJIJ]

I'm currently trying to do this on my MacBook Early 2008 just for fun.

Any chance you'll update MacPostFactor to support El Capitan?

There is no ETA for MacPostFactor 2.0 as of now.

 

[TMRJIJ]

As said in the Yosemite thread:

A bug has been discovered in OS X Extractor 1.31 installer that results in installation hanging and refusal to end the background tasks for shut down or restart. This issue seems to affect only certain Macs that upgraded from version 1.3 but I am not sure.
A workaround would be to force turn off by holding down the power button. If your Mac refused to boot after this:

1. Turn off your Mac
2. Start or restart your Mac. As soon as you hear the startup tone, press and hold Command-S on the keyboard.
3. Right after the root# prompt, enter the following:
   

   /sbin/fsck -fy

4. Press the Return key.
5. You’ll see the prompts in the picture above as each part of the hard drive’s directory is checked. (Checking extents overflow file, Checking catalog file, Checking multi-linked files, etc.) It will take a few minutes.
6. Right after the root# prompt, enter the following:

Reboot

7. Press the Return key. Your Mac should restart normally.

We are currently investigating this issue. We are sorry if we caused any inconvenience.​

 

[garirry]

Is the 'Install OS X Yosemite.app' in your Applications folder?

Dumb me, that's exactly the problem, El Capitan isn't in my Applications folder! I put it in, ran the extractor, and it appears some folders have appeared. Lemme try continuing the process now.

 

[garirry]

Okay, the process didn't work. I did everything except the boot.efi file changing (since I'm running on an EFI64 Mac), and while it would boot from USB and show the loading bar, after that, it would give me the Broken Boot icon. Any help?

 

[Riwam]

Is the 'Install OS X Yosemite.app' in your Applications folder?

**********
It certainly is.
However my MB 4.1 just offers ML ot Mavericks.
The Yosemite circle is transparent, not available.
I tried in the past and it was always so.

 

[Riwam]

Okay, the process didn't work. I did everything except the boot.efi file changing (since I'm running on an EFI64 Mac), and while it would boot from USB and show the loading bar, after that, it would give me the Broken Boot icon. Any help?

***********
Exactly the very same failure.
Only difference: I tried in my case Yosemite with the Extractor 1 3.1.
I followed the instructions point after point, leaving only those needed for EFI 32 Macs since it was a MB 4.1.
After booting and finding the well known circle with the inclined bar I followed the further instructions and tried to mend it from the Installer again, from the Recovery and from the Terminal (which didn't accept for unknown reasons to me the indicated instructions sudo codes!).
At that moment the MB began shutting down by itself and I thought I had ruined the machine for good
Finally I gave up and reinstalled the original Lion cloning it from an external drive which, thanks God worked.
I don't know why and cannot speak for others but at least for my MB 4.1 Mavericks seems to be the utter limit making no difference if I try the MCPF 1.0.1 or the Extractor 1.3.1. to go further than Mavericks.
In both cases total failure.
Ed

 

[atvusr]

[...] while it would boot from USB and show the loading bar, after that, it would give me the Broken Boot icon. Any help?

Try on the MB4,1 to remove the PlatformSupport.plist:

sudo rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist

If this doesn't help, try to boot the patched Installer via FireWire (or a replaced HDD) or try to run a transferred OSX 10.11 from a supported Mac with both Boot.efi replaced and Remote Desktop enabled, also via FireWire (or a replaced HDD). It seems that Apple has dropped the support for older Chipsets and therefore the USB-support is missing.

 

[Riwam]

Try on the MB4,1 to remove the PlatformSupport.plist:

sudo rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist

If this doesn't help, try to boot the patched Installer via FireWire (or a replaced HDD) or try to run a transferred OSX 10.11 from a supported Mac with both Boot.efi replaced and Remote Desktop enabled, also via FireWire (or a replaced HDD). It seems that Apple has dropped the support for older Chipsets and therefore the USB-support is missing.

**********
It's surely kind and nice that people try to help others as you do.

Hiwever I cannot avoid asking myself if "try this" followed by "try then that" and "try also this" is really all worth while...

As long as "Trial and Error" brings human kind to valuable new knowledge, it is certainly a good way for advancing all kind of research in every field.
However in this case it is almost always "Trial...and more and more Error".
Not worth it IMHO...
Ed

 

[Riwam]

There is no ETA for MacPostFactor 2.0 as of now.

*********
Would it be possible for you to ask MLforAll to let us know?
Thank you very much in advance!
Ed

 

[TMRJIJ]

*********
Would it be possible for you to ask MLforAll to let us know?
Thank you very much in advance!
Ed

He may not be available this weekend? These are finals weeks for us, so neither me nor Kelian will have free time to really get much work done on MCPF 2.0 or OS X Extractor 1.32. The current progress of MacPostFactor:

[11/6/15, 5:26:34 PM] MLforAll: Dmtest just asks the DiskManagement framework to do the job. Some error are caused due to the fact that I want, for example to create a Yosemite recovery from ML. So, I’ve made a workaround for that (the mac will reboot just like it would with a recovery, however, the rechd partition still doesn’t exists yet, and it will create the recovery. This way, I’m sure that there will be no issues related to OS X versions — i know, it’s a bit complicated this way but I’m using what Apple is using ) . The 2nd workaround is part of a new feature called “Small Recovery”. Instead of providing the OS X packages in the recovery, which takes HDD place, the recovery will ask you those when you’ll want to the the “clean install” feature from it. The workaround here, is to first create a recovery with the original Apple dmg, then replacing the boot.efi, kernelcache, com.apple.Boot.plist and BaseSystem files to get a MacPostFactor recovery.
[11/6/15, 5:27:32 PM] MLforAll: Also, these new workarounds allow the app to be fully compatible with SL!
[11/6/15, 5:30:03 PM] MLforAll: I’ve also made my own OS X Installer, so I’m able to do what I want of it
[11/6/15, 5:30:26 PM] MLforAll: found how to get the progress status from the installer command
[11/6/15, 5:31:29 PM] MLforAll: So I have a determinate progress bar This installer also allows me to immediately start the installation. The user doesn’t have to do anything after putting his password in the MacPostFactor window. Just like the real OS X update system!
Here’s what I still have to do :

- Add 1 or 2 features
- Make some changes in RTF files (changing credits…)
- 1 BIG interface change (boring…)
- test everything and fix remaining bugs (I already know some bugs I have to fix before the release, but I’ll fix them later as they aren’t crucial)

 

[atvusr]

For additional Kexts or replacing those it's necessary to turn off the System Integrity Protection (SIP) via the Recovery HD. If the Mac has EFI32 then the Boot.efi must also be replaced in the mounted Recovery HD.

For mounting the Recovery HD via Disk Utility the Debug menu must be enabled via Terminal:

defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

Now set a checkmark in the Debug menu at 'Show every partition' and the hidden Recovery HD partition will be displayed alongside the already mounted partitions. The Recovery HD is still greyed out but can now be mounted via right-click. The Boot.efi can then be replaced.

To disable the System Integrity Protection (SIP) reboot into the Recovery HD.

Open the Terminal-App and use the command:

csrutil disable

After that reboot the Mac to complete the changes.

It should now be possible to add or replace Kexts in the /System/Library/Extensions folder.

The SIP status can be checked via the Terminal-command:

csrutil status

SIP can also be re-enabled via Terminal-command plus reboot:

csrutil enable

The Disk Utility Debug menu can be disabled via Terminal-command:

defaults write com.apple.DiskUtility DUDebugMenuEnabled 0

 

[MacVidCards]

******
Whoever reads that kind of words can only wonder if living in Hollywood does change something in the way people over there see and consider themselves.
I was taught that a bit of modesty in life never harmed...on the contrary!
Maybe times have changed so much...

your recent posts complain about the installer not working.

In the quoted post you complain I am bragging.

What I was trying to establish is the truth. The OP would love to hand you a working solution (with a few ads in the installer) but he has yet to do so.

I have explained how to make it work as is. I have also explained that despite the obfuscation, there isn't a working solution, YET. You can't have it both ways, either someone is honest with you, or someone offers you possible solutions that don't work yet.

I am in a very unique situation where I can test kets since I already have a Mini in Recovery mode for El Cap. The OP is welcome to offer up modified kexts when they are ready. I'm not going to run an installer with things I don't need.

 

[Riwam]

your recent posts complain about the installer not working.

In the quoted post you complain I am bragging.

What I was trying to establish is the truth. The OP would love to hand you a working solution (with a few ads in the installer) but he has yet to do so.

I have explained how to make it work as is. I have also explained that despite the obfuscation, there isn't a working solution, YET. You can't have it both ways, either someone is honest with you, or someone offers you possible solutions that don't work yet.

I am in a very unique situation where I can test kets since I already have a Mini in Recovery mode for El Cap. The OP is welcome to offer up modified kexts when they are ready. I'm not going to run an installer with things I don't need.

********
I never said I do not appreciate all the effort that people like you invest to help people like me, lacking all the knowledge you, the thread starter and all the developers behind MCPF and Extractor truly have.

I just appreciate as well that, in spite of that undeniable and extremely valuable knowledge, those people having it should show a bit of modesty in the way they describe their achievements in their posts.
Luckily most of them do.
That is one of the truly nice things in this forum (or in any other one).
People like me not possessing that necessary knowledge(alas!) do not need to feel bad because of it.
Ed

 

[Riwam]

For additional Kexts or replacing those it's necessary to turn off the System Integrity Protection (SIP) via the Recovery HD. If the Mac has EFI32 then the Boot.efi must also be replaced in the mounted Recovery HD.

For mounting the Recovery HD via Disk Utility the Debug menu must be enabled via Terminal:

defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

Now set a checkmark in the Debug menu at 'Show every partition' and the hidden Recovery HD partition will be displayed alongside the already mounted partitions. The Recovery HD is still greyed out but can now be mounted via right-click. The Boot.efi can then be replaced.

To disable the System Integrity Protection (SIP) reboot into the Recovery HD.

Open the Terminal-App and use the command:

csrutil disable

After that reboot the Mac to complete the changes.

It should now be possible to add or replace Kexts in the /System/Library/Extensions folder.

The SIP status can be checked via the Terminal-command:

csrutil status

SIP can also be re-enabled via Terminal-command plus reboot:

csrutil enable

The Disk Utility Debug menu can be disabled via Terminal-command:

defaults write com.apple.DiskUtility DUDebugMenuEnabled 0

************************
El Capitan is the first OSX I remember in which post installation may need much more effort and much more additional measures that the installation itself.
The list of ToDos after "normal procedure" (assuming installation works at all, which shouldn't be taken for granted) is frightening large.
Is any OS upgrade truly worth to fight so much to try to have it work properly?
Personally I very much doubt it, unless it would be the ONLY OSX available in the world...which is certainly not the case!
I am not a masoquist. For the time being I prefer not willingly suffer with El Capitan, no matter how many "new features" Apple might promise
Ed

 

[Riwam]

He may not be available this weekend? These are finals weeks for us, so neither me nor Kelian will have free time to really get much work done on MCPF 2.0 or OS X Extractor 1.32. The current progress of it

********
I wish you good luck for your "final weeks"
Ed

 

[TMRJIJ]

I think I found a fix for the issue with OS X Extractor 1.31 failing installation and crashing Macs.
It will replace the current pkg in post 1.
Happy Thanksgiving (why people are downloading MCPF and OSXH and using the site on a holiday is beyond me )

 

[Riwam]

I think I found a fix for the issue with OS X Extractor 1.31 failing installation and crashing Macs.
It will replace the current pkg in post 1.
Happy Thanksgiving (why people are downloading MCPF and OSXH and using the site on a holiday is beyond me )

*******
Hello TMRJIJ
Maybe some people find enough joy by managing to inject new life to old appliances they cherish that it is their way to celebrate the holiday.

Since you are well informed...do you have any signs regarding MCPF 2.0 ?

Have a nice week end
Ed

 

[Spleeny]

Hello
My MP1.1 Reboot on old partition when I choose the new for install, when I try the screen turn black with white apple for 5 sec then turn grey with dark grey apple and boot 10.8 instead 10.11 installation menu.
I can't bless partition
When I try I get

Error while getting file ID of /Volumes/OS X Base System/boot. Ignoring...
Could not find IODeviceTree:/options

I've tried: reset pram, single user mode, safe mode

 

[atvusr]

My MP1.1 Reboot on old partition when I choose the new for install, when I try the screen turn black with white apple for 5 sec then turn grey with dark grey apple and boot 10.8 instead 10.11 installation menu.

For the Mac Pro 1,1/2,1 there's more help in this Thread: https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2-1-and-os-x-el-capitan.1890435 .

 

[Fred57]

Almost working...
Installed El Capitan through VM on Macmini 2,1
AutoDmg it
Restored on new partition

Which led me to be able to go to the installer menu
But no USB, so installed Rehabman's USBinjectall and fakepciid
https://github.com/RehabMan/OS-X-Fake-PCI-ID
https://github.com/RehabMan/OS-X-USB-Inject-All (all credit and copyright to Rehabman)

USB and all the rest is functional. I even removed those kexts and USB was still working.

Only issue, KPs after 15-30 seconds of use. Initially on
System uptime in nanoseconds: 135070116768
last loaded kext at 33842408104: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7f98f71000, size 28672)
last unloaded kext at 123159778124: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f987d8000, size 40960)

So I removed the audio driver, then on the magic track pad kext then on another, etc...
Apparently coming from something in the Kernel, but my knowledge stops there.

In a nutshell, I can boot EC on the Macmini on GMA950 with SL kexts, move my mouse, use KB, but not stay there for very long until next reboot

Ideas ?

 

[lhn555]

Trying to install on a MacBook4,1 and have done anything, but every time I try to boot it just boots into my OS X install. I've tried the normal custom boot.efi and the custom gray one and both do the same thing. I have tried blessing it as well. It is formatted properly as Mac OS X Extended Journaled.