Skip navigation

Category Archives: Xtras

http://redwolfberry.com/rupertgee/iBlog/
http://redwolfberry.com/rupertgee/iBlog/

WordPress.com is the best blog host par none but nothing beats a self-hosted blog for flexibilities. So I have moved the blog to our own server.

http://redwolfberry.com/

See ya there.

In the past three days or so, many users can’t find “OktoPrep” from the Installer. I needed to find out why. Apple today also updated iTunes to 7.6.1. I wondered if it breaks anything for Mac users.

So here I go again, subjecting my iPod touch and myself to the tedious task of jailbreaking to find the answers.

Leopard, iTunes 7.6.1 (yup the latest one)
-After AppSnapp, Installer is version 3.0
-Tweaks (1.1.1) is not in it!
-Found and Installed the “Community Sources” package (ver 3.6). It was previousy installed by default.
-Tweaks (1.1.1) appeared with OKtoPrep inside!
-Installed OKtoPrep.
-Option+Update, no sweat.
-Jailbreak.jar, OK too.

The missing OKtoPrep issue is due to Installer not including the Community Sources by default like it used to. Mystery solved.

Moving on to jailbreak to 1.1.3.
-Whoops. iNdependance 1.4b2 is *not* compatible with iTunes 7.6.1.
-Jailbreaking failed. Sob sob.

Lucky for me I can use ZiPhone GUI 2.4.
-Ah, Jailbroken in 45 sec!
-I love Zibri. 😛

So iTunes 7.6.1 is not a recommended upgrade for Mac users who has to use the Official Dev Team GUI method to jailbreak their 16 or 32 GB iPod touch, or 8GB iPod touch on Tiger and/or a PowerPC Mac.
[Feb 24 Update] iNdependance has been updated to 1.4 beta 5, and compatible with iTunes 7.6.1.

iTunes 7.6.1 is perfectly alright with the ZiPhone GUI Method, except of course the ZiPhone only works for 8GB iPod touch, on Leopard and an Intel Mac.

nothanksalready098.jpg
One of the most annoying thing ever on iTunes (or Mac OS X for that matter) is the “No Thanks” button simply doesn’t work for some of us. Prior to today, clicking it even brought up an error message afterwards. At least Apple have fixed that error for me, but now the nag screen simply won’t go away. Since when did Steve Jobs become so bitchy and nags his worshippers?

dismis.jpg

To get rid of the nag screen, click the little “x” icon when you connect your iPod touch, and say “I’ll buy it once you operate an iTunes Online Store for Singapore.”

20060710-dsc_1354-th.jpg
Remember Singapore? Read More »

weird1.png
Quite cool eh? 😀

Just wiggle away those docked icons to the next page. The Dock need not be occupied.

That’s the handsome Gee Theme, in case you’re new here.

STE posted a valuable insight into the recent 1.1.3 firmware update. It’s important enough I re-produce it here for youre reading pleasure.

It’s true; the situation now is quite messy due to the different jailbreaking methods available. I had opted for the Nate True’s method even though I know it isn’t exactly right as it offers best 1.1.2 compatibility. But I have since gone with the official dev team method, despite losing the ability to install quite a number of useful apps.

If you must find out, here’s one way to know which methods a jailbroken iPod touch is using:

  1. SSH into your iPod touch.
  2. Try and navigate to /private/var/mobile/
    • If you can, the iPod touch has the right 1.1.3 structure.
    • If the directory cannot be found, or is a symbolic link (alias), you have Nate True’s special file structure.

 

_________________ The article is reproduced below _________________

The release of the 1.1.3 firmware has caused a ton of headaches for developers and package maintainers. Many packages store media and preferences under /var/root/Media and /var/root/Library. With the release of 1.1.3, most packages will now need to store that stuff under /var/mobile/Media and /var/mobile/Library.

For developers, they have to write their apps to be firmware version aware, so that they can read/write from the correct location, depending on what firmware they are running on. For packagers, we have to install/uninstall that stuff from the right place, depending on the firmware.

It’s a nightmare.

Nullriver has released the full 3.0 version – no beta any more – of Installer.app. This release allows packagers to install the stuff mentioned above into ~/Media and ~/Library and Installer.app will put it in the right place, based on the firmware of the device.

This version of Installer.app also provides packagers with the ability to check how much free space is available, before installing, so that we don’t fill up the root partition any more. It also adds features that will help in migrating applications out of /Applications to other locations. There is more – this release is really chock full of stuff to make life easier for all of us.

It is imperative that you upgrade to Installer.app 3.0 as soon as possible. By that, I mean NOW. Right now, today. I am going to start releasing package updates today that will rely on the new features. They will not install correctly on older releases of Installer.app. If you run into any trouble and find you need to manually download and install Installer.app, get it from here, which always points to the latest version. Other repositories will start using these new features shortly, too, so it really is in your best interest to upgrade right this minute. If you do not, and you have an issue installing any of my packages, my response will be “please upgrade, try again, and only come back if you still have a problem”.

To prevent this kind of chicken-and-egg issue in the future, one new feature in this release is the ability for the package maintainer to specify a minimum Installer.app version required for the package to install. Unfortunately, this time, we can’t really use it, because the older Installer.apps don’t understand that feature.

For a full listing of changes in this release of Installer.app, please see the “Featured” page in your current Installer.app.

-ste