Stupidly, I restored the stock 2.2.1 firmware, and now my iPhone has been deactivated. Restoring custom 2.2.1 firmware with the phone in *true* DFU mode results in the dreaded 1600 or 21 errors.

Is this because I'm using 10.5.6 on a MacBook Pro (late 2008)?

I've tried QuickPwn as well, but with my iPhone in DFU mode, it does nothing when trying to inject the custom firmware.

Am I struggling with the dreaded DFU problem in 10.5.6? Is there no workaround besides installing the older kexts?

OK, I installed the USB kexts from 10.5.4, and QuickPwn was able to do its work. Then (again stupidly), I option-restored the stock firmware from 2.2.1, and now I'm back to square one, except that things are worse: now QuickPwn tells me:

"The firmware installed on your iPhone is not supported by Quickpwn"

How can this be?

I'm virtually certain that 2.2.1 was restored by iTunes!!

What do I need to do to be able to get QP working again?

Hi

May be a stupid question but you r using the correct version of Quickpwn for 2.2.1 firmware?

QuickPwn 2.2.5

Originally Posted by n350z

Hi

May be a stupid question but you r using the correct version of Quickpwn for 2.2.1 firmware?

QuickPwn 2.2.5

Yeah, I'm using 2.2.5. That should work with all known firmware, right?

Originally Posted by n350z

May be a stupid question but you r using the correct version of Quickpwn for 2.2.1 firmware?

What happened is that I accidentally restored the 2.1 firmware instead of 2.2.1 (I discovered this because the Windows version of QuickPwn gives more informative error messages than the Mac version!). This complicated matters considerably because I had to hunt down QuickPwn 1.1. It was able to jailbreak my phone, but then how to update to firmware 2.2.1? I thought I could do an option-restore of custom firmware 2.2.1, but I kept getting the dreaded 1600 error. Eventually I did a stock restore of 2.2.1, then QuickPwn 2.2.5. But I found that even after that, I couldn't do a DFU or a recovery restore of custom firmware 2.2.1 created by PwnageTool 2.2.5. I kept getting an error 2 or 17 (I think).

Any idea why?

Frankly, restoring firmware and updating has become several orders of magnitude more complicated with iTunes 8, OS X 10.5.6, and unibody MacBook Pros.

I have a MacBook Pro (late 2008) running 10.5.6. I've found that even after installing IOUSBFamily-315.4.1.pkg, I cannot successfully option-restore custom firmware generated by PwnageTool 2.2.5. I can put my iPhone in DFU mode and do a restore of stock firmware and then run QuickPwn 2.2.5, but trying to option-restore custom firmware results in the dreaded errors 1600 or 27. Just thought people should know

i have a problem i dont know how to find the bootloader v39.bin or how to download it