To begin, let’s look at the sizes for the [...]]]> This post is in response to yesterday’s article that claimed the G1 would not receive future Android updates like Donut and Eclair.  T-Mobile responded they would work with Google to introduce “future software updates”, but that still doesn’t explain how G1 owners will get Donut.

To begin, let’s look at the sizes for the default partitions of the T-Mobile G1.  These sizes are defined by your device’s secondary program loader(SPL) and do not change.

The partitions of the T-Mobile G1.

The default partition sizes of a T-Mobile G1:

• dev: 49460K
• sqlite_stmt_journals: 4096k
• system 69120K
• data: 76544K
• cache: 69120K

The largest partition is data which is where all your apps are installed.  Many users have experienced this filling up after installing 40-50 apps.  The next largest partitions are system and cache.  System is where the Android operating system is installed and cache is where OTA updates are stored.  Note they are the same size.  The cache needs to remain large so that system updates can be downloaded and stored on the device before flashing.

So how full exactly is the system partition where the Android OS is installed?  Out of an available 69120k of storage, 68780k is being used as of the last official T-Mobile update(CRC1).

The system partition free space. Virtually zero.

I tried to make a pie chart, but it was a solid circle.  Of the total available space in the system partition, 99.5% is being used. This means there is only 340K of space left for future system updates.

As mentioned in my previous post, Google had an extremely difficult task of making Android 1.5 (Cupcake) even fit on the G1.

“Where the situation is really tricky is that the system partition on the US G1 was already filled to the brim with cupcake, and we were routinely flirting with build sizes that were a few dozen kB under the limit (or several MB over…), which means that even small changes to the core platform could very easily push the system size over the limit and staying under the limit took some effort”. Jean-Baptiste Queru, Android Software Engineer

If Cupcake barely fit on the G1, how do you expect Donut or Eclair to be installed? The only possible fix is to rewrite the partition table to expand the system storage.  This would require flashing a new SPL which would erase all data on the device.  I see no way T-Mobile would ever release an OTA update that flashed the SPL and erased all the partitions.

Could Google and T-Mobile technically find a way to update the G1?  Yes, they could engineer an update method to back data up to the SD card, but I just don’t see it happening.  The fact remains that the internal storage space is physically limited and this will never change.  It was a major oversight by someone and we have to live with it.

Others have suggested that Google should allow apps to be installed on your SD card.  Again, I never see this happening.  We know for sure this will not happen anytime soon because Donut and Eclair are already feature frozen and do not include this request.

What about the myTouch 3G?

The picture for the myTouch 3G is much better.  The sytem partition has been increased about 33% over the G1 and sits around 90 MB.

The default partition sizes of the myTouch 3G:

• dev: 49460k
• sqlite_stmt_journals: 4096k
• system: 92160K total
• data: 302848K
• cache: 81920k

The myTouch 3G still has space to spare in the system partition.

Out of the 92160K in available space, 71660K is used and 20500k is free.  This means there is about 20 MB of space left for future updates to the operating system.  It is highly likely that the myTouch 3G will get more updates, but for how long will that be the case.  Will that 20 MB of free space be enough to last a full 2 years of updates? Time will tell.

Please understand this post is not intended to scare you.  I just want to expose the situation now, so you are ready when the next update drops.  We loved the discussions in the previous post and welcome your feedback.  How do you think Google and T-Mobile should handle the situation?

The next treat on the Android menu [...]]]> For several months we heard the chant, “Where’s my cupcake?”.  Rumors and leaks were rampant as everyone tried to guess the official release date of the Android 1.5 build.  After many delays, T-Mobile finally rolled out the update and the complainers took a break to enjoy their dessert.

The next treat on the Android menu is Donut, which was recently demonstrated at Google I/O.  New features include a system wide search, multilingual text-to-speech, and gesture input controls.

If you missed the presentation video, here is Romain Guy showing off the Donut build (starts about 3:30).

Multiple sites have been referring to Donut as Android 2.0, but that is not the case.  A few of the Android engineers have made this point clear:

“Just to set the record straight, there are currently no official version numbers for future versions of Android, so let’s please not call anything “2.0″ as nobody knows what that refers to.” – Jean-Baptiste Queru

“First of all there is no such thing as Android 2.0. Donut is Donut, that’s all. Then we never said Donut would not be supported on ADP1 or G1.” – Romain Guy

“We don’t know what android 2.0 will be.  We are doing all our work by pastry and someone on the marketing side makes up the version number later” – Mike Lockwood

