View Single Post
Old 05-03-2012, 23:11   #1 (permalink)
cts2007
No Life Poster
 
cts2007's Avatar
 
Join Date: Dec 2007
Location: Inside iPhone
Age: 39
Posts: 1,102
Member: 643010
Status: Offline
Sonork: 100.1612806
Thanks Meter: 2,856
.....:::: iOS 5.1 Untethered Jailbreak Ready ::::.....

.....:::: iOS 5.1 Untethered Jailbreak Ready ::::.....
--------------------------------------------------------

pod2g successfully jailbreak his iPhone 4 on iOS 5.1

Good news for hopeful iOS 5.1 jailbreakers, infamous iOS hacker and Chronic Dev Team member ‘pod2g’ just tweeted that he has his iPhone 4 running an untethered jailbreak on iOS 5.1. For those who don’t know, the difference between a tethered and untethered jailbreak is huge; the former means you have to re-jailbreak every time the device reboots while the latter means you’re jailbroken until you update to a new version of iOS.
There’s still a lot of work to be done on the untethered iOS 5.1 jailbreak for iPhone 4S owners, but an untether for iPhone 4 and iPad 2 users looks to be on the distant horizon. The iPhone 4S runs on a faster A5 processor, making it a totally different nut to crack for jailbreak hackers.
Creating a jailbreak for mass distribution takes a lot of time and tedious work. New vulnerabilities in iOS have to be found and exploits have to be packaged together and tested rigorously. A poll was conducted on pod2g’s blog asking the community whether the hackers should release a jailbreak for iOS 5.1 or wait for the iOS 6 beta later this summer. The majority voted for releasing the untethered 5.1 jailbreak as soon as possible.
Once a jailbreak is released, Apple patches the exploits and they’re usually unusable for future jailbreaks. It’s getting harder and harder to find exploits in iOS, so hackers are starting to be more judicious about burning their exploits. You know what they say, “waste not, want not.”

  Reply With Quote
The Following 26 Users Say Thank You to cts2007 For This Useful Post:
Show/Hide list of the thanked
 
Page generated in 0.09875 seconds with 7 queries