Surface Pro 5 Core i7 - 8 GB RAM - Working?
Closed this issue · 7 comments
Hi Bro,
I hope you are doing well.
It is good to see, you are still supporting this development. Thank you very much.
Recently I got a Surface Pro 5. I was very impressed with SP3 & SP4 Hackintosh build by yours, near to perfect for daily use. Is there any build for Surface Pro 5 from your side? Can we use your SP3, or SP4 or SP7 build for SP5 as perfect as your SP3 build?
Thank You very much in advance
@alappatsj Hi and thank you.
As of now I am not planning on providing a release for the SP5, however I believe the SP4 release will likely work with the SP5 with little modification.
The key differences between the two are simply the processor and graphics. You likely only need to change the graphics identifier to a compatible but matching identifier in the config to get it to boot. You also will likely need to change the SMBIOS to a compatible one for the processor of your SP5.
It is possible that some of the kexts or other patches won't be compatible and will need to be disable or deleted but I highly doubt it. There was so few differences between the two computers they even used the same screens at one point.
I definitely would start with my SP4 EFI as your base since it does have key patches that will allow macOS to upgrade natively as well as allow you to use the correct SMBIOS without it being unsupported. Most other EFIs even if designed for the SP5 would likely not have those patches. While it didn't matter back then, it matters now since Apple has been removing support for older systems.
Lastly none of my EFIs support anything newer than Sonoma currently. It's important that you only test with Sonoma and older. Trying to boot the latest beta OS will only add more problems which is why it's not enabled on my EFIs currently.
Thank you very much for detailed response. But I am novice in coding or this kind of work. I used to just download your EFI builds and replace the existing EFIs for SP3 & SP4.
@alappatsj I did a quick google search and it appears there is an active repo for the Surface Pro 5 here: https://github.com/PGBSean/Surface-Pro-5-OpenCore
I haven't tested it or looked at the EFI to see how well it works since I don't have a SP5 to test on but based on the readme page it appears to have all the most recent fixes and features.
I generally try to avoid creating a repo if its already been done by someone else except in a situation where I have the device and when the other repo seems to be no longer updated and/or is missing significant features or fixes. Hope that link will get you up and running. Happy to answer further questions if you have them
I tried his EFI.
I had Monterey installation USB ready for your SP3 & SP4, and I have replaced the EFI with his SP5 EFI.
The installation was little easy. But the 1st boot or setup is giving issues. Hangs either at Hello or Language selection and it cannot go past selecting country or region. Even after multiple reboots, cannot go past select your country page.
My device is Surface Pro 5 CORE * i7 * , 8 GB RAM. So any issues with graphics?
Plz help
I changed the Deviceproperties for device id & platform id for iris 640 mentioned in the dortania display config article. And now I can boot with his SP5 EFI & I had multiple manual restarts. So for now, it seems to be working fine. Thank you very much. Now the issue is, my external hard disk is not accessable neither on macos nor on windows. It is showing in device list in both devices, but unable to access the files. My entire backup (files) is in it. I know it is off topic, but your experience can help me in this
@alappatsj glad you are making progress.
USB issues is almost always USB mapping and power patching issues. I'm guessing that repo isn't as polished as they said in the repo.
First think I would try is resetting NVRAM from OpenCore by pressing the spacebar and selecting the reset NVRAM icon. Depending on what is in that EFI it might not be available which would mean you should add it. You can add that tool by downloading the same version of Opencore and copying it to your EFI and then adding that tool entry to your config.plist.
If that doesn't fix it and because the issue is happening in Windows you may want to patch your own USB ports manually after a cold boot and booting direct to Windows. This means you may need to remove OpenCore temporarily (move to usb drive so you can still get back to macOS).
Booting windows after cold boot can clear junk that can cause issues that is stored in NVRAM. You can use this tool to map your ports in windows. You will need to output the kext and also need its associated kext linked in that repo and place in your EFI. Don't forget to also add those two kexts to your config.
If neither of those options work I am unsure what would be the issue. That said I'm 99% sure one of those will fix your issue.
closing due to lack of activity. If additional help is needed please reopen