The developer says the following:

According to technical documentation, every Push application has to request the unique token from the Apple's APNS servers to identify the device it's running on. Thanks to that token, APNS servers always know which device is yours. The token can be understood as an IP address — the server has to know where to send the notification and for which application. APNS can also change your token regularly for higher reliability, so it's critical that the application requests the token again on every start (or when enabling the Push feature) to replace the old one if new token is forced by APNS.

On any unlocked iPhone, the application requesting the token is stuck. APNS does not provide any response at all and the application can either cancel the request completely by automatic timeout or let user wait with the proggress bar forever. Either way, the user will never receive any Push message, because APNS has not provided the token.

However, I have an unlocked iPhone here in Spain and the push notification works perfectly—for example, with AIM. The catch, however, may be that my JesusPhone is using the official Movistar network, not a different one.

Whatever is the case, can Apple legally block these push services to people running iPhones on non-official networks? Would they be interested in doing this on purpose—since unlocked iPhones is such a small percentage of units? Or maybe it's just a technical glitch?

According to the developer, it doesn't matter: They argue that Apple has all the right to block services for these users—since they don't use the official carrier—even while it's hurting its ratings. However, they are asking Apple to provide a way to inform users with unlocked phones about why they don't get push services using third-party applications. [Powerybase via AppAdvice via 9to5]

The image associated with this post is best viewed using a browser.

Though it was announced earlier today, they still haven't revealed too much about "ultrasn0w" yet for fear of Apple updating the software with a lock, only saying that the new software should be out this Friday for your hacking pleasure. It's not totally clear that the newly-rebranded ultrasn0w will work on the new iPhone 3GS, either, but Apple hasn't been able to create an iPhone the Dev Team can't jailbreak yet. Check out the video above for more info, with the caveat that the first two minutes are just a static image. [iPhone Dev Team]

On Tuesday evening they will do a live demo of the new yellowsn0w carrier unlock working on official 3.0 firmware, just before the big Apple release. While jailbreaking is already possible on 3.0, this is good news for would-be unlockers with an iPhone 3G, though those going for the 3GS will have to wait a bit longer. [DevTeamBlog via TheModShop—Thanks, Dylan!]

Yellowsn0w, the iPhone 3G unlock, runs as a small command line application that gets installed in any jailbroken iPhone 3G using Installer. It's very easy to install:

• First, update your iPhone 3G to the latest iPhone OS provided by Apple using the latest iTunes.

• Then, use QuickPwn 2.2 to jailbreak and activate your iPhone 3G. If you have Mac OS X 10.5.6 installed, you should follow these instructions before doing it.

• Use Installer or Cydia to install yellowsn0w, which is completely free. Here are the addresses you have to use to add yellowsn0w to your installer application:

For Cydia enter: http://apt9.yellowsn0w.com/
For Installer enter: http://i.yellowsn0w.com/

• That's it. There are some special SIM cards that give problems, but f you have a normal SIM card from any non-official carrier, you are fine.

BEWARE: This is a beta application—version 0.9.1— so install at your own risk—I'm installing, it, though. Since it's a daemon which doesn't alter anything permanently, it seems safe. Just proceed with caution and be warned.

Update: I've been trying to get this to run all day. The installation is very easy. Getting it to work right is a completely different matter.

After reboot, the iPhone won't pick my Vodafone carrier (the Vodafone SIM card works fine in an iPhone first generation, unlocked with the old unlock). It will just sit there, idle. Won't give any error, but it won't connect to the carrier network.

My iPhone 3G has the 2.28 baseband, as it should, and has been Quickpwned for the first time to do the unlock. Installer and Cydia are there, working fine. I've carefully followed the instructions in their page—about getting out the SIM card for a minute, then get it back in (and all other possible combinations)—but it just won't fly.

Like they say, this is beta. It won't damage your iPhone—in theory—but it may or may not run. It seems like there are other reports of the same, as well as other people talking about losing the network connection.

Even while this is labeled as a beta, it saddens me that the iPhone Dev Team has embraced the damn beta culture just to make the release on a cute date. It looks like the old days of solid versions are long gone by.

