Page 3 of 8 FirstFirst 12345678 LastLast
Results 21 to 30 of 71
Discuss According to apple store employee, 1.1.1 unlocks will be bricked in 3 months!?! at the General - Hackint0sh.org; Originally Posted by jhollington That doesn't sound like an organization who is going to plant ...
  1. #21
    Senior Professional Array

    Join Date
    Jul 2007
    Posts
    169
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    Quote Originally Posted by jhollington View Post
    That doesn't sound like an organization who is going to plant timebombs into their firmware to break or re-lock iPhones....
    No-one here is actually suggesting they are doing that. The whole point of this thread is that Apple/AT&T employees are saying that they are. Given we all agree this is a lie, then if this isn't FUD what is.


  2. #22
    Senior Professional Array

    Join Date
    Sep 2007
    Posts
    169
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    We all know that this is a DAMN LIE to scare you. Apple Store workers said that it was impossible to unlock 1.1.1. They were wrong. It will be done by The DEV TEAM.

  3. #23
    Rookie Array Gricko666's Avatar

    Join Date
    Oct 2007
    Posts
    17
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    If they did that, they would be first mobile phone manufacturer to do something
    so radical. Product just entered market recently, it would be suicide to do that
    upon entry on market, especially if they wanna reach those 10 mills.

    Since they asked you first do you plan to unlock etc (and you would be taking
    money away from them by doing so), basically they need to turn you away
    from buying in smart and polite way. A test and a good one...average consumer
    is not informed at all about unlocking etc, they know someone that can do it for $
    and thats about it. And ofc he would chicken out and give up on buying.
    On other hand if your intentions are "true" and you like paying 2000$ for phone,
    you will buy it without doubt.

    Cat and mouse game indeed.

  4. #24
    Senior Professional Array

    Join Date
    Jul 2007
    Posts
    195
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    16

    Default

    Quote Originally Posted by Tonyd View Post
    No-one here is actually suggesting they are doing that. The whole point of this thread is that Apple/AT&T employees are saying that they are. Given we all agree this is a lie, then if this isn't FUD what is.
    My point is that there is rampant paranoia out there, and there are people who have been on this rampage believing that Apple is in fact deliberately trying to break unlocked iPhones.

    This isn't the case.... Trying to prevent iPhones from being unlocked in the future? Sure. Trying break existing phones? Hardly.

    It's certainly FUD, but it's also coming from a low-level retail store employee. Most informed consumers don't listen to what the employees at Best Buy tell them, so why should an Apple Store employee be any different?

  5. #25
    Senior Professional Array

    Join Date
    Sep 2007
    Posts
    169
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    This is like.... I'm buying candy. The store owner says that i will get food poisoning 3 weeks after i eat the candy. would you eat the candy?


  6. #26
    Newbie Array

    Join Date
    Oct 2007
    Posts
    1
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Just my 2 cents, but I think that the Apple Store Employee actually meant that in three months there will be another Firmware Update that will likely brick unlocked phones! Which is exactly what happened with the 1.0.2. -> 1.1.1 update.

  7. #27
    Guest Array izim1's Avatar

    Join Date
    Sep 2007
    Posts
    108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by Magicpie2007 View Post
    i believe you, i know what these kind of people are like, ignore that guy There are alot of overly aggressive people on this site that really do need removing
    that's funny. the same thing can be said for the ones that start the same paranoid filled threads that have already been posted over and over again. and how about the ones that start threads asking the same questions that have already been asked and answered before just because its easier than using the search function? some would argue that those are the ones that need to be removed.


    *cough* but im not saying any names *cough*

  8. #28
    Guest Array izim1's Avatar

    Join Date
    Sep 2007
    Posts
    108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by jhollington View Post
    There's a lot of rampant paranoia going around about the idea that Apple is going to deliberately damage iPhones that have been hacked or unlocked.

    However, the reality is that even the v1.1.1 release does not indicate anything of the sort. Consider this...

    Firstly, if Apple really wanted to lock down unlocked iPhones and/or penalize users for unlocking, they would have targeted all unlocks, not just the iUnlock/AnySIM methods. Apple mentioned these first two by name, and significantly omitted any mention of the IPSF solution.

    It would not have been impossible or even at all unreasonable for a firmware update to target the IPSF solution just as easily, if Apple were targeting unlocked iPhones. A simple baseband/modem query will return the unlock status, and even if IPSF uses a "legitimate" unlock method, the reality is that there aren't supposed to be any unlocked iPhones out there right now.

    The reality is that the iUnlock/AnySIM solution modify the seczone/EEPROM in such a way as to cause the "stock" baseband firmware to return an error condition that makes the iPhone unusable with any SIM. This is not a v1.1.1 specific issue -- restoring the "stock" v1.0.2 firmware will result in the exact same problem. The difference is that you can recover from this in v1.0.2 simply by running iUnlock again and restoring the patched firmware that understands the information in the seczone and returns the iPhone to an unlocked state.

    However, when updating to v1.1.1, of course the firmware is updated, and the iUnlock-patched firmware is replaced with "stock" firmware. The problem in v1.1.1 is that until just a couple of days ago, there wasn't even a way into the OS, much less a patched v1.1.1 firmware that could be applied to fix this issue. The inability do downgrade the baseband firmware (under any conditions), further complicates this issue.

    Now, Apple certainly could have taken steps to repair this situation as part of the firmware update process, but really why should they? Even if Apple was feeling magnanimous, it's just not good business sense to spend research, development and testing time to solve a problem that should not have occurred in the first place. Not to even mention the possible unintended consequences (side-effects) of doing this as part of the firmware update process.

    Likewise, it's not good business sense for Apple to spend money trying to defeat unlocks that haven't otherwise modified the iPhone from a standard software/firmware state.

    In the end, Apple tightened their security with v1.1.1 to prevent future hacks, but otherwise took a very neutral approach to the entire unlocking issue.... They provided a stock firmware update with no specific intention of either locking or bricking any phones... If replacing the firmware happens to brick your phone because of what iUnlock did to the seczone, then that's not really Apple's problem, nor is it their responsibility to address this issue.

    But let's get away from this nonsense that Apple did anything to deliberately break any iPhones, as that's simply not rational... They certainly could have done this if they wanted to.... However, instead, they provided more than adequate warning before the v1.1.1 update, and even in the midst of the update process (nice big bold warning letters), advising people that the update may cause problems for unlocked iPhones.

    That doesn't sound like an organization who is going to plant timebombs into their firmware to break or re-lock iPhones.... Merely an organization that is going to continue to release neutral updates that are only designed and tested for the stock firmware that the iPhone was shipped with, and was supported with.


    (Consider this as a reasonable analogy... If you modified the BIOS in your PC or Mac with unsupported hacker code to overclock the processor or otherwise enable some unsupported feature, and then your entire computer crashed because you tried to apply an OS update in this situation, would it really be Microsoft or Apple's fault?)
    dude how dare you come into this thread and use reason to try and make sense?! just who do you think you are? you should be banned.

    BTW if you have an imac or macbook apple is watching you right now through your isight camera.

  9. #29
    The Man Array aviegas's Avatar

    Join Date
    Sep 2007
    Posts
    1,108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    73

    Default

    A street seller of fake iPhones told a friend of mine not to by the original thing because he heard from a friend that works for an Apple store that the next iPhone firmaware upgrade will contain code that on boot will check the unlock status and if the phone was unlocked or the signature of any file did not match (jailbreak and activation), the firmware will cause the battery to self explode!



    Sorry I could not resist the joke!

  10. #30
    Professional Array

    Join Date
    Sep 2007
    Posts
    85
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    11

    Default

    I was told something similar to this also but an apple employee at walden galleria in buffalo,NY. He said in 3 months they will have forced updates where if you don't update, you can't sync your phone with itunes.

    Its weird how both reps said the 3 month mark. Obviously something will happen later on down the road but nothing to this extreme.


 

 
Page 3 of 8 FirstFirst 12345678 LastLast

Similar Threads

  1. Replies: 0
    Last Post: 07-21-2011, 11:00 PM
  2. Slashdot: Apple Store Employee Attempts To Form Union
    By hackint0sh in forum Latest Headlines
    Replies: 0
    Last Post: 06-13-2011, 01:20 AM
  3. Replies: 0
    Last Post: 02-22-2011, 04:40 PM
  4. Replies: 0
    Last Post: 02-17-2011, 09:50 PM
  5. Replies: 0
    Last Post: 12-29-2010, 09:00 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Powered by vBulletin®
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Search Engine Friendly URLs by vBSEO
(c) 2006-2012 Hackint0sh.org
All times are GMT +2. The time now is 11:43 AM.
twitter, follow us!