Wednesday, November 24, 2010

Thanksgiving with Apple

From the ever fabulous iPhone Dev-Team:

With Turkey Day a few days off, today Apple publicly released FW version 4.2.1. As always, ultrasn0w unlockers please stay far far away from this official firmware (and all official firmware). Wait for the ability to create custom 4.2.1. IPSWs that don’t update your baseband! If you’re not an unlocker, read on!

The best news of all is for owners of iPhone3G, older iPhone3GS, and non-MC iPod touch 2G. Due to a combination of our original pwnage2 exploit, the arm7_go exploit, 24kpwn, and limera1n, your device is “just as jailbreakable as ever.” You reap the full benefit of an untethered 4.2.1 jailbreak.

Next are the owners of all the more recent devices. The good news there is that due to geohot’s limera1n exploit, all recent devices can be jailbroken (this will be true until Apple released new hardware that fixes geohot’s limerain exploit in the bootrom). The bad news is that right now, the 4.2.1 jailbreak is *tethered* on all of these recent devices. A tethered jailbreak means that each time your device loses battery power or needs to be rebooted, you must attach it to a PC or Mac to boot into the jailbroken state. @comex is working hard on a method that may untether the 4.2.1 jailbreak, but it will require you to have your 4.1 SHSH blobs in order to use it. No word on how much more effort it will take though (please don’t bug @comex about it!). (We also have an alternative method that may work, but @comex’s method is much more elegant.)

So when does all this 4.2.1 jailbreak action happen? Well if you’re a JB developer or tinkerer, you’ve already probably used the redsn0w mentioned in our last post to jailbreak 4.2.1 and at least get SSH working. But beyond that, there are still some last minute issues with MobileSubstrate and comex’s kernel patches that are being fixed. We’ll tweet and post a blog update when it’s all available (we hate to give ETAs, but barring any unforeseen problems, probably later today). It happens “now’…see Update #1.

In the meantime, please make sure you have your 4.1 SHSH blobs for all your devices. These will be important even for firmware beyond 4.1 (using both comex’s method and our alternative, depending on how each of them turn out.)

ultrasn0w unlock: After redsn0w is officially released with the new Cydia and kernel patches, we’ll be able to assess the unlock situation. It’s already looking very promising though, so expect the unlock for the 3G and 3GS to be coming this week. The i4 unlock is taking more effort though, and no further concrete info is available about that yet.

Feel free to ask questions in our comments section below, where we’ve got some awesome new additional moderators — sherif_hashim, dhlizard, and Frank55!

Update #1: redsn0w version 0.9.6b4 is now available for your 4.2.1 jailbreaking pleasure. Please read all the above to understand what this jailbreak currently entails.

PLEASE UPGRADE TO iTunes 10.1 FOR BEST RESULTS
WINDOWS 7 USERS SHOULD RUN redsn0w IN “XP COMPATIBILITY” MODE



Mirrors -

Mac

http://www.iphone-storage.de/redsn0w_mac_0.9.6b4.zip
http://cdn.nspwn.com/redsn0w_mac_0.9.6b4.zip
http://tgq.nl/redsn0w_mac_0.9.6b4.zip

Windows

http://cdn.nspwn.com/redsn0w_win_0.9.6b4.zip
http://tgq.nl/redsn0w_win_0.9.6b4.zip
http://bubele.eu/redsn0w_win_0.9.6b4.zip
http://kwek.no-ip.org/redsn0w_win_0.9.6b4.zip


Update #2: The notion of a “tethered” jailbreak is pretty new to many people, so here’s a quick rundown on what to expect:

