Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,616 posts in this topic

Recommended Posts

4 hours ago, tluck said:

@tasteTheBacon

 

the HD3000 kext set really need to be in the OS (/S/L/E) as they don't seem to work properly from the ESP.  

 

but now you are saying it wont boot into graphics mode at all?

 

you can try to boot up in non-HD3000 by setting the GFX ID in the Clover Options menu. then you go to graphics sub menu to set the product id to 0x12345678 - then it should boot up in basic mode. this way you can remove stuff from the ESP and and validate stuff in /S/L/E 

 

@tluck

Yes, unfortunately it won’t boot into graphics mode at all now. 

In the meantime I’ve deleted the 10.14 folder from the ESP (ultrabay hdd has windows 10, used it for deletion ). So conflict shouldn’t be an issue in any case now. 

I’ve tried to boot with product id 0x12345678, but sadly it didn’t make any difference. 

I’m pretty confident that the HD3000 and SNB kext is in the right place, even checked permissions with “ls -l” after all the previously ran commands in /S/L/E. 

Tried again with -v, -x, nv disabled, injection of edid , without injecting intel , without injecting any kext and the combinations of all of the above. 

Its all lead to the same result. 

 

Edited by tasteTheBacon
Typo

Share this post


Link to post
Share on other sites
Advertisement

tluck-  I'll try an installation of High Sierra. I do have an untouched USB stick of that ready to go. If I have any sort of success, I'll let you know.

 

Regarding a rollback to an earlier version of Clover.. There might be a way to do it from the Windows side but I'm far too much of a novice to know how to do that. I could roll back if I could get into OSX, but obviously that isn't happening at the moment :)

 

Let me try an HS install and go from there.

 

Thanks-

Steve

 

Edited by skoon432

Share this post


Link to post
Share on other sites

Well this didn't take long at all!

 

High Sierra is suffering the same problem as Yosemite.  It tries to start and it simply stalls out. OSX is seeing something it doesn't like, period.  At this point, I give up.  Whatever is wrong is far beyond my scope of understanding but I still firmly believe the fault lies in a bad version of Clover. I'm convinced that it had some sort of very bad bug in this specific version and it totally trashed up the OSX partition in some weird way. Oh how I wished I had just left it all alone and not tried upgrading to a newer Clover release. A lesson learned and now its too late! :(

 

 

IMG_1392.jpg

Share this post


Link to post
Share on other sites
21 hours ago, tasteTheBacon said:

 

Its all lead to the same result. 

 


To be pro-active: I've tried everything, even reset my bios settings, deleted and re-copied everything to the SSD ESP.
None of these helped. 

But fortunately, I figured it out, sort of. 

The solution for me was to go in to the Clover Options menu while booting up and manually select a different config.plist and then re-select the default one (Which was highlighted by default).

Without this manual step the boot hangs.

With it it boots fine.

I've even got the HD3000 kext loaded and brightness working with this step.

If you ask me it doesn't make any sense to me. Can this be a Clover bug? 

 

Not sure if you have any tip on how to skip this manual step, but either way, thank you for the support @tluck , and also @goodguess for the tip. It's all highly appreciated.

 

Screenshot 2018-12-14 at 20.26.20.png

Share this post


Link to post
Share on other sites

great. so which config file worked? I think you are saying use used the default config.plist but you manually selected it? 

Edited by tluck

Share this post


Link to post
Share on other sites
On 12/16/2018 at 12:33 AM, tluck said:

great. so which config file worked? vs the default config.plist

 

So this is what I've done :

When I created the USB installer for Mojave I've renamed the Mojave 1600x900 config plist to config.plist in the USB EFI / Clover folder.

My intention was to convert it to become the default config that clover selects.
While installing MacOS from the USB this setup worked.

Once MacOS finished install to the SSD I've copied everything from the USB EFI to the SSD EFI.

When I tried to boot from the SSD it failed as detailed in previous comments. 
Clover properly highlighted my config.plist (which was originally the 1600x900 Mojave config) as the selected one, despite this I had to manually select a different config and re-select the default one to make a successful boot attempt.
I suspect that if I delete all other config.plist it will boot just fine and this is a Clover bug, but I didn't have the time to check this yet.

 

 

Share this post


Link to post
Share on other sites
On 11/3/2018 at 9:59 PM, goodguess said:

I still have the BIOS/UEFI stuff on a 1GB thumb drive.

My BIOS was at 1.48 with my last T420, lets hope the downgrade still works via DOS with BIOS 1.5.2

The bootable thumb drive is 1 GB, I´ll copy the needed files to a folder.

You will need to make a bootable volume from them to get into DOS for downgrading BIOS.

 

Here are the files: https://www.magentacloud.de/lnk/fvStA9ob

Good luck!

 

hi goodguess

sorry to bother you,

i must be stupid, cos i don't know how to do :(

there're 2 readme.txt (in TP and in root level)

i'm under w10 and my bios is 1.52 i want to wl to use my new wifi card

what must i do cos the stuff un-zip on USB doesn't boot my t420

can you please give step by step how to

Thanks for your help

best regards

Share this post


Link to post
Share on other sites

so i figured out why the Panel LCD brightness slider is missing for some folks. WhateverGreen conflicts with the AppleBackupLightInjector so it is not setting the ApplePanel property correctly. it is missing F10Txxxx in its Info.plist 

 

So for now remove WhatheverGreen.kext from your ESP or /L/E

or add this to the Info.plist

 

                                <key>F10Txxxx</key>

                                <data>

                                ABEAAACMANgBNgGPAf4CowNFA+cExwU1B1oJHAsTDZsQ

                                WRMS

                                </data>

 

to the WhateverGreen.kext/Contents/Info.plist right above F14Txxxx

Edited by tluck

Share this post


Link to post
Share on other sites
23 hours ago, Tetonne said:

hi goodguess

sorry to bother you,

i must be stupid, cos i don't know how to do :(

there're 2 readme.txt (in TP and in root level)

i'm under w10 and my bios is 1.52 i want to wl to use my new wifi card

what must i do cos the stuff un-zip on USB doesn't boot my t420

can you please give step by step how to

Thanks for your help

best regards

 

It has been some time since I downgraded my second T420, memory does not better with age either. :)

