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..
Related
I'm running MoDaCo's 1.1 and HAVE NOT installed the new MR.
On my college campus, I get HORRIBLE signal; but that is nothing new. I usually switch to roaming and pull from some strange tower in some far away land. Not usually a big deal. Well, today on campus, my signal dropped off completely and didn't switch over to roaming. I figured I'd just update my PRL and maybe that would help. No go. It searches and searches and eventually comes up with error 1012. Trying to update my profile does the same thing...
I pulled the battery out, and my signal came back (two bars, woo -_-) but I still cannot update any of the above.
Is this some awkward anomaly, or is it because I don't have the new MR? Could it be something I haven't thought of?
I've had that issue before but I just tried it again later and it worked. I couldn't find out why it didn't work the previous times but I assume it's probably a connection issue or whatnot... just keep trying from time to time and hopefully it'll work for you eventually like it did for me.
I am on Fresh .6 getting this error all day now. tried again and again all over a 60 mile range. 1012
gqukyo said:
I've had that issue before but I just tried it again later and it worked. I couldn't find out why it didn't work the previous times but I assume it's probably a connection issue or whatnot... just keep trying from time to time and hopefully it'll work for you eventually like it did for me.
Click to expand...
Click to collapse
ya know what? you're right. about 20 minutes ago, it "just worked". color me confounded...
So last night I noticed my phone had no signal, thinking it was a tower issue I waited till morning, nope. I've tried a reboot, reset, installing a different rom, prl update... nothing is working. I didn't change any settings or download anything last night either. What would cause this????
Have you tried going into range of another tower? Your local tower may be down, it happens.
no not yet, how far on average do you think they separate towers?
This will give you an idea of how far apart Sprint cell towers are, at least in my area.
http://maps.google.com/maps?f=q&sou...-88.21968&sspn=0.007664,0.013797&ie=UTF8&z=11
I got the data from an app I had on my old BlackBerry.
I'm sure this is not the problem but I had the same problem a while ago then realized I forgot to pay my bill...lol
i actually had a similar problem. it ws fine last night but then this morning i had no bars and data read "1x" instead of "Ev". it was like this all morning but it just started working like normal about 5 minutes ago. so i guess it was just a tower messed up here or something
Papa Smurf151 said:
I'm sure this is not the problem but I had the same problem a while ago then realized I forgot to pay my bill...lol
Click to expand...
Click to collapse
Fail. LOL
Well, at least you figured it out.
Got my phone working. Turns out my prl file was bad, I tried to do an OTA update before but it would just give me an error. So I started looking around and found there was a prl update back on 7-13, I downloaded it and did a manuel update. Service came right back. BTW thanks for the suggestions.
On 2 occassion today my phone has had the incorrect time. When it had the wrong time, I could still text and make phone calls. It was 9AM but was displaying noon.
I unchecked the option to obtain the date/time from the network. I then checked it again and it corrected the clock in the top panel (place where the signal and mail icons display.) But the clock on the beautiful weather widget was still off.
Then it happened again randomly. It was 1:50 and it was showing 7:50.
I rebooted the phone and it seems correct now.
Never had this happen before. Now, I don't know if this is coincidence or not but the phone did a software update 2 nights ago.
Any thoughts?
Whiteice
Then a bit later today, it did the same thing.
same here
dude, I've been having those problems ALL EFFING DAY today. I have myself half convinced it's because I flashed the new rooted OTA update, along with the radio kernels posted on here. What setup are you running? Are you stock? Have you installed the new OTA update? If someone on here can figure this out you're my hero.
As a side note, when my phone time was off, it said in my settings that it was pulling time info from the "w. africa" time zone... I'm in Michigan. If I refreshed the option to "load time from network", it would correct for a second then go back to africa... wtf
Dnomyar220 said:
dude, I've been having those problems ALL EFFING DAY today. I have myself half convinced it's because I flashed the new rooted OTA update, along with the radio kernels posted on here. What setup are you running? Are you stock? Have you installed the new OTA update? If someone on here can figure this out you're my hero.
As a side note, when my phone time was off, it said in my settings that it was pulling time info from the "w. africa" time zone... I'm in Michigan. If I refreshed the option to "load time from network", it would correct for a second then go back to africa... wtf
Click to expand...
Click to collapse
Everything on my EVO is stock, nothing rooted. And I did the OTA update 2 days ago via WIFI.
well I'm somewhat glad to hear it's not because of the root, but it's still disappointing. I've tracked it down to the new radio kernels though... and I believe the reason is the cell network boosters some buildings use. My company I work at has them, and now that's the only place I have this problem. Didn't have it with the old kernels, but I do with the new ones. It's fine everywhere but at work where the boosters are
I don't remember when hut recently my evo also had he wrong time, I don't remember and of the details but I was recently and it seemed like I notes it twice in one day....
Im on stocked rooted 3.29
Sent from my PC36100 using XDA App
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).
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