viking1304

I will check as soon as I install HS during weekend. I am too tiered to do that now.

I had busy week at work, so didn't have time to test this further earlier. I finally was able to properly boot HS installation (with your A17 bootpack), and I am equally ashamed and confused. Please take a look at this photo Everything is very clear. Just boot USB with -v. Right? It should be that easy, but it's not. When I tried to boot installation for the first time (with old kexts) I pressed F12, chose USB in BIOS boot menu and I got exactly same screen. I selected USB from that menu, added -v and chose boot. I did that first few times. Once I forgot to press F12 on start, but I got exactly same screen. So I thought that USB is probably earlier in boot order than SSD, since I had option to boot from USB. Later I was just trying to boot from USB, without pressing F12 first. I was getting similar errors, so I didn't give any significance to fact that I didn't pressed F12 first. Now I am aware that the Clover that was launched was Clover from my SSD and not from USB. I figured that out when I installed Clover 4233 on USB, and saw 4200 on this menu. So yes, you were right, I wasn't booted this properly. But now I am confused. Looks like it is important which Clover was booted, but this makes not sense to me. Shouldn't Clover read config from drive that I am trying to boot, and not the drive where it were started from? btw. I would like to update "Generic EFI Folder" in order to use latest version of those files (from latest Clover 4233). I am aware that Themese folder is not same, but I am not sure what else is different. I would like to be able to prepare this myself next time when I need a fresh USB installation. Thank you very much once again Jake, and sorry for the confusion that I eventually made.

Thank you very much Jake. Unfortunately still no luck. With "Enable Legacy Option ROMs" boot crash with same error I had from start. If "Enable Legacy Option ROMs" is off I am getting KP and system reboots. I disabled reboot on KP and took this image. I am confused about version info in "Last unloaded kext" - it says ALC 1.1.3 but info on file from bootpack states 1.1.4?! I have an idea. What is the minimal set of needed kexts? I should check if I can boot this with that minimal set of kexts, and then I could probably add one by one to see when it will crash. I am sorry if sometimes I sound little ignorant, but I am fairly new to all this. EDIT: Looks like dual grapics is the problem after all. https://www.tonycrapx86.com/threads/fix-window-server-service-only-ran-for-0-seconds-with-dual-gpu.233092/ Would you mind to help me with this?

I am starting to suspect that real problem here is my BIOS or some piece of my hardware. I installed Sierra while I had A15 BIOS. I updated my BIOS to A17 and was prepared that Sierra might stop working, but everything continued to work without any problem, so I didn't expect any problems with HS. HS just refuse to boot properly. Sometimes boot process hangs, sometimes it crash and system restarts. I am starting to suspect that something is wrong with ACPI patches or that nVidia can't be disabled for some strange reason. I even downgraded my BIOS to A15, but still wasn't able to boot, so I reverted BIOS back to A17. All this time Sierra works without any problem. I have no idea what else to try. Origin attached if someone have time and will to take a look. btw. is there a way to create log file while booting from USB? I am not able to take a proper picture since text goes too fast. I suspect that there is some error message in the middle of boot process that might point what's wrong, but I just can't capture it.

I only have one 512GB SSD drive, so removing Windows drive is not an option. Shouldn't -lilubetaall flag do exactly what you are saying - enable beta flag for lilu and all plugins? I can try to add flags for all plugins. That's is not a problem, but I am not sure that it would help. All I can think off now is to try to update all kexts that are in Jake's bootpack, but there is currently some network issue with SF, so I will try that tomorrow.

If I understand correctly this is same as this flag is for versions above 10.13. But doesn't mean that I am right. I cleaned USB again and started from scratch. I updated those kexts from Jake's post to latest versions. I also put new config that Jake posted. Just added that flag to boot options in config over Clover Configurator and will take another try. I will report results soon. EDIT: Architecture couldn't be recognized! PCM_BOOT 0 = <ptr>, PCM_BOOT 42 = 0x00000011

Looks like Enable Legacy Option ROMs must be off, since I am getting exactly the same error as before if I try to enable it. If that option is off, I am getting this error:

Thank you very much. This is faster and easier method to create USB installation than to mount dmgs, restore and copy/paste. I guess my question might be misleading. I was able to boot installation from USB, but I am still not able to boot it properly and completely. If I enable Legacy Option ROMs it crash almost instantly If I disable that option t takes longer, but installation fails with another message Then I tried to update IntelGraphicsFixup (with RehabMan-IntelGraphicsFixup-2017-0819.zip) but still didn't managed to boot it. One more info that might be important - I am also using latest versions of IntelGraphicsDVMTFixup.kext and Lilu.kext since I restored my BIOS defaults. Those two works just fine in my current Sierra installation. Maybe I should try without those two and with 96MB patch?

Sierra works fine (posting this message from it), but can't boot High Sierra installation. Already prepared install USB two times, but there was no difference. E7450 with discreet graphics using official High Sierra from store EFI_4200.zip, E7450_A15_Disabled-840m.zip and Clover Boot 4220. Any idea what I might be missing?

In order to resolve first issue, be sure that you have disabled hibernation. Check FAQ section.

TP-LINK USB Adapter TL-WN725N works like a charm with Sierra.

Fn key doesn't work at all. First I though I had a problem with karabiner elements, but I actually have a problem with non-working Fn key. Every key tested with Karabiner-EventViewer gives some value. Fn key gives nothing. Is there any help? EDIT: After lot of googling I found out that on some keyboards, the Fn key is only seen by the keyboard itself, so it can't be seen by Karabiner Elements. Since Fn + F10 changes illumination intensity of my laptop keyboard without any problem, Fn key definitely works as expected. This means that every problem that I have is related to Karabiner Elements. I din't found option to delete this message, but it might be good to delete it in order to avoid confusion, especially since some time ago I posted another similar message where I properly blame Karabiner Elements for my problems.

Now I understand. Unfortunately it is Intel® Dual Band Wireless-AC 7265. Looks like I always have at least one "special" component in any of my laptops, that doesn't work, make problems or is incompatible with at least one OS.

I just noticed that I have no Wi-Fi at all. In System Presences / Network I can only see Ethernet and BlueTooth. I tried to replace FakePCIID_Broadcom_WiFi and FakePCIID in /Library/Extensions with new ones from RehabMan-FakePCIID-2017-0527.zip and to fix permissions and rebuild cacse as instructed here https://osxlatitude.com/index.php?/topic/9740-solved-dell-latitude-e7450-intel-5500-with-discrete-nvidia-840m/?p=69179 There is no change. I guess I already had same files since I used updated bootpack.

I successfully installed Sierra on E7450 with 840m. I just have one small issue with Karabiner-Elements. I just can't make F11 and F12 keys to work. EDIT: Everything work if Use all F1, F2, etc. keys as standard function keys is off. Is there a way to use Fn+F11 and Fn+F12 instead of F11 and F12 for screen brightness?

Enabling Legacy in BIOS helped. I installed everything with only one small issue after that. ssdPRGen complained that my i7-5600u was unknown. Downloaded new version and everything worked fine. Thank you.

Thank you for quick reply Jake. EDIT: I need to edit my complete post now in order to avoid possible confusion. You posted two different archives with same name and I downloaded both of them. I guess I somehow managed to add wrong one to EFI and I was getting service exited with abnormal code 1 errors So I compared files from E7450_A15_Disabled-840m.zip and E7450_840m.zip and noticed few differences in config.plist, but most noticeable difference that I noticed was (not) using NewWay <key>NewWay_80000000</key> <true/> I also noticed that some files in ACPI/patched folder are not same. Those two files are different: DSDT.aml SSDT-11.aml So I tired to replace files that I mentioned, but I still had same problem. Then I tried again with EFI_4128.zip and E7450_A15_Disabled-840m.zip. Replaced Boot and Clover folders on USB and tried again. It boots, but I have garbled screen again. I guess I need to check everything again, since I need to be sure that this time I did everything properly. btw. I knew that mentioned files were update only, so I tried to make bootpack myself before I posted here. I combined files from E7450_Sierra.zip, E7450_840m.zip and RehabMan-FakePCIID-2017-0527.zip, and then add those to EFI_v4119.zip, but obviously I messed something up.

I have E7450 (with 840m). BIOS version is A15. Latest Sierra install form app store. I followed Jake Lo's guides: https://osxlatitude.com/index.php?/topic/8514-dell-latitude-e7450-clover-uefi-only/ https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-precision-clover-guide/ I used EFI_v4119.zip generic EFI, replaced some files with those from E7450_840m.zip as per instructions here https://osxlatitude.com/index.php?/topic/9740-solved-dell-latitude-e7450-intel-5500-with-discrete-nvidia-840m/?p=69173 Patched both 0x15b and 0x15c, changed SATA mode to AHCI. Booting goes fine, but unfortunately initial screen where I should select language is garbled and unusable. Any advice? What I am doing (did) wrong?