The Dev Team has just released PwnageTool 3.1.4 for Mac OS X. This release supports the 3.1.2 iPhone software for the following devices: iPhone 2G/3G/3GS and iPod Touch 1G/2G.

• The iPhone 3GS is now supported out of the box in PwnageTool 3.1.4 (or if you have upgraded to 3.1.x in iTunes)
• The iPod 2G is still supported in PwnageTool 3.1.4 but you must already be jailbroken (we’ll update this if there’s a big demand from non-jailbroken ipt2G owners)
• The iPod touch 3G is NOT supported

If you’ve Unlocked your iPhone under 3.0, and want to maintain your unlock, it’s vital to remember:

This release allows your baseband to remain unlocked at 3.1.2, but it does not unlock a new baseband put there by restoring to official 3.1.x. It is super important that people who need the unlock to understand they can keep it only by starting at 3.0 (or earlier) and updating solely to custom IPSWs that don’t update the baseband.

If you used some other method, including blackra1n that involved upgrading to Apple’s 3.1.2, your baseband has also been updated and there’s no unlock until (if?) someone figures it out, and the Dev Team has no time table for that.

For the full details please visit the Dev Teams blog and read carefully as TiPb is not responsible for your jailbreak outcome, good or bad.

Need more help? Visit TiPb’s iPhone Jailbreak/Unlock forum.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Dev Team Releases iPhone/iPod PwnageTool 3.1.4 for Mac OS X

It was just one day ago we mentioned that a new PwnageTool was on the horizon and for those iPhone 3GS owners who stayed on 3.0, your patience has paid off as the latest PwnageTool for Mac OS X has been release by the Dev-Team. If you couldn’t wait and you updated your iPhone 3GS to 3.1 via iTunes, you have a slight problem as you will not be able to jailbreak.

The iPhone 3GS is now supported in PwnageTool 3.1.3, assuming the phone was pwned at 3.0 or 3.0.1 – PwnageTool does not support the 3GS out of the box. If your iPhone 3GS has 3.1 preinstalled and is not Pwned then there is no tested jailbreak solution at the moment.

For the full details be sure to check out the Dev-Teams blog and make sure you fully understand what you are getting yourself into before attempting a jailbreak.

If you don’t understand the process, do not attempt it, and as always – TiPb takes no responsibility for the outcome. Need help? Check out our iPhone Jailbreak and Unlock forum.

[Thanks to everyone who sent this in!]

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

PwnageTool 3.1.3 for Mac OS X Released by Dev-Team: Supports iPhone 3GS 3.1

The Dev Team have updated their blog to let the jailbreakers of the world know how to go about jailbreaking iPhone 3.1. It seems as if Apple has really thrown a monkey wrench into jailbreaking the 3.1 software, however, so sit tight as this may be a bit confusing…

First and foremost they have released the PwnageTool 3.1 for Mac OS X that should only be used with the original iPhone and iPhone 3G. Sorry 3GS owners, you’ll have to wait. Be sure to heed some of the Dev Teams warnings before attempting to jailbreak your device.

• If you are using a 3G iPhone with ultrasn0w and rely on ultrasn0w to obtain cellular service, then you should only upgrade to 3.1 with a PwnageTool created .ipsw. – Stay away from Apple’s direct updates.
• If you have an original iPhone (1st generation) then 3.1 unlock works with this PwnageTool release. iPhone 3G users upgrading to 3.1 will need to continue using ultrasn0w with a PwnageTool created 3.1 .ipsw
• PwnageTool WILL work for Original iPhone (1st Generation), Original iPod touch (1st Generation) and the iPhone 3G.

For the full rundown please visit the Dev Teams blog and make sure you fully understand what you are getting yourself into before attempting to jailbreak iPhone 3.1.

If you don’t understand it, don’t do it, and TiPb takes no responsibility for the outcome either way. Need more? Check out TiPb’s Forums.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Dev Team Releases PwnageTool 3.1 for Mac OS X

