Jump to content
fantomas1

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

About USB max limit port patch, use this one instead under 10.13 (17A306f) Target kext changed from AppleUSBXHCIPCI to AppleUSBXHCISPT but the patch seems to be the same at list in my system.

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Comment</key>
<string>change 15 port limit to 26 in XHCI kext (100-series)</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>g32MEA==</data>
<key>MatchOS</key>
<string>10.13.x</string>
<key>Name</key>
<string>AppleUSBXHCISPT</string>
<key>Replace</key>
<data>g32MGw==</data>
</dict>
</plist>

Share this post


Link to post
Share on other sites
Advertisement
​​​About USB max limit port patch, use this one instead under 10.13 (17A306f)

<string>change 15 port limit to 26 in XHCI kext (100-series)</string>

​...

Thank you.

​Question:

 

Is it safe now to do this? I mean because it was a 15 port limit because some potential crash / or overflow in apple XHCI usb driver. Does this fix / avoid that crash overflow (above 15 ports used) ? I ask Rehabman about this a while back. But at that earlier time he said there was no known fix (it being an issue in apple's code)....

 

Yes I know its still ok that many people who just use USBInjectAll.kext and do not bother to worry. Who dont disable any USB ports. And those other guys who have NUC or laptop with much fewer USB ports = less than 15 total. It doesnt matter for those guys.

Share this post


Link to post
Share on other sites

Also, as a side note, there's no need to argue over such topic. I mean, seriously. :)) We're a community. We don't compete over who's right or wrong. There's no such thing. Anybody can be equally right and wrong. The point here is to learn from each other's successes and failures so we can evolve together as a community.

 

 

I second that; but: the question was if it was possible to install DP4 on HFS+j on a SSD. I think it's proven enough that it is.

He is arguing on the answers that are given to him in a way that is, well, not so friendly. But enough about that.

 

Anyway, 

The reason why I'm still using HFS+j is because Sierra and High Sierra are on the same disk. 

When I tried APFS it corrupted my partition map and both partitions were not able to mount anymore, which forced me to reinstall everything. 

 

When HS final is out I will wipe the SSD and I will install HS on APFS

Share this post


Link to post
Share on other sites

Thank you very much for your reply. :) As I said at the beginning of my previous post, if you wanna have it done that way, you can have it. And you definitely prove that that's possible.

 

Now, about the reason you're sticking to HFS+... Actually, I'm using Sierra and High Sierra on the same SSD (different partitions, of course). But....I've got no issues. Sierra uses HFS+, High Sierra uses APFS. Not sure how did that happen in your case. Surely not something you would want. But...it didn't happen to me. I was also a bit reluctant to try High Sierra (especially in APFS) on the same drive. But yeah, I got no issues here.

Share this post


Link to post
Share on other sites

Thank you very much for your reply. :) As I said at the beginning of my previous post, if you wanna have it done that way, you can have it. And you definitely prove that that's possible.

 

Now, about the reason you're sticking to HFS+... Actually, I'm using Sierra and High Sierra on the same SSD (different partitions, of course). But....I've got no issues. Sierra uses HFS+, High Sierra uses APFS. Not sure how did that happen in your case. Surely not something you would want. But...it didn't happen to me. I was also a bit reluctant to try High Sierra (especially in APFS) on the same drive. But yeah, I got no issues here.

It did boot at first without issues. Then I enabled Trim and verified the disk through disk utility but it said it couldn't due to a corrupted partition map.

The next time I booted the machine it ran fsck and BAM! Partitions gone. I don't know if it was a bug or an error at my hand, but i find it too risky to try again  :lol: 

 

Even more because like I said, once HS is out I will wipe the SSD and install HS @ APFS on it  :) 

 

Good to hear that you're not experiencing any issues though.

 

I need to say that I did not install HS on APFS right away, since it would only let me install on a HFS+ journaled disk, no idea why...

So I converted the disk to APFS through terminal after the installation

Share this post


Link to post
Share on other sites