So while Donut will be released this year, Android 2.0 is quite a few more pastries away in the future.  If you are wondering when Android 2.0 will drop, there is no answer in site.  Keep an eye on the official Android roadmap, but it hasn’t been updated since early 2009.

G1 Lifecycle

While we are on the subject of updates, let’s discuss the lifespan of the T-Mobile G1.  The phone should receive the Donut update, but there are concerns if it will be compatible with later Android builds.  The problem should be no surprise to heavy Android users – the G1 is limited by its small internal memory.

Already, we have seen this space issue become a problem for G1 owners trying to load Magic and Hero builds of Android.  Some roms require a new SPL, secondary program loader, which repartitions the internal storage to free up more space.  Other builds require that some data is loaded onto your SD card to make up for the limited space.  Either way, the phone must be hacked which doesn’t fly for an official T-Mobile update.

This point is again explained by more Android engineers:

“If the data doesn’t fit on /data, no amount of backup/restore will make it fit. It just doesn’t fit.  An upgrade can require to wipe /data, which is not acceptable on the G1″ – Jean-Baptiste Queru

“Also I think the chance that we deliver an OTA update to existing devices that repartitions the flash storage as part of the update is…  very small.” – Dianne Hackborn

With these physical limitations in place, the days of the G1 could be numbered.  HTC has addressed this issue in new phones by upping the internal memory, but where does that leave all the early adopters?  All we can do is wait and see what happens.

In order to better understand this upgrade process, allow us [...]]]> Why is T-Mobile holding up the release of their cupcake update?  Why would you want to install the cupcake update manually, when you will eventually get it?  What are the pros and cons of using a non T-Mobile build of Android?  Where is my cupcakes?

In order to better understand this upgrade process, allow us to examine the relationship between HTC, Google, and T-Mobile.  HTC is the hardware manufacturer of the G1, Google develops the Android operating system, and T-Mobile sells the device to end users with a service contract.  All three companies are members of the Open Handset Alliance which exists to push the Android platform.  A similar comparison that is more familiar with many of you would be the way Dell, Microsoft, and Time Warner operate.

Who is really in control?

So what does any of this have to do with Cupcake?  Let’s look at the PC side first and see how they operate together.  Microsoft develops the Windows operating system and then Dell pays for a license to distribute it on their PCs.  Does Dell ship out a plain vanilla version of Windows? No.  They take the operating system and then modify it by adding additional software and drivers for their equipment.

Time Warner basically provides no role in the operating system, except that they choose to offer support for it.  If you would like, you could take your Dell PC and load a version of Linux onto it, but then Time Warner would not provide you with technical support.  They exist in this scenario for one purpose, to provide you internet access.

Now let’s look back at Android and examine the similarities.  When Google releases a new version of Android, T-Mobile takes it and adds their own software like MyFaves.  At the same time, HTC releases their own images of Android that lack the T-Mobile branding.  They do this so that developers can take the latest release and test it to ensure compatibility with their applications.  Just like in the PC world, if you do not like the version of the operating system that shipped with your device, you can install an alternative.

The huge difference between these two scenarios is that Microsoft Windows is a closed operating sytem and Android is open source(mostly).  Since Android is open source, it is actually encouraged that users take the operating system and modify it to their liking.  And that is exactly what has happened.  Android enthusiasts like Jesusfreke have taken the Android operating system and modified it to include new features like multitouch, installing apps to your SD card, WiFi tethering, and more.

Pros of an alternate version of Android

The biggest advantage of having an alternate version of Android is freedom.  Instead of allowing T-Mobile to dictate how you use your phone, you have the power to choose what apps are installed on your device.  Even if you do know how to modify the operating system yourself, there are many versions out there including releases from Jesusfreke, Haykuro, and The Dude.  The highlights of an alternate build are:

• Full root access to modify the operating system however you see fit
• Support for new features like multitouch
• More frequent updates vs T-Mobile
• Ability to upgrade on your own schedule and not T-Mobile’s
• Option to install other Linux distros like Ubuntu

As you can see from the recent cupcake update, the root users had several weeks head start to play with the new Android 1.5.  T-Mobile USA has yet to confirm the details of their rollout and it could be weeks before everyone gets it.

Cons of an alternate version of Android

The real power users would tell you there are no cons of an alternate build, but the average person could run into difficulty.  And when they run into difficulty, where do they turn?  That is the main concern at this point in time.

