Froyo released too early?

Froyo released too early?

For those that are blissfully unaware, Google started pushing Android 2.2 (Froyo) to the Nexus One a little over 3 days ago. However, Google put the update file online for those users that wanted to do the update themselves manually (and avoid the wait!). However, after shortly doing so, Google promptly removed this file and nothing more was said.

Of course, the file found its way online anyway since many users had already downloaded it. It turns out that those users who downloaded this file and installed it manually may have installed an ‘unfinished’ version of Froyo, or at least one which was not properly audited. Sounds rather unlike Google if you ask me. The clincher is that those who have received the update OTA are showing no signs of the problem(s). However, the guys at QuietlyCoding managed to speak with someone within Google. Here is what they found out.

“…no one was actually sure what happened or how the OTA was received by someone outside of Google. … in trying to push the update internally to Google employees there were a few imei numbers in the push that were not supposed to be there.”

So it now appears as though that guy at TechCrunch wasn’t just a lucky so-and-so after all!

“The link to the OTA update was removed because it is not supposed to be circulating in the public. Google has not made a formal announcement relating to the removal of the OTA update from there servers either.”

It would seem as thought I was wrong. Even within Google, things can go wrong, and sometimes they do.

James Tromans

Contributing editor of, based in the U.K.