Tag Archives: repair

[Ableton] Repairing Defective ALS Files Manually



What happened?

  • many avoidable (stupid) situations arise from hectic rush: we for instance accidentally deleted an ableton set (.ALS file extension) from a local NAS server
  • without going too deep into detail: since we don’t have a RAID based NAS we could recover (some parts of) the desired .als file by putting the NAS’ drive into an old PC and restored the found data with UFS/XFS-Explorer (absolute recommendation) to an external USB drive
  • after loading the recovered ALS file, we encountered the corrupt file error from Ableton


The following article is written by a Mac user, but many (if not all) things should most likely be able to be applied to Windows aswell. Continue reading

[iOS] Apps Crashing iOS 5.01


You’re running a jailbroken iOS 5.01 on an iPad 2 and you cannot use Firewall iP. Installing Firewall iP shows no indication of errors, but when you try to start it, it just splashes shortly and closes instantly. This behaviour is known to some more applications (like Safari or Mail).


It looks like incompatible iOS Apps are responsible for that behaviour. At the moment there seems to be no known approach to find out which app causes issues, but trial and error.

Step 1. Preparations

  • connect your iDevice to iTunes (cable preferred, WiFi may take forever)
  • login and authorize iTunes on this Mac/PC

Continue reading

[MacOS] Save your Data after EFI-X Crash

I. Abstract

Imagine the following situation. You are very keen on this EFI-X device that’s now on sale. So you order a testing device. Some days later the device arrives from Taiwan. Your EFI-X compliant system already kept waiting with a blank SATA 250GB on a Gigabyte EP35-DS3.

After having plugged the EFI-X module to your system, you install MacOS on your PC. It’s really worth the bunch of money since EFI-X lets MacOS boot like a charm. Easy and nice to handle for everyone who is not more willing to hack device drivers into their Hackintoshs. But as a tinkerer who wants to see how it works in real life and so you decide to apply the newest update for your EFI-X module. Since you’re a Mac user you decide to use the MacOS tool provided by the EFI-X team.

All works well during update, until you do the reboot. All of a sudden the intro boot screen of EFI-X looks quite garbled (like the screen below). You wonder what might have happened and do a reboot. As it doesn’t help you plug your EFI-X to another computer hoping you may be able to flash it again using Windows XP. But after all the installation argy-bargy with EFI-X’ virtual device driver under Windows XP – the update tool tells you, you are running the current version.

To make a long story short. EFI-X has customer service and they will exchange their defective units. You may also have a look at the EFi-X Bug Hunt forums for further assistence (please don’t link our article from EFI-X Bug Hunt forums, they will remove it and may ban you – don’t say we didn’t warn ya ;-) Anyway if you need to have access to your data until the RMA unit arrives, we prepped the following article. We’re going to show you how to make your system bootable after the EFI-X device broke for whatever reason.

A short remark before we start: this article is partly based on a HowTo by a guy going by the nick Menoob. We shamelessly stole the method of installing retail Leopards on PCs and adapted it a tiny bit for this EFI-X specific case. Anyway: all the shouts fly out to him.

II. What you need

  • 30 minutes of your precious life time – you may use this time to think about why you didn’t buy a real Mac
  • a Boot-132 disk – it contains your MacOS compatible bootloader (find a list of Boot-132.iso’s for different mainboards and chipsets here – in case you don’t know you should always give the generic.iso a try) – Kudos to Sonotone/Hackint0sh forums!
  • burn the Boot-132 onto a blank CD-R or CD-RW

III. Prepping your hardware

  1. remove the defective EFI-X device and if you feel you don’t need it, send it to the CCC for further examination
  2. let only the MacOS drive and the CD/DVD drive plugged, unplug all other drives from your motherboard
  3. start your computer and hit DEL key to go into your BIOS
  4. inside of your BIOS: set the MacOS harddrive as first boot device and enable AHCI mode for SATA drives – your drives will appear orange/yellow in MacOS, don’t worry about that
  5. save the BIOS changes and reboot