If you are not running an official T-Mobile version of Android, they are not likely to offer you support when you run into problems.  Thankfully, the community of root users grows every day and many people are willing to help.  So instead of picking up the phone to dial T-Mobile support, you might ask your question via Twitter or any of the Android forums.

Another concern that has not really been discussed is T-Mobile’s position on the alternate builds.  To date, I have seen nothing from them that would indicate they frown upon it.  We are in essence like their beta testers and I believe we contribute greatly to the community.  If they have accepted us this long, I doubt they will move to disrupt the open source community.

So should I root my phone or leave it alone?

If you are coming to me and asking about rooting your phone, it really depends on your technical knowledge.  Each month that passes the upgrade process is simplified, but there are still quite a few hoops to jump through.  In the future it might be as simple as 1-click and I would suggest it to more people, but we are not there.

Look in the mirror and ask yourself this question: Am I comfortable loading an operating system on my home PC?  If the answer is yes, then by all means go ahead.  If you are not really sure, I’d sit on the sidelines a little longer and wait for the process to be refined even further.

If you are still curious about this whole root process, you can browse through our root guide that is a work in progress.  I’m not ready to remove the huge warning I placed on it, but you can still browse it over to see what is actually involved.

One cupcake does not satisfy all. We need more choices.

Update: T-Mobile has confirmed the cupcake update for next week and here is a video from Google to make the wait that much more painful.

I first wrote this guide several months ago, but decided not to post it.  After all the cupcake builds were released and people kept asking for help with upgrading, I decided to [...]]]> This guide is outdated and a newer version if offered.  Please visit How to root a T-Mobile G1 and myTouch 3G.

I first wrote this guide several months ago, but decided not to post it.  After all the cupcake builds were released and people kept asking for help with upgrading, I decided to touch it up and put it out in the open.  If you are interested in rooting your phone and installing one of the latest cupcake builds, please read the entire guide before getting started.

If you are nervous about upgrading or want more information on the pros/cons read our article about the different flavors of Android.

This article serves one purpose:  demonstrating the easiest method possible to root your Android device.  It is currently intended for the T-Mobile G1 and will be updated when other hardware becomes available.  If you do not know what root access is, then you most likely should not attempt to modify your phone.  Having a rooted phone is mostly for power users.

Preparing Your Phone For Root – Important Disclaimers

Before we begin to root your phone, let’s cover a few basics.

This guide is intended for US phones.  If you are in a country other than the United States, please visit the xda-developers forums for more information on rooting your Android device.

If you do not read and follow instructions, you will have trouble.  We are trying to make this guide as fool proof as possible, but if you do not follow instructions, you will have problems.  I suggest reading the entire guide before you start.  This way you can become familiar with the entire process.  Thankfully, most upgrade problems can be resolved by flashing the RC29 downgrade and starting over.

Make sure your battery is fully charged.  We do not want your phone to die out in the middle of an upgrade flash.  Go plug it in now while you read the rest of this guide.

Set aside at least 60 minutes to root your phone.  The entire process can be completed in about 30 minutes, but I suggest you plan on it taking longer.  We do not want you to get half-way through and then stop.  If you start the root process and do not complete it, you might be unable to use your device and make phone calls.

If you install a non T-Mobile build of Android, you will be missing T-Mobile apps like MyFaves. You can still update your MyFaves online, but will be missing the app for now.  If this is a problem for you, then do not upgrade.  Also absent from the Android Developer Phone builds are several of the messaging clients like MSN, Yahoo, and AIM.  If you need these apps, there are many replacements available in the market.

A WiFi connection will greatly reduce the total time required and I highly suggest it.  You will be downloading several files with some as large as 40MB.  Connect to a WiFi network when possible.  You could attempt this over 2G/3G but I do not recommend it.

The first time you root your phone, all data will be wiped.  Any data you want to keep must first be backed up before you begin.  Most of the important information on your phone is synced with Google, but there are other things you might want to backup.  Call logs, SMS history, and phone settings are the most commonly backed up items.  Thankfully, there are several applications in the Android Market that can backup most data on your phone.  MyBackup Pro from Rerware allows you to backup your data to your SD card or online.

Part of the root process requires you to format your SD card.  After you have backed up data to your SD card, be sure to copy it all over to your PC before formatting.  If you have an extra microSDHC card, I suggest using the spare for the root process.  Also note it takes several minutes to format your micro SD card to the FAT32 file system, so I suggest using the smallest sized card to speed up the process.

