plistutil command man page - libplist ManKier

Success To Be [OC, M.2 DualBoot, AMD R5, RX 5700 XT, 16GB RAM, BCM94360CD]

Success To Be [OC, M.2 DualBoot, AMD R5, RX 5700 XT, 16GB RAM, BCM94360CD]

OpenCore AMD DualBoot Hackintosh! This would absolutely not have been possible without this community and especially Khronokernel! Many, many thanks - this is my first Hackintosh and self-built PC!! :D


See also: OpenCore config below!
Part Model
CPU AMD Ryzen 5 3600X 3.8GHz 6C
Video Card PowerColor Radeon RX 5700 XT 8GB Red Devil
Memory G.Skill Ripjaws V 2 x 8 GB DDR4-3200C14
Storage ADATA XPG SX8200 Pro 2TB M.2-2280 NVMe SSD
Power Supply Corsair HX750 750W 80+ Platinum Certified Fully Modular ATX
CPU Cooler Noctua NH-D15S
Case Fan 2x Noctua NF-A14 PWM 140 mm
Thermal Paste Thermal Grizzly Kryonaut, 1g
Case Fractal Design Meshify C ATX Mid Tower
Monitor AOC 24G2U/BK 24" 1920x1080 144Hz
Keyboard Apple MB110LL/B Wired
Mouse Logitech G Pro Wireless Optical
Wifi/BT Card via PCIe Fenvi BCM94360CD, AliExpress (Fenvi FV-A436CD)
USB 3.0 PCIe Card Some cheap thing (no brand found?!) I had laying around, not expected to work on macOS, good on Win10
PCPartPicker Part List (without BCM94360CD) About $1600, most parts - especially the expensive ones - where bought on sale, though!
I had these goals in mind:
  • Hackintosh, of course!
  • DualBoot
  • 2K Performance (Everyday PCing to AAA Gaming) with proper heat management, unlike Apple
  • Longevity, my previous Main, a MacBookPro 13'' (Early 2011), still flourishes! :) Good boi!
  • Low noise, hence the Powercolor Graphics Card and the beefy NH-D15S (also for performance)
  • As little dust as possible (see case)
  • As small as possible - without compromising on goals
  • As little RGB as possible (sorry.), which turns out to be difficult
Max credit goes here and here!! Also, here, here, here, here and here. Totally solid work, guys! This Project was started on December, 1st 2019. Now it is February, 7th 2020!


  • Vanilla Hackintosh
  • OpenCore 0.5.5
  • DualBoot on one 2TB M.2 SSD with Win10
  • AMD Ryzen 5 Processor with RX 5700 XT (Navi 10) and 16GB RAM on MSI B450
  • Wifi and BT via BCM94360CD over PCIe (Windows compatible)
  • Sleep/wake works
  • Fixed iServices, even though I probably won't use them...
  • I consider my goals met.
  • Mapped USB ports, see below.

Known issues

  • Bluetooth is always "on", but not working. Probably USB Mapping; Resolved here.
  • Internal drives shown as externals (yellow-orange). Solved..
  • Black screen when setting resolution to 1080i instead of 1080p in system preferences. Minor issue.
  • Cannot boot into Recovery mode. Solved.
  • Won't sleep after set time (system prefs). "HibernateMode" set to "Auto" in config & port mapping KEXTs, see below.
  • Cannot adjust volume of built-in-monitor speaker (DisplayPort)~~~~. Solved with software.
  • Some Motherboard RGB issues - Solved by USB Mapping.
  • Choosing to boot into Windows via Bios (F11) - I don't consider this much of an issue.
I will try to solve these issues in separate threads and update this one, but any help much appreciated! Any comments - e.g. on Kexts; do I need them all?! - are welcome too...

Not tested yet

  • Microphone jack on case.
  • FileVault - don't need that, probably won't test

Advice for interested people


My Hackintosh configuration

  • OpenCore 0.5.5
  • macOS Catalina 10.15.3
  • The following EFI is on my OpenCore stick. There is also the latest macOS on there. If you go for DualBoot, keep this stick around & updated as Windows seems to be able to mess around with your EFI... With this stick you'll always be able to boot your Hackintosh and repair its EFI partition.
  • FULL EFI FOLDER: See in comments ("PlatformInfo" has to be populated in config.plist - see below... You can copy over the info from your current config. Also, my changes in DeviceProperties/Add might be a problem for your storage setup.)
  • OpenCore EFI files:
  • Config.plist: EDIT: See comments (only use if exactly same components as me; see below. Change according to OpenCore Guide!! [PlatformInfo removed; Populate this yourself like this!] I'd advice you to make your own config.plist.) Changed with ProperTree strictly according to the OpenCore Guide. Differences to sample.plist:
    • Probably outdated: All of the following modifications are for OC 0.5.5. If you are on a later version of OC it is likely that these have changed!
    • 5 initial Warnings removed.
    • DeviceProperties/Add: Removed "PciRoot(0x0)/Pci(0x1b,0x0)" and "PciRoot(0x0)/Pci(0x2,0x0)" as well as their children
      • Added Key "PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)" as child of "Add" with Type "Directory". Added child beneath the just made child with name "built-in", type "Data" and value "01000000". To address drive issue above, see here.
    • Populated this config.plist with OC snapshot function of ProperTree (CMD/CTRL+R, point to EFI/OC/) . Adds KEXTs and SSDT.
    • Kernel/Emulate: Removed "CpuidMask" and "CpuidData" (were blank anyway).
    • Kernel/Patch: Ryzen/Threadripper(17h) Patch applied.
    • Kernel/Quirks:
      • "DummyPowerManagement" set to True
      • "ExternalDiskIcons" set to True
      • "PanicNoKextDump" set to True
      • "PowerTimeoutKernelPanic" set to True
      • "XhciPortLimit" set to True (set to False after USB mapping in step F)
    • Misc/Boot:
      • "HibernateMode" set "Auto" after USB mapping
    • Misc/Debug: Nothing changed.
    • Misc/Security:
      • "AllowNvramReset" set to True
      • "AllowSetDefault" set to True
      • "AuthRestart" left False
      • "RequireSignature" set to False
      • "RequireVault" set to False
      • "ScanPolicy" set to 0
    • Misc/Tools: Shell.efi added by the OC snapshot function.
    • NVRAM/7C436110-AB2A-4BBB-A880-FE41995C9F82:
      • "boot-args" set to "-v keepsyms=1 debug=0x100 agdpmod=pikera alcid=1"
      • "nvda_drv" set to <>
      • "prev-lang:kbd" set to my preferences. (Use "656E2D55 533A30" = HEX for keyboard layout "en-US:0"; find your own with a TEXT to HEX converter and this.
    • NVRAM/"WriteFlash" set to True,
    • PlatformInfo: Populated with info according to the Guide with GenSMBIOS. Went with a "iMacPro1,1". Found "Purchase Date not Validated" numbers after about 3 (x10) times.
    • UEFI/Drivers: Drivers auto-added by the OC snapshot function.
    • UEFI/Input:
      • "PointerSupport" changed to "Data" and set to <>
      • "PointerSupportMode" changed to "Data" and set to <>
    • UEFI/Protocols/"ConsoleControl" set to True
    • UEFI/Quirks:
      • "ProvideConsoleGop" set to True
      • "RequestBootVarFallback" set to True
  • Bios settings strictly according to the OpenCoreGuide:
    • Disabled:
      • "Fast Boot"
      • "CSM" [UEFI instead]
    • Enabled:
      • "EHCI/XHCI Hand-off"
      • "Above 4G decoding"

My process (only successful part)

(You'll need 3 USB sticks! 2 with at least 4GB, 1 with at least 8GB. I am not sure, whether the Linux Part is really necessary, or if the partitioning can also be done from the macOS or Win10 stick...)
A) The basic build
  1. Built PC.
  2. Installed Windows 10 from USB stick [8GB] (made from Microsoft Media Creation Tool, instructions here, don't forget to install in UEFI mode - see second link in 3.!). Did some fan adjustments in BIOS too... Keep that stick!
  3. Set up Windows 10, installed drivers (see here, here).
  4. Installed Python 3.7! (For SSDTTime, below. Don't get Python 3.8.1!)
Do not set up Windows too much yet, it will be deleted completely and reinstalled again.

B) Creating the OpenCore Stick
  1. Followed Snazzy Lab's Video (read its description!) to create the OpenCore stick, everything on the above Win10: (useful additional help: khronokernel and VanillaAMD and Github)
    1. (Maybe format your stick to GUID HFS+ via Linux or Mac first... See Github.)
    2. Downloaded latest macOS via gibMacOs.bat (Recovery package!) (Admin privileges needed!). Update 7zip first for step B)1.II. and B)1.III. and use a Lan connection!
    3. Made a bootable install of that via Makeinstall.bat (Number + o) (Admin privileges needed!).
    4. Opened the EFI folder on the now newly made USB stick.
    5. Deleted everything (3 files) in EFI/OC/Drivers/, except FwRuntimeServices.efi.
    6. Deleted everything (2 files) in EFI/OC/Tools/.
  2. Put in the following drivers from AppleSupportPkg on the stick to EFI/OC/Drivers/:
    1. ApfsDriverLoader.efi
    2. VBoxHfs.efi
  3. Put KEXT and SSDT and Drivers on the stick:
    1. For troubleshooting afterwards - while booting from the stick - consult: khronokernel/troubleshooting!!
    2. Put the above KEXTs on the stick, all in EFI/OC/Kexts (instructions: khronokernel, more kexts: onedrive).
    3. Put the following SSDTs on my stick (into OC/ACPI)
      1. See above! SSDTTime not needed.
    4. Created config.plist with ProperTree (search with crtl+f!) (full instructions: khronokernel plus config documentation mentioned above in B)3.a.!!):
      1. Renamed "simple.plist" in the downloaded OpenCorePkg folder to "config.plist" and copied it over to the stick into EFI/OC/.
      2. Open Propertree.bat (Admin privileges maybe needed!) and opened said config.plist via the menu bar "File" of proper tree.
      3. Created my own config via "OC snapshot" in the menu bar "File", navigated to EFI/OC of my stick.
      4. Patched my config with patches.plist from AMD_Vanilla (17h): Open simultaneously in ProperTree. (See Snazzy Laps Video and this on how!)
    5. Edited config.plist, followed Vanilla Guide/amd-config.plist (partly later because of errors): See above!
    6. Saved via menu bar "File".

C) Created bootable Linux stick and made partitions on my internal SSD for dual boot (I was recommended this procedure here), install macOS:
  1. Still in Windows 10: Followed the Ubuntu Tutorial to make another stick.
  2. Shut down Windows 10.
  3. Booted again, with the OpenCore Stick connected, temporarily changed the boot partition with F11 and chose my stick (some of the above mentioned config.plist changes were applied AFTER this step, because certain errors occured):
  4. Got to the boot picker and reset NVRAM.
  5. Restarted the same way and chose the macOS installer (Step 3).
  6. Went into the macOS installer's Disk Manager. Formatted the whole internal SSD (maybe ExFat? Probably doesn't matter) and made two partitions for macOS (APFS) and Windows (don't remember what, maybe ExFat?, doesn't matter)
  7. Exit the Disk Manager and enter the installer. Install macOS. Maybe create a backup of that.
  8. Do this: Especially the EFI copying! How to mount the EFI partition on macOS.
  9. Shut down.

E) Created Windows:
  1. Booted into Linux, via Stick.
  2. Got synaptic and hfsprogs for Linux:
    1. Searched the Programs for "Software & Updates". Enable second option: Community-maintained free and open-source software (universe). "Close" this window and let it do it's download.
    2. Opened Terminal (Ctrl+Alt+T), entered:
      1. sudo apt-get update
      2. sudo apt-get install synaptic
      3. sudo apt-get install hfsprogs (not needed anymore?!)
  3. Searched for "Disks". Designated the 200MB partition from above as EFI (I believe via the cog wheels > Format Partition). Close that window.
  4. Searched in progs for "GParted":
    1. Format the second, partition to NTFS.
    2. (You should see three partitions on your internal SSD: EFI, Mac (APFS - probably unrecognised) and Windows)
  5. Shut down Linux.
  6. Boot with Windows Stick connected into the Windows installer.
  7. Install Windows on that NTFS partition.
  8. (Mac and Windows will write their EFI on the same partition! Keep at least your OpenCore Stick!!)