Update 2: There's a poll here with people saying if it works or not. At the time of this writing, these were the stats:

It worked: 23 34.33%
It doesn't work: 44 65.67%
Voters: 67.

Hopefully, a more stable and predictable release will come soon. Until then, I will keep trying. If you have any reports, drop me a line via email.

Update 3: iPhone Dev Team has released version 0.9.4. After some magic moves in the terminal, it worked for me. My iPhone 3G is now working in Spain in the Vodafone network. [IPhone Dev Team]

Yes, all we have here is an annotated hour-long PowerPoint, and yes, almost all of the content is of interest only to the actual haxxors that gathered at 25C3 to watch, but for me, it's a thrill to hear these guys talk about the software that we've covered and used ourselves for so long. It's also a thrill to hear little tidbits like the 180 IP addresses inside apple that the Dev Team guys have tracked as frequent updaters of Pwnage and Quickpwn.

Up until this weekend in Berlin, most of the iPhone Dev Team had never met each other in person. And I only wish we could have gotten a quick camera pan over to the guys identified as the team members who wish to remain anonymous—in the corner, wearing "PwnApple" t-shirts, speaking Russian. [hackaday via BBG]

The update prevents jailbreaking by disabling the software at the computer level, a step up from what the company usually does: release a firmware update that re-locks the iPhone. Now it's stopping your Mac from recognizing the device in DFU (device firmware update) mode by inflicting new code on the USB ports on Apple computers.

While the iPhone Dev Team is no doubt working to figure out a new hack around this, some are reporting that the simplest way to work around the update for now is to copy some of the 10.5.5 framework files over the newer ones... or not update. [Information Week and Spaziocellulare]

Get ready, because the iPhone 3G unlock is coming to an iPhone 3G near you. The iPhone Dev Team have been able to break in the baseband processor. As you may remember from the first-generation iPhone unlock, this is big news because it means they have access to the core of the system, which gives them the ability to fully manipulate the iPhone 3G hardware and, therefore, unlock it. They gave us all the technical details and posted a demo of it in action:

This is a video of a custom application running on the iPhone 3G baseband, which is big news.

Nucleus is the operating system that runs on the PMB8878 baseband processor, we are using minicom running on the iPhone to talk to the basband via AT commands, the AT command shown is a custom AT command that has been inserted into the PMB8878 that starts an application on the baseband, one of the things that this application does is to lists the tasks (processes) that are running within Nucleus.

Now it's just a matter of time before they come with the unlock and, at last, total carrier independence on compatible 3G networks. [iPhone Dev Team Blog]

The nice thing about iTunes decisions is that we can provide you with patches to counter them. We have one such patch already for Mac iTunes 8 for iPod touch. We’ll be working out the full suite of patches for all the combinations over the next week.

Begun the Apple-Hackers iTunes Wars have. [iPhone Dev Team Blog]

According to their site, WinPwn 2.0.0.1 has the following features:

- Support for both 1.1.4 and 2.0

- Custom Image Support

- Custom Payload Support

- 3g iPhone support

[WinPwn and Rapidshare Mirror]

- It auto-finds the bl39 and bl46 files better, if they’re on your computer.
- It creates the ~/Library/iTunes/Device Support/ folder if not present, which should help with some 1600 errors people have been having.
- Many people have reported the PwnageTool not starting up at all (the icon never stops bouncing). This issue should be resolved now.
- The Sparkle AppCast URL is fixed in this version, so automatic updates should work for future releases.

If you successfully jailbroke and unlocked your iPhone with OS 2.0 with the previous one, there's no need for you to use this version. Otherwise, you can download from here or here.

We can't wait for the tool to be released. [iPhone Dev Blog]

Breno MacMasi, one of the Brazilian guys who achieved this, told us how it works:

Our procedure consist in using one SIM adapter to simulate a fake IMSI test card. Instead of the AT&T IMSI like in the universals.

In other words, like the original SIM card hacks for the iPhone classic, this method forges the International Mobile Subscriber Identity, making the phone believe it's working in the network in which it's supposed to work. There's no word yet on the availability of this hack, but we will keep all of those who don't want to pay roaming charges updated. [Techguru]

