Slashdot Mirror


Apple Sued Over iPhone Bricking

An anonymous reader writes "The week's debate over the iPhone 1.1.1 has finally resulted in legal action. InfoWeek reports that on Friday, California resident Timothy Smith sued Apple in a class-action case in Santa Clara County Superior court. The suit was filed by Damian Fernandez, the lawyer who's been soliciting plaintiffs all week for a case against Apple. The suit doesn't ask for a specific dollar amount, but seeks an injunction against Apple, which prevents it from selling the iPhone with any software lock. It also asks that Apple be enjoined from denying warranty service to users of unlocked iPhone, and from requiring iPhone users to get their phone service through AT&T."

17 of 418 comments (clear)

  1. Stupid lawsuit again...? by cavac · · Score: 5, Insightful

    If you modify an embedded system in a non-vendor approved way and then install a vendor update and the update brakes cause you did something incompatible.... Then it's your fault, not the vendors...

    While i agree that Apple should be forced to sell unlocked phones, modifying a product in a non-approved way DOES invalidate your waranty. Why should the vendor be held reliable if YOU break his software?

    --
    Look, this thing is totally safe! Built it myself, you know. You just press that button like this and then turn that lev
    1. Re:Stupid lawsuit again...? by cbunix23 · · Score: 5, Insightful

      Exactly. There hasn't been any information as to exactly what the nature of that update from Apple was. All we know is after the update unlocked iPhones were no longer usable after the update was applied. The tech-ignorant media has been suggesting the purpose of the update was to turn unlocked iPhones into iBricks, but there has been no proof of that.

      Apple did not release an iPhone SDK or API that could be programmed to. Why should they be held responsible for what happens when iPhone updates break iPhones with arbitrary software on them.

      It would be like changing the linux kernel for some special project you are workin on and then complaining that your unapproved changes no longer worked when the next kernel release came along. That's why there are API and SDKs and manual pages. Go beyond them at your peril.

    2. Re:Stupid lawsuit again...? by peragrin · · Score: 4, Insightful

      actually the guys looking at the code are saying that apple did a complete rewrite of the software. Maybe Apple didn't want third party applications because the first version of the software while functional was ugly from an internal standpoint

      Think OS X 10.0 versus 10.2 they work the same yet the code itself has been cleaned up.

      --
      i thought once I was found, but it was only a dream.
    3. Re:Stupid lawsuit again...? by speaker+of+the+truth · · Score: 3, Insightful

      Then it's your fault, not the vendors... Unless of course writes code that does nothing EXCEPT break modded phones. It would sort of be like Microsoft detecting you have open office installed on your computer while giving you a patch for Microsoft Word and then bricking your computer.

      Now I've seen nothing but insinuations that Apple did this myself. But some lawyer obviously thinks there is a bit more then insinuations. Whether or not he's hoping to confuse the courts or has a good case remains to be seen.
      --
      Using openSUSE instead of Windows since 9th of October, 2007 and liking it.
    4. Re:Stupid lawsuit again...? by janrinok · · Score: 4, Insightful

      Apple deliberately made the update brick the phone if third party applications were installed

      How do you know? The upgrade might have had that effect but it might not have been deliberate, but simply the result of trying to apply an update to software that was in an unknown state because it have been modified by the user.

      --
      Have a look at soylentnews.org for a different view
    5. Re:Stupid lawsuit again...? by ciw42 · · Score: 5, Insightful

      I stand to be corrected here, but is there any *actual* evidence (apart from hearsay) that the bricking was deliberate. It seems to me perfectly understandable that if the software and configuration files on the phone aren't exactly as they were shipped, then an update could quite reasonably fail, and as the iPhone isn't a consumer product which allows the user to install new software, then there is no reason for Apple to develop updates which work with anything other than the default software shipped with the unit. It's entirely their baby, and unless the update causes problems on phones with their default install, they're not responsible for any problems you may have.

      We're not talking physical materials or workmanship here, we're talking about people changing the software on their phones, and that is something which goes against the terms of Apple's warranty for the product. Your car analogy isn't a particularly good one, as Apple aren't saying they won't repair a phone which has physical faults or non-software related issues. Apple are in no way responsible for the software if it's been modified by the end-user. This is fairly standard stuff in software development/support terms.

      Unlocking an iPhone isn't a simple process, and it's not something you'd do accidentally or casually without understanding what you were doing. Anyone unlocking their phone did so on purpose, and knew at the time they were invalidating their warranty. It's made very clear on every single website I've seen which details one of the approaches to doing this. If you got the instructions, then you knew the risks. Simple as. Anyone who's unlocked their iPhone is no longer entitled to support either, as they're not using their iPhone for the purpose for which it was intended.

  2. Watch them lose the case.... by 3seas · · Score: 4, Insightful

    ... and this will settle the matter once and for all.

    I mean when you have to buy numerous formats of a song because you are not allowed to pirate what you buy, to yourself for use on another device.... then of course At&T iphone lockin is acceptable.... If you want to use a different carrier you need to use a different format/device.

    Anticompetitive practices is the only thing to argue here, but if you bring in a bunch of other non-issues then you can make the case lose.

  3. Caveat Emptor by Nymz · · Score: 4, Insightful

    Caveat Emptor - let the buyer beware.

    Honestly, Apple has not attempted to deceive anyone on this issue, and they make it clear that service is with AT&T only. If you don't want to be locked-in with AT&T, then don't buy an iPhone. Period. If you still must absolutely have a class-action lawsuit, then do it against the Steve Jobs backdating accounting scandal.

  4. Bloody idiots. by ciw42 · · Score: 3, Insightful

    This lawsuit is just absurd.

    OK, so I'm with everyone else hoping that before long the practice of locking phones to specific networks gets outlawed, but in this particular case, Apple haven't done anything wrong.

    They are only responsible for providing updates which work with their software as supplied, and not software and iPhones which have been hacked specifically against Apple's advice, to get them working on other networks.

    If your phone gets bricked by an Apple update after you've unlocked it, then it's entirely you fault. No-one else's. You did something that you knew full well at the time you shouldn't have done, and let's face it, it's not a simple process, so there can be no possible claim that you didn't know the consequences of your actions, and if you didn't understand this process and the implications, then you're even more of a fool for doing it. You've learned valuable lesson here - don't mess with things you don't understand. You immediately voided your warranty, again something you were fully aware that you'd be doing, and began using it in a way it was never intended or designed to be used, so you're not entitled to support. And now you've came out of it looking like a cock. With no phone. You bloody idiot.

  5. DMCA Confusion by Nymz · · Score: 4, Insightful

    Except mobile phone vendor lockin is against the law.

    Is it? I think the current situation is as follows:
    • The DMCA has an exemption for users to unlock their own phone
    • But the DMCA still prevents sharing of code that circumvents locks
    • So while you may unlock it, you must be able to do it all on your own
    • Leaving Apple free to use DRM, to make exercising your rights very difficult
  6. Why is the iPhone any different than a computer? by LwPhD · · Score: 4, Insightful

    I really see no true difference between using your iPhone (with a carrier OF YOUR CHOICE) and hooking your landline (with a carrier OF YOUR CHOICE) through your computer's modem so you can use a software phone and answering machine. Also, how is it any different from using your laptop with a cellular card (with a carrier OF YOUR CHOICE) to get internet connectivity on the go?

    To my layman eyes, the law in this area seems ad hoc and gives special attention to handheld cellular devices. Fortunately, it seems likely that unlocking is legal. I seriously hope this case will be the first of many to push regulation of companies that maliciously sabotage their customers after they bought the product to maximize profit.

    I'm currently a very satisfied Mac user (I'm writing this post from a 3 year old PowerBook G4 17" that still runs like a spotted assed ape) but these sorts of moves sour me on AAPL. I'll give them a few chances to mess up and be forgiven, but as a computer savvy person who's primary love of Apple is for how they've beautifully wrapped what's under the hood, I can just as easily go right back to Linux where I came from. After all, that's what I use on the desktop and in the server rack already. Why is it, just when Microsoft seems to have shot itself in the foot with Vista and controlling what users do with their hardware, that Apple jumps right of the cliff with them?

  7. Apple could have avoided this by jdc180 · · Score: 5, Insightful

    If the software in the phone is in an unknown state, then don't allow the upgrade to run.

    Apple obviously wanted to brick the phones. Just about every other upgrade i've ever run checks the bits it's upgrading to make sure it's good to go.

  8. Re:OfCOM by GPL+Apostate · · Score: 5, Insightful

    The staff are actually quite good at matching the phone to the individual, it may not necessarily be the most expensive phone they have on offer nor might it be the coolest looking but it will be roughly what the customer is after.

    It sounds like the sales staff are active advocates for the needs of the customer, like they listen to what the customer needs and earn their salary by tailoring a package to meet those needs.

    That isn't allowed in the U.S. No Sales Manager would allow such a salesperson out on their retail floor. Here 'sales' is about maximizing return to the retail establishment at whatever expense. The customer is treated like a consumable.

    --
    Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
  9. Testing for the unknown by Midnight+Thunder · · Score: 4, Insightful

    Wasn't it announced *ahead of time* that the upgrade would brick unlocked phones?

    That sure sounds like premeditation to me.


    Nah, that sounds more like them taking into account that if you do some unsupported random modification, then there is no way for them to know what you did. And if they don't know what you did, how is the testing process going to know what to test for? Private APIs are always going to be changing, since they don't need to take into account third-party applications are using them and if they are they shouldn't be.

    If you hack something then you should accept the risks associated with it. Yes I believe Apple should be making the iPhone more open, but until it is anything you do which is not officially supported is at your own risk.

    BTW Haven't a number of people come up with solutions to unbrick the iPhone?

    --
    Jumpstart the tartan drive.
  10. Re:OfCOM by maxwell+demon · · Score: 3, Insightful

    Is there also a law that an unlocked phone must be cheaper than a locked phone plus contract?

    --
    The Tao of math: The numbers you can count are not the real numbers.
  11. Bricking not intentional by tgibbs · · Score: 5, Insightful

    What is now becoming clear is that many unlocked phones come through the upgrade unbricked, albeit re-locked. Considering that recognizing an unlocked phone should be a simple matter of a checksum, it seems clear that Apple was not intentionally "bricking" phones. There are reasons to believe that this is likely an unintended side effect of an update designed primarily to enhance iPhone security. If it was not intentional, Apple is in the clear, as they are under no legal obligation to debug an update to work with phones that have been modified in violation of warranty. And indeed, it seems that while Apple is under no legal obligation to do so, Apple sotres are restoring "bricked" iPhones. Moreover, it is not as if Apple failed to warn owners of unlocked iPhones that applying the update would likely harm their phones.

  12. Re:OfCOM by drsquare · · Score: 3, Insightful

    Why is it that every single thread about American businesses not having their own way in Europe ends up with comments like this? Is it a prick to the American ego that your beloved mega-corporations can't steamroll over the rest of the world like they can in the US?