| || |
Re: How to update to Jelly Bean 4.1.1 via Kies
Well that was three hours of my life wasted that I will never get back. Kies recognizes my phone but doesn't acknowledge an available update. So I called AT&T. First woman I spoke to was very nice. She tried to connect remotely to my phone to no avail. (That's the second time in a month that's happened.) She checked all her available diagnostics and could find nothing wrong. Finally, when I told her that I was not using the most recent version of Kies, because it was such a pain in the *** to update, she suggested that that must be the problem. So, I said fine, hung up and went through the process of uninstalling Kies through the control panel, downloading the new version from the Samsung website, installing it, going back again and uninstalling the newly updated Samsung mobile device driver, reinstalling the version 184.108.40.206 version (because otherwise I get the Hardware ID missing error), disconnected the computer from the internet, connected the phone and let it update, reconnected the computer to the internet and restarted Kies. And I got a snazzy new version of Kies that still didn't acknowledge any available firmware updates. So I called AT&T back. The guy I spoke to this time looked at my notes from the previous call and I explained everything I had done since and after about 20 minutes he came to the conclusion that the problem was with Kies and not the phone. So he connected me directly to a Samsung technical rep (at least I didn't have to wait on hold at this point). After about a half-hour of talking and trying different things with this person, he acknowledged that he had no idea what was going on or what to do about it and so he wrote a trouble ticket and passed it up to level 2 support. He then put me into their line and told me that someone would be with me shortly. Which was where I waited on hold for 55 minutes. When I finally spoke to someone, she determined in about 30 minutes that the problem likely was with Kies and that there was nothing she or I could do about it. She said she "would send a ticket up to the Kies developers to let them know there was a problem." I had steam coming out of my ears at this point and I wanted to ask her how the f*** that would help me, but I didn't go there. At that point, I did ask her if a copy of the update was available on the Samsung website so that I could update it using Odin. She kind of chuckled and said no, because it's not "supported." I think if she could have, that's exactly what she would have recommended. I was going to root the phone in a few weeks anyway, once its out of warranty in mid-June, but I think it's time. The really infuriating thing is that I spent so much time with AT&T's and Samsung's bull**** that I don't have time to do it right now or I would. It'll probably be another week. With the hundreds of posts online about the myraid problems with Kies, the only way Samsung could not know about them is if they go to great extremes to avoid knowing about them. Did I say three hours? It was probably closer to four. I wish I could reach through the phone and slap somebody at the other end.