Search This Blog

14 March 2009

Upgrading the ADP1 from the default 1.0 firmware to the official 1.1 firmware

I was planning on using my OpenSolaris box to do my Android development, but currently I don't have the time to try to port the SDK.  I didn't want to allocate permanent memory to a linux xVM, so instead of using Xen, I decided to use VirtualBox to run Linux to work on the Android development...  VirtualBox can not be run on a system booted into HVM mode, so that meant running Linux in VirtualBox on Windows instead.  Since my x64 machine has a habit of crashing whenever I plug in USB devices anymore, I decided to do it on my laptop.

Unfortunately, after getting the SDK and Eclipse (yuck) and the JDK installed - I couldn't get adb to work inside the VirtualBox version of Ubuntu.  I gave up on that for now and decided to update the phone via Windows.

I extracted the SDK and then put the fastboot binary (available here) into the tools subdirectory.
When you plug the device in, it will prompt you for drivers. They are in the usb_drivers/x86 subdirectory.

Here's the dos prompt portion of the instructions above... how to boot, fastboot, etc is covered in that doc.

C:\devel\Android>adb devices
HT846GZ39410 device

C:\devel\Android>adb push 1.1\ota-radio-1_22_14_11.zip /sdcard/update.zip
1155 KB/s (0 bytes in 9131603.007s)

C:\devel\Android>fastboot update 1.1\signed-dream_devphone-img-130444.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >

Unfortunately, it never gets past that point. Trying to run 'adb devices' or 'fastboot devices' both show no devices.  Booting into the phone normally, adb works again.

The solution, unfortunately, is to replace the drivers again...




1. Boot device into fastboot, connect to PC
2. Navigate to Start > Control Panel > System > Hardware > Device
Manager > Universal Serial Bus Controllers
  a. Observe that there is a USB Mass Storage Device there
3. Right-click USB Mass Storage Device and select Uninstall
3b. unplug it and plug it back in
4. Windows then prompts with with New Hardware Found Wizard. Pointed
this to the USB driver included in the SDK

C:\devel\Android>fastboot devices
HT846GZ39410    fastboot

C:\devel\Android>fastboot update 1.1\signed-dream_devphone-img-130444.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 0.95.3000
Baseband Version.....: 1.22.14.11
Serial Number........: HT846GZ39410
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-baseband... OKAY
checking version-bootloader... OKAY
checking version-cpld... OKAY
sending 'boot' (1500 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (1722 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (53645 KB)... OKAY
writing 'system'... OKAY
rebooting...

At this point, 'fastboot devices' and 'adb devices' both work...

Go into the Market app and install “Latitude Enabler for Root”.  Reboot.

5 comments:

  1. Thanks man... Your post was very helpful for me to find why fastboot was stuck on 'waiting for device' for me.

    ReplyDelete
  2. I can't get adb to work in a Virtualbox Ubuntu guest either! It keeps saying "error: device not found", even when I've managed to get lsusb to list the device.

    Is this the same problem you had?

    DJC

    ReplyDelete
  3. This is one of the fantastic idea.I like your blog technique.This is one of the magnificent post.Thanks for share with us.

    ReplyDelete