Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,529 posts in this topic

Recommended Posts

Advertisement
On 10/30/2018 at 8:46 PM, goodguess said:

Thanks tluck.

As I was uncertain how to get back the trackpad function, installed from scratch again on the USB2 volume.

Until right now trackpad, trackpoint and keyboard do work. Same for sound, volume keys and camera.

Why the kexts were no loaded last time remains the question.

I´ll try some more, than replacing HS with Mojave will be on schedule.

 

I´m getting system crashes in an early stage, three out of four times.

I´ll try with my other T420, as there may be a ACPI issue as seen before.

The crash report (first lines) is attached.

 

For the lost trackpad and sound, could HWSensors be the culprit?

The devices did work on my second trial until installation.

Afterwards Trackpad and sound are missing and HWSensors are not loaded either - strange.

panic_report.rtf

 

I've got the same problem, after HS/Mojave install laptop keyboard/trackpad/sound/network was working, but on some subsequent boot not anymore.. I only realized this later at some point, since I'm using usb keyboard/mouse while docked, and usb speakers..

Gonna try a reinstall also, and try to pay attention at when/what's happening.

 

Share this post


Link to post
Share on other sites

@davidian: Did you install the HWSensors package too, from tluck´s repository?

Is 10.14 booting flawlessly on your side - without KP?

I could not make HiDPI work either, not that I would need it actually.

 

@Tetonne: I seem to recall that there was no valid whitelist removal after 1.46, things may have changed meanwhile.

Downgrading BIOS from Windows did not work for me back in the days either.

The DOS flash solution did work as described, see my txt file included with the upload.

Best stay with the patched 1.46 with WL removal, I think that the spyware Intel AMT function is disabled that way too. ;)

 

Share this post


Link to post
Share on other sites
3 minutes ago, goodguess said:

@davidian: Did you install the HWSensors package too, from tluck´s repository?

Is 10.14 booting flawlessly on your side - without KP?

I could not make HiDPI work either, not that I would need it actually.

 

@Tetonne: I seem to recall that there was no valid whitelist removal after 1.46, things may have changed meanwhile.

Downgrading BIOS from Windows did not work for me back in the days either.

The DOS flash solution did work as described, see my txt file included with the upload.

Best stay with the patched 1.46 with WL removal, I think that the spyware Intel AMT function is disabled that way too. ;)

 

 

I did install it, yes. Are you suggesting not to install it after a fresh install? I like having that, would be good to know if that affects things somehow.

 

Another thing that I noticed with HS was that I could not boot a lot of times. After selecting to boot HS in clover, my laptop would reboot as soon as the boot process started. Then I would switch on verbose logging, and it would boot all the way.. This seems sporadic, because sometimes I could boot normally. I did not have this issue with Mojave though.

I didnt check back the logs, so I do not know for sure if I had KPs or not.

I also need to do a compare between tluck's patched DSDT and my own, as some things (addresses) might be different, so I need to keep only the patched bits. I assume (maybe wrongly) most people don't do this if things work out of the box, but sometimes the problem lies there, some things might not work, because someones T420 DSDT is a bit different than the patched one posted in the guide. A compare of the decompiled DSDT's would show of there's some difference there besides the patches.

 

 

Share this post


Link to post
Share on other sites

@davidianI have not been installing kexts to my HD OS for awhile now - I just leave them in the ESP. so the _kext-install.command is optional in that regard. in fact needs to be updated for use with Mojave to perhaps install gfx kexts in /S/L/E vs /L/E. 

 

i compared the 1.52 DSDT to the 1.46 DSDT and i could not find any differences that would matter for macOS. The fix-region clover patch may make a change so i always use that option.

 

My 8GB/AUO LCD system has 2 disks, Disk0 (main disk) is Mojave and Windows10 and Disk1 (in my expansion bay) is a backup Mojave and HighSierra. So in essence has 3 OS.

i use the same config.plist kexts to boot Mojave and HighSierra - and I cannot see any difference in performance etc. otherthan some minor issues with Mojave LightMode etc.

both 10.13 and 10.14 have random glitches.

Share this post


Link to post
Share on other sites

@tluck thanks for the info!

I have not run the kext install command either, just wondering.. I know that I did when installing El Capitan, but it was not written as mandatory in the current guide, so I didn't.

 

What I meant about the DSDT file, was sthing like this:

OperationRegion (MNVS, SystemMemory, 0xDAF9D018, 0x1000)

vs

OperationRegion (MNVS, SystemMemory, 0xBAF9D018, 0x1000)

 

On my Fujitsu Laptop I had differences like this in my old and new DSDT after a motherboard replacement.

