@Casey have you check-out Osy's repos at Github? There he talks about different aspects of Thunderbolt controller including ACPI related methods. I think he is very close...
Sometimes it's possible to force a UEFI/BIOS downgrade by forcing the motherboard to fail POST during boot. After this, the motherboard will try UEFI recovery process. In Asus it's call: ASUS CrashFree BIOS.
Asus motherboards will try to recover seeking the UEFI file in an USB2 drive or DVD...
It's still there, but without an user account it won't show-up. You would find it Online, by searching with the term: I225-Vmod . But some of these options are for Windows. If you dual boot it could work but not everyone is dual booting.
Just boot again with the same USB installer you used to install macOS and at the boot screen pick the partition where you installed macOS which is on another external USB drive.
Once you boot proceed to mount partitions and to copy EFI folder to the EFI partition where your macOS is located.
USB drives have a hidden EFI partition when you use the Guid Partition Map Scheme.
There are plenty different apps/tools that can help you mount your EFI partition including OpenCore configurators.
I use hackintool for this but use any one you prefer.
EFI mounter is available on this site...
Perhaps, after installing to your USB Drive you forgot to add your EFI folder with OC to your EFI partition. Your USB drive won't be bootable until you add the EFI folder into your USB EFI partition.
What's the size of your USB Drive?
If I'm correct, then mount the EFI partition of your USB...
You have two options when creating a USB macOS bootable installer:
Online installer, which is made with recovery installer image file (minimum size suitable for small capacity USB drives).
Offline installer which is base on full macOS image file (bigger download)
When going the offline...
I decided to replicate your problem on my computer.
First a created an online recovery macOS Big Sur USB installer following the Dortania Guide.
Then I added the EFI partition folder with all kexts related to Ethernet or WIFI disable...
Did you tried different USB ports?
Security Disable?
Try with this other kext to see if is different.
Also boot argument:kext-dev-mode=1 allows unsigned kernel extensions (kexts) to load.
Add it to your boot arguments and try again.
First of all, check your BIOS version. Some users reported problems with old UEFI/Bios versions.
If it's old update to at least the A12 version.
Also if you search online the term: Dell E6430 i5 OpenCore
You will find Github proyects related with your same computer model. Just adapt the EFI...
Check if your Phone is in Debug mode. This option can be hidden. Search about how to enable/disable it.
Make sure you activate tethering/hotspot before you plug your phone to computer.
Sometimes it won't work at first boot but could work after a reboot so try again.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.