OTA fail?

C

Cortny

New member
I was wondering if anyone is having problems with OTA Flashed and non flashed cricket phones, i have noticed this on flashed phones mainly but not sure.

North Cal

Touch Pro (my phone) When i try to OTA it only gets to Downloading Nam... then it after about 50 sec's it says im sorry but where not able to program your phone etc etc. so far i have only been able to fix this by loading the 1040 PRL and doing a MDN/MIN Pair. never had that problem befor. i have also noticed it on these phones as well.

Sanyo M1 X 2 OTA failed
Sanyo M1 X 4 OTA ok
Touch Pro X 1 OTA failed *but works if you 1040 prl and OTA it like 20 times
Cricket Samsung A870 x 2 ( real cricket A870 not flashed, will not OTA )
LG VX8500 x 1 Failed OTA
LG VX8500 x 1 OTA ok, both where done at the same time and put on the same account, i even changed the nuraber still will not work.

thats all the info i have right now, i know phones can be program by hand but it gets kind of hard having to load the PRL's by hand, since they change based on what plan and stuff a person add's on. anyhow i noticed this since on the 28th of Dec.


What do you think is going on? Also has anyone else have had this problem in the month of Dec and this month as well.

On a side note has anyone with a Touch Pro have had any problems with getting there phones OTA'ed?
 
well i know it was like that for about 6 months when they 1st started to allow non cricket esn's on there network, but after that i've really never had any problems, maybe once or twice but this one in the last week and a half has been very odd, just case its been so random. on my touch pro its like nam ok and then the rest goes to hell lol but my Touch D phone OTA's just fine e.e so odd.
 
Use CDMA Workshop. Set SPC to six zeroes. Use non-roaming PRL. Set in NAM tab MDN/MIN pair, MSID, MCC, MNC, and at least ONE SID/NID pair. Three pull-down settings at the bottom of NAM tab: Enabled, Standart, Enabled. Write, then close CDMA Workshop to get the reset phone dialogue. Press OK to reset.

Flashed phones will OTA depending on the carrier and the model. In my market, for example, *2 for Sprint Samsungs NEVER works.
 
ive had some issues with the ota also, with most samsung sprint models the *2 suaully works, if it does not,, we sometimes have to use diff prls from time to time, ive used the 1039, 1040, and 1050. some phones ota, some dont, and yeah, it can be hit and miss mostly,

joey :buddies:

and aye i agree with berry, the steps he listed usually will work, and sometimes they dont, as sometimes manual programming a phone will help
 
I know that when I flashed my touch pro, set the spc to all 0's and tried to otap it I couldn't get it to work until I loaded a different prl on the phone. After trying about 6 different prl files I finally found one that let the phone otap.

Hope this helps.
 
I had the same issue Berry, i had to load (been about a month now so forgive my memory) 1041 i think to get it to OTA. And when it did, i still didnt get the correct roaming PRL, i ended up pulling it off my Vogue and transfering it that way lol. Quite annoying though, i will have to try some of the roaming PRL's and some others as well, as mentioned i as well tried multiple PRL's till i found one that worked. I know it was a 104X PRL though.

David
 
i alwas use the latest non0roaming prl, set mdn/min to 000000xxxx, and set sid to 0...

that works 4 outta 5 times for me and even does the pro and diamond
 
I would try a zero SID if all else fails.

And CDMA Workshop can generate an ESN-based MSID; i.e., 00000000xxxx. I've heard some users have had success using random nurabers, even.
 
I was speaking to a cricket porting rep earlier and he had me do *228 (even though I knew I didn't have the right MSID). I asked him for it but he said just do *228. So, I did and it failed. Then he said ok one min, I dunno what he did but he had me try it again and then it worked. I had PRL 1050 and the OTA gave me 1013.

Now, my phone calls work and I can get text but I cannot send any. I found the below on a sticky and my settings are different. Instead of my phone nuraber, the MIN's and True MIN's fielRAB have the MSID. Is this the problem?

Mobile Directory Nuraber : Your Full Cricket Nuraber
Min1: Your Cricket Nuraber with out the Area Code
Min2: Your Area Code
MSID: Your Cricket MIN Nuraber goes here
Ture MIN1: Your Nuraber without the Area code
Ture MIN2: Your Area Code
True IMSI_S: Your Nuraber with Area code

I have yet to install a custom ROM, probably will do that later tonite...

Peace
 
Right, I understand MIN/MSID is the same. I am changing MIN1 to my nuraber with no area code and as soon as I do, it changes MSID to my nuraber. Or, if I change MSID then it changes MIN1. Driving me nuts.... my MIN/MSID is not the same as my MDN so what can I do? I update one field and it changes the other.
 
I guess I must be. The sticky post I found (from cellkeeper) states that the values should be this:

Mobile Directory Nuraber : Your Full Cricket Nuraber
Min1: Your Cricket Nuraber with out the Area Code
Min2: Your Area Code
MSID: Your Cricket MIN Nuraber goes here
Ture MIN1: Your Nuraber without the Area code
Ture MIN2: Your Area Code
True IMSI_S: Your Nuraber with Area code

So, this is not right then correct? Since, MIN = MSID and not MDN (cricket nuraber) as it says above. :confused:

Thx
 
When you change MIN1 and MIN2 it will automatically change true MIN1 and 2. I hope that is what you're asking. Change the first 3 lines there, MDN, MIN1 MIN2 and set your SID and your phone should OTA with a good PRL.
 
Back
Top