A rundown of my issue. One morning I woke up, got on facebook mobile on my phone and the phone crashed. Once it booted it up it asked for a Network Control Key(only 10 attempts allowed).
I had no idea at the time what a NCK was so I took my phone to ATT and the associate tried random keys until the phone wouldn't let her enter anymore keys (as instructed by another ATT employee). Well now the message says "Network unlock PIN number is entered incorrectly. Contact your Service Provider."
One odd thing I've noticed is that the IMEI number in the phone is a wingding type text, something like a number and then boxes and non-traditional fonts.
So a problem I ran into is that Samsung has denied my claim to get a replacement(this phone is a refurb), and it's still under warranty for about 20 more days. No idea why it's denied as the ATT employee was talking to Samsung in my behalf.
Last night I decided to root my phone, which was successful.
So with my IMEI number jacked up is my phone still able to be fixed?
Thanks in advance!
Hi,
I have a problem that someone here might be able to help me with. I have recently moved between countries (say from country A to country B). I keep WhatsApp under my phone line in country A, because the vast majority of my contacts use that number to contact me. I still pay a small monthly fee to keep the line. Initially I had no problems with WhatsApp, I simply inserted the new SIM card from country B into the phone I brought from Country A.
However, now I have bought a new phone (Moto X 2013 (=no SD slot) and I am trying to link WhatsApp to my usual number, in country A. Even though I still own that line, I can't receive any SMS/calls from it in country B. Unfortunately, WhatsApp doesn't let me use alternate methods of verification. I am stuck with using my old phone (Galaxy s3 mini) for WhatsApp.
Is there a way to move WhatsApp from my old to my new phone, in a way that no verification is required?
I have the same problem with Telegram, but (unfortunately) my contacts use WhatsApp the most.
Both phones are rooted. The new one has the bootloader unlocked. I am willing to tweak these features if necessary ( I will need proper guidance though, I have never played wit them before).
Thanks
I signed up for the Tmobile Digits service which is supposed to work somewhat like AT&T's number sync. Basically it assigns the same phone number as your phone to your watch or more than one device. The theory is that when you use your phone in standalone mode the watch acts like your phone for texts and calls. So I signed up. Big mistake and I should have figured. How would I forward stuff from my phone to my own number on the watch.
So I sign up and first thing is that Tmobile does is change my watch number to something different than the phone so basically my watch is useless in standalone mode because the watch thinks it's another phone number that doesn't exist. I can't even make phone calls from the watch in standalone.
I call support and they forward me to a special group that handles the new digits program. I basically tell them to forget about it and change my number back to the old number and nobody at Tmobile can change my number back. My watch now has a phone number that doesn't exist and tmobile can't fix it. They supposedly sent it to it another group which may take a few days to correct the problem. Not only that, the rep told me that they were having issues with gear watches not working with the service because messaging forwarding doesn't work when the watch has the same number.
So I am basically SOL for a few days until they can change my watch back to the old number.
I am also on Digits. I thought the same thing when the Beta software changed my number on the S3. Actually it is way better than the current call forward setup. Your watch now virtually simulates your main phone number to your phone. When you are connected via BT you get all your calls, data, etc... through the phone. Say you forget or leave your phone, your watch is now on the mobile network (if you set your mobile network settings to auto). So if you get a call or text to your mobile phone it will simultaneously ring/arrive on both your phone and your watch. You don't have to remember to turn on call forwarding. You can no longer call your Gear S3 number, it is tied to the virtual number.
It is still in beta so there are some bugs, but so far I have been able to add my Gear S3, Gear S2, and my primary phone to the Digits Service. All 3 devices ring or receive text at the same time when someone calls/texts me.
Bladder61 said:
I am also on Digits. I thought the same thing when the Beta software changed my number on the S3. Actually it is way better than the current call forward setup. Your watch now virtually simulates your main phone number to your phone. When you are connected via BT you get all your calls, data, etc... through the phone. Say you forget or leave your phone, your watch is now on the mobile network (if you set your mobile network settings to auto). So if you get a call or text to your mobile phone it will simultaneously ring/arrive on both your phone and your watch. You don't have to remember to turn on call forwarding. You can no longer call your Gear S3 number, it is tied to the virtual number.
It is still in beta so there are some bugs, but so far I have been able to add my Gear S3, Gear S2, and my primary phone to the Digits Service. All 3 devices ring or receive text at the same time when someone calls/texts me.
Click to expand...
Click to collapse
They're correct^^^
I had the exact same freak out and called into the department last week and they were so confused lol. Saw my sim numbers swapped on my account and the inability to dial out and had to explain everything to them, with them offering a potential fix upon more research.
I do agree with the above in terms of a better method of call forwarding when working with a non Samsung smartphone. I'm using an LG V20 and prior to Digits I would have to enable call forwarding if I knew I was planning to be away from my phone, not allowing me to forget my phone and remain connected.
However when using a Samsung smartphone, you have an auto call forwarding option in the Gear Manager app. I had my Note 5/S7E/Note 7 paired up to my Gear S2 Classic 3G and it would auto call forward upon being disconnected via Bluetooth, basically doing what Digits does without the virtual number.
Somehow my ability to dial out self resolved so now I'm digging this setup
Torridred04 said:
They're correct^^^
I had the exact same freak out and called into the department last week and they were so confused lol. Saw my sim numbers swapped on my account and the inability to dial out and had to explain everything to them, with them offering a potential fix upon more research.
I do agree with the above in terms of a better method of call forwarding when working with a non Samsung smartphone. I'm using an LG V20 and prior to Digits I would have to enable call forwarding if I knew I was planning to be away from my phone, not allowing me to forget my phone and remain connected.
However when using a Samsung smartphone, you have an auto call forwarding option in the Gear Manager app. I had my Note 5/S7E/Note 7 paired up to my Gear S2 Classic 3G and it would auto call forward upon being disconnected via Bluetooth, basically doing what Digits does without the virtual number.
Somehow my ability to dial out self resolved so now I'm digging this setup
Click to expand...
Click to collapse
You may not be digging it when the beta expires and you have to start paying for it. Sometime in the Spring...
kronium said:
You may not be digging it when the beta expires and you have to start paying for it. Sometime in the Spring...
Click to expand...
Click to collapse
This is the first week of beta testing. Issues are to be expected. Those (like me) who have no appetite for dealing with this shouldn't volunteer.
T-Mobile will figure it out. Sharing a number across devices will become a necessary linchpin as we become increasingly more connected.
T-Mobile won't charge much for Digits. AT&T and Verizon don't charge for their (admittedly less capable) service. And Google Voice, which Digits is modeled after, is also free.
kronium said:
You may not be digging it when the beta expires and you have to start paying for it. Sometime in the Spring...
Click to expand...
Click to collapse
Personally I'm not too worried. They state the service shouldn't cost much once it arrives, though I do feel they should issue the finished product free to beta testers for a limited time for our services.
If I go back to Samsung which is most likely, that will eliminate my need for it. If I don't, well the discount on my bill makes it dirt cheap that I'm not losing sleep over it. Perks of working at T-Mobile haha
Well all I know is that they changed my watch number to to some different number that doesn't exist on my account and nobody can correct it or change it back to the old way. I'm going on 3 days now and nobody can resolve the issue. I asked that they just take me off the beta and they can't even do that.
I understand that it's a beta and you live with the growing pains of bugs but PLEASE! They can't even take me off the program and restore my service back to normal! That means this is more of an Alpha than Beta stage! You don't release a Beta when you can't even get the basic functionality right!
Not to mention I am being sent numerous text messages that I added a new line to my account and when I call tmobile is clueless as to why I am getting those messages which I am sure it is due to digits.
Tmobile has nice customer service reps and great prices but when it comes to company communication and overall customer service experience they are clueless. I have never experienced a company more clueless and disorganized! I went through the Note fiasco with them and when I first started they shipped me like 10 iPads when I only ordered 1.
Sorry but Tmobile is a joke. I only stick with them because of convenience.
I'm having a great experience with the beta program so far, it's way better than the Samsung Auto forwarding. Because when I'm out and about and I make calls from the watch when the phone is at home it shows my actual phone number and not the watch phone number, and everything important is forwarded to my watch as well.
Sent from my SM-G935F using XDA-Developers mobile app
In the beta digits program also I have my gear s3 and gear s tied to my original number. I have to wait for the gear s tho cause they are sending me a sim card I don't know why I can't use the one I already have in it.
Digits works well for me
I am really enjoying my digits experience. I frequently leave my phone at home or in the car on the charger. Before digits my calls would not always be forwarded from my s6 edge to my gear s2 causing me to miss calls at times. That defeated the purpose of me paying for the watch number. I also hated that in the event I left my phone at home and forwarding was not working people could not reach me on my watch had I not given them that number. I have no trouble placing calls from the watch in standalone mode. My only annoyance with the program is when I do go outside of Bluetooth range all my texts are synced to my watch, which I just do not need. I wish there was an option to turn this off or on since I do not need it but some people might. I will definitely keep digits provided it does not cost me much more than the watch line I pay for currently.
sorry I am late to the party, and this might be a dumb question (but the T-mobile special tech people can't seem to answer it)...
Do I cancel the Gear S2's service and then use its SIM to sign up for the beta? Or do I have to keep the service active? Cause that's what I did - kept the service, signed up for the beta with the SIM number, but nothing's happened and the watch still has its own number. Does it take a while to change over?
Thanks.
hawk1500 said:
sorry I am late to the party, and this might be a dumb question (but the T-mobile special tech people can't seem to answer it)...
Do I cancel the Gear S2's service and then use its SIM to sign up for the beta? Or do I have to keep the service active? Cause that's what I did - kept the service, signed up for the beta with the SIM number, but nothing's happened and the watch still has its own number. Does it take a while to change over?
Thanks.
Click to expand...
Click to collapse
T-Mobile will send you a welcome to digits email and instructions on how to set up on your phone. It took 24 hours for me to get the email. You can also call t-mobile and ask to speak to the digits beta team and they will patch you through and the beta team can pull up your request and speed up the process.
Hope this is still relevant
hawk1500 said:
sorry I am late to the party, and this might be a dumb question (but the T-mobile special tech people can't seem to answer it)...
Do I cancel the Gear S2's service and then use its SIM to sign up for the beta? Or do I have to keep the service active? Cause that's what I did - kept the service, signed up for the beta with the SIM number, but nothing's happened and the watch still has its own number. Does it take a while to change over?
Thanks.
Click to expand...
Click to collapse
So I was paying for watch plan when I signed up for digits beta. Tmobile was more than happy for me to keep paying. However I was having issues with digits not working and still missing calls. Finally I got someone on the phone that knew that I didn't need the watch line I only needed the digits line. Has worked great since they stopped the watch line and linked my digits with my phone. The digits line incluse so many my of data which is why the separate watch plan is unneeded.
Hello,
i messed up my samsung account. My old number (which doesnt exist anymore) is still registered to my samsung account as two-factor-auth. Usually i could solve the problem with my personal data, IMEI and serial number, but somehow my birthday is wrong in my account. The support refuses to help me because they only accept the legitimation with name+birthday.
I have activated usb-debugging and oem-unlock and now i want to reinstall android to login in a new samsung account. Now my question:
Is this working? Because the IMEI and serial number are still registered on the old account.
The support said i can go to a samsung service center and pay like 80€ for it. Well the next service center is 400km far away, so i would pay like 300€ for the traveling. Any Ideas for me?
Thanks for reading
Goldk4t
I submitted the post below to the AT&T Community hoping to get some answers. So far I gotten none. No one from AT&T support has been able to figure out how to re-provisione my watch 4 classic. I'm posting it here to see is someone has an idea of what could be happening. I think the issue is that no matter what they/we do the ICCID in the watch remains the same. (This ICCID is the original one installed scanning the UPC of an activation card that came with the watch) We have factory reset it and tried adding another eSIM, but the ICCID doesn't change. The current (unchangeable) ICCID has been flagged on their systems for some reason and it can not be reused. Has anyone experienced a similar issue... and if so how did you resolve it.
"My numbersync stopped working a couple weeks ago and after spending almost 3 hours on Saturday with an AT&T Phone Support rep... she ended up manually deactivating and tried re-activating the phone service for my watch. After entering all required activation codes manually (ICCID, IMEI... etc) on AT&T systems my "AT&T purchased" Galaxy Watch 4 Classic ended up with a "SIM not provisioned MM#2" error message. We tried factory resetting the watch 4 and restarting it multiple times, but the error would no go away. Long story short, she said that the only way to get it re-provisioned was for me to visit a AT&T store and get a new eSim card with a UPC with the Activation codes. Well, I went to the AT&T store in my neighborhood and spent 3 hour there. They tried a couple of new eSim cards and they could not get the watch to get activated. The store clerk called 2nd level tech support and the technician said that the only way that he could fix was if I got a new phone number. Reluctantly, I agreed, but that didn't work either. I still get the SIM not provisioned error. In the process to try to fix it, the battery of the watch ran out and they didn't have a compatible charger in the store. I plan to return to the store again tomorrow with my charger and my wife's Watch 4 which is working correctly with numbersync. The rep suggested that "maybe" the numbersync service was changed to require that it be used with the same phone number as my phone. This was never the case, I had a S3 Frontier for 3 years and upgraded to the Galaxy Watch 4 Classic for about 5 months and both had their own unique phone numbers that allowed the watches to make and receive phone calls independent of the Phone. Or work with numbersync when I turned it on. I could make phone calls to the watch phone number and make calls from it. Now it has been suggested that it needs to use the phone number from the phone to do so... Someone from AT&T with expertise in SIM provisioning for Galaxy watch 4 watches and numbersync... PLEASE!... get to the bottom of this issue."
tamanaco said:
I submitted the post below to the AT&T Community hoping to get some answers. So far I gotten none. No one from AT&T support has been able to figure out how to re-provisione my watch 4 classic. I'm posting it here to see is someone has an idea of what could be happening. I think the issue is that no matter what they/we do the ICCID in the watch remains the same. (This ICCID is the original one installed scanning the UPC of an activation card that came with the watch) We have factory reset it and tried adding another eSIM, but the ICCID doesn't change. The current (unchangeable) ICCID has been flagged on their systems for some reason and it can not be reused. Has anyone experienced a similar issue... and if so how did you resolve it.
"My numbersync stopped working a couple weeks ago and after spending almost 3 hours on Saturday with an AT&T Phone Support rep... she ended up manually deactivating and tried re-activating the phone service for my watch. After entering all required activation codes manually (ICCID, IMEI... etc) on AT&T systems my "AT&T purchased" Galaxy Watch 4 Classic ended up with a "SIM not provisioned MM#2" error message. We tried factory resetting the watch 4 and restarting it multiple times, but the error would no go away. Long story short, she said that the only way to get it re-provisioned was for me to visit a AT&T store and get a new eSim card with a UPC with the Activation codes. Well, I went to the AT&T store in my neighborhood and spent 3 hour there. They tried a couple of new eSim cards and they could not get the watch to get activated. The store clerk called 2nd level tech support and the technician said that the only way that he could fix was if I got a new phone number. Reluctantly, I agreed, but that didn't work either. I still get the SIM not provisioned error. In the process to try to fix it, the battery of the watch ran out and they didn't have a compatible charger in the store. I plan to return to the store again tomorrow with my charger and my wife's Watch 4 which is working correctly with numbersync. The rep suggested that "maybe" the numbersync service was changed to require that it be used with the same phone number as my phone. This was never the case, I had a S3 Frontier for 3 years and upgraded to the Galaxy Watch 4 Classic for about 5 months and both had their own unique phone numbers that allowed the watches to make and receive phone calls independent of the Phone. Or work with numbersync when I turned it on. I could make phone calls to the watch phone number and make calls from it. Now it has been suggested that it needs to use the phone number from the phone to do so... Someone from AT&T with expertise in SIM provisioning for Galaxy watch 4 watches and numbersync... PLEASE!... get to the bottom of this issue."
Click to expand...
Click to collapse
Your going to have to call tier 2 and have them remove all but the last number they tried to activate the watch with. Have them reprovision the last number and wait 24 hours. Then after 24 hours go to settings and try to activate mobile network and you should be good.Do not use the card to activate because with the newer watches don't use them.I hope this helps....
The issue with the "SIM not provisioned MM#2 " error was resolved. But my original issue with NumberSync remains. Below is the follow up that I posted in the AT&T Community.
"I spent about an hour or so in the AT&T store yesterday. Long story short... the issue was related to adding the ICCID to the watch using the Wearables app and selecting "New Plan". - Rep in the store kept factory resetting the watch and starting the activation process from scratch and selecting "Existing Plan" because as he said... we didn't want to add charges to my account.
The issue was solved by getting a new UPC in eSIM card and working along with a 2nd level tech support rep over the phone. Scanning the UPC code of a new eSIM card and making sure to select "Add to Watch" in the Wearable App as there are two options (One is for the phone) We had used this option before, but it would not overwrite the existing ICCID in the watch... reason being that we were selecting "Existing Plan!" This time we selected "New Plan!" with the new eSIM. The 2nd level support tech over the phone also made sure that the ICCID was active on their system before we added it to the watch via the Wearable app. SIM not provisioned error gone and the watch can make and receive calls.... BUT!
We could not get NumberSync to work no matter what we tried. We keep getting the following on the Wearable App when we try to activate it either from the watch or from the phone "Code: PD-GE-RsC-NullPointerException". Ended up opening a case number with the AT&T 2nd level rep related to this issue. If the issue doesn't resolve itself in the next 10 days I'm suppose to call back. "I" believe there's something wrong with the process that enables NumberSync on Watch 4 with Samsung S21 phones running Android 12 in the AT&T network. I always found that activation/deactivation of NumberSync to be a bit wonky. It sometimes deactivated itself for no apparent reason. I have hundreds of AT&T text messages saying... "You've suspended NumberSync for wearables...". Of course in 99% of those instances "I" had not suspended anything.
I have an AT&T Galaxy 4 Classic and a AT&T Samsung Galaxy S21+ running Android 12 Build G996USQU5BULJ and Wearable App version 2.2.47.21122061 with Galaxy Watch 4 Plugin version 2.2.11.21120251"
tamanaco said:
The issue with the "SIM not provisioned MM#2 " error was resolved. But my original issue with NumberSync remains. Below is the follow up that I posted in the AT&T Community.
"I spent about an hour or so in the AT&T store yesterday. Long story short... the issue was related to adding the ICCID to the watch using the Wearables app and selecting "New Plan". - Rep in the store kept factory resetting the watch and starting the activation process from scratch and selecting "Existing Plan" because as he said... we didn't want to add charges to my account.
The issue was solved by getting a new UPC in eSIM card and working along with a 2nd level tech support rep over the phone. Scanning the UPC code of a new eSIM card and making sure to select "Add to Watch" in the Wearable App as there are two options (One is for the phone) We had used this option before, but it would not overwrite the existing ICCID in the watch... reason being that we were selecting "Existing Plan!" This time we selected "New Plan!" with the new eSIM. The 2nd level support tech over the phone also made sure that the ICCID was active on their system before we added it to the watch via the Wearable app. SIM not provisioned error gone and the watch can make and receive calls.... BUT!
We could not get NumberSync to work no matter what we tried. We keep getting the following on the Wearable App when we try to activate it either from the watch or from the phone "Code: PD-GE-RsC-NullPointerException". Ended up opening a case number with the AT&T 2nd level rep related to this issue. If the issue doesn't resolve itself in the next 10 days I'm suppose to call back. "I" believe there's something wrong with the process that enables NumberSync on Watch 4 with Samsung S21 phones running Android 12 in the AT&T network. I always found that activation/deactivation of NumberSync to be a bit wonky. It sometimes deactivated itself for no apparent reason. I have hundreds of AT&T text messages saying... "You've suspended NumberSync for wearables...". Of course in 99% of those instances "I" had not suspended anything.
I have an AT&T Galaxy 4 Classic and a AT&T Samsung Galaxy S21+ running Android 12 Build G996USQU5BULJ and Wearable App version 2.2.47.21122061 with Galaxy Watch 4 Plugin version 2.2.11.21120251"
Click to expand...
Click to collapse
You may need to call samsung and make sure the watch is not black flagged. There was a batch of watches with known issues by samsung.
All the luck in the world to you to get through to Samsung. You should try to get this escalated quickly to the next level. I am making a bad joke here, but from my own experience you only get stuff done if you are at tier 4 or 5.
Apparently the error "Code: PD-GE-RsC-NullPointerException" with NumberSync was an issue on the AT&T network side. This morning without making any configuration changes to either my Watch 4 Classic or my S21+, I was able to re-enable NumberSync following the steps that start with getting an activation code.