Apple’s New Macbooks Declaring War On Jailbreakers?

What a bizarre turn of events we have here… It seems that everyone who has a new Macbook, Macbook Pr, or Macbook Air and wants to jailbreak there iPhone is in for a surprise. You will be unable to do so. New Macbook owners will notice an iPhone or iPod Touch will not be detected when it is booted into DFU mode, which we all know is key for jailbreaking.
At first I thought that Apple had to make some sort of hardware change within their new Macbooks. Then Dieter politely gave me the version of iTunes running on his new Macbook, 8.0.1 (12). Now the version that everyone else has on their older Macs is version 8.0.1 (11). Very interesting. If it’s a simple software change that would only slow down the Dev Team for a few days until a new work-around is found.
Now keep in mind this is not the first attempt by Apple to slow down jailbreaking. A few months back they attempted a counter strike when firmware 2.1 dropped, only to have the Dev Team find a solutions merely days later.
On a side note, I’ve seen a lot of people having issues with jailbreaking lately, please keep in mind if you do not have a new Macbook, you still can jailbreak. There was a rumor going around on the forums with members concerned they can not jailbreak. This is simply not true.
(Thanks to Landon for the tip!)
[Note: Anyone not using a new Macbook, but looking for help Jailbreaking, check out Jeremy's awesome guides for Mac, Windows, and iPhone 2G, and if you need extra help, drop by our Jailbreak Forum! - Rene]

















November 4th, 2008 at 4:11 pm
pretty smart by Apple. But software is no match for the devteam
November 4th, 2008 at 4:15 pm
Pew Pew! HA!
November 4th, 2008 at 4:44 pm
This sucks. I was planning on jailbreaking my iPhone 3G soon so I could get push notifications for apps and background apps. I was going to get a MacBook Pro too but I guess I’ll just wait for the MacBook Pro until the devteam comes out with a work around this minor problem.
November 4th, 2008 at 9:22 pm
@endrit…. obviously you are ignorant
November 4th, 2008 at 11:12 pm
^^^^ +1 Maybe he loves his clamshell too much to upgrade! I know I love them, with all 7 colors of my heart.
November 5th, 2008 at 11:42 am
LOL PEW PEW!
November 5th, 2008 at 11:56 am
Apple is really REALLY trying to take over from Microsoft as the evil empire.
November 5th, 2008 at 9:47 pm
Won’t this affect genuine iPhone software being recovered in cases of major problems/crashes?
I’ve certainly restored my iPhone a few times.
November 8th, 2008 at 10:15 am
Well I bought a 13.3″ Macbook and jailbroke my 3g iphone yesterday, im running 8.0.1 (12) I didnt even have an issue. Maybe i will try it again on my wife’s iphone and see what happens…
November 8th, 2008 at 9:57 pm
they must want to sell less notebooks
December 6th, 2008 at 11:48 am
I only find the problem to exist if you try to enter DFU mode with the iPhone connected & iTunes open. I was able to enter DFU mode & then connect up to load my new 2.2 pwnage ipsw file just fine.
December 6th, 2008 at 7:55 pm
to clarify – I could get into DFU mode fine with the original iPhone in the above comment. with a 3G iPhone I’m unable to get into DFU mode regardless of it being plugged into iTunes or not
December 22nd, 2008 at 2:02 pm
if you have bootcamp running isn’t it possible to perform the unlock in windows on your macbook aluminum?
January 17th, 2009 at 6:40 pm
I have a late 2008 macbook pro. If i jailbreak my iphone 3g on a different machine, and also unlock it, can i then go back to using it in the future with my macbook pro. Or will i still have problems plugging it into my macbook pro once it is jailbroken and unlocked? thanks…
March 20th, 2009 at 12:31 am
Is there a solution yet to Jailbreaking on the new MacBook Pros?! I have go idea when I am supposed to plug and unplug the USB cable multile times from the unlocking 3G on new Pros. Can you please clear up directions? Thank you
George
May 26th, 2009 at 2:52 pm
If i have a 1G 4gb iphone what is the most recommended firmware to install? Can i install 2.2.1?