Jump to content

391 posts in this topic

Recommended Posts

Ah...
Edit the theme.svg file in a text editor and look for a line near the top of the file that defines the background scaling.

BackgroundScale="scale"

If it’s set to scale then change it to crop, or vice versa.

Share this post


Link to post
Share on other sites
Advertisement
10 minutes ago, blackosx said:

Ah...
Edit the theme.svg file in a text editor and look for a line near the top of the file that defines the background scaling.

BackgroundScale="scale"

If it’s set to scale then change it to crop, or vice versa.

 

BackgroundScale="scale" is the right parameters for my system. Now I don't understand why I can't see icons completely

Capture d’écran 2019-01-16 à 18.04.15.png

Share this post


Link to post
Share on other sites

Lol. That’s my carefully crafted icon design so they’re supposed to be like that. I like my MacOS icons to be distinguishable from each other and not all the same.

If you would prefer a simple Apple logo then you can edit the file and change each mac icon (os_moja, os_HighSierra, os_Sierra etc.) to use the default ImageMacOS (I think as I’m not at my computer) image.

Share this post


Link to post
Share on other sites
3 hours ago, blackosx said:

 

EDIT3: Maybe we could look at some Clover colour cycling for effects?....

 

Same way we can move or rotate or transform Banner .

The problem is we rendered all images before enter GUI. Except text.

May be we can remake Clover to render SVG images at draw time then we will have dynamic picture.

Share this post


Link to post
Share on other sites

It was just an idea that I was throwing out there :)

 

Drawing directly to the video buffer would be amazing but how much work would that require? and would it be worth the changes? Would people make use of if?

Share this post


Link to post
Share on other sites

You wouldn't be changing the image size, right? So you could actually just rasterize right back into the same image buffer since you wouldn't need the old image anymore and just continue to render using image buffer.

Share this post


Link to post
Share on other sites

Here's a revised version of the silver theme I posted the other day but this time is uses simple flat coloured icons on a flat coloured background. Its pink for now, but the user can easily set it to whatever colour they wish.

 

image1.thumb.jpg.5254899e9d5a7d05ee8862918d05c0a1.jpg

image2.thumb.jpg.795d7cc17b94cff5681c1d00eb1a1f2d.jpg

 

The idea here is the theme colours can be easily changed by the user by editing only the following values near the top of the theme.svg file. Far easier than searching and replacing different elements through the whole file for different settings.

 

This setting will change the colour of the menu selector.

<clover:theme
  SelectionColor="0xb20068FF"
/>

And these settings css classes can be used to change the other colours.

