Resolved OS X Yosemite on Unsupported Macs [Guide]

[chokung]

THANK YOU everyone for contributing on the development of running modern OS X on unsupported macs.

I got a Macbook 4,1 as a gift and I'm trying to make use of it; Ended up install Yosemite on my other MBP2012 then removed platformsupport.plist from /System/Library/CoreServices

Next install all the required kexts from my graphiccard (GMA X3100 144mb) and AppleHDA for the sound, I use AppleHDA from here.

It seems like my Macbook doesn't like VoodooHDA (sound is super low). I can live without graphic acceleration on this old guy but hoping that it can normally sleep && wake as in MountainLion in the future.

 

[Riwam]

Here is what I have so far Beta 1 Build 29 (I know right. lots of builds for just one beta). This package is 50KB but keep in mind that like OS X Extractor, its main files/scripts are running from the OS X Hackers site so make sure you have an active internet connection (5 GB minimum of disk space free).
Make sure the OS X El Capitan or Yosemite installer is in your Applications Folder. Once it is done. You should see an output.pkg in '/Volumes/.' The package doesn't automatically finish making the patched Installer so run this on a external or different partition. Upgrading from the same partition will not work and just return you back to the current OS.

More Betas to come of course.

*******
Hello TMRJIJ
I am very much hoping you are fine in spite of the US storms which caused such a lot of destruction in some states

Any new Beta of the previous Beta of your new tool ???
Anxiously awaiting the fruits of your unrivaled talent
ol' Ed

 

[Riwam]

I am developing a new tool in case MCPF 2.0 doesn't see any resolve.
I am working with new developers on OS X Patcher. If you recall in previous during OS X El Capitan Beta times, I designed OS X Extractor 1.3 with a new structure. All the smaller packages for Kexts, Software Update Patch, etc. are Flat distribution packages. The flat package uses a more compact format for its payloads which can be easily be put in OS X Installer. Basically my updates are somewhat future proof for this tool.
No ETA (most likely have public betas next week) but 50% of the scripts are already written and we're at the point where the Patcher is able to make a full fledged OS X Installer for Yosemite, and Mavericks. It gets caught in certain exceptions when during the Upgrade and Install method for certain Macs and can't determine Boot.fi's just yet.

I will notify if @MLforAll comes out of his contact cryosleep.

**********
Hello TMRJIJ
Since I haven't heard much about the development of the new tool you mentioned and was afraid you might not find the time to finish it, I tried again the MCPF 1.0.1 with my MacBook 4.1 early 2008.

First I tried Yosemite and was surprised that this time it was not grayed out like in the past. My next surprise was that the 4 steps ended with an announcement of "success".
However the "Reboot" asked did not work and restarting by myself welcome me with an yet entirely unknown large triangle sign saying something like wrong hardware or software.
I had never seen that triangle notice before!!!

That forced me to install Lion back since trying the Recovery partition gave me just the Hackers front page with a growing horizontal line below, but afterwards not the usual "manager" page allowing to rehack etc. I had always seen in the past.

Then I tried selecting Mavericks, but this time the 4th step ended with a failure notice and a log file on the desktop. ERROR CODE 3 is what it gives. Does it say anything to you?
The final trying was with Mountain Lion 10.8 and also the 4th step ended with a failure and a log file on the desktop.

Several monthes ago I had managed to install both Mountain Lion and Mavericks on this same Macbook 4.1 using MCPF 1.0.1.
(Yosemite was in the past always grayed out).

My MB 4.1 has now a SSD and I added some RAM to a total of 6 GB (maximum possible according to different sources in the web) but I cannot believe that THAT should be the reason of entire failure with all the 3 OSX over Lion 10.8, 10.9 and 10.10.

Any kind help would be very appreciated!
Thank you very much in advance!
Ed

PS. I opened the mcpfLog after a new failure with Mavericks (Error Code 3) and found inside:

dmtestPipeline.mc
done.extract.recm.mcp
done.modify.recm.mcpf
error.base.recm.mcpf
instTo.mcpf
mav.inst

 

[chmedly]

It’s all going into a MBP 2.1 with 6GB of RAM and 240GB SSD from OWC. I’ll let you know how it goes.
Thanks again!!

Dave

