Enlarge EFI, inject permissons, make it bootable from UEFI

[Full-R]

So ...

Stuck to use USB keys ...

Idea maybe again use something like mKEXT(if supported fallback in Tahoe maybe can use old system to puck extensions) or packed RamDisk from another partition.

Maybe any variant do that using attaching snapshot operation to boot.efi file and emulate hfs+ or apfs container in RAM because insufficient EFI size and no any permissions futures(that shit makes troubles).

 

 

In uEFI/BIOS there are no future to boot from EFI partition if size enlager.

 

P.S.: hardware dev's says about SSHD technology means to use for that HDD cache based on Solid Sate chip to use for small system but no one software and firmware developers attach thes solution. ha-ha ;D 

 

P.S.S.: and maybe variant to automatically put sign key for secure but via efi console??? guys says it's possible to replace PK key and forgive

 

Edited August 28, 2025 by Full-R

[Full-R]

xD 

Sorry ... Leave a forum because Over B*t*art happens with not positive end for some humans ...

 

Good luck with that's

[Full-R]

Fixed ...

A pay of feel self again an genius/idiot(gidiot) is a pain to loose all the data on my drive.

Steps:

1). Backup all.
2). Use Win11 Ghost USB with AOMEI P.E.
3). Make install to the full space of your drive.
4). Reboot to the P.E. and make delete all the partitions instead of EFI(maybe you can move 16mb MSR partition after enlarge EFI that is by MacOS is disk0s1 but it's not needed game for your brains).

5). Reserve a new partition for clean Windows 11 Ghost installation about 50Gb in NTFS.

6). Pre-place a one more partition for all free space in NTFS that you can use as APFS or HFS+ after Windows installed because macOS diskutil won't to understad how AOMEI partition software works with a disk space and crops all free space and macos filesystems to the void(few times look on my 256Gb SSD looks about 100Gb and no chances to recover).

7). When all the steps in AOMEI P.E. editor applyed your should install Windows on first partition after EFI, not to change anything and shutdown.

Be care with another partition wizards(seems Linux software very-very bad for works with cross systems).

8). Just use create install media terminal command to make MacOS installer. It can be [ BigSur ... Sequoia ](this tree have another versions of APFS containers and HFS formates and be care with DMG files sometimes can't be opened/readed). 

9). Apply Open Core EFI folder by copy files from another system to the USB with MacOS installer EFI partition and make change all you need like config.plist, add/remove drivers, tools and kexts.

10). Boot from USB into MacOS recovery installer and using disk utility make erase last NTFS partition "in the end" to HFS+ or APFS container that you can explode to separate volumes inside.

11). Using install MacOS just pick fresh created HFS+/APFS partition and install MacOS there.

12). When MacOS installation done's you can mount EFI and move Open Core boot files with Microsoft boot inside replacing a file name bootx64.efi to ms-bootx64 efi first.

I make enlarge size of EFI partition to 900mb and can play with some situations I need Windows boot for restoring some BIOS/UEFI settings to OEM and use Open Core to configure that's.

Trouble in a situation disk utility shows EFI partition in three variants FAT, FAT16,FAT32 and broke boot ability that every time your do something.

After steps we have one small error about EFI size is incorrect but it is not trouble.

Be care with a snapshots. Using tree-method be an animal and fix all the partitions inside all the containers deeper twice for all the containers on all the drives. We need do that to make backups success, files done to copy, delete, save a datas and performs APFS/HFS versions migrate before every reboot or shutdown. Take you banana and sleep in dreams next day you head not become to be a frozen ;)

We can put a lot of kexts, settings keeping Windows boot original and via Open Core and add a firmwares attached to hardware like Board-ID and some motherboard or periheral chips.

Usually this firmwares attached to EFI automatically when Open Core config.plist configured as well with trust options and enabled Dorge UEFI, Secure and AppleSecure boot futures when VT-D/VT-X enabled.

And placing needed kexts with installer boot before install is not need a OC GUI method. All kexts loaded aoutomatically while install done and you can apply any updates or installers from BigSur to Sequoia without any additional steps.

In some reasons this case makes SMC and sleep works better and MacOS can use some additional integrated feautures that hackintosh usually have not.

P.S.: hmm ... pain to remember how this trouble solved.

P.S.S.: Care look twice: seems works perfect. Good luck ...

 

[Full-R]

P.S.S.S:

To make Open Core bootable from internal drive use Easy UEFI applecation for Windows. Add new entry linked to OpenCore.efi into OC directory and reboot.

Some hardware(usually notebooks) not allow to pick it from BIOS and boot menu.

So. You free from USB stick.

Edited September 7, 2025 by Full-R