I only checked for that because some of the things did not work after mobo replacement, like battery, sound...

Maybe it was because it came with a newer BIOS, but I didn't check.

Is it correct to assume that if people use the same BIOS like yours, differences like this one should not be present?

It might not be relevant here, I don't know, but since then, I check for things like this :)

 

I just tried to boot now with the mojave plist in high sierra, and it worked. First time I tried it didnt, donno why.

 

EGPU also works in High Sierra with the appropriate nvidia web drivers, and reverting your SLOT1 modification in DSDT for EXP4, thats where is connected. Unfortunately no web drivers yet for Mojave..

 

Edited by davidian

Share this post


Link to post
Share on other sites

Comrades, I got a fresh small SSD today and let CCC do its job to clone from my USB-2 external.

10.14 is booting without crashing/lagging now. Could have very well been the old pATA drive via USB having issues.

 

The 10.14.1 upgrade did work without issues, a couple of boot trials were needed though.

GPU support did persist after upgrading.

 

Thanks all for keeping the T420 alive and updated!

 

Edit: KP got even worse now. I can boot MJ maybe 1 out of 8 times.

Don´t know whether I´d better give up and be content with Windows 10 / Sierra / HS.

The few times 10.14 boots, everything seems to be OK (except Preview) but a OS not booting can really become annoying. :(

 

I´m attaching my latest KP, hoping that someone finds the issue.

KP_MJ_10-14-1.rtf

Edited by goodguess

Share this post


Link to post
Share on other sites

@goodguess Does it happen also if you boot with -v flag (verbose)? It's just a curiosity, shouldn't have any effect unless it's maybe a timing issue or sthing I have no idea about. Everytime I couldn't boot and I tried to do a verbose boot after, to see what's what, it booted (for me it was High Sierra, Mojave didn't do this so far)..

Edited by davidian

Share this post


Link to post
Share on other sites

I tried with both my T420, the usual 16GB rig and the 8GB Windows machine.

As expected its not a -v issue. Both Thinkpads do have kernel panics, the Windows flavour maybe a bit less.

The KP always is like this, cpu 1 caller or cpu 2 caller do change. I never saw such in Sierra or HS.

 

Quote

*** Panic Report ***
panic(cpu 1 caller 0xffffff80084d84dd): Kernel trap at 0xffffff8008a067a0, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff8008f6342d, CR3: 0x000000000bfb6000, CR4: 0x00000000000626e0
RAX: 0x0000000000000000, RBX: 0xffffff801997a8c0, RCX: 0x0000000000000000, RDX: 0x000000000000c7c8
RSP: 0xffffff81093abb10, RBP: 0xffffff81093abb10, RSI: 0xffffff8008fb46ea, RDI: 0xffffff8008f6342d
R8:  0x0000000000005cee, R9:  0x000000000000b9dc, R10: 0x0000000000000001, R11: 0x0000000000000000
R12: 0x0000000000000853, R13: 0x0000000000000853, R14: 0xffffff801997a968, R15: 0xffffff801997a968
RFL: 0x0000000000010246, RIP: 0xffffff8008a067a0, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0xffffff8008f6342d, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 2


Edit1: I´m booting with -v in the config.plist meanwhile, and don´t see KP right now.

Whether this is some voodoo, or related to swapping SSD/HDD I can´t tell.

Maybe the T420´s sATA connectors degrade too over decades.

 

Edit2: Does anybody else have the issue with Preview (Mojave HD3000) not opening .jpg files?

PNG files do work as expected. Not a big issue, just wondering whether it´s a problem on my side.

Edited by goodguess

Share this post


Link to post
Share on other sites

Hi, 

Finally got Mojave working on the T420 (HD300 1600X900).

Noticed that the Brightness keys were not working. But then I see that the brightness slider is missing from the System Pref --> Display option. I thought we did have a brightness slider there.

 

Not sure where to look, is it a problem with the keyboard mapping or is some kext not working as it should.

 

I have done the Mojave Hack and also updated to the 10-31 zip. 

Share this post


Link to post
Share on other sites

Hey, 

 

i have a question again... i am running 10.13.6 and just bought a new wifi card: AR9280 AR5BHB92. it should be able to do 5GHZ, but i cannot see any network! The only think wich looks strange to me is, that the profiler just sais it can do up to channel 140 - and shuldnt be there 160 channels for 5GHZ? So if anyone knows how to fix that it would be just awesome!!!!

 

So my goal is to have it running in 300mbit 5hgz. Any chance to do that?

 

Cheers,

 

Pcace

