I have a Nexus One phone that I bought to use for development. A little while ago, I installed Android 2.2 on it, only to discover that I could no longer get it talk to the Android SDK. ADB completely failed to recognise the device. It seems I wasn’t the only person with the problem, but there was no sign of a solution. As a development device, it was now effectively useless. Luckily, the development work I had bought it for was now complete, and so the Nexus One sat on a shelf gathering dust for a while.

Yesterday, I was going out in the evening to the Multipack Leamington Social and somebody there had wanted to take a look at the phone, so I fished it off the shelf and plugged it in to charge. After a little while, it gleefully announced that there was a system update available and would I like to install it? I was hopeful. Perhaps Android 2.2.1 would fix my ADB problem and allow the phone and the SDK to make friends again and once more start talking to one another. I pressed ‘Install’. The phone rebooted and commenced installation, and after a brief pause, this was the result:

And that’s it. It’s stuck there. It won’t even power down. I didn’t have time last night to deal with it, so I just left it and went out. I guess that’s yet another thing to try to sort out today then.

Oh, how I love my Android phone.

Update: So, with the help of Google, I figured out how to get out of that particular error screen. Holding down Power and Volume Up eventually gives me a menu which includes an option to reboot. That worked and I’m now back at 2.2, with my phone telling me I’m up to date. I’d still like to try getting 2.2.1 installed to see if that fixes my adb problem, but that particular adventure can wait for another day when I’m less busy.