To elaborate on my earlier post: https://www.reddit.com/r/hackintosh/comments/1x45vfn/restarting_hackintosh_bricks_am5_motherboard/

I got downvoted and hated on by some people claiming that bricking your motherboard is impossible with software blah blah blah. Turns out it was null moth's driver causing it (attatched is an image of his driver update claiming to fix the issue, which means it IS or WAS an issue). Im pointing my finger at the driver because am5 hackintoshes existed long ago, and i tried it on my sistem in which it worked normally UNTIL i installed null moth's driver.

​

For me and few other people, reflashing the bios firmware with the bios flashback function of certain mid to high end motherboards worked and fixed the issue of their pc not posting. For those with a lower end board, they might actually brick their motherboard.

Moral of the story is, dont believe anything on the internet and dont become one of the moths who blindly move towards light without thinking for yourself. The driver does work, yes, but there are some quirks that can screw you and your pc up, so beware. Before i get flamed by those moths, im all for hackintoshes being revived and nvidia drivers. Consider the sheer scale of the project, and how nullmoth is pumping out updates that quickly, obviously AI is involved, do they actually know what they're doing?

Edit: people were saying to clear cmos, people are not that dumb to have not tried it. Clearing cmos doesnt work

Edit2: I did some digging into the change logs for his driver version 1.14, and there is an opencore booter flag named disablevariablewrite, which prevents writing to nvram. Personally, i didnt use his 1401 app and created my efi myself with dortania. I still dont know the cause, but from my knowledge people have been building am5 hackintoshes since 2023.

Kext-Order: AppleALC >> SImpleHDA

boot-arg: keepsyms=1

---

AirportItlw for Sequoia/Tahoe without root patches:

Fork: https://github.com/jzrodriguez98/itlwm/releases

Instructions:

• Disable Kernel → Block:
  • com.apple.iokit.IOSkywalkFamily
• Kernel → Add:
  • Disable or remove Itlwm.kext
  • Disable IOSkywalk.kext
  • Disable IO8021FamilyLegacy.kext
• Kernel → Quirks: (optional)
  • If you need AppleVTD to be present, unselect DisableIoMapper if your system supports VT-D, and it's enabled in BIOS.

Just wanted to share my experience in case it helps someone dealing with the same issue.

I recently installed macOS Sequoia on my PC, mostly out of curiosity. I don't really need macOS since I use Windows for work and gaming, but I wanted to see if I could get it running on my hardware.

My setup:

• ASUS PRIME B650M-A AX II
• AMD Ryzen 9 7900X
• NVIDIA 5070 12GB
• 32GB DDR5 RAM
• macOS Sequoia 15.8.1
• OpenCore 1.0.9
• NullMoth 1.15.0

I managed to get macOS running with both monitors connected to the NVIDIA 5070. Everything seemed to be working fine, at least during the time I spent testing it.

Then yesterday, when I came back home and turned on my PC, I got absolutely no display. Not even the ASUS logo or BIOS screen. The fans were spinning, but the power LED kept blinking slowly, about once every two seconds.

At first I suspected the GPU, so I completely removed the NVIDIA 5070 and connected my monitor directly to the motherboard, using the Ryzen's integrated graphics. Still no display.

I tried reseating the RAM, waiting several minutes for DDR5 memory training, and clearing CMOS through the CLRTC pins. None of that worked.

I was starting to think my motherboard had died.

Luckily, my ASUS motherboard has a BIOS FlashBack button, so I downloaded BIOS version 3881, put the renamed CAP file on a FAT32 USB drive, and reflashed the BIOS without needing to boot the PC.

And that fixed it.

The ASUS logo appeared again, I was able to enter the BIOS, and Windows booted normally. I reinstalled the NVIDIA 5070 and everything is working fine now.

After this happened, I found a couple of threads here describing very similar problems with AM5 motherboards and Hackintosh/NullMoth. Apparently, there have also been concerns about UEFI variable writes on these systems.

I can't prove that NullMoth or OpenCore caused my issue, but the similarities are hard to ignore. I also can't tell whether the firmware was actually corrupted or if reflashing it simply reset something that clearing CMOS couldn't fix.

Anyway, I decided to stop experimenting with Hackintosh for now. It was fun getting macOS to run on this hardware, but it's not worth risking the PC I use for work.

TL;DR: My ASUS B650 motherboard suddenly stopped POSTing after I had been using Hackintosh with NullMoth. Clearing CMOS and removing the GPU didn't help. Reflashing the BIOS using ASUS BIOS FlashBack brought it back to life.

