A tethered jailbreak for iOS 5.1 is now currently available for the original iPad and the iPhone 4, and earlier model iPhones. (If you have an iPhone 4S or iPad 2, don't attempt to update to iOS 5.1 and jailbreak, it won't work.)

As always, unlockers that rely on ultrasn0w are going to want to stay away unless you use a custom IPSW to install iOS 5.1 in order to preserve your baseband.

If you are an iPhone 3GS user with an old boot room, congratulations. You can have an untethered jailbreak now on iOS 5.1. All other devices will be tethered.

I typically recommend staying away from tethered jailbreaks unless you absolutely have to. Given the fact that iOS 5.1 didn't bring too many features to the table, I'd probably stay on iOS 5.0.1 until an untethered version is released and upgrading at that time.

And I can't say this enough times: if you have an iPhone 4S or iPad 2, this does NOT apply to you.

You've been warned. If you're still convinced you need your iOS 5.1 jailbreak now, you can pick up redsn0w 0.9.10b6 via our download links below. It's available for both Mac and Windows users.

Source: iPhone Dev-Team

Additional resources:

• Download redsn0w 0.9.10b6
• iMore jailbreak help and discussion forums

If you plan on jailbreaking your iPhone 4S or iPad 2 as soon as a jailbreak for Apple A5 chipset-powered devices is released, update to iOS 5.0.1 ASAP if you haven't already.

If/when Apple releases an iOS 5.0.2 patch or iOS 5.1 they'll most likely stop signing iOS 5.0.1 pretty quickly. iOS 5.1 patches the current exploit used on iOS 5.0.1. That means if you don't update before then, you'll be stuck waiting for jailbreak developers to find a new exploit for iOS 5.1 and we have no idea how long that'll take.

So the moral of this story is if you'd like to jailbreak sooner rather than later, update your devices to iOS 5.0.1 now. If you've got an iPhone 4 or other Apple A4 chipset device, you can jailbreak untethered now on iOS 5.0.1.

While jailbreaking already provides tons of functionality, there's still room for improvement and expansion in 2012. Last year I did a list of jailbreak concepts Apple should implement and low and behold, they implemented quite a few of them. But that's part of the game. Part of what spurs more innovation is creativity and pushing boundaries. And at the end of the day it's really the user base that is the most useful when it comes to helping developers out. They can't create it if they don't know we want it. So this is our list of the top 5 things we'd like to see jailbreak accomplish in 2012.

A jailbreak for A5 devices

We already know pod2g is working on this. While we will most likely get one in 2012, I'm not excluding it as one of the biggest wants for many users. We just received an untethered jailbreak for A4 and older devices. Hopefully a jailbreak for the iPad 2 and iPhone 4S aren't that far behind. While an untethered version would be epic win, I'd take a tethered version for starters.

Cydia updates

While Cydia is probably one of the most used apps on my iOS devices, it can become rather frustrating at times. Saurik made some updates to Cydia in 2011 but nothing to get too excited about. Cydia could use a facelift and some speed enhancements.

While it may not be at the top of saurik's list right now, I know Cydia is frustrating for many users on a day to day basis. Not to mention the organization of packages is rather daunting for many new jailbreakers. They have no idea where to start or what apps they should be downloading. Sure, they can always come to TiPb but for those not familiar, how about adding a jailbreak starter pack in Cydia? I know several new users revert back to stock quickly out of confusion and frustration.

I'd like to see Cydia step up its game to show users what jailbreak is all about. It isn't about pirating apps and installing illegal software at all. It's about enhancing and customizing your experience.

More iPad compatible apps and tweaks

While there is support for jailbroken iPads, it's very minimal. I'd really like to see that change. As of right now, I really can't find a good reason to jailbreak my iPad. A lot of this could have to do with the lack of support for current iPad 2 users. Jailbreak developers may not want to put the time and effort into supporting the low number of jailbroken iPads.

Hopefully a jailbreak for A5 devices will create more interest in jailbreaking the iPad. Even though there are a few good reasons to jailbreak the iPad, I'd like to find a reason I can not live without. I'd like to have a reason or find a jailbreak application compelling enough to make me not want to live without my iPad being jailbroken.

If I'm missing out on some to die for jailbreak utilities for iPad, please let me know. I've yet to find them.

More support updates from developers

After iOS 4 was released, Cydia was plagued with tons of apps and utilities that were never updated to support it. Even though jailbreak tool after jailbreak tool was released supporting almost every device on the market, tools were left to collect dust. Some of them were actually very useful utilities that I really missed using after updating. Things like changing keyboard styles were little tweaks that were left untouched for months.

Some developers are extremely good about updating their tools. Others are not. Where that happens, I'd really like to see new jailbreak developers step up and come out with new solutions. Heck, just improve upon someone else's idea. It seemed as if the jailbreak community was left with a ton of tools that were left in limbo. A package may work, it may not, it may just crash your springboard. I'd like to see less of this.

Maybe this is something that needs to come bundled with updates to Cydia. This is another reason jailbreak may be off-putting to some new users. They download tweaks that aren't compatible with their devices and when it isn't stable, they restore and never give jailbreak another chance. We need to avoid experiences like this as developers.

A more unified jailbreak process

This one may be asking a bit too much but heck, I'll throw it out there. While redsn0w and tools like it are pretty user friendly to begin with, there are tons of tools out there and that's confusing to new users. What tool do they use? Is one not compatible with their device? Programs like ipswDownloader aim to make it easier for beginners, but a lot of beginners won't know what an IPSW is let alone what the tool does, where to find it, or know why they need it.

If jailbreak developers could come together to make a great tool that accommodates all users, I think the jailbreak community would see a great benefit and many more users. I see tons of people in my office every day that bricked their device or jailbroke it with an incorrect tool. I also see people that searched and researched jailbreak online, became overwhelmed, and would rather come and pay me to do it correctly than mess something up themselves. I know there are tons of other users out there that are put off by the overwhelming amount of information and tools out there. Working together to find a way to make the process more streamlined would be time spent that would pay off in the long run.

Bottom line

I think my overall outlook on jailbreak is this - people buy Apple devices because of the experience and the ease of use. If jailbreak complicates things too much, they'll stray away. Of course there will always be power users and ninjas that will put in the time to make it work. But the bottom line is that most iOS users just want their device to work and work well. If jailbreak developers can find ways to make the process and overall experience better, I think they'd see a lot more users willing to give it a try or a second runaround.

What do you guys want to see jailbreak developers aiming for in the coming year? Let us know!

Heard about the untethered jailbreak for the original iPad, iPhone 4, iPod touch 4, and older models running iOS 5.0.1 and curious how to use it on your own device?. This jailbreak won't yet work with newer, Apple A5 chipset-powered devices, namely the iPhone 4S or iPad 2, but if you own anything earlier, you're in luck.

Supported devices

• iPhone 4 (GSM & CDMA)
• iPod touch 4th generation
• iPad (orignal model)
• iPhone 3GS

What you need

• A supported device - please note this will not work for iPhone 4S or iPad 2
• A Mac or PC
• redsn0w 0.9.10b1 - Mac, Windows

Untether via the Corona Cydia package

If you're already tethered jailbroken on iOS 5.0.1, you can untether your jailbreak using the Corona package in Cydia.

Untether via redsn0w

If for some reason you'd prefer using redsn0w to untether, you may do so. Just run the version of redsn0w linked above over your existing jailbreak. When prompted what you want to do, just uncheck Install Cydia since you already have it installed. Let redsn0w do its thing and you should be untethered when it completes.

Jailbreak your device

If you're not jailbroken at all, perform the following steps -

1. First Launch redsn0w

2. This version and other newer versions of redsn0w should automatically detect what version of iOS you are running. No need to manually browse to a firmware file this time. Just click Jailbreak and follow the prompts.

3. Next redsn0w will prompt you to only continue when your device is powered off. If it isn’t already, power your device off while it’s connected to the computer.

4. Next you will be guided through putting your device into DFU mode. Follow the steps and redsn0w will take care of the rest.
5. After redsn0w finishes doing it’s thing, you’re done!

Common issues and how to solve them

Stuck on Apple logo or in recovery mode

Some users seem to be experiencing this issue. Performing a clean restore in iTunes and then attempting to jailbreak after a clean install should alleviate this issue.

redsn0w fails

First attempt to select a custom IPSW under Extras in redsn0w and navigate to the iOS 5.0.1 IPSW to see if this fixes the issue. If it still fails, try a clean restore in iTunes and then attempt to jailbreak again.

If you're running into other issues, make sure to check out our jailbreak and unlock forums for further help troubleshooting common and not so common jailbreak issues.

Daily Tips range from beginner-level 101 to advanced-level ninjary. If you already know this tip, keep the link handy as a quick way to help a friend. If you have a tip of your own you’d like to suggest, add them to the comments or send them in to dailytips@tipb.com.

redsn0w has been updated to version 0.9.9b9d in order to fix a few bugs. This update comes right after an update to ultrasn0w and after adding support to redsn0w for iOS 5.0.1.

iPhone3GS owners in our comments section below noticed a problem with the untethered jailbreak available for the old-bootrom 3GS. We’ve corrected that problem in 0.9.9b9d. If you have an old-bootrom 3GS and have already used last night’s redsn0w on it, you can re-run it again without losing anything. Just use this new version, go to Extras->IPSW and manually select the 5.0.1 IPSW, then go back and Jailbreak it again (but you can uncheck Cydia because it’s already installed).

Keep in mind this jailbreak is still tethered unless you have an iPhone 3GS with the old bootrom. You can grab the updated version via the links below then check out our guide on how to jailbreak iOS 5.0.1 via redsn0w. If you have questions or run into issues, check out our jailbreak and unlock forums as well!

Download links: Mac, Windows Source: Dev-Team blog

If you need to tethered jailbreak iOS 5.0.1 via redsn0w you can now do so without having to manually point to iOS 5.0. The Dev-Team has updated their redsn0w tool to offer native support for iOS 5.0.1. Other notable changes include full support for the newer 8GB iPhone 4, iBooks issue fixed, custom IPSWs for 3GS owners without blobs, and more.

The full list of changes for redsn0w 0.9.9b9b are as follows -

native support for 5.0.1 (no need to point redsn0w at 5.0 IPSW or use command-line args). Support automatically extends to all of redsn0w’s various functions: “Jailbreak”, “Just boot”, “Fetch blobs”, “Stitch blobs”, “Recovery Fix”

iBooks fixed in 5.0 and 5.0.1. This is a targeted fix that doesn’t remove entire sandbox mechanism. 5.x users already using redsn0w “Just Boot” can just use the new version without redoing entire jailbreak again

3GS old-bootrom owners can now create custom IPSWs without blobs

ultrasn0w compatability update (i.e. same baseband requirements) for 5.0.1 will be available on Cydia Monday

support for newer 8GB iPhone4 (which until now had problems with “Fetch blobs”). Thanks to @JKjeepnJeff for loaning us one of these newer i4 units for testing!

allows Windows users (not just OS X users) to use the “Custom” button to create IPSWs without baseband updates. (Update: please wait for 0.9.9b9b for this!)

accommodates APTickets in 5.x (until next Apple countermove). APTickets are crypto-verified before submitting to Cydia, just like the main blobs. Cydia server support for sending back the APTickets is upcoming. For now, use stitched IPSWs for 5.x. Due to APTickets, stitched 5.x IPSWs now require user to start in “Pwned DFU” mode

Support added for stitching 4.x blobs to iPad2-GSM IPSWs. Similar to @notcom’s TinyCFW but doesn’t require lots of RAM or a TSS-assisted restore. Won’t work for iPad2 5.x blobs (or iPhone4S at all) until a bootrom-level exploit is out

top line now shows whether (and where) a redsn0w update is available, or if the version being run is the latest. Uses DNS TXT record to alleviate any concerns about snooping

no 5.1 beta support at this time (major apps like Cydia are not yet compatible)

@pod2g has been doing a great job porting his 5.x untether…check his blog for updates!

Owners of newer 3GS iPhones must not flash the iPad baseband. The iPad baseband will not work on 3GS iPhones built later than 2011 week 35. You have a week 35 or later device if your serial # starts with xx135.

While this is good news and makes the process a lot smoother, I know many of you are still holding out for untethered. Hopefully that'll be next.

The iPhone Dev-Team has gone ahead and updated UltraSn0w as planned with full support for unlocking your iPhone 3G, 3GS and iPhone 4 under iOS 5.

UltraSn0w 1.2.4 is available in Cydia now and supports iPhone 3G and 3GS basebands 04.26.08, 05.11.07, 05.12.01, 05.13.04, and 06.15.00. Remember, If you're trying to unlock your iPhone 4, the only baseband currently supported by UltraSn0w is 01.59.00.

You'll need to jailbreak your iPhone running iOS 5 before getting started. It's possible to preserve your baseband on the iPhone 4 while still updating to iOS 5 by using the latest version of Redsn0w for Mac (a Windows version is in the works).

Got any questions? Just jump into our jailbreak and unlock forums to help you along the way!

Source: iPhone Dev-Team

iOS Dev-Team member MuscleNerd says that UltraSn0w will be updated as soon as tomorrow with support for iOS 5, allowing iPhone users to unlock their device to use on unsupported carriers.

will coordinate ultrasn0w iOS5 compatibility update to come out after a planned MobileSubstrate update tomorrow

Keep in mind that the UltraSn0w unlock will only work for 01.59.00, 05.11.07, 04.26.08, 05.12.01, 05.13.04 and 06.15.00 basebands, so if your baseband differs from these you won't be able to unlock your iPhone using UltraSn0w until the Dev-Team finds a new exploit.

It's currently possible to upgrade your iPhone to iOS 5 while preserving your baseband using the current version of RedSn0w, which you'll also need to jailbreak your iPhone before starting.

Will you be unlocking your iPhone with UltraSn0w?

Source: MuscleNerd

iPhone Dev-Team member MuscleNerd has gone on the record stating a port of Siri to other iOS devices outside of the new iPhone 4S will require piracy, and likely won't ever see the light of day as a consequence.

Anyone hoping for a "port" of Siri from iPhone4S: pending a very low-level A5 exploit, it likely can't be done without piracy

(only way to extract Siri files from iPhone4S filesystem without pirating is to have the main FS keys, requiring low-level exploit)

Essentially, the only way to get Siri working on other iOS devices would be to take the required files from an iPhone 4S and transfer them onto the other device manually. It's also possible that Apple may flag such devices since Siri talks to Apple's servers to complete certain tasks.

On the other hand, piracy in the jailbreak community has been running rampant lately, so it's also possible we could see this come from other, less ethical jailbreak developers.

Source: MuscleNerd

It hasn't even been a full day since Apple seeded iOS 5 GM to developers, but the iPhone Dev-Team has already updated Redsn0w to fully support the gold-master release.

redsn0w has been updated to 0.9.9b3 to auto-detect iOS5 GM firmware. Remember: it’s still tethered for all devices except for iPhone 3GS with old bootrom. If you don’t use redsn0w to “Just boot” at power up, all jailbreak apps (and even some native ones like MobileSafari) will fail to launch.

If you already jailbroke the GM by pointing an older redsn0w at the beta7 IPSW, there’s no need to re-run the full jailbreak step again…just use this newer one to make the tethered boot easier

The following devices are supported under Redsn0w 0.9.9b3a.

• iPod touch 3G
• iPod touch 4G
• iPad 1
• iPhone3GS
• iPhone4 (GSM)
• iPhone4 (CDMA)

It's important to note that this does not support unlocking your iPhone, and those requiring an unlock should stay away from iOS 5 completely until an unlock is available. Additionally, this is still a tethered jailbreak (unless you're on an older bootrom) which means you'll have to plug it into your computer each time a reboot is needed.

We'll have a full how-to up shortly to help you through the steps of jailbreaking under iOS 5 GM.

Source: iPhone Dev-Team

We're getting a lot of questions from Jailbreakers and would-be Jailbreakers both on iOS 4.x and iOS 5 so we figured it was time to once again take a look at the state of iPhone, iPod touch and iPad Jailbreak. Here it is:

If you still have an untethered Jailbreak on iOS 4.3.3 or below and want to stay untethered, don't upgrade just yet.

If you've already updated and you currently have a tethered jailbreak on iOS 4.3.5, you'll probably have to stay tethered until the release version of iOS 5 drops this October.

Why not? Because if they release an untethered Jailbreak based on an exploit in iOS 5 beta, Apple could easily patch it in the next beta and it's back to square one.

I'm currently on iOS 5 beta and personally can't wait to have my jailbreak back. iOS 5 is a major improvement but I still miss apps like Mail Enhancer and SBSettings. I'd much rather wait and have an untethered jailbreak for the iOS 5 final release than a quick fix now that Apple kills off during the beta.

If you're currently running iOS 5 beta 5 but just can't live without your jailbreak, the Dev Team has already released RedSn0w beta 5. The only catch is, it's tethered, just like the previous beta versions of RedSn0w for iOS 5.

Be advised that not all jailbreak apps and tweaks have been updated to support iOS 5. If you're alright with running tethered and don't mind a few bugs here and there, follow along for a quick walkthrough.

By this point, almost anyone jailbreaking is already familiar with RedSn0w and how it works. It's no different this time.

Devices Supported

• iPod touch 3G
• iPod touch 4G
• iPad 1
• iPhone3GS
• iPhone4 (GSM)
• iPhone4 (CDMA)

And I can't say this enough times, if your device is not listed above, please do not attempt to jailbreak it on iOS 5!

What you need

• iOS 5 beta 5 IPSW from Apple's Developer Portal
• RedSn0w 0.9.8b5 - Mac Link, Windows Link

After you have iOS 5 beta 5 installed on your device and your version of iTunes upgraded to 10.5 beta 5, follow the steps below to jailbreak.

1. First launch RedSn0w.



2. It should ask you to navigate to a firmware file. Simply navigate to the iOS 5 beta 5 firmware file instead of beta 2.
3. Once you click next, RedSn0w will take a minute to do it’s thing. You should see a patching kernel message and that Redsn0w successfully recognized your firmware.



4. Next select the options you’d like RedSn0w to perform. I typically only select Install Cydia. It’s worth noting that this is where you will perform a tethered boot if needed as well. You will just select Just boot tethered for now if you need to do this or your device reboots or dies.



5. Redsn0w will now walk you through putting your device into DFU mode



6. After you’re successfully in DFU mode, simply let Redsn0w do its thing and you’re done!

That's it! The process is pretty much the same as the first time around. But if you do run into problems or have questions, make sure you check out our TiPb Jailbreak Forums. We've got tons of great members more than ready and willing to help!

Tips of the day will range from beginner-level 101 to advanced-level ninjary. If you already know this tip, keep the link handy as a quick way to help a friend. If you have a tip of your own you'd like to suggest, add them to the comments or send them in to dailytips@tipb.com. (If it's especially awesome and previously unknown to us, we'll even give ya a reward...)

Just get iOS 5 beta 2 and already wondering how to Jailbreak it? We recently showed you how to jailbreak iOS 5 beta 1 with Redsn0w. Fortunately, the process for beta 2 isn't much different. You'll simply need to use the beta 1 IPSW in order to jailbreak.

As always, betas are already buggy to begin with, and iOS 5 is no exception. The Dev-Team and many jailbreak devs are really only encouraging developers to jailbreak iOS 5 beta as of now. So if you are a developer (or a ninja who is afraid of nothing), follow along for a short walk-through.

Devices Supported

• iPod touch 3G
• iPod touch 4G
• iPad 1
• iPhone3GS
• iPhone4 (GSM)
• iPhone4 (CDMA)

And I can't say this enough times, if your device is not listed above, please do not attempt to jailbreak it on iOS 5!

What you need

• iOS 5 beta 1 IPSW from Apple's Developer Portal
• Redsn0w 0.9.8b1 - Mac Link, Windows Link

After you have iOS 5 beta 2 installed on your device and your version of iTunes upgraded to 10.5 beta 2, follow the steps below to jailbreak.

1. First launch Redsn0w.



2. It should ask you to navigate to a firmware file. Simply navigate to the iOS 5 beta 1 firmware file instead of beta 2.
3. Once you click next, Redsn0w will take a minute to do it’s thing. You should see a patching kernel message and that Redsn0w successfully recognized your firmware.



4. Next select the options you’d like Redsn0w to perform. I typically only select Install Cydia. It’s worth noting that this is where you will perform a tethered boot if needed as well. You will just select Just boot tethered for now if you need to do this or your device reboots or dies.



5. Redsn0w will now walk you through putting your device into DFU mode



6. After you’re successfully in DFU mode, simply let Redsn0w do its thing and you’re done!

That's it! The process is pretty much the same as the first time around. But if you do run into problems or have questions, make sure you check out our TiPb Jailbreak Forums. We've got tons of great members more than ready and willing to help!

Tips of the day will range from beginner-level 101 to advanced-level ninjary. If you already know this tip, keep the link handy as a quick way to help a friend. If you have a tip of your own you'd like to suggest, add them to the comments or send them in to news@tipb.com. (If it's especially awesome and previously unknown to us, we'll even give ya a reward...)

Miss your tweaks and wondering how to Jailbreak iOS 5? As long as your okay with a tethered jailbreak for now, you can get your jailbreak on again thanks to Redsn0w 0.9.8b1.

It's worth noting first that the Dev-team is calling this jailbreak a beta. Which means there could (and probably will be) quite a few bugs. Also keep in mind that a majority of jailbreak apps have not been updated to support iOS 5 as of yet. So just be forewarned. If you're okay with being tethered and dealing with a few bugs, click through for a quick walkthrough!

Devices supported

• iPod touch 3G
• iPod touch 4G
• iPad 1
• iPhone3GS
• iPhone4 (GSM)
• iPhone4 (CDMA)

If your device is not listed above, please do not attempt to jailbreak your device. Yes, iPad 2 owners, I'm looking at you!

1. First you will need to download Redsn0w - Mac Link, Windows Link
2. Next you will need to make sure you have the iOS beta 1 firmware file from the Apple Developer Portal or wherever else you choose to find it.

3. Launch Redsn0w. You should be asked to navigate to the firmware file from the previous step. Select it and click next.

4. Once you click next, Redsn0w will take a minute to do it's thing. You should see a patching kernel message and that Redsn0w successfully recognized your firmware.

5. Next select the options you'd like Redsn0w to perform. I typically only select Install Cydia. It's worth noting that this is where you will perform a tethered boot if needed as well. You will just select Just boot tethered for now if you need to do this or your device reboots or dies.

6. Redsn0w will now walk you through putting your device into DFU mode

7. After you're successfully in DFU mode, simply let Redsn0w do its thing and you're done!

Have you jailbroken iOS 5 yet? If so, what has been your experience? Are your normal tweaks working for you or have you had more issues than usual? Let us know in the comments or in our TiPb jailbreak and unlock forums!

Tips of the day will range from beginner-level 101 to advanced-level ninjary. If you already know this tip, keep the link handy as a quick way to help a friend. If you have a tip of your own you'd like to suggest, add them to the comments or send them in to news@tipb.com. (If it's especially awesome and previously unknown to us, we'll even give ya a reward...)

As you can see from the tweet above, the Dev Team has updated their popular PwnageTool to support an untethered jailbreak under iOS 4.3.2. You now have the option of using either PwnageTool or redsn0w to jailbreak iOS 4.3.2.

We have experienced some issues with jailbreaking iOS 4.3.2. Some users say they have had issues as well while others are perfectly fine. I'm personally staying on 4.2.1 for now since I have no compelling reason to upgrade.

The updated version of PwnageTool is available at the link below. It supports the following devices -

• iPhone 3GS
• iPhone 4 (GSM)
• iPod touch 3G
• iPod touch 4G
• iPad First generation

So iPad 2 users and Verizon iPhone users need not apply. And a final note to unlockers - you should only ever use a custom IPSW when upgrading firmware. While ultrasn0w will unlock your iPhone running iOS 4.3.2, that only applies if you are running an older baseband. So never restore to a stock firmware in iTunes because that will not preserve your baseband! Check out more details and grab your download from the link below!

[Dev-Team Blog]

