Motorola Droid X and Droid 2 won’t brick themselves after all, they’ll just get stuck in Recovery Mode
A couple of days ago we let you know just how serious Motorola is about not letting you run any custom ROMs on their Droid X and Droid 2.
Not only were these phones confirmed to have locked bootloaders, but it appeared that they were also employing a technology called eFuse, that would effectively brick your device if it detected a kernel, bootloader or ROM that was altered in any way.
And now Motorola has stepped up and officially made this story funnier.
So, they say, these things that were going through the blogosphere are not true. The phones won’t brick themselves, they’ll just only ever boot in Recovery Mode until an “official” software version has been reloaded.
And I guess technically it’s true. The Droid X and Droid 2 will not become bricks if you mess with their software components.
But they’ll be exactly as useless as bricks, since you can’t use a device that only boots to Recovery Mode.
It’s still off to Verizon and/or Motorola to reload ‘approved’ software, if they will indulge you.
So it’s like I said before. If you’re the type of person who can’t wait to root the Android device you’ve just bought, and want to try as many custom ROMs as possible, don’t buy the Droid X or Droid 2.
Other Android smartphone manufacturers are a lot more relaxed about this stuff, though warranties generally don’t apply in any case if you’ve got a custom ROM – keep that in mind.
If you liked the post, you might find these interesting too:
- Motorola Droid X custom recovery image booted, custom ROMs on the way
- Verizon Motorola Droid 2 gets root access
- Video: Verizon Motorola Droid X gets custom ROM. Sort of
- Motorola confirms locked bootloaders for Atrix 4G and others
- Motorola Droid X and Droid 2 will brick themselves if you mess with their bootloaders