By Chuong Nguyen | July 17, 2010 7:42 PM
Motorola has stirred up a bit of controversy with its eFuse implementation to prevent the use of custom or baked ROMs for the Motorola Droid X on Verizon Wireless. Users were originally concerned that the eFuse implementation may brick their device, rendering it as a paperweight, if an unapproved ROM image gets loaded, but Motorola says that the device won’t be bricked and instead will go into recovery mode. According to Motorola, users can re-install a valid ROM image at that point and the device should be okay; eFuse is supposed to protect the Droid X and other Motorola phones from unwarranted tampering, not lock the users out.
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 IntoMobile)