MacbookPro 2,1? I have a few of those and they only support 3GB (well, a pinch over 3GB to accurate) of ram. If you have 6GB in it then you must have found a 4GB card. They aren't the easiest to find. And unfortunately, that machine can't take advantage of it.

I've almost given up on these 2,1 machines. I did get Yosemite installed but it had enough glitches and issues that it wasn't particularly useful. Especially since I couldn't figure out a way to play netflix. That big 17" screen begs to be a mobile video machine but video playback is not good except in Lion. And I need at least Mavericks to run some other software that I need.

 

[TMRJIJ]

**********
Dear Isiah
Since I haven't heard much about the development of the new tool you mentioned and was afraid you might not find the time to finish it, I tried again the MCPF 1.0.1 with my MacBook 4.1 early 2008.

First I tried Yosemite and was surprised that this time it was not grayed out like in the past. My next surprise was that the 4 steps ended with an announcement of "success".
However the "Reboot" asked did not work and restarting by myself welcome me with an yet entirely unknown large triangle sign saying something like wrong hardware or software.
I had never seen that triangle notice before!!!

That forced me to install Lion back since trying the Recovery partition gave me just the Hackers front page with a growing horizontal line below, but afterwards not the usual "manager" page allowing to rehack etc. I had always seen in the past.

Then I tried selecting Mavericks, but this time the 4th step ended with a failure notice and a log file on the desktop. ERROR NR 3 is what it gives. Does it say anything to you?
The final trying was with Mountain Lion 10.8 and also the 4th step ended with a failure and a log file on the desktop.

Several monthes ago I had managed to install both Mountain Lion and Mavericks on this same Macbook 4.1 using MCPF 1.0.1.
(Yosemite was in the past always grayed out).

My MB 4.1 has now a SSD and I added some RAM to a total of 6 GB (maximum possible according to different sources in the web) but I cannot believe that THAT should be the reason of entire failure with all the 3 OSX over Lion 10.8, 10.9 and 10.10.

Any kind help would be very appreciated!
Thank you very much in advance!
Ed

PS. I opened the mcpfLog after a new failure with Mavericks (Error Nr. 3) and found inside:

dmtestPipeline.mc
done.extract.recm.mcp
done.modify.recm.mcpf
error.base.recm.mcpf
instTo.mcpf
mav.inst

Error Code 3 is a known issue that I discussed with MLforAll. It has something to do with the way the OS X Installer creates the Recovery Partition (dmtest)
As far as the new error you are receiving, can I by chance know that type of RAM you put in your Mac? There seemed to have been repeat incidents of MCPF failing due to the brand or maybe type memory that is being installed in these Macs.

OS X Patcher Beta, OS X Extractor, and the entire backend of the OSXH website is expected to be updated this weekend. As some may have noticed, the Facebook page now provides support in addition to the support emails.
MacPostFactor is still idle. I haven't contacted MLforAll in a while but he didn't have much to do on it except bug fixes and backend work.
Downloads/Installs have been increasing dramatically requiring incremental updates and bug fixes not mentioned on these forums so I hope to simply as much stuff as I can for these three platforms that I do have control over.

 

[raserror645]

/QUOTE]

**********

Hello TMRJIJ

Since I haven't heard much about the development of the new tool you mentioned and was afraid you might not find the time to finish it, I tried again the MCPF 1.0.1 with my MacBook 4.1 early 2008.

First I tried Yosemite and was surprised that this time it was not grayed out like in the past. My next surprise was that the 4 steps ended with an announcement of "success".

However the "Reboot" asked did not work and restarting by myself welcome me with an yet entirely unknown large triangle sign saying something like wrong hardware or software.

I had never seen that triangle notice before!!!

That forced me to install Lion back since trying the Recovery partition gave me just the Hackers front page with a growing horizontal line below, but afterwards not the usual "manager" page allowing to rehack etc. I had always seen in the past.

Then I tried selecting Mavericks, but this time the 4th step ended with a failure notice and a log file on the desktop.

ERROR CODE 3 is what it gives. Does it say anything to you?

The final trying was with Mountain Lion 10.8 and also the 4th step ended with a failure and a log file on the desktop.

Several monthes ago I had managed to install both Mountain Lion and Mavericks on this same Macbook 4.1 using MCPF 1.0.1.

(Yosemite was in the past always grayed out).


