Jump to content
5539 posts in this topic

Recommended Posts

v11.6 installed perfectly fine with OS v0.7.3 based on @eSaF config.

image.png.3e8ff04e47fc8ed8d91609bd0c24cad7.png

Edited by panosru
  • Like 2
On 9/13/2021 at 7:56 PM, panosru said:

v11.6 installed perfectly fine with OS v0.7.3 based on @eSaF config.

image.png.3e8ff04e47fc8ed8d91609bd0c24cad7.png

 

Hi I have the Same configuration for my hackintosh but unfortunately i fail to update. Can you please share your EFI? Thanks in advance

Edited by nikhil96widhani
2 minutes ago, nikhil96widhani said:

 

Hi I have the Same configuration for my hackintosh but unfortunately i fail to update. Can you please share your EFI? Thanks in advance

 

  • Like 1
On 9/14/2021 at 2:56 AM, panosru said:

v11.6 installed perfectly fine with OS v0.7.3 based on @eSaF config.

image.png.3e8ff04e47fc8ed8d91609bd0c24cad7.png

 

Can actually confirm that it worked like a charm for me as well, with a few minor modifications for my setup.

@eSaF thank you for the great work and for making me understand how to work on my EFI for future reference.

On a different note, I remember you mentioning that the same EFI works on Monterrey as well. Would any big changes need to be made for the new OS or is it plug&play?

  • Like 1
44 minutes ago, eSaF said:

I will assume you have a gigabyte z390 Pro, Master or Pro wifi as you haven't filled in the Specs of your machine in your profile as mandated. You can try the EFI Folder in its entirety and just fill in your S/N etc, etc or if you have specialised SSDT files pertaining to your setup, you can copy those over instead after discarding mine and also make the change to the config.plist to reflect your SSDT files.

 

Sorry about that I have :
System - Motherboard: Gigabyte Z390 AORUS PRO, CPU: Intel i7 8700k, Video Card: AMD RX580, RAM: 32GB, WIFI: FENVI T919

 

I have built the EFI and i am trying to test it off a usb drive but cannot make it to work. For creating the pendrive i formatted a pendrive with fat32 format and then pasted my EFI in it. I rebooted and press f12 to select usb but i done get my system boot from it Am i missing anything in terms of making an EFI test pendrive?

Edited by nikhil96widhani
6 hours ago, eSaF said:

@nikhil96widhani - Ok it all depends on how your BIOS is set up also what version. With your specs if your BIOS is setup correctly, you shouldn't be having that kind of trouble booting off the EFI Partition of a correctly formatted USB Drive. I think at the beginning of this Thread or some where about, @AudioGod listed the BIOS settings required to boot, run or install OS X. Have a look and compare your settings again incase you missed something. Good luck.

 

Hello,

I spent whole day trying to boot but i am unable to make it work. I changed serial number and other details for the new efi provided by you but cannot figure out what is wrong. One thing i found is that my old EFI has kext for wifi but i don't know if just need to copy that kext over to new one. I am uploading my 2 efi old and new if you can review them and help at your convenience. the one tagged as OLD efi is being used with Mac Bigsur 11.2.1 right now with 12k bios version (MSR unlocked and audio gods settings done). We have similar system but mine motherboard is non wifi and i have fenvi wifi added. 

 

below is the link which has my old working efi and new one and i am sending you the password to access the file by message

https://cloud.nikhilwidhani.com/s/7ypmfRcqRYKpEYf

i could attach my efi here but everyone says its not safe so i will share password with @eSaF and @AudioGod  in message.

 

System - Motherboard: Gigabyte Z390 AORUS PRO, CPU: Intel i7 8700k, Video Card: AMD RX580, RAM: 32GB, WIFI: FENVI T919

 

I thank you in advance, please help me if you can :) 

Edited by nikhil96widhani
On 9/8/2021 at 1:20 AM, eSaF said:

@xtddd and @unknownharris - Guys follow my example in this EFI Folder. Everything is updated including all kexts, I have removed all my personal data so you'll have to furnish it with your own. The changes in the released .0.7.3 is as shown and must be enabled for the GUI to be shown and the Boot to be successful. One more thing do not use any files from your previous EFI Folder apart from your personal data. Good luck.

Just to add and to avoid confusion, Your SSDT Files can be carried forward, your Mapped USB kext can be carried forward all other kexts should be updated to the latest versions.

  Reveal hidden contents

1504872498_Screenshot2021-09-08at05_09_36.png.c959c8f22f04111c7a89fef41072600a.png

 

EFI.zip 50.82 MB · 45 downloads

Thanks for this!  Everything went well in the update after adding my own info to the EFI.  I added the AirportBrcmFixup.kext as my wifi speeds were a little slow (to see if that will help), but everything else seems to be ok with boot up.  I did a "Find Differences" using BBedit and there was a few things were picked up from the original I had, but likely due to the update as everything is working. 

17 hours ago, eSaF said:

@mariodj - See attached and carefully copy all that is shown in the box, also enable Internal Graphics in the BIOS as well should be ok.

  Hide contents

1073197292_Screenshot2021-09-16at21_34_19.png.5fcaf2bcdb7f77b83e0c2baae6f9f916.png

 

But this add is already in your EFI, after boot i got green screen.

1 hour ago, eSaF said:

What Mac Model is your machine also did you alter the settings in the BIOS for internal Graphics only and save, are you running the latest BIOS version for your board? I don't know how much difference that makes but the EFI Folder is based on Mac Model 19.1 plus Gigabyte BIOS version k.

i compare your EFI with latest from our God Audiogod , do some small changes and it works now :)

 

  • Like 1
34 minutes ago, AudioGod said:

If I have the time I will try to put up 0.7.4 EFIs for you all when it releases. No promises though but I will try to get it done. 

Please do this every Christmas :)

  • Haha 1
34 minutes ago, AudioGod said:

If I have the time I will try to put up 0.7.4 EFIs for you all when it releases. No promises though but I will try to get it done. 

Very very good!!! 

On 9/16/2021 at 3:51 AM, eSaF said:

Ok I will take a look and see what the problem is.

All done check your inbox.


i want to thank @eSaF he went beyond and above to help me and get my hackintosh working again. I learned a lot as he helped me. So i want to thank him. Also thanks to audiogod :) 

  • Like 3

I am needing a little help.  I am having trouble accessing recovery mode from boot, is there a simple way to do this?  I am dual booting with windows so I have an OC selection screen at boot up between Windows and MacintoshHD, but no matter how quickly I press command R I cannot seem to access recovery at boot.  That goes for resetting pram as well via Winkey, ALT, P,R.  Do I need to adjust a setting in the EFI config?

 

Mainly attempting this to disable CSRutil for a cycle to delete a defunct but stubborn system folder in the trash.  I can't disable csrutil it in Big Sur via sudo commands in the terminal

 

Update:  Search is working and found the answer earlier in this thread.  SPACE Bar at OC boot screen.

Edited by Hifi33
clarifying not booting into Windows while attempting this.

Just going to check in with the more knowledgeable people on the board... My Win10 installation needs a major update, and since my internet is bit slow, I'm plan to do an "upgrade in place" with the offline installer. I've had a couple of issues upgrading Windows with my old P55 Hackintosh when I had MacOS on a separate drive:

  1. Installation fails unless I disconnect the other SATA storage devices, or...
  2. The installer puts the Microsoft EFI on Mac formatted drive instead of Windows.

To avoid these problems I'm thinking of trying the following:

  1. Disable all SATA ports in BIOS, except Windows of course.
  2. Change the boot order to make sure Windows drive boots without touching the Mac drive's EFI.

MacOS is on the m.2 drive, and I don't see a way to disable it in BIOS. I'd like to avoid physically removing it, since it is inconveniently blocked by the video card.


Any opinion on my approach? Any potential pitfalls I might be missing? Thanks for any advice you might have!

 

On 9/20/2021 at 3:27 AM, eSaF said:

@Project 2501 - Hi it is a pity you can't isolate the OS X disk by removing it as Windows has a habit of trying to be the dominant OS in a multi-booting system and could corrupt the data of the other. You could try and isolate/disable the OS X drive in the BIOS and make Windows the first and only boot disk then do the upgrade/install like that hoping nothing will touch the other OS X disk then when done bring it back in to play as before. Good luck.

 

Well, I can physically remove MacOS, but would need to remove the video card first... a relatively minor inconvenience, but I'm in a tight space without a lot of working area. I would have to unplug everything, pull the tower off the desk, remove the video card, remove the m.2 card, reverse the process, then repeat to get it all done. I'll just have to reserve more time to do the upgrade I guess... maybe during Thanksgiving Holiday (USA).

 

Another option is just to manually transfer the Microsoft EFI back to the Windows drive; assuming the Windows installer doesn't mess up the boot sectors (Win7 didn't). Windows put its EFI in a separate directory, so it can co-exist; it's just that Windows becomes dependent on the MacOS drive being functional. So if something happens to the m.2 drive, I can't boot Windows.

 

Is there a way to disable the m.2 slot in BIOS like the SATA ports? I looked for that setting, but I couldn't find it anywhere (F12j).

 

Edited by Project 2501
On 9/20/2021 at 12:30 PM, eSaF said:

One way of doing it without dismantling the rig, go into the BIOS and choose 'Boot Option Priorities' and highlight the M.2 entry that has OS X installation, hit enter on the keyboard that will bring up a few more options, choose disable then save and hopefully that will isolate Windows from corrupting OS X in the process. When the Windows upgrade/install is done, go back into BIOS and 'Boot Options Priorities' again and enable the M.2 disk and make it the first in line disk to boot then save. All should well.

 

Yes! I was looking all over the place for this. I thought it would be under I/O settings where you could disable SATA ports. I never thought I would need to drill down the boot order settings.

 

I'll still choose a day when I'll have extra time to fix any problem that might pop up, though...

 

  • Like 1

 

On 9/20/2021 at 6:27 AM, eSaF said:

@Project 2501 - Hi it is a pity you can't isolate the OS X disk by removing it as Windows has a habit of trying to be the dominant OS in a multi-booting system and could corrupt the data of the other. You could try and isolate/disable the OS X drive in the BIOS and make Windows the first and only boot disk then do the upgrade/install like that hoping nothing will touch the other OS X disk then when done bring it back in to play as before. Good luck.

I've done this before with varying degrees of success.

3 hours ago, pkdesign said:

 

I've done this before with varying degrees of success.

 

I'm hoping that by running the installer within Windows, it will prioritize updating EFI on the Windows drive, even if it somehow detects the MacOS drive after taking "precautions". If something goes wrong, I at least hope that it doesn't mess the boot sectors. Of course, I'll have the bootloader on USB flash drive just in case.

 

 

hi friends,

 

12.0 beta 7 is out and we are able to update via "wrong" SMBIOS but still my sys suffers from Bluetooth Wake from Sleep errors.

Since beta 6 the natively supported BCM96430CS2 returns disconnected from Sleep  -  only a manual restart of the bluetoothd daemon helps (or via slider off/on)

 

Someone here with same issues and having an idea how to resolve ?

 

Thanks and cheers

 

 

Edited by texem
×
×
  • Create New...