You can download from here and here.

If you were wondering how I was doing push email tests on iPhone OS 2.0 and Vodafone UK, this is the reason why. The code wizard commandos at the iPhone Dev Team have been working on this non-stop since the early days of beta testing. In fact, I had iPhone OS 2.0 running on my iPhone since last week. That was version 5A345, two below 5A347, but identical in functionality.

Now that the official iPhone OS 2.0 is out, the iPhone Dev Team will release their Pwnage tool for everyone to unlock and jailbreak their iPhones soon, although the specific date/time is not firm yet. It may not be as interesting as before—since most countries now have the iPhone and it will be impossible to buy without doing a contract first—but people looking to install unsigned applications and buy pay-as-you-go cards while traveling—instead of roaming—will find it very useful.

And besides, we don't get tired of seeing the Death Star exploding again and again. [iPhone Dev Team Portal]

Apart from the previous unlocking and jailbreaking, the new version has three main features:

• Easily customizable images for start and restore screens.
• You can use packages to customize your firmware and install software right away, on one single update.
• You can now pwn iPhone 1.2.0 beta 3.

We also got confirmation of what we already hinted last week: Apple is preparing up to battle the hackers, with more and more code running signed and secured inside the iPhone. This will make things more difficult for the iPhone Dev Team.

How much more difficult? Would this be a real challenge to the iPhone Dev Team's current dominance in the hacking war? According to them, it may be. But it just makes things more interesting and fun, which is exactly what we wanted to hear.

Get your update now. [iPhone Dev Team via Pwnage in Gizmodo]

Pwnage is extremely simple to use. First you have to back up your iPhone data using iTunes.

Then, connect the iPhone, select the firmware from your hard drive and iPwn the iPhone. Pwnage will upload the new firmware to the iPhone and that's that: the tool will take care of everything and, in a few minutes, your iPhone will be ready to go.

I tried this with the latest modified version of iPhone firmware update 1.2.0 and it works as good as with the previous version. So go ahead, punks, and make Steve's day.

Note: if by any chance you come across a pwned version of the latest 2.0 firmware, my advice is not to use this version, as this Apple beta is not as stable as I wish. Instead, use the previous beta, which worked perfectly. [iPhone Dev Team]

Update: Due to legalities the Pwnage tool has been delayed. We'll keep you updated with any release information as we get it. [iPhone Dev Team]

[Hackint0sh]

Whats new? Visible changes are:

• Exchange Support
• Appstore
• Parental Controls
• SDK Support
• Calculator is more advanced
• CISCO VPN support
• Mail mass deletion

Features not included:

• There is no spotlight icon

[Gizmodo's iPhone Hacking Coverage and Hacint0sh]

pwned firmware means it's custom [firmware], you can have it install anything you would ever want :-) Pwned works with some magic, it will be hard to close but nothing is impossible (from Apple) with a mindtwist. But first, we will enjoy :)

They told us that this is all part of their previous Pwnage project, which instead of trying to hack into the iPhone, directly patches the firmware itself to both unlock it, so you can use the iPhone with any carrier you want, and allow you to install any applications you want. You can see how it works here:

According to the Dev Team, the custom 2.0 firmware (technically, 1.2.0,) is now up and running without problems in many of their iPhones, running unsigned applications without a single problem. However, current Installer.app applications need to be changed: "they changed lots of the API, a lot. We will see how much has to be changed to the Toolchain [the previous development tool for iPhone independent developers] to still work after 2.0."

The best news, however, is this: "the hacked 1.2 firmware works with anything. AT&T and others, it's pwned. And Apple will not really be able to patch it this time... somehow :-)"

I'm flabbergasted. As Han Solo would say, "that's one in a million, kid!" Once again.

The cool thing here is that Dev Team told us that this is 1) a true unlock and 2) Apple will have a very difficult time closing this hole. That's the news, not just jailbreak—in fact, it's not even jailbreak in the classic sense. It's built-in the hacked firmware, which allows for installation of any application, unsigned or "Apple Approved"

