SRL Archive - Open Source Communities

If the eFuse failes to verify this information then the eFuse receives a command to “blow the fuse” or “trip the fuse”. This results in the booting process becoming corrupted and resulting in a permanent bricking of the Phone. This FailSafe is activated anytime the bootloader is tampered with or any of the above three parts of the phone has been tampered with.

http://www.mobilecrunch.com/2010/07/14/droid-x-actually-self-destructs-if-you-try-to-mod-it/

:/ Disappointing. I was looking forward to the Droid X.

Apple has a similar thing on their OS and all their apps. There's ways around it as there probably will be with this

Of course there are ways of around it. That's not the point. It's more so that Android is all about being open and now if you do anything with that openness, you lose your device for good. It just bothers me.

360 also has eFuses but removing one resistor did the job.

Again, not the point. :p

Again, some company trying to fuck with an open software.

http://www.boygeniusreport.com/2010/07/15/reality-check-modding-the-droid-x-may-not-lead-to-a-bricked-phone/

EDIT: http://www.engadget.com/2010/07/16/motorola-responds-to-droid-x-bootloader-controversy-says-efuse/ It appears that the eFuse will not brick the phone.