Surface Laptop stuck on +++ on first boot

[halorocker89]

Sorry if I forget to include some information--I'm kinda new to this. I've successfully Hackintoshed my desktop PC, but some configuration changes and the Nvidia primary GPU have made it completely impractical for the couple of things I need a Hackintosh machine for.

I have the original Surface Laptop with the i5-7200U (HD 620 Graphics). I've attached my EFI folder for reference--I started with RehabMan's awesome HD 620 etc. config.plist, and added some DVMT patching stuff. The main drive is an SSD (fairly sure it's NVMe), and I currently have an installation of Windows 10 that I'm not attached to and intend to wipe.

I can boot into clover and it detects my macOS installer, but Verbose shows just a line of +'s.

Many thanks for any help!

 

[P1LGRIM]

Not a Desktop - Moved to Laptop Support.

 

[halorocker89]

Not a Desktop - Moved to Laptop Support.

Oops! This was my first post and I don't know the site layout too well.

 

[BeastOnFire]

Hey,
Since this evening I'm also trying to get past the ++++ screen on my surface laptop (core m3 variant though). I'll keep you updated if I find the solution. I've got it to boot to the installation screen before but that was a long time ago. Now, since I've gained quite some experience (full desktop and laptop hackintosh) I'll give this anther shot. Did you find a solution yet?

 

[halorocker89]

Hey,
Since this evening I'm also trying to get past the ++++ screen on my surface laptop (core m3 variant though). I'll keep you updated if I find the solution. I've got it to boot to the installation screen before but that was a long time ago. Now, since I've gained quite some experience (full desktop and laptop hackintosh) I'll give this anther shot. Did you find a solution yet?

I've made some progress--OpenCore has better documentation than Clover in my opinion, and one of its boot verification tools let me see that Cfg-Lock appears to be forced on in the UEFI firmware. The normal solution for this would be to patch the firmware, but Surface's UEFI firmware is rather irritating--it comes in a .bin file with abnormal structure, a .cab file with data, and an .inf file as an index. I have no clue how to parse these myself, or even if the firmware is patchable. I have Boot Configuration Lock off in the firmware settings, but maybe I'll turn it on and back off again just for kicks. Glad I'm not the only one trying to figure this one out.

 

[BeastOnFire]

I've made some progress--OpenCore has better documentation than Clover in my opinion, and one of its boot verification tools let me see that Cfg-Lock appears to be forced on in the UEFI firmware. The normal solution for this would be to patch the firmware, but Surface's UEFI firmware is rather irritating--it comes in a .bin file with abnormal structure, a .cab file with data, and an .inf file as an index. I have no clue how to parse these myself, or even if the firmware is patchable. I have Boot Configuration Lock off in the firmware settings, but maybe I'll turn it on and back off again just for kicks. Glad I'm not the only one trying to figure this one out.

It shouldn't be that hard to do, I remember getting to the installation screen, I just don't remember how to solve the issue for getting further than the +++++. I'll give itt a shot agaion today but I don't have that much time since Ihave exams.

 

[halorocker89]

It shouldn't be that hard to do, I remember getting to the installation screen, I just don't remember how to solve the issue for getting further than the +++++. I'll give itt a shot agaion today but I don't have that much time since Ihave exams.

Maybe it's my USB drive? In my searching I found that sometimes using USB 2.0 in an XHCI port is bad...but idk

 

[halorocker89]

Maybe it's my USB drive? In my searching I found that sometimes using USB 2.0 in an XHCI port is bad...but idk

Wait nevermind--I remember trying with a USB 3.0 drive and that had no effect. I read it could be ApitoMemoryFix, but I personally think the BIOS is just locked down.

 

[BeastOnFire]

Wait nevermind--I remember trying with a USB 3.0 drive and that had no effect. I read it could be ApitoMemoryFix, but I personally think the BIOS is just locked down.

Did you have any success booting it yet? I didn't have time to test since I had exams, but I might give it a shot this evening.

 

[halorocker89]

Did you have any success booting it yet? I didn't have time to test since I had exams, but I might give it a shot this evening.

Not yet—I’m like 90% sure it’s a graphics problem cuz I’ve had problems with 620 before...do let me know if you have luck cuz I’m stuck for now.