If you’re on an iPhone3G, old-bootrom iPhone3GS, or non-MC ipt2g, life is easy. redsn0w installed an untethered jailbreak and so nothing below applies.
“Tethered” does not mean you cannot boot at all without PC/Mac assistance. If you have not installed any tweaks that hook into important programs like SpringBoard or CommCenter, your device will actually boot. However, jailbreak programs like Cydia won’t work (and Cydia may still have a white icon). Also, certain built-in apps that had to be moved by Cydia will fail (Safari being the most noticeable example).
If you’ve installed MobileSubstrate tweaks that hook into SpringBoard or other important programs, your boot will actually fail (you’ll get stuck at the Apple logo). You need to use redsn0w to “Just boot tethered right now”.
Remember, @comex and others are working on a way to untether the 4.2.1 jailbreak. Meanwhile, the above 3 points hopefully will make it all seem less confusing :)

Wednesday, November 3, 2010

redsn0w+limera1n fun

From the Dev-Team:

It looks like geohot’s recent limera1n exploit for iPhone3GS/iPhone4/iPad/ipt3g/ipt4g/atv2g will be very beneficial to jailbreakers and unlockers for the next few months (at least). geohot’s limera1n program and the alternative greenpois1on program both use his same exploit (although greenpois0n refuses to tell you that, FWIW), and hopefully SHAtter can be saved for some later device.

In the meantime, we’ve also incorporated the limera1n exploit into redsn0w. But we’ve added a few extras:

* custom bootlogos for iPhone3G/iPhone3GS/iPod2G users (with qualifying bootroms)
* an option that implements the “DFU” button in PwnageTool. This button (which you can use from Windows) lets you prepare your device for a custom DFU. Even if you’re purely a Windows user, you can get a trusted friend to run PwnageTool over your IPSW to create a custom IPSW. You can now install that custom IPSW on your own Windows box, after you run this redsn0w version.

This latest redsn0w is available at:

