Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About jimmyco2008

  • Rank
    InsanelyMac Protégé
  1. jimmyco2008

    FileVault 2

    Ideas about why the keyboard has stopped working... but hey it's all good, it turns out that I am an idiot! I am working on cloning everything to another SSD and I realized it was probably booting from that new SSD's Clover, which may not have the keyboard fix applied. All is well, Slice! All is well!
  2. jimmyco2008

    FileVault 2

    Hey Slice, thanks again for the info earlier... Unfortunately, the keyboard has stopped working in FileVault Preboot after working for the last couple of days with the UsbKbDxe patch. The only thing I can think of is that FileVault finally finished encrypting the entire drive, otherwise I haven't installed any new kexts, or macOS updates, or made any changes to clover (although it is and has been on the latest version). Any ideas? EDIT: I stupid
  3. jimmyco2008

    FileVault 2

    Hello, So based on this thread, it looks like everything I need should be in the Clover package? I'm one of those with a USB keyboard and AMI BIOS. Last I read (on another thread) the driver for my situation was in beta, is this no longer the case? Thank you!
  4. The kexts I've linked in the OP are for Hackintosh, and worked with Mountain Lion. Your proposal might work... I definitely encourage you or anyone who's willing to give it a try. I don't have anything to test it on, all my OS X devices are actual Macs these days. It's my understanding that the AppleAHCIPort.kext has to be modified for each version of OS X. I would imagine the modification that needs to be made remains the same, however I do not believe the AppleAHCIPort.kext from Mountain Lion works with Mavericks, and so on... I would imagine there are a few small differences that Apple makes so that a Mountain Lion kext cannot be used with Yosemite for example. A little while back some users were looking for an AppleAHCIPort.kext that worked with Mavericks, but now that Yosemite is out, I'm not sure how useful your Mavericks version would be. Still, I encourage you to upload it to the Downloads section of Insanelymac.com so others can have access to it if they so wish.
  5. Hey all, First, I don't actually have the kext working for Mavericks or Yosemite. This is a thread, for those who are dedicated, to try and create such a kext so that you can install Mavericks/Yosemite on your computer with SATA mode locked to RAID (as opposed to AHCI or IDE) because your BIOS/EFI is extremely limited. Here's a link to the AppleAHCIPort.kext for Mountain Lion: http://www.insanelymac.com/forum/files/file/56-appleahciportkext-for-raid/ eep357 is "retired", so I'm stuck going through our past message from years ago trying to figure out just what he did to the original AppleAHCIPort.kext to get it to recognize my HP m6-1045dx's hard drive (in RAID SATA mode of course, for some reason). Here's what I know: My laptop had an Intel HM77 chipset. I gave him (eep357) the device ID that was showing up when I booted Linux on the laptop and ran lspci. It was 282a (the Intel SATA/RAID controller). He made two versions of the kext for me (https://dl.dropbox.com/u/12515989/untitled%20folder%202.zip), one unmodded is with the 2829 (AHCI) entry somewhere (not sure if it's info.plist or what...) and one modded with the 282a (RAID) entry. I'm almost certain the 282a one is the one I used to get OS X to finally recognize my RAID SATA hard drive. I'm just not sure what part of the kext he edited... But if we can figure that out, we should just have to apply the "282a" to AppleAHCIPort.kext for Mavericks and/or Yosemite to derive updated versions of the kext. I vaguely remember him having to convert the 282a to binary or hex or something... I'm not sure. I have Yosemite GM3 on my MacBook Pro, and so I'll upload the AppleAHCIPort.kext from that in case it's of use (see below). AppleAHCIPort.kext.zip
  6. jimmyco2008

    [GUIDE] HP Pavilion m6-1045dx (Mountain Lion)

    So I finally found the Gatsby Kext Pack: http://goo.gl/oINTKU And the Gatsby Everything Else Pack: http://goo.gl/ZqvFHi They may be older versions, but it's better than nothing, right?
  7. Unfortunately I wrote this guide using my real MacBook Pro, so it's tough for me to help you, there. You might try plugging the hard drive for your hackintosh into a legit Mac, and booting from it. Then you should be able to follow this guide.
  8. When I had this problem today, Google wasn't much help. Thread after thread with this problem and no solution, except of course to wipe the drive. Files are important, especially your files, right? Background I was running OS X 10.10 Yosemite, and was attempting to rid of a Bootcamp partition I set up on my Macbook's SSD. Disk Utility said no, and I figured the problem would be fixed with a disk repair, since I got the same error when trying to create the bootcamp partition. To do this properly, the disk (internal SSD) can't be in use, so I put it in Target Disk Mode and plugged it into my Mac Mini. I of course have FireVault 2 enabled, and so it asks for the password every time I use TDM. I go to Disk Utility on the Mac Mini and begin the Repair Disk operation for the Macbook's SSD. It fails. Not only that, but it fails to remount the partition. So I unplug it and plug it back in. It asks for the password. I give it the password. No dice. Just hangs. So I started panicking, I shut off the Macbook, tried to boot it normally. It wouldn't actually do anything, just sit on a black screen (Yosemite replaces the white/light gray background with black). So I rebooted again, this time holding the alt key. It brought up my Macbook's SSD. I selected it, and it started booting. Phew. It asked for my password right off the bat of course, because it's FireVault, and it took it and started booting. But then it got stuck about 40% of the way through the loading bar (Yosemite also has a loading bar instead of s spinning circle). I tried booting a few times this way, kept getting stuck. Let it sit for a while. Nothing. So at this point I was freaking out. It seemed there was no way to access the files on this drive. I resorted to Googling the problem, but found nothing, aside from how to format my SSD and reinstall OS X. Like I said, though, files are important, so that wasn't an option... The Magic So in order to recover your files from your FileVault 2 SSD, first you must ensure that you are in the same position I'm in. You tried repairing, didn't work. You can hold alt at boot and actually get to enter your password, and OS X does start to boot. If you can't get that far, because that unlocks FileVault, then you may be out of luck. Otherwise, great! Let's get to work. What we'll be doing is booting OS X into Single-User Mode (Safe Mode + Verbose if you will), and using bash (gasp!), which you may also know as "Terminal", to access the precious files, mount a USB flash drive, and copy said files to said flash drive. Make sure you have a flash drive of decent size. Ideally it's large enough to fit all your files onto it. Otherwise, if you're like me and all you have is a lowly 16GB drive laying around, that'll still work, you'll just have to make multiple "trips" if you will between your Macbook and the device (hopefully another Mac) you're unloading all these files onto. For clarification, if your flash drive is NOT large enough for all your files, you should have another Mac around that can take the files from the flash drive, so you can repurpose the flash drive for receiving new files from the corrupt drive. Also, you'll want to make sure that there aren't any external drives plugged into the problem-child Mac. This complicates things down the line. So anyway, with the Mac off, power it on, and immediately hold alt. Once you're at the "boot drive selection screen", hold command + s and while holding those two, hit enter. In a sec it'll ask for that FileVault password. Go for it, and then you'll see a light show of text, and a cursor at the bottom. Type in /sbin/mount -uw / to cancel the automatic shutdown of Single-User Mode and to mount the Mac's HD/SSD. Insert that flash drive, making sure that it's formatted as HFS+ (Mac OS Extended, Journaled). Type in hdiutil mount /dev/disk2s2 to mount the flash drive, which 99% of the time will be disk2s2, though if you get an error it probably isn't. Look at the disk in Disk Utility on a functional Mac to verify that the HFS+ part of the flash drive is in fact s2. Also, if you have a Mac Mini Server, or really any Mac with more than one internal HD/SSD, it may actually be disk3. So try disk3s2 if disk2s2 doesn't work. Next, we'll want to make a mount point for the flash drive on the Mac's internal HD/SSD. mkdir /Volumes/flashdrive You can replace "flashdrive" what whatever you damn-well please, but do remember what you decide to name it. Okay, so we didn't really mount the flash drive earlier, that was more so you didn't have to type in this longer command multiple times while trying to figure out if the flash drive is disk2 or disk3, etc. /sbin/mount_hfs /dev/disk2s2 /Volumes/flashdrive Of course replace disk2s2 with whatever you figured out your flash drive is, though again, for most people it should be disk2s2. Note: if you eject this flash drive improperly (just pulling it out), upon reinsertion, it will take the next available disk number. So if it was disk2s2, now it's disk3s2. +1 for every time you do this. It's taking me so many trips to back up all my stuff I'm up to disk5s2, so don't feel too bad if you don't feel like ejecting properly. If you do feel the need to eject properly, here's the command to do so: hdiutil eject /dev/disk2s2 Though as long as you're sure there are no file transfers in progress, you're pretty much clear to remove the flash drive improperly. If that white block/cursor is preceded by "bash-3.2#" (or something similar), the transfer is complete. Keep that in the back of your head. So actually copying the files. Ideally, you know what files you need to back up, and you know where they are. Here's an example snippet for copying your Documents folder to the flash drive: cp -r /Users/you/Documents /Volumes/flashdrive Now there are multiple "copy" commands we can use, I went with cp because that's the first one I found in Google. The -r is important because it tells cp to copy all files AND folders (a.k.a. directories) in your specified path. So without the -r, the above command wouldn't copy squat. You could tack on a * at the end of that (../Documents*) to copy all files in Documents, but it would still skip the directories (folders). The more you know. Anyway, if you have a large enough flash drive, you can backup your entire home folder with: cp -r /Users/you /Volumes/flashdrive Woo! Afterthoughts - If you don't know exactly where thinks are, use the ls command. For example, ls / will list all the folders (directories) in the root of the Mac's HD/SSD. You can work from there. For example, you might not recall where exactly this important file is, but you can use ls /Users/you/Desktop and ls /Users/you/Downloads to see if it's in your Documents folder or your Downloads folder. -Remember, hidden folders and files are preceded by a period (ie, .localized), and files have their extensions affixed to them (ie, file.txt). Otherwise, it's a folder! - To navigate to folders with names that have spaces (ie, "iTunes Media"), put a \ in between the last letter of the first word and the space itself to look like so: ../Music/iTunes\ Media - File transfers take considerably longer than if you were using a perfectly-functional Mac. Be patient. Ideally, you have a flash drive like a SanDisk Cruzer that flashes incessantly when it's transferring files. That should keep you content while you nervously wait for the first batch of files to backup. -Make sure you backed up EVERYTHING that you need before formatting that pesky HD/SSD with the Recovery partition or an OS X USB Installer or Single-User Mode if you like it so much. - When setting up OS X all over again on the Mac, really, really think before enabling FileVault 2 again. Remember, if not for FileVault, you wouldn't even have been in this mess.
  9. Hey all! A little over a year ago I published a guide on Hackintoshing the HP m6-1045dx, and hundreds of people downloaded the "all the files you need" pack for it that I had on either Google Drive or DropBox. Here's the original thread: http://www.insanelymac.com/forum/topic/283609-guide-hp-pavilion-m6-1045dx-mountain-lion/ I have the older pack, but I can't seem to find the final one I put out, which is dated 12/09/12. If anyone has it, I'd be much-obliged if you could get it to me so I can get the link working again!
  10. jimmyco2008

    [GUIDE] HP Pavilion m6-1045dx (Mountain Lion)

    I second this. Haven't been in the Hackintosh game for a while, just came back to check in... The files should still be up, but it seems Google screwed up the goo.gl link so it doesn't know where to redirect to.... Nor do I, I think it's in a DropBox account I forgot I had, to be honest. If anyone has it, I'd be much obliged if you sent it to me so I can update the link... Or if you want to host it, that's cool too.
  11. jimmyco2008

    AppleAHCIPort.kext (for RAID)

    Alas, it is not (I assume so, since it didn't work for you... I no longer have the m6-1045dx or any PC for hackintoshing). Thank you for confirming this for other people who visit this page.
  12. jimmyco2008


    I used it with OS X 10.6 (Snow Leopard), the computer I tested it with had an AMD processor, so I couldn't really try out Lion or ML.. or Mavericks.
  13. jimmyco2008

    10.9 DP3 About this mac information

    It also shows installed OS X Mavericks DP updates in the App Store under "Updates".
  14. jimmyco2008




    Makes OS X and the installer work with the nForce 430 chipset. More specifically, allows OS X/installer to see the SATA and IDE (yes, IDE, too!) devices plugged in to your computer, including hard drives and disk drives. This kext does NOT make nForce LAN or anything else work, just SATA and IDE/ATA HDDs and ODDs. --------------------------- Works great with the Compaq Presario SR55 series!
  15. jimmyco2008

    HP Envy 6-1076ez

    Sorry for taking a break from InsanelyMac for a while! No, the HDD has nothing to do with this, "waiting for root device" with a USB installer basically means that the USB port the flash drive is plugged into is not functioning properly with OS X/the installer. In other words, the installer, which has been loaded onto the RAM of the ultrabook, can no longer see the flash drive on the USB bus/chipset, it's not being detected. This is especially true of USB 3.0 because, at least last I checked, USB 3.0 doesn't work right on Hackintoshes, except with USB 3.0 devices. I suppose you might try a USB 3.0 flash drive in a USB 3.0 port, but I'm not sure, since you can't get this 2.0 drive to boot in a 2.0 port. Again, really weird situation, it's a perfectly-hackintoshable ultrabook..... Try, when it gets to waiting for root device, plugging the flash drive into EVERY USB port, yes the 3.0 ports, when you plug it in to each, wait a minute, if you have a flash drive that lights up, it should start flashing almost immediately, if it does not, you can move on to the next port. Otherwise, give it a minute in each port!