You might wanna know that I got TRIM enabled too. :D And...I've rebooted probably tens of times since then. No issues whatsoever. So there might be something else going on with your drive...

 

How did you enable TRIM? Cause there's one way with a kext, if I'm not mistaken, something called TRIM enabler. And there's another way through terminal, using sudo trimforce enable (that's what I used).

 

I have to say, pretty weird issue you're describing there.

 

However, I perfectly understand why you're not feeling very comfortable with APFS at this point in time. You have every reason to feel like that. And yeah, after all, it's still a beta. And if that was a bug, which is not impossible, we can hope it will be fixed until the final release, so you can update as well, this time with no issues.

Share this post


Link to post
Share on other sites

Thank you.

​Question:

 

Is it safe now to do this? I mean because it was a 15 port limit because some potential crash / or overflow in apple XHCI usb driver. Does this fix / avoid that crash overflow (above 15 ports used) ? I ask Rehabman about this a while back. But at that earlier time he said there was no known fix (it being an issue in apple's code)....

 

Yes I know its still ok that many people who just use USBInjectAll.kext and do not bother to worry. Who dont disable any USB ports. And those other guys who have NUC or laptop with much fewer USB ports = less than 15 total. It doesnt matter for those guys.

I havnt tested the new patch but since Sierra I have been using a custom ssdt with UsbInjectAll.kext. Even in HS the same ssdt.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

 

 

Update:

 

After re-reading Chris' post (thanks Chris), looks like it does occur for SATA SSDs, as well. Cool! That answers our No. 5 question.

Yes its possible and if the people read this Post  correctly It is very easy to install in APFS or HFS + J and to have Clover install in UEFI or ESP even on a volume apfs

I find it a pity that people are a lot of trouble to install HS and that it still uses the Core.pkg method which in fact does not even create certain Essential Volumes. They find themselves with an uncomplete instalation

Share this post


Link to post
Share on other sites

Yes its possible and if the people read this Post  correctly It is very easy to install in APFS or HFS + J and to have Clover install in UEFI or ESP even on a volume apfs

I find it a pity that people are a lot of trouble to install HS and that it still uses the Core.pkg method which in fact does not even create certain Essential Volumes. They find themselves with an uncomplete instalation

 

The Core.pkg method is really not a good one, but really a bad one. :thumbsup_anim:

Share this post


Link to post
Share on other sites

Hello Everyone ,, Trying to boot the Clover Legacy but it doesent show the apfs partition. Renamed the apfs efi to apfs-64 efi and paste it to the drivers64 .. but it still cant show the apfs partition

can any one help me or send me the clover legacy apfs please.. Thanks 

Share this post


Link to post
Share on other sites

Hello Everyone ,, Trying to boot the Clover Legacy but it doesent show the apfs partition. Renamed the apfs efi to apfs-64 efi and paste it to the drivers64 .. but it still cant show the apfs partition

can any one help me or send me the clover legacy apfs please.. Thanks 

apfs.efi go in drivers64uefi without renaming.

Share this post


Link to post
Share on other sites

Hello guys,

 

Today I accidentally discovered this wonderful topic (since I am collecting different patches for broadcom 4360 kext).

My idea is to implement a new Lilu plugin to patch this kext in the more intellectual way, just not by replacing bytes (thanks to @PMheart for the initial idea).

It's called AirportBrcmFixup: https://sourceforge.net/projects/airportbrcmfixup/

And here I found out that I missed something: BCM4352-iovar. 

I was not able to find any explanations what this patch actually does.

What is the influence of this patch?

 

Could somebody answer to my question, please?

 

 

hello 

airport extreme fix here

enjoy :)

 

BCM4352-Airport-Extreme, (credit skvo)
com.apple.driver.AirPort.Brcm4360
6b100000 750d
6b100000 9090
10.13.x

BCM4352-Airport-Extreme, (credit Sherlocks based on skvo original)
com.apple.driver.AirPort.BrcmNIC
6b100000 750d
6b100000 9090