redsn0w 0.9.6rc13 is here and it brings with it the promise of an untethered Jailbreak for iOS 4.3.2 devices including iPhone 3GS, iPod touch 3 and 4, and iPad 1. iPhone 4 will be coming as soon as a fix is made, and iPad 2 is still waiting on a new exploit (yes, we're sad too.) According to the Dev-Team:

Only a few weeks after the 4.3.1 untether created by @i0n1c was released, Apple pushed out firmware 4.3.2. Thankfully, it appears Apple didn’t have a chance to fix the hole used by @i0n1c’s untether, so he ported his code over to 4.3.2’s kernel. Today’s redsn0w has been updated to include it.

Check out our complete iOS 4.3.2 untethered Jailbreak guide (updated from our 4.3.1 since the process is essentially unchanged) and if you need any help jump on into our Jailbreak Forum.

Are you apart of #teamjailbreak? Are you updating to 4.3.2 and giving the new redsn0w a try? Let us know how it works for you!

UPDATED: iPhone 4 (AT&T/GSM) is good to go!

redsn0w rc14 includes the fixed i4 untether from @i0n1c. You can re-run redsn0w rc14 right over the tethered rc13b to transform the i4 JB into an untethered one.

[Dev-Team, thanks @daveizzle!]

The Dev-Team will be releasing the official tools for an untethered iOS 4.3.1 jailbreak tonight. Both Redsn0w and PwnageTool will be available within the next 24 hours and will support all iOS devices including the iPhone 4 and latest generation iPod touch, but will not yet be compatible with the iPad 2.

Over the weekend the Dev-Team let the world know that if #sundayisfunday started trending on Twitter they'd release an untethered jailbreak shortly after. It has since been confirmed that they're planning to release the official tools at GMT-8, which should translate for us in the US and Canada to the following times:

• 12AM Pacific
• 1AM Mountain
• 2AM Central
• 3AM Eastern

It's been a long time coming, but it looks like we'll finally be able to jailbreak iOS 4.3.1 without needing to tether to a PC or Mac each time a reboot is required. We're not sure when a jailbreak will be out for the iPad 2, but we've heard rumblings of something in the works from Comex. The Dev-Team may hold out on an iPad 2 jailbreak to make sure Apple doesn't patch hardware vulnerabilities with the iPhone 5, but with rumors that we won't see the iPhone 5 in June this year they may end up releasing a tool sooner rather than later.

Will you be jailbreaking after Redsn0w and PwnageTool are released tonight? Let us know in the comments!

[iphonedownloadblog]

Following up on earlier news that an untethered exploit was handed over to the Dev-Team from developer Stefan Esser, prominent Dev-Team member @MuscleNerd tweeted that the exploit is working and they're hammering out remaining jailbreak issues at this time.

well @i0n1c's untether is solid! Just working out overall 4.3.x JB issues and Cydia

It looks like we could see a working untethered iOS 4.3 jailbreak tool released soon based on the progress update, but remember it won't work with the iPad 2 unless a new vulnerability is found and implemented (Apple patched the userland exploit found by Comex in 4.3.1).

Do you think we'll see a jailbreak released for 4.3 soon? Sound off in the comments below!

Will I be able to Jailbreak iPad 2 running iOS 4.3 when it launches? That's a question on a lot of user's minds. We already know the jailbreak community is working towards an iOS 4.3 jailbreak. What we "do" know is that a tool won't go official until iOS 4.3 is out of beta and in the hands of consumers. Most of the reason behind this is so Apple doesn't patch it in a last minute update.

Where the iPad 2 is concerned, it's anyone's guess whether or not the solution they're currently working towards will definitely jailbreak the iPad 2. According to @p0sixninja, one of the main contributors of greenpois0n, they are hoping the SHAtter exploit will still be a viable solution on the iPad 2 as well.

While we wait for a definitive answer, check out our massive jailbreak guide and mingle with other fellow jailbreakers in waiting over in our TiPb jailbreak forums.

I've been receiving a lot of questions about the state of current jailbreaks, especially when it comes to the just released iOS 4.3 beta and the Verizon iPhone (demo models ran iOS 4.2.5). The jailbreak community is working on a jailbreak but they have stated it will not come out as long as iOS 4.3 is in beta. There's a good reason for this. Most jailbreakers already realize it's a cat and mouse game with Apple.

If one of the dev teams has an exploit, they don't want to burn it. If they release it now, Apple can patch it before the final release and it's of use to no one. Unlocker @MuscleNerd isn't planning on releasing an unlock until iOS 4.3 is official, and for good reason. Here's what he has to say -

Official iPhone unlock statement: no unlock will be released until after 4.2.5 or official 4.3 (whichever is last) is out

I can't imagine a general jailbreak tool being any different. No point burning exploits for no good reason. So on that front, just be patient. And as always, don't upgrade right away if you plan on jailbreaking.

In the mean time, you can make sure you save your SHSH blobs if you're already jailbroken. You can also read through our jailbreak starter's guide if you're curious but new to the jailbreak scene.

Click through for a current list of firmwares and what your jailbreak options are under each firmware. We've also got some links handy after the break to walkthroughs explaining each method.

• iOS 4.1 and below - greenpois0n, limera1n, Pwnagetool
• iOS 4.2 and above - redsn0w

Please note that redsn0w is currently a tethered jailbreak. There is a redsn0w beta out that allows for an untethered jailbreak but it's still got issues. I personally recommend staying on 4.1 until an easier (less buggy) solution is available if you can.

Keep in mind you always need to check your device type against each of these methods to make sure it's compatible. Click through to the links for more detailed descriptions of each and what they can offer you. If you still have questions, make sure to check out the TiPb jailbreak forums.

With Comex not able to finish his planned iOS 4.2.1 untethered Jailbreak in time for Christmas, MuscleNerd and the iPhone Dev-Team are pushing ahead with a redsn0w "backup plan" and are looking for a few good, qualified testers.

To keep things manageable, this will be a Mac-only test program. We also request that any volunteers NOT need the ultrasn0w unlock (in case things go very wrong).

Right now, the “backup plan” requires that you have the 4.2b3 IPSW on your Mac, and that Cydia has your 4.2b3 SHSH hashes. Please don’t pirate that 4.2b3 IPSW! (We’re also working on a way that this technique might apply to all those with 4.1 IPSWs, but that’s not the first goal right now.)

If they're talking to you, follow @redsn0w_testers on Twitter for more information, and send them feedback via the link below. Meanwhile, let us know how it works for you!

(If you're not sure what any of this means, check out our Jailbreak starters guide first!)

[iPhone Dev-Team]

PwnageTool 4.1 was recently released and a lot of jailbreakers have been waiting for this one.  The main difference between some other methods and PwnageTool is that it preserves your baseband in most cases.  Meaning for unlockers, they'll still be able to safely upgrade and keep their unlock.  We've covered how to jailbreak iOS 4.1 via limera1n and how to jailbreak iOS 4.1 via greenpois0n, and now we'll look at how PwnageTool 4.1 differs and walk through this process as well.

PwnageTool 4.1 will jailbreak the following devices:

• iPhone 4, 3GS, and 3G
• iPod Touch 4G and 3G
• iPad
• Apple TV 2nd Generation

As usual, we take no responsibility for what you may or may not do to your phone.  If you're okay with that, jump through for a regular and video walkthrough!

First you'll need to download the torrent for PwnageTool 4.1 from the Dev-Team blog.  There is an official and a couple mirrors.  Once you've got it all unpacked, continue on.

When you first launch PwnageTool, you'll be asked to select your iDevice model. You'll also notice across the top you'll have two modes, expert and simple.  Simple will install Cydia and a few common addons.  Expert will let you choose what custom applications and utilities you'd like to install.  For this example, we'll just use simple mode on an iPhone 3GS.  If you guys have questions or need help with expert mode, jump over to our jailbreak forums and we'd be glad to help you out.

After you've selected your iDevice, you should click Next and be presented with a screen that asks you to select your firmware version.  PwnageTool is normally pretty good about bringing up the correct one, but if for some reason it doesn't, you can always click browse and navigate to your chosen firmware version.  On the Mac, iTunes puts your firmware under Library\iTunes.  My iTunes has a mind of its own and sometimes firmware doesn't show up. I use the following site for past and present firmware versions quite often:  iPhone Firmware Versions - Past and Present

Just make sure you select the correct firmware if more than one comes up.  You'll then receive this message followed by one asking you if you activate normally.  If you're unlocked, select no. Just follow all the prompts through and PwnageTool will then begin building a custom .ipsw for you that'll save to your desktop.

Once that's done, PwnageTool is going to walk you through putting your phone in DFU mode.  If you're unsuccessful the first time, that's ok, it'll let you keep trying until you get it.  After that, you'll simply open up iTunes and alt + option click on restore and navigate to your custom firmware on your desktop.

And that's it! Once you're iDevice reboots, you should be jailbroken!

The Dev Team has commented on Geohot's multiple iOS device jailbreak, limera1n, released yesterday. A bootrom-level Jailbreak for iPhone 3GS (2009/2010), iPhone 4 (2010), iPod touch 3 (2009), iPod touch 4 (2010), iPad (2010), and theoretically Apple TV (2010). which was released yesterday and it's fair to say it hit the community like a small yield nuclear blast:

Limera1n uses a different exploit than SHAtter, and in fact covers more devices. Although some may question geohot’s dramatic and competitive style, he obviously does have considerable skill pulling this together in just over a day (although he’s had the underlying exploit for months). Credit also goes to @comex, who provides the untethered aspect of limera1n via another one of his growing list of kernel hacks.

The release of limera1n has (hopefully!) averted the burning of 2 bootrom holes at once (both his and SHAtter). Releasing SHAtter now would be a complete waste of a perfectly good bootrom hole in light of limera1n, and so it can be held until Apple closes limera1n’s hole. While there’s no guarantee that Apple won’t also close SHAtter by then, it provides a ray of hope for devices after Apple’s bootrom respin. Meanwhile, look for an alternate implementation of the limera1n exploit in greenpois0n (and possibly other tools), where it should undergo more testing too.

While exploits are how Jailbreak payloads are delivered, they're also security risks that enable any other type of payload delivery -- including malware if bad guys decide to go after iOS. That means Apple has to patch them either in new firmware or in hardware revision that fix more base-level exploits.

The Dev Team also points out limera1n doesn't appear to be well tested or polished yet, but that Geohot has a history of iterating and improving his releases quickly.

Check out our Jailbreak Forum for help and more information on limera1n and other Jailbreaks. And let us know, do you like this newly competitive, somewhat dramatic Jailbreak landscape or would you rather the various individuals and teams coordinate things better?

[Dev Team]

Using a publicly released version of the Apple TV iOS 4.1 firmware, the Dev-Team has decrypted its keys, the first step necessary to a Jailbreak, which could very well be on its way. That's less than 24 hours after the iPod Touch 4G fell victim to the same SHAtter exploit.

UPDATE #1: It’s looking like SHAtter is going to be the gift that keeps on giving. Even though the new AppleTV isn’t yet in people’s homes, the firmware is available on Apple’s normal public distribution servers and SHAtter has been used to decrypt its keys!

Cydia apps? 1080p output? At this point anything seems possible.

A way to control the UI absent finger-on-screen multitouch would still have to be worked out for standard iOS apps to function, but getting Hulu, PC to AppleTV streaming for video formats like DIVx and MKV, and Mobile freakin' Safari up there would all be excellent starting points.

Does the idea of a Jailbroken Apple TV make it more appealing to anyone? And what would you want to see running on it?

[Dev Team]

This is an official entry by Farbod21 in TiPb’s next top blogger contest. Think you have what it takes to join Team TiPb? Bring it!

iPhone Dev Team has put @pod2g’s SHAtter exploit into actual use with it's first application as a jailbreak tool on the iPod touch 4 [Video Below]. Right after Apple released iOS 4.1, Former Chronic Dev Team member pod2g announced his development of a low level bootrom exploit that would be difficult to patch via a software release.

Since then, both Chronic Dev Team and iPhone Dev Team have been hard at work to implement that exploit into a usable jailbreak tool. The next domino has fallen as they have been able to use this exploit via a beta version of their PwnageTool on the iPod Touch 4G.

Although PwnageTool was a useful first test of a full iPod 4G jailbreak via SHAtter, it’s really overkill compared to the faster tools being developed. Its main use in PwnageTool will be for those with iPhone4’s, to allow updates while preserving the baseband and ultrasn0w carrier unlock. In any event, this is another exciting time for iPhone and iPod touch users…the cat and mouse game continues!

While many wait impatiently for the next jailbreak tool to be released, this news is reassuring and will give us something to look forward to in the weeks ahead. How long until the iPhone 4 falls to the likes of the Dev Teams? Tell us what you think below...

[Dev Team Blog]

This is an official entry by Farbod21 in TiPb’s next top blogger contest. Think you have what it takes to join Team TiPb? Bring it!

There seems to be a fake jailbreak tool circulating at the moment that is being called "greenpois0n" that is claiming to be using the SHAtter exploit. Now this would all be fine and dandy except for the simple fact that the SHAtter jailbreak exploit has yet to be released by the Chronic Development Team. According to security researcher Costin Raiu at the Kapersey Labs, all that greenpois0n is doing is stealing users passwords.

We've seen scams similar to this before and we will more than likely see them again in the future so please remember if you see any website or program that claims to be capable of jailbreaking a iOS device running 4.0.2 or above, it is highly likely a scam or something much more damaging unless of course if it were to be released by Dev Team or Chronic Development Team themselves.

For more jailbreaking information be sure to visit our jailbreak and unlock forum.

[Ars Technica]

Several tweets this morning are indicating that a jailbreak for iOS 4.1 could come sooner rather than later.  Could there be any better news you ask? Why yes! Jailbreaker @pod2g as well as other sources are indicating that this "particular" exploit would require Apple to flash to a whole new bootrom in order to fix it.

What does this mean for jailbreakers?  It means they run less of a risk of accidental updates and what-not being so catastrophic.  Apple can't fix this exploit by simply issuing a software update.  It would require a flashed version of the bootrom out of the factory.  We may eventually see new iPhone 4s shipped with newer bootroms but any older ones would remain jailbreakable, regardless of any software update Apple may issue.

So if you're like me and lost your jailbreak for 4.1 (darn prox sensor!), you'll soon be able to have jailbreak goodness back again.  How many of you still plan on jailbreaking and how many of you think iOS 4.x gave you what you needed?  For me, notification systems are still a valid reason to jailbreak.  What about you?

Update: A source  BGR was in contact with has now stated that a flashed bootrom would not be sufficient.  A whole new processor revision would be necessary. Jailbreakers rejoice!

[via BGR]

The iOS Dev-Team, the folks behind a lot of the Jailbreak technology, have issued an Admiral Ackbar-style warning to Jailbreakers and unlockers about the impending iOS 4.1 update -- stay away for now:

This time of year there are lots of new iPhone owners, and not everybody knows that accepting new iOS updates is the surest way to lose your jailbreak and/or unlock. While those of you who have Cydia or TinyUmbrella backups of your FW hashes will always be able to get back to 4.0.1 if you make this mistake, this doesn’t hold for unlockers. There’s currently no known way to revert your baseband — if you update your baseband you’ll lose the ultrasn0w unlock, possible forever.

On the plus side, sounds like a safe, ultrans0w-friendly Jailbreak upgrade path for 4.1 is in the pipeline. Maybe a clean 4.1 Jailbreak as well?

The iPhone Dev-Team will not release a jailbreak for iOS 4.0.2/3.2.2. And that means if you purchase a new iPhone 4, which is currently shipping with iOS 4.0.2, you are out of luck in terms of jailbreaking. It is a never ending cat and mouse game between Apple and the jailbreak community and for current iOS software, the Dev-Team are choosing to sit on the side line and for good reason.

"No, there won’t be. FW 4.0.2/3.2.2 was only released to fix the jailbreakme hole. With FW 4.1 still in its beta stages, it makes no sense to escalate the “cat & mouse” with Apple for FW updates that only fix the jailbreak holes. To quote WOPR, “the only winning move is not to play”."

They do go on to say that a future 4.1x FW jailbreak may be compatible with 4.0.2/3.2.2 but that it will be highly unlikely. For more jailbreak chatter be sure to visit our iPhone Jailbreak and Unlock forum.

[Dev-Team blog]

Those of you looking to break your iPhone 4 free from it's carrier lock have less than 48 hours to wait as iPhone Dev Team member planetbeing announced late last night on Twitter that the unlock is just around the corner. It was just yesterday that Comex released his new web-based jailbreak but not without some issues. Those issues consisted of some users losing MMS and FaceTime. Since then those issues have been cleared up and if you give the jailbreak a try you should be good to go, at least until Apple releases a new firmware update which will break this jailbreak method.

How many of you are chomping at the bit to get a hold of this iPhone 4 unlock and what carrier are you looking to be free from?

Geohot has updated his blog to let us know that he's apparently jailbroken his iPhone 4 in less than one day.  There's a little caveat though -- he's said he probably won't release it.  Well I guess my question is, what's the point in posting it up then?  Most people are familiar with Geohot's blackra1n and purplera1n jailbreak tools.  They were simple and downright easy.

He also took the time to mention the rumors of limera1n.com -- basically stating that it's no more than a waterdrop on the web and he's never mentioned it before, so don't read too much into it.  My opinion? A picture of Cydia on an iPhone 4 is pretty unconvincing.  He certainly has the skills and the record to find an exploit and jailbreak iPhone 4, but why no video, and why no seeming interest in releasing it?

To say the least, the reason for the post is confusing.

As for now, we've got PwnageTool 4.0.1 for iOS4, but iPhone 4 users are going to have to wait a while longer.  I guess we'll see what the Dev Team and Spirit developers come up with.

[ Geohot]

Alright kiddies, you've been asking for it, so here it is.  The Dev Team has officially announced their jailbreak and unlock for iOS4.

There's a few caveats though, you must:

• Own a Mac (if you're a 3GS user, there is a windows solution for 3G users)
• NOT have jailbroken previously with Spirit
• Have a previously jailbroken device

Questions about upgrading or whether your device is okay? Check out the Dev Team's blog before doing anything! And if you're wary, we'd recommend staying away. I'd assume a PC version will follow.  When that will happen is anyone's guess.  Have questions or concerns? Leave them below.

[via Dev Team]

The iPad 3G + Wi-Fi was released this past Friday and on that very day Dev Team member MuscleNerd showed the world it was jailbroken. The new iPad proved to be vulnerable to comex’s “Spirit” jailbreak. Unfortunately, the software is not yet publicly available but it should be released soon.

Any of our readers getting a itchy trigger finger to jailbreak you iPad? Sound off in the comments!

MuscleNerd’s video after the break!

[comex, Dev-Team Blog, MuscleNerd]

If you have a itchy trigger finger when it comes to updating the software on your iPhone then this latest release of the Dev-Teams PwnageTool for Mac OS X is just for you. Now unless you care to have have a supposed more accurate battery indicator there really is no reason to upgrade to the 3.1.3 software but never the less there will be those of you who absolutely feel the need to upgrade.

Like always there are a ton of different scenarios that can play out here depending on your device model and current firmware so check out the Dev-Teams blog in the link below to get the full details and as always, proceed with caution. If you need some help, visit our dedicated forum for jailbreaking and unlocking.

[Via Dev-Team Blog]

iPhone Dev-Team member, MuscleNerd has announced that redsn0w 0.9 is officially out of beta and is now available in both Mac and Windows flavors.

"redsn0w 0.9beta3 results were good, may as well take it out of beta: http://is.gd/7ppQO (new: ipt3G and IPCC tethering)"

This version of redsn0w supports all iPhone and iPod touches running the 3.0 and 3.1.2 firmware. If you need to perform a carrier unlock on your iPhone 2G, redsn0w can do that for you but for the 3G and 3GS you must use Cydia to install blacks0w for baseband 04.26 and ultrasn0w for baseband 05.11. And yes, for late model 3GS devices you are still limited to a tethered jailbreak.

For the full details and download links be sure to check out the official redsn0w 0.9 wikee.

The iPhone Dev-Team is back, this time with the first beta of RedSn0w 0.9 for Mac and Windows. Version 0.9 will allow for jailbreaking, unlocking, and customizing of the iPhone OS 3.0/3.1.2 software. It is important to note that this beta supports every iPhone and iPod touch with the exception of the iPod touch G3. (That will be supported after the beta period is over.)

For quite some time now blackra1n has been the most-used tool to get your jailbreak on but the way this new version of redsn0w works, could that change? You see this software uses the original Pwnage bootrom exploit from iPhone 2G, iPhone 3G, and iPod 1G. What this means is the only way for Apple to combat it is via a hardware change. However, for the iPhone 3GS and iPod 2G running 3.1.2, things are a little different as they still use the USB exploit that is said to be going away with the iPhone 4.0.

Due to some last minute forum software changes, the Dev Team isn't promoting the release yet, but if you'd like to check it out for yourself, the Mac version can be downloaded here while you can grab the Windows version here. (We'll update with a link to the Dev Team post when it goes live).

[Via iClarified]

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.

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!]

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.

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.

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!

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?

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!

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!

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.

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?

George Hotz has taken it upon himself to create a new iPhone 3GS unlocking solution which he calls purplesn0w. It seems the original iPhone hacker and creator of the jailbreak software purplera1n, was once again not happy with the Dev Teams software, this time it was their unlocking tool, ultrasn0w.

First off, what is purplesn0w? It's a soft unlock for your 3GS that I'd actually use day to day. It's not a daemon that takes any resources, and it doesn't add a task to your baseband. It's very close to a true unlock. All it does is patch three files, CommCenter, lockdownd, and your wildcard activation plist (which you need, activate w at&t sim first, no hacktivation support yet). That's it, no other files are installed.

So as you can see Hotz needs to do some more tweaking to get purplesn0w in pristine full working condition. If you do choose to use this software now be prepared to jump thru a few hoops such as having a legitimately activated AT&T sim card. On the bright side - Hotz claims that all of the issues people have had with ultrasn0w, such as Wi-Fi loss, battery fails, unlock fails, etc... are now gone if you use his unlock. If you can hold off for a day or two, do so as Hotz will release an update according to his twitter account.

For the full details on purplesn0w be sure to check out his blog. In the meantime, the competition is heating up between the Dev Team and Mr. Hotz. It's time to sit back with some popcorn and enjoy the show!

There has been so much jailbreak/unlock news as of late, it's enough to make your head spin. So let's end this week with two more tidbits of news from the community.

The Dev Team has released yet another demo video. This time they are showing off their iPhone 3GS 3.0 ultrasn0w unlock. Please keep in mind for the unlock to work you cannot update to 3.1 -- and yes, this includes the 3.1 beta.

It's pretty well known in the jailbreak community that the Dev Team delayed releasing their iPhone 3GS jailbreak for their own reasons. Well someone else has stepped up to the plate to bring you a iPhone 3GS jailbreak alternative. iPhone original hacker, George Hotz, has released purplera1n which is currently only available to Windows users (not Windows 7 though). Mac users don't panic, your version is coming soon!

In his latest blog post, not only does George explain the steps you must take to jailbreak your iPhone 3GS, he is pretty vocal on why he has decided to release purplera1n to the public.

Normally I don't make tools for the general public, and rather wait for the dev team to do it. But guys, whats up with waiting until 3.1? That isn't how the game is played. We release, Apple fixes, we find new holes. It isn't worth waiting because you might have the "last" hole in the iPhone. What last hole...this isn't golf. I'll find a new one next week. Also your purplera1nyday files ensure that you can always get back to a jailbroken state, so if you have it it's just a matter of tools.

Has this brought back to life a heated rivalry? It's time to sit back, relax, and jailbreak!

And as always, TiPb and staff take no responsibility for any bricking, failures, security risks, etc... that may occur during the jailbreak process. Proceed at your own risk!

[Not iPhone-friendly video -- we know -- please encourage them to post video to YouTube in the future. Thanks to everyone who sent these in!]

Right in time for iPhone 3.1, the iPhone Dev-Team has begun issuing their usual warnings about jailbreak/unlock users and new firmware updates:

ultrasn0w users must stay away from official 3.1 (incl. betas) until we release the tools for it, or you'll lose unlock!

Tempting as a tasty new beta may be, if you can't live without your hacked iPhone, don't hit that update button now, or any time before the iPhone Dev-Team has new, tested tools ready for you.

Once again, you've been warned!

[Via Twitter]

Sad day it is for all of you jailbreak fiends out there. The Dev Team has come out to let you all know not to expect a iPhone 3GS jailbreak solution any time soon. While they do have the software ready for prime time they are holding off on pulling the trigger to release it - for a few good reasons. The biggest reason being - Apple.

Apple is surely coming out with a 3.0.1 firmware release shortly. They need to fix ultrasn0w. They need to fix some UI issues. 3.0 is buggy and 3.0.1 is coming. We’re going to wait and see what 3.0.1 brings before figuring out the release date for our version of the jailbreak.

They also seem to be a bit worried about their exploit this time around and think Apple will definitely "fix" it rendering their software useless to people who purchase an iPhone after a fix is released.

Once the jailbreak is out, Apple will fix the iBoot-family bug we use to accomplish it. They will simply stop signing the old iBoots and only sign the fixed ones. If you bought your phone after Apple has done this, there’s nothing you can do…the jailbreak isn’t going to work for you.

So there you have it folks, all of you who are anxious for a iPhone 3GS jailbreak solution will have to exercise a bit of patience. For the full scoop head of to the Dev Teams blog.

The wait is over ladies and gentleman. The Dev-Team has released their latest software to unlock iPhone 3G's running the 3.0 software. Again, it is important to remember when a 3G S jailbreak application is released do not use Ultrasn0w with the iPhone 3G S.

To unlock your iPhone 3G 3.0 is as simple as jailbreaking your device, downloading Ultrasn0w via Cydia, and running the software. For full detailed directions be sure to check out the Dev-Teams blog.

Before you decide to jailbreak and unlock there are a few things you should know. If you do not know what you are doing - please do not attempt this as there is a possibility you can permanently damage your device. Regarding jailbreaking, remember most of the apps available will not work on 3.0 due to the developers not updating their apps yet. So be careful on what you install.

Want to learn more? Visit Jailbreak Central in TiPb forums.

NOTE: iPhone 3G S need not apply!

While I don't have anywhere near the midichlorians Jeremy has for all things Jailbreak, I can tell when the infamous iPhone Dev-Team has their game on:

redsn0w is an easy to use, multi-platform, multi-device jailbreaking and unlocking (iPhone 2G only) tool for the iPhone 2G (original iPhone), the iPhone 3G (but not the 3GS) and also the iPod touch (first and second generation). Currently it is available for Windows and Mac OS X (there are some issues using redsn0w with OS X PPC, please use an Intel Mac until we have this problem resolved).

They point out that that redsn0w provides similar functionality to Quickpwn, and provide more instructions in their full post.

As always, experts only and proceed completely at your own risk. If you don't understand something -- put your iPhone down and back away slowly!

If you need help, check out our iPhone Jailbreak Central forums.

Now before you get too excited let me just off by saying this jailbreak is not for Apple's latest hardware, iPhone 3G S. This is only for the iPhone 3G or iPhone 2G running the 3.0 software.

Now with that said, the Dev-Team has released the proper tool for Mac OS X users to jailbreak your iPhone 3G's running 3.0, PwnageTool 3.0. Be warned, if do not know what you are doing, don't attempt it!

This is the low down on our tools for use with the 3.0 firmware from Apple, read the whole post in full before attempting anything. Because of some bugs and unexpected changes this will be a multipart release, starting with the release of PwnageTool for Mac OS X. QuickPwn for Mac OS X and Windows will follow sometime soon, please don’t bug us about it, we are working flat out to get everything finished to release them.

So there you have it expert users. And for those less certain of their skills, more and more jailbreak options will be available to you in the near future. Sit tight and be patient.

Engadget Mobile brings word that the iPhone Dev-Team has shown off a working Jailbreak and Unlock -- now dubbed UltraSn0w -- via Qik video.

The Jailbreak and Unlock should be available on Friday, though TiPb's guess is it may not work on the new iPhone 3G S, since it took 6 months to unlock the iPhone 3G via yellowsn0w and longer for the 2nd generation iPod touch via redSn0w. We'll likely know more when the Dev-Team gets some quality time with the new hardware and figures out what, if any, new cats Apple has brought for the mice to game...

Just a little reminder for those of you who are waiting for the Dev-Team to unveil the 3.0 software unlock for iPhone 3G, there is a live demo tonight.

On Tuesday evening (just before the big Apple release) we’ll do a live demo of the yellowsn0w carrier unlock working on official 3.0 firmware. The actual link for the feed will be twittered by @MuscleNerd and also placed here when the feed starts. The demo should answer everything you need to know about the new yellowsn0w. But it’s good news for iPhone 3G unlockers everywhere.

Keep in mind this unlock will not work along with the iPhone 3G S hardware. It is noted they may or may not be working on cracking the latest Apple has to offer.

P.S. For the new iPhone 3GS, please don’t expect periodic updates about any progress we have or don’t have. Nothing gives Apple the upper hand like someone tweeting or blogging partial hack results.

The cat and mouse game continues...

Tomorrow is the start of WWDC and there are some people out there who truly believe Apple will official release the iPhone OS 3.0 software very soon. Whether or not it is released this week or within the next month, don't be so quick to pull the trigger on the upgrade button within iTunes if you are planning on unlocking your device. If you choose to update there is a high possibility that you will lose your option to unlock in the future. Don't want to listen to us, ok, will you take the Dev-Teams word for it?

you all paid lots of money for your iPhones, and so we know that if you are depending on a software unlock, this is a sensitive issue. It’s a very sensitive issue to us too, which is why we can’t say or release anything prematurely that could potentially compromise any 3.0 software unlock.

In other words, don't do anything until the Dev-Team releases any official unlock for the 3.0 software. Also something to keep in mind, which we've warned you about in the past, don't be fooled these fake wanna be Dev-Team websites that are out there.

We’re used to (though still aren’t happy about) less predatory websites, like quickpwn.com. That site (1) is not us. We don’t consult with them in any way (2) makes money from their Google hits (they’re usually near the top) (3) sometimes gives very very bad advice (like tweeting yellowsn0w users to use QuickPwn on 3.0 betas. Bad suggestion). (4) also owns yellowsn0w.net, another money making website.

For more information, be sure to check out the official Dev-Team blog. So there you have it folks, be careful out there.

Jeremy already passed along the warning from the iPhone Dev-Team on iTunes 8.2. In case you missed it, they told jailbreakers and potential jailbreakers NOT to install Apple's just-released iTunes update.

According to their latest Dev-Team Blog post, the reason seems to be:

It breaks your ability to use QuickPwn, PwnageTool, and iPhone Tunneling Suite (ssh over usb). We don’t think this is a deliberate breakage of these tools. It’s just that Apple has updated a low-level USB protocol that normally only Apple cares about (but jailbreakers care about).

Is Dev-Team working on a fix? Youbetcha, but they don't want to release anything further until iPhone OS 3.0 is final. This may annoy people who have the 3.0 beta, but legit developers probably have more pressing concerns than jailbreaking at the moment, and why would the Dev-Team waste their energy and tip their hand to Apple when the betas will likely keep changing every couple of weeks before release anyway?

Of course, the blogsphere now has another concern, since last week's announcement that the Palm Pre syncs with iTunes, likely by faking Apple's USB protocols to disguise itself as an iPod (see Daring Fireball's take on this as well). There have been two pre-release versions of iTunes 8.2, going back over a month, but the obvious question still becomes: will the iTunes 8.2 final release also effect the Palm Pre sync?

Dev-Team thinks it's possible:

It may actually break Palm Pre’s connection to the device (please give us feedback on this).

We think Palm's Jon Rubinstein -- who used to head the iPod division at Apple -- may just have compromising pictures of the iPhone taken during it's "bachelor" party the night before Macworld 2007 ... We mean, it's got to be something, right?

Today Apple officially released the latest version of iTunes (8.2). Anyone who is familiar with jailbreaking should be well aware that now is a time to wonder, will the cat and mouse game continue? It seems like it has but @MuscleNerd claims it is unintentional on Apple's part.

Today's iTunes 8.2 update changes the way your computer talks to the device. This affects things like QuickPwn and PwnageTool when they try to identify what's connected. Also, ssh over usb breaks due to same reasons. Fixes are in the works but for now avoid 8.2

So if you are planning on jailbreaking anytime in the near future, be sure to avoid this latest version of iTunes until the fix is made available to the public.

Stay tuned as TiPb will bring you the latest updates as they become available.

Good news for Mac OS X-based Jailbreakers! After having to resort to using powered USB hubs or patching in older versions of files to work around a bug in 10.5.6 that prevented DFU mode from being recognized, the iPhone Dev-Team dropped a note a Twitter to give 10.5.7 the all-clear:

The new 10.5.7 Leopard update is safe. In fact it's more jailbreak-friendly than 10.5.6, since the DFU-mode bug is gone.

So no nasty cat-and-mouse-game shenanigans this time around, and even a slight improvement over the previous -- unintentional -- round.

Only one thing left -- figure out what to do with all those now-redundant USB hubs...

(Via Jamesus)

The iPhone Dev-Team has posted a few words regarding Jailbreaking the 3.0 software:

Because there are so many beta releases, we couldn’t possible refine, test, and release both PwnageTool and QuickPwn for each of them. That’s why we’re waiting until the final release. You may have seen other “hijacked” versions of QuickPwn out there, but all of them are buggy, none of them work on OSX, and almost everyone who uses them reverts back to 2.2.1 (because none of the useful jailbroken apps (Qik, Cycorder, and others) work on 3.0 yet).

Now this does not mean you currently can not Jailbreak 3.0 because you can, it's just that the Dev-Teams software is not fine-tuned for the iPhone beta software. If you do decide to Jailbreak the 3.0 beta you will run into some issues. The biggest issue, as stated above, being a lot of the applications available via Cydia will not be compatible with 3.0. It is also important to note that if you ever want to unlock your iPhone 3G, you need to avoid the 3.0 software altogether unless and until the Dev-Team provides a safe jailbreak path.

So our advice to the Jailbreakers of the world: have some patience. When the final build of 3.0 drops sometime this summer you will be able to Jailbreak your iPhone 3G.

(The only way Apple could prevent a Jailbreak does not rest within the software, rather the hardware. As for Jailbreaking the next generation of iPhone, only time will tell, we are sure Apple will make it interesting...)

Hackers vs. hackers. FreeHacks vs. AdHacks vs. PaidHacks. Jeremy covered the state of iPhone piracy yesterday, and while the argument over apps rages, the Jailbreak and potential unlock sitch could become just as confusing. Witness the Dev Team's Cat. Bag. Mouse. post which warns against using "unofficial" (according to the Dev Team) versions of, er, the unofficial (according to Apple) iPhone jailbreaking QuickPwn:

THE MOST IMPORTANT THING ABOUT THE UNOFFICIAL QUICKPWN RELEASES IS THAT IF YOU USE THEM, YOU WILL KILL YELLOWSN0W, POSSIBLY FOREVER. That’s because QuickPwn, by its very nature, requires you to already have accepted Apple’s official IPSW, along with its baseband update. If you do that, you will (possibly forever) lose your ability to software-unlock your iPhone 3G.

As to what the Dev Team itself is up to... check out the rest of their post.

Anytime there's an update -- or in this case, even a new beta firmware for developers to test out months ahead of an update -- the iPhone Dev Team reminds Jailbreak users, especially those running unlocked using YellowSn0w to stop, breathe, and wait for the "all clear" before updating.

In this case, the Dev Team says:

If you find yourself with access to the 3G IPSW for 3.0 via the iPhone Dev Center program, and you are using yellowsn0w, do not update or restore to that official IPSW. You will lose yellowsn0w and find yourself unable to revert the baseband to get it back.

And for those wondering, yes the 3.0 OS is jailbreakable on all devices. It’s just those using 3G yellowsn0w that have to show some restraint and wait for PwnageTool to create a custom IPSW that avoids the baseband update.

No big surprise they can crack the 3.0 firmware, though Apple might still throw some curves their way in future betas or the final release. We're guessing the true next step in the cat and mouse game will be iPhone 2,1 hardware, which could prove as tricky, if not trickier, than the iPod touch 2,1 which took quite a while to get to RedSn0w...

(Thanks to everyone that sent this in!)

Today is a good day to be a iPod touch 2G owner. Particularly if you have been waiting for an untethered jailbreak method to appear. The Dev Team put up a post late last night on their blog:

The iPod Touch 2G is now another member of the “pwned for life” family. It has a fatal flaw in its bootrom that means you will always be able to pwn these devices no matter what firmware updates come along. This is the full, untethered jailbreak, something that iPod Touch 2G users have not had before today.

For more information about this iPod touch 2G jailbreak and to download the software you'll need, visit here. If any of you are feeling adventurous, be sure to let us know how it goes!

[Via blog.iphone-dev.org]

The illustri-notorious Dev Team has blogged about Jailbreaking iPhone OS 2.2.1, released by Apple earlier this week.

Simple version: You can now Jailbreak, if you haven't already upgraded to 2.2.1 via iTunes, are using a Mac, aren't affected by the OS X 10.6 DFU-mode bug, and -- if you want to keep using yellowSn0w for unlock -- are happy to spin your own custom firmware.

Complex version: involves closing the barn door -- see here.

(For community-based jailbreaking advice and support, please check out our Jailbreak Central Forum)

Hopefully an easier solution will surface when the Dev Team has spent more time hacking away at iPhone OS 2.2.1. Until then, the cat and mouse game continues!

So if you don't live under a rock you would have noticed that Apple released a iPhone/iPhone 3G firmware update this past Tuesday. TiPb then warned all of you jailbreakers/unlockers out there not to proceed with updating your firmware... Judging from the comments, some of you took heed to our warning, while others were not so lucky.

To get a better understanding of what is going on with this latest Apple firmware and why you should not update just yet, be sure to check out the video above from iPhone Dev Team member, musclenerd.

[Via blog.iphone-dev.org]

So if you are a Twitter user, and follow the Dev Team (@iphone_dev), you may have noticed an interesting early hour post. So it begins, all of the crazy rumors on what this new code word means. Rumors and speculation all set aside, our very own Rene, had a very good idea... iPod touch 2G Jailbreak perhaps?

It seemed like the iPod touch was being left behind ever since iPhone 3G was released. Most likely due to the Dev Team putting all of their effort into a iPhone 3G unlock. Which is very much appreciated and a good thing for all of you iPhone owners out there. For you iPod Touch owners out there, we've heard rumblings that redsn0w will drop on or around January 30. So sit tight for a few more weeks.

For more information about @redsn0w be sure to follow it via Twitter!

The cat and mouse game continues on!

[Thanks for the tips - Scott, jamesus, and Rene!]

The iPhone Dev Team is still hard at work on their beta, pre-release version of the yellowsn0w process which runs on Jailbroken iPhone 3G's to unlock the devices from their carriers. The latest, 0.9.5 is working for some folks right now, but others are still experiencing problems including the inability to make outgoing calls (signal drops off). If you're trying and failing, be sure to give the Dev Team your feedback.

In addition, the Dev Team is also girding themselves, and their code, to fend off those who violate the yellowsn0w (and pwnage) license and try to make a buck by re-selling the Dev Team's work to unsuspecting web surfers. Whether you can really go after someone for abusing the license on a unlocking process that is designed to let people abuse the license of locked products shows just how complicated both commercial and non-commercial protectionism and freedom movements have become.

If you're unlocked, or trying to unlock, let us know how it's going for you. If you have any opinions on the debate around freeing commercial hardware and commercializing free software, drop us a comment as well!

If you have been living under a rock for the past few months, you might not have heard all the talk about unlocking iPhone 3G. Well the time is officially here, the iPhone Dev Team has released the latest software unlock for iPhone 3G!!! It is only available on a Jailbroken iPhone 3G via the Cydia Installer and is to be used on the latest firmware with the newest baseband!

Dev Team update from their blog:

The unlock about to be released works exclusively with baseband 02.28.00. This baseband is provided by the latest firmware update (2.2) from Apple. You’ll need to upgrade to this release using iTunes and then use QuickPwn to activate etc. [...] Because it works on 02.28.00, it is available to everyone on the planet. This means we don’t need to unnecessarily expose holes in earlier basebands, which is an important concern.

So who will be the first to give this a try? If you do, be sure to comment and let us know how it goes!

While the Dev Team still hasn't released the final iPhone 3G software Unlock, they certainly aren't taking New Year off. In addition to squashing some last minute permission errors, they have an extra-special surprise for 2009:

The soft unlock has undergone many changes in the last two days. The most significant one: the soft unlock will now be only for baseband 02.28.00 (the most recent baseband).

Jeremy is keeping an eye on all the details and will be bring us word as soon soon as the Unlock is live.

So, even if it's a beta, who's going for it?

Jeremy posted this earlier in the month and linked to the video, and he'll be back again when the iPhone 3G Unlock goes live, but until then, we just wanted to remind everyone (who's never updated their iPhone from OS 2.0!) that today is supposed to be the day!

Well it is now official, the Dev-Team has updated their blog today to let you all know when the iPhone 3G software unlock will be released. Seems as if New Years eve is what they are aiming for.

• The target release date for the unlock is New Year’s Eve 2008.
• This unlock method is available to iPhone 3Gs that have 2.11.07 baseband or earlier, we did warn you.
• The unlock requires a jailbroken 3G iPhone.

Guess Times Square won't be the only massive countdown going on today!

For the first time ever, the complete iPhone Dev Team finally got together and met each other face to face. They gathered recently and gave a presentation at the Chaos Communication Congress in Berlin.

Keep in mind the video is 58 minutes long and they do go pretty deep but it is definitely a interesting thing to check out. My favorite part of the whole thing comes in around the 2 minute 30 second mark: there are 180 IP addresses inside Apple that the Dev Team have tracked who have "updated their quickpwn and pwnage tool on a regular basis".

Very interesting indeed.

[Via Gizmodo]

Ok, in case you have been missing all of the iPhone 3G unlock talk lately, the Dev-Team yesterday previewed their unlock software for all of us to see.

It will be available to anyone who wants it (and is still running the original base band!) on New Years Eve. Until then let the video above fill your craving! Enjoy!

[Via Blog.iPhone-Dev.org]

Well it is now official, the Dev-Team has updated their blog today to let you all know when the iPhone 3G software unlock will be released. Seems as if New Years eve is what they are aiming for.

• The target release date for the unlock is New Year’s Eve 2008.
• This unlock method is available to iPhone 3Gs that have 2.11.07 baseband or earlier, we did warn you.
• The unlock requires a jailbroken 3G iPhone.

Another bit of jailbreaking related news, a word of warning to all Mac owners: If you are planning on jailbreaking or unlocking your iPhone, TiPb suggests you put the Mac 10.5.6 system update on the back burner until the Dev Team comes up with a solution to the issue. Or you try the following work around:

We believe this behavior is due to a kernel bug not a specific countermeasure by Apple. Possible fixes are (try at your own risk!)

1. Replace the following plugin kexts from within IOUSBFamily.kext with the ones from 10.5.5 and then rebuild kextcache (if you don’t understand this, then you shouldn’t attempt it!)

   • /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext
   • /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriver.kext

2. Use a USB hub in-between the DFU device and the Mac and insert/reinsert the iPhone’s USB cable.

3. Use a PwnageTool created .ipsw on Windows! Oh the irony!

Again, take heed to their warning, if you don't understand what they are saying, Don't Attempt It!

[Via blog-iPhone-dev.org]

Disclaimer: This guide is for educational and entertainment purposes only. Neither TiPb nor the author take any responsibility for any problems/issues/bricking/etc. that may occur while using this or any software to modify your iPhone. Please be aware of what you are doing. If you're not sure, don't do it.

Note to New Macbook Owners - if you have a late 2008 model aluminum MacBook, MacBook Pro, or MacBook Air and have not previously Pwned your iPhone (under firmware 2.1 or earlier), the issues we blogged about previously mean you will have to use a different computer to Jailbreak 2.2.1. Sorry folks. If you have already Pwned under 2.1 or previous, then you can simply put your iPhone into recovery mode and restore with the freshly created IPSW. (If you don't understand what all that means, keep reading, or go to our Jailbreak Central Forum for help)

This applies if you have a locked iPhone 3G and you wish to update to 2.2.1 but preserve the iPhone’s current baseband software. Preserving the baseband will ensure that you can still use “yellowsn0w” the iPhone 3G unlock application. To upgrade your phone to 2.2.1 and preserve the state of the baseband you need to create a custom .ipsw with PwnageTool. This custom .ipsw will not contain the baseband update but of course will still give you any new stuff from 2.2.1

*You must be on firmware 2.2 or below in order to preserve your baseband. If you are already on 2.2.1 prior to Jailbreaking you will not be able to unlock your phone.

Let’s get started, after the jump!

1. Get the Tools

First things first, make sure you are running the latest version of iTunes [8.0.2]

Then you will want to create a folder on your desktop to keep things clean. Name it whatever you'd like.

Next you want to download the Pwnage 2.2.5 tool to the folder you just created.

Now download the 2.2.1 iPhone 3G firmware. Make sure to place that in the above folder as well. If you are able to use Firefox for this download, please do so. In the last set of guides, many of you had issues downloading the file with Safari.

2. Install the Tools

Now double click on the PwnageTool file to mount PwnageTool. Once mounted click and drag the PwnageTool application into the Pwnage folder you created on your desktop.

Then double click the icon that was just created to launch the PwnageTool.

3. Expert Mode

This is a easy one, select "Expert Mode".

4. Select your Device

Which in this case would be the iPhone 3G.

5. Browse for IPSW

Click the blue arrow button to continue. You will be brought to the "Browse for IPSW" page. It should automatically find the correct file, then click the blue arrow to continue. If Pwnage does not find the file, you must manually browse to the IPSW file that is in the folder you created on your desktop.

6. Menu with 7 Options

You will then be brought to a menu with 7 different options. We will only address the "General" and "Custom Package Settings". More advanced users can make any changes they see fit. Select the "General" tab and then click the blue arrow button to move forward.

When you are in the "General" tab there are a few things you must take care of. Here you will decide your partition size, 530 MB should be good. Next, if you are using your iPhone on an official carrier (AT&T, O2, Rogers, etc.) uncheck "Activate the phone". Lastly, check "Disable partition wipe-out". Hit the arrow button to continue.

Next select the "Custom Package Settings" tab. Be sure that "Cydia Installer" and "Installer" are both checked, hit the arrow to move to the next step.

7. Ready to Begin Pwnage Process!

Click the "Build" button and then click the arrow to begin the Pwnage process.

Now simply select where you would like to save the custom IPSW file that will be created. The folder you created on your desktop would be a good place.

Your IPSW is being created. Please be patient during this process, it could take up to 15 minutes. During this time Pwnage will ask for your administrator password, this is normal, enter it.

8. DFU Mode

First you will be prompted to shut off your iPhone.

This next part seems to give some people trouble, pay close attention. Pwnage will ask you to hold the home button and the power button for 10 seconds. Then, you will have to release the power button and hold the home button for 10 seconds. This should put you in DFU.

If you have succeeded you will see the following graphic.

*Important Note - The new Macbooks that were recently released prevent you from entering DFU mode. It is possible to go from 2.1 Pwned to 2.2.1 Pwned but you will not be able to go from 2.1 stock to 2.2.1 Pwned. Got that? In order to proceed, you must enter recovery mode as outlined in this Apple Knowledge Base article.

9. iTunes Restore

Now we have to go into iTunes and restore the iPhone with the custom built firmware. Do so by pressing the Alt/Option button and click "Restore".

Simply select the following file, "iPhone1,22.2.15G77CustomRestore.ipsw", from the folder on your desktop.

iTunes is now restoring the firmware on your iPhone. This can take up to 10-15 minutes.

When complete you will be asked to "set up as a new iPhone" or "restore from a backup". You can select either option but my recommendation is to start fresh and select "set up as a new iPhone".

Congratulations! You are now the owner of a freshly jailbroken iPhone 3G with the 2.2.1 firmware!

Have questions? Run into problems? Check out our Jailbreak Central Forum for help!

Let me just start off by saying that the iPhone 3G unlock feature is not yet available in the latest Dev Team software, QuickPwn and the PwnageTool, but you are now able to jailbreak the 2.2 firmware!

It is important to note: Things have gotten a bit more complicated compared to previous releases. If you are users of first generation iPod Touches, 2G/EDGE (first generation) iPhones, factory unlocked iPhone 3G's (the kind you can buy in places like Hong Kong) or you just have no interest in software unlocking your iPhone 3G - you can use the QuickPwn tool. If you are an iPhone 3G user that is interested in unlocking, Apple has tossed a monkey wrench in the mix for you. The 2.2 firmware upgraded the baseband. This forces you to use PwnageTool (available to Mac users only at the moment) to create a custom .ipsw file that keeps the 2.1 baseband but adds in the software functionality of the 2.2 update.

Please read the official post from the Dev Team for the all of the details, instructions, and downloads. And be sure to hit our Jailbreak Central Forum more news and help.

Good luck to you all!

[Via blog-iphone-dev.org]

Ok, so here we have yet another update on the Dev Team's blog. This time they tell us everything we want to know about the 2.2 firmware and jailbreaking.

So, as anticipated our friends the misfits have recently released the long awaited 2.2 update. We can confirm that this update SHOULD NOT be applied using iTunes if you want the chance of a soft-unlock in the near future. If you want to keep that option of a ‘soft-unlock in the near future’ available but you want the new features of 2.2, you will be able to update to 2.2 using a PwnageTool created custom ipsw file that disables the baseband update. You will be able to do this using an updated version of PwnageTool that will be released sometime soon.

Notice the "to be released soon" part? Yeah, so did we. For a full list of facts regarding the firmware and jailbreaking please proceed to the Dev Team post. The most important fact to be aware of is if do update to 2.2 right now and are jailbroken you will not only lose the jailbreak but you will not be able to jailbreak 2.2 until they release their new PWNage tool. So, proceed with caution out there.

Of course, when they do release said 2.2 PWNage, you know we'll be all over it.

[Via blog.iphone-dev.org]

I have a funny feeling that sometime shortly after the 2.2 firmware drops, we will see the iPhone 3G software unlock in the next version of the ever so popular PWNage tools from the Dev Team.

They just updated their blog with more good news, the ability to spawn background tasks. Which is great and means they have everything they need for the unlock except for the implementation. Watch the video above for more details.

Keep up the good work guys. Everyone here at TiPb appreciate your work!

[Via blog.iPhone-dev.org]

Well if this is not a bit of foreshadowing I don't know what is. The Dev Team just posted a update on their website with a "warning" to would be unlockers.

Update warning! Now for something a bit more serious, we’ve explained about the pros and cons of applying Apple’s updates in the past and we’ve warned against the immediate installation of these updates without knowing what they do to your device. This is indeed true of the iPhone 3G’s upcoming 2.2 release. Installing ‘2.2’ straight away on the iPhone 3G using the iTunes auto-updater could affect your chances of any software unlock in the near future (should one be found and released), so when you see an update in iTunes await our instructions first! Please don’t blindly install the update and then complain about it later

Did any of you happen to notice the "software unlock in the near future" part? Yeah, so did we here at TiPb. Looks like if you have been waiting for a unlock for the iPhone 3G your patience may be paying off.

Stay tuned in the upcoming few weeks... I think Christmas may be earlier for some of you!

[Via Blog-iPhone-dev.org]

Now does this really come as a surprise to anyone out there? Well it comes as no surprise for all of us here at TiPb that the Dev Team has jailbroken the latest 2.2 firmware beta released by Apple to developers. Not too shabby, and it should make all of you out there happy to know that the wait to jailbreak the 2.2 firmware will not be long! Short and painless. Now remember this is a beta right now so Apple may make some changes that can toss a wrench into the Dev Team's work but seriously how long would that slow them down? A day or two? Props to the Dev Team, they have yet to let us down.

For all of your jailbreaking needs be sure to check out our dedicated forums on that particular topic, iPhone Jailbreak Central and iPhone Jailbreak Apps.

{Via iPhone-dev.org]

Apparently, when it comes to working on unlocking the iPhone 3G to run on other carriers, for the iPhone DevTeam, Sunday is funday...

So, still no software unlock for the 3G (don't let the web scams fool you!), but they're getting closer...

Since Canada has no other GSM carrier, this won't change much for me locally, but it would make traveling so much easier (change country, change SIM!). How about you? Waiting to get your unlock on?

Ok all of you Windows peeps, this is what you have been waiting for. And no, sorry, still no unlocking for the 3G yet, but you can jailbreak the 2.1 firmware with the freshly released Windows Quickpwn 2.1!

More on Windows QuickPwn 2.1:

Supports 2.1 firmware with the unlocking and jailbreaking of iPhone 1st generation (2G) device. Supports the jailbreaking of iPod Touch 1st generation device and iPhone 3G. Does not support the unlocking of iPhone 3G or jailbreaking of second generation (n72ap based) iPod Touch.

So what are you waiting for Windows jailbreakers?! Head on over and grab Windows Quickpwn 2.1!

As always, TiPb takes no responsibility for any wrong doings to your devices, you dig? Please know what you are doing and have fun!

(Thanks Tommy for sending this in!)

Here and TiPb we like to protect our readers from all that is evil. Well today we have a little warning from the Dev Team regarding the fake QuickPwn sites on the internet.

We would just like to point out that that there are lots of fake sites using the QuickPwn name, these muppets don’t know anything special, and they don’t have anything unique. They are vultures that sit on the domain names and plagiarize content and information in the hope that you donate to them, or click the google ads.

As we’ve mentioned before we don’t accept donations and we certainly don’t allow ads on our site, anyone who asks for donations in our name is lying, end of story.

There have been a few readers lately inquiring about unlocking of the iPhone 3G. Lets put all these rumors to rest right now. There is currently NO software unlock for the iPhone 3G. The only way possible (which I would not recommend even to my worst enemy), is a SIM unlock. For more information regarding the dangers of those please head to our forums.

If it's not on the Dev Teams official web site, please think twice about downloading it and using it.

[Via iPhone.-dev.org]

ZOMG! Apple has fought back! The only way Apple can fix the exploit that the iPhone Dev Team has been using to Jailbreak iPhone's and iPod Touch's (check out our forums for more on that) is to fix their hardware, but it seems Apple has figured out a way to program iTunes 8 to detect and prevent the Pwnage exploit.

Apple may have won that battle but they have not won the war. The Dev Team reacted promptly:

"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."

So take heed fellow Jailbreakers... it is not wise to jump all over that 2.1 firmware update coming this Friday. Best to wait it out until the Dev Team puts out that patch. Again this warning is for Jailbreakers only.

[Via iPhone-Dev.org]