Re:Motorola: no e-fuse in DroidX
by macemoneta on Friday July 16, 2010 @04:15PM
(#1522377)
I don't understand the thinking here. You pay for the hardware (either directly or through your service contract). The software is free and open source. What do they think they are protecting?
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.
Re:Motorola: no e-fuse in DroidX
by dolinsky on Friday July 16, 2010 @04:26PM
(#1522423)
They are protecting from unsigned, unauthorized malware to be installed on the phone which could cause a large amount of harm to the network at large. Does this open up the possibility of "abuse" of this feature on the part of Motorola and others who employ this "feature"? Sure, but it's not pure evil either.
Re:Motorola: no e-fuse in DroidX
by macemoneta on Friday July 16, 2010 @04:38PM
(#1522470)
Rooting isn't impossible on the Droid X, it's just annoyingly difficult. If someone wanted to distribute malware ROM images, they just need to wait for the root to be accomplished by someone else. There's no real protection.
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":
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.
Re:Motorola: no e-fuse in DroidX
by fragmede on Friday July 16, 2010 @04:59PM
(#1522546)
"The FCC has indicated that it is unlikely to take action on Wireless Carterfone beyond a possible rule requiring carriers to unlock handsets at the end of their contract periods."
Re:Motorola: no e-fuse in DroidX
by Groxx on Friday July 16, 2010 @05:38PM
(#1522700)
>which could cause a large amount of harm to the network at large.
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.
Re:Motorola: no e-fuse in DroidX
by chc on Friday July 16, 2010 @11:44PM
(#1523263)
That happened to me with a dumbphone about 10 years ago. Forgiving all those fees made me a huge fan of T-Mobile. It didn't seem to do their network any harm, though.
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.
Re:Motorola: no e-fuse in DroidX
by Groxx on Saturday July 17, 2010 @03:19PM
(#1524451)
This implies the average person reads those, much less understands them or cares. If anything, because of that an Android app is significantly more dangerous than jailbreaking, as a jailbreaker is more likely to know what they're doing.
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.
Re:Motorola: no e-fuse in DroidX
by Tichy on Saturday July 17, 2010 @05:24PM
(#1524668)
I think even a normal user will have to think at least a little bit. A smartphone is a powerful device. You can't just hit the street with your new car either, you need a drivers license.
Just saying - much as I pity the average user for their helplessness, but their is a limit to the level they can be accommodated.
Re:Motorola: no e-fuse in DroidX
by Groxx on Saturday July 17, 2010 @08:37PM
(#1524943)
In my experience, the average person is significantly less informed about their computers than their cars. Most people get the oil changed in their cars relatively regularly.
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.
Re:Motorola: no e-fuse in DroidX
by Tichy on Sunday July 18, 2010 @07:43AM
(#1525605)
Sure, but still, if you want to, you can check the security settings for an app in Android. They are not that cryptic ("network access", "send SMS", "make phone calls"). If a chess app wants to make phone calls, even an idiot should get suspicious.
If you install a hacked OS, you don't have that security anymore. Unless you can trust the provider of the OS.
Re:Motorola: no e-fuse in DroidX
by tman on Friday July 16, 2010 @08:32PM
(#1523023)
FUD FUD FUD. What an awful summary.
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.
Re:Motorola: no e-fuse in DroidX
by rdtsc on Friday July 16, 2010 @11:03PM
(#1523218)
> 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?
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.
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.
http://en.wikipedia.org/wiki/Carterfone
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.
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.
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.
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.