Has anyone had this error message with their Z3? I have searched the web, and all that I can find is that Tmo needs to send an update to the phone to fix. Called customer service, waited for the update, restarted phone, and nothing. They then said to switch out the SIM card, and that did nothing either. Any others?
Yup, the same exact problem, they sent a sim update, new sim card, hell I even had them send me a new phone. Same thing. E911 is also set up correctly, lol they know where to send the bill. My daughters all have the one touch fierce and their WiFi calling works perfectly. My wife's m8 also works fine. What's the freaking problem.
I had that for a day and it dissapeared, my dad's M8 had it too and it went away somehow in a day or two.
This has been going on for 2 weeks now and no one seems to have an answer
I guess mine was slightly different.
Apparently TMO has to send you an OTA update. Also make sure its enabled in services in your MyTmobile account under services if not just tick the box and enable it.
TMO Forums:
https://support.t-mobile.com/thread/78656
I had same issue
Artood2s said:
Has anyone had this error message with their Z3? I have searched the web, and all that I can find is that Tmo needs to send an update to the phone to fix. Called customer service, waited for the update, restarted phone, and nothing. They then said to switch out the SIM card, and that did nothing either. Any others?
Click to expand...
Click to collapse
I bought my mother-in-law this same phone (as I already have the D6616). Her phone had the same problem as you. Took me awhile to figure what happened, but like others have said, you need to contact T-Mobile and give them the error code. (I did this over T-Mobile chat) They in turn will push out a quick OTA update (can take up to two hours). Bad thing is I never received notification that it had updated, and I even asked the T-Mobile rep if I will see the update, and she stated yes. So, after two hours, and you still don't see the update, go ahead and restart your device. Once it reboots, your wifi calling feature will be updated and will then work. Oh, MAKE SURE YOUR WIFI IS TURNED OFF and WIFI CALLING IS TURNED OFF AS WELL! Your device will not update if you are not on the T-Mobile cellular network (as needed to push out the OTA). Be sure to turn on wifi calling once phone restarts and then you’re free to also turn on wifi.
Wifi calling error code reg90
U need to setup "e911" information with your service provider.
Hey M8 crew!
New to the M8, just bought the phone from swappa. Apparently it has root/s-off/some lollipop build installed on it. Clean ESN.
Took it into verizon to activate it on my line, but the sim doesn't appear to activate as they expect. It detects that it was inserted, says to reboot, after reboot still says no service, and never performs any activation. Verizon rep was claiming that the rom was causing the failures, and it does appear to likely be software related if it is never launching the activation. VZW tech support was no help other than saying it may take up to 12 hours to activate the sim (bs meter going off). Spent 2 hours in the store trying to get it to activate, saying everything was fine on their end. Tried a couple sims in store to rule out a bad sim. Have even tried the tape on the sim trick to see if that might have something to do with it.
Has anyone ever seen / heard of this sort of situation before and have any idea of how to fix it?
Would a stock RUU flash help out in anyway?
Is it because it is not a verizon rom that the activation is not happening? Would I somehow be able to use a different verizon phone to activate the sim, then put it in my phone and have service start working?
Any ideas?
nectur said:
Hey M8 crew!
New to the M8, just bought the phone from swappa. Apparently it has root/s-off/some lollipop build installed on it. Clean ESN.
Took it into verizon to activate it on my line, but the sim doesn't appear to activate as they expect. It detects that it was inserted, says to reboot, after reboot still says no service, and never performs any activation. Verizon rep was claiming that the rom was causing the failures, and it does appear to likely be software related if it is never launching the activation. VZW tech support was no help other than saying it may take up to 12 hours to activate the sim (bs meter going off). Spent 2 hours in the store trying to get it to activate, saying everything was fine on their end. Tried a couple sims in store to rule out a bad sim. Have even tried the tape on the sim trick to see if that might have something to do with it.
Has anyone ever seen / heard of this sort of situation before and have any idea of how to fix it?
Would a stock RUU flash help out in anyway?
Is it because it is not a verizon rom that the activation is not happening? Would I somehow be able to use a different verizon phone to activate the sim, then put it in my phone and have service start working?
Any ideas?
Click to expand...
Click to collapse
If the phone was used on another carrier it might be stuck in a non lte/CDMA mode. Flash stock vzw ruu. Do a factory reset. Go into mobile settings and make sure it's set to global. Then see if default network is set to vzw. Then check provisioning.
That did it. Thanks!
nectur said:
That did it. Thanks!
Click to expand...
Click to collapse
Np...bought an m8 for my dad a couple months back and same thing happened. I finally realized it was used on a different carrier.
I'll start from the beginning, II was rooted and I wanted to speed up my phone so I tried to use SWAP. I never got it to work for some reason but then out of no where I was on the home screen and then my phone rebooted but wouldn't start again, it got stuck at the T-Mobile 4g LTE splash screen. I was still able to go into recovery and all that. So I decided to format my phone. The. That screwed it up even more because then it got stuck at the Samsung Galaxy light start up screen. So then I used Odin and flashed a stock rom. But that still didn't help it got stuck at the T-Mobile splash screen again. I went into recovery and it said era error. I managed to fix that and that went a way. Then after an hour of searching I was able to boot up my phone because some forum said all I needed to do was spam the volume up and down buttons at startup to get it to work. After that I set up my phone but then I was getting any 4G and I couldn't make any calls but it said I had 5bars. I kept getting a message saying not registered on network. Nothing would make it work. I called T-Mobile and I went into setting tried fixing my apn, tried connecting to T-Mobile again but nothing. They just called me back today and after I gave them my i di number they said it's not working because I rooted my phone. It doesn't have a bad i eu or anything it's just not working. I did see that my imei on my account is different than the imei my actual phone displays. I am able to do wifi calling and that works. So obviously something got jacked up when I formatted my phone. I want to know if anyone can help. I didn't back up my efs because I didn't know I had to, the only thing I've rooted before was my tablet. I have a Samsung Galaxy light SGH-T399 . Can anyone help. Ik my thread was long but I wanted to kae sure I got every little detail. And so basically what I need to know is why this keeps happening and what do I need to do to fix this. Could it have been because I formatted my phone completely, and I mean completely I got an error saying no OS found. I have an spouses module for an imei chNger and I changed it back to original and still nothing. My serial number also isn't the same in settings has it is in my battery compartment, it's not even the right length.
I spent over 2 hours last nite with att reps trying to enable numbersync to work between the s3 and s8 phones.. the s8 phone is an unlocked phone (not bought through att), only to find out today via another rep that the phone must be bought via ATT or truly att branded.. which i find a bit absurd, as i think others have succeeded..
Is this really the case.. anyone know or have this same experience?
Specifically this error would appear after going through the get started via the watch then on the phone (after creating a seperate accessid):
Oh darn! We can't enable device syncing on this phone. Want to find out more? Call us at 800.331.0500 so we can help.
(MSSITWINREL12)
If this turns out to really be an unlocked phone issue (which is a bit ridiculous), i think i read that it might be possible to take my sim card out of that phone and put in another phone that is att branded, enable number sync then put the card back in my s8 and go from there
Thanks
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
pasco8525 said:
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
Click to expand...
Click to collapse
Thanks for the reply.. your saying you had an unlocked tmobile phone on att and it was working till a recent tizen update then?
The rep further told me to take the phone to the best buy samsung experience store and have it flashed with the att firmware to get around this issue.. maybe not needed then? (which i assume means a wipe and possibly lose my unlock)
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
karlkarloff said:
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
Click to expand...
Click to collapse
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
markm75 said:
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
Click to expand...
Click to collapse
.
When I first bought the watch it was for the numbersync feature. My first problem was even though the Samsung rep and the bestbuy rep said that it would work with my Note3, it did not. took several calls and many hours of trying to figure out the HD Voice (VOlte) provisioning. Bought a TMobile Note 4, rooted and rom'ed this worked to setup numbersync. the only problem was it would occasionally turn off numbersync, this occurred about once a month. Then if failed completely said that this line is not accceptabl;e for numbersync. this was after about six months. Discovered that it appeared to be age of firmware related, I was on a TM firmware that was several updates out of date. When I odin flashed the latest firmware numbersync worked again until the recent update to 3.0.0.1 on the gear firmware. Now I have the line not acceptable for numbersync again. I'm going to try to update firmware again to see if that works. If not I will probably look to change carriers to TM. will cost the price of a new watch, but will get me out of AT&Ts locked boot loader.
BTW, setting up numbersync on a different phone and switching back will not work, Tried several times and as soon as you turn on the phone that is not HD Voice capable with your SIM card in it the system sees it and turns off numbersync almost instantly. went throught that trying to get my Note 3 to work.
In all my experience the Samsung and AT&T reps were not a good resource. Numbersync does not appear to be a very popular feature and they do not know much about it.
pasco8525 said:
.
When I first bought the watch it was for the numbersync feature. .
Click to expand...
Click to collapse
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
markm75 said:
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
Click to expand...
Click to collapse
Yes, that is the whole point of numbersync. The watch uses the phones number not it's own.
Tried updating to the latest firmware and a ROM based on it. No luck still get a rather comical response "Oh darn! We can't enable device syncing on this phone. " worked until the tisen update.
There also seems to be confusion on numbersync with the att reps.. one person told me the watches dont need their own numbers.. that numbersync is all we need (but how would the watch make a call if the phone is off).. another said yes they need external numbers for number sync or solo
edit: i see your last post.. so the latest reps are correct then.... so they assigned us numbers and $10 access fees each with activation fees for no reason basically.. ugh
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Just a quick note...i too spent 3 hours in an AT&T store trying to get numbersync to work..., finally returned the S3 Frontier cancelled the number in it and left frustrated...i now have a GS8 unlocked on AT&T through my work...that is synced to a Verizon Gear S3 Classic lte and i simply use call forwarding with YouMail. If i do not answer my phone after 3 rings it gets sent to my watch and if I still do not answer then Youmail picks it up..If I call out or text with the watch separately then I just let my customers know that I have 2 numbers 1 for my cell and one for their watch. I just don't think AT&T is ready for the Numbnersync technology yet and they just don't care enough to train their own people on it, sad as it is a good promise...
Sent from my iPad using Tapatalk
pasco8525 said:
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Click to expand...
Click to collapse
I meant phone number.. are you saying phone number? After the rep said i didnt need a phone number for each watch, she credited me back the cost of the two lines and said just to contact them that they would enable the numbersync once i had the phones ready.. I'm assuming number means imei, which they still have in the system.
Yes each watch has to have it's own phone number. I believe this is another case of AT&T rep not understanding number sync.
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
markm75 said:
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
Click to expand...
Click to collapse
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
markm75 said:
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
Click to expand...
Click to collapse
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
eaglerugby04 said:
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
Click to expand...
Click to collapse
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
Thanks. It sounds like the latest firmware they did seems to fix some of the issues from bringing a non-ATT phone over but does not resolve everything. It looks like I won't be able to do this though. ATT and the ebay seller are unable to clear the ICCID on my watch, I have to sadly do a return now.
Kinda unrelated, yet ATT was horrible even for normal Sammy phone/watch. After dumping ATT service/hardware for various reasons a few moths back... Sammy watch/phone from Verizon hardware/service works flawlessly. Am carrier neutral, but one works reliably, one didn't.
BTW, Sammy pay via watch hiccuped via ATT at times, yet works flawless via Verizon.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
well 5 chat people later they finally fixed the unknown callerid issue.. apparently there is an internal back end feature for numbersync regarding it set to active and on.. both toggles were on.. the rep removed the "on" and now my callerid shows my number when calling from my phone (and from the watch when watch is in solo mode too).. everything works! :laugh:
So, I have an S10e (SM-G970U) that was bought from Verizon a while back. The phone was set up on a Verizon post-paid plan, but was later switched to prepaid. The phone worked fine for months, but about a week ago, the phone randomly stopped making and receiving calls, texts, and the ability to use mobile data. It was taken to Verizon, and they tried "all they could" in their words, which included a new SIM card, resetting network settings, and eventually a factory reset from settings. Nothing seemed to work, and they gave up, claiming it "seemed like a bad antenna." They did call their "tech support" who claimed the most recent Android 11 update supposedly caused an issue with mobile network connection with the Verizon S10e devices, which I haven't heard of, but didn't know. He claimed a reset would fix it.
Since none of that fixed it, it was taken to a shop to be inspected. They claim the phone has nothing wrong with it. So, that, in theory, rules hardware issues out. Their only claim was that when an AT&T SIM was inserted, it was able to connect to the network, but never tried to make any calls due to the SIM not being activated. I assume this is due to someone trying to "help" inserting an activated AT&T SIM into the slot when testing, which I assume ended up installing the carrier branded version of the firmware. They gave a couple possible reasons, but neither seemed to make sense.
Since it had the AT&T bloatware and was working with only AT&T SIMs, I decided to flash both the VZW G970U firmware (the earliest version I could to ensure the supposed "issue" from Verizon support wasn't a problem) and the G970U1 firmware. Both firmware flashes have seemed to have done nothing, as the phone is still having the issue. Most times, it will connect to the Verizon network, but the signal seems to rise and fall quickly (like the bars going from 5 to 1 to 3).. Still no calls, texts, or data, though. I have no idea what's going on, at this point, honestly. Any ideas?
Hardware problem
iBowToAndroid said:
Hardware problem
Click to expand...
Click to collapse
LanGar21 said:
Since none of that fixed it, it was taken to a shop to be inspected. They claim the phone has nothing wrong with it. So, that, in theory, rules hardware issues out.
Click to expand...
Click to collapse
If the people it was taken to were competent and did their jobs correctly (one of the best around, according to reviews and carrier recommendation), their diagnostic results show no hardware damage to the phone. Then again, their explanation for the problem was that it had been locked to ATT network (a Verizon bought phone that never had any affiliation with another carrier, aside from Verizon and a month-long stint with Straight Talk). Some idiot she knows that used to work for a Verizon retailer popped his ATT SIM in there, and it flashed ATT firmware.. Their POSSIBLE solution was to try and have it network unlocked from ATT. As we know, though, the IMEI obviously did not change, and the process of confirming the identifier is done on the mobile network level. Therefore, flashing a different carrier's firmware won't do much (permanently), aside from changing the boot screen and bloatware apps. We even tried to explain to the guy that the ATT SIM had never been popped in until after the problem began, as there was no reason to beforehand. I also mentioned I had flashed firmware multiple times before I ever came to him, to no avail. I should've pushed harder, but I had been out all day, frustrated and ready to go home.
It's been over a month since that issue began, and I haven't thought much of it lately.. We've since found her a new phone (and stowed the other one in a drawer). Those guys did blurt some moronic statements.. In hindsight, I'm not too sure I should trust their judgement after hearing what I did. Maybe it was an antenna issue or otherwise hardware, but I sort of assumed if anyone can happen to keep a repair shop open, they'd at least be able to complete the simple tasks fairly easy. I don't know. I'm not paying another repair shop to find out, though.
I had a very similar problem where my phone would just randomly lose all connection for about a minute, then it would reconnect I would start doing whatever I was and it would do it again and this one on for months. I took it to AT&t and they told me to replace the SIM which I did and it didn't work. after a couple updates it fixed itself.