Tagged: Motorola Droid X
has denied the eFuse technology used in its Android smartphones will leave customers handsets "bricked" if they attempt to install unofficial ROMs, though the company concedes that the system will indeed be non-functional with anything other than Motorola firmware. "If a device attempts to boot with unapproved software" Motorola explains, "it will go into recovery mode, and can re-boot once approved software is re-installed."
"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."It seems the real difference between the rumors earlier in the week and the truth about eFuse - which is found in the DROID X, DROID 2 and other Motorola Android devices - is that users themselves will be able to "restore" their handsets rather than needing to send them off to Motorola to be reflashed. That's certainly the implication from the official statement. However, the end result is the same: if you want an Android device that's open to the various third-party ROMs available, Motorola probably shouldn't be your first port of call.
wrote yesterday about Motorola's confirmation that the DROID X, DROID 2 and - most likely - all future Android handsets from the company would come with a locked bootloader and thus make hacking pretty difficult, we didn't realise quite how difficult it would actually be. According to MyDroidWorld, Motorola's locking system uses a so-called eFuse chip that verifies the handset's firmware (i.e. the ROM), the kernel and the bootloader version. If it detects that a non-Motorola ROM has been loaded, then that's when the problem starts. If any of those three elements have been modified unofficially, the eFuse "blows" and the handset is bricked to the user. Now, the eFuse can be reset but that can apparently only be done with specialist hardware that Motorola themselves had; in other words, you'll have to test quite how happy the company is with you loading third-party ROMs and then trying to claim under their warranty. Considering yesterday's information, we're guessing Not Happy At All is the answer.
DROID X has finally gone up for sale, hitting Verizon Wireless' site for $199.99 after a $100 online discount (and with a new, two-year agreement). Your money gets you an 8-megapixel camera, huge 4.3-inch 854 x 480 touchscreen, EVDO Rev.A connectivity - complete with a 3G mobile hotspot app to share it via WiFi - and Android 2.1 with Motorola's updated MOTOBLUR social networking integration. Still undecided about the DROID X? Check out our full review over at SlashGear.
Motorola's Droid X launches this Thursday. However, while the device itself is high profile, it doesn't look like Verizon locations around the country are getting high profile numbers in the inventory category. According to some screen shots sent over to Droid Life, it looks like quantities are being kept at a pretty respectable level.