Hello,
Lately I have been unable to send or receive text messages that contain pictures or videos. The error message is always the same "National access coverage not available."
I called Verizon, on Thursday of last week (1-13), and the technician was unable to figure out the problem. He escalated it to the next level and said that someone would be contacting me in a day or 2. Well it's now Wednesday (1-19) of the following week and so far, nothing!
Has anyone else run into this problem? If so, what's the fix? Any help would be appreciated, especially since Verizon has been no help at all!
I'm using a Moto Droid2 ver, 2.3.2 Rooted and OC'd @ 2.25Ghz
Thanks,
Scott
Dial *228 and update your PRL.
silverfang77 said:
Dial *228 and update your PRL.
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately, it didn't work. I updated it waited the 15 minutes. When it didn't work I rebooted the phone figuring maybe it needed to be refreshed or something, (long time windows tech, reboot fixes everything!) but still nothing. Just that same message.
I get the exact same error when sending or receiving MMS 50 percent of the time with the first initial try... *228 does not fix this.. verizon cannot fix it either...
OK, got tired of waiting for Verizon to call back. On the phone with 2nd tier support now for about the last hour, so far nothing.
Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.
OK, got finished with the Verizon tech, who was very helpful, but we still could not resolve the issue.
She removed and reloaded my data from the server, switched me to another IP address and did a few other behind the scenes things but nothing worked. She suggested doing the factory reset, but I'm ready to give up troubleshooting this issue yet. If all else fails, then I guess I will have no other option.
Since sending MM text's in not a huge part of what I use my phone for, I may just wait for the next release of the software and hope that fixes it.
In the mean time I'll just keep playing with settings and searching Google and the message boards in the hope that someone can come up with a fix that doesn't involve having to wipe it.
rtfield said:
Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.
Click to expand...
Click to collapse
I used to use that app, but removed it long before this started happening. I wonder if it left behind some orphan files that are somehow in there wreaking havoc?
Since the problem still existed even running the phone in safe mode, I would think that would not be the case, but anythings possible.
my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through
1250x said:
my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through
Click to expand...
Click to collapse
That's the thing. Since so many people are having the same or similar issue, I just find it hard to believe it's not something on Verizon's side or with their software. This many people screwing up their phone's in the exact same way all around the same time just seem a little suspect to me.
Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.
rtfield said:
Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.
Click to expand...
Click to collapse
Yeah, I guess I'm going to have to try something. I want to make a nandroid backup first just to be safe and then I'll give it a shot.
Thanks.
This is great!
So, I just finished the factory reset (which DID fix the problem) and was starting to configure all my custom settings when the Verizon tech I spoke with called me back. She said that she had just spoken to Motorola and they said it was a known problem with their phones! They are not sure what it is yet, but they are working on it. In the mean time, the only thing they can suggest is to reset the phone as a work around!
I asked the Verizon tech if there was any kind of documentation about this that she could send me, but of course there isn't. And there's also nothing on the Motorola site about the error either, at least nothing I could find.
While it doesn't make the situation go away, it does make me feel better knowing what the root of the problem is, sort of. Only problem is, there is no guarantee that it won't happen again.
i turn airplane mode on then off... works for me
Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App
S.Meezy said:
i turn airplane mode on then off... works for me
Click to expand...
Click to collapse
Yes, I had heard that worked for some people, and I did try that but it still didn't work. Even so, that would only be a work around and not really fixing the issue.
V.A.T.Juice said:
Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Interesting, since I did the factory rest I haven't had a problem. If it happens again, I'll be sure to check that.
Related
yes i did a search =) and i turned up nothing... plenty of people with the problem, but no one with any answers. this has been going on since i got the phone.
\ no wifi is not on,, i did the updates when stock, im now running fresh 1.1 and problem has not changed. i get the text (in both messages and handsent) but all there is, is a box to press to download. \
doing so does nothing but gives me an -unable to download- message.
any help would be uber great. thanks so much in advance
is it safe to try updating firmware again now that i have fresh 1.1 on there?
kraash said:
is it safe to try updating firmware again now that i have fresh 1.1 on there?
Click to expand...
Click to collapse
Wont work...
Sounds to me like you have a data issue of some kind. The stock SMS app is not very good. I have never heard of this issue though.
Call sprint and tell them that you cannot recieve MMS and they can reset stuff on their side. I have had to do that because I wasn't getting SMS, they put me on hold for a few minutes reset it, then theyll send you a test message that should work.
Kcarpenter said:
Wont work...
Sounds to me like you have a data issue of some kind. The stock SMS app is not very good. I have never heard of this issue though.
Call sprint and tell them that you cannot recieve MMS and they can reset stuff on their side. I have had to do that because I wasn't getting SMS, they put me on hold for a few minutes reset it, then theyll send you a test message that should work.
Click to expand...
Click to collapse
My friend has/had this same problem. I sent him some pictures once and same thing happened; no one has sent him a MMS since, so I don't know if it's still an issue.
Anyway if I were you I would contact Sprint Customer care.
theresthatguy said:
if I were you I would contact Sprint Customer care.
Click to expand...
Click to collapse
x2
most likely your account needs to be re-provisioned
Im having the same problem and Sprint seems to know nothing about it. I have spoken to customer service numerous times about this and even brought it in to the store. The only thing they suggest is a factory reset. I have tried that yet as I dont think that will fix the problem.
ya they tell me on the phone "lets do a hard restart, that fixes everything".. but i havnt done it because i dont want to mess up my root and rom, and i dont even know what will happen.
ok so they tried doing the reprovision today (i actually got some one who new what they were talking about) and it didnt work.
the only step left is a hard restart. will this affect fresh 1.1 or root in any way?
It Could be my provider problem, but just wanted to make sure.
Is anyone having failed attempts at calling , where it continues to keep ending the call every time u press talk?
Yep. When that happens nothing works. Texts. Email. Everything. Reset fixes it.
Sent from my Nexus S using Tapatalk
bkfresh1 said:
It Could be my provider problem, but just wanted to make sure.
Is anyone having failed attempts at calling , where it continues to keep ending the call every time u press talk?
Click to expand...
Click to collapse
Happened to me first time today, had phone since launch.
Flashed my first customer ROM yesterday (CM7) and thought it might be that. Only a reboot fixed it, not even switching to Airplane mode.
How often does it happen to you guys?
Mujja said:
Happened to me first time today, had phone since launch.
Flashed my first customer ROM yesterday (CM7) and thought it might be that. Only a reboot fixed it, not even switching to Airplane mode.
How often does it happen to you guys?
Click to expand...
Click to collapse
it started happening to me recently, and quite often.
i really dislike pressing call over and over for it to keep failing.
I thought it was my carrier too, but normally a reboot fixes everything!
That was happening to me quite a lot. During a phone call it would drop the call but had full 3g service. Nothing was working, calls, internet, emails, google chat.
Hasn't happened since I did a factory reset. It's a pain in the arse to keep entering all the info again but it hasn't done it since.
I guess it a temporary solution.
It happens to me as well.
Happens to me too. I'm not sure if it's just the Nexus S since it happened pretty often on my Nexus One. I use Google Voice with all calls and I think that that may be the culprit.
It may have started with the 3.3.2 update for me.
It needs a reboot to fix it. Really annoying.
This happened to me yesterday. At first I was like wtf is going on here, then I rebooted the phone.
Two days ago I un-installed the e-bay app as I noticed it started up all the time by itself, and since doing so have not had any calls dropping out.
Ok heres one for you guys!
Theres been multiple times i've been asked why I didnt answer my phone when people called, but on my phone it has not rung nor does it show a missed call. My GF just called and said she called a few minutes prior but i didnt pick up. She knew i mentioned this problem so she called again and i got it.
I REALLY dont like this bug......
Calls drop with 2.3. 3 too.
Dial..., nothing. Dial..., nothing.... sometimes it takes multiple attempts, with mane green bars.
Sent from my Nexus S using XDA App
bkfresh1 said:
It Could be my provider problem, but just wanted to make sure.
Is anyone having failed attempts at calling , where it continues to keep ending the call every time u press talk?
Click to expand...
Click to collapse
I have i sinilar problem that i press call or speed dial then It does not call at all just goes back to the dialler screen.
I keep getting an error that pops up on my phone occasionally : Error code 107 - data call failure.
Anyone know anything about this or how to fix it? My Mom gets it on her shift too. It's annoying, but doesn't seem to affect anything on the phone.
tatonka_hero said:
I keep getting an error that pops up on my phone occasionally : Error code 107 - data call failure.
Anyone know anything about this or how to fix it? My Mom gets it on her shift too. It's annoying, but doesn't seem to affect anything on the phone.
Click to expand...
Click to collapse
I got it a lot on my hero, and when I first got my Shift. I called and complained, told them I'd already been through factory resets, ## dialer codes, everything.
Eventually after a couple girls finished reading an apparent universal HTC tech support guide to me they passed me along to a nice fellow. He said he'd seen that problem a lot, changed my user name, I reset my data profile again and VOILA! Over a month, no data call failure!
Sent from my MikShift.
In settings, wouldn't update profile fix this? Even though errors might pop up during the process, just ignore them and let the update do it's thing. That is if it is what I think it is.
herbthehammer said:
In settings, wouldn't update profile fix this? Even though errors might pop up during the process, just ignore them and let the update do it's thing. That is if it is what I think it is.
Click to expand...
Click to collapse
yep your right... i think ...
amehdi43 said:
yep your right... i think ...
Click to expand...
Click to collapse
Not every time. For me update/reset/complete device wipe didn't do it. Even ruu'd and did factory reset that way (since factory reset in our current bootloader boots to clockwork, wanted everything back stock.)
Sent from my MikShift.
I get this once in a while also, but it happens when I go from roaming to Sprint. Or at least that seems to me when it happens.
Sent from my HTC EVO Shift 4G using XDA App
herbthehammer said:
In settings, wouldn't update profile fix this? Even though errors might pop up during the process, just ignore them and let the update do it's thing. That is if it is what I think it is.
Click to expand...
Click to collapse
wardfan220 said:
I get this once in a while also, but it happens when I go from roaming to Sprint. Or at least that seems to me when it happens.
Sent from my HTC EVO Shift 4G using XDA App
Click to expand...
Click to collapse
Updating the profile didn't fix it. I updated it Tuesday afternoon with no errors popping up, and still got the error code 107 this morning.
I think Wardfan220 is at least partially correct. More often than not, it happens at home, where I'm roaming about 90% of the time. It happens at work occasionally though, but that's on a repeater, so I could see that being the cause. I never got the error on my Hero though, that's why I was thinking it was an issue with just this phone.
tatonka_hero said:
Updating the profile didn't fix it. I updated it Tuesday afternoon with no errors popping up, and still got the error code 107 this morning.
I think Wardfan220 is at least partially correct. More often than not, it happens at home, where I'm roaming about 90% of the time. It happens at work occasionally though, but that's on a repeater, so I could see that being the cause. I never got the error on my Hero though, that's why I was thinking it was an issue with just this phone.
Click to expand...
Click to collapse
Yeah, I never got it on my Hero also, but it seems to be, for me at least, when switching from roaming back to Sprint's network and vise versa, I was also getting a 107 erroe with my data at one point, but that was jsut a billing issue (wife didn't pay, lol).
Using stock sense and sprint/gv integration and i can receive texts in gv as well as send them from the stock messaging app and gv.
i've contacted sprint on the phone a couple times and got to the highest level tech support and they couldn't fix it. also tried the sprint store and they just want to give me another evo. they have one on order, but i'd much rather keep my rooted evo! the new one will likely have 2.3 installed stock and i'll need to wait for root.
this really doesn't seem like a hardware issue anyways, seems like it's a network side problem.
i've made sure sms forwarding is enabled to my mobile number on gv, tried factory and hard resets multiple times. tried unintegrating and reintegrating my sprint number with gv.
the weird thing is even when i'm unintewgrated and using just vanilla sprint i don't receive texts at all. i can send them, make and receive calls too but never does a text come to my phone.
there doesn't seem to be anyone else reporting this problem i8n my area.
phone is rooted, stock rom, the problem started after iu hard reset my phone. i was hoping a hard reset would fix some buis i was experiencing with the GB update. i can't say for sure this was because i hard reset, buit it's a huge coincidence that it happened at approximately the same time. i can't think of any logical reason the hard reset would affect my sms this way.
btw i installed a rooted version of 2.3.3 as well as the latest combo radio pack. that was over a week ago though and this issue just cropped up yesterday.
hopefully this post wasn't too jumbled and i gave enough info, any ideas?
edit: crap, should be in the Q&A forum, please move if necessary :/
Try updating your profile
Sent from my PC36100 using XDA Premium App
i've done that a bunch of times, so did sprint.
[Q] If you call one of the people you text, does the return text from them show up after the call?
dpilcher said:
[Q] If you call one of the people you text, does the return text from them show up after the call?
Click to expand...
Click to collapse
No it doesn't.
Brandito said:
No it doesn't.
Click to expand...
Click to collapse
Not what I was going through a few months back then, but I could make calls but not receive calls. I don't use GV either so probably not the same issue. Just thought I would ask, turns out those issues for me was my 3G going out on my phone. Ended up getting it replaced.
Hope you find a solution, I know how frustrating it is.
dpilcher said:
Not what I was going through a few months back then, but I could make calls but not receive calls. I don't use GV either so probably not the same issue. Just thought I would ask, turns out those issues for me was my 3G going out on my phone. Ended up getting it replaced.
Hope you find a solution, I know how frustrating it is.
Click to expand...
Click to collapse
sprint is ordering me another phone, hoping against it being a refurb, though then i likely have to wait for a new root method for gingerbread.
preferably they'd get it working on my current evo. i really think it has to be a network issue.
Brandito said:
sprint is ordering me another phone, hoping against it being a refurb, though then i likely have to wait for a new root method for gingerbread.
preferably they'd get it working on my current evo. i really think it has to be a network issue.
Click to expand...
Click to collapse
You should be good, I had two replacement refurbs as early as last week and they both had 3.7 on them. Watch for the sunspot on the screen when it boots initially (bright white spot in the lower half towards the middle), both of the refurb replacements had the bad screen. You can't see it if it boots all the way..you'll have to go to a bright screen to see it but it will just get worse to where you will see it all the time. Finally the rep gave me a NIB 004..also 3.7. Just make sure they don't update it, I would ask if you could do the activation as well so you can look for the screen issue on initial boot. Good Luck! Guess I didn't have to quote due to it being right above mine...lmao
Think they'll give me any trouble if I turn in my phone still rooted? I don't feel like unrooting it, not to mention if the new/refurb doesn't fix my issue I'm going to keep my current evo anyways.
I mean they've already approved me for the replacement.
I had the same problem
I had the exact same situation happen last weekend. All I did to fix it was to flash back to a Stock Sense 2.2 ROM, Update Profile/PRL, and then open EPST and Reset Data connection using THIS little tutorial.
foxtrotftw said:
I had the exact same situation happen last weekend. All I did to fix it was to flash back to a Stock Sense 2.2 ROM, Update Profile/PRL, and then open EPST and Reset Data connection using THIS little tutorial.
Click to expand...
Click to collapse
can't even get it to do anything after entering ##3283#, never even pops up a dialog.
foxtrotftw said:
I had the exact same situation happen last weekend. All I did to fix it was to flash back to a Stock Sense 2.2 ROM, Update Profile/PRL, and then open EPST and Reset Data connection using THIS little tutorial.
Click to expand...
Click to collapse
Ya..did all that and then some to mine..no dice. But good advice. Hardware issue won't be solved by software no matter the method I found out. Believe me..even went as far as unrooting and seeing if stock would be the same..it was.
The unrooting process is very easy and with the replacement coming in, why not. Sounds like hardware anyway. Here is what I did to go back and forth:
http://forum.xda-developers.com/showthread.php?t=1113620
You can also look at the stickies at the top of general/Q&A for options.
Good Luck.
dpilcher said:
Ya..did all that and then some to mine..no dice. But good advice. Hardware issue won't be solved by software no matter the method I found out. Believe me..even went as far as unrooting and seeing if stock would be the same..it was.
The unrooting process is very easy and with the replacement coming in, why not. Sounds like hardware anyway. Here is what I did to go back and forth:
http://forum.xda-developers.com/showthread.php?t=1113620
You can also look at the stickies at the top of general/Q&A for options.
Good Luck.
Click to expand...
Click to collapse
doesn't seem like hardware at all to me though. and if that's the case and I unroot and end up keeping this phone i just shot myself in the foot by locking my bootloader.
i wish i would have had them try activating another phone today to see if another phone would be able to receive the texts.
No need to unroot! Go to voice.google.com, click on the "gear" icon to go into Voice Settings. Find your gv/sprint phone number, click Edit and check the checkbox for "receive text messages on this device." Hit save, and enjoy.
jesuspgt said:
No need to unroot! Go to voice.google.com, click on the "gear" icon to go into Voice Settings. Find your gv/sprint phone number, click Edit and check the checkbox for "receive text messages on this device." Hit save, and enjoy.
Click to expand...
Click to collapse
that's only the FIRST thing I tried, along with unchecking, rechecking, removing integration, readding it..twice! and about a dozen combinations of applying settings, checking and unchecking boxes and finger crossing.
Brandito said:
that's only the FIRST thing I tried, along with unchecking, rechecking, removing integration, readding it..twice! and about a dozen combinations of applying settings, checking and unchecking boxes and finger crossing.
Click to expand...
Click to collapse
Apologies, but you didn't mention that you did this in your post. Had no way of knowing that you've already tried this.
jesuspgt said:
Apologies, but you didn't mention that you did this in your post. Had no way of knowing that you've already tried this.
Click to expand...
Click to collapse
I actually did in my first post, though that post is a bit of a mess I realize, it's hard to really put everything I've already tried in any neat order.
No worries either way, any suggestions are welcome at this point.
Hey guys, I'm hoping somebody might be able to lend me a hand.
After applying the Temp-Root to my EVO Shift (GB, 2.3.3 (temp-root found here)), I'm getting the following error message:
Data Call Failure
Error Code 67: Unable to establish wireless data connection.
Has anybody seen this message? It comes up randomly it seems. I'm still able to connect to the internet via wireless. I'm not really sure what the deal is. It's similar to another one going around, but the other refers to the username/password. This one does not.
I have googled the error message, but almost everything I come across is a mass hysteria of confused people. I've tried the things I've found.
I haven't tried rebooting, yet, as that'll kill my temp-root (doesn't work in most cases anyhow, from what I've read). But, I'm willing to try it tonight if no other options are available. I've tried updating profile and prl, but issue remains. Not really interested in getting Sprint support involved, as from what I hear they're mostly a bunch of... uhm... funny people.
Any help is appreciated!
I should also note: This may have nothing at all to do with the Temp-Root. As far as I can remember, it worked fine for the first day (I applied it about 2 days ago, I think). However, I didn't do anything that day that required use of the Wireless connection (but wireless was still enabled).
i got that error once and just rebooted and retemprooted and havent gotten it again
Upadte profile, thru settings
Sent from my PG06100 using XDA App
-somebody- said:
i got that error once and just rebooted and retemprooted and havent gotten it again
Click to expand...
Click to collapse
I'll try this tonight if no other resolutions come up (not at home currently). Thanks for the suggestion.
madplaya1 said:
Upadte profile, thru settings
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
As per my original post, I have already updated both profile and PRL. Thanks for the suggestion, just the same.
Edit: The problem may be due to billing issues. Will wait for that to get fixed and see if that fixes is. Will report back.
Another Edit: Does appear this is due to billing issues. Seems to be working just fine again, re-rooted and all.
Was getting this Error message for about a half a day a few weeks back. Updated PRL and Profile, didn't fix the issue. Called Sprint, turns out they were doing some work on the towers. Rebooted the phone and all was good. You might want to try and put the phone in Airplane mode for a few minutes. Then turn off Airplane mode, see if that helps.
prboy1969 said:
Was getting this Error message for about a half a day a few weeks back. Updated PRL and Profile, didn't fix the issue. Called Sprint, turns out they were doing some work on the towers. Rebooted the phone and all was good. You might want to try and put the phone in Airplane mode for a few minutes. Then turn off Airplane mode, see if that helps.
Click to expand...
Click to collapse
I actually tried all of that. In my case it seemed to be a billing issue, because as soon as that was cleared up (the phone didn't have service, and I didn't realize til' I tried to make a call) everything worked fine... and has since. Thanks, though.
No problem, here to help when I can. Glad you got it sorted out.
MikShifted on XDA Premium APP
TEAM MiK
Mik ROMs Since 3/13/11