Slashdot Mirror


Apple May Be Breaking the Law With Policy On iPhone Unlocks

an anonymous reader writes "Apple's recent decision to void warranties for folks that unlocked their iPhones may wind them up in legal hot water. The site Phone News points out that Apple appears to have broken a key warranty law relevant to SIM unlocks. The Magnuson-Moss Warranty Act, a law decades old, would seem to prevent Apple from voiding warranties in the way it is threatening to do with the iPhone, or so the site argues. 'The Magnuson-Moss Warranty Act states that Apple cannot void a warranty for a product with third-party enhancements or modifications to their product. The only exception to this rule is if Apple can determine that the modification or enhancement is responsible [for] damaging the product in question ... The legal [questions are]: Is the SIM Unlock process that has become mainstream doing damage to iPhone? And, also, is Apple designing future software updates to do damage to iPhone when said SIM Unlock code is present?'"

385 comments

  1. Why this is probably wrong by daveschroeder · · Score: 5, Interesting

    It's not about unlocking phones.

    It's about the radio firmware being altered in an unknown way, or even damaged. (Note: this is DIFFERENT from jailbreaking, OS hacking, and installing third party apps.)

    Why should that be covered under warranty?

    [...] is Apple designing future software updates to do damage to iPhone when said SIM Unlock code is present?

    NO!

    Absolutely not.

    Apple has already explicitly stated that they are not going to intentionally or proactively do anything to unlocked phones. Even a small amount of logic would reveal that when the baseband radio firmware is in an unknown state (this is different from the OS on the phone, and doing the "hacking" to install third party applications, and so on), future updates, either to the firmware or the OS or both, may break things. Even a software update that expects the radio to accept commands or interact with the OS in a particular way could end up breaking things.

    Oh, I know a lot of you really want to believe Apple is actually going to intentionally damage phones that are unlocked. Sorry to disappoint, but that is simply not the case.

    If there is any legal issue that erupts over this, Apple will very easily be able to prove that there is no way for it to predict the state of the hardware when it does updates when it has been altered, perhaps irreparably depending on the method, in an unknown fashion by the user.

    Further, I think it's funny that some seem to carp about how Apple will be "fixing" the mechanism via which phones are currently unlocked, as if it's evil. Of course they will! It's a general buffer overflow that happens to be used in the unlock process. Should Apple not fix an exploitable buffer overflow in the OS just so people can continue to unlock phones? The arguments on this topic are laughable.

    Moreover, while end-user unlocking of handsets is legal in the US under the current DMCA exemption, the vendor is under NO OBLIGATION to support the phones in such a state with future software/firmware updates. I can hear all the "But what about the UK?" people chiming in now. Apple will do whatever is required by law in any jurisdiction. If a certain jurisdiction REQUIRES unlocked phones, Apple may skip that market entirely (for now). Even in the UK it isn't as clear as some people like to think it is, because the phone technically isn't subsidized, meaning that it may not have to be unlocked after the subsidy is repaid - because there is no subsidy. And a large part of Apple's iPhone strategy with carriers is tight integration for things like the activation process: things that simply aren't supported with anyone but the partner carrier.

    Remember: it's "legal" to do a lot of things which also might end up voiding the warranty of a particular product. Something being "legal" doesn't imply all of these things people seem to think it does. A lot of odd arguments appeared in the last story about this, saying that since the DMCA exemption allows handset unlocking, somehow, Apple must actively enable it. Wrong.

    Customers have a choice:

    - Don't ever apply a software update after unlocking (unless applying said update to a phone unlocked using your exact mechanism has been confirmed to work by others), and your phone will stay unlocked

    - Don't buy an iPhone

    Don't act like Apple is somehow bound to support all unlocked phones via any mechanism, some which may damage the phone, in any and all future software updates, especially when it can't possibly predict all iterations. You don't have to buy an iPhone.

    And if you want to argue about simlocking in general, it's a very common practice the world over, and your beef isn't with Apple. If Apple just sold all iPhones unlocked, like some people think they should, there would be nowhere near the tight integration with any and all carriers, the pleasant do-it-yourself activation process that is part of what makes the iPhone genius, not to mention the economic arguments, where

    1. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      anonymous submitter = dave schroeder

    2. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      Thanks for blowing my cover!

      Hugs and Kisses,
      Dave

    3. Re:Why this is probably wrong by betterunixthanunix · · Score: 4, Insightful
      Apple knows that the best course is to protect their exclusive contract, not to leave the phones as-is, and certainly not to shrug off people hacking their iPhones. Apple isn't doing this because they dislike their customers; they are doing it because they don't respect their customers. They also happen to be thwarting attempts to sync iPods with software other than iTunes -- I suppose this is also a completely normal, acceptable practice, to prevent people who use Amarok or Rhythmbox from syncing up their iPod?

      Maybe they didn't tell their developers to find a way to cause hacked iPhones to stop functioning. But I doubt that when one of their developers said at a meeting, "...and this update will cause unlocked iPhones to stop functioning..." they thought anything other than, "Good!"

      --
      Palm trees and 8
    4. Re:Why this is probably wrong by PeterBrett · · Score: 4, Informative

      Moreover, while end-user unlocking of handsets is legal in the US under the current DMCA exemption, the vendor is under NO OBLIGATION to support the phones in such a state with future software/firmware updates. I can hear all the "But what about the UK?" people chiming in now. Apple will do whatever is required by law in any jurisdiction. If a certain jurisdiction REQUIRES unlocked phones, Apple may skip that market entirely (for now). Even in the UK it isn't as clear as some people like to think it is, because the phone technically isn't subsidized, meaning that it may not have to be unlocked after the subsidy is repaid - because there is no subsidy. And a large part of Apple's iPhone strategy with carriers is tight integration for things like the activation process: things that simply aren't supported with anyone but the partner carrier.

      I think you'll find that locking phones in the UK is only permitted because the carrier subsidises the cost of the phone.

    5. Re:Why this is probably wrong by Henry+V+.009 · · Score: 0, Troll

      Of course, this will devolve into disinformation where people believe that even the third party application hacks also might void the warranty or "damage" the phone, or that Apple is purposely "damaging" phones that are unlocked, and then villainously not honoring the warranties just to "stick it" to them, when in reality it's nothing of the sort...so I expect it to be a big bad press brouhaha when the first people get their phones bricked.
      That would be so Apple, and you know it.
    6. Re:Why this is probably wrong by drcagn · · Score: 2, Insightful

      Apple has already explicitly stated that they are not going to intentionally or proactively do anything to unlocked phones.

      No, Apple has said that they are not going to intentionally or proactively do anything to people who write third party applications.
      On the other hand, Apple has said that they are going to do what they can to stop unlockers.

      --
      Scorta futuere amo!
    7. Re:Why this is probably wrong by svendsen · · Score: 3, Insightful

      Except your statement assumes that Apple hacked a few iPods into the exact same state as all the hacked iPhones and already ran a patch to see what would happen.

      My feeling is why waste that time and moeny? THey will build a patch that will work with a non hacked iPhone 100%. They won't spend a single dime testing it on a hacked one (why should they the ROI on that is a negative). Simply say we can;t guarantee what it will do on a system with a changed state not done by Apple.

      From what some posters are posting on here (not the parent just what I have read) is that Apple should somehow make sure the patch will work with every combination of a hacked iPhone. Hmm wonder what that would cost.

    8. Re:Why this is probably wrong by Anonymous Coward · · Score: 0, Troll

      I think you'll find that locking phones in the UK is only permitted because the carrier subsidises the cost of the phone.

      Then I guess we'll find out whether the iPhone is locked to a carrier in the UK when it comes out, won't we?

      And if it is, then what? A bunch of crying and whining?

    9. Re:Why this is probably wrong by toleraen · · Score: 1

      Ruh roh, for once I actually agree with you.

      I don't see how this is huge news, it's pretty much the same for hacked HTC (running WM) phones...of course they've been hacked quite a bit more. After applying custom firmwares to the phone, if you want to go back to an official release there are several downgrading steps that need to be done. Directly applying an official update can seriously screw it up, but that's not HTC's fault.

      Welcome to the world of custom firmware Apple fans!

    10. Re:Why this is probably wrong by p0tat03 · · Score: 3, Interesting

      Except, AFAIK, the burden of proof is upon Apple to show that the SIM unlock process being employed by the customer is bricking the phone. I have an unlocked iPhone, and as far as I can tell the only tricky part about the unlock process is the buffer overflow to get into the phone in the first place - certainly not something that will damage hardware. The firmware modifications are not real modifications, so much as it appears to be flipping a switch - literally a setting that Apple had placed in there in the first place. The phone supports unlocked mode, and no custom firmware code is being written, just settings, AFAIK. Correct me if I'm wrong here.

    11. Re:Why this is probably wrong by 644bd346996 · · Score: 2, Insightful

      See my post here. Firmware shouldn't be able to cause permanent damage to the hardware, and the user should be able to recover the device from a botched firmware upgrade (or a bad hack job), without a JTAG. Not ensuring those two things will cause problems for Apple, even if they can discourage people from trying to hack the iPhone.

      Have you ever used a PDA or graphing calculator that required a JTAG to un-brick after a failed update? It's simply unacceptable in those markets. Why should Apple get away with it in the iPhone?

    12. Re:Why this is probably wrong by Applekid · · Score: 2, Informative

      It's pretty well known that Apple gets a kickback of the charges collected by AT&T within the two year contract with an iPhone.

      --
      More Twoson than Cupertino
    13. Re:Why this is probably wrong by betterunixthanunix · · Score: 1

      Oh no, certainly not. But a developer could probably tell what effect his code will have on the hacked iPhones (developers should be sitting down and carefully designing code before writing it). The developers would probably mention it as a footnote or afterthought, but I doubt they would simply skip over it when their manager says, "OK, tell us what this update does and how it will affect the customers."

      --
      Palm trees and 8
    14. Re:Why this is probably wrong by Microlith · · Score: 1

      They also happen to be thwarting attempts to sync iPods with software other than iTunes


      They added a hash, that the firmware checked before loading. That was cracked fairly quickly and could have been much harder. Prove to me they did it deliberately and intentionally to remove other syncing utilities.
    15. Re:Why this is probably wrong by betterunixthanunix · · Score: 1
      "Why should Apple get away with it in the iPhone?"

      Because the iPhone is cool.

      --
      Palm trees and 8
    16. Re:Why this is probably wrong by betterunixthanunix · · Score: 4, Insightful
      This hash has absolutely no technical use. The iPods worked fine before the hash, and exhibit the same level of functionality with the hash. All the hash does is restrict how the iPod can be synced.

      Or can you demonstrate a legitimate, technical need for that hash to be there?

      --
      Palm trees and 8
    17. Re:Why this is probably wrong by daveschroeder · · Score: 1
      ...and the misinformation begins.

      No. Apple said:

      Apple has discovered that many of the unauthorized iPhone unlocking programs available on the Internet cause irreparable damage to the iPhone's software, which will likely result in the modified iPhone becoming permanently inoperable when a future Apple-supplied iPhone software update is installed. [...] Apple strongly discourages users from installing unauthorized unlocking programs on their iPhones. Users who make unauthorized modifications to the software on their iPhone violate their iPhone software license agreement and void their warranty. The permanent inability to use an iPhone due to installing unlocking software is not covered under the iPhone's warranty.


      and:

      ''This has nothing to do with proactively disabling a phone that is unlocked or hacked,'' Phil Schiller, Apple's senior vice president of worldwide product marketing, said in an interview. ''It's unfortunate that some of these programs have caused damage to the iPhone software, but Apple cannot be responsible for ... those consequences.''

      The current unlock mechanism uses a buffer overflow in the current version of the iPhone's OS to unlock. Will that be fixed, thereby "stopping" unlockers? Yes.

      This doesn't mean they're going to intentionally damage phones that have ALREADY BEEN unlocked.

      So I'm sorry, but you're incorrect.
    18. Re:Why this is probably wrong by PeterBrett · · Score: 1, Insightful

      I think you'll find that locking phones in the UK is only permitted because the carrier subsidises the cost of the phone.

      Then I guess we'll find out whether the iPhone is locked to a carrier in the UK when it comes out, won't we?

      It will be.

      And if it is, then what? A bunch of crying and whining?

      Probably a consumer rights lawsuit after they void a couple of people's warranties for unlocking. But not from me. I really couldn't give a shit about the iPhone or any of Apple's other predatory business practices.

    19. Re:Why this is probably wrong by Experiment+626 · · Score: 1

      Even in the UK it isn't as clear as some people like to think it is, because the phone technically isn't subsidized, meaning that it may not have to be unlocked after the subsidy is repaid - because there is no subsidy.

      Maybe Apple's brilliant line of reasoning will catch on in other industries.

      You: I want to buy this house! *hands realtor a check for the full price of the property*

      Realtor: Thanks.

      You: Can I have the deed to my new property?

      Realtor: Nope. See, we have to give you the title to the land after you pay off the mortgage.

      You: Um, but I didn't take out a mortgage?

      Realtor: Right, so I get to keep your money and never have to give you the deed! Ha ha ha you sure are a moron! *walks off, sticking the check in his pocket*

    20. Re:Why this is probably wrong by suggsjc · · Score: 1

      Considering how authoritative and absolute this post is, I'm going to have to assume (only for discussion purposes) that daveschroeder is an Apple employee who is *very* highly in "the know" about their corporate politics. Because if not, then this is just an Apple fanboi rant trying to save some face from what is a corporation knowingly reducing functionality of a device to (questionably) boost their own profits.

      That said, I do agree that since the unlock process does take advantage of a buffer overflow problem that Apple should fix it, but I'm not sure why subsequent upgrades would be an issue.

      I'll be upfront about me not being 100% sure about the following, so please correct if I am wrong. Considering that this only affects the baseband chip, which serves a single purpose...to communicate with the GSM/GPRS networks, and those methods are well understood and for the most part static. I would highly doubt that they would need to make any changes to that stack/chip. Most of the times when building phones, you just purchase the baseband chips and you can't directly interact with the firmware...there is that whole FCC licensing that they have to get after all (only the chips have to have the certification, i think). Anyway, if this next update does brick the phone I would be inclined to think that it was nothing other than 100% deliberate.

      --
      When I have a kid, I want to put him in one of those strollers for twins and then run around the mall looking frantic.
    21. Re:Why this is probably wrong by Microlith · · Score: 0, Troll

      If they wanted it to be truly restricted, they'd encrypt the database.

      But I suppose you've never had a terrible 3rd party sync util (EphPod) go and fuck your iPod's database up on what was only supposed to be a read, have you?

    22. Re:Why this is probably wrong by garyrich · · Score: 3, Insightful

      "Except your statement assumes that Apple hacked a few iPods into the exact same state as all the hacked iPhones and already ran a patch to see what would happen."

      IF you think they haven't already, I'd have to say you are barking mad.

      "My feeling is why waste that time and moeny?"

      What does it cost to have some junior level dev guy hack one and play around with it for a day and write up a report? Basically nothing.

      "THey will build a patch that will work with a non hacked iPhone 100%. They won't spend a single dime testing it on a hacked one (why should they the ROI on that is a negative). "

      OF course this is true, but you are answering a different question. Real testing and "validation" would be very expensive. Particularly since that validation would have to meet the standards of AT&T, which obviously has a vested interest in having any such thing fail validation testing.

      "Simply say we can;t guarantee what it will do on a system with a changed state not done by Apple."

      Unofficially, they will know perfectly well what it will do. If there are two roughly equal ways to implement a desired feature and and they know one of them breaks on the hacked phone -- that is the one that will be used. Apple would reverse engineer an unrelated reason for why they picked that implementation.

      "From what some posters are posting on here (not the parent just what I have read) is that Apple should somehow make sure the patch will work with every combination of a hacked iPhone. Hmm wonder what that would cost."

      They have no such obligation, totally agree. What they do have is a contract with AT&T to ensure and protect their exclusive carrier rights. If they don't do everything legally possible to make sure people can't switch carriers - they will sure Apple for everything they can.

      --
      -- your Web browser is Ronald Reagan
    23. Re:Why this is probably wrong by T-Bone-T · · Score: 1

      Firmware shouldn't be able to cause permanent damage to the hardware Keyword: shouldn't. It happens in the real world all the time, though.
    24. Re:Why this is probably wrong by walt-sjc · · Score: 3, Insightful

      Except your statement assumes that Apple hacked a few iPods into the exact same state as all the hacked iPhones and already ran a patch to see what would happen.

      That's a pretty damn safe assumption to make. Any COMPETENT product engineering team / product management team would ABSOLUTELY do so.

      You KNOW that they have at LEAST applied the unlock hack to phones to see exactly what it does and how it works. You also know that they are working on (and surely finished by now) a patch that "undoes" the unlock hack.

      It would be ridiculous to think that they would make the statement that their updates will brick a phone without knowing for sure.

      It would also be ridiculous to think that any information on this at Apple would remain secret during a court case and the resulting subpoenas / depositions.

      Come on. We, and Apple, just are not that stupid.

    25. Re:Why this is probably wrong by djh101010 · · Score: 4, Informative

      Apple knows that the best course is to protect their exclusive contract, not to leave the phones as-is, and certainly not to shrug off people hacking their iPhones. Apple isn't doing this because they dislike their customers; they are doing it because they don't respect their customers.
      No, Apple is "doing this" (I assume you mean, discouraging unlocking of iPhones) so AT&T doesn't have any reason to claim Apple is violating a contractual agreement. Could Apple make sure nobody can unlock the phones? Probably, yes. Have they done so? Nope. Just like every other time they've changed something to make some mega-corp happy, they make it so joe-user has to go out of their way, and that way Apple is covered. Want to copy a CD? Can't do it with drag & drop, sorry. Download a tool to do it? Well, it's not Apple's fault, they didn't give you the tool. Want to get around the DRM? You need to use a tool that isn't from Apple to do it. Want to unlock your iPhone? Same story. They can't just give you a way to do it, or they'd be in trouble with AT&T's lawyers. But, if they put up a token effort to keep people from doing it, and someone smart bypasses that (my bet is at 2 hours after the release being the time to workaround), well, (shrug) we tried, AT&T, I guess they're just too smart.

      They also happen to be thwarting attempts to sync iPods with software other than iTunes -- I suppose this is also a completely normal, acceptable practice, to prevent people who use Amarok or Rhythmbox from syncing up their iPod?
      I don't disagree that a recent update broke that function. I don't think we agree on why the change was made though. And, how long did it stay broken? If Apple really wanted to lock people out, I'm pretty sure they could have. The fact that they haven't tells me something.

      Maybe they didn't tell their developers to find a way to cause hacked iPhones to stop functioning. But I doubt that when one of their developers said at a meeting, "...and this update will cause unlocked iPhones to stop functioning..." they thought anything other than, "Good!" Yup, "Good"...followed by a chuckle, and a thought of "That'll keep AT&T off our ass, and the mods community will have it licked in an hour or three".
    26. Re:Why this is probably wrong by walt-sjc · · Score: 1

      Your right. Misinformation began already... But it was with the original and subsequent Apple statements.

      Apple has discovered that many of the unauthorized iPhone unlocking programs available on the Internet cause irreparable damage to the iPhone's software

      This is bullshit by definition. The phones still work, so the software is not "damaged." Yes, the firmware values may now be "different" but "different" does not automatically equal "damaged." In fact, one may go so far as to conclude that the software was "enhanced" by the unlocking code as it allows the phone to work with other carriers AS WELL as AT&T.

      This exact scenario has been well hashed out in the courts regarding third party modifications to automobiles and warranties. I believe Apple will lose this one in any court case, certainly in the court of public opinion.

    27. Re:Why this is probably wrong by djh101010 · · Score: 1

      Of course, this will devolve into disinformation where people believe that even the third party application hacks also might void the warranty or "damage" the phone, or that Apple is purposely "damaging" phones that are unlocked, and then villainously not honoring the warranties just to "stick it" to them, when in reality it's nothing of the sort...so I expect it to be a big bad press brouhaha when the first people get their phones bricked.
      That would be so Apple, and you know it.
      Really? When specifically has Apple ever done anything like that? When my iPhone's multitouch panel died in an area, I sent back my modded phone, no problem, they replaced it free without complaint. So, my direct personal experience is at odds with your apparent claim.
    28. Re:Why this is probably wrong by illegalcortex · · Score: 1

      Your post seems to lack "a legitimate, technical need for that hash to be there". I'm still waiting to hear what that is.

    29. Re:Why this is probably wrong by djh101010 · · Score: 1

      Considering how authoritative and absolute this post is, I'm going to have to assume (only for discussion purposes) that daveschroeder is an Apple employee who is *very* highly in "the know" about their corporate politics. Because if not, then this is just an Apple fanboi rant trying to save some face from what is a corporation knowingly reducing functionality of a device to (questionably) boost their own profits.

      Some day, when/if you grow up, you'll learn that not all people who correct wrong information, are doing it for financial gain. Sometimes people do it because it's the right thing to do. A few seconds of investigation would show you that Dave doesn't hide his contact information, that he's at the University of Wisconsin, and provides his email address, right with every post he makes on Slashdot. Now, I suppose it's possible that Apple pays him to defend them on slashdot, but, if that's true, I'd love to get in on that deal. The more logical and likely answer is that he knows what he's talking about, is passionate and well spoken about the topic, and points out factual and logical errors when people make wrong statements about apple either through ignorance or malice.

      Oh, and by the way? When you use the word "fanboi" it pretty much shoots any credibility your post might have. Just so you know.
    30. Re:Why this is probably wrong by mstone · · Score: 4, Insightful

      You haven't spent much time working with real-time signal processing systems, have you?

      By way of analogy, think about juggling: You don't throw the ball to where your hand is right now. You throw it to the correct spot in the pattern -- 12" off center, and 36" off the ground -- then make sure your hand is in the right place by the time the ball comes down. It requires some prediction and timing, but it's basically doable.

      Now try doing it in an earthquake. The 'correct spot in the pattern' is no longer a simple location. You have to predict where the ground will be when the ball comes down, and adjust your throw accordingly. That's a lot more complicated, and there's always a chance that something will happen between the throw and the catch that you didn't predict.

      The number of possible states and unpredictable events is more or less infinite, so there's no way you can possibly cover them all. The best you can do is try to keep everything within a range where you can spot the failures early enough to recover before they trigger a train wreck.

      Systems like that are delicate. Screw with the timing just a little, and you can bump a few 'recoverable' cases over into the 'train wreck' category. They won't show up right away, though.. you have to get just the right combination of events before the thing will hang.

      And with embedded systems, there's no option to shut down, reload the program, and start from a fresh, known state.

      And, of course, the job is just that much harder when someone else has fiddled with the system in ways you don't know about.

      Apple's announcement is just their way of saying they can't be positive they've hit every possible edge case that might cause this next update to interact badly with any unknown, unauthorized, and unsupported firmware tinkering people might have chosen to do on their own.

      Honestly, I don't know why there's so much fuss about this. Hacking the firmware is very much an "at your own risk" procedure, and anyone who pretends not to know that is being deliberately stupid.

      And why is everybody dumping this problem on Apple? Why aren't people yelling at the guys who released the unlocking software, demanding a "100% guaranteed or we'll replace your iPhone for free" reversion kit? If anyone should know how to return a hacked iPhone to its factory state, it would be the guys who hacked it in the first place.

    31. Re:Why this is probably wrong by Fulcrum+of+Evil · · Score: 1

      Apple will very easily be able to prove that there is no way for it to predict the state of the hardware when it does updates when it has been altered, perhaps irreparably depending on the method, in an unknown fashion by the user.

      But can they prove that the alterations are what caused the iPhone to fail? Probably not, especially if there's a year between the mod and a failure.

      Remember: it's "legal" to do a lot of things which also might end up voiding the warranty of a particular product.

      But it isn't clear that unlocking an iPhone voids its warranty.

      Don't act like Apple is somehow bound to support all unlocked phones via any mechanism, some which may damage the phone, in any and all future software updates, especially when it can't possibly predict all iterations. You don't have to buy an iPhone.

      If I did, I would expect Apple to stand behind it. Unlocking the phone doesn't free Apple from that obligation.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    32. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      Dude, do you even have a real job? I'm glad I'm not paying your salary.

    33. Re:Why this is probably wrong by Anonymous Coward · · Score: 0
      So, how about this:

      • Apple want to upgrade the GSM firmware in a future update, to enhance the GSM functionality.
        (Note that the GSM chip runs its own OS, is separate from OSX and acts almost independently.)

      • The existing unlocking code overwrote some of the firmware-updating code by mistake (also stored in the firmware of the GSM chip).
      • Apple use the correct API to rewrite the firmware, but of course it blows up because the updater code is screwed up.
      • Welcome to iBrick.


      The code that updates the firmware is usually separate from the firmware itself, but it's still usually in the flash-ram. The phone being useable doesn't say anything about the upgrading-software still being useable. Your claim of 'bullshit by definition' is bullshit, I'm afraid.
    34. Re:Why this is probably wrong by suggsjc · · Score: 1

      All I was saying is that Dave sure did post like he knew beyond a shadow of doubt that everything he spoke was 100% truth and did not give any type of disclaimer, that was why I questioned him. If he doesn't have anything to back up what he is saying other than it being his opinion, then I do think that he should be questioned/challenged.

      In regards to me having credibility, I don't need any. I just need Dave to show that he does.

      TFA was about whether or not Apple would be infringing on the Magnuson-Moss Warranty Act. Dave didn't even mention that, he just talked about the DMCA and having the choice of whether or not to purchase the iPhone or not. It wasn't necessarily on or off-topic. Either way, my main point was that even though the base-band chip code was altered, I don't (again disclaimer about not being certain) see how that should be something that an Apple update should conflict with. Meaning, in my opinion, that if it does end up with bricking the device, then it was 100% intentional. That is my only point that I wanted added into the equation.

      --
      When I have a kid, I want to put him in one of those strollers for twins and then run around the mall looking frantic.
    35. Re:Why this is probably wrong by pthisis · · Score: 1

      Have you ever used a PDA or graphing calculator that required a JTAG to un-brick after a failed update?

      Yes, it's the norm for many of the the PDAs I've used, as well as many mp3 players and wireless routers.

      In the early days of Linux-on-IPAQ development there were all kinds of people mailing their devices back in to Jim Gettys' handhelds.org group at Compaq for a reset if they got bricked (thankfully that was an alternative firmware actually supported by the vendor to some degree).

      It's simply unacceptable in those markets.

      No, it isn't.

      Why should Apple get away with it in the iPhone?

      Why should they be any different from everyone else?

      --
      rage, rage against the dying of the light
    36. Re:Why this is probably wrong by stewbacca · · Score: 1

      I would have posted the same thing as daveshroeder and I'm not an Apple employee, insider or fanboi. I am an intelligent person who can cut through the overt biases of the article summary.

    37. Re:Why this is probably wrong by dnoyeb · · Score: 1

      I do write embedded software on communication devices and I still disagree with you. I do not have any hardware that is not controllable by the software. Furthermore, I do not have any hardware that lacks the ability to be put into a known state. That known state is typically reset. But its there and most developers use it rather than ignore the fact that the hardware is in an unknown state.

      And this delicate timing is not so easy to screw. These critical communication portions of the software are not related the application portions. Not in my case. I assume not in any case that takes even the slightest pride in the code they write. Now if they are shipping the code out to Russia or China or India, etc. Then sure these things can happen. That is how MS Office sucks worse and worse since 97...

    38. Re:Why this is probably wrong by drcagn · · Score: 1
      No, it's come straight from The Steve's mouth--he's a bit higher up than Phil Schiller.

      Jobs Says Apple Will Fight iPhone Unlocking Hacks
      http://www.pcworld.com/article/id,137330-c,iphone/article.html

      "People will try to break in, and it's our job to stop them breaking in.".
      --
      Scorta futuere amo!
    39. Re:Why this is probably wrong by cayenne8 · · Score: 1
      "This exact scenario has been well hashed out in the courts regarding third party modifications to automobiles and warranties. "

      I dunno about that. At the very least, you will need lawyers and deep pockets to get them to uphold the warranty if at all. I know it doesn't work that well for cars.

      In my case...I'm speaking of common mods to the '04-'05 Mazdaspeed Miatas...the factory turbo'ed ones. There are neat kits that will let you start out by changing out the air intake system, and exhaust system. These mods really should not affect the factory turbo warranty.

      However, on the boards...there are stories coming in now that the factory turbo's are blowing up...on both modded and 100% stock cars. Well, on cars that have any exhaust changes, etc....Mazda is flat refusinig to replace the turbo under warranty. Now...if you want to try to battle them...get some lawyers and $$...and put your car in the garage for a couple years I guess.

      So, while the act is a nice thing to try to protect you from warranties being voided by any 3rd party mods, in reality, it is hard to do anything as a consumer when the BIG company sayd No!

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    40. Re:Why this is probably wrong by dnoyeb · · Score: 1

      Not necessarily. Sometimes legal instructs that certain things should not be tested, as policy.

    41. Re:Why this is probably wrong by daveschroeder · · Score: 1

      Yes.

      And that doesn't mean Apple will intentionally damage phones that have been unlocked out of spite.

      It means exactly what it says: that Apple will fight unlocking hacks.

      Which means they'll be doing things like patching the buffer overflow currently used to unlock, which means that current unlocking mechanisms won't work in the future.

      Schiller's statement is 100% accurate and not in conflict with, or "trumped", by what Jobs said. What Schiller said is the voice of Apple, and was probably vetted with Jobs himself, to be frank.

      So to reiterate, you are wrong. Apple WILL NOT be intentionally or purposely damaging or disabling unlocked phones. I was already aware of Jobs' statement, and that doesn't change any of this. If you choose to believe it means that Apple will be intentionally bricking unlocked phones, or that since Jobs is "higher" than Schiller (...), you choose to interpret his statement as meaning Apple will be intentionally bricking phones and Schiller's statement is invalid, be my guest.

    42. Re:Why this is probably wrong by mstone · · Score: 1

      There's a difference between "causing permanent damage to the hardware" and "wedging the firmware in a state where the device no longer accepts input and can only be reverted to factory state through direct access to the hardware."

      There were BIOS viruses that basically turned PCs into bricks back in the 1990s. The basic principle was the same: If you have to go through the firmware to modify the firmware, you'd better make damn sure you don't mess with that access path. If you do, your only remaining choice is to remove the chip that contains the firmware and replace it with one that does what it's supposed to.

      The rest of the hardware can work perfectly, even if the firmware won't let you talk to it.

    43. Re:Why this is probably wrong by mr_lizard13 · · Score: 1

      Apple has already explicitly stated that they are not going to intentionally or proactively do anything to unlocked phones.

      To the contrary:

      "It's a cat-and-mouse game. We try to stay ahead. People will try to break in, and it's our job to stop them breaking in" -Steve Jobs, Tuesday 18th September 2007

      Link: http://www.news.com/8301-10784_3-9781162-7.html

      I think you might have been mistaken with Apple's earlier statement around iPhone hacking, i.e. shoe-horning 3rd party native apps onto the iPhone. Here, Apple have said they are taking a "neutral stance" on iPhone hacking. In short, iPhone 'hacking' and 'unlocking' refer to different things.

      Link: http://www.appleinsider.com/articles/07/09/11/apple_not_opposed_to_native_iphone_app_development_report.html

      :-)
      --
      "We live in a global world" - Harvey Pitt, former Securities and Exchange Commission Chairman
    44. Re:Why this is probably wrong by mstone · · Score: 2, Interesting

      Cool. What techniques do you use to guarantee that your code will never enter a race condition, even if someone else modifies it?

    45. Re:Why this is probably wrong by realthing02 · · Score: 1

      I think you should try replying to the portion of the post that says the communications aspect of the device is sseparate from the application side. I mean, are they really updating the communication/signal processing part of the iphone? i think that should have been pretty solid by, you know, release.

    46. Re:Why this is probably wrong by Neo_piper · · Score: 1
      I'll start with mentioning that IANAL but after looking over the parent's Curriculum Vitae he doesn't seem to be either.
      I'll second with the fact that I have been a strong Apple fan for the larger portion of my life, though simple economics seem to be swaying my heart *nix ward of late.

      I'll start quoting here

      It's not about unlocking phones. No it isn't it's about enumerating warranty voiding actions in the main text and not changing them without authorization or agreement.

      Moreover, while end-user unlocking of handsets is legal in the US under the current DMCA exemption, the vendor is under NO OBLIGATION to support the phones in such a state with future software/firmware updates.
      And end there
      If you read all the included links and make a reasonable effort to understand them you'll see that the basic problem the law is put in place to solve is if little Sally Doe puts a sticker on her iPhone and then the main board frys itself then Apple must still honor(/honur) the warranty because
      1. The sticker wasn't clearly and understandably a warranty voiding item listed in the terms of use or whatever.
      2. The sticker was, likely, not the cause of the malfunction.

      None of this means that little Susy can sue apple if she can't get all the sticker gunk off her iPhone and can't read part of it or that the touch interface won't work through the sticker, BUT if Apple has a press conference about a "War on iPhone stickers" and that they may be checking the screen capacitance during updates and disabling phones with illegal screen decorations, they can't stop serving the warranty on those bricked phones.


      Or that's how I read it, take it with some salt.
    47. Re:Why this is probably wrong by KZigurs · · Score: 1

      Aaah, but there is a very certain subsidy - the rev share deal, that, btw, places apple in the same line as the provider (okay, that _could_ be argued now about, but...).

      Ether apple sells phones unlocked - and there is no subsidy OR it sells phones locked and for use on a particular network where they state (in APPLES' documentation) a required minimum contract length (aka - a minimal amount of rev share they agree to sell this product to you).

    48. Re:Why this is probably wrong by Attila+Dimedici · · Score: 1

      However, on the boards...there are stories coming in now that the factory turbo's are blowing up...on both modded and 100% stock cars. Well, on cars that have any exhaust changes, etc....Mazda is flat refusinig to replace the turbo under warranty. Now...if you want to try to battle them...get some lawyers and $$...and put your car in the garage for a couple years I guess.

      If it is happening on both stock and modded cars in the same manner, look for a major class action law suit in a couple of years. If this is not a result of things that people have done to their cars there is a chance that you could get a lawyer to take the case under the local state's lemon law. I think there is a reasonable chance that the courts would rule differently in the Apple Phone case, but it would depend on the specific judge and what arguments the lawyers for both sides make.
      --
      The truth is that all men having power ought to be mistrusted. James Madison
    49. Re:Why this is probably wrong by argmanah · · Score: 1

      Apple has already explicitly stated that they are not going to intentionally or proactively do anything to unlocked phones.... Oh, I know a lot of you really want to believe Apple is actually going to intentionally damage phones that are unlocked. Sorry to disappoint, but that is simply not the case.
      It isn't? How do you know, because they said so? If you really believe that I have some land in Florida I'd like to sell you. There is clear motive, means, and opportunity to do so, and it's not a big leap to believe that they would.

      If a firmware update breaks the iPhone, proving they do so intentionally is not as hard as you might think. In civil court, "preponderance of the evidence" (a.k.a. "more likely than not") is sufficient, unlike criminal court.
      --
      Overrated Moderation: This posts sucks... because.
    50. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      ...and add an overt bias of your own == Fanboi. Woot stfu ftw.

    51. Re:Why this is probably wrong by 644bd346996 · · Score: 1

      You didn't read the post I linked to, did you? The bootloader and OS update code should be in ROM, not Flash. That solves the problem completely, and has a negligible impact on the cost of the device.

    52. Re:Why this is probably wrong by toleraen · · Score: 1

      Why wouldn't you want the ability to update the bootloader?

    53. Re:Why this is probably wrong by dctoastman · · Score: 1

      Software can cause physical damage to hardware.

      http://en.wikipedia.org/wiki/Killer_poke

    54. Re:Why this is probably wrong by diamondsw · · Score: 0, Flamebait

      Come on. We, and Apple, just are not that stupid.

      Apparently you are.

      --
      I don't know what kind of crack I was on, but I suspect it was decaf.
    55. Re:Why this is probably wrong by jelton · · Score: 1

      It's simply unacceptable in those markets.


      What do you mean by unacceptable?

      Do you mean that systems that don't require a JTAG to fix a botched firmware update, by nature of this requirement, are superior products favored by consumers and destined to control the market?

      OR

      Do you mean that products that require a JTAG to fix a botched firmware update, by nature of this requirement, are causing harm so severe that the government should step and regulate?

      Just curious if you're advocating that the gubmint should get involved?
      --
      I am not a lawyer. This post does not constitute any form of legal advice.
    56. Re:Why this is probably wrong by davidsyes · · Score: 1

      Isn't this whole fiasco REALLY about Apple helping verizon maintain a sweetheart deal when Apple AND the consumer would be better off if verizon were NOT the only carrier to support the iPhone. I bet verizon is putting the screws to Apple to take the brunt of the criticism, and that Apple execs are winning more than the rank-and-file Apple employee, and telephone consumers are being screwed.

      I mean, just LOOK at the phones available in South Korea, Japan, the rest of Asia, and even in Europe. Hell, I just learned that Samsung had released its own phone better than the iPhone-- BEFORE the iPhone was available. I don't CARE about which local cell phone makers/distributors/carriers get hurt, but short of going to Europe or Asia to buy a killer phone that is ALSO compatible with the relatively decrepit US carrier system, I don't see why I should have any concern for the well-being of US-based carriers. Apple's conduct in tying the iPhone to ONLY verizon is endemic of how software companies are in some form or another SCREWING the US tech-savvy, but price-sensitive would-be-loyal consumer/prosumer.

      Thanks, Apple.

      --
      Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
    57. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      at&t

    58. Re:Why this is probably wrong by Anonymous Coward · · Score: 1, Interesting

      Ha ha this whole thing is so full of lose.

      Apple suppy a phone and the firmware to run it. You can use their firmware, or the hacked firmware offered by third parties (which consists of a specific version of the apple firmware plus hacks).

      Apple don't support the third party firmware, and why should they? You didn't pay for that support, and Apple never implied that that support was on offer.

      It's as simple as that. This whole recurring topic is just control-freak software socialists trying to tell Apple what services it may or may not offer its customers, and for how much - then trying to demonise Apple by making them look like the ones trying to be controlling.

      Apple didn't mislead you and they didn't hold a gun to your head. Go away.

    59. Re:Why this is probably wrong by davidsyes · · Score: 1

      WHuuuuppppssss! I meant AT&T... (NOT the right choice...either...)

      --
      Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
    60. Re:Why this is probably wrong by earlymon · · Score: 1

      Stupid has nothing to do with it - organizational bandwidth has everything to do with it.

      I love my Macs - wouldn't trade 'em. However - there was the bad run of 10.2 CDs for OS X that bricked my iMac, while the laptop and G4 was just fine. Then there were the 3 or 4 automatic updates that required reboot and then wouldn't allow logins or something equally evil - sorry to not recall the specifics on that one, and no intention to exaggerate the true facts. Then there were the early 10.1 updates that temporarily caused our SuperDrives to not work with iDVD.

      In my experience - and shared by many longtime OSX users - Apple simply doesn't have the investment in their testing department to really do boundary condition testing. Judging by the paucity of those horror stories over time, I personally think they've improved. But they're far from perfect still - example, if you don't automatically repair permissions after any major update from them, you're nuts. (iTunes updates seem to always be a culprit, btw.)

      But if you're expecting them to spend 10 seconds doing a boundary condition test that they don't absolutely need to - think again.

      If anything, expect them to maybe brick SOME of the first generation of UNMODIFIED iPhones when the second generation appears and some new update happens - not the first time for any big vendor to suffer that nonsense, but there it is. Expecting them to care about bricking modified product - laughable, my friend, laughable.

      IOW .... Never attribute to conspiracy what some lame manager's budget shortfall explains?

      --
      Pathological kinda promises Path + Logical - but instead, you get stuck with pathetic.
    61. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      Regardless if you agree with the opinions of the parent post or not, please understand that daveschroeder (516195) has a a well known history on /. of representing his opinions as "fact", you can look at his posting history. Do not be fooled. He speaks as if what he claims are undisputed facts and he just knows how things will work out. Only when asked for more information about his claims will he finally revel his proof as being "it seems", "they should be", "they could", "why would they", "it is obvious" and similar. Most people in a discussion will include these words assuming that anything can happen, daveschroeder (516195) will not use those words and then include in bold/italics or underline a general statement that it will never happen or it can never happen and make a claim as if the end is already here and everything has already been worked out and the final has come. He may also link or reference other posts that are also opinions that agree with his own opinion and even his own posts sometimes as evidence. I guess he thinks that if he feels something is true (even without any evidence), and he finds another person that also feels something is true (even without evidence), he can tie the two together and represent the opinions as a factual item.

    62. Re:Why this is probably wrong by SuperKendall · · Score: 2, Informative

      The hash is easy to explain - basically a checksum to ensure the file it references is valid and still the same file as it is expecting. Don't forget that new iPods are a lot more easygoing about being disconnected in the middle of a sync. It's also a good way to be sure that the file properly downloaded from the iTunes store over a spottier wireless connection.

      I think you are asking why the hash is encrypted, which has less reason for being so though I could easily wave hands a bit and say it's a light form of security that makes it harder for malware to infect and affect an iPod. So it's not like there's no valid technical reason even for that, it's just more dubious as far as value added. But the other poster makes a great point, they could have easily engineered a far tougher nut to crack so the truth must not be as dire as you are making it out to be.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    63. Re:Why this is probably wrong by davidsyes · · Score: 1

      I heard (from a Korean) it was released in Korea before iPod (was released there?)...

      (Note, the Techeblog site fracks with my Mozilla Firefox browser in that it DELAYS my getting off their page and back into my Slashdot tab... I suspect some fracked up ad code, cookies/java/other code interrupting my keyboard and mouse...)

      http://www.newsfactor.com/news/Samsung-Introduces-an--iPhone-Killer-/story.xhtml?story_id=0210017RZFZR

      http://www.macnn.com/articles/07/09/14/samsung.croix.for.vodafone/

      http://www.techeblog.com/index.php/tech-gadget/samsungs-iphone-killer-f700

      Now, on the techeblog site, someone remarked that the phone was not touchscreen capable.... Their comments were in February.

      The MacNN site has commentary that it is touchscreen.

      The NewsFactor site article is also in Feb 07. See "Features Galore" section.

      But, as for regular phones, check out things that kick the pants off US-market phones (tho I realize most of the cell phones here ARE from Japan or Korea):

      http://au.kddi.com/english/product/index.html

      http://mb.softbank.jp/mb/en/

      http://mb.softbank.jp/mb/en/product/3g/815t/index.html

      I used to have a Vodafone phone that had a multicolor strobe emitting from the camera flash. It was independently activated.

      http://www.sharp.co.jp/products/v402sh/

      When I lost it I wanted to DIE.

      --
      Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
    64. Re:Why this is probably wrong by Marful · · Score: 1
      According to the Wikipedia Entry on the Magnuson-Moss Warranty Act(http://en.wikipedia.org/wiki/Magnuson-Moss_Warranty_Act)

      Requirements of the Magnuson-Moss Act

      The Act provides that any warrantor warranting a consumer product to a consumer by means of a written warranty must disclose, fully and conspicuously, in simple and readily understood language, the terms and conditions of the warranty to the extent required by rules of the Federal Trade Commission. The FTC has enacted regulations governing the disclosure of written consumer product warranty terms and conditions on consumer products actually costing the consumer more than $15. The Rules can be found at 16 C.F.R. Part 700.

      Under the terms of the Act, ambiguous statements in a warranty are construed against the drafter of the warranty.

      Likewise, service contracts must fully, clearly, and conspicuously disclose their terms and conditions in simple and readily understood language.

      Full Warranty Requirements Under a full warranty, in the case of a defect, malfunction, or failure to conform with the written warranty, the warrantor: * must, as a minimum, remedy the consumer product within a reasonable time and without charge;
      * may not impose any limitation on the duration of any implied warranty on the product;
      * may not exclude or limit consequential damages for a breach of any written or implied warranty on the product, unless the exclusion or limitation conspicuously appears on the face of the warranty; and
      * if the product, or a component part, contains a defect or malfunction, must permit the consumer to elect either a refund or replacement without charge, after a reasonable number of repair attempts.

      In addition, the warrantor may not impose any duty, other than notification, upon any consumer, as a condition of securing the repair of any consumer product that malfunctions, is defective, or does not conform to the written warranty. However, the warrantor may require consumers to return a defective item to its place of purchase for repair.


      Under 15 U.S.C. 2302 Secton C (of The Magnuson-Moss Warranty Act) says:

      (c) Prohibition on conditions for written or implied warranty; waiver by Commission
      No warrantor of a consumer product may condition his written or implied warranty of such product on the consumer's using, in connection with such product, any article or service (other than article or service provided without charge under the terms of the warranty) which is identified by brand, trade, or corporate name; except that the prohibition of this subsection may be waived by the Commission if--

      (1) the warrantor satisfies the Commission that the warranted product will function properly only if the article or service so identified is used in connection with the warranted product, and
      (2) the Commission finds that such a waiver is in the public interest.

      The Commission shall identify in the Federal Register, and permit public comment on, all applications for waiver of the prohibition of this subsection, and shall publish in the Federal Register its disposition of any such application, including the reasons therefor.
    65. Re:Why this is probably wrong by spun · · Score: 1

      Go read Dave's homepage. He doesn't work for Apple, he works for someone much, much scarier. And realize that, if he admits that much on his home page, the reality is probably far worse. Knowing who he really works for and what he really is puts all his posts in the proper perspective.

      --
      - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
    66. Re:Why this is probably wrong by Thumper_SVX · · Score: 1

      I tend to agree with you. I've already pointed out around here that Apple have amply demonstrated their ability to create a very difficult to crack code (witness: iTunes video). The fact that it was so lightly encrypted leads me to the conclusion that it was probably just as you say; a hash to ensure database integrity.

      I mean come on... no technical reason for this? Well, how about the number of times I've hosed and restored my iPod because I trashed the database through some stupid act (disconnecting without ejecting)? A database hash wouldn't fix these problems necessarily, but might make it a little less likely.

    67. Re:Why this is probably wrong by Stewie241 · · Score: 1

      If it can be proven that Apple deliberately went out of their way to brick modded phones, then they should be responsible for that.

      If it cannot, then they have no liability to support warranty claims that result from these modifications.

      But, they should still honour warranties in some cases on modded phones. i.e. if I mod my phone (I should say that I don't have an iPhone, and will not buy one, but if I did...) and the touchpad hardware breaks because a solder joint went cold, they had better honour the warranty, because this has nothing to do with the modifications.

    68. Re:Why this is probably wrong by RubberDogBone · · Score: 1

      Come on, that would be like Apple disclaiming responsibility if they pushed and OS X updater which expected to find Macs with wifi turned on, which then bricked all the Macs which had wifi turned off.

      The radio would be in a state Apple didn't expect. So it's not their fault if they brick it?

      Excuse me, my Mac is MY property. My phone is MY property. You can't come in to my home and break these devices without being held accountable and neither should Apple be allowed to come in remotely and effectively destroy my Mac or phone without being held accountable.

      Sure, my Mac was made by Apple and runs their OS but that doesn't give them any right to do whatever the hell they want to it. And if they do something malicious, then welcome to lawsuit time.

      --
      Sig for hire.
    69. Re:Why this is probably wrong by vertinox · · Score: 1

      Don't act like Apple is somehow bound to support all unlocked phones via any mechanism, some which may damage the phone, in any and all future software updates, especially when it can't possibly predict all iterations. You don't have to buy an iPhone.

      That is the thing. I don't and probaly won't unless they were to change such happenings.

      If people didn't complain about policies they think everything was fine and keep doing it. If I kept saying "You know. The iPhone is cool and all, but I just can't see myself buying a product from a company who so incessantly fights its customers freedom." then perhaps others will chime in and eventually if enough people complain Apple might change its ways (although unlikely).

      Apple doesn't have to do anything it doesn't want to, but if they do want me to consider buying their iPhone they need to change their ways.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    70. Re:Why this is probably wrong by Bri3D · · Score: 1

      Apple has said that the new update will PROBABLY brick phones. Not that it *might*.

      This isn't them saying they can't cover some corner case, this is them trying to scare people who have unlocked their iPhones.

      And you don't have the update, so you CANNOT say that Apple will not brick phones.

      While I too believe "OMG THEY R BRICKIN US" comments are overboard, they are what Apple intended and it is a course that they could take.

    71. Re:Why this is probably wrong by davester666 · · Score: 1

      It's pretty well known that Apple gets a kickback of the charges collected by AT&T within the two year contract with an iPhone.

      But that is quite different from being a subsidized phone.

      You can buy an iPhone without signing up for an AT&T contract. After you have completed the purchase, you can sign up for either a 2 year contract or a pre-paid contract.

      For a subsidized phone, you sign the contract when you buy/are given the cell phone. You don't get the phone without signing the contract.

      While the net result might be the same [as in, Apple and AT&T wind up with roughly the same amount of money, it's unlikely to be able to treated the same as "normal" cell-phone subsidies from an accounting perspective or from a legal perspective...

      And let's not forget the explicit DMCA exception for unlocking cell-phones.

      --
      Sleep your way to a whiter smile...date a dentist!
    72. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      So have thousands of other products' manufacturers. That's nothing special, and can not be used to argue in favor of Apple. Stop sucking now, please.

    73. Re:Why this is probably wrong by lysse · · Score: 1

      Even a small amount of logic would reveal that when the baseband radio firmware is in an unknown state... future updates, either to the firmware or the OS or both, may break things.

      And the sensible thing to do with things that are in indeterminate states is completely reset them to a known state. Not guess the state and go patch-happy. Following this logic, the only negative effect that an unlocked iPhone would suffer on upgrade is that it relocks itself (because the radio firmware is reloaded as part of the upgrade process); anything worse than this (especially a bricking) seems quite hard to justify on technical grounds.
    74. Re:Why this is probably wrong by p0tat03 · · Score: 1

      Except in this case it appears all they did was flip a setting within the the firmware's flash... I can understand the argument if we're talking about actual custom code running on the modem - but this doesn't appear to be the case. If I hack an executable with a hex editor and enable a bool switch that you disabled... it's still running YOUR code...

    75. Re:Why this is probably wrong by mrsteveman1 · · Score: 1

      It would be one thing if Apple agreed not to screw with unlocked phones, but they won't do that and you know it. They spent quite a bit of time working on this system, they are going to protect it.

      Also remember this is a DRM system being circumvented in place, these people are USING the phone as-is with another carrier, not installing Linux on it.

    76. Re:Why this is probably wrong by dctoastman · · Score: 1

      What if that switch is flipped to prevent a killer poke? Bounds checking and all that.

      Not to mention, I was just trying to show that software can physically damage hardware despite what some people here believe (probably not you).

    77. Re:Why this is probably wrong by jkoke · · Score: 1

      I just want to point out that Apple doesn't "come in" anywhere. They offer an update, which you have to deliberately accept by clicking a button which causes your computer to connect to their network. They are not updating your equipment without your knowledge or permission.

    78. Re:Why this is probably wrong by westlake · · Score: 1
      Except, AFAIK, the burden of proof is upon Apple to show that the SIM unlock process being employed by the customer is bricking the phone.

      remember - that as a practical matter - you won't be going into court unless your phone has been bricked. that puts Apple in a very strong position to say that you botched it.

    79. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      Yes, but we are still trying to determine who this 'anonymous coward' really is, as he seems capable of submitting millions of posts on different discussions on various topics within seconds of each other, in RealTime(TM), despite all our attempts to Slow down, Cowboy!. We suspect he is not Of This Earth.

    80. Re:Why this is probably wrong by ChrisA90278 · · Score: 1

      Typically you use a hash in firmware so you can do a kind of self diagnostic check. It is a very, very common technique. The first thing many devices do is compute a checksum of themselves and stop with an error message if the checksum fails. Doing this means that yur suport people will not see so may random unrepeatable errors.

    81. Re:Why this is probably wrong by overcaffein8d · · Score: 1

      Awesome post. Makes a lot of sense. One question, though. How the hell did you type that all up between 10:41 and 10:42?!?

      --
      Those of us who think they know everything annoy those of us who do.
    82. Re:Why this is probably wrong by josh_db · · Score: 1

      What I get from this comment (I don't know if it's true) is that Apple has included a switch in their phone, and all modders are doing is uncovering the switch and flipping it.

      Rockstar included some stuff in San Andreas, and modders uncovered it and played with it.

      So... If you find these situations to be equivalent (relevant, even), what does that mean for Apple and the iPhone unlocking business?

      If Rockstar included a hidden sex minigame in their game and got their game rated as if it was unhidden, what would Apple have to do/face if the switch was treated as unhidden, i.e. if you could easily unlock your phone?

    83. Re:Why this is probably wrong by juniorbird · · Score: 1

      First of all, it's not in their interest to protect their exclusive contract. In Europe, people pick the handset and then the carrier; in the US, it's the reverse. Apple wants to make the US market more like the European one. An unlocked iPhone is key to them accomplishing that. Because of the state of the US market, starting out with an unlocked phone and selling it without a plan isn't currently possible, so Apple had to make a deal with some devil; they chose AT&T.

      The simplest explanation is that, even if Apple understands all of the unlocking tools on the market now, it's impossible for them to know the full universe of possible unlocking options that a consumer may choose. Heck, we know for sure that one guy took a soldering iron to his iPhone. There's a pretty good chance that modification interacts poorly with a firmware update, and sooner rather than later.

      Apple's firmware update may not expect a specific state on the phone when it's first run. But, it's a safe bet that, at some point in the update, it expects to be able to put the phone in a certain state. Heck, changing the phone's state is the whole point of the firmware. If that state is no longer achievable, then it's possible a firmware update could fail catastrophically. That's just reasonable.

    84. Re:Why this is probably wrong by _LORAX_ · · Score: 1

      Um... the fact that the new line of iPods ( granted only the iPhone and touch ) can have media downloaded to it outside of a USB sync.

      The hash is a simple and effective was to not only ensure integrity and to check to see if there are new songs on the iPod. If they wanted to lock out 3rd party use of the iPod they would have just gone with an encrypted volume.

    85. Re:Why this is probably wrong by daveschroeder · · Score: 1

      Yes, spun, it's a very scary place indeed! ;-)

      It's like I'm working for the special branch of the government that spreads propaganda about Apple!

      Or could it be that I just posted my personal thoughts about this story? Nah, that'd be too obvious! It must be something sinister!

    86. Re:Why this is probably wrong by FelixGordon · · Score: 1

      He's part of that internet hate machine/hackers on steroids crew. http://www.youtube.com/watch?v=UxWgRY1I_SI

    87. Re:Why this is probably wrong by HermMunster · · Score: 1

      The firmware modification is the unlock. The unlock is protected by law. You are entitled to unlock the iphone due to a Library of Congress exemption to the DMCA. Apple can not claim that they don't like this or that type of unlock. If they were smart they would have simply allowed us to unlock the phone.

      Listen, you can't split hairs here. To break the phone due to an unlock when you know you will be breaking it and didn't make an attempt to accommodate the unlock (due to the unlock being legal as granted by the Library of Congress) then you are negligent to say the least and you are probably in violation of the DMCA if you do release the update and it breaks the iphone.

      Apple should have simply created an easy switch to unlock the phone since it is ALLOWED by law. That way the consumer would not have to modify the firmware.

      Many of you may not understand this yet but the phone is owned (as in controlled) by AT&T (not Apple) for the life of the iphone. Why is this? Because you can't do a single thing with the phone except make an emergency phone call until you unlock the phone through AT&T (or you hack it). Since Apple did not provide you a method of unlocking the phone you are committed to AT&T for the life of the phone (unless you hack it). So, your phone is worthless without service from AT&T unless you hack it, even after the 2 year contract is up.

      I don't know if anyone has tested it yet, but what happens when your contract invalidates due to 2 years or you cancel the contract? Is your phone totally locked out again?

      No matter how you look at it Apple should not, and better not (to be wise), brick anyone's phones. They know the techniques. They know the exact procedure, they know exactly how the hacks works. Obviously. By implementing a fix without accommodating the legal unlock they would be in violation of the DMCA and subject to cease and desist letters as well as lawsuits, if not class action lawsuits.

      --
      You can lead a man with reason but you can't make him think.
    88. Re:Why this is probably wrong by spun · · Score: 1

      You always seem to support the status quo, big money, and the rights of the powerful over the rights of the little guy. Knowing where you work, it frightens me. Maybe you aren't being paid by the government to propagandize for Apple, but I don't like to think of people in positions of power, with little oversight, fighting for the rich and powerful. Maybe you've posted something sometime that sticks up for the little guy, but I've never seen it.

      Nothing I've got to say is going to change anyone's mind anyway. Either they see you for what you are, or they never will because they're just like you. That's just my anti-authoritarian take on things, who knows, maybe in person you're a real nice guy.

      --
      - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
    89. Re:Why this is probably wrong by Stu+Charlton · · Score: 1

      Sort of.

      Apple used a baseband chip that is 3rd party and well understood. It has a Hayes (AT) command set, just like a consumer modem. One of those commands is "sim unlock", but it requires an 8 digit passcode.
      The unlock exploits a buffer overrun to effectively make this password "00000000".

      The bricking, as far as I can tell, is due to how certain information that tied the firmware to AT&T is overwritten. It will require some creativity to get it back.

      --
      -Stu
    90. Re:Why this is probably wrong by gripen40k · · Score: 1

      I think you might be a bit too pessimistic my friend. I think the parent is right in saying that the comms part is a completely different sub-system altogether, and screwing with that to remove any lock-in code won't necessarily wreck the entire system. And what's to say that the people who made the crack are not competent coders, and have made a relatively minor adjustment that isn't unstable? I also think that Apple has an obligation to fix the buffer overflow bug that caused the unlocking to begin with because, well, it's a bug. That doesn't mean that they won't test it on an unlocked iPhone out of pure curiosity, and it also doesn't mean that they will try to brick all unlocked iPhones. I say just wait it out, see what happens, and try to keep quite till then ;).

      --
      Har?
    91. Re:Why this is probably wrong by TheVelvetFlamebait · · Score: 1

      "Except your statement assumes that Apple hacked a few iPods into the exact same state as all the hacked iPhones and already ran a patch to see what would happen."

      IF you think they haven't already, I'd have to say you are barking mad.
      Why? Apple certainly doesn't need to spend the money on making compatible things that aren't iPhones in both specification and compatibility with software. In fact, it's in their best (legitimate) interest not to support these "iPhones", since opens the floodgates to supporting any number of stupid hacks. They tested the iPhone as it was, how they made it, and that should be it. To pander to all the hacked and broken "iPhones" would simply paralyse firmware updates, which is bad for those who actually bought an iPhone and kept it an iPhone.

      What does it cost to have some junior level dev guy hack one and play around with it for a day and write up a report? Basically nothing.
      That's great for finding the obvious incompatibilities. What about ones that only manifest rarely, after long series of events? And if Apple were to start supporting the hacked iPhone, what about the iPhones where something has gone wrong in the hacking process? Why, that would lead to a messy and very, very expensive situation, where apple has to ascertain for themselves that the hack has been done correctly, and that any problems with it arise from the phone itself, not a potentially bad hack.

      Unofficially, they will know perfectly well what it will do. If there are two roughly equal ways to implement a desired feature and and they know one of them breaks on the hacked phone -- that is the one that will be used. Apple would reverse engineer an unrelated reason for why they picked that implementation.
      How do you know? Seriously? How do you know?

      Bricking hacked iPhones isn't good for them. In exchange for a small rise in AT&T's exclusivity contract, they'd lose a significant number of Apple customers. On the other hand, compromising the firmware update for hackers, as I explained earlier, would also be a bad idea. But who knows, perhaps the assumption that the GP pointed out is incorrect (as it probably is), and they simply didn't know.

      What they do have is a contract with AT&T to ensure and protect their exclusive carrier rights. If they don't do everything legally possible to make sure people can't switch carriers - they will sure Apple for everything they can.
      I'm absolutely positive that AT&T's lawsuit would fail if they tried to sue Apple for not bricking hacked iPhones. No judge would prosecute that. Of course, that is assuming AT&T would themselves recognise that not bricking the hacked iPhone constitutes breach of contract. It's only obvious now that the update is actually going to brick the iPhone.
      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    92. Re:Why this is probably wrong by arminw · · Score: 1

      ....if I mod my phone......

      Then you simply um-mod it before you send it in to Apple to be repaired. Apple has the right to demand that the phone be restored to the state it was in when they sold it to you, except for normal wear. Anyone who uses some hack to mod the phone, should make sure that they also have a hack to unmod it to whatever it was before the hack was applied. The same goes for applying Apple patches. You restore the phone, patch and then re-apply the mod. If the mod doesn't work on the patched phone, the person who supplied the hack should patch the hack so it works again. Any hack that's not reversible is worse than useless, it's dangerous.

      --
      All theory is gray
    93. Re:Why this is probably wrong by TheVelvetFlamebait · · Score: 1

      It's not about the hack so much as it's about the fact that it is hacked, and no longer the standard that Apple supports. The burden lies with the hackers to make their iPhone variants compatible with standard iPhone software. The burden that Apple has to bear is to make the firmware compatible with the standard iPhone. If anything can't run it, then it isn't a compatible iPhone.

      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    94. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      Well that was about the most ridiculous thing I have ever read on slashdot. You are obviously an apple fanboy. Sometimes apple does cross the line just like Microsoft, IBM and several other companies. I personally wont buy an apple product because I don't like buying an inferior product that has everything I want to do locked out of it. Sure the iphone is cool and new but really take a look the nokia lines of phones available and you can find all the iphone features and more without all the apple bullshit.

    95. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      You haven't spent much time working with real-time signal processing systems, have you?

      I could ask the same about you after reading your post. You have to be careful what you write because some of us actually write the shit for a living and can nail you as a fraud.

      But, I'll be polite this once.......

    96. Re:Why this is probably wrong by AltF · · Score: 1

      interesting observation. its simply impossible!!

    97. Re:Why this is probably wrong by gig · · Score: 1

      > Apple isn't doing this because they dislike their customers; they are doing it because they don't respect their customers.

      Apple is not even nearly big enough to fuck with anyone in the way you're implying. Get a grip. Apple respects their customers by making complete and finished products with a stable list of features that will work for the life of the product. Unlike every other phone, music player, and PC manufacturer. Unlike every single other one. That is why you hear Apple Monopoly, it is because they are working a full generation ahead of everyone else. Stop complaining about what you think they should do. Man up. Make your own music player, according to iSuppli you can do it for like $50 in parts. Should take you no longer than a weekend since you're a Slashdot reader.

    98. Re:Why this is probably wrong by gig · · Score: 1

      > This is bullshit by definition. The phones still work, so the software is not "damaged."

      First of all, if the phone is unable to be updated to the next firmware reliably, then it does not "still work". Second, a cracked version of Photoshop that can do 100% of the image-editing functions but doesn't serialize is still damaged and Adobe won't upgrade it and nobody would expect them to.

      Install one app on your Palm or Windows Mobile and kiss what little stability you had good-bye. Hack an iPhone and expect full warranty support and trouble-free firmware upgrades for life. Talk about a double standard.

    99. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      that wall of text just broke my iphone. thanks.

    100. Re:Why this is probably wrong by gig · · Score: 1

      > You: I want to buy this house! *hands realtor a check for the full price of the property*
      > Realtor: Thanks.
      > You: Can I have the deed to my new property?
      > Realtor: Nope.

      No, we're not talking about the deed. We're talking about the maintenance contract. It's quite common to buy a property such as an apartment and have to not only pay fees to keep the plumbing going but also have to abide by certain rules like you can't flush certain items. But I own this apartment you might say, I'll flush a hammer any time I please and I expect the maintenance people to fix it. Apple is saying if you flush a hammer you are on your own.

    101. Re:Why this is probably wrong by wolverine1999 · · Score: 1

      There are countries where phones are democratically sold without any simlock. and that's how it should be in real life I think...
      Give the consumer a choice. I wonder what the EU says about this... sure this doesn't respect consumer rights at all.
      Best thing is not to buy an iphone at all for the time being.

    102. Re:Why this is probably wrong by Shadowmist · · Score: 1

      Unlike Microsoft which has revealed that it has sent stealth software updates even to users who had opted out of auto update. If MS can get away with this. There isn't a cause to action Apple over an update which requires USER action and approval to install.

    103. Re:Why this is probably wrong by mpe · · Score: 1

      Even in the UK it isn't as clear as some people like to think it is, because the phone technically isn't subsidized, meaning that it may not have to be unlocked after the subsidy is repaid - because there is no subsidy.

      It's more likely to be the other way around. Without a subsidy there is no good reason for any SIM locking not to be removable immediatly.

    104. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      You think Apple is the ONLY company that makes phones, music players, or computers that are stable and "complete" products and you're telling someone else to get a grip? Thank god Apple finally got into designing cell phones, huh? Otherwise this whole cellular phone idea might not have taken off, and we'd be stuck with corded phones forever.

    105. Re:Why this is probably wrong by sjames · · Score: 1

      Hacking firmware can definatly brick any embedded system. However, it's usually trivial to provide a means of un-bricking. Most processors intended for embedded use provide a debugging interface that can be connected to a parallel port with about $10 worth of parts to enable reflashing the firmware on a completely bricked device. Often enough the factory uses that interface in production to load the firmware in the first place. There'sno good reason why any embedded device should be hard to return to factory condition no matter how much firmware hacking has been done.

      Of course in the case of the iPhone, Apple welds the case shut to prevent even a simple battery change by the end user. I'll bet a lot of iPhone users are about to realize they just shoveled WAY too much money at a company that holds them in contempt. That's where Apple may find itself between a rock and a hard place. They asked a lot of people to pay top dollar for a product and swore that welding the case shut was the right thing to do. If that welded case bites enough people they will have a serious marketing problem, especially since their other major products have the same "feature". At the same time, all those iPhones tht might be bricked only got into that state because a known bug in their firmware was exploited (as most such bugs will be sooner or later).

      I suppose people are dumping this on Apple because the product violates their expectations for a $500 product. After paying that much, people expect NOT to be told where they can use it and with what services. They KNOW the product would be a LOT cooler than it is now if it could accept 3rd party apps. Because it was Apple, they thought it WAS ultra cool. Now thgey're discovering it has significant downsides. In a way they're complementing Apple since they honestly believed that beyond cost Apple hardware didn't have a big downside. The difficulty for Apple is they can't seem to live up to their hype. To be fair to Apple, they never said the end user could do any of those things. Now they have to decide if they can step up and BE as ultra cool as their customers actually think they are or if it's time to "limit expectations" and take a big marketing hit. If their contract with ATT doesn't allow them to step up, they're about to face the natural consequences of making a deal with a patently UNcool company.

    106. Re:Why this is probably wrong by drcagn · · Score: 1

      My point had nothing to do with whether or not Apple will brick unlocked iPhones, but whether or not Apple will STOP unlocked iPhones. Phil Schiller's comment seems to suggest that they aren't going to bother stopping hacked iPhones, but if an update breaks it, it breaks it. However, Steve's comment contradicts it, saying that they will go out to stop hacked iPhones.

      --
      Scorta futuere amo!
    107. Re:Why this is probably wrong by daveschroeder · · Score: 1

      For the sake of clarity, Jobs is saying they're going to try to stop *unlocked*, not "hacked", iPhones. "Hacked" in this context is generally construed as the process via which people install third party applications or ringtones, and is different from unlocking. Apple is not expected to stop "hacking", and has already stated as much.

      When Jobs said he wants to fight unlockers, this also doesn't have to mean end customers who unlock their phones - it means stopping tools, processes, and vulnerabilities in the Phone that enable unlocking. It doesn't mean Apple is going to go after end users who have unlocked their phones.

      Even given Jobs' statement, it does NOT mean Apple is going to try to disable already-unlocked iPhones. In fact, Apple would probably like to avoid this, because breaking peoples' otherwise-working phones would cause a negative PR firestorm. What they DO want to stop is any process or procedure that allows any new phones to be unlocked from that point forward, which they will be doing as such methods are discovered. Apple will not intentionally be disabling iPhones that are unlocked, but is warning that it MAY happen for reasons beyond their control.

      Again, if you choose to believe that this situation combined with Jobs' statement means Apple is going to be intentionally disabling already-unlocked phones, that's your prerogative, of course. The reality is that Apple is simply going to do whatever it can to stop the cottage unlocking industry, which includes patching vulnerabilities in the phone that currently are used for unlocking...not intentionally damaging or disabling already-unlocked phones.

    108. Re:Why this is probably wrong by Anonymous Coward · · Score: 0

      Because of the state of the US market, starting out with an unlocked phone and selling it without a plan isn't currently possible

      Even Wal-Mart.com sells unlocked phones, I don't care to post a link but their site has many of them under the section of "Unlocked Phones", obviously seems possible to me and since Wal-Mart is doing it, I'd assume there is a market for it and it is a viable option here in the US. Care to take another guess of why Apple had to make a deal with AT&T?

    109. Re:Why this is probably wrong by StikyPad · · Score: 1

      IF they are selling the iPhone at a profit, then the ROI is only negative when you assume that lost sales will be negligible. If the number of ostracized potential customers is significant, then not testing for compatibility is actually detrimental. Losing the profit of the phone + the profit of AT&T kickbacks is worse than simply losing the kickbacks alone.

    110. Re:Why this is probably wrong by garyrich · · Score: 2, Informative

      Unofficially, they will know perfectly well what it will do. If there are two roughly equal ways to implement a desired feature and and they know one of them breaks on the hacked phone -- that is the one that will be used. Apple would reverse engineer an unrelated reason for why they picked that implementation.
      How do you know? Seriously? How do you know?,.

      Simply because I've seen it done many many times. It's standard business practice. Heck, I've seen just Microsoft do it a dozen times. I can think of a dozen times between DOS 3.2 and Windows 3.1/DOS 5. I've seen pharmaceutical companies intentionally sabotage generic competition with this tactic.



      What they do have is a contract with AT&T to ensure and protect their exclusive carrier rights. If they don't do everything legally possible to make sure people can't switch carriers - they will sure Apple for everything they can.


      I'm absolutely positive that AT&T's lawsuit would fail if they tried to sue Apple for not bricking hacked iPhones. No judge would prosecute that. Of course, that is assuming AT&T would themselves recognise that not bricking the hacked iPhone constitutes breach of contract. It's only obvious now that the update is actually going to brick the iPhone.

      Of course the suit you mention would fail. They wouldn't sue for that. They would sue claiming that Apple did not exercise due diligence in protecting their exclusivity. Doesn't even really matter if they win, the goal is to tie Apple up in court and squeeze concessions out of them to settle.
      --
      -- your Web browser is Ronald Reagan
    111. Re:Why this is probably wrong by El+Gruga · · Score: 1
      Unlocking is a normal event in the life of a phone and your long-winded post doesn't change the fact that after 90 days it is your RIGHT to have your phone unlocked. The iPhone may be many things, but it also a PHONE and they can be unlocked legally. The radio firmware isnt 'broken' because its unlocked - why do you say that? Its obviously BS because I have an unlocked iPhone and like all the other thousands of iPhones,it works really well. Apple is heading for a storm of legal proportions that will be unprecedented - can you say Class-Action? This will get nasty because the Consumer's right to play with his purchase in any way she/he chooses is being compromised - thats illegal.

      Here is the scenario:

      You can cancel your iPhone contract, legally, with AT&T.


      So you do.

      Then you say 'Hmmm, I think I will get a contract with T-Mobile and , of course, I want to use my iPhone that I LEGALLY OWN'.

      So you walk into T-Mobile, after paying the contract cancellation fee with AT&T, and you sign up.

      Then you say - 'Please put my new SIM into my iPhone please.'

      And then what? The iPhone dont work - so you go BACK to AT&T and say 'Please unlock my iPhone'.

      AT&T may charge you $500, but they MUST unlock that sucker.

      THATS where the legal challenge will arise, if it isn't already written up on some class-action lawyers desk......

    112. Re:Why this is probably wrong by gl4ss · · Score: 1

      well, physically it works 100% even if it's "bricked" to state where it does not accept any sim. there's no hardware error so... there is nothing to replace a device that works perfectly - it's just the settings that are wrong that you set...

      afaik a the modem firmware is reflashed during the unlocking process. a very real modification. of course, a contract breach too and all that shit. they did a half ass job at locking the iphone down but it was specced to be locked down.

      apples mistake in all this is acting "different". if the at&t contract would be done when you pick up the phone like with any other phone then if it's locked or not wouldn't matter as much(you'd still be in the contract with at&t).

      and apple has pretty big incentives to lock it down and keep it locked. who operator would do a deal with them if they don't manage in something as simple as keeping their phones simlocked even for few months? why wouldn't they? they even tried to lock ipod classic users to using itunes.

      --
      world was created 5 seconds before this post as it is.
    113. Re:Why this is probably wrong by paanta · · Score: 1

      After paying that much, people expect NOT to be told where they can use it and with what services.

      So true. And that's why nobody buys iPods.

  2. Duh. by Anonymous Coward · · Score: 0

    If you don't like the product then don't buy it.

  3. That Linux on Laptop No Warranty Story... by mjpaci · · Score: 3, Insightful

    ...from a few days ago is a better lithmus test for this act, don't you think?

    1. Re:That Linux on Laptop No Warranty Story... by milamber3 · · Score: 1

      No, because the store already admitted that was a mistake and are honoring the warranty.

    2. Re:That Linux on Laptop No Warranty Story... by Bloke+down+the+pub · · Score: 2, Funny

      Apart from the fact that it's on a different side of the Atlantic, it's a damn good precedent.

      (Disclaimer: IANASNAB,WATTKOLWHIE&W.IHNIAS,BIPD)

      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
    3. Re:That Linux on Laptop No Warranty Story... by mjpaci · · Score: 1

      What, you expect me to READ the article? I just read the comments, they're usually much more entertaining.

    4. Re:That Linux on Laptop No Warranty Story... by Speare · · Score: 1

      That was probably a typo, but it's spelled "litmus test."

      --
      [ .sig file not found ]
    5. Re:That Linux on Laptop No Warranty Story... by Anonymous Coward · · Score: 0

      The company admitted it, but the manager at the store was still being a prick about it last time I heard.

    6. Re:That Linux on Laptop No Warranty Story... by Anonymous Coward · · Score: 0

      He hath a lithp you inthenthitive bathtard!

  4. John McCain: Former Presidential Candidate by Anonymous Coward · · Score: 0


    U.S.A Communist Party FP !

  5. Nice law - may applie to linux installs too? by Anonymous Coward · · Score: 0

    It seems that this would also apply to people who have had their warranties voided due to linux installation. like here . Let's hope so.

  6. Its not Apples QA Departments responsibly by Anonymous Coward · · Score: 0

    If a firmware update from Apple breaks an iPhone, how it that Apples fault?

    Its not the QA departments responsibility at Apple to test their updates on unsupported platforms. What is the QA department suppose to do scourer the web for iPhone hacks and test their Firmware updates against them.

    1. Re:Its not Apples QA Departments responsibly by gr3kgr33n · · Score: 1

      No, they should not have to scour the web for these modifications however they also should not push out an update that will knowingly cause Unnecessary Damage

      --
      My backup chemistry thesis stored on Data Storing Bacteria mutated; granting me a degree in forensic anthropology. v4sw7
    2. Re:Its not Apples QA Departments responsibly by Anonymous Coward · · Score: 0

      It states that a firmware update "May" not "Will" break the iPhone, meaning they did not test their update against modded phones.

    3. Re:Its not Apples QA Departments responsibly by sqlrob · · Score: 1

      It should be impossible to brick the hardware, *period*. There should be nothing, other than data loss possible with any failed firmware update. If the customer can't reset the phone to a known good state from any failed update, then it is IMHO, Apple's fault entirely.

    4. Re:Its not Apples QA Departments responsibly by homer_ca · · Score: 1

      There's a huge difference between a firmware update accidentally bricking a phone due to inadequate QA and designing firmware to deliberately detect and brick a modified phone. It's a question of intent. If it's deliberate, there are definitely emails to document that and in a lawsuit will come out in discovery. Apple qualifies the statement by saying the update "will likely result" in a bricked phone. Sounds like a mobster saying, "that's a nice restaurant you have. It'd be a shame if something were to happen to it."

    5. Re:Its not Apples QA Departments responsibly by djh101010 · · Score: 1

      No, they should not have to scour the web for these modifications however they also should not push out an update that will knowingly cause Unnecessary Damage
      It's amazing how people are condemning Apple for something that hasn't happen, won't happen, and arguably, can't happen. Since the whole thing is based on speculation and handwaving, how exactly is this non-problem Apple's fault? Can't people wait until something actually happens (and it won't) before getting all up in arms about how evil Apple is for something that hasn't and won't happen?

      Sheesh.
    6. Re:Its not Apples QA Departments responsibly by illumin8 · · Score: 1

      It should be impossible to brick the hardware, *period*. There should be nothing, other than data loss possible with any failed firmware update.
      If you think about it, you'll realize you're mistaken. Giving you the power to update firmware in the field always comes with it the capability of corrupting or destroying said firmware. You could eliminate this possibility by using ROM, instead of EEPROM (eraseable programmable ROM), but then you wouldn't be able to update the firmware after the phone was manufactured.
      --
      "When the president does it, that means it's not illegal." - Richard M. Nixon
    7. Re:Its not Apples QA Departments responsibly by stewbacca · · Score: 1

      Actually, I think it is more like a real estate agent telling you not to buy a house in THAT neighborhood, because something WILL happen to it.

    8. Re:Its not Apples QA Departments responsibly by sqlrob · · Score: 1

      You mix ROM and EEPROM. There are motherboards that do this to allow recovery from bad flashes.

    9. Re:Its not Apples QA Departments responsibly by gnasher719 · · Score: 1

      There's a huge difference between a firmware update accidentally bricking a phone due to inadequate QA and designing firmware to deliberately detect and brick a modified phone. It's a question of intent. If it's deliberate, there are definitely emails to document that and in a lawsuit will come out in discovery. Apple qualifies the statement by saying the update "will likely result" in a bricked phone. Sounds like a mobster saying, "that's a nice restaurant you have. It'd be a shame if something were to happen to it."
      What about an experienced fire fighter having a look at your restaurant kitchen and saying "that's a nice restaurant you have. It'd be a shame if something were to happen to it."
    10. Re:Its not Apples QA Departments responsibly by czmax · · Score: 1

      Use a three layer approach: (1) some boot loader ROM sufficient for launching or reloading the firmware (2) the EEPROM firmware (3) all the OS stuff. That way in a 'brick' situation you can always drop back to the ROM to reload the EEPROM firmware. This costs a bit more money though and I can see why a company would save on the costs of the ROM etc and just figure on some small percentage of devices getting accidentally bricked (power outage during firmware update) and dealing with them as warranty cases.

    11. Re:Its not Apples QA Departments responsibly by homer_ca · · Score: 1

      Only if he were to booby trap my sprinkler system to spray water if I'm in building code compliance and gasoline if I'm out of building code compliance.

    12. Re:Its not Apples QA Departments responsibly by illumin8 · · Score: 1

      Use a three layer approach: (1) some boot loader ROM sufficient for launching or reloading the firmware (2) the EEPROM firmware (3) all the OS stuff. That way in a 'brick' situation you can always drop back to the ROM to reload the EEPROM firmware. This costs a bit more money though and I can see why a company would save on the costs of the ROM etc and just figure on some small percentage of devices getting accidentally bricked (power outage during firmware update) and dealing with them as warranty cases.
      Yep; I've seen motherboards that do this by having two copies of EEPROM and flashing one, but keeping the known-good copy as a backup. I suspect Apple just didn't want to take up extra space with another chip.
      --
      "When the president does it, that means it's not illegal." - Richard M. Nixon
  7. Why? by Frosty+Piss · · Score: 0, Redundant
    Naturally, the whole thing is taken out of context as far as the law is concerned. This is what happens when non-lawyers hack up a plate of leagl code.

    But even if it wasn't, I don't understand why certain sectors are frothing about this. The iPhone is a product and it's configured in a certain way at the factory to work a certain way. It's not "commodity" hardware, a generic phone. I just don't understand why, if you dink around with it's software, which is an integral part of its operation, its "total experience", why Apple shouldn't void the warranty. It's not the same thing they sold you, why should they be responsible for it?

    --
    If you want news from today, you have to come back tomorrow.
    1. Re:Why? by Cadallin · · Score: 1
      As an aside, I think its valid to argue that a large portion of the legal morass these days is caused by the rise of lawmakers with no legal training. Back in the "good old days" (sarcasm intended) the vast majority of members in a State Legislature, or United States Congress would at least have legal education (whether they had actually practiced criminal or civil law or not although the further back in time you go, the more common it is for members to have experience in Criminal Law Practice). Nowadays, Bill Frist is the more common model, a Medical Doctor with no legal education whatsoever. MBAs are also common.

      I argue that this gives rise to chaos when it comes to actually enforcing the law, as actual legal professionals have to then interpret and decode the ramblings of uneducated amateurs into their language.

      For a Comp-Sci analogy - what happens when you take an amateur web-developer, who does mostly HTML, but knows a little Perl and PHP, and put him in charge of a production C/C++ OS development team?

    2. Re:Why? by stewbacca · · Score: 1
      Certain segments are frothing for several reasons: They are locked in to their own existing sucky phones and are really jealous of the iPhone. They can't stand the fact that Apple has another runaway hit consumer device because if this Apple thing gets rolling, all the hackers and tweaker dweebs of the world will eventually be locked out of their favorite past times. They love the 851 features of their Blackberries and couldn't imagine life with a CONSUMER (not business) phone that doesn't include a UPC bar code scanner. They don't like the fact that AT&T got their logo back on the #31 Chevy Cingular/AT&T car in NASCAR. They don't like the fact that Apple uses a glass surface that really doesn't scratch. They really love Outlook and can't survive with any other email service. They hate functionality. They can't stand the fact they can't walk around with that dweeby bluetooth ear thingy, trying to look cool while talking to their imaginary friends in public. They have general life issues in that they actually take time to make fun of somebody in a coffee shop using a MacBook or an iPhone to surf the web and feel the need to project their own insecurities about how smug or status-conscious that person is, when in reality, the person is just surfing the web.

      Ok mod me down, but that sure was my best troll/rant this week!

    3. Re:Why? by Anonymous Coward · · Score: 0

      we're just sick of these icrap posts, you numb nut. you so happy with yo icrap, then shut up and enjoy yo icrap, but stop posting it here.

  8. The way they are going about it by Rinisari · · Score: 1

    I think Apple is simply going about it wrong. Rather than being all vocal and tolling hell's bells, it could just release updates that make the current method not work. Once the new update is cracked, release another. It's a motivation to deliver something new in every update (*cough*flash*cough*).

    Yeah, it's might be like brushing it under the rug, and AT&T wouldn't like that. A policy of "We are not responsible and we do not support the unlock and will not repair the software of unlocked phones--only the hardware, but un-unlocked phones are repairable in full" might do the trick.

    1. Re:The way they are going about it by ThirdPrize · · Score: 1

      Yeah, its a bit of bad PR spin. If they had relased the update and a 'few' iPhones had stopped working, and they just happened to be the modded ones then people wouldn't be so up in arms.

      The trouble is people don't know if Apple are deliberately going to kill the iPhones where they have been tampered with or whether it's just some part of the update mechanism that has been hacked and therefore doesn't work any longer.

      I still say move development over to the iPod Touch. No one actually brought the iPhone for the phone part of it. They brought it for the touchscreen. I am sure hacking the touch will be a lot less problematic.

      --
      I have excellent Karma and I am not afraid to Troll it.
    2. Re:The way they are going about it by stewbacca · · Score: 1

      Except Apple IS going about it the way you explain. They've even gone so far as to say they will never take proactive measures to make a hacked iPhone not work. All they are stating is that they can't promise your hacked iPhone will work with future updates.

  9. Sorry Charlie by Danathar · · Score: 1

    All this sounds like griping from people who hacked their phone to unlock it.

    What did you expect? Now that Apple will probably brick your hacked phone you are pissed off. You took the risk.

  10. One more time: Warranty != Rights by mlwmohawk · · Score: 2, Insightful

    All the people posting here that, somehow, the warranty defines your rights or a manufacturer's responsibilities are absolutely 100% wrong.

    Federal, state, and local statutes trump warranties every time.

    If Apple knew, or should have known, that its firmware will destroy an iPhone regardless of after market modification, it *MUST* exercise care to prevent this from happening.

    Any defense of Apple that does not account for law or relevant legal precedent are, at best, flawed.

    1. Re:One more time: Warranty != Rights by falcon5768 · · Score: 4, Informative

      If Apple knew, or should have known, that its firmware will destroy an iPhone regardless of after market modification, it *MUST* exercise care to prevent this from happening.
      Nope. State and Federal courts are quite clear on the fact that the manufacturer is in no way obligate to support a item if the user manipulates said item so as it is not covered under the agreed to contract or warranty. Since hacking your phone to allow it to use other carriers SIM card both voids your AT&T contract AND your warranty with Apple, Apple legally has no obligation to support it at that point. And if your wondering how they came to know this courts wise, ask your local cable company. This is why its completely legal for them to burn out all the tuners in your house with a firmware upgrade to kick off people who are hacking the boxes to steal cable. A least in this case Apple isnt knowingly doing it unlike the cable companies who actually flat out broadcasted that you WILL get your equipment burned out if you put illegal stuff on their system.
      --

      "Slashdot, where telling the truth is overrated but lying is insightful."

    2. Re:One more time: Warranty != Rights by mlwmohawk · · Score: 1

      Since hacking your phone to allow it to use other carriers SIM card both voids your AT&T contract AND your warranty with Apple, Apple legally has no obligation to support it at that point.

      Only in so far as the modifications affect "supportable" operation. For instance, if the modifications keep it from connecting to the AT&T network, they don't have to fix that, but that does not free them of further responsibility.

    3. Re:One more time: Warranty != Rights by falcon5768 · · Score: 1

      since the software for the iPhones whole purpose is based around the AT&T network, yet it does mean they do not have to support it.

      --

      "Slashdot, where telling the truth is overrated but lying is insightful."

    4. Re:One more time: Warranty != Rights by mlwmohawk · · Score: 1

      since the software for the iPhones whole purpose is based around the AT&T network, yet it does mean they do not have to support it.

      This would have to be an assertion for the defense, but ....., seeing as the same basic software with a few small modifications works with other phone companies, it doesn't seem all to promising.

    5. Re:One more time: Warranty != Rights by Dun+Malg · · Score: 2, Insightful

      since the software for the iPhones whole purpose is based around the AT&T network, yet it does mean they do not have to support it. AT&T's network bis essentially a bog-standard GSM system. There is nothing special about it the iPhone can be "based around".
      --
      If a job's not worth doing, it's not worth doing right.
    6. Re:One more time: Warranty != Rights by BUL2294 · · Score: 1

      State and Federal courts are quite clear on the fact that the manufacturer is in no way obligate to support a item if the user manipulates said item so as it is not covered under the agreed to contract or warranty.
      Not entirely true. Auto manufacturers were known for doing this up until the '70s. Replace the factory radio or even the speakers with something else and your entire car's warranty (including the engine, transmission, even the paint job) was voided. Enough people got burned and got Congress to pass the Magnuson-Moss Warranty Act of 1975, specifically forbiding this practice both in the automotive industry and all other industries. This allowed a car warranty to be voided only if the aftermarket part caused the problem (with the burden of proof lying on the car manufacturer). Even then, the warranty is only partially voided. If the replacement radio shorts out the electrical system, the manufacturer is still obligated to fix a transmission problem.

      Unfortunately, Stevie J. feels he owns every little iPhone that has gone out the door and is making no effort to keep Apple under the radar. This is too bad because, while the courts may side with their flawed reasoning, all it takes is for enough pissed-off customers to lobby Congress to side with them... (Yes, it does happen--the "Do Not Call" registry being an excellent example). And someone will sue Apple under the Magnuson-Moss Warranty Act...
      --
      Windows 3.1x calc: 3.11 - 3.10 = 0.00
    7. Re:One more time: Warranty != Rights by pthisis · · Score: 1

      since the software for the iPhones whole purpose is based around the AT&T network, yet it does mean they do not have to support it.

      Hmmm. Even if the "whole purpose" is based around a service, the only way to avoid fulfilling the warranty terms when the product is used with something other than that service is to explicitly apply for an FTC waiver (which requires convincing the FTC that the item only works properly with the service and that the waiver is in the public interest). But you have to actually get that waiver _before_ using it, meaning it's got to be published in the Federal Register and an appropriate public comment time passed.

      No warrantor of a consumer product may condition his written or implied warranty of such product on the consumer's using, in connection with such product, any article or service (other than article or service provided without charge under the terms of the warranty) which is identified by brand, trade, or corporate name; except that the prohibition of this subsection may be waived by the Commission if--
      (1) the warrantor satisfies the Commission that the warranted product will function properly only if the article or service so identified is used in connection with the warranted product, and
      (2) the Commission finds that such a waiver is in the public interest.
      The Commission shall identify in the Federal Register, and permit public comment on, all applications for waiver of the prohibition of this subsection, and shall publish in the Federal Register its disposition of any such application, including the reasons therefor.


      This seems to be the only part of the Act about 3rd-party services, though.

      It looks to me like Apple may have a quite credible argument that the warranty isn't conditioned on using AT&T/Cingular; they'll happily fix phones that haven't been connected at all. The warranty is actually conditioned on not _modifying_ the product--which seems perfectly legal to me, much like those "no user servicable parts--warranty void if open" stickers.

      --
      rage, rage against the dying of the light
    8. Re:One more time: Warranty != Rights by Anonymous Coward · · Score: 0

      >And if your wondering how they came to know this courts wise, ask your local cable company. This is why its completely legal for them to burn out all the tuners in your house with a firmware upgrade to kick off people who are hacking the boxes to steal cable. A least in this case Apple isnt knowingly doing it unlike the cable companies who actually flat out broadcasted that you WILL get your equipment burned out if you put illegal stuff on their system.

      What you're speaking of is the infamous "cable bullet". It did not "burn out" any hardware (assuming it was installed correctly, I suppose if you built your own equipment out of spec, anything can happen). It didn't purposely burn out any hardware because that is illegal (and remains so). You are never allowed to take the law into your own hands, and that means you can't break a law (vandalism) even if someone else is breaking a law ("theft" of cable service) unless life or limb are on the line (there are minor exceptions to this, such as shopkeepers being able to temporarily detain shoplifters, etc, but they are far and few between).

      Instead, the "cable bullet" (really just a change in how the signal was supplied) was designed so these tuners would either no longer be able to descramble the channels or, more interestingly, would tune to a channel telling customers their cable service had an issue, or that they had won a prize, and to call customer service (at the listed number, which was a piracy hotline) immediately. At no point was the hardware modified, and the software wasn't either (I doubt that was possible, back then it was on EPROM, not EEPROM).

      It is still absolutely illegal to modify hardware for this purpose unless the company owns it. This is why with satellite service, you will find they never, ever destroy the box itself (except for editing the code they own, or select settings, and that is only when the code accepts the update, all of which are "repairable" by installing factory software again -- the "updates" are not designed to stop the box from booting up, either, they are only designed to stop the box from receiving that providers stations [there is a difference]). Instead they "destroy" (more like put in a logic loop) their smartcards, which you will clearly see state they are the property of the satellite/cable/whatever company, and not yours.

      Apple, in cahoots with AT&T would, with these rules in mind, be within their rights to modify the software on your unlocked iPhone to stop it from working with AT&T or Apple services (even this is very shaky ground). However, everything else would need to work properly, and there would need to be a method for the customer to restore the phone to original, hence proving it is a software only method. If, by mistake, some phones did get purposely bricked, that is different. A purposeful destruction of private property would never be legal, however.

      Oh, any cable company saying they will destroy your private property if you "theive" their signal should be reported to the police for suspicion of illegal activity. Unless they say they'll only do it if it will save someone's life (good luck them proving that).

    9. Re:One more time: Warranty != Rights by mstone · · Score: 1

      This is a firmware update.. if it hangs in the middle of an 'unsupported' operation, you end up with a very stylish paperweight.

      The fact that the paperweight can still execute its 'supported' features in potentia, e.g.: if it wasn't completely wedged, doesn't stop it from being a paperweight, now does it?

    10. Re:One more time: Warranty != Rights by Anonymous Coward · · Score: 0

      The warranty is actually conditioned on not _modifying_ the product--which seems perfectly legal to me, much like those "no user servicable parts--warranty void if open" stickers.

      Fail: Those stickers are meaningless without a waiver on record. Since there's no waiver, Magnuson-Moss applies. Apple must prove that owner modifications caused the failure, otherwise, they must honor the warranty. They might be to prove this if the hack is hardware. Showing that a software modification by the owner turned an iPhone into a brick would prove extremely difficult, at best.

      Oh, one other snark: You buy the iPhone. There is no contract with AT&T unless and until you sign up for AT&T service.

      -AC

    11. Re:One more time: Warranty != Rights by JoelKatz · · Score: 1

      "State and Federal courts are quite clear on the fact that the manufacturer is in no way obligate to support a item if the user manipulates said item so as it is not covered under the agreed to contract or warranty."

      Here we agree.

      "Since hacking your phone to allow it to use other carriers SIM card both voids your AT&T contract AND your warranty with Apple, Apple legally has no obligation to support it at that point."

      Here, you are wrong.

      15 USC 2302: "No warrantor of a consumer product may condition his written or implied warranty of such product on the consumer's using, in connection with such product, any article or service (other than article or service provided without charge under the terms of the warranty) which is identified by brand, trade, or corporate name..."

      Apple cannot void your warranty simply because you choose to use your phone with another carrier just like Ford can't void your car's warranty if you have your oil changes done by Jiffy Lube.

  11. Modchips? by fishybell · · Score: 2, Informative

    It's not illegal to unlock a phone because of an excemption in the DMCA, but the DMCA says nothing about requiring warranties remain invalid. If this law were used to force Apple into maintaining warranties on unlocked iPhones, then wouldn't Microsoft be also obliged to maintain warranties on 'chipped Xbox's. Right now they're merely banning them from Xbox live, but shouldn't the inability to get online with a product which heralds its online capabilities be a warranty issue?

    --
    ><));>
    1. Re:Modchips? by Anonymous Coward · · Score: 0


      Once I read The Magnuson-Moss Warranty Act states that Apple cannot void a warranty for a product with third-party enhancements or modifications to their product. The only exception to this rule is if Apple can determine that the modification or enhancement is responsible [for] damaging the product in question I thought of modchips as well.

      Looks like I may have had warranty on my PS2, XBOX and xbox 360!

  12. Auto makers have been doing it for years by steveo777 · · Score: 4, Informative
    Any car reseller, big or small, will tell you that installing 3rd party stuff in your car voids the warranty, and if you're not willing to fight, they'll walk all over you. Usually it's things like turbos and aftermarket brake systems, but sometimes they'll try to get away with little stuff. I have an aunt who had a new stereo installed to replace the factory tape deck (about 5 years ago) and when there was an ABS problem they tried to say that the CD player voided all warranties. Until I called them...

    iPhones can probably play the same crap. As long as they warn you that 3rd party software or hardware may brick the system, they're fine. Nintendo just did that with Metroid Prime 3. There is a warning saying that upgrading the firmware will most likely brick machines with mods, and even gave instructions on how to circumvent the installation. You couldn't play the game, but at least you don't have a brick.

    --
    This sig isn't original enough, it's time to come up with something witty...
    1. Re:Auto makers have been doing it for years by LWATCDR · · Score: 1

      That is exactly what the law is supposed to prevent.
      If you fry a piston and have an aftermarket turbo yea your warranty is void. But if your ABS has issues you are covered.
      So yea they might try to tell you that but it is baloney.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    2. Re:Auto makers have been doing it for years by 91degrees · · Score: 1

      Of course, in this case, you have aftermarket software and you've fried your software.

      It's a bit trickier ion that their software has fried your software. I don't think there's an obvious parallel that can be drawn by a service causing damage because of aftermarket components.

    3. Re:Auto makers have been doing it for years by Anonymous Coward · · Score: 0

      I personally just want to know when we'll start tagging defectivebydesign on hardware made by folks other than Microsoft. Sounds to me like every modern game console, the iPhone, and a multitude of other devices need it.

      Oh wait, I'm sorry, it's Apple we're talking about here. Not allowed to accuse them of doing wrong. Even though they're, you know, mini-Microsoft in a turtleneck.

      I can understand refusing to give technical support (as in deal with the calls) from unlocked users. But refusing to give basic updates, destroying the phone, then saying "Tough shit"? Refusing to support hardware warranties when the software/firmware was all that was altered? How the hell is this accepted? Because people have stopped insisting on being treated as customers, and started ACCEPTING being treated as mindless consumers.

      If more people would vote with their bucks not to pay for this bullshit, we might manage to get companies back to serving US instead of the other way 'round.

    4. Re:Auto makers have been doing it for years by tgd · · Score: 1

      No, thats not what its supposed to prevent, the aftermarket associations wishful thinking aside.

      MM is meant to do one thing and really one thing only -- prevent a warranty to be dependent on the use of manufacturer provided service and parts in lieu of *equivalent* OEM parts and service.

      It has *nothing* to do with modifications. They *can* void your warranty for changing one part of a car to an out of spec part, and its up to you to prove in the court that the change could not have caused a seemingly unrelated failure. In your example, the replacement of a piston with an aftermarket one that is not equivalent (nevermind that makes no sense) absolutely can void the warranty on the ABS because you could've damaged the ABS as an inexperienced mechanic who does not have credentials up to their standards while you were making the change.

      So, you might be trying to tell people otherwise, but FYI, its baloney.

    5. Re:Auto makers have been doing it for years by steveo777 · · Score: 1
      Try reading the example given again. The piston wasn't replaced with aftermarket parts. The situation is, if you were to install a turbo and you fried a piston due to the new turbo the warranty would not cover the damage. These parts are not directly related. As to another post about airbag circuitry included in the radio makes absolutely no sense. Not because it isn't true, but because factory radios are known to be very faulty...

      This relates to the iPhone ordeal because a third party application certainly can interfere with other parts of the systems, but it should never 'brick' a system. At least the user should be able to un-install and be done with it. But if you modify the system files you might be in a bit more trouble. The internal memory can obviously be edited by Apple remotely, so why not make it 'resetable' from iTunes to rid it of the unlocking if that is what needs to be done?

      --
      This sig isn't original enough, it's time to come up with something witty...
    6. Re:Auto makers have been doing it for years by stewbacca · · Score: 1

      The problem with your car analogy is that car companies test brakes, tires, engine power, etc. and then choose legal and safe combinations based on those tests. If the consumer wants to mess up those equations and make their car unsafe, impractical, whatever, then the car company doesn't need to be liable for what happens. Any reasonable person would know that adding an aftermarket seat cover or stereo doesn't harm the engine, so laws like the one this article talks about are in place. But I fail to see how anyone could release liability from the consumer when they muck up the guts of the iPhone. If you add a gel-cover or a different set of headphones, yeah, Apple couldn't do anything to you, but you people want to tweak the electronics of the phone.

    7. Re:Auto makers have been doing it for years by SIIHP · · Score: 1

      "The situation is, if you were to install a turbo and you fried a piston due to the new turbo the warranty would not cover the damage. These parts are not directly related."

      Um, what? Are you saying here that a turbo is not directly related to the operation of the piston?

      I'll give you a chance to clarify that.

      --
      I only go to buffets for the unlimited soft serve.
    8. Re:Auto makers have been doing it for years by stewbacca · · Score: 1

      No, if the ABS has issues and he added a turbo he WOULDN'T be covered, because the ABS is tested and calibrated based on the horsepower output of the engine in it's stock configuration. If you add more horsepower to a car, it goes faster, and the brakes have to work harder to stop. This is why companies have the right to void warranties, because consumers fail to see the cause-and-effect consequences of their actions.

    9. Re:Auto makers have been doing it for years by stewbacca · · Score: 1

      And furthermore, if he believes his own logic, doesn't he mean to say the warranty would HAVE to cover the damage, since the parts are, *cough*, somehow NOT related? Stuff like this (and iPhone tweaking) is best left up to the engineers who designed and tested it. For those who want to play weekend engineer with a $400 iPhone and they screw it up...sucks to be them.

    10. Re:Auto makers have been doing it for years by Fulcrum+of+Evil · · Score: 1

      That doesn't make any damn sense. Adding 100 hp may make my car do 130 instead of 120 - BFD. ABS is not calibrated based on HP, it's a sensor-based loop that tries to prevent wheel lock.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    11. Re:Auto makers have been doing it for years by multipartmixed · · Score: 1

      Nobody wants to tweak the electronics of the iPhone, you dumbass, they want to intall their own software on it.

      Hey, if you bought a Dell laptop and put Linux on it, then the screen broke.. Would you expect the screen to be replaced under warranty? Or would you expect Dell to tell you to shove it up your ass?

      --

      Do daemons dream of electric sleep()?
    12. Re:Auto makers have been doing it for years by steveo777 · · Score: 1
      I think I was typing two ideas at once. The turbo/piston thing is DEFINITELY related. Although I think you're more likely to fry your compression rings before you blow a piston, but that's not always predictable.

      The radio and ABS systems, however, are not related.

      --
      This sig isn't original enough, it's time to come up with something witty...
    13. Re:Auto makers have been doing it for years by stewbacca · · Score: 1

      Nobody wants to tweak the electronics of the iPhone, you dumbass, they want to intall their own software on it.
      Oh really now? So all these calls to free the iPhone from AT&T are pure fantasy? You can't unlock the iPhone with a software only solution. You have to physically hack your iPhone by opening it up and add/remove/alter electronic components to do so. You shouldn't be so quick with the "dumbass" moniker, because it is quite clear that the issue at hand is modifying the firmware and electronic components to free the iPhone from AT&T cellular service plans. One of the videos posted on YouTube actually require a soldering iron for cyrin' out loud. How is that NOT tweaking the electronics?
    14. Re:Auto makers have been doing it for years by multipartmixed · · Score: 1

      > You can't unlock the iPhone with a software only solution.

      Tell you what. Mail me your iPhone and seal the hell out of the case. I'll send it back to you unlocked.

      If the seal is broken, I'll also send you $500.

      If the seal is unbroken, you can send ME $5000.

      Deal?

      > You have to physically hack your iPhone by opening it up and
      > add/remove/alter electronic components to do so.

      Even the original, hardware-assisted unlock did not add or remove elctronic components. In fact, the only modification that was made was raising one of the address lines so that the CPU would read memory in an unprotected area during boot up, allowing arbitrary code to be executed. This is a temporary modification and requires little more than a steady hand and an ultra-sharp paperclip. The current unlock is the same, except the arbitrary code is executed by means of a buffer overrun. That's right.

      > You shouldn't be so quick with the "dumbass" moniker

      Really? You wanna ask us again what a brick is?

      > One of the videos posted on YouTube actually require a soldering iron
      > for cyrin' out loud. How is that NOT tweaking the electronics?

      You know, if I posted a video on YouTube of me smashing a car window with a brick so that I could hotwire it -- would that imply that ALL vehicles are stolen by smashing the window? Or would it imply that ONE way to achieve that goal was to smash the window?

      > How is that NOT tweaking the electronics?

      Finally, I did NOT say that people were not tweaking the electronics. I stated that that was not their GOAL. Their GOAL is to be able to run arbitrary software on the phone.

      I think, perhaps before you run off at the mouth, that you should either become technically competent in the field you're talking about OR increase your reading comprehension. Both would be nice, but I think either would suffice.

      --

      Do daemons dream of electric sleep()?
    15. Re:Auto makers have been doing it for years by stewbacca · · Score: 1
      Wow. Nice people skills. Or, instead of your rampage/diatribe, you could, I don't know, actually have submitted the fact that people are indeed unlocking iPhones with software solutions as contrary evidence to my uninformed claim. You know that way, you could have informed me (and hundreds of others) AND be a helpful, supportive contributor to slashdot. I'm not the one that was being argumentative and went right for the dumbass moniker.

      Really? You wanna ask us again what a brick is?
      Nope. The others adequately clarified that for me, without feeling insecure enough to call me a dumbass for asking. Maybe you should give that a try some time instead of basking in your intellectual superiority.
    16. Re:Auto makers have been doing it for years by stewbacca · · Score: 1
      Sorry for the double post, but I still can't find anything about unlocking an iPhone with software only. I'm not saying it isn't possible, in the light of your claim to the contrary, but I am saying that EVERY mention of unlocking the iPhone in this thread and a quick look on the Internet talks about physically swapping a SIM card, then using software to convert it over. You provided a link to the endgadget software, but I went there and there were no details. For all I can tell, it is the software interface needed to associate the new physical SIM card with the iPhone.

      So yeah, I may be a dumbass, but at least I'm TRYING to follow up on your claims before I revert to your childish mannerisms. Call me a skeptic, but I generally don't take people's word for gospel when they oversimplify issues and call people a dumbass in the middle of a civil, logical conversation.

    17. Re:Auto makers have been doing it for years by multipartmixed · · Score: 1

      A SIM card swap is not a hardware modification. A SIM card is (basically) a memory card -- it is a purposefully-removable item. SIM stands for Subscriber Identity Module. Changing a SIM card is a normal operation for a GSM phone, and the only difference between Apple's phone and others' is that the SIM tray needs to be popped out with a paperclip... most phones hide it under the battery or in a tray that you can claw out with a fingernail.

      The linked software, when run and activated unlocks the phone. This means that the phone will allow itself to be used with a different network's SIM.

      > I generally don't take people's word for gospel when they oversimplify issues and
      > call people a dumbass in the middle of a civil, logical conversation.

      Call me a bigot, but I call people dumbasses when it's apparent (to me) that they have difficulty stringing together coherent thoughts.

      I don't think I've even seen ONE reference to ONE person EVER modifying their iPhone so that they could monkey with the hardware. Virtually EVERYONE wants to modify it so that they can run arbitrary software on it / use it on another network. Whether the hardware mods are required to achieve this goal is orthogonal to your original claim. The fact of the matter is, modifying the hardware is no-one-that-I-can-think-of's goal. People just want to use the phone as a general computing platform and/or use it on a different network.

      --

      Do daemons dream of electric sleep()?
    18. Re:Auto makers have been doing it for years by stewbacca · · Score: 1
      Ok, that's more civil. Thank you. So basically we agree more than you think, because my initial point is that people are "hacking" iPhones to get a different carrier and you say they are hacking it to get ANY type of benefit from third party apps. My contention is that Apple isn't taking a stance against third party software, only attempts to unlock the phone to third party carriers. Even then, it isn't really a stance or a threat more than it is the reality that their upgrades simply can't/won't work if the iPhone isn't set up the way the upgrades are designed to work.

      I see other terms used on slashdot for what you are talking about (jailbreaking) but "unlocking" seems to be used solely for the purpose of switching carriers.

      So our disagreement boils down to the fact that you don't consider swapping a SIM as hardware manipulation, and I (perhaps mistakenly) do. Replace all instances of my use of "hardware" with "SIM" and I think we basically agree, dumbass aside.

    19. Re:Auto makers have been doing it for years by ajs318 · · Score: 1

      By increasing the engine kilowattage, you might potentially have driven the feedback control system outside of the designed linear region and into a state which potentially could not be corrected. Any braking system is only good up to a certain engine kW -- it can only convert kinetic energy to heat at a certain rate. And if the engine is supplying KE faster than (this rate plus losses due to friction), then the brakes will not be able to bring the car to a halt, even at 100% duty.

      --
      Je fume. Tu fumes. Nous fûmes!
    20. Re:Auto makers have been doing it for years by Fulcrum+of+Evil · · Score: 1

      Listen, sport, you stop feeding the throttle when the brakes are on. Never mind that every braking system out there is capable of locking the wheels on oem tires. The thing that changes how brakes work is bigger, stickier tires, not increased engine power and the feedback loop for abs is between applied brake torque and a sensor that measures wheel spin. Oh, and designed linear region? You just don't know what you're talking about.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    21. Re:Auto makers have been doing it for years by tgd · · Score: 1

      And my point is that from a legal standpoint, contrary to what SEMA, etc like to say Magnusson-Moss does not protect you in either case. If a single part or a single service on the car has been done using non-OEM-spec parts or service by people who have not met the requirements set by the manufacturer for certification, the warranty can absolutely legally be voided. Its not done very often because generally companies want to keep customers happy, but MM does NOT in any form protect against modifications to a vehicle or any other device.

      SEMA has persisted in that BS because there's a multibillion dollar industry they represent that relies on people voiding their warranties. But when push comes to shove in court, no one wins when they try win that battle against the manufacturer.

  13. Apple = Conservative company by Anonymous Coward · · Score: 0

    As we have seen in many instances, and especially in SteveJob's recent flagrant disregard for the law in his options backdating, Apple is a very conservative company, in the respect that it doesn't really care what the law is (meaning, they behave as a conservative).

    So the conservative solution to this is like all conservative solutions: if you break the law... just get rid of the law you broke! Support "deregulation" of the consumer protection laws Apple ignores. It's the only truly conservative recourse.

    1. Re:Apple = Conservative company by Aurisor · · Score: 1

      "conservative"

      That word doesn't mean what you think it means. Perhaps you meant "neo-conservative"?

  14. Huh? by IANAAC · · Score: 3, Insightful

    Is the SIM Unlock process that has become mainstream doing damage to iPhone?

    Who said it's mainstream? I know of no one that has actualy unlocked their iphone.

    1. Re:Huh? by Winckle · · Score: 2, Informative

      I think he means SIM unlocking in general, which is fairly mainstream in the UK. If a friend asks me whether he can give his phone to his mum or it needs unlocking he would certainly understand my reply.

    2. Re:Huh? by daveschroeder · · Score: 1

      No, it means, "among the unlocking mechanisms for then iPhone, the one which is the most popular". This does not imply that iPhone unlocking is mainstream, and is not referring to SIM unlocking in general. It is referring to the most common unlock for iPhone, and "mainstream" was far from a suitable choice of words.

    3. Re:Huh? by JM78 · · Score: 1

      Huh is right; how did this get modded insightful?

      Those that have unlocked their iPhones use the SIM Unlock process making the SIM Unlock process the mainstream way of unlocking. Because you don't know anyone who has actually done it doesn't make the most popular process any more or less mainstream.

      --
      I am Jack's smirking revenge.
  15. My question is... by IwarkChocobos · · Score: 2, Interesting

    Why should apple care? Doesn't unlocking a phone only take customers away from the carrier? Apple already got the profit from the phone when it was purchased, who gives a shit if someone wants to use it on a different network. If anyone should be pissed, it's Cingular/ATT. Also, this practice of voiding warranties for "hacking phones" is not new. I've hacked my Verizon Razr V3c because it just works way better with the hacks (all it does it enable features that are normally disabled, I dont change the software) and guess what, that voids the warranty with Verizon, but not with my phone insurance company.

    1. Re:My question is... by falcon5768 · · Score: 1
      Apple has a exclusive contract with AT&T. When the exclusiveness of said contract is being threatened, I think the carrier is going to bitch to you to lock your fucking phone better.

      --

      "Slashdot, where telling the truth is overrated but lying is insightful."

    2. Re:My question is... by LynnwoodRooster · · Score: 1
      Apple makes money monthly for every iPhone on the AT&T network. Apple probably doesn't care about the profit on the phone, considering the $3/month they make for every AT&T subscriber with an iPhone. And an additional $8 for every non-AT&T subscriber that switches over to an AT&T iPhone. Sell 3 million iPhones, you're making $108,000,000 a year.

      Note that this is pure profit for Apple; they have zero costs in receiving this revenue! AT&T pays for the wireless network and its maintenance. Apple just gets the "royalty", so to speak. One hundred million dollars a year in gross profit.

      The iPhone isn't revolutionary because of its form factor or UI. It's revolutionary because for the first time in the US a cell carrier is sharing monthly revenue with a phone manufacturer. That's never happened. And the rumors are that Verizon and T-Mobile rebuffed Apple over this very sharing. Which is why Apple partnered with AT&T.

      It's the backend royalties where the big money is. Considering cell phones are kept for 2 years on average in the US, that means Apple makes at least $72 additional on every iPhone (this is $72 in PROFIT, not just revenue) that sticks on the AT&T network.

      No, there's a huge incentive to keep the iPhones firmly in the grasp of AT&T...

      --
      Browsing at +1 - no ACs, I ignore their posts. So refreshing!
    3. Re:My question is... by stewbacca · · Score: 1

      Note that this is pure profit for Apple; they have zero costs in receiving this revenue!
      Not true. Apple will be dipping into the coffers to cover the initial and ongoing R&D expenses for the iPhone for years to come. Not to mention, they just opened a huge new section of the Austin campus to handle iPhone customer service and training. That staff of hundreds of people aren't making minimum wage either. One trainer job I applied for paid $75,000 per year, and there were three or four of them open still. Then there are all the administrative/accounting jobs required to manage the iPhone business department revenue, such as that coming from AT&T kickbacks. And probably 100 other costs that I can't think of at the moment. Consumers like to think everything is free, and companies are evil for requiring money to provide goods and services.

      I'm sure there's a business term for the amount of money Apple is losing due to lost customers because of being locked into AT&T as well, so getting every penny out of using AT&T is probably a good tradeoff and business practice.

    4. Re:My question is... by prockcore · · Score: 1

      Apple will be dipping into the coffers to cover the initial and ongoing R&D expenses for the iPhone for years to come.


      I love how people think that R&D is some external cost. Apple is profitable every quarter. That means that R&D for the iPhone has already been recouped. Income was more than Payroll last quarter and will be again this quarter.
    5. Re:My question is... by LynnwoodRooster · · Score: 1
      If the iPhone is used with ANY OTHER CARRIER, that recurring income goes away. If all iPhones are used on networks other than AT&T, then Apple loses that $108 million a year. Suddenly those tech support costs go completely into the red.

      The biggest reason Apple would want to lock you down to AT&T is the fact they get a residual every single month. They would have to have support folks for the iPhone regardless of the carrier; those are fixed costs you have to bear. The fact they get extra revenue from AT&T that they would not get from T-Mobile or any of the other carriers means it's extra profit above and beyond the baseline.

      --
      Browsing at +1 - no ACs, I ignore their posts. So refreshing!
    6. Re:My question is... by stewbacca · · Score: 1

      They would have to have support folks for the iPhone regardless of the carrier; those are fixed costs you have to bear.
      Except as soon as someone calls in and says they have a hacked iPhone, Apple doesn't have to support them. That's kind of what this whole deal is about. It kind of proves my point, that to keep the iPhone support, r&d, and all related costs going, they need to get revenue from sales and AT&T contracts to do so.
    7. Re:My question is... by gl4ss · · Score: 1

      unsubsidized phones and plan competition for the win.

      iphone isn't cheap, it's one of the most expensive phones on the market.

      --
      world was created 5 seconds before this post as it is.
  16. No other option outside of the US by Starturtle · · Score: 1

    If Apple would assist with providing an easily accessible method to have a working iPhone in Canada I'll have no reason to unlocked an iPhone.

    1. Re:No other option outside of the US by betterunixthanunix · · Score: 1
      Sorry, I guess that like me, you are not special enough to be in the exclusive Apple club. I cannot run iTunes on my computer, nor can I access iTunes 7 shares over my LAN. Remember: Apple is EXCLUSIVE! Apple is a high standard than everything else; you can't have everyone using Apple hardware and software, or else Apple wouldn't have that image of something that is "better" than what everyone else has.

      Why else would they deliberately limit their market by refusing to license iPhones to other carriers?

      --
      Palm trees and 8
    2. Re:No other option outside of the US by Anonymous Coward · · Score: 0

      This is obvious to most, but your post shows it's not obvious to all.

      The exclusive contract with AT&T may have occured because Apple could not find a carrier to invest in the iPhone launch without an exclusive. Or, Apple may have realized that carriers have a history of poorly supporting new technology launchs, and the exclusive with AT&T was there to incent AT&T to properly support the launch of iPhone.

      As to the product not working in Canada... I don't believe Apple markets the iPhone in Canada, so they likely have no interest in whether or not it works there.

    3. Re:No other option outside of the US by RFaulder · · Score: 1

      Well, originally they wanted to go with Verizon in the US, but they wanted to put their shitty Verizon OS on it and add restrictions like they do with every phone they have.

    4. Re:No other option outside of the US by betterunixthanunix · · Score: 1
      Or, since every other phone maker sells phones across networks, and Apple is going for exclusive contracts elsewhere, we can conclude that your "Well, Apple may have realized ..." and "it may be this" are just speculation. Look at Apple's marketing campaigns. They love being exclusive, it is driving their sales. The fact that Apple products appear to be floating above everything else is the best marketing campaign Apple has thought of. "Think different" and "I'm a cool guy personifying a Mac, there is a geeky guy personifying the rest of the market." iPods only officially work with iTunes, and iTunes music can't be played on anything else. Mac OS X only officially runs on Apple hardware, and until very recently, Apple hardware only officially ran Mac OS X. And iPhones are only available with one carrier, even though other phones are available on every other carrier.

      Sorry to burst your bubble, but Apple isn't some shiny, brilliant group of engineers that love seeing their products in use. Apple's moves have nothing to do with creating superior technology, unless they can get a hold of it for free; their moves have to do with making money, as much as possible as fast as possible, and putting up a facade of being on a completely different level than the rest of the market drives up their sales.

      --
      Palm trees and 8
  17. Software/Firmware != Hardware by betterunixthanunix · · Score: 1
    If they grant you a warranty on the phone, then that warranty is on THE PHONE. If you change the configuration of the phone, including the software, they can only get out of their warranty obligation if your configuration actually damaged the phone. The iPhone is billed as a computer (and it is), so installing different software on it should not void the warranty, unless that software deliberately damaged the phone. If they install software and your phone that stops the phone from working, I fail to see how they are not responsible for fulfilling the warranty.

    But I can see them simply re-locking the phone as part of the warranty. IANAL, by the way.

    --
    Palm trees and 8
    1. Re:Software/Firmware != Hardware by Frosty+Piss · · Score: 1

      If they grant you a warranty on the phone, then that warranty is on THE PHONE.

      The software that runs the phone is part of the phone.

      If you buy a Chevy arnd replace the engine with some aftermarket engine, Chevy isn't going to fix it when you break it.

      --
      If you want news from today, you have to come back tomorrow.
    2. Re:Software/Firmware != Hardware by betterunixthanunix · · Score: 1

      The software is part of the configuration of the phone, not the phone itself. Software (including firmware) is not some tangible thing like a car engine. Software is just another form of data -- data that directs the behavior of the hardware. A better comparison is taking your new Chevy, and reconfiguring the the buttons on your dashboard, so that they are more comfortable for you, and Chevy claiming that voids your warranty when your brakes fail.

      --
      Palm trees and 8
    3. Re:Software/Firmware != Hardware by king-manic · · Score: 1

      The software that runs the phone is part of the phone.

      If you buy a Chevy arnd replace the engine with some aftermarket engine, Chevy isn't going to fix it when you break it.


      In most markets, if you buy a Chevy and replace the engine and then find the door hinge is defective. They must fix the door hinge. Any part not directly affected the replacement. The manufacturer would obviously not want to fix anything. Laws vary by jurisdiction.

      --
      "There are more things in heaven and earth, Horatio, than are dreamt of in your philosophy."
    4. Re:Software/Firmware != Hardware by arkanes · · Score: 1

      If you buy a Chevy arnd replace the engine with some aftermarket engine, Chevy isn't going to fix it when you break it.
      Utter bullshit, and could only be said by someone without the slightest inkling of what consumer protection laws are for. Why do you think there's an aftermarket for car parts at all? If you replace the engine in a Chevy, Chevy won't fix the *engine*, but if the differential burns out they'll sure as hell fix that. And if you take it to the dealership to get your brake pads changed, they'll do that. And if they ruin your car while doing that service on, they're going to be liable no matter how many aftermarket parts you had in it.

      I could see cases where an update might legitimately brick a phone, like if someone installs custom firmware on it. But the SIM unlocking isn't a firmware replacement or even a hack, it's a settings update, and there's no reason whatsoever why a firmware update should damage the phone in any way. At the very worst, it should refuse to install, but there's not really much justification even for that.

    5. Re:Software/Firmware != Hardware by Frosty+Piss · · Score: 1

      The software is part of the configuration of the phone, not the phone itself.

      I think that's a pretty liberal view. The phone was designed specifically to work with the software, it is an integral part of the phone.

      I don't see a problem with cracking the software issue and customizing it with your own brew. But don't expect Apple to want to support something they didn't make (the software) and have no control over.

      --
      If you want news from today, you have to come back tomorrow.
    6. Re:Software/Firmware != Hardware by SIIHP · · Score: 1

      "If you change the configuration of the phone, including the software, they can only get out of their warranty obligation if your configuration actually damaged the phone."

      Source? Right...

      --
      I only go to buffets for the unlimited soft serve.
    7. Re:Software/Firmware != Hardware by Anonymous Coward · · Score: 0

      If you buy a Chevy arnd replace the engine with some aftermarket engine, Chevy isn't going to fix it when you break it.

      They better fix the door look when it breaks. Car analogies are worthless and stupid.

    8. Re:Software/Firmware != Hardware by SIIHP · · Score: 2, Informative

      "Chevy won't fix the *engine*, but if the differential burns out they'll sure as hell fix that."

      No they won't. The diff operation is changed by the different engine you installed, and will not be covered. Saying so doesn't change that, it just makes you wrong.

      And the rest of your post is wrong too.

      --
      I only go to buffets for the unlimited soft serve.
    9. Re:Software/Firmware != Hardware by Fulcrum+of+Evil · · Score: 1

      If you buy a Chevy arnd replace the engine with some aftermarket engine, Chevy isn't going to fix it when you break it.

      They still have to fix the radio when it breaks.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    10. Re:Software/Firmware != Hardware by seriesrover · · Score: 1
      Exactly. In a nutshell you can't expect Apple to warranty something they didn't sell you. Your nitpicking about the software being a configuration of the phone, instead of the phone, is way off base. Its clearly not. Apple is responsible for any untouched runnable code (software or firmware) that the user can configure through said code.


      The way to change any configuration on the iPhone is through the Apple 'authorized' UI (be it hw or sw), not some hack that someone can got working.

    11. Re:Software/Firmware != Hardware by vought · · Score: 1

      A better comparison is taking your new Chevy, and reconfiguring the the buttons on your dashboard, so that they are more comfortable for you, and Chevy claiming that voids your warranty when your brakes fail. And if you screwed up the electronics that control any aspect of the braking system they'd be completely in the clear claiming this.
  18. Wow by Anonymous Coward · · Score: 0

    The astroturfers are quick!

  19. redux: Warranty != Rights by mlwmohawk · · Score: 0

    People wake up!! All the people posting here that, somehow, the warranty defines your rights or a manufacturer's responsibilities are absolutely 100% wrong.

    Federal, state, and local statutes trump warranties every time. You have rights, and Apple has responsibilities!!!

    If Apple knew, or should have known, that its firmware will destroy an iPhone regardless of after market modification, it *MUST* exercise care to prevent this from happening.

    Any defense of Apple that does not account for law or relevant legal precedent are, at best, flawed.

    1. Re:redux: Warranty != Rights by Anonymous Coward · · Score: 1, Insightful

      If Apple knew, or should have known, that its firmware will destroy an iPhone regardless of after market modification, it *MUST* exercise care to prevent this from happening.

      They did. They told you not to fuck around with modifications, dummy.

    2. Re:redux: Warranty != Rights by mlwmohawk · · Score: 1

      If Apple knew, or should have known, that its firmware will destroy an iPhone regardless of after market modification, it *MUST* exercise care to prevent this from happening.

      They did. They told you not to fuck around with modifications, dummy.


      Depending on the applicable laws, they probably don't have the right to demand that you do not modify YOUR property.

      if, they can't prove that *you* damaged the device, and mere modification is not necessarily "damage," regardless of their protestations, they have legal responsibilities. If an expert testifies and can prove the modifications made do not harm the unit, and all reports seem to indicate that, Apple is responsible regardless of what ever their warranty says.

    3. Re:redux: Warranty != Rights by stewbacca · · Score: 2, Insightful
      Well, I'm not the smartest person on the planet, but everything you say seems exactly 180 degrees off. It isn't a company's responsibility to ensure their product works outside of the realm of how that company created the product to work. It IS the consumer's responsibility to take responsibility for any problems they cause to their product with unapproved hacks.

      Now if you'd like to bolster your claims to the contrary, why don't you actually post some relevant legal precedent for reference?

    4. Re:redux: Warranty != Rights by stewbacca · · Score: 1

      Apple isn't demanding that you not modify YOUR property. They are telling you IF you do modify YOUR property, it MIGHT not work correctly in the next upgrade cycles.

    5. Re:redux: Warranty != Rights by mlwmohawk · · Score: 1

      Its funny, but about 10 years ago, a nail polish company was found to be negligent because its nail polish did not cure chigger bites. While they did not advertise or claim to support that use of their product, they were held negligent for the failure because it was a "common" practice and the knew or should have known that was a use of their product.

      I don't know the specific laws or decisions off the top of my head, but suffice to say an OEM's warranty only applies in the absence of relevant statute.

    6. Re:redux: Warranty != Rights by Anonymous Coward · · Score: 0

      it *MUST* exercise care to prevent this from happening

      that's exactly what they're trying to do by
      a)releasing regular updates and
      b)making public statements warning against it

  20. Application of this Law by raijinsetsu · · Score: 1

    I can see how this law would prevent Apple from voiding the HARDWARE warranty, but I see that "hacking" your phone would void all software warranties. According to the excerpt, unless Apple could prove that the changes to the firmware caused hardware failure, then they would have to continue their warranty on hardware replacements. They could, however, refuse to re-flash the phone or deal with any interface/software problems. I think this law would be better applied to those stories we hear about laptop and PC owners being denied under-warranty hardware replacements when they are using non-Windows OS's.

  21. Jobs had a sink-the-company idea: AT&T! by Futurepower(R) · · Score: 3, Informative

    This entire problem occurred because Apple partnered with AT&T. It was a sink-the-company idea for Apple, in my opinion, guaranteed to get Apple some VERY bad press.

    People have a legitimate need to use other SIM cards in their phones. For example, if you travel to Europe or Asia or South America, it is common to buy a SIM card there (GSM phones only) because then you get a local number, making it much cheaper for local people to call you and for you to call them.

    Locking the iPhone while charging the full price for it was an attempt to squeeze more money from buyers, most of whom don't fully understand all the ways cellular phone companies, and now Apple, can abuse them, in my opinion.

    AT&T is no longer the old AT&T, because the name was sold to SBC. My understanding is that the SBC trademark was worse than useless because the company is so abusive. So, the managers decided to use another name. Those interested in how that happened can watch Stephen Colbert explain in a 1 minute 14 second video: The New AT&T.

    SBC taking the name AT&T is, in my opinion, a kind of legal fraud, but fraud nevertheless. People are bound to be confused and misled. AT&T had a very good reputation. SBC-AT&T is a completely different company, and has no connection in its culture with the old AT&T. At the very least, the SEC should require the company to disclose in the first sentence of any prospectus for its stock that there is no connection whatsoever.

    1. Re:Jobs had a sink-the-company idea: AT&T! by LcdAngel · · Score: 0

      One problem At&t has is their coverage. I live in middle of the United States. Coverage extend from the east to the west only. From the west to the east coverage is very sparse. I know a lot of people here who would buy an Iphone, but its not available. If Apple had not contracted with such a low coverage provider, they would not be facing these problems.

      Not only that, but when you compare the following (for our area. It could be higher for others):

      • T-Moblile at 60$/1500 minutes
      • Sprint at 80$/1350 with better coverage
      • US Celluar at 60/1300
      • and At&t at 80$/1350 with less coverage

      The winners will always be Sprint, T-Mobile, and US cellular. The Iphone will not save At&t's wireless branch. And until it's available to other carriers, it will not see and end to unlocking phones. Its simple supply and demand. When you have something from apple that is so in demand why wouldn't you unlock it to work with a better network?

    2. Re:Jobs had a sink-the-company idea: AT&T! by another_neophyte · · Score: 0

      The last point that 'there is no connection whatsover' is just wrong. SBC and AT&T merged with the resultant company choosing to use the AT&T name and brand. SBC was certainly the controlling party in the merger, but it was a merger. Not a completely different company. It may not have any connection in it's culture to the old AT&T.

    3. Re:Jobs had a sink-the-company idea: AT&T! by Electrawn · · Score: 1

      AT&T is no longer the old AT&T, because the name was sold to SBC.

      SBC taking the name AT&T is, in my opinion, a kind of legal fraud, but fraud nevertheless. People are bound to be confused and misled. AT&T had a very good reputation. I have no clue how the parent post is informative when they obviously are too young or too ignorant to know about AT&T's 1982 monopoly breakup.

      1982: AT&T->7 baby bells + AT&T long distance.

      1990s:Ameritech, Southwestern bell, Bell South, Pacific Bell merge over the years to form SBC.

      2005: SBC (a bunch of former baby bells) and AT&T (former monopoly) merge again to create...AT&T. And the death star is rebuilt again in shiny Web 2.0.

      Wikipedia link (remember to fact check):

      http://en.wikipedia.org/wiki/Bell_System_divestiture

      -jtp

    4. Re:Jobs had a sink-the-company idea: AT&T! by lelitsch · · Score: 1
      Some people really need to get a hobby. Uh, sorry, I forgot this is Slashdot--so this is the hobby
      Seriously, how interesting is a cell phone that we now had a few hundred stories about it.

      It's a phone, not food, water or shelter

      It's one of hundreds of phones in the market, you can buy it or not

      OpenMoko will be out soon and it will be much better than the iPhone. And it will play ogg.

      OK, coming back to your point: No major US wireless company sells unlocked GSM phones, you have to go to Europe or Asia for that. And since only 15% of US citizens even have a passport, AT&T and Apple couldn't really give a hoot.

      Anyway, I have an iPhone, I travel to about 10 countries a year, so yeah, I'd love to have an unlocked iPhone. But I knew that when I bought it--and quite frankly, on most European data plans, I would not want to use any GSM smart phone. A number of Australian carries have pretty sweet $20/month data plans, though.

      But please, doesn't anyone have anything more important to do than bitch about a phone???? Oh yeah, I forgot, this is slashdot...

    5. Re:Jobs had a sink-the-company idea: AT&T! by dctoastman · · Score: 1

      You say that but don't bother to mention that Bellsouth/Cingular was the last merger to take place (in 2006). After SBC had assumed the AT&T name.

    6. Re:Jobs had a sink-the-company idea: AT&T! by Raenex · · Score: 1

      I'm not a fan of Colbert's show, but that clip is awesome. Thanks for the link :)

  22. -1 industry apologist by Aurisor · · Score: 4, Interesting

    I don't know if you've written any software yourself, but the first rule about deploying patches to consumer software is that you are NOT allowed to make any assumptions about the state of the hardware or software.

    The reason people are up in arms is because apple has raised the possibility of this update permanently bricking your iPhone. That possibility is unacceptable. Any decent programmer would just have the update checksum the software and firmware and overwrite any hacked copies with the new version. None of your arguments about altered radio firmware and so on have any bearing on the issue...what does it matter which piece of firmware we're talking about? If an update requires consistency on the part of other elements of the phone, it needs to ensure that they are consistent, and if they are not, either fix them or fail gracefully.

    The bottom line is that there is a lot of precedent for hardware warranties being unaffected by the actions a consumer takes with his software. Any manufacturer who causes users 4-600$ dollars worth of hardware loss via a software update would be liable. End of story.

    Believe me, if PC manufacturers could have voided your warranty for installing a different operating system (as they would be able to according to your arguments), they would have years ago.

    1. Re:-1 industry apologist by daveschroeder · · Score: 3, Interesting

      Apple is doing this with iPhone OS updates; that is, checking to see if it is in an expected state, and if it's not, requiring the iPhone to go through a "restore".

      However, for the radio firmware, Apple is alleging that some unlock mechanisms may have irreparably damaged the hardware of the phone. If that is correct - if the iPhone hardware has been permanently damaged - then I don't think Apple is to blame. If, however, it is all software-only and reversible, then I agree with you completely, and expect Apple to try to follow exactly that path.

    2. Re:-1 industry apologist by WidescreenFreak · · Score: 4, Interesting

      Believe me, if PC manufacturers could have voided your warranty for installing a different operating system (as they would be able to according to your arguments), they would have years ago.

      They do try! Years ago, I made the mistake of buying an HP PC that came with a very new XP (pre-SP1). Before I even turned the PC on, I took the hard drive out, installed a new one, and installed a fresh copy of Windows 2000. Less than a year later (still within warranty), the optical drive died. Sure enough, HP's outsourced, "have to follow the checklist" tech people tried their best to tell me that I was not entitled to a DVD drive replacement because I didn't have the "correct" operating system installed. Anyone of a less stubborn nature than me would have given up, but I fought through several days' worth of phone calls and demands to talk to managers. At that point it became a matter of principle. But I finally got the replacement sent to me. They might not have been "voiding" the warranty by initially denying my warranty claim, but I don't see any difference between voiding and trying to not honor a warranty. Either way, you're not getting the service that you're entitled to.

      Just because we know that trying to blame software for hardware failures is ridiculous, there are even more people out there who have no clue that they're separate issues and will just give up.

      --
      The Overrated mod is for reversing inappropriate, positive mods, not for voicing disagreement with a post.
    3. Re:-1 industry apologist by stewbacca · · Score: 1

      I don't know if you've written any software yourself, but the first rule about deploying patches to consumer software is that you are NOT allowed to make any assumptions about the state of the hardware or software. This is why any and all software ever written works on every platform available? Of course you make assumptions about the state of the hardware and operating systems in play when you start ANY project. These assumptions are what make Apple products work so well. These assumptions are also what make Apple 5% of the computing market share.
    4. Re:-1 industry apologist by Aurisor · · Score: 1

      "This is why any and all software ever written works on every platform available? Of course you make assumptions about the state of the hardware and operating systems in play when you start ANY project. These assumptions are what make Apple products work so well. These assumptions are also what make Apple 5% of the computing market share."

      Read what I wrote again. I said the STATE of the hardware or software when DEPLOYING PATCHES. We're not even talking about the same thing.

    5. Re:-1 industry apologist by teknopurge · · Score: 1

      What if part of the process of "hacking" the iPhone causes the mechanism that fetches the checksum to fail? Fail so bad that it bricks the phone? How can apple code for something they did not do and may not be able to detect?

      Just wondering.

    6. Re:-1 industry apologist by alshithead · · Score: 1

      "They might not have been "voiding" the warranty by initially denying my warranty claim, but I don't see any difference between voiding and trying to not honor a warranty. Either way, you're not getting the service that you're entitled to. "

      I see where you're coming from but I have to respectfully disagree. The difference I see is poor customer service versus the company's flat out refusal because they know they are in the right. Better examples of customer service would help you in EITHER case and there are companies out there that will give replacements or repairs even though the damage is caused by the customer. In your case, their customer service failed by not recognizing that what you did in no way impacted the part that failed. In another case, where someone's actions caused the part failure, they would certainly be justified in telling you to go to hell. I think that is the difference between trying not to honor a warranty and out and out voiding.

      Cheers,

      al

      --
      I reserve the right to think for myself. Others' opinions are optional. Puppy on lap = typos...not illiteracy.
    7. Re:-1 industry apologist by sjames · · Score: 1

      What if part of the process of "hacking" the iPhone causes the mechanism that fetches the checksum to fail? Fail so bad that it bricks the phone? How can apple code for something they did not do and may not be able to detect?

      That's actually quite simple. If it can't fetch the checksum, then the update should not happen at all. It should report the update failure and leave the phone functional. In other words, an update shouldn't actually overwrite ANYTHING until it can be sure all's well.

      In PCs, a common approach is to divide the BIOS into a boot block that doesn't ever get updated and the rest which does. Should an update fail, that leaves the boot block ready to try again (possibly requiring a "rescue" jumper to be moved). In other cases, there are 2 boot blocks and a jumper to select which one gets used. Finally, in a very few boards there are two completely seperate flash chips with two entirely seperate BIOS loads.

      In the embedded world, the boot block is sometimes on a PROM (not EPROM, PROM. That is, can't be changed without a soldering iron). It's only job is to decide if it should jump to the flash firmware or enter rescue mode for a re-flash.

      For an example of recoverability, the WRT54GL can accept flash updates from the production software. If the firmware update goes wrong (for example, power fails in mid update) or buggy firmware causes a crash, the bootloader which is not part of the update (called CFE) will accept new firmware via TFTP. If that fails, thers's a JTAG interface on the board. At the factory, the JTAG is accessed with a "bed of nails" interface. Hackers sometimes choose to solder pins in but it's not necessarily most of the time.

    8. Re:-1 industry apologist by coolGuyZak · · Score: 1

      Just because we know that trying to blame software for hardware failures is ridiculous, there are even more people out there who have no clue that they're separate issues and will just give up.

      Sorry, but anyone who believes that software cannot induce hardware failure doesn't understand the relationship between hardware and software, much less the constraints imposed by embedded systems.

      Here's some personal anecdote: A while back, when I was still a Gentoo fan, I was recompiling my kernel. I wasn't paying attention and "accidentally" enabled the pass arguments via registers feature.

      I installed the kernel, rebooted the machine, and left to grab a soda. Returning, Pepsi in hand, X greeted me with the delightfully tangy fragrance of a spring shower (ozone), and I could swear I heard the faint pitter-patter of rain (exploding transistors).

      Then the monitor went dark, and it slowly dawned on me this wasn't some great feature of my new kernel. I rebooted.

      The monitor stayed dark; my inner penguin cried.

      It turns out that the NVidia driver was expecting values to be passed on the stack. Meanwhile the kernel was fine and dandy, but in register-land. The driver read just the right values to fry the card.

      Here's the great part: you don't have to destroy the hardware to render it inoperable. Say we have an OS running on a CPU, a peripheral including CPU-controlled firmware, and a bus to connect them. Now say I modify (intentionally or not) the firmware-CPU interface. The hardware operates (albeit it has no clue what I want it to do); the CPU operates; the bus signals the peripheral just fine. Everything except the firmware, which isn't capable of understanding the signal, is in order. Oops, Borked.

      Or, say that the firmware is ok, but there's some value (such as a lock code) stored in nvram/flash/PROM, and I modify that value. Then a firmware update changes how the value is interpreted, so my value is no longer valid (but the unmodified value would have been fine). Oops, borked.

      This completely ignores the design of embedded devices. There's not many resources, so the coupling tends to be tighter between components, and most components aren't designed for general computing... Long and short, everything has to be tiny, tight ant integrated.

      The reality is that most geeks don't understand low-level computing (even me), and it shows in conversations like this one.

  23. not necessarily by Anonymous Coward · · Score: 0

    Some car manufacturers integrate non-audio circuitry into the radio. GM, for example, did (still does?) that for the airbag controls so its not necessarily baloney that replacing your car's factory audio headunit caused your ABS to cease operating or operate incorrectly.

    Sometimes the line between vendor-forced lock-ins and blind cost-reduction engineering is hard to distinguish.

  24. Call me a pessimist, but... by niktemadur · · Score: 1

    ...I believe there's a good chance that other corporations are monitoring this case very carefully, then will dispatch fleets of lobbyists in Washington to push legislation to repeal the Magnuson-Moss Warranty Act, with Harry Reid more than willing to comply. It cannot be understated that both major political parties in Congress have made it very clear, in the last ten years or so, that they are for the most part sympathetic towards Big Business.

    Think copyright laws and the virtual demise of public domain.
    Think file sharing. Think internet radio.

    --
    Lil' Thindime, lilting a lacrimose lament, krashes the kwaint konfines of Kokonino Kounty
  25. Software controlled radio by goombah99 · · Score: 2, Insightful

    You are plugging a radio device into a regulated liscenced network. You have a responsibility not to screw with the emissions of the device or misuse it. More than a responsibily--a legal obligation. But Apple also has a responsibility to try to prevent misuse of the device since it can't be expected that every user knows what they are doing and can weigh the ramifications of software installation. They need to make it reasonably safe but beyond that it's the end user that commits the crime.

    It's also remotely plausible software can ruin the device and even increase the risk of fire. So making it hard to mess with also makes sense from that perspective. This is much more of a minor concern than the former, as there are already many perfectly safe battery operated computers. The reason it matters here at all is simply the numbers game. Unlike most moddable handhelds, theres millions of these things and they are very likely to be operated on airplanes and public transportation. Some prudence is required.

    But beyond apples need to due dilligence above they also have the desire to make the thing have some value to the carriers and to the music sellers. Thus locking them helps the carriers. If there's a kickback for sales then it lessens the initial purchase cost to the consumers too. And it makes a market for DRMd music. (people who whine about fairlplay can't be pleased--it's a freakin fair-use speedbump folks, not a lock in. At least for the music. Video is a different story.). People may not like DRM but the mass consumer likes having a marketplace so they want to make that possible. To do that they need to enhance the sales value to attract the sellers. Personally I'm pretty happy with the line apple walks between buyers and sellers interests on audio sales. You can disagree with me on the DRM, but please see the point that apple has its reasons for needing to keep the device secure given its middleman position in the market.

    Finally, my guess is that like their video DRM (as opposed to audio) they are not trying to win the cat and mouse game here but simply perpetuate it at a level where the rodent population is tolerable. hardcore folks will play update games. Everyone else will not.

    So sure there may be sim card laws that say they can't prevent that. But they can prevent people from unlocking many of the other parts of the phone which may amount to the same thing, indirectly.

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:Software controlled radio by aaarrrgggh · · Score: 1

      Beyond the immediate iPhone issues, the Video DRM is actually more emblematic of my complaint with how Apple is dealing with this. The iPod and consequently iTMS would have never caught hold if it wasn't for the whole "rip, mix, burn" campaign-- the fact that it was possible and legal, and not the marketing. The same is required for the success of video sales long-term-- things need to be opened up sufficiently to allow unintended uses that expand the market.

      When taking this argument to the iPhone, people must realize that there are unintended uses of the iPhone that both drive sales and improve customer satisfaction. You can buy an iPhone in Bangkok today. There are over 100 stores with them in stock by my estimates. The stores are charging a healthy premium above cost in the US, and they are selling fairly well. Apple is not likely to ever sell iPhones directly in Thailand. The same story is true the world over.

      What incentive does a company have for restricting their products from a market at a cost comparable or higher than their target markets?

      There is also a specific subset of people that buy Apple's products whose needs are different than everybody else. If you travel abroad, leave the iPhone at home! Why the hell would I buy a quad-band world phone if I can't use it to at least make calls-- ideally take advantage of some of the functions with a controlled cost?

      I've been an Apple fan, consumer, and stockholder for a long time, and I have to say that they are moving in a direction that is not conducive for me to remain any of the three.

    2. Re:Software controlled radio by Anonymous Coward · · Score: 0

      I wouldn't contest the legal responsibilities you put forth. I would point out, however, that these same responsibilities encumber ALL cell phone manufacturers, yet many of them offer unlocked wireless devices that (I gather) are fully compliant with the law. This indicates that other manufacturers are capable of selling unlocked, programmable devices without skirting the responsibilities you correctly point out.

      I suspect that Apple's interest is more monetary here, and/or limited by agreements with AT&T, than anything else.

  26. Seems that TiVo might be a guide here by Overzeetop · · Score: 2, Interesting

    You can hack your Tivo, and there has been some (backhanded) help from Tivo insiders to do so. You can make it do all sorts of wonderful things that Tivo did not intend, or were to litigation averse to embed in the system. Thing is, when Tivo updates the boxes you lose all your hacks. The community realized this and created a workaround that prevented automatic updates. Then they get the new software update, sifted through it, and either provided new hacks or a customized update to work with existing hacks.

    I don't own an iPhone - I have a cingy 8525. I have flashed it to a not-quite-released WM6 firmware. If I want the latest and greatest approved stuff from AT&T, I need to load their software (though it does not appear to affect my unlock status...but it could). If I don't want the updated goodness, I don't update. My DTivo is about 3-4 minor updates behind, and before the last update I was a major upgrade behind. I'm not willing to lose my TiVo hacks for a couple bells and whistles (proper DST...which could be an issue coming up here...and folders).

    If the firmware upgrades are "forced", those with hacked phones need to either code a workaround to avoid the updates or just suck it up.

    --
    Is it just my observation, or are there way too many stupid people in the world?
  27. Disagreement from Slashdot's Unofficial Law Dude by Anonymous Coward · · Score: 5, Informative

    The author is no doubt referring to 15 USC 2302(c): "No [company] may condition [a] ... warranty ... on the consumer's using ... an[] article or service ... which is identified by brand ... or corporate name; except ... if the [company can show] that the warranted product will function properly only if the ... service ... is used in connection with the warranted product."

    What this literally means is that Apple's warranty cannot say "This warranty is void if you use the iPhone with a company other than AT&T." However, Apple's warranty doesn't say that. It says that the warranty is void if you mess with the firmware. It HAPPENS TO BE that the only way to make it POSSIBLE to use another company's service requires doing something else that will void your warranty, but the warranty terms themselves aren't anti-competitive, the firmware is.

    Even if the terms of the warranty did say this, Apple is probably still safe because it wouldn't be hard to argue that the iPhone isn't "function[ing] properly" if Visual Voicemail is broken.

    Any case brought under this law would be without merit and would probably be dismissed for failure to state a claim.

  28. Why this _is_ wrong... by msauve · · Score: 5, Informative
    In the US, a warrantor can say the whole warranty is nullified for just about anything they can define. The only thing they need to do is state so in plain terms. Read the Magnuson-Moss Warranty Act, if you want to know.

    Most of the "they can't do X" crap, stems from a misinterpretation of one specific part of the act:

    No warrantor of a consumer product may condition his written or implied warranty of such product on the consumer's using, in connection with such product, any article or service (other than article or service provided without charge under the terms of the warranty) which is identified by brand, trade, or corporate name; except that the prohibition of this subsection may be waived by the Commission if -
    (1) the warrantor satisfies the Commission that the warranted product will function properly only if the article or service so identified is used in connection with the warranted product, and (2) the Commission finds that such a waiver is in the public interest.

    The clause is to prevent, say, a vacuum cleaner company from requiring used of their own brand of bags (unless they provide them free). It doesn't mean you can modify your car for more horsepower, and expect the manufacturer to cover the engine under warranty when it breaks. It also doesn't mean a manufacturer can't put a clause in the warranty which says the car's warranty is voided if you hang fuzzy dice from the mirror. It means that they can't put a clause which says "Use of any brand fuzzy dice other than ACME brand fuzzy dice will void the engine warranty."

    Specific to the case at hand, since Apple provides firmware "without charge" during the warranty period, Magnuson-Moss does not require that they allow third party or modified firmware to be used under the warranty terms, and Apple is within the law if they require that only their firmware be used to maintain a valid warranty.
    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  29. The new iPhone has DTT!!! by Futurepower(R) · · Score: 1

    Because the iPhone is cool. The new iPhone is much cooler because it has DTT*.

    *Digital Turnip Twaddling (I'm quoting what I think you will agree, or not, is an authoritative technical authority. Opus threw his obsolete iPhone in the trash.)
  30. I'm thinking it's Apple FUD by dpbsmith · · Score: 2, Insightful

    ...like the printer instruction books that warn you that third-party ink cartridges may damage your machine.

    It could even be just what Apple says: they've found that there really is an innocent, unintended incompatibility between their updates and the hack. Certainly, there are perennial conflicts between Apple OS updates and software tweaks like Unsanity's "Haxies," and I don't think Apple is doing it deliberately.

    I think Apple is using scare tactics, both to keep AT&T happy and to keep them out of the nightmare scenario of being forced to provide support for hacked iPhones.

    I could be wrong, of course, but I'm curious to wait and see whether iPhones actually do get bricked... and whether a smoking-gun memo will emerge--"The job's not complete 'till unlocked phones are dead meat"

  31. Simple question.. by scubamage · · Score: 2, Insightful

    Ok, if you buy a brand new car with a warranty, and you then perform a bunch of aftermarket mods to it, including modifying the computer, should the manufacturer support it? No. You performed modification to a device which is meant to function in a specific way. You assume whenever you hack something you're voiding your warranty. There are books entitled, "How to have fun while voiding your warranty" about hardware hacks. You're just pissed because you bought a 500$ device, and now you face bricking it because you rushed out of the gate to mod it. You have implemented things from a 3rd party, not apple. Why should apple support things that aren't theirs? It is no longer the device they sold you. Turn to the 3rd party hack vendors to update. Seriously, you can't have the best of both worlds. Get the hell over it. The most important thing is that apple informed you. Imagine if they released the update and said nothing? At least now you can continue using your iphone as is. So really, you haven't lost anything.

    1. Re:Simple question.. by compro01 · · Score: 1

      bullshit. if you install an aftermarket turbo on the car, the warranty on the engine is almost definitely void (which is fine), but if the stock sound system stops working later, the warranty on that is still good, as it had nothing at all to do with the modification.

      anyone who is telling differently is full of shit (most dealerships are like this).

      of course, you'll likely have to go through the 8 circles of court to get them to follow the law.

      --
      upon the advice of my lawyer, i have no sig at this time
    2. Re:Simple question.. by BrianRoach · · Score: 1

      It goes farther than that.

      You can put the turbo on the car, and they *still* have to honor the warranty on the engine unless they can prove that the turbo (or the installation of) was the direct cause of the failure you are trying to get repaired.

      Now ... if you have a blown head gasket? Yeah ... you're pretty much on your own. :D

      - Roach

  32. not by scolbert · · Score: 1
    Apple is not violating this law. Often people read the article about the law and not the law itself. Apple is not bound to provide warranty coverage on an altered product any more than one would expect a car manufacturer to warranty a car engine if it were altered under its warranty period. This is much to do about nothing, no one will succesfully press this to the point of suit because any reasonable lawyer knows Apple will prevail. Moreover, and perhaps more importantly, any fool that "bricks" his iPhone through modifications and then doesn't restore the "factory" firmware before service/etc. deserves what they get.

    -
    Sammy
    iPhone

    1. Re:not by compro01 · · Score: 1

      Apple is not bound to provide warranty coverage on an altered product any more than one would expect a car manufacturer to warranty a car engine if it were altered under its warranty period.

      1. they are not required to support it, but they are not legally allowed to deliberately destroy the phone (through the deliberately part would be tricky to prove).

      2. sure, but if you install an aftermarket sound system, but didn't touch the engine, the engine warranty wouldn't be legally voidable.

      --
      upon the advice of my lawyer, i have no sig at this time
    2. Re:not by Anonymous Coward · · Score: 0

      Umm did you say any reasonable lawyer? Where do we find this reasonable lawyer? I'm sure their can't be more than 1.

  33. What's the Fuss? by Anonymous Coward · · Score: 0

    Nothing ever goes wrong with Apple products, right? So what do you need a warranty for?

    1. Re:What's the Fuss? by Anonymous Coward · · Score: 0

      "Nothing ever goes wrong with Apple products, right? So what do you need a warranty for?"

      NOBODY knows anybody who actually believes such nonsense and neither do you.

  34. Licence Terms by Anonymous Coward · · Score: 0

    Peoples approach to thinking that they actually 'own' an iPhone is wrongheaded. You technically 'own' the nice shiny plastic/metal case, but that's about it. The firmware is licenced to you. You have a licence to use the firmware , for a particular purpose (make and receive calls, use features, etc).

    You are NOT licenced to reverse engineer/dissassemble it etc.

    Don't like Apple's terms, too bad, should have read the licence agreement.

    Enjoy your pricy brick. Apple is not obliged to do anything to fix it.

  35. iCRAPPLE by BSDetector · · Score: 0

    iCRAPPLE

  36. Antitrust law 101 by nbauman · · Score: 1

    Duh. Would you like to pay monopoly prices, which are twice as much or more?

    In the wild west of free-market capitalism, a few companies dominate most big industries, the way Carlos Slim took over the Mexican phone industry.

    In the U.S., this got so bad that we passed antitrust laws to prevent businesses from doing this. IBM used to sell computers, and make you buy the punch cards from them. Those were the most expensive punch cards ever sold. If you bought a Chevrolet, you had to buy GM parts at twice the price.

    So because of these abuses, we passed antitrust laws. You can love or hate the free market, but it works a lot better (for everyone except Carlos Slim) with more competition.

  37. Find the bias by stewbacca · · Score: 0, Flamebait
    The bias is always found right in the slashdot contributor's "summary" of the article, and this article is no exception:

    And, also, is Apple designing future software updates to do damage to iPhone when said SIM Unlock code is present?'"
    Yeah, slightly cynical. And of course Apple PR has already spun (if you must maintain your bias) the fact that will not proactively make iPhones not work. HOWEVER, given the tight integration of the phone with iTunes, any reasonable customer would expect ANY deviation from that successful model to cause problems with the phone's functionality.

    Consumers who want to jack up their iPhones by HACKING it, don't deserve consumer rights. As far as unlocking the sim card...caveat emptor. You should have known before you bought the phone that you get AT&T and that's it.

    1. Re:Find the bias by stewbacca · · Score: 1

      -1 for moderation? This is the ONLY post I've made in this thread that I actually DID moderate. Can someone make me a better slashdotter and point out why my post lacks moderation?

    2. Re:Find the bias by Slashcrap · · Score: 1

      -1 for moderation? This is the ONLY post I've made in this thread that I actually DID moderate. Can someone make me a better slashdotter and point out why my post lacks moderation?

      You seem a little confused about how Slashdot works. You didn't moderate your post - someone else did.

      As for the reasons why they moderated your post, I can only guess at their motives but I would advance the following theories :

      a) They noticed that you had posted 22 comments to this story alone and decided you needed to shut the fuck up.
      b) No seriously, shut the fuck up.

      And to answer your second question, you can become a better Slashdotter by shutting the fuck up.

    3. Re:Find the bias by stewbacca · · Score: 1

      Now THAT is the type of post that I would expect to get a -1. Thanks for the clarification.

    4. Re:Find the bias by LKM · · Score: 1

      Dude, if you write stuff like "Consumers who want to jack up their iPhones by HACKING it, don't deserve consumer rights", you should not be surprised that you get modded down. I don't even think you understand what "hacking" means.

    5. Re:Find the bias by stewbacca · · Score: 1

      Modded down for MODERATION, however? How does my point that people who screw up their consumer device should not expect to get services such as warranty work for the things they screwed up? Note, I didn't say anything about skilled hacking, which, you know, doesn't actually screw up your phone.

    6. Re:Find the bias by LKM · · Score: 1

      Ah, I get it :-)

      You did not get modded down for "moderation." What you probably saw was "Moderation -1." This means that somebody applied a moderation of -1 to your post, not that your post got modded down for moderation! The reason it got modded down is below the "Moderation -1" part: "100% Flamebait". So somebody thought your post was flamebait.

  38. Re:Why this _is_ wrong... by suv4x4 · · Score: 1

    It means that they can't put a clause which says "Use of any brand fuzzy dice other than ACME brand fuzzy dice will void the engine warranty."

    Funny how this doesn't apply to ink printer cartridges, doesn't it.

    I interpret the law a bit differently, since the law says it's not illegal to unlock a phone, but this doesn't mean it's illegal to void warranty on unlocked phones.

    You won't end up in jail, but you'll have no warranty..

  39. quick question by stewbacca · · Score: 1

    What does getting "bricked" mean? I've seen it mentioned several times on this thread. Thanks.

    1. Re:quick question by dpbsmith · · Score: 1

      To be transformed in such a way as to have the same computing functionality as a brick.

      To become completely disabled. Gronked. Smoked. Kaput. Dead. Discombobulated. Gone kerplooie.

    2. Re:quick question by compro01 · · Score: 1

      rendering the phone unbootable or equivalent with no way to make it bootable again.

      --
      upon the advice of my lawyer, i have no sig at this time
  40. Re:Why this _is_ wrong... by XenoPhage · · Score: 3, Insightful

    I read through some of the information on this Magnuson-Moss Warranty Act and it seems that the purpose here was to ensure that manufacturers provided the consumer with a document that is both easy to understand, and not ambiguous. However, it does not put any stipulation on that manufacturer to prevent them from invalidating the warranty if you don't use the device correctly.

    However, this act falls a little short in the realm of electronics and firmware. Sure, Apple can't go around saying that your warranty will be void if you use a Motorolla bluetooth headset instead of an Apple one. But, can they say that the warranty is void if you use a different firmware? It seems to me that there's a gray area there. Firmware is required to make the device work, but it's provided by the manufacturer. So, can the manufacturer prevent you from using someone else's firmware by invalidating the warranty?

    I suppose the underlying question is, what does the warranty cover? If it's merely electronics, then perhaps the manufacturer cannot dictate the firmware used, but, in the event of a failure, they can surely attempt to load the device with "official" firmware in an effort to determine the problem. Of course, if the unit is completely dead, that won't help. In that instance, the question becomes more of a "what caused the failure" type of question.

    That's where 3rd party firmware can become a problem. How do you prove that the firmware was the cause and not the hardware? I'm sure it can be done, but to the satisfaction of the customer? And is it really Apple's responsibility to determine if the firmware was the cause? In the end, it may cost Apple quite a lot of money to make that determination, only to turn back to the customer and refuse the warranty claim. It's sort of a lose-lose situation.

    --
    XenoPhage
    Technological Musings
  41. Re:Why this _is_ wrong... by homer_ca · · Score: 2, Insightful

    Let's use your fuzzy dice example. What happens if an unlocked iPhone has a completely unrelated hardware failure, like the touchscreen or button? Apple would say the warranty is void, but the way I understand it, you can't void a warranty unless an unauthorized modification directly contributed to the failure.

  42. Re:Why this _is_ wrong... by Anonymous Coward · · Score: 0

    http://images.apple.com/legal/warranty/iphone.pdf

    Exclusions, paragraph 3, section e.

    "This warranty does not apply: ... (e) to a product or part that has been modified to alter functionality or capability without the written permission of Apple;"

    That seems fairly clear that modifying the firmware to alter the capability to use other networks/sims voids the warranty.

  43. The iPhone SIM unlock is mainstream? I doubt it. by whjwhj · · Score: 1

    > Is the SIM Unlock process that has become mainstream doing damage to iPhone?

    Mainstream? I really wonder what percentage of iPhone owners have messed with SIM unlock crap. I bet it's some fraction of 1 percent. Mainstream? I seriously doubt it.

  44. Re:Why this _is_ wrong... by james_pb · · Score: 1

    Seems like that "one specific part of the act" you're talking about clearly states that they'd have to apply to the "Commission" to get a waiver, and the commission would have to find that "such a waiver is in the public interest." Any evidence that Apple has gone through that process? Until that happens, sounds like Apple is SOL.

  45. Re: And if knew what Magnuson-Moss is .... by BrianRoach · · Score: 1

    Apple is not bound to provide warranty coverage on an altered product any more than one would expect a car manufacturer to warranty a car engine if it were altered under its warranty period

    Pssst. You might want to read Magnuson-Moss. Because that's exactly what it talks about.

    They DO have to honor the warranty, unless the modification leads directly to the failure in question and can be proved as such.

    This is why a car manufacturer can not void a warranty because you put after-market parts on/in your car (and some car/motorcycle dealers will STILL try and tell you that they can void the warranty if you do).

    For example ... you can put an after-market exhaust or air intake on your car, and they can't not honor your warranty when you take the car in for an oil leak.

    - Roach

  46. Its just not that simple by Orig_Club_Soda · · Score: 1

    Its more complex than simply unlocking the phone, you are hacking its OS. In some cases changing the hardware. How can a company warranty a product that is used in ways unintended, beyond it's off the shelf capabilities?

    I find this whole controversy strange. It seems like the people who hate Apple are complaining that they cant use the iPhone... While the people who love Apple are content to use the iPhone with AT&T.

  47. It depends on the 3rd party stuff by mveloso · · Score: 1

    If you re-chip your car, you probably void your warranty across the board - for obvious reasons.

    That's the car equivalent of reflashing your iPhone firmware.

    Does it do anything bad? Well, probably not, but you never now. For car firmware, there may be a corner case that the chippers didn't think about...like pulling a controlled skid at 85 mph (oops).

    Not sure what the equivalent would be for iPhone firmware, accidentally boosting the transmit power so it fries the users' brain?

    1. Re:It depends on the 3rd party stuff by steveo777 · · Score: 1
      I realize I wasn't being too clear about my comparison.

      Adding third party apps should be like adding seat covers or a 'foofy' steering wheel cover. It shouldn't really mess with the inner workings of the iPhone, and should be easy to get rid of them when you need to do so. Even perhaps with OS hacks, they shouldn't hurt the hardware at all. You might have to re-flash the main memory to fix a major problem, but that's it. It's quite obvious it can be done, because Apple is releasing a firmware update as it is.

      If hacking the software really did actually harm the iPhone, like fry out the antenna or release some general magic smoke, then, yes, I would see it voiding warranties left and right. Perhaps Apple could offer it's (paid for by user) services of re-installing the OS for those whose phones become bricked. Or let us do it with iTunes.

      Hopefully my analogy is more clear?

      --
      This sig isn't original enough, it's time to come up with something witty...
    2. Re:It depends on the 3rd party stuff by gnasher719 · · Score: 1

      Adding third party apps should be like adding seat covers or a 'foofy' steering wheel cover. It shouldn't really mess with the inner workings of the iPhone, and should be easy to get rid of them when you need to do so. Even perhaps with OS hacks, they shouldn't hurt the hardware at all. You might have to re-flash the main memory to fix a major problem, but that's it. It's quite obvious it can be done, because Apple is releasing a firmware update as it is. Problem is, we are talking about a firmware update. The firmware is among other things responsible for installing firmware updates. If you manage to damage the part of the firmware that installs firmware updates, you're out of luck. Some people have posted here that unlocking an iPhone doesn't damage it. Now consider this possibility: If a firmware change has correctly unlocked the iPhone, but has also damaged the part of the firmware that does firmware updates, to a point where it works incorrectly, then your unlocked iPhone will work absolutely fine until you try any other firmware update for whatever reason. And there have been reports from people trying to re-lock the iPhone saying that either the re-lock didn't work, or bricked the iPhone. That could be explained by the firmware updating firmware being either completely hosed (doesn't work anymore, but can't cause damage either) or being slightly hosed (bricks the iPhone).
    3. Re:It depends on the 3rd party stuff by steveo777 · · Score: 1

      Thanks for the explanation. Was never too sure how that worked. So, basically, the instructions to change the firmware are in the firmware? Could the firmware somehow be backed up and forced back onto the main memory? Or is that wishful thinking?

      --
      This sig isn't original enough, it's time to come up with something witty...
  48. Magnuson-Moss knew Apples go bad by Anonymous Coward · · Score: 0

    The Magnuson-Moss Warranty Act states that Apple cannot void a warranty for a product with third-party enhancements or modifications to their product.

    It actually *states* all that? Damn! Pretty good for a decades old law; not sure why they decided to make it apply only to Apple though.

  49. No airbag or ABS controls run through the radio by name_already_taken · · Score: 1

    No GM vehicle has any mechanisms that have to do with the functioning of the airbags or ABS integrated into the radio. They are not stupid enough to expose themselves to liability like this by integrating a safety-critical system (such as airbags or ABS function) into a part of the car that is often replaced by the owner, like the radio.

    What they did integrate into the radio were things like all the audio chimes for things like Onstar, lights-on/door open/key-in, low brake fluid (yes, there's a warning chime for that now), seatbelt warning, memory seat function (ok this one makes no sense for it to be integrated into the radio, I'll admit), parking brake warning, and in some cases the steering wheel controls for the heater and air conditioning.

    There are, however, several aftermarket interface modules that allow you to install an aftermarket audio system while keeping all of the factory functions (except perhaps the steering wheel audio controls which would depend on your aftermarket stereo supporting those).

    --
    Putting moderation advice in your .sig lowers your karma!
    1. Re:No airbag or ABS controls run through the radio by Politburo · · Score: 1

      low brake fluid (yes, there's a warning chime for that now)

      I've always wondered why there is rarely a light/sensor for this. Yes, it's extremely rare to have a brake fluid problem, but if you do, you really want to know about it ASAP (usually you find out when the brake pedal slams to the floor). I always found it odd that car makers would put in silly lights like "Low washer fluid" but not have any indicators for oil, brake fluid, coolant level (not temp.), etc.. then again I suppose it's to their advantage. A $5 light vs. the cost of repairs...

    2. Re:No airbag or ABS controls run through the radio by Anonymous Coward · · Score: 0

      The brake light in a car is a dual purpose light, it indicates when the fluid is low AND when the parking brake is on. A lot of cars have a low coolant light, since the level changes with operating conditions, the actual level indicator would not be very useful. Oil pressure and a low oil light is more then adequate, some cars do not have a pressure gauge but will integrate that into the light.

      Oil is "burned" and can leak and still that is considered normal and acceptable. It is not normal to ever be low on brake fluid or coolant, if so, you need to investigate before just filling them back up. Another useless tip, if you know your brake fluid is not leaking (which it should not be), if you are lower then normal, you probably need to replace your brake pads. Sounds odd right? Well as the calipers (disk brakes) and the wheel cylinder (drum brakes) move out to compensate for the warn pads, fluid is displaced into them and causes the level to go down. If you fill up your brake reservoir to the max fill line when you have four worn out brakes, the fluid will overflow after you change out the brakes.

  50. because it ISN'T a waste of money by Jafafa+Hots · · Score: 1
    "My feeling is why waste that time and moeny? THey will build a patch that will work with a non hacked iPhone 100%. They won't spend a single dime testing it on a hacked one (why should they the ROI on that is a negative)." They may not have tested it, but they may well have, because if there are thousands of hacked phones out there that are going to self-destruct after the next update, then Apple will have to deal with support phone calls, people trying to return them to Apple stores, bad press, etc. All of which will cost money.

    When you are designing and testing a product, you don't only test for how you WANT the product to be used, you test for how people are likely to use it in ways you DON'T want.

    --
    This space available.
    1. Re:because it ISN'T a waste of money by Zeinfeld · · Score: 2, Insightful
      When you are designing and testing a product, you don't only test for how you WANT the product to be used, you test for how people are likely to use it in ways you DON'T want.

      The original post raises a number of questions, not least how the author managed to type in so much text and still be first post. Perhaps he is a subscriber.

      There are many interesting questions here, not least being whether Apple does have an interest in locking the phone, it is AT&T that bears the loss. Only Apple is getting paid some form of bounty for each phone from AT&T in return for the exclusive status. This looks and smells to me like a subsidy and I will bet it would to a UK judge as well.

      If this was Microsoft we were talking about there would be nobody defending the lock in strategy. OK, almost nobody since there are always some trolls.

      Europe has decided as a matter of public policy that customers have the right to use their phone on any carrier they choose. Apple's marketing plans are irrelevant to them. If Steve Jobs does not want to play according to the rules they set there will be no iPhones in Europe as in none, zip, zero, nada, nyett, non-parle-iPhone.

      Europe has come to a similar decision about DVD players, you can readily obtain unlocked DVD players in every part of Europe. The EU decided that the movie studios were using the zone system to enforce differential pricing. The RSS consortium has decided to ignore the fact that the manufacturers offering unlocked players are technically in breach of their agreement. They know that they would quite likely lose their patent rights entirely and suffer significant fines if they were to attempt to do so.

      Public policy trumps Steve Jobs and any exclusive contracts he might sign. It is as simple as that. Wearing a black turtleneck does not provide immunity from the EU anti-trust laws.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    2. Re:because it ISN'T a waste of money by apoc.famine · · Score: 1

      The original post raises a number of questions, not least how the author managed to type in so much text and still be first post. Perhaps he is a subscriber.


      I was wondering about that too. I sent an email to Cmdrtaco and asked him to put an asterisk or something next to their names so we can figure out who subscribes. He seemed to like the idea.
      --
      Velociraptor = Distiraptor / Timeraptor
    3. Re:because it ISN'T a waste of money by arminw · · Score: 1

      ...you test for how people are likely to use it in ways you DON'T want......

      So then a manufacturer of lawnmowers will test how well they work as hedge clippers? Someone making a device for ironing clothes will check to see how well it works as a bed warmer? The iPhone was made as a phone, to work only with AT&T's network. Anybody who misuses it for some other company's network takes the risk for whatever happens to them and the phone upon themselves. If the house burns down because some jerk misapplies an iron as a bed-warmer, is that the manufacturers fault? No manufacturer of anything can possibly anticipate the sum total stupidity of humanity. Whatever happened to that old-fashioned idea of people being responsible for their own actions?

      --
      All theory is gray
    4. Re:because it ISN'T a waste of money by Kalriath · · Score: 1

      The asterisk can be removed by the poster, by checking "No Subscriber Bonus" (which I do), in order to prevent people applying negative modifiers to subscribers.

      It should of course be noted that even subscribers don't have a reply button (to create a post) until it goes from red to whatever-colour-the-subsite-uses.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    5. Re:because it ISN'T a waste of money by Jafafa+Hots · · Score: 1
      First of all, your analogy is piss-poor. Using a lawnmower as a hedgetrimmer would be aking, to... I dunno, using your iphone as... a hedgetrimmer.

      People are trying to use their iPhone as a PHONE. A more apt analogy would be that people have bought an iMower, which is a standard mower in a cool design that has had an additional additional mechanism added to make it only mow one lawn... they're trying to mow other lawns with it. Not an unreasonable thing. In saying mower/hedgetrimmer, or iron/bed warmer, you are being deliberately obtuse.

      That having been said, even if you DO consider that unreasonable, you miss the point entirely. Its not about responsibility, it's about seeing what could be a problem for your business, regardless of who is responsible, and designing to negate that problem. Its about efficiency. I worked for a major manufacturer and we tested for every reasonably conceivable misuse of the product, if at least to be able to answer calls about it or put warning stickers on.

      --
      This space available.
    6. Re:because it ISN'T a waste of money by arminw · · Score: 1

      .....Using a lawnmower as a hedgetrimmer .......

      Well, I used that analogy because it actually happened and the @%$#$% jerk even tried to sue the manufacturer after he got his teeth knocked out! Hot coffee at McDonalds?

      The iPhone was designed to be used in a certain way, with a certain network. The lawnmower was designed for a certain type of fuel or electricity to mow lawns. The phone and the network were meant to go together. Apple always deals with the whole SYSTEM, not just bits and pieces, like the rest of the computer makers. They do this for Macs, the iPod-iTunes system and now the iPhone and the AT&T network system. That's why their stuff "just works", at least most of the time.

      If you, with the help of some hacker figure out how to use the iPhone on some other network, fine, more power to you. Just don't blame the manufacturer if something goes wrong. The hackers should include a means to RESTORE the phone to what it was when you walked out of the store with it. Then before you apply an update from Apple, you restore the phone, apply the update and then re-apply the hack, if it still works. If not ask your hacker friend for an update to the hack, especially if you paid him money. If all that is worth it to you, for whatever reason, good for you. Apple would likely honor the warranty, if say the screen burned out, but not if the hack hosed the system to where it couldn't be restored to what it was at the factory. It's not too likely that a software hack would destroy the device, but it might cause extra work for Apple for which they would be justified charging you for.

      (.....it's about seeing what could be a problem for your business......)

      Exactly and that's why they're warning people that these hacks COULD brick their phone. Having a bunch of irate customers with dead phones would be a problem for their business. Maybe they should put a warning sticker on each iPhone.

      Apple will let you install Windows on their computers. They even supply the means for you to do it and won't void the warranty on a shiny new Mac. However, they are not obligated to support your Mac after that. If you brought it to them, they might install OSX thereon (if it wasn't on there still) and determine that the Mac works just fine. If so, you probably would end up paying some money to them for their trouble. I have Windows XP on my Macbook-pro. The built in camera works only on OSX. Otherwise it seems to work quite well.

      --
      All theory is gray
  51. Re:Why this _is_ wrong... by Anonymous Coward · · Score: 0

    The clause is to prevent, say, a vacuum cleaner company from requiring used of their own brand of bags (unless they provide them free). Or, say, to prevent an stylish electronics company who sells music online from requiring the use of their own brand of digital audio player. Wait...
  52. Perhaps you can't read... by msauve · · Score: 1

    ..."other than article or service provided without charge under the terms of the warranty."

    As stated (perhaps you didn't read this either: "Apple provides firmware "without charge" during the warranty period."

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  53. Re:Why this _is_ wrong... by Fulcrum+of+Evil · · Score: 1

    IANAL, but I'm pretty sure that the M-M act trumps this. Apple has to prove that the mod contributed to the failure.

    --
    "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  54. Re:Why this _is_ wrong... by TheGreatGraySkwid · · Score: 1

    The clause is to prevent, say, a vacuum cleaner company from requiring used of their own brand of bags (unless they provide them free). It doesn't mean you can modify your car for more horsepower, and expect the manufacturer to cover the engine under warranty when it breaks.

    This is...mostly correct, but somewhat incomplete. If you install some aftermarket part in your vehicle, and there is evidence that the installation of that part resulted in the vehicle damage that you are seeking to repair under warranty, then the manufacturer is within their rights to refuse warranty service. However, if you install a cold air intake, and then you suffer from a failure in the suspension or electrical system, there would be no grounds for refusal of warranty service because your modification could not reasonably shown to be at fault.

    How far this analogy extends to the iPhone clearly depends on the extent and nature of the modifications being performed, IMO.

    (IANAL, but this is the collective wisdom of the auto-modding community as I have received it)
    --
    The Humblest Mollusk on the Net
  55. Your understanding is incorrect... by msauve · · Score: 1

    find anything in the Act which says anything similar to your "understanding." Pointing to some web site which has some incorrect, self-serving interpretation (there are lots of 'em) doesn't count. Like I said, a manufacturer can, as long as it is clearly spelled out in the warranty terms, void the entire warranty on a car if you hang fuzzy dice from the mirror. It is the market, not the law, which serves to prevent them from doing so in actual practice.

    It all depends upon exactly what Apple says in the warranty terms. If they say "this warranty is void if any unauthorized modifications are made to the product," then that is the case. It makes no difference if a problem was caused by the modification, or not.

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
    1. Re:Your understanding is incorrect... by homer_ca · · Score: 1

      I wouldn't exactly call the FTC website a self-serving interpretation. However, the reason they give for new car warranties doesn't apply to electronics. There's a prohibition on sales tie-ins as a condition of warranty service. Cars need routine maintenance and spare parts. A car maker can't require a customer to purchase original OEM parts or maintenance from a dealer as a condition of warranty service because that would be an illegal sales tie-in.

      Electronics (especially from Apple) are sealed and maintenance-free for the life of the product. The battery does wear out, but usually not before 3 years. The only way this might apply is if non-Apple accessories like cases or headphones void the warranty.

    2. Re:Your understanding is incorrect... by Marful · · Score: 1

      find anything in the Act which says anything similar to your "understanding." Pointing to some web site which has some incorrect, self-serving interpretation (there are lots of 'em) doesn't count. Like I said, a manufacturer can, as long as it is clearly spelled out in the warranty terms, void the entire warranty on a car if you hang fuzzy dice from the mirror. It is the market, not the law, which serves to prevent them from doing so in actual practice.

      It all depends upon exactly what Apple says in the warranty terms. If they say "this warranty is void if any unauthorized modifications are made to the product," then that is the case. It makes no difference if a problem was caused by the modification, or not. How about the actual Magnasun-Moss Warranty Act itself? 15 U.S.C. 2302 Secton C (of The Magnuson-Moss Warranty Act) says:

      (c) Prohibition on conditions for written or implied warranty; waiver by Commission

      No warrantor of a consumer product may condition his written or implied warranty of such product on the consumer's using, in connection with such product, any article or service (other than article or service provided without charge under the terms of the warranty) which is identified by brand, trade, or corporate name; except that the prohibition of this subsection may be waived by the Commission if--

      (1) the warrantor satisfies the Commission that the warranted product will function properly only if the article or service so identified is used in connection with the warranted product, and
      (2) the Commission finds that such a waiver is in the public interest.

      The Commission shall identify in the Federal Register, and permit public comment on, all applications for waiver of the prohibition of this subsection, and shall publish in the Federal Register its disposition of any such application, including the reasons therefor.
  56. What is this "Apple" you speak of? by PPH · · Score: 1

    I seem to recall a company by this name. But they drove themselves out of business with silly hardware and service lock-in policies.

    --
    Have gnu, will travel.
    1. Re:What is this "Apple" you speak of? by Anonymous Coward · · Score: 0

      That's kind of funny.

      AAPL stock ticker, circa 1997: ~$5/share
      AAPL stock ticker, circa 2007: $150/share

      For being out of business, I sure wish I had some of their stock! Please, STFU, or at least have some idea of what you are talking about.

  57. Re:Why this _is_ wrong... by stewbacca · · Score: 1

    if you install a cold air intake, and then you suffer from a failure in the suspension or electrical system, there would be no grounds for refusal of warranty service because your modification could not reasonably shown to be at fault.
    Ok this is the third incorrect analysis of a car analogy in this thread so far. If you install a cold air intake filter and improve horsepower by as little as 5hp, you have altered the state of the vehicle as compared to when the chasis and suspension where engineered and tested. An increase in horsepower equals a faster car, which changes the dynamics of the chasis. If you break a suspension part in spirited driving, the car company could easily, and rightfully claim you changed the characteristics of the car, and the suspension is NOT guaranteed to work with your modifications. I can't find a way to tie cold air intake into electrical systems, but I'm sure some crafty corporate lawyers have.
  58. forget cars by commodoresloat · · Score: 1

    Great. Now we need juggling analogies to make things understandable.

    1. Re:forget cars by mstone · · Score: 1

      Well, I was going to use the "pendulum hanging from a pole that sits on the vertex of a teeter-totter" analogy, but the juggling seems, y'know.. more folsky.

  59. Re:Why this _is_ wrong... by stewbacca · · Score: 1

    Except that you are just GUESSING that Apple would say the warranty is void. I've had Apple honor warranties before EVEN after I voided the warranty in another area. Hell, I got a new motherboard on beige G3, even after I overclocked it and I removed the sticker covering the jumpers that said: "removing this voids your warranty". There was a flaw with the ethernet on my board, and Apple gave me a new motherboard (and bumped the CPU from 233 to 300 for me in the process. My 20+ years of Apple experience makes me feel safe that Apple general tries to do the right thing, as oppossed to what all the slashdot cynics suggest.

  60. You are wrong... by msauve · · Score: 1

    the Act says no such thing, and I challenge you to point out where it does. Not some self-serving website, cite from the M-M Warranty Act.

    Your's is one of the most common mistaken beliefs about the Act (propagated by deliberately misleading self-serving claims of aftermarket modification makers).

    It all depends on exactly what the warranty says. If it says "damage caused by unauthorized mods not covered," you're close to correct, but for the wrong reason. If it says "warranty void if any unauthorized mods are made," you're just plain wrong.

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  61. The argument is that cellphones are a special case by argent · · Score: 1

    Because cellphone *unlocking* is specifically allowed without violating the warranty, they are different from other consumer devices. IANAL, but I do think that if this argument holds then analogies with car computers aren't very useful.

    There is still a question in my mind as to whether this applies to some of the other modifications, like installing an SSH server or third-party GUI apps.

    The courts will have fun with this one.

  62. Fuck apple by Anonymous Coward · · Score: 0

    Screw the corporate Mofos over and dont buy their crap-ware. 600 bucks for a locked in expensive piece of hitech shit? Screw that!

  63. cars too by CraniumDesigns · · Score: 0

    this same kind of thing happened when i bought my 2006 scion tc. they wanted to sell me the crappy scion stock security system. i said i would be installing a viper system, and they said it would void my warranty. i ignored them and looked up the magnusen warranty act and went happily on my way. car's out of warranty now since it has 46k miles on it, but just nice to know i had a legal leg to stand on.

  64. Bricking vs Warranty by GStyle98 · · Score: 1

    Does anyone who unlocked their iPhone really give a hoot whether Apple will void the warranty or not? The car example was used above in relation to aftermarket parts and, as was mentioned, adding an aftermarket dvdplayer won't void the warranty on the whole car regardless of what the dealership might say. But even if it did void the warranty on the whole car, the car would not be bricked. It would function just fine (assuming you didn't screw up installation somehow... damn wires). Now lets say there's a recall on the car to upgrade the pistons or something because they aren't performing properly (ie, it's a bug).

    You now have 2 choices. One, don't go through with the recall and stick with stock pistons. Two, go with the recall and hope it doesn't make your car unusable. In theory, because you just installed a new radio, changing the pistons (firmware) doesn't brick the vehicle so, in theory, you're fine.

    Now lets look at the iPhone. If Apple wants to void a warranty on an unlocked phone that is legally unlocked due to exemptions in the DMCA... fine. The product will still work. I could take my unlocked phone to T-Mobile or over to Europe or somewhere else and be fine. I don't think that's the issue. The issue is bricking the phone, making it so the entire device ceases to function. No phone, no ipod, no contacts, no nada. Such an act is pretty uncool. Unfortunately I'm not savvy enough to know how the various iPhone unlocks work in relation to the rest of the code-base thus making any comment on how firmware upgrading would brick the entire device retarded, but if the iphone dev team unlockers can come up with an app that will 'restore' the iphone to it's original status then this may be a non-issue anyway.

    This will be interesting in 2 years when AT&T contracts are up, that's for sure. But by then we'll have very different iphones than what we have today :)

  65. Re:Why this _is_ wrong... by MobyDisk · · Score: 2, Insightful

    It doesn't mean you can modify your car for more horsepower, and expect the manufacturer to cover the engine under warranty when it breaks. The issue is that people are modifying the engine and the warranty says that Apple will is thus to support the seat belts. It's like the guy who installed Linux on his laptop and HP refused to fix the broken keyboard.
  66. FUD by MrCrassic · · Score: 2

    While many might be hoping that there would be some kind of barrier to prevent Apple from deploying such a limitation, it is everything but illegal to do so. The writer of the original article, while providing persuasive evidence that there might have been a warranty violation breach, does not analyze the full letter of that law nor does any sort of comparison with Apple's own legal warranty claims.

    If you take a look at the official Apple warranty for the iPhone, there are a couple of points in their exclusions that make clear that they are within legal bounds to do this:

    "...to damage caused by service (including upgrades and expansions) performed by anyone who is not a representative of Apple or an Apple Authorized Service Provider ("AASP")..."

    "(a) to damage caused by use with non-Apple products;..."

    "(e) to a product or part that has been modified to alter functionality or capability without the written permission of Apple"

    If these rules were illegal, they would have been contested before their publication, thus before the release of the device. Apple needs to have these rules in place so that they do not have to pay costs for repairing devices that were broken by people who bought phones to intentionally harm them by all sorts of means. The company made a deal with AT&T, and in that deal there was an implicit demand that the phones stay locked to only their service provider, hence making them an exclusive carrier. Altering this would alter the functionality of the phone against Apple's policy, thus proving a legal voiding of warranty.

    We can even take this a step further. Even if Apple had no EULA and only went by the letter of the Magnuson-Moss law, the clause in defense only applies for full warranties, for which Apple's product comes only with a limited warranty. This makes a significant difference, as those provisions no longer apply. This is clearly stated in the Wikipedia article linked to this article.

    While I do not defend this decision entirely, it is obvious that if you are a user of an unlocked iPhone, and the firmware update only serves to remedy this "flaw," then the solution is easily to avoid the upgrade. There are no new features or enhancements being introduced in this update, so why is this even a concern?

    1. Re:FUD by Anonymous Coward · · Score: 0

      The article responded to that... it specifically covered Magnuson-Moss's applications to Limited Warranties, and Apple's iPhone Limited Warranty in particular... read the article.

  67. Re:Why this _is_ wrong... by Anonymous Coward · · Score: 0

    Couldn't Apple's default setting locking it into AT&T be interpreted as a "buy only ACME fuzzy dice or else..." sort of situation? Since Apple's phones only will work as intended (as a phone) with that one carrier, it seems like at the very least a nasty Hobson's choice.

  68. Much Confusion... jailbreak, unshackle, not unlock by Anonymous Coward · · Score: 0

    so... unlocking is when you want someone other than AT&T with the iPhone, so you need to unlock it to get another company's sim in there... jailbreaking is hacking the iphone to put 3rd party software on the iphone, and doesn't necessarily mean that you've unlocked the iPhone... you could still have AT&T & the 2 year contract, and still want to jailbreak the iPhone to play Nintendo NES games. Unshackling is sort of like this, opens the phone for third party intalls, but doesn't require jailbreaking, unjailbreaking the thing.

    I feel I fit into the third category. I don't care about AT&T, they're not "THE EVIL" for me, I've been a customer forever (i.e. ~4 years). But my 2nd contract ended with them a few weeks ago, and I don't WANT another contract, as who the fuck knows what I'll be doing or wanting at any point in the next 2 years.

    this dude helped me get what I want

    So I paid Apple. I am still paying AT&T, though they don't know I am using an iPhone, but technically, I didn't "unlock" the phone. I just hacked it to work with my current AT&T SIM, and I am still contract free. Why should Apple CARE about someone like me enough to WARN me that they may break my phone, or not fix it under warranty?

    OK, I have to admit. I am EXTREMELY disappointed by Apple in all of this greedy-give-me-control-shit. "Control Freak" is a term that comes to mind, now... and I'd love to see Jobs on a crossfire type dillio trying to explain how its "better" this way for everyone.

    And I didn't even want an Apple made phone... I want a frickin' OS X slate, with inkwell in full functionality. Apple could develope and release such a product with their eyes closed. And make a decent profit. But it might hurt their precious iPhone sales... so... no product.

  69. Forgot one thing by homer_ca · · Score: 2, Informative
    There are exceptions to the rule on sales tie-ins. Described here

    Although tie-in sales provisions generally are not allowed, you can include such a provision in your warranty if you can demonstrate to the satisfaction of the FTC that your product will not work properly without a specified item or service. If you believe that this is the case, you should contact the warranty staff of the FTC's Bureau of Consumer Protection for information on how to apply for a waiver of the tie-in sales prohibition.
  70. Re:Why this _is_ wrong... by Bazar · · Score: 1

    [quote]That's where 3rd party firmware can become a problem. How do you prove that the firmware was the cause and not the hardware? I'm sure it can be done, but to the satisfaction of the customer? And is it really Apple's responsibility to determine if the firmware was the cause? In the end, it may cost Apple quite a lot of money to make that determination, only to turn back to the customer and refuse the warranty claim. It's sort of a lose-lose situation.[/quote]

    I'm pretty sure that if your phone turns into a brick when you update it using itunes, it was the hacked firmware.
    If your thinking of lying to apple/at&t/whatever when you return the phone, they can simply ask how it turned into a brick, and of course, they'll then ask if you hacked it. You could lie through your teeth, but its clear at this point who's being unethical.

    In the case of firmware causing damage on an arbitrary point in time, i would expect for that warranty act to enacted, the burden of proving beyond reasonable doubt that your firmware didn't cause the breakdown would rest on you.

    But IANAL, so i could be wrong, just seems like common sense to prove your mods didn't cause harm at their expense.

    --
    To avoid criticism; Say nothing, Do nothing, Be nothing.
  71. jailbreak, not unlock, using AT&T w/o contract by catmistake · · Score: 1

    so... unlocking is when you want someone other than AT&T with the iPhone, so you need to unlock it to get another company's sim in there... jailbreaking is hacking the iphone to put 3rd party software on the iphone, and doesn't necessarily mean that you've unlocked the iPhone... you could still have AT&T & the 2 year contract, and still want to jailbreak the iPhone to play Nintendo NES games. Unshackling is sort of like this, opens the phone for third party intalls, but doesn't require jailbreaking, unjailbreaking the thing.

    I feel I fit into the third category. I don't care about AT&T, they're not "THE EVIL" for me, I've been a customer forever (i.e. ~4 years). But my 2nd contract ended with them a few weeks ago, and I don't WANT another contract, as who the fuck knows what I'll be doing or wanting at any point in the next 2 years.

    this dude helped me get what I want

    So I paid Apple. I am still paying AT&T, though they don't know I am using an iPhone, but technically, I didn't "unlock" the phone. I just hacked it to work with my current AT&T SIM, and I am still contract free. Why should Apple CARE about someone like me enough to WARN me that they may break my phone, or not fix it under warranty?

    OK, I have to admit. I am EXTREMELY disappointed by Apple in all of this greedy-give-me-control-shit. "Control Freak" is a term that comes to mind, now... and I'd love to see Jobs on a crossfire type dillio trying to explain how its "better" this way for everyone.

    And I didn't even want an Apple made phone... I want a frickin' OS X slate, with inkwell in full functionality. Apple could develope and release such a product with their eyes closed. And make a decent profit. But it might hurt their precious iPhone sales... so... no product.

  72. Re:Why this _is_ wrong... by realthing02 · · Score: 1

    better not use the iphone as a paper weight... or it will become one!

  73. Non-sequitor. by msauve · · Score: 1

    A "no mods" provision is not a "tie-in" provision.

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  74. Well then, what about... by OreoJRLKing · · Score: 1

    I have Realplayer installed on my mac. And MS Office. These are third party applications. Shouldn't my mac warranty be voided the next time I update iTunes? I'm absolutely sick of Apple dancing between the lines with their phone. They need to stop pretending it's some consumer electronics holy grail and treat it like they treat the rest of their products.

  75. Re:Why this _is_ wrong... by Durzel · · Score: 1

    My intepretation of this is that it's like an aftermarket ECU for a car. Aftermarket drop-in ECUs essentially replace all of the software in the car, and usually provide a performance boost, change timings on various things, etc. ECUs can run components in the car at performance levels/speeds that are outside manufacturer tolerances, as usually these bits of hardware are just dumb devices that have no real failsafes.

    Therefore since software CAN damage hardware by forcing it to operate outside of it's tolerance I'd say that Apple do have a pretty strong case for automatically voiding the warranty on any iPhone that is unlocked or has a firmware that has been tampered with. If you can't guarantee the operating parameters of a product then you can't really provide, or be expected to provide, a full warranty for when it goes wrong.

  76. Oversimplification by stewbacca · · Score: 1
    No, R&D is an ongoing cost. It also has external costs too, just like every other aspect of every other business. I am willing to bet there are at least 20 external consulting contracts associated with all things iPhone. Apple has to pay these people to come in and do the work that Apple doesn't have the manpower to do on their own. Sometimes it just costs less to pay some other agency to do it for you.

    Just because the collective gains of Apple as a business puts them in the black, doesn't mean they don't have to create a business model that at least partially recovers the costs of designing, developing, implementing and maintaining the iPhone. If they just left all the other division up to making enough money for the iPhone, then they would not have any money for the iPhone division. Cannibalizing from one department to cover another is never good business.

  77. Dave Shroeder - Apple's Attack Dog by Anonymous Coward · · Score: 0

    Dave, has there *ever* been a crappy move/statement/product of Apple's that you have not rushed into defend. You should be getting paid for your efforts. Are you?

  78. Computer Analogy by _KiTA_ · · Score: 0

    This would be like Dell refusing warranty service on someone who hooked up a HP printer, or bought a ATI video card off NewEgg.Com.

    The worst they can do is ask you disconnect the 3rd party hardware to see if that fixes the situation.

  79. Did anybody notice this? by Speed+Pour · · Score: 1
    I admit, I haven't got the time to read the legal writing, but in the summary it says:

    ...if Apple can determine that the modification or enhancement is responsible [for] damaging the product in question... It seems to me, after reading this, that if the unlocking method does NOT damage the iPhone, and the upcoming patch DOES brick it...then that means Apple's own patch constitutes an 'enhancement' that will void the warranty, because their own patch damages the product.

    If this ever reaches class action status (the only way apple will ever pay out on this issue), and if this particular law manages to be invoked, I expect that one of the primary platforms for the suit will be that Apple's release of the patch intentionally voids the warranty on any phone that previously had a valid warranty despite having been legally, legitimately, and safely unlocked.
    --
    - Nobody would know what RTFA meant if it didn't need to be said all the time
  80. Re:FUCK YOU MOD by arkanes · · Score: 1

    What bullshit world do you live in that "and the rest of your post is wrong too" constitutes proof of any kind?

  81. If someone thinks differently, he is stupid? by Futurepower(R) · · Score: 1

    "But please, doesn't anyone have anything more important to do than bitch about a phone???? Oh yeah, I forgot, this is slashdot..."

    This IS Slashdot. You showed it by thinking that, if someone has a different point of view, that person is stupid.

    I am genuinely interested in why companies self-destruct, and have been studying that for more than 20 years.

    Did Steve Jobs not realize that locking the iPhone to a single high-cost provider would cause problems, and damage the reputation of Apple? Apparently not, but why?

  82. Re:FUCK YOU MOD by SIIHP · · Score: 0, Troll

    What kind of idiot are you that you ignore the part of my post that DOES prove him wrong?

    --
    I only go to buffets for the unlimited soft serve.
  83. How to get around this by llevity · · Score: 1

    Step 1) Warranty is only void if modification caused the problem
    Step 2) Issue a firmware update that bricks the phone if it is modified
    Step 3) ???
    Step 4) Profit!

    Seems to me, the modification caused the malfunction. :)

  84. Remember to fact check, please. by Futurepower(R) · · Score: 1

    I will give your advice back to you: Remember to fact check. The management of the new company called "AT&T" is very different from the more trustworthy company that was AT&T. That's the point. Should Apple have partnered with that new company? I think not.

    Why do I think that? Apple will get criticism for everything bad the new "AT&T" does. For example, see the August 23, 2007 article AT&T Ditches 'Fewest Dropped Calls' Ad Campaign, which was apparently fraudulent. This article notes that AT&T's new slogan, "more bars in more places", seems to be exactly the same claim, in different language: AT&T Drops 'Fewest Dropped Calls' Claim.

    To understand the new management, consider the history. For $16 Billion SBC got AT&T's VOIP customers, and the AT&T name. Quote from the Business Week: "It isn't clear whether or not AT&T CEO David Dorman, who will earn about $20 million from the sale of AT&T, will stick around."

    So, a manager who presided over the failure of his company made $30 million (not $20 million) from selling the company to other managers who are reputed to be just as inept.

    The Wikipedia article says, "Dorman's management finesse can be ascertained by tracking the value of AT&T stock during his tenure." Dorman became president in 2000, Wikipedia says. The stock performance tanked beginning just before that, and continued down until the AT&T name was sold to SBC.

    It looks from the stock quotes that AT&T is doing well now, but apparently that is only because the AT&T name was pasted on a new company. (It's like unscrewing the radiator cap and driving a different car underneath. That's not real car repair.)

    That's Apples new partner. Does that seem like a partner that will enhance a reputation?

  85. -1 Whiny Whiner by aztektum · · Score: 1

    Your argument is silly. Just because they CAN do something to prevent issues doesn't mean they're in any way required to, legally or even ethically IMO. They made the decision to sell hardware configured in a certain way. They offer updates and are saying "If you've altered the stock configuration, update at your own risk."

    Is it technically feasible for Apple to work around this? Sure. Should they have to? No. It's YOUR damn phone now, not theirs. They're offering updates as a courtesy on their terms, not bending over backwards to suit anyone and everyone. That's how Apple has done business for YEARS.

    --
    :: aztek ::
    No sig for you!!
    1. Re:-1 Whiny Whiner by Anonymous Coward · · Score: 0

      That may be, but checking to see if the patch will destroy your phone(Altered code or otherwise) should be enforced. What if you didn't alter your phone and the update bricked your phone? Are you at fault for a software defect that had nothing to do with you? I should think not. Sure, they aren't entitled to code around your changes. Sure they aren't entitled to send you a replacement phone if your hacks brick your phone. But if their updates brick your phone, they could have prevented it, and it wasn't a result of someone's hacking, they are at fault. Taking that into consideration, even if they aren't at fault for bricking your phone if you hacked it, it should have been fixed even if you hacked it because if you hadn't and there was a fault in the software this kind of prevention would have prevented it.

      As for the hardware side of the equation(I know you didn't touch it, just going over it anyway), yes, if the hack causes hardware failure Apple has obligation to fix your phone.

      Also, I'm just using the term "brick" because everyone else is. I would much rather use the term "broken". ^.^

  86. It's a moot point, they've already broken the law. by Anonymous Coward · · Score: 1, Interesting
    It's not a question of whether they've broken the law with their software update policy. The question in my mind is... how did they slip past the antitrust laws in the first place?

    Requiring me to sign up for a specific provider's service in order to fully realize my new iPhone's potential (ie, make calls without voiding my warranty) sounds very similar to requiring me to purchase and use Brand X vacuum cleaner bags in my Brand X vacuum... or having to purchase and use gasoline only from Exxon because I purchased a Chevy vehicle. So, tell me again how their initial policy is legal?

    Settle that for me, and I'll consider worrying about the firmware updates.

  87. It is only illegal if you get caught. by TavisJohn · · Score: 1

    The mentality of corporate America is that it is legal until a judge says so.

    "Even if another company did the same thing and got busted for it, I can do it because the judge never said I could not do it, just them..."

    This is where the bottom line is more important than what is legal.

    Corporate America also takes into account fines and such. "Is it more cost effective to break the law and pay the fine, than to do it legally?" If it is, then the law will be broken!

  88. what does this do for modchips? by spir0 · · Score: 1

    Modchips for consoles are 3rd party add-ons. Will this set a precedent for them? If so, why didn't they dig up this ancient law to support their cases?

    Will those who were sued into oblivion or shut down by Sony/MS be able to now claim back that they are legitimate 3rd party add-ons? or will Apple use them as a precedent to support their stance for the iPhone?

    --
    The reason girls and Windows users don't understand UNIX is because all the documentation is in Man files.
    1. Re:what does this do for modchips? by Anonymous Coward · · Score: 0

      I'm also really interested in this. According to most people, putting a modchip... or even opening your console voids the warranty. Is that legal?

  89. What's the problem here? by Rexdude · · Score: 1

    First there's the 'don't buy if you don't like it' argument. Apple is free to set whatever terms they choose, and you're free to vote with your wallet either way.
    Secondly, how's fiddling with the firmware to unlock it any different from overclocking your CPU, or adding an aftermarket modification to your car's engine to make it go faster? In both these cases you void your warranty and the manufacturer is not liable for any damages that may result.
    Apple provides the iPhone integrated with AT&T as a bundled service, as an 'experience' if you will; they cannot guarantee things will work perfectly if you change the working specs in this manner.
    It is lamentable that they don't provide an unlocked phone to begin with, but one can't complain much here.

    --
    "..One hosts to look them up, one DNS to find them, and in the darkness BIND them."
  90. "beyond areasonable doubt" --- again by westlake · · Score: 1
    In the case of firmware causing damage on an arbitrary point in time, i would expect for that warranty act to enacted, the burden of proving beyond reasonable doubt that your firmware didn't cause the breakdown would rest on you.

    This becomes a little tiresome.

    But "proof beyond a reasonable doubt" has almost no meaning outside of a criminal trial.

    Your burden of proof is simply to persuade a judge that it is reasonable to believe that your modifications didn't brick your phone, not so easy to do, of course, if your modified phone has - in fact - been bricked.

  91. The Apple Product Cycle by cybereal · · Score: 1
    The Apple Product Cycle

    I think we are in this stage:

    Apple releases the first software update for the new device through its Software Update control panel. Several hours later, it pulls the updater. A small number of people who applied the update experience crashes, data loss, headaches and ennui. The Apple support forums are filled with outraged posts. A day or so later, Apple releases a revised installer without comment, then quietly removes the angry posts from its support forums.

    or possibly this one still:

    A minor, rarely occurring flaw in the device begins to be discussed in the Apple support forums. Whiny, artistic types post lengthy diatribes about how this terrible design flaw has made the device unusable and scarred them emotionally. Electronic petitions are created demanding that Apple replace the devices for free, plus pay for counseling to help traumatized users overcome their emotional distress.

    and just about to enter the former stage.

    I'm amazed at how accurate this product cycle document is...

    Also, I'm decidedly disappointed in the people who are complaining about this warning. First of all, it's nothing more than a warning so far. It is probably not going to amount to ANYTHING. Second, why shouldn't this warning be issued? The company is displaying that they are aware of what is being done with their product and reiterating that they don't support it and their actions could conflict with those of the hackers.

    As for the armchair lawyers, why do you think you have any idea what you are talking about? These areas of law are gray, and extremely tenebrous unexplored areas, and the requirements on companies like Apple or AT&T are unknown. That's the point of trials. If this ends up with a trial behind it, regardless of the winner, it's a positive thing to clarify some laws for us with precedents. But, the important thing to remember is that you don't know what you're talking about. Neither do any of you, or you, or you. So please, stfu about the law aspect of this issue.

    The naiveness displayed by all parties of this issue is blinding. You have the hackers making permanent changes to an embedded device. Apple haters claiming legal foul on an issue that hasn't even HAPPENED yet. The apologists blindly supporting the downsides of vendor lock-in. The armchair lawyers deciding for the courts before anyone has even offered a case.

    Has anyone bothered to point out that this is the same issue you have in any other example of firmware hacks to accomplish device unlocking?

    Has anyone bothered to realize that the DMCA exception protects you from legal action, AGAINST you, under copyright law, and nothing else? Why do so many people think this somehow implies responsibility on the side of the OEM?

    Personally I'm happy to see Apple showing that they have the guts to continue on with their business model on the iPhone, without taking heed to the tech world underbelly who likes to have it both ways til Sunday. This is the only way we're going to continue to receive excellent software on mobile devices, which simply has not existed before the iPhone. These negative aspects of the iPhone model and release are exactly what we need to motivate other companies to create devices that may actually rival the iPhone and sell them by advertising that they aren't locking you in, that you can get SIM unlocked versions, etc.

    Slashdot won't bring you any news or valid commentary but it sure as hell can generate massive amounts of speculative fiction for those who like to read that genre.

    --
    I read the script, and I think it would help my character's motivation if he was on fire. -Bender
  92. Customer loyalty by Anonymous Coward · · Score: 0

    Apple is probably counting on its fanbois to not raise a stink. Its time Apple customers need to realize that they are just like every other company and stand up to when Apple is wrong.

  93. Re:Why this _is_ wrong... by R3d+M3rcury · · Score: 1

    Pretty much, but with some exceptions.

    You're right, but it is up to the car manufacturer to show that the modification caused the problem. So if I blow my engine because of my turbo modifications, it's pretty easy for the car manufacturer to void engine repairs/replacement based upon this. However, if my power windows stop working, the car manufacturer can't void my warranty because of my turbo modification without showing how the turbo modification caused the problem.

    Software can damage hardware, but it would be up to Apple to show that software that the user installed damaged the hardware. That's sort of the point.

    Now, is it worth it for Apple to do this or just say, "Fine, whatever!" and give the customer another $400 phone? That's the question. I suppose it depends on how many people show up on Apple's doorstep saying, "You bricked my iPhone!"

    IMHO, you're gonna need a lawyer to get involved.

  94. Boo at all this by hollywoodb · · Score: 1

    I'm tired of reading about the iPhone.

    C'mon guys, can't we discuss something interesting like that linux scheduler fiasco? I heard Con Kolivas might not maintain some patchset or something anymore. That's interesting too, right?

    Oh, and I've heard the RIAA is really just a front for some record company or something and they're suing people!!one!1!

    --
    I may have to share this planet with animals, but I'm doing my damn best to eat every last one of them.
  95. hand-wavey and possessive by null.account · · Score: 1

    Because it alters the way in which users make use of the device, I'd guess Apple would argue it's doing damage to the product, not the phone. They'd effectively have to argue that "How you use it is part of what we're marketing to you, and it's part of what you buy".

  96. Re:The argument is that cellphones are a special c by mr_matticus · · Score: 1

    If by fun you mean "rejecting outright and thus saving the legal system from one more piece of pointless litigation," you're absolutely correct.

    Being able to unlock a cellular SIM due to a copyright exception has no bearing whatsoever on warranty validity. If you modify the firmware of your PC and it breaks, that's your problem. If you modify the firmware of your cell phone and it breaks, it's your problem.

    In addition to the other well-developed applications about the warranty's compliance, here's another: the section of Magnuson-Moss as quoted by the "no tying" crowd covers product warranties for parts and workmanship. It does not apply in the same way and to the same extent as a service warranty, which all iPhones possess. It does not apply to software warranty claims at all.

  97. Told ya so... by InakaBoyJoe · · Score: 1

    A month ago we had a thread on this topic, and I mentioned the potential applicability of the Magnuson-Moss Act. I'm surprised it didn't get any replies and continued to languish at a +1 mod score. Anyway, there might be some interesting stuff in that thread about whether Apple can deny software updates for unlocked iPhones...

  98. Re:The argument is that cellphones are a special c by argent · · Score: 1

    Like I said, I Am Not A Lawyer, and I didn't claim anything one way or another about the validity of the case. I was just pointing out that IF (important word) the arguments being presented were correct, THEN the analogy with an automobile engine computer didn't apply, SO just presenting it without dealing with the arguments wasn't useful.

    Thank you for the clarification.

  99. hardware defects should still be covered by Anonymous Coward · · Score: 0

    Example; the screen begins to separate from the bezel. The "touch" sensitivity ceases to respond. The home button stops functioning. The battery explodes (and we all know how likely that is!!!) The battery holds no charge after 8-weeks. Etc. Etc...

    All likely and easily provable as hardware defects (as long as no evidence of user neglect, of course)...all should be covered under warranty and Magnuson-Moss Act protects the consumer in these situations.

    Apply a software "unlock" to modify firmware and immediately phone does not boot....warranty for restoring the software to a usable condition proabably void, Apple has no obligation to offer a restore or any support...must wait for the community to profer a solution...IF APPLE CAN PROVE that the 3rd-party software likely caused the malfunction. But, if the 3rd party mod can't be reasonably be attributed to have caused the problem, warranty still should apply. Read the Apple warranty...it even states this!

  100. How does it alter how you use the device? by Anonymous Coward · · Score: 0

    How does it alter how you use the device? it is still being used as intended...as a phone...and iPod, etc...the iPhone after a 3rd party unlock still works as intended, designed, and does not really alter how it is used (which is the only real exception to the warranty ain't it).

    Altering how it is used would be like, if I put my beer bottle on it and used it as a coaster and then went in to have the screen replaced because it no longer responds to "touch."

    1. Re:How does it alter how you use the device? by null.account · · Score: 1
      When I wrote "make use of" and "use the device", I was implying "[make use of/use the device] as a phone/media player/web interface device" Maybe a slighty better wording would have been:

      "How it provides telephone/media services[*] to you is part of what we're marketing to you, and we've decided that it's part of what you're buying when you buy the device." [*] That is, the pre-built service provider lock-in to AT&T, among other things (unpublished APIs).
  101. +1 industry realist by TheVelvetFlamebait · · Score: 1
    The firmware update is for the iPhone and the iPhone alone. They could check the firmware and overwrite the cracks, but they don't have to. They are simply not obliged to make their software compatible with anything but an iPhone that's stock standard and covered under warranty. The onus is on you, the hacker, to make your iPhone compatible, or at least to refuse updates.

    Any manufacturer who causes users 4-600$ dollars worth of hardware loss via a software update would be liable. End of story.
    Don't forget that they aren't shoving this update down your throats. You are the one causing $400-600 dollars of hardware loss by modifying your phone, and then updating it like you hadn't.

    Believe me, if PC manufacturers could have voided your warranty for installing a different operating system (as they would be able to according to your arguments), they would have years ago.
    If you do modify (or change) your PC's OS, and then accept an update that's not compatible with your non-standard arrangement, then you alone are responsible any hardware damage by software that occurs. I mean, who else would be responsible?
    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  102. Re:Why this _is_ wrong... by TheVelvetFlamebait · · Score: 1

    Firmware is required to make the device work, but it's provided by the manufacturer. So, can the manufacturer prevent you from using someone else's firmware by invalidating the warranty?
    Put it this way: does altering the firmware affect compatibility between your device and future updates? If so, then yes they can.
    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  103. Re:FUCK YOU MOD by TheVelvetFlamebait · · Score: 2, Informative

    Obviously the kind that realises that just because they may be wrong about one thing, doesn't mean that everything else they say is wrong because of it.

    In regard to your whinging about the troll mod, let me say that troll mods have nothing to do with truth, or logic. If you put your opinion in an inflammatory or obstructive way, no matter how logical or truthful you may think it is, you run the risk of legitimately getting a troll mod. That last "and the rest of your comment was wrong" line was especially obstructive. How are you meant to discuss the topics at hand if everyone just said "you are completely wrong" and provided little to no evidence why.

    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  104. Amazing by snickkers · · Score: 1

    "The Magnuson-Moss Warranty Act states that Apple cannot void a warranty for a product with third-party enhancements or modifications to their product." -- it's incredible that a decades-old law was so specific as to only target Apple.

    --
    GLORX 3:16
  105. Anyone remember that laptop? by Klion · · Score: 1

    The one PC world wouldn't repair because Linux was on it? http://linux.slashdot.org/linux/07/09/15/2031231.shtml Seems that whole "'The Magnuson-Moss Warranty Act states that ______ cannot void a warranty for a product with third-party enhancements or modifications to their product. The only exception to this rule is if Apple can determine that the modification or enhancement is responsible [for] damaging the product in question ..." might apply there as well eh?

  106. You do know, this means war... by MacDork · · Score: 1

    Nope. State and Federal courts are quite clear on the fact that the manufacturer is in no way obligate to support a item if the user manipulates said item so as it is not covered under the agreed to contract or warranty.

    Apple is going further than not supporting an item. They are deliberately bricking phones. It would take no effort on Apple's part to run a checksum on the firmware for originality. Not original? No update. It's that simple. That would be perfectly legal.

    Instead, Apple is saying, "Our update ignores the existence of aftermarket upgrades that may be incompatible. We are aware that it will brick your phone. We are taking no steps to prevent our update from damaging your hardware. Tough shit." No, really, they are:

    Schiller said that at least two unlocking programs, iUnlock and Anysim, can cause the iPhone to stop working once the software is updated.

    I doubt that sort of negligence is legal.

    If anyone at Apple is reading this: I've been an Apple fanatic for 10 years. I've owned nothing but Apple computers... until recently. I chose Nokia's N95 over the iPhone because of your stance on locking and a native SDK. That led to the purchase of a PC laptop to run firmware updates on my phone, since the software doesn't support the Mac. Given your current open hostility toward your customers, I am now reconsidering the future purchase of any Apple hardware. I have already let my "ADC Select" developer membership lapse. No native SDK was a real slap in the face. Continue this negligent, hostile behavior, and I will leave your platform as a customer and developer entirely.

  107. Re:Why this _is_ wrong... by Anonymous Coward · · Score: 0

    You require iTunes to purchase a track... iTunes plays that track. iTunes is free. Warranty act is met. Just because you want to play that track somewhere other than a machine with iTunes.... well thats your problem :)

  108. Re:Why this _is_ wrong... by kronsrepus · · Score: 1

    HOWEVER other functions of the iPhone (such as Visual Voice Mail) only work correctly on AT&T. The whole "registration" process only works on AT&T... you're buying a packaged product with functions other than a phone.

    Sure the product works adequately on other carriers, but it does not work as Apple intended. Unless other carriers are willing to invest in the infrastructure required for the iPhone to function correctly Apple are in the clear, obviously no other carriers were willing to invest (at least as much as AT&T were willing to invest) - otherwise they would have negotiated a deal with Apple prior to the launch.

  109. Easy now, take a deep breath by Whuffo · · Score: 1
    What Apple is doing when they make comments like "updates may render your altered IPhone inoperative" is making a disclaimer. They aren't planning on bricking your IPhone and it's highly unlikely that such a thing would ever happen.

    But in case it does, they're on record as having warned you - which will greatly reduce their liability...

  110. Apple's plans might even be covered... by walter_f · · Score: 1

    ... by this Magnuson-Moss Warranty Act, formally-legally.

    I don't know.
    IANAL.

    Still, there's a point to the suggestion raised here:

    ---
    Shame on Apple! ...

    Frankly, I think the solution is to quickly organize a massive "Do Not Buy Apple Products" day before the new firmware comes out. Maybe October 1. Send a message to Apple that they enjoy success at our pleasure, and that a second rate iPhone experience is not acceptable and not what we've come to expect from Apple.

    So on October 1, do not run Software Update. Do not buy an iPhone. Do not buy Mac apps at all, including shareware or third party OS X stuff. Let's piss off Apple, let's piss off small developers who will have no one to complain to but Apple. ...
    ---

    http://firsttube.com/read/Shame-on-Apple

  111. Re:FUCK YOU MOD by SIIHP · · Score: 0, Troll

    "Obviously the kind that realises that just because they may be wrong about one thing, doesn't mean that everything else they say is wrong because of it."

    Well, since I didn't make that claim, that makes you an idiot also.

    "How are you meant to discuss the topics at hand if everyone just said "you are completely wrong" and provided little to no evidence why."

    Well, since I didn't do THAT either, that makes you an idiot^2.

    Also, I couldn't care less about your opinion, and why you have time to waste commenting on my comment of a troll mod is beyond me, but thanks for the opportunity to tell someone off, that made my morning.

    --
    I only go to buffets for the unlimited soft serve.
  112. Much ado about nothing by LKM · · Score: 1

    It's not even that. I'm getting my iPhone today, and first think I'll do is unlock it. I never expected to be able to install any updates from Apple after that, so this whole brouhaha seems totally absurd. I just won't update iTunes on the Mac I sync the iPhone with anymore, and that's that.

  113. Criminal Damage by ajs318 · · Score: 1

    If I own a telephone which I bought and paid for with my own money, and someone sends a message over-the-air that my telephone receives, and the effect of that message is that my phone that I own is somehow damaged, then whoever sent that message is guilty of criminal damage. They broke my property. That is a matter for the police.

    Unfortunately, I won't be able to dial 999 because my phone is broken .....

    --
    Je fume. Tu fumes. Nous fûmes!
  114. iPhone Warranty by joeyblades · · Score: 2, Insightful

    I'm confused. Apple's iPhone warranty clearly states:

    > Limitations| The Plan does not cover: ... unauthorized modification

    Clearly unlocking a phone is unauthorized modification. There are laws that enable individuals to unlock their own cell phones, but these laws do not require the OEM to honor the warranties on the equipment. Unlocking a phone is something you do at your own risk.

    Since the warranty is clear, I don't think Magnuson-Moss applies...

    As for firmware that causes damage to unlocked phones, I think Apple would be overstepping it's bounds. There are other ways to skin that cat. A simpler, less volitile solution would be for Apple to patent a custom SIM package and the iPhone would only work with SIM cards that Apple produced.

    1. Re:iPhone Warranty by Anonymous Coward · · Score: 0

      I think are correct.
      Apple should not update or help out with modified iPhones, those users voided their warranty. IMHO their contract should not be renewed.
      But Apple should not damage any equipment, it belongs to the User not Apple.
      Apple should simply release updates that only work with non-modified iPhones. They should of had a process that re-flashes it over the wire.

  115. Re:FUCK YOU MOD by TheVelvetFlamebait · · Score: 1

    Also, I couldn't care less about your opinion, and why you have time to waste commenting on my comment of a troll mod is beyond me
    I'm bored, home alone sick, no-one's listening to me peddling the same ol' crap (just check my comment history, with particular focus on the latest apple stories). Anyway, into more pointless, yet still valuable stuff:

    "Obviously the kind that realises that just because they may be wrong about one thing, doesn't mean that everything else they say is wrong because of it."

    Well, since I didn't make that claim, that makes you an idiot also.
    What about your reply, where I seem to recall you saying "What kind of idiot are you that you ignore the part of my post that DOES prove him wrong?" The person replying to you accused you of over-generalising by calling the whole post wrong based on one part, and you responded by implying that the rest of your post proves that, i.e. that the part that you think he got wrong makes him wrong, and that the generalisation is warranted. I would be an idiot not to come to that conclusion.

    Well, since I didn't do THAT either, that makes you an idiot
    You said the rest of the comment was wrong, you provided little evidence. Sure you poked holes in one little statement, but that constitutes little to no evidence. It's both inflammatory and obstructive. You can't really pull to pieces an argument that doesn't show any evidence, so it obstructs the argument. It's inflammatory because it's insulting to others to harshly call them completely wrong, and then provide no details, or reasons why such a harsh judgement is warranted.
    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  116. Re:FUCK YOU MOD by SIIHP · · Score: 1

    "Also, I couldn't care less about your opinion"

    I don't think you read that part before you wasted your time composing a reply I'll never read.

    --
    I only go to buffets for the unlimited soft serve.
  117. Re:Why this _is_ wrong... by Anonymous Coward · · Score: 0

    That is not the intent of the MM act and it is not used in that manner. Using your theory, you would not be able to do anything with the car or the warranty would be void which would make the entire MM act useless. It is far from useless.
    In your theory, changing tires to something that handled better then stock which would allow you to drive more spirited would also voilate the warranty, how about using synthetic oil or using high octane fuel? The auto maker has to PROVE that your modification did not cause the problem. The fact that you have 5 more HP does not prove why the rear shocks blew out.

    On that note though. I had an AC hose that was in close contact to my exhaust manifold. It was not a hose that you could move and it was installed in that position from the factory build. I had actualy noticed it a month prior and made a mental note that it should not be that close to the exhaust and tried to manipulate it by hand but soon forgot about it. The 95 degree day that I had no cold air from the AC, I immediately thought about that hose. I was initially denied warranty repairs because of "modifications" I had done to the car. Well there was absolutely no modifications at all and the car was only 4 months old. Me and the dealer were involved in some heated discussions and eventually they fixed it under the warranty free but it took a while.
    I have no doubt that certain dealers will attempt to weasel out of repair work if possible.

  118. Re:FUCK YOU MOD by TheVelvetFlamebait · · Score: 1

    I read it. You seem to want to end the conversation, yet the replies keep coming.

    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  119. Re:FUCK YOU MOD by SIIHP · · Score: 1

    "Also, I couldn't care less about your opinion"

    I still don't think you read that part before you wasted your time composing another reply I'll never read.

    --
    I only go to buffets for the unlimited soft serve.
  120. My Note to Apple and The Response by Anonymous Coward · · Score: 0

    Posted to: http://discussions.apple.com/thread.jspa?threadID=1151569&stqc=true

    Subject: Apple. I will abandon you.

    The iPhone is a platform. I expect 3rd party apps. I expect them on a Sony phone. I expect them on a Symbian Phone, a Windows Mobile Phone, a BlackBerry and a Palm.

    The iPod is an appliance. I no more expect third party apps on it than I do my DVD player or my digital camera. Confusing the iPod appliance with the iPhone platform isn't a mistake the market should forgive.

    If you brick my phone because it has SSH and Navizon on it. I will abandon you.

    Do the right thing and make a proper SDK.

    About an hour later I received this (it's technically right - but while I'm already irritated about the news I took it just as aggravating):

    Please read our Apple Discussions Use Agreement so that you may discover what constitutes an appropriate post to our service. Section two, "Submissions," is most germane.

    Your post, copied below, has been removed from Apple Discussions. This area is intended to address technical issues about Apple products. Posts that do not conform to the Apple Discussions Use Agreement are inappropriate.

    Please see the Apple Discussions Use Agreement at http://discussions.apple.com/help.jspa for more information on the proper use of Apple's Discussion forums.

    Each Discussion user is required to agree to these terms before gaining posting privileges. You reserve the right to not post on Apple Discussions should you disagree with these terms.

    If you would like to send feedback to Apple about a product, please use the appropriate selection at http://www.apple.com/feedback

    Sometimes you have comments or concerns for which there is no technical response. If you need the kind of help that a troubleshooting expert can't prfovide, you can call Apple's Customer Relations group.

    ++++++++++

    This message is sent from a send-only email account. Any replies sent to this address are deleted automatically by the system.

    So I guess I'll resend to the feedback group instead of the discussions.

  121. Re:FUCK YOU MOD by TheVelvetFlamebait · · Score: 1

    Yeah, but if I don't reply, how will I stress that I'm the better man for walking away without having the last word?

    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  122. Re:FUCK YOU MOD by SIIHP · · Score: 1

    "Also, I couldn't care less about your opinion"

    I still don't think you read that part before you wasted your time composing yet another reply I'll never read.

    --
    I only go to buffets for the unlimited soft serve.
  123. Re:FUCK YOU MOD by TheVelvetFlamebait · · Score: 1

    Let's just see how many combinations of the same ol' crap you can make before:

    a) You run out of ideas, and the lameness filters get you
    b) The thread closes

    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  124. Re:Why the fuss? by Jeremy_Bee · · Score: 1

    Honestly, I don't know why there's so much fuss about this. Hacking the firmware is very much an "at your own risk" procedure, and anyone who pretends not to know that is being deliberately stupid. It's all part of the rabid popularity of the iPhone and the commercialisation of the unlocking procedure. It's a very unusual and new situation. Unlike true "old-school" hackers, these guys are selling the hacks, and selling them into a market that wants an iPhone so badly they just can't wait.

    Traditionally, the hacker takes his chances and doesn't cry foul when the firmware is revised, or he/she slips with his soldering iron and ruins the product. If he/she passes on the hack to his friends or publishes it on a newsgroup, this same "traditional" hacker doesn't invest anything into it other than personal pride and a hope that it proves useful to someone else. Here, on the other hand we have "monetized hacks" and the hackers have a vested interest in making Apple look as bad as possible.

    The main problem here however, is that we also have a frenzied army of consumers with absolutely no idea about hacking, computer firmware, or the history of hacking practices. We have "mom and pop" iPhone users that bought a bill of goods from some hacker on eBay and do not understand why Apple is "abandoning" them. On top of that, we have an associated group of juvenile idiots spreading rumors everyday on Digg about Apple's monopolistic and "evil" intentions (as if they actually know anything about this).

    The net result is that these assholes (the iPhone "hackers"), are making a bundle, all the teenagers get to cry foul on Digg, and Apple has to clean up the mess and take the heat for being "evil."
  125. The Law, as far as I know.... by El+Gruga · · Score: 1
    Apple can NOT just write an agreement and then do what they want.

    IF the agreement violates the consumers rights, then it is simply garbage, and furthermore, you can NOT agree to a warranty or contract that removes your rights.

    Apple's little 'warning' is hogwash - you can NOT say 'Oh that plane ticket you bought, if you get on the plane wearing a red shirt we are going to fly into a mountain' NO.

    ALL phones MUST be able to be 'released' from the shackles of any cell service provider. What if you cancel with AT&T and want to take YOUR iPhone to T-mobile?

    As long as you pay the cancellation charges etc., WHY cant you do that?

    Apple are in seriously deep-dish legal crap on this one.....

    The rights of a consumer may NOT be subverted by a company writing a EULA that subverts those rights for its own gain - thats simply illegal.

    As someone else has said here, wrecking the phone with an 'upgrade' sent over the 'net is tantamount to a criminal act by Apple - criminal damage, in fact.

    This one is just starting to heat up - look for some very interesting action in the next week or so!

    I predict an unlocked iPhone by Apple in less than six weeks, with some recompense to AT&T for the loss of income.

    Apple have been greedy and power-crazed here, and I suspect that Steve Jobs is really trying too hard - take it easy Steve, World Domination aint all its cracked up to be......

  126. Re:It's a moot point, they've already broken the l by El+Gruga · · Score: 1
    Agreed!

    You buy the damn phone and then they tell you what you can do with it - if this were Condoms, presumably the CEO would be in your bedroom telling you how to make out with your wife, and if you dont do as he says, the condom breaks and she gets pregnant.

    As some one else says, Corporate America do what they like and wait for the lawsuits. The law is never an issue for them.

    Shame to see Apple doing this, with their market share going up and all.....

  127. Re:The argument is that cellphones are a special c by El+Gruga · · Score: 1
    The car analogy is idiotic.

    The issue here is NOT the bloody warranty - its the notion that iPhone OWNERS can unlock their damn phones so they work on any network they choose. All other phones are available unlocked, why not the iPhone?

    Apple, unlock the bloody phone so we can all get on with our lives - you are ruining a damn good product with your frickin control-freakery, you idiots.

  128. Re:FUCK YOU MOD by SIIHP · · Score: 1

    How fucking stupid are you that you keep posting replies I don't bother reading?

    --
    I only go to buffets for the unlimited soft serve.
  129. Re:FUCK YOU MOD by TheVelvetFlamebait · · Score: 1

    If you cared to read them, you'd find out why.

    --
    You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
  130. what about the functionality of the phone? by Kwirl · · Score: 1

    ok seriously, who cares about the warranty. the non-functional/recoverable 600 dollar phone is something people DO care about. (yeah i know, warranty good etc - point is, the issue is more about the lack of use of your iphone)

  131. Re:FUCK YOU MOD by SIIHP · · Score: 1

    How fucking stupid are you that you keep posting replies I still don't bother reading?

    I mean, I enjoy dressing your idiot ass down, so this is recreation, but what kind of loser has the time to take such an ass whipping?

    Oh, your particular kind of loser does.

    --
    I only go to buffets for the unlimited soft serve.