My MB 4.1 has now a SSD and I added some RAM to a total of 6 GB (maximum possible according to different sources in the web) but I cannot believe that THAT should be the reason of entire failure with all the 3 OSX over Lion 10.8, 10.9 and 10.10.

Any kind help would be very appreciated!

Thank you very much in advance!

Ed


PS. I opened the mcpfLog after a new failure with Mavericks (Error Code 3) and found inside:


dmtestPipeline.mc

done.extract.recm.mcp

done.modify.recm.mcpf

error.base.recm.mcpf

instTo.mcpf

mav.inst

__________



Hello,



Were you using Yosemite installer 10.10.5 or 10.10? I ask because I got the same error. Software/environment error after the reboot. I was trying to install 10.10.5 and a post in here suggested using 10.10. I did and it installed fine but no sounds and for that, you’ll need the apple hd.



BTW, does anyone know if the files from applications/osxhackers can be used if MPFT was used to install instead of the extractor?



Also, this might help. If you plan to experiment/hack but don’t wan’t to keep reinstalling the OS if the changes you made doesn’t work, try carbon copy. So for example, in my case, I have two partitions. A has Lion and B has Yosemite. I installed CC on the Lion partition and carbon copied the Yosemite partition to an external drive. If I make changes to the Yosemite files and it fails to reboot, I end up in the Lion. From here, I can either troubleshoot the changes I made or erase partition B then carbon copy Yosemite from the external drive to partition B. This has saved me time and headaches.



MBP 2.1 6GB RAM and 240GB SSD both from OWC

 

[raserror645]

MacbookPro 2,1? I have a few of those and they only support 3GB (well, a pinch over 3GB to accurate) of ram. If you have 6GB in it then you must have found a 4GB card. They aren't the easiest to find. And unfortunately, that machine can't take advantage of it.


I've almost given up on these 2,1 machines. I did get Yosemite installed but it had enough glitches and issues that it wasn't particularly useful. Especially since I couldn't figure out a way to play netflix. That big 17" screen begs to be a mobile video machine but video playback is not good except in Lion. And I need at least Mavericks to run some other software that I need.

Hello,



Yeah, I thought I was maxed out at 3GB but saw comparisons from OWC. I noticed a difference when I added the 4GB so I can’t really complain. I also ended up getting the Mercury SSD from them since it supported Trimm with no additional software. I suppose it’s one of those where YMMV. If you want to try it out, OWC guarantees performance and satisfaction, if you don’t notice a difference, return it in 30 days for a refund.



I dual boot so if I need to watch a video or a picture doesn’t look good in Yosemite, I rreboot into Lion. Since I’m blind, I am more concerned about the sound since I use voiceover, so the video/picture quality doesn’t bother me much.



So why does a blind guy like me have a 17 inch MBP? I really wanted a 13 inch but since it’s a hand me down, I had no choice. LOL Since this MBP is my hobby/project PC, I’m alright with it.



Current project MBP 2.1 with 6GB Ram and SSD both from OWC

Previous Projects

Apple MDD dual CPU upgrade and quiet kit

iMac 8600 cpu upgrade and OSX 10.1 using xpostfactto Wow, this one makes me feel really old LOL

 

[Riwam]

Error Code 3 is a known issue that I discussed with MLforAll. It has something to do with the way the OS X Installer creates the Recovery Partition (dmtest)
As far as the new error you are receiving, can I by chance know that type of RAM you put in your Mac? There seemed to have been repeat incidents of MCPF failing due to the brand or maybe type memory that is being installed in these Macs.

OS X Patcher Beta, OS X Extractor, and the entire backend of the OSXH website is expected to be updated this weekend. As some may have noticed, the Facebook page now provides support in addition to the support emails.
MacPostFactor is still idle. I haven't contacted MLforAll in a while but he didn't have much to do on it except bug fixes and backend work.
Downloads/Installs have been increasing dramatically requiring incremental updates and bug fixes not mentioned on these forums so I hope to simply as much stuff as I can for these three platforms that I do have control over.

******************
Thank you very much for reacting to my repeated request of help.
The RAM is the usual SoDimm 667MHz which the MacBook 4.1 takes.
I just added some, nothing special.

Is there a way to overcome that damned error code 3 ?

