I have a rooted droid Eris that i'm going to give a friend... do i need to unroot before he could activate it? We'd be activating by phone of course...
No but *228 doesn't work because the keypad wont show up. I think its *22833 or something. I'm sure someone will post the right number for you, or do a quick Google search.
Sent from my ADR6400L using XDA App
You will be fine activating the rooted Eris - dial *22890 and it will program the phone AND update the PRL, or in the future, dial *22891 to update the PRL or roaming (same as dialing *228, wait for the automated voice prompt, then 2 on the keypad)
When it's finished, you should see a screen message - something about taking up to 15 minutes for the phone to be ready & authenticated on VZW's CDMA network.
It is not required, but it's a good idea to reboot the phone - or power off and start it up again - verify that data connection is working and then go ahead & make that first voice call. It should be "registering" on the network & allow the call to go thru.
If for some reason, your device isn't being "authenticated" - you can dial #8899 on the phone - and the calll will be transfered to a live agent, upon verifying some account information, check your account settings & do whatever is necessary to reset & make it happen. ***
*** This happened to me last week as I was flashing several custom Eris Roms and finally, I had to call in & something about a security update/check being necessary, took only a few minutes OTA while I was on the Eris with them - and I was able to make outgoing calls again. (BTW, incoming calls were okay - it just won't allow outgoing ones)
Good luck & have fun with the Eris.
Related
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?
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).
Hello everyone,
I am rooted and locked runinng MOF 2.3.5 ish v2.0.
Yesterday AM I started receiving an error (unable to send text) when trying to send texts through GO SMS. I also received the same error when using the stock messaging app. Then I discovered I was also not receiving texts. I can send and receive texts through Google Voice. I integrated my Google number with Sprint several months ago. I had made no changes to Google voice settings, or my text settings in several months. This just came out of the blue.
I tried restoring a backup from Titanium, that did not work. I tried de-linking Google voice from my phone and that did not work. I uninstalled GO SMS- still nothing. I have since re-linked Google voice to my Sprint # as it is the only way I have of receiving my messages.
Today I called Sprint. After a few tests with no luck, they instructed me to accept the OTA 2.3.5 update. They claim that one of the issues fixed in this OTA update was a fix of this "known issue with SMS". I told them I did not want to do that because it would perma lock my boot loader. They also suggested having them de-link Google Voice from my Sprint #. They said that if they de-linked Google Voice, I would not be able to re-link Google voice to my number later and that was a "known issue" with Google.
So, I have 3 options...
1) Keep it as is until upgrade time, but of course Google Voice does not have MMS support. And Google Voice leaves a lot to be desired with SMS threading and customization.
2) Take the OTA upgrade and "hope" it solves my texting issue, but of course that opens another can of worms with the bootloader.
3) Have them de-link Google Voice and hope that works. However, I enjoy having one number when I travel, etc. And if it doesn't work, according to them I wont be able to re-sync and then I will not have any access to my texts.
Has anyone else ran into this issue? I didnt see the exact issue in a Google search.
Thanks in advance
I also use Google voice to manage/backup my voicemails and texts remotely. I hate the google voice app. I only use it in it rare situations where I have no signal and no roaming available, but have wifi.
This has happened to me a couple times, I'll notice my gvoice has texts that my phone never received via SMS.
What is your preffered network set to? I've noticed my prefered network mode changes mysteriously on this phone. I'll just set it back normal and all my missed sms come flooding in.
Sent from my MB855 using xda app-developers app
Thanks for the reply. I normally set to automatic. I just checked and it was changed to any cmda. I will play with the options and see if that helps. Thanks again.
type in *#*#4636#*#* on the phone dialer
Sent from my MB855 using xda app-developers app
Hello, it was on CDMA Auto (prl). What do you generally set yours on for domestic use?
Your answer got me thinking. Saturday afternoon I removed a sim card from another country because I was here in the us and didn't need it. So when I got home I put the sim card back in and switched network to automatic and then all my texts arrived. Thanks again :thumbup:
After using QPST for my Dad's Inc4g it has 2 odd cellular problems.
#1
It can make outgoing calls for a few minutes.
But then it says that the “phone number is not active or invalid” (like it’s not activated).
Then the only call it can make is to 611 (data and wifi off), but it gives me his correct balance and minutes used (so it's still connected to his account).
Rebooting does not allow it to make outgoing calls either.
It's as if it's partially dropped off the verizon network somehow because turning the radio on and off again also doesn't work (airplane mode on/off).
And when another phone calls him it goes straight to his voicemail.
BUT….if another verizon phone calls he CAN receive that incoming call no problem.
*Then once he answers that incoming call, he can magically make an outgoing call again!
So can anyone tell me what I might need to change, to stop it from loosing the ability to make outgoing calls?
It’s brand new (NOT rooted or anything else).
The Preferred network is set to CDMA only.
Only changes have been through QPST, and switched to NV-Only mode so he doesn't have to use the sim card.
Also after QPST the roaming triangle popped up, but I have the 58012 PRL (isn’t this the latest for this phone)?
#2
If he starts to dial a number, but then immediately hangs up (accidental dial), his next call gets the "system busy" network error.
Then attempting to make a call after that gives the same error as above (requiring a verizon phone to call to get him back on the network).
Could someone try do this and see if they can repeat this error?
So to anyone who has used QPST with this phone, or flashed it to another carrier, do you have any change suggestions for either of these problems? Maybe changing something in EPST?
Thanks for your help.