Posted on 19 October 2009
Let’s be clear upfront that this isn’t for the casual iPhone jailbreaker, but if you feeling like living on the edge, you can give your original model an added boost of MMS capability, or any device with OS 3.1.2 the power to tether. Highlighted in a series of tweets today by iPhone dev team lead MuscleNerd, whiterat (for MMS) and two-bit (for tethering) will get the job done, but both require tinkering with the baseband, which is exponentially more advanced and brick-inducing than, say, Read the full story
Popularity: 6% [?]
Posted on 11 September 2009
Whenever Apple releases a new version of iPhone OS or iTunes, one of the most frequently asked questions by users who havejailbroken and/or unlocked their iPhone is whether it is safe to download and install them.
MuscleNerd from the iPhone Dev Team has answered this question for us about iPhone OS 3.1 and iTunes 9 that were released by Apple at the special event today.
Read the full story
Popularity: 2% [?]
Posted in News
Posted on 29 August 2009

The iPhone Dev-Team has confirmed that all its tools work well with Mac OS X Snow Leopard.
Snow Leopard, the OS released for Mac on Friday, poses no new wrinkles for the redsn0w jailbreak or ultrsn0w unlock.
Read the full story
Popularity: 3% [?]
Posted on 20 July 2009
It looks like version 0.9 of ultrasn0w fixed up the vast majority of any problems people were seeing with the 3G/3GS carrier unlock. But here’s a brief list of fixes for anyone still seeing problems:
- Unusual battery depletion is almost always caused by people choosing to “Restore from backup”instead of “Setup as new iPhone” when iTunes asks you. This isn’t caused by either the jailbreak or the unlock, but it’s a common 3.0 snafu. The fix is to just re-run the official 3.0 restore and choose “Setup as new” this time. Your music and apps and all that will still be synced, but you’ll get rid of any conflicting wifi, bluetooth, or carrier settings. Then just re-run redsn0w and install ultrasn0w. Read the full story
Popularity: 2% [?]
Posted in News
Posted on 13 July 2009
We don’t have confirmation on this beyond the word of a Czech-based developer who has tested it, but apparently Apple is blocking push notification services in unofficially unlocked iPhones. However, we have tested it and it works.
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.
Read the full story
Popularity: 2% [?]