Archive for the ‘Mac’ category

How to Steal an Android Market App

April 10th, 2010

One of the biggest fear plaguing any freelance application developer is piracy. All their hours and hours of work to bring you the next useful little app that they hope you’ll enjoy. So why shouldn’t they be compensated for their hard work. Sometimes however this fear can hurt a new platform more than it can help. That is why in this article I will show you how easy it is to steal even a protected android market app.

Step One – Rooting your phone

Rooting your android device is similar to jailbreaking your iPod Touch or iPhone. Basically gives you the ability to perform tasks normally reserved only for the ‘root’ user of the device. The method of rooting vary greatly depending on the device. I personally own a T-Mobile MyTouch 3G Limited Edition (fender) which is identical to the new T-Mobile MyTouch 3G v1.2 with the headphone jack on top, the only difference is design, and the size of the miniSDHC card that comes with it. I rooted my phone by following the instructions found in this XDA Developer forum thread. If you have one of the older MyTouches you can easily find how-to guides on the same forum corresponding to the Magic 32A and 32B.

Warning: Like most things in gadget life, performing an action such as above not only has the possibility of voiding your warranty, but can also brick your device, that is to say it’ll be no better than a brick that won’t even turn on. So proceed at caution. It is very important to not only carefully read any instructions (such as provided by the link above) but also to verify that your device actually matches the instruction’s requirements. Most people who do this tend to have no problems, but those who fail to actually follow instructions have a very good chance at flashing the wrong recovery or radio image.

Once you are rooted, you can download the Android Software Developer’s Kit, or find the ConnectBot App in the market place. Sometimes protected applications (like the free Paypal app) may not show up after rooting, usually installing the Market Enabler fixes this.

Step Two – Purchase

For this demonstration to work we need to make a purchase. For this article I’ve decided to purchase Retro Defense by Larva Labs. I’ve always enjoyed the games from Larva Labs.

Ok, so we have purchased the game, now what?

Step Three – Back it up

With your rooted phone you can now either open up ConnectBot, or in your terminal run “adb shell” (from the SDK).

Once you are in the terminal as root (you may have to type su if you see $ instead of # to elevate yourself as the root user), you can then follow the following commands, to make a directory and copy the game to that directory.

# cd /sdcard
# mkdir /backapk
# cd /data/app
# ls (you'll see a screen showing you the file content, find the file you want)
# cp com.larvalabs.retrodefense.apk /sdcard/backapk

You may be prompted by SUuser application to allow Connectbot root access (if you used adb shell instead you won’t see this prompt)




At this point all you have done was make a backup of your app/game onto the SD card. Protected application usually exist in /data/app-private as an apk (leaving a small .zip in the /app location)

OS X Quick Tips: Windows 7 x64 on a Macbook

January 13th, 2010

I’ve been a mac user off and on since 2002; It wasn’t until early 2008 that I moved strictly to using a mac for my everyday affairs. I thought it would be a nice gesture to once in a while throw up quick Macintosh related tips, especially as it pertains to my early 2008 13.3″ Macbook.

Right now Windows 7 nor 64bit OSes are officially supported by Apple for this particular model of Macbooks. Officially the only non-pro macbook that should be able to install bootcamp onto Vista 64bit is the late 2009 13-inch Macbook.

There is however a quick way to get around this, and in my particular case using Windows 7 x64.

Normally you would execute the setup executable from your OSX installation DVD, in my case Snow Leopard 10.6. But instead once we’ve installed Windows 7 (x64), we’ll want to type ‘cmd’ into the run prompt. However be sure to right click it and select ‘Run As Administrator’.

Once the command line interface has appeared, navigate your way to the installation DVD, followed by the Apple Driver’s folder.

cd D:
cd drivers\apple

Within the folder you’ll notice a pair of msi files, these are installers. However trying to execute these from windows explorer will complain that they need to be run from an installation shell with administrative ownership. However since we’re running cmd as an Administrator we can simply run the msi package.

BootCamp64.msi

If your luck was as good as mine, this should install everything successfully.

Mighty and Magic Mouse

In some cases you may notice that your mighty and/or magic mouse may stop functioning after successfully installing the bootcamp drivers. What happened was me, was I could not connect to either device. The quick fix for this was to reboot into OSX , and remove or un-pair the mouse from OSX. Then from there you should be able to connect to the mouse in Windows. Reconnecting the mouse on the OSX side did not break the relationship on windows.

The mighty mouse for the most part will function fully with the scroll ball and side buttons. The magic mouse however would not scroll without a small hack found here: Uneasy Silence, where I downloaded the 64bit installer.

The mighty mouse as well as the macbook’s trackpad worked quite exceptionally in Windows 7, with all the normal functions I expected such as tap to click/right-click. The Magic mouse on the other hand after installing the hack, did work, but was a little quirky at times. Worst case scenario was to fall back to the trackpad which worked fine.

Why 64-bit

I don’t wish to get into a lengthy discussion about the benefits or disadvantages for that matter of 64-bit version 32-bit, which can be found numerously online. But simply put I did not like to waste a 1GB of my 4GB rams due to being forced to use the 32-bit version of Windows in Bootcamp.

Why Windows 7

Personal preference mainly. The combination of Windows 7 with Bootcamp 3.0 made it more ideal to be up with the times while still enjoying the stability I had with Windows XP but UI improvements of Vista. Also Bootcamp 3.0 brings HFS+ reading capabilities to Windows making it easier to access files on the Mac Side. While you cannot write to HFS+ partitions without using additional software, it is useful either way. I spend 98% of my time on the OSX side, normally I would just open VmWare Fusion to run XP in order to determine how my work appears under Internet Explorer. Installing Windows 7×64 via Bootcamp was a “Because I could” move more than anything else.

Hopefully these quick tips may help someone who has a stronger reason to run Windows 64-bit on their Mac, especially those not officially supported by Apple. Remember you need at least an Intel Core 2 Duo processor to even think about running 64-bit on your Mac.