ianinsane

I've been trying to install HS on my E6220, using this guide. But I can't get the install process to work. After creating the USB installer and booting up, the Clover Screen loads fine. Then I choose the "Install High Sierra" option with -v flag. Then it goes through all the commands and suddenly reboots, prompting the message "attempted to boot uefi volume from legacy mode" and going no further... Do you have any leads what to do? I've tried several times to create USB-installers, both with Clover r4689 and r5097 (with the latter, using the customized settings from the E6220 Mojave guide)

lately i've been experiencing trouble with my keyboard. A couple of keys stopped to respond, working only after hitting it multiple times. if it was a single key I'd say it was a mechanical issue and get a new keyboard. But since it's a handful of keys (Left Shift, couple of keys in the upper letter row, Backspace) that acted up all at once, I've been wondering if there might be software reasons. Has anyone experienced this as well or does have any idea about this? I'm running a E6220 on Sierra with Enoch.

Many thanks for the hint! I just started to do that and ran into a problem right away. After using sudo /Desktop/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/HSInstaller to create the USB installer I got the answer /Desktop/Install macOS High Sierra.app/Contents/Resources/createinstallmedia: command not found I'm not sure what went wrong here. The installer app has only a size of 23MB, though - am I using the wrong one?

I have an E6220 i5 running with Sierra per Hervés guide with Enoch, everything running smoothly (except the need for a reinstall every couple of months ), but the HDMI output. When I connect an second display (monitor or projector), then Sierra can identify the second display but only shows a white screen on it. Any ideas what to do?

Reinstalled it - three weeks running smoothly. And now it happened again: Header read size 200 Incorrect image signature, expected version 10.7 Why, oh why??

OK, now, this is funny. I just did a complete re-install of my Sierra system - and guess what? Again this memory allocation error. Now I just tried to resize the background.png in /Extra/Themes/Default to match my screen resolutions and - voila! It worked. Strange that this seems to affect only my E6220..?

So I'm probably looking at a complete ré-install here. I'm just afraid that I'm going to face the same problem again if I can't find the source of it...

Sorry, I was confused. I didn't use Clover on my USB install disk, but Enoch.

In that case on the USB installer's folder?

IIt's just the same: Booting from SDD Bootloader into OS X SDD installation failure (header read size 200 etc) Booting from USB Bootloader into OS X SDD installation failure (header read size 200 etc) Booting from USB Bootloader into USB OS X Installer works, but apparently problems with Terminal access to SDD installation

OK, I mounted the SSD partition with diskutil mount /dev/disk0s2 which succeeded ("Volume Macintosh SSD on /dev/disk0s2 mounted") But it didn't change anything on the outcome of the commands in Terminal...

To rule out a misunderstanding: I was now booting from the USB installer into the Sierra installation menu and ran Terminal from there.

The first command triggers this response: ls: /Volumes/Macintosh/var/vm/: no such file or directory Still tried to rebuild the cache and got "no such file or directory" for the first two directories, "read-only file system" for all the flags and "not a directory" for the last directory...

Of course:

No, I wasn't able to boot... And I didn't install any updates, also diskutil list shows the SSD as Apple_HFS. The first time this problem appeared was after it wouldn't boot due to low battery. I plugged in the power chord and hit f1 to continue booting, like I did so many times back when I was running Yosemite on that machine. This time though, with my 2 month old HS Sierra install, it got me this problem.

That's strange. I did disable that... Yes I'm using Enoch, but when trying to boot with KernelBooter_kexts= Yes -f -v I get this message: No kext.plist replacement found :-( Is there anything else I can do?

My E6220 with HS Sierra was running smoothly, but when I last booted it failed after the bootloader screen. It said: header read size 200 Incorrect image signature, expected version 10.7 Normal boot and with -s flag does not work. Do you have any idea where to start troubleshooting?

Well, I'm not sure what happened, but it seems to work now. I completed the rest of the post-installation fine-tuning after my try with only the AICPUPM kext. And now the reboot seems to work!! Maybe the newly generated SSDT did do something different than the first time - or it had to do something with my resizing of the background image in the Extra/Themes/Default folder to match my screens resolution, like hinted in this post? Thank you very much for your help, time and effort, Hervé! I've been using this machine daily, set up with your guide and Yosemite more than two years ago. Now I can continue using it with High Sierra!

Yes, I'm just trying to find out at what step the problem is. When I installed the bootpack properly I had the same error, so I'm just trying it step by step, with my clumsy non-knowledge...

OK, what I tried now: - Manually copied Extra to Root HDD - Installed Enoch r2921 (Installer Log see post above) - Disabled Hibernation - Copied the Sierra patched AICPUPM kext to /System/Library/Extensions (I used 10.12.6 - hope that's right!) - Edited /Extra/kernel.plist and set KernelBooter_kexts parameter to No - repaired kexts permissions and rebuilt cache (did prompt some error messages...) - did a test reboot --> Memory allocation error. Do you have any idea where the problem is located?

Something seems not working with this Terminal command during post-installation: in my case: cp -R /Extra /Volumes/Macintosh SSD I only get the "usage: cp" response... EDIT: Proceeded anyway and yes, there was no Extra folder on Macintosh SSD. Copied it from the USB Installer first thing after completing the 1st boot installation finalisation, booted then again, still from USB installer since no Enoch installed yet. EDIT: Chamelon Installer Log:

I'm going to try to go back step by step und try to move the files one by one to the extensions folder, rebuilding the cache after each, then booting after each and see when the error starts to appear... EDIT: Didn't work, same error. I'll reinstall the system from the USB installer and start again from there.

I don't know if that made any sense without installing a newer Enoch version, but I rebuilt the cache and after booting got the same Memory allocation error...

Yes , forgot to mention, I used r2921 from the beginning...