Jump to content


  • Content Count

  • Joined

  • Last visited

About maxneko

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
    US - NYC
  • Interests
    Macs & Photography
  1. maxneko

    All USB ports are unresponsive

    Resolved by reflashing the BIOS and doing a clean installation to a different drive. I guess the more we mess around with a startup partition, the more likely something like this becomes.
  2. maxneko

    All USB ports are unresponsive

    Thanks @MaLd0n. If I put RunMe.app on my installer USB, can I boot into recovery mode and run it from the terminal?
  3. maxneko

    can't open mojave after install

    Does it just reboot before it reaches the desktop while text is scrolling? I had that, too. In my case, it had to do with my graphics settings in Clover.
  4. TLDR: I've gotten myself up a creek without even a working keyboard and mouse. My setup Asus X99 Deluxe motherboard Dual Asus Radeon R9 280x GPU's i7 5930K CPU G.Skill - Ripjaws Series 32 GB (4 x 8 GB) DDR4-2400 Memory Highpoint 2721 RAID controller + 4 hard drives EVO 850 Pro SSD Mojave 10.14.4 Profile: MacPro6,1 I had installed Mojave and had set it up to boot directly into my user account with no need for a password. Both Clover and IORegistryExplorer were set as log-in items. This was because I was working on activating my SS ports. The X99 Deluxe USB ports are set up as follows: USB3_E1 to USB3_E10 at the rear (Asmedia controller) USB_13 & USB_14 at the rear (Intel) USB1112 & USB1314 (headers on the motherboard) USB3_12 & USB3_34 (front) This adds up to potentially 34 ports, far more than I need. I had three patches enabled to remove the 15 port limit but they weren't doing the trick. So I disabled the ten USB3 ports on the rear that are subject to the Asmedia controller in BIOS. I also disabled the Asmedia USB3 controller. All I really need are the four USB3 ports on the front panel, along with one of the motherboard USB2 headers. This should have gotten me down to under 15 ports. One SS port appeared in IORegistryExplorer but I couldn't locate it when I tested every active port. I'm not sure what I did but everything went sideways. I found that I was booting into Mojave, Clover and IORegistryExplorer were launching but the mouse cursor was frozen in the corner and the keyboard was dead. Moving the keyboard and mouse to different ports didn't help. Meanwhile the OS was giving me a message about looking for a BT keyboard which I don't have. I've tried the following to no avail: -- reinstalling Mojave -- various combinations of USBInjectAll.kext, XHCI-X99-injector.kext, X99_Injector USB 3.kext, and GenericUSBXHCI.kext -- resetting the CMOS -- enabling and disabling the ten Asmedia USB3 ports on the rear -- enabling and disabling the port limit patches below: I haven't reflashed my BIOS which is something I do when starting from scratch, although I don't see why it would matter. I'm open to that, burning incense, whatever will help. In the end, I need at least 1-2 working USB3 ports. But right now, I just need to get my keyboard and mouse working again. I've been going in circles on this all day and could really use some good ideas. Thanks so much. Max config copy.plist
  5. Yes!!! I just tried with a 16GB USB3 flash drive and it worked! (I tried with the 32GB version of the same flash drive, but didn't have any luck yesterday.) My PNY 8GB USB2 flash drive is quite old. I wonder whether there are firmware updates for it. Thanks so much. EDIT (Update): I checked the three USB flash drives that I had been using. While they were all formatted with FAT32, two of them had GUID Partition Maps. I must have formatted them on my MBP without first selecting Show All Devices. Had I done so, I would have seen the partition map option which otherwise doesn't appear. Even though these devices were accessible through the UEFI, this might explain why the USB flashback wasn't working. This was an expensive lesson from a time standpoint. I built my Hackintosh back in late 2014 because Apple wasn't making the computer that I wanted. I need to remind myself of this because if I place any value on the time I've put in over the years, this turns out to be vastly more expensive than the trashcan Mac Pro of 2014. At the end of the day, you have to enjoy the process.
  6. Thanks, @fabiosun. I've been trying for the last day or two, off and on but still without success. With the power supply switch on but the computer not yet turned on, I pressed the red button that clears CMOS. The computer would wake up and start trying to boot. I then turned the power off and back on. I then tried the flashback but no different result. I would hold down the flashback for about two seconds until the LED started to blink. The LED would blink a total of three times and on the fourth remain lit for however long the power supply was left on. When I'd restart the computer, my CMOS settings had been cleared but the BIOS was the same. The latest BIOS, 3902, is designated as a beta, although it's been out for nearly a year. I downgraded to 3802 via the UEFI and then tried to upgrade to 3902 via USB flashback. That, too, didn't work. I tried patching 3802 but no better luck when it came to the USB flashback. I haven't yet tried removing the CMOS battery, although I'm not quite sure why it would make a difference. I tried disconnecting everything connected to the motherboard except the CPU. Still no luck. This has been object lesson to me in leaving well-enough alone. A few months ago, I had a fully functioning Hackintosh in High Sierra. But I had always been annoyed by my failure to get both GPU's working. For some reason, my Hackintosh was only happy when it had a Thunderbolt card that I never used in the fifth slot. I decided to ditch the adapter and go with just the two GPU's and RAID controller. As I was taking things apart, it occurred to me not to get greedy. I then couldn't get it to reboot in High Sierra and finally decided to take the opportunity to update to Mojave. Since then, I've had to do my photo editing in Windows which isn't impossible but generally sucks. I have 10GB of data on an HFS-formatted RAID that Windows can read thanks to software from Paragon. I'm concerned that this isn't a resilient setup, particularly because while I have the usual arsenal of Mac troubleshooting software, I have nothing equivalent in Windows and wouldn't know how to use it if I did. While it's more elegant to proceed with a patched BIOS, I assume that it's not a dealbreaker. Is it time to move on?
  7. Thanks, KGP, I appreciate you really spelling things out. I've made progress but am not quite there yet. updated the microcodes in the Asus stock BIOS in Windows, using mmtool. unlocked the msr register using UEFIPatch (no error messages and patched BIOS file created) as suggested, I ran UEFIPatch first and then updated the microcodes in Windows am using a PNY USB 2.0 8GB flash drive, formatted FAT32, with the patched BIOS renamed to X99D.CAP in the correct port (the one with the green rectangle around it I turned on the power and held down the flashback button until the first blink of the blue LED (about two seconds). I released it whereupon it blinked three more times and then turned solid. It stayed solid indefinitely. I tried the above using an unpatched Asus BIOS file with the same result (encouraging, in a way). I successfully reflashed the Asus BIOS from within the UEFI using the same unpatched Asus file. I tried reflashing with the patched BIOS from within the UEFI. I got an error along the lines of "This is not a proper BIOS." (I believe this expected?) My guess is that I either have a hardware issue with my motherboard or else that there is something blindingly obvious (except to me) that I'm doing wrong with the USB flashback. Does it matter what devices are connected to the motherboard? Could the CMOS backup battery come into play? Is there a command that resets the board to its out of the box state?
  8. Thanks, KGP. I actually tried the short version after changing directories and I got "-bash: UEFIPatch: command not found". I assumed that I needed to edit my bash file. I located another version of UEFIPatch here: <<https://github.com/LongSoft/UEFITool/releases/download/0.26.0/UEFIPatch_0.26.0_mac.zip>> and ran the command successfully, inasmuch as a new .CAP file was created. Unfortunately, the flashback failed. I'll now try your suggestion above. Thanks again, Max
  9. Last login: Fri Mar 8 16:08:46 on console MacBook-Pro:~ maxneko$ cd /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx MacBook-Pro:UEFIPatch_0.3.9_osx maxneko$ /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx/UEFIPatch /Users/maxneko/Desktop/UEFIPatch_0.3.9_osx/X99D.CAP parseImageFile: Aptio capsule signature may become invalid after image modifications parseSection: section with unknown type 52h parseFile: non-empty pad-file contents will be destroyed after volume modifications parseSection: section with unknown type 52h parseFile: non-empty pad-file contents will be destroyed after volume modifications Function called with invalid parameter MacBook-Pro:UEFIPatch_0.3.9_osx maxneko$
  10. Ouch! Sorry... So I went back to the X99D.CAP file generated in the UBU folder and ran it through UEFIPatch on my MBP. I got the text you mention in the guide that is harmless. The difference was that, in my case, it ended with "Function called with invalid parameter". No patched .CAP file was generated.
  11. Hi KGP, Thanks for your encyclopedic effort with this and other guides. I've run into a roadblock modifying the BIOS file for my Asus x99 Deluxe. The microcode update appeared to go smoothly, inasmuch, as my outputs match your screenshots. However, when I tried to run UEFIPatch, I get the following error message: Unsupported 16-bit Application The program or feature "[...] UEFIPatch.exe" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available. FYI, I tried loading the BIOS file created by MMTool directly from a USB flash drive with the computer off but the update didn't go through. The LED just flashed four times and then stayed solid. I also tried via the UEFI at startup but got an error message. Any thoughts on how to proceed? Thanks for your help. Max