Database Users

data call failure error 67

anybody else get constant data call failures when taking the phone out of sleep mode after disabling data connection always on? i was told turning it off will help battery life. the only way i can fix it is by updating my profile or doing a full data profile reset.
this has happened on both damage & fresh roms.

Did it happen yesterday about 2pm est? I have the paper at home with the instructions. I had to call advanced tech support twice yesterday and it finally cleared up around 7pm est after a couple of internet resets in advanced hidden menu. The one that worked, I didn't update profile, updated prl automatically. I cancelled when it tried looking for updates. Phone is working good today!
Sent from my PC36100 using XDA App

markus_del_marko said:
anybody else get constant data call failures when taking the phone out of sleep mode after disabling data connection always on? i was told turning it off will help battery life. the only way i can fix it is by updating my profile or doing a full data profile reset.
this has happened on both damage & fresh roms.
Click to expand...
Click to collapse
Have you flashed one of the customer kernels recently?

no custom kernels were used. this happened both yesterday and today with 2 different roms.

When I get that error I just do a Update Profile, it clears it right up.

danoftw said:
When I get that error I just do a Update Profile, it clears it right up.
Click to expand...
Click to collapse
exactly what i do too...

danoftw said:
When I get that error I just do a Update Profile, it clears it right up.
Click to expand...
Click to collapse
i know this, my question is why does it keep happening?

reboot
i had the same thing.
you should reflash fresh...

I had this constantly happen to me. I did ##rtn# and haven't it happen once since then.
Sent from my PC36100 using XDA App

i get this error when trying to connect to my PC via Internet Sharing with 3/4G.
It workes fine with WiFi though.
I will most likely end up calling Sprint to see what's up with this.

i posted fix here
http://forum.xda-developers.com/showthread.php?p=11836696#post11836696
posted solution here hope that helps

Error Code 67 - No 3G Data - Out of the blue!

Just happened out of the blue. Had wifi on, but wasn't at home, so went to turn it of, did some facebook checking and then checked for a prl update...now no 3g data and EC67.
Looks like it forgot our sprint user name and password.
Tried doing a ##3282#, which did nothing and ##775# doesn't work.
Running Fresh 3.2 and the new htc kernel.
Sent from my PC36100 using XDA App

Have you tried updating profile? That'll usually fixit
Sent from my PC36100 using XDA App

kixcastillo77 said:
Have you tried updating profile? That'll usually do it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Tried that but of course sense 3G doesn't work, it gave me the same error faster than I could press dismiss.
I'll try again via wifi and 4g.
EDIT: Looks like that fixed it - Thanks! Haha. I can't believe that I didn't think to try it over wifi/4g, but I remember trying to update my PRL over wifi/4g and it wouldn't work, awhile back.
EDIT 2: It didn't work. Haha. The Firmware updated without giving me the error, but now the profile update is giving me a 1020 error.
EDIT 3: I think I fixed it. I remembered that I had that startup cleaner app running and that it might be killing off the handsfree updater. Looks like I'm golden now.

I had the same issue yesterday, I updated profile a few times, didn't work. Updated PRL twice, it worked. I think it was a coincidence that it worked, probably an issue at Sprint's end.

I was having this issue last night and couldnt figure out why.. my wifi tether kept stalling out and my 3g kept going in and out.

Same here, they must have done something yesterday

Welcome to hell, dude. My wife and I have been experiencing these errors for weeks now. I have tried everything in the book and nothing seems to be a permanent fix. Updating PRL and Profile is temporary at best. PRI Update to 1.40, then to 1.77 did nothing either. This bites.

Wow. When it first happened I was taking my Grandma to the store and half expected to find everybody on XDA freaking out and it had been some national/regional bug that screwed everybody's evo up - Must not have been big, but something to hit a few of us.
It's working just fine this morning after I did a ##3282# and turned up startup cleaner.

I had this same issue the last couple days. Fine today so far. Nyc area btw.
Sent from the void...

I just called them and they told me that they are having network issues in my area and there is an "open ticket." I'm sitting here thinking something is wrong with my phone until 3 other people on sprint told me they couldnt make calls.

same here nyc also did 1.7 pri update i figure thats was the problem now i am stuck with 1.34 (hours and hours took me to go back ) now i dont know what to do should i go back to 1.7 since is every one?

sf103100 said:
same here nyc also did 1.7 pri update i figure thats was the problem now i am stuck with 1.34 (hours and hours took me to go back ) now i dont know what to do should i go back to 1.7 since is every one?
Click to expand...
Click to collapse
Not the PRI. I've been with 1.34 forever, never changed it and I had this issue.

wuclan48 said:
Not the PRI. I've been with 1.34 forever, never changed it and I had this issue.
Click to expand...
Click to collapse
i had 1.40 did update to 1.7 had major problems so i had to go back to 1.34 now i cant get 1.40 back (i dont have problems with 1.34 )
Just be clear

sf103100 said:
i had 1.40 did update to 1.7 had major problems so i had to go back to 1.34 now i cant get 1.40 back (i dont have problems with 1.34 )
Just be clear
Click to expand...
Click to collapse
I updated to the 1.7 PRI last night after I got the error codes figured out. Haven't had a problem, yet, but it's been off this morning anyhow.
Never had a problem with 1.34 PRI, but last night, after installing 1.7, I did a few speedtests in bed and I constantly got 150/190 up and 550/600 down, and before I was getting either better than those, by 50% or worse than those by 50%.

This is a frequent occurrence (at least in New York City). It's annoying but don't worry about it. Anything you try to correct it will only be a temporary fix until it eventually goes away at random.

I've had Error Code 67 come up once in a while since I got my phone. Sometimes it comes in bursts, maybe 4 or 5 in a row. Super annoying. I called Sprint today and they had me update the profile a couple of times which did nothing as I kept getting the error while on the phone with them. They are sending me out a replacement Evo in the mail which I should get tomorrow. I'll report if it fixes the problem. Tech Support mentioned they do have them in stock if anyone else feels like they might be in the same boat.

FunkyAroma said:
This is a frequent occurrence (at least in New York City). It's annoying but don't worry about it. Anything you try to correct it will only be a temporary fix until it eventually goes away at random.
Click to expand...
Click to collapse
I'm in NYC as well and I can't stand this error. If there was a way to supress I would be a lot more happy since if the error pops up while you are typing a number into the dialer it will clear out all the numbers after you press dismiss.

The error code is a result of Sprint working on upgrading the network to increase 3G capacity. I was getting the error messages when my PRI was 1.37, and I have gotten them a few times after updating to 1.77. At first I used to try updating my profile, but I would get the error message again. What worked for me was turning off my 4G (I'm in NYC, and there is a few test towers up), then turning on airplane mode for a minute or so, then turning it off again. For me, the 3G would kick in, and I won't have the error.

I am getting the error on 3G with 4g off or 4g since I got the phone. Sprint rep said it's not normal so Lets see what my replacement does.

looks like it hard us in NYC hard.
anyone else have horrendous battery life today after fixing this? I barely used it, I only got about 8 hours. I fully charged it when i got home, and literally watched it go down from 100% to 80% in 15 minutes..

[Q] Error sending/receiving MMS "National access coverage not available."

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.

[Q] No longer receiving sms in stock messaging app

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.

[Q] EVO Shift: Data Call Failure after Temp-Root

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