32718776_Bildschirmfoto2018-11-12um21_11_23.jpg.74ceabc3a68299a553010534c71e2a6c.jpg932197702_Bildschirmfoto2018-11-12um21_28_46.thumb.jpg.b1857f7d1c7d62d671c6732a1a66b252.jpgB

Share this post


Link to post
Share on other sites

Hi,

 

Im kinda new to the hackintosh community and i have been trying to get OS X High sierra 10.13.6 to work on my T420 (2436)

So the problem that im facing is the graphics, i cant seem to get any higher resolutions than 960x600 with HD3000.

I have done everything as instructed in the tutorial, yet cant make it work?

Share this post


Link to post
Share on other sites

@goodguess I also have problems with Preview (Mojave) opening pictures, don't know why and didn't think to mention it here or check for different formats, but glad that you did!

 

As for the sATA connector degrade hunch, my gut tells me it can't be that, because then ElCapitan should do that too.. and for me it never did, it's the most stable Hackintosh I had so far on T420.

Edited by davidian

Share this post


Link to post
Share on other sites

@ snike: Not sure what you did, actually. The Mojave Hack is for Macs afaik.

Are you using the pre-build EFI folder, tluck posted at GitHub?

I have the slider and the brightness keys with my T420.

603007708_Screenshot2018-11-15at17_33_00.png.f689f1ef02fdebf646d58d042b7d8803.png

 

@ pcace: Thats really weird. You will hardly need channels above 140 though. :)

Ch 100 to 140 may run with 1000 mW, Ch 149 to 165 may only output 25 mW !

As a lazy guy, I´m using a DELL 1510 WiFi card, as I wanted a Broadcom chip.

 

345703376_Screenshot2018-11-15at17_41_25.png.63f53635084ba7b24309a1961da9cf8d.png

 

@Arttu: Did you select the correct config.plist in EFI/EFI/Clover from the package tluck offers?

A small screen lets me assume that your HD3000 kexts did not load correctly and/or that your T420 is running without GPU hardware acceleration.

Does Alt-Shift-3 work for taking a screenshot on your side?

Does your Graphics/Display section look like this?

 

2029603044_Screenshot2018-11-15at17_43_08.png.4a13bf389724f149c00a2eed56676bd8.png

 

 

Share this post


Link to post
Share on other sites
On 11/15/2018 at 12:20 PM, goodguess said:

@ snike: Not sure what you did, actually. The Mojave Hack is for Macs afaik.

Are you using the pre-build EFI folder, tluck posted at GitHub?

I have the slider and the brightness keys with my T420.

603007708_Screenshot2018-11-15at17_33_00.png.f689f1ef02fdebf646d58d042b7d8803.png

 

@ pcace: Thats really weird. You will hardly need channels above 140 though. :)

Ch 100 to 140 may run with 1000 mW, Ch 149 to 165 may only output 25 mW !

As a lazy guy, I´m using a DELL 1510 WiFi card, as I wanted a Broadcom chip.

 

345703376_Screenshot2018-11-15at17_41_25.png.63f53635084ba7b24309a1961da9cf8d.png

 

@Arttu: Did you select the correct config.plist in EFI/EFI/Clover from the package tluck offers?

A small screen lets me assume that your HD3000 kexts did not load correctly and/or that your T420 is running without GPU hardware acceleration.

Does Alt-Shift-3 work for taking a screenshot on your side?

Does your Graphics/Display section look like this?

 

2029603044_Screenshot2018-11-15at17_43_08.png.4a13bf389724f149c00a2eed56676bd8.png

 

 

I mean the hack for getting the HD3000 kexts. I am using the Pre built folder from Tluck's Github. This is how it looks for me 

 

Screen Shot 2018-11-17 at 10.09.02 PM.png

Screen Shot 2018-11-17 at 10.11.06 PM.png

Share this post


Link to post
Share on other sites

Hi, I don't know how but I'm just fresh install my hack 10.13.6, but even install all install*.command in Utilities, my Hack still got Sleep Wake Failure after wake from sleep, bluetooth, wifi and usb port is not working, and a few moment later my hack got panic!!

Share this post


Link to post
Share on other sites

SuperReaper, are you talking about Conti´s MyHack?

AFAIK Conti did stop development of his repository years ago.

Conti was using a Chameleon boot loader, fundamentally different from Clover, which is common grounds in this thread.

For a working T420 Hackintosh, you should install with Clover and use the repo tluck posted at GitHub.

There are many guides how to create a USB installer, every search engine will come up with some.

As you already seem to have a High Sierra OS installer, I would strongly recommend to go the Clover way.