Basically you have to create a thumb drive which boots into DOS.

As you got that, you copy over the files I pointed to, onto that thumb drive.

Then after DOS boot, you downgrade with the DOS utility (everything else failed on my side)

At last you flash the patched 1.46 (with whitelist removed) in Windows.

 

I´ll look through my writing to check what still makes sense to me.

Share this post


Link to post
Share on other sites

So yeah, the procedure seems to be still doable.

Looks like I did not want to delete anything I had found, though it is not needed to get the downgrade done.

Follow these simple steps:

1. Grab a USB stick and format it FAT32 with the hidden DOS system files on it.

I think I used HPUSBDisk.exe and the files from usbdos.zip while running some Windows OS.

2. Copy over all needed files.

 You will need at least PFLASH.exe, B146.FL1, B146M.FL1 and the TP directory with the winflash.exe.

3. Boot from your USB device into DOS.

4. Type in: PFLASH /sa B146.FL1 (This should downgrade your T420 to BIOS 1.46)

5. Boot into Windows again, open a DOS window and navigate to USB/TP/bios_mod.

6. Type in: winflash /sa B146M.FL1

From the winflash GUI, select "Flash BIOS only" then click on the "Flash" button.

That should be it - reboot and enjoy your modded BIOS.

You may have guessed that M stands for the modded BIOS you finally want.

Besides the whitelist removal, some AMT features are also disabled with the mod.

 

Good luck!

 

For the rare possibility that you already ditched all your Windows installer DVDs:

The Internet Archive has one here: https://archive.org/details/HPOperatingSystemDVDWindows7ProfessionalSP164-bit650434-DN32012

No serial needed, but the install is not a "genuine" W7 of course. ;)

 

HPUSBDisk.exe

usbdos.zip

OpenMe.iso

Edited by goodguess

Share this post


Link to post
Share on other sites
On 12/6/2018 at 4:31 PM, tluck said:

@MikeDece

 

hmm. i just went through creating a HighSierra and Sierra Installer to validate the process not long ago.

  

so for you, it seems like the installer runs and started to do the install - without black screen when you removed ScreenResolution 900x600?

 did it complete install?

 is there a microsoft install on the disk?

 