After you root your phone, you will not receive system updates from T-Mobile.  Part of the root process blocks T-Mobile from applying updates to your phone.  This is done on purpose to prevent a future update from removing root access.  The good thing is you can manually update your phone to a new custom version of the operating system.  T-Mobile tends to roll out new updates over the span of several days, but when you have root you can apply the update as soon as its available.  This update process for some root users has been simplified with the application JF Updater.  See the end of this article for more information on keeping your phone up to date.

If you run non supported software, T-Mobile will not offer technical support for you.  This can be a make or break issue for some people.  Instead of turning to T-Mobile when you have problems, you will turn to the community for help.  There are many ongoing efforts in the community to help people and most questions can easily be answered via Twitter or several Android forums.  You can of course, return to the official T-Mobile version of Android whenever you choose.

Part 1. Downgrade Your Phone to RC29.

Before we begin, let’s check the current build of Android you are running.  From the home screen, press the Menu button and select “Settings”.  From the settings menu, scroll to the bottom and click “About Phone”.  At the bottom of the about screen you will find the “Build Number”.  Look for the part that says “RC##”.  The numbers after RC indicate the release canidate you have installed.  If you have RC30 and above, you will need to downgrade back to RC29.  The purpose of this downgrade is to exploit a security hole that existed before RC30 was released.

In order to apply updates to your phone, we must first format your micro SD card to the FAT32 file system.  As noted above, when you format your SD card, it will erase all data.  Most micro SDHC cards are already formatted for FAT32, but some are FAT16 and I suggest doing it again if you are not sure.  Instructions for Windows users:

• Hook your phone up to your PC using a USB cable.
• Click the notification on your phone that says “USB Connected”.  Select the “Mount” option.
• Once the device is mounted, you will see a removable disk show up on your computer.  Right click the device and select Format.
• Pick FAT32 for the file system and click start.  Do not perform a quick format.
• When the format is complete, you can disconnect your phone by clicking “safely remove hardware” like any other USB device.

Now that your SD card is formatted, we can start the root process.  For this guide we will be using the root application created by Mike Moussa.  His app simplifies the process by including download links to the required files you will need.  It also scripts some of the commands to prevent you from making typing errors.

Download the root app here:  http://www.androidactivity.com/root/root.apk

You can either download the file on your PC or directly to your phone(I suggest phone).  Before we can install the file, we need to tell your phone to allow non-Market applications.

• From the home screen, press “Menu”.
• Go to “Settings” first then “Application Settings”.
• Check the box that says “Unknown sources”.

Now that we can install non-Market applications, we need to find the file on your phone and launch it.  If you are in the Android browser, you can go to menu > more > downloads.  If you have a file manager like Linda installed it should be located in “/sdcard/download”.  Click the file called “root.apk” and hit install.

Update:  Some users have reported the DREAIMG.nbh file gets corrupted when downloading over 3G/Edge.  To avoid this just download the file to your PC and then copy it to the SD card.

When the root application is installed, launch it from your application tray.  Click on “Step1: Download NBH file” to start the first download.  This file “DREAIMG.nbh” is what will downgrade your phone back to RC29.  Wait for the download to finish, then complete the following steps.

• Power off your phone.
• Holding down the camera button, power the phone back on.
• Wait for the bootloader to come up all the way, and press the Power button to begin the update.
• When the first part completes it will prompt you to hit the action key to continue.  The trackball is the action key.
• Once the update is finished, you can reboot your phone by pressing TALK+MENU+POWER.

Stop and Verify:  When the phone reboots, you should be greeted by a fresh install of Android.  Go through the setup process again for signing into your Google account.  You can double check that the downgrade was successful by checking your build number as explained earlier.  Press “Menu”, then “Settings”, and click “About Phone”.  Your version after the downgrade will read RC29.

Part 2. Install New Bootloader.

Now that we are running RC29, we can exploit the known security hole to gain permanent root access.  The next step involves replacing the SPL or secondary program loader.  This new bootloader is what allows us to load a custom build of Android.  Note that the SPL is independent of the Android build that runs on top of it.

Since the downgrade wiped our phones, we will need to reinstall the root application we used earlier to finish up the process.

Download the root app again here:  http://www.androidactivity.com/root/root.apk

Follow the previous instructions to install the root app and launch it.  We will now perform “Step2:  Download IMG and HardSPL files”.  The security hole we will be exploiting requires you to type a command on the physical keyboard.  After you click Step 2, wait for the download to complete and then perform the following steps.