Now that the dust is starting to settle after the return of Steve, we would like to take a moment and issue another friendly reminder to all of you who currently using an unlocked iPhone 3G or the 3GS – do not install the iPhone 3.1 update via iTunes. You will lose your unlock and it may be permanent as Dev Team’s MuscleNerd stated on Twitter earlier today:

3G+3GS unlockers..you must not update to official 3.1! unlock needs pre-hacked 3.1 with 04.26.08

So what does that mean, well like I mentioned earlier do not update via iTunes. You must first hack the 3.1 software to include modem firmware 04.26.08. If this confuses you, please do not attempt to unlock your phone until an easier way is released.

We here at TiPb are wondering, what about iTunes? Have any of you with unlocked iPhones updated to iTunes 9.0? Let us know how it went in the comments!

As always, be safe out there, as we are not responsible if you blow up your iPhone.

*If you have questions regarding unlocking please visit our iPhone Jailbreak and Unlock forum.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

iPhone OS 3.1 and Unlocking Don’t Mix Well: Yet…

On Friday, Apple launched their new Mac operating system, OS X 10.6 Snow Leopard, and whenever that happens, Mac iPhone Jailbreakers everyone wonder if, on purpose or by accident (oh, hi DFU bug!) Apple will somehow break the Jailbreak. Well, good news this time around — Snow Leopard looks to be Jailbreak safe according to the Dev-Team:

Snow Leopard, the OS released for Mac on Friday, poses no new wrinkles for the redsn0w jailbreak or ultrsn0w unlock. [...] We’re glad to see Apple joining in on the “snow” theme. If only Apple had called their new OS “Sn0w Leopard”!

Indeed!

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Dev-Team: Snow Leopard Safe for Jailbreak or Unlock

The iPhone Dev-Team take a break from the Jailbreak to throw some light on the issue of 3rd party iPhone apps tracking users’ location. Joey Hess and our friends over at PreCentral.net kicked up a bit of a ruckus last week detailing how the Palm Pre reports users’ location data back to Palm HQ. Well, says the Dev-Team:

Although we have yet to find an application by Apple that tracks your location, there are certainly a number of “free” applications in the official AppStore that are designed to do just that. Case in point: there’s this rather cute/gimicky app that lets you determine the tip for your waiter or waitress by tilting your phone as you pass it around the restaurant table. But if you dig a little deeper (like bushing did) you’ll find it uses a library by Pinch Media that is specifically designed to track your geographical location through time, then upload that data to Pinch Media. (Oh and it also show you an ad, as an extra bonus).

They point out that the iPhone will ask before any app is allowed to use location data, but also that it will keep asking to the extent that users might just agree to prevent being constantly annoyed with popups.

The Dev-Team goes so far as to describe these types of apps using the dreaded “s” word. That’s right — SPYWARE. However, in a web increasingly dominated by companies seeking to aggregate (hopefully anonymized?!) user data as a way to monetize (providing free or cheap apps in exchange for the shared data and tolerance for advertising), how broadly can that term now be applied? Many, especially tech-savvy, users are happy to let Google’s Gmail scan their email and serve ads in exchange for the service (and don’t even get us started on Chrome parsing all URLs a user enters through Google, or their purchase of DoubleClick…)

Should we be concerned more about small, 3rd party companies? About Apple, Palm, and Google-type companies? Or is it just the way of the world now?

How about this — Perhaps Apple could give us app-specific Location settings, much as we now have app-specific Notification settings? That way, there’d be a list of apps that use location, and we could individually turn off those with which we don’t want to share our location. How about it, Apple?

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Dev-Team: Palm Pre May Track User Location, but 3rd Party iPhone Apps Do Too!

The iPhone Dev Team updated their blog to let all of you jailbreak crazed iPhone owners that you can safely update to the latest software, OS 3.0.1. It is a fairly straight forward procedure with one little twist.