In other words, true carrier and applications independence. And for a long time.

Note: as you can see, the Dev Team is still working hard in making the iPhone a completely open, carrier-independent platform. If you want to help them, please send a Paypal donation to iphone.devteam@gmail.com or join them at hackint0sh.org.

geohot's 1.1.2 software unlock yes, this is what you have all been waiting for now fixed to support 1.1.3

1. Download these:
gunlock and the secpack from http://iphonejtag.blogspot.com/ or the blog :)
the 4.02.13 fls from http://george.zjlotto.com/index.php/baseband/

2. Downgrade your phone to 1.0.2. See all the great tutorials online to do this.
Your baseband won't be downgraded, this is normal.
This will probably work on other versions too, but 1.0.2 doesn't lose wifi on bb access.

3. Kill CommCenter and run "gunlock secpack ICE04.02.13_G.fls"

4. Reload CommCenter. For some reason my phone was in brick mode. Use the elite team bricktool to get out.

5. Enjoy your 1.1.2 OTB unlocked iPhone

Now, who'd have thought it'd be this easy : )

This release is no thanks to elite/dev
I wish they would share like the old days.
I don't believe everyone in the team is like this, but come on guys.

Oh, the drama. Next in Venezuelan Telenovela TV, Hackers Passion! ¡Rosita, tú mataste a tu hermana! ¡No, lo hizo Pablo! ¡Sí! ¡No! ¡Amparo! [iPhonetag]

The Digg badge in this post is for the original story in Geohot's blog.

• Google Maps Faux GPS has problems working unless you install Navizon.

• Cannot change EDGE Settings. Jesus's EDGE is now nonfunctional because he can't enter in the custom settings for his provider. This is not a big deal for people actually on AT&T or one of the three official providers in Europe, but for people who've SIM unlocked and are wandering about on other networks, it's a huge deal.

• The jailbreak may break official third party apps from the SDK? We don't know if this will be the case, but iPhone Atlas claims that the method Nate used to jailbreak disables "Nikita," which is a component in the iPhone that installs signed software. Signed software, in the iPhone's case, would be official third party apps that are signed by Apple to make sure they don't corrupt or kill your device. If this is broken and unfixable, then jailbreakers may be unable to get in on the SDK action in February.

The official iPhone Dev Team jailbreak was released yesterday, but we haven't had any experience with this yet.

What have you heard? Drop a note in the comments detailing the problems you've had with the jailbreak or just 1.1.3 in general.

