Hello!
After taking the OTA 3.16 upgrade (S-ON, rooted), I've now got a problem where the phone start rolling to voicemail and not ringing for incoming calls. I've been upgraded now for three days, and it's happened each day. It seems to happen after a few hours of inactivity. A reboot or turning airplane mode on/off will bring the phone back online.
Any thoughts or suggestions as to what might be going on? Any suggestions for trouble shooting tips?
Thanks!
Just an update...I did some testing this morning, where I was calling my phone at regular intervals. After about 3 hours, it stopped ringing and started rolling directly to voicemail.
Try hitting Update profile, if it's still wonky you can always call customer service and they'll guide you through to fix it.
They prolly going to send a "reset signal" (or w/e it's called) and make you enter a few pound-pound commands
zmag said:
Try hitting Update profile, if it's still wonky you can always call customer service and they'll guide you through to fix it.
They prolly going to send a "reset signal" (or w/e it's called) and make you enter a few pound-pound commands
Click to expand...
Click to collapse
Thanks for the reply. I will probably have to call CS. I've already done update profile and PRL, did a battery pull sim, and played with a number of settings, all to no avail.
After further testing, the problem occurs in as little as one hour. Also, making an outgoing call will (in addition to restart and airplane mode on/off) solve the problem for another hour or so.
I have been seeing the same issue. I was at 3.15 when the issue started so I relocked and took the upgrade to 3.16. I am now rooted again with s-off, 3.16 FW, latest MeanBean with the same issue happening from time to time. Profile update as well as the latest PRL have been applied. I am wondering if it could be an issue with the area I am in. I know that sprint was doing some additional tower work for LTE here in the north Plano area where I live.
donc said:
I have been seeing the same issue. I was at 3.15 when the issue started so I relocked and took the upgrade to 3.16. I am now rooted again with s-off, 3.16 FW, latest MeanBean with the same issue happening from time to time. Profile update as well as the latest PRL have been applied. I am wondering if it could be an issue with the area I am in. I know that sprint was doing some additional tower work for LTE here in the north Plano area where I live.
Click to expand...
Click to collapse
I'm wondering the same thing now as well. My phone was rolling over early this morning, so I reset it, was going to let it "break", and then this afternoon when I had some time, call CS with it in the rolling-over state. I took the phone with me when I went out for lunch, and then ran some errands. I've been home now for several hours, and the problem hasn't resurfaced. FYI, I'm in south Arlington.
Related
Ok, I jumped into upgrading the ROM on the xv6800 I picked up from Verizon earlier today. After lots of looking around, I determined that I needed and located the SPL / bootloader (Olipro 2.40), a custom ROM cooked up courtesy of DCD, and the 3.27 Radio ROM.
Got the bootloader going, upgraded the ROM and got the dreaded locked Verizon screen. Didn't take long to figure out I needed to load the Radio ROM so I then got that loaded.
Immediately I started getting the message that my phone needed to be programmed, so I started to dial *228 but my phone just said "Call Lost" or something along those lines. Then I noticed it was just searching for signal continuously.
Weird thing is, after a LONG while (as I searched this forum for a couple of hours and tried and re-tried flashing the ROMS) I had signal, I did the OTA programming and upon reboot lost signal again.
I have now used the relock tool to return to the official Verizon ROM and I now have signal again. However, I have to call in for the AKEY.
Anybody else experience complete loss of signal? (not the data drop issue)
Edit: Just a side note, I called VZW tech support and basically admitted to flashing the ROM and flashing back. He wanted to know how I knew about the AKEY...told him I had been in wireless for years (true, but years ago as well) and was very knowledgeable. He shrugged it off and was happy to give me the key. I'm back up and running, but a bit gun shy to go flash the ROM again tonight. What time does VZW tech support shut down??? LOL
Im on sprint but changing my Mobile IP Settings helped me fixed this same problem.
limezednem said:
Im on sprint but changing my Mobile IP Settings helped me fixed this same problem.
Click to expand...
Click to collapse
Did you copy these from the EPST before you flashed the ROM?
Oh yeah, forgot to mention that I re-entered the MSID and the MDN.
Still can't connect to data....probably have to call tech support again soon. blah...
try using the msid and reset your ip to Mobi'e Prefoired
sandiegodude said:
try using the msid and reset your ip to Mobi'e Prefoired
Click to expand...
Click to collapse
Can you explain a bit further? Are you talking about MIP_MODE? That is set to "Mobile IP Preferred"
Ok, so I tried again and it happened again. I'm sitting here looking at a phone that is constantly searching.
This time the MSID and MDN are intact.
Any suggestions?? Which IP settings would I be checking and what should I be setting them to?
And as before, I now have signal about 20 minutes later (faster this time than last night.)
I need to do an OTA programming, I'm sure it will die again after the reboot.
Programming now.....rebooting.....and it's dead again. Any thoughts?????
Edit: Almost 20 minutes later again and I have signal, but not authorized again...guess I'm calling support for the A Key once more. Soft reset takes signal offline again.
I'm running a NexVision ROM based on DCD's 2.2.4, Sprint network. This issue happened to me three times, but not until after I loaded PRL 60711 (with Sprint). Was probably just a coincidence, though. Since then, it's been fine for a week.
Well, it came back up again. So it looks like I've narrowed it down to just a long delay in acquiring signal.
I'm on the phone w/ VZW now getting my A Key once again.
I dont know much about verizon but isnt the Akey always the same? Also, try toggling the MIP back and forth a few times. That has worked for some of us.
The A Key changes each time on VZW from what I understand. That comes from sources on here as well as VZW techs. I didn't write it down today and the one I did write down last night is @ the office so I have no way to compare for a definitive answer.
What would I toggle the key back and forth from/to? Can you explain that in a bit more detail? THX
Edit: Is this what you were suggesting? Under M.IP Settings
Changed MIP_MODE to Mobile IP Only then reset
Changed to Simple IP Only then reset
Changed to and back to Mobile IP Preferred
Tried and no go.
Sorry to hear it didn't work. It seemed to have helped a couple of us in this thread. Maybe it might take a couple more tries. But we all seem to be having the same problem.
Just found this post:
http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1
Tried again...no good. Maybe I'll try a few more times just for posterity.
Geckotek said:
Just found this post:
http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1
Tried again...no good. Maybe I'll try a few more times just for posterity.
Click to expand...
Click to collapse
Well, good luck! Haha
limezednem said:
I dont know much about verizon but isnt the Akey always the same? Also, try toggling the MIP back and forth a few times. That has worked for some of us.
Click to expand...
Click to collapse
Verizon isn't using the a-key (at least not in all locations) to validate the phone. They have some other authentication in house that gets reset by them. My a-key is blank, but after the update, I had to authenticate my phone to be able to make calls.
It appears they use both because they have given it to me twice now.
But back to the task @ hand...does anybody have a guess at why it would take 15+ minutes to acquire signal?
I did find one temp solution on my VZW phone:
after a reset, while the phone is searching for a signal, I went to the phone func and entered *22803. It then finds a roaming signal and starts "programming". At that point I hit call end and it picks up the signal and goes to EV, full bars. The phone says programming unsuccessful, but if I close the phone and re-open it, everything is fine.
pkp190 said:
I was also having this problem, what I did that fixed the problem was i reentered the MSID and MDN in the ##MSL# screen. Then allowed the phone to reset. from that point forward I get signal as soon as it powers on from reset. Hope this helps.
Click to expand...
Click to collapse
Thanks pkp190!!!!
Edit: Spoke too soon. After another *228 the problem has returned and trying it again didn't fix it this time.
radio
It seems to my feeble mind that the problem your are experiencing is caused by the flaky 3.27 radio rom. Its the very reason I have, unfortunately, given up on the gps roms. Some people report no problems at all, and others report serious issues. For me it was a problem so I gave up and went back to dcd1.7.0 which I find to be the best rom yet.
Some people have reported that toggling MIP settings (see http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1) helps but for me it didn't work. You could try that and see if it helps your case.
Others have reported that recooking a new rom with fewer OEMs might solve the problem. Once again, for me, it didn't work.
Otherwise, you might have to just wait for a new radio to be "officially" released before gps is a reality for you.
Geckotek said:
The A Key changes each time on VZW from what I understand. That comes from sources on here as well as VZW techs. I didn't write it down today and the one I did write down last night is @ the office so I have no way to compare for a definitive answer.
What would I toggle the key back and forth from/to? Can you explain that in a bit more detail? THX
Edit: Is this what you were suggesting? Under M.IP Settings
Changed MIP_MODE to Mobile IP Only then reset
Changed to Simple IP Only then reset
Changed to and back to Mobile IP Preferred
Tried and no go.
Click to expand...
Click to collapse
I think that in areas where the A-key is still used you can consider the a-key like a serial number for a piece of software (in this case ur authenticating into the verizon network).. there is an algorithm based on your ESN and any random number of keys can be generated to fit the algorithm and be accepted.
In other words although they may give you different A-keys every time that you call all of them are equally valid and can be entered to authenticate into the network.
Its like a keygen for pirated software when u can keep hitting that generate button to make random keys but all of them work in theory(not that I have ever contemplated using or used pirated goods)
I was wondering if anyone else has seen this behavior.
The phones appeared to have the original VZW roms on them but I admit I didn't look as closely as I should have and write down the numbers.
I've two warranty replaced phones that work this way.
1. Flash olipro&latest radio & latest (4.1) DCD rom
2. *228 (succesfully)
(Thinking back, the first time I did this I *228ed before applying the carrier rom)
3. After that calls cannot be made EVERY call even *228 results in a roaming "call lost"
I can flash back the original signed VZW rom that was posted here a while back and restore phone operations.
The *228 update then worked but could not check messages. The switch to non-broadband phone and back to the titan got me able to check voicemail successfully. I've redone the cycle but after applying the DCD rom, it doesn't take me back to a phone needs initial programming state. I'm gonna try to go full circle a third time now and see if I missed anything when it was 2am.
*ADDITIONAL: I just realized that when power is hit or the phone battery saves to power off, it locks up. Even though the lights still blink.
Do you have any thoughts? Have you seen this before?
I'm tempted to install the latest from HTC, but I don't want to give up on GPS - or has it the recovery from that been proven now?
Status update!
I had also noticed that there was a 2mo newer carrier cab from DCD. That didn't help.
At this point I've up/down/crossgraded to MR2 successfully.
This resolved the lockup problem.
I am in the process of following this thread to resolve the GPS issues. Hopefully the new roms will work with this radio http://forum.xda-developers.com/showthread.php?t=481750
A work around
Ok I went through that whole process to no avail.
However, I found a solution that I REALLY dislike and you will too once I tell you what it is.
It seemed pretty obvious that vzw somehow flagged the phone during the upgrade process to disable it. This was perhaps because I hadn't loaded the carrier cab when I updated, though I've done that before on earlier without any lasting effect.
**** NOTE *****
I strongly discourage you from taking the steps I have done below. Done incorrectly, you are committing a prosecutable crime with jail time involved.
**** NOTE *****
Knowing calls were blocked and that I would have a chance to hit hangup before the call was actually placed (that's why it beeps) I dialed 911 hit send and hit hangup. Obviously the call did not even start because the phone was in lock down mode (I haven't mentioned this before but the phone always booted to the extended network.) when the call was attempted. However, Verizon is also obligated to process all 911 calls. So, it switched from extended, to roaming, to Verizon. The call had been canceled even before it got to roaming, so there was no contact with emergency services. The upside is that the phone is now on the Verizon Network with the new radio and new ROM. I can do everything except a *228. This includes checking voicemail, #768, rebooting etc. I've not tried a hard reset, nor do I think I will.
I REALLY don't like the method, but I have my phone back.
I'm traveling to TX next week for SxSW again. I may see if I can do a *228 from there and get a better result.
I bought a touch pro off of ebay. When I got it the phone was already unlocked. I went to get it activated last night. when I left I called my voicemail and checked my messages. Everything worked fine. But before I went to sleep I noticed I wasnt getting good signal. I did *228 and did both options. Didnt help.
Today at work I received two text messages, but i still could not connect to data (email) So after work I drove to alltel to see what was wrong. Come to find out I couldn't make or receive any calls. They told me the speaker was broken, after convincing them that it wasn't in fact the speaker, they put me on the phone with alltel tech. They concluded that my PRL was way out of date, amd they couldnt figure out why my phone wouldnt make any calls and that my phone was broke. I asked if I could just update the prl manually via EPST and they said yes but essentially it would not make a difference because it has to be done over the air. And since I could not make any calls Im basically S.O.L.
So basically when I left alltel I was under the impression I was infact S.O.L. and I bought a junk phone.
But a mile down the road, it worked again, granted, it took along time for calls to go through, but i could make a call to my voicemail, to *228, and I got the "test" txt message from the alltel rep that never went through..
now, 3 miles down the road, a little bit out of town, I tried to send the rep a txt message saying "IT WORKS!!" But it would not work, I am back to square one and cannot make any outgoing calls. Its almost like I am "out of coverage area" But any other time I have full bars at my home, which is only 6 miles out of town.
I manually updated my PRL to no avail. I cant do anything with this phone.
I think either its on its way out, and is working intermittently, or I need to go back to town where it was working earlier, and try to reprogram the phone again now that I have the new PRL in the phone, but I doubt this will work.
I am wondering if re-locking the phone will take care of the issue, but I am skeptical of that as well. I think the phone is screwed.
There's a link to a recently released alltel stock rom on this site, have you tried flashing the newer rom? It will update your PRI and PRL and radio. It may be worth a shot, seems you're up the creek anyway.....
do you have a link to the rom? I cant find it. I downloaded the one from HTC website and its from 2009-07-07. I flashed it last night.
the 7-7-09 one is the one he is talking about... once flashed it will install a PRL from 2 months ago what is a good PRL and update to the latest radio. if that doesnt fix you issue i think u got sold a bad phone man srry... find the guy who shipped it to you and burn down his house
depending on how the first person unlocked the phone could of caused some issues but none of the unlockers that i know of would cause this. so re locking it depending if it was on alltel before or not could fix it but could also make it so you cant flash anything to it.
I am experiencing a large number of dropped calls. Like every other call gets dropped. I'm restoring back to OEM non-root and going to test it. Does anyone else have this issue?
I haven't personally experienced this issue, but I would recommend flashing a new radio first before restoring. It could save you some headache.
Where are you at? I'm in dallas tx a and have been having alot of issues.
angasreid said:
I am experiencing a large number of dropped calls. Like every other call gets dropped. I'm restoring back to OEM non-root and going to test it. Does anyone else have this issue?
Click to expand...
Click to collapse
I am having precisely the same issue. I have flashed to the latest MR2 radio AND updated to BAMF 2.1's excellent Gbread build, but if anything, it's worse. The symptoms are the same as others experiencing the issue - talking normally, when bam - the phone hangs up (my wife is an especially big fan of this).
I honestly don't think it's a rooted vs: non-rooted issue. It started happening before I rooted!
I see other people resolving the issue by dialing *228 and selecting option 2, but when I do that, the phone tells me it already updated the roaming profile at boot up via the SIM card.
Does anyone have any other suggestions before I un-root and get a new one from Verizon?
Unroot and test. Call vzw and see if there is any dropped calls or problems in the area..
Starr 228 doesn't work on 4G everytime you turn on your device it searches for towers
I suddenly can't send or receive any text messages. I don't have a clue what caused it. Last night I installed the app wifikill and used it for a few minutes which did cause my phone to reboot and for some reason made it look for a profile update, firmware update and prl update. Everything else seems to be working, so I'm not sure what's going on. I already attempted to delete everything in my phone and restore from a nandroid backup before this happened, and the problem still persist. Any ideas of what could have caused this and how to fix it?
I don't know if it is related or not, but I've been having texting issues with the LTE as well. Sometimes they go through, sometimes they don't and I end up turning airplane mode on, then off after waiting 30 seconds.
I've also been having MAJOR delays in getting sent messages (some are coming in more than 2 hours after they were sent to me according to the time stamps on the incoming messages)
It is really driving me crazy (oh, and along with data crapping out as well with no rhyme or reason as to why and when).
fastamx79 said:
I don't know if it is related or not, but I've been having texting issues with the LTE as well. Sometimes they go through, sometimes they don't and I end up turning airplane mode on, then off after waiting 30 seconds.
I've also been having MAJOR delays in getting sent messages (some are coming in more than 2 hours after they were sent to me according to the time stamps on the incoming messages)
It is really driving me crazy (oh, and along with data crapping out as well with no rhyme or reason as to why and when).
Click to expand...
Click to collapse
+1 to this issue.
That's no really the same problem I'm having. I simply can't send or receive text messages at all. It just suddenly started happening with no warning, so I'm not sure what caused it or how to fix it. Please let me know if anyone else is having this problem. If I don't hear anything soon, I'm thinking about unrooting my phone and re-locking the bootloader and taking it to sprint to see if they can do anything with it.
NoClemency said:
That's no really the same problem I'm having. I simply can't send or receive text messages at all. It just suddenly started happening with no warning, so I'm not sure what caused it or how to fix it. Please let me know if anyone else is having this problem. If I don't hear anything soon, I'm thinking about unrooting my phone and re-locking the bootloader and taking it to sprint to see if they can do anything with it.
Click to expand...
Click to collapse
I would run the ruu which will put you back to stock and see if the problem remains.
njfoses said:
I would run the ruu which will put you back to stock and see if the problem remains.
Click to expand...
Click to collapse
Sadly I already did that, and it still wasn't able to send or receive text messages. But here is the real kicker. Soon as I made a call to one of my friends who also knows a lot about phones to ask him if he had any suggestions, all the text messages that I made that wouldn't send all sent. By simply making a phone call, the phone must of connected with the sprint towers and made it start working. Super bizarre, but it's working again. So now I'm in the process up setting everything back up. Thank you Titanium Back up.
I'm currently experiencing modified version of your problem. I can't send text messages, but I can receive them. The only messages I can send are picture messages because they are looked upon as data.
NoClemency said:
Sadly I already did that, and it still wasn't able to send or receive text messages. But here is the real kicker. Soon as I made a call to one of my friends who also knows a lot about phones to ask him if he had any suggestions, all the text messages that I made that wouldn't send all sent. By simply making a phone call, the phone must of connected with the sprint towers and made it start working. Super bizarre, but it's working again. So now I'm in the process up setting everything back up. Thank you Titanium Back up.
Click to expand...
Click to collapse
Are you new to Sprint? Text messaging on Sprint has done this on several different devices for the past two years (since I joined Sprint). And when I make a phone call several tend to come through.
Oddly enough this doesn't happen in Utah when I go to visit, only Puerto Rico (where I live).
Try making a phone call and updating your prl within Sprint Zone. That fixed it for me.
I tried EVERYTHING to fix my phone. I rooted, unlocked and installed 2 different ROMS. None helped. I had to update my PRL every hour, and sometimes that didn't help either. I wiped everything, unrooted and relocked, ran RUU and went to Sprint. They replaced my phone. They are not allowed to work on these phones currently, so you'll either get a new one or a reconditioned one. Because I signed up for insurance, I got a new one.
I have not had any of the same issues since getting a new one. To me, it seems the issue is the PRL. It's showing that it's been updated, but it's not updating. There's a conflict between what Sprint sees on their side and your phone. But.. I'm not a Sprint tech, so I don't know.
All I know is I have a NEW phone and the problem is FIXED. For now anyways..
shinedown87 said:
Are you new to Sprint? Text messaging on Sprint has done this on several different devices for the past two years (since I joined Sprint). And when I make a phone call several tend to come through.
Oddly enough this doesn't happen in Utah when I go to visit, only Puerto Rico (where I live).
Click to expand...
Click to collapse
Actually know, I've been with Sprint close to 20 years now. I've always had a lot of different problems with them, but I've never had this particular problem before. But I'm glad I got it figured out, and everything is working again.