10.1.1 Permanently Killed my iPhone

[Nancy bout]

That doesn't sound right YOU should not be out an iPhone over that? Wow!

 

[Aragornii]

Interesting. Are you within the two week return period for the new phone? You must be, right? Your original post was only 10 days ago.

Can't you rerun the new phone you got? And, yeah, typically it's quite hard and usual to actually brick an iPhone with an update--it can certainly happen, but even then in enough instances it's some installation/software weirdness and it's not actually bricked.

I'm out of the country and sending my phone back is not an option right now.

 

[simonmet]

That was some clsss A bull sh|t from the Apple Store described in the opening post. No way I would've believed that a 1-year old phone in good condition (and without liquid damage) was broken and needed replacing, and even if it was what does that say about the reliability of their super-premium phone that it would die after just 1 year? The fault was overwhelmingly theirs by software bricking the phone during the upgrade process and in either case the staff should've been apologetic and offered you a replacement. Perhaps you looked like buying another phone was no problem for you and their pressure sales tactics obviously worked.

It makes me sad to think how many other unsuspecting people Apple screws around by pulling crap like that. If I was a cynic I'd wonder whether software bricking a just out-of-warranty device isn't just a little too convenient!

If I were you I'd go back (eventually) to the shop, find out who gave you that advice and then call Apple Support to report it and seek resolution from them such as accepting the replacement you bought. Perhaps also try speaking with the store manager and ask if it's their policy to give false advice about problems for which they haven't performed a diagnosis and have no proof.

Disgusting!

 

[Statusnone88]

So here's an update on this. To answer all the questions, yes, I tried every manner of resetting to factory settings, and also tried manually downloading the update and installing via iTunes.

None of that worked and Apple was firm that the phone was unusable (as stated in one of the earlier posts, they claimed that it wasn't the update that killed the phone, but the update uncovered a defect in the phone). So I bought a new phone and stuck mine in a drawer. This week Apple pulls 10.1.1 and releases a new update, so I tried that on my broken phone and lo and behold it works fine. So now I'm stuck with two phones, and Apple clearly was in the wrong about it not being the update that bricked it.

Will have to pursue some sort of compensation but I won't hold my breath.

What an absolute load of horse ****. They were in the wrong and now you're the one who pays the price (literally). I'm sorry this happened OP, but I wouldn't over burden yourself with stress. It already happened, it sucks that it did, and move past it. If you plan on sticking with Apple products, I recommend AppleCare+ for situations like this in the future.

Sucks having to add $130 to the price of your phone for an additional year of manufacturers warranty (and accidental damage, of course), but it will alleviate the stress of having to deal with something like this in the future.

 

[sethlution]

As someone here mentioned already, have you tried plugging it in while in DFU/Recovery mode? That seems to fix all my boot-loop related problem before.