Few hours ago Dev-Team released their new PwnageTool that can jailbreak iPhone OS 3.1.3. Unfortunately this version can’t jailbreak iPodTouch 3G nor iPhone 3GS!
iPhone 3GS users still be aware to update to this new version of OS (3.1.3), if you update accidentally like me you have to wait until the next releases of Dev-Team tools.
You can find the whole article here at Dev-team Blog.
Official Releases
Unofficial Mirrors
Once again Alex posted some useful stuff about developing for a jailbroken iPhone. Below you can find it! Vital stats:
Let’s do it.
UPDATE: Corrected a problem with the run script build phase: corrected the directory names for the new version and copied the new phase that doesn’t include “resource_rules.plist.”
The Goal: we want to be able to click “build and go” in Xcode and get the app we’re working on to load to the phone and start up. More than that, we want to be able to DEBUG on the thing!
Abstract: Our methodology is slightly different this time around. This time we’re going to tell Xcode that it doesn’t need to codesign for iPhoneOS targets, then we’re going to tell it don’t codesign for iPhoneOS targets, then we’re going to tell it, well, actually, codesign but do it using our script, not your built in method.
The Process:
cd /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS3.1.2.sdk cp SDKSettings.plist SDKSettings.plist.orig vi SDKSettings.plist
<key>CODE_SIGNING_REQUIRED</key> <string>YES</string>
<key>ENTITLEMENTS_REQUIRED</key> <string>YES</string> and change YES to NO again.
cd /Developer/Platforms/iPhoneOS.platform/ cp Info.plist Info.plist.orig vi Info.plist
<key>CODE_SIGN_CONTEXT_CLASS</key> <string>XCiPhoneOSCodeSignContext</string>
<string>XCiPhoneOSCodeSignContext</string>
<string>XCCodeSignContext</string>
cd ~/Desktop vi script
#!/bin/bash cd /Developer/Platforms/iPhoneOS.platform/Developer/Library/Xcode/Plug-ins/iPhoneOS\ Build\ System\ Support.xcplugin/Contents/MacOS/ dd if=iPhoneOS\ Build\ System\ Support of=working bs=500 count=255 printf "\xc3\x26\x00\x00" >> working dd if=iPhoneOS\ Build\ System\ Support of=working bs=1 skip=127504 seek=127504 /bin/mv -n iPhoneOS\ Build\ System\ Support iPhoneOS\ Build\ System\ Support.original /bin/mv working iPhoneOS\ Build\ System\ Support chmod a+x iPhoneOS\ Build\ System\ Support
chmod 777 script ./script
255+0 records in 255+0 records out 127500 bytes transferred in 0.020355 secs (6263821 bytes/sec) 189216+0 records in 189216+0 records out 189216 bytes transferred in 1.200354 secs (157633 bytes/sec)
At this point, you’re done telling Xcode it doesn’t need to codesign. Now, we tell it don’t codesign:
Now you’ve told Xcode “don’t codesign”
mkdir /Developer/iphoneentitlements312 cd /Developer/iphoneentitlements312 curl -O http://www.alexwhittemore.com/iphone/gen_entitlements.txt mv gen_entitlements.txt gen_entitlements.py chmod 777 gen_entitlements.py
Now you’re good to go! But there’s just one last thing. You have to do this last part for every new project you make. Go to the menu Project > New Build Phase > New Run Script Build Phase. In the window, copy/paste this:
export CODESIGN_ALLOCATE=/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate export CODESIGN_ALLOCATE=/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate if [ "${PLATFORM_NAME}" == "iphoneos" ]; then /Developer/iphoneentitlements312/gen_entitlements.py "my.company.${PROJECT_NAME}" "${BUILT_PRODUCTS_DIR}/${WRAPPER_NAME}/${PROJECT_NAME}.xcent"; codesign -f -s "iPhone developer" --entitlements "${BUILT_PRODUCTS_DIR}/${WRAPPER_NAME}/${PROJECT_NAME}.xcent" "${BUILT_PRODUCTS_DIR}/${WRAPPER_NAME}/" fi
That will call the script you just downloaded in step 5 to sign our app with a fake signature. This is important only for debugging. If you do build and go otherwise (in debug build mode) the app will load onto the phone, and will launch and run manually just fine. However, if the debugger tries to launch it then attach to the process (as when build and go is clicked), the app will segfault and die, causing the error Error from debugger: The program being debugged is not being run
Error from debugger: The program being debugged is not being run
Perhaps the most confusing part about this error is that build and go works fine up until that point WITHOUT disabling regular code signature! If you sign with a fake identity like we used to in the previous tutorials, everything installs fine, but the legit CODESIGN generated signatures cause the segfault, whereas the gen_entitlements.py ones don’t. To further confuse, the regular CODESIGN in this version of Xcode happens last in the build process, wheras it used to be that the custom run script phase happened last before. Meaning we have to kill legit codesigning or it wipes out our fake codesigning. All one monster headache.
But that should do it. Take all those steps and you should be home free for JBDev without paying $99.
Oh right, except the one last (critical) part. You have to have a jailbroken iPhone, and it has to have Installd Patch installed! That part’s critical. You can find Installd Patch in the iphone.org.hk repo at http://iphone.org.hk/apt, if you don’t have it installed.
CREDITS: alexwhittemore.com
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)
In this guide I want to help you to choose the right firmware for your device with the speed in mind. I already test all firmware from 1.1.4 to 3.2.1 (the latest firmware as I write this article) on my iPhone 2G.
The speed factors are as below:
1.x
There is nothing to say about 1.x family because there is no AppStore on this family, So JUST FORGET IT!
2.x
If you remember the early versions of 2.x family (2.0, 2.0.1, 2.0.2, 2.1) is full of bugs so everyone decide to upgrade to newer version as soon as Apple release them. But by the releases of 2.2 the game changes. It’s stable, fast and accurate in action and also if you jailbreak it, it will bring all the good things that you need to enjoy your iPhone such as AppStore, Copy/Paste (clippy), Video recording (Cycorder), Bluetooth file transfer (iBluetooth), Background application (Backgrounder), etc.
3.x
The main feature of OS 3 is the “Push notification”. Actually there is no more notable things in this version (you can find full list here), all the things that they add to this version was previously resolved by jailbreakers. Beside that if you have to unlock your 2G using any kind of PWNing tools you will lose the Push ability, after that you will found a way called “push fix” by Dev-Team that bring push to your 2G but when you enable it, first of all your device will works very slowly and also you will get lots of false push alerts. The speed impact of the 3.x family on 2G was very ridicules, I think Apple intentionally do this in order to force 2G users to buy an iPhone 3GS. It may also happens because of jailbreaking.
Conclusion
If you want to have a fast iPhone 2G I suggest you to use OS 2.2 (if you already upgrade to 3.x you can easily downgrade it, i will post something about that in near future).
If you upgrade to 3.1.2 :
If don’t upgrade to 3.1.2 (stay on 2.2)
I remember the first day I got an iPhone, one of my friends had been using one for quiet a while and after a few short minutes of using his, I thought I gotta have one.
before that I was a long time Palm user and I really couldn’t work with buttons and I thought the iPhones keyboard would be hard to use but being an Apple fan and really loving the iPhone, I went and got one, at first i didn’t know much about jailbreaking or stuff like that but slowly I begun learning, the first time I jailbroke a phone was nearly a month after I got mine, it felt good and I wanted to learn more so I didn’t stop, in fact after only two years now, I have become what I consider a veteran in iPhone jailbreaking and unlocking, the knowledge I have is only gained by experience and cannot be written or given to others in anyway. Read the rest of this entry »
Look at this:
What do you think? Apple can detect cracked ipa! hah!?
Today I got this message while using IM+. I didn’t see any kind of limitation in IM+ after that message but I think jailbreakers have to find a way to resolve this issue. I think it’s time to update the cracking process, Installous, etc.
[iPhone 2G - OS 3.1.2]
DevTeam released PwnageTool 3.1.4 for Mac OS X that support iPhone OS 3.1.2 (iPhone 2G/3G/3GS, iPod Touch 1G/2G)!
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. For those who have been onboard the “unlock train”, simply install ultrasn0w via Cydia once you’ve restored to your custom IPSW. Don’t forget to turn off the “3G” setting in Settings->General->Network if you use T-Mobile in the U.S.A. SUMMARY: 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
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. For those who have been onboard the “unlock train”, simply install ultrasn0w via Cydia once you’ve restored to your custom IPSW. Don’t forget to turn off the “3G” setting in Settings->General->Network if you use T-Mobile in the U.S.A.
SUMMARY:
The guys at appleturk.net ( makers of iReb – the itunes 16xx error bypasser ) have released iReb 3.1 which solves the crash problem on windows and mac and also, as promised, they have released a tool for 3GS users ( which was a surprise ) that saves your ECID and SHSH so you can downgrade your firmware even after apple releases new firmwares and stops signing the old ones!!!
To download iReb go to http://ih8sn0w.com ( where ‘0′ is a zero ) and click the Windows or Apple logo depending on your OS.
Then, you can run iReb and follow the onscreen instructions.
For the custom firmware, you can either create one using this on mac on download one and use it for windows.
Screenshot:
Appsync (installd) is now available for iPhone OS 3.1 (& iPod Touch).
Appsync is a mobileinstallation patch for OS 3.x. As one knows in order to install cracked iPA files via iTunes, we need to install appsync (3.x) or mobilesintallationpatch (2.x)
How to install Appsync for OS 3.1
For more information about how to use Appsync please read the following articles:
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 Saurik: This will allow iPhone 3GS users who upgraded to 3.1 to downgrade to 3.0 even though apple stopped signing the 3.0 firmware the day 3.1 released. The guide to do so is expected by tomorrow.
There’s always a way out Apple..
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.
Today Apple announce iTunes 9 along with iPhone OS 3.1 (Build 7C144). As DevTeam said, iPhone users who wants to unlock their iPhones with Ultrasn0w should not update their iPhone to 3.1 and have to wait for new version of Redsn0w and PwnageTool.
Below you can find direct download link for iPhone OS 3.1
iPhone 2G – iPhone1,1_3.1_7C144_Restore.ipsw iPhone 3G – iPhone1,2_3.1_7C144_Restore.ipsw iPhone 3GS – iPhone2,1_3.1_7C144_Restore.ipsw
To get message delivery reports on your iPhone follow these steps:
