Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Update of a 4,1 iMac upgraded to Core2Duo

6 posts in this topic

Recommended Posts



I've an early 2006 iMac (4,1) that I updated with Core2Duo. I then upgraded the firmware to 5,1 and everything works without issues. It is currently running 10.6.8. System profile reports it correctly as an iMac5,1.


I wanted to update it to El Capitan (or Mavericks at the very least) because most apps are in dire need of upgrade. The problem is that the MPF and macOS extractor guides have a prerequisite that you start at Lion (10.7) and I just can't get it installed.


I've followed the procedure described in this post: http://www.insanelymac.com/forum/topic/249877-how-to-install-lion-on-any-coreduo-mac-upgraded-to-a-core2duo/, specifically post#8. In a nutshell, I've:

  • created an "InstallLion", restoring it to the contents of the BaseSystem.dmg file found inside the installer volume.
  • removed the symlink and copied the installation packages.
  • deleted the PlatformSupport.plist and copied the new  OSInstall.mpkg.

It doesn't even boot from the image. I've also tried in an external USB drive and no dice. It starts booting and immediately shuts down.


Does anyone have any clue where to trouble shoot? Is there an updated procedure that has a better success rate? Is it possible to get a bare system image from someone with an upgraded iMac5,1 that has it working?



Share this post

Link to post
Share on other sites

I believe that, yes, this will create a correct boot image. I use it that way, then I install clover and kext and it works correctly, I suppose that it will also be that way in its necessity.

Share this post

Link to post
Share on other sites

Did you give a bless(ing) command:

sudo bless -folder /Volumes/Boot -file /Volumes/Boot/boot -setBoot -legacy 

You may have to edit this to be compatible to your system the way you named the file.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.