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

19

Comments

+ Add a Comment
avatar

Fecal Face

If I buy a house, I want to put whatever furniture I want in it.

If I buy a phone, I want to install whatever ROM I want on it.

Why should anybody be able to tell me what I can / can't do with my own property?

avatar

nadako

If we the modding community wants to mod our phone then let us they have no right to tell us what we can and cant do to our phone. And second thing if it isnt stated anywhere on the phone and or guide then the manufacture is at blame for breaking our phone. Seriously why do you think i got a droid. Moding a phone is great fun.

avatar

Curtai

why would they bring this up now?

avatar

HeartBurnKid

You sell me the device.  You have no right to tell me what I can or can't run on it afterwards; it is then my device, not yours.  End of story.

avatar

mdkplus

Perhaps this comes as a result of the Cyanogen mod? Just sayin.... and if it is then blame GOOGLE

avatar

jxchamb

Based on principle alone I wouldn't buy a Droid X.    This is just insane to think that a company would do something like this to their customers.  WTF??  If you pay 200 bucks or more for this phone then you should be able to what you want to it.   It's like putting a custom exhaust on your car and then realizing that Honda put a chip in the engine that won't let it start anymore because you modded the car. 

avatar

burntjuggalas

it personally doesnt affect me because 1. im getting the samsung captivate here in a few days. and 2. ive had a BAD history with every single motorola phone i've had and i will not buy a motorola phone again.

avatar

LovTrain

I think Verizon has a big say on how a manufacture creates a phone for them, Verion has always keeped their phones locked down to prevent unauthorized changed to their product while active on Verizon's network.

I'm sure they will find a solution to the problem because they want to keep the phones "open source"

avatar

TechJunkie

UPDATE:

http://www.engadget.com/2010/07/16/motorola-responds-to-droid-x-bootloader-controversy-says-efuse/

Sorry for this MAXPC but I have to put the minds at ease.

Motorola is saying that an unapproved bootloader will render the phone useless....but you can re-install the approved bootloader (stock) and it will load making your phone work again.

Still, this is crap to me. If I want to void my warranty and install a non-approved rom, that's my business not theirs. 

 

avatar

Cy-Kill

IMHO, this is going to cost Motorola a tonne of money, because it's someone's personal property after they buy it, and whatever they want to do to their property is their business.  If Motorola is bricking phones, that's destruction of personal property, and the lawsuits will start flying. 

Cy-Kill

avatar

Purity999

So if this eFuse chip that is the same as the one in the original Droid, how have we been able to root and install custom ROMs without bricking our phone?

avatar

TechJunkie

Because it wasn't "activated". The efuse and the tech is there, it just wasn't turned on at the factory.

avatar

TechJunkie

I have an EVO so I won't worry with this.....for now. BUT...After we purchase a phone at retail (with or without plan) it becomes ours and we own it, not them. We should be able to use, mod, destroy, or decapitate our phone at will and in any way we choose.  By literally "bricking" the phone after purchase should be criminal as it destroys your property. I can see them saying that you lose your warranty if modded in any way, but that still gives you the right to choose.

You buy a house out right, with no mortgage...all paid for, and the builder says you can't paint your house a different color or we will lock you out and change the locks.

avatar

dracoress

I am buying your product.

 If I decide that I want to void your warranty so you won't support me fine.  It's my expense to get it fixed.  Fine, that is the risk I take.  It's my money.

 But your putting a trap in my own phone were as if I want to do this. 

 This is something I'd expect from Apple but not and Android phone maker.

 I dont' mod my phones but I think this is BS!

avatar

Kyokugen

My phone contract is up in September, and I was dead set on a Droid X.  This, however, would be a dealbreaker.  The whole reason I want an Android handset is how easily they can be modded, and if this is the only handset that can't be modded, then it'll be an HTC Incredible or original Droid for me.

avatar

Michael Ellis

Even putting that capability in the phone is crossing the line.

HP Pavilion Elite e9280t  AW020AV-ABA

avatar

Michael Ellis

I don't even mod my phones and this pisses me off.

HP Pavilion Elite e9280t  AW020AV-ABA

avatar

IFLATLINEI

Motorola found themselves in a  rough spot. Their mobile business was in decline as well as some of their other business's. They had a large manufacturing facility near my home in Buffalo NY that closed up shop a few years ago. This was a company in trouble. Until in part because of the Android OS and their newest smartphone the Droid. Its my opinion that the Android OS and its fans almost single handedly helped Motorola become relevant again. Atleast in its cell phone division. if this chip turns out to block custom roms and render the phone a brick that would be a serious kick in the teeth to the very people they need to stay relevant. Doesnt sound like a good move. I think the customer has spoke loud and clear when they purchased Android phones. The message is I may never mod my phone but Im buying Android in case the need arises.

avatar

reutnes

IMO I can't see any reason for Motorola to lock down the phone, but if the carrier decides they want to put in their bloat apps and lock them in there, disabling custom ROM is the way to do it.  This is more likely Verizon's fault than it is Motorola's.

Log in to MaximumPC directly or log in using Facebook

Forgot your username or password?
Click here for help.

Login with Facebook
Log in using Facebook to share comments and articles easily with your Facebook feed.