Related
Is it just me or is anyone else unable to roam on verizon towers after the new rom/radio upgrade (3.16/3.27)? I get a recording while roaming "Welcome to Verizon Wireless, We're sorry, we're currently unable to authenticate your phone, Please try your call again. If you continue to experience problems please hang up and dial #8899 from your wireless phone"
Any help is appreciated.
Thanks
What PRL do you have?
I never tried making calls but I don't roam on their towers anymore when it comes to data. I just get the triangle and 1x and no web browsers will let me connect to any sites. I kinda just gave up on it since I only needed it in the DC Metro.
I can roam with the new rom. im using prl 60610 and data roaming works as well.
kind of ironic because it didn't work before for me
1X roaming works on Alltel and VZW with 60610 and 3.x ROM here, but EvDO roaming is a no go on Alltel, even though it works fine with 60610 and 2.x ROM.
I guess you are not the only one having the problem. it's a no for me for both prl 60610/60611.
However I am only having the problme at home. I can roam onto vzw at different locations (voice and 1x data) $%^%^&#!$#@!$
People say it may have something to do w/ a-key which is blank on my phone ...
TopGun2000 said:
I guess you are not the only one having the problem. it's a no for me for both prl 60610/60611.
However I am only having the problme at home. I can roam onto vzw at different locations (voice and 1x data) $%^%^&#!$#@!$
People say it may have something to do w/ a-key which is blank on my phone ...
Click to expand...
Click to collapse
Using PRL 60610. I downgraded my phone back to radio 1.40 and it worked fine but it will not work with the new one. I guess roaming had to be given up for GPS.
Problem Solved. Seems like Sprint's System wanted to do the PRL update themselves for record purposes because after I got the rep to shoot a new prl (60611) roaming worked. I then downgraded to 60610 (best one for me) and viola it stuck. everything is working now.
keeepinitgansta said:
Problem Solved. Seems like Sprint's System wanted to do the PRL update themselves for record purposes because after I got the rep to shoot a new prl (60611) roaming worked. I then downgraded to 60610 (best one for me) and viola it stuck. everything is working now.
Click to expand...
Click to collapse
Ok, so how did you fix this again? Can you give me the current setup of your phone or the steps you took to get to where you are?
Here is what I have done so far:
- Flashed from 2.17/1.47.1 to 3.16/3.27 and got the no Verizon roaming issue you described.
- Figured it was an issue with the new ROM, so I then downgraded back to the stock 2.17/1.47.1 ROM from the HTCAmerica website. (The downgrade wiped all my settings for MDN and MSID) However, the issue persisted.
- I updated the PRL to 60611. Still no luck.
- Called Sprint, who initiated an over the air PRL update of their own to 60611. Still no Verizon roaming. Sprint says they are "investigating" and will get back to me, whatever that means...
The only other thing I can think to do is to downgrade again back to 2.09/1.40.
Also another question, when you view ##778#, does your phone show anything on the "A-Key" page under the "Authentication Key" setting now that you have roaming working? Mine is currently blank, and I have read a couple threads talking about needing to figure it out, but those users all seemed to be Verizon customers. I would be interested to find out if Sprint customers have that setting or not.
This issue is driving me nuts, and any help is greatly appreciated.
Call sprint technical support and tell them you need an "HLR Reload". If they don't know what this is, ask to speak to someone who does.
aatreya said:
Call sprint technical support and tell them you need an "HLR Reload". If they don't know what this is, ask to speak to someone who does.
Click to expand...
Click to collapse
Wow. Genius! Got Sprint technical support on the phone and asked for the "HLR Reload." The guy knew exactly what I was talking about and was able to do it right away. I am now able make calls and get data while roaming (currently using 2.17/1.47.1).
Thanks again!
glad to know it worked
rfrankli said:
Wow. Genius! Got Sprint technical support on the phone and asked for the "HLR Reload." The guy knew exactly what I was talking about and was able to do it right away. I am now able make calls and get data while roaming (currently using 2.17/1.47.1).
Thanks again!
Click to expand...
Click to collapse
wow, now i know what i need to do w/ my 3.16 rom
edit: got a call from spint. the tech guy said that he found an authentication failure on my account and reset it. will test the roaming again when i get home. he also had no clew what the "HLR reload" is...
edit2: whatever reset sprint did at their end seems to work. voice/1x roaming is working now, still no evdo though.
Still wont work for me *sigh*
aatreya said:
Call sprint technical support and tell them you need an "HLR Reload". If they don't know what this is, ask to speak to someone who does.
Click to expand...
Click to collapse
I called and had them do this, but i had no luck. Still no EVDO roaming in places where there should be. I can make and recieve roaming call and data roam in 1X but evdo is gone. This is on both the 60610 and 60611 PRL. EVDO roaming worked on both PRL's with the 1.47 radio and 2.17 rom.
Any more ideas?
well I thought I didn't have these problems, but now I'm not certain. I don't think I've ever been able to EVDO roam on verizon, at least not sice I started paying attention which was already after moving to a 2.17 with 1.40 radio and orginal PRL. I know verzion has evdo in this area, but sprint doesn't. Maybe there is no agreement here for evdo becuase of that? I guess it couldn't hurt to try this trick and see if I get it.
I found more problems using 3.16. I did encounter the roaming authentication error. So I called, got the HLR reload. That made things MUCH worse. Now nothing works. My MSID and whatnot are all correct and I see signals, but can't make calls or data connections. Sprint tried some things but nothing worked. I'm going to do a hard reset and see what happens.
Sprint was surpisingly willing to work with me knowing that I am using the test rom though... but in the end still suggested I revert to an official rom when nothing worked out.
Anyway, not sure I'd reccomend the HLR reload on the 3.16... try at your own risk.
holy crap
sorry to hear that
if you get it figured out, lemme know what fixed it.
I suspect sprint just hit the wrong button. I hard rest... still no dice, but I noticed that dialing *2 does work.. normal numbers and network don't. Seems like an authentication issue. I doubt seriously it has anything to do with the rom, but I just flash 2.17, casue otherwise I don't hink I'll get far with sprint.
Now when I try to make it call it tells me the phone has not been activated. (with 3.16 I just got the call end dings imeediately)
SO when I fix this and flash back to 3.16, will I dare to try this again after roaming gets broken again?... tough call.
Edit... still need to fix MDN and MSID in the 2.17 .. more soon.
Edit: fixed MDN and MSID in 2.17... now having the same problem as in 3.16... ding ding ding... no call. Looks like I have to call sprint again.
ON the phone with sprint now. Have rebooted for them a couple of times. This guy is still stumped and he doesn't seem generically ignorant.
I started a new thread for my issue.
http://forum.xda-developers.com/showthread.php?p=1881522#post1881522
You might want to read it before doing any HLR updates in 3.16 though. I'm on my third rom today and a few hours with sprint tech and I still can't make calls.
(EDIT
SOLVED... see above thread. It seems they messed me up badly when they did the HRL reload... however.. it doesn't have to be done badly... at least now we know the fix if it happens to someone else.. so don't let my experience stress you too much. Now to upgrade roms again.
and voice roaming works now..
Roaming not working
ahhh!!! after the upgrade, i cannot roam on vzw...
Called and spoke to several reps... no one knows what HLR Reload is... according to them turning the phone off and taking out the battery for a few minutes will force the HLR reload....
I don't know what to do.... These reps are impossible to deal with.. Anyone have any suggestions?
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 cannot get my new phone to get a signal after the following:
1. 2.4 unlocker (Hard-spl-mfg.exe)
2. Sprint Rom (RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship.exe)
3. DCD Rom (DCD_3.0.1_Verizon.exe)
I believe I followed all of the instructions and upgraded my XV6800 from stock to DCD 3.01. When I finally get booted up I can never get a signal acquired. I can dial *22802 and let it connect and then I get a signal, but even then I get an error about the #777 internet access, so something is wrong. I new A-Keys and made sure all of my info was written down and correct.
Is there a way to start over from stock? Can I relock and put the stock Verizon on and try again?
Help!
did you.....
When you ran in the Sprint ROM did you let the customization run ? If so then there is the problem, as it overwrites verizon parms with the sprint. That can be fixed by getting the VZW PRL and running it in with the EPST, then set your home SID/NID also in EPST, then you should have VZW signal and not roaming, then a *228 should reprovision the rest. If you did not write down your info before you flashed then you missed a step.
I was under the assumption that the Sprint customizations don't run until I tap the welcome screen which I did not. I immediately installed DCD 3.01. I'm returning it to stock to see if I can get a signal then starting over.
Where can I get the VZW PRL? I will search now.
ok then they did not run
well I guess they did not run but maybe your PRL and provisioning data got wiped, MSID, MID, SID/NID, you know that stuff. There are stock VZW ROM images out there but my methode would fix it safer and easier as I am sure that the signal issue is a missing or wrong PRL. Go into EPST (##778) and select 'view' and then look at PRL which should show 50989 or somthing close as that is the current VZW PRL, a different number would be someone elses overwritten on yours, blank is no PRL which is also badd. then look at SID/NID where the first set should be populated. If you fix just these 2 things then you should get back on VZW signal and be able to provision it. Going with a full restore is like crushing and reconstituting your car when it only needs a wash and the ash trays emptied. If you do still want to though, the stock images do exist here.
I relocked and put the Verizon stock back on and went through the setup procedures and the phone works great back at stock.
I started the update over.
Installed the Unlocker.
Installed Sprint ROM. No customizations allowed.
Installed DCD 3.01
Signal does not acquire but will after 15 minutes or so and all is fine. As soon as I soft-reset.. no signal. The PRL is the 50989 the latest. All of my MSID and other numbers match.
Maybe it's the DCD 3.01. I don't know where to find 3.0.0.
I'll keep searching. Thanks madman34 for your help!!!!
I've noticed that after waiting for the signal 15 minutes, everything works wonderfully. I've tried changing the MIP MODE over and over but that hasn't worked.
Anyone with DCD 3.01 and the new Sprint ROM Radio able to get a signal without waiting 15 minutes?
HELP!
Yep, I get signal within 3 seconds.... Not sure what the issue is with your phone....? I am currently a Verizon user....
I am a Verizon user with DCD's 3.0.1 and upon soft reset get a signal within 2-3 seconds.
Hi guys, just to let you know I'm in the same boat at the OP with a Verizon phone and No2Chem's 5055. I'll start a new thread with a more descriptive title and see if we can get some additional help.
KeithGP said:
I relocked and put the Verizon stock back on and went through the setup procedures and the phone works great back at stock.
I started the update over.
Installed the Unlocker.
Installed Sprint ROM. No customizations allowed.
Installed DCD 3.01
Signal does not acquire but will after 15 minutes or so and all is fine. As soon as I soft-reset.. no signal. The PRL is the 50989 the latest. All of my MSID and other numbers match.
Maybe it's the DCD 3.01. I don't know where to find 3.0.0.
I'll keep searching. Thanks madman34 for your help!!!!
Click to expand...
Click to collapse
Did you try the *22802 and hanging up? Geckotek mentioned that as a fix to the problem.
I also found that the customizations tried to run after installing DCD 3.0.1, did you let those run?
Osteo said:
Hi guys, just to let you know I'm in the same boat at the OP with a Verizon phone and No2Chem's 5055. I'll start a new thread with a more descriptive title and see if we can get some additional help.
Click to expand...
Click to collapse
What city do you have service in?
I did try the *28802 and it didn't fix it for the N2C rom. Man, I'm getting depressed over this.... I'm in middle Tennessee (Cookeville), great cell coverage for both Sprint and Verizon.
Osteo said:
I did try the *28802 and it didn't fix it for the N2C rom. Man, I'm getting depressed over this.... I'm in middle Tennessee (Cookeville), great cell coverage for both Sprint and Verizon.
Click to expand...
Click to collapse
is your PRL 50989?
http://www.corolada.com/prl/
lllboredlll said:
is your PRL 50989?
http://www.corolada.com/prl/
Click to expand...
Click to collapse
I've gone back to stock so that's what it says now. During my 1st call to tech support they had me go over many of the EPST settings and I think that's what it said but I was so perturbed I don't recall. I'll try again (was thinking of trying DCD's most recent as he has carrier specific ROM's) and if I loose the radio, I'll check again. Thanks for the input....
Is the fundamental issue here that your installing a SPRINT rom on a VERIZON VX6800?
Why not try installing a VERIZON rom?
spreeway said:
Why not try installing a VERIZON rom?
Click to expand...
Click to collapse
If I wait for VZ to release a WM6.1 ROM with GPS I could be old and gray... I'll try DCD's most recent with VZ ROM and Sprint Radio tomorrow...
spreeway said:
Is the fundamental issue here that your installing a SPRINT rom on a VERIZON VX6800?
Why not try installing a VERIZON rom?
Click to expand...
Click to collapse
Spreeway, there is no such creature that enables RevA and GPS. These are enable by using the new sprint ROM (to upgrade the radio) and then a custom rom (DCD!) for verizon.
Quick update. Resolved. It was a prl issue, rolled back to an older prl and all is well. I guess I'll have to wait for an official rom from VZW to get the latest prl but all is working now.... How odd.
I am using 50989 with 3.0.1. Now that you're back to an older prl, dial *228 NOT *22802 and then press 2 at the prompt. Update the prl OTA and see if it works this time.
Tried and failed... Yesterday, once I figured out about the older PRL, I upgraded and called for a new A key. Tech support updated the A key on their side and he had me run *228 option one and when it rebooted I had no signal. I checked the PRL and it was 51020! They must have just released a new one... Rolled back with the tech on the line, didn't need a new A key and all is well since.
I still can't figure out why any of the Nationwide PRL's drop my signal but as my plan has coast to coast no roaming, I think if I get outside of my home zone it should still pick up towers (I hope but I dont travel much).
Also, I can't figure out why I can't change the roaming options in the phone options. It currently has no check infront of 'Sprint only' or 'roam only' and if I check either I loose the cell radio. Very odd!
Hope you guys/gals can help me out with this one!? I really don't want to flash back to Alltel's outdated rom.
Everything has been working great! The phone has no problems making/receiving calls, internet doesn't drop while downloading files, GPS has been really great, IR beams, bluetooth, and so on are all working better than they every have.
But, as soon as I leave my home area (Lynchburg, VA) the phone cannot make/receive calls, and the internet will not connect. For example I am traveling today in Roanoke, VA (normally solid triangle now flashing) and I try to make a call the recorded voice (Verizon) says that it cannot authenticate my phone. I called Alltel customer service and he could not see my phone either. What's funny is if I dial *611 I can talk to customer support. None of these things were happening until the upgrade.
Thanks for your help! Hope I did not leave anything out. If you have any questions, please ask!
Do you have the latest alltel prl?
gcincotta said:
Do you have the latest alltel prl?
Click to expand...
Click to collapse
I believe I do? It says I have 30031.
Thanks for the quick reply, keep them coming! I really need to get this fixed. I didn't realize how much my job depends on this damn phone! lol
yeah agree with gcincotta, check your prl. should be 30031 i believe. then check your epst. ##778 send. click on edit. 000000. when you are in your nam settings, check to make sure that everything looks like it should. i would say especially check the SID and make sure its for your local area. then check your security settings, make sure the HDR pass is your ESN. I cant think of anything else really.
have you tried doing a *228
update the roaming first, let your phone restart.
start again, update the programming with option 3
the only other thing i can think of is that the ESN might be jacked. look at your phone info (just in settings) and check the ESN, make sure it matches whats on the box that your phone came with. i have heard of these flashes sometiems erasing the ESN to 000000
It's not the PRL...
I went through this a couple weeks ago, it's a "security issue" with your account and Alltel's roaming partners. You need to call 1-888-295-3569 and tell them you are getting that recorded message when out of your "home area". They will ask a couple questions like "are you roaming now", "are you on that phone now" and SHOULD take you less than 5 minutes to get squared away.
YMMV, but they fixed me up quick.
I got this information from this post so proper credit is given: http://forums.wirelessadvisor.com/491543-post10.html
I am a Lynchburg, VA alltel 6800 user as well. I have been running the DCD 3.0.1 rom for the past week or so. I haven't had any issues, and I was in roanoke monday evening.
Have you checked the HDR AN AUTH Password in epst?
Send me a pm,
Marlin
Does anyone know about the PRL?
I am sitting in an area right now in New Hampshire where there is no Alltel coverage. Because I used to be VZW cust with Blackberry I know that in this house VZW has full coverage with EVDO data available. I also know that the Sprint Towers can been seen by my phone but just barely and there is no EVDO available in this area with Sprint.
According to Alltel the PRL is setup to have Sprint be the first choice for Roaming and there is no way to change it.
Does anyone know if there is a way to set my PRL to have VZW as the first Roaming choice?
Mr.Ellsworth
Mills00013 said:
yeah agree with gcincotta, check your prl. should be 30031 i believe. then check your epst. ##778 send. click on edit. 000000. when you are in your nam settings, check to make sure that everything looks like it should. i would say especially check the SID and make sure its for your local area. then check your security settings, make sure the HDR pass is your ESN. I cant think of anything else really.
have you tried doing a *228
update the roaming first, let your phone restart.
start again, update the programming with option 3
the only other thing i can think of is that the ESN might be jacked. look at your phone info (just in settings) and check the ESN, make sure it matches whats on the box that your phone came with. i have heard of these flashes sometiems erasing the ESN to 000000
Click to expand...
Click to collapse
Everything looks fine, but where do I find the HDR pass? I see the ESN (Hex,Dec). I will have to check the ESN with the box, but it is not 000000.
I did the *228 option 2, but not the option 3. Since everything was working in my home area, I thought it was ok. I will give that a try when I get back home.
And yes, I used to be able to make calls from here. I travel 4 states, and have never had a problem at any of my stores.
Thanks for the help!
jake1s said:
It's not the PRL...
I went through this a couple weeks ago, it's a "security issue" with your account and Alltel's roaming partners. You need to call 1-888-295-3569 and tell them you are getting that recorded message when out of your "home area". They will ask a couple questions like "are you roaming now", "are you on that phone now" and SHOULD take you less than 5 minutes to get squared away.
YMMV, but they fixed me up quick.
I got this information from this post so proper credit is given: http://forums.wirelessadvisor.com/491543-post10.html
Click to expand...
Click to collapse
Did you call them on your phone or from a landline? The only way I can call them from the phone is *611. I have been reluctant to call them again, because I thought they might ask if I have flashed my phone?! If nothing else works, I will have to.
Thanks!
I actually waited until I got back into my home area and called since I couldn't call out and didn't have another phone handy, but he said if you call from another phone WHILE roaming it makes it easier for them to verify that's the problem.
If you're still out I'd grab a landline or a friends phone, shouldn't take you long. After they are done, and they will probably tell you, you'll have to power cycle the phone.
EDIT: He didn't even question the radio version or ANYTHING about me messing with my phone. Just did his thing, sure enough I now call out in areas I couldn't before.
jake1s,
I was wondering that, I thought they might have a way of telling. Did not want to lose my warranty just yet. lol
Everyone else,
Thanks for all your help, I will keep you posted on what happens. I'm sure this had to happen to others, and maybe they just don't know it yet since they have not traveled out of their home area? Maybe it's just a Alltel/Verizon thing, not Alltel/Sprint.
Thanks!
hinds73 said:
jake1s,
I was wondering that, I thought they might have a way of telling. Did not want to lose my warranty just yet. lol
Everyone else,
Thanks for all your help, I will keep you posted on what happens. I'm sure this had to happen to others, and maybe they just don't know it yet since they have not traveled out of their home area? Maybe it's just a Alltel/Verizon thing, not Alltel/Sprint.
Thanks!
Click to expand...
Click to collapse
Happened to me with Alltel/Sprint. I called Alltel, said I had the message, told them where I was and my phone number. It was fixed in 2 minutes flat. I called from a coworkers phone.
jake1s said:
It's not the PRL...
I went through this a couple weeks ago, it's a "security issue" with your account and Alltel's roaming partners. You need to call 1-888-295-3569 and tell them you are getting that recorded message when out of your "home area". They will ask a couple questions like "are you roaming now", "are you on that phone now" and SHOULD take you less than 5 minutes to get squared away.
YMMV, but they fixed me up quick.
I got this information from this post so proper credit is given: http://forums.wirelessadvisor.com/491543-post10.html
Click to expand...
Click to collapse
Well, this is what worked. I'm not sure exactly what he did, but in about 2 or 3 minutes it was fixed.
Thanks for all the help!
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.