You can re-use redsn0w v0.8 we released a few weeks ago to jailbreak today’s 3.0.1 update. Just let iTunes update or restore you to official 3.0.1 then run redsn0w. The only “trick” is that when redsn0w asks you to identify the IPSW used, point it at the 3.0 IPSW instead of the 3.0.1 one. After the jailbreak, reinstall ultrasn0w 0.9 if you need the unlock.

Sadly, George Hotz said you can forget using purplesn0w as it will not work. You may be wondering why not? The answer is he doesn’t know.

And for those of you curious as to whether or not ultrasn0w is still capable of unlocking a 3.0.1 device, yes it does. The 3.0.1 software update does not change your baseband so you are good to go.

If you’ve tried the Dev Teams process how did it go? Let us know in the comments!

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

iPhone 3.0.1 redsn0w & ultrasn0w Safe for Jailbreak

The Jailbreak and Unlock wizards behind the iPhone DevTeam are off to DEFCON 17, the security/hacking convention that juxtaposes Black Hat 2009, and have provided a set of tips to help those at the conferences (or anywhere really) avoid getting their iPhone hacked into. The tips are really targeted at Jailbroken iPhones, but some cross over to regular iPhone users as well.

Disable all your login cookies in Safari. If you use the hotel or conference wifi, it is 100% guaranteed that your traffic will be sniffed. If you allow a web site (like twitter.com) to store your login info in a cookie, and if you connect to that site through a normal http connection, your login info will be exposed. At the very least, you’ll end up on the Wall of Sheep. But you’ll be giving up your password to anyone else sniffing too.

They also advise avoiding any public Wi-Fi at hotels, conference centers, airports, etc. (and to tether instead), and either uninstalling or disabling SSH access, or at the very least changing the root and mobile password from Apple’s default.

They also provide their suggestions for talks that might interest the iPhone jailbreak community. If anyone attends, let us know how it goes via our iPhone Jailbreak and Unlock Forum. And If you have more pro tips, send them our way!

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Pro Tips: How to Secure Your Jailbroken (or Regular) iPhone Against Hackers

It was just this past Thursday that the Dev Team updated their software unlock, ultrasn0w, to version .09. While this update seems to have eliminated most of the issues some users were experiencing, the Dev Team have been nice enough to post some pro tips for unlocking your iPhone 3G/3GS with ultrasn0w .09. The following are just a few:

• 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.
• T-Mobile in the USA doesn’t use the 3G frequencies that the iPhones support, so turn off 3G in Settings->General->Network. (Some T-Mobile territories gracefully hand down to Edge mode, but most do not).

So there you have it folks, two very important tips for the unlockers of the world. We here at TiPb can not stress exactly how important that first tip really is to “Setup as new iPhone” within iTunes while restoring your device. Not doing so can and will create issues for you somewhere along the way.

For the full list of tips, swing by the Dev Teams blog.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Dev Team Pro Tips for iPhone Unlockers

In the past 24 hours we have seen major updates to not one but two software unlocks for the iPhone 3GS. Who says competition isn’t a good thing and who doesn’t love a good old fashion hacker fight? Let’s get it on:

In the red corner we have George Hotz along with his fresh version of purplesn0w RC2.

• 3G(the network speed) issues fixed
• Now only patches one file, CommCenter
• Leaves no traces on your baseband after it runs.
• Much more clean and reliable.

In the blue corner we have the iPhone Dev Team. And since Hotz released his source code, his competition used it to create their latest version of ultrasn0w .09.

• Works on both 3G and 3GS
• Doesn’t patch any mach-o binary whatsoever. (Doesn’t require a separate patch as each new firmware comes out).
• Has no race conditions, no popups about “Missing SIM”, no network issues
• Is almost 7000 times smaller than its nearest competition

So there you have it – two software unlocks for your iPhone 3GS and one update for your iPhone 3G unlock. You have to credit George Hotz for stepping his game up when the Dev Team has been dragging their feet. It really seems to have sparked up a good rivalry that we can all benefit from.

There is one major question though, how do you score the match?

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Ultimate iPhone Hacker Championship: Purplesn0w vs Ultrasn0w