Tag Archives: Restore

[Ableton] Repairing Defective ALS Files Manually

abletonlogoneu2

 

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

bildschirmfoto-2014-01-01-um-3-59-16-pm

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] iPhone 4 and the iOS 6.x firmwares

iphone4-pwnedAbstract

You are using an iPhone 4 and you coincidentally updated to iOS 6.1.3, which cannot be jailbroken at the moment. Since you saved the SHSH blobs you think you can restore by doing a replay APTicket attack with TinyUmbrella or Cydia. Sadly iTunes shows errors like 1600, 1601, 1602, 1604 etc.

If you have an iPhone 4s or iPhone5 you can stop reading here. This article will not be able to help you. The iDevices with an A5 CPU or later cannot be downgraded with replay attacks at the moment. Continue reading

[MacOS] Backup Chameleon Boot USB-Stick

1. Abstract

You have the situation that you installed Chameleon for security and compatibility purposes on an external USB-stick. For safety reasons you should consider making a backup. But all diskimaging (either Apple’s Diskutility, Carbon Copy Cloner or Super Duper) tools fail to create a proper backup since the bootblock is just not copied. So you end up with having to create a second usb-stick, but this takes time. So why not copying it? In the following article we’ll show you some basic steps to create a proper backup of your precious Chameleon bootable USB-Stick.

This session is not considered for newbies. You need to understand the steps and understand that you can completely destroy your system when you apply certain steps in a wrong way. The following steps comprise a forum threat on OSX86.net.

2. Walkthru: Backing up your Chameleon USB-Stick

Continue reading

[iPhone] Workarounds for Issues with PwnageTool/QuickPwn for Firmware 2.1

We read all over the net and found some solutions to the most common issues that occurred. If you are kinda conservative user, we’d recommend not to update to firmware 2.1 and wait until a PwnageTool and QuickPwn update has been released. Since the iPhone Dev Team is reacting very fast, this should take only some days.

Known Workarounds:

Error 1600 and Error 6: restore with stock firmware 2.1, then QuickPwn (you may then put into restore mode and install custom IPSW, but it’s not necessary- credits to “HomeGrown”).

Error 1600: when Pwnage asks, if already pwned your device, answer NO, no matter if you pwned if before or not (credits to “Maurofoto”)

Error 1600: let iTunes download firmware 2.1 again (you may delete it from the local folder if you already downloaded it via iTunes. Folder on a Mac: ~/Library/iTunes/iPhone Software Update/), then exit iTunes, prep a custom IPSW using Pwnage, delete the iTunes downloaded firmware from the above mentioned folder again and copy your custom IPSW to that folder, but name it exactly as the original firmware was named (credits to “Markat”)

[ID1082] Was the information provided above helpful?

View Results

Loading ... Loading ...