Quote:
Originally Posted by nttdemented
Hmmm... I think I came close to this by accident but I also think I messed something up by accident. I was on the phone last night (got the phone yesterday morning) with CS and they were giving me all the my EPST info so that I could enter it (it was all blank). She didn't get the change 0 to 1 on active profile, I did but it didn't work. BUT! I think I screwed something up, while I was doing the steps as she direted me I changed the default profile info instead of Custom Profile 1.
Can someone tell me what they got on the Default Profile? I know the user name is <MEID>@hcm.sprintpcs.com and the HA IP addresses are different. Particularly I think the AAA Shared Secret was a bunch of ASCI characters...
Can anyone browse into their EPST settings and tell me what they got in there?
|
Default Profile from another device prolly wont do you any good (as its specific to the device) - as you noticed the user name is the device identifier (ESN or MEID) and the password is prolly a 32 digit hex value that shows/showed as special charactors in EPST. The only way I know to successfully write this value is thru QPST. To read this value, based on past experiences with PPCs, you will need a program like QXDM or CDMA Workshop. Note that you would also need an MFG bootloader. Now the technology used (to update the device over the air) from previous PPCs like the 6700,6800, and 6900 is a little different - but one would think that they are similar in some aspects. 1 notable difference is the fact that with the diamond it will completely program the device (MDN, MSID, NAI, etc) where as the older PPCs would only update the data profile in the EPST settings (would NOT update MDN, MSID, etc) - At this point i think your best bet would be to modify m.ip profile 1 to the correct values. As far as the PHA and SHA, if you should need to edit them, you can use ##778# to access m.ip profile 1 and actually be able to edit them. (MSL required of course) - once you've established profile 1 as enabled it should connect to data using that profile and if programmed correctly (and provisioned correctly on sprint's side) then it should work.
*edit* you could also try a hard reset and let customizations run, just to see if that reset the EPST settings...