Dude, re-read my earlier post. I did not say that Motorola should pay me money. I explained that *I* paid the money to have my Droid X put back together again. I repeat my last sentence from the previous post " We have no reason to harbor a grudge towards Motorola and Verizon?" My point is that the presence of their eFuse caused the lockup, I paid to have it fixed and now harbor a grudge - ill feelings, strong dislike - for Motorola, I don't want them to pay me any money, and my original post made no implication of that. I simply wish them very bad luck in all future business dealings, and will never spend any of my money on their products in the future.
Dude, re-read my post. I didn't say that you said Motorola should pay you money. I said it's not Motorola's fault, or problem that you bricked a device which you knew had an efuse and which you knew would void your warranty if you messed with it. Whether or not you have any ill will or feelings toward motorola has nothing to do with it. it's not their fault at all. it's 100% your fault that you had to pay some guy to fix your phone.
while i understand your position, i don't necessarily agree with your analysis. and let me disagree (respectfully) with an example/analogy: when you purchase a car, you can "chip" it with after-market parts, and obtain increased performance and power from your vehicle [which is very similar to rooting your phone, installing custom roms, and overclocking]. everyone understands that "chipping" your car voids your warranty. but, what if the car manufacturer installed a system that would sense when you "chipped", and caused the computer system to seize up and render your new vehicle non-functioning - would anyone consider that appropriate/permissible???
imho, a similar rationale would apply here. just because a phone manufacturer can lock down its phones, that doesn't make it right. anyone who hacks their phones understands (or at least, should understand) the risks. if i purchase a phone, and understand the risks of hacking, i believe i should be permitted to assume those risks without also having to assume the risk of the manufacturer booby-trapping my phone. (i believe this may have been part of the reason that the Library of Congress came out with its policy statement against locked down phones.)
as for the argument that Moto is doing it to preserve profits (against people who brick their phones and then ask for Moto to replace them), that also doesn't make sense to me. as has been pointed out, the percentage of users who hack their phones is but an infinitesimal percentage of total users. and, the percentage of those people who brick their phones is equally infinitesimal [out of the 1M+ posts in this forum, there has been maybe one instance of an actual bricking]. the costs of developing a locked bootloader far and away exceed any costs of replacing phones that have been bricked from hacking. yet, the cost of a locked bootloader is something Moto makes us pay for. and why??? i still don't know the answer to that...
when i say "right" i don't mean "correct" i mean it's their "freedom" to do that if they wanted to. Whether or not they are correct in doing it is as you said debatable and I'd agree with you that maybe it's not "right" in that sense since we buy the devices and they shouldn't be able to dictate what we do with them. heck i've hacked my navigation unit in my car to play dvds while driving whereas before it would only play if parked. i know my units warranty is voided by me doing that, but i also knew there could be a risk that i could mess up my unit and i would not be able to get a warranty repair on it. i wouldn't be mad at the manufacturer for that though...
i guess it comes down to were you informed of the consequences. let's say that the car dealer told you "if you chip this car, it may destroy it because we've installed a system to prevent such a thing to protect our proprietary software"...is it right? maybe not. is it their prerogative to that? yes. i guess what i'm saying is it's not like Motorola snuck that efuse in their and when phones brick they put their fingers together like Mr. Burns from the Simpsons and say "Excellent" and laugh at the user. Even if there was no efuse, the risk of destroying your phone exists anytime you make some kind of software change You should be fully aware of the risks and the consequences of hacking a phone with an efuse or without (and if you're not you shouldn't be hacking it).
however, again, none of this would be an issue if people took responsiblity for what they do.