Device Management, Connecting to DM Server??? =S - Vibrant Q&A, Help & Troubleshooting

So i just went back to stock rom like 30 mins ago and in the notification bar that's what it says and it was been there for a while? can someone tell me what that is?

I'm on Bionix-V 1.2.1 and just had it connect to the DM server for 5 minutes. Seems like nothing has happened, but still never seen it before.

creator2456 said:
I'm on Bionix-V 1.2.1 and just had it connect to the DM server for 5 minutes. Seems like nothing has happened, but still never seen it before.
Click to expand...
Click to collapse
It Appears to be an update just got message and did the steps it says that tmobile or samsung have an update for your device, lets see what happend!!

Odd, same here...Saw the notification in the status bar for about 5 minutes, then disappeared. Went to settings>software update, no firmware. Last time I got this it was for the ji6 update. Running stock froyo.ka6.

Yeah I just got it twice this afternoon. Said it couldn't connect both times...runnin bionix 1.2.1 dow kernel

I got this today as well. First time failed. The second time it took about 5 minutes, but no update. Running stock Froyo 2.2 KA6 build

I believe this is why we are seeing the DM working and not getting any updates
What are your thoughts.......
Samsung Vibrant 2.1 OTA Update.Options
Mark as NewBookmarkSubscribeSubscribe to RSS FeedHighlightPrintEmail to a FriendReport Inappropriate Content....02-07-2011 02:57 PM
Beginning February 7, T-Mobile and Samsung will begin sending an OTA update to Samsung Vibrant devices using Android 2.1. This update includes minor changes to the device software to ensure compatibility with upcoming network enhancements.
•There are no additional features included with this update. The device functionality will remain the same.
•This is NOT an upgrade to Android 2.2 (Froyo). See: Samsung Vibrant upgrade to Android 2.2 using Kies Mini.
•Customers who have already upgraded to Android 2.2 (Froyo) will NOT receive this OTA.
•Customers with rooted phones or who use unofficial device software versions will not receive this update.
....

i too have got this update notification several times. each time it asks to restart the phone. when the phone is booting up, the update icon is in the notification bar and says "connecting to DM server" but then disappears, and so does the update icon. when i check for software update is says no firmware. running 2.1 update 1 eclair uvji6 and was rooted, but the update somehow unrooted it.

Related

[Q] Updated to J16, still showing update available

So the "connecting to DM Server..." icon came up. I didn't know what it was at the time, but it disappeared. So I connected with kies mini and updated that way. After all was finished and the phone booted up fine, the update icon came up again and now tells me I have the update available, even though I already updated, and I can't get it to go away.
Anyone have any ideas?

[Q] The device manager is trying to connect to the server - Nero V3

mmm.... I wonder should I go back to stock 2.1? I feel like it's trying to push the update, I've seen this happen a couple minutes ago and it failed, now this is the second time in a row...
no, its a accident, tmobile keeps saying that.

Did i just update

