Motorola: no e-fuse in DroidX
engadget.com
engadget.com
Why not make it OS agnostic, like a PC? They can still limit support to the original OS (like many PC vendors). It seems they just making it hard to root because that's the way they've always done business - and change is hard for them.
If it's Verizon that's behind this to "protect the network" it's starting to sound like we're heading for another "Carterfone Decision":
https://secure.wikimedia.org/wikipedia/en/wiki/Modem#The_Car...
The Nokia N900 doesn't make life difficult for users. To root it you just download and run 'rootsh'. Done. The network hasn't exploded simply because it's easy to root and update ROMs.
What kind of harm? I don't see any harm you could do with this phone that you can't do with another / an antenna. And if it's P.R. harm they're afraid of, people who replace their OS / jailbreak are usually proud to claim they did so to anyone in the vicinity, so any bad experience on their part isn't spread to others from what I can see.
Remember the failure of Vista's security dialogs? And how everyone just kept hitting "yes"? Same story. The average user wants it to work, not to not work. If A and B are required for it to work, they'll add A and B without a second thought.
Just saying - much as I pity the average user for their helplessness, but their is a limit to the level they can be accommodated.
Computers do not require a user's-license in the least, and it shows in how much BS support lines have to put up with.
If you install a hacked OS, you don't have that security anymore. Unless you can trust the provider of the OS.
Conversely, a lot of people have modified their Android phones, yet this doesn't seem to happen to them.
Because of the lack of correlation between any of these things (hacked phones, phones misbehaving and network disruptions), I have a very hard time believing this nonexistent problem is really the motivation for these policies.
no boom, but still no boot
There is an efuse and they refer to it in the statement: "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". The technology is there in the device, says Motorola. It's just loaded with good intentions.
Now, what's it for? "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."
What does it mean that Motorola's "recovery mode" is eFuse based? It means exactly what was reported earlier. The phone is bricked until you go to the Motorola store to get your software reloaded and the eFuse reset. Find somewhere where Motorola says that you can get out of their friendly "recovery mode" without their assistance. If it walks like a brick, if it quacks like a brick...
What's a bigger issue to me is why so many hackers fall for easy market-speak like this. Are they English-challenged? Verbal-intelligence-challenged? Well, explains why certain politicians get so popular on the internets, I guess.
No. They understand and speak plain, unambiguous English, C, Python and Lisp. They don't speak corporate weasel propaganda. This kind of speak, throws all kinds of exceptions, causes segfaults, or returns a non-0 and sets errno in their heads.
That should throw a few red flags up.