Droid X eFuse Chip Riles Modding Community, But Should It?

Paul Lilly

Motorola's Droid X has been stirring up quite the stink on the Internet lately, with several websites pointing out how the device's eFuse chip could potentially spell the end of third-party mods.

Here's how it works. The eFuse chip is tasked with verifying the handset's firmware (ROM), the kernel, and the bootoader version. If it detects that something is awry -- like a third-party ROM -- the eFuse chip "ignites," so to speak, bricking the phone. The only way to undo the damage is to ship the device off to Motorola and hope that they'll be sympathetic to your plight. Perhaps you fell down a long flight of steps and through a series of bumps and bangs, you inadvertently downloaded a third-party ROM and installed it.

Sounds pretty gruesome, right? But let's back up a moment. It's now coming to light that the eFuse chip isn't anything new, and in fact it's included on all of TI's OMAP3 processors. Why is that relevant? Well, the gloom and doom scenario being played out in the press hasn't been an issue for past devices with the eFuse mechanism, like the original Droid and Milestone, and it would be odd if Motorola suddenly switched directions with the Droid X.

Let's not forget that the ability to mod is a huge draw for the Android platform, and something like this wouldn't be good for either Motorola or Google.

Would you be okay with Motorola locking down its hardware and bricking modded devices, or does something like this cross the line? Does all the hoopla surrounding eFuse influence your decision on whether or not to get a Droid X?

Around the web