(we also captured the date of the SHA1 of the above image for historical purposes here and here)
Why did we not release the jailbreak two weeks ago when the above image was captured and hashed? There are many reasons, mostly resource-related:
1. We don’t want to have to release a new version of PwnageTool and QuickPwn for every beta release. Last time around during the 2.0 beta period, there were nine (9!) Apple releases, spaced within a few weeks of each other.
2. There are unresolved problems that we’re still working on. It’s currently impossible to get the 3.0 firmware to talk to baseband 02.28 where yellowsn0w lives, for instance.
3. We don’t want to have to support everyone who wants to back down from the betas…because the betas are, well, buggy.
4. It’s silly to play cat&mouse with Apple during a beta period, when relatively few people are willing to actually use the beta software in their everyday lives. There are ways Apple can tighten the screws, and we’d rather not burn methods just for a beta release.
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.
They say that imitation is the sincerest form of flattery, and so perhaps we should be flattered that so many ad-supported sites are now using our own tools to create unofficial jailbreaks (QuickPwn in particular is so easily adapted from one release to the next that it’s reduced to a handful of binary pattern searches in a good hex editor). But please don’t expect support for them on this blog, because we’re actually busy with the hard part of the 3.0 jailbreak (the 02.28 incompatibility and the new compressed ramdisk they’re using).
Saturday, April 25, 2009
Beta O'Clock
Today at exactly 2 minutes past Beta O’Clock we are releasing a beta version of redsn0w. The release hopes to simplify the jailbreaking of your iPod touch 2G.
redsn0w is currently in beta as it relies on the user running it from the command line, but this new redsn0w functionality is being added into our GUI applications.
If you are not fully confident with using the command line, then hold off for those simpler tools that will be released sometime soon.
Related links
* iPod Touch 2G: Hi, welcome to the jailbreak family
* 0x24000 Segment Overflow
Credits
implementation ⓒ2009 iPhone Dev Team
vulnerability: pod2g, MuscleNerd
exploit: planetbeing, CPICH, posixninja, chronic, ius
Legal
This work is copyrighted with all rights reserved. Modification or redistribution without written consent is expressly prohibited.
UPDATE
The redsn0w site shows the latest release version, it is currently at v0.3.
2 weeks ago
Comments
Cat. Bag. Mouse.
Well, the cat is out of the bag. The 3.0 firmware from Apple can be jailbroken, and there are now sites out there giving you that jailbreak (after you sort through various ads and browser popups, etc).
Of course it’s not really a surprise that it can be jailbroken. One of the nicest things about the jailbreaking iPhones and iPod Touches nowadays is that once a given device can be jailbroken, it can always be jailbroken. The exploits we’re forced to resort to are down at the hardware level, where nothing can be done about them via software. That’s why within a day or two of 3.0 beta1’s release we were able to snap this screenshot of a jailbroken system:
Today at exactly 2 minutes past Beta O’Clock we are releasing a beta version of redsn0w. The release hopes to simplify the jailbreaking of your iPod touch 2G.
redsn0w is currently in beta as it relies on the user running it from the command line, but this new redsn0w functionality is being added into our GUI applications.
If you are not fully confident with using the command line, then hold off for those simpler tools that will be released sometime soon.
Related links
* iPod Touch 2G: Hi, welcome to the jailbreak family
* 0x24000 Segment Overflow
Credits
implementation ⓒ2009 iPhone Dev Team
vulnerability: pod2g, MuscleNerd
exploit: planetbeing, CPICH, posixninja, chronic, ius
Legal
This work is copyrighted with all rights reserved. Modification or redistribution without written consent is expressly prohibited.
UPDATE
The redsn0w site shows the latest release version, it is currently at v0.3.
2 weeks ago
Comments
Cat. Bag. Mouse.
Well, the cat is out of the bag. The 3.0 firmware from Apple can be jailbroken, and there are now sites out there giving you that jailbreak (after you sort through various ads and browser popups, etc).
Of course it’s not really a surprise that it can be jailbroken. One of the nicest things about the jailbreaking iPhones and iPod Touches nowadays is that once a given device can be jailbroken, it can always be jailbroken. The exploits we’re forced to resort to are down at the hardware level, where nothing can be done about them via software. That’s why within a day or two of 3.0 beta1’s release we were able to snap this screenshot of a jailbroken system:
Subscribe to:
Posts (Atom)