I know that you may accidentally update your 3GS (New boot rom) to 3.1.3… Unfortunately you didn’t backup your ECID SHSH… Same as me
I can’t find anyway to jailbreak my iPhone … Here is the list of what I done in order to jailbreak my iPhone…
It seems that we should wait until the releases of OS 3.2 … Sorry!
Apple today released a new version of iPhone OS. This update contains 3GS baseband upgrade (05.12.01) so BE WARNED. DON’T UPDATE YOUR iPHONE 3GS.
There is not any notable change in this firmware.
iPhone 2G users : Can use redsn0w (download here) in order to jailbreak it. Please note that you should have firmware 3.1.2 file and you must point redsn0w to that files after updating (or restoring) to 3.1.3.
iPhone 3G users : If you need to unlock your iPhone baseband (using ultrasn0w, etc) DON’T UPDATE TO 3.1.3. otherwise use the above method.
iPhone 3GS users: BE WARNED. DON’T UPDATE YOUR iPHONE AT THIS TIME.
iPod Touch 1G users : Same as iPhone 2G.
iPod Touch 2G users : Do not update to 3.1.3
iPod Touch 3G users : Do not update to 3.1.3
The above information maintained from Dev-Team blog
Dev-Team released the new version of redsn0w that support iPhone OS 3.1.x.
You can download it here:
How is it different from PwnageTool? redsn0w doesn’t require a system restore like PwnageTool does (it doesn’t even use iTunes at all). On the other hand, PwnageTool can prevent your baseband from being upgraded when you upgrade your firmware, preserving your unlock. (redsn0w doesn’t touch your baseband but it doesn’t help preserve it during an upgrade either). redsn0w works by modifying your current filesystem, so your existing baseband, data and applications should remain intact. How is it different from blackra1n? - It uses our original Pwnage bootrom exploit for iPhone 2G, iPhone 3G, and iPod 1G. (Because it’s a bootrom exploit, it can’t be fixed by Apple without a new hardware release.) Note that redsn0w 0.9 does use the USB exploit for iPhone 3GS and iPod 2G running 3.1.2, but that exploit will be fixed in Apple’s next FW release. - It offers custom logos and verbose boot - It installs Cydia without needing a separate download - It’s not as fast (but redsn0w handles more variations)
How is it different from PwnageTool? redsn0w doesn’t require a system restore like PwnageTool does (it doesn’t even use iTunes at all). On the other hand, PwnageTool can prevent your baseband from being upgraded when you upgrade your firmware, preserving your unlock. (redsn0w doesn’t touch your baseband but it doesn’t help preserve it during an upgrade either). redsn0w works by modifying your current filesystem, so your existing baseband, data and applications should remain intact.
How is it different from blackra1n? - It uses our original Pwnage bootrom exploit for iPhone 2G, iPhone 3G, and iPod 1G. (Because it’s a bootrom exploit, it can’t be fixed by Apple without a new hardware release.) Note that redsn0w 0.9 does use the USB exploit for iPhone 3GS and iPod 2G running 3.1.2, but that exploit will be fixed in Apple’s next FW release. - It offers custom logos and verbose boot - It installs Cydia without needing a separate download - It’s not as fast (but redsn0w handles more variations)
Few minutes ago, Dev-Team released their new PwnageTool for jailbreaking iPhone OS 3.1
iPhone 2G (1st Generation) Use PwnageTool to do the magic and then restore with iTunes using your newly created .ipsw ‘nuff said, you don’t need to worry about anything, the baseband will be unlocked, the phone jailbroken. iPod Touch 1G (Original iPod Touch) Use PwnageTool to create a firmware image and restore with that .ipsw using iTunes. iPod Touch 2G (New iPod Touch) Sorry, no support at this time within PwnageTool, use Redsn0w for an earlier (pre 3.1) firmware release instead.
iPhone 2G (1st Generation) Use PwnageTool to do the magic and then restore with iTunes using your newly created .ipsw ‘nuff said, you don’t need to worry about anything, the baseband will be unlocked, the phone jailbroken.
iPod Touch 1G (Original iPod Touch)
Use PwnageTool to create a firmware image and restore with that .ipsw using iTunes.
iPod Touch 2G (New iPod Touch)
Sorry, no support at this time within PwnageTool, use Redsn0w for an earlier (pre 3.1) firmware release instead.
Torrent Link:
According to the latest news from DevTeam members :
DONT UPDATE TO OS 3.1, WAIT for the new version of pwning tools.
Stay Tuned.
Users who wants to use Installous, Appsyne, Mobileinstallation patch on their iPhones should wait for the new releases of DevTeam products (Redsn0w, PwnageTool, …) in order to Jailbreak their iPhones.
This week Apple will be all over the news with their announcements at Wednesday’s “Let’s Rock” event. But with so many new owners of the iPhone 3GS, and with so many new owners of the iPhone 3G (perhaps sold to them by these new 3GS owners)…now is a good time to send out this general advisory. If you update to Apple’s new software using the normal iTunes process, you will lose your ultrasn0w unlock. In fact you may lose it permanently, because for most people the baseband firmware cannot be reverted to a previous version (unlike the main application CPU firmware). But don’t worry…our PwnageTool program lets you update your main firmware without touching your baseband firmware, so you can still have the best of both worlds. But you must be diligent about saying “no” to your iTunes request this week to update your firmware.
This week Apple will be all over the news with their announcements at Wednesday’s “Let’s Rock” event. But with so many new owners of the iPhone 3GS, and with so many new owners of the iPhone 3G (perhaps sold to them by these new 3GS owners)…now is a good time to send out this general advisory.
If you update to Apple’s new software using the normal iTunes process, you will lose your ultrasn0w unlock. In fact you may lose it permanently, because for most people the baseband firmware cannot be reverted to a previous version (unlike the main application CPU firmware).
But don’t worry…our PwnageTool program lets you update your main firmware without touching your baseband firmware, so you can still have the best of both worlds. But you must be diligent about saying “no” to your iTunes request this week to update your firmware.
Stay tuned for more update & news.
I don’t know what exactly causes this problem but after hours of combat with my Mac, I’ve finally figured out how to go around this so let me first let you know what the problem was, I’ve read reports of other people having this problem as well, the problem only happens on Uni-body Macs running OS X 10.5.7 and redsn0w 0.8, the exact problem is that after you’ve put your iPhone into DFU mode, you have to wait forever for a reboot, the way to fixing this is simple, when Redsn0w is waiting for reboot, simply disconnect then reconnect your iPhone, don’t reconnect to different USB, reconnect to the same one because redsn0w will be looking for it there.
it didn’t happen before, it only happened when I updated to the version that worked for 3GS as well,if you haven’t updated redsn0w to this version, don’t expect this problem.
Both ultrasn0w & redsn0w updated to version 0.8.
Torrent Link for redsn0w 0.8
Cydia repo for ultrasn0w
iPhone Dev-Team:
About 5 hours ago (Thursday evening, less than a week after the 3GS launch), we were able to verify that the 24Kpwn exploit that the hybrid team used on the iPod Touch 2G is still present in the bootrom of the iPhone 3GS. That means we can apply the same sort of technique used by our current redsn0w tool to jailbreak and unlock the iPhone 3GS. This is great news, but how did it happen? Why didn’t Apple fix this in their normal cat&mouse fashion? Well it seems this bootrom was cut in about the August 2008 timeframe, so the unintended early reveal of 24Kpwn earlier this year didn’t affect the iPhone 3GS. For our technical notes on where the 24Kpwn exploit is in the 3GS, see here (pastebin hash of it is here). Our original blog post for when this exploit was first found is here. And yes, ultrasn0w will be able to be used on the iPhone 3GS for you unlockers! Important: Apple has not given up on the cat&mouse game, and in fact there are challenging aspects of the 3GS jailbreak that aren’t in the other devices. It’ll take some time to safely work these into our tools, but the fundamental weaknesses are there: The bootrom is exploitable via 24Kpwn, and the baseband is exploitable via ultrasn0w. (And just like with the 3G, ultrasn0w for 3GS requires that you not update your baseband when Apple comes out with new firmware.)
About 5 hours ago (Thursday evening, less than a week after the 3GS launch), we were able to verify that the 24Kpwn exploit that the hybrid team used on the iPod Touch 2G is still present in the bootrom of the iPhone 3GS. That means we can apply the same sort of technique used by our current redsn0w tool to jailbreak and unlock the iPhone 3GS.
This is great news, but how did it happen? Why didn’t Apple fix this in their normal cat&mouse fashion? Well it seems this bootrom was cut in about the August 2008 timeframe, so the unintended early reveal of 24Kpwn earlier this year didn’t affect the iPhone 3GS.
For our technical notes on where the 24Kpwn exploit is in the 3GS, see here (pastebin hash of it is here). Our original blog post for when this exploit was first found is here.
And yes, ultrasn0w will be able to be used on the iPhone 3GS for you unlockers!
Important: Apple has not given up on the cat&mouse game, and in fact there are challenging aspects of the 3GS jailbreak that aren’t in the other devices. It’ll take some time to safely work these into our tools, but the fundamental weaknesses are there: The bootrom is exploitable via 24Kpwn, and the baseband is exploitable via ultrasn0w. (And just like with the 3G, ultrasn0w for 3GS requires that you not update your baseband when Apple comes out with new firmware.)
REDSN0W PROVIDES SIMILAR FUNCTIONALITY TO QUICKPWN. Dev-Team Said
Using redsn0w is easy as 1,2,3 but the GUI is not good as Quickpwn
What we need
The process
