Jump to content

BugsB

Members
  • Content Count

    1,447
  • Joined

  • Last visited

About BugsB

  • Rank
    InsanelyMac Legend

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Kauai, Hawai'i

Recent Profile Visitors

14,715 profile views
  1. getting closer, partial success: What I did was, copy the DiskManagement.framework from your Disk Utility for Mojave (not there yet).app into Disk Utility 13 (607).app, overwriting the old one (after backing it up). Obviously the volumes in the side bar on the left are now missing. I did some testing back and forth of the folders and files inside DiskManagement.framework: the DiskManagement binary is the "do-jobby" here and thus the ONLY culprit file to fix, at least for High Sierrra. I see both binaries have the exact same byte count, so I compared them with Hex Fiend: there is 66 differences (most just one or a few bytes), which is too much for byte restore debugging. You apparently have more experience with and a better handle on byte patching, so I'm sure you'll succeed. Getting this to work in High Sierra seems like a good basis for Mojave GOOD JOB !!!!!
  2. @Tetonne you are welcome. @dimosgmx that's good news. I also got your message but reply here for best exposure and open collaboration. I have also been debugging via Terminal: File: Debug Disk Utility 13 (607).command (attached) #!/bin/bash clear echo "Put this script next to Disk Utility 13 (607).app" echo "" cd "$(dirname "$0")" sudo ./"Disk Utility 13 (607).app/Contents/MacOS/loader.sh" with the following results (10.13.6): On start: Failed to connect (cancelRecreate) outlet from (DUWindowController) to (NSButton): missing setter or instance variable Failed to connect (repairSheetInfo) outlet from (DUWindowController) to (NSTextField): missing setter or instance variable 10.4-style NSNumberFormatter method called on a 10.0-style formatter, which doesn't work. Break on _NSNumberFormatter_Log_New_Methods_On_Old_Formatters to debug. This message will only be logged once. Click onto: 1. New Image; File/ New Blank Disk Image (same error): *** Assertion failure in void *FinderKitLibrary()(), /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1561.60.100/Nav.subproj/NSSavePanel.m:810 2. Convert; Verify; File/ New Disk Image from Folder; Open Disk Image (same error): *** Assertion failure in void *FinderKitLibrary()(), /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1561.60.100/Nav.subproj/NSNavFinderViewFileBrowser.m:48 I see from your Disk Utility for Mojave (not there yet).app (which does not even start in my 10.13.6, not even after I signed it) you already added the AppKit.framework It might be necessary to kill any running default OS process of the same name DU 13 needs to access. It might also be helpful to run DU13 via terminal debug in Sierra 10.12.6 (I don't have it installed) to see how the messages should look like. But maybe that would be an extra step. Does anyone know if this got broken from 10.12.6 to 10.13.0, or if it was still running in the initial High Sierra and got broken with a 10.13.x update (as did the diskmanagementd command requiring a killall after the 10.13.4 update)? It would be much easier to debug within a High Sierra update line, just looking at the files of the culprit update. Good luck! Let me know if I can test anything. I might be a bit unresponsive the next three days, but then things should lighten up a bit. Debug Disk Utility 13 (607).command
  3. BugsB

    Disk Utility (patched_v2)

    Here you go: Disk Utility v.13 built 607 with Debug Options for macOS Sierra & High Sierra up to 10.13.6 Not tested yet in Mojave.
  4. @MaLd0n a from YOU weighs 1k fold - obrigado amigo Do you (or @dimosgmx etc.?) happen to have any idea which files(s) from Sierra might be needed to revive the file window functions? If we manage to figure that one/ these out, we'll again have a full-fledged DU for High Sierra (and hopefully beyond). Also: can you test my built on Mojave?
  5. BugsB

    Disk Utility v13 for macOS Sierra.zip

    Here you go: Disk Utility v.13 built 607 with Debug Options for macOS Sierra & High Sierra up to 10.13.6 Not tested yet in Mojave. I recommend everyone to update their v.13 (606) because this mod of mine also fixes the original Disk Utility Error: framework unable to communicate with disk management daemon tested with Disk Utility v.17.
  6. Version (built 607)

    52 downloads

    This is my mod of dimosgmx's Yosemite (10.10) Disk Utility app with the El Capitan (10.11) diskmanagementd: https://www.insanelymac.com/forum/files/file/621-disk-utility-v13-for-macos-sierrazip Please read his statements over there FIRST !! This built (607) is dimosgmx's built 606 ever-so-slightly edited* by me (BugsB) for usage in High Sierra beyond 10.13.3. It thus works in 10.12 - 10.13.6 (not yet tested in Mojave because I don't have it installed). Therefore I bumped CFBundleVersion to 607 and BuildVersion to 19 to differentiate it from dimosgmx's 606/ 18 which was only compatible up to 10.13.3. You can use it side-by-side with the default Disk Utility. NOT WORKING (at least not in High Sierra): functions which would invoke a Finder style window, like clicks onto "New Image", "Convert", "Resize Image", "Image", "File/ New/.." etc. In case of issues with the default (original/ stock/ vanilla) Disk Utility: run killall diskmanagementd, also supplied in this package. If you have the SIMBL plug-in AFLOAT installed and have not included AppleScript Utility in mySIMBL's blacklist**, you MUST blacklist Disk Utility 13 (607) (see screenshot "AFLOAT users mySIMBL application blacklist")! Enjoy & Greetings BugsB 2019-01-05 --- * Disk Utility 13 (607).app/Contents/MacOS/loader.sh: Added two instances of: sudo killall diskmanagementd ** in mySIMBL: System Info/ SIMBL application blacklist (because Afloat is NOT fully compatible with Apple Scripts (parts of Disk Utility 13 (60x)) PS: let me know if it also works in Mojave. Include your EXACT version (10.14.0/ .1/ .2 /.3 BETA etc.)
  7. So then - do you like it? Does it work for you ?
  8. After the 309 Update, what should be the login screen (after the verbose mode screen with all the lines flashing by and the brief intermediate black screen with the progress bar), is now a black screen, with just the mouse pointer movable (doesn't change when pressing keys). On my X510UAR in High Sierra 10.13.6 booting to Desktop with BIOS 308/ 303/ 301 has always worked fine regardless if with static or hot patch, and even w/o any DSTD patches. Latest hotpatch v.8 from saintno1997, but same thing with original/ stock ReHabMan config_HD615_620_630_640_650.plist instead of hotpatch config.plist, or any previous EFI folder from backup. Latest Clover versions (by RehabMan on Volumes/EFI, by Slice on Volumes/Clover) and latest versions of all kexts, installed to L/E. When I wait a few seconds for the black screen, type my PW, press enter, plug in my external monitor, it usually kicks in after some seconds displaying the Desktop, then the Laptop screen comes alive, too (or I need to unplug the external for that to happen)! But at first everything was painstakingly slowed down, like running on 1% CPU power. Activity Monitor did not reveal anything unusual. I managed to solve at least that one malfunctioning aspect by setting the UHD 620 ig-platform-id 0x59160000 in Clover config/ Graphics, but still many things graphics-related are "sticky": - apps with transparency effects etc. misbehave - Dock magnification tends to stick - no preview when I type something into Spotlight etc. - dragging files and folders I've done file-by-file diff compares of corresponding *.dsl pairs with Beyond Compare 308 --> 309. Final findings: DSDT: only two differences: 309, line 70 (added line): External (_SB_.PCI0.GFX0.GLID, MethodObj) // 1 Arguments (from opcode) then in both BIOSes, under Scope (_SB.PCI0.LPCB.EC0): 308, Line 40301: Device (LID) { Name (_HID, EisaId ("PNP0C0D")) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Store (One, Local0) Store (RPIN (0x11), Local0) If (LEqual (Local0, Ones)) { Store (One, Local0) } Return (Local0) } } was changed into 309, line 40263: Device (LID) { Name (_HID, EisaId ("PNP0C0D")) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Store (One, Local0) Store (RPIN (0x11), Local0) If (LEqual (Local0, Ones)) { Store (One, Local0) } If (IGDS) { ^^^^GFX0.GLID (Local0) } Return (Local0) } } So all I see accdg. to Beyond Compare is a If (IGDS) condition inserted into Device (LID). Removed the 4 lines with the If (IGDS) condition, compiled, applied to Clover/ACPI/patched, rebooted --> black screen. Applying the misc_LidPoll.txt work-around via MaciASL [misc] Poll for LID changes + ACPIPoller install --> reboot did NOT solve this, either. SSDTs: the 6 SSDTs SSDT-x.dsl and SSDT-x3_x.dsl are all exactly the same = did NOT change from 308 --> 309. Unless there is a graphics related change in one of the other SSDTs, ^^^^GFX0.GLID (Local0) would be the culprit causing a black screen where the login screen should be, and simply commenting it out does not help any. Does that produce an incorrect lid state leading to a black screen? Or is this a framebuffer issue introduced by the 309 upadte? I next also tried the other ig-platform-ids I know of for the UHD 620 (0x59180002 and 0x59180009), but these don't work. From what I know studying the boards, there is no other ig-platform-id which would make sense trying, right? this being a ACPI related issue. As usual ASUS did not provide a change log. Here's what else I've already tried, with same result: - boot with -f - boot into safe mode -x - static patch config.plist w/o any DSDT - empty EFI/CLOVER/ACPI/patched folder w/o any SSDTs - put to sleep and wake back up - SMBIOS sys def 15,2 (hotpatch v.8 from saintno1997), or 14,1 (the one I have always been running) - in Clover, re-activated kext patch AppleBacklightInjector.kext (credit RehabMan) What to do next - how to proceed from here? What's new with this Notebook after this 309 BIOS update is that it does NOT even boot w. static patch config.plist and no patched DSDT. Therefore I don't think that creating a static patch DSDT would help here. Black.dragon74's gen_debug script gets stuck at "dumping Clover files" in this limited mode, even after 30 minutes or so, and neither does it work in single user mode mode in general, so I generated problem reporting files booted in 309 BIOS manually (below). I attached the full debug_BIOS_308_GOOD.zip, + the manual_debug_BIOS_309_Black-Screen.zip with only the changed files, all other files already being present in debug_BIOS_308. That way you can have a look at what changed from 308 to 309 in the graphics related sections, and can hopefully give me hints how to proceed. Back on 308 for now, but concrete pointers are very welcome! Thanks, everybody. PS: for those with DSDT knowledge, here is a Google search on If (IGDS) ^^^^GFX0.GLID (Local0). manual_debug_BIOS_309_Black-Screen.zip debug_BIOS_308_GOOD.zip
  9. BugsB

    ESP Mounter Pro

    by request I can post a tutorial how I managed to have ESPs show up again in ESP Mounter Pro.
  10. BugsB

    ESP Mounter Pro

    @all: Download latest version: https://mac.softpedia.com/get/Utilities/ESP-Mounter-Pro.shtml @Micky1979 & @Mirone: Thank you. It slipped your attention that v.1.9.1 is displayed with a version # 1.0 in Finder because of wrong CFBundleShortVersionString in ESP Mounter Pro.app/Contents/Info.plist. Easy to correct ..
  11. BugsB

    Shutdown on low battery

    Have a look at It's open source and you can adapt anything to your liking
  12. SleepOnLowBattery (“SOLB”) by BugsB, based on a script by Toggi3 * + more code snippets from the www For those of us whose HackBook/ MacBook does not go to into power saving mode automatically on very low battery but just powers down coldly: “SOLB”, a small and low load footprint AppleScript based utility that checks the battery level every 2 minutes. You can choose between two versions, either with or without sound. Both display a notification in the top right of your screen. Between ≤10 and >8% battery charge: Between ≤8 and >5% battery charge: On ≤ 5% battery charge you will see a 10 seconds countdown dialog box in 1 second intervals: which you can cancel, or have your your *ac*Book be sent to sleep when down to 0. The version with sound uses the pleasant macOS US female voice Allison. If the lady is not installed, you can download "her" via System Preferences, Accessibility, Speech (pane tab should get opened by the install script), click onto the two arrows to the right of System Voice, Customize, English (Unites States) -- Female, activate Allison, OK (macOS downloads voices to /System/Library/Speech/Voices - Allison consumes 120 MB). If you want to see/ see and listen first, disconnect your Mac from its power supply and double click the “run Demo” file in either folder, with or without sound. The launcher is installed per user, so one user can use the script with and another user the script without sound. Run your desired install.command, with or without sound. The script should be active right away without restart. Regarding the sound version, you can also: - download any other English voice of your liking and edit the name inside the script at the very top - download any language voice and translate the text inside the script Edit with Apple Script Editor, save, install, reboot. Tested working in macOS High Sierra 10.13.6. Please feedback if this utility also works in Mojave. If you have ideas, experience bugs, etc., please contribute as precise, succinct, productive and friendly as possible. In case of a bug, always include your version of macOS for me or others to try and help. Thank you. ENJOY VERSION HISTORY: 2018-11-10: 1.0 (initial version) IDEAS TO IMPLEMENT IN FUTURE RELEASES: Have the sound version install script check if Allison is installed, and if not, offer to download and install it. Purely cosmetic: find a way to have the display notification in the top right of the screen not display the Script Editor icon but the one of the utility without turning the utility into an app but by maintaining a script to keep the load footprint low. This is currently neither possible with an Apple Script nor with an Apple Script Bundle file, only with the script compiled into an app. One possibility might be a Perl approach, if someone volunteers. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Thanks to Toggi3 for the base script: https://hints.macworld.com/article.php?story=20110219013713667 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ THE CODE (of the version with sound): install.command: LaunchAgent SleepOnLowBatterySound.plist: Script SleepOnLowBatterySound.scpt: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SleepOnLowBattery (SOLB) by BugsB v.1.0 (2018-11-10).zip
  13. Hello tluck. Thanks for maintaining this package. I was lead here through your Broadcom PatchRAM driver package with changes of the timings to support USB BT on the Lenovo T460. For me (and also others across the hackintosh forums), your kexts solved the glitch of no Bluetooth after wake from sleep after two or more wake-ups on battery with stock RehabMan kexts (for me most current v.2.2.10, 2018-05-06). I am running a swapped Lenovo FRU 04X6020 BCM94352Z NGFF M.2 in my Asus Vivobook Laptop. The kexts on your releases page are very old (v1.4.1, 2015-02-08), so I compiled your latest 2.2.7c code from 2018-04-09 myself, and the resulting release built BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext work just fine. I bet you are fully aware that they are based on old code - RehabMan 2.2.7 2016-07-05, thus compatibility will most likely become an issue sooner or later. A few questions and requests to you, if I may: 1. Have you tried to apply your timing changes to RehabMan's latest code from 2018-05-06? If so, did it result in the desired effects, or not? 2. Can you update your releases page with the latest working kext binaries, either 2.2.7c or 2.2.10, if you have compiled them and you have tested them to be working? 3. Can you document your modifications, best on github? Which file(s) did you modify, and with which modifications (find/ replace with, single or all occurrences)? Just 6 IOSleep value changes and 1 IOSleep addition in BrcmPatchRAM.cpp, or anything else? With fork mod info on github, others can potentially carry on your work (it's always sad when knowledge dissipates into the nothingness of time) Would be great to hear from you (I hope you are reading this). Cheers, Bugs
  14. BugsB

    Shutdown on low battery

    Very cool. Is any of the sleep or hibernate scripts still known to work in macOS High Sierra 10.13.6? /Applications/Utilities/deepsleep ; exit; dyld: lazy symbol binding failed: Symbol not found: _IOPMCopyActivePowerProfiles Referenced from: /Applications/Utilities/deepsleep Expected in: /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit dyld: Symbol not found: _IOPMCopyActivePowerProfiles Referenced from: /Applications/Utilities/deepsleep Expected in: /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit Abort trap: 6 logout
×