<style type="text/css">
  <!-- Change overall theme colours with these classes -->
  .FillColourContent{fill:#b20068;}
  .StrokeColourContent{fill:#b20068;}
  .FillColourBackground{fill:#380021;}
  .FontColour{fill:#f7a4d4;}
  .FontColourNight{fill:#f7a4d4;}
  <!-- -->
</style>

- FillColourContent will change colours of banner, badges, menu items and selectors.

- StrokeColourContent is just for Knoppix badge (for now - may need a re-work of this logo).

- FillColourBackground will change the background colour

- FontColour and FontColourNight as self explanatory. 

 

EDIT: The scroll bar, for now, takes it's colours from the FillColourContent and FontColour classes.

 

FlatCustom.zip

 

* This is still a work in progress but its completely useable as it is.

 

Edited by blackosx

Share this post


Link to post
Share on other sites

@Slice

New cesium theme has an issue with count down times, it cuts into the volume label. I took the screenshot with the times on the screen but its gone in the screenshot as you can see.

 

@Slice @blackosx

Also both Clovy and BGM_SVG themes freeze up if i let the countdown timer expire (10 seconds).

If this is just me it's happening too i will post files needed.

screenshot0.png

Edited by SavageAUS

Share this post


Link to post
Share on other sites

Yeah. I also experience a freeze with GUI using vector themes @SavageAUS.

 

I've been pretty busy recently so haven't run proper tests but using BGM_SVG I see freeze when:

- leaving timeout to countdown to zero.

- pressing return to boot selected boot device.

- pressing space and choosing to boot selected boot device from the menu.

 

I'll try to look in to it soon.

Share this post


Link to post
Share on other sites

@SavageAUS

The bug with messages on screen was resolved in Clover 4871.

May be the bug with freeze too. You should confirm it with recent clover.

 

I encounter some freezes that I can't still understand. It looks like vector theme rendering depends on hardware. I already reported that the same picture looks different with Intel and Nvidia cards. It's impossible because drawing performs same way as PNG theme, same procedures. The differencies only on image preparation, pure mathematics. But how mathematics may depends on graphics? I may suggest that float arithmetics run on Intel GPU :shock: if present. If it is true then it can be a reason why vector themes are not working on some hardware. For example, SavageAUS, did you have IGPU enabled in BIOS? What if reverse?

Share this post


Link to post
Share on other sites

Here, Clover will successfully load and draw both Clovy and BGM_SVG themes and present a working UI.


Testing with Clover r4871.

1 - If Theme entry in config.plist is BGM_SVG then on choosing to boot selected device, the GUI locks up.

2 - If Theme entry in config.plist is Clovy then on choosing to boot selected device, all is good and Mac OS boots.

3 - If Theme entry in config.plist is Clovy then I switch to BGM_SVG in Clover GUI, then on choosing to boot selected device, I sometimes get the GUI freeze, or I have sometimes see Clover successfully close and pass on to the next phase.

 

screen.jpg.a7360896f22ee2b241d3fd7264ed7b51.jpg

 

But I get a reboot after that.

 

Checking debug log, the last line is:

33:973  0:092  Finally: ExternalClock=26MHz BusSpeed=100001kHz CPUFreq=3400MHz PIS: hw.busfrequency=104000000Hz

 

Spoiler

28:215  0:002  Checking EFI partition Volume 15 for Clover
28:217  0:002  === [ GetEfiBootDeviceFromNvram ] =========================
28:276  0:059   - found entry 2. 'Boot macOS from HighSierra', Volume 'HighSierra', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(2,GPT,CE7D0665-EFE8-47C0-83CE-BC89C9C1938C,0x64028,0xDE4A310)\System\Library\CoreServices\boot.efii'
28:278  0:002  DefaultIndex=2 and MainMenu.EntryCount=14
28:280  0:002  Use anime=<null string> frames=0
33:875  5:595  BootVariable of the entry is empty
33:881  0:005  === [ StartLoader ] =======================================
33:973  0:092  Finally: ExternalClock=26MHz BusSpeed=100001kHz CPUFreq=3400MHz PIS: hw.busfrequency=104000000Hz
0:100  0:100  MemLog inited, TSC freq: 3400032970
0:100  0:000  LegacyRegion2: Chipset/proc: 0x01008086
0:100  0:000   Next Generation Core processors (PAM 0x80-0x86)

 

Is this behaviour memory related?

Could there be something in BGM_SVG, which is not in Clovy, which uses a different drawing routine which is causing the issue? I may try to remove items from BGM_SVG, one by one, and see if it makes a difference.

Share this post


Link to post
Share on other sites

:blink:

I see something new on your screen

RegisterData protocol installed successfully

What is it? If 10.13.6 then I also use the system and see no such message.

What drivers do you use in drivers64UEFI folder?

 

About theme differences I am not sure if it will be very useful to know what picture causes the crash but yes it still looks like a serios bug in rendering engine.

I tested in windows in QEMU with Clover compiled under VS2012. Vector themes have no OS_icons. It may be a bug of VS2012 compilation. Or may be the bug of the render.

Share this post


Link to post
Share on other sites

I'm not sure exactly what drivers I have in my Clover sub directory. I can check when I get home tonight.

 

However, that protocol comes from boot.efi

$ strings /System/Library/CoreServices/boot.efi | grep RestartData
RegisterRestartDataProtocol
Failed to install the RestartData protocol.
RestartData protocol installed successfully.

I guess this triggers the reboot after presenting the screen messages in the photo. 

 

Would trying to identify what makes boot.efi load that protocol help narrow down the issue, though maybe boot.efi just loads that if 'anything' is wrong so it probably won't help.

Share this post


Link to post
Share on other sites
2 hours ago, blackosx said:

I'm not sure exactly what drivers I have in my Clover sub directory. I can check when I get home tonight.

 

However, that protocol comes from boot.efi


$ strings /System/Library/CoreServices/boot.efi | grep RestartData
RegisterRestartDataProtocol
Failed to install the RestartData protocol.
RestartData protocol installed successfully.

I guess this triggers the reboot after presenting the screen messages in the photo. 

 

Would trying to identify what makes boot.efi load that protocol help narrow down the issue, though maybe boot.efi just loads that if 'anything' is wrong so it probably won't help.

Usually boot.efi search for external protocols. If it embedded then it can't be failed!

So some efi driver or even UEFI BIOS should provide this protocol. Is it 10.13.6?

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 Reel
      All work except camera
      You need SwitchResX that the screen does not freeze
         


    • 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
       
      Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM?
       
      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 at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence.
       
      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.
       
      My USB 3 ports seem to suffer from low power output, and I don't know why.
       
      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 JhonneR
      Good morning, everyone, I'm sorry if I was wrong in choosing the topic but I need help.
      I have found it extremely difficult to mount a Hackintosh in my acer.
      Setup;
      I5 2430m 2.4 6GB RAM
      Mobo P5we0 - Intel intel Graphics 3000
      At the moment I have not found out what my audio codecs are.
      but I'll leave the link on the motherboard.
      however, my real problem is several.
      I have already used the itakos image, I have already used several images that could be installed normally and that after installing the image I do not have internet via cable or wireless.
      And another, I already looked in other forums and I know that I will be called a donkey in the logical question but I have not been able to install the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or clover to start from the Hard Disk, so I do not know what to do.At the moment I still do not know if there has already been someone who has already installed the High Sierra or just the Sierra in this notebook model and obtained permanent success.
      If anyone can help me, I'll be grateful.
      Installations without success, but with the system already installed in ACER;
      SIERRA
      HIGH SIERRA
      MOJAVE
      All with the same symptom. Starting only by the bootable USB stick and without internet connection via cable and wireless.
      Appreciate ! Acer 5750 Official Page
    • 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 corbrink
      Hi,
      I have the following system:
      - Gigabyte Z370M-D3H M-ATX
      - Core i7-8700K Coffee Lake
      - Gigabyte Radeon RX 560 4GB
      - Crucial Ballistix 16GB DDR4
      - 960 EVO 1TB NVMe SSD
      - 850 EVO 500GB SSD
      - Crucial 500GB SSD
      - The 2 500GB SSD's run in Raid for data storage.
      - Western Digital 3TB HDD - Time machine
      - EFI here (too large to attach): EFI.zip

      Questions:
      1. I have a dual screen running from Radeon card, 1 on DP and 1 on HDMI. The one screen on DP goes randomly blank from time to time. Any ideas?
      2. I've read that the kexts should preferably be installed in /library/extensions. I would like to know what kexts should remain in the EFI. I read that you should install FakeSMC in both locations (EFI and L/E). If I follow this route must I change something in the config.plist?
      3. USB info in System Information (attached does not seem correct. I've followed the changes suggested but I'm not sure if this is the best it can be.
      4. Are there something in the EFI and config.plist I don't need or doing wrong?

      Feedback will be appreciated.


×