All Articles Tagged Dev Team

Jeremy already passed along the warning from the iPhone Dev-Team on iTunes 8.2. In case you missed it, they told jailbreakers and potential jailbreakers NOT to install Apple’s just-released iTunes update.

According to their latest Dev-Team Blog post, the reason seems to be:

It breaks your ability to use QuickPwn, PwnageTool, and iPhone Tunneling Suite (ssh over usb). We don’t think this is a deliberate breakage of these tools. It’s just that Apple has updated a low-level USB protocol that normally only Apple cares about (but jailbreakers care about).

Is Dev-Team working on a fix? Youbetcha, but they don’t want to release anything further until iPhone OS 3.0 is final. This may annoy people who have the 3.0 beta, but legit developers probably have more pressing concerns than jailbreaking at the moment, and why would the Dev-Team waste their energy and tip their hand to Apple when the betas will likely keep changing every couple of weeks before release anyway?

Of course, the blogsphere now has another concern, since last week’s announcement that the Palm Pre syncs with iTunes, likely by faking Apple’s USB protocols to disguise itself as an iPod (see Daring Fireball’s take on this as well). There have been two pre-release versions of iTunes 8.2, going back over a month, but the obvious question still becomes: will the iTunes 8.2 final release also effect the Palm Pre sync?

Dev-Team thinks it’s possible:

It may actually break Palm Pre’s connection to the device (please give us feedback on this).

We think Palm’s Jon Rubinstein — who used to head the iPod division at Apple — may just have compromising pictures of the iPhone taken during it’s “bachelor” party the night before Macworld 2007 … We mean, it’s got to be something, right?

Today Apple officially released the latest version of iTunes (8.2). Anyone who is familiar with jailbreaking should be well aware that now is a time to wonder, will the cat and mouse game continue? It seems like it has but @MuscleNerd claims it is unintentional on Apple’s part.

Today’s iTunes 8.2 update changes the way your computer talks to the device. This affects things like QuickPwn and PwnageTool when they try to identify what’s connected. Also, ssh over usb breaks due to same reasons. Fixes are in the works but for now avoid 8.2

So if you are planning on jailbreaking anytime in the near future, be sure to avoid this latest version of iTunes until the fix is made available to the public.

Stay tuned as TiPb will bring you the latest updates as they become available.

Good news for Mac OS X-based Jailbreakers! After having to resort to using powered USB hubs or patching in older versions of files to work around a bug in 10.5.6 that prevented DFU mode from being recognized, the iPhone Dev-Team dropped a note a Twitter to give 10.5.7 the all-clear:

The new 10.5.7 Leopard update is safe. In fact it’s more jailbreak-friendly than 10.5.6, since the DFU-mode bug is gone.

So no nasty cat-and-mouse-game shenanigans this time around, and even a slight improvement over the previous — unintentional — round.

Only one thing left — figure out what to do with all those now-redundant USB hubs…

(Via Jamesus)

The iPhone Dev-Team has posted a few words regarding Jailbreaking the 3.0 software:

Because there are so many beta releases, we couldn’t possible refine, test, and release both PwnageTool and QuickPwn for each of them. That’s why we’re waiting until the final release. You may have seen other “hijacked” versions of QuickPwn out there, but all of them are buggy, none of them work on OSX, and almost everyone who uses them reverts back to 2.2.1 (because none of the useful jailbroken apps (Qik, Cycorder, and others) work on 3.0 yet).

Now this does not mean you currently can not Jailbreak 3.0 because you can, it’s just that the Dev-Teams software is not fine-tuned for the iPhone beta software. If you do decide to Jailbreak the 3.0 beta you will run into some issues. The biggest issue, as stated above, being a lot of the applications available via Cydia will not be compatible with 3.0. It is also important to note that if you ever want to unlock your iPhone 3G, you need to avoid the 3.0 software altogether unless and until the Dev-Team provides a safe jailbreak path.

So our advice to the Jailbreakers of the world: have some patience. When the final build of 3.0 drops sometime this summer you will be able to Jailbreak your iPhone 3G.

(The only way Apple could prevent a Jailbreak does not rest within the software, rather the hardware. As for Jailbreaking the next generation of iPhone, only time will tell, we are sure Apple will make it interesting…)