After preparing the USB stick for the macOS installer, copy the EFI folder from tluck into the EFI partition of the stick. 

Select the config.plist from EFI/EFI/Clover that matches your T420´s screen, rename it to config.plist.

Boot from the USB device, set up your macOS volume and install - thats all.

 

On a side note, Chameleon was great work, back in the days.

I´m still using it with Snow Leo on my T60 - installed with Nawcom´s Mod CD. :)

Share this post


Link to post
Share on other sites

@SuperReaper - hard to know what is going on in your situation. i was able to install Sierra, HighSierra and Mojave with the same configuration i posted... 

 

 

@snike - where did you install the GFX kext in /L/E or /S/L/E? - i cant figure out how to not get the slider!? 

 

run these commands to see what you get:

 

ioreg -l|grep -v Diag |grep IODisplayPar

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |       "IODisplayParameters" = {"commit"={"reg"=0},"fade-time2"={"min"=0,"max"=10000,"value"=4000},"linear-brightness-probe"={"min"=0,"max"=4866,"value"=4866},"ggsc"={"min"=0,"max"=65536,"value"=65536},"vblm"={"min"=0,"max"=196608,"value"=65536},"dsyp"={"min"=0,"max"=2,"value"=2},"rgsc"={"min"=0,"max"=65536,"value"=65536},"fade-style"={"min"=0,"max"=10,"value"=0},"fade-time1"={"min"=0,"max"=10000,"value"=500},"bgsc"={"min"=0,"max"=65536,"value"=65536},"brightness-probe"={"min"=0,"max"=1024,"value"=1024},"fade-time3"={"min"=0,"max"=10000,"value"=500},"bklt"={"min"=0,"max"=4882,"value"=4866},"linear-brightness"={"min"=0,"max"=4866,"value"=4866},"brightness"={"max"=1024,"min"=0,"value"=1024},"brightness-fade"={"min"=0,"max"=1023,"value"=0},"usable-linear-brightness"={"min"=1220,"max"=4866,"value"=4866}}

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |       "IOMatchCategory" = "IODisplayParameters"

    | |       "IODisplayParameters" = {"brightness"={"max"=255,"min"=40},"commit"={"reg"=0}}

 

 

$ ioreg -l|grep -v Diag |grep ApplePanel

    | | |   "ApplePanelRawBrightness" = 4882

    | |       "ApplePanel" = {"F10T02e3"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>}

 

Share this post


Link to post
Share on other sites

@pcace on your wifi -- i have the same card. but i wonder if the range of values has to do with the locale set? mine is set to FCC... a long time ago i remember re-flashing the chip. i connect at 300 at 5 Ghz on channel 48

 

 

Quote

 

  Software Versions:

  CoreWLAN: 13.0 (1370.8)

  CoreWLANKit: 13.0 (1370.8)

  Menu Extra: 13.0 (1376.2)

  System Information: 12.0 (1300.2)

  IO80211 Family: 12.0 (1200.12.2)

  Diagnostics: 1.0 (805)

  AirPort Utility: 6.3.9 (639.7)

  Interfaces:

en1:

  Card Type: AirPort Extreme  (0x168C, 0x1081)

  Firmware Version: Atheros 9280: 4.0.74.0-P2P

  MAC Address: xxxxxxxxxxxx

  Locale: FCC

  Country Code: US 

  Supported PHY Modes: 802.11 a/b/g/n

  Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165

  Wake On Wireless: Supported

  AirDrop: Supported

  Status: Connected

  Current Network Information:

LuckyDog:

  PHY Mode: 802.11n

 Current Network Information:

LuckyDog:

  PHY Mode: 802.11n

  BSSID: xxxxxxxxxxxx

  Channel: 48,-1

  Country Code: US 

  Network Type: Infrastructure

  Security: WPA2 Personal

  Signal / Noise: -45 dBm / -96 dBm

  Transmit Rate: 300

  MCS Index: 15

 

Share this post


Link to post
Share on other sites
On 11/15/2018 at 6:20 PM, goodguess said:

 

@tluck Hey, Thank you for your quick response! I originally looked for the channels, because i cannot see my 5Ghz network, (which runs at channel 140 ?!)  - but with my proper MacPro i can see it. The second strange thing is, that it only uses a single channel, even if it is dualchannel - wich should allow connections up to 300mbit even in 2,4ghz. 

That was the reason why i imagined that there might be a problem related to the channels the card can see? But probably i am wrong. 
What exact chipset are you using? Or can you suggest one wich fits in the T420 and maybe also does triplechannel wifi on 5GHZ + runs out of the box? ?

