I followed Bentenrai's guide to S-Off, Rooting, and Recovery. Internet (both Wi-Fi and 3G/4G data) works, but I am unable to make/receive phone calls or send/receive text messages.
The phone call error occurs after about 2 rings, which says "Error 16 (then in Spanish) Switch 694".
The sms error is: "sms error radio interface resource shortage" with details "cause code:64, error class: 2".
I tried everything from the "Phone does not work after S-Off" thread and was on the phone with 2 Sprint operators for over an hour. The first operator had me update profile and PRL, then had me turn off/pull battery while she did stuff twice to no avail. The second operator (who was mean and treated me like a moron) had me turn mobile networks off and on again, update profile and PRL, and pull battery (yes, she actually wanted me to pull the battery while the device was on; I powered it off first).
Is anyone else experiencing this or has anyone found a solution?
Thank you very much!
Yup, I found the fix. It's really easy! Tell the person to do a "CHLS Refresh", and then restart your phone.
http://forum.xda-developers.com/showthread.php?t=1194460
Thanks! I also just saw the thread in the General section about all the lucky people who achieved S-Off without the error.
I'll call them back tomorrow and report back.
i had the same error after rooting my phone, just try to call any number, and after listen to the message, it will connect you to a sprint rep. they will confirm some information with you and they will tell you that they will reset from their side and ask to turn off the phone for 30 sec and boom, it's a go.
After some thought, I realized both Sprint reps only had me pull the battery for a few seconds. I decided to leave the battery out for about 5 minutes and when I powered back on, I was able to connect to voicemail. I let it stay connected for a bit and then was able to make phone calls and texts. Suddenly, I began receiving Error 67 messages, so I updated profile and PRL. Since then, (knock on wood) everything has been ok. Phew!
Forgot to mention this tidbit of wisdom from the 2nd Sprint rep: She told me my problems with making calls was because there's an outage in my area. I told her that wasn't likely because I was using another Sprint phone to talk to her. She still persisted in saying it was an outage. Yay!
That's it? no other responses to this. My sons phone is a paper weight at the moment. He can't even dial Sprint and nothing else has worked. Anyone have another idea?
Related
Hi all,
Looking for a bit of help/advice.
On occasions, probably between 1-3 times a day, when I try to make a call on the Hero, the call appears to look like it is dialing out but it just sits there saying 'dialing' but never connects to the destination which can be any UK number / Orange 150 etc. Either rebooting the phone or leaving it for 10 mins or so fixes the problem, but it does become annoying!
At the same time as this happening, when I try to send an SMS, I get the error 'SMS not able to send' in the notification bar. Again, I have to keep trying and it sorts itself out.
A final problem and I am not sure if it is related or not is I have had numerous people try calling me at various times, my phone doesn't ring or display a missed call, nor do I get a missed call SMS but the person who tried calling me said the line was actually ringing first and then went through to voicemail. I have witnessed this myself by calling my phone, getting a ringing line but the phone doesn't respond?
Any ideas of help would be appreciated. This problem has existed on Modaco Roms 2.2, 2.8 and 3.0 - I'm on Orange UK.
Thanks,
Nick
I have the same problem with the Orange Poland. When I logged on to the 3G sometimes you can not call or send SMS. When I switch to the 2G network problem disappears.
Yeah, it is strange, I have done that too, turn off the 3G to 2G and back to 3G which sometimes cures it, but not all the time.
I've tried various things, made sure the apps aren't closed with Taskkiller or anything like that. There is no specific time or occasion it happens, it just does now and again.
Well I have tried everything. I recieved all the settings from my operator , changed over 10 ROMs and gone back to the original too, i tried what you said to turn 3G off , i reset to factory , i unrooted.....Nothing works for me. I just get "Unable to send". I also tried 4 SIMs from different operators !!!
A lot of people, after running Revolutionary, have been getting the "Error 16, Switch ____ " automated message when calling any number but Sprint Customer Support. This is a 100% definite fix for the problem. The good news is that it's an easy fix. The bad news is that the fix has to be done on Sprint's side:
--------------
A) Listen to the Error message, and at the end of the message you should be transferred to a special department that specifically deals with and fixes this error message. They'll work their magic in less than 5 minutes and then your phone should go through Hands Free Activation and work correctly.
--------------
B) If at the end of the Error message you don't get transferred, call the normal 888 Sprint Customer Support number from a different phone Option 1 (for English) -> Option 4 -> Option 4. Tell Tech Support to do a "CHLS Refresh". After they do that, do a Restart on your phone. Hitting "Turn Off" from the power menu will just put it to sleep. After your phone restarts, it should go through Hands Free Activation correctly and update the Profile and PRL.
--------------
C) If your phone doesn't go into Hands Free Activation, download "MSL Reader" from the Market to get your MSL code, or just ask the tech on the phone for it. Then, open up the dialer on your 3D and punch in ##786#. Hit Menu -> Reset. Type in your MSL. Your phone will reboot and go through activation. After that you should be good. Try and make a test call.
Hopefully that helps! If a mod could sticky this, that'd be great.
[CLICHE]Please hit Thanks if I fixed your problem![/CLICHE]
---------------------------------------------------------
A tech support person named Dawn and I found the fix last night when we couldn't get the number for the "special department". If you're curious as to why some people don't get transferred after the error message, it's because they're on an Employee referral plan, which are treated as employee accounts (Everything Plus plans). Those accounts go to call centers in Texas and Virginia only, while the "Error 16 department" is in Maryland.
Much appreciated for taking your time to write this buddy!
Like my help? Thank me
Called Sprint. The tech was very nice, but didn't really what error 16 was. Went through pulling out the battery and updating the profile, but neither method worked. It wasn't until I told him about the CHLS refresh that I read on the internet. He knew exactly what it was and went ahead and did it for my phone. Volia! the phone was able to dial out again! Thank you for all your help!
By the time I called today (about 5 PM) the rep I spoke to laughed as she guessed why I was calling today before even asking for any account info. She did the refresh immediately, So it appears that word is spreading of at least how to fix the "issue"...
Thanks for the tip ! having the sam issues here. already got my MSL code, but my problem is when I dial ##768# nothing happens just like a refresh of my dialer history .. also tried ##778# and and that brings up the Reverse Logistech support and i press Menu and reset on that and it says restore factory default so I went ahead and tried that and it rebooted and reset and the hands free setup activation did come on for that and so did the auto profile and prl update as soon a I booted back in but still a no go... im using the new Synergy evo 3d rom
any idea why ##768# seems to be inactive for me? thanks
Fixed it, you must have your phone off and the battery out for the fix to work. It didn't work for me the first time as I had to call from my phone, then pulled the battery.
Happily rooted now with tether.
Because I'm a moron. It's ##786#
Product F(RED) said:
A lot of people, after running Revolutionary, have been getting the "Error 16, Switch ____ " automated message when calling any number but Sprint Customer Support. This is a 100% definite fix for the problem. The good news is that it's an easy fix. The bad news is that the fix has to be done on Sprint's side:
--------------
A) Listen to the Error message, and at the end of the message you should be transferred to a special department that specifically deals with and fixes this error message. They'll work their magic in less than 5 minutes and then your phone should go through Hands Free Activation and work correctly.
--------------
B) If at the end of the Error message you don't get transferred, call the normal 888 Sprint Customer Support number from a different phone Option 1 (for English) -> Option 4 -> Option 4. Tell Tech Support to do a "CHLS Refresh". After they do that, do a Restart on your phone. Hitting "Turn Off" from the power menu will just put it to sleep. After your phone restarts, it should go through Hands Free Activation correctly and update the Profile and PRL.
--------------
C) If your phone doesn't go into Hands Free Activation, download "MSL Reader" from the Market to get your MSL code, or just ask the tech on the phone for it. Then, open up the dialer on your 3D and punch in ##786#. Hit Menu -> Reset. Type in your MSL. Your phone will reboot and go through activation. After that you should be good. Try and make a test call.
Hopefully that helps! If a mod could sticky this, that'd be great.
[CLICHE]Please hit Thanks if I fixed your problem![/CLICHE]
---------------------------------------------------------
A tech support person named Dawn and I found the fix last night when we couldn't get the number for the "special department". If you're curious as to why some people don't get transferred after the error message, it's because they're on an Employee referral plan, which are treated as employee accounts (Everything Plus plans). Those accounts go to call centers in Texas and Virginia only, while the "Error 16 department" is in Maryland.
Click to expand...
Click to collapse
They didn't do a CHLS refresh. . .didn't know what it was, but she did do a refresh. . and I THINK it worked. I did a test call. . .and then I made a call. but someone called me right after, and i believe that it rang once. . .and then all of a sudden I had a voice mail from them. . .MAYBE I accidentally sent the call to voice mail. . .I shall find out with more testing. . but for right now. .. I thank you!!!
Is there any way that this error can be resolved withOUT calling up Sprint, like via MSL hacking, and forcing it to HFA?
Is this possibly Sprint's way of detecting root? I had to call to fix this error too and the rep mentioned this is a new security feature on the network. Just can't find any info on this new security.
It took three calls to Sprint to get this done on my phone. It seems there is a small window of opportunity in which the phone must be turned off when the change is directed to the phone.
After the third attempt, all is good in the hood.
Thanks for the info, I have a good suspicion that without specifically asking for THAT refresh this might have been a much more drawn out process.
Id like to add that I had the same problem after rooting. No calls or texts were failing error 97 class 3. I called sprint and preformed the above steps and got me fixed in a few mins. About a week later (and several roms) my texts started failing again with errors 97 class 3 and error 64 class 2. I called sprint again and they got me all fixed up,(for now anyways.) Has anyone else experienced problems after their first call/fix to sprint.
str8upx said:
Id like to add that I had the same problem after rooting. No calls or texts were failing error 97 class 3. I called sprint and preformed the above steps and got me fixed in a few mins. About a week later (and several roms) my texts started failing again with errors 97 class 3 and error 64 class 2. I called sprint again and they got me all fixed up,(for now anyways.) Has anyone else experienced problems after their first call/fix to sprint.
Click to expand...
Click to collapse
Never heard of those errors dude.
The refresh is actually a CHLR refresh, you also want to ask them to refresh OMA-DM which will push the reprogramming through the network for your device.
Edit: Also if you want to try to fix it without calling TSS or ATS then try a profile update. If that doesn't work then do the ##RTN#. For it to work you will need your MSL. Once you enter there ##RTN# press the menu key and hit reset, I believe it is. RTN works because it is a reset that actually wipes the programming out of the phone as well as resetting the device. It does completely wipe the phone. Consider yourselves warned.
Sent from my PG86100 using XDA Premium App
str8upx said:
Id like to add that I had the same problem after rooting. No calls or texts were failing error 97 class 3. I called sprint and preformed the above steps and got me fixed in a few mins. About a week later (and several roms) my texts started failing again with errors 97 class 3 and error 64 class 2. I called sprint again and they got me all fixed up,(for now anyways.) Has anyone else experienced problems after their first call/fix to sprint.
Click to expand...
Click to collapse
I got this error out of nowhere today. I rooted a while back and had no issues. Today I tried to send a text and got the error 97 class 3. Then I tried a call and got the error 16. I didn't change anything on my phone today prior to getting the error.
I'll try the steps in the first post here and see if it works. I hope this isn't an error that will periodically recur after fixing it!
rtmeikle said:
I got this error out of nowhere today. I rooted a while back and had no issues. Today I tried to send a text and got the error 97 class 3. Then I tried a call and got the error 16. I didn't change anything on my phone today prior to getting the error.
I'll try the steps in the first post here and see if it works. I hope this isn't an error that will periodically recur after fixing it!
Click to expand...
Click to collapse
Yep, it worked! Thanks for this thread.
Has anyone else experienced what I did, where this error just pops up out of no where?
Thanks!
It just happened to me today after flashing CeanROM 2.5, however the phone worked for over a day after the flash then I got the error out of no where today. Strange, but a call to Sprint fixed it.
Maybe they detect a phone provisioning and triggers this "error 16"
product f(red) said:
a lot of people, after running revolutionary, have been getting the "error 16, switch ____ " automated message when calling any number but sprint customer support. This is a 100% definite fix for the problem. The good news is that it's an easy fix. The bad news is that the fix has to be done on sprint's side:
--------------
a) listen to the error message, and at the end of the message you should be transferred to a special department that specifically deals with and fixes this error message. They'll work their magic in less than 5 minutes and then your phone should go through hands free activation and work correctly.
--------------
b) if at the end of the error message you don't get transferred, call the normal 888 sprint customer support number from a different phone option 1 (for english) -> option 4 -> option 4. Tell tech support to do a "chls refresh". After they do that, do a restart on your phone. Hitting "turn off" from the power menu will just put it to sleep. After your phone restarts, it should go through hands free activation correctly and update the profile and prl.
--------------
c) if your phone doesn't go into hands free activation, download "msl reader" from the market to get your msl code, or just ask the tech on the phone for it. Then, open up the dialer on your 3d and punch in ##786#. Hit menu -> reset. Type in your msl. Your phone will reboot and go through activation. After that you should be good. Try and make a test call.
Hopefully that helps! If a mod could sticky this, that'd be great.
[cliche]please hit thanks if i fixed your problem![/cliche]
---------------------------------------------------------
a tech support person named dawn and i found the fix last night when we couldn't get the number for the "special department". If you're curious as to why some people don't get transferred after the error message, it's because they're on an employee referral plan, which are treated as employee accounts (everything plus plans). Those accounts go to call centers in texas and virginia only, while the "error 16 department" is in maryland.
Click to expand...
Click to collapse
when i called cs, they asked me for my number. My number is under boost not sprint. Please help me to get this done.
resueman said:
when i called cs, they asked me for my number. My number is under boost not sprint. Please help me to get this done.
Click to expand...
Click to collapse
Then you'd have to call Boost. I can't help you out if you're not on Sprint. Sorry. It's not that I don't want to, it's that I don't know how Boost operates.
I know it's been a pretty common issue for rooted EVO 3D users to get an error 16 while roaming, which requires them to call Sprint and go through some rigmarole to get the phone working again.
I seem to be having a different (although similar) issue. I have no issues making calls, or with data while I'm on the Sprint network. But now that I'm roaming off of a nearby Verizon tower out here in the middle of no-where, I'm having issues. I try to place a call, and immediately the phone sounds a disconnection beep and that's it. I also do not have data.
About 45 days ago up here I received a message about not being authenticated (the error 16), but I was told that they couldn't fix this without me bringing my phone into the store. I just reset the phone and did hands free activation again, and avoided the store. I haven't noticed any issues after that, and I do go in and out of roaming areas sometimes while in the city.
I just tried to do a chat with Sprint. I specifically said I had an error 16 and needed an HRL refresh (I lied). The rep had me power off my phone while she attempted to send it a signal. After this she had me dial *2 and my phone process crashed while I tried this. I also still couldn't call out. She tried having me power off again. Same problem. Next she told me to power off my phone and keep it off for 30 mins. If it wasn't fixed by then, she gave me a support number to call.
Anyway, not sure if the support number will help. Figured I'd just see if anyone has had a similar issue or experience. I found another thread mention resetting through ##786# and using your MSL to get into it. My EPST process seems to crash when I try this. ##DATA# doesn't crash though...hm.
I'm running the Synergy 3Dvo Rom (Nightly 344 I think?). Stock kernel.
Having a really weird problem.
Every time I try to make a call, the call timer starts and gets to 5 seconds before saying call ended and I get a "beep" from the phone. No dial tone or anything. Then if I call my phone number it tells me that the call can't be completed.
I have pulled the battery and sim card. I even thought it might be related to the boot looping issue. So I was going to try and see what mode the phone was in. But I can't get the *#*#4636#*#* number to work. I dial it and nothing happens.
I did confirm that I could still connect to the mobile network and was still receiving data.
Also I might add I just did the ICS OTA update a couple days ago. After that I went through the process of unlocking the bootloader and rooting the phone. Haven't flashed a rom or anything. And the phone worked fine for a couple days, and boom now I can't make calls. I did uninstall updates and disable both the blockbuster and nfl mobile app.
Anyone have any possible advice?
Ok apparently Verizon is having problems in Columbia.
This thread can be deleted by the mods if necessary.
you can get into the 4636 hidden menu by using the HZutils app.
EDIT: 11:15pm 9/25/2012 - ISSUE RESOLVED, SEE BOTTOM OF POST FOR SOLUTION
Okay, relevant information first:
Evo 4G LTE on Sprint
HBOOT 1.15 S-ON HTC DevUnlock
Current ROM CM10 Nightlies
Sprint-Google Voice integrated number
Now for the issue:
Texts can not be sent through the messaging app. When attempting to send a text, it will say "sending..." for a few seconds, then I get a notification saying "message not sent". Clicking on this notification takes me to the messaging app where the failed message has a red triangle next to it. When I long press the failed message, it comes up with a menu, and when I click "view details" it says "Error Code 98".
This happens both when connected to WiFi and when not connected to WiFi. It also happens both in my home town, and another town 45 minutes away (meaning the issue doesn't seem to be with the particular tower).
The last successful text sent or received was on Sept 13th.
Calls still operate as normal.
No changes were made by me between when my SMS was working properly, and when it stopped working. (Same ROM, Recovery, Kernel, etc). I haven't downloaded any SMS apps (handscent, gosms, etc) that could be interfering with the messaging app. I DO have the Google Voice app, but I had that when SMS was working properly as well, and the GV app hasn't been updated since March (meaning it shouldn't have changed how it was behaving).
Other peculiar behavior:
In addition to not being able to send texts via the messaging app, it seems that my number is also unable to receive texts. When texts are sent to my number, my phone does not receive them and they also do not show up in my Google Voice inbox. The sender is given no notice that the text has not been received. I am able to send texts from the Google Voice app, and others successfully receive them. When I send a text to myself from the Google Voice app, I receive it in my Google Voice app, but not in the stock messaging app (even though my Google Voice app settings say that texts will be received via the messaging app).
Things I've Tried (Updated: 3pm EST, 9/25/2012 ):
* Turning it off and on again
* Updating CM10
* Changing Google Voice settings (though it's possible I overlooked a setting)
* Factory Reset, Reflash ROM
* Flash Sense ROM, Update Profile/PRL
* Flash different AOSP ROM (Paranoid Android)
Things I've Not Tried (in order of how willing I am to do the things):
* Using an alternate SMS app (GoSMS, Handscent, etc)
* Un-integrating (and Re-integrating) Google Voice
* Giving the EvoLTE a relaxing bubble bath, to calm it down
* Flash Stock, Unroot, Update Radio
So, does anyone know what might cause this problem, and/or how to resolve it?
EDIT: Solution below
STORY:
I called Sprint Support, and had them reactivate my old phone (Evo4G running a CM9 alpha), by giving them the MEID for that phone. At this point I powered the phone back on, and called an activation number that they had given me (888-546-0314). On a Sense ROM, I would have simply updated my profile, instead of calling the number. We then tried SMS on the reactivated phone, and it worked (also, texts began showing up in Google Voice again at this time). I turned off my Evo 4G LTE, then I gave him the MEID for it and had him switch my number back to that phone. After he said he had switched it, I powered the Evo 4G LTE back up, and updated the profile, which I was able to do since I was still on Viper4G (note: I had to update the profile via WiFi, it might have worked over data, but it was taking longer than expected so we cancelled and just use WiFi for the update). Once the profile had updated, I called the test number again to confirm that the phone was activated. When I tried SMS, it worked as it should, including sending a copy to Google Voice.
TL;DR:
1. Find an old phone
2. Write down the MEID of both phones
3. Find a third phone to use to call Sprint (since you'll be activating/deactivating the other phones throughout the call)
4. Call Sprint Customer Support (888-211-4727), and punch the appropriate numbers until you are talking to someone
5. Have them switch your number to the old phone's MEID. Make sure the old phone is activated.
6. Have them switch your number back to the new phone's MEID. Make sure the new phone is activated.
7. Texting should be working on your new phone again.
Notes: The old phone may not be necessary. It may be enough for the Sprint Service Rep to deactivate your phone and then reactivate it. But I figured I would write out the EXACT method that solved the problem for me, since I am positive that this method has worked at least once. I have neither the means nor the desire to recreate the problem, so I will have to leave testing of other methods to the next person that experiences this problem.
Update: Clean flash of Paranoid Android did NOT resolve the issue. Still getting "Error Code 98".
So, this tells me/us this is not an issue with CM10 (which is not surprising, since I have no idea how what ROM I have flashed would keep Google Voice from receiving the texts as well).
This may sound odd but try moving the time up an hour or back an hour, error 98 is a problem with home agent, it's a sprint network error. I don't know of anything else that's helped
Try calling sprint and ask them if they can do anything. When I went s-off I had to call them bc my calls and text had errors. Data worked though.
They pushed something that fixed it in less than 10 seconds. Just wanted me to verify my account.
I tried changing the time 1 hour forward, and 1 hour backward, neither of those resolved the issue.
On hold with the Sprint tech department (it's taking longer than 10 seconds, but hopefully they figure out how to fix it.)
EDIT:
Mini-Update: Flashed Viper4G (a sense ROM), problem persists.
Updated profile and PRL while in Viper4G, problem persists.
Was told by Sprint technical support to press ##6-digit-MSL-here# and edit something, then reboot. Did that. Problem persists.
SOLUTION
The problem has been resolved, and the OP has been edited to include the method used to solve the problem.
If this was a game, Anthonicia would win for being closest (though it took closer to 2 hours on the phone with Sprint to fix the issue, if we include all four calls I made, 20-30 minutes if we only include that final one).