The drama surrounding the SHAtter exploit continues. A Dutch dev threatened to leak the code last week, and even though that threat was thought to have subsided, someone apparently did go ahead and leak SHAtter Wednesday. This led to a Twitter fight between p0sixninja and MuscleNerd, whom p0six had accused of being the leaker. Musclenerd denies this, but according to p0sixninja, SHAtter has been burned.

The SHAtter exploit was originally developed by onetime Chronic-Dev hacker pod2g. A weakness in the S5L8930 bootrom of A4-based devices (iPhone 4, iPad, Apple TV 2G, iPod touch 4G). It was originally intended for the 10.10.10 (10th October 2010) release of greenpois0n before Geohot came out of nowhere with the limera1n jailbreak for all iOS devices. SHAtter was held in reserve for a future jailbreak to conserve exploits in the ongoing cat-and-mouse game with Apple.

At this point, all we know for sure is that for unknown reasons, the code was potentially released by an unknown party Wednesday. It’s unclear at this time if this was the genuine SHAtter or a fake designed to throw Apple off the scent, as people who claim to have the leaked version are reporting trouble getting it to compile. However, Apple should be able to figure out pretty quickly if it is genuine or not. Meanwhile, in a furious back-and-forth on Twitter (blowing up the phones of all their followers all Wednesday afternoon), p0sixninja accused MuscleNerd of the iPhone Dev-Team of being responsible for leaking the exploit. MuscleNerd rejected the accusation, explaining that it would make no sense for him to do so as he will need to be able to jailbreak the iPhone 5 in order to unlock it. MuscleNerd also noted that there were 15 to 20 others in the room when pod2g showed his SHAtter code for the first time, so the pool of suspects is large.

If SHAtter is truly burned, it’s potentially not catastrophic, as p0sixninja says another “untether bootrom exploit” is supposedly on the way. However, if we’ve lost a valuable tool due to some personal drama among devs, it’s a sad statement about the jailbreaking community.

Source: Twitter

The Dev-Team is warning about a potential issue with ultrasn0w for iOS 4.2.1 on iPhones with the 06.15.00 baseband. An increasing number of users with that version of the baseband software are reportedly losing GPS functionality when they unlock their device. The blog post says they are looking for the root cause but haven’t found it yet, and notes that it’s not a problem for all or even most users with that baseband. Still, to be on the safe side, they’re suggesting people should just not expect GPS to work if they want to unlock iPhones with the 06.15.00 baseband using ultrasn0w:

Source: Dev-Team Blog

redsn0w 0.9.6beta4 was just recently announced, and beta5 is now out giving both Windows and OSX users the ability to flash the iPad 06.15 baseband on iPhone3G or iPhone3GS. (why?).

This release jailbreaks iPhone3G, older iPhone3GS, and non-MC iPod touch 2G. It also assists 3G and 3G[S] users with baseband 05.14 or 05.15 who have been stuck without an unlock upgrade their baseband to 06.15 in order to use the new ultrasn0w which was just released. DO NOT DO THIS UNLESS YOU NEED TO. More on that here.

A much upgraded Cydia is also included in this release, which we’ll be writing a full story on in the morning – a ton of great improvements thanks to saurik and chpwn.