Bu Yezi Posted November 18, 2021 Share Posted November 18, 2021 Both Wifi and Bluetooth on my E5470 (Big Sur old version) worked very well with this EFI folder given by Jake LO. All went well until I updated to the latest Big Sur 11.5.2. Now the Bluetooth stopped working. Is there any fix for this @Jake Lo or the Intel Card doesn't support anymore? Here's my EFI folder. Please help if you have any solution for this. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted November 18, 2021 Moderators Share Posted November 18, 2021 @BuyeZi Give this a try. Updated to OC 0.7.5 and latest kexts. Set for Intel wifi/ BT, will be Monterey compatible. E5470_OC_0.7.5.zip Link to comment Share on other sites More sharing options...
Bu Yezi Posted November 19, 2021 Author Share Posted November 19, 2021 > Updated OC 0.7.5 > Replaced the EFI folder > Cleared nVram I'm stuck here. Not sure if I did anything wrong. Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted November 19, 2021 Administrators Share Posted November 19, 2021 did you also update VirtualSMC.kext ? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted November 20, 2021 Moderators Share Posted November 20, 2021 try replace with this config.plist config.plist.zip Link to comment Share on other sites More sharing options...
Bu Yezi Posted November 20, 2021 Author Share Posted November 20, 2021 @Bronxteck I replaced the entire EFI folder, from my past experience you guys asked me to replace the EFI folder. I followed the same. @Jake Lo I didn't know the ways around replacing the plist file without booting into OS and mounting the EFI. So I reinstalled Big Sur with same old guide and EFI folder (downloaded in August) all over again. Track pad, Bluetooth, Wifi are not working. I'm thinking, can I update to Monterey and try fixing the BT, Wifi & trackpad? Monterey runs well on E5470? Action plan: > Update OS. > Update to latest OC configurator. > Use the EFI folder you have provided above. Will it work? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted November 22, 2021 Moderators Share Posted November 22, 2021 You shouldn't have to re-install if it fails to reboot, just have to fix the EFI boot back. You should always have a backup bootable USB handy. Just format a USB drive (all it need is 256 mb), you can use an SD Card too. Format to Fat32 and place the whole EFI folder on the root. You have LauncherOption set to Full on your original file, so I think it create a boot option in your BIOS call OpenCore. Try going into your BIOS and remove that boot option. As stated the files should work for Monterey, if you like create a new installer for Monterey and use that bootpack. 1 Link to comment Share on other sites More sharing options...
Bu Yezi Posted November 25, 2021 Author Share Posted November 25, 2021 Now I realized that was a stupid move to reinstall the Big Sur again. I fact, I had the Big Sur USB stick previously used. I should have booted into the machine and replaced the EFI folder from my EFI backup. Anyway, no point talking... I'm installing Monterey now. Made USB stick for Monterey using createinstallermedia command, EFI partition mounted using opencore configurator and I ejected EFI partition by mistake thinking it was System EFI. Now I'm trying to mount the EFI partition of the USB again. Opencore configurator is not recognizing EFI partition of the USB stick, MountEFI tool says there's no partition associated with the disk. Any solution for this? Please help! Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted November 25, 2021 Moderators Share Posted November 25, 2021 Unmounting EFI partition does not make it go away. I don't use OCC and don't know of MountEFI app. I use ESP Mounter Pro by Micky1979 Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 25, 2021 Administrators Share Posted November 25, 2021 EFI partitions do not exist by default on a raw/reinitialised USB key. It usually is created by bootloaders such as Clover (or older bootloaders before). Since you do not have any EFI partition on the device, you may manually create it and format it FAT32. Or, if you find the associated process not within your grasp, install Clover temporarily on the USB key. Once you wipe out the contents of the EFI partition created by the Clover installer, you'll have an empty EFI partition to play with. Link to comment Share on other sites More sharing options...
Recommended Posts