What puzzles me is that in the past I had managed with MCPF 1.0.1 to install both Mountain Lion and Mavericks...and now... it's as if MCPF would have been modified in some way...

I am anxiously awaiting the results of your effort in the coming days.
I do not expect miracles. To succeed to install Mavericks in my MB 4.1 would be enough for me.
Thank you very much in advance for your kind help!
Ed

 

[Riwam]

Error Code 3 is a known issue that I discussed with MLforAll. It has something to do with the way the OS X Installer creates the Recovery Partition (dmtest)
As far as the new error you are receiving, can I by chance know that type of RAM you put in your Mac? There seemed to have been repeat incidents of MCPF failing due to the brand or maybe type memory that is being installed in these Macs.

OS X Patcher Beta, OS X Extractor, and the entire backend of the OSXH website is expected to be updated this weekend. As some may have noticed, the Facebook page now provides support in addition to the support emails.
MacPostFactor is still idle. I haven't contacted MLforAll in a while but he didn't have much to do on it except bug fixes and backend work.
Downloads/Installs have been increasing dramatically requiring incremental updates and bug fixes not mentioned on these forums so I hope to simply as much stuff as I can for these three platforms that I do have control over.

******
Hello TMRJIJ
I haven't seen yet any change in your site.
Hopefully you find soon the time for the intended new things.
Thanks in advance!
Ed

 

[TMRJIJ]

******
Hello TMRJIJ
I haven't seen yet any change in your site.
Hopefully you find soon the time for the intended new things.
Thanks in advance!
Ed

The site should be down now
All downloads and support emails are temporary disabled in preparation of future updates.

EDIT: Maybe not. It appears the Backend has a bug. SSH console is not working either.

 

[Riwam]

Error Code 3 is a known issue that I discussed with MLforAll. It has something to do with the way the OS X Installer creates the Recovery Partition (dmtest)
As far as the new error you are receiving, can I by chance know that type of RAM you put in your Mac? There seemed to have been repeat incidents of MCPF failing due to the brand or maybe type memory that is being installed in these Macs.

OS X Patcher Beta, OS X Extractor, and the entire backend of the OSXH website is expected to be updated this weekend. As some may have noticed, the Facebook page now provides support in addition to the support emails.
MacPostFactor is still idle. I haven't contacted MLforAll in a while but he didn't have much to do on it except bug fixes and backend work.
Downloads/Installs have been increasing dramatically requiring incremental updates and bug fixes not mentioned on these forums so I hope to simply as much stuff as I can for these three platforms that I do have control over.

**************************************
Hello TMRJIJ

After almost a week your site is back reachable.
However I cannot find any new thing as you intended to post there.
If there is such a thing, would be grateful to know where?
Thanks
Ed
[doublepost=1455899442][/doublepost]

The site should be down now
All downloads and support emails are temporary disabled in preparation of future updates.

<><><><><><><><><><><><><><><><><><><>
Where are they supposed to be, now that the site is back
Ed

 

[zjays]

Hello,

Does Flash in Firefox work for anyone running an iMac 5,1/X1600 graphics card? In Yosemite (and Mavericks), Flash shows as installed at the link below, but the animation under Step 5 doesn't show up.

https://helpx.adobe.com/flash-player.html

It only works for me in Mountain Lion. Is graphics acceleration required for this to work?

 

[Riwam]

OS X Patcher Beta, OS X Extractor, and the entire backend of the OSXH website is expected to be updated this weekend. As some may have noticed, the Facebook page now provides support in addition to the support emails.
MacPostFactor is still idle. I haven't contacted MLforAll in a while but he didn't have much to do on it except bug fixes and backend work.
Downloads/Installs have been increasing dramatically requiring incremental updates and bug fixes not mentioned on these forums so I hope to simply as much stuff as I can for these three platforms that I do have control over.

***************
Hello TMRJIJ
I can see from your site being so often down that you are still making great efforts to help the community.
Thank you very much!

Allow me a question.
After much effort I managed with MCPF 1.0.1 to install in my MacBook 4.1 early 2008... Mavericks.
Mavericks works OK except in one point.
VLC, which is the best and more comfortable Media application, does not show me the image of my videos, only the sound track can be heard.

Any hint where the problem might be found and how to solve it will be very appreciated.
Thanks!
Ed

 

[01mggt]

