Here is a download links for iPhone OS 3.1.2. I know that this is not the latest firmware but I think  everyone should have this files.

• 3.1.2: iPhone1,1_3.1.2_7D11_Restore.ipsw(2G)
• 3.1.2: iPhone1,2_3.1.2_7D11_Restore.ipsw(3G)
• 3.1.2: iPhone2,1_3.1.2_7D11_Restore.ipsw(3GS)

You can find full list of iPhone firmware (1 to 3) here.

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

• PwnageTool 3.15 Torrent  - PwnageTool_3.1.5.dmg.5344262.TPB.torrent
• SHA1 Sum = 16611fb60d088edd2fa5128e4f95f35d8e56a603

Unofficial Mirrors

• http://www.hackthatphone.net/PwnageTool_3.1.5.dmg
• http://www.ipodtouchmasterfr.com/files/PwnageTool_3.1.5.dmg
• http://apfelportal.de/host/images/PwnageTool_3.1.5.dmg
• http://zombisoft.com/tools/PwnageTool_3.1.5.dmg
• http://www.accesoriigsm.net/PwnageTool_3.1.5.dmg
• http://files.bestblog.de/iphone/PwnageTool_3.1.5.dmg

Once again Alex posted some useful stuff about developing for a jailbroken iPhone. Below you can find it!

Vital stats:

• iPhone OS 3.1.2
• Xcode version 3.2.1, 64 bit
• Mac OSX 10.6.2 Snow Leopard

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:

1. Make some Plist adjustments, starting with SDKSettings.plist:
   cd /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS3.1.2.sdk
cp SDKSettings.plist SDKSettings.plist.orig
vi SDKSettings.plist
   Find
   <key>CODE_SIGNING_REQUIRED</key>
<string>YES</string>
   and change YES to NO
   then find
   <key>ENTITLEMENTS_REQUIRED</key>
<string>YES</string>
and change YES to NO again.
2. Now, move on to the platform Info.plist
   cd /Developer/Platforms/iPhoneOS.platform/
cp Info.plist Info.plist.orig
vi Info.plist
   Three times, the following appears:
   <key>CODE_SIGN_CONTEXT_CLASS</key>
<string>XCiPhoneOSCodeSignContext</string>
   Find each occurrence by, in vi, typing the “/” key and CODE_SIGN_CONTEXT (typing / will open a “find” box at the bottom of the window)
   Replace the
   <string>XCiPhoneOSCodeSignContext</string> with
   <string>XCCodeSignContext</string>
3. And now the real bad boy, some binary patching of Xcode:
   cd ~/Desktop
vi script
   hit the “i” key and copy/paste:
   #!/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
   type the keys, in order: “:” “x” “enter”
   chmod 777 script
./script
   If it works right, you should see something like
   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:

4. With a new project open and ready to go (presumably you want to debug this one, though once you change these settings once, they’ll persist from project to project) open Project>Edit Project Settings (from the menu).
   Find “Code Signing Identity” and its child “Any iPhoneOS Device” in the list, and set both to the entry “don’t code sign”

   

   Now you’ve told Xcode “don’t codesign”

5. The final step is to tell Xcode “well, actually you should 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

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

If you want to use Appsync (installd, mobileinstallation patch, etc) on your iPhone you should wait for Dev-Team to release their new tools that support OS 3.1.3. I highly recommend you to wait…

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

With the releases of iPad Apple shown up a new OS to developers. iPhone OS 3.2 only support iPad as they said.

• Initial support for the newly released iPad
• Initial support for landscape springboards
• Includes new frameworks for recognising custom gestures, custom keyboards etc.
• Allows display output to an externally connected display for compatible 3rd party apps
• Allows user to change home screen background
• At this point, only applicable to the iPad and not the iPhone

Apple released their new tablet named iPad. As rumured it has a large (9.7 inch) multi touch screen, 1Ghz apple custom processor.

Actually there is nothing new because we see all these technologies in our iPhones. iPad has the same UI (as you see above) as iPhone. I think that apple made a big mistake by releasing iPad. They should work more on the UI, hardware, etc. There is no camera, no USB host, no more storage, … just 10 hours battery. Shame on you Steve!

Dev-Team released the new version of redsn0w that support iPhone OS 3.1.x.

You can download it here:

• Windows
  
• Mac

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)

It seems that Apple wants to release the new version of iPhone OS. iPhone OS 4.0 will be avabilbe only for 3G & 3GS versions of iPhone. It’s very bad news for who already have their original iPhone 2G like me!

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. Switching between pages.
2. Keyboard speed (while typing text messages)
3. Application execution times (I know that is mainly depends on the CPU speed)

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 :

• Overall speed reduction
• Battery life Get
• Some Cydia application did not work properly in all situations such as iBluetooth

If don’t upgrade to 3.1.2 (stay on 2.2)

• There is no Push Notification
• You can’t arrange app icons using iTunes
• You can’t play multiplayer games (the games that runs on more than 2 iPhone)
• SMS delivery report (actually I did not test it on 2.x)

NEXUS ONE is a new mobile phone from Google!

Full spec here.

Nothing to say…

Hmm …

Let’s think about write something about web development in  this blog …

I know that the main content of this blog is about iPhone

…

I found a new application for iPhone in Cydia called SIManager. You can manage your SIM contact in your iPhone. In this version (1.4 beta) you can also export your contacts to SIM card.

In order to install SIManager you must add the following repo in cydia then select SIManager package and install it.

• http://test.beyouriphone.com