Yeah once, I removed the default 900x600 resolution and adjusted it to fit mine, I was able to get it to the point where it allowed me to use the diskutility tool in order to repartition and whatnot. Once I created the base partition and it copied the files over from the USB to the installation partition, and I'd boot into it, it got about midway before stopping and telling me the `NSLocalizedDescription` error as seen in the following JSON response:

2018-12-05 11:35:49+00 MacBook-Pro OSInstaller[552]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Core.pkg”." UserInfo={PKInstallPackageSHA256Digest=f6947c0c5ae5d2bd3bf90a557647131c186627831e182a624c8239b5ed9cd2c4, NSLocalizedDescription=An error occurred while extracting files from the package Core.pkg”., NSFilePath=/Volumes/macOS/.OSInstallSandboxPath/Root, NSURL=Core.pkg -- file:///Volumes/InstallESD/Packages/OSInstall.mpkg, PKInstallPackageIdentifier=com.apple.pkg.Core, NSUnderlyingError=0x7fba4786a1f0 {Error Domain=PKXARArchiveErrorDomain Code=101 "archive verify failed" UserInfo={NSURL=file:///Volumes/InstallESD/Packages/Core.pkg#Payload, NSFileOwnerAccountID=0, NSFileHFSTypeCode=0, NSFileSystemFileNumber=462, NSFileExtensionHidden=false, NSFileSystemNumber=16777245, NSFileSize=4460809648, NSFileGroupOwnerAccountID=0, NSFileOwnerAccountName=root, NSFilePosixPermissions=420, NSFileHFSCreatorCode=0, NSFileCreationDate=2018-07-04 19:40:30 +0000, NSFileType=NSFileTypeRegular, NSFileGroupOwnerAccountName=wheel, NSFileReferenceCount=1, NSFileModificationDate=2018-07-04 19:42:05 +0000, NSLocalizedDescription=archive verify failed}}} {
	    NSFilePath = "/Volumes/macOS/.OSInstallSandboxPath/Root";
	    NSLocalizedDescription = "An error occurred while extracting files from the package \U201cCore.pkg\U201d.";
	    NSURL = "Core.pkg -- file:///Volumes/InstallESD/Packages/OSInstall.mpkg";
	    NSUnderlyingError = "Error Domain=PKXARArchiveErrorDomain Code=101 \"archive verify failed\" UserInfo={NSURL=file:///Volumes/InstallESD/Packages/Core.pkg#Payload, NSFileOwnerAccountID=0, NSFileHFSTypeCode=0, NSFileSystemFileNumber=462, NSFileExtensionHidden=false, NSFileSystemNumber=16777245, NSFileSize=4460809648, NSFileGroupOwnerAccountID=0, NSFileOwnerAccountName=root, NSFilePosixPermissions=420, NSFileHFSCreatorCode=0, NSFileCreationDate=2018-07-04 19:40:30 +0000, NSFileType=NSFileTypeRegular, NSFileGroupOwnerAccountName=wheel, NSFileReferenceCount=1, NSFileModificationDate=2018-07-04 19:42:05 +0000, NSLocalizedDescription=archive verify failed}";
	    PKInstallPackageIdentifier = "com.apple.pkg.Core";
	    PKInstallPackageSHA256Digest = f6947c0c5ae5d2bd3bf90a557647131c186627831e182a624c8239b5ed9cd2c4;
	}

 There was no prior microsoft install, I had some partition table that wasn't the GPT, on which I had a main partition with a Fedora LLVM partition and an extended partition that contained Gentoo and Ubuntu. When I was going through the install I wiped the entire disk, created a GPT table, and made two formatted HFS+ filesystem partitions from an Ubuntu Live USB, which I later deleted and reformatted from the disk utility tool found in the HighSierra install.

 

After making these posts, I tried to obtain a legitimate MacOS HS installer which I had my friend download for me (since it wasn't letting me do it), verified it, and repeated the process. Got the same result as before.

Note: Since I don't have a Mac myself, I used VirtualBox on Ubuntu 18.04 to run the latest Sierra to create the USB installer for part 1. 

 

Apologies for the late response, I gave up on hackintosh and just installed Windows and ElementaryOS. I'd be willing to give it another shot but at the moment I don't see the sensibility if I can't create a proper installer without having access to a Mac. 

Share this post


Link to post
Share on other sites

Sorry to hear about your mischief MikeDece.

As you mentioned your T60, mine is still running Snow Leopard 10.6.7.

I recall installation was brain dead simple with the use of Nawcoms Mod CD and a SL retail DVD.

You may know that Internet Archive is hosting SL retail DVDs:

https://archive.org/details/cd-roms?and[]=snow+leopard&amp;sin=

I could dig out Nawcoms Mod CD for sure.

Note that Nawcoms Mod will only work with a 10.6.0 or 10.6.3 retail DVD - not with the grey DVDs.

Such install would give you basic Intel "Mac" sort of. ;)

