The whole efuse thing has been blown out of proportion. The idea that tripping it will send your Droid X to the Droid graveyard was a misconception. It does nothing more than keep you in recovery if you try to load an unsigned rom and stays there until you load official motorola software back on the device. And FYI, the Droid X has already been rooted with no issues. The issue now is trying to figure out a way to get past the signed software check so that you can load the custom roms instead of waiting for official releases from Verizon. Motorola will continue to have the right to prevent non-official roms just as we have the right to try to hack them on the device but we need not expect support if we break something.
http:/http://www.engadget.com/2010/07/16/motorola-responds-to-droid-x-bootloader-controversy-says-ef...
"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."
