jh
Member since: Feb 6th, 2006
jh's Latest Comments
Blog Activity
| Blog | # of Comments |
|---|---|
| TUAW.com | 21 Comments |
| Engadget | 5 Comments |
| Joystiq Xbox | 1 Comment |
Member since: Feb 6th, 2006
| Blog | # of Comments |
|---|---|
| TUAW.com | 21 Comments |
| Engadget | 5 Comments |
| Joystiq Xbox | 1 Comment |
Giveaway: Two new Element carbon-fiber iPhone 4 cases
Jun 2nd 2011 9:04AM (TUAW.com)Enter to win a copy of the Sparrow email client for Mac
Feb 9th 2011 6:56PM (TUAW.com)TUAW review and giveaway: OtterBox Defender / Commuter for iPad
Jul 18th 2010 2:15AM (TUAW.com)iOS 4 is now live
Jun 21st 2010 1:23PM (TUAW.com)Konami takes Harmonix to court over Rock Band
Jul 11th 2008 12:00PM (Joystiq Xbox)Phoenix, Arizona Apple Store planned
Jul 7th 2008 6:34PM (TUAW.com)VBA to return in next version of Microsoft Office; SP1 released
May 13th 2008 2:04PM (TUAW.com)For more discussion of this issue - http://groups.google.com/group/microsoft.public.mac.office.word/browse_thread/thread/dfeec048e739346d
How to relock your iPhone before the firmware update
Sep 25th 2007 9:32AM (TUAW.com)ATT (to my knowledge) does not charge for SIM cards, so this was not an inducement to cheat them out of anything. Playing dumb simply avoids a potentially awkward conversation with an underpaid and probably equally knowledgeable retail employee.
While I don't support the approach involving what could easily be considered credit fraud, I do take issue with the rest of your comment as it is couched in fallacy and ignorance.
First, your argument assumes there is free will vs. predestination (haha).
Second, in order for people to knowingly violate their warranties they must have read them. Most don't. Perhaps they should have reasonably expected to void (aka negligently voided) their warranty... but knowingly? You're aiming high with that one. I'd even allow recklessly voided.
Third, being warned at every stage of the possible bricking consequences is also a high standard. Can you say that with substantial certainty? Could it even be true? Many warnings were simple, stock disclaimers that if anything went wrong - the person(s) who wrote the software would not be liable. As to some sort of discussion regarding the potential outcome being a "bricked" phone really happen immediately (or at all in some cases) at every step. Hindsight is 20/20, but forging your argument by changing or inventing the past is just intellectual laziness.
Fourth, again with the overreaching - shamelessly? Really? You could detect that in the comments? You should have stuck with just "declare" as it would have been more honest and accurate.
Fifth, "undo the consequences of your own intentional actions." Yikes - where to begin? A) There have been no consequences yet and it is possible that there will never (or close to it) be as no firmware has been released to cause an issue. B) Taking action to alter or reverse prior action is suddenly not an option for people to consider, let alone choose to do? That's absurd. If there's an approach that effectively replaces every modification with stock, factory-fresh code/firmware/settings/etc - what's the problem? This argument would be different if it were a hardware modification, but with software not so much. Apparently this amorphous concept was lost upon you, as was the point of a warranty. If, using the approved software and configuration there is a problem with the device covered under warranty - it's *SHOCK* covered under warranty. If you made a modification to the software that is causing the problem and the modification is still present *SHOCK* it's not under warranty. However, if you (are able to) restore everything back to the proper software and it still has the problem - it's likely not the modified software at fault and should be covered as something is obviously wrong with the hardware. The notable exception to this would be if the modified software caused issues related to the device overheating or acting in some way that would lead to physical damage. Playing tic-tac-toe, Excitebike, using a terminal program, or *gasp* unlocking the phone does not fit the bill. Would you really try and argue that if an issue arose where significant numbers of "hacked" and normal iPhones experienced headphone jack failures, that it should not be under warranty due to software modifications? Whoops - we reached the logical boundaries of your argument. Sorry about that.
How to relock your iPhone before the firmware update
Sep 25th 2007 12:44AM (TUAW.com)How to relock your iPhone before the firmware update
Sep 24th 2007 8:09PM (TUAW.com)This method seems to nuke the ICCID information for the SIM card as far as the iPhone is concerned. I am not certain if this would occur if you can manage to remove the SIM card at some point during the flashing process or if there is any real approach to avoid this end result.
The SIM card, while unusable in the iPhone, still worked in my old blackberry... go figure.
Anyway, the theoretical solution is to stroll into your local ATT store, play dumb, and get a fresh, new & most importantly free SIM card. I would recommend doing this sooner than later before a memo goes out to stores regarding a potential flood of iPhone owners experiencing this mysterious problem with SIMs having unknown ICCID issues...
However, in my particular case, iTunes sees this new SIM as an unsupported card.