Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

thabandit

macrumors member
Original poster
Nov 10, 2007
34
0
anyone else heard this? its all over the net, surprised to see its not discussed here (unless i missed it).

anyway the new macbooks seem to have a new build of itunes, new hardware, etc. that does not recognize iphone/touch when its in DFU mode, so first time PWNage fails. i believe it still works if your phone has been pwnd already, then its just a restore in itunes to custom firmware.

any thoughts?
 
anyone else heard this? its all over the net, surprised to see its not discussed here (unless i missed it).

anyway the new macbooks seem to have a new build of itunes, new hardware, etc. that does not recognize iphone/touch when its in DFU mode, so first time PWNage fails. i believe it still works if your phone has been pwnd already, then its just a restore in itunes to custom firmware.

any thoughts?

umm.. dude... Dfu is a mode on the phone...not the computer.
 
umm.. dude... Dfu is a mode on the phone...not the computer.

"iphone/touch when its in DFU mode", ....um yea DUDE my wording may have been confusing, i mean itunes wont detect it when THE iphone or itouch is in DFU........
 
http://gizmodo.com/5074713/new-macbooks-disable-pwnage-tool-open-second-front-in-war-on-jailbreaking

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.

Though the hardware is where one sees the most conspicuous changes in the new MacBook, this problem most likely stems from a subtle software modification. It's not clear what specifically changed, but a new build of iTunes, unique to the new MacBooks, seems like a likely culprit. Of course, this news comes just after we're once again reminded of the App Store's awesome competition-busting rules. Your move, Dev Team.
 
The gizmodo post quoted above doesn't make any sense. If the computer can't recognize a phone in dfu mode, then you can't restore with a pwned image whether you created the image yourself or you already have one. Also, the pwnage software doesn't need DFU mode to create the ipsw file, only to flash it to the device.
 
The gizmodo post quoted above doesn't make any sense. If the computer can't recognize a phone in dfu mode, then you can't restore with a pwned image whether you created the image yourself or you already have one. Also, the pwnage software doesn't need DFU mode to create the ipsw file, only to flash it to the device.

I was confused too. I never let Pwnage flash my phone, I just let it create the ipsw and then use iTunes to flash. I have no plans to get a new Macbook Pro
 
if its just itunes no problem......just dfu + pwn first time in winpwn (via boot camp or fusion or parallels :p), then create another custom firmware in pwnage tool in osx and just option+restore in itunes.........:D
 
These machines can still use QuickPwn. It's only PwnageTool that has been affected.

I asked this question on the Dev Team's blog, and MuscleNerd confirmed it for me.

TheConfuzed1 said:
Do you guys have any input on the new Apple laptops incapacitating PwnageTool? Does this affect QuickPwn as well?

MuscleNerd said:
QuickPwn doesn't use iTunes at all, so any iTunes issues don't affect QuickPwn.

PwnageTool does use iTunes. I think though that any iTunes issues will probably be worked out by Apple long before they start affecting PwnageTool.
 
When I try quickPwn it just hangs on the last screen...Quickpwn is about to run on your phone.
 
I tried at least 10 times using either quickpwn, or pwnage tool to no avail last night. I read this thread and jumped on my windows machine and was done in minutes using quickpwn. I should have tried using bootcamp to see if it had something to do with the macbook itself or the version of itunes that it came with. I just hate running windows on my macbook, it just gets entirely too hot.

BTW, the windows machine had a fresh install of XP and I downloaded itunes to it directly from apple just before installing quickpwn.

Thanks for the heads up, thabandit.
 
I tried QuickPwn in vmFusion on my new MB. Will not go into DFU. Worked in Fusion on my Imac even though says not supported in virtual machines.
 
Not an iTunes thing

Since It's only on the new MBPs, It's definitely a hardware issue. Probably a USB thing or something, because QuickPwn doesnt use iTunes and that doesn't work either. I tried QuickPwn like 50 times before trying Pwnage Tool and actually getting an iTunes error from that, thus finding out about this stupid thing.

I want to hear from the dev team and see what they've come up with..

Anyway, no biggy. Just gonna use my friend's PC to jailbreak my iPhone.

This isn't getting much attention on blogs... :/
 
i cant get it to work on my new macbook pro either! ive done it so many times before and i was wondering what the hell was going on. dfu doesnt work in itunes and quickpwn stays stuck on 'preparing your phone for quickpwn'
 
i tried using quickpwn on my new macbook and that didnt work either. its not just the new pros. i then tried it on my friends older macbook and it worked just fine. he also has the latest version of itunes installed. it just freezes up right after putting it in dfu mode and itunes comes up with error 2001, then you have to soft reset your iphone.
 
I was able to use QuickPwn on my Aluminum MacBook. What I did was when it got to the part where you put it into DFu mode I never released to lock button making it go to restore mode( with the usb cord showing). Then just let it go. Pwned indeed.
 
Here is an ineteresting Note:

My Aluminum IMAC has had issues with quick pwning 2.1 previously. On 5 different devices, FIVE, it failed the first time.

After a Fail, I restore the phone or ipod through iTunes, then try pwn again and it works, always on the second try.

Could there be some trace of this hardware or software config in the Aluminum iMac?
 
I've tried like 5 times already to get quickpwn to work using my new MB, but it just won't work. No DFU mode whatsoever.

Anyone have a solution?
 
I was able to use QuickPwn on my Aluminum MacBook. What I did was when it got to the part where you put it into DFu mode I never released to lock button making it go to restore mode( with the usb cord showing). Then just let it go. Pwned indeed.

Can you please elaborate on what you did to get it to work? I tried holding power + home button, without letting go of power button when quickpwn prompts me to, and it goes into restore mode (with usb/itunes logo). Then what should I do? My Quickpwn app just hangs at the last screen (where it's getting ready to install quickpwn onto my iphone 3g) and that's it...
 
When quickpwn hangs and says about to run on your iPhone, I unplug then plug back in my phone. Hold both buttons untill it goes to restore mode( USB cable in pic) then Quickpwn takes over.
 
When quickpwn hangs and says about to run on your iPhone, I unplug then plug back in my phone. Hold both buttons untill it goes to restore mode( USB cable in pic) then Quickpwn takes over.

Will this work when jailbreaking a phone for the first time? Or only when updating an already jailbroken phone?
 
Since It's only on the new MBPs, It's definitely a hardware issue. Probably a USB thing or something, because QuickPwn doesnt use iTunes and that doesn't work either. I tried QuickPwn like 50 times before trying Pwnage Tool and actually getting an iTunes error from that, thus finding out about this stupid thing.

I want to hear from the dev team and see what they've come up with..

Anyway, no biggy. Just gonna use my friend's PC to jailbreak my iPhone.

This isn't getting much attention on blogs... :/

It's not a hardware issue. I got the new MB/MBP Mac OS X disc to install on my ver. 1 Air to see if I could get four-finger multitouch support to work and DFU mode doesn't work anymore with the machine. Comparing the new MB/MBP Mac OS X ver. to the standard 10.5.5 on my iMac reveals that the MobileDevice framework on the new machines is newer (3.3.0 vs 3.2.2). I would imagine replacing it by the older version may work to fix the problem.

Edit: I did just try replacing MobileDevice.framework with the older version but that doesn't work. There most certainly is something else that'll need to be hacked/changed. But it's definitely a software issue. DFU worked fine with my iPhone connected to my MBA before I used the AluMB install.
 
i got it working.

i went to walmart and bought a 10 dollar 4 port usb hub. it worked fine just plugging the phone into that.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.