It seems you can't hit a tech news site or read a magazine these days without encountering some mention of Android. If you've not been keeping up on the news, Android is a Linux-based OS, designed by Google that's geared to run on lightweight devices like cellular phones and Webpads. One of Android's key features is that developers can write code for the OS in Java, making it a very easy platform for developers to work with.
The first Android-powered product was the T-Mobile G1, made by HTC and known as the Dream. The Dream has a 528MHz ARM11 CPU, 192MB of RAM and 256MB of Flash, so it's a capable smartphone, and it's part of an open standards effort from the Open Handset Alliance and Google. As a result of Google's involvement, it's been touted as “The Google Phone” by the press.
For this article, I set out to see how many devices I could put Android on and how difficult each one was to get running. Because we're hearing buzz about Android-powered Webpads, phones and even Netbooks, I wanted to discover just what the hype was about. I elected to skip past the gloss and dive into the OS itself and see exactly what it takes to get it running on a device.
The HTC Dream/T-Mobile G1 phone (Figure 1) comes in a developer version that allows unsigned binaries to be run, and it does a few other things that the regular G1 doesn't do. Because I had a regular G1, I figured a good place to start my Android exploration would be to see if I could get the developer OS running on a release device. Not surprising, T-Mobile frowns upon anyone doing this and puts roadblocks in the device to prevent it from happening. Also surprisingly, it turned out to be really easy, as there are holes in the firmware that allow you to gain root access on the phone.
Once you get root, you pretty much can do what you want to the device, including flashing the developer version of the OS. The “Hacking Your G1/Dream” link in the Resources section of this article contains the details, but basically the steps are mostly standard Linux command-line fare, taking advantage of a bug in the firmware where everything you type at the keyboard is sent to the OS. (Try typing reboot on an older G1 at any time. It will reboot spontaneously!)
You most likely will have to downgrade your firmware to a version that has the known exploit, and then take advantage of the exploit to gain root, but once that's done, you can reflash the device with any firmware you choose, using the standard update method. If you choose to do this, standard disclaimers and waivers apply about breaking your hardware (see the Disclaimers and Waivers sidebar), as you're definitely doing something that has the potential to turn your several-hundred-dollar smartphone into an expensive brick. If you do decide to do this, however, I recommend JF's excellent 1.51 ADP build, as that retains root capabilities and allows you to run unsigned binaries (see the link to JF's Blog in the Resources section).
Once the latest build of the OS (code-named Cupcake) is on the now-rooted phone, you can build your own binaries for it, if you're a coder type, or grab things others have done from the Internet. Of course, if you do download someone else's binaries, standard disclaimers apply there too. Can you imagine the data charges that could be possible if you had a rootkit or trojan on your always-connected mobile device? This is exactly why T-Mobile doesn't want the devices hacked, as it could congest its network.
As getting control of a G1 was relatively easy, I started wondering about installing Android on other devices. A quick scan of my desk revealed an unused AT&T Fuze cell phone, otherwise known as the HTC Touch Pro (code-named Raphael100). The HTC Touch runs Windows Mobile, not Android, but the units are both made by HTC and seemed to have similar hardware. I began to wonder if it would be possible to run Android on that phone, because they had the same manufacturer.
I started researching the feasibility of running Android on the Touch Pro, and I discovered that a group of enterprising developers already had done this very thing. Luckily for me, they made their distribution available as well (see Resources), so getting Android running on the HTC Touch Pro was almost as easy as getting it going on the G1 (Figure 2).
As it turns out, getting Android running on the Touch Pro was as easy as downloading a .zip file of the distribution and unzipping the contents of that file to a MicroSD card. Once that was done, I put the card into the phone and used the Windows Mobile file manager to navigate to a directory on the card called tmp. Within that directory was a program called haret.exe. I ran that, and the screen on the phone went black, and then it showed me the familiar Linux kernel messages as it began to boot Android (Figure 3).
Just like the loadlin days, when a DOS program could bootstrap the Linux kernel into booting, haret.exe bootstraps Android from the Windows Mobile environment. Before long, I was greeted with the Android desktop environment. However, all was not right with this port of Android. Although I could launch some of the applications, like the contact manager and browser, the 3G modem inside the phone was not operational, nor were the microphone or speaker. About the only thing I could do was send and receive SMS messages, though it did do that exactly like the G1. Yes, just like the early days of Linux, it seems that device drivers for various pieces of hardware don't exist or don't work properly. However, this is a rapidly moving target, and the Android developers are working hard to make progress in this area.
Bill Childers is the Virtual Editor for Linux Journal. No one really knows what that means.
- Easy Watermarking with ImageMagick
- The Only Mac I Use
- Ubuntu & SUSE & CentOS, Oh My!
- New Products
- Promise Theory—What Is It?
- Integrating Trac, Jenkins and Cobbler—Customizing Linux Operating Systems for Organizational Needs
- Tech Tip: Really Simple HTTP Server with Python
- RSS Feeds
- Returning Values from Bash Functions
Linux Journal Annual Archive
Editorial Advisory Panel
Thank you to our 2014 Editorial Advisors!
- Jeff Parent
- Brad Baillio
- Nick Baronian
- Steve Case
- Chadalavada Kalyana
- Caleb Cullen
- Keir Davis
- Michael Eager
- Nick Faltys
- Dennis Frey
- Philip Jacob
- Jay Kruizenga
- Steve Marquez
- Dave McAllister
- Craig Oda
- Mike Roberts
- Chris Stark
- Patrick Swartz
- David Lynch
- Alicia Gibb
- Thomas Quinlan
- Carson McDonald
- Kristen Shoemaker
- Charnell Luchich
- James Walker
- Victor Gregorio
- Hari Boukis
- Brian Conner
- David Lane