Hi there, i updated my S2 to 4.03 in April with ther official Tmobile UK update via Kies.
I have read on a few sites recently about 4.04 being out and that it makes further improvements. Well yesterday i connected my phone to Kies and was informed there was an update due so i went throught he whole update process and when complete it shows my phone as still being on 4.03.
At the end of the update my phone had all my apps, contacts, pics, everything still on phone. I did not have to reinstall anything. Kies now shows that i have latest firmware but i can see no difference.
Kies reports firmware as PDA:LPD / Phone:LPB / CSC:LPD (TMU)
Anyone had anything similar and bottom line is did i get an update or not.
Thanks for any help.
LPD is quite an "old"-ish ROM, if we can say so (check here for details: http://forum.xda-developers.com/showthread.php?t=1544487).
The Build Date is 8th May 2012.
I have found LPG to be the most stable version of 4.0.3 (Build date: 24 May 2012).
Looks like we're gonna have to wait a while longer for 4.0.4 (I meant worldwide coverage for it cause as far as I have found out this latest LPO for NEE is quite alright).
Cheers,
Mihai
jmbill said:
Hi there, i updated my S2 to 4.03 in April with ther official Tmobile UK update via Kies.
I have read on a few sites recently about 4.04 being out and that it makes further improvements. Well yesterday i connected my phone to Kies and was informed there was an update due so i went throught he whole update process and when complete it shows my phone as still being on 4.03.
At the end of the update my phone had all my apps, contacts, pics, everything still on phone. I did not have to reinstall anything. Kies now shows that i have latest firmware but i can see no difference.
Kies reports firmware as PDA:LPD / Phone:LPB / CSC:LPD (TMU)
Anyone had anything similar and bottom line is did i get an update or not.
Thanks for any help.
Click to expand...
Click to collapse
There was an update for Kies (just the program you run on your computer) lately, are you sure it wasn't just that?
SNAP!!
Hi guys,
I just went throught the same update issue. I had already upgraded to 4.0.3 earlier this year - but I have been experiencing problems with the phone simply turning itself off at random times and needing to have it's battery removed and reinserted to get it going again.
I e-mail Samsung support and got advised to do a firmware upgrade via kies.
So I did - and lowe and behold it found an update and duely installed it - but I am still showing droid version as 4.0.3 and I can see no difference what at all.
I also didn't need to reinstall any apps etc - so exactly what is going on?
Have samsung realised that they made a mistake with the initial release of ICS and applied a patch?
I've got my fingers crossed that what ever it is, it will hopefully stop the phone turning itself off.
Meanwhile I have e-mailed samsung back to ask exactly what was in the update - if I get anything back I'll post it on here.
Samsungs latest firmware is on 4.0.3.
When upgrading with Kies, none of your apps and personal data is tempered with. Just the system is updated and the rest is left untouched.
So, yes, your're upgraded to the latest firmware.
Sent from my GT-I9100

[Q] Problem Updating OTA to 4.1.2

I am having an issue with updating via OTA with Verizon. The OTA update came out a couple of weeks ago but I never received notice. When I went to search for it I got an error message, no matter where I was or whether it was on 3g, 4g or wifi. The message states "service unavailable". My service is working fine and I can use the internet without any issues. I called Verizon and they didn't know what was causing it but they did confirm I have an update available. I have powered off, taken out the battery cleared cache, tried to update manually with ODIN (which failed) and have come to my wits end. I am trying to avoid factory resetting the device and having to wait for all my apps to be reinstalled. I have rooted several devices before but don't want to do that this time.
Does anyone have a suggestion to help me accept the OTA from Verizon? Again, I am locked and unrooted running everything stock.
Thanks for your help!

[Q] Freshly installed 4.3 produces ghost OTA update notifications

I have installed Android 4.3 from occam image downloaded from Google to my Google Nexus 4. The phone has been rooted and set up with TWCR.
The problem is that every week or so the phone thinks there is an OTA OS update from Google: a notification icon pops up telling that an "update to Android 4.3" has been downloaded (update size 1.8M). The update "installs" in a second, boots into TWCR which offer to repairs root access (and I do), and then boots normally. There is no that "optimizing app N of M" lengthy process as with a real OS upgrade.
I confirmed that the build incremental version in /system/build.prop does not change; in fact, the build fingerprint is not changed by this "update":
Code:
ro.build.fingerprint=google/occam/mako:4.3/JWR66V/737497:user/release-keys
Why does this happen and what may I try to do to prevent this?
same issue happened yesterday with my phone
andorkin said:
same issue happened yesterday with my phone
Click to expand...
Click to collapse
My wife's all stock Nexus 4 with Android 4.3 got an update notification today, and run an upgrade that did not change anything in the "About phone" page. Unlike mine, thought, it did the "Optimizing application X of Y" step after a reboot.
So maybe there was a systemic glitch which just coincided with my phone re-flash? This explanation would hold if I do not see any more of these "updates" coming in the next few weeks.
Hi kkm000
today I unroot my phone and flash stock recovery and then successfully installed the update.
version of the build changed from JWR66V to JWR66Y

Categories

Resources