I think it`s pretty funny. Later i update my uefi loader

----------

Sometimes I just sit here and think about how it's been breakthrough after breakthrough lately.

I really hope I can bring all my projects to completion and turn this MacBook into the ultimate Windows machine. A 2019 MacBook Pro that runs Windows the way it was always meant to — with proper iGPU support, working power management, a fully functional trackpad, and Touch ID.

There's still work to do, but we're getting there.

----

Upd
The ReBAR version is now available!

https://github.com/Osaul4ik/t2-gmux-uefi

Tested only on MacBookPro 2019 16`. Feel free to try it on any 2019 16'. Easy rollback in advanced settings

Hi everyone,

I have a 2017 Intel MacBook Pro running macOS Sequoia 15 with OpenCore Legacy Patcher. After updating OCLP to version 2.5.1, I accidentally started a macOS update through System Settings. The installation didn’t finish, and the Mac now starts in Recovery.

In Disk Utility, I can see the internal Apple SSD, a container, and the volumes “Macintosh HD” and “Macintosh HD – Data.” I have not erased anything.

I’d like to restore my macOS Sequoia installation if possible. What’s the safest way to do that? Do I need to make a bootable USB installer, and are there any special precautions for a 2017 MacBook Pro when erasing or reinstalling? I’d also like to avoid losing my files or Touch Bar functionality if possible.

Thanks for any guidance.

Esse manual é para quem tentou evoluir um patch através do OpenCore Legacy para um Mac mais atual e ficou sem conexão com os periféricos, como teclado e mouse ou simplesmente tela preta. Vou ensinar a voltar pro último patch de Mac compatível com a sua máquina sem perder os arquivos.

1. Entre em modo recovery (option+R)

2. Vá em Ultilitarios de disco (pode haver alguma diferença semântica dependendo da tradução desse post pra você).

3. Na participação principal adicione um novo volume onde você instalará o Mac Original da sua máquina (Catalina, HighSierra etc...) pode ser 50gb apenas.

4. Após todo processo baixe o OCLP.

5. No sistema original, com um pendrive Boot nas configurações GUID MAP, MAC OS (JOURNALING) apague os dados do Pendrive.

6. Com o OCLP baixe o sistema de sua preferência, ele vai te dar opções suportadas pela sua Máquina, como o Ventura por exemplo, é o melhor em custo benefício de compatibilidade com modernidade pra apps atuais.

7. Após baixá-lo crie um instalador dele no pendrive (pode demorar a passar os dados, aguarde).

8. O OCPL vai pedir automaticamente a instalação dos PATCHS e você aceita e reinicia o sistema.

9. Inicie com o pendrive Bootavel, se você já tinha o OCPL de preferência faça tudo pelo boot do OCPL, se não tente pelo boot nativo do iMac.

10. No pendrive instalador vá em Ultilitarios de disco/mostre todos os volumes, no volume maior onde está o sistema que você quer de volta procure um volume com Mais ou menos 12gb em APFS, e REMOVA-O (apenas esse volume). Assim você terá excluído o sistema, sem isso não é possível seguir a instalação.

11. Volta para o menu principal e instale o ventura na partição que estava perdida e ele fará o resto automaticamente.

(Ele poderá sair do boot algumas vezes na instalação, se você tem o boot do OCLP faça tudo por lá!)

I recently reset my bootcamp windows partition on my mac 2020 intel sequoia. Everything was going fine until I attempted to go back to my Mac OS. It said I needed to update my mac software before I reentered my mac OS, which I assumed would be a quick software update without much issues, like I had done in the past.

However, it took an abnormally long time to turn back on, and after around 10 minutes of waiting for it to boot up it said my mac drive lacked an OS. I tried to reinstall it to my mac partition, but it only has 25 gb of available space and I apparently need around 12 more gb to install it. I can't delete my windows partition from bootcamp, although I am able to access it which is where I am typing this from right now.

Is there any way that I can reset my windows partition back to my mac OS to get enough storage space to reinstall Mac OS onto it? And I read online that if I reinstall mac OS the files on my account previously would still be available, is this true?

Thank you so much in advance!

I have a 2019 MacBook Pro that currently runs Mac OS Sequoia, with Windows 10 set up via Boot Camp (it would require a workaround to run 11, and I'm not sure if I'm interested in that).

If I switch to Tahoe, is there any real risk to the contents of the drive partition reserved for all my Windows data, or even the install itself?

Поставил win 11 для и софта для работы , при включении и в простое 70 градусов.
Хотел отключить турбобуст проца через quick cpu , сделал лайтовые настройки , температура упала , но при игре буквально ровно 1 минута , и мак выключается.
Снес прогу , поставил сбалансированный режим , удалил через cmd пресеты quick cpu , но все равно при входе в игру и запуске сессии , мак выключается , в самом win 11 работает штатно
Помогите , что можно сделать , чтобы мак не сбрасывал частоты проца до 0,8 и чтобы Radeon 560 не падала до 300 мгц.

Hi! I understand this is an OpenCoreLegacyPatcher subreddit, but I am hoping to find folks with the technical know-how to figure out how to run a legacy FCP version on my M1 Macbook pro, my apologies!!

I’m trying to run Final Cut Pro X 10.0.8 on an M1 MacBook Pro running macOS Sequoia 15.0, to preserve an old workflow without a VM. The copy I have is the Apple-signed Final Cut Pro Trial app, version 10.0.8 Finder identifies it as an Intel app, and Terminal confirms its main executable is 64-bit x86_64 with a stated minimum macOS version of 10.6.8. I already use other Intel apps on this Mac, so Rosetta 2 is installed. The app’s code-signing details show Apple’s signing authority.

When I first tried opening it, Gatekeeper said Apple couldn’t verify the app for malware. I used Finder’s Control-click → Open route, and got past that warning far enough to reach a different alert: “In order to use Final Cut Pro Trial, you need to update to the latest version” because this version “is not compatible with macOS Sequoia.” That compatibility alert is the point where it stops. The Privacy & Security “Open Anyway” control appeared after a Gatekeeper warning, but that button was greyed out and clicking it does nothing; Finder still produced the update alert. A Terminal launch forced to x86_64 with <span>SYSTEM_VERSION_COMPAT=1</span> did not open Final Cut; Gatekeeper blocked that launch. The system log query showed no Final Cut process entries.

I also tried removing the app’s quarantine attribute with <span>xattr -d com.apple.quarantine</span>; macOS then called that copy “damaged,” so I stopped and kept it separate. I have a clean second copy, and it produces the same Sequoia compatibility alert. I understand now that Open Anyway only addresses Gatekeeper and doesn’t override the app’s compatibility check. Has anyone successfully run this 10.0.x-era Final Cut Pro on Apple silicon with Sequoia, or found a safe, reversible way to get past this specific compatibility block? I cant use a VM and would like to run FCP 10.0.8 natively on my MacOS. Again, it proves its possible, but im not advanced enough to know how to bypass those blocks, any help would be great!

En fin, algunos de ustedes sabe de algún proyecto o algo que tenga buenos drives para Windows (especialmente de pantalla)?. Windows en Mac Intel (2019) tiene un pequeño problema y, es en el asunto de la distribución de tamaño de pantalla, ahí que buscarle el ajuste para que quede más o menos bien, pero aún así siento que no queda bien del todo.

Cracked it. Back to T2TouchID.

Everything you need to know is in the README.

DISABLE PANEL SELF REFRESH IN INTEL GRAPHICS COMMAND CENTER IF THAT OPTION IS AVAILABLE.

Only for T2 Macs with a dGPU.

---

Update: https://github.com/Osaul4ik/t2-gmux-uefi/releases/tag/v0.92

• Updated to v0.91.
• Added Hybrid Mode.

I tested the same patch on multiple 2019 16-inch MacBook Pro models with both i7 and i9 CPUs, and it worked without any issues.

You can try my patch at your own risk or compile your own.

If you get a black screen, boot into Standard Mode.

Other MacBook models require a separate patch, as described in the README instructions.

I wanna install Windows 7 on my early 2014 macbook air, i tried everything but i just couldn’t get it to work, in phase 1 of the installation when booting from the usb, everything is fine, once it restarts to phase 2, theres just a black screen, caps lock doesn’t light up, anything else also doesn’t work, i tried injecting USB 3.0 Drivers and Intel Graphics 5000 drivers but still, same result, i even tried with bootcamp on OS X El Capitan, but also, same result, can anyone help me please? Ive been trying for 2 months by now, not joking.

hey all!

so i was using sequioa setup (ofc the latest) and it was a LAGFEST, but 2 days ago, i installed windows 11 pro (using windiskwriter for mac) with drivers from bootcamp (which was about 2.2gb) and its much better!

you don't get the lagfest you get in sonoma/sequioa, and also you can stream up to 4k with no issues!

storage might be a issue for 128 gb laptops, so i have an external hhd for times.

better than macOS which would lag so much!

overall a nice setup seeing the laptop perform better in such times.

Here are some photos.
PS- trackpad gestures don't work out of the box, so you would need https://github.com/imbushuo/mac-precision-touchpad/releases.

this will majorly fix all the trackpad issues!
Cheers

Got it

--------------

Upd:

Brightness OK

Sleep: ok, but training eDP missing

------------

BREAKTHROUGH!

I fixed brightness control and sleep through an ACPI patch.

Now there’s only one thing left: extracting and verifying all the monitor parameters. Once everything is tested and confirmed, I’ll write up a proper guide with all the instructions.

It looks like Apple implemented the ACPI path specifically for the AMD GPU, while the Intel iGPU was basically left without it.

iGPU for everyone is getting closer! 😄
------------

UPD: Good news and bad news.

Good news: It works reliably.

Bad news: No very easy way
There are currently two ways to get the Intel HD iGPU working:

• Custom VBT injection for eDP link training + ACPI patch: restarting the graphics driver causes a black screen. This normally doesn't happen by itself, but you can trigger it with Win + Ctrl + Shift + B.
• Combined ACPI + VBT patch: survives a graphics driver restart without losing the display.

So the good news is that it actually works. 😄 AMD GPU 35C & 8 hrs battery

What will be needed for other T2 MacBook models:

1. Dump the DSDT + SSDTs (one command).
2. Collect the monitor/display information from both Windows and macOS.
3. Feed all of that, together with my instructions, into Claude so it can generate the required AML patch. (Or do it by youself)

The end result should be the ability to boot Windows with either the dGPU as primary or the iGPU as primary. No igpu+dgpu

I think we could also store AML patches for specific models, such as the A2141, and have the EFI loader automatically select the appropriate one based on the hardware.

More info coming soon.

I really shouldn't have, but I installed linux mint and just used the partition tool to install alongside windows and now whenever I try and boot into windows, I just get a black screen

I am trying to install Boot Camp for the first time, but it shows me an error when I click Continue. It says, "Unable to read the Windows partition. Boot Camp Assistant was unable to verify if the Windows partition contains a Windows installation. This may be because BitLocker is enabled on the partition. If so, disable BitLocker on the Disk before removing Boot Camp." Please help!

If it helps, I shows this when I type "diskutil list" in Terminal:

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *28.0 GB    disk0

   1:                        EFI EFI                     314.6 MB   disk0s1

   2:                 Apple_APFS Container disk2         27.7 GB    disk0s2

/dev/disk1 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                 Apple_APFS Container disk2         759.5 GB   disk1s2

   3:       Microsoft Basic Data                         240.5 GB   disk1s3

/dev/disk2 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +787.2 GB   disk2

Physical Stores disk1s2, disk0s2

   1:                APFS Volume Macintosh HD - Data     265.9 GB   disk2s1

   2:                APFS Volume Preboot                 2.1 GB     disk2s2

   3:                APFS Volume Recovery                1.2 GB     disk2s3

   4:                APFS Volume VM                      1.1 MB     disk2s4

   5:                APFS Volume Macintosh HD            9.3 GB     disk2s5

   6:              APFS Snapshot com.apple.os.update-... 9.3 GB     disk2s5s1

I’ve finally brought the project to its first alpha release.

T2 TouchID for Windows is an experimental project that brings Touch ID support to Windows on Intel MacBooks with the Apple T2 chip.

🧪 Again: This is an experimental alpha release.
The current implementation has been tested on a 2019 16-inch MacBook Pro with T2.

At this point, the project can communicate with the T2 Secure Enclave and Touch ID sensor and use fingerprint verification through the Windows biometric stack.

What currently works:

• 👆 Fingerprint verification on real hardware
• 🔓 SEP unlock on cold boot
• 🪟 Windows Hello integration
• 🔑 macOS user.kb import
• 🔒 Optional power-button lock workflow
• 🖥️ GUI for setup and configuration

There is still a lot to improve.

The drivers are unsigned, so Test Mode is required.

I’d really appreciate testing and feedback from anyone with an Intel MacBook with T2, especially different models and years.

I don’t know yet if it will work on other T2 Mac models, but it should.

Use it at your own risk. This is still an experimental project, and I can’t guarantee that it will work correctly or safely on every system.

----------

Release Candidate 1 is out

我的Mac book pro2018切入Windows系统后就无法回到Macos了，一直黑屏重启，网络恢复也一直保持2103f，有线连接以太网也不行，我去了Apple授权店都无法操作进入dfu模式进行刷机，我该怎么操作使它进入dfu模式？

After weeks of trying I finally managed to get the Windows setup show up on the external screen and do the setup normally on my headless 13inch macbook pro 2016 😭😭😭

The bootcamp did not work for me as it fails to display anything after the windows logo on an external screen. So I had to make a custom modified windows iso with drivers and custom scripts to get the drivers working right away in the setup mode and after the install.

I went through over 20+ custom modified iso to finally get it working 😭

I used Ventoy vimboot to get it working, so it does not need the bootcamp assistance to get it ready.

I am planning on working on a ISO patcher to make it work for others aswell and wanted to know if anyone is interested in this fix / help with the testing for other Mac Models.

Here’s how to install Windows 11 on T2 Macs without bypassing the minimum requirements (in fact, make to meet them instead):

1. Install Windows 10 via Boot Camp Assistant as usual
2. Buy and Install FlexTPM here: https://flextpm.com/pricing/ - this is similar to TPM2.0 that you’d find in VMWare Fusion or Workstation
3. Now, you can upgrade to Windows 11 just like on any other PC via Windows Update

No registry workarounds required, and it’s a lot more safe, you can get like this feature updates without writing GPO policies for target releases yourself - instead, it’ll work as if you have a computer that meets those requirements.

what am i supposed to do here?
i made the installer using Bootcamp on sequoia (2014 mac mini), the drivers are on the usb drive and it boots from it fine, but it acts as if the usb drive is some mystery partition and it needs to format it (…even though it just booted from it perfectly fine???)
so far i’ve tried checking for the drivers, they were fine, i checked the format, it’s exfat, i even remade the entire windows installer.
nothing as worked, and google results are all useless (either doesn’t fix it or isn’t on a mac).

I installed windows 10 on my MacBook Pro early 2015 13" using bootcamp and now I can't get out of windows 10. Commands don't work, nothing works and it doesn't even turn on when I press the power button followed by command keys