From there, you could follow the guide to set up a bootable thumb drive with Clover / Sierra.

 

Other than using your T60, setting up 10.6 Server via virtualisation is possible too.

I cant tell how to do that in GNU/Linux.

Its easy enough on a Mac with VMWare Fusion, but thats another hen-egg problem for you. :(

Edited by goodguess

Share this post


Link to post
Share on other sites
On 12/19/2018 at 6:06 PM, goodguess said:

1. Grab a USB stick and format it FAT32 with the hidden DOS system files on it.

I think I used HPUSBDisk.exe and the files from usbdos.zip while running some Windows OS.

2. Copy over all needed files.

 You will need at least PFLASH.exe, B146.FL1, B146M.FL1 and the TP directory with the winflash.exe.

3. Boot from your USB device into DOS.

4. Type in: PFLASH /sa B146.FL1 (This should downgrade your T420 to BIOS 1.46) 

 

on W10 : These 4 first steps are OK but they bring me back from 1.52 to 1.49 (not 1.46).

I suppose i have to test it again on W7 :(

 

Step 3 with : No GUI, no Windows (10), just the DOS prompt A:∖ on an empty black screen.

Edited by Tetonne
add info about step 3

Share this post


Link to post
Share on other sites

Tetonne, did you really boot into DOS?

No GUI, no Windows (10), just the DOS prompt A:∖ on an empty black screen.

Its a miracle to me how you should have got 1.49 when you had 1.52.

When I tried (long ago) PFLASH from DOS was the only way to downgrade BIOS.

Usually you could only upgrade to a higher version from the Windows command line.

As I never had BIOS 1.52 things may be different by now or something is locked.

 

Please bear with me asking the above, maybe I got something wrong. :)

Edited by goodguess

Share this post


Link to post
Share on other sites

Some sort of off topic, but I saw the T420s being sold at affordable prices.

Did anybody succeed with a T420s hackintosh?

The specs are looking similar, except for USB3, there also seems to be modded BIOS available for whitelist removal.

Share this post


Link to post
Share on other sites

@goodguess - yes T420s is very similar hack as T420. i am not sure if the USB3 is still supported and working though. 

Edited by tluck

Share this post


Link to post
Share on other sites

Thanks tluck, I was thinking of the T420S, USB3 will be an issue there too.

Also I´m curious whether somebody succeeded flashing BIOS for whitelist removal. 

Presumably PFLASH (DOS) would do the job.

Share this post


Link to post
Share on other sites
Quote

found on bios-mods.com thanks to zmb :

 

Here are some additional modifications to the bios modded some time ago (I think everything that people usually want):
- No whitelist
- AES-NI lock removed
- MSR 0xE2 unlocked
- Added advanced menu
- Memory lock to 1333 removed (now supports DDR3 1600 and 1866)
- Intel vbios updated from 2089->2170
- Re-signed with custom key to get rid of 5 beeps on boot (Does anybody have these beeps? If you get the error 1901: or some nonsense about security after this, you need to reset bios settings to defaults)

In the folder mod, there are bioses with different number of modification. It is possible to know what modification is applied from the name of the file: NWL - no whitelist, NWL_ADV - no whitelist + advanced menu etc. if you need to apply specific bios from the list, you need rename it to $01C8000.FL1 and place it to the folder 83ET82WW.

All credit goes to the TimeWalker and ValdikSS from the folowing posts:
1. https://www.bios-mods.com/forum/Thread-T...#pid114437 (this post has nice descriptions how to implement all the modifications)
2. https://www.bios-mods.com/forum/Thread-R...#pid141098
 (the re-signing thing)

Every modification is tested on my t420. But as always, use it at your own risk.

Link: http://rgho.st/private/7DYcBR7MF/7572e9d...8da07b25e0

 

Quote
found on bios-mods.com thanks to zmb :
When the newer version of the bios will be available (if at all) you could try change yourself. There is an easy way to apply modifications to the new bios version without disassemblers or any such fancy tools.

For this you need one external tool: UEFItool 

This tool could be used to extract some specific module from the bios image (*.FL1 - file) and then to replace it with the modified one. Each module is a program, which performs some functions. For example the whitelist check is done in the module "LenovoWmaPolicyDxe.efi"

The idea is that for the minor bios changes the modules in the bios-image of different versions are the same. And it is possible to replace the original module in the newer version of the bios with patched module from the older one. (see pic1)pic1.jpg.3c85e61c4fd656ed73d6deaecc55a432.jpg

For example if I extract the "LenovoWmaPolicyDxe.efi" from 1.51 bios and from 1.52 and compare them in binary mode, then I will see that the modules are the same. (command for binary compare: fc /b file1 file2 - see pic2)pic2.JPG.8f387e02bd193f82fe238da326e542df.JPG


This means, that I could take the patched module from the v1.52 ("LenovoWmaPolicyDxe_modded.efi") and replace the original module in the v1.51. This way I would get the whitelist free version of the bios v1.51.

The example above may be true for the next version of the bios v1.53 and for other models of thinkpads as well.

Of course If the extracted module is not the same and the binary compare shows differences, then bad luck and it is better not to touch it.

 

 

Share this post


Link to post
Share on other sites

so back to 1.52 after downgrade to 1.49.

but i did not success to apply mod with "run WINUPTP.EXE /S from this folder"

WINUPTP.EXE dosen't seem to be recognised :(

from this 1.52mod: http://rgho.st/private/7DYcBR7MF/7572e9d...8da07b25e0

pain in the neck

can someone help

i now know how to downgrade from 1.52 to 1.49 (not 1.46)

back to 1.52 ok

i tant to WL this {censored}... T420 (1.52 or previous lol)

 

 

Share this post


Link to post
Share on other sites

Hi T420 peeps!  I'm a first time hackintosh builder and I could use some help getting my machine off the ground.  I've researched for about a week and I've spent a couple days just trying to get a mountable USB to use (and I'm not even sure if I did that correctly).  To some extent I followed TLuck's guide, but I had to create some workarounds for limitations - I'm not sure if maybe I skipped something vital that is creating my current road block.

 

