Related
I just got my phone rooted... ran nandroid backup and whatnot and then I tried to make a call on my phone. I get a nice Verizion Wireless lady (recording) telling me that Verizon Wireless could not authenticate my phone and to dial #8899.
This transfered me to a customer service rep (no hold time at all) and I had to explain to her that I didn't do anything to my phone. She "sent updated security" to my phone and now it works.
Did anybody else have this problem? I haven't seen anybody else say anything about this.
I am assuming you had the phone fully activated and working before you rooted it right?
krelvinaz said:
I am assuming you had the phone fully activated and working before you rooted it right?
Click to expand...
Click to collapse
Yep. I've had the phone since launch day. I'm just happy it is working now! I was just surprised to hear the message.
I've had this many times with WM on my TP2 when I installed custom ROMs- it's common... Just tell VZW that you cleared your storage or something and that when you did that, you had to reprogram the phone, and then you got the message. I'm not sure what causes it... Do any of the Devs know if there is a VZW file saved on the phone whenever you activate and program? Maybe the phone randomly checks for this file? I'm not sure how VZW knows... Maybe when you program a phone it checks to see if it has EVER been programmed by VZW - since you installed a ROM that was built from scratch it doesn't have this info preallocated, VZW tells you that they can't authenticate your phone and you have to talk to a rep.
It's their way of trying to find out who jacked with their phones, and if you admit to any foul play, they'll probably void the warranty and maybe even refuse service until you have it brought back into a VZW store for official programming. Not sure though...
Calibob2001 said:
since you installed a ROM that was built from scratch it doesn't have this info preallocated, VZW tells you that they can't authenticate your phone and you have to talk to a rep.
Click to expand...
Click to collapse
Understand your idea, but I didn't install any custom ROM. All I did was root it, installed recovery reflash, did a backup and then I tried to make a call. I was just surprised because I never saw anybody else mention it. Oh well.... My phone still works, so I'm happy!
eMpTy3000 said:
Understand your idea, but I didn't install any custom ROM. All I did was root it, installed recovery reflash, did a backup and then I tried to make a call. I was just surprised because I never saw anybody else mention it. Oh well.... My phone still works, so I'm happy!
Click to expand...
Click to collapse
That is weird... VZW is tricky, who knows what they can actually see has been done to the phone. I mean, if we open up a menu that tells us what ROM were running, I'm sure they can too
It lost the akey is what it sounds like, happens sometimes when a phone is hard reset or wiped, Droid Eris does it all the time but Ur all good calling tech is all it takes.
Sent from my ADR6300 using XDA App
just rooted and flashed cm6 and my it says that under status "my phone number unknown" ive rebooted/ removed sim and put back in, i can call people and my number comes up, text people. why would it say this? i can call my number and enter my passcode to check my voicemail. . . .
mulletcutter said:
just rooted and flashed cm6 and my it says that under status "my phone number unknown" ive rebooted/ removed sim and put back in, i can call people and my number comes up, text people. why would it say this? i can call my number and enter my passcode to check my voicemail. . . .
Click to expand...
Click to collapse
I'm working on a fix for this. It does not affect all people, but so far I have tried reinstalling the radio, changing to other builds, but any and all 2.2 builds I try show this. If I install a 2.1 build, it will display the number without problem.
I'll be trying to change the format of the number on the SD Card later on today. Right now mine is 1xxxxxxxxxx. I will try 1-xxx-xxx-xxxx and just xxx-xxx-xxxx to see if that displays it.
Unfortunately, after that, I have nothing else to try and it will prove that the problem is, in fact, with the roms that the devs are using.
I don't know if this is something that will help, but this is something i tried for a customer at the store i work at. He was having the same problem so i called customer care and they pushed out a text message to him saying "welcome to your new [x plan] your number is xxx xxx xxxx.
After that we restarted and it displayed his number.
Alright...so I have some bad news...
I put my sim into a blackberry and changed the number from 1xxxxxxxxxx to just xxxxxxxxxx since you can't do dashes on the blackberry in the number field...restarted the slide with the sim, and it still showed "unknown."
I decided to check the sim that was in the blackberry, and sure enough, THE NUMBER DISPLAYED!
I just called T-Mobile again to see if they could provision my old sim card from my G1 but she said that it takes 2 weeks to go through the process to reactivate an old sim, but that I can go to a store for a new one and she noted in my account to waive the $20 fee.
She also said that she has helped out a ton of TIKL users for this same issue. She did say that for some she was able to send the ota provision of the number as long as the sim is placed into a non-android phone for the ota.
I'll post back tomorrow after I go to the T-Mobile store...
So at this point I'm at a loss...
Went to T-Mobile, got a new SIM card, popped it in...phone number unknown.
Came home, called Customer Care, spoke with a tech in the PDA/Smartphone department, he tried EVERYTHING he had done to get other Android phones to display the number...no luck...
I may just have to swap the phone out...
Well, its unfortunate, but apparently this is something the powers at be (Cyanogen, Chief, etc.) are going to have to fix. There is some incompatibility between their ROM, the radio software, and the SIM cards that is causing this issue.
I am back on Chief's 2.1 build and the number shows up no problem.
I'll forward this thread to Chief and Cyanogen and see if they are able to lend any support.
Thanks, and sorry!
I wouldn't blame it on the rom just yet...
I'm not so sure this is the ROM's fault.. as i have two phones here that disprove both things you've noticed on yours. I have rooted both mine and my husband's G1's and both are running Cyanogen ROMS. I'm running CM6 and my phone number displays just fine. His is running CM5.0.8 and the phone number is blank. In fact, I think I recall my phone number being missing at some point running an earlier CM rom and it came back on it's own.. I wasn't concerned with it at the time because everything worked so I can't say for sure WHEN it came back... but I've ran through MANY CM roms starting with 4.2.13. Hubby's phone was rooted and taken straight to 5.0.7 then later 5.0.8 (he doesn't like messing with experimental roms as much as I do. ).
Next time he's home (he's a truck driver ... one of the reason's he doesn't like to take chances with his phone) I'll pop his SIM back into one of the old Sidekicks we've got laying around collecting dust and see what happens... We were going to play around with TIKL and that's when we noticed the issue....and also when I noticed that my phone showed the number again.
It's definitely an odd thing. I have not tried calling T-Mo yet to see if they can OTA the number to his phone... what's this about it having to be a non-android for this to work? First I've seen mention of that.
Currently, I'm not rooted yet, and had this problem, I thought I was the doing of a suspesius app for music download I had, I cheched all other apps, and that one was the current one that read phone state and identity, I removed it and shut down took off battery and restarted. I did it twise, and even thought I'm not sure if it was that app fault, it's solved now thanks God
Fuerza, Inteligencia, Paciensia, es Tranquilidad.
¤MyTouch 3G Slide HTC Espresso¤
Call T-Mobile, make sure you get T2 or at least a rep that sounds like they know what they're doing in customer care, and tell them you need the "activation message sent via the OTI" and you'll also need your location cancelled. Works everytime I've done it.
SamZzz: Code mentioned that this happens sporadically on phones with any 2.2 based ROM. So there is something to do with the ROMs, but no one is quite sure yet. Luckily I am not having the problem, and so far, this seems to only be an issue for those using things like Tikl that rely n the number to be "known".
I've had this problem every since I got my SECOND G1. When I had my FIRST G1 I had it in my pocket and dumped a gallon of paint all down the front of me. Needless to say I needed a new phone after that. So I got a new one and it was fine for a while but I got a refurb and still had my original, paint covered SIM. It still worked fine but after a while I stopped receiving txts so I bought a new SIM and its the one I have in my slide right now, and it has NEVER shown my number as anything but UNKNOWN. In my g1 it said unknown. I have called tmobile numerous times and they'll tell me they're gonna fix it and tell me to check it in a couple hours and it should be fixed...never works. I honestly just kinda forgot about it. But its definitely not specific to one rom, or one device for that matter.
-BMFC
Sent from my T-Mobile myTouch 3G Slide using XDA App
The reason it shows that is sometimes, for whatever reason, the sim doesn't push it's assigned mobile number to the phone itself. Making it unreadable, this actually happens on blackberries, iphones, etc as well. Just ask for that activation message via the OTA and that should fix it. As I've said, I have never had it fail for me when I have a customer experiencing the problem.
i am having the same problem. although its not a BIG deal but i do sometimes like to use tikl. but if what you are saying about having the activation message sent. if i change carriers will it get fixed? im asking because i will soon be changing carriers
rodriguez27 said:
i am having the same problem. although its not a BIG deal but i do sometimes like to use tikl. but if what you are saying about having the activation message sent. if i change carriers will it get fixed? im asking because i will soon be changing carriers
Click to expand...
Click to collapse
It certainly should. It's always been the network/sim card not telling the phone the right information. So by changing networks it just quickly resolve itself. Especially with any cancel and then an activation.
smerff said:
It certainly should. It's always been the network/sim card not telling the phone the right information. So by changing networks it just quickly resolve itself. Especially with any cancel and then an activation.
Click to expand...
Click to collapse
smerff said:
The reason it shows that is sometimes, for whatever reason, the sim doesn't push it's assigned mobile number to the phone itself. Making it unreadable, this actually happens on blackberries, iphones, etc as well. Just ask for that activation message via the OTA and that should fix it. As I've said, I have never had it fail for me when I have a customer experiencing the problem.
Click to expand...
Click to collapse
I don't know how to explain this any other way....
My phone + my sim + ANY 2.2 ROM = phone number unknown
My phone + my sim + ANY 2.1 ROM = my phone number shows up correctly
My phone + my mom's sim + ANY 2.2 ROM = her phone number shows up correctly
I've called T-Mobile customer care 7 times over 2 weeks. They've sent probably 10 OTAs over multiple days. They have gone through what they do with every other customer with this problem. They suggested I go to a T-Mobile store and get a new sim card.
I went to T-Mobile, got a new sim card, number still shows up unknown in 2.2, but when I flash 2.1 it shows up no problem. I called customer care again, and they tried over and over to get it to display without any luck. They are at the point that they want to replace the phone. I will wait until T-Mobile releases 2.2 and see what it displays...
This is happening for A LOT of people.
PS - I just flashed the stable CM6 (8/28/10) and it still displays the number as unknown.
In CM6, hit Call Settings -> Additional Settings -> My Phone Number
The issue is because there's no MSISDN written to the SIM, and no tag name for it either. I added this option because I had the same issue. Just set your number and it will write it to the SIM.
cyanogen said:
In CM6, hit Call Settings -> Additional Settings -> My Phone Number
The issue is because there's no MSISDN written to the SIM, and no tag name for it either. I added this option because I had the same issue. Just set your number and it will write it to the SIM.
Click to expand...
Click to collapse
Everybody...Cyanogen HAS SOLVED THIS ISSUE!!!
While my sim did have the number stored as it showed up in 2.1, doing this DOES MAKE THE NUMBER DISPLAY!
Thanks Cyanogen!
cyanogen said:
In CM6, hit Call Settings -> Additional Settings -> My Phone Number
The issue is because there's no MSISDN written to the SIM, and no tag name for it either. I added this option because I had the same issue. Just set your number and it will write it to the SIM.
Click to expand...
Click to collapse
The only options I have in "additional settings" is for Caller ID and Call Waiting. I don't have an option for "My Phone Number". I was on RC1 previously but flashed Stable last night.
-GB
Sent from my Rooted T-Mobile myTouch 3G Slide using XDA App running CM6.0.0 Stable.
cyanogen said:
In CM6, hit Call Settings -> Additional Settings -> My Phone Number
The issue is because there's no MSISDN written to the SIM, and no tag name for it either. I added this option because I had the same issue. Just set your number and it will write it to the SIM.
Click to expand...
Click to collapse
GeekBrat said:
The only options I have in "additional settings" is for Caller ID and Call Waiting. I don't have an option for "My Phone Number". I was on RC1 previously but flashed Stable last night.
-GB
Sent from my Rooted T-Mobile myTouch 3G Slide using XDA App running CM6.0.0 Stable.
Click to expand...
Click to collapse
Did you wipe before you installed? If so, try flashing stable again...it is there for me...
One issue though is that upon restart the number shows up as "unknown." You have to go back through this every time you restart your phone, but hey, its better than nothing!
Code3VW said:
I don't know how to explain this any other way....
My phone + my sim + ANY 2.2 ROM = phone number unknown
My phone + my sim + ANY 2.1 ROM = my phone number shows up correctly
My phone + my mom's sim + ANY 2.2 ROM = her phone number shows up correctly
I've called T-Mobile customer care 7 times over 2 weeks. They've sent probably 10 OTAs over multiple days. They have gone through what they do with every other customer with this problem. They suggested I go to a T-Mobile store and get a new sim card.
I went to T-Mobile, got a new sim card, number still shows up unknown in 2.2, but when I flash 2.1 it shows up no problem. I called customer care again, and they tried over and over to get it to display without any luck. They are at the point that they want to replace the phone. I will wait until T-Mobile releases 2.2 and see what it displays...
This is happening for A LOT of people.
PS - I just flashed the stable CM6 (8/28/10) and it still displays the number as unknown.
Click to expand...
Click to collapse
Interesting, the closest thing I've seen is a blackberry do it before. Can't say I've ever seen it on an android device without an OTA working. If the OTA doesn't work on a blackberry you just have to manually program your number in. Perhaps if you have a friend or pop into a t-mo store they can let you use one temporarily to set it up. My memory sucks on it but once your sim is in the blackberry I *think* it's settings > options > advanced options > sim card > my number or stored number. Something like that. If you can get it, the thing is though, the ota does the same thing. So theoretically you shouldnt have to do this if it is a sim error. The fact you're saying it doesnt happen in any other versions of android with the same sim I would agree it has to be some glitch in the s/w. How to fix it besides trying a manual program in a blackberry or any other device that lets you do so is beyond me. ;/
For some strange reason my phone number wont work on my phone. If I call it from another phone it says the " the number or code you have entered is incorrect, try again". I took it to Sprint and they couldn't figure it out. They were going to give me a new phone and send me on my way but the same thing happens on the new phone. Now a number I've had for 12yrs I may have to change it. I wonder if I can switch services and keep the same number? Has this happen to anyone?
I'm wondering, were you using a 3rd party VVM app?
Sent from my PC36100 using xda premium
I thought it may have been google voice but I disabled that and still nothing. I don't think it would make my phone not be able to do do anything, even after they reset my phone, de-activated then re-activated my service, and switched to a new phone..
I see Sooooo many people have major problems after using Google voice. Like the can't get calls anymore, or can't get texts. I've always stayed away from it, but always read awful stuff.
Are you sure you disabled it properly, did you disable it from a desktop website?
There are a few guides floating around the forum RE: Google voice. Sorry, can't remember where, exactly.
Sent from my PC36100 using xda premium
I went and picked up another Evo from Sprint, the free one they try'd to reset yesterday. Everything works now, I can make calls and receive them. The funny thing is they dont know how it got fix. The tech came in the morning to try and fix it again and it worked itself out. They still have no clue what happened.
I was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
BGray210 said:
I was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
ianmb said:
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
Click to expand...
Click to collapse
Yes, San Antonio was one of the first markets with Sprint to have 4G WiMax and then 4G LTE. It had been running just fine for months, but suddenly stopped working. Even after flashing stock back on without root or any added apps besides Sprint's auto-downloads, it still had the problem. Took it to the store yesterday and baffled them all for 2 hours before they ordered me a replacement. They even tried a new sim card because I told them that I've had problems intermittently in the past with the Roaming Guard popping up and forums stated it could be a bad sim card. The Sprint # codes wouldn't even work. Anyways, they ordered me a replacement- won't have it until Tuesday but thanks for the response. I had never heard of anything like this happening before and it struck me as odd. I even checked the settings for the network and they all checked out fine, Sprint store reps did the same and were just as perplexed as I was.
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Txdaredvl said:
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Click to expand...
Click to collapse
Yes, I am on Sprint Note 4, but the pound codes wouldn't even work. As soon as I put in the last # sign it just cleared out the dialer. I found a complete list of # codes on sammobile or samfirmware site, can't remember which, and even Sprint attempted them. I had flashed back to stock available on Sammobile prior to going to Sprint, but it still didn't work. You don't think different flashes or ROMs or kernels could have caused this do you?
Anyways, I have the insurance through Sprint and have a new one on the way Tuesday. I just hate not being able to figure out a software related problem. I was also trying to find a way to do it manually while rooted, but couldn't find the right edits because I cannot even remember how to get into the correct settings at the moment-mind cluttered with too many projects.
I appreciate all of the responses though and really enjoy learning about my device on xda and hope to either create my own apps or even cook a ROM in the near future.
Wi-Fi Calling is not working at all on my stock s7. Is anyone else experiencing this? Getting enablement error. Spoke with sprint tech support who is stumped and now escalating up to higher level team.
Rest of phone (including wifi and hotspot/tethering) working as it should.
Saw one post about disabling Bluetooth and BT share. tried that with no improvement.
-Josh
What kind of testing would help?
I have never used this before, so keep it simple, lol
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
cwb1231 said:
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
Click to expand...
Click to collapse
That sounds promising.They have called me three times to keep escalating. Any chance you would PM me your #. I can ask them to look at your acct to figure out how to fix mine.
Also if you have air rave try turning that off
cwb1231 said:
Also if you have air rave try turning that off
Click to expand...
Click to collapse
I didn't have any problem with the Airrave and my S5 using Wi-Fi calling.
I think I had to do that sometimes because the phone was trying to use both or maybe just to eliminate that possibility
Anyone have a solution for broken Wifi calling. I tried everything I could find including calling Sprint. Running the latest Sprint S7 update, was working before the phone updated. Really not looking forward to do a hard reset.
It's a problem with the data code on your account.Will need tech suport to fix. They are having issues with s7 not carrying code over correctly.
Thanks for the feedback, do you mean my Data plan is not correctly assigned to my phone. Ill probably have to hold the Sprint tech supports hand to get it going.
No its the actual billing codes for your account and how wifi is coded on it.
No luck, was on the phone with Sprint for almost an hour. They made a Ticket, said said I needed to take my phone to a repair center
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
cwb1231 said:
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
Click to expand...
Click to collapse
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
WiFi Calling
I have the same issue with my S7 with the enablement error. I have been on the phone with Sprint for over 1 hr with no help - they state it is a Samsung software issue. I went back to Best Buy where I got the phone and exchanged it but still the same problem. I took it to the Samsung reps who were there and they also were stumped. I reached out to "advanced tech Sprint support" who stated its a Samsung issue and will not be fixed until they release a patch. I reached out to Samsung and they stated they were not aware of any issues and to send the phone to their repair center - which made no sense. I see online that some have no issues doing wifi calling so it may be luck of the draw. I think that Sprint will blame Samsung who in return will say no issue. I am going to try to exchange the phone again and hope the third time works!
Did you try a hard reset?
Check wifi calling doesn't support messaging at this time..
Chetski said:
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
Click to expand...
Click to collapse
It only recognized my fingerprint a couple times then after power off it wouldn't. Also found out find my mobile isn't set up by Samsung for s7 yet, if ever. . I use nova launcher which allows you to save your homescreen and widget and folder setup. I use helium to back up apps and data. Restore was only really annoying not horrifically annoying. Don't forget to back up your Samsung account settings and take your sd card before you go the Google reset route. . The most help I got was the Samsung rep at best buy
Sent from my SM-T330NU using XDA-Developers mobile app
Thank you, that's a lot of great information.
I had 4 reps tell me to bring it to store for repair, did hard reset etc.... got up to advanced tech support before guy called me and said "fixed the problem, go ahead and try"and worked fine after that.