Andy Vandijck Posted July 15, 2013 Author Share Posted July 15, 2013 Thx! any ideas about name? Give me the patched EDID for that monitor please. I'll check it this evening. EDIT: Oh... you uploaded it. It was a very bad EDID. It had 3 times monitor name string (3x 00 00 00 FC entry). It had no monitor range limits inside. I corrected it to conform to EDID 1.4 totally. Try it and let me know. EDID2_Fixed.zip 1 Link to comment Share on other sites More sharing options...
Andy Vandijck Posted July 16, 2013 Author Share Posted July 16, 2013 I made a Windows driver that can override the EDID of a non-plug and play monitor. I use it to give Windows an EDID of my VGA connector of my TV. By default it sets the EDID of a TV with a resolution of 1280x960. You can edit the EDID inside the .inf file by editing this: [ANV_EDID_OVERRIDE-1_AddReg] HKR,EDID_OVERRIDE,"0",0x01,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x00,0x06,0x10,0x12,0xA0,0x00,0x00,0x00,0x00,0x1C,0x16,0x01,0x04,0xB5,0x30,0x1B,0x78,0x22,0x6F,0xB1,0xA7,0x55,0x4C,0x9E,0x25,0x0C,0x50,0x54,0x00,0x00,0x00,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x01,0x30,0x2A,0x00,0x08,0x52,0xC0,0x28,0x30,0x60,0x70,0x13,0x00,0xE0,0xE6,0x10,0x00,0x00,0x19,0x64,0x19,0x00,0x40,0x41,0x00,0x26,0x30,0x18,0x88,0x36,0x00,0xE0,0xE6,0x10,0x00,0x00,0x19,0x00,0x00,0x00,0xFD,0x00,0x16,0x50,0x0E,0x5B,0x10,0x00,0x0A,0x20,0x20,0x20,0x20,0x20,0x20,0x00,0x00,0x00,0xFC,0x00,0x69,0x4D,0x61,0x63,0x0A,0x20,0x20,0x20,0x20,0x20,0x20,0x20,0x20,0x00,0xA5 NOTE: The EDID is preseeded by "0",0x01,... You can modify the resolution in this are: [1024] HKR,,MaxResolution,,"1024,768" [1280] HKR,,MaxResolution,,"1280,960" And this gets put here: AddReg=ANV_EDID_OVERRIDE-1.AddReg, 1024, 1280, DPMS Note that the EDID first has a 0x01 before the EDID data.If you edit the driver inf, change this: CatalogFile=anvdisplay.cat To this: ; CatalogFile=anvdisplay.cat You can then install the driver after a save (change driver of your Monitor that is non-plug and play).Enjoy... Tested on Windows 7, should work on better too... EDIT: New version (V2) This one has 2 drivers (1600x1200 and 1280x960) I fixed sync issue causing the image to not always stand on the right place. I fixed driver params for horizontal and vertical resolution. Now there is a perfect way to get an EDID in Windows with TV's connected through VGA. The newest version (V2 signed) has got a Certum correct code signature. Now it doesn't say it can't verify the signature after install of the public certs provided along. Enjoy... EDIT: If anybody wants an EDID override for Windows for a plug-and-play monitor, contact me and I'll make one. AnV_Windows_TV_EDID_Driver_V2_signed.zip Link to comment Share on other sites More sharing options...
EvgeniX Posted July 17, 2013 Share Posted July 17, 2013 Give me the patched EDID for that monitor please. I'll check it this evening. EDIT: Oh... you uploaded it. It was a very bad EDID. It had 3 times monitor name string (3x 00 00 00 FC entry). It had no monitor range limits inside. I corrected it to conform to EDID 1.4 totally. Try it and let me know. and here is 2 working!! Thx! 1 Link to comment Share on other sites More sharing options...
djdjukic Posted July 17, 2013 Share Posted July 17, 2013 I've compiled this for Snow Leopard (32 and 64-bit) with Xcode 3.2.6.It seems to build just fine with no changes at all. I found this quite useful for an AMD rig. It eliminates a bunch of "decryption failed" boot messages and seems to speed up the boot process.AppleDecrypt-Sinetek-AnV.10.6.kext.zip 1 Link to comment Share on other sites More sharing options...
tonydickinson Posted July 28, 2013 Share Posted July 28, 2013 Hey Guys - I have just come across this thread, I really had no idea what Apple were doing - @ Schiedk MacBookPro, yeh you have been a solid supporter of OSX 86 for a long time but they look so cool and hold their value, and really no others (laptops) even begin to compare and you can still contribute.... Link to comment Share on other sites More sharing options...
Slice Posted July 28, 2013 Share Posted July 28, 2013 Version of 2008 if someone interested AppleDecrypt.kext.Leo.zip Link to comment Share on other sites More sharing options...
Slice Posted July 28, 2013 Share Posted July 28, 2013 @AnV I notice significant change in the new sources.Old call is aes_decrypt_cbc from kernel. New call is DSMOS_BF_cbc_encrypt from BLOWFISH DECRYPT from OpenSSL.Are you sure it is the same and more portable? Understand. encryptdecrypt? I'll recommend to exclude IOLog from page_transform and from compare_setup. I also think there is not needed check for PPC. There are no PPC Hackintosh. I am interesting to use AppleDecrypt together with FakeSMC. Results will be after long testing. Link to comment Share on other sites More sharing options...
WinstonAce Posted July 28, 2013 Share Posted July 28, 2013 Is this kext a replacement to fakesmc? Link to comment Share on other sites More sharing options...
Slice Posted July 28, 2013 Share Posted July 28, 2013 Is this kext a replacement to fakesmc? Yes and No. This kext permits you to boot OSX without FakeSMC but you loose some functionality due to absent of other SMC keys. Link to comment Share on other sites More sharing options...
eep357 Posted July 29, 2013 Share Posted July 29, 2013 That would be really cool. That explains why it doesn't complain about those kexts when you install them. Just came across this, looks to have a very short "exclude" list and then very long list of kexts that are OK to load without a valid signature. The allowed list has some kext that come from the Install OSX app, 3rd party and every Hackintosh kext I know of, even see my own name in this list too! My guess would be Apple just added dump of every kext they have could find any reference to without reviewing their function, then from here on they can just remove ones from the list that are a problem, causing much less work down the road and less upset average users. Also if there is a size check on file, adding new entries to it would cause much more work than simply removing existing entries. Link to comment Share on other sites More sharing options...
Andy Vandijck Posted August 5, 2013 Author Share Posted August 5, 2013 Just came across this, looks to have a very short "exclude" list and then very long list of kexts that are OK to load without a valid signature. The allowed list has some kext that come from the Install OSX app, 3rd party and every Hackintosh kext I know of, even see my own name in this list too! My guess would be Apple just added dump of every kext they have could find any reference to without reviewing their function, then from here on they can just remove ones from the list that are a problem, causing much less work down the road and less upset average users. Also if there is a size check on file, adding new entries to it would cause much more work than simply removing existing entries.If signed drivers would mean this list doesn't matter, the second Apple blocks kexts with no valid signature like FakeSMC, we could rebuild them and sign them with an Apple developer certificate (like I have, as I'm a paying dev).Only a theory though... I think kexts with no valid dev certificate only are passed through this list. We need further testing on this. Link to comment Share on other sites More sharing options...
Andy Vandijck Posted August 5, 2013 Author Share Posted August 5, 2013 Just came across this, looks to have a very short "exclude" list and then very long list of kexts that are OK to load without a valid signature. The allowed list has some kext that come from the Install OSX app, 3rd party and every Hackintosh kext I know of, even see my own name in this list too! My guess would be Apple just added dump of every kext they have could find any reference to without reviewing their function, then from here on they can just remove ones from the list that are a problem, causing much less work down the road and less upset average users. Also if there is a size check on file, adding new entries to it would cause much more work than simply removing existing entries. If signed drivers would mean this list doesn't matter, the second Apple blocks kexts with no valid signature like FakeSMC, we could rebuild them and sign them with an Apple developer certificate (like I have, as I'm a paying dev). Only a theory though... I think kexts with no valid dev certificate only are passed through this list. We need further testing on this. EDIT: Oh yeah? size check.... probably checksum that verifies the file wasn't modified, which is probably far worse than a size check if it's a custom checksum... @AnV I notice significant change in the new sources. Old call is aes_decrypt_cbc from kernel. New call is DSMOS_BF_cbc_encrypt from BLOWFISH DECRYPT from OpenSSL. Are you sure it is the same and more portable? Understand. encrypt<->decrypt? I'll recommend to exclude IOLog from page_transform and from compare_setup. I also think there is not needed check for PPC. There are no PPC Hackintosh. I am interesting to use AppleDecrypt together with FakeSMC. Results will be after long testing. Yes, the encrypt parameter has a value indicating encryption and decryption. Apple silently switched from a double AES decryption to a single Blowfish decryption (with OSK0 and OSK1 concatenated to a single key) but still disguising it as AES in the Dont steal Mac OS X.kext binary. It's true the PPC code can be excluded as there never was any encryption on PPC mac anyway and these days there also is no more PPC macs with 10.6 or better as it is all Intel. The decryption handler in action was used in verbose mode to check it handled the decryption. True this was only used for debugging check and can be excluded too Link to comment Share on other sites More sharing options...
boy_iran_64 Posted August 31, 2013 Share Posted August 31, 2013 please guide me for Vendor ID and Device ID for use fix EDID software? i have 2 type Vendor ID and 2 type Device ID (in ioreg ) once in GraphicsEnabler=No (in this mod enable LVDS but HDMI and VGA not work) DisplayProductID Number 1815 DisplayVendorID Number 1970170734 (in GraphicsEnabler=Yes AtiConfig=Gibba [olny vga worked] is same) but in GraphicsEnabler=Yes AtiConfig=Pondweed [only HDMI worked] DisplayProductID Number 1DisplayVendorID Number 7789 please Guide me... also i upload my edid file (make by edid manager) http://d-h.st/cBa Link to comment Share on other sites More sharing options...
Andy Vandijck Posted September 6, 2013 Author Share Posted September 6, 2013 (edited) I decided to dump a friend of mine's iMac's firmware. I used phoenix tools to extract all the modules uncompressed. The result is thus also all .ffs (.mod) files. I generated a firmware map report using mmtools for Aptio. Both are capable of extracting and modding Apple's firmware files. Hopefully somebody will be able to put these modules to good use Enjoy... EDIT: For the Info - Apple seems to use Tiano style EFI BIOS... EDIT2: I borrowed a friends MacBookPro5,3 and did the same to it... now we also have the same dump of a MacBook Pro EDIT3: Got my hands on a rom of a MacBookPro8,1, did the same. Also have one for MacBookPro8,2 but that is for tomorrow... iMac11,1_BIOS_Dump.zip MacBookPro5,3_BIOS_Dump.zip MacBookPro8,1_BIOS_Dump.zip Edited September 29, 2013 by Andy Vandijck 9 1 Link to comment Share on other sites More sharing options...
xpamamadeus Posted September 6, 2013 Share Posted September 6, 2013 And now the "Fun" starts But only after knowing which module is which and naming then so. i know 2 modules that i use(used in past) for clover. HFSPlus driver and firewire driver to solve console spam about invalid GUID Link to comment Share on other sites More sharing options...
Andy Vandijck Posted September 7, 2013 Author Share Posted September 7, 2013 Et voila! MacBookPro5,3 dump + info + extracted modules... Enjoy 1 Link to comment Share on other sites More sharing options...
Andy Vandijck Posted September 13, 2013 Author Share Posted September 13, 2013 This tool is made by me for reading and writing to CPU MSR registers. It works in kernel mode by a driver which is linked to the tool in user land with a user client. Source is included WARNING: Don't randomly read or write to MSR registers... If you read or write invalid MSR registers, or invalid data written, your system will crash... Usage: anvmsr read E2 = read MSR register E2 and show value. anvmsr write E2 0BAD = write 0BAD to MSR register E2 Enjoy... AnVMSR-1.0.zip A version for BigSur see here 5 Link to comment Share on other sites More sharing options...
CodeRush Posted September 13, 2013 Share Posted September 13, 2013 Haven't tested yet, but thanks anyway. Is there some software to read and interpret values of common PCI registers, such as LPC (D31:F0) or ME interface? Will be very useful too. 1 Link to comment Share on other sites More sharing options...
Slice Posted September 13, 2013 Share Posted September 13, 2013 Haven't tested yet, but thanks anyway. Is there some software to read and interpret values of common PCI registers, such as LPC (D31:F0) or ME interface? Will be very useful too. lspci? It included into DarwinDumper, see inside. Andy, See to compare msr_tools 3 Link to comment Share on other sites More sharing options...
Andy Vandijck Posted September 13, 2013 Author Share Posted September 13, 2013 lspci? It included into DarwinDumper, see inside. Andy, See to compare msr_tools Ok, just checked out the source... I'll build and test that tool too 1 Link to comment Share on other sites More sharing options...
Alex009988 Posted September 13, 2013 Share Posted September 13, 2013 What is a benefit for usual users? Can it help to find registers, voltage for example, for ACPIsensors who use laptops. Link to comment Share on other sites More sharing options...
Dr. Hurt Posted September 13, 2013 Share Posted September 13, 2013 Forgive my ignorance but could this eventually develop into something that can allow us to bypass BIOS/AICPUPM patching for native power management? Link to comment Share on other sites More sharing options...
Slice Posted September 13, 2013 Share Posted September 13, 2013 Forgive my ignorance but could this eventually develop into something that can allow us to bypass BIOS/AICPUPM patching for native power management? Sorry, no. MSR register 0xE2 has a property WriteOnce. It means that if BIOS write something in it then further writing is impossible. This is the reason why you need to patch ASUS BIOS no matter what you do later. Another method is to patch AICPUPM so that it will not use the register at all. 2 Link to comment Share on other sites More sharing options...
Dr. Hurt Posted September 13, 2013 Share Posted September 13, 2013 Sorry, no. MSR register 0xE2 has a property WriteOnce. It means that if BIOS write something in it then further writing is impossible. This is the reason why you need to patch ASUS BIOS no matter what you do later. Another method is to patch AICPUPM so that it will not use the register at all. Thanks for the explanation Link to comment Share on other sites More sharing options...
VanillaCracker Posted September 15, 2013 Share Posted September 15, 2013 A bit of info about modules Old stuff but still useful i believe SmmCoreDispatcher.efi APP 240612B5-A063-11D4-9A3A-0090273FC18ELegacyLoad.efi APP 2B0585EB-D8B8-49A9-8B8C-E21B01AEF2B7SpiUtil.efi APP 5604D863-BF24-439B-BBF6-636D72036E07PasswordUI.efi APP 9EBA2D25-BBE3-4AC2-A2C6-C87F44A1278CBootPicker.efi APP E1628C66-2A2D-4DC5-BD41-B20F3538AAF7FireWireOhci.efi DRV 0412A7A1-C050-42C2-877A-77C379F9F5F1LegacyMetronome.efi DRV 07A9330A-F347-11D4-9A49-0090273FC14DAppleHidInterface.efi DRV 07B37006-9302-408E-B416-B524D110DD7FEbc.efi DRV 13AC6DD0-73D0-11D4-B06B-00AA00BD6DE7SmmControl.efi DRV 1A2B4139-0DA4-416C-ADE3-85877B318266ScriptSave.efi DRV 1C6B2FAF-D8BD-44D1-A91E-7321B4C2F3D1SstSpiFlash.efi DRV 1E843AD6-E237-42FC-BDA2-DE78542E16DDAppleBrightnessControl.efi DRV 1F36527E-A97C-45F8-B24A-9D95B0A940FELegacyRegion.efi DRV 208117F2-25F8-479D-B726-10C10BED6DC1Intel945Uga.efi DRV 2342CA44-3B35-4A34-995B-CEDEEB1A9576IsaBus.efi DRV 240612B5-A063-11D4-9A3A-0090273FC14DUsbBus.efi DRV 240612B7-A063-11D4-9A3A-0090273FC14DIdeController.efi DRV 2686340E-665C-427F-8819-05BA54F030F5GmchMbi.efi DRV 26FFD0D2-33DE-4FCE-9E70-82B37A903668BiosVideo.efi DRV 29CF55F8-B675-4F5D-8F2F-B87A3ECFD063AcpiS3Save.efi DRV 2BDED685-F733-455F-A840-43A22B791FB3UsbMouse.efi DRV 2D2E62AA-9ECF-43B7-8219-94E7FC713DFEUsbKb.efi DRV 2D2E62CF-9ECF-43B7-8219-94E7FC713DFEFirmwarePassword.efi DRV 2D61B52A-69EF-497D-8317-5574AEC89BE4Uhci.efi DRV 2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7SmmAccess.efi DRV 326E9CC6-9839-4885-B2ED-275903B668E1Ich7MSmmDispatcher.efi DRV 35C5AB3E-B77A-450C-8854-159B2F0D32A5PcRtc.efi DRV 378D7B65-8DA9-4773-B6E4-A47826A833E1IchPowerButton.efi DRV 398262C1-5165-4725-87FC-BB786A972582ConSplitter.efi DRV 408EDCEC-CF6D-477C-A5A8-B4844E3DE281SmbiosMemory.efi DRV 42F5F135-3F50-4319-98A2-3B22DF559D20AppleBootPolicy.efi DRV 4391AA92-6644-4D8A-9A84-DDD405C312F3Partition.efi DRV 43B93232-AFBE-11D4-BD0F-0080C73C8881SmartTimer.efi DRV 45424D0C-E6AF-4AF2-AD99-FA77168742D1SmbiosMisc.efi DRV 46F9D8DA-2670-44B2-9E42-C9B130CE2465SataController.efi DRV 4C5C6A74-BAB7-46D6-8688-3B2E7F246E3FFtwLite.efi DRV 4C862FC6-0E54-4E36-8C8F-FF6F3167951FHfsPlus.efi DRV 4CF484CD-135F-4FDC-BAFB-1AA104B48D36Fat.efi DRV 5058F21C-BC34-11D4-BD18-0080C73C8881AcpiSupport.efi DRV 506533A6-E626-4500-B14F-17939C0E5B60ApplePowerState.efi DRV 508A61DC-2C57-4848-A54A-58015179C94ACrc32SectionExtract.efi DRV 51C9F40C-5243-4473-B265-B3C8FFAFF9FAConPlatform.efi DRV 51CCF399-4FDF-4E55-A45B-E123F84D456ADataHub.efi DRV 53BCC14F-C24F-434C-B294-8ED2D4CC1860BiosKeyboard.efi DRV 5479662B-6AE4-49E8-A6BD-6DE4B625811FIcnsConvert.efi DRV 5C08E2E2-AD70-4C99-94A2-AE604EA033DAYukonEthernet.efi DRV 5D337D63-2677-4868-8251-B97C6D1F0E90DxeIchInit.efi DRV 5F4735F7-DCF9-40FD-8858-026F931942A9FireWireDevice.efi DRV 6074610C-93C6-4A50-9AAA-0927DE7C6975AppleMemoryTest.efi DRV 60A14F6F-55B9-47A3-B067-01A93027F3FEGraphicsDisable.efi DRV 6229630C-32C3-4638-8091-838D985DFA82MpCpu.efi DRV 62D171CB-78CD-4480-8678-C6A2A797A8DEIchSpi.efi DRV 62FC1B9A-8851-4654-90AD-CEA8C07FE259ActiveBios.efi DRV 67AC0B1E-54C2-41A6-B57E-C2A321416ABCIdeBus.efi DRV 69FD8E47-A161-4550-B01A-5594CEB2B2B2SmmPlatform.efi DRV 6C077FAF-8258-4C08-B86D-B8DC632632B4AcpiPlatform.efi DRV 6C79BA9B-5926-4295-A450-46B3401D95A5SmmBase.efi DRV 737FE1C2-15E7-45D6-B37B-319FE880F733AppleAirport.efi DRV 74CBEC3C-8190-42A0-9C02-D1C5ADC706D7BSDP.efi DRV 77475D4F-7965-4038-B970-863FC73E0761Legacy8259.efi DRV 79CA4208-BBA1-4A9A-8456-E1E66A81484EAppleGraphicsPolicy.efi DRV 8A107CC5-DCDA-4FB7-A272-4243B41AFBFEApplePlatformInfoDB.efi DRV 8B24E4D4-C84C-4FFC-81E5-D3EACC3F08DDSmmThunk.efi DRV 8D3BE215-D6F6-4264-BEA6-28073FB13AEAEnglish.efi DRV 8F26EF0A-4F7F-4E4B-9802-8C22B700FFACAppleDataHubUpdate.efi DRV 91538AC9-A5D3-4DEF-9A70-28A087DEFA79Lpc47N20x.efi DRV 9204A71D-2050-4AB7-AD42-749CF9ADB4EBIsaSerial.efi DRV 93B80003-9FB3-11D4-9A3A-0090273FC14DNetBootUI.efi DRV 9A08BC1A-7561-4A68-8875-C0977C91573CAppleDiagnosticVault.efi DRV 9E85F0D5-5185-482B-8D50-5671307FEA80Terminal.efi DRV 9E863906-A40F-4875-977F-5B93FF237FC6LegacySataController.efi DRV 9F2A114A-834B-4916-945C-1C09F4944819StatusCode.efi DRV 9F455D3B-2B8A-4C06-960B-A71B9714B9CDUnknownBoot.efi DRV A2AB9D42-967A-45B3-9507-28CCC7021F51SNP.efi DRV A2F436EA-A127-4EF8-957C-8048606FF670UsbCbi0.efi DRV A3527D16-E6CC-42F5-BADB-BF3DE177742BAppleRemote.efi DRV A3CF349D-639C-4D08-AC4A-C95341FB4F94UsbMassStorage.efi DRV A5C6D68B-E78A-4426-9278-A8F0D9EB4D8FAppleDebugSupport.efi DRV A62D933A-9293-4D9F-9A16-CE81994CC4F2Bds.efi DRV A6F691AC-31C8-4444-854C-E2C1A6950F92AppleKeyMapAggregator.efi DRV AC4CE557-F5CD-439E-963C-40F09683DAC5PciHotPlug.efi DRV AC6993CF-43C8-4FCB-840C-B7CF2E079977AppleLegacyStartup.efi DRV AD21F7A0-7F5B-47FE-8CC0-241F318CABF5MonotonicCounter.efi DRV AD608272-D07F-4964-801E-7BD3B7888652IncompatiblePciDevice.efi DRV AD70855E-0CC5-4ABF-8979-BE762A949EA3FwBlockService.efi DRV B1659B1F-F74E-4866-9D66-2930900391A5UsbCbi1.efi DRV B40612B2-A063-11D4-9A3A-0090273FC14DUsbBot.efi DRV B40612B9-A063-11D4-9A3A-0090273FC14DRuntime.efi DRV B601F8C4-43B7-4784-95B1-F4226CB40CEECpuIo.efi DRV BAE7599F-3C6B-43B7-BDF0-9CE07AA91AA6LegacyBiosPlatform.efi DRV BC6D08DC-865D-4FFE-8B7A-FB5FB04F12F1AppleBootBeep.efi DRV BCCAD460-4F7D-4E51-8A5D-3BBA236D9EBBBinConvert.efi DRV BD87394D-465C-40A9-9657-FBED21789860EfiDevicePathPropertyDatabase.efi DRV BDFDE060-7E41-4EAE-AD9B-E5BBA7A48A3ALightPciBusPciBus.efi DRV C0734D12-7927-432B-986B-A7E3A35BA005DxeIchSmbus.efi DRV C21CF0E2-6ABC-4C3B-9DE6-3ABA8C3F83C9DiskIo.efi DRV CA261A26-7718-4B9B-8A07-5178B1AE3A02DataHubStdErr.efi DRV CA515306-00CE-4032-874E-11B755FF6866Variable.efi DRV CBD2E4D5-7068-4FF5-B462-9822B4AD8D60PciHostBridge.efi DRV CC322E80-6A08-4E80-8BCA-01A84BA6CFE4AppleFirmwareFeatures.efi DRV CC582C73-F48F-4B62-83E8-A586B4C88F84GraphicsConsole.efi DRV CCCB0C28-4B24-11D5-9A5A-0090273FC14DPngConvert.efi DRV CCEC84CD-CDC5-4C75-8637-D4508FC79CCDBmpConvert.efi DRV CD51358D-6E7E-45CA-B450-57C046BDFDDCIchS3Save.efi DRV D26374A5-7716-4708-AD9F-9C4F2C02547EIntelIchLegacyInterrupt.efi DRV D3709BB4-B194-4B71-B9C0-DBD8D2DA97ADLegacyBootFS.efi DRV DF9A9591-B646-4621-AF0D-18143A73289FSaveMemoryConfig.efi DRV E0ECBEC9-B193-4351-A488-36A655F22F9FAppleRtcRam.efi DRV E121EC07-9C42-45EE-B0B6-FFF8EF03C521PciPlatform.efi DRV E2441B64-7EF4-41FE-B3A3-8CAA7F8D3017AppleEvent.efi DRV E364A338-2842-4F57-A7C7-CDC8CFDF6CD7IntelIchReset.efi DRV E424C009-CD92-4FEC-8029-D79D3F1CF3DESmbios.efi DRV EAF59C0E-BD46-413A-9AE9-DD9F6D1A927DSetupBrowser.efi DRV EBF342FE-B1D3-4EF8-957C-8048606FF670SmmUsbLegacy.efi DRV EF33C296-F64C-4146-AD04-347899702C84WatchDogTimer.efi DRV F099D67F-71AE-4C36-B2A3-DCEB0EB2B7D8LegacyBios.efi DRV F122A15C-C10B-4D54-8F48-60F4F06DD1ADSecurityStub.efi DRV F1EFB523-3D59-4888-BB71-EAA5A96628FAAppleSmc.efi DRV F46998C9-DD30-4C64-966C-E17777B2568APlatformSetup.efi DRV F6D35FBB-63EA-4B25-81A5-5E62B4886292PowerManagement.efi DRV F7731B4C-58A2-4DF4-8980-5645D39ECE58HiiDatabase.efi DRV FCD337AB-B1D3-4EF8-957C-8048606FF670TargetDiskModeUI.efi DRV FF478412-38C3-4770-85F6-5D076C62125FDxeMain.efi DXECORE 35B898CA-B6A9-49CE-8C72-904735CC49B7PeiMain.efi PEICORE 52C05B14-0B98-496C-BC3B-04B50211D680CpuPeim.efi PEI 145971E9-AD52-4094-A8C8-BE5B3FECC82DIchSmbusArpDisabled.efi PEI 1DA353A3-6400-4241-9AB0-E3E65C690EF7PeiCdExpress.efi PEI 31E147A6-D39A-4147-9DA3-BEFD4D523243MonoStatusCode.efi PEI 371B0018-B4B4-474C-AD91-2632C89B7E2AAppleDebugSupportFireWireInit.efi PEI 54CE6010-2A6D-42AA-B1E2-FD97DE9C4DA8MemoryInitWrapper.efi PEI 77C0B0CB-0406-4868-AEB5-C36B01D42FF6DxeIpl.efi PEI 86D70125-BAA3-4296-A62F-602BEBBB9081S3Resume.efi PEI 8BCEDDD7-E285-4168-9B3F-09AF66C93FFEPciExpress.efi PEI A19FB0EE-05F4-4CD6-8F28-59B782FF95C6AtapiPeim.efi PEI B7A5041A-78BA-49E3-B73B-54C757811FB6PlatformStage2.efi PEI BB5B5907-5F8E-42AD-915D-5D98B52ED697Capsule.efi PEI C779F6D8-7113-4AA1-9648-EB1633C7D53BApplePpiPlatformInfoDB.efi PEI CD2B6EB3-EA11-4848-B687-AFE57D3D1C0FPlatformStage1.efi PEI F103A5A5-9345-4C3F-B496-DA14F41B6269PeiIchInit.efi PEI F21173FE-DF86-4B8B-AFF9-C7CB77B9C7DDSecCore.efi SEC 1BA0062E-C779-4582-8566-336AE8F78F09 2 Link to comment Share on other sites More sharing options...
Recommended Posts