iDownloadBlogreports that popular iOS pirated app community Hackulous has announced that it is shutting down. This means that the Installous jailbreak tool used to install pirated apps on iOS devices will no longer be available. A statement from Hackulous reads:
We are very sad to announce that Hackulous is shutting down. After many years, our community has become stagnant and our forums are a bit of a ghost town. It has become difficult to keep them online and well-moderated, despite the devotion of our staff. We’re incredibly thankful for the support we’ve had over the years and hope that new, greater communities blossom out of our absence.
The report also observes that other piracy tools, both existing and new, will probably rise in popularity due to the removal of Installous. Piracy continues to be a major issue for many iOS app developers, as there have been many incidents of piracy causing developers to remove their apps from the App Store. Good riddance.
The Digital Millennium Copyright Act (DMCA) was first passed back in 1998, at a time when the term “jailbreaking” did not even exist. It was passed mainly to prevent bypassing of Digital Rights Management technology. Back then, it was also established that DMCA could have its own exemptions. Yesterday, a new set of exemptions were announced for the DMCA, which will come into effect on October 28, and will continue to be valid for three years until 2015.
These exemptions announced by the DMCA are extremely arbitrary, and their poorly defined scope undermines the premise of having DMCA in the first place. Ars Technica puts together these discrepancies as-
The new batch of exemptions illustrate the fundamentally arbitrary nature of the DMCA’s exemption process. For the next three years, you’ll be allowed to jailbreak smartphones but not tablet computers. You’ll be able to unlock phones purchased before January 2013 but not phones purchased after that. It will be legal to rip DVDs to use an excerpt in a documentary, but not to play it on your iPad.
Apparently, Tablets were excluded from jailbreaking because the definition of tablets is too broad at the moment. The deadline of January 2013 for unlocking phones has no explanation as well, but the most disappointing news from this exemption list is related to unlocking of smartphones.
Jailbreaking of phones was already legal according to the DMCA. However, according to this revised law, phones cannot be jailbroken anymore without the permission of the carrier. DMCA’s argument against unlocking was a comparison with software purchase, which says that you are essentially licensing the software for use according to the EULA, but you cannot claim ownership on the software.
If DMCA can be so flexible that it takes concepts of software purchase and applies them to hardware purchase, how is it so rigid to allow the same freedom on one device, and take away that freedom on another?
The video shows off an iPhone 4S running iOS 5.0.1, complete with Siri, powered on and off after having been jailbroken. With full access to Cydia and an untethered restart, it’s a fully functional and end-user ready jailbreak. Hopefully the exploit can be packaged into the currently available tools and released once it’s been fully tested.
Be sure to watch the official page for a release by the Chronic Dev Team. It’s also highly likely that the iPhone-dev team will also have their tools updated with the new exploit for eager jailbreakers soon.
It looks like Apple is about to aggressively combat the replay attacksthat have until now allowed users to use iTunes to restore to previous firmware versions using saved SHSH blobs.
Those of you who have been jailbreaking for a while have probably heard us periodically warn you to save your blobsfor each firmware using either Cydia or TinyUmbrella (or even the copy from /tmp during restoremethod for advanced users). Saving your blobs for a given firmware on your specific device allows you to restore *that* device to *that* firmware even after Apple has stopped signing it. That’s all about to change.
Starting with the iOS5 beta, the role of the APTicketis changing â€” it’s being used much like the BBTickethas always been used. The LLB and iBoot stages of the boot sequence are being refined to depend on the authenticity of the APTicket, which is uniquely generated at each and every restore (in other words, it doesn’t depend merely on your ECID and firmware versionâ€¦it changes every time you restore, based partly on a random number). This APTicket authentication will happen at every boot, not just at restore time. Because only Apple has the crypto keys to properly sign the per-restore APTicket, replayed APTickets are useless.
This will only affect restores starting at iOS5 and onward, and Apple will be able to flip that switch off and on at will (by opening or closing the APTicket signing window for that firmware, like they do for the BBTicket).
Starting with iOS5, Apple will be using a new technology which they can turn on and off at will. This will limit the device from being restored to an earlier version. However, all is not lost yet since the Dev-Team says that tethered jailbreaks will still be possible and users would be able to downgrade to an earlier version provided they use an older version of iTunes, so don’t delete those old installers yet.
geohot’s limera1n exploit occurs before any of this new checking is done, so tethered jailbreaks will still always be possible for devices where limera1n applies. Also, restoring to pre-5.0 firmwares with saved blobs will still be possible (but you’ll soon start to need to use older iTunes versions for that). Note that iTunes ultimately is *not* the component that matters here..it’s the boot sequence on the device starting with the LLB.
Apple has always been playing games with jailbreakers by watching over them and quickly releasing patches when an exploit is discovered and used for jailbreaking. Apple has also gone out and released unlocked iPhone 4 in the market. This might be aimed at controlling the unlocked iPhone market which is achieved through jailbreaking. With the introduction of iOS5, Apple might be hoping to restrict jailbreaking completely, even though it is legal.
It was just a couple of days ago that Apple released iOS 4.3.3 to the general public. The new version of iOS was mainly aimed at fixing the location tracking bug, and battery life improvements.
Thankfully, Apple did not patch the i01nic’s exploit used in iOS 4.3.x to jailbreak it. Now, the iPhone Dev. Team has updated ported over the exploit code to iOS 4.3.3, and incorporated it in their application – redsn0w.
This means, iDevice owners running iOS 4.3.3 can jailbreak it by using redsn0w. iOS 4.3.3 supports iPhone 3GS, iPhone 4, iPad 1, iPad 2, Apple TV 2G and the iPod Touch 3G/4G. Except for the iPad 2, all other iDevices can be jailbroken using the latest version of redsn0w.
Pwnage Tool – Mac counterpart of redsn0w has also been updated by the iPhone Dev. team. Verizon iPhone 4 owners, running iOS 4.2.8 need to use the latest version of snowbreeze, to jailbreak their handset.
iPhone 3GS and iPhone 4 owners who have unlocked their handset using ultrasn0w, are recommended to stay away from this jailbreak. By upgrading to iOS 4.3.3, they may loose their unlock.
Apple recently rolled out iOS 4.3.2 for the iPad 1/2, iPod Touch 3G/4G and the iPhone 4. The update was a minor one and was mainly aimed at fixing bugs, and improving the battery life.
Thankfully, Apple did not patch the exploit used by hackers to untether’ jailbreak iOS 4.3.1. Now, @i0n1c has made changes in his jailbreak code so as to make it compatible with iOS 4.3.2.
The iPhone Dev. Team has also released an updated version of redsn0w incorporating the code. This means iPhone 3GS, iPod Touch 3G/4G and iPad 1 owners can now jailbreak their device running iOS 4.3.2.
There is some problem jailbreaking the iPhone 4 with this version of redsn0w, so users need to wait until the Dev. Team releases a fix for it. Until then, they can use redsn0w to tether’ jailbreak their iPhone 4.
iPhone 4 users who have unlocked their handset using Ultrasn0w are recommended to stay away from updating to iOS 4.3.2. They should wait until an updated version of the app supporting iOS 4.3.2 is released.
iDevice jailbreaks can download the latest version of redsn0w from here.
The iPhone Dev. Team has just released a new jailbreak for iOS 4.3.1, about which we reported a couple of days ago.
The new jailbreak is an untethered one, unlike the previous jailbreak released for iOS 4.3.1. The new jailbreak supports iPhone 3GS, iPhone 4, iPod Touch 3G/4G, Apple TV 2G and iPad 1 running on the latest version of iOS.
The jailbreak is also available for all Windows and Mac owners via Redsn0w or PwnageTool. Readers can download the application from here.
iPhone 4 owners, who have unlocked their handsets using Ultrasn0w, need to wait until an updated version of the app comes out. Right now, Ultrasn0w unlock is incompatible with iOS 4.3.1.
Sadly, iPad 2 owners need to wait for a jailbreak, until a boot rom level exploit is found for their device.
Incidentally, the first version of PwnageTool was released on this very day, three years ago!
MuscleNerd of the iPhone Dev Team has just confirmed via Twitter that his team will soon be releasing an untethered jailbreak for all iTouch devices running iOS 4.3.1.
At the moment, the only jailbreak available for iOS 4.3.1 is a tethered jailbreak released by DjayB6. MuscleNerd also confirmed that the jailbreak is in its final stage, with the team busy in ironing out some bugs.
This new jailbreak will work for the iPhone 3GS, iPhone 4, iPod Touch 3G/4G, Apple TV 2G and the original iPad. However, like the DjayB6‘s tethered jailbreak for iOS 4.3.1, this new jailbreak method will also not support the iPad 2.
iPhone 4 owners who have unlocked their device via Ultrasn0w, are recommended not to update their iOS version and use this jailbreak. If they do so, their baseband version will be upgraded and they will lose their unlock.
The jailbreak is based on an exploit found by i0n1c, and will be available for both Windows and Mac users via Redsn0w and PwnageTool, respectively. Hopefully, the iPhone Dev Team will release the updated version of PwnageTool and sn0wbreeze within a week or so.
Apple released the iOS 4.3.1 a couple of days ago, to address battery life issues and graphical glitches with iPod Touch.
Now, within a day of its release, iOS 4.3.1 has been jailbroken by DjayB6. Sadly, the jailbreak is a tethered’ one at the moment. This means iTouch device owners will need to jailbreak their device, every time they reboot it.
As of now, the iOS 4.3.1 tethered’ jailbreak will only work for the iPhone 3GS, iPhone 4, iPod Touch 3G/4G, Apple TV 2G and iPad.
Owners of the latest generation Apple’s tablet, iPad 2, will have to wait for some more time before a jailbreak comes out for their device. Until then, they are recommended not to update their iOS version to 4.3.1.
Also, iPhone 3GS and iPhone 4 owners who have unlocked their handset using Ultrasn0w are recommended not to update to iOS 4.3.1. If they do so, their baseband version will be upgraded and they will lose the network unlock. The tethered’ jailbreak is only available for Mac OS X based PCs.
Hopefully, a Windows version will be released soon. The steps to jailbreak your iTouch device running iOS 4.3.1 can be found here.
Apple is smart which is why it has been taking longer and longer to jailbreak the newer versions of iOS. However, the Dev team has been able to find a workaround to jailbreak and unlock. It’s more of a cat and mouse game between these two.
The fix was put in place by @comex and @pushfix who managed to fix the issue with the latest jailbreaking tool, allowing users to continue reading book they purchased through the app store.
So if you have been facing an issue with the iBooks software, head over to the Dev Team blog to download the latest PwnageTool 4.2 bundle to jailbreak and unlock your iPhone, iPod Touch and iPad and start using iBooks again. These updates will also be made available through the Cydia app, so you can just update the app and start using iBooks app without having to restore and jailbreak your device again.