VERIZON users on Custom Rom's - annoying voice-only network notification??

[CrossroadsTech]

Originally Posted by mike2037

I tried the flash back to stock and then custom without hard reset. It did not fix the problem.

I tried that as well and still got the pop-up. My PRL workaround seems to work so far so good.

[clueless25]

Radio PRL for verizon is done with the *228 option 2 method.

wat rom & version are you using now?

Originally Posted by thayer

PRL is loaded. I am doing this rather than the switch back and forth between stock and Mighty. Cross your fingers.

If this fails I will try the "flashback" method.

It also looks like the fellow in the PRL thread is modding the most recent prl. That would rock like striper.

[NinjaDuck]

Originally Posted by CrossroadsTech

I tried that as well and still got the pop-up. My PRL workaround seems to work so far so good.

The fact that the PRL fixes it gives me some ideas. I need a few days because of work, but I will ping the group if I find anything.

[whetzel]

Originally Posted by mike2037

I tried the flash back to stock and then custom without hard reset. It did not fix the problem.

Hum, strange.

I wonder what I'm doing differently? I've flashed at least 4 different times now and I don't get that pop-up any more.

Did you update via *228 after you flashed back to stock and before you flashed the custom ROM?

Thanks for the input though.

[thayer]

I'll also confirm that the prl works well. No more message. It also has changed the connection speed to 1x.

A friend has a storm2 and he is getting 3g. Makes me think that an updated prl would get us back on 3g. I'm off to learn how to crack the prl.

[NinjaDuck]

Originally Posted by whetzel

Hum, strange.

I wonder what I'm doing differently? I've flashed at least 4 different times now and I don't get that pop-up any more.

Did you update via *228 after you flashed back to stock and before you flashed the custom ROM?

Thanks for the input though.

Yes, I did the *228 thing.

[dwbartlett72]

I haven't had that problem with my Touch Pro 2. I am on Verizon and haven't had a problem where it dropped the EV. Might just be the ROM that you are running.

[thayer]

Originally Posted by dwbartlett72

I haven't had that problem with my Touch Pro 2. I am on Verizon and haven't had a problem where it dropped the EV. Might just be the ROM that you are running.

Yeah, read the thread....its ONLY with custom roms. Are you running custom?

[CrossroadsTech]

Originally Posted by thayer

I'll also confirm that the prl works well. No more message. It also has changed the connection speed to 1x.

A friend has a storm2 and he is getting 3g. Makes me think that an updated prl would get us back on 3g. I'm off to learn how to crack the prl.

You are correct. With all the changes with the Alltel integration its likely a newer PRL is needed for EVDO in your area.

I found from searching that we can just as easily update the ERI, like the PRL. Dial ##374 Talk. Problem is I need a VZW ERI for our phones. Then we need to see if reloading the VZW ERI as is fixes the problem. If not, then we change the "Extended Network" entry to roaming indicator off, and I believe our problem is solved and everyone will be able to download current and future PRLs without modification. I'm going to work on this over the weekend as I don't have QPST installed as I need to reinstall it. Wish me luck.

Also, there is a new Verizon OEM update with 6.5 that has been discovered and posted in the CDMA ROMs sub-forum. It has an updated radio and I think it may have a newer ERI file. It shows ERI version 5 in the screenshots. I've got Mighty installed right now and it doesn't have the ERI info in its Device Info so I'm not sure what ERI we're using with it. If anyone wants to try, and I will to, I'm going to flash to the OEM 6.5 to get the new radio and then flash back to Mighty and see if we still have the pop-up with a current PRL (shows "Extended Network).

[CrossroadsTech]

My MightyROM and stock has ERI version 4, while the new Verizon OEM 6.5 ROM has version 5. I'm thinking version 5 might fix our problems... stay tuned.