Hackers vs. hackers. FreeHacks vs. AdHacks vs. PaidHacks. Jeremy covered the state of iPhone piracy yesterday, and while the argument over apps rages, the Jailbreak and potential unlock sitch could become just as confusing. Witness the Dev Team’s Cat. Bag. Mouse. post which warns against using “unofficial” (according to the Dev Team) versions of, er, the unofficial (according to Apple) iPhone jailbreaking QuickPwn:

THE MOST IMPORTANT THING ABOUT THE UNOFFICIAL QUICKPWN RELEASES IS THAT IF YOU USE THEM, YOU WILL KILL YELLOWSN0W, POSSIBLY FOREVER. That’s because QuickPwn, by its very nature, requires you to already have accepted Apple’s official IPSW, along with its baseband update. If you do that, you will (possibly forever) lose your ability to software-unlock your iPhone 3G.

As to what the Dev Team itself is up to… check out the rest of their post.

Anytime there’s an update — or in this case, even a new beta firmware for developers to test out months ahead of an update — the iPhone Dev Team reminds Jailbreak users, especially those running unlocked using YellowSn0w to stop, breathe, and wait for the “all clear” before updating.

In this case, the Dev Team says:

If you find yourself with access to the 3G IPSW for 3.0 via the iPhone Dev Center program, and you are using yellowsn0w, do not update or restore to that official IPSW. You will lose yellowsn0w and find yourself unable to revert the baseband to get it back.

And for those wondering, yes the 3.0 OS is jailbreakable on all devices. It’s just those using 3G yellowsn0w that have to show some restraint and wait for PwnageTool to create a custom IPSW that avoids the baseband update.

No big surprise they can crack the 3.0 firmware, though Apple might still throw some curves their way in future betas or the final release. We’re guessing the true next step in the cat and mouse game will be iPhone 2,1 hardware, which could prove as tricky, if not trickier, than the iPod touch 2,1 which took quite a while to get to RedSn0w…

(Thanks to everyone that sent this in!)

Today is a good day to be a iPod touch 2G owner. Particularly if you have been waiting for an untethered jailbreak method to appear. The Dev Team put up a post late last night on their blog:

The iPod Touch 2G is now another member of the “pwned for life” family. It has a fatal flaw in its bootrom that means you will always be able to pwn these devices no matter what firmware updates come along. This is the full, untethered jailbreak, something that iPod Touch 2G users have not had before today.

For more information about this iPod touch 2G jailbreak and to download the software you’ll need, visit here. If any of you are feeling adventurous, be sure to let us know how it goes!

[Via blog.iphone-dev.org]

The illustri-notorious Dev Team has blogged about Jailbreaking iPhone OS 2.2.1, released by Apple earlier this week.

Simple version: You can now Jailbreak, if you haven’t already upgraded to 2.2.1 via iTunes, are using a Mac, aren’t affected by the OS X 10.6 DFU-mode bug, and — if you want to keep using yellowSn0w for unlock — are happy to spin your own custom firmware.

Complex version: involves closing the barn door — see here.

(For community-based jailbreaking advice and support, please check out our Jailbreak Central Forum)

Hopefully an easier solution will surface when the Dev Team has spent more time hacking away at iPhone OS 2.2.1. Until then, the cat and mouse game continues!

So if you don’t live under a rock you would have noticed that Apple released a iPhone/iPhone 3G firmware update this past Tuesday. TiPb then warned all of you jailbreakers/unlockers out there not to proceed with updating your firmware… Judging from the comments, some of you took heed to our warning, while others were not so lucky.

To get a better understanding of what is going on with this latest Apple firmware and why you should not update just yet, be sure to check out the video above from iPhone Dev Team member, musclenerd.

[Via blog.iphone-dev.org]

So if you are a Twitter user, and follow the Dev Team (@iphone_dev), you may have noticed an interesting early hour post. So it begins, all of the crazy rumors on what this new code word means. Rumors and speculation all set aside, our very own Rene, had a very good idea… iPod touch 2G Jailbreak perhaps?

It seemed like the iPod touch was being left behind ever since iPhone 3G was released. Most likely due to the Dev Team putting all of their effort into a iPhone 3G unlock. Which is very much appreciated and a good thing for all of you iPhone owners out there. For you iPod Touch owners out there, we’ve heard rumblings that redsn0w will drop on or around January 30. So sit tight for a few more weeks.

For more information about @redsn0w be sure to follow it via Twitter!

The cat and mouse game continues on!

[Thanks for the tips - Scott, jamesus, and Rene!]