droidX bootloader isn't going to blow up

Motorola has come clean about the eFUSE questions, and we're all relieved to hear the Droid X won't blow up if you try to hack it.  I can imagine that my questions were just a drop in the bucket and Moto had a stack of e-mail that they couldn't ignore.  They reached out to Engadget with the following, saying (among other things):

"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."

The good news is that your shiny new Droid X won't go boom if you try to hack it.  The bad news is that Motorola has placed another layer of security in an attempt to thwart people from customizing or modifying their Android phone.  One that I'm sure has a big old target on it now -- the biggest challenge draws the brightest people :)  I hope Moto's new trick doesn't work, and that they change their ways in the future, but I'm not expecting it.  In the end, all I really wanted was an official statement from Motorola, and they delivered.  Now it's up to us to show them the error of their ways. Check out the source for the full quote. [Engadget]


Reader comments

Motorola speaks: The Droid X will not self-destruct in 5 seconds (or if hacked)


I have no doubt that in time it will be hacked but the only thing that's going to change their position is $. We can hack it all we want, the only thing that's going to happen is their going to make it harder. So if you don't like the path their taking vote with your wallet not your mouth. I personally don't like the path so I'm not going to buy the phone. No matter how much I want 4.3 inches of android goodness

Well first you need to hack the bootloader engineering bootloader may work. Then theirs the efuse which looks at the kernel rom, and bootloader.etc its going to be a super hard nut to crack

I agree wholeheartedly with thebiz, the only thing that will change Motorola's no bootloader policy is a lack of funds.

Opt out of buying the device and you're saying something.

Besides, thebiz, if you really want 4.3 inches of goodness, the EVO is waiting.

The only problem with thebizz's idea is there's probably a lot more of the general public that just want a shiny new toy. As much as the development and hacking community has grown, I can't imagine that they make up even a marginal percentage of Droid X's consumer base. I say Motorola can keep putting this 'Unrootable' target up if they want to, but all that means is MUCH more publicity when the Dev community shoots it down. This is either an incredibly stupid marketing scheme, or an incredibly brilliant one. Imagine how much in demand this product would be if a root method comes along right about the time that 1.5 ghz devices start to drop? It would essentially extend demand on the device for at least another quarter.

I know the other side of things also. Their are way to many people who just want the toy and can care less how hackable it is. And that will show with the galaxy s line that's pretty much open. But having said that what's are best decision give up on Motorola it hack the crap out of their phone and throw it in their face. Your also right about being able to overclock it that's part of the reason the Droid is still going strong. But if the development community for instance gave up on Motorola and moved to HTC. They will feel it in the long run as people see if you want these things don't buy a Motorola device. That's my rant really just want to see open devices instead of manufactures acting as if the ugly useless skin they put on android is. So important that they have to lock the crap out of it to protect it. I personally would rather have vanilla android

Been Sitting on the fence with the x since this flaw first came to light. Until this i was ready to be the first in line on launch day. I have no plans of rooting however if i do decide to, i want the option. Even with this update i'm still not sure if i want this phone or not. If sprint worked in my area (3g would be fine with me) i would drop verizon and forget the motorola name for good. So for now i'm just going to see how long i can wait to get over a faulty bootloader vs how long i can wait for sprint to put up a tower in my area.

If the protection means that there is a hardware level assurance that the bootloader is secure, GOOD.

This means that there is a base level of protection against malware, spyware, etc. and I for one am willing to wait for approved updates if it means avoiding these things on my phone. It's only a matter of time before the Android community starts seeing malware (it's already happened on the iPhone, the hackproof holy grail) and of all the things I don't want to have to worry about getting a virus, it's my phone (well my car is #1 but the phone is up there on the list).

Actually, this makes it more suspect to malware. Wouldn't take 5 minutes to code something that tries to flash an "unapproved" file at your next restart, which instead of just plopping out an error like every other Android phone, locks you into recovery until you can get someone to place "approved" software back in place.

Moto didn't do this to protect you. They have their own agenda.

And as it stands to my knowledge android is pretty well sandboxed. Without root and su your not touching the system partition. Now stealing your data is a different story all together and to me that agenda Is to turn blur or whatever they load into their own proprietary os

You know where I'm coming from. Imagine an app that secretly dl's the wrong radio for your droid, then does the same trick Rom Manager does so it flashes it at next boot.

Now substitute any file, with the right name so the X stock recovery would try to flash it. As long as it isn't signed by Moto, enter eFUSE, and a trip to Verizon. My advice to X users -- don't sideload ANYTHING you didn't write yourself.

In all honesty, I can't say I blame Moto for making sure their device functions as designed. After all, making sure the device is as designed helps them with providing support.

However, as we all know, there are different ways Moto can accomplish the same goal while still allowing users of their devices to customize their device to the fullest. *sarcasm* Not like Google hasn't proved that possible. *sarcasm*

Like Jerry said, we need to show Moto the errors in their ways.
I'm sure most of you here are just like me. If it can't be customized then its pretty much worthless.
Which is hard for me to say about the Droid X, cause its so purty. :)