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. Read the rest of this entry »
After a long wait.. finally.. iphone genius george hotz ( better known as GeoHot ) has taken up the challenge to unlock the latest baseband 05.11.07.
He calls this new unlock Blacksn0w.. as of now he is working on it and as soon as there is any update on this, we will post it here..
The wait for BlackSn0w has begun..
According to macgadget.de Apple released the first major update of Snow Leopard to developers (Beta1 Build 10B503)
Mac OS X 10.6.1 fix bugs and incompatibilities associated with the Dock, DVD playback, Motion 4.0 & more.
The iPhone OS SDK from Apple is wonderful, and being able to develop and debug on-device even without paying the entry tax is even more wonderful. To really take Jailbreak development to the next level, though – to develop Apps that don’t play nicely in Apple’s SDK playground – you are going to need the open tool chain. Here’s how to rock Xcode OTC style.First, what IS the open tool chain? Apple’s SDK gives you a bunch of APIs to work with. For example, there’s CoreLocation, which helps you interface with the GPS, there’s UIKit, which helps you interface with the display and other basic functions, and so on. These are great, and let you write full-featured apps for the platform and all devices running it. They aren’t very deep, though – they don’t let you do things like access hardware directly. They don’t let you do things like modify system code. Moreover, they weren’t publically available before the SDK was released.
Read the rest of this entry »
The making of a SDK to develope iPhone Applications on Windows Continues… Devs at WiSDK are making a Windows Compatible SDK for the iPhone [ Official Site of WiSDK ]. The software is still in Alpha testing and will soon get into Beta. Quoted by the makers:
With this tool, you can develop your personal applications. We supply you complete set tools, to realize your projects by the beginning till the end. WiSDK includes an environment of development code, an IDE for design interfaces, an iPhone simulator, and acompiler to prepare your applications for the distribution via platforms as Apple AppStore, Cydia, or the others.
From the Screenshots it looks pretty impressive: Check back here at CaziSoft.com for updates..
Yes you read that right.. Windows 95 can now be run on your iPhone.
Curious to check it out?
Follow the instructions below:
Screen Shots:
There is good news for iPhone developers who don’t want to pay Apple for iPhone developer application! Now you can update your iPhone to OS 3.0 and start on device debugging!!
Big thanks to Alex for great and easy instructions!
Requirements
The Process (iPhone OS 3.0)
Step 1 (This step will already be done if you followed our previous procedure, and you may not need to repeat it!)
Step 2 (Special Step for OS 3.0)
cd ~/Desktop chmod 777 script ./script
This will execute the script to patch the Xcode plugin. If it executed correctly, you should see something like this:
Note: You may notice that a number of the steps you remembered from last time are gone now. I believe the few-byte hack above takes care of all the steps. As far as I know, there’s no need to even modify your projects with that one Plist key, everything just works.
[Via alexwhittemore.com]
Few days ago I found an interesting article (in www.alexwhittemore.com) about “How to developing application for the iPhone (Jailbroken iPhone!). I can’t test it because I love my PC and don’t want to turn it to a MAC (Yes it’s possible to install MAC OS X on your own PC). Below you can find Step by Step guide regarding that!
The iPhone uses code-signing to restrict what gets run on the device. Under normal conditions, this means that John-developer signs up with ADC (Apple Developer Connection) and gets, among other credentials, a code signing identity. He downloads a certificate, plugs all the info into XCode, and when he compiles his project for debugging or release, it gets signed with this certificate. When it gets transferred to an iPhone (say, for debugging) or released to the App Store, this signature gets checked to ensure that the code came from a registered, trusted ADC member.
What WE want to do is run our own code, developed in XCode, on our iPhone without this valid certificate from Apple. Part of this process allows code from OTHER non-ADC-signed developers to run on other phones, but that’s not the real point. The goal of this tutorial is to make the Build and Go live-on-device debugging work on a jailbroken iPhone without the proper signature, in other words without the need to pay. Note: this does not allow you to develop for the App Store. This is only good if you’re only developing for yourself or you plan to distribute only for jailbroken iPhones/iPod Touches.
/Developer/Platforms/iPhoneOS.platform/Info.plist
<key>NATIVE_ARCH</key> <string>armv6</string> <key>PLIST_FILE_OUTPUT_FORMAT</key> <string>binary</string> <key>PROVISIONING_PROFILE_ALLOWED</key> <string>NO</string> <key>PROVISIONING_PROFILE_REQUIRED</key> <string>NO</string> <key>SDKROOT</key> <string>iphoneos2.2</string>
<key>SignerIdentity</key> <string>Apple iPhone OS Application Signing</string>
UPDATE 12/24/08: I realized after a few comments from other blogs that I totally forgot to add the step where you actually USE the code signing certificate you created. I believe that step 5 is correct, so please re-try this. Otherwise, the first post above from iphonesdkdev.blogspot.com should have, somewhere inside, what you need. If the procedure above doesn’t work, please try looking around that post and let me know what step I need to add. It’s difficult to recreate exactly what I did now that my setup works.
UPDATE 1/14/2009: One of the commenters pointed out a key point: After you’ve generated the certificate and configured xcode, you MAY have to restart to get things working, else you may get an “Codesign error: no certificate for identifier “iPhone Dev” was found in your keychain” error. If a restart doesn’t fix it, see my comment below following his.
Information in this post came from the following places:
Apple seeded iPhone developers with the first beta of iPhone Software version 2.2, which arrived as build 5G26 alongside a new version of the iPhone SDK labeled build 9M2611
See the latest news here