So I created a Yosemite installer on my MBA running El Capitan for my 2006 iMac using the latest Yosemite app from the App Store. When I boot it up the progress bar is stuck at half way. Verbose mode shows tons of lines of text stating binary was improperly signed or not signed properly. Can't remember which one. What can I do to fix it?

Do I need to use a particular version of the installer app or something? It gave no errors when it was creating the USB drive. I also removed 2GB of ram from the iMac per the suggestion on post 846. I am almost to the point of just putting ML on here and being done

 

[duffman8]

I'm having a similar boot issue to the one mentioned above. I'm using a white MacBook 2,1. When I install the Yosemite installer (from App store) onto an 8GB flash drive using MacPostFactor 1.0.1, I am able to complete the USB preparation successfully only to find that I cannot get past the Apple boot/load screen when I go to use it (after holding option and selecting the correct drive during restart). The grey apple boot screen loads to ~50% and just remains there for hours.

I also used the Command-V option during restart to see what was going on, and there was a lot of code mentioning improperly signed binaries.

I should mention that I don't think this issue has anything to do with the USB because I used the same one to successfully install Mountain Lion.

Having given up on the USB installer issue, I moved on to directly installing Yosemite on a hard drive partition using MacPostFactor 1.0.1 once again. This allowed me to get as far as the OS X Hackers logo with the loading bar, but quickly thereafter went to a warning stating that "You're not running this app in the proper environment". It then directs me to an installation log page where I can see errors like "rm: /swap/mcpftmp: No such file or directory" or "mkdir: /swap: No such file or directory". There's a bit more but I won't fill the thread with it.

In light of these issues, if anybody has any idea how I can get Yosemite installed on my Macbook 2,1 2007 using MacPostFactor 1.0.1 (whether by USB or partition), that would be much appreciated.

 

[Riwam]

I'm having a similar boot issue to the one mentioned above. I'm using a white MacBook 2,1. When I install the Yosemite installer (from App store) onto an 8GB flash drive using MacPostFactor 1.0.1, I am able to complete the USB preparation successfully only to find that I cannot get past the Apple boot/load screen when I go to use it (after holding option and selecting the correct drive during restart). The grey apple boot screen loads to ~50% and just remains there for hours.

I also used the Command-V option during restart to see what was going on, and there was a lot of code mentioning improperly signed binaries.

I should mention that I don't think this issue has anything to do with the USB because I used the same one to successfully install Mountain Lion.

Having given up on the USB installer issue, I moved on to directly installing Yosemite on a hard drive partition using MacPostFactor 1.0.1 once again. This allowed me to get as far as the OS X Hackers logo with the loading bar, but quickly thereafter went to a warning stating that "You're not running this app in the proper environment". It then directs me to an installation log page where I can see errors like "rm: /swap/mcpftmp: No such file or directory" or "mkdir: /swap: No such file or directory". There's a bit more but I won't fill the thread with it.

In light of these issues, if anybody has any idea how I can get Yosemite installed on my Macbook 2,1 2007 using MacPostFactor 1.0.1 (whether by USB or partition), that would be much appreciated.

*********
Just my modest experience.
In a MacBook 4.1 early 2008 I could only install Mavericks with MCPF and an experiment with Yosemite made a complete mess forcing me to reinstall Lion and begin again with MCPF.
Although I have no explanation, MCPF seems to kind of "recognize" the limits of aged Macs and allows only an upgrade "to a certain point"and no more, in my case up to Mavericks.
Coming from Lion this means an upgrade to a 2 versions newer OSX, so I am satisfied with Mavericks since the only bug I found until now is VLC not showing the image of a video but only the sound.
A workaround was converting avis to MP4 and seeing those movies through Miro or Quicktime, which accept MP4 but not avi.

TMRJIJ the owner of the OS X Hackers.net, the place of MCPF 1.0.1, is trying new things.
Let's see when they will be ready there.
Ed

 

[jema68]

Is it possible to install with MCPF on a Raid (0 in my case)? I have tried, but it works here only if I break the raid and install on a single drive. Its not really important but I'm curious if it could work somehow. The machines are old 2006 Mac Minis, upgraded to 2.33 and SSD.

 

[raserror645]

I'm having a similar boot issue to the one mentioned above. I'm using a white MacBook 2,1. When I install the Yosemite installer (from App store) onto an 8GB flash drive using MacPostFactor 1.0.1, I am able to complete the USB preparation successfully only to find that I cannot get past the Apple boot/load screen when I go to use it (after holding option and selecting the correct drive during restart). The grey apple boot screen loads to ~50% and just remains there for hours.
----------------

Hello,

I had this issue as well when I tried to install on my MBP 2.1. I found if I used the first version of an OS like 10.9.1 or 10.10.1, it will install fine. But if I use a newer version, I get an enviromental error. I read this has occured to others and I wish I could tell you which post I found it on but there are 40 pages of posts on this thread.

 

[Riwam]

******
In my MacBook 4.1 early 2008 with Lion on it as the last supported OSX according to Apple, I chose this time Yosemite and an external installer media in the welcome screen of MCPF with the different options.

It ended however in...a Mavericks installation, as had been the case when selecting Mavericks and installing directly in the inner hard drive.

As I mentioned in the past MCPF 1.0.1 seems to decide by itself how far can be hacked the aged computer one tries to update.
How this happens I don't know but...it happens.
Ed

EDIT

After months of unsuccesfully trying, I finally managed to have Yosemite run in that MB 4.1.
In "some way" it was the strange result of using MCPF 1.0.1 in two ways, as an installation directly over the inside drive and as a way to create a USB key as an external installer.
Those 2 ways in some (for me) not understandable way made it possible.
Afterwards I added the missing sound as described in post #976 of "chokung" in this thread.
Of course it is not like running Yosemite in a newer mac, but somehow it works...

 

[Machist]

Hi all..

MacBook 3.1
Yosemite installation goes fine and its runs pretty good

But there is something what I don't figure out??

1. Boot problem. If I run updates I need to do this every time (
sudo rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist
)
'Software Update Patch' pkg is installed

EDIT: I run some updates again, and now it works? Maybe that first update was "gore" upgrade or something?

2. No sound. I only install GMA X3100 Kexts.pkg because I don't know where is this "attachment zip"

E: Install these 64 bit Kexts from the Kexts folder from OS X Extractor
(These will better the graphics by a little but you will not have Graphics Acceleration. Still in beta so they may not work well)

1. open the KextUtility.app by dropping all of the files inside this attachment zip folder named “kexts[yourgraphicsmodel…]“ to it. Don't forget to drop in the AppleHDA.kext for sound.
2. reboot.
3. Boot into Single User Mode (Hold Command-S after hearing the bong sound)
4. enter:
   Code:
   sudo nvram boot-args="kext-dev-mode=1"
5. reboot again normally.

 

[gpatpandp]

For those searching for a more reliable, useful solution to their otherwise unsupported ATI Radeon X1600 equipped Mac (iMac, MacBook Pro etc.), I gave Windows 10 64 Bit a whirl on our 2006 iMac 5,1 machine and after doing some homework, I'll be darned how exceptionally well it runs. Not a thing crippled functionally about it...fully operational and working with accelerated/beautiful graphics, SATA AHCI drivers for an SSD Hard Drive and Trim enabled, HD Audio, built-in iSight, Wireless, Ethernet, Bluetooth etc.

You'll need access to a PC w/ the app "ImageBurn" in order to build a custom Windows 10 64 Bit install disc as well as a combination of bootcamp drivers from v4, v5, and the latest BootCamp 6. Googling ATI Radeon X1600 for Windows 10 will instruct you how to get graphics working. I suppose you could install the

32 Bit version and avoid some work however constructing the 64 Bit install disc allows of course the operation of a 64 bit system while also the ability to install Windows 10 without the bootcamp assistant app (you install the bootcamp drivers manually).

 

[Riwam]

Hi all..

MacBook 3.1
Yosemite installation goes fine and its runs pretty good

But there is something what I don't figure out??

1. Boot problem. If I run updates I need to do this every time (
sudo rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist
)
'Software Update Patch' pkg is installed

EDIT: I run some updates again, and now it works? Maybe that first update was "gore" upgrade or something?

2. No sound. I only install GMA X3100 Kexts.pkg because I don't know where is this "attachment zip"

E: Install these 64 bit Kexts from the Kexts folder from OS X Extractor
(These will better the graphics by a little but you will not have Graphics Acceleration. Still in beta so they may not work well)