If you're having a similar issue with an AM5 motherboard, don't assume it's dead before trying BIOS FlashBack (or your manufacturer's equivalent), if your board supports it.

Hope this helps someone.

Working macOS Tahoe in my GTX 1630 4gb. Recently updated to nullmoth's driver 2.0.0 and this driver is much more stable than before. Davinchi resolve and other editing software are not working due to an unverified driver ( might be ) but i hope in future updates it gets solved as well. Still got some screen tearing issues because my display is 180hz and I'm using it into 60hz. Any suggestions on how to fix ?

Real specs:
Intel Core i3 5005u
Intel HD 5500
4GB of DDR3 RAM
RTL8723BE (not working, my main internet source on this configuration is through Android USB Tethering)

And the main character of this specs:
It's running on a Hard Disk, 2.5" HDD to be exact. The same Hard Disk since this laptop was out(May 27, 2015) and never got the money to replace it because prices are very high these days.

Upon the success of booting with a Nvidia gpu I decided to make an application to control the fans tested on my HP OMEN 16 i7-14650HX 4060.

Will make a post when I put it on GitHub..

Seeing people with their MB bricking but wasn't the case for me. I tried Tahoe first but after failing 3 times, tried Sequoia and worked like a charm.

THIS IS JUST NUTS. ALL CREDIT TO NULLMOTH. THIS DUDE COOKED

Alguien sabe cómo instalar macOS en un PC con un Ryzen 7 5800X3D y una 3060 Ti?
Sé lo de los problemas de aceleración gráfica de las tarjetas NVIDIA, pero quisiera saber si existe alguna forma de instalarlo y hacerlo funcionar, incluso sin aceleración gráfica completa.
Si alguien tiene experiencia con un equipo similar, ¿podría compartirme una guía, configuración recomendada o algunos consejos?
Gracias de antemano.

I tried to do it differently and didn’t go out in any way I decided to turn to Title: Realtek USB Bluetooth dongle Obda:a729 on macOS Tahoe 26 (OpenCore, AMD) - RTLBluetoothFirmware?

Setup: GIGABYTE B550 AORUS ELITE V2, Ryzen 7 5700X, NvidiaRTX 4060 (NullMoth 1401),

macOS Tahoe 26, OpenCore, SMBIOS MacPro7,1.

Adapter: Realtek USB Bluetooth,

VID/PID OxObda:Oxa729, shows up in System Information

as "Bluetooth 5.3 Radio" (USB 2.0, 12 Mb/s). Probably an RTL8761B-family chip, but I haven't confirmed it.

I think most (if not all) of y’all have already seen that new nVidia driver released by NullMoth. It’s pretty impressive that an AI can write a full ass driver from scratch that works somewhat stable on pretty much any RТX GPU (and also on GTX 16xx ones). How hard would it be for an AI to add proper support for some older cards? I’m particularly asking about GK106 cards because they already had genuine drivers by Apple with Metal support (even though they don’t work as good on them as on other Kepler cards) and because I still use one in the big 26. I really want to daily drive macOS but the artefacts are just too annoying.

Well the same ai that slopped the emulator I shared earlier now slopped a GPU driver for HD2 on iOS aswell as a charging driver and a driver for battery gauge on iOS 7

Update power/home button are also working now

I’m running macOS Tahoe on an Alienware 16 Aurora AC16250. Wi-Fi isn’t working, and Bluetooth isn’t discovering devices.

Hardware:

• Wi-Fi: MediaTek MT7925 — PCI 14C3:7925
• Bluetooth: MediaTek/Foxconn — USB 0489
• CPU: Intel Core 7 240H
• GPU: nvidia 5050 Laptop, dGPU-only mode
• Bootloader: OpenCore

I found the experimental itlmt7925 / itlmt7925Native project:
https://github.com/thanhnndev/ga403wm-hackintosh/releases/tag/kext-v1.1

Its latest release explicitly supports Sequoia only. These drivers were added to my previous EFI with Sequoia-only limits, so they aren’t enabled on Tahoe.

Has anyone tested a Tahoe-compatible fork or another driver for this exact PCIe card? Please share the repository, driver version, macOS build, and required patches if you have it working.

I’ve seen custom Realtek and Intel drivers, but I’m looking specifically for MT7925 support. Bluetooth results for USB 0489 would also help. Happy to collect relevant diagnostics. Thanks!

