Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 08/27/2021 in all areas

  1. If I have the time I will try to put up 0.7.4 EFIs for you all when it releases. No promises though but I will try to get it done.
    13 points
  2. Ok I got it Downloads InstallAssistant.pkg then leave it in Downloads folder Delete any Install macOS Monterey.app in Applications Make sure your not have Folder InstallAssistant in Downloads This is the contents of the script, you can read and open with TextEdit Attach script create_app.command-v2.zip #!/bin/bash # script for making installer Monterey Beta 7 # by chris1111 echo " **************************************************** ****** Install macOS Monterey ******* ****************************************************" sudo rm -rf /Applications/"Install macOS Monterey beta.app" sudo rm -rf $HOME/Downloads/InstallAssistant sudo installer -verboseR -pkg $HOME/Downloads/InstallAssistant.pkg -target / echo "Expand Package Please Wait. . . " pkgutil --expand $HOME/Downloads/InstallAssistant.pkg $HOME/Downloads/InstallAssistant Sleep 1 echo "Attach Image " echo " " hdiutil attach -nobrowse $HOME/Downloads/InstallAssistant/SharedSupport.dmg sudo mkdir /Applications/"Install macOS Monterey beta.app"/Contents/SharedSupport echo "Copying Resources Please Wait. . . " sudo cp -R /Volumes/"Shared Support"/* /Applications/"Install macOS Monterey beta.app"/Contents/SharedSupport echo "Done. "
    10 points
  3. full installer macOS 12 Beta 7 (21a5522h) https://swcdn.apple.com/content/downloads/06/05/002-02555-A_W1UDYXDDUZ/aorhr3psk29e00zwe7r41ur3humfp9cf80/InstallAssistant.pkg
    10 points
  4. Beta 6 (21A5506j) InstallAssistant.pkg http://swcdn.apple.com/content/downloads/41/36/071-90564-A_7W7WHLSY3Z/fx095l2r9n27ykzxmviuycydg88h86fjv7/InstallAssistant.pkg
    10 points
  5. I had more time to do the Script much better Now you can select InstallAssistant.pkg from anywere See script spoiler Attaching V3 create_app-V3.zip Enjoy
    9 points
  6. First monday = exciting day! 😁 Already get OC 0.7.3 running veery smooth here! Thank you devs 👏👏
    9 points
  7. Just to add to my previous post. I have just managed to download (again) and completed the install. These are the steps I followed from the previous posts: 1. I made a new installer USB drive with the SMBIOS of iMac 17.1 2. In the config.plist this change was made: SecureBootModel: Default (nothing else apart from as I said the 17.1 Mac Model) 3. These steps enabled me to do a clean install of Beta 6 as I preferred because of all the trials and errors, I wanted to start afresh. 4. With this clean install I joined the Dev program and was offered the Beta 7 update which downloaded without a hitch. 5. I completed the install still with 17.1 without signing into Apple iCloud, at the Desktop I mounted the EFI Partition and changed the config.plist to my original Mac Model 19.1 Rebooted, clean NVRAM twice and booted to the Desktop containing the new Beta. 6. Signed back into iCloud so that iMsg/F-Time, App Store etc, would be accessible. I must add, dual booting with Windows 11 insider preview I have to enable TPM in the BIOS if not it breaks Windows Activation causing a complete reinstall as it will no longer accept the key once it is broken, I tried leaving it enabled for OS X install and it caused constant reboot loop until I disabled it.
    8 points
  8. Fool-proof guide: Every time a new OpenCore version is released: Download the RELEASE tag from their GitHub repo Read the Dortania post that accompanies the release because if there are any changes that need super attention it will be stated there as well. Keep a backup of your current EFI on a USB Stick's EFI partition so you can boot if things go south. Copy EFI/BOOT/BOOTx64.efi from the downloaded zip to your EFI/BOOT folder. Copy EFI/OC/OpenCore.efi from the downloaded zip to your EFI/OC folder. Copy the drivers you are using on your EFI/OC/Drivers folder from the downloaded zip. Copy the tools you are using on your EFI/OC/Tools folder from the downloaded zip. Read Docs/Differences.pdf Double check that the Resources folder structure has not changed on the new version (from Differences.pdf) Apply changes on your config.plist stated on the Differences.pdf file (if any). Open a terminal, go to the OpenCore folder from the downloaded zip then /Utilities/ocvalidate. Type "./ocvalidate " then drag and drop your EFI's config.plist on the terminal window and press enter. This tool will let you know if something's wrong with your config.plist. Open your Kexts folder Go one by one on your kexts -> Go to the acidanthera GitHub page and visit the repo of each kext, download the latest release from the Tags tab. Unzip and copy the kext to your EFI/OC/Kexts folder. Reboot PS1: I prefer first deleting the files that I am about to copy over to my EFI folder. So I do not replace the files, but add them fresh. PS2: If you read the Dortania OpenCore guide MANY MANY times then you will start understanding how to create an EFI by yourself, and this will lessen the possibility of doing mistakes when updating as well.
    8 points
  9. For anybody that’s not seeing the beta6 update using smbios 1,1 or 7,1 and probably anything else, What you need todo is go into the Config.plist and set the SecureBootModel to j160 restart and the update will show up and then disable the SecureBootModel while it’s downloading and let the system do its thing. This is the only method that seems to work so far.
    8 points
  10. I use my Kext-Install.app with the patch Binaries files Install done Reboot Test on DELL Optiplex 790 Sandy bridge system i5 2500K UEFI booting OpenCore 0.7.3 Works well
    7 points
  11. As always, please read the message by @vit9696 , the best place to learn about the changes received by OpenCore. During the month of August, OpenCore Team has taken a break compared to other months but, despite this, more than 25 compilations have been launched making improvements in OpenCore, OpenCanopy and Drivers. The main changes (but not the only ones) are: Linux support to be natively displayed in the OpenCore boot pickers Updated MacPro7,1 database with new AMD graphic cards Improved laptop backlight (SSDT-PNLF compatibility with CFL+ graphics) Fixed OpenCanopy performance reverting a change introduced in 0.6.9 that was causing redraw of all of screen right and below mouse position at every frame Implemented Boot Entry Protocol, allowing plug-in boot entry drivers Improved security (updated Apple Secure Boot variables for x86legacy...). config.plist Misc > Security > ScanPolicy Operating system detection policy list has been modified: changed 0x00001000 (bit 12) — OC_SCAN_ALLOW_FS_EXT >> OC_SCAN_ALLOW_FS_LINUX_ROOT, allows scanning of Linux Root file systems added 0x00002000 (bit 13) — OC_SCAN_ALLOW_FS_LINUX_DATA, allows scanning of Linux Data file systems added 0x00004000 (bit 14) — OC_SCAN_ALLOW_FS_XBOOTLDR, allows scanning the Extended Boot Loader Partition as defined by the Boot Loader Specification. UEFI > Drivers Updated Drivers to support arguments, requires config.plist update. Each driver has now 3 properties: Path, Enabled and Arguments (some OC plugins accept optional additional arguments which may be specified as a string). <key>Drivers</key> <array> <dict> <key>Path</key> <string>OpenRuntime.efi</string> <key>Enabled</key> <true/> <key>Arguments</key> <string></string> </dict> </array> UEFI > Quirks > added ForceOcWriteFlash (boolean) to enable writing to flash memory for all OpenCore system variables. This value should be disabled on most types of firmware but is left configurable to account for firmware that may have issues with volatile variable storage overflows or similar. OpenCanopy Updated Linux variants in Flavours.md Fixed overlong boot entry names breaking text flow in builtin menu. Drivers Added OpenLinuxBoot.efi, OC-native Linux autodetect and boot plugin, implementing OC_BOOT_ENTRY_PROTOCOL to allow direct detection and booting of Linux distributions from OpenCore without chaining via GRUB Added ext4_x64.efi, open source EXT4 file system driver required for booting with OpenLinuxBoot from the file system most commonly used with Linux. Added btrfs_x64.efi, open source BTFRS file system driver required for booting with OpenLinuxBoot from a file system which is now quite commonly used with Linux. Note: btrfs_x64.efi and ext4_x64.efi come from rEFInd 0.13.2. They can be downloaded from OcBinaryData. It is highly recommended that users interested in using OpenLinuxboot to boot Linux systems read the OpenLinuxboot section of the OpenCore 0.7.3 Configuration.pdf file. Kexts AppleALC 1.6.4: Allow optional audio for GPUs and other improvements... CpuTscSync 1.0.4: Added constants for macOS 12 support... DebugEnhancer 1.0.4 HibernationFixup 1.4.3 Lilu 1.5.6: Added helper APIs for backlight smoother in WhateverGreen... MacHyperVSupport: Added network driver stub... RestrictEvents 1.0.4: Skip leading spaces for automatically received CPU names, fixed dual-core CPU spoofing on macOS 10.14 and earlier... VirtualSMC 1.2.7: Improved EC fan monitoring on some systems... VoodooPS2 2.2.5 WhateverGreen 1.5.3: Added the backlight smoother for Intel IVB+ platforms, added two Asus AMD R9 380 graphics cards... Thank you, OpenCore team!
    7 points
  12. Pleasant awakening this morning everything ok here too😀 https://www.insanelymac.com/forum/topic/348778-problems-with-latest-opencore-073-build/?do=findComment&comment=2765709
    7 points
  13. Please always use ocvalidate before posting reports. Don't rely on other junk tools, ocvalidate uses the exact scheme engine from OC + extra sanity-checking, and it is automatically up-to-date with updates.
    7 points
  14. Hello guys, how are you? Just to inform, that to make the community more secure we changed the way we all make logins. Instead of using your "display/user name", now you'll use your email address. Is more secure, and it'll avoid people try to break your accounts. 😉 And also, we put the option to all of you set a 2FA authentication method, getting your account way more secure. Go to Your profile > account settings > Security and Privacy (enter your password) and set the Google Authenticator. 😃 Cya guys!
    6 points
  15. It was time for her to end with the problems
    6 points
  16. Clean install using USB installer. Install time 30 min. Tips to repair Install Monterey App. 1. Open package content of Install Monterey App 2. Create SharedSupport folder 3. Open Install Assistant.pkg wit Better Zip and extract SharedSupport.dmg 4. Copy contents of SharedSupport.dmg and paste it to the folder created in step 2. That's it enjoy.
    6 points
  17. After Update B7 I use my app I will make a new page on github today
    6 points
  18. Beta 7 full installer is not yet available https://mrmacintosh.com/macos-12-monterey-full-installer-database-download-directly-from-apple/
    6 points
  19. @5T33Z0Incremental automatic update has been added, please download the latest release. More suggestions or questions are welcome.
    6 points
  20. Using a USB with my EFI cloned I booted with SecureBootModel set to j160 so show the update. While the update was downloading changed SecureBootModel back to Default and set the SMBios to iMac17,1. Used the USB EFI to complete the first boot into "Macintosh HD" and after that reboot removed the USB and proceeded to use my main EFI with SecureBootModel Default and MacPro7,1 SMBios. Just don't boot into your system with the different SMBios or your iMessage, iCloud, Watch Unlock etc could get broken
    6 points
  21. Update going through on my Latitude E7270 (Clover r5133) and Toshiba R50-B (OC 0.7.0) after rebooting Monterey beta6 with iMac17,1 SMBIOS and re-launching the whole update process. Seems we got a major bug on our hands here. Let's wait and hear from real Mac users... Edit: update to beta7 completed and I was then able to reboot my Latitude E7270 and Tosh R50-B with their original MacBookPro SMBIOS without issues. One of the other major changes with this beta7 is the disappearance of the nVidia kexts: no more GeForce and NVDA kexts which means end of the road for nVidia Kepler cards, at least natively. Whether patching will work like it did for other GPUs in the past remains to be seen.
    6 points
  22. Same here for me as well, boots faster than BS, no glitches or freezing, super impressive so much so that I use it as my daily driver but still have BS incase of an emergency. Another fact to add, I am constantly hitting it with nightly OC releases with no adverse effects to the performance, at the moment running with OC 0.7.4 (03162e0) release.
    6 points
  23. @panosru 12.0 will not be the last version of MacOS with Intel support by a country mile. You have at least 4 or 5 more years of OS support before they do something like that or you would find a lot of Intel Mac users in the court rooms suing over there Intel Mac that they bought in 2021. As much as Apple would love to do it they simply can’t…lol…Hackintosh is safe for a fair few years yet.
    6 points
  24. I see and thank you for the info!! Unfortunately I’d like to make it work on OC 😕 Slice provided a perfect solution. The problem for you is that OC does not yet allow sufficient configurability of SMBIOS. Since you have access to the OC developers on this forum, you might suggest a future improvement by adding Board ID to the PlatformInfo/Generic section of the config.plist. In the meantime, I have both Clover and OC in my EFI and use the boot selector that can be installed to BOOT in EFI to allow me to switch between Clover and OC at will. (The boot selector can be installed as part of the Clover installer package.) It's amazing how far bootloaders have come in the OSx86 community. Since Clover has been around longer than OC, it has more features. I understand the allure of OC and I use it more often than Clover myself but OC still has a ways to go before it matches Clover in configurability. Props to Slice. It's sad to see him have to pitch Clover like it was 3-day old fish. It's not. To Mods: Sorry that this was off-topic.
    6 points
  25. For anyone upgrading to 0.7.3: Make sure to check your config.plist file against the "ocvalidate" utility... The validation errors might be not that clear but the most important thing is that your UEFI>Drivers should follow the "Dictionary" format instead of "String". Check the sample configuration there and update your files accordantly. Don't be like me, always read the changelog messages
    6 points
  26. Compare your plist with the Sample.plist inside the release the driver structure has changed from this 0.7.2 to this 0.7.3 Each driver has now 3 properties: Arguments, Enabled and Path (Also added ForceOcWriteFlash in UEFI -> Quirks) Otherwise the drivers are not loaded (see ocvalidate) Penalty text menu without GUI and the system will not boot Attention doing ocsnapshot with ProperTree could undo the changes made, double check with ocvalidate and edit manually with Plistedit pro
    6 points
  27. I just updated 2 machines to OpenCore 073 Commit 09930f3 After that, BootPicker GUI no longer worked and both machines didn't boot. So there's either an issue with the built or something drastically changed over night. Seems to be related to OpenRuntime.efi. EDIT: I compared the config against the sample and noticed UEFI > Drivers has a different form now: After adding these entries, everything is back to normal.
    6 points
  28. Clover 5138. Nothing to change
    6 points
  29. 👉 Rules Our goal is ensure that the forum remains a helpful & friendly place to learn about how to run Mac OS X on non-Apple hardware, and of course other general banter. We want you to be able to discuss anything and everything here, and to do so we ask that you check out these guidelines for forum use. Do not upload anywhere else files when developers specifically ask not to. We take this matter very seriously, as developers are the very heart of our community. No Flaming. This includes racism, threatening, personal attacks, victimization or hateful content. Retaliation will not be tolerated either; if a member has broken a rule, please use the report feature on the forum and the staff will deal with the situation appropriately. No posting of direct or indirect links to warez or pirated pieces of software, this includes cracks, serials and torrents. Do not publicly argue the decision of a moderator. If you disagree with a moderator take it up with them in private via PM. Only one (1) login is allowed per member. Duplicate accounts will be banned or deleted. Bumping of posts is not permitted. Other than being less annoying it also keeps the posts more informative. Meaningless and useless posts may be removed at Moderator's discretion. Only post your post once (1). This keeps the forum cleaner and makes it easier to find what you are looking for. No advertising or business offers of any kind. No posting of copyrighted material. This includes copying and pasting news articles from news websites. Attached materials must come with clear descriptions of what they are and what they do, linking to this information elsewhere is not sufficient. Materials derived from Open Source must include source code, as well as an explanation of what has been done to it. Discussion of P2P, torrent sites, or similar download sites of any kind will not be tolerated. We do not want to know your illegal downloading habits. Do not post spyware or any other malware. This includes linking to other sites which may contain it. Posting just to promote another site, product, or service (spamming) is not allowed. This site is not here for you to promote your own or anyone else's material. Discussion of commercial spin-offs of the OSx86 scene is allowed if it’s to understand their existence, but no discussion of how to use them, nor any support for these commercial spin-offs are allowed as they are not in the spirit of the OSx86 scene. Example of commercial spin-off: tonymacx86. Why InsanelyMac does not support tonymacx86 VERY IMPORTANT: PLEASE READ! (ABOUT TONYMACX86 AND iATKOS M / Y / EC / SR) 👉 Posting Guidelines If you have a question please do your best to use the search feature and search the forum before creating a new topic. Post in the correct forum and read the forum description. This will make sure that your post will not be removed. Pick an appropriate title and tags (if any) for your post. A good title makes it easier to find what you are looking for. Using informative tags allows for improved searching of related topics. All posts must be clearly written and easy to read. For example, if you have long blocks of text, use the Code option, etc. Limit "empty lines" as much as possible, use punctuation where you can and be concise. Posts may be edited for this reasons by InsanelyMac staff at their discretion. Please remember that you are in a public forum, a bit of courtesy is always welcome. It's always nice to start by saying "Hi" or "Hello" before asking a question or seeking help. Also a "thank you" would be appreciated, especially if the help you get is effective. Your topic does not deserve any more attention than others seeking help hence topic titles must reflect their content, and topic titles containing things like: 'please help' 'look here' 'cash reward' 'urgent' or other inaccurate descriptions will be removed. This includes all-caps titles. Give your hardware specs when necessary (asking for support) and any other time where it may be beneficial to have them listed. Watch this video to guide you how to do that: [Video] How to add a signature. 👉 Signatures, Avatars and Nicks Keep your signature/avatar clean and tidy - should you receive a PM from the staff regarding your signature/avatar, please make the requested alterations or it may be removed/shortened appropriately. To keep pages loading fast for everyone, we request that your signatures and avatars contain no animations or high-definition graphics of any kind. Signatures should be no more than 6 lines of text using a regular font. If you can't fit all of your system specs in that you'd like, why not create a small graphic to contain the information? They should also contain no referral or affiliate program graphics. Avatars should be in "good taste," a qualification that is broad enough to let us determine what is and isn't. Goth-devil-child-wild-eyed-in-the-violent-blackness probably qualifies as being in bad taste. Nothing offensive, pornographic, or vulgar. Nicknames must be readable by the system (without question marks). This will ensure that your nickname can be searched, and that other users can contact you. They should also not contain staff member groups (administrator, moderator, developer, etc.) to prevent confusion. Nicknames should also show respect to the community, thus nothing containing offensive language. Email addresses must be real. Accounts not in line with the last two rules will be edited or deleted without warning. 👉 Policing Do not publicly discuss the decision of a moderator. If there is any issue with a decision of a staff member PM them or contact an admin. Moderators have the ability to suspend or impose posting restrictions upon accounts based on the user's history. Records are kept to keep track of user's behavior and point out repeat offenders. Attempts to circumvent posting restrictions will lead to your account being banned, and any other accounts affiliated with your account being banned also. These rules cover a broad spectrum and are set up to preserve a free and open (and fun) place for discussion. They, in conjunction with common sense and good judgment, should steer you in the right direction. We're all human and we know that people make mistakes... but that's also not an excuse. More rules are subject to appear on this board as we see fit, so please check back from time to time for your own benefit. Thanks for joining our community and helping make it the best it can be. In case the rules localizations should differ, the English rules are the standard.
    6 points
  30. USB Create Install Media HP Probook 6570b Works here OC 0.7.4 Lattest compill MacBook Pro 13.1 (j132) Secound stage Boot install edit *** after secound stage boot Setup MacBook Pro 13.1 (Disable) complet other step boot then result is perfect
    5 points
  31. Intel HD 4000 worsk good on Beta 7 HP Probook 6570b
    5 points
  32. Well, welcome aboard ... you're okay with Linux too 👍 The icons come from myself, every now and then it takes my fancy and I create some sets 🙂 (Backgrounds are resized to your 2560x1440 resolution) https://drive.google.com/file/d/1yiuk4G2fnbGIAngP0LhWjhqNPYAXGVeA/view?usp=sharing
    5 points
  33. Nice find. I use the macOS Calculator app in Programmer mode for Field that has bit setting (like the ScanPolicy). Basically, open the OC Configuration.pdf and go to the section you are interested in changing. Open Calculator App Change View to "Programmer" (CMD+3) Then click each Bit you wish to set the Calculator will show you the new Hex value. Copy and Paste that hex value into the plist editor. If the editor cannot handle hex value, you can convert the hex to decimal in the Calculator App by simply clicking on 10 button before copy-n-paste.
    5 points
  34. AudioGod maybe absent doing other things but the Thread is still alive and well for members with queries. Big thanks to @ntuneddu and @WizeMan nice one Guys, much appreciated I am sure.
    5 points
  35. @tonyx86 Not sure, the XML stack is entirely @vit9696's work. At the moment we have more urgent issues, like the continuous breaking of Apple Secure Boot, sorry.
    5 points
  36. Sorry, I will upload ccpv in each Release.
    5 points
  37. If it can be useful to anyone CloverConfigPlistValidator_r5139.zip
    5 points
  38. Another good example of ALWAYS using OCVALIDATE BEFORE switching to a new version of OC.
    5 points
  39. I managed to get beta 6 show up with CLOVER. This is what I did: 1) updated CLOVER from 5138 to 5139 (no effect) 2) switched from VirtualSMC to FakeSMC with SMCHelper.efi (no effect) 3) changed SMBIOS from iMacPro1,1 to iMac17,1 and deleted NVRAM (update shows up) Hope this helps!
    5 points
  40. Well, that was not the point. The point was that in Monterey, a Windows Disk is detected as an external Drive and therefore is displayed alongside USB Sticks and external drives connected via USB cable – even if the option to have internal drives displayed on desktop is turned off…
    5 points
  41. I solve my Windows 11 SSD showing as external disk by installing a trial version of iBoysoft NTFS for Mac. After installing the Windows 11 disappeared. It works for me and there is no harm in trying.
    5 points
  42. The beta 6 build is available in ANYmacOS now:
    5 points
  43. 5 points
  44. All is OK. Don't bother.
    5 points
  45. v0.9.6 comes with a bunch of fairly important bug fixes and enhancements. Downloads are available at the release page. In short, the driver is pretty stable now. USB-based card readers should be working properly, while PCIe-based ones should work even better than before. Please refer to the changelog for a list of changes since the previous 0.9.5 release. I would like to acknowledge the following members, @b0ltun, @Sherlocks, @whatnameisit, and @gnpaone, for testing early, unstable builds and reporting issues for USB-based card readers. This release won't be possible without their support. Thank you every much.
    5 points
×
×
  • Create New...