Fot the Windows version, you need to download an install iBrickr (instructions are on Nate's site), which will guide you through downloading and installing the firmware. The whole thing will take about 15-30 minutes, based on estimates.
[Cre.ations.net]

Adam from Lifehacker has a walkthrough for the process as well.

Mac version is here.

We had some doubts, but now we can tell you we are sure: the new firmware 1.1.3 is real. Or as Nate puts it: "if it is a hoax, they did a buttload of work." The fact is that it installs normally and it works perfectly. For those not familiar, Natetrue is one of the most respected and veteran iPhone hackers and the author of the popular app iBrickr.

Nate goes on to say that "it installs on the phone no-questions-asked and for that you need to have Apple's private key, which i can confirm that the iphone hacker community does not have—as much as we would love to have it." Indeed, Apple's private encrypted key, used to authenticate all accesses to the iPhone most-private guts, hasn't been uncovered yet by anyone in the world.

In other words, no firmware upgrades can be installed without the knowledge of this key. Furthermore, the idea that someone would have access to this key and spend months to create a fully functional firmware update, with key new features and without any documentation whatsoever seems just absolutely silly.

Effects on unlocks and Third-party applications
The update breaks AnySim's unlocks. Logically, you can't unlock this update using AnySim and there's no alternative to iTunes for activation. If you want to activate, it will only work using iTunes and a standard AT&T account. Nate says, "that is the only way we have been able to activate so far." Nate tried to upgrade an AnySim 1.2u iPhone and it failed. Even while he was able to force it to boot, the phone refused to activate even with a normal AT&T SIM card. "I suspect it's due to the fact that the baseband could not be upgraded to the 1.1.3 'required' version", he says.

Other updates remain untested, like iPhone Sim Free or any of the hardware-based ones, like TurboSIM. In theory, these should work just fine, but jailbreak and activation would be absolutely impossible for the time being. We would have to wait until the update gets released in the open to try new alternative activation methods.

Your favorite third-party apps will be gone too, with no possibility of return for now. The update fixes the bugs which allowed "the jailbreak method we were using for 1.1.2, locking us out again, as expected."

Other effects
Like previous firmware upgrades, whatever is in the user partition remains unchanged. Only the Apple-owned part is affected by 1.1.3. So for those of you who claim that this is a fake because it says "Nate" in the network instead of "AT&T," that's the reason. He changed the network name in 1.1.2 using a program by Erica Sadun, of TUAW, called Make It Mine.

New features and future releases
The list of new features are confirmed too: all are correct, but he couldn't confirm if they are the only ones or not.

Many of you would be wondering how this could have happened, knowing the extremely tight security around the iPhone firmware updates. We don't know, but apparently the leak has occurred because "someone wanted to help the unlock effort." The source of the leak is completely anonymous, even to the people who have had access to the upgrade.

Why the update hasn't hit Torrent yet? The code could be watermarked to catch any leaks "so for now it's screenshots and videos." Also, distributing it won't make much sense at this point: according to Nate the iPhone 1.1.3 Firmware update could hit as soon as next week.

Stay tuned for more updates. [Cre.ations.net - Thanks Nate for your insight and Markus for the tip]

(WARNING: if you have used anySIM or iUnlock in your iPhone, don't upgrade to 1.1.1. You won't be able to apply this and you will brick your iPhone. Everyone else, including people who use TurboSIM or IPSF Paid solution, can do it.) [Official Jailbreak Download (Comes with Tutorial) - (Additional reporting by Jesús Díaz)]

First off, if you apply this patch you won't be able to sync any data to iTunes in its cracked state. To sync again, you're going to have to "delete the symlink Media [directory] and rename OldMedia to Media." Or restore to the previous state, which of course means you will lose the jailbreak.

Also, just to apply the patch, you're going to have to be familiar with IPHUC, a command line utility that that lets you browse your phone's file structure. It also involves directory manipulation when you're inside the phone, also not a basic task. This alone requires you to have basic linux command line knowledge, and rules out most of the regular folks who just want Super Mario on their phone.

In addition to this, if you have an iPhone, this tool won't activate it. The iPod touch doesn't require activation.

So our recommendation is to wait. This is a good start, a step in the right direction, but wait until a much friendlier jailbreak is out. (Additional reporting by Jesús Díaz) [toc2rta]

• Third Party apps run. Kind of. We probably have to recompile many of them for the new frameworks because many of them crash.

• Springboard no longer recognizes DisplayOrder.plist. And the list of "whitelisted" apps (that is, the official Applications including Safari, Photos, Calendar, etc) seems to be hard-coded into Springboard.app

• The iPhone has been activated via third-party workarounds.

• The 1.1.1 binaries barely work with 1.0.2—at least not well enough to run the music store without major hacking.

• The Mobile Terminal App works on 1.1.1.

• The entire bsd suite still works—as do standard command-line utilities compiled for ARM.

• 1.1.1 references both com.apple.mobile.radio and com.apple.mobile.nike.

• The jailbreak method is nowhere near ready for prime time. So please be patient.

[Tuaw]

I can understand why Apple made the decision to make the Nike+ Sport Kit not work with the iPhone (providing a reason to buy an iPod Nano, preventing possible damage to a $399 device, differentiating products, whatever), but iPhone users still want this thing to work with their phones. After all, the phone's flash-based, relatively small and light (if you use an armband), and should work perfectly with the kit—in theory.

Is making the kit work with the iPhone possible? Can you access the 30-pin accessory port with the iPhone? If you can, is it possible to interface with this thing using the iPod nano as reference? Is this a pipe dream, or could this possibly be done?

If enough people get behind this idea, there could even be a bounty set up to reward the hacker(s) that enable this. Let's see where we can take this.