1. open the KextUtility.app by dropping all of the files inside this attachment zip folder named “kexts[yourgraphicsmodel…]“ to it. Don't forget to drop in the AppleHDA.kext for sound.
2. reboot.
3. Boot into Single User Mode (Hold Command-S after hearing the bong sound)
4. enter:
   Code:
   sudo nvram boot-args="kext-dev-mode=1"
5. reboot again normally.

*+*+*+*+*+*+*+*+*+*+
Regarding sound see post #976 from chokung in this thread.
..." I use AppleHDA from here "...
That "here" links you in that post to another post also with a "here". Following this new "here" you find a folder to download which you can open with 7z for mac (a free useful tool).
Inside, among many kexts NOT suitable, you will finf AppleHDA as well as a kext.app to install kexts.

Just be cautious.
I installed a kext which killed the wi fi in my MacBook 4.1 early 2008
A bootable clone USB stick of my system helped me to correct my fault.
That safety measure should always be done prior to trying something unknown in order to allow an easy restore. Another safety measure is of course TimeMachine.

INHO kexts should be installed always one after the other with a newstart in between to check for possible faults.
Ed

 

[Machist]

*+*+*+*+*+*+*+*+*+*+
Regarding sound see post #976 from chokung in this thread.
..." I use AppleHDA from here "...
That "here" links you in that post to another post also with a "here". Following this new "here" you find a folder to download which you can open with 7z for mac (a free useful tool).
Inside, among many kexts NOT suitable, you will finf AppleHDA as well as a kext.app to install kexts.

Just be cautious.
I installed a kext which killed the wi fi in my MacBook 4.1 early 2008
A bootable clone USB stick of my system helped me to correct my fault.
That safety measure should always be done prior to trying something unknown in order to allow an easy restore. Another safety measure is of course TimeMachine.

INHO kexts should be installed always one after the other with a newstart in between to check for possible faults.
Ed

Thanks!
It works

Graphics Acceleration is little slow but otherwise this works very well..

 

[mamarrash]

I have successfully installed OS X Yosemite in a Mac Mini 2.1 (Core 2 Duo, 4GB RAM)

I used MacPostFactor 1.01. I´ve installed also the PikeYoseFix for the updates to work (once you reboot), Kext Utility App and everything else from OS X hackers. So far everything is excellent, except:

-Recovery partition: Does not work. It says 10.10.3 but it won´t boot from there.

-Wi-FI: I used a kext from Mountain Lion. In that way the wi-fi card appears in system information. BUT, it won´t detect any networks available. So it´s useless. to clarify, I must have test at least 10 "IO80211Family.kext" but with no results.

Any ideas. Solutions? Anyone with the same Mac that have had success?

 

[Riwam]

I have successfully installed OS X Yosemite in a Mac Mini 2.1 (Core 2 Duo, 4GB RAM)

I used MacPostFactor 1.01. I´ve installed also the PikeYoseFix for the updates to work (once you reboot), Kext Utility App and everything else from OS X hackers. So far everything is excellent, except:

-Recovery partition: Does not work. It says 10.10.3 but it won´t boot from there.

-Wi-FI: I used a kext from Mountain Lion. In that way the wi-fi card appears in system information. BUT, it won´t detect any networks available. So it´s useless. to clarify, I must have test at least 10 "IO80211Family.kext" but with no results.

Any ideas. Solutions? Anyone with the same Mac that have had success?

View attachment 620473 View attachment 620474

****
Unfortunately my Yosemite runs in a MacBook 4.1 and not in a MacMini.
Did you looked in the Atheros drivers supplied for a BootCamp installation?
Did you download the supporting files of OSX Hackers.net for the other tool, The Extractor 1.3.1 ?
Inside those additional files there are different kexts.

As to the Recovery Partition for Yosemite, in my Mac it is entirely missing.
I use clones (USB sticks cloned with CarbonCopyCloner) and TimeMachine backups all the time, since any update (even a security minor update) causes me losing sound in the microphone and speaker that I have to correct each time with AppleHDA.kext and the kext install.app (found in post #976 of chokung following his linked report). There are also different kexts.

Le deseo mucha buena fortuna, amigo, y mucha paciencia hasta que logre que todo funcione como es debido.
Cordiales saludos
Ed