We’ll see!

The first answers when hitting google will be to restore your phone. Unfortunately, you are not allowed to downgrade to an official version but would have to install iphone os 3.1.3 which is not jailbreakable (simply said). Unfrtnately jailbreaking and unlocking the phone is essential, because I do not have a Mr. T molie contract.

A little more googling showed up a possible solution, but reading through all of the posts it looked like the method does not reliably solve the problem.

After even little more googling I learned the differences between old and new bootrom. All you have to know is, that the old bootrom allows you to install custom firmware (CFW) images, which is exactly what you want if you do not have a factory unlocked iphone. The reason for this is the baseband version which gets updated on a restore with the official release by the time of writing and that this new baseband can not be unlocked and probably never will be. The crucial information was, that 359.3 is the old bootrom and 359.3.2 is the new.

I checked the bootrom version of my phone and was very lucky to find out that my phone runs the old bootrom version.

Restored the phone with CFW, ran blacksn0w, followed some instructions and the phone is running again. Upon connecting the phone, iTunes will offer you to restore the backup it has made the last time you synced and restore all your settings and sync all of your data (except the music).

Very relieved now, knowing that I can do this whenever I want and restore the phone to the factory settings (sort of and maybe, we can just enter the next step by checking out the tethering.

I guess the lesson learned here is you don’t reset the network settings unless you really have to, as that was where all the hassle started.

I hope this will be useful!

The place where you can get this: CocoaDevCentral

The article Learn Objective-C contains everything you need to get that basic understanding and it will take you approximately 5 minutes to read.

I know this is old news, but I just rejoiced over my finding that I had to share it.

This will place an .app folder in the following directory: /PATH_TO_YOUR_PROJECT/build/Debug-iphoneos/. This .app folder contains everything to run the application, but most importantly the binary.

Self sign your binary using ldid. You can also do this on your phone but I prefer to do it on the development machine. Ldid for osx is here. For convenience, add it as a build step in xcode:
* Under targets, your project, right click and select  Add, New Build Phase, New Run Script Build Phase.
* Type in /usr/bin/ldid -S FULLPATH_TO_YOUR_BINARY

Now use <code>ssh</code> to copy the .app folder to the /Application directory of your phone

$ scp -r YOUR_APP.app root@YOUR_PHONES_IP:/Applications


First time only:
If this is the first deploy of your application you need to respring in order to make the icon show in your springboard. I found respring to be handy because it may be operated via command line. Install it via apt-get:

$ apt-get install com.bigboss.respring


Basically it wants you to pay the 99$ for an ADC membership. I did not want to pay that while still toying around and not sure about when my application will be ready. Did some research and, of course, this “feature” can be turned of.

In order to finally deploy an application to your iPhone you will need it to be jailbroken, but that goes into another post

1. Switch off code signing in xcode plist

$ cd /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk
$ sudo vi SDKSettings.plist


Change the value of CODE_SIGNING_REQUIRED to NO.

2. Switch off code signing in Xcode

Open info for your project:

Navigate to the “Build” tab and the Code Signing options accordingly

Et voilà, no more error messages!

and after installing some of this:

http://linux.voyage.hk/

and a little tweaking, there is lots of nice things to come. Stay tuned!

cd /usr/local/stuff

tar cf - . | ssh remote "cd /backup; tar xf -"

Basically, you’re telling tar to tar up everything in your current directory (.) and send it to -, which is standard out; this is piped to ssh, which (once logged in) will send it to standard input of the process it runs, in this case tar.

Other way round:

ssh remote "cd /usr/local/stuff; tar cf - ." | tar xf -

will copy everything from /usr/local/stuff to your current directory.

(Original source: http://macosx.com/forums/unix-x11/16999-piping-tar-datastream-over-ssh.html)

$ java -cp h2*.jar org.h2.tools.Server

If you are using maven, as I do, the h2 packages reside in PATHTO/.m2/repository/com/h2database/h2/LATESTVERSION/.

The same information may be found at http://www.h2database.com/html/tutorial.html

A little bit of research brought up an answer to the problem. Source was the Java Security Manager. It is configurable through files in /etc/tomcat5.5/policy.d/ but it can be very tedious, because it you have to di it explicitly for every file. If you are the only one deploying to the server you can also disable the security manager tomcatwide by editing /etc/default/tomcat5.5 and setting TOMCAT5_SECURITY to ‘no’.