EDIT <PPST or something I did killed data connection (juicy / mighty not the problem) - Page 4

**razorloves** · #31 (**permalink**) 05-30-2009, 09:07 PM

Quote:

Originally Posted by Success100

yeah sometimes custom roms go bad. my phone was fine, and the next morning wouldnt connect to the web, when its all said and done, i had to re-lock and reflash a sprint rom, and then thru a couple hours of troubleshooting and testing, somehow the phone forgot its own MSL(NO MSL worked, not the device one, temporary one, even a ##786# wouldnt work), and I had to get a replacement. SO yes, sometimes custom roms can hose your baby

custom roms are not the cause of the problem. It's the user making a mistake. In your case, you probably ran the Update PRI or Update PRL program and it corrupted your pst settings. It is a common problem and threre is an easy fix. You just do ##786# - menu - reset like mentioned earlier in this thread and problem fixed. You didn't have to get a replacement from sprint. There's a whole thread about it here. http://forum.ppcgeeks.com/showthread...&highlight=dcd Just FYI.

frostj9445 · #32 (**permalink**) 05-30-2009, 10:05 PM

Quote:

Originally Posted by razorloves

custom roms are not the cause of the problem. It's the user making a mistake. In your case, you probably ran the Update PRI or Update PRL program and it corrupted your pst settings. It is a common problem and threre is an easy fix. You just do ##786# - menu - reset like mentioned earlier in this thread and problem fixed. You didn't have to get a replacement from sprint. There's a whole thread about it here. http://forum.ppcgeeks.com/showthread...&highlight=dcd Just FYI.

In my case it was not the roms...they were fine. Verizon told me it was a corruption on their end. ##786# did not work.

Thanks again to everyone.

**razorloves** · #33 (**permalink**) 05-31-2009, 12:03 AM

Quote:

Originally Posted by frostj9445

In my case it was not the roms...they were fine. Verizon told me it was a corruption on their end. ##786# did not work.

Thanks again to everyone.

That's good. Glad you got it fixed man.

mitpianoman · #34 (**permalink**) 07-07-2009, 04:09 PM

frosty, thanks for posting your fix. I've come across a similar issue on my phone (separate thread started for it here). Coming across this solution, I decided to call verizon to see if they could straighten it out for me as they have for you. Did you have to get escalated to the network repair team? I got up to tier 2, and they informed me that DMU key resets (which is what I'm guessing the tech did for you) are handled by a separate team, which is going to take 24-48 hours to get back to me. Does any of this sound familiar?