augustopaulo Posted January 11, 2018 Share Posted January 11, 2018 Hi, I got a Dell Latitude E5570 with the following hardware: Intel l7-6820HQ 2.70GHz Skylake-H Intel HD Graphics 530 / AMD Radeon R7 M370 (touchscreen) Realtek ALC3235 (ALC293) 16GB DDR4 BIOS Date: 1.5.0 04/22/2016 Fingerprint sensor, webcam, etc... Now with the attached EFI, I'm able to get quite far, where the graphics would usually show up, but then it keeps saying re-spawning for 10 seconds indefinitely... In the EFI/CLOVER/ACPI/origin, you'll find my extract (F4) .aml files. Can someone have a look & tell me the next steps please ? Thanks in advance. Boa sorte, Paulo EFI.zip Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted January 12, 2018 Moderators Share Posted January 12, 2018 Try replacing contents into /EFI/Clover Updated file with custom EDID to fix wake to blank screen issue E5570_Disable_M370.zip 1 Link to comment Share on other sites More sharing options...
augustopaulo Posted January 12, 2018 Author Share Posted January 12, 2018 Hi Jake Lo, Thanks so much for your help - The laptop is UP and RUNNING MacOSX 10.13.2!! (I'm typing from it) Initially, I followed all your instructions but the boot would always stop just after the USB were detected, followed by the STOP sign... Then, I just changed the EF/CLOVER/kext/other with my own and voila, I was able to install it completely and then even update with latest security update... What works: CPU with power management Intel HD 530 with full resolution Full sound: speakers & microphone full keyboard with backlight, brightness and sound USB3 external SSD boot disk (not SATA) WLAN on external USB dongle (RTL2870 compatible) Battery fully reporting charge Touchpad, stickpad & touch screen fully working ("Ink" panel in system preferences) webcam Onboard LAN What doesn't work: Internal Wifi & bluetooth sleep: it does go into sleep, but reboots on wakeup fingerprint sensor other sensors I've attached the new EFI folder., .ioreg & output from Runme. Boa sorte, Paulo Send me paulo’s MacBook Pro.zipEFI.zippaulo’s MacBook Pro.ioreg.zip Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted January 13, 2018 Moderators Share Posted January 13, 2018 Could be an EDID issue...try this Intel Wifi is not supported, replace with DW1560 or DW1830 1 Link to comment Share on other sites More sharing options...
augustopaulo Posted January 13, 2018 Author Share Posted January 13, 2018 Hi Jake Lo, You're the MAN!! - SLEEP and WAKE UP working!!!! Only small issue, is that I loose sound after wake up... The guide is easy to follow and get the right display EDID information to be used for injection in Clover. Boa sorte, Paulo Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted January 13, 2018 Moderators Share Posted January 13, 2018 Can you attach your Config file with the injected EDID so I could update the bootpack? Install EAPDFix.kext to /L/E repair permission and rebuild cache kext can be found in my Other/LE folder Link to comment Share on other sites More sharing options...
Headshotde Posted May 20, 2018 Share Posted May 20, 2018 augustopaulo do you have a NVME in your E5570 ? i can boot the installation with your EFI folder but i cant find my SSD in Diskutillity Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted May 20, 2018 Moderators Share Posted May 20, 2018 NVME is natively supported in HS. What NVMe brand does it have? Have you tried clicking on the drop down arrow in Disk Utility? Link to comment Share on other sites More sharing options...
Headshotde Posted May 21, 2018 Share Posted May 21, 2018 Its a Intel SSDSCKKF256H6 I've already tried show all devices in Diskutillity but it shows only my USB stick and not the internal NVME With Sierra and Patches of https://github.com/RehabMan/patch-nvme in config.plist it works Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted May 21, 2018 Moderators Share Posted May 21, 2018 You might have to initialized the drive either in Windows or another OS first. Link to comment Share on other sites More sharing options...
Recommended Posts