• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Post Here if You Have Received The Update

Did a Check for update on mine & the wife's phone, both installed without a hitch.
Her phone default setup, mine rooted with firewall.
Had to allow the update software to communicate via 3G to get the update though.
 
Razer511 said:
Every time I have EVER looked for an update I get the message "DM initialization is not ready. Check Network or SIM card." It has done this since it was new, and I got the phone the second day of release and it has done it since then. Is my SIM card messed up somehow? It did this before root, and now it is rooted and is still doing it.

No txt message, and no way to manually check for me now it seems. :( Anyone have any ideas?
Click to expand...

Im just reading your post if still unresolved make sure you dont have a task manager killing download management its a service that needs to run for updates to work
 
Finally got it to download now. Every other time it just failed or said no update.

I still miss my bricked Captivate that this update killed. That phone and GPS worked great :(
 
New here and just when the update (checked manually)was about to finish i received a sms message from :

lovely at@t (nice timing) . Update and rebooting all worked fine. GPS not sure yet ?

2 weeks old and stock but today phone really lagged more than usual .

Xda "Ryan`s" and Voodoo caught my interest while updating which leads to more

questions such as a preference between them or the downside to either .

Inform and or vote to tweak or not to tweak if you will .
 
my phone has never been able to connect to even check, rooted or stock, it always says "unable to connect to server"
 
I'm also one of the number of people who would get "failed to communicate" errors when checking for the update. It has always done this for me and never done it on my wife's phone. Her's also and pulled the OTA update down with zero issues.

I just went with cognition 2.1.1 and I'm very pleased so far. It was also fairly quick and painless. I'd recommend this route if you aren't too worried about flashing it yourself... sure beats dealing with AT&T or samsung customer support :)
 
I was getting unable to connect or no firmware messages, so I did a factory reset, then I was able to do the update manually...
 
I got the update on mine fine (by doing a manual check). Hubby, not so much. It started to download, and then failed, and then restarted, and now he can't power up. Any thoughts?
 
DBryden said:
Are any of you having the issue that I posted above?

Every time I reboot my phone it congratulates me for the update...
Click to expand...


Yes..exactly the same. And the "no firmware" as well under update. Yet my phone clearly did update, and I have never rooted it.
 
drs155 said:
Yes..exactly the same. And the "no firmware" as well under update. Yet my phone clearly did update, and I have never rooted it.
Click to expand...


Woohoo..I made the "phone has been updated message" go away at reboot. Went to settings/applications/manage applications...set filter to all....selected device management and then hit "clear data" under storage. Rebooted and no more message. Plus, update still shows in place.
 
drs155 said:
Woohoo..I made the "phone has been updated message" go away at reboot. Went to settings/applications/manage applications...set filter to all....selected device management and then hit "clear data" under storage. Rebooted and no more message. Plus, update still shows in place.
Click to expand...

Thanks - this worked here to get past the "no firmware" popup, and the constant "software update has been installed" dialog upon bootup, after updating a stock Captivate.

Only problem now is that when checking "the AT&T server for new software update", it failed to connect, and the subsequent update said "wait 24 hours", as expected. so, either ATT's update server's *are* temporarily down, or refusing connections from frequent updaters, or there's still an unresolved problem client-side.
 
I manually checked las night when I got an edge signal (wouldnt work on wifi). Downloaded and installed and everything worked first try.
 
OK, an update on my issues. First, the "unable to connect to server..." issue never went away. Calls to ATT resulted in ATT blaming Samsung and telling me to contact them and, as you can discern I'm sure, Samsung telling me it's an ATT issue (ATT claimed that Samsung handles all the updates and the server). I went to my not-so-local ATT corporate store (the local 'ATT' store hid behind the franchise exclusion principle and wouldn't talk to me) and they very generously swapped out my phone for a new one. It was 5 weeks and a few days out of the initial 30 days and 1 day past 30 since my last swap. The new phone still would give the server error message, I even did it in the store in front of the rep. A day later however the server error disappeared. It was replaced by "no update available". I have been doing this every day and nothing as of today. On the GPS front, it worked great (great for a Galaxy) OoB. Locks were fast with only occasional drops followed by a quick return. After about a week I've noticed a decrease in quality. It now takes sometimes 10 minutes to get a lock, even with 9 or 10 sats in view. Once 'locked', it tends to go in and out and even when 'in', that is a very loose description. But overall, it is still working, GPS-wise, we'll see what the next week brings, if the degradation trend continues. I can't find any 'download manager' service or app running, according to my task killer. Is this an issue in my update matters? edit: Sorry for lack of line feeds - the editor is jamming everything together and I don't feel like trying to find out why at the moment...
 
I checked for an update it started downloading it however my phone is rooted and all. What are the risks involved in this with a rooted phone?
 
hotguy69 said:
What are the risks involved in this with a rooted phone?
Click to expand...

- It might refuse to install.
- It might install fine but you will lose root and have to re-root
- It might brick your phone

A lot depends on what method you chose to root and what other hacks you (or it) may have done.
 
GalaxyS609 said:
my phone has never been able to connect to even check, rooted or stock, it always says "unable to connect to server"
Click to expand...
After I received my update (pre rooting) I would receive this message when ever I manually checked for updates. I went to settings/applications/manage applications/all (under filter in sub menu)/device management/clear cache. This fixed the unable to connect to server issue and now regularly communicates with At & T server with no issues.
 
MYFASTANG said:
After I received my update (pre rooting) I would receive this message when ever I manually checked for updates. I went to settings/applications/manage applications/all (under filter in sub menu)/device management/clear cache. This fixed the unable to connect to server issue and now regularly communicates with At & T server with no issues.
Click to expand...

Same issue here after the update
 
MYFASTANG said:
After I received my update (pre rooting) I would receive this message when ever I manually checked for updates. I went to settings/applications/manage applications/all (under filter in sub menu)/device management/clear cache. This fixed the unable to connect to server issue and now regularly communicates with At & T server with no issues.
Click to expand...

my "clear cache" is grayed out. . .I though I found a fix when i came across your post . . . .guess ill have to keep looking for another way to try and get updates . . .Ive heard about keysmini or something but haven't tried it yet. . .
 
I just got my Captivate (again) and the first thing I did was the update (checked manually) and everything went smoothly. Tested the GPS (didn't try it before the update) and it performs excellently :).

I am so glad because that was the sole reason why I returned it.
 
I purchased my phone almost 2 months ago. I never did receive an update so I just went and did it manually. It worked just fine OTA. I am disappointed that I had to manually make the change but it is done now.
 
You must log in or register to reply here.
Back
Top Bottom