F) Finished. Set up both machines (Windows: here and here) completely!! :D
  • Mapped my ports by removing the XHC0 controller with this kext completely (lost two ports in the process, but that's ok) and (optionally) mapped the PTXH controller with this kext (you might have to adjust this!). For why, see here. See here and here, too!
  • Disabled OpenCore logging: Values set to 0. (In config above not included!)
  • Found "valid" SMBIOS numbers, fixed iServices according to this. (In config above not included!)
  • Didn't enable FileVault or OpenCore Security Features yet... Probably won't.
submitted by CrayCJ to hackintosh [link] [comments]

Gigabyte Z390 M, OpenCore, and Hackintosh Catalina: A Beginner’s Guide and Key Resources

Gigabyte Z390 M, OpenCore, and Hackintosh Catalina: A Beginner’s Guide and Key Resources
My setup!


I realise build guides are a dime a dozen, but it’s always reassuring to see one by someone who’s used a combination of components as similar to yours as possible, and even more so when that someone happens to be a newbie. So here I am, with the steps I followed to get macOS Catalina up and running on the tower I’d built.
I’ll take this step by step, and will make an effort to avoid confusing language. Of course, if you have any questions, feel free to ask, after you’ve read the whole thing! Just bear in mind that I, too, am a novice.
Moreover, I have next to no experience with Ryzen builds, or prebuilt machines like laptops, so again, this guide is specific to modern Intel builds and chipsets. If you need help selecting components, look no further than this brilliant, concise primer by Mykola. My guide is by and large limited to the processes I followed, though I’ll try to include alternative steps for anyone that may need them.
Lastly, this guide may be extra handy for Indian Hackintosh enthusiasts — all my components were purchased in in India itself. So if you’re a fellow Indian interested in building one of these for yourself, there’s a good chance these components are readily available for you without having to import anything. But first, some vanity shots:

My old faithful 1080p ASUS monitor, I hope to replace it with a better 1440p 100% sRGB one soon!

Pretty low-end as far as cases go, but very practical! NZXT cases are quite expensive in my country...

The innards! It's actually a lot better cable-managed than it looks here.
The innards! It's actually a lot better cable-managed than it looks here.
Before You Get Started:
You HAVE to be a computer enthusiast, and have basic knowledge of how computers work. It’s crucial that you understand that there are no shortcuts to this.
Morgonaut’s videos on YouTube are an example of what not to do — if you blindly follow what someone spoonfeeds you without truly understanding why something works the way it works, you’re setting yourself up for failure, and we won’t be able to help you because you wouldn’t be able to tell us what you’ve done.
This also applies to tonymacx86 tools like Unibeast; they take user-intervention and transparency out of a process that absolutely depends on both of those to work reliably.
Hackintoshing is a precise process to begin with, and what works for someone else may not necessarily work for you. Take the time and effort to read through every line of the more specific guides I’ll be linking further ahead, and toggle exactly what is specific to your hardware. What you don’t get, Hackintosh and its Discord channel will be happy to lend you a hand with.
Don’t be anxious! It’s an intimidating prospect when you’re doing it for the first time, but once you’ve got everything up and running, you’ll realise that the process is actually pretty straightforward.

The Hardware:

The first thing you’ll need to do is, of course, build a computer, so build a computer, I did. Here are my components:
The parts that will affect your Hackintosh setup:
  • Motherboard — Gigabyte Z90 M
  • Processor — Intel i7-9700K
  • Graphics Card — Sapphire Pulse Radeon RX 580
  • Storage — WD Black SN750 (500GB)
  • WiFi + Bluetooth PCIe Card — Fenvi HB-1200
The parts that normally won’t:
  • RAM — 32GB, 2400MHz, DDR4 (Crucial CU16GU2400, 16GB x 2)
  • Power Supply — Antec NeoEco 650M (650W, rated Bronze)
  • CPU Cooler — Antec C400 Elite
  • Case — Corsair SPEC 01
  • Fans — Antec Spark 120mm x 4 (that’s a total of five fans, including the one that comes with the case)
You’ll notice that I’m using a Z390 motherboard, something Mykola explicitly advises against in the guide I’d linked above. He’s right — the best motherboard for Hackintosh computers is the slightly older Z370 series. It supports all the same processors that the Z390 chipset does, though you’ll need a BIOS update to run 9th gen Coffee Lake chips. More importantly, Z370 boards come with native NVRAM support, which is something macOS requires to function smoothly.
The Z390 motherboards don’t have native NVRAM, but there’s a workaround to emulate it. If you’re starting from scratch, this becomes an unnecessary step, so stick with the Z370 series. However if you, like me, weren’t aware of this at the time of buying your components, no stress! The workaround to emulate NVRAM support is a rather easy one.
Besides this, the other oddity you’ll notice is the Fenvi HB-1200. Here’s the deal: MacOS normally plays well only with very specific Broadcom cards for perfect WiFi and Bluetooth connectivity. So if you want AirDrop and Handoff to function properly on your Hackintosh build, you’ll need one of these things. Installing them is very easy, though, and if you’re unable to find one locally, AliExpress sells these in great abundance. It’ll take about 2-3 weeks to reach you, though. Until then, your only option for internet connectivity is via Ethernet. A more high-end alternative of the same is the Fenvi T919.
Finally, macOS has no built-in framework for controlling the RGB lighting in your system. If you want to control the lighting via your motherboard’s RGB header, you’ll have to do it via BIOS. If even this option isn’t available, a hardware remote is your best bet*, I’m using this one.
*You can mess with your RGB settings via Windows and have your settings persist when you reboot into macOS, but for this, Windows will have to be installed on a partition in the same disk as macOS. This often causes a number of complications and is generally not recommended.
We now move on to the nitty and the gritty, the part of this process that puts the “Hack” in Hackintosh:

Setting up macOS Catalina:

The recommended method for getting started with a Hackintosh build — the vanilla method — involves having an actual Mac device around. It gives you the simplest, most reliable, and trustworthy way to download a fresh copy of macOS Catalina, straight from Apple’s own App Store. The download itself is free and won’t cost you anything. If you don’t own a Mac, borrow a friends’ — this way, you can also natively format your Catalina USB drive to a Mac-compatible format using macOS’ built-in tools, rather than having to rely on third-party methods.
With this in mind, the guide I’d followed is the OpenCore Vanilla Desktop Guide, once again by the brilliant Mykola. I’ll be referring to this multiple times, and will straight up link directly to it where I don’t have anything specific to my experience to add. Remember, my guide is sort of like an addon to Mykola’s Vanilla guide, and is NOT meant to act as a replacement.
A proven alternative method for those don’t have access to a Mac is Midi Jari’s Internet Install method. I have no experience with this, though, so I can’t really comment on what this entails. But it’s also a trusted method and has produced successful results for many folks here, so don’t stress out unduly! It’s just not something that I personally have used, given I simply borrowed my girfriend’s MacBook for this purpose.
The only other hardware you’ll need is a 16GB USB drive. Until macOS Mojave — the previous version — 8GB USB drives were enough to hold macOS, but unfortunately, Catalina is slightly larger than 8GB, so 16GB drives are the new minimum.
A Brief Prologue:
Here’s a grossly oversimplified primer on how macOS (or any OS, really) boots on a Hackintosh system:
BIOS —> Bootloader —> macOS
Similarly, let’s take this step by step.


First, your motherboard’s BIOS fires up. This is normally where the “Gigabyte” or “Asus” or whichever else company’s logo pops up, depending on your motherboard’s make. Here, repeatedly tapping on a button — which can vary from manufacturer to manufacturer — should take you to your BIOS’s settings. This is where your setup process begins.
MacOS requires a specific set of BIOS settings to be toggled, which can be a little daunting for first timers. Luckily, Mykola’s got your standard BIOS settings covered in his guide, so simply reset your BIOS to its optimised defaults, and make the necessary changes he’s highlighted here.
Once this is done, we move on to the big one:

The Bootloader, OpenCore:

The bootloader is the key to achieving a successful Hackintosh build, and this is where most of your efforts will be directed.
Ordinarily, on most Windows computers and actual Macs, the bootloader is invisible; you wouldn’t even know it exists beyond the existence of the loading screen. Given we’re off the beaten path, we will need to use a custom bootloader put together by several smart people in the community. This custom bootloader is what will let us boot macOS on non-Apple hardware.
Until very recently, Clover had been the standard bootloader for all Hackintosh builds. It’s well-documented, has a GUI that you’re used to operating, and comes with thousands upon thousands of guides and years of documented online support. It is also, however, nearing the end of its life. A lot of its code is deprecated, unmaintained, and can break anytime.
This brings us to OpenCore — a spanking new bootloader that many believe is the future of Hackintoshing. It’s designed to be a whole lot more flexible than Clover, and uses more modern protocols to offer a far stronger degree of futureproofiness — and dramatically faster boot times, to boot. There’s certainly a lot about it I don’t fully understand, but it’s been painstakingly documented over here in acidenthera’s GitHub page, so do pop over and give it a read if you’re interested.
It’s in the final stages of beta testing — v0.5.3 at the time of writing this — and aims to be released as a stable, public v1.0 build in the coming weeks. Given it’s so close to release, as long as you’re not running a laptop or a prebuilt, OpenCore will run just fine for you once properly setup. Seriously — if you’re not scared of a more transparent process where you have far more control over what your bootloader will end up doing, OpenCore is the way to go.
At this juncture, I’ll simply redirect you to Mykola’s guide, full on. It summarises the process of setting up OpenCore as simply as possible without skimping on important details.
I do, however, have three points to add:
  1. In this guide I’m writing, I’d originally wanted to include an issue specific to my motherboard model that Mykola walked me through because it wasn’t in the guide (and I’m a newbie), but he went ahead and added it to his guide so idiots like me wouldn’t run into the same problem in future; the parts of his guide referring to CFG Lock settings in the configuration file and the BIOS allude to this.
  2. Once you clone/download OpenCorePKG, use macbuild.tool to compile your copy of OpenCore. Once the process finishes, you’ll find the folder you need in the same folder, under:
Binaries > Release > (the contents of this zip file are what you ultimately need)
  1. HfsPlus.efi is preferable over VboxHfs.efi. This is because HfsPlus.efi is Apple’s own driver for reading HFS volumes, wheres VboxHfs.efi is a community-built, open source variant that’s quite a bit slower, but is a better bet if you prefer playing it safe and like your code open source.

My OpenCore EFI folder structure:

Here, you can also have a look at my drivers and kexts. You’ll also notice a file called SSDT-UIAC.aml which isn’t explicitly present in Mykola’s writeup, but is something every Hackintosh user needs to build for themselves. This particular file is called a custom SSDT, and I’ll get into it in just a moment.
EFI ├── APPLE │ ├── EXTENSIONS │ │ └── Firmware.scap │ └── UPDATERS │ └── MULTIUPDATER │ ├── Mac-BE088AF8C5EB4FA2.epm │ ├── Mac-BE088AF8C5EB4FA2.smc │ ├── MultiUpdater.efi │ ├── SmcFlasher.efi │ ├── flasher_base.smc │ └── flasher_update.smc ├── BOOT │ └── BOOTx64.efi └── OC ├── ACPI │ ├── SSDT-AWAC.aml │ ├── SSDT-EC-USBX.aml │ └── SSDT-UIAC.aml ├── Drivers │ ├── ApfsDriverLoader.efi │ ├── FwRuntimeServices.efi │ └── HFSPlus.efi ├── Kexts │ ├── AppleALC.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── AppleALC │ ├── IntelMausi.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── IntelMausi │ ├── Lilu.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── Lilu │ ├── SMCProcessor.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── SMCProcessor │ ├── SMCSuperIO.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── SMCSuperIO │ ├── USBInjectAll.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── USBInjectAll │ ├── VirtualSMC.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── VirtualSMC │ ├── WhateverGreen.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── WhateverGreen │ └── XHCI-unsupported.kext │ └── Contents │ └── Info.plist ├── OpenCore.efi ├── Tools │ └── Shell.efi └── config.plist 
You can find my config.plist over here, but once again, be warned — no good ever came off copy-pasting without at least some superficial understanding of the flags I’ve toggled in my .plist.
Once you’ve got all of this sorted, your OpenCore folder is now ready!
Follow the instructions here to make yourself a USB drive to install macOS Catalina from (assuming you’ve already downloaded it from the App Store and quit the installer). Once the process is complete — it should take about 20 minutes — use this super handy Python script from Corp Newt to mount the EFI folder in your USB drive. Then simply copy the contents of your OpenCore folder to the EFI folder.
The final structure should be similar to the folder tree I’d shared above.

Installing macOS:

This is very straightforward. Boot from your USB drive, and when you arrive at the OpenCore selection menu, pick the partition in which your macOS installer is sitting.
It is at this point that many first timers may see an error, indicating that you’ve overlooked something while setting up your OpenCore configuration. Don’t stress! Take a picture of the error you’re seeing, keep your hardware configuration and your EFI folder’s contents handy, and approach the subreddit or the Discord channel for help. It’s more often than not just a couple flags that need to be sorted out, after which you’ll be good to go.
Once you arrive at your macOS installer, before you do anything, find Disk Utility in it (it’s in one of the menus up top) and format your storage drive to Mac OS Extended (Journaled). Once that’s done, go right ahead and install the OS onto your disk!
There’s only a few things left to do after. One of them, Mykola’s already outlined — set up your NVRAM emulation if your motherboard doesn’t have native NVRAM. The other is setting up your custom SSDT. Let me explain why this is necessary.

Setting up your Custom SSDT:

MacOS, unlike Windows, has an interesting limitation: you’re limited to a maximum of 15 USB ports, including the internal ones sitting on your motherboard for Bluetooth connectivity, etc. To make matters worse, if you have a USB 3.0/3.1 port that’s backwards compatible with USB 2.0 connectors, to the OS, that one physical port counts as two ports — one for 3.0/3.1, one for 2.0. So even if your motherboard has exactly 15 physical USB ports, if even one of them is USB 3.0, you’re likely above the limit.
A second problem is, when you install macOS on a motherboard whose firmware isn’t specifically written for supporting macOS, it gets the placement of your USB ports wrong. So your super high-speed USB 3.0 port may not even recognise a USB 3.0 device plugged into it. This may also cause issues with your Hackintosh facing weird sleep/wake issues, among others.
This is where the USBInjectAll kext* comes in. If you’ve got it enabled, it’ll force macOS to “see” all the USB ports it possibly can, including ones that don’t physically exist on your motherboard. This isn’t a solution to get all your ports working, though — this shoots you well beyond the 15 port limit (you’ll likely see around 30 ports, instead), and will more often than not cause more problems than it fixes. This brings us to the custom SSDT — this file is what “talks” to UsbInjectAll, telling it which ports to inject and which ones to not bother injecting. Once you setup your SSDT file properly, you’ll have eliminated all the ports that don’t actually exist, or that you don’t intend to use, to bring the total number of ports down to 15, or lower. After this, macOS will communicate with your motherboard’s USB ports perfectly, the way you’d want it to.
*Some motherboards, such as mine, will require UsbInjectAll.kext to be accompanied by the XHCI-unsupported.kext for it to work properly.
Here’s another super handy Corp Newt Python script to very quickly map your USB ports. If you want a clearer understanding of what USB mapping is all about, I recommend this guide for newbies, and this one for people who want an even deeper dive into the subject.
Corp Newt’s script actually provides you with an alternative — once you’ve mapped your USB ports, you can either generate your custom SSDT file and place it in your ACPI folder the way I have, or you can generate an all-new kext called USBMap that will replace both the USBInjectAll kext and your SSDT file (you’ll still need XHCI-unsupported, though). USBMap is the more recommended method, as USBInjectAll isn’t maintained all that frequently, and could stop working properly after a macOS update.
Once you set up USBMap.kext (or your custom SSDT), you’ll never need to do it again for your motherboard, so be patient, set it up, and then forget about it.

And that’s it!

You should have yourself a Hackintosh that just works. If you don’t, there’s a detailed post-install section in Mykola’s guide that should see you through common problems that occur once everything is up and running. If it doesn’t, you’re always welcome to share your troubles with us at the Discord channel, or in the subreddit. Just make sure that what you’re facing is a Hackintosh-related issue, rather than a macOS bug that’s all Apple’s fault. Enjoy!


I really can’t thank enough all the people who patiently sat down and helped me through my various rookie mistakes and anxieties. There are certainly more names — forgive my terrible retention — but among others, u/dracoflar, u/CorpNewt, and u/fewtarius have been invaluable in teaching me how to approach the entire process and in answering all the questions I had about the same. Thanks a billion, y’all.
submitted by Shirt_Shanks to hackintosh [link] [comments]

How to add GSettings support to Meson project

So this is a guide on how to add support for GSettings or gschema to a Meson project. You can read about what it is and why it is necessary here.
"One of the nice things about GSettings is that it is a high-level API with backends for various native configuration systems. So, if you ever get around to porting your application to OS X or Windows, your application will automatically use the expected platform API to store its settings (the registry on Windows, and plists on OS X).
And even if your application will never be ported to those platforms, the dconf backend that is used on Linux has powerful features such as profiles and locks that let system administrators configure your application without you having to worry about it."
First of all create ... gschema. The file name is important if you just leave gschema.xml then it wont work. Before gschema.xml you should specify something like the host address of your project in reverse order. So, for example, if my project located here then my gschema file should be named like this: com.gitlab.gavr123456789.krontechgtk.gschema.xml I think you understand the pattern. (by the way, your project should be called in a similar way)
So we created our file, usually in the data folder. Now we need to decide what application parameters we are going to save in it.
For each parameter we create tags like this:
..... You can read about how parameter types are defined here and here.I'll just give you a few examples:i for intb for boold for doubles for string(is) for tuple of int string pairsa{is} for array of int string hash mapseasy right?
Each schema parameter has 3 tags:
  1. default for default value
  2. summary for short description
  3. description ...
So here example of full gschema that have 2 parametrs:
    381 Horizontal position The saved horizontal position of main window   380 Vertical position The saved vertical position of main window    
I think it's all clear. Now we need our application to be able to use this file. To do this, the scheme must be compiled in binary format(to optimize the speed of working with it, because it will only be read by programs and not by people)
Without Meson, we would have to do this manually, using the glib-compile-schemas utility, which takes a directory and compiles what has the * pattern in it.gschema.xml. But we use a Meson that can do it for us.

So in the data folder, create and add the following code to it:
gnome = import('gnome') gnome.compile_schemas(build_by_default: true,depend_files: 'com.gitlab.yournick.yourappname.gschema.xml') install_data('com.gitlab.yournick.yourappname.gschema.xml',install_dir: join_paths(get_option('datadir'), 'glib-2.0', 'schemas'),rename: meson.project_name() + '.gschema.xml',) 
(Don't forget to make a subdir ('data') at the top level)
So the first part here is responsible for compiling resources and placing them in the build folder. It is only needed so that we can test our app without installing it (installation requires sudo, this would be a bad practice)
The second part puts our xml in the place where it should lie, this is determined automatically using get_option ('datadir') but we still need to compile it, and if you change the file during development, you can recompile it again using a custom post-install script in python.
PS rename here is needed to make sure that your schema will have the name of your application. You can also add something like assert('com.gitlab.gavr123456789.krontechgtk.gschema.xml'==meson.project_name() + '.gschema.xml', 'proj name and gschema file not the same')
So, post install script. Creating the "build-aux" folder if your app supports more than one build system(meson, snap, flatpack) or just "meson" if only meson. And create "" there with the following content:
#!/usbin/env python import os import subprocess install_prefix = os.environ['MESON_INSTALL_PREFIX'] schemadir = os.path.join(install_prefix, 'share/glib-2.0/schemas') if not os.environ.get('DESTDIR'): print('Compiling the gsettings schemas ...')['glib-compile-schemas', schemadir]) 
As you can see, we just call the glib-compile-schemas command from here with the directory argument that we get from the Meson environment variable.
Now we need Meson to run this script after the installation is complete, this is done as follows:meson.add_install_script('meson/')
In the app itself you can try add something like this:
var settings = new GLib.Settings("com.gitlab.gavr123456789.krontechgtk"); int pos_x = settings.get_int("pos-x"); 
Now if you run your app it will crash, because the scheme will not be detected(because we havent installed it yet). To avoid this, set the environment variable like this: SETTINGS_SCHEMA_DIR=build/data/ ./build/com.gitlab.gavr123456789.krontechgtk
I recommend that you just create something like for this.
If you are developing a library and you do not need to manually run your application(unit tests) , you can configure your environment variables using Meson with environment() or add_test_setup()
Looks like thats all. If I forgot something please indicate it in the comments.
submitted by gavr123456789 to vala [link] [comments]

Patch Notes v 4.14

New features

Bug fixes

New news sources

Improved news sources

submitted by DarkHeraldMage to Calibre [link] [comments]

i9-9900k | ASUS z370g WIFI | OpenCore 0.5.8 | Avid Media Composer 2020.4 | macOS Mojave

There she is.
Finally finished my Film Editing Hackintosh running Mojave, Avid Media Composer 2019.12.1 2020.4 and Davinci Resolve 16!
I'm going to give an overview of the process in case it helps someone later.
Took a few weeks of preparation picking parts and reading guides - and 3 obsessive days of work with much help from Discord and the forums.
I followed the Dortania Guide - henceforth referred to as 'The Guide'.
My parts:
My build:
All straightforward except I had to dismantle the built in wifi housing and remove the glued in Intel wifi card so I could replace it with the Broadcom chip. It was a 1 to 1 swap, no adaptors necessary.
Here is the WIFI housing disassembled
Drivers (all from The Guide):
Kexts (all from The Guide unless noted):
Resources (optional, but I’m using for OpenCanopy boot selection GUI):
All the ones from OcBinaryData-master (linked in The Guide)
BIOS settings (this took the longest in some ways because I had to find everything, so here are the locations of what I could find):
Couldn't find in BIOS (if you know where this is let me know!):
Everything was pretty much plug and play, but there were some issues that I had to figure out.
First of all I was having a hard time wrapping my head around the OpenCore boot concept, though it didn’t result in any errors: First the machine boots the motherboard BIOS - then you tell it to boot from your USB install drive - then it essentially loads what I needed to think of as the OpenCore EFI BIOS from your USB stick - where you select with more specificity what you want to boot.
So you can do weird things like boot your finished OSX install from your USB stick EFI (which is really helpful if you fuck something up). Or You can use your OSX EFI to boot something off your USB stick.
So at first you want to boot the USB install using the USB EFI - then you want to boot OSX from the USB stick EFI - then you want to copy that EFI over to your Mac SSD and ultimately boot OSX from your Mac SSD EFI. Anyways, I got through the whole thing without understanding any of that, so don’t worry if that is the most confusing thing you’ve ever read.
Anyways, I feel like I had to reboot a few times during my first install to get my selections correct.
Install was otherwise totally straightforward.
After getting OSX up and running I copied my USB EFI over to my main HD.
And then I needed to do these small fixes:
To get DRM 4 working for the Apple TV app with the RX580, I had to add the shikigva=80 value in my config.plist. (Instructions are in The Guide)
To get AppleALC working the way I liked, I ended up going with layout 20 - so that it just registers three things: speakers, mic, and line in.
To get my USB ports all mapped correctly, I didn’t need any extra kexts. Just changed the XhciPortLimit in the config that is mentioned in the guide. I used Hackintool and simply plugged a usb3 drive into each port to map where it was located - then did the same with a usb2 device - then I labeled each one USB2 or USB3 - I labeled the bluetooth one internal - then I deleted the rest and did an export from Hackintool of the layout. Dropped that kext into the kexts folder and updated my OC snapshot, changed the XhciPortLimit back to false. And it was good to go.
Had to get my MAC address to line up - very easy, but thought I’d mention it.
Oh and for the record the Blackmagic card works the same as it did in my older Mac Pro - just install the Blackmagic drivesofware and it’s ready to go.
And that’s it!
So I initially did all this in Catalina and it was working just fine, but Media Composer 2020.4 was crashing on launch. There were two plugins (MSP_AVCHD.avx and TSParser.acf) that it would hit that would just throw the whole launch process. I was able to work around this by holding option during the entire launch process and selecting ‘HW SDK’ for audio, but I didn’t like that I had to do that for every launch.
So I saved my whole EFI - copied it over to my usb stick and made a new installer with Mojave. Started by running Avid Media Composer 2019.12.1. No crash on launch. Update: But unfortunately I was getting redraw issues - the numerical values from trim mode wouldn't disappear when I'd go back to source/record mode. So I decided to try MC 2020.4, but on Mojave. This works perfectly so far (knock on wood). Getting really good playback on 3k files Prores4444 files in green 'full quality' playback mode.
My Cinebench score is around 4500 if that means anything to you. Curious to see how it looks with an overclock.
I did a Prores HQ export from Resolve and the 60s clip finished in 28 seconds. More than twice as fast as my older computer.
Todo List:
I have not yet done the security stuff like enable FileVault and all that. For some reason I feel like it’s going to make life more difficult down the road? If anyone has opinions on this part of the build I'd love to hear them.
submitted by videowordflesh to hackintosh [link] [comments]

iOS 12: Download and install iOS 13! shortcuts

Hello iOS 12 users. These shortcuts download iOS 13 shortcuts from iCloud links and install them in iOS 12.
The normal procedure does not allow this since the Shortcuts app checks the version information of the downloaded shortcuts. iOS 12 and iOS 13 shortcuts are not fully compatible. But you can run an iOS 13 shortcut on iOS 12 if you are lucky.
Download iCloud Link Shortcut plist:
If your device has iOS 12 and you tap on an iCloud link of an iOS 13 shortcut then the name of the shortcut is shown but you cannot download it by the normal procedure. Instead you can start this shortcut via the share sheet. It downloads the iOS 13 shortcut and stores it in 3 files in different formats. It creates the target folder /Shortcuts/ios13/ to store the files. The names are appended by _bin, _xml, and _json to indicate the formats binary plist, xml plist, and json, respectively. The json is prettified for better readability. You may like reading the _json and the _xml files.
You can install the iOS 13 shortcut in your iOS 12 Shortcuts app. To do this you share the _xml file in the Files app and call the following shortcut via the share sheet.
Shortcut Version iOS 13 to iOS 12:
This shortcut modifies some version and release numbers in the xml plist. It removes the appended _xml from the file name and stores the file with the extension '.shortcut'. You should store it below the Shortcuts folder.
Now you can tap on the new shortcut file and it will be installed in your iOS 12 Shortcuts app.
You can inspect the newly installed shortcut in the shortcuts editor. The Shortcuts app indicates the actions that it does not recognize. Unrecognized options are not indicated. Test if the shortcut runs properly.
There are some devices that run iOS 12 but are not supported by iOS 13 or iPadOS. I hope this can be mitigated by these shortcuts.
The first shortcut may even be interesting for iOS 13 users.
You may like to combine both shortcuts to one shortcut that downloads and installs iOS 13 shortcuts in iOS 12.
submitted by Shoculad to shortcuts [link] [comments]

Git for Your Shortcuts — Make Readable, Versioned Shortcut Backups with Git (via Working Copy)

With the new Free Private Repositories on GitHub as of today, I think this is a great time to share a way to keep your shortcuts safe via Git.
Git is great for development, but the .plist files are binary and not readable on GitHub, so this shortcut converts them to a readable .XML file format before committing them so that you can see and read the changes more readily.



Ideas for further enhancement:

I am actually pretty new to both Git and Working Copy. So, this is just a start.
Get Git for Shortcuts on Routinehub
submitted by pbassham to shortcuts [link] [comments]

[Discussion] Why Installer 5 deserves a chance and my thoughts on it

Recently read this post and want to give my own opinion on it. Before I start notice how immature the post is, clearly it's purpose is to bash Installer and not to maturely give its downsides. Some of the Installer devs have replied with pretty mature and good points. That's why I'll keep this post peaceful and will try to be as objective as possible.
Firstly, I'd like to start with some of the major criticisms multiple devs made.
Make a new file, add 7777 permissions to it and change ownership to root. zip that file and extract it somewhere else, did any of the permissions change? Did the ownership change? It didn't when I tried. CC: Daily1JB
EDIT: Looks like setuid permissions are only saved if I extract the archive using Filza. (I don't get why?) If I use Terminal they're not. As for ownership it takes the ownership of the user which extracts it, so not an issue for Installer. Thanks to josephwalden for pointing it outl
The biggest point of Installer is getting rid of the need for dependencies. Therefore everything must be concentrated in a single app. It is easy for a dev to say "here you got a vulnerability" but not easy for who's working on so much things at once to not miss anything.
This is where I'd like to reply to the post above.
Indeed it is, but was it meant to be used on iOS? Most Linux systems have it preinstalled, what about iOS? The only way to install it is by using a .tar bootstrap full of 20MB of files. Is that dangerous? Of course it is. Not much for end-users, it's been tested a lot of times, but when devs take their time and put efforts in a new jailbreak indeed it is. Putting random untested files all over the filesystem doesn't sound good right? iOS's filesystem can change with time. What if there's an important change which makes an older bootstrap not work anymore? What's the worst thing that can happen? I believe you can imagine that. Just to compare, take a look at this:, that's what a Cydia jailbreak installs on your device. The simplest Installer jailbreak needs just two directories, one for Installer and one for binaries. Easy to get rid of, chance of it not working with future iOS almost 0, and the best part: it's easier to bypass jailbreak detections. EDIT: Forgot to mention, this way also makes sure we get new jailbreaks faster, there's no need to make and test a new bootstrap. Remember? That was the main reason electra 1.0 was delayed so much.
Literally there's no reason to waste 20 seconds of your time to run uicache, it's much easier to detect application installs. As for packages which use postinsts, I'm sure all of them run uicache manually, perfect example: Ext3nder Installer
As for other arguments used by Daily1Jb, they're mostly false and not based on evidence.
their team has no idea what the setuid/setgid permissions are!
How did they ran Installer with root permissions then?
you cannot specify checksums for a package like you can with Cydia
After speaking with their team, there are checksum checks. Also, less chance to screw up (instead of "more") as by default you cannot install untested packages (unless you disable the option)
Making an Installer repo gives you a full package management tool, you visit the website, enter the key and you can upload packages, refresh the repo with a few clicks. Cydia repos need you to manually run perl scripts to scan packages one by one and then upload the new files manually by FTP or something (depending on your repo).
Yes there are some things I don't like, but I'm sure it'll get improved over time:
Those were my points. If you don't agree with something feel free to make a peaceful discussion with me. I'll try to answer everyone.
Note: was going to be a longer post, but my device crashed to Safe Mode while I was writing and I had to shorten some things.
submitted by LEL-LAL-LOL to jailbreak [link] [comments]

[Tutorial] How to upgrade/downgrade to iOS 10.2 using futurerestore (prometheus) (JAILBROKEN METHOD) on MacOS. (Detailed tutorial for newbies).

UPDATED ON 9th of Feb 2017

by the gentleman: iPodHacks142
a link to his channel:


I know in the title I said it's for newbies.. but apparently I mis-estimated the difficulty level of this be fair it's fairly complicated and full of spaghetti, specially if you've never done things on terminals before.. or have no idea what any of the terms used mean ><.. so proceed with your own risk.. (edit added on 31st jan 2017).

Hi guys, in this tutorial I will be walking you through the requirements and the steps needed to use Prometheus to easily upgrade to 10.2 when it's no longer signed by Apple. Also, keep in mind that this tutorial is for MacOS users only.
This is particularly useful for people who are willing to hold onto their current jailbroken firmware, until a 10.2 jb is released to the public and confirmed working. It allows you to basically update to 10.2 (in this case at least, when it's no longer signed by apple) I know I sound redundant at this point, but just some clarification for those who haven't been in the scene for a while, only do this if you know what you're doing :D!
I myself am a windows user, but had no dice in getting futurerestore to work on windows, so I installed MacOS on a VM and proceeded from there.
** VM MIGHT NEED SOME DEPENDENCIES FOUND IN : this thread made by u/li0nic**
As the title says, this method is for jailbroken users only (means you have to be upgrading from a jailbroken OS that has task_for_pid0 enabled. So if you're on 9.1, 9.3.3 (with luca's jbme website) or 10.1.1 (yalu jailbreak mach_portal) you're good to go. Don't know about any other jailbroken firmwares that have taskforpid0 enabled. Also, of course this is going to be for 64 bit devices only (preferably below 7 and 7 plus since updating to 10.2 on them is useless). ** ***IIRC, Pangu 9.0-9.0.2 doesn't enable tfp0, but Pangu 9.1 does Also remember that 9.2-9.3.3 only has tfp0 if you jailbreak with after the initial jailbreak. * (EDIT ADDED BY u/Samg_is_a_Ninja , thanks to him)
***BEFORE YOU BEGIN, keep in mind this is a full restore! it won't retain your data! so make sure you back-up your phone through itunes before you do any of the steps below! and restore your backup later!*
1)Shsh2 blobs for 10.2 (you can get them from telegram or by following this reddit thread )
2)Futurerestore obviously, you can get it from here:
3)Nonceenabler, since we're going to be using the jailbreak method. You can get it from here:
4)iOS 10.2.1 IPSW file, you can get it from: for your particular device.
5)OpenSSH installed on your phone from cydia. DEFAULT PW FOR IT IS alpine
6)iOS 10.2 IPSW file also.
*********7)Baseband file, SEP file, buildmanifest.plist file. TO GET THOSE: Change the name of ios 10.2.1 Ipsw file you downloaded from .ipsw to .zip THEN extract it, Copy the buildmanifest.plist file and put it in some folder you create, then go into Firmware and Copy the .bbfw file from there into the folder you created with buildmanifest.plist, there might be 2 .bbfw files. copy the one with "Mav10-5.32.00.Release.bbfw" in it if you're on: iPad Air 2, iPad Pro (12.9 inch), iPad mini 4, iPhone 6, iPhone 6 Plus and iPhone SE. OR COPY the one with Mav13-2.41.00.Release.bbfw in it if you're on: iPhone 6s, iPhone 6s Plus and iPad Pro (9.7 inch) and paste the respective file in the folder with the others. *(Check THE BBFW SOURCES BELOW IF I DIDN'T LIST YOUR PHONE, YOU WILL FIND THE CORRECT BBFW UNDER EACH MODEL (the 10.2 or 10.2.1 ones, they're identical anyway), I LINKED IPHONE WIKI, DOUBLE CHECK TO SEE :))**********
Then, go into all_flash then into all_flash.n66map.production (notice you have to go into the folder with your boardid configuration, which you can find on the iphone wiki). in my case I was using a 6s plus TSMC (so n66map). then, copy sep-firmware.n66m.RELEASE.im4p file and paste it in the folder you created earlier with buildmanifest+bbfw files.**
How I got the bbfw file for each device:
MDM9615: iPhone 5s, iPad Air, iPad mini 2, iPad mini 3
  • iOS 10.0.1/10.0.2/10.1(.1): 7.01.00
  • iOS 10.2: 7.21.00