Pertinent information

83ET79WW  BIOS 1.49

41786vu
intel i5-2520 2.5ghz
Intel HD 3000 x Nvidia NVS 4200m

1600x900

BIOS settings Album

 

 

Creating the USB... After many attempts to create a working USB install directly from my windows desktop using things like R-drive, rufus, win32diskimager, etc., I ended up creating a Mojave environment in VM Workstation.  However, I cannot download a copy of Mac OS from the app store, for some reason it keeps returning with an 'incomplete' error even though it's up-to-date.  At any rate, I downloaded a .raw file from olarila and used etcher to flash it to my USB.  I then ran Clover r4726 pkg from the 10-31-2018 utilities and plugged it into the T420. 

 

USB finally working... I boot to clover and the initialization scripts run - I finally see the "Install Mac OS" and disk utility.  Which brings me to my current road block: I cannot write to my internal disk.  I have unplugged it and swapped it into my desktop to reformat to no avail.  I also swapped in a spare clean drive with no luck.  My gut feeling is that something in the BIOS is stopping the USB installer from speaking to the hard disk.  Any ideas?

 

 

EDIT:

I'm so dumb.  "diskutil eraseDisk JHFS+ disknamehere disk0" formatted it with no issues.  However now it says that I can't install 10.14 on this computer...

ERROR_F236DD3E91

1770041574_2018-12-2717_07_19.thumb.jpg.e406b6a1122e2879b46f26ebb4d6528e.jpg

 

 

 

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

When I run "diskutil list", I'm met with about 30 "drives" including my 160gb install drive and the USB, but also ~28 weird drives of varying sizes.

1178819920_2018-12-2714_57_32.thumb.jpg.652939d85d97e4dbf00a575a9d1026fe.jpg

Attempted First aid:

Running First Aid on "" (disk0s1)

