PwnageTool 2.0.2 for iPhone starts sparkling – then stops

by Alex Zaharov-Reutt

Saturday, 09 August 2008

Page 1 of 2 ! The update for PwnageTool 2.0.2 to jailbreak iPhone 2G and 3G models, and unlock the iPhone 2G, was moved to the iPhone Dev Team’s “sparkle update system” when a serious bug was noticed – and the update removed. But the sparkling will start happening once more in a few hours! If you’ve been desperately waiting for the PwnageTool 2.0.2 to arrive so you could update your iPhone OS from 2.0 to the new 2.0.1, there’s good news and bad news. The good news is that the update is 99.99999% complete, and was deemed so complete that it was added to the iPhone Dev Team’s “sparkle update system” which allowed existing PwnageTool 2.0.1 users to quickly and easily update to the new version. The new version would then take the iPhone 2G or 3G OS 2.0.1 (of which there are two separate versions) and would change Apple’s .IPSW files (the extension of the iPhone OS file which is actually a zip file) to the iPhone Dev Team’s modified versions, ready for upload onto whichever iPhones or iPod Touches you happen to own. This was announced in a thread at the iPhone Dev Team’s blog called “It is sparkling!” – but only a short time later this blog post was edited to read “It isn’t sparkling – yet”. Which is, of course, the bad news. Many people had expected the "Friday" timeframe (Northern Hemisphere) to mean Friday, but when it comes to hacking, and the possibility of creating iBricks, the iPhone Dev Team simply doesn't want to take any chances, something that is a very sensible stance. After all, the moaning and groaning from users would be endless, so it obviously was a better idea to just let people moan for a few more hours instead. As for what actually happened, it's probably best to let the iPhone Dev Team explain it themselves: “Just as we moved PwnageTool to the sparkle update system (just after making this original post) one of our team noticed a nasty bug that only happened on his intel iMac running Leopard, we held off and tried to fix it and get it out but it still isn’t fixed. “This isn’t anything to do with 2.0.1 being unhackable or other kooky idea, so don’t worry about that, it is a bug with the building of the final ipsw, which is kinda fundamental and we were worried that it would appear on similar systems, the bug wouldn’t have caused any damage to systems, but it would have been a support nightmare, and it just wouldn’t work.” Continued on page 2. << First page <   1 2 Next page > Last page - Post your comment >>

 

< Next story in category		Previous story in the category >

Visitors last 30 days Suscribers

904,266 13,751