OSX86 Recovery – Tools and How To

Couldn’t fix your OSX partition via fsck or OSX tools ? You want your data back , if so , read this guide
Most of the guides out there explains on how to get OSX86 up and running but there are very few guides out there which explains on how to recover OSX86 partition in an event of file structure corruption. Bear in mind that this guide does not cover fully if your disk starts to fail. By default OSX or your BIOS should alert you if SMART (Its a simple self-check of the device to determine if its O.K or K.O ) status shows that it is not okay.
I’ve faced couple of issues with my disk , mostly related to directory structure. I believe this is because I do not shutdown my computer properly and bam one day OSX did not boot at all. Of course , I tried the usual stuff such as booting into (single user) and tried running fsck . Of course it did show that there was an error with my partition , however it could not fix it. Thankfully I’ve managed to discover few great tools which would help to fix your disk-related issues.
1. You need to have MacOS X Installed on another hard disk or on USB pendrives. I highly recommend you to grab a 16GB or 32GB USB pendrive and install OSX to it. It will be a “reecovery” OSX partition whereby you are able to use it in times of fixing your main partition. This is a must have as for us hackint0sh uses we don’t have the privilege of creating a Disk Warrior recovery disc or stuff like that
2. Your OSX partition (your main system that is) must be using GPT , some recovery tools for Mac (especially related to fixing file structure ) would cease to work in MBR.
Tools that you’ll be needing (provided that you are willing to pay and your data is very important)
Disk Warrior (I highly recommend you to purchase this , if you really want to recover data)
Drive Genius
TechTool Pro
Some of the functionality of these tools do overlap with one another , but I prefer to have more than one tool . These softwares do cost money , so do keep that in mind ! I know , you could resort to dark side if you want too , but thats your call
The Free Method
So you don’t want to fork out $50 on a recovery software. The best way is for you to boot via your “recovery OSX disk” and start copying files over to another drive. If you want to keep your “user settings” preserved , I highly recommend backing up your home folder as it would contain your wallpaper , your downloads and whatever you’ve stored. You could move it as well , however it would not contain your applications which you have installed and other system kexts.
However , it would not fix the problem with the hard disk if the file structure is corrupted. Basically you would have to wipe your hard disk and start all over again
If you insist on doing a 1:1 copy , try CopyCatX or Clone X
(Yes , I know what you are thinking . I am just stating an alternative anyway)
Fixing File System related issues
If you have tried fsck and it did not fix your hard disk issue. This is where Disk Warrior comes in play . Disk Warrior fixes a lot of problem related to the file structure. So if fsck couldn’t fix it , you would use Disk Warrior. A word of caution , Disk Warrior could fix your drive , however you may have risk of losing some of your files. Be sure that you have backed them up. So far I have not faced any issue.
Fixing HDD sectors
If fsck reports no errors with the directory/file structure , and OSX is taking a long time to boot with kernel panics. It simply means one of your HDD sectors is bad.By default , your HDD should alert you that it is failing. If you insist on fixing your hdd sectors , give Drive Genius or Tech Tool pro a shot. There are risks involved in fixing hdd bad sectors. If you want to learn more about HDD sectors , click here

Other methods
If you have managed to recover or fix your OSX partition by other means. Feel free to post a comment and I’ll certainly highlight it here



newer hardware and OSX

It has been ages since I’ve updated on OSX. I am pleased to announce that , there are newer hardware supports out there. So if you are on a second generation Core i7 computer or if you are using ATI Mobility card there is some hope for you. I’ve discovered some thread in InsanelyMac today.
However bear in mind , that the article on ATI Mobility 4xxx support for hackbook is technical. So you may have to spend some time on understanding. Nevertheless , if you have some questions to ask , feel free to post in that thread or ask me here. I may give you a clearer explanation as mostly its related to programming and stuff. Here is the thread , feel free to check it out
As for the latest and greatest hardware support , tonymac has updated his iBoot to include latest generation stuff
EDIT : Made a mistake there , nawcom’s blog is the place that you should be going to and yes i’ll be updating my blog as well
My blog you ask – I’ll be here on providing some tutorial advice and stuff on OSX issues and Hackintosh in general. Stay tuned for it

Fixing CSR Bluetooth in OSX (updated info)

Recently , I noticed that my CSR (Cambridge Silicon Radio) bluetooth does not quite work well . These Bluetooth adapters generally cost under $5 and its widely used in many of the laptops. Even real macs do use CSR. I did notice that generic ones would use Apple Generic Bluetooth driver instead of Apple CSR Drivers. Even if you did change the device id and included your device ID in the kext , it would still fail. Of course the generic Bluetooth driver has few issues when it comes to pairing , waking Bluetooth keyboard/mouse from sleep and other general issues

Voila - My $5 adapter thinks its Genuine Apple CSR Bluetooth
Voila - My $5 adapter thinks its Genuine Apple CSR Bluetooth

I did a research further and found out that the kext were hardcoded to work with Apple-branded CSR Devices. Yes , we could simply fire up hex editor and include our Device ID and Vendor but this would be complicated and in return it would require us to perform patching every time we upgrade OSX. Thankfully , AnV did something for Broadcom devices. I took the kext and modified it to work with CSR Devices (Cambridge Silicon Devices). Basically it fools , OSX thinking that our Bluetooth adapter is Apple’s Bluetooth Adapter therefore forcing OSX to load Apple’s CSR driver instead of Generic drivers.
With the injector , the Allow Bluetooth devices wake option is no longer grayed out
With the injector , the Allow Bluetooth devices wake option is no longer grayed out

Anyway , I am quite sure that you are tired with the explanation. Now lets get our hands dirty and start fixing it.
1. Firstly you would need to know your Device ID and Vendor ID for your Bluetooth adapter. It can be obtained from System Profiler. Be sure to convert it from Hex to Dec. If you are unsure , just google for Hex to Dec Calculator
2. Download this kext . Open it up and navigate your way to Info.plist (if you are unsure , right click and select view package content)
3. In Info.plist replace instances of
<key>idProduct</key> <integer>1</integer> <key>idVendor</key> <integer>2578</integer>
with your Product ID and Vendor ID in base 10 (Dec). You shouldn’t need to replace this value as most of the generic CSR adapter would use this value
4. Place it in your /Extra/Extensions folder (or EFI partition) and fix permission.
5. Reboot and the first thing you should notice is that Bluetooth can be toggled on and off and Wake from Sleep option in Bluetooth shouldn’t be grayed out. If it is still grayed out , you will have to fix your USB (Search for USB DSDT patch)
UPDATE #1 – After studying a bunch of IORegistry (just think of a bunch of detailed stuff , that gives the internal working of a system) . I’ve found out that Firmware version plays an important role here. It seems that these cheap $5 dongle that comes from China have different frimware. Each of it reacts differently