At last, Apple has released a much-needed patch: iPhone OS 3.1.2 is out and it solves the sleep issue--in which the iPhone refused to wake up--brought in by the previous version. There are other fixes too: • Resolves sporadic issue that may cause iPhone to not wake from sleep • Resolves intermittent issue that may interrupt cellular network services until restart • Fixes bug that could cause occasional crash during video streaming
It weighs 241.7MB. Go get it in iTunes. After the update--which is also available for the iPod Touch--you will be able to update to AT&T Carrier Settings 5.6.
Holy Moly. This is big, big, big news. Bell and Telus have officially announced that they will be carrying the iPhone 3GS on their newly upgraded GSM networks, meaning that Rogers (Robbers?) will finally have some competition in the iPhone arena. I doubt this will have much effect on me since I’m already signed into a three-year plan (and AT&T users think two years is bad?!), but I’m just so happy to know that somebody is out there actively trying to kick Rogers in the behind. If either Bell or Telus offer something significantly different in terms of pricing, I might even consider moving to them as soon as next year. I hate it being on Rogers that much, as they have — bar none – the worst customer service I have ever experienced.
Now I’m not saying these two companies are angels and there haven’t been any numbers released as of yet, but my hope is that Canadians will get to see more competitive pricing overall and see more decent plans start to roll out. What kind of “smartphone plan” doesn’t include caller ID anyway? Yeesh.
[news via iPhone in Canada, confirmed also at Globe and Mail]
The posting of the usb_control_msg(0x21, 2) Exploit by Chronic Dev to the iPhoneWiki caused a little bit of upset today with GeoHot threatening to stop work on the exploit."OMG CHRONIC, WHY DID YOU POST THE EXPLOIT? SHIT LIKE THAT MAKES ME NOT WANT TO WORK ANYMORE""i discovered that exploit first, and that was really a low blow to try and take credit. have fun with greenpois0n, i am not releasing"Chronic Dev has since posted the full story on his blog to explain things.We wanted to make this perfect and bug-free, so it was taking awhile. Soon, people started commenting and emailing me complaints about it taking so long. I can handle this. Then, I start getting ppl threatening to file a dispute with PayPal to get a refund. This is an issue, not because they don’t realize that these were donations, but because PayPal usually sides with the “buyer”, as I have heard in many PayPal horror stories.When GeoHot announced he would have a jailbreak in two days this sent angry donators into overdrive.Some people started saying that I was an all out scammer and when geohot released first they would dispute their donation because it “seemed like it was all an elaborate hoax to get a free iPod touch”.Chronic decided to publish the exploit on the wiki for numerous reasons:- We knew that we could not get greenpois0n completely finished in time. We needed a perfectly safe NAND write, a ported over 24kPwn, and more to make it totally stable.- Geohot would release in a few days anyway, so “hiding the exploit from Apple” was not a concern at all.- We had done a lot of research on the exploit, how it worked, and why it worked, and had everything written up. If Geohot would release in a few days, and we knew we couldn’t do anything, why not share what we already knew with the community? Geohot usually writes up short descriptions and gradually adds on when it comes to exploits, while we already had a nice write-up already made.- Again, Geohot said a few days, so the idea that we were giving anything to Apple is false, since they would have had it in “a few days” anyway.- This would cause people to stop hounding about progress + threats to dispute their donation, because it would show that their money went to good use.GeoHot has since posted that he understands Chronic Dev's reasons and that the two parties discovered the exploit independantly. "oh i understand your reason...people were reversing their donations. why you shouldn't ask for donations before release""i want to apologize, chronic didn't steal the exploit, and i phrased http://bit.ly/1YkFH9 badly. independently discovered"Those just looking for a jailbreak can rest assure that it is being worked on and still has an ETA of 2 days."eh, you're right, I shouldn't take it out on the end user. sorry, i'm pissed off in the morning. k fine, back to work. #2days"Those threatening to withdraw their donations to Chronic Dev should be grateful for the team's hard work and continued contribution to the community. GeoHot has amazing talents that not many can match. His ability to release a jailbreak earlier does not reduce the importance of donating; especially when donations are used to purchase devices needed for testing and development.
Written by Eric Slivka The Washington Post reports that AT&T may be planning to announce support for Skype, Google Voice, and other related Voice over Internet Protocol (VoIP) services over its mobile networks, including via Apple's iPhone. One source close to the thinking of AT&T executives said the company has been deliberating the decision for weeks and that top executives have said they were close to accepting voice over Internet services on all AT&T phones, including the iPhone. The source spoke on the condition of anonymity because a decision hadn't been officially announced. Skype currently operates on the iPhone through WiFi access, but not on AT&T's 3G mobile network.
Apple reportedly rejected a Google Voice iPhone application in late July, sparking an inquiry into the situation from the Federal Communications Commission (FCC). In its response to the FCC, Apple claimed that it had not formally rejected the application and was still reviewing it, but Google's response painted a very different picture, claiming that Apple senior vice president Phil Schiller had directly delivered the rejection notice to a Google executive via telephone.
For its part, AT&T noted that it played no role in the specific Google Voice iPhone application review process, although the company's agreement with Apple does reportedly require that it provide permission for any iPhone functionality to originate or terminate a VoIP connection on its network.
You remember GeoHot? He was the 18 y/o kid who was the first to unlock the first gen iPhone back in 2007. More recently, GeoHot released PurpleRa1n, which was the first jailbreak method for the iPhone 3GS running OS 3.0. In other words, the kid is a little genius…
Lucky for us, GeoHot is back at it and this time, he decided that just jailbreaking the iPhone 3GS was not challenging enough so he took on the task to release a tool that will jailbreak all iDevices: iPhone 2G, 3G, 3GS, iPod Touch 1G, 2G, and 3G.
In a blog post called “Meet the Family” (see picture above), GeoHot says it all in just a few words: “And prepare to meet the program that will jailbreak them all.”
This great new comes just a few days after the Dev Team released its own jailbreak for the iPhone 3GS 3.1 and iPod Touch 2G 3.1.1; a jailbreak which still prevents iPhone 3GS users to jailbreak if they updated their iPhones to 3.1 without pwning it first. This is obviously a big problem for many users who had updated to 3.1 and are now stuck there without being able to jailbreak (even though there are some tricky workarounds).
GeoHot doesn’t have a name for the tool yet. We actually don’t know much about what it will do besides that we know it will “jailbreak them all”. Will it work on both Mac and PC? We don’t know but I do think it will.
The big question is “when”. When will this tool be released? GeoHot said on Twitter he’s got an ETA of 2 days. I really can’t wait to see what he’s got up his sleeves and I’m sure I’m not the only one.
As usual, I will keep you updated as the news come. You can always refer to our jailbreak section for the most up-to-date info on jailbreaking. -- Post From My iPhone3g
The Chronic Dev-Team has posted an update on the jailbreak for the new iPod touch (ipt3).
----- - After a stupid mistake was corrected, posixninja was able to use a payload written by ius that retrieved the location of the aes_crypto_cmd routine, so now we can decrypt the firmware files. - “greenpois0n”, as in, the payload, is coming along quite nicely. This is it’s third rewrite, and I am doing it entirely in C with the exception of the loader.
Plans for the end product - No DFU required - No extra time to send over a ramdisk and boot that, everything is planned to be done over iBoot - No IPSW required, firmware files are read directly from flash, then decrypted and patched on the fly, then reflashed and / or put aside to be booted from later - If the device is connected in Normal Mode, automatically reboot into Recovery Mode - Jailbreak takes less than 1 minute from the time it boots to recovery - Verbose reporting of progress, like “patching iBoot” or “reflashing DeviceTree” on the screen of the device, if you don’t understand what this means, it is similar to what the screen looks like if you were verbose booting your Mac / iPhone - Extra patches such as access to the UID and GID keys from userland automatically applied, no need to dig up kernel decryption keys and use the patcher provided in xpwn and such - Totally untethered jailbreak. This may or may not require an extra exploit. - In case our exploit is in any other firmware revision, it can be ported in just a few line changes.
If you did not understand what some of that meant, this is the most important fact: on release, you will be able to go up to some random laptop at Best Buy, download the very small program plug in your device no matter what state it is in (normal or recovery), run it, and 1 minute later your device will be jailbroken. I am obviously not suggesting you randomly go in and do that, but the point I am trying to get across is that you will not need to prerequisites like libUSB, just plug it in, push a button, and the jailbreak is done in 1 minute. This is the way jailbreaking should always be.