• Go to the home screen and open up your keyboard.
• Hit enter, pause a second, then hit enter again.
• Type “telnetd” in all lower case minus the quotes. Ignore the contact search that comes up.
• Press enter again.

After typing the “telnetd” command return to the root.apk app and press “Step3: Protect your root”.  This step runs a script that will perform the SPL upgrade.  If you see any errors, it means the telnet session is not open.  Return to the previous instructions and try launching telnet again.  If you are still having problems with Step 3, reboot your phone and try again.  After the script runs, we need to reboot the phone to apply the update file.

• Power off your phone.
• Hold down the Home key and power the phone back on.
• When you see the triangle with the ! inside it, then press Alt+L to display the bootloader options.
• Press Alt+S to apply the update.zip file.
• When the update is finished, you can reboot by pressing TALK+MENU+POWER.

Part 3. Upgrade the Radio Image to support Android 1.5

Before we move onto the last part, we must upgrade the Radio Image to the latest version that supports Android 1.5.  The new radio image has been posted on HTC’s support website for download.  In order to apply the Radio update, we must download the file “ota-radio-2_22_19_26I.zip”.

Update: If the HTC download does not work, here is an alternate link to download ota-radio-2_22_19_26l.zip.

Once the file is downloaded, it must be renamed update.zip and placed in the root directory of your SD card.  This means to place it in the main directory and not inside any folder.  If there is an update.zip file already present from the previous steps, it is ok to overwrite the file or delete it.  When the radio image file is renamed as update.zip and placed on your SD card perform the following steps:

• Power off your phone.
• Hold down the Home key and power the phone back on.
• When you see the triangle with the ! inside it, then press Alt+L to display the bootloader options.
• Press Alt+S to apply the update.zip file.
• When prompted, hit Home+Back to write the image file.
• When the update is finished, you can reboot by pressing TALK+MENU+POWER.

Stop and Verify:  You can check the version of your radio image to make sure it updated.  Go to Settings > About Phone > Baseband version.  The version number should end in 2.22.19.26l just like the original name of the update file.

Part 4. Install Custom Android Build.

Now that the hard parts are over, we are ready to install a custom build of Android.  There are many to choose from, but I suggest the most recent build from JesusFreke.  His version includes multi-touch support in the browser and a host of other features.  I have chosen the JF build because it was voted the most popular and has been downloaded the most times.  There are also custom builds available from Haykuro and The Dude that we will explore in a future post.  For this last part, we will no longer use the root.apk application.  It links to an old version of a JesusFreke build that we do not want to install.  Instead, we will download the latest build from his blog http://jf.andblogs.net.

The file we want to download is JFv1.50 ADP1.5.

Please note that this cupcake build along with the others is based on the ADP version of Android and is different from the RC builds that T-Mobile offers.  The Android Developers Phone version is the build given to developers and lacks the T-Mobile branded apps.  The Release Candidate builds are approved and released by T-Mobile.  You can swap back and forth between build types, but you will need to wipe your phone each time.

Once you have downloaded the update file JFv1.50 ADP1.5 it must be renamed update.zip and placed on your SD card like before.  Make sure the file is named update.zip and copied to the main directory of your SD card.  The most common problems I have seen are Windows users who name the file update.zip.zip by mistake and others who place the update.zip in the wrong place.  After the file is in place we need to reboot and apply it:

• Power off your phone.
• Hold down the Home key and power the phone back on.
• Wait for the bootloader to display, then press Alt+L to display the bootloader options.
• Press Alt+W to wipe the data and cache folders.  You must wipe when going form a RC to ADP build.
• Press Alt+S to apply the update.zip file.
• When the update is finished, you can reboot by pressing TALK+MENU+POWER.

After the phone loads back to the home screen, you are now complete.  One of the first apps you should download is JF Updater.  This will make getting updates in the future much easier and you will not have to repete all these steps.

Stop and Verify:  Look at the list of programs you have installed.  You should now see Terminal Emulator.  This means you are now running a custom build.  Launch Terminal Emulator and type the following command to display what version you have:  “getprop ro.modversion”.  It should read JFv1.50.

More To Follow:

• Creating an ext2 Linux partition on your SD card
• Moving your apps and cache to your SD card
• Installing and using a WiFi Tether app

I could keep typing forever, but I will stop and let people check for errors.  Will update in the morning.