* OS X (See update #3)
* Windows (See update #3)

For Windows users who have run redsn0w and chosen “Just enter pwned DFU mode right now”, your device is now completely vulnerable. Running iTunes and selecting a custom IPSW from PwnageTool (choose it by pressing Shift+Restore)….you’ve now convinced your device and iTunes to restore to a custom firmware. Congratulations!

If you are timid about software and running these programs…please just wait! Don’t jeopardize your carrier unlock for a firmware upgrade. Wait for even easier methods than this latest redsn0w release.

Update #1: Today Apple released to developers the GM seed for 4.2. Tinkerers will find that yesterday’s redsn0w jailbreaks today’s 4.2 GM seed, simply by pointing redsn0w at the 4.1 IPSW (rather than the 4.2 one). Right now it mostly only makes sense for JB app developers to do that because many apps (including Cydia itself) need to be updated for 4.2. However, if all you want to do is enable afc2 (to use iFunBox or other file browsers), or to tweak settings like Battery % and Homescreen wallpapers, then go for it (if you have valid paid access to the GM seed). Be sure to uncheck the Cydia box, though! Ultrasn0w unlockers should stay very far away from this!!

Update #2: By all accounts, we’re within a few days of Apple’s official public release of Firmware 4.2. Here’s what you need to know:

* Thanks to geohot’s limera1n exploit, and our original pwnage2 exploit, and @pod2g’s ipod2g-MC exploit, absolutely all devices at all iOS firmware versions are capable of being jailbroken.
* The untethered jailbreak of those very latest FWs and latest devices depends on @comex hacks. His hacks so far extend only to 4.1 and 4.2beta3. He’s working on a way to extend it to 4.2 and beyond. Just wait for him to work out his method.
* iPhone 3G and 3GS unlockers will be covered by our upcoming unlock. Stay away from any updates to Apple FW until our official release and you’ll be okay. Just stay away from all Apple IPSWs :)
* iPhone4 unlockers are not left out in the cold. @sherif_hashim has found some very promising avenues to pursue. Those will be explored as soon as possible after all the 4.2 madness.

What does this mean to you?

* If you’re an unlocker, just stay where you are. Please, just stay where you are. Any mistakes you make now may be permanent.
* If you only care about the jailbreak and you’re absolutely sure you have your personalized 4.1 SHSH hashes, feel free to experiment but keep in mind that any mistakes you make may result in your losing pictures or notes or bookmarks that you’d rather keep. Honestly unless you love living on the bleeding edge, it’s better to just wait for official updates from Cydia/redsn0w/PwnageTool.
* Don’t buy or donate to any unlock or jailbreak scammers. Every legitimate solution you will find for unlocks or jailbreaks will be offered without an extended hand. That’s how the iPhone jailbreak/unlock community has succeeded. It’s about freedom to do what you want with your $300 device — not about donations, egos, tweets, or “interviews.”

Update #3: (Warning: if you use the ultrasn0w unlock, please read no further…this doesn’t apply to you yet!) We’ve made some updates to redsn0w to make it easier for jailbreak developers (and tinkerers) to get their programs ready for 4.2.1. As noted above, the public version of Cydia (and MobileSubstrate too!) is not 4.2.1-compatible. redsn0w will now let you install your own custom bundles independent of Cydia (the bundle can actually be Cydia if you’ve compiled it on your own). These bundles can be up to 15MB in size, and should be in the form of a gzip-compressed tar file.

The new redsn0w 0.9.6b3 is available at:

* OS X
* Windows

It’s very important that you get the file permissions and ownerships right in your custom redsn0w bundles. To give you a practical example of such a bundle, here’s one that includes OpenSSH, OpenSSL, and the basic apt installer programs:

* SSH bundle

redsn0w has also been updated to recognize the 4.2.1GM IPSWs. *However*, as noted above, the 4.2.x jailbreak is not yet untethered for most devices! That means until someone like @comex comes up with a way to untether it, you must use redsn0w (or a similar utility) to boot your device into a jailbroken 4.2.1 state. (The only exceptions to this are the iPhone3G, non-MC iPod touch 2G, and old-bootrom iPhone3GS. redsn0w will jailbreak those untethered!)

With the above redsn0w and SSH bundle, jailbreak developers and tinkerers can jailbreak and SSH into their 4.2.1 devices, provided they’ve done a tethered boot (using redsn0w’s “Just boot tethered right now” option).

Note: The Cydia that’s included in 0.9.6b3 is the same one as in 0.9.6b2, and so it will *not* work on 4.2.1. Don’t try installing it on 4.2.1! Instead, use the SSH bundle, or compile Cydia on your own. If you’re familiar with the apt utilities, you can use “apt-get” to install many programs from the command line. Be sure to do “apt-get update” first to refresh your sources!

PLEASE CONSIDER THIS AN ADVANCED TOPIC!
!
It’s not meant for the masses because it involves rather nerdy things like command lines and tar files. But for those who know how to use this new redsn0w feature, have fun!

Saturday, October 30, 2010

AppleTV Firmware Files - Direct Downloads

Here are the direct links to the AppleTV Firmware Files for every released firmware version.

1.0.0: OS-dot-DMG 1.0.dmg
1.1.0: 2Z694-5248-45.dmg
2.0.0: 2Z694-5274-109.dmg
2.0.1: 2Z694-5387-25.dmg
2.0.2: 2Z694-5428-3.dmg
2.1.0: 2Z694-5485-1.dmg
2.2.0: 2Z694-5499.dmg
2:3:0: 2Z694-5573-24.dmg
2.3.1: 2Z694-5587-18.dmg
2.4.0: 2Z694-5660-029.dmg
3.0.0: 2Z694-5789-067.dmg
3.0.1: 2Z694-6004-003.dmg
3.0.2: 2Z694-6013-013.dmg
4.1.0: AppleTV2,1_4.1_8M89_Restore.ipsw
4.2.0: AppleTV2,1_4.2_8C150_Restore.ipsw
4.3.0: AppleTV2,1_4.3_8F191m_Restore.ipsw
4.3.0 (Version 2): AppleTV2,1_4.3_8F202_Restore.ipsw

MacOS X 10.4.9 Combo Updater


I will update this post as new firmware links become available.

iPhone Firmware Files - Direct Downloads

Below are the direct links to the iPhone Firmware Files for every released firmware version.

Please note that if you use Safari you must disable the auto unzip feature (Safari->Preferences->General->Uncheck "Open Safe Files After Downloading") , or just use a different browser type.


1.0.0: iPhone1,1_1.0_1A543a_Restore.ipsw
1.0.1: iPhone1,1_1.0.1_1C25_Restore.ipsw
1.0.2: iPhone1,1_1.0.2_1C28_Restore.ipsw
1.1.1: iPhone1,1_1.1.1_3A109a_Restore.ipsw
1.1.2: iPhone1,1_1.1.2_3B48b_Restore.ipsw
1.1.3: iPhone1,1_1.1.3_4A93_Restore.ipsw
1.1.4: iPhone1,1_1.1.4_4A102_Restore.ipsw
2.0.0 (2G): iPhone1,1_2.0_5A347_Restore.ipsw
2.0.0 (3G): iPhone1,2_2.0_5A347_Restore.ipsw
2.0.1 (2G): iPhone1,1_2.0.1_5B108_Restore.ipsw
2.0.1 (3G): iPhone1,2_2.0.1_5B108_Restore.ipsw
2.0.2 (2G): iPhone1,1_2.0.2_5C1_Restore.ipsw
2.0.2 (3G): iPhone1,2_2.0.2_5C1_Restore.ipsw
2.1.0 (2G): iPhone1,1_2.1_5F136_Restore.ipsw
2.1.0 (3G): iPhone1,2_2.1_5F136_Restore.ipsw
2.2.0 (2G): iPhone1,1_2.2_5G77_Restore.ipsw
2.2.0 (3G): iPhone1,2_2.2_5G77_Restore.ipsw
2.2.1 (2G): iPhone1,1_2.2.1_5H1_Restore.ipsw
2.2.1 (3G): iPhone1,2_2.2.1_5H11_Restore.ipsw
3.0.0 (2G): iPhone1,1_3.0_7A341_Restore.ipsw
3.0.0 (3G): iPhone1,2_3.0_7A341_Restore.ipsw
3.0.0 (3GS): iPhone2,1_3.0_7A341_Restore.ipsw
3.0.1 (2G): iPhone1,1_3.0.1_7A400_Restore.ipsw
3.0.1 (3G): iPhone1,2_3.0.1_7A400_Restore.ipsw
3.0.1 (3GS): iPhone2,1_3.0.1_7A400_Restore.ipsw
3.1.0 (2G): iPhone1,1_3.1_7C144_Restore.ipsw
3.1.0 (3G): iPhone1,2_3.1_7C144_Restore.ipsw
3.1.0 (3GS): iPhone2,1_3.1_7C144_Restore.ipsw
3.1.2 (2G): iPhone1,1_3.1.2_7D11_Restore.ipsw
3.1.2 (3G): iPhone1,2_3.1.2_7D11_Restore.ipsw
3.1.2 (3GS): iPhone2,1_3.1.2_7D11_Restore.ipsw
3.1.3 (2G): iPhone1,1_3.1.3_7E18_Restore.ipsw
3.1.3 (3G): iPhone1,2_3.1.3_7E18_Restore.ipsw
3.1.3 (3GS): iPhone2,1_3.1.3_7E18_Restore.ipsw
4.0.0 (3G): iPhone1,2_4.0_8A293_Restore.ipsw
4.0.0 (3GS): iPhone2,1_4.0_8A293_Restore.ipsw
4.0.0 (4): iPhone3,1_4.0_8A293_Restore.ipsw
4.0.1 (3G): iPhone1,2_4.0.1_8A306_Restore.ipsw
4.0.1 (3GS): iPhone2,1_4.0.1_8A306_Restore.ipsw
4.0.1 (4): iPhone3,1_4.0.1_8A306_Restore.ipsw
4.0.2 (3G): iPhone1,2_4.0.2_8A400_Restore.ipsw
4.0.2 (3GS): iPhone2,1_4.0.2_8A400_Restore.ipsw
4.0.2 (4): iPhone3,1_4.0.2_8A400_Restore.ipsw
4.1.0 (3G): iPhone1,2_4.1_8B117_Restore.ipsw
4.1.0 (3GS): iPhone2,1_4.1_8B117_Restore.ipsw
4.1.0 (4): iPhone3,1_4.1_8B117_Restore.ipsw
4.2.1 (3G): iPhone1,2_4.2.1_8C148_Restore.ipsw
4.2.1 (3GS): iPhone2,1_4.2.1_8C148a_Restore.ipsw
4.2.1 (4): iPhone3,1_4.2.1_8C148_Restore.ipsw
4.3.0 (3GS): iPhone2,1_4.3_8F190_Restore.ipsw
4.3.0 (4 GSM): iPhone3,1_4.3_8F190_Restore.ipsw
4.3.1 (3GS): iPhone2,1_4.3.1_8G4_Restore.ipsw
4.3.1 (4 GSM): iPhone3,1_4.3.1_8G4_Restore.ipsw
4.3.2 (3GS): iPhone2,1_4.3.2_8H7_Restore.ipsw
4.3.2 (4 GSM): iPhone3,1_4.3.2_8H7_Restore.ipsw
4.2.7 (4 CDMA): iPhone3,3_4.2.7_8E303_Restore.ipsw



I will update this post as new firmware links become available.

iPod Firmware Files - Direct Downloads


Below are the direct links to the iPod Firmware Files for every released firmware version.

Please note that if you use Safari you must disable the auto unzip feature (Safari->Preferences->General->Uncheck "Open Safe Files After Downloading") , or just use a different browser type.


1.1: iPod1,1_1.1_3A101a_Restore.ipsw
1.1.1: iPod1,1_1.1.1_3A110a_Restore.ipsw
1.1.2: iPod1,1_1.1.2_3B48b_Restore.ipsw
1.1.3: iPod1,1_1.1.3_4A93_Restore.ipsw
1.1.4: iPod1,1_1.1.4_4A102_Restore.ipsw
1.1.5: iPod1,1_1.1.5_4B1_Restore.ipsw
2.0.0: iPod1,1_2.0_5A347_Restore.ipsw
2.0.1: iPod1,1_2.0.1_5B108_Restore.ipsw
2.2.0 (1G): iPod1,1_2.2_5G77_Restore.ipsw
2.2.0 (2G): iPod2,1_2.2_5G77a_Restore.ipsw
2.2.1 (2G): iPod2,1_2.2.1_5H11a_Restore.ipsw
3.1.2 (3G): iPod3,1_3.1.2_7D11_Restore.ipsw
3.1.3 (3G): iPod3,1_3.1.3_7E18_Restore.ipsw
4.0.0 (2G): iPod2,1_4.0_8A293_Restore.ipsw
4.0.0 (3G): iPod3,1_4.0_8A293_Restore.ipsw
4.0.2 (2G): iPod2,1_4.0.2_8A400_Restore.ipsw
4.0.2 (3G): iPod3,1_4.0.2_8A400_Restore.ipsw
4.1.0 (2G): iPod2,1_4.1_8B117_Restore.ipsw
4.1.0 (3G): iPod3,1_4.1_8B117_Restore.ipsw
4.1.0 (4G): iPod4,1_4.1_8B117_Restore.ipsw
4.2.1 (2G): iPod2,1_4.2.1_8C148_Restore.ipsw
4.2.1 (3G): iPod3,1_4.2.1_8C148_Restore.ipsw
4.2.1 (4G): iPod4,1_4.2.1_8C148_Restore.ipsw
4.3.0 (3G): iPod3,1_4.3_8F190_Restore.ipsw
4.3.0 (4G): iPod4,1_4.3_8F190_Restore.ipsw
4.3.1 (3G): iPod3,1_4.3.1_8G4_Restore.ipsw
4.3.1 (4G): iPod4,1_4.3.1_8G4_Restore.ipsw
4.3.2 (3G): iPod3,1_4.3.2_8H7_Restore.ipsw
4.3.2 (4G): iPod4,1_4.3.2_8H7_Restore.ipsw



I will update this as new firmware versions come out.

iPad Firmware Files - Direct Downloads

Below are the direct links to the iPad Firmware Files for every released firmware version.

Please note that if you use Safari you must disable the auto unzip feature (Safari->Preferences->General->Uncheck "Open Safe Files After Downloading") , or just use a different browser type.


3.2.0: iPad1,1_3.2_7B367_Restore.ipsw

3.2.1: iPad1,1_3.2.1_7B405_Restore.ipsw
3.2.2: iPad1,1_3.2.2_7B500_Restore.ipsw
4.2.1: iPad1,1_4.2.1_8C148_Restore.ipsw
4.3.0 (iPad 1): iPad1,1_4.3_8F190_Restore.ipsw
4.3.0 (iPad 2 Wi-Fi): iPad2,1_4.3_8F191_Restore.ipsw
4.3.0 (iPad 2 GSM): iPad2,2_4.3_8F191_Restore.ipsw
4.3.0 (iPad 2 CDMA): iPad2,3_4.3_8F191_Restore.ipsw
4.3.1 (iPad 1): iPad1,1_4.3.1_8G4_Restore.ipsw
4.3.1 (iPad 2 Wi-Fi): iPad2,1_4.3.1_8G4_Restore.ipsw
4.3.1 (iPad 2 GSM): iPad2,2_4.3.1_8G4_Restore.ipsw
4.3.1 (iPad 2 CDMA): iPad2,3_4.3.1_8G4_Restore.ipsw
4.3.2 (iPad 1): iPad1,1_4.3.2_8H7_Restore.ipsw
4.3.2 (iPad 2 Wi-Fi): iPad2,1_4.3.2_8H7_Restore.ipsw
4.3.2 (iPad 2 GSM): iPad2,2_4.3.2_8H7_Restore.ipsw
4.3.2 (iPad 2 CDMA): iPad2,3_4.3.2_8H8_Restore.ipsw

I will update this post as new firmware links become available.

Wednesday, October 20, 2010

20102010 event

From the iPhone Dev-team:

We’re pleased to release PwnageTool 4.1 4.1.2 for Mac OS X (free of charge, blog ads, and donation requests — as always!). Today’s big new addition to the jailbreak family is AppleTV 2G, which was first shown jailbroken in its release week!

[Update: Version 4.1.2 should fix any issues that OS X 10.5.x users were seeing. You only need to run this version if you’re at OS X 10.5.x and were seeing Cydia errors]

ULTRASN0W UNLOCKERS BEWARE!! ULTRASN0W UNLOCKERS BEWARE!! The biggest mistake you can make (and it is a big one!) is lettings iTunes restore to the official IPSW — you’ll lose the unlock and won’t be able to go back! You must use Option-Restore, not just the Restore button by itself. Then navigate to your custom IPSW — not to the stock one! If you accidentally started a restore to the official IPSW, unplug your iPhone immediately before the restore gets to the “Updating Firmware” step!

Through a combination of the recently released geohot limera1n exploit , @comex’s recently released pf kernel exploit, and our original pwnage2 exploit, PwnageTool 4.1 works untethered on these devices at firmware 4.1:

* AppleTV 2G
* iPad (firmware 3.2.2)
* iPod touch 4G
* iPod touch 3G
* iPhone4
* iPhone 3GS
* iPhone 3G

PwnageTool allows you to restore to a custom IPSW file. For instance, you can restore to a pre-jailbroken firmware while simultaneously maintaining your current baseband (and thus your ultrasn0w carrier unlock). You can also add whatever packages you want in the “Expert” mode of PwnageTool, if you wish to pre-install Cydia packages. iPhone 3G users get the additional benefit of selecting their own boot and recovery logos, and features like multitasking and battery charge percentage.

PwnageTool’s main advantage to ramdisk-based methods (limera1n, greenpois0n, redsn0w) is for unlockers — those that need to keep their current baseband and preserve their ultrasn0w unlock. But in this new age of both bootrom- and userland-based exploits, it’s an excellent platform for continuing the jailbreak through all future firmwares. More on this later! In the meantime, please enjoy this free software and please provide any usage feedback in our comment section below.

AppleTV 2G users: Welcome to the JB family! Right now, about all you can do is command-line stuff via ssh. You also have afc2 available, so you can use tools like ifunbox to move files around. These are the *very* early days of AppleTV 2G jailbreaking, so it’ll take some time for JB app developers to come up with methods to use your AppleTV 2G from the remote, versus the command line. PS: Your ssh password is “alpine”…please change it when you can :)

