So it seems Apple isn’t the only one who can maintain break-neck code drop schedules. The iPhoneDev Team is back already with the latest version of their pineapple-iconed Pwange tool for jailbreaking iPhone 3G and iPod Touch, and jailbreaking and unlocking the original iPhone 2G.
Version 2.0.2 for use with 2.0.1 may be a little confusing for some, so maybe a better numbering system can be worked out there, but this update also includes the beta Installer.app 4, as well as Cydia.
Want it? rev up your Pwnage’s sparkle-powered Software Update (what a world we live in…) or head on over to the iPhoneDev Team site.
And, as always, whenever performing ninja-like acts on your hardware, proceed with caution.
(Via TUAW)
This is fun. It’s like a game of cat and mouse between Apple firmware and the jailbreaking community, Apple launches an update and the iPhone-dev team works feverishly to jailbreak said update. This time, they are said to be putting the finishing touches on PwnageTool 2.0.2 which will be able to jailbreak the “snappier” 2.0.1.
Excited much? Well, there still won’t be Installer.app because Installer 4 isn’t ready for the primetime yet but a new version of Cydia will be there so you can still get some apps. There still is a lot of catching up to do on developing jailbroken apps and it still won’t unlock the iPhone 3G, but all in due time. We’ll follow up with a link to PwnageTool 2.0.2 when it is released.
ReadVia
We told you when iPhone 2.0.1 dropped, we asked you how 2.0.1 was doing for you? And we warned iPwners to stay away. Turns out people running on Vodafone (in the 10 countries they currently supply) might want to consider staying away for now as well. TUAW reports on the problems:
Specifically, users who paid to have their 3G iPhones unlocked by Vodafone* are unable to re-connect to the service following the update, and instead receive a “0xE8000001″ error message. How helpful. It seems to happen on both Windows and Mac OS X.
Another problem, via iPhoneAtlas, occurs when users try to upgrade when in the radio-silent Airplane Mode:
Having Airplane mode turned on can result in a non-functional phone when the update is applied. You may receive the error message: “Information for activation cannot be obtained from the iPhone” Fortunately, you can disable Airplane mode from the emergency screen if your iPhone is put into an inactivated state by a problematic update.
If you do get 2.0.1 installed (and I confess, mine installed quickly and flawlessly), what will you find under the hood?
Apple said “bug fixes”, which seems to include fixes to sluggish interface animations/transitions and app launches in general (especially Contacts and SMS). Some are claiming faster backups, more stable App Store app behavior, and better or more accurate cell strength and GPS placement. And others have even joked that, like a placebo, we’ll see any update as a general purpose cure-all for what’s been aggravating us.
Have you noticed any specific, repeatable improvements? Keep pounding away and let us know what you find!
So it’s been a day since 2.0.1 was made available and we at TiPb would like to know how it’s been running on your iPhone. Did this bug-fixer of an update actually fix any bugs? Or are we all getting suckered into believing that the update has made things snappier? Pains in the update process? Backups faster? Apps Crashing? Or are things just less sucky? Maybe you completely avoided the update..anything and everything, we want to know!
Personally, things have “felt” a little bit smoother. Contacts load noticeably quicker but my SMS is still a good couple of seconds too long. No crashes to report yet but I did have one ginormously big hiccup after updating: the mail app crashed on launch. I had to completely restore and set up my iPhone as a new iPhone which was more than mildly annoying, to put it lightly. So other than that, YAY 2.0.1. Woot.
So TiPb faithful, how is 2.0.1 treating you?
While most of us have installed the 2.0.1 update (or, ahem, are still waiting for a backup we started last night to finish so we can install it), there’s a key group of folks that should stay away: Jailbreakers and unlockers. As is always the case when a new update comes out, our advice to these users is to wait and see how the iPhone hacking community responds. Right now, according to iphone-dev [via Engadget Mobile], they appear to be responding with a teensy bit of bravado:
We don’t see any major problems with the release that Apple made, but we have not released an update for PwnageTool for it as yet and therefore PwnageTool 2.0.1 will currently not work!
Their advice is pretty sound and mirrors ours: if you never intend on leaving your carrier, feel free to update away whenever if you don’t mind losing jailbroken apps. If you do (or already have), stay the heck away from updates until things clear up.
What about you? Are you law-abiding and currently enjoying a bug-free existence? Jailbreaker glancing longingly at 2.0.1’s reportedly better keyboard response? Unlocker living on the periphery of the cell phone ‘Verse, staring into the black and in danger of becoming a Reaver? Let us know!
Fire up iTunes, hit the Update button, and BOOM! 2.0.1 is live and in prime time. Actually, in 250MB of what Apple’s always super-verbose product details says “includes: big fixes”.
I’m downloading it as I type this, but Engadget’s already gotten their mitts on it, and say things feel snappier.
Have you gotten it yet? Getting it now? Gonna wait and look for error reports first?
Whenever you get your 2.0.1 on, please drop us a note and let us know how it’s working (or not!) for you.
And Apple — thanks much! Now about that 2.1…
Given the general sluggishness and overall er… crashing issues many — including us — have raised about the new iPhone 2.0 update, it can’t come as any surprise that Apple is prepping a 2.0.1.
But could we already have confirmation? Intrepid Boy Genius Reporters scoured their server logs and came across:
[S]ome interesting build numbers for the iPhone and iPhone 3G. It appears that AT&T and Apple are testing iPhone device software version 2.0.1, builds 5B101 (iPhone) and 5B103 (iPhone 3G). Although we are not certain of much more information than this little bit, we do know that testing began prior to the launch of device software 2.0 and the iPhone 3G on July 11th. We have also narrowed down the known test users to the San Francisco (40 mins from Cupertino) and Atlanta (HQ of AT&T Mobility) areas. Hmm.
Doubtless it will include Apple’s usually opaque description along the lines of “Fixes compatibility and general stability”. Fortunately, this time around that’s just what we need!
Read
