Reports suggest that PwnageTool has been disallowed from detecting an iPhone in DFU Mode on the new MacBooks, according to a Gizmodo report.
----- It's a given that each firmware update for the iPhone and iPod Touch will seal up exploits used by the Dev Team to 'Pwn' the devices, but nobody expected the new MacBooks to present a problem for would-be Jailbreakers. Users over at HowardForums and iPodTouchFans are reporting problems running the Pwnage tool on the new aluminum MacBooks, which don't seem to be able to recognize an iPhone or iPod Touch when it is booted into DFU mode, a vital requirement for jailbreaking.
It's a very specific problem, too the tool still runs, and users who have a pre-modified firmware created on another Mac or Windows machine are able to 'restore' their devices to a jailbroken state without any trouble. It's the creation of modified firmware, which is the central purpose of the Pwnage tool, that has been kneecapped. -----
Rather then a hardware change it seems more likely that a new build of iTunes, unique to the new MacBooks, is the culprit.
I have not been able to pwn with my new macbook.
I did 2 unpwned phones, with out the dfu mode when i tried installing the pwned firmware it errored.
however a already pwned phone no problems installing a pwned firmware.
Apologies, forgot to mention that even 2G iphones could not be unlocked with the QuickPwn or Pwnage through the iTunes 8.0.1. That is, perhaps, even more important to know.
This issue has been known for quite some time since the iTunes 8.0.1 has been released and it would not allow QuickPwn or Pwnage tools to jailbreak a 3G iPhone regardless. Only if older versions of iTunes were used, everything was well and as expected. I do own a new MacBook, but have not even tried to use Pwn tools with that - not so much because it is a new MacBook, but because I knew it would not work with iTunes 8.0.1. anyway. In short, I do not believe the issue discussed has anything to do with the new laptops as such, but with the current version of iTunes which was released well before the new MacBook and MacBookPro.
Os X build is different in new MB/MBP's, possibly due USB/nVidia chip change.
This might cause the "DFU problem" and then it's bug in new build.
Hopefully this is fixed in next Os X update :-)
actually, DFU mode works excellent through quickpwn. You'll have trouble with DFU mode through itunes as it may give you the common error 1600. If you do still get that error, switching between DFU and restore mode will eventually make it work, but the problem is with this new macbook, quickpwn wont recognize it in DFU....so that kinda gets ride of the entire thing eh
I had this very same problem using my older White Macbook to jailbreak / unlock my first generation iPhone. I found that connecting the iPhone to the Macbook thru the Dock (not USB cable direct to iPhone) allowed the computer to see the iPhone in DFU mode and successfully complete the Pwnage process.
If you don't have the dock and have your phone connected to the computer via the USB cable, simply doing an "Option-Restore" and choosing the Custom File you made with the Pwnage Tool will work as well. No need to put the phone in DFU mode.