Expert mode: By popular demand, the IPSW file selection in Expert mode is now completely manual (doesn’t use Spotlight). Just pick your IPSW file directly instead of waiting for the Spotlight search to complete. In Expert mode, the default is to hacktivate (“Activate the iPhone”), so if you have a legit SIM card be sure to deselect that option in Expert mode.

DFU button: That “DFU” button in PwnageTool is more than it looks like. It guides you through the DFU process, but then also runs the appropriate exploit to convince your device and iTunes that all is legit. The DFU button in PwnageTool is not just your average DFU.

Official Bittorrent Releases

PwnageTool 4.1 Torrent - PwnageTool_4.1.dmg.5898597.TPB.torrent

SHA1 Sum = 4f216e5863d191f30f84b6201e8c2bbea031e691

Unofficial Mirrors


The following links are unofficial download mirrors, you download these archives at your own risk, we accept no responsibility if your computer explodes or if it becomes part of a NASA attacking botnet or even worse if your hands fall off mid-way during the use of these files. We do not check these links and we accept no responsibility with regard to the validity of the files, the other content that these links may provide or with the content that is on the third-party linked site.

Always check the files that you have downloaded against our published SHA1 hash.

We would prefer that you downloaded the official bittorrent release that is linked above, but you are welcome to try these if you really must.

