Sadly pod2g has discovered that his untether does not work on the iPod 3G or iPhone 3GS, according to a recent tweet by the hacker.
Sad news. Just tested the untether on an iPod 3G. The kernel vulnerability don’t happen on this one. I think iPhone 3Gs is out too.
the iOS version don’t really matter. It’s about the hardware.
This means these devices can only be tethered jailboken.
This will be disappointing news for many although it’s possible a kernel vulnerability could yet be found for these older devices. For those wondering, pod2g reminds us that the old bootrom 3GS will be untethered jailbroken for life.
Pod2g has announced the discovery of 2 new vulnerabilities in his quest to jailbreak the iPhone.
News: a productive week-end. Found 2 big vulnerabilities. 1 kernel land and 1 root land.
Too bad I have to be secret again…
Last week pod2g noted that a jailbreak of iOS 5.1 would take at least a month to complete. We’ll post more information about how these new vulnerabilities will affect that schedule as soon as we hear more.
If the kernel land vulnerability is exploitable this could provide a jailbreak for the device no matter the firmware.
Famous hacker pod2g has announced that the Chronic Dev-Team now has all the exploits required to release a userland jailbreak for iOS 5.1.
News: we have all exploits required to do a new jailbreak. I’m working on bypassing ASLR at bootup.
Last month Pod2g said that the team only had a few pieces of a userland jailbreak. Now that the team has them all, it will still take some time to put them together in a public ready tool.
Since this is a userland jailbreak, it will be the first publicly available jailbreak of the iPad 3. I0n1c has demonstrated a jailbreak of the new device, however, he’s said he will not release his jailbreak to the public.
This week Gareth Wright reported that Facebook’s app for iOS has a security vulnerability through which malicious users can access login credentials saved in a .plist file of the app. With a copy of that .plist file malicious users could automatically log into the affected user’s Facebook account on another device. Reportedly, the vulnerability also exists on Android devices.
Wright describes several different ways in which your login credentials could be obtained by a malicious user, including hidden applications installed on shared PCs, customized apps, or modified speaker dock that could copy your plist.
According to Facebook, the issue only affects jailbroken or lost devices, as it requires physical access or installation of a custom app on the device. But Wright and The Next Web pointed out that simply plugging into any device would be sufficient for malicious users to gather these files.
The Next Web has confirmed that Dropbox for iOS is also vulnerable to this issue. Given that two such high-profile apps as Facebook and Dropbox are vulnerable to credential theft, it is likely that other apps are also affected by the issue.
As many reports note, this method of gathering login credentials is not actively utilized in a malicious manner, and users can protect their data for the time being by not plugging their devices into shared computers and charging stations.
FireCore announced today that they have successfully jailbroken the Apple TV 2 with the latest iOS 5.1 (5.0). The jailbreak is tethered which requires the Apple TV to be connected to a Mac/PC when powering it on (each time).
Today we’re happy to release new versions of Seas0nPass and aTV Flash (black) that are compatible with latest 5.0 (iOS 5.1) software running on the ATV2.
What’s new in the 5.0 AppleTV software? Should I update?
New interface: - Fast, visual access to all content choices
Movie purchases in iCloud: Support for buying movies on Apple TV and playing back purchased movies from iCloud
Genius Recommendations: Recommendations for content on the iTunes Store based on previous rentals and purchases
Screensaver photos: New National Geographic photos built-in for screensaver
On-device sign-up: On-device sign up for content partners on Apple TV using your Apple ID
Updating to the new 5.0 software is not required, and all aTV Flash (black) features will continue to be supported on AppleTV versions 4.2 and later.
What about the ATV3, will this work?
Unfortunately not. Work is still ongoing for the ATV3, and we hope to have more news soon. For the latest updates be sure to follow us on Twitter.
Which plugins are currently supported on 5.0?
Couch Surfer (works)
Media Player (works)
RSS Feeds (works)
Overflow (not working)
Plex (not working)
Remote HD (not working)
Rowmote (not working)
XBMC (not working)
Note: Non-working items require an author update for 5.0 compatibility.
Using saved SHSH blobs, iH8sn0w was able to downgrade his A5 iPad 2 from iOS 5.1 to iOS 5.0.1. He says his method will also work with the A5X processor once firmware updates are released for the new iPad. That means that it’s possible to restore to any firmware you want on A5 devices, as long as you have the SHSH blobs saved.
This is great news for those with the iPhone 4S and newer iPads. As it stands now, if you have to restore for any reason, you will be forced to upgrade to the latest firmware. This could leave you without the ability to jailbreak for some time.
Found a loophole in Apple’s apticket system. Restored my iPad 2 to 5.0.1 from 5.1. Works on all A5 devices.
A5X devices will work too once Apple pushes a new firmware for it.
Hope we will see update to current utilities soon.
A tool named Absinthe and developed by the Chronic Dev Team will install the untether on your device. Also the iPhone Dev Team will release a CLI (command line) tool to help diagnose issues and repair things if it goes wrong.
This is a little scary I know, but the chance you break something is really small, since we made lots of tests to verify the process on different devices. But it is the first time we use the backup / restore functions of iTunes to install software, and there are maybe things we are not aware of.
For more detailed information ahead of the jailbreak please read the information from iPhone Dev-Team.
iPhone Dev Team has posted a blog entry about upcoming public release. If you have iPad 2 or iPhone 4S go ahead and read it:
But we’re now near the final stages of testing the public version of the jailbreak. Please allow time to clean up any remaining bugs in the jailbreak clients.Jailbreak programs:
To be as flexible as possible, the A5 version of the corona jailbreak will take multiple forms:
Chronic Dev have incorporated the overall flow into a GUI that runs on your Mac or PC. The goal is for the GUI to be enough for most cases.
iPhone Dev have also incorporated the exact same flow into an alternative command-line interface (CLI). This will allow us to help users through individual steps of the jailbreak manually, to both help the user and help improve the overall flow. Although the CLI will also allow the user to perform the entire jailbreak from beginning to end, we anticipate it will be more useful in debugging the occasional errors. The CLI currently has over 20 individual options (in addition to the single “jailbreak” option) that should be useful during debug after the GUI release.
Once all the bugs in the flow are worked out, we’ll also incorporate it into the redsn0w GUI (but still leave the CLI freely available too). In order to maximize the chances of the jailbreak working for everyone, the redsn0w GUI will use native Apple iTunes libraries — this technique is slightly different than how the Chronic Dev GUI handles communications, and should provide nice combined coverage for all the odd computer configurations out there.
iPhone4S: 5.0 (9A334), 5.0.1 (9A405) and the “other” 5.0.1 (9A406)
iPad2: 5.0.1 (9A405)
iPhone4S owners looking to maximize their chances of achieving an eventual software-based carrier unlock should be staying at 5.0. Everyone else should be at 5.0.1. If you’re an iPhone4S owner who already updated to 5.0.1, it’s too late to go back down to 5.0, but if you’re on 9A406 it is possible to downgrade the BB by going to the 9A405 version of 5.0.1 while the window is still open.
The overall flow used by the GUI and CLI to inject the A5 corona jailbreak has never been done before, and there may be unforeseen problems once it’s released to the public. It’s very important for you to sync your data, photos, and music before attempting any version of this jailbreak. We’ll be watching the comments section below for signs of any widespread problems, but please be aware that you jailbreak at your own risk!
As mentioned at the start of this post: when testing has shown most of the bugs have been fixed!