Repairing file system.
volume is already unmounted.
performing fsck_exfat -y -x /dev/rdisk0s1
checking volume.
checking main boot region.
main boot region is invalid. trying alternate boot region.
checking alternate boot region.
alternate boot region is invalid. 
the volume could not be verified completely.
file system check exit code is 1.
restoring the orignal state found as unmounted
file system verify or repair failed

Operation failed...

Attempting to format/erase:

1715503746_2018-12-2714_58_58.thumb.jpg.010423837b236730d1d958dcc1c43e58.jpg

 

 

 

Edited by namisloc

Share this post


Link to post
Share on other sites

Hi namisloc.

I would assume that you did hit several obstacles at one time.

My thoughts:

- A macOS Hackintosh can not boot with two active GPU. Did you disable the NV graphics in BIOS?

- HD 3000 IvyBridge laptops are incompatible with 10.14 Mojave.

- Your boot volume should be empty and clean for installation. Best use a Gparted Live CD to swipe clean your HDD/SSD.

 

If I was in your place, I would step back to a Snow Leopard machine and prepare a bootable USB device for 10.11/10.12/10.13 from there.

Snow Leo still runs fine on Core2Duo rigs. You may install with Nawcoms Mod CD and a SL retail DVD from the Internet Archive.

A virtual machine running 10.6 Server is another option of course.

 

As you got macOS on your boot USB device with tlucks EFI package, you may install on your T420.

Of course tluck´s EFI package has to be copied to your HDD/SSD to boot from it.

Remember that the Clover package must be installed onto the hidden EFI partition EFI/EFI/Clover.

The EFI partition is automatically created by macOS DiskUtility when initialising your HDD/SSD as HFS drive.

(Use a GPT partition table at this step.)

As you got e.g 10.12 on your T420 and booting with tlucks EFI package, you may DL 10.14 from the app store,

as the T420 pretends to be a MBP late 2013 which is supported for Mojave upgrades.

 

Mojave will only work with the new APFS file system.

You can only format your HDD as APFS as you already got Mojave.

When upgrading to Mojave from an earlier macOS, your HDD/SSD will be converted to APFS by force.

The procedure may fail for several reasons: Too little room on the given device, Mojave dislikes the drive, its a Monday, etc. ;)

Either way, be aware that the upgrade will take a really long time and may fail several times.

 

It may be recommendable to start a new thread for your work.

Most of us here already had several macOS versions on their T420 and do read here only for fine tuning.

 

Share this post


Link to post
Share on other sites

Hi, first of all thanks to everyone keeping this alive.

 

I recently upgraded to Mojave after having El Capitan installed for more than 2 years without any serious problems, but it was time to upgrade... Install went smooth but I'm having same issues with black screen as @tasteTheBacon . His solution to remove all configs and use default config.plist worked and now I can boot fine, but there are some problems: brightness adjustment doesn't work - I guess it will work with the 1600x900 mojave config.plist if the booting problem is fixed. I've also noticed that I'm sometimes getting system freezes for few seconds if I click on some items in the menu bar (Apple logo for example) or when I use Preview app or similar image viewers (Xee^3), it is very random and difficult to reproduce as it didn't happen during writing of this post when I tried to randomly click on items in the menu bar. Is anyone else having same problems? I might try to downgrade to High Sierra, but dark mode feature is great.

 

Also my T420 configuration is: i5 2520M CPU, 1600x900 resolution, 16GB RAM if that helps.

 

Edit: Now it froze completely and had to reboot when I tried to open video with Quicktime, also now I've noticed that I can move cursor around while it is frozen.

Edited by bxe

Share this post


Link to post
Share on other sites

Hi bxe!

Got exactly the same T420 config as the one you posted.

Did you install Mojave over your existing El Cap?

I recall some black screens and freezes during the Mojave upgrade, but things are working fine since (booting with -v).

I´m using tluck´s 1600x900config.plist renamed to config.plist.

The only issue I found so far is Preview not opening jpg files.

I did assign jpg files to "XnView MP MacOSX" but Finder displays the ever spinning cartwheel when clicking a jpg just the same.

I had a system freeze yesterday after inserting a SD card from a camera - tons of JPEG on it of course.

My guess is that Finder/Preview tries to access the metal API, which is unsupported by our SandyBridge iGPU.

Other apps may call for metal too, thus freezing the hack, could you share the QT file in question eventually?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
×