Mirror owners should email direct dmg download links only (no rapidshare type sites please) to blog@iphone-dev.org — please don’t place mirrors in the comments as they will be deleted.

* http://www.pyrofallout.com/PwnageTool_4.1.dmg
* http://www.ipodtouchmasterfr.com/files/PwnageTool_4.1.dmg
* http://www.d4sys.com/download/PwnageTool_4.1.dmg
* http://leimobile.com/mirrors/PwnageTool_4.1.dmg
* http://claytonbraasch.com/downloads/PwnageTool_4.1.dmg
* http://martinkup.com/PwnageTool_4.1.dmg
* http://fsckyou.org/PwnageTool_4.1.dmg
* http://chronzz.com/dl/PwnageTool_4.1.dmg
* http://zaone.ro/PwnageTool_4.1.dmg
* http://gumballtech.com/files/PwnageTool_4.1.dmg
* http://theplacefordee.com/PwnageTool_4.1.dmg
* http://download.sourcekills.com/files/devteam/PwnageTool_4.1.dmg
* http://www.buzzspan.com/downloads/PwnageTool_4.1.dmg

Tuesday, October 12, 2010

Greenpois0n is out!!

Greenpois0n is up and running!!



You can find the Windows jailbreak here and The Linux Jailbreak here. The Mac version is not out yet, but keep an eye out for an update. Update: MAC Version is here.

