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]