The Apple TV 2 will be included in the upcoming jailbreak, according to MuscleNerd of the Evad3rs Dev-Team.
Awesome…as @EvilPenguin_ pointed out, we’re seeing the final ATV2 6.1 today too. So ATV2 will be covered by the JB (not ATV3 tho).
Unfortunately, as mentioned earlier the Apple TV 3G will not be supported by this jailbreak.
The iPhone Dev-Team has announced an updated version of RedSn0w and an upcoming update to UltraSn0w for iOS 6 compatibility.
Version 0.9.15b3 fixes the redsn0w “error 2601” that Windows users were seeing using the Restore button. It also fixes a related Windows iTunes error 14 for stitched files. Note that if you have a baseband, you should probably avoid stitching and simply use redsn0w’s native Restore (not iTunes).
Those lucky recipients of new iPad minis and iPad4s on Friday can use this redsn0w to save your 6.0 blobs off to Cydia. First connect your new device and turn it on, then use redsn0w’s Extras->SHSH Blobs->New and point it at the 6.0 IPSW.
Expect an ultrasn0w compatibility update for iOS 6.0 by Friday (mostly useful for 3GS old-bootrom users who are currently enjoying the untethered 6.0 jailbreak!). Same baseband support as with 5.x.
Thanks to @iamgolfy for helping test the 2601 Windows fix!
You can download the latest version of RedSn0w from .
Famous hacker P0sixninja has recently announced via Twitter that he has left the Chronic Dev-Team.
Just so everyone knows, I’m no longer associated with Chronic-Dev Team. And hopefully by now everyone sees it was never about the money for me.
It’s unclear what exactly has led p0sixninja to depart from the team and whether or not he will continue working independently on iOS jailbreaks.
P0sixninja contributed to the scene with work on GreenPois0n, Cdev Reporter, Absinthe, etc.
Chronic Dev Team released Absinthe 2.0 with much anticipated untethered jailbreak for iOS 5.1.1.
Absinthe 2.0 supports the following devices:
You can download Absinthe 2.0 .
Step-by-step tutorials are available .
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.
This week Gareth Wright 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.
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 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.
The Chronic Dev-Team has released an update to its Absinthe jailbreak utility that brings support for Mac OS X 10.5 (Intel + PPC) and fixes several bugs.
@pimskeks announced the update:
#Absinthe 0.4 released greenpois0n.com/?p=173 – OSX 10.5 support (PPC+Intel). Re-jailbreaking not required. Changelog: pastebin.com/DdwGKstR
What’s New in Absinthe v0.4:
You can download Absinthe for Windows, Mac OS X and Linux from .
Here are our step-by-step tutorials:
iPhone Dev-Team released RedSn0w 0.9.9b9 with full iOS 5.0.1 support (no need to point to iOS 5.0 any more). New version also features support for SHSH and APTickets:
- native support for 5.0.1 (no need to point redsn0w at 5.0 IPSW or use command-line args). Support automatically extends to all of redsn0w’s various functions: “Jailbreak”, “Just boot”, “Fetch blobs”, “Stitch blobs”, “Recovery Fix”
- iBooks fixed in 5.0 and 5.0.1. This is a targeted fix that doesn’t remove entire sandbox mechanism. 5.x users already using redsn0w “Just Boot” can just use the new version without redoing entire jailbreak again
- 3GS old-bootrom owners can now create custom IPSWs without blobs
- ultrasn0w compatability update (i.e. same baseband requirements) for 5.0.1 will be available on Cydia Monday
- support for newer 8GB (which until now had problems with “Fetch blobs”). Thanks to @JKjeepnJeff for loaning us one of these newer i4 units for testing!
- allows Windows users (not just OS X users) to use the “Custom” button to create IPSWs without baseband updates. (Update: please wait for 0.9.9b9b for this!)
- accommodates APTickets in 5.x (until next Apple countermove). APTickets are crypto-verified before submitting to Cydia, just like the main blobs. Cydia server support for sending back the APTickets is upcoming. For now, use stitched IPSWs for 5.x. Due to APTickets, stitched 5.x IPSWs now require user to start in “Pwned DFU” mode
- Support added for stitching 4.x blobs to iPad2-GSM IPSWs. Similar to @notcom’s TinyCFW but doesn’t require lots of RAM or a TSS-assisted restore. Won’t work for iPad2 5.x blobs (or iPhone4S at all) until a bootrom-level exploit is out
- top line now shows whether (and where) a redsn0w update is available, or if the version being run is the latest. Uses DNS TXT record to alleviate any concerns about snooping
- no 5.1 beta support at this time (major apps like Cydia are not yet compatible)
- @pod2g has been doing a great job porting his 5.x untether…check for updates!
- Owners of newer 3GS iPhones must not flash the iPad baseband. The iPad baseband will not work on 3GS iPhones built later than 2011 week 35. You have a week 35 or later device if your serial # starts with xx135.
Update #17b: Version 0.9.9b9b enables the “Custom” button for Windows users, and make the 3GS week 35 warning a more explicit part of the process.
You can download RedSn0w 0.9.9b9b .
UPDATE: redsn0w updated to redsn0w 0.9.9b9d.
The Chronic Dev-Team has released , their new tool that lets you help find jailbreak vulnerabilities, for Windows.
You can download the Mac and Windows versions of CDevReporter here:
More information is available in our recent post ““.
Semi-tethered jailbreak is already available for some devices for both iOS 5 and iOS 5.0.1. But we all want untethered jailbreak and we want jailbreak for iPad 2 and iPhone 4S. So why not help hackers to find new exploits and vulnerabilities?
The Chronic Dev-Team has a released a tool to collect crash reports from iOS devices in order to find vulnerabilities that could lead to an untethered jailbreak.
The idea is very simple. When your iPhone, iPad or iPod Touch crashes it sends data to Apple (you can turn it this off though). Apple uses these reports to update iOS in the future. By the way, it also uses them to fix exploits found by jailbreakers. P0sixninja says that Apple closed several exploits they have found in IOS 5 beta before the final version of the software was released.
In order to find more vulnerabilities as fast as possible, the team has developed a tool which will copy the crash reports from your device and analyze them to locate potential exploits. The tool will also remove the crash reports from your device and modify your iTunes installation to prevent uploading of that diagnostic information to Apple.