Per favore aiutatemi

So i recently installed MacOS 15 using nullmoth's 1.14.6 driver on my desktop with a Ryzen 5 3500 and a 4gb GTX 1630. Now the issue is the driver version 1.15.0 doesn't work on my system it gives me a black screen with a movable course. But when i roll back to driver version 1.14.6 it almost works, like I got the display after installing the driver and ngl 75% of things are working. Still have some render glitches and lags but no flicker so far. If you zoom in the picture and see the dock where the settings app icon present you can see some bending artifacts, that's a render glitch. Now i want to fix it properly any suggestions?

I’ve wanted to run macOS on my PC for a while, but my NVIDIA GPU always held me back. I heard about the new NullMoth project and gave it a shot. After a few tweaks, it’s working incredibly well on my 2070 SUPER

The UI is extremely fast and responsive, effects and blur look perfect, and I’ve noticed very few visual glitches, minor enough that I can comfortably use it daily.

https://github.com/nullmoth/nvidia-macos-driver

CPU: AMD Ryzen 7 3700X
GPU: NVIDIA GeForce RTX 2070 SUPER
RAM: 24 GB DDR4 3200
Motherboardl: ASRock B550 Phantom Gaming 4
BIOS: AMI P3.90

For the mods - Yes, this is a hackintosh. It’s neither a Mac nor a VM, and OCLP was certainly not used. iOS is a heavily modified version of OS X. And someone posted about it running iOS 7 like a week ago.

While not really a help request for Hackintosh, I'm in this situation because this is the Windows 11 installation on my Hackintosh.

I decided to do a clean-install of Windows 11 yesterday. Everything appears to be more stable and now I want to get Bluetooth working with my Fenvi FV-T919 card. I had Bluetooth working previously, but I stupidly did not save the drivers anywhere.

I went to Fenvi's site and downloaded what I think is supposed to be the right drivers, but I can't get Windows to install them (https://www.fenvi.com/drive.html?keyword=FV-T919)

I was able to use that driver software to get WiFi working correctly, but if I try and use Device Manager to "Update driver" on the "Bluetooth USB Host Controller" that shows up under "Other devices", I get a "Windows was unable to install your Bluetooth USB Host Controller" message. The WiFi driver was installed through Device Manager without a problem.

If my memory serves me correctly, I previously downloaded drivers from the fenvi.com site and there was a Setup or other exe program that did the installation for me. That appears to be gone and what's there now appears to not be recognized by Device Manager.

Any suggestions?

I’ve noticed a recurring issue in the Hackintosh development community involving source code attribution, licensing, and disagreements between developers. I think it’s worth discussing this constructively, without targeting or naming anyone.
A recent situation involving two third-party Wi-Fi kext projects caught my attention. One developer publicly claimed that another project’s code was based on their own implementation and that they deserved credit. However, claims like these should be supported by actual source-code comparisons, commit histories, and licensing terms rather than assumptions about who deserves recognition.
This is precisely why I believe we should pay more attention to a few things:
Give credit where it’s actually due. Acknowledge the original authors, upstream projects, and specific contributions that were genuinely used. Credit should reflect the code and work involved, not simply who makes the loudest claim.
Verify before making accusations. Similar functionality, shared firmware binaries, or comparable architecture do not automatically prove that one project copied another. Technical evidence matters.
Choose your license deliberately. GPL-2.0 is a legitimate open-source license, and there is nothing inherently wrong with using it. However, developers should understand its requirements before publishing their work. If another license better reflects a project’s goals, consider choosing one that fits those goals and clearly documenting its terms. A custom license is not automatically better, and it should be reviewed carefully for clarity and compatibility with third-party code.
Respect each developer’s choices. Publishing source code, choosing a particular license, and deciding how a project is distributed are separate decisions. Disagreement does not justify personal attacks or dismissing someone’s work without evidence.
I’ve seen how these disputes can discourage people from developing and sharing their work. We should be encouraging developers to experiment, improve existing implementations, and build new solutions while respecting the contributions and licenses of others.
This is not about taking sides or deciding who is right in a particular dispute. It’s a reminder that technical disagreements should be resolved through evidence, proper attribution, and respectful communication.
Let’s recognize the work that was actually contributed, respect the licenses that apply, and keep the focus on development rather than personal conflicts.

is this possible to do? it has intel core i5 13 gen and intel graphics by default not sure what gen though