Offical 3.1 Jailbreak Thread.

ok so my 3g failed during a software download on cydia and wouldn't boot. so restored in itunes and stupidly upgraded to 3.1 have tried the downgrade by holding shift and restoring with both 3.0 and 3.0.1 this restores but when on the last verify bit i get an error and the iphone shows the iphone and usb logo. the instructions say to restart the iphone in dfu and go straight to jailbreak, i use redsn0w 0.8 and 3.0 IPSW. this does go through the jailbreak process and i get a phone with cydia installed. however the iphone due to the itunes fail, never activates so i'm left with no service.

is there a work around or can i (on a 3g) downgrade the baseband, i would wait for the next jailbreak for 3.1 but i'm on hols in 2 days and have now lost my european sat nav!!

If theres one thing weve been stressing the last few weeks, its that if you want to keep the jailbreak or unlock on your 3GS, you should resist all urges to install Apples official firmware updates without knowing if a jailbreak exists for that version yet. Unless another (different) bootrom exploit is found for the 3GS that doesnt require a foot in the door with a signed official iBoot, then accepting official updates willy-nilly may cause you to be cutoff from the jailbreak. And it will definitely cause you to be cutoff from the carrier unlock.

Now, there are ways to ensure that even after taking an official 3GS update (which you really shouldnt do!), that youll nonetheless be able to revert to a jailbreakable 3GS (this is NOT true for the unlock, see NOTE #1 below). Weve been explaining these methods (like the iTunes /tmp technique) over the last few weeks, and theres been some great discussion and feedback for the methods in the comments.

Having said all that, we realize that some of you updated your 3GS to 3.1 anyway. If you want to come back to the world of the jailbreak (but NOT the sim unlock, sorry!) then sauriks new on file server may be able to help. Hes got all the details in a new article so do check it out.

Even if you did not update your 3GS to official 3.1 (good job! You really shouldnt do that!), then you should still read the article and make those changes today. We fully recommend redirecting your iTunes signing process through sauriks on file server to future-proof your 3GS jailbreak through all future updates.

AFTER ADJUSTING YOUR ITUNES SETUP, YOU SHOULD STILL AVOID DOING AN ACTUAL FIRMWARE UPDATE. For all the reasons mentioned in this post, youll lose the unlock forever, and lose the jailbreak until a new one for 3.1 comes out. And theres no guarantee that your 3.0 signed files were captured by saurik in time. This is more about protecting your 3GS jailbreak in future updates its not a way to jailbreak 3.1 right now.
NOTE #1: the carrier sim unlock is a different story. Jailbreaking and unlocking have two different security mechanisms, and if you update your 3GS (or 3G) to 3.1, you will lose your carrier unlock, possibly forever. Even if you downgrade from 3.1 to 3.0, you will have lost your carrier unlock. So if you think youll ever want to carrier unlock your 3G or 3GS (or maybe give it away or resell it later as an unlockable iPhone), then please stay clear of all official Apple IPSWs. Youll soon be able to create custom 3.1 IPSWs using PwnageTool that let you pre-hack your 3.1 update in a way that preserves the carrier unlock.
NOTE #2: The custom IPSW flow using PwnageTool also ensures that even if Apple fixes all the iBoot holes, youll still be able to retain your jailbreak through later updates. Thats because a jailbroken iPhone will happily accept a custom (pre-jailbroken) firmware update even though its not blessed with Apples signatures. This is the once jailbroken, always jailbroken approach. Its very powerful, but it requires you to only update to pre-hacked IPSWs.
NOTE #3: None of this applies if you have an iPhone 2G, iPod touch 1G, or iPod touch 2G. The iPhone 3G is also unaffected by Apples signing process for the jailbreak, but it is susceptible to permanent loss of the carrier unlock as mentioned in note #1.

"This is the low down on our tools for use with the 3.1 firmware from Apple, please read the whole post in full before attempting anything. Because of changes with Apples update techniques (that complicate the 3GS upgrade process) this will be a multipart release. This release starts with PwnageTool 3.1 for Mac OS X - this application supports the iPhone 1st Generation (2G), the iPhone 3G and the iPod touch 1G. NB: THIS DOES NOT SUPPORT THE 3GS OR 2G/3G IPOD TOUCH. redsn0w for Mac OS X and Windows will follow sometime in the near future, please dont bug us about it - well release when we have something ready."

If theres one thing weve been stressing the last few weeks, its that if you want to keep the jailbreak or unlock on your 3GS, you should resist all urges to install Apples official firmware updates without knowing if a jailbreak exists for that version yet. Unless another (different) bootrom exploit is found for the 3GS that doesnt require a foot in the door with a signed official iBoot, then accepting official updates willy-nilly may cause you to be cutoff from the jailbreak. And it will definitely cause you to be cutoff from the carrier unlock.

Now, there are ways to ensure that even after taking an official 3GS update (which you really shouldnt do!), that youll nonetheless be able to revert to a jailbreakable 3GS (this is NOT true for the unlock, see NOTE #1 below). Weve been explaining these methods (like the iTunes /tmp technique) over the last few weeks, and theres been some great discussion and feedback for the methods in the comments.

Having said all that, we realize that some of you updated your 3GS to 3.1 anyway. If you want to come back to the world of the jailbreak (but NOT the sim unlock, sorry!) then sauriks new on file server may be able to help. Hes got all the details in a new article so do check it out.

Even if you did not update your 3GS to official 3.1 (good job! You really shouldnt do that!), then you should still read the article and make those changes today. We fully recommend redirecting your iTunes signing process through sauriks on file server to future-proof your 3GS jailbreak through all future updates.

AFTER ADJUSTING YOUR ITUNES SETUP, YOU SHOULD STILL AVOID DOING AN ACTUAL FIRMWARE UPDATE. For all the reasons mentioned in this post, youll lose the unlock forever, and lose the jailbreak until a new one for 3.1 comes out. And theres no guarantee that your 3.0 signed files were captured by saurik in time. This is more about protecting your 3GS jailbreak in future updates its not a way to jailbreak 3.1 right now.
NOTE #1: the carrier sim unlock is a different story. Jailbreaking and unlocking have two different security mechanisms, and if you update your 3GS (or 3G) to 3.1, you will lose your carrier unlock, possibly forever. Even if you downgrade from 3.1 to 3.0, you will have lost your carrier unlock. So if you think youll ever want to carrier unlock your 3G or 3GS (or maybe give it away or resell it later as an unlockable iPhone), then please stay clear of all official Apple IPSWs. Youll soon be able to create custom 3.1 IPSWs using PwnageTool that let you pre-hack your 3.1 update in a way that preserves the carrier unlock.
NOTE #2: The custom IPSW flow using PwnageTool also ensures that even if Apple fixes all the iBoot holes, youll still be able to retain your jailbreak through later updates. Thats because a jailbroken iPhone will happily accept a custom (pre-jailbroken) firmware update even though its not blessed with Apples signatures. This is the once jailbroken, always jailbroken approach. Its very powerful, but it requires you to only update to pre-hacked IPSWs.
NOTE #3: None of this applies if you have an iPhone 2G, iPod touch 1G, or iPod touch 2G. The iPhone 3G is also unaffected by Apples signing process for the jailbreak, but it is susceptible to permanent loss of the carrier unlock as mentioned in note #1.

Will this later be applied to Redsn0w? I haven't used Pwnage tool since July because Redsn0w is so much faster.

this may be a stupid Q but thought i'd ask, if we update an app thru iTunes or our iPhone will that mess up the JB & Unlock? i've noticed a few app updates have said in order to sync you must be on 3.1

So just to clarify if I have already updated to 3.1 and have ATT can I go ahead and jailbreak? Or should I have waited to upgrade until the jailbreak came out. I have an iPhone 3g and from what I have read it looks like I can jailbreak. Any help would be appreciated. Love the site by the way. I check it upwards of 3 to 4 times daily. Has anyone done this?

This may be a stupid question, but what if you restore your computer back to when you had 3.0 weather a day or week or whenever and then plug the phone in to iTunes? I am aware that you can not physically re install an older firmware version but what about the PC restore as this changes the registry files. Or is it that it is the way the phone is designed that will not allow it to go back to an older version?

This may be a stupid question, but what if you restore your computer back to when you had 3.0 weather a day or week or whenever and then plug the phone in to iTunes? I am aware that you can not physically re install an older firmware version but what about the PC restore as this changes the registry files. Or is it that it is the way the phone is designed that will not allow it to go back to an older version?

This may be a stupid question, but what if you restore your computer back to when you had 3.0 weather a day or week or whenever and then plug the phone in to iTunes? I am aware that you can not physically re install an older firmware version but what about the PC restore as this changes the registry files. Or is it that it is the way the phone is designed that will not allow it to go back to an older version?

why would restoring your computer affect what the phone does if the phone does not allow you to re-install an older firmware?

I'm a newbie here; patiently waiting for the Dev-Team's release of the Windows unlock/jailbreak of 3.1 on my 16g iphone 2g (which I foolishly upgraded to 3.1 via itunes 9). I'm wondering "who" the Dev-Team is? Are they affiliated with Apple, or completely autonomous? Is their identity a taboo subject? If it is, I apologize in advance for asking!

I'm a newbie here; patiently waiting for the Dev-Team's release of the Windows unlock/jailbreak of 3.1 on my 16g iphone 2g (which I foolishly upgraded to 3.1 via itunes 9). I'm wondering "who" the Dev-Team is? Are they affiliated with Apple, or completely autonomous? Is their identity a taboo subject? If it is, I apologize in advance for asking!

The dev team is a team of people that make Jailbreaks and Unlocks for the iPhone. They are not affiliated with apple at all.

Anyone with a 3G used the pwnage tool to JB 3.1 how is it? any random freezes or reboots? I've read about the vanilla guys having this problem and just wondering if it's a problem with the firmware. There's people at my work with 3G updated to 3.1 and none o them have had any problems with freezing or reboots.