What steps will reproduce the problem? 1. Stop iTunes Helper 2. Start iNdependence 3. Click Activate Phone

What is the expected output? What do you see instead? Expected would be an activation. Instead, it says Waiting for Jailbreak, the iPhone restarts in recovery mode, and iNdependence immediately crashes out. Every time I try to restart it, it crashes again. I then have to recover the iPhone with iTunes, so iNdependence will start. It happens every time I try to activate.

What version of the product are you using? On what operating system? 1.4 beta 5, Leopard

Please provide any additional information below.

I was able to get around the problem, only by using a second Mac. No idea what the problem is there.

1. Independence working perfectly.
2. Installed iPhone sdk.
3. Independence crashes every time the iPhone is in recovery mode.

The sdk was the only thing I installed in the period between independence working and not working.

My eventual workaround was to do. Fresh install of 10.5 on an external disk, update iTunes to the latest version, load 1.1.4 on the iPhone using iTunes, and then run independence. Ran without any errors on the clean install.

Hopefully this helps others out.

Interesting - I did indeed install the iPhone SDK on that computer earlier, so that could really be the issue. I wonder how I can completely uninstall it?

I tried running the uninstall-devtools script, but it didn't seem to help at all. I can't seem to find any running processes that would cause this. I guess I'll keep looking. Any tips from the devs?

I have noticed the same issue. I'm guessing the SDK installed new versions of some shared library that is used by libPhoneInteraction, and thus libPhoneInteraction needs to be rebuilt, but I'm not familiar enough with the Independence source (or the SDK) to confirm my speculation.

Thread 0 Crashed: 0 ??? 0x3c3a71d7 0 + 1010463191 1 libPhoneInteraction.dylib 0x00022700 PhoneInteraction::jailbreak113StageTwo(am_recovery_device*) + 76 2 libPhoneInteraction.dylib 0x00022c9c PhoneInteraction::recoveryConnectNotificationCallback(am_recovery_device*) + 34 ...

Also, to clarify, the crash is a segfault (EXC_BAD_ACCESS) with code KERN_INVALID_ADDRESS -- maybe making a system call that doesn't exist? See attached crash log.