JUMP TO SOLUTION Solved

Original topic:

Galaxy Watch Ultra number sync not working on At&t

(Topic created: 07-22-2024 06:07 PM)
1185 Views
Zackwalton
Cosmic Ray
Options
Galaxy Watch
Does anyone else have issues transfering an old watch line to the Ultra? Whenever I try to log in to my at&t account to transfer my old watch line to my new line, it says incorrect account even though everything is correct and kicks me out
8 Replies
realaud
Honored Contributor
Options
Galaxy Watch
You have to contact AT&T
0 Likes
Zackwalton
Cosmic Ray
Options
Galaxy Watch
I talked to them. It's a problem on Samsungs end, not AT&T. Most likely, due to the watches not being officially out yet
0 Likes
meself
Honored Contributor
Options
Galaxy Watch
It could be a activation issue
0 Likes
Solution
LongHiker
Galactic Samsung Care Ambassador
Options
Galaxy Watch

@Zackwalton AT&T probably won't load the IMEIs onto their system until the release date of 7/24. 

0 Likes
ToroToro
Constellation
Options
Galaxy Watch
Having the same issue. This is helpful information. I'll wait till the 24th and try again.
0 Likes
Members_T88TFMX
Constellation
Options
Galaxy Watch

I tried to do for past few days since I got my new watch. Neither the wearables app (which I have to request a new data plan (charging me $35 for activation) nor customer service can link my old data plan to my new watch. They suggested that I go into a physical store to have it activated. ATT customer service also said in their system the watch shows up (when entered with IMEI number) that the watch requires a "Physical sim" which we all know is not true. I will go into the Store today to see if they can activate it. If they cannot, I will return the watch to Samsung and repurchase it through @ATT. The problem is that I already mailed in my old watch to Samsung for the $200 credit.

user1gyZX5aQYJ
Constellation
Options
Galaxy Watch
I'm having the and exact issue
0 Likes
userbmcVCErLSS
Constellation
Options
Galaxy Watch
I as well am having the same issue now. What was the fix? Or how did you resolve this issue?
0 Likes