elBuey Posted June 30, 2021 Share Posted June 30, 2021 Hello Guys, After successfully hackintoshing my Dell Latitude E7270 and my wife's Inspiron 5559 with valueable help from @Jake Lo I'm now trying to Hackintosh my dad's Dell Latitude 3390 2-in-1. The hardware is the following: Intel i3-7130U @2.7GHz CPU Intel HD 620 graphics Intel Dual Band Wireless-AC 8260 wireless 256GB SSD 12GB RAM I've followed the guide from dortania.github.io, trying for the first time to make manually my own SSDTs (dumping the DSDT with SSDTTime and following Dortania's instructions) but after choosing on the OC menu to boot from the USB, I get an error message saying "OCB LoadImage failed - Unsupported" My EFI folder can be downloaded from the following link: https://we.tl/t-U9O8lEFT5s (it exceeds 19.53 Mb so I wasn't able to attach it here) Any help you can provide me would be much appreciated. Regards, elBuey Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted June 30, 2021 Moderators Share Posted June 30, 2021 Try setting SecureBootModel from Default to Disabled Link to comment Share on other sites More sharing options...
elBuey Posted June 30, 2021 Author Share Posted June 30, 2021 Thanks for your prompt response, @Jake Lo. I switched SecureBootModel from Default to Disabled and still get the exact same error message: "OCB LoadImage failed - Unsupported" Link to comment Share on other sites More sharing options...
Administrators Hervé Posted June 30, 2021 Administrators Share Posted June 30, 2021 DmgLoading set to "Signed" ? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted June 30, 2021 Moderators Share Posted June 30, 2021 Try enabling JumpstartHotPlug Link to comment Share on other sites More sharing options...
elBuey Posted June 30, 2021 Author Share Posted June 30, 2021 Thank you for your always present willingness to help, @Jake Lo and @Hervé. Yes, DmgLoading was set as String to "Signed" I tried enabling JumpstartHotPlug and still the same. The only thing that got me a bit confused was when generating the Plug SSDT: on the DSDT I dumped with SSDTTime the 4 threads appeared with one name, but on the Windows Device Manager, under BIOS device name they appeared under _PR.PR01 and I used this last for building the SSDT. Do you think it could help to edit the SSDT using the path shown on the DSDT.aml file I dumped? Link to comment Share on other sites More sharing options...
Administrators Hervé Posted June 30, 2021 Administrators Share Posted June 30, 2021 Try and change LauncherOption to Full. Can't see or imagine any relation to the CPU PM SSDT. Link to comment Share on other sites More sharing options...
elBuey Posted June 30, 2021 Author Share Posted June 30, 2021 Thank you @Hervé, but still no luck... exactly the same error message... This is so frustrating! Link to comment Share on other sites More sharing options...
Administrators Hervé Posted June 30, 2021 Administrators Share Posted June 30, 2021 You do reset NVRAM after any OC config change, right? Link to comment Share on other sites More sharing options...
elBuey Posted June 30, 2021 Author Share Posted June 30, 2021 I wasn't, but now that you've told me to I did, and still no luck. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now