If you have any idea... ....that would be just awesome!

Oh, there is no way to tell you how much i appreciate your work, support and help here! Just amazing!!! Thanks!

 

Quote

@ pcace: Thats really weird. You will hardly need channels above 140 though. :)

Ch 100 to 140 may run with 1000 mW, Ch 149 to 165 may only output 25 mW !

As a lazy guy, I´m using a DELL 1510 WiFi card, as I wanted a Broadcom chip.

  

345703376_Screenshot2018-11-15at17_41_25.png.63f53635084ba7b24309a1961da9cf8d.png

 

 

 

 

EDIT: 

@tluck

i just saw your second post! Thats what i was reading around but i never really found a definite answer, nor a definite way to reflash it.
I Guess i would have to reflash Vendor, Device and subvendor ID, + Vendor name? Do you know of any working tutorial for this?

I got the card working by just adding  "                <string>pci168c,2a</string>
" to "/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros40.kext/Contents/Info.plist 

 

Soooo if you know of any method... ...let me know!! Or maybe you could let me know what exact values your card runs on... ...ill figure out a way to flash it ;)

 

EDIT2: i guess i found a method. At least i dumped the Firmware as hex from the Atheros... did this with a tool i found here: https://github.com/andyvand/AtherosROMKit

 

But i just cannot find the appropiate hex to change.. is anyone clever enough to find it? It is attached...

 

Thanks!!

hex_dump2

Edited by pcace

Share this post


Link to post
Share on other sites

@pcace do you have windows to test this card? the macOS atheros driver does not seem to be as "good" as the atheros windows drivers.
meaning i recall connecting at like 450 on windows, but just 300 for macOS? Note: i didnt have to edit/modify any atheros kexts drivers (other than adding in Mojave), it just works out of the box for that same card.

 

Edited by tluck

Share this post


Link to post
Share on other sites

Hi,

running 10.13.6 on my Lenovo W520 i7, 32 GB RAM, IntelHD3000 since 2 months or so.

Everything fine so far ... till last system update, maybe two weeks ago. Probably minor security update or so.

Since then I am not able to open some preference panes any more (keyboard, mouse, trackpad, accessibility)

Regarding the first three i get a message that it's not possible to open the panel because I am on an intel machine, with accessibility its's just a 'could not be loaded' message.

 

...added screenshots

 

Anybody having the same problem ?

Clue of a solution ?

 

 

accessibilty.png

keyboard.png

Share this post


Link to post
Share on other sites
On 11/20/2018 at 10:56 PM, goodguess said:

i bought this cos the one i had wasn't compatible

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   1 member

  • Similar Content

    • By Abhiabhash
      I have a lenovo laptop with pentium 2020M 2.4ghz with 4gb ddr3 ram intel graphics and 500gb wd hdd i wanted to install hackintosh on my pentium for editing purposes beacuse windows sucks so can you please tell me how can i install it and which version should i install
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By tbianco
      Ho comprato da poco un Acer Aspire 5750G e girando su internet ho trovato la cartella efi che garantiva quasi tutto funzionante perfino il wifi (https://github.com/zipippino/HighSierraAspire5750G).
      Allora felicissimo installo macOS e a parte incappare in errori stupidi, riesco a fare tutto, ma quando sono riuscito ad installare clover Legacy e sostituendo la roba con la 'mia' efi clover si avvia ma macOS no, semplicemente non carica (si nota anche pk la spia dell'hdd che dice se è in attivitá è spenta.
      Qualcuno può aiutarmi?
    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not get iMessage to work properly. It worked precisely once, on my first installation attempt. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - if you can get NVRAM/PRAM working properly on this hardware, please do edit the config as you see fit.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JLMOX
      I think, at this point converting to hfs+ is out of the question, Apple has been pushing the apfs file policy very aggressively, so does anybody solved the missing "Boot macOS from Mojave " (this last word may be different). I have installed the latest clover in HDD and USB, but I can only see 3 Mac Os related tabs but not the one for actually loading the Mojabe mac OS. I updated high sierra to Mojave and everything went fine. My laptop (Dell E6530) booted up normally, Mojave system loaded up, I finished the setup and spent sometime exploring. I updated clover to the latest version and turned of machine. When I restarted, I noticed Clover did not have an option for booting into the system like High sierra had it. I tried adding the apfs.efi or the ApfsDriverLoader-64.efi driver to the clover efi folder in the HDD and also tried with a USB clover installation and the result is the same: No boot option for the Mojave OS. I used the recovery option and I was able to explore the partion where the system is located but that´s as far as I could go. Does anybody has an idea of what happened?

×