Contribute
Register

[solved] Unable to boot installer -- OsxAptioFixDrv Error

Status
Not open for further replies.
And I also wrote about desktop :)

Desktop questions should be asked in the appropriate desktop forum.

Note: The solutions for this problem are well known. OsxAptioFixDrv2-64.efi vs. OsxAptioFixDrv-64.efi (two versions 96mb/128mb [updated by me]). And disabling SIP config.plist/RtVariables/CrsActiveConfig=0x67.
 
Thanks guys & sorry, didn't realize I was in the laptop forum. Just did a search for this error & was the result that appeared to make the most sense. I will give it a shot when I get home later & thank you again!
 
I think OsxAptioFixDrv-64.efi needs modifications... I attached one here for you to try also... This one has a modest increase in the amount of memory reserved for this function. It can be increased further.

Try it, but if not working, also try OsxAptioFix2Drv-64.efi.

Fixed it for me on a Dell Latitude E5430. Freezes on loading AirPort kexts, though :( gonna delete my wifiinjector kext and see what happens.
 
Good night friend RehabMan,

It is too much to ask if you can attach the EFI entire folder for me?

I want to simply copy and paste this blessed folder in a pendrive and voila.

I have the same problem as the guy from the original post and honestly and I do not have much time to wandering around this stuff, especially when possibly you have this things at your fingertips.

I'm working 24 hours and at night too :=)

I don't have a Hackintosh available at this time to install Clover and so on.

I'll take care of any problems that may occur. I'll appreciate it a lot.

By the way, I have a Samsung NP530U3C (HD 4000 graphics, too rebel to install El Capitan)

So sorry for my (very) lousy english.
 
Good night friend RehabMan,

It is too much to ask if you can attach the EFI entire folder for me?

I want to simply copy and paste this blessed folder in a pendrive and voila.

I have the same problem as the guy from the original post and honestly and I do not have much time to wandering around this stuff, especially when possibly you have this things at your fingertips.

I'm working 24 hours and at night too :=)

I don't have a Hackintosh available at this time to install Clover and so on.

I'll take care of any problems that may occur. I'll appreciate it a lot.

By the way, I have a Samsung NP530U3C (HD 4000 graphics, too rebel to install El Capitan)

So sorry for my (very) lousy english.

The most common cause of this problem is too old Clover or incorrect settings for disabling SIP in config.plist.

Both are easy fixes that you should be able to apply yourself.
 
The most common cause of this problem is too old Clover or incorrect settings for disabling SIP in config.plist.

Both are easy fixes that you should be able to apply yourself.


Hello, this is my config.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ACPI</key>
<dict>
<key>DropOemSSDT</key>
<string>Yes</string>

<key>FixDsdtMask</key>
<string>0x0000</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
</dict>
<key>Graphics</key>
<dict>
<key>CustomEDID</key>
<data>AP///////wBMowAC/////wAWAQOAHRD/LwAAoFdJmyYQSE8AAAABAQEBAQEBAQEBAQEBAQEBnhtWeFAAGDAwICUAJaUQAAAZAAAA/QAAPADZCAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMs=</data>
<key>GraphicsInjector</key>
<string>Yes</string>
<key>InjectEDID</key>
<string>Yes</string>
<key>PatchVBios</key>
<string>No</string>
</dict>
<key>KernelAndKextPatches</key>
<dict>
<key>KextsToPatch</key>
<dict>
<key>0</key>
<dict>
<key>Find</key>
<data>AQAAAAIAAAAwAAAA</data>
<key>Name</key>
<string>AppleIntelFramebufferCapri</string>
<key>Replace</key>
<data>BQMAAAIAAAAwAAAA</data>
</dict>
</dict>
<key>ATIConnectorInfo</key>
<string>No</string>
<key>AppleRTC</key>
<string>No</string>
<key>AsusAICPUPM</key>
<string>Yes</string>
<key>KernelCpu</key>
<string>No</string>
</dict>
<key>PCI</key>
<dict>
<key>DeviceProperties</key>
<string>020400000100000001000000f60300001200000002010c00d041030a000000000101060000027fff04002a0000004100410050004c00300030002c0050006900780065006c0046006f0072006d0061007400000008000000000000002400000067007200610070006800690063002d006f007000740069006f006e00730000000800000004000000180000004100410050004c00300030002c0054003100000008000000000000002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601180000004100410050004c00300030002c0054003400000008000000c8000000360000004100410050004c00300030002c0049006e007600650072007400650072004600720065007100750065006e006300790000000800000000000000180000004100410050004c00300030002c005400370000000800000090010000280000004100410050004c00300030002c004c0069006e006b0046006f0072006d0061007400000008000000000000001e000000730061007600650064002d0063006f006e006600690067000000f00000005500000000000000000000000000000001000200030066010000000000c800c800000000005e0110070f0100000000000000000000000000000000000000000000000000000000000000000000000000000000000001010205000610c59c02010004000000000000000020435204000520038f0000002e0000003000200003000600000520030014000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002a0000004100410050004c00300030002c0044006100740061004a0075007300740069006600790000000800000001000000180000004100410050004c00300030002c0054003300000008000000c8000000240000004100410050004c00300030002c004400750061006c004c0069006e006b0000000800000000000000180000004100410050004c00300030002c005400360000000800000000000000240000004100410050004c00300030002c004c0069006e006b005400790070006500000008000000010000002c00000062006f006f0074002d00670061006d006d0061002d0072006500730074006f0072006500640000000c0000000000000000000000180000004100410050004c00300030002c005400320000000800000001000000180000004100410050004c00300030002c005400350000000800000001000000200000004100410050004c00300030002c0044006900740068006500720000000800000000000000</string>
<key>LpcTune</key>
<string>No</string>
<key>StringInjector</key>
<string>No</string>
<key>USBInjection</key>
<string>No</string>
</dict>
<key>Pointer</key>
<dict>
<key>Speed</key>
<string>8</string>
</dict>

<key>CPU</key>
<dict>
<key>Turbo</key>
<string>Yes</string>
<key>CpuFrequencyMHz</key>
<string>2400</string>
</dict>

<key>SMBIOS</key>
<dict>

<key>BiosVendor</key>
<string>Apple Inc.</string>
<key>BiosReleaseDate</key>
<string>21/03/12</string>
<key>BiosVendor</key>
<string>Apple Inc.</string>
<key>BiosVersion</key>
<string>MBP91.88Z.00D3.B00.1203211536</string>
<key>Board-ID</key>
<string>Mac-6F01561E16C75D06</string>
<key>Family</key>
<string>MacBook Pro</string>
<key>BoardManufacturer</key>
<string>Apple Inc.</string>
<key>ProductName</key>
<string>MacBookPro9,2</string>
<key>BoardSerialNumber</key>
<string>C02J5W69DTY3</string>
<key>Version</key>
<string>1.0</string>
</dict>
<key>SystemParameters</key>
<dict>

<key>InjectSystemID</key>
<string>No</string>
<key>boot-args</key>
<string>-v slide=0</string>
<key>iCloudFix</key>
<string>No</string>
<key>prev-lang:kbd</key>
<string>ru:0</string>
</dict>
</dict>
</plist>

I repeat, I don't have a Mac/Hack at this moment, so any help will be appreciate.
 
I replace the OsxAptioFixDrv.efi modified to 128MB by RehabMan, and i setted also the config.plist value of CsrUtilEnable to 0x67. The allocation error gone. I can boot. I am using clover 3526.

Later, I updated the OsxAptioFixDrv.efi with the one included on the installer of my clover version which is today version. It works. When i set the value of CrsUtilEnable to 0x3, the system does not boot. It gives the famous allocation memory problem.

It Looks that does not matter which version of OsxAptioFixDrv.efi i put over EFI drivers folder, because the 0x3 value make it does not work. In case of 0x3, the boot process works only with OsxAptioFixDrv-2.efi.

Thanks, now i can use OsxAptioFixDrv.efi. I supose that there is a mechanism of protection on new versions of El Capitan, that the process of overriding boot.efi fails.

I said that because the allocation error came at same time that i made El Capitan 10.11.4 update process. On 10.11.3 updating process it was very very good. like an authentic macintosh. like my laptop. Now, i supose it wont be dangerous to update to 10.11.5
 
I replace the OsxAptioFixDrv.efi modified to 128MB by RehabMan, and i setted also the config.plist value of CsrUtilEnable to 0x67. The allocation error gone. I can boot. I am using clover 3526.

Later, I updated the OsxAptioFixDrv.efi with the one included on the installer of my clover version which is today version. It works. When i set the value of CrsUtilEnable to 0x3, the system does not boot. It gives the famous allocation memory problem.

It Looks that does not matter which version of OsxAptioFixDrv.efi i put over EFI drivers folder, because the 0x3 value make it does not work. In case of 0x3, the boot process works only with OsxAptioFixDrv-2.efi.

Thanks, now i can use OsxAptioFixDrv.efi. I supose that there is a mechanism of protection on new versions of El Capitan, that the process of overriding boot.efi fails.

I said that because the allocation error came at same time that i made El Capitan 10.11.4 update process. On 10.11.3 updating process it was very very good. like an authentic macintosh. like my laptop. Now, i supose it wont be dangerous to update to 10.11.5

No such thing as CsrUtilEnable.

You need to set config.plist/RtVariables/CsrActiveConfig=0x67.
 
Status
Not open for further replies.
Back
Top