Thursday, October 1, 2009

Upgrading Android Developer phone 1(ADP1) from 1.5 to 1.6

Discovering that HTC had posted new firmware images on their site, I felt like trying them out to see what new features it had in store, and if it improved performance in any way. However after just after downloading the images, discovered that they were wrong and not signed. And that to get the unsigned images to work one would have to wipe the userdata partition, as some google applications failed to start when opening when "signed" userdata was present. Well a bit later the proper images was posted, I downloaded them happy that I did not have to wipe my userdata.
To update the ADP1 there are two strategies: 1. The recovery image way and the fastboot way, I choose to use the fastboot strategy as I did the Recovery-image strategy when I upgraded to to 1.5. So when the image was all downloaded I booted the device in "fastboot" mode. I assume it is called fastboot mode as it boots right away, if it does not boot right away you probabily did something wrong. For my phone i booted up while holding the camera button down, but it might be something else on other phones on HTC's site it say you have to hold the back button down, as one might imagine that didn't work for me. When the phone is in fast boot mode, it should look something like this.

Some happy looking skateboarding Android characters and in the middle there should say serial something, press the back button until it says FASTBOOT.

 If you want to exit the fast boot screen you have to hold the MENU+SEND+END buttons down, where Send is the CALL button on the ADP1 and END is the power button(end call).
Well now you have to get the fastboot application, it can be found at HTC's site here.
The fastboot application should be downloaded to the \tools directory, as it is dependent on AdbWinApi.dll and will not start without it. If you want to run the fastboot application from another directory you will need to add the \tools directory to your PATH enviroment variable.

now you have to type something like this: 
fastboot.exe update
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
'waiting device'

If you do not get past the waiting for device part there is something wrong with the connection between the phone and the fastboot application. This may be that it is not connected, the driver migth not be installed or not installed properly, and the phone might not be in fastboot mode.
 When successfull there should be some output in the commandline looking something like this:
Bootloader Version...: 0.95.3000
Baseband Version.....:
Serial Number........: HT91RLZ00368
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
checking version-cpld... OKAY
sending 'boot' (1838 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (2088 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (58570 KB)... OKAY
writing 'system'... OKAY

When rebooting it might take a bit longer than usual. And then you're done, if you look at the Android market it should look something like this.

1 comment:

  1. Nice description.This is one of the pretty information.I like your blog definition.This is one of the enjoyable post.