IV. Booting your system

  1. turn on your computer
  2. insert the just burnt Boot-132 CD-R into CD/DVD drive
  3. during BIOS startup hit the F12 key to manually choose your boot device (applies to Gigabyte boards only!!!)
  4. Choose to boot your CD/DVD drive
  5. Your screen will show that ISOLINUX 3.6x is prepping to boot the Multiboot loader
  6. since this ISOLINUX bootloader is not too user-friendly ;-) you will find yourself with a screen similar to this.
  7. Hit the F8 Key. You’re gonna see this:
  8. Hit the ESC Key. and You’re gonna be welcomed with this screen.
  9. Now enter 80 and hit return, if the name of your MacOS harddrive shows up, 80 was the right number, if it does not show up, give 81 a try and so on.
  10. Once you’ve found your MacOS harddrive, the bootloader will require again some parameters. Simply enter -v -x as parameters and hit return (you may find more infos about these Darwin boot parameters here)
  11. if you experience the “still waiting for root device” issue, just reset your system and play with the AHCI mode for SATA inside of your BIOS
  12. Anyway: booting will take a long while – in our case about 5 minutes until the login screen appears
  13. login into your system

V. Saving your data

  1. Examine which data you require from your formerly known as almost native system
  2. plug your external harddrive (if you plan to migrate data to Windows, better have the external drive FAT32 formatted)
  3. Copy the files

VI. Final Words

Ooop duh. You got some more options here that we cannot cover at this time:

  1. You may revive this system with the hackint0sh ingredients (dsmos.kext and kexts for audio and video cards) – this will be a longer journey
  2. You may also get a real Mac. In this case Apple will suddenly love you…
  3. We recommend to give also Microsoft’s Vista a try. We feel like Vista Aero Glass effects are currently superior to Leopard’s effects. In this case Microsoft will love you (and us for suggesting this)…
  4. You could also go up the hill to the end and find Debian and ask yourself why it took so long to understand that unix is beautiful – in this case nobody will really love you but during installation you’ll find plenty of new friends in the Ubuntu community explaining you Debian…
  5. :-)

Anyway we hope that article helped you a tiny bit. If so you may also consider our sponsors, they also help you (and us of course)…

[MacOS] Install Leopard from .dmg Image to your System

“and first for something complete different”: Muzaq… coding or administrating system can’t do without gooood muzaq. Check our latest tunes here :-)

This time we’re gonna install Leopard from a .dmg image instead from DVD. The purpose is having a repair and recovery system by the hand in case you need it. My story is this: after having had a clean install of Leopard finished and having had applied all the updates, my MBP simply crashed again and again (two mouse pointers error – I found a solution in the meantime: that bug belongs to the Leopard Graphics Update – read it here howto fix it), since at that point I could not fix it, I then decided to reinstall. Something seemed fishy and would hopefully be gone after another fresh install. But as you expect: the same problem occurred again. I then decided to restore my previous tiger install and installed the Leopard DVD to a second partition. This way nothing can stop me, whereever I am, whatever does not work…

Ok what to do now?

I assume

  • You don’t have a bootcamp partition installed
  • means your harddrive is single partitioned
  • You got Tiger installed
  • You know the size of your harddrive (you can also find out in “Disk Utility”)

Now, let the game begin…

    1. Insert Leopard installation DVD into your drive
    2. Start “Disk Utility” to make a .dmg image of your installation DVD (see picture)
    3. click the Mac OS X Install DVD (highlight it) and choose New Image



  1. Choose Read as type of image and name it Mac OS X Install DVD(see picture)


  2. Wait forever (15-20minutes)
  3. Close Diskutility and
  4. Open terminal and enter:
    sudo diskutil resizeVolume disk0s2 139G "HFS+" "LeoInst" 10G
    (in this example the total harddrive size is 149GB = “139G + 10G”)
  5. This command resizes the first partition to 139GB and generates a second partition formated in “HFS+” with size of 10GB. The name of the second partition will be LeoInst (disk0s1 is in this case the EFI partition – see here, what makes the EFI partition so interesting, system partition starts at disk0s2 – that’s the partition we’re gonna resize and split into disk0s2 and disk0s3)
  6. After having executed this command successfully you need to reboot
  7. After reboot open “Disk Utility” again
  8. You should now see two partitition on your harddrive (see picture)


  9. Click on the second partition named “LeoInst”
  10. Click “Restore”
  11. As Source choose your Mac OS X Install DVD.dmg image (should be located on the desktop!)
  12. As destination drag and drop the second partition called “LeoInst”
  13. click “Restore”
  14. Wait about forever to have the DVD copied to your drive (again 15-20mins)


  15. Close Disk Utility
  16. Go to “System Preferences” and choose “Startup Disk”
  17. Choose your Mac OS X Install DVD (which is in fact now a partition) as start volume
  18. reboot system and install Leopard

Additional notes

These instructions are intended to be applied to genuine Apple systems rather than HackMacs. In my case I used my MacBook Pro. Because of the different .kexts to be applied to HackMacs this guide will not work for those systems! Be warned!