MDM9625: iPhone 6, iPhone 6 Plus, iPhone SE, iPad Air 2, iPad Pro (12.9"), iPad mini 4
  • iOS 10.0.1/10.0.2: 5.24.00
  • iOS 10.1(.1): 5.26.00
  • iOS 10.2: 5.32.00
MDM9635: iPhone 6s, iPhone 6s Plus, iPad Pro (9.7")
  • iOS 10.0.1/10.0.2: 2.30.00
  • iOS 10.1(.1): 2.36.00
  • iOS 10.2: 2.41.00
MDM9645: iPhone 7
  • iOS 10.0(.1): 1.00.02
  • iOS 10.0.2: 1.00.03
  • iOS 10.0.3: 1.00.05
  • iOS 10.1 1.02.13
  • iOS 10.1.1: 1.02.15
  • iOS 10.2: 1.02.15
MDM9645: iPhone 7 Plus
  • iOS 10.0: 1.00.02
  • iOS 10.0.1: 1.00.03
  • iOS 10.0.2: 1.00.04
  • iOS 10.0.3: 1.00.05
  • iOS 10.1(.1): 1.25.00
  • iOS 10.2: 1.33.00
We should note that Wi-Fi devices such as the iPod Touch 6G and the Wi-Fi iPads do not have a baseband file. Since we have no test devices, we aren't sure how to proceed. You can try omitting the baseband file from the Terminal command at your own risk, but there's no guarantee that would work.
Special thanks to Stoppels for pointing this out and providing the list and source.
Then, put the nonceenabler+futurerestore+the shsh2 file of your device+ iOS 10.2 IPSW file into the same folder. Finally now you would have a folder with the following if you did everything right.
A) buildmanifest.plist
B) the bbfw file.
C)the im4p file (the SEP file).
D) Nonceenabler+ ios 10.2 IPSW file + Futurerestore (unzipped ofc) +the shsh2 file of your device.
I advise renaming that folder to Prometheus Downgrade (or any name of your choice really).

