Looks like a dev over at XDA-Devs (where else?) has managed to root the Motorola Droid 2. As this is the device's first root and it was just released, it's not surprising that the method is still dependant on manually typing a number of commands. The process requires adb and Motorola drivers to be installed, and involves pushing and executing the root file with ADB. While it doesn't look overly complex, it's probably not something suitable for more novice rooters.
Today I awoke to see a response from Tim Bray on the Android Developer's Blog regarding my previous article on circumventing the Android License Verification Library, and I almost completely agree with him. The License Verification Library is a very good start - above and beyond what, if anything, Google owes developers. Copy protection is and should be the responsibility of the developer. Google has given us a great tool, provided thorough documentation, and even open sourced the project.
Modder’s Monday is a weekly column about rooting, hacking, and other forms of modifying Android written by Jaroslav Stekl, a man who spends his days coding, hacking, hiking, and of course, writing for Android Police.
One of the many things that I love about Android, especially after spending several years with an iPhone, is how customizable it is - right out of the box. You can change your keyboard, tweak the status bar to make it work any way you like, change apps’ icons, and even install home replacements that alter how your homescreen works.
[Update: 8/24/10 @ 7:45 PM EST by Aaron] Tim Bray responded to Justin's article, but seems to have misunderstood the goal. Thus, Justin has written a follow-up article here.
This article was not written to teach people how to pirate or ridicule Google's Android License Verification Library (LVL) that handles communication with Google's Android Market Licensing Service.
I am very much against piracy, and very much pro-Google.
It seems a few community developers (@barakinflorida) have been inching towards releasing a functional, bone stock version of Android 2.1 for the Samsung Galaxy S (That is, without Samsung's TouchWiz interface). Their efforts are paying off, as this video shows.
The only big issues remaining lie in getting the camera/camcorder to actually, well, work. A relatively minor inconvenience, and a problem many developers have struggled with when developing full-ROM releases for phones with UI overlays.
Ok, so this is technically “so last month” too - it’s from July 30, and we just happened to miss it the first time around. Luckily for us, good ole’ ChiefzReloaded tweeted (or retweeted?) some pictures of CM6 running on the HD2. After doing a little poking around, I found that there’s a pretty solid build out there - it’s even CM6 RC1. As a result, nearly everything works on the device: GPS, camera (with flash), torch (for the camera LED), Adobe Flash, and so on.
MyDroidWorld has scored a big one today: they’ve hosted the Droid X Froyo ROM, thanks to the hard work of P3Droid, Birdman, and rootzwiki. Installation seems relatively simple, and boy is it a popular download: their server was bombarded with 15,000 download requests shortly after posting it.
Installation seems rather simple, assuming you're rooted and are running stock recovery:
This morning on Vodafone’s forums, a VF employee announced that the Froyo update for the HTC Desire would be rolling out on Monday. We knew it was coming soon - on August 12, we relayed that they expected it to roll out in 7-10 days - sans crapware. The update is rolling out a bit later than expected (August 23 would be 11 days) because they wanted to make sure they’d worked out all the kinks.
If you’re a rooted user, you’re probably familiar with the ADB command, and that it requires you to connect your phone to your PC with a cable. Enter adbWireles, which allows you to - wait for it - use ADB over WiFi.
The specifics of how it works are pretty technical, but here’s the laymans version provided by the dev (and translated from Spanish by the Goog):