Mike Taylor

I am booting from USB. I have two different Clover templates (for USB and HDD) so there's no confusion over which one I'm booting from.

Yeah, I did, on USB stick, but I believe that HDD ones are overriding the USB ones. How can I prevent them from doing so? I can't replace them on HDD until I successfully boot to a system.

Same result. I hope I'm doing it right. I copied those patched files to USB colver and booted MacOS on HDD usiong USB colver (not hdd clover).

find Attached origin.zip

Jake, after doing so the bootloader hangs on at a very early stage, see screenshot. BIOS changes requires aml-s to be reconfigured/recompiled?

Thank you. The system booted, however the brightness issue is still present edit: actually what happened after booting from HDD is that the brightness is completely gone from the system (Displays), the buttons won't react either Nevermind the edit. The brightness bar was gone because I disabled Kext patch in Clover, I brought it back and brightness bar is back again, tho not working as supposed to.

I updated the BIOS which, as you said, caused system not to boot anymore. Attaching latest origin. I'm just worried, after you patch it, won't it be a problem that I have different aml-s on USB stick clover and different one on HDD Clover? Wouldn't HDD override the USB ones like it did with kexts? origin.zip

I followed this EDID guide, unfortunately brightness issue didn't go away. I assume I followed this method properly as I got the "warm" colour issue that he mentioned in his post.

Ugh. I messed something up and now I see black screen only. I need to access the filesystem to fix it. I tried to get Terminal access by booting from USB stick but I still get black screen. Same goes when I try to run installer from USB! Is it possible that HDD Clover kexts override the usb ones? How can I force Clover to ignore what's on HDD and focus on USB only?

Coming attached PS: For the reference I uploaded the video showing how the screen reacts to brightness buttons. You can see that the screen is dimmed until brightness is set to 100%, then decreasing until ~30% does nothing and then when decreased to ~25% it dims and starts flickering heavily. Now when trying to decrease/increase the brightness it will cause it to go off completely. https://www.youtube.com/watch?v=fT9D-AKJg1M PPS: Another thing related to the brightness. You suggest in your guides to use karabiner to disable F-keys functionality for the purpose of using them as special functions (such as volume, brightness etc) however I need those F-keys to be *the* F-keys for terminal apps. However karabiner eventviewer reacts to fn+f1/f2/f3 (which is mute, volup, voldown) whereas when I click fn+f11/f12 (which should be bright down/up) it shows nothing, like no keyboard event occured. Any ideas? PPPS: Also you don't mention anything about this "invalid signatured" information that appear in the output so I guess it's not relevant? Attaching IOREG output. RETARD’s MacBook Pro.zip

Dumping IOREG. IOREG dump failed. Retrying by increasing delays... Increased delay by x2 times. Retrying... IOREG dump failed. Retrying by increasing delays... Increased delay by x3 times. Retrying... IOREG dump failed. Retrying by increasing delays... IOREG dump has failed 3 times. Dumping generic IOREG report instead. What can I do about it?

I'm still getting following output bash-3.2# ./permission.sh rebuilding //System/Library/PrelinkedKernels/prelinkedkernel Kext with invalid signatured (-67062) allowed: <OSKext 0x7ff2f8e2e400 [0x7fff86458af0]> { URL = "AppleBacklightInjector.kext/ -- file:///Library/Extensions/", ID = "org.rehabman.injector.AppleBacklightInjector" } kext file:///Library/Extensions/DisableTurboBoostBattery.kext/ is in hash exception list, allowing to load KernelCache ID: A1C0354DBA3602AC3F914CE489558B7D kextcache updated critical boot files, requesting launchd reboot Finished I'm uploading a new debug file although please note that while generating script I got following message, is that OK? System dump not requested. You may use gen_debug -sysprofile to generate system dump. debug_30450.zip

Attaching the debug file. I found another issue screen related (I think). When I close the lid, the screen turns off (but PC is not asleep as the LED is *not* blinking) but the display won't come back after I open the lid. It has gone by itself, no idea what happened. After latest reboot it works as it should. The brightness issue persists tho. edit: Minor side note, the keyboard backlit goes away very quickly (like 5 seconds). How can I increase the delay? debug_27482.zip

I removed FakeSMC from /L/E and ran permission.sh again. The output is exactly the same except that the line mentioning FakeSMC is missing (the line mentioning AppleBacklightInjector is still there). There's no additional output which prints list of kexts from /L/E which you mentioned. I guess the AppleBlacklight is not working as supposed to because: I can control brightness in a way that I see this brightness indicator although as I decrease the brightness level, the screen isn't dimming (it remains as is), however when the brightness level reaches the end, the screen turns off completely and I can't get it back unless I reboot. Nonetheless, ethernet, touchpad, sound, battery etc seems to be working again.

Jake! Legacy ROM options is disabled in BIOS. The kexts you mentioned are in the EFI/Clover directory (pls refer to the screenshot) I can't remember now if the permissions.sh executed successfully the first time but I ran it again now and there are 2 exceptions that showed up (see screenshot) PS: For reference I'm uploading screenshot from /Library/Extensions

@Jake Lo, I was able to install the system using your package - thank you for that. I've encountered a different problem. According to your instruction in "post-installation" I moved all the CLOVER files from USB stick EFI to HDD EFI and copied Kexts from "Kexts\Other\CopyToLE\" to /Library/Extensions (none were replaced, just added). I've also ran the "permissions fix" command. I couldn't however execute the 'ssdPRGen.sh ' part (CPU architecture was not found, or something like that). Still, I've rebooted the machine and now some of the modules that were working before (Ethernet, laptop keyboard, touchpad, sound) are not working anymore (they did before, when I was loading macos from USB Clover. Right now no matter if I boot the system from HDD Clover or USB Clover, I still can't use any of those features. Luckily USB devices are working so I can plug Keyboard and Mouse but still no internet. Any idea what happened and what can I do about it? PS: As to your previous question. I'm running 1.7.3 BIOS (rom attached) DellInc.-1.7.3.rom.zip

I'm trying to install 10.13.6 on E5570. I know that I should grab my own *.aml-s, disassemble them and fix but thing is, I have absolutely no idea what I am about to fix, thus I rely on somebody else's files which most likely won't work. Correct me if I'm wrong but I understand that Kext files are hardware universal but OS dependant (meaning I can take Kexts from i.e. Jake's E7470 EFI but I can't use his ACPI files), right? Anyway, I've downloaded the attachment posted by @Headshotde and replaced Kexts with @Jake Lo's E7470_1.17.5_HS.zip, however no matter how I mangle the Kexts I'm still getting following "error" (which actually ain't error, instead the boot hangs like it was about to print another character but it couldn't). The ACPI/orig files are generated by myself (F4 in Clover) but the ACPI/patched are from @Headshotde package, I haven't changed anything there. I really wish I understood what I am doing there but I just open this disassembled file and I have absolutely no clue where to even start looking. I mean I've found this _SB.PCI.SP1.FPNT._INI and _SB.PCI.SP1._CRS methods but there's nothing there that I see as broken or any patch that would correct it. Please find my CLOVER and screenshot attached. Note that these are two different screenshots where system boot hangs on different lines of text but the error is probably the same, just different timing. CLOVER.zip