aperture 2.1.1 hack

Ok, the offset for this latest update is 0x6f4bf0 – see the original Aperture 2 post for full details.

The summary is that you need to hex edit the Aperture.app/Contents/MacOS/Aperture file so that the string that starts at offset 0x6f4bf0 reads performLicenseCheck and is followed by five zero characters (ie: replace all of the text in the original performRequirementsCheck string).



  1. Shane September 14, 2008

    I made a duplicate of 2.1 before updating. After updating and changing the offset string to “performLicenseCheck” Aperture now unexpectedly quits on launch. The older 2.1 copy will not launch anymore either. Any ideas?

  2. ian September 14, 2008

    If you have a plain 2.1 and not 2.1.1 you need the offset described in this post.

    As for the backup – try deleting the version of Aperture you’ve been altering and rename the old one back to Aperture.app I suspect that the backup is still picking up changes you made.


  3. Shane September 14, 2008

    Ian, I’m struggling with this to get it working. Let me give you all the details:

    – I was running 2.1 up until yesterday without problems on a Sawtooth G4 with a NewerTech 2Ghz CPU upgrade, OSX 10.5.4, 1.25GB Ram, Radeon 9800 Pro 128MB.
    – I duplicated Aperture and left it renamed “Aperture copy”.
    – I ran Apple Software Update and updated 2.1 to 2.1.1.
    – I used 0xED to open /Applications/Aperture/Content/MacOS/Aperture.app (this is the 2.1.1 version)
    – I searched for Offset 6F4BF0 and changed it from “performRequirementsCheck” to “performLicenseCheck” and zeroed out the 5 remaining hex values and saved the file
    – I launched Aperture 2.1.1 and after about 5 to 10 seconds of watching the icon bounce in the dock, the finder pops up the “unexpectedly quit” message.
    – I trash Aperture 2.1.1 and rename “Aperture copy” (the old 2.1 version) back to just “Aperture” and launch it, the icon bounces for 5 to 10 seconds and then the finder pops up the “unexpectedly quit” message.

    So now I have no working version of Aperture. Please help if you know of a fix?

  4. Shane September 24, 2008

    I still haven’t found a fix for this. Can you help? Thx.

  5. mark September 24, 2008

    Any idea on how to bypass the graphics card check for 2.1.1? I’ve managed to get everything else working but I still can’t open it because of an unsupported graphics card.

  6. ian September 24, 2008

    Hi Shane,

    I’m really not sure what’s gone on for you – I can only assume that some support library got updated during the 2.1.1 update that makes the old copy fail. Which doesn’t help much. Can you re-apply the 2.1.1 update ? If not, you can grab a stand-alone 2.1.1 from the Aperture trial website (http://www.apple.com/aperture/trial/) and try again.

    For the record, once the hack has been applied if you open Terminal.app you can double check that the result is the same as mine by using the md5 command, eg:

    cd /Applications/Aperture.app/Contents/MacOS/
    md5 Aperture
    MD5 (Aperture) = 46b26c6ac9ccef15c1915596d9341bb3

    If that matches, and it still doesn’t work then I’m truly stumped as that is what I use !


  7. ian September 24, 2008

    Hi Mark,

    There’s some detail in the comments of the original Aperture 2 post, but basically have a look inside the /Applications/Aperture.app/Contents/Resources/MRCheckPro.bundle/Contents/Resources/minsys.plist file, and see if you can’t find something in there to help out.

    I did have some success in altering the AELMinimumVRAM entry to say that 16MB of video memory was sufficient – I can’t be sure that will bypass all of the video card checks though.


  8. Charlie Croker September 27, 2008

    If you are still having problems getting A2.1.1 to work then follow the instructions here:

    Remember though that performLicenseCheck has changed offset/location in 2.1.1 simply use the offset above (6f4bf0) as detailed to (PerformLicenceCheck) I didn’t enter zeros though I used Full stop/periods


    Open 0xED
    Choose File -> Open…
    Navigate to /Applications, then Aperture.app, then Contents, then MacOS, and finally choose the Aperture file and then click on Open
    Ensure the editor is set to Overwrite mode (Edit -> Write Mode)
    Enter 6D237C into the Offset box and hit Enter
    Check the ASCII side of things and you should see the string PowerBook starting under the cursor
    Open Terminal and type sysctl hw.model. On my MDD dual 867MHz system this returns: hw.model: PowerMac3,6
    Replace the Book part of the string in the 0xED window with the four characters after the word Power in the sysctl result. In my case, this means Mac3 so the string in the 0xED window now reads PowerMac3
    Save this file

    My Dual 800 G4 with Geforce 6200 and 1,256 of RAM runs it better than I expected.

    By the way thanks for a fantastic website help page, I couldn’t have done it without the info on here!

  9. Pandy October 30, 2008

    Would it be worth it to try this on version 2.1.2?

  10. ian October 31, 2008

    Hi Pandy,

    Version 2.1.2 has a different offset than 2.1.1 – I’ve put the value up in a new post: https://minimal.cx/2008/10/31/aperture-212-hack/


  11. Chris Tucker December 18, 2008


    0xED 1.06 (latest version) will not allow the offset 0x6f8f0 to be entered.

    I have a downloaded copy of Aperture 2.1.1. I performed the needed TextEdit fixes in the installer.

    The installer functions properly as far as I can tell. When finished, I open Aperture and it informs me that my Mac is not supported. No surprise, as I saw the same message when I installed 2.0 and 2.1. I fixed them using your instructions and they both worked. Foolishly, I deleted 2.1 when I downloaded the 2.1.1 installer. Searching for the performRequirementsCheck string, finding it and replacing it with the performLicenseCheck and 5 zero character string, saving it, and opening it results in a crash on launch.

    Essentially, I am doing the same things I did to make Aperture 2.0 and 2.1 work on this Macintosh.

    And now I come to find that I get the same crash on launch message using a newly hacked 2.1 Aperture.

    So, are there perhaps any invisible files installed by Aperture that would be missed by AppZapper? Any preference files I should be aware of?

    Thanks in advance!

Comments are Disabled