Motorola’s Response to Droid X Bootloader controversy
You have probably heard all the noise from the angry shouts in the Android Community concerning the newly released Droid X, and it’s super locked-down bootloader. Motorola has gotten a lot of flak because they have made it next to impossible to root the Droid X, which is something that a lot of people who are active in the Android Community want to do so they can try out different custom ROMs on the unit.
There has been a rumor floating around that Motorola has so locked down this device, that it can sense when a non-native ROM is installed, and cause your phone to brick. The culprit of this supposed functionality? An IBM program called eFUSE, which allows the circuits of a device to be altered on demand, giving higher security to developers and manufacturers, and supposedly giving them power to brick as many handsets as they want.
According to a quote from an article over at Engadget, this absolutely not the case. eFuse does not brick the Droid X, but causes it to boot into recovery when it senses unapproved software. Here is Motorola’s response about this issue as stated in the Engadget article:
“Motorola’s primary focus is the security of our end users and protection of their data, while also meeting carrier, partner and legal requirements. The Droid X and a majority of Android consumer devices on the market today have a secured bootloader. In reference specifically to eFuse, the technology is not loaded with the purpose of preventing a consumer device from functioning, but rather ensuring for the user that the device only runs on updated and tested versions of software. If a device attempts to boot with unapproved software, it will go into recovery mode, and can re-boot once approved software is re-installed.Checking for a valid software configuration is a common practice within the industry to protect the user against potential malicious software threats. Motorola has been a long time advocate of open platforms and provides a number of resources to developers to foster the ecosystem including tools and access to devices via MOTODEV at http://developer.motorola.com.”
While not a popular response or stance, it is not fair to say that Motorola has been out to maliciously brick devices as retaliation for hacking up their ROM.
As for an opinion on this development of the lockdown of the Droid X, I think it is a bad move on Motorola’s part, the Android platform and community brought them from the precipice and made them lucrative again. They have begun to make impressive handsets again, and they have done so on the coattails of Android. I think it is always a bad move to alienate your strong user base by denying them something that does no harm to your brand, but yet gives them a reason to own and use your handset for longer than the expected life span. Let’s hope they do not make this corporate policy for future handsets.