Bricked during GDR 2

[etad putta]

Dagnabit, SHAWN THE IT DIRECTOR DOES NOT NEED YOUR WEAK AND PUNY HELP WP CENTRAL! How DARE Nokia provide a solution to a problem, that according to SHAWN is all in our heads. 3 thousand people have read this thread...3 GRAND. Hell, the phone barely has that many OWNERS. But its ALL IN THEIR HEADS TOO. If AT and T is causing the issue with the update (which honestly, I don't doubt), are the Verizon folks having issues with any of their devices? I ask that in all earnest, as I normally loathe Verizons data caps, but if their phones are more stable WP formats, it's worth the consideration.

I think it is still a very nice phone, it just has some reset\update issues that can hopefully be resolved in the near future.

 

[jojapath]

Note the word "UPDATE" notice the lack of "ATT ONLY"

Well, the proof is there my friend. Read this forum (or all the other forums on the net if you want) from the past 2 months when the update was released for all other carriers and you won't find any other carrier but AT&T having the bricked phones issues because of the GDR2 / AMBER update. Having bricked the phones because of a hard-reset, you will find many but not because of the update.

Hey! I haven't even read 1 thread from a Verizon customer complaining of having bricked the phone while updating to GDR2 / AMBER!!!

Conclusion and I repeat: AT&T tampered the firmware (taking out data sense, etc...) and made it unstable and without doing the proper testing, released it to the public!
Making AT&T customers their guinea pigs...

 

[etad putta]

Well, the proof is there my friend. Read this forum (or all the other forums on the net if you want) from the past 2 months when the update was released for all other carriers and you won't find any other carrier but AT&T having the bricked phones issues because of the GDR2 / AMBER update. Having bricked the phones because of a hard-reset, you will find many but not because of the update.

Hey! I haven't even read 1 thread from a Verizon customer complaining of having bricked the phone while updating to GDR2 / AMBER!!!

Conclusion and I repeat: AT&T tampered the firmware (taking out data sense, etc...) and made it unstable and without doing the proper testing, released it to the public!
Making AT&T customers their guinea pigs...

http://forums.windowscentral.com/no...em-after-updating-lumia-920-amber-update.html

 

[etad putta]

Flashing (updating a firmware) a device has nothing to do with hard-resetting it.... At all.....

And I repeat, The GDR2/AMBER update went almost flawlessly on all the other carriers in the world! Just look at the forum and you'll notice that the only ones who are having their phones bricked after flashing are AT&T customers!

http://forums.windowscentral.com/no...nning-gears-lumia-521-after-amber-update.html

 

[etad putta]

Of course you won't find anything on the 1020. GDR2 / AMBER is already installed on it!

The 1020 hasn't received any kinds of update yet.

Spinning gears: Nokia Lumia 521 | T-Mobile Support

 

[jojapath]

http://forums.windowscentral.com/no...em-after-updating-lumia-920-amber-update.html

A total of 20 posts on this thread and only the first 2 had their phones bricked by resetting the phone while updating!

Just read the thread man!

 

[jojapath]

Spinning gears: Nokia Lumia 521 | T-Mobile Support

6 posts and only the first had the problem (out of probably THOUSANDS !!!).... Are you kidding me?

I guess the other carriers' customers must be shy then !!!! :wink:

 

[etad putta]

Actually, I think the problem is with AT&T. They had 2 months to change some stuffs (taking off data sense, etc...) in the ROM and it made it unstable.

The GDR2/AMBER update went almost flawlessly on all the other carriers in the world!

Lloyyd
Posts: 50
Re: Stuck on running gears for over 8 hours!! Nokia Lumia 920
[ Edited ]
Options

‎2013-09-09 11:40 - edited ‎2013-09-09 11:51

guys i really need your help.. :smileysad:



My red L920 with amber update is now at the spinning gears for 3 days(phone offline and several restarts done).. and the key sequence didnt work for me yet..
any informations that this won't work with the amber update or something? also my 920 is from germany with no branding on it.

I tried to enter the key sequence a few times after it rebootet with volume down + power off.. at the blackscreen, at the nokia logo - nothing worked yet..

I really need the phone to work :-(

 

[jojapath]

Lloyyd
Posts: 50
Re: Stuck on running gears for over 8 hours!! Nokia Lumia 920
[ Edited ]
Options

‎2013-09-09 11:40 - edited ‎2013-09-09 11:51

guys i really need your help.. :smileysad:



My red L920 with amber update is now at the spinning gears for 3 days(phone offline and several restarts done).. and the key sequence didnt work for me yet..
any informations that this won't work with the amber update or something? also my 920 is from germany with no branding on it.

I tried to enter the key sequence a few times after it rebootet with volume down + power off.. at the blackscreen, at the nokia logo - nothing worked yet..

I really need the phone to work :-(

Again. just one... Not thousands like the AT&T update.

He even had to come to this forum as he probably couldn't find anything related to this in a German forum!

 

[etad putta]

"Well, the proof is there my friend. Read this forum (or all the other forums on the net if you want) from the past 2 months when the update was released for all other carriers and you won't find any other carrier but AT&T having the bricked phones issues because of the GDR2 / AMBER update"....WRONG only one example was needed to prove this statement incorrect. 3 were provided. Enjoy your day.

 

[jojapath]

WRONG

You must be working for AT&T !!!

Anyway.... To be fair, the reality is that on the other carriers, maybe 1 out of 1000 had this problem and most of them was because of resetting their phone while updating...
On AT&T, it seems like 1 out of 10 has this problem! Their phones were working fine before the update or not?

So the problem is definitely firmware-related because AT&T PLAYED with it.

 

[etad putta]

You must be working for AT&T !!!

Anyway.... To be fair, the reality is that on the other carriers, maybe 1 out of 1000 had this problem and most of them was because of resetting their phone while updating...
On AT&T, it seems like 1 out of 10 has this problem! Their phones were working fine before the update or not?

So the problem is definitely firmware-related because AT&T PLAYED with it.

Ok your turn. Show some proof that the items removed will cause an update restart\gears problem. What items in the update were played with and how do they cause this problem. Thanks in advance.

 

[jojapath]

Ok your turn. Show some proof that the items removed will cause an update restart\gears problem. What items in the update were played with and how do they cause this problem. Thanks in advance.

First of all, DATA SENSE was taken off of the update .... And, can you get into the field test??? (By dialing ##3282#) If not, that was taken off too ... And probably some configurations etc.... And, everybody knows that if you tamper with an original firmware you risk making it unstable.

Like a computer, go into your BIOS settings and start changing things in there. you risk making your computer unstable and will have to go back to the BIOS and choose the default settings for it to be stable again ...

 

[etad putta]

First of all, DATA SENSE was taken off of the update .... And, can you get into the field test??? (By dialing ##3282#) If not, that was taken off too ... And probably some configurations etc.... And, everybody knows that if you tamper with an original firmware you risk making it unstable.

Like a computer, go into your BIOS settings and start changing things in there. you risk making your computer unstable and will have to go back to the BIOS and choose the default settings for it to be stable again ...

It would appear to be "probably" and speculation. I wish i could see actual solid information rather than generic statements. You could be right, but alas, without any proof...this conversation has become boring anyhow.

 

[jojapath]

It would appear to be "probably" and speculation. I wish i could see actual solid information rather than generic statements. You could be right, but alas, without any proof...this conversation has become boring anyhow.

Well, AT&T will never admit any wrong doings that's for sure.

But if you ask me, they probably were so busy adding their bloatwares, removing apps and altering configurations on this firmware that they forgot to change the installation process and it got stucked at trying to install apps that are no longer there and bloatwares not compatible with this new firmware version.

Also, Don't forget that this is a new OS even for the AT&T techs ...

 

[Sean Miller4]

AT&T and every other phone supplier has no idea about any phones, they are not trained in electronics they are hired off the street with no experience and paid crappy salaries and get very little training, they have no idea what they are talking about ever, that being said yes at&t has had way more issues than anybody else and took way longer for thier update and its not just stuff removed they add stuff in, because they want to be able to charge for every little thing, so every carrier has a different software unless its an international phone, like jojo said almost no incidents on international phones try and find a problem, but i'm sure they are a few out there. BUt to tell you the truth most of the at&t problems are user related at&t might be a slower update than other carriers but most are not bricked because of the phone its because software the user installed, impatience and a number of other factors. Nokia this fix out because too many dumb people out there with no patience probably arent even doing the sequence right to begin with. This problem should be less and less with gdr3 and 8.1, but for now its pretty common on at&t 920 but easily fixed.

 

[Khyzersoze]

Well, got my replacement phone yesterday. Finally got GDR2+Amber on it and that went fairly smooth.

Today I did the GDR3 update and that went even smoother. Happy camper now!

Phone = ATT Lumia 920

 

[dkp23]

So on day two of spinning gears of death on my dads 920, i think i will remain patient for another 32 days, is that enough?

 

[boo516]

I love that GDR 3 took 15 min to install on my new 920 and GDR2 took 40 min on the same phone.

 

[srmiller82]

Gdr3 isn't a firmware update just software it should take no longer than 20 min. That's expected