wraggster
September 23rd, 2010, 20:59
http://www.blogcdn.com/www.engadget.com/media/2010/09/2010-09-23droidhotwire.jpg
That picture above is no joke -- that's where I ended up last night trying to revive my Droid X review unit. It was fun, in a hacky mad-scientist sort of way, but it's also really sad -- a testament to how Google approves Android device hacking with a wink and a nod, but doesn't provide any safety nets for its most passionate users.
Let's back up, though. How did I end up in such dire straits? It started when I had the nerve to update this Droid X to the leaked Android 2.2 build -- a simple process that involved installing the file on a microSD card and restarting. Unfortunately, since Motorola refuses to provide a sanctioned upgrade path from the leaked build to the official 2.2 build released earlier this week, I was forced to downgrade back to 2.1 to get back on track. Based on how easy the update was, this would be a piece of cake, right?
http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking/
That picture above is no joke -- that's where I ended up last night trying to revive my Droid X review unit. It was fun, in a hacky mad-scientist sort of way, but it's also really sad -- a testament to how Google approves Android device hacking with a wink and a nod, but doesn't provide any safety nets for its most passionate users.
Let's back up, though. How did I end up in such dire straits? It started when I had the nerve to update this Droid X to the leaked Android 2.2 build -- a simple process that involved installing the file on a microSD card and restarting. Unfortunately, since Motorola refuses to provide a sanctioned upgrade path from the leaked build to the official 2.2 build released earlier this week, I was forced to downgrade back to 2.1 to get back on track. Based on how easy the update was, this would be a piece of cake, right?
http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking/