aufannada

Can anyone help to provide OpenCore EFI files for install Sonoma on Dell Latitude E7270? I have tried to install Sonoma using EFI Ventura but it failed. @Jake Lo only provide a guide for the E7470. Usually, there is for E7270 too. Please help.

Thanks, I tried that, and it worked, but only once. After the keys are added in config.plist and then the laptop is restarted, the bluetooth is successfully activated/enabled. However, after the laptop is turned off and on again, Bluetooth becomes deactivated / disabled again. Furthermore, every time the laptop is turned on, Bluetooth has never been activated/enabled again until now.

I've done according to your suggestion, but nothing has changed. Bluetooth is still disabled or not active. Just for information, that I'm NOT using an Intel wifi card, but I'm using a Broadcom wifi card : DW1830 AC BCM943602BAED NGFF M.2 Maybe you have another way?

My Dell Latitude E7270 laptop is installed with MacOS Ventura 13.3 and boots using Opencore from @Jake Lo which I took from : https://osxlatitude.com/forums/topic/9179-dell-latitude-e7x70-clover-and-opencore/#comment-116224 Everything looks good and works normally. I updated to MACOS Ventura 13.3.1 and 13.3.1a and all functions work normally, including bluetooth. But after I updated to MacOS Ventura 13.4 my bluetooth became disabled and there was nothing I could do. My E7270 uses DW1830 AC BCM943602BAED NGFF M.2 Please help to solve bluetooth problems on E7270 with MacOS Ventura 13.4. Your kindness to help me would be greatly appreciated. Thank You.

BCM943602BAED DW1830 AC BCM943602 NGFF M.2 1300Mbps BT4.1 WiFi Wireless Network Card. Yes, I did. I selected 'Clean/Reset NVRAM'. Am I wrong? Is that a problem?

Well, I've done that, and I've got the debug files. I attach the debug file below. Please help. opencore-2020-11-17-152020.txt.zip

Thanks @Jake Lo, but after I used your config, the result is still the same as this :

1. After I enabled AppleDebug in Misc / Debug and then I booted again using USB Installer, and when the error occurred again, I didn't get the log file on the root of EFI. Is there any other way to get that log file? 2. After that, I then returned to try the second method, switching VoodooPS2 with ApplePS2Controller + plugins that's included in the EFI and changing the config like this : and the result after rebooting again is like this : only until there the boot process.

I have created Big Sur USB Installer and copied the EFI Opencore that @Jake Lo uploaded to EFI on my USB. After I booted, what appeared was like this : Is the EFI valid for the E7270 in general? Please help so I can install Big Sur on my E7270. Thanks.

Sorry @Hervé, I'm not asking about "what is airplane mode". I know what Airplane mode means. What I'm asking is how it should deactivate the airplane mode. Not what Airplane mode means, but how do you turn it off? That's what I meant by the question "Airplane mode?" Btw, all the instructions (or at least, almost all) that you have given above I have done before. And all I ask is only if I miss what I have done, because so far there has been little by little progress from the first I consulted. Maybe right, what I haven't done is tape a pin to allow it to work as @Bronxteck said. I've read the instructions about tape a pin to allow it.

Airplane mode? What kind of incorrect WWAN profile? Can you please tell me.

Of course I have my SIM card inserted. I can use it when I boot using Windows or Linux. But if I use Mac I can't use it.

But there has been little progress. The WWAN menu on System Information -> Network -> WWAN has appeared WWAN Information after I have changed the kext in the Product ID and Vendor ID fields with the contents 0x81cc and 0x413c (Dell Inc.) But until now it still can't work. Any idea?

Thank you for your instructions @Hervé but after I used that kext, my WWAN DW5816e / EM7430 still can't be used. There is no change from before.

Ok. Thanks for your suggestion. But according to what you know, it's compatible right?

Thanks for your answer @Hervé Because there are some people who doubt it. And there are also argue that the Samsung 970 Evo Plus M.2 NVMe has the PCIE3.0x4 protocol while the E7270 only supports the PCIE3.0x2 protocol. That's what makes a lot of people doubt because SSD sellers also don't want to open their purchase box just to try. In addition, the problem is capacity limitation. In some cases, laptops that are installed with a 2TB SSD capacity can only be read a 1TB by motherboard. And the SSD seller in my place no one has ever tried it on a Dell Latitude E7270. So, Samsung 970 Evo is really compatible with E7270 right? If so, I'm determined and confident to buy and install it.

I am so sorry I late to answer the question because I was sick last time. I didn't change anything. The problem appears after I update with Security Update 2019-007 (High Sierra). A then when reboot I can't boot to desktop.

Can E7270 use Samsung 970 EVO Plus NVMe M.2 SSD 2TB?

Excuse me, I have a problem when my dell boot today. The problem is like on the picture. Please help me.

Okay @Hervé now the module has been detected and seen. What to do next because I can't add it to the network.

Ok Hervé, I see. That's why I asked for help because my WWAN module wasn't detected in the USB section of System Information (SysProfiler). I have done several ways, and one of them is using Legacy_Sierra_QMI_10.13.kext. But until now, the module has not been detected yet in the system. Please help.

I bought WWAN DW5816e aka Sierra Wireless EM7430 for my laptop Dell Latitude E7270. After I install it and install the driver, the EM7430 can work well on Windows and Linux. But, when I used on MacOS High Sierra, EM7430 can not detected. I have tried to follow the methods written on this forum but still can't use the WWAN, because not detected. Hope you can help me. I include debug files my laptop below. In the E/C/k/O folder there is Legacy_Sierra_QMI_10.13.kext that I use after I have successfully changed USBCOMP=8 using Ubuntu (USBCOMP=14 does not support for EM7430). COMMANDS: sudo ls -la /dev/cdc* sudo dmesg | grep cdc sudo apt-get install perl sudo apt-get install libuuid-tiny-perl sudo apt-get install libipc-shareable-perl sudo apt-get install modem-manager-gui sudo perl swi_setusbcomp.pl --device=/dev/cdc-wdm1 --usbcomp=8 debug_30345.zip

Okay Jake, I understand. Now there is no problem. Even now, I have tried using HDMI or miniDP to DP and everything can run well. I don't need to revert back to the old Config. And all of them can make a sound. Thank you very much. debug_30345.zip

Okay Jake, now MiniDP to HDMI to Samsung TV can already make a sound. Same as when using HDMI to Samsung TV directly. Thank you very much. If I may know, what is added or changed from the config.plist above?

Ya, a miniDP to HDMI to Samsung TV