Bronxteck

are you trying to boot os 10.10 or a newer os? if its a newer os you probably will need to update the kexts and config plist to the newest sierra stuff if thats what your attempting. at least the fakepciid's. and generic usb probably wont work in sierra either or the version of clover thats in the bootpack probably does not support the newer kernels either.

if you are using a patched kernel like for chameleon you will need to re patch the new one from the 10.12.4 update. if it's clover your booting from then try repair the disk using disc utility from usb os installer or recovery. Herve has some listed here

looks like second stage glitch. leave it there a bit and see if it continues to the installer. you have to have compatible trackpad drivers in your installer usb

choose to boot in verbose mode in clover GUI. press space bar for the option.

Try making the clover installer for UEFI booting and also set your bios to UEFI. press F12 at initial bios boot and see if it has a UEFI USB boot entry option. hopefully you will get to the clover boot GUI.

dependency 'as.vit9696.Lilu' not found. did you add lilu? if not add it https://github.com/vit9696/Lilu you need to add it inside of the AppleALC.kext' plugins folder i believe.

you might have to downgrade your bios to A03 then Back to A012. because of graphics glich.

here is some info on PR03x not sure if it's similar but might still apply to your machines E6x30 family https://osxlatitude.com/index.php?/topic/9623-e6430s-2-external-monitors-output-with-pr03x/?hl=docking you can also find them cheap with power adapter http://www.ebay.com/itm/Dell-PR03X-Latitude-E-Series-E-Port-E6420-E6520-Docking-Station-130W-AC-Adapter-/201792074995?hash=item2efbbeb4f3:g:DDYAAOSwal5YCPsk

use More Reply Options button to attach files. select the file first then press attach tab. is Bios SATA set to AHCI?

This also seems to have ALC 271 compatibility using layout 9 or 31 it (AppleALC) will also need another plugin called lilu to work

If you are booting bios in legacy mode from usb try installing clover on the usb with legacy install option, if booting the laptop in UEFI mode install clover in UEFI mode onto usb. maybe thats why it does not show up in your F12 boot menu selection screen. I compiled latest clover trunk rev 4045 because 4035 has some issues that are corrected in latest trunk in case thats the issue you are having. Clover_v2.4k_r4045.zip

what rev of clover are you using?

as a general rule if you are trying to boot off of the hard disk for the first time anfter installing the OS and have not installed a boot loader to the hard drive it will not boot. but i dont know how far you have gotten. if thats the case boot the usb stick and select the new os to boot it then install/ transfer your bootloader files to the HDD.

has that usb stick booted clover before that you know of not all usb sticks can be used for booting especially encrypted usb sticks.

yeah looks like apple boot display is on port 0 but it says display type is none yet port 3 is LCD so maybe try 3. if not it looks like you might need to patch connector types? i am not familiar with that part.

https://github.com/philippetev/HP-ProBook-Installer/wiki try that

you will probably need something like Ozmosis http://www.insanelymac.com/forum/topic/291655-ozmosis/

you can try using this newer battery kext https://bitbucket.org/RehabMan/os-x-acpi-battery-driver/downloads/

you can try typing this in Clover's EFI Shell: the commands are as follows bcfg boot add 3 fs0:\EFI\BOOT\bootx64.efi “Clover” You must then type bcfg boot mv 3 0 This second bcfg command moves your new entry to the top of the boot list

try different ATI Framebuffers maybe baboon is not work properly in sierra.

you might have to use ioregistry app to see what video port is set as primary and switch it to your lcd by setting it in clover config under BootDisplay option. EDID might also be a factor. you can try playing with clover boot gui options and see if having clover inject edid helps.

what do you have for a config attatch it here

what bios rev are you on.

try running this in terminal to see if it can give you an idea of what is causing the issue. log show --style syslog | fgrep "Wake reason"

maybe this program can work.