1. Download our Official Android App: Forums for Android!

Support IMPORTANT: Samsung Infuse UCKE3 (firmware) update

Discussion in 'Android Devices' started by dlee1001, Jul 10, 2011.

  1. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    Is anyone else having the same problem as I am?

    Whatever I do, I can't get the 8 MB maintenance update that was released over a month ago. I tried installing KIES Mini from the i897 (a Captivate phone) and all it says is that the firmware is "unregistered," probably because there's no supported driver for the i997, the Infuse.

    Also tried installing the regular KIES, only to have it say that the device is not supported in the current version of KIES.

    Yes, I've done the Settings>Software Update a GAZILLION times, only to have the exact same result each time I do it:

    "Connection failed

    "Unable to connect to the AT&T server."

    Just recently did I find out that you can force the phone to check for updates by doing *#*#2432546#*#*. I've tried that several times and then went to Settings>Software Update (after it said "checkin succeeded"). No dice. Epic fail.

    And yes, I've tried calling AT&T about it, which had very mixed results; some say that there is no update. Others do recognize that there was a (maintenance) update released on June 3. That's all they said. They tried to get me to turn my phone off, clear data for the DM (or the other way around), and then check for updates. Still an epic failure.

    They've tried filing a case for my problem, but they closed it because they "didn't have enough information," despite me explaining in detail to the tech support reps.

    Samsung made me restore to stock settings, but that had no effect whatsoever in terms of firmware updates.

    A month and a week has passed with no update notification of any kind and with constant (and gradually annoying) connection error messages.

    I tried changing the time and date (the date I tried setting forward a year, then tried it with it set to the day after the update was released, June 4) and then check for updates. Guess what! Fail!

    Again, please help me. This is driving me crazy.

    Not the update; I personally don't care about the minor maintenance update itself. My top concern is that this problem may adversely affect the way all updates on my phone get installed on my phone. If this error message is persistent even when Gingerbread comes out for this phone, I won't be able to enjoy the full capabilities of this phone, not to mention that it's a 4G phone, which may be fully enabled through another OTA update, which, based on the current and past results, will also fail.

    Please help. If there is anything that, based on this information of what I've done to try and get the update, I haven't tried yet, please tell me and tell me how it can be done so that my poor phone will have itself updated.

    Thank you.
     

    Advertisement

  2. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    Hi dlee1001,
    You already know I've got the same issue, so I have nothing to offer in the way of a fix. I've been through the same ringer with no success. I suspect there are others with this issue, maybe not on this forum, and maybe not even aware of the problem. I don't know why we are getting this error, but I gave up on the theory that it is the phone a long time ago. What I've done as a remedy is to stop worrying about it. Hopefully, it is still coming. If not, I'm hoping the next one will. If not, at this point I'm not sure how much it really matters.

    If this is really bothering you, try taking it back as defective, if you can. Probably too late for that. See if ATT or Samsung will send you one that has been updated in exchange. Can either of them "service" your phone to install the update? Of course, that would probably mean sending it back to them. I am surprised, if it is true, that they can not force the update, or perform some sort of diagnostic to determine why the connection fails. The support people I spoke to ran through a whole battery of things, several times, but I'm not sure how much they can diagnose the problem. Actually, I thought that was the reason for openning a case, so the engineers get involved, but I never heard from them. I don't even know whether they looked at it.

    Again, not much I can offer to help. If we're the only two people in the whole world that this has happened to we must be pretty special. If anything happens, or changes for me, I will let you know.
     
  3. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    I've yet to get a call from AT&T about the matter. If I'm in a good mood later, I might get in touch with either AT&T or Samsung (or both). If I do, I'll nearly demand that a fixing case be filed for me and that this matter/case does not end unresolved. It's been getting engaging that I can't even get any of that thing (I don't even want to say the same of that app anymore) to work so I can get that stupid update. More updates on this later when my contact with them ends. I'll explain in detail everything I did to try and get that update, but to no avail.

    If this somehow doesn't fix the problem, I'm going to follow your advice and just not worry about it. But I'm taking that as a last resort; if all fails, then I have no choice but to live with what I have, regardless of how annoying it may get. Maybe I'll get it some day, maybe I won't.

    BTW, have you tried the *#*#2432546#*#* method yet, as I mentioned above? Not that there's any point in doing so; I tried it numerous times with the same results.
     
  4. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    Yes, I did try sending that code, twice. I got the same "checkin succeeded," which brings up an interesting question. I'm not sure what the code does that is different (if different) than checking for updates from the settings menu, but if it is connecting to the same ATT servers then isn't it intersting that we're getting a different response, one that would indicate no problems. What does "checkin succeeded" actually mean? Assuming it is not just another poorly worded response, I take it to mean that it connected and there is nothing to be done. In other words, if I didn't know there was an update available this would tell me everything is wonderful. But, was it actually looking for updates, or just testing the connection? If indeed it was checking then why didn't it find it? If nothing else, it would at least confirm that it does connect, and maybe strengthens the theory that either our phones are not due for the update, or it thinks they are already up-to-date. I once asked a tech person if it is possible that it only checks the firmware version to determine if an update is needed. I asked this because a Samsung person said I didn't need the update based on me telling her I had firmware version 2.2.1. The problem with my theory is that I assume everyone started with 2.2.1, so why have other people gotten the update. Is there a difference with the version we have? I don't know.
     
  5. kubuli

    kubuli Lurker
    Rank:
    None
    Points:
    6
    Posts:
    1
    Joined:
    Jul 12, 2011

    Jul 12, 2011
    1
    1
    6
    I live in northern VA and had the same problem; but went to NC for the weekend and it updated right away. So I don't believe it's the phone; but the AT&T server.

    When you finally get the update your settings should have:

    Baseband ver. I997UCKE3
    Build number FROYO.UCKE3
     
    somanyapps likes this.
  6. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    That's interesting. I'm probably not far from you, near Fredericksburg, VA. I wonder if a trip to Richmond, for example, would be enough to get me into a different area? Hadn't really thought about going "far" from home to try it.
     
  7. boxer0987

    boxer0987 Lurker
    Rank:
    None
    Points:
    5
    Posts:
    6
    Joined:
    Jul 8, 2011

    Jul 8, 2011
    6
    0
    5
    I've tried the update and it says I have latest release but it is not the e3 that you post it should be it is still the d5. Does anyone know what the update is for. Something to do with 4g maybe. I wish it would make this phone get better service cause I'm probably going to have to take it back which sucks cause this phone is awesome!
     
  8. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    There was a post somwhere that gave some details about the update, but I don't remember where I saw it. A search will probably bring it up for you. It is a small update. I don't think it had anything to do with providing 4G capability, but might be wrong about that. I was told, and I think read as well, that it is not an important update, but I know people like to have the latest, me included.

    Regarding your service, do you see a definite reduction in quality of the service with the Infuse? I've been a little suspicious at times, but frankly, I had problems with my previous phone on occassion. So, I can't say with any certainty that the Infuse is really any better or worse as far as making phone connections or dropping calls.
     
  9. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    Maybe me living in Maryland is to blame? That sounds dumb; we shouldn't just not get a software update based on where we live!


    And, somanyapps, I live in a basement, so I don't have the best reception there, topping out at 3 bars if I'm like all scrunched up on a window. Other areas in the basement, I get anywhere from no service to 2 bars. But if I go outside right where I live, I can get a maximum of 4 bars.

    I don't know if this is suspicious or not (it probably isn't), but it seems like every time I ride in someone's car and look at my phone's reception, the signal strength loves to fluctuate--sometimes significantly for the better or for the worst.

    And there's one place where I can hardly get any data: there's a Costco warehouse store about 10-15 miles away from where I live, and every time I go in there, I always get the E icon instead of the H+. But I guess that's just the way the store was structured. I get H+ again right away if I go outside.

    Again, not sure if any of this is suspicious, but it's just an FYI.

    Signal strength seems be almost irrelevant to our ability to get the update. I say that because it doesn't seem to matter whether I have a maximum 5 bars or only 1-2 bars. The same connection error message still appears, no matter where I am in Maryland.

    I'd just love it if AT&T finally rolls the update out to the Maryland and Virginia residents. That'd work wonders. Yes, I'm one of those people who like to have the latest version. If I don't, there's always something inside of me that bugs me.
     
  10. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    It is curious that three people in this thread reporting the problem live within a relatively short distance from each other. Maybe just coincidence. Of course, kubuli got the update when he went to NC. Is that because he was in NC? Maybe we need to go to NC and test out kubuli's experience.

    dlee1001,
    I don't live in a basement, but I don't get great reception in my house either, and even get E (I think that's the Edge or 2G network) from time to time. I was told that I would not get the OTA updates if connected to the E network. But like you, I generally get H+ when outside, and not far from home get 4 and 5 bars, so should not be a problem.

    I understand the desire to get the latest. As we've discussed, it's probably less about the update itself and more about the inability to get the update being an indication of a problem with the phone. And will we be able to get the big updates in the future?
     
  11. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    Exactly! That's the concern I'm talking about! Now I have something new to tell AT&T (about how some people living in only certain areas got the update) when I try to contact them and go through all of that. But now I have a bit of renewed hope. Let's continue to update each other on new information. I know I will.
     
  12. boxer0987

    boxer0987 Lurker
    Rank:
    None
    Points:
    5
    Posts:
    6
    Joined:
    Jul 8, 2011

    Jul 8, 2011
    6
    0
    5
    When I have service the call quality is perfect. The problem is when I'm at work I lose service completely in the only area of the building I am allowed to make calls. I took my old phone's in today to test them. A samsung impression and samsung go phone and neither had issues losing service. They would hang on to 1 or 2 bars. The infuse will not. Also I have noticed that the signal strength is very jumpy. Don't understand that. And why is the wifi so week. If I step out my house I lose connection sometimes. My wifes phone stays strong with an excellent connection.

    The phone is awesome just in my certain circumstance I might have to return it. Sucks big time.
     
  13. trusktr

    trusktr Newbie
    Rank:
    None
    Points:
    16
    Posts:
    23
    Joined:
    Jul 14, 2011

    Jul 14, 2011
    23
    2
    16
    I just updated my phone yesterday fine with no problems. Got the brand new Infuse last week. I have UCKE3 now. That's the only thing i noticed that changed I think.

    You can't get UCKE3? That's so strange! I wish I knew what is wrong.
     
  14. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    trusktr.
    I wish you knew what is wrong too. :)
     
  15. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    What state do you live in? Our current "obsession" is that we didn't get the update because of what state we live in.
     
  16. boxer0987

    boxer0987 Lurker
    Rank:
    None
    Points:
    5
    Posts:
    6
    Joined:
    Jul 8, 2011

    Jul 8, 2011
    6
    0
    5
    Update. I got the update this morning. Tried to connect and it did. I live in TN.
     
  17. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    Did you get your first DM notification this morning when you got that update? Like was it the first time you saw it?
     
  18. boxer0987

    boxer0987 Lurker
    Rank:
    None
    Points:
    5
    Posts:
    6
    Joined:
    Jul 8, 2011

    Jul 8, 2011
    6
    0
    5
    I haven't had any notifications just new there was an update from reading here.
     
  19. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    So now my question is this: Why is it that those who live in closer proximity to the Carolinas are able to get the update but those who don't can't? Like for those of us who live in northern VA and in MD. I don't think AT&T rolled these updates out to all 50 states yet. At least, that's what I think.

    And another thing worth mentioning: it just doesn't make sense for those of us who can't get the update for the thing to keep showing a connection failure message every time we check for updates. I personally think that the AT&T servers get clogged with traffic every single day trying to push updates out that it might not have enough bandwidth available to process all of our requests. But that too is just what I think. I could be wrong.

    I collected myself and called AT&T this morning. The tech rep said that he will use a program the manager uses to try and push the update to my phone (before I called, I cleared the DM data, did a battery pull, then reported the phone). Pretty soon, out of nowhere, I spotted the DM arrows on the top left corner of the screen. It had NEVER done that before, not without my intervention.

    But what's the point? It just failed again. So I rebooted the phone and when it started initiating, the arrows appeared again and repeated the procedure, complete with the error message. I rebooted again, and the same thing happened, or would have, because the phone froze up completely while the DM was connecting itself and the media scanners were running. So I had to reboot again. That's when the first scenario occurred, where the arrows appeared for a whole and showed me that all-too-familiar connection failed message.

    The rep told me that the update was pushed out successfully, but that it's pending receipt. He didst know why that was.

    Then the rep started doing a third-party search on this issue, and he came across my other post ("Software Update for Infuse 4G?"). He started reading it out loud and this went on for a while. I had to stop him because I knew the problem won't be resolved. I declined his offer of calling me back because if I didn't get the update within 24 hours, he'd replace my phone, a path where I DO NOT want to go just because of a minor issue.

    The best thing to do is either keep checking until it cones through, or wait until KIES for Infuse cones out.
     
  20. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    Hi dlee1001,
    You are clearly frustrated, and I don't blame you, except that I do not plan to call ATT support again on this issue unless I have a very good idea of what's going on. Calling support is what's frustrating.

    Two points:

    I mentioned this previously. We see the response "checkin succeeded" when we try to update by sending the code. What does that mean? It worked? But we still didn't get the update. We see connection failures when we go through the settings menu. Is that because it failed, or because we are not due the update, or something else? How are the two processes different?

    I was told by a support person, but I am skeptical, that they can not force the update. I was basically told I had to wait until it was pushed to my phone.
     
  21. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    Yes, calling support is frustrating because the answers we get from them are not standardized (they're not the same answers).

    I have yet to find out what "checkin succeeded" means. But I certainly did try that before and during the DM server connection attempt (but not back to back). Still an epic failure.

    I did read somewhere though, that the checkin command forces Android to check for system updates, but if that's true, we shouldn't even have to go to settings. Maybe it just alerts the servers that the phone will connect to the AT&T servers? I don't know. The words "checkin succeeded" are too vague and there's no clear explanation of it anywhere. But I'll update you if I do find more clarity in it.

    Maybe I'll try calling Samsung tomorrow and see what they have to say. If they even try referring me to AT&T, I'll simply say that they told me to contact the manufacturer, which is by all means Samsung.
     
  22. dlee1001

    dlee1001 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    118
    Joined:
    Jun 2, 2011

    Jun 2, 2011
    118
    7
    36
    somanyapps, I found something that may confirm our belief that the update was released in only certain areas. Check this out: At&t just pushed a software update to my phone - gingerbread? [Archive] - xda-developers. The information on our belief appears near the bottom of the page, but it doesn't hurt to read all of it.

    There is a brief part of a post that implies that a user installed custom ROM, but that hasn't any effect on our belief or the ability to check for updates.
     
  23. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    Interesting. I had been to the xda site before when looking for info on the update, but hadn't seen that thread (maybe I didn't read it all). Anyway, it is interesting that the posts mention being in this area not getting the update, but PA and NC have. I didn't see a follow-up posting from the person near Baltimore as to whether they got the update when they went to PA. It would be interesting to know that, or if anyone who hadn't gotten it finally did without having to take a trip.

    Is this all news to ATT? Nobody I spoke to mentioned a regional thing. You would think they would know this. And I didn't know it at the time to tell them.
     
  24. Jack Dangers

    Jack Dangers Lurker
    Rank:
    None
    Points:
    5
    Posts:
    1
    Joined:
    Jul 16, 2011

    Jul 16, 2011
    1
    0
    5
    I live in Washington DC and was having trouble getting the update. Went last week to LA for business and had no problem getting it then. now the only problem is that it seems that I'm getting more dropped calls now. :thinking: quite a lot...
     
  25. somanyapps

    somanyapps Well-Known Member
    Rank:
    None
    Points:
    36
    Posts:
    172
    Joined:
    May 27, 2011

    May 27, 2011
    172
    5
    36
    VA
    Again, interesting. Of course, the few that have posted here are not a lot of folks. So, it might be suspicious, but not conclusive. I'm wondering, what are the limits of the DC area? In other words, how far do I have to go to ensure I would not be connecting to the same source? Right now we're talking a fairly large area in question. Well, maybe not that large as the crow flies. I'm willing to take a drive and test the theory, but where and how far do I go?
     

Share This Page

Loading...