Skip navigation

Tag Archives: cydia

I’m not going to tell you what you can or cannot do, or what is right or wrong. When it comes to hacking and cracking, it’s best to adopt the politician’s mentality – there is no right and wrong, only winners and losers. So depending on your integrity (or the lack of it), you choose your own destiny and that of your mobile device. Now that we’ve got that out of the way…

For those of you running the firmware 3.0.1 on the new 3G S and want to have more than the standard apps that come by default with the phone or downloadable free from the App Store, read on.

Before anything can take place, your iPhone must first be jailbroken. As with all jailbreaking process and methods, all procedures done to hack the iPhone will have its risks, so proceed with caution.

I will assume you have had your iPhone already jailbroken. If not, kindly refer to “Jailbreak At Your Own Peril!“. If your 3G S is as free as mine, let’s move on.

Previously, upon a successful jailbreak, there were a number of methods that would allow you to install cracked .ipa files into your iPhone. I think the most popular of these is one that would require you to install openSSH from Cydia, log into WinSCP on your PC, modify some permission settings for a number of device folders, and renaming the mobileinstallation file, all while being on a wifi connection. This method was tried and tested by many to be effective, and although quite simple to do, it was still considered complicated to users who are not familiar with SSH and setting folder permissions. People without accessible wifi would find this method less than perfect as well. I was about to use this method myself yesterday when I stumbled upon another method much simpler by comparison.

This new method can be found at iPhoneheat’s blog. It is rather straightforward in nature and requires that you only download an executable patch (downloadable from iPhoneheat’s blog) which when activated with your iPhone connected to your PC, would give you similar results like above and enable you to install cracked .ipa files directly to your device. The fantastic thing about this method is you do not need wifi to perform the patch or install .ipa files. It seems this method would work with iPhones running the 3.0 firmware, regardless of device model. At least it was reported that it even worked for a first generation iPhone, provided it had been updated to the 3.0 firmware. I have successfully performed this operation on my 3G S running on the 3.0.1 firmware, and can confirm that it works too. Some prerequisites are in order, as given on that blog:

  • iPhone must already be installed with OS 3.0 (or 3.0.1 in my case)
  • iPhone must already be jailbroken (this you must do for the iPhone to be a great servant!)
  • PC must be running on at least iTunes (iTunes in my case)
  • PC must be installed with .NET Framework 2.0 (most newer PCs would already have this by default, if not head on over to for a download first)
  • iPhone must be connected to iTunes at least once before

If you do not want any unwanted surprises, please do not ignore the last prerequisite. It is simple to do, and I would recommend that you install at least one free app from the App Store via iTunes for even measure.

To check for .NET framework in your PC, just perform a search in Windows XP for .net through Start > Search > All Files and Folders, OR type .net in the Search box in Windows Vista.

My reply post at iPhoneheat’s blog after the successful operation was as follows:

For those of you with the iPhone 3G S running on FW 3.0.1, this method is confirmed working. Upon the manual reboot right after patching, you will come across the apple logo as reported, but the logo may stay on longer than expected, giving you the impression that the phone has hung, crashed or **worse* have been bricked. Just be patient and let the phone ride along for awhile…you will be pleasantly surprised with the image of your wallpaper in about 5 minutes and under.

Just to be certain, what I did was left my phone connected to the PC throughout, even after the reboot. I don’t think there should be a difference connected and disconnected, but just to be sure, you could follow what i did.

I have already had free apps from the App Store installed before this, so it was just a simple case of clicking (or double-clicking) one of the .ipa files in my hard disk downloaded before. If your PC does not recognize the .ipa file, just select a program from the list, and make iTunes the default program to run future files with this extension.

I’m running on iTunes and it works! Excellent work there Rizwan, and all concerned. Bravo for a job well done!!!

May the Force be with you on this…


In a previous post, I did mention that it was more natural to use finger motion to flick to page 5 on the springboard (screen pages on the iPhone) than to search for apps or folders using buttons and the D-pad joystick on other devices. What happens when you have double that number of pages and you want to launch an app which resides on page 8? Flick 8 pages from the Home Screen? Everytime? You have to be a hardworker or really enjoy flicking pages for a living to not mind doing that! For me, an app known as SpringJump is the surest way to go.

For those of you who needs this application badly, this will be one of the reasons you will need to Jailbreak, as the application is available for download only via Cydia at time of writing. At less than 90kb, the file is a small one that will make huge changes in the way you use your iPhone.


SpringJump allows one to place soft key buttons on any page of the springboard, buttons which when activated by touch will jump and bring you to the designated page indicated on the soft key button itself. There are a total of 9 buttons, ranging from Page 0 for the Home Screen, to Page 8 for the 9th screen at the end. To access the 10th screen and beyond, you would have to jump to Page 8 and flick to get to the pages at the end. This alone would have saved you 8 finger flicks out of a total of 9, if you were heading for Page 9 (10th screen). On top of that, the app also allows you to name each of the screen which then appears at the top of each corresponding screen. On the left is a snapshot of the home screen on my iPhone, where I have used only 4 of the 9 arrow buttons available. There is no point in cluttering my first home screen with arrow button nos. 1 and 2. You can see that now, the top of the first page is now labelled Home, as you will find Reference and Office on pages 3 and 8. The 16 icons on each page are vertically squeezed slightly together in order to allow room for this screen heading. You may also replace those dull grey arrow buttons with an icon of your choice. Very customizable.

There are other alternatives which provide similar functionality, such as Categories…but from reports circulating around, SpringJump is the most stable, and more stable than some of its competitors. If this is what you need or what you’ve been looking for, find and download it over at Cydia. It is simple to use on its own without having to refer to any manual.

Previously, I had thought that it wouldn’t be necessary to jailbreak the iPhone 3G S. With over 50,000 apps in the App Store of which 30% are free for download, is there a need to jailbreak the 3G S? Surprisingly, the answer is still YES! A resounding one at that.

For the less initiated ones amongst us, jailbreak is a process in which you modify the system and OS of the phone, allowing you to install third-party applications not approved by Apple. For many reasons, some good – most bad, Apple doesn’t want you to install apps which have not been tested by them, or tested but doesn’t meet their standard and requirement. It is a good call, considering that the majority of the millions of us are not tech-savvy enough to solve mobile phone problems often due to a buggy software. What then, for the more tech-savvy ones amongst us? The answer: Jailbreak.

Jailbreaking has its risks too, and while some steps may look simple, the whole procedure is not for the faint-hearted. Many users have bricked their phones (i.e. rendered useless), sometimes necessitating a trip to a phone outlet to get it sorted for a fee. There are reports of permanent damage which required direct exchange, but I somehow think that in bricking a phone, the damage is never permanent and can usually be reversed, with due diligence during the procedure and in the research prior to that. Most dead phones happen because people get too impatient and jump right into doing it without having read or heard all the horror stories. I was soon to learn that myself.

I decided to jailbreak for many reasons. Despite knowing that it would void the one-year warranty on a three-day old phone, I went ahead with it. The push factors to that decision must have been compelling ones. And they certainly are. Partly, it was the ego. You see, all my phones in the past, regardless of platform and OS, had been hacked to a certain extent. If I had done it to Windows Mobile and Symbian OS, what good reasons do I have not to do it on the Mac OS X? Void warranty? Nope, not good enough.

These devices, being rich in multimedia features and equipped with state-of-the-art sensors have one main goal in mind. That is to serve their masters to the best of their bestowed abilities. How can they serve well if restrictions are put on them? If they had flawed mortal desires like we do, they would be begging to be hacked! Crashes and hangs? You know, sometimes we allow ourselves trivial pursuits which may be bad or unhealthy for us in the short run, but what is life if not for living? What is an iPhone if not for hacking? Jailbreak us, I hear them beckon.

To please my 3G S with its trivial pursuits, I decided to jailbreak it on the third day. If I know I was going to do it someday, let it be at the beginning of ownership. The earlier you do these things, the longer you get to reap its benefits and enjoy its full’er’-fledged features during its limited specs lifespan, expected of any technology and mobile device in the market.

For obvious reasons, I will not be going into the real reasons of jailbreaking a phone. Maybe in future posts this will be self-explanatory. But I will outline my procedures in the following, including where I went wrong, so that those of you treading the same path as I did may learn to avoid the pitfalls I had stepped into. I begin:

Performing a process like jailbreaking in the wee hours of the morning has its plus and minus. Plus is no one is around to disturb you, and you are unlikely to receive a call at that hour that would throw you off-track. Minus is, if you’re not used to being awake at those hours, you may lose concentration as sleepiness gets the better of you. For me, sleeping at 5 or 6 am is routine, so the lack of concentration out of sleepiness wasn’t so much the problem. The problem was knowing I had to sleep by 6 am, and not having enough time to complete the jailbreak process by then. In a bid to rush things, I had left out the part on “having done sufficient research”. I had read in a number of post that the purplera1n method was best suited for the 3G S. I had known about the redsn0w method as well, but that required downloading huge files. While that was downloading, I went ahead with the purplera1n method.

Plugging in the 3G S to the laptop, I initiated the purplera1n jailbreak, and in almost an instant, the screen on the 3G S went blank and at the same time, the program on the laptop crashed. I knew then something dreadful had happen. The iPhone with a blank screen that failed to respond to button presses and the purplera1n software that kept crashing on the laptop confirmed this. It was only then that I did further research and discovered that in much later forum and blog postings, the creator of purplera1n had claimed that his brainchild will only work with firmware 3.0 and not with firmware 3.0.1, due to some differences in the kernel and patches. And it was also then that I learned that redsn0w 0.8 was the way to go. What a time to realise that!

At that time, the firmware versions (3.0 and 3.0.1) needed for the redsn0w to work was being downloaded. At nearly 300 MB each, it didn’t seem I was going to complete the jailbreaking, if at all still possible, that morning itself. I did a bit of further research (which were to save me further trouble later as I had come to know) before I retired for the night. Or morning. Before going to bed, I removed the SIM card from the iPhone and inserted it into my old Nokia E90. It seems the E90 was going to serve me for the day to come.

The complete download was almost finish when I woke up 4 hours later, and was done when I was ready to go to work. I decided to do my jailbreak in the office.

With the firmware versions 3.0 and 3.0.1 in my hard disk, I thought I was already on safe ground. I plugged my iPhone and connected to iTunes on the laptop. iTunes came back saying that the iPhone was in recovery mode and needed to be restored. Fine. To point to the firmware sitting in the hard disk, you would need to click the Restore button in iTunes while holding down the Shift key (in Windows). After that, iTunes will then prompt you to select the file on the hard disk to be restored to the connected iPhone. After selecting 3.0.1, iTunes then went online to seek approval from the Apple server. The message came back saying the device was not eligible for 3.0.1. Somewhere along those lines. I repeated the procedure with 3.0 and received the same response. I believe that it was only possible if I did not hold the Shift button down and allowed iTunes to restore my iPhone to the latest firmware available then i.e. 3.1. Thanks to much research during the hours before bedtime earlier, I had learned that going to 3.1 was a point of no return that had left many woeful iPhone owners with regret and sorrow. If I had to, that would be the very last resort when I have exhausted all resources.

With the 3G S still in recovery mode, I started the redsn0w program and ran it like normal. I did this with the SIM card back in the iPhone. It may be a necessary step as advised by some forumers. When I came to the part to install Icy and Cydia, I made sure that ONLY the Cydia tick box was checked. I had also learned during the research some hours back that installing both Icy and Cydia would result in a lot of problems. Given Icy’s lack of support and hence implied unreliability, I chose Cydia. This is also recommended by many in the online community.

A few clicks on the subsequent Next buttons and I began to see some activity on the iPhone screen. When the picture of a half-bitten pineapple appeared on the iPhone screen, I knew that I was on the right track, and that the jailbreak process was on its way to completion. The only thing I wondered then was whether my phone with its firmware 3.0.1 and its contents would still be there once this was over.

It only took about a minute or so after that before that familiar “slide to unlock” appeared on the screen, together with my selected pebbles wallpaper. I knew then that all was fine. Everything had been left as it was and the phone was finally restored, with Cydia sitting on the springboard. Excellent. Keeping the E90 back in the laptop bag, I was on my way with the iPhone once again.

For those of you with an unlocked iPhone 3G S running on the firmware 3.0.1, this would be the surest way to go. If your iPhone is a locked version, of an earlier model or with a firmware other than 3.0.1, a different method and further research would be needed.

The detailed step-by-step for the redsn0w 0.8 method outlined above can be found here.

Good luck!