NOW BEFORE YOU PROCEED, Make sure you delete any tweaks that tamper with system plists.. like karen's tweaks "norecoverypls(?) or mikoto" or so.. and turn any daemons you turned off by icleaner back on and turn low power mode off if it's on.

First of all you should do this in the jailbroken state of your phone!
1- Open terminal and cd into the folder you created, an example if it's on the desktop, you type in the terminal: cd desktop (hit enter) then cd (foldername). For simplicity we'll call this Terminal (A).
2-Ssh into your device by typing this in your terminal "ssh [email protected]" (your phone's ipadress can be found in settings>wifi> hit the ! mark next to the wifi you're connected to and you will find it) example : ssh [email protected]
then hit enter,
you will be prompted to enter a pw, default pw is alpine if you've never played with ssh before.
now leave that terminal after you've entered the pw, and follow the following
3-open new terminal tab (we'll call it terminal B) and cd into the folder you created. you need to push the nonceEnabler binary into device. To do so type in the same terminal “ scp nonceEnabler [email protected]: “ and enter the password. (take note that at the end of the ipadress theres a colon(:) )
4-switch back to the first tab (terminal A) then you have to set a specific variable, and in order to do that you have to patch the kernel first with nonceEnabler. Do so by executing (typing in terminal) “ ./nonceEnabler “ Enter in the terminal you just switched to (first one).
Now to set a new variable run “ nvram (the generator is a value you can get from your shsh2 file by making a copy of it, then changing the extension from shsh2 to .plist of the copy then open it up and scroll down, you will see a string underneath the generator with numbers and letters in between > and < an example : so you replace the generator with that value in the command " nvram "
-if anyone is still having trouble writing generator to nvram "nvram: Error setting variable - '': (iokit/common) general error". try running the command from the device via either [[Mterminal]] or any other terminal app. (edit added by syto203) or check
5- In the same terminal (terminal A), type in "nvram auto-boot=false" this will essentially disable the autoboot (booting up into your ios, so you can proceed with prometheus instead)
(Also there's an optional step: check that auto boot is false by running “ nvram -p and hit enter, you should see a bunch of lines, one of which is auto boot is set to false, if so, you're good to go).
In the same terminal again (terminal A) type in “ reboot “ and enter.
Device now should be in recovery (go ahead and plug it in into your computer if you had not done so already, and close iTunes if it launches)
6- Device should already be in recovery mode (the itunes screen with the cable on your device).
now run: chmod +x futurerestore_macos (in terminal A, and hit enter then proceed to the next step).
now run “ ./futurerestore_macos -t blob.shsh2 -b baseband.bbfw -p BuildManifest.plist -s SEP.im4p -m BuildManifest.plist -w targeted.ipsw “
ofc, in terminal A.
targeted.ipsw = the iOS version you want to RESTORE TO not the one you pulled sep, and other files from.
note that you replace each of those with their names, an example baseband.bbfw will be Mav10-5.32.00.Release.bbfw, and so on for every other parameter.
Full example:
./futurerestore_macos -t 4795253457241214_iPhone8,2_n66map_10.2-14C92.shsh2 -b Mav10-5.32.00.Release.bbfw -p BuildManifest.plist -s sep-firmware.n66m.RELEASE.im4p -m BuildManifest.plist -w iPhone_5.5_10.2_14C92_Restore.ipsw
hit enter and let it restore.. (if your screen turns green during the process, it's a good sign ;)).
if you run into any errors after this step, it's either you have messed something up, or the shsh2 file you used was incorrect.. in any case, to exit the recovery mode; download reiboot and exit it through it... and try again if you desire.
ALSO IT'S important to note that your device reboots every 15 mins in recovery mode, meaning that it will lose the nonce you set it to, the "generator" so you will have to redo the steps.. so it's better to just make sure everything is ok before entering the recovery by "reboot" command, like make sure all the dependencies are installed and everything is running right, then restore.
Since this can be used for any iOS 10 version (and 9, but let's not make it too difficult), any "iOS 10.2" should refer to "targetVersion" (or so) and all "10.2.1"'s should refer to the currently signed version 🤔 Since 10.2.1 might be the final with a compatible SEP, we could just note it beforehand edit We should note beforehand that downgrading from 10.2.1 to 10.2 will keep Touch ID functional, but downgrading to 10.0.x and 10.1.x will result in the loss of this functionality for Touch ID devices.
note: we only needed terminal B once, sorry for confusing y'all :D
EDIT1: I am by no means professional at doing this at all, it took me a lot of attempts and research, also some people helped me to get through the countless errors I had on the VM. So a native mac is your best bet if you're new to this..
Also, I advise waiting until 10.2 is no longer being signed to try this tutorial, since it's pointless to do it now as you can't downgrade to your jailbroken firmware. I used a burner device to try this and touchid worked (thanks to a friend).
If someone wants to add anything, feel free to comment below and I will add it to the tutorial if it's beneficial.. I tried making it concise.. and I am really busy so sorry for the horrible format and the hurried up typing! I apologize! I have finals and stuff wish me luck ;D!
and goodluck everyone ;D
EDIT2: OSX only, I tested on sierra (the latest one).
EDIT3: Since everyone is wondering whether this breaks Touch ID or not, it doesn't folks. The sep file from 10.2.1 is compatible if not identical to that of 10.2, so no issues ensue when upgrading this time with prometheus; unlike the last time where 10.2 sep wasn't identical to that of ios 10.1.1, and hence the touch id issues. Hope this makes it clear. And also more confirmation will emerge when 10.2 stops being signed, I will make sure to let you know if this causes any issues afterwards. As for now you don't have to be worrying about it, specially if you want to update to 10.2, it's still being signed so you can do it through iTunes. If you're torn between waiting for the 10.2 jailbreak then updating through this method but afraid of touch id issues, or hesitant to update now, I'll wait myself on 9.3.3 if that says anything. After all it's your choice.
TL;DR: it doesn't break touch id.
A topic about it:
if you are stuck in recovery mode and want to exit, downlod reiboot from google and exit using it.
if you encounter any errors check this thread made by u/li0nic
he included a bunch of other necessities and requirements so yeah!
submitted by itzmekhaled to jailbreak [link] [comments]

Cut, copy & paste actions

Hi there,
I’ve made probably a really useful workflow that can cut, copy and paste actions between workflows. Read on!
But first


You are solely responsible for your own workflows. This workflow can damage other workflows if you overwrite them when asked by the Workflow app. I am not responsible for any loss or other damage, which is a direct or indirect result of executing my workflow.


Copy or cut actions from a workflow and paste them in the same, another or a new workflow. (It seems simple, but under the hood it’s not). You can also filter the workflow selection list by some key words. Just enter them in the first Text action. If you enter a second line, it will be used for filtering the target workflow list and the first line for the source workflow list. There is also an update checker built in. To invoke it, open the CopyPaste Actions workflow, scroll down to a comment action describing this feature (its near the top). It will check against this post.

How to install

  1. Run the downloaded workflow, it will import two other workflows. It’s basically my Install Workflow
  2. You can delete the downloaded workflow when both workflows CopyPaste Actions and CopyPaste Action Parser are imported and can be opened

How to use it?

  1. Run the workflow CopyPaste Actions like you run any other workflow
  2. A list of your workflows will be presented, ordered A-Z and a-z
  3. Select your workflow
  4. A list of the actions of that workflow will be presented (or an error, if something went wrong)
  5. Choose the actions you want to cut or copy. If you choose one of the If, Choose from Menu, Repeat (with Each) actions, the workflow will automatically select all actions inside that block and the block itself. If you choose a menu item from Choose from Menu, it will only select its contents. Likewise it will do it, if you choose the Otherwise action of an If block. If you choose the closing action End ..., the whole block will be selected.
  6. After pressing Done on the Choose Actions List, you can choose between copying or cutting the actions after a short wait. Maybe I will update it sometime, to speed it up
  7. Now you can choose in which workflow you want to paste. If you choose Another Workflow, you will be presented a list of your workflows again to pick the other workflow
  8. As of version 1.2 this step was removed and handled automatically If you have selected an action that includes an UUID and in the target workflow is the same UUID already present, you will be asked, if you want to generate new UUIDs. UUIDs are used with (magic) variables and with the block actions. Its workflows way to keep track, which actions belong together and which magic variable represents which action output. If you have copied one of the block actions, you should generate new UUIDs, unless there is no other block action in the target workflow. If there are two block actions with the same UUID in a workflow, the indent of the second will be broken and if gets executed, workflow will crash. If you only copy actions that contain variables, you should only not generate new UUIDs, when these variables are connected (that is the case if it is the same workflow or the source and target workflow were duplicated or you have already copied another action with the same variable)
  9. At the last step, you have to choose where you want to paste it. You have the options Beginning, Choose... and End. The first and last are clear. If you choose Choose..., a list of the actions in the target workflow is presented again, where you choose one action, after which it should be pasted. The first action in the list with the index 0 is only a dummy item, so you can still paste at the beginning if you’ve changed your mind
  10. You will be notified, if you have to run the workflow once more, if you have cut the actions to another or new workflow.
  11. The Workflow app will now ask you, if you want to override the workflow you have pasted in. As I wrote in the disclaimer, there is the possibility that the imported workflow does not work, but it is your decision to make, if you want to override it. My advice is to have a backup of that workflow somewhere.
  12. If you have chosen to cut the actions to another or a new workflow, the old workflow has to still be modified. Because workflow asks the user, if he wants to override a workflow, it cancels the following imports. As there is the possibility that this happens, I couldn’t chain them together, to import them at the same time. Because of that, the source workflow will be temporally saved to iCloud Drive in /workflow/CopyPaste tmp/ and when you run my workflow again and there is at least one file, it will try to import it in Workflow and delete it in iCloud, so make sure that you don’t save any files in there, or they will be deleted the next time you run my workflow. As it happened sometimes for me that the source workflow didn’t import. So before it gets imported, it will be copied to the iCloud folder /workflow/CopyPaste tmp2/. If you run my workflow a third time, it will find the source workflow in the that folder and ask you, if it was imported successfully. If you choose Yes, it will delete it completely. Otherwise it will import it again and ask you again the next time until you choose Yes.

How does it work?

A workflow is saved as a bplist or binary property list, a standard format on Apple systems. Luckily, using a Set Name action on a workflow with setting the extension to .plist, converts it to a plist, the XML version of the property list. Then I put that into my Javascript and run it to parse the actions (I had a version, where workflow itself parses it, as workflow recognises it as dictionary, but that was super slow. A 350 action long workflow took 480 seconds...). After the actions are chosen, it extracts the first number, the index, from the choosen text items and gets the actions in XML from the plist and creates a version of the workflow that has the selected actions removed. It then inserts the action in the target workflow and puts the XML of the new workflow again in a different Javascript. This time, it encodes it as bplist again, as workflow doesn’t import plist only files... (sometimes, it works without encoding it again, but I don’t know why and when, but at least then reliable, my Installer workflow uses that).


The list of actions is very simple to understand: Each action is one item in the list. Each item has an index, followed by possibly a parenthesis containing another index, a comma, and an expression that is maybe cut off by an ellipsis. After that follows a : and the action name. If the action has data saved (if you have modified the options of the action) and if I have implemented the extraction parameters for that action, another parenthesis will follow the action name. In that parenthesis is a short version of the selected options, maybe cut off by an ellipsis ("..."), if it is too long for the line. For example:
> 1: Text (something)
> 2: If (= something)
> 3: Text (Yay :D)
> 4 (2, = something): Otherwise
> 5: Text (Oh no :()
> 6 (2, = something): End If
> 7: Show Alert (Title: ◃If Result▹, Body: , Show Cancel Button: No)
Variables are enclosed in ◃ and ▹ and if they have some options set, it will display the same thing as workflow, but like ◃variable name|selected option▹. If you like, you can enter your own characters in the parser workflow except " and \, but the | separator can’t be changed (if you find it in the Javascript, go ahead and change it, but don’t break it ;) )
It took me since October 2017 till today to develop the workflow. I originally had the parsing done in workflow itself, but that took 480s for a 350 action long workflow, and that is definitely too long. It also took me 2 months in that time, to build the information for the parsing of the action options, which is saved as JSON, so it is easily extendable. Also I’ve not included every action in the parsing of their settings, as I don’t own most of the third party apps that have actions in workflow, but their action name will still be displayed. It took me that long, as Workflow doesn’t provide any usable error, if something goes wrong while importing the workflow and I had to find an app that can at least show the javascript console to get some error messages. And it has about 530 actions.
A big thank you to u/JoeReally and u/maskedWrestlurker for testing the workflow! It should work on Workflow 1.7.6+ and iOS 9+, maybe also on Workflow 1.7.5, but I couldn’t test that.
Current version: 1.2.1
I changed the link, it should work now.


v1.2.1 -2018-08-25

v1.2 -2018-08-20

v1.1 - 2018-05-28

v1.0.1 - 2018-04-16


Initial release
submitted by schl3ck to workflow [link] [comments]

Gentoo Linux+QEMU KVM+AMD RX 560 GPU Passthrough+HighSierra/Win10 (Both Successful and Near-Native)

READ THE UPDATE BELOW. I FINALLY got all three (yes 3) of Gentoo, High Sierra and Windows 10 all running at the same time on the same machine, with the High Sierra on RX 560, and the Windows 10 on Nvidia GTX 1080, and Gentoo host on intel HDA 630 all at the same time. HAHAHA!
"Hardware and Software Hybridization of Guest Operating Systems"
by rev0lt
Experiment's Goals:
(1) High Sierra at near-native speed on Linux QEMU KVM with AMD GPU Passthrough (Success);
(2) Win10 at near-native speed on Linux QEMU KVM with AMD GPU Passthrough (Success);
(3) To achieve (1) and (2) but using Nvidia GPU (Successful on Windows10, everything works perfect; able to boot on High Sierra boot screen, but it ends with a stop sign); and
(4) To achieve (1) and (2) simultaneously. (Success!). I got Linux+HighSierra+Windows10 all running at the same time on the same machine.
Rationale ("Why?"):
Can you feel it?
Jokes aside, a bit of a brief background -- this whole trouble started with my Apple Magic Mouse (Series 1). I really love this mouse -- it has been with me almost 8 full years now, and yes, it still looks beautiful; and I really wanted this wonderful mouse to work in an acceptable manner in Gentoo Linux. I managed to get it to work, but somehow the scrolling and movement in X Window just does not "feel right," even if I tried tuning it with xinput.
So, being OCD'd, I tried to get the mouse to work in an acceptable manner in Windows 10 too. It does work somewhat okay-ish, using Apple's Bootcamp driver for the mouse which I got using my MacBook Pro. But the scrolling and "feel" are still somewhat "off".
Which brings us to this point. From my OCD perspective, this is all done just to get the mouse to work "right" on my setup below.
Hardware Setup:
Apple Magic Mouse (Series 1) <3 <3 <3
Asus Maximus Code IX Intel i7-7700K EVGA Nvidia GTX 1080 Hybrid ASUS Strix AMD RX 560 (purchased for testing this setup) G.Skill TridentZ DDR4-3200 16G Samsung NVMe SSD 960 EVO M.2 250GB Samsung SSD 850 PRO 256GB EVGA Supernova 850w G2 Gold Dell P4317Q 4K Monitor (43-Inch) CoolerMaster MasterKeys Pro L (Cherry MX Red) Sony Playstation 4 PRO Thermaltake Core X71 Thermaltake Water 3.0 Apple MacBook Pro
Software Setup:
The SSD 850 Pro is the drive of interest here, since it is where I store the Linux host for learning computer science and programming as a hobby. (The NVMe M.2 drive is installed with Windows 10 as my primary OS for daily use, so it is irrelevant here.)
I compiled Linux Gentoo 4.13.8 on the SSD 850 Pro as the host OS, with KVM, IOMMU, VFIO functions enabled in the kernel. I also compiled QEMU 2.10.0.
For AMD RX 560 to work in High Sierra, all is needed is to make sure Lilu and WhateverGreen kexts are installed. This worked even without editing the AMD9500Controller.kext binary.
More importantly -- I finally got the EVGA Nvidia GTX 1080 to passthrough in Windows 10 Enterprise (free trial)!!! Sound through the Display Port of the card works perfect, as long as MessageSignaledInterruptProperties is added or changed from 0 to 1 in the Windows Registry. Sound works flawless without any lag.
Basically to get the GTX 1080 card to passthrough, I (A) compiled OVMF in Gentoo and then used the default OVMF_CODE and OVMF_VARS fd files under /usshare/edk2-ovmf/ for QEMU; and then (B) adjusted the -cpu flag in QEMU command line, such that my QEMU command line looks like this:


echo 1 > /sys/kernel/mm/ksm/run &&
qemu-system-x86_64 \ -enable-kvm \ -machine q35,type=pc,accel=kvm,kernel_irqchip=on \ -m 4G \ -cpu host,kvm=off,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_vendor_id=hello \ -smp 4,sockets=1,cores=2,threads=2 \ -device vfio-pci,host=01:00.0,multifunction=on,x-vga=on \ -device vfio-pci,host=01:00.1 \ -vga none \ -usb -device usb-host,hostbus=1,hostaddr=3 \ -usb -device usb-host,hostbus=1,hostaddr=8 \ -drive if=pflash,format=raw,readonly,file=OVMF_CODE.fd \ -drive if=pflash,format=raw,file=OVMF_VARS.fd \ -boot order=d \ -drive file=win.disk,format=raw,cache=none,aio=native \ -cdrom win10.iso \ -nographic \
Note the passthrough of the Nvidia GTX 1080 in the command line above. I did not even need to specify the Nvidia rom dump.
Using the above command line and OVMF files, I was able to boot into the Windows 10 installer to install the trial version. Everything works in Windows 10. Video is smooth and slick. Very near native.
Then, I tried to adjust the above command line for High Sierra too -- the Nvidia card passed through successfully and High Sierra (I used the installed version that was derived from the AMD card experiment detailed below, adding the NvidiaFixedUp.kext to the EFI's kext/Other folder in addition to Lilu and WhateverGreen that are already there). High Sierra was able to boot until it ended up with a stop sign.
I think with more experimentation, I can get the Nvidia card to passthrough and boot successfully into High Sierra too. Probably an issue with the config.plist file???
By the way, this is the QEMU command line I used to test the Nvidia card under High Sierra:
qemu-system-x86_64 \ -enable-kvm \ -m 4G \ -cpu Penryn,kvm=off,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,$MY_OPTIONS,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_vendor_id=hello \ -machine q35,type=pc,accel=kvm,kernel_irqchip=on \ -smp 4,sockets=1,cores=2,threads=2 \ -device vfio-pci,host=01:00.0,multifunction=on,x-vga=on \ -device vfio-pci,host=01:00.1 \ -device isa-applesmc,osk="" \ -drive if=pflash,format=raw,readonly,file=OVMF_CODE.fd \ -drive if=pflash,format=raw,file=OVMF_VARS.fd \ -smbios type=2 \ -device ich9-intel-hda -device hda-duplex \ -device ide-drive,bus=ide.1,drive=MacHDD \ -drive id=MacHDD,if=none,file=higher.img,format=qcow2 \ -netdev user,id=usr0 -device e1000-82545em,netdev=usr0,id=vnet0 \ -balloon none \ -vga none \ -nographic \ -device vfio-pci,host=00:14.0 \
As mentioned, the above booted with the Nvidia card passthrough -- but stops at the end of the boot screen with a stop sign. Anyone knows how to fix this?
I will try to reproduce this but boot in verbose mode instead to see what is going on. But my gut instinct is that this is very fixable.
Anyhow, I will clean up the old stuff below when I have more time. Will also do more fine tuning and perhaps test with benchmark and games. Will try to get video and screenshots posted.
And yes, when I have both High Sierra (with AMD RX 560 passed through) and Windows 10 Enterprise (with Nvidia GTX 1080) running on the Gentoo (using Intel HD 630) host, all three systems run at near-native or native speed, even though all three are running at the same time. I have not benched marked yet, but they run smooth, even all simultaneously, with videos playing. HAHAHHA.
OLDER STUFF (Read the UPDATE first):
To get High Sierra (10.13 release) working on Linux with QEMU, I followed the instructions at The two OVMF files (OVMF_CODE-pure-efi.fd and OVMF_VARS-pure-efi-1024x768.fd) and also the Clover.qcow2 file there all worked out of the box. All you need is to download those 3 files onto the Linux host. Then, I prepared the requisite High Sierra USB installer by using the usual USB+Clover method that most folks use to test this (select the UEFI option under Clover, not the Legacy option). After that, using the script below (commenting out the 2 VFIO GPU passthrough lines -- the lines mentioning 03:00.0 and 03.00.1 -- for now and use gtk or vnc to output video since GPU passthrough is yet to be done) to get High Sierra installed and running with "soft" video output through gtk, vnc, spice, etc. for the moment, at least until passthrough of the GPU is done later. (Was I repeating myself there? That is the trouble with OCD, there is this irresistible compulsion to do a certain thing in a specific way). I have tried many other methods, but presently it seems that the instructions in the above GitHub link are the only ones that worked.
It is a bit trickier to get High Sierra to run with GPU passthrough to obtain near-native speed. To achieve that, once I installed and booted into High Sierra with soft video output, I [a] patched the AMD9500Controller.kext in /System/Library/Extensions in the High Sierra guest's hard disk using xxd; and then [b] installed the Lilu.kext and WhateverGreen.kext into /System/Library/Extensions. It seems that the binary needed to drive the AMD RX 560 is already included in High Sierra, inside the AMD9500Controller.kext folder. All that is needed is to hex-modify the binary so that the hardware layout of the RX 560 is correctly reflected the binary file in that kext. I modified the "Acre" personality entry in the binary in AMD9500Controller.kext for convenience sake because it has 3 connectors at the back, the same number of connectors as the RX 560. (It is unclear whether [a] is needed if [b] is done -- I have not tested such scenario.)
Specifically, for example, this is what I changed in the binary based on information from the Baffin.rom file from the RX 560 card:
For the "Acre" personality located at 0x121f80 in the binary file, change the hex (of bs=48 since 3 connectors x 16=48) from
to this
All the connectors (DP, HDMI, DVI) at the back of the card should now work perfect.
At any rate, I did both [a] and then [b], and High Sierra boots successfully with AMD RX 560 passthrough, using the following Linux QEMU command line script adapted from


MY_OPTIONS="+aes,+xsave,+avx,+xsaveopt,avx2,+smep" export QEMU_AUDIO_DRV=alsa && qemu-system-x86_64 \ -enable-kvm \ -m 8192 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,$MY_OPTIONS\ -machine pc-q35-2.9 \ -smp cpus=8,sockets=1,cores=4,threads=2 \ -device isa-applesmc,osk="" \ -drive if=pflash,format=raw,readonly,file=OVMF_CODE-pure-efi.fd \ -drive if=pflash,format=raw,file=OVMF_VARS-pure-efi-1024x768.fd \ -smbios type=2 \ -device ich9-intel-hda -device hda-duplex \ -device ide-drive,bus=ide.2,drive=Clover \ -drive id=Clover,if=none,snapshot=on,format=qcow2,file=./'Clover.qcow2' \ -device ide-drive,bus=ide.1,drive=MacHDD \ -drive id=MacHDD,if=none,file=./high.img,format=qcow2 \ -netdev user,id=usr0 -device e1000-82545em,netdev=usr0,id=vnet0 \ -balloon none \ -device vfio-pci,host=03:00.0,multifunction=on \ -device vfio-pci,host=03:00.1 \ -vga none \ -monitor unix:/tmp/monitor.sock,server,nowait \ -nographic \ -device vfio-pci,host=00:14.0,bus=pcie.0 \
Once the above is done, the separate AMDRadeonX4250.kext (responsible for 3D acceleration, etc) seems to get loaded by High Sierra and the RX 560 card should be functioning perfectly, directly connected to the guest OS with metal support.
Note that using the above command line, I have passthrough my USB controller as well (vfio-pci,host=00.14.0). The result is that bluetooth and all my USB ports (I have not tested the 3.1 one) worked out of the box, with my Apple Magic Mouse (Series 1) working perfectly with that tight, smooth buttery feel. Also working flawlessly are my CoolerMaster L keyboard and all other USB devices, including USB external drives, etc). I would then control the Linux host underneath via ssh from the High Sierra guest. When the Dell monitor is dedicated to the High Sierra guest at full 4K, the linux host basically becomes transparent and invisible to the user.
Performance-wise, High Sierra runs buttery smooth and beautifully with the AMD RX560 passthrough in QEMU KVM. It is impressively silky, fast and responsive, with QE working and no glitches or hangs or crashes. Apps open almost instantaneously (split second). Ethernet works out of the box and the sound works perfect via the audio output jack of the Dell monitor which is connected to the AMD RX 560 via Display Port. In fact, the setup is so near-native that I'd speculate that a layperson would not notice the difference compared to say, a 2017 iMac (Geekbench 4 benchmark that I ran seem to suggest similar scores) unless the setup is revealed to him. Personally and anecdotally, I do not notice the difference even if I look for them. I mean, this thing is bat-out-of-cave fast. Certainly, it is a whole different league and at a whole different level from the usual slowish virtual box, parallels, vanilla vmware experience. Even compared to my MacBook Pro (also running High Sierra), this setup feels substantially smoother, faster and more responsive.
There are only two very minor noticeable glitches. First, flac audio playback on Fidelia would intermittently "tear" for split seconds if I concurrently run very heavy compile tasks in the Linux Gentoo OS underneath the QEMU/HighSierra. But this is expected. I have not tried CPU-pinning to dedicate specific CPUs to High Sierra yet, but I suppose using CPU-pinning, the lag can be removed since High Sierra would not then have to compete for CPU with the Gentoo Linux host running underneath. Netflix video playback on Chrome/Safari runs smooth, without any lag even under heavy load. Also, the sound in High Sierra via the AMD graphics card works perfectly -- does not suffer from the slight lag as in the case of running Win 10 in QEMU with the same card passed through. Second, in the High Sierra boot screen, the progress bar under the logo would tear slightly during boot up and appear to freeze (but it is still booting underneath) for say 5-6 seconds, before booting into the login/password screen.
With more fine-tuning, I think I can get the set-up to run High Sierra even faster -- but as it is now, it feels like a native machine already. I am super, super impressed with the performance.
Windows 10:
Windows 10 Enterprise (90-trial version) also works with this QEMU KVM GPU passthrough setup. Everything works out of the box without any patching. All that is needed is for one to download and install the AMD Radeon video drivers. Performance is very smooth too and near native -- except that the audio output lags behind the video output during Netflix playback by a second or two. I feel that Win 10 in this setup is not as impressive (the "Wow" factor") as getting High Sierra to work at near-native with GPU passthrough. Both are near-native, but High Sierra just "feels" (to me anecdotally) better, tighter, more finely tuned, more "buttery" and smoother in this setup as compared to Win10 under the same. Maybe it is just a function of graphical user interface design generally. I don't really know why.
Further Experiment:
Note that all of the above is done despite the fact that I have plugged the AMD RX 560 only in the PCIE x4 slot on the motherboard. This is because I already have the Nvidia GTX 1080 installed in the PCIE x8_1 slot. The AMD RX 560 can't be placed in the x8_2 slot because I use the GTX 1080 for the Linux OS and those two x8 slots are in the same IOMMU hardware group, and hardware in the same IOMMU group cannot be passthrough to two different OSes.
Thus, theoretically, performance in such experiment above could be further improved if I were to use the Intel HD630 onboard graphics for Linux, disconnect the power to the Nvidia GTX (due to the power supply constraint -- by the way, does anyone know how to prevent a GPU card from powering up via the Asus motherboard bios?), and place the AMD RX 560 in the x8_2 slot for the passthrough. Additionally, I can try moving the Linux host to the NVMe .M2 drive for testing for a significant disk speed improvement.
A much more interesting next step would be to procure a second AMD RX 560 card, and place it in a x4 slot, with the first AMD RX 560 card in the x8_2 slot, have Linux running on the Intel HD 630, and then passthrough both AMD cards to High Sierra and Win 10 simultaneously, such that Linux Gentoo, High Sierra and Win10 all run on the same machine at the same time and all at native or near native-speed!
Alternatively, if anyone here knows how to get the Nvidia GTX 1080 to passthrough to High Sierra or Windows via QEMU, I would appreciate it if you could share your knowledge! I have tried to do so many times, but it all ends in black screen with the Nvidia card.
I intend to achieve this as the final goal of this experiment -- with the Dell P4317Q displaying the 4 machines all at the same time -- four split screens at 1920x1080 resolution each, each split screen for each of linux, high sierra, windows, and also my PS 4 Pro.
I also wonder, what happens if I install Gentoo Linux on my MacBook Pro, compile and run QEMU KVM on it, and then passthrough the GPU to the High Sierra guest? Without X Window running (perhaps ssh'ing in to control), I'd speculate that the Linux overhead would be relatively small.
With all this running on top of Gentoo, there's basically no need to reboot or to troubleshoot incompatible hardware. There are no crashes in the host or the guest though sometimes the guest fails to fire up. Also, backup of guest OSes seems easy -- I just copy the qcow2 hard disk file into storage. And I can fire up and power off the guest anytime I wish without interfering with the Gentoo host running underneath, which has basically becomes transparent. Also, this setup seems, in theory, more resistant to problems when upgrading the OS. And by the way, the messages app seems to work out of the box too.
It is interesting to note that with KVM allowing guest to access many aspects of the host hardware directly, in addition to passing through control of the GPU and USB controllers, discs, other devices etc. to the guest directly, plus pinning CPUs to the guest, the guest is arguably a hybrid of hardware and software, rather than just software. In fact, to me at least, it feels more bare metal than software.
Feel the POWER of Gentoo.
All for fair-use, learning, experimental testing only
Screenshots: (High Sierra GPU Passthrough at full 4K glory) (High Sierra + Linux + PS4 Pro) (Win 10 + Linux + PS4 Pro) (Apple Magic Mouse (Series 1))
D. Kholia (
submitted by rev0lt001 to VFIO [link] [comments]

[Guide] Sierra for the Dell Insprion 5559

I made High Sierra boot on that laptop, so you can now use the new updated guide posted here

My first hackintosh, therefore my first guide! Let's start.
First, what works:
  • Graphics (With acceleration, only issue is some pixels sometimes get black at the top left corner, but they magically disappear after some days of using)
  • Ethernet
  • Bluetooth
  • Audio (With speaker and pretty bad but acceptable sound in headpones)
  • Web Camera (Fully working, don't worry skype lovers)
  • Battery Indicator
  • Keyboard
  • Trackpad (with gestures)
  • Disk Drive
  • Sleep mode (only mentioning it cause on some hackintoshes it doesn't work)
What doesn't work:
  • WiFi (The stock card from the laptop doesn't work, maybe if I buy a custom one I'll make a tutorial. A compatible card is BCM94352Z DW1560, and if you manage to put it into the laptop and get it working with the hackintosh, please let me know so I can update the guide.)
  • SD card reader doesn't seem to work as well.
Now, the guide:
First, prepare the clover USB drive with UniBeast. Google it if you don't know how.
After you have a drive, open the clover folder and do the following:
  • Grab the config.plist from here, open it with a text editor (best choice is notepad++ for windows and Sublime Text for linux) and there find #Resolution and edit it to 1366x768 so you have the correct resolution.
The VoodooHDA kext
All the kexts must be moved to /Clovekexts/Other and HFSPlus.efi must be moved into /CloveDrivers64UEFI
Now, partition your hard drive. Also be sure to have the GPT partition type and the UEFI bootloader mode with secure boot disabled.
Now, boot into clover and boot the Sierra installer with the platform-id 12345678 for the graphics card or you are going to get a kernel panic. Open Disk Utility from the top bar, and format the partition you want to install macOS on with OS X extended (journaled) and complete the installation. Note that if it gets stuck at "15 minutes remaining" just wait for about 3 minutes and it is going to continue.
After the installation finishes, boot up the OS with clover again with the 12345678 ig-platform-id for the graphics card, rebuild kext cache (just open kext utility), and after this boot with the default platform-id from the config and you should be fine with graphics. If something goes wrong, feel free to ask me.
Post-installation goodies:
  • Noone can live without the ctrl key. So, to fix it, go to Systme preferences > Keyboard > Modifier keys... > put command key to control key and control key to command key.
  • If the black pixels at the top left corner are too annoying, search for "dark" in system preferences, and than enable "Dark menu bar and Dock" so the black pixels don't look so annoying on the dark meu bar. By the way, after a few days they actually disappear at all, but I still like dark dock and menu bar.
  • I just updated from 10.12 to 10.12.5, everything worked fine, so feel free to try 10.12.5 or update if you tried older versions. I didn't either need to reinstall kexts or rebuild kext cache.
  • To get the battery indicator to work, do the following:
  1. Download the needed kext.
  2. Download kext utility if you didn't already.
  3. Open the kext utility and drag the kext into it.
  4. Reboot and you should be fine.
  5. Open System Preferences Energy Saver Show battery status in menu bar.
  6. Optional: if you wanna have battery percentage, click on the battery indicator and select 'show percentage'.
By the way it was such a surprise for me when after a reboot I saw the battery indicator :D The kext was from 2013 so i didn't expect it to work, that's the reason.
  • Getting AirDrop to work: open terminal from the applications menu and type this: defaults write BrowseAllInterfaces 1 && killall Finder. Take note, this only works for sharing from your hackintosh to another hackintosh or a real mac cause apple limited AirDrop between macOS and iOS.
submitted by ArtikusHG to hackintosh [link] [comments]

First successfull hackintosh! High Sierra older hardware

  • Intel i5-3330
  • ASUS P8H77-M
  • ASUS DUAL Readon RX 460 OC 2GB
  • Samsung EVO 500GB SATA drive
USB installation media
I formatted my Sandisk 16 GB USB memory with a HFS+ partition on a GUID table and named the partition “Untitled”. I downloaded High Sierra and ran the command included in the install file:
sudo /Applications/Install\ macOS\ High\ --applicationpath /Applications/Install\ macOS\ High\ --volume /Volumes/Untitled 
I then downloaded Clover_v2.4k_r4334 from and run and customised settings with these options:
  • Install for UEFI booting only
  • Install Clover in the ESP
  • Boot loader
    • Don’t update MBR and PBR sectors (greyed out)
  • Drivers64UEFI
    • EmuVariableUefi-64
    • OsxAptioFix2Drv-64
    • OsxAptioFixDrv-64
    • PartitionDxe-64
I downloaded HFSPlus.efi and put this file in the /EFI/CLOVEDrivers64UEFI. In the same folder I removed the file VBoxHfs-64.efi. I then downloaded the following kexts:
  • FakeSMC
  • NullCPUPowerManagement
  • RealtekRTL8111 (for my the ethernet card on my motherboard)
And put these into /EFI/CLOVEKexts/10.13/
Mostly copied from this guide
In the config.plist I updated the RadeonDeInit in the graphics section to be true.
Configuring system
First I began by updating my bios from version 0606 to the most current version 1347. Since these motherboard had problems booting GUID drives.
Boot the clover USB by pressing F8 and choose the USB memory. Clover will now start, choose “Install OSX start with Install High Sierra…”
First I started the Device Utility and formatted my SSD as one big HFS+ partition on a GUID partition table and named this partition “Hackintosh”. Then I exited and went through a normal installation.
After rebooting I needed to disable APFS conversion by booting the USB again and choosing terminal in the menu under utilities. In the terminal I changed the file /Volumes/Hackintosh/macOS\ Install\ data/minstallconfig.xml So that the where false instead of true for conversion. I rebooted and finished installation.
BIOS Patching
Did this since I didn't get sleep to work at first. (Read below for my real problem)
I don’t know if this done anything for me: But I’ve patched my BIOS with UEFIPatcher and removed the NullCPUPowerManagement.kext. Followed guide from here (used older version which had mac binaries).
SSDT file generation
I used the script for picker-alpha to generate an SSDT.aml file for my system. Followed instructions from:
Post Installation
In the new system on first boot, I downloaded the Clover Configurator and copied the EFI partition from the USB to my desktop. I copied the EFI folder from my Desktop to the EFI folder on my boot disk.
I fixed SMBIOS according to his guide:
The where gone so I found the script here:
There seem to be a bug in 10.13.2 where sleep with RX 460 don’t work and solved this for me. (Putting Lilu.kext and WhateverGreen.kext in /System/Library/Extension and added the arbitrary settings form the screenshots)
I used values 03 for my CFG,CFG_FB_LIMIT since my card have 3 outputs.
What’s not working
USB2.0 Ports works but not with hubs, only one devices will be detected (e.g. the keyboard but no connected mice in the built in hub). My USB3.0 ports works with multiple hubs.
I’m using an Audient iD14 for audio plugged in to one of my USB3.0 ports. The built in probably works but I haven’t checked.
submitted by ikuo_kemo to hackintosh [link] [comments]

[Guide] OSX 10.11.3 El Capitan w/ dual-boot Windows 10. (GA z97x-ud3h, intel i7, evga gtx970)

I'll be using tonymac's El Capitan guide as a reference. Many builds have found success with it and it comes with decent illustrations. The guide can be found here:
I hope my instructions will clarify anything left ambiguous. Also, big thanks to this community and all the devs who helped make my Hack possible.
Preparing to Install OSX
Don't need to remove memory or graphics card.
Create a bootable USB using Unibeast. This is done by formatting the USB through Disk Utility first, then running Unibeast. I had to switch to a different USB to get it working.
Settings for Unibeast:
  • El Capitan
  • UEFI
  • Don't inject graphics
BIOS settings:
  • In order to get into BIOS, on keyboard press DEL. To boot from specific drive, press F12. (Varies based on Motherboard)
  • Once in BIOS, Set optimized defaults, then disable vt-d. No other settings need to be configured, though might need to enable windows setting for multiboot. (explained later)
If using an external Nvidia GPU, use boot flag nv_disable=1 until Nvidia's alternate drivers are installed.
Installing OSX
Boot from Unibeast USB (will be referred simply as OSX USB from now on) and install OSX. At some point in the installation, a restart is required. Afterward, boot into Macintosh HD using OSX USB again to complete installation. This is because MacHD doesn't have config.plist or kexts yet at this point.
Open Clover Configurator, mount EFI of MacHD (should be the first drive, numbered 0), copy included config.plist into MacHD's EFI.
Install El capitan Post Install Tools (Contains Clover UEFI and customac pkg with kexts) Actually this is useless, follow the next step.
Install fakesmc, intelmausi, and all other kexts manually by dragging them into /clovekexts/other Delete all other numbered directories (OSX versions) in /clovekexts/
If using a dedicated GPU, install drivers for it. In this case, it's nvidia alternate driver
Mulltiboot (Installing Windows)
This part requires creating a Windows installer USB enabled for UEFI/GPT. The tool to use is Rufus (Windows only) so create it from either a virtual machine, etc. The target Windows drive needs to be formatted as GPT. With both MacHD and target drive connected, boot into MacHD (OSX), launch disk utility and delete the target drive. This will format it as GPT.
When installing, delete the entire partition and reinstall (there will be errors saying Windows unable to install on non NTFS format otherwise. The drive still contains GPT partition map). The following BIOS flags are required, provided here.
  • BIOS > BIOS Features > Windows 8 Features : Set this to "Windows8"
  • BIOS > BIOS Features > CSM Support : Set this to "Never"
  • BIOS > BIOS Features > Secure Boot : Set this to "Disabled"
After setting this, BIOS Boot Option Priorities should look clean and should contain only three things:
  • Boot Option #1 : UEFI OS
  • Boot Option #2 : Windows Boot Manager
  • Boot Option #3 : Disabled (Could be remaining option Mac OS X)
** Problems I ran into and their Solutions **
  • Bluetooth errors during boot are apparently related to graphics? - use nv_disable=1
  • Abnormal code: 255 (during boot) - Missing FakeSMC.kext. Copy the one form USB or download it.
  • Audio not working - Run audio_realtek_110.command. It will notify you to set CsrActiveConfig to 0x3. Did that, rebooted, ran the command, rebooted again and audio fixed.
  • Incorrect memory frequencies displayed in "About this mac"- fixed by adding “trusted” flag in SMBIOS.
  • Monitors must be plugged into the GPU in specific port configuration, or one will need to be turned off and before it gets visuals. Not sure why. Seems like this is resolved by the new config.plist I took from the unibeast USB.
  • Sloowwwwww boot into OSX from clover. - solved by copying the config.plist from unibeast USB. Also added SMBios 14,1 to it.
  • Trying to get multi-boot working... See Multiboot section
  • Extra/repeated/glitchy-looking Boot Options in BIOS - disable everything except the main boot partition, and save/exit. Returning to the BIOS after should reveal that everything is clear.
  • Hiding non-partition entries at boot (Clover GUI). - Uncheck "legacy" flag in GUI (Clover Config)
  • Untitled Windows Local Disk (untitled) - easy, rename it in Windows
  • Displays incorrect disk usage in About This Mac > Storage (Apps) - reindex spotlight by adding MacHD to exclusions in System Prefs > Spotlight > Privacy (tag), then remove it via '-' button.
  • Hardware stats (temperatures, etc) not displayed - install HWSensors binaries.dmg (kexts), NOT .pkg. Did not use the FakeSMC provided in this .dmg, as there's already one in place.
  • Multiboot, Windows time incorrect: run regedit.exe >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation >> New > DWORD (32-bit) >> RealTimeIsUniversal >> set value to 1
submitted by atlasffqq to hackintosh [link] [comments]

[Guide] MSI Z97 gaming 5 Hackintosh

About This "Mac"
Step 1: Create flash drive and Download needed kext
  1. Format the USB as Mac Os Extended (Journaled) and GUID Partition Table and name it as USB
  2. Run the following sudo /Applications/Install\ macOS\ --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\
  3. Download clover HERE pick the newest option (one on top)
  4. Once the installer is made, run clover and make sure to install it onto the usb and not the hard drive.
  5. The EFI partioton should still be mounted, if not use Clover Configurator to mount the EFI partioton.
  6. Download fakesmc from here (open the dmg and drag and drop the kext) and put it in /efi/clovekext/other
  7. Download nvidiagraphicsfixup Here
  8. Download Lilu here
  9. Download atherosE2200Ethernet V2.2.0 and put it in /efi/clovekext/other
  10. Download Alternate NVIDIA Graphics Drivers
  11. put fakesmc.kext and atherosE2200Ethernet.kext into /efi/clovekext/other
  12. download Applealc from Here
  13. Put all the kext, Alternate NVIDIA Graphics Driver, and Clover Configurator on a seperate usb incluiding fakesmc and atherosE2200Ethernet for simplicity sake.
Step 2: Recommended BIOS Settings
  1. Enter bios/UEFI by holding Delete key
  2. Load Optimized Defaults
  3. Enable XMP
  4. (Optional) Overclock (I'm at 4.7GHz at 1.25V)
  5. Set Overclocking/CPU Features/CFG Lock to Disabled
  6. Set Overclocking/CPU Features/VT-d to Disabled
  7. Save configuration and reset
STEP 3: Install OS X Sierra
  1. Turn on the computer
  2. Press the hotkey to choose boot device (F11)
  3. Choose USB
  4. At Clover boot screen, choose Boot Mac OS X from USB
  5. When you arrive at the Installer, choose language.
  6. Erase and format the destination drive according to the following steps before continuing.
    a. In the top menu bar choose Utilities, and open Disk Utility
    b. Highlight your target drive for the Sierra installation in left column.
    c. Click Erase button
    d. For Name: type what ever you want. Mine is MAC OS
    e. For Format: choose OS X Extended (Journaled)
    f. For Scheme: choose GUID Partition Map
    g. Click Erase
    h. Close Disk Utility
  7. When the installer asks you where to install, choose MAC OS
  8. Upon completion, the system will automatically restart.
  9. On the next boot chose the Hard drive in clover, not the USB.
  10. Open and install clover and restart booting off usb 1 last time.
  11. Use clover configurator to mount the EFI Partition of the hard drive not the usb
  12. Put fakesmc.kext in /efi/clovekext/other
  13. Put atherosE2200Ethernet.kext in /efi/clovekext/other
  14. put Lilu.kext in /efi/clovekext/other
  15. Put nvidiagraphicsfixup.kext ine /efi/clovekext/other
  16. Install Alternate NVIDIA Graphics Drivers and do not reboot.
  17. Open Finder and go to /EFI/EFI/CloveConfig.plist and open it with clover-configurator.
  18. Select SMBIOS and click the wand.
  19. Select iMac and then iMac 15,1
  20. Click Shake ~5 times
  21. Go to
  22. Enter serial number and enter the code. If the checker comes back with “We're sorry, but this serial number is not valid. Please check your information and try again.” or something similar, you are golden! However, if it comes up with purchase date and coverage, you need to shake the two variables again.
  23. Assuming you have an invalid SN, copy that and paste it into “Board Serial Number” Now, while still in the same text box (with caps locks on) type 5 random letters and numbers.
  24. Open terminal and paste “uuidgen" (Without quotation marks), then hit enter.
  25. Copy the results of the terminal command you ran and paste it in the "SmUUID" field in the SMBIOS settings.
  26. Save/export your config.plist
  27. Open terminal once again and run the following list of commands on at a time:
*cd ~/Library/Caches/
rm -R
rm -R
*cd ~/Library/Preferences/
*rm -R ~/Library/Messages/
  1. Reboot!
  2. Open Clover Configurator and go to Boot. Click XMPDectition=Yes
  3. mount efi once again
  4. put Applealc.kext in /efi/clovekext/other
  5. reboot and you have a 100% working hackintosh
I might have had a brain aneurism during this write up so if there is an error or if something does not work, let me know
iMessage - Sierra
FaceTime - Sierra
Phone calls - Sierra
Internet - Sierra
Sound - Sierra
Sleep - Sierra
  • MSI Gaming Z97 GAMING 5 LGA 1150 Intel Z97
  • Intel i5-4690K Processor (OC 4.7Ghz 1.25V)
  • CORSAIR Vengeance 16GB (4 x 4GB) 1866 (CMZ8GX3M2A1866C9)
  • Kingston V300 120GB SSD (OS X)
  • Samsung 850 EVO 1TB (Windows)
  • MSI GTX 970 Gaming 4G (x2)
submitted by puffpants to hackintosh [link] [comments]

Only one resolution available(1024x768) on 10.11.3

I disabled the internal graphic hd4600 Instead, I use the GALAX GT 610 as my graphic card. However it only shows the 1024x768 to me.
Here's my system info
  • Gigabyte Z97 D3H
  • Intel Core i5-4460 (hd4600)
  • GALAX GT 610
  • OSX 10.11.3
Here's my config.list
![inline]( =300x "Title")
![inline]( =300x "Title")
![inline]( =300x "Title")
![inline]( =300x "Title")
![inline]( =300x "Title")
This is my boot log
0:100 0:100 MemLog inited, TSC freq: 3200003850 0:100 0:000 0:100 0:000 Now is 28.1.2016, 0:38:33 (GMT+2047) 0:100 0:000 Starting Clover rev 3333 on American Megatrends EFI 0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,1F52ECF2-39A5-4A6B-A149-760935D9EDD1,0x28,0x64000) @9F507518 0:100 0:000 SelfDirPath = \EFI\BOOT 0:100 0:000 Total Memory Slots Count = 4 0:100 0:000 Type 17 Index = 0 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 ChannelA-DIMM0 0:100 0:000 Type 17 Index = 1 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1 0:100 0:000 Type 17 Index = 2 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 2 ChannelB-DIMM0 0:100 0:000 Type 17 Index = 3 0:100 0:000 SmbiosTable.Type17->Speed = 1866MHz 0:100 0:000 SmbiosTable.Type17->Size = 8192MB 0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 3 ChannelB-DIMM1 0:100 0:000 Boot status=0 0:100 0:000 Clover revision: 3333 running on Z97-D3H 0:100 0:000 ... with board Z97-D3H-CF 0:100 0:000 CPU Vendor = 756E6547 Model=306C3 0:100 0:000 The CPU supported turbo 0:100 0:000 BrandString = Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz 0:100 0:000 MSR 0xE2 before patch 1E000404 0:100 0:000 MSR 0xE4 00021814 0:100 0:000 MSR 0xCE 00080838F3012000 0:100 0:000 non-usable FLEX_RATIO = 10000 0:100 0:000 corrected FLEX_RATIO = 0 0:100 0:000 FSBFrequency=100MHz DMIvalue=100000kHz 0:100 0:000 Corrected FSBFrequency=100MHz 0:100 0:000 VendoModel/Stepping: 0x756E6547/0x3C/0x3 0:100 0:000 Family/ExtFamily: 0x6/0x0 0:100 0:000 MaxDiv/MinDiv: 32.0/8 0:100 0:000 Turbo: 32/33/34/34 0:100 0:000 Features: 0xBFEBFBFF 0:100 0:000 Threads: 4 0:100 0:000 Cores: 4 0:100 0:000 FSB: 100 MHz 0:100 0:000 CPU: 3200 MHz 0:100 0:000 TSC: 3200 MHz 0:100 0:000 PIS: 400 MHz 0:100 0:000 PCI (00|00:00.00) : 8086 0C00 class=060000 0:100 0:000 PCI (00|00:01.00) : 8086 0C01 class=060400 0:100 0:000 PCI (00|01:00.00) : 10DE 104A class=030000 0:100 0:000 Found NVidia model=nVidia GeForce GT 610 0:100 0:000 PCI (00|01:00.01) : 10DE 0E08 class=040300 0:100 0:000 PCI (00|00:02.00) : 8086 0412 class=030000 0:100 0:000 Found GFX model=Intel HD Graphics 4600 0:100 0:000 PCI (00|00:03.00) : 8086 0C0C class=040300 0:100 0:000 PCI (00|00:14.00) : 8086 8CB1 class=0C0330 0:100 0:000 PCI (00|00:16.00) : 8086 8CBA class=078000 0:100 0:000 PCI (00|00:19.00) : 8086 153B class=020000 0:100 0:000 LAN 0, Vendor=8086, MMIO=F7800000 0:100 0:000 PCI (00|00:1B.00) : 8086 8CA0 class=040300 0:100 0:000 PCI (00|00:1C.00) : 8086 8C90 class=060400 0:100 0:000 PCI (00|00:1C.03) : 8086 8C96 class=060400 0:100 0:000 PCI (00|03:00.00) : 8086 244E class=060401 0:100 0:000 PCI (00|00:1F.00) : 8086 8CC4 class=060100 0:100 0:000 PCI (00|00:1F.02) : 8086 8C82 class=010601 0:100 0:000 PCI (00|00:1F.03) : 8086 8CA2 class=0C0500 0:100 0:000 Clover load options size = 0 bytes 0:105 0:005 Using OEM config.plist at path: EFI\CLOVER\config.plist 0:105 0:000 EFI\CLOVER\config.plist loaded: Success 0:107 0:002 Found theme directory: applestyle 0:110 0:003 Found theme directory: EMBEDDED 0:111 0:001 Found theme directory: RANDOM 0:112 0:001 Loading early settings 0:112 0:000 timeout set to 1 0:112 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 0:112 0:000 KextsToPatch: 2 requested 0:112 0:000 KextsToPatch 0: AppleHDA (Audio patch) Kext bin patch, data len: 4 0:112 0:000 KextsToPatch 1: AppleAHCIPort (External icons patch) Kext bin patch, data len: 8 0:112 0:000 Default theme: embedded 0:112 0:000 Hiding entries with string VolumeName_NOT_SHOWN 0:112 0:000 Hiding entries with string EntryPath_NOT_SHOWN 0:112 0:000 Hiding entries with string VolumeUUID_NOT_SHOWN 0:112 0:000 CustomEDID ok 0:112 0:000 LoadDrivers() start 0:114 0:002 Loading FSInject-64.efi status=Success 0:116 0:001 Loading OsxAptioFix2Drv-64.efi status=Success 0:117 0:001 Loading OsxFatBinaryDrv-64.efi status=Success 0:118 0:001 Loading VBoxHfs-64.efi status=Success 0:119 0:001 - driver needs connecting 0:119 0:000 1 drivers needs connecting ... 0:119 0:000 PlatformDriverOverrideProtocol->GetDriver overriden 0:119 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok 0:312 0:192 LoadDrivers() end 0:312 0:000 Dump SMC keys from NVRAM: 0:353 0:041 SetMaxResolution: found best mode 4: 1920x1080 1:190 0:836 Video mode change to mode #4: Success 1:190 0:000 - set 1:190 0:000 Console modes reported: 6, available modes: 1:190 0:000 Mode 1: 80x25 (current mode) 1:190 0:000 Mode 2: 80x50 1:190 0:000 Mode 3: 100x31 1:190 0:000 Mode 4: 128x30 1:190 0:000 Mode 6: 120x50 1:190 0:000 SetScreenResolution: 1920x1080 - already set 1:190 0:000 reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,1F52ECF2-39A5-4A6B-A149-760935D9EDD1,0x28,0x64000) 2:513 1:322 MAC address of LAN #0= FC:AA:14:C8:87:92: 2:513 0:000 ScanSPD() start 2:513 0:000 SMBus CmdReg: 0x1 2:513 0:000 Scanning SMBus [8086:8CA2], mmio: 0xF7838004, ioport: 0xF040, hostc: 0x11 2:513 0:000 Slots to scan [8]... 2:527 0:014 SPD[0]: Type 11 @0x50 2:536 0:008 DDR speed 1777MHz 2:536 0:000 Slot: 0 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=060C010805030906 2:550 0:014 SPD[1]: Type 11 @0x51 2:558 0:008 DDR speed 1777MHz 2:558 0:000 Slot: 1 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=070701080203020E 2:573 0:014 SPD[2]: Type 11 @0x52 2:581 0:008 DDR speed 1777MHz 2:581 0:000 Slot: 2 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=07040108060F020E 2:595 0:014 SPD[3]: Type 11 @0x53 2:604 0:008 DDR speed 1777MHz 2:604 0:000 Slot: 3 Type 24 8192MB 1777MHz Vendor=Kingston PartNo=KHX1866C10D38G SerialNo=07050108060A020E 2:628 0:024 ScanSPD() end 2:628 0:000 Get Acpi Tables List from RSDT: 2:628 0:000 Found table: FACP A M I len=132 2:628 0:000 Found table: APIC A M I len=114 2:628 0:000 Found table: FPDT A M I len=68 2:628 0:000 Found table: SSDT Ther_Rvp len=3054 2:628 0:000 Found table: SSDT Cpu0Ist len=1337 2:628 0:000 Found table: SSDT CpuSsdt len=2932 2:628 0:000 Found table: MCFG A M I len=60 2:628 0:000 Found table: HPET A M I len=56 2:628 0:000 Found table: SSDT SataTabl len=877 2:628 0:000 Found table: SSDT SaSsdt len=23390 2:628 0:000 Calibrated TSC frequency =3200003850 =3200MHz 2:628 0:000 Loading main settings 2:628 0:000 Read NVCAP:0000000000000000000000000000000000000000 2:628 0:000 USB FixOwnership: true 2:628 0:000 Config set ResetAddr=0x0 2:628 0:000 Config calc ResetVal=0x0 2:628 0:000 Config set ResetVal=0x0 2:628 0:000 Config set ChassisType=0x6 2:628 0:000 Config set QPI=65535MHz 2:628 0:000 Config set CpuFreq=3199MHz 2:628 0:000 Config set CpuType=605 2:628 0:000 Config set BusSpeed=99999kHz 2:628 0:000 Error: invalid CustomUUID '' - should be in the format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX 2:628 0:000 found 4 volumes with blockIO 2:628 0:000 0. Volume: 2:628 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0) 2:629 0:000 Result of bootcode detection: bootable unknown (legacy) 2:629 0:000 1. Volume: 2:629 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,1F52ECF2-39A5-4A6B-A149-760935D9EDD1,0x28,0x64000) 2:629 0:000 Result of bootcode detection: bootable Clover (clover) 2:635 0:005 This is SelfVolume !! 2:635 0:000 2. Volume: 2:635 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(2,GPT,7BB0DBB6-3FB6-4FCF-9508-35C31C06D230,0x64028,0x1BD8A540) 2:636 0:000 3. Volume: 2:636 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(3,GPT,99455448-8CE7-426E-8E5C-D7A16F77F418,0x1BDEE568,0x135F20) 2:636 0:000 using embedded theme 2:636 0:000 Choosing theme 2:637 0:000 Custom entries start 2:637 0:000 Custom entries finish 2:637 0:000 Scanning loaders... 2:637 0:000 0: 'Whole Disc Boot' no file system 2:637 0:000 1: 'EFI' 3:545 0:908 2: 'capitan' 3:554 0:008 AddLoaderEntry for Volume Name=capitan 3:559 0:004 Check if volume Is Hibernated: 3:559 0:000 Check sleep image 'by signature': 3:565 0:006 read prefs \Library\Preferences\SystemConfiguration\ status=Success 3:565 0:000 SleepImage name from pref: ImageVolume = 'capitan', ImageName = '\private\var\vm\sleepimage' 3:570 0:004 Reading first 512 bytes of sleepimage ... 3:570 0:000 OurBlockIoRead: Lba=173E5828, Offset=2E7CB05000 (BlockSize=512) 3:570 0:000 sig lion: 1010004 3:570 0:000 sig snow: 42601 3:570 0:000 no valid sleep image offset was found 3:570 0:000 Reading completed -> Success 3:570 0:000 sleepimage offset could not be acquired 3:570 0:000 hibernated: no - sign 3:573 0:003 3: 'Recovery HD' 3:574 0:001 AddLoaderEntry for Volume Name=Recovery HD 3:576 0:001 Custom legacy start 3:576 0:000 Custom legacy end 3:576 0:000 Scanning legacy ... 3:576 0:000 0: 'Whole Disc Boot' (legacy) not legacy 3:576 0:000 1: 'EFI' (clover) add legacy 3:576 0:000 added 'Boot Clover from EFI' OSType=3 Icon=clover 3:576 0:000 2: 'capitan' (legacy) not legacy 3:576 0:000 3: 'Recovery HD' (legacy) not legacy 3:576 0:000 Custom tool start 3:576 0:000 Custom tool end 3:578 0:001 found tool \EFI\CLOVER\tools\Shell64U.efi 3:578 0:000 Checking EFI partition Volume 1 for Clover 3:578 0:000 Found Clover 3:579 0:000 GetEfiBootDeviceFromNvram: efi-boot-device-data not found 3:579 0:000 EfiBootVolume not found 3:579 0:000 found entry 0. 'Boot Mac OS X from capitan', Volume 'capitan', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(2,GPT,7BB0DBB6-3FB6-4FCF-9508-35C31C06D230,0x64028,0x1BD8A540)\System\Library\CoreServices\boot.efi' 3:579 0:000 DefaultIndex=0 and MainMenu.EntryCount=9 3:647 0:067 Found Mouse device: 3:648 0:000 GUI ready 5:648 2:000 StartLoader() start 5:648 0:000 Entry->Settings: 5:648 0:000 Finally: Bus=99999kHz CPU=3199MHz 5:648 0:000 Kernel and Kext Patches at 90FE82B0: 5:648 0:000 Allowed: y 5:648 0:000 Debug: n 5:648 0:000 KernelCpu: n 5:648 0:000 Lapic: n 5:648 0:000 Haswell-E: n 5:648 0:000 AICPUPM: y 5:648 0:000 AppleRTC: y 5:648 0:000 KernelPm: y 5:648 0:000 FakeCPUID: 0x0 5:648 0:000 ATIController: null 5:648 0:000 ATIDataLength: 0 5:648 0:000 0 Kexts to load 5:648 0:000 2 Kexts to patch 5:648 0:000 KextPatch[0]: 4 bytes, AppleHDA 5:648 0:000 KextPatch[1]: 8 bytes, AppleAHCIPort 5:648 0:000 Loading boot.efi status=Success 5:861 0:213 GetOSVersion: : 10.11.3 5:862 0:000 insert table 9 for dev 0:0 5:862 0:000 insert table 9 for dev 0:1 5:862 0:000 insert table 9 for dev 19:0 5:862 0:000 Channels: 2 5:862 0:000 Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23 5:862 0:000 SMBIOS Type 17 Index = 0 => 0 0: 5:862 0:000 DIMM1 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 8192 5:862 0:000 SMBIOS Type 17 Index = 1 => 2 2: 5:862 0:000 DIMM2 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 16384 5:862 0:000 SMBIOS Type 17 Index = 2 => 1 1: 5:862 0:000 DIMM3 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 24576 5:862 0:000 SMBIOS Type 17 Index = 3 => 3 3: 5:862 0:000 DIMM4 1777MHz 8192MB 5:862 0:000 mTotalSystemMemory = 32768 5:862 0:000 NumberOfMemoryDevices = 4 5:862 0:000 Type20[0]->End = 0x7FFFFF, Type17[0] = 0x2000 5:862 0:000 Type20[1]->End = 0x17FFFFF, Type17[2] = 0x8000 5:862 0:000 Type20[2]->End = 0xFFFFFF, Type17[1] = 0xC000 5:862 0:000 Type20[3]->End = 0x1FFFFFF, Type17[3] = 0x14000 5:862 0:000 Table 131 is present, CPUType=31 5:862 0:000 Change to: 605 5:862 0:000 RSDT 0xABDC5028 5:862 0:000 FADT from RSDT: 0xABDC5100 5:862 0:000 XSDT 0xABDC5078 5:862 0:000 FADT from XSDT: 0xABDD5AD8 5:862 0:000 Xsdt reallocation done 5:862 0:000 old FADT length=10C 5:862 0:000 Found OperationRegion(GNVS, SystemMemory, ABDFCA98, ...) 5:862 0:000 Found OperationRegion(PNVA, SystemMemory, ABDFDD98, ...) 5:862 0:000 Found OperationRegion(CPSB, SystemMemory, ABC5AE98, ...) 5:862 0:000 Found OperationRegion(TMMB, SystemMemory, FED40000, ...) 5:864 0:001 Apply DsdtFixMask=0x00000000 old way 5:864 0:000 drop _DSM mask=0x0000 5:864 0:000 ========= Auto patch DSDT Starting ======== 5:864 0:000 VideoCard devID=0x104A10DE 5:864 0:000 DisplayADR1[0] = 0x10000, DisplayADR2[0] = 0x0 5:864 0:000 VideoCard devID=0x4128086 5:864 0:000 DisplayADR1[1] = 0x20000, DisplayADR2[1] = 0xFFFE 5:864 0:000 USBADR[0] = 0x140000 and PCIe = 0xFFFE 5:973 0:109 Audio HDA (addr:0x1B0000) setting specified layout-id=1 (0x1) 5:973 0:000 first CPU found at B7FC offset B7FF 5:973 0:000 score candidate at B7F8 5:973 0:000 score inserted in acpi_cpu_score _PR 5:973 0:000 Found ACPI CPU: CPU0 And CPU1 And CPU2 And CPU3 And CPU4 And CPU5 And CPU6 And CPU7 within the score: PR 5:974 0:000 Found PCIROOTUID = 0 5:974 0:000 ========= Auto patch DSDT Finished ======== 5:974 0:000 Patch table: SSDT Ther_Rvp 5:974 0:000 SSDT len = 0xBEE 5:974 0:000 Patch table: SSDT Cpu0Ist 5:974 0:000 SSDT len = 0x539 5:974 0:000 Patch table: SSDT CpuSsdt 5:974 0:000 SSDT len = 0xB74 5:974 0:000 Patch table: SSDT SataTabl 5:974 0:000 SSDT len = 0x36D 5:974 0:000 Patch table: SSDT SaSsdt 5:974 0:000 SSDT len = 0x5B5E 5:974 0:000 Drop tables from Xsdt, SIGN=XXXX TableID= Length=0 5:974 0:000 Xsdt has tables count=10 5:974 0:000 corrected XSDT length=116 5:974 0:000 Inserting SSDT-SB-OC.aml from EFI\CLOVER\ACPI\patched ... Success 5:975 0:001 CPUBase=0 and ApicCPUBase=1 ApicCPUNum=4 5:975 0:000 EdidDiscovered size=128 5:975 0:000 00 | 00 FF FF FF FF FF FF 00 15 C3 31 25 01 01 01 01 5:975 0:000 16 | 2F 18 01 03 80 35 1E 78 EA 7E 75 A7 55 52 9C 27 5:975 0:000 32 | 0F 50 54 A1 08 00 81 80 B3 00 A9 C0 81 C0 81 00 5:975 0:000 48 | 01 01 01 01 01 01 02 3A 80 18 71 38 2D 40 58 2C 5:975 0:000 64 | 45 00 10 29 21 00 00 1E 00 00 00 FF 00 33 36 30 5:975 0:000 80 | 34 31 31 31 34 0A 20 20 20 20 00 00 00 FD 00 31 5:975 0:000 96 | 3D 0F 44 0F 00 0A 20 20 20 20 20 20 00 00 00 FC 5:975 0:000 112 | 00 45 56 32 34 35 30 0A 20 20 20 20 20 20 01 03 5:975 0:000 NVidia GFX injection not set 5:975 0:000 Intel GFX injection not set 5:975 0:000 HDA Controller [8086:0C0C] :: PciRoot(0x0)\Pci(0x3,0x0) => setting specified layout-id=1 (0x1) 5:975 0:000 USB Controller [8086:8CB1] :: PciRoot(0x0)\Pci(0x14,0x0) 5:975 0:000 LAN Controller [8086:153B] :: PciRoot(0x0)\Pci(0x19,0x0) 5:975 0:000 HDA Controller [8086:8CA0] :: PciRoot(0x0)\Pci(0x1B,0x0) => setting specified layout-id=1 (0x1) 5:975 0:000 RCBA access disabled; trying to enable 5:975 0:000 stringlength = 1362 5:975 0:000 CurrentMode: Width=1920 Height=1080 5:975 0:000 Beginning FSInjection FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 9F507218 FSInjectionInstall ... - Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 9F507218 5:980 0:005 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 5:981 0:000 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.11 5:983 0:002 Extra kext: EFI\CLOVER\kexts\10.11\AppleACPIPS2Nub.kext 5:986 0:003 Extra kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext 5:993 0:006 Extra PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext\Contents\PlugIns\ApplePS2Keyboard.kext 5:997 0:004 Extra PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext\Contents\PlugIns\ApplePS2Mouse.kext 6:000 0:003 Extra PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2Controller.kext\Contents\PlugIns\ApplePS2Trackpad.kext 6:004 0:004 Extra kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext 6:008 0:004 Extra kext: EFI\CLOVER\kexts\10.11\NullCPUPowerManagement.kext 6:014 0:005 Removed efi-boot-device-data variable: Not Found 6:014 0:000 Custom boot screen not used because entry has unset use graphics 6:014 0:000 Closing log
submitted by poc7667 to hackintosh [link] [comments]

More Complex Binary Option Setups The truth - Forex trading, Binary trading etc and Vusi ... binary options robot: connect mt4 indicators with iQBot (using include file - Method #1) Full Explanation - Trading binary options live tutorial ... Forex Trading VS Binary Options Trading Philippines Form panduan OP All Pair Binary Option - Signal 4G LEBIH UNTUNG TRADING BINARY OPTION ATAU FOREX DAN SAHAM ... What Are Binary Options? - YouTube The Best Candlestick Patterns to Profit in Forex and ... Binary Options Trading - Binary Options - The Best Binary Options Trading Guide for 2017

Home » Blog » App Development » How To: Working with Plist in Swift. How To: Working with Plist in Swift Written by Reinder de Vries on August 6 2020 in App Development, iOS, Swift. A property list, commonly abbreviated as plist, is an XML file that contains basic key-value data.You can use a plist in your iOS apps as a simple key-value data store. Let’s find out how that wor I’ve detailed these and other free options in the video below. If you’re a developer you’ve got a lot of options for free editing of PIST files. I wrote an article about Open-Source code & tools for PLIST editing of both binary & XML format data. Plistinator, by Smithsoft. Smithsoft builds apps and games: and we use PLIST files a lot! One day we needed a cross platform PLIST editor ... This changes the plist in XML back to binary format. Once it’s in binary format it will not be editable with a standard text editor again, unless you convert it back into XML, or use Xcode’s built-in property list editor tool.The modified binary list files can then be placed back into various system level or app level directories as necessary. Available options for this command; json or xml.This does not only control the display format of binary property lists, but also for json and xml files. If the option is set to json, property lists in xml format will be displayed as json as well (but the format used when saving will be preserved).. Change the plist format used when saving property lists: The best OST to PST converter software is SysTools, an all-in-one utility for Windows systems that ensures full data conversion from OST files such as emails, calendars, contacts, notes, and tasks into PST format. It allows for batch conversion, file migration along with attachments, selective email export, file scanning and previewing, and decryption of encrypted OST file. The binary plist format seems like a good choice. Unfortunately plistlib doesn't do binary files, so step right up PyObjC. (Segue: I'm very open to any other thoughts on how to accomplish live search. I already pared down the data as much as possible, including only displaying enough results to fill the window with the iPhone keyboard up, which is 5.) Unfortunately, although I know Python and ... plistutil allows to convert a file in Property List format from binary to XML format or vice-versa. Options-i, --infile FILE. Input FILE to convert from. If this argument is omitted or - is passed as filename, plistutil will read from stdin. -o, --outfile FILE. Output FILE to convert to. If this argument is omitted or - is passed as filename, plistutil will write to stdout.-f, --format [bin ... A rails plugin to use the .plist format to return binary plists - jeena/plistifier Library to handle Apple Property List format files in binary or XML: ms: summary refs log tree commit diff stats: diff options. context: space: ... AUTOMAKE_OPTIONS = foreign. ACLOCAL_AMFLAGS = -I m4. SUBDIRS = libcnary src include tools test docs + if HAVE_CYTHON . SUBDIRS += cython. endif + if BUILD_FUZZERS. SUBDIRS += fuzz. endif. diff --git a/cython/ b/cython/ index ... Offers Two-Mode Scanning Options that Allows to Easily View ... It stores the complete data in PST format, which includes the data of different mailbox items like emails, tasks, calendars, etc. The file extension of PST is a binary file format that is exclusively designed to save email information in particular order. The latest version of Outlook generates a Unicode PST format that can ...

[index] [25385] [22767] [723] [7254] [26601] [20585] [29464] [1075] [20249] [25664]

More Complex Binary Option Setups

Binary options are form of options trading based on a yes or no question. Try binary options today at: You're either right... add new ready indicators to your MetaTrader and easy way to connect with iQBot watch the full video to see how to edit indicators to add include file inside any indicator Whatsapp: ... Form panduan Open Posisi All Pair Binary Option Olymptrade The Secret of SO 532 - by Signal 4G Salam PR... binary options format binary options free binary options free no deposit bonus binary options edge binary options europe binary options explained binary options exchange binary options expert ... The Best Candlestick Patterns to Profit in Forex and binary - For Beginners trading forex, forex strategy, forex,Online Trading Strategy #Candlestick_Pattern... Presenter: James Ramelli with AlphaShark Trading Learn how to use binary options to collect weekly income, trade non-directional breakouts and other more com... Trusted spots blog To register a free account on desktop or laptop, click here To register a f... BELAJAR TRADING ONLINE BERSAMA SAYA (DIMANAPUN DAN KAPANPUN ANDA DAPAT BELAJAR LANGSUNG) Instagram ... I have been receiving a lot of messages from people saying that I am into trading and that I am trying to get other into this trading business. I do not trad... With binary options, besides options trading and enjoying yields of up to 92% binary options trading - Conservative binary options trading strategy introduction to binary options trading. Freedom ...