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)

Apple has just released Mac OS X Leopard 10.5.7, and incremental update to their current desktop and laptop operating system (widely expected to be supplanted later this year by Mac OS X 10.6 Snow Leopard).

Why does this matter for iPhone users? When iPhone 3.0 Beta 4 arrived, note syncing — which worked fine under Betas 1-3 and OS X Leopard 10.5.6 — was suddenly gone, replaced with a statement saying simply that OS X Leopard 10.5.7 would be required for note syncing from then on. Beta 5 arrived with nothing but the same warning. Hopefully with 10.5.7 now available, note sync — still something of a sore spot having taken 2 years to deliver — will be restored.

Apple has also been known to sneak other iPhone friendly features, like Google syncing, into previous updates — and not so friendly bugs into others that made Jailbreaking more difficult — so we always keep our fingers just a tiny bit crossed.

Mac users, let us know if you find anything!

(Thanks daveizzle and sil3ntrid3r11 )

iPhone 3.0 Beta 4 required iTunes 8.2 Pre-Release to install, and it looks like iTunes 8.2 Pre-Release requires… Mac OS Leopard 10.5.7 in order to sync notes now. Which, of course, is not yet available.

Previous iPhone 3.0 Betas have synced perfectly well under the current Mac OS release, 10.5.6.

A sign of 10.5.7′s immanent arrival? Perhaps. A more interesting question is what’s changed in note sync to require it where previous betas did not?

(via daveizzle on Twitter)