BCM4352-fvco, (credit Sherlocks based on the-darkvoid original)
com.apple.driver.AirPort.BrcmNIC
81f952aa 000074bf
81f952aa 00006690

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC
85db4c8b 65c87971
85db4c8b 65c8eb71

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC
4883c410 89c385db 7946
4883c410 89c385db eb46


BCM4352-Airport-Extreme, (credit Sherlocks based on skvo original)
com.apple.driver.AirPort.BrcmNIC-MFG
6b100000 750d
6b100000 9090

BCM4352-fvco, (credit Sherlocks based on the-darkvoid original)
com.apple.driver.AirPort.BrcmNIC-MFG
81ff52aa 000074c4
81ff52aa 00006690

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC-MFG
0f896201 0000
0f886201 0000

BCM4352-iovar, (credit Sherlocks)
com.apple.driver.AirPort.BrcmNIC-MFG
4883c410 89c385db 7944
4883c410 89c385db eb44

 

Share this post


Link to post
Share on other sites

Hello guys,

 

Today I accidentally discovered this wonderful topic (since I am collecting different patches for broadcom 4360 kext).

My idea is to implement a new Lilu plugin to patch this kext in the more intellectual way, just not by replacing bytes (thanks to @PMheart for the initial idea).

It's called AirportBrcmFixup: https://sourceforge.net/projects/airportbrcmfixup/

And here I found out that I missed something: BCM4352-iovar.

I was not able to find any explanations what this patch actually does.

What is the influence of this patch?

 

Could somebody answer to my question, please?

Actually didnt see difference.

But you can get iovar error in HS kernel log.

I just disable iovar error and enable iovar stuff on HS dp1.

 

If use iovar patch, log is fine. But flood log. Ofc iovar error log also flood.

 

Maybe we need to wait HS release. Then see kernel log. As result, skip iovar patch once. After release HS, then consider iovar error

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Actually didnt see difference.

But you can get iovar error in HS kernel log.

I just disable iovar error and enable iovar stuff on HS dp1.

 

If use iovar patch, log is fine. But flood log. Ofc iovar error log also flood.

 

Maybe we need to wait HS release. Then see kernel log. As result, skip iovar patch once. After release HS, then consider iovar error

 

나의 LG-F800S 의 Tapatalk에서 보냄

Thank you for the fast reply!

So it is only related to some annoying messages in the kernel log.

I think we can wait for HS release.

 

In 10.13 I still have issues with natively supported SD Card Reader and Ethernet Card (both Broadcom), hopefully they will fix all broadcom stuff.

Share this post


Link to post
Share on other sites

Anyone have a GeForce 6600GT working natively with High Sierra? If so is it possible to add this card in with my 960 and have the 960 for Sierra and the 6600GT for High Sierra?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Anyone have a GeForce 6600GT working natively with High Sierra? If so is it possible to add this card in with my 960 and have the 960 for Sierra and the 6600GT for High Sierra?

 

Sent from my SM-G930F using Tapatalk

it is better to switch to rx480 for high sierra

Share this post


Link to post
Share on other sites

Yes, with Lilu and Whatevergreen the newest AMD GPUs work without Helper Card. No Blackscreen anymore.

Thank you for this info! I was wondering if anyone managed to get it to work without it.

 

What's still weird to me....is that this is one of the cards which is supposed to work "OOB". But here we are looking for workarounds, and using helper cards and all that which makes the entire experience totally not "OOB". :))

 

I'm using an old GTX 650. To me, working OOB means plug & play. Connect the card, start your computer, enjoy. No kexts, no tricks, no nothing. It's still not very clear to me why do we need these kexts and patches for this case. Maybe someone can give us a bit more information on that.

 

I suppose it should work the same way with the RX580, right?

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
      Mac Downloader (thanks to ricoc90)
      Stuck boot in Beta 5 (thanks to MaLd0n)
       
    • 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) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : 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
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.6_18G87
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.6.zip
       
    • By Lucalab03
      INSTALLATION GUIDE (BY ME):
       
       
       
      FIX ALL PROBLEMS (BY ME):
       
×