Please read on for a tutorial on how to use Greenpois0n:

These are instructions on how to jailbreak your iPhone 3GS and iPhone 4 using Greenpois0n for Windows. Greenpois0n only supports iOS 4.1 firmware. Use Limera1n if you want to jailbreak iOS 4.0, iOS 4.0.1, iOS 4.0.2.

Remember: Do not update to iOS 4.1 if you need the unlock. Ultrasn0w does not support that baseband yet. The only exception is the iPhone 4. You can update to iOS 4.1 without upgrading your baseband by following this tutorial.

Step One
Open your web browser of choice and navigate to http://www.greenpois0n.com. Click the Windows link at the bottom of the screen, or just use the link at the top of this post.


Step Two
When prompted save the download to your desktop



Step Three
Double click the downloaded gp_win_rc2.zip file then drag the greenpois0n.exe file to the desktop. Double greenpois0n.exe from the desktop to launch the application




Step Four
Power off your iPhone then click the large Prepare to Jailbreak (DFU) button


Step Five
You will now be instructed on how to place your iPhone into DFU mode. You can get help with this here.

You will be asked to press and hold the sleep button for 2 seconds.


Continue holding sleep; press and hold home for 10 seconds.


Release sleep button; continue holding home for 15 seconds.


Step Six
Once your iPhone is successfully in DFU mode you may click the Jailbreak button.


Step Seven
Greenpois0n will now jailbreak your device




Step Eight
Click the Quit button once the software application has completed.


You'll notice some verbose mode text scrolling on your device.

Step Nine
After the iPhone restarts you'll notice a new Loader application on your Springboard. Press to launch it.


Step Ten
Press to select Cydia then press the large Install Cydia button that appears.


Step Eleven
Once Cydia has installed successfully you will be asked if you want to remove Loader from your device. Press the Remove button then press the Home button. Your device will now automatically reboot.


Step Twelve
When your iPhone has restarted you can run Cydia. Let it do all the necessary updates then follow our Unlock tutorial if possible for your device.



Please visit The Chronic Dev Team and The iPhone Dev Team's blogs for more info and to express your thanks for this Jailbreak.

Thanks All!!

Sunday, October 10, 2010

Limera1n surprise

From the iPhone Dev Team:

After a few very dramatic days in the jailbreak community, geohot has come out of nowhere to release limera1n. It’s a bootrom-level jailbreak that works on the iPhone3GS, iPhone4, iPod touch 3G, iPod touch 4G, the iPad, and (technically) the AppleTV 2G.

DO NOT USE LIMERA1N IF YOU USE THE ULTRASN0W CARRIER UNLOCK — wait for PwnageTool to incorporate the limera1n exploit. This is so that you can avoid updating your baseband and losing the unlock (possibly forever).



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 (thankfully!) 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.

Limera1n wasn’t tested very thoroughly and does have some issues. Geohot typically works these out in subsequent (and rapid) releases (there are already 3 beta versions of it as of Saturday night!). In the meantime, feel free to discuss any problems and their solutions in our comments section.

Update #1: Because the “untethered” part of this jailbreak comes from a userland hack from @comex, you should still backup your SHSH hashes for 4.1. Do this by either letting Cydia keep them (“make my life easier”), or using Tiny Umbrella. This way you can always come back to an untethered, jailbreakable 4.1 on your devices after Apple has closed their 4.1 signing window (they’ll close the 4.1 window once they push out their next firmware version). If you fail to do this and ever need to restore to 4.1 again, you can still jailbreak but it will be a tethered JB (you’ll need to connect to your computer to finish the booting process, each and every time).

And remember: you can backup your 4.1 SHSH hashes without even being at 4.1 or even being jailbroken, by using Tiny Umbrella.

Limera1n release delays Greenpois0n

A decision was made today to delay the release of Greenpois0n. iPhone 4 users will have to wait for the new jailbreak for the time being


I'm certain the decision was not made lightly and is for good reason. That reason apparently is due to the untimely limera1n jailbreak release by Geohot. Limera1n is still in beta and is only usable on Windows. The reason why Geohot's Limera1n is the root of the Greenpois0n release delay is the fact that the Limera1n tool uses a different bottom exploit than the one that was supposed to be released today based on the work of the Chronic Dev Team and the iPhone Dev Team.



The Chronic Dev Team states:

Thanks to the irresponsible antics of geohot, we will have to delay the release of greenpois0n (new ETA = as soon as possible), so that we have time to clean up his little mess and integrate the exploit he uses in limera1n into greenpois0n. This way, we can save SHAtter for future devices that may still be vulnerable to it.

We know that this is not what some people want to hear, but due to geohot needing to feed his ego (as usual) and revealing his limera1n exploit, we do not have any other responsible options.