Alrighty! Not to drag up an aged thread on my first post, but I've had some fun recently with the EVDO issues Damager & friends have encountered. Speaking of, many thanks, I've spent the past week or so doing the ol' google-trawl for info, and some of it has proved invaluable.
Long story short, I've got a Titan that was flashed to 6.5 without saving the HDR settings, and has now reconnected to EVDO. How? Still working that one out..
I purchased a Titan that'd already been flashed to WM6.5, and had lost the EVDO in the process. Previously used an Apache, upgraded with no issues whatsoever, happily EVDO-ing away (Within reason, given data rates, sigh). Spent a week tweaking the Titan to my standards, finally decided to run the ESN change today. Still hadn't had any joy with the EVDO..until now. Tried simply mirroring the Apache's EPST settings with the Titan, no luck there, since the Titan has extended info (Is there an app or some such to examine the Apache's HDR settings?)
Now, prior to this, the Titan had just shown connectivity to the 1x service. Whether there's a phone number provisioned on it or not, my Apaches would still indicate the presence of EVDO capability, so I figured the problem wouldn't be all that easy to fix - the device itself not connecting to the network, presumably due to the HDR password authentication issues.
After NAMing my Titan and having TCNZ run the change, there was no connectivity joy at all. Odd, I thought, since I trust myself not to screw up something as ridiculously simple as programming in my own phone number, eheh. So I headed to the phone settings, and switched the NAM from NAM2 to NAM1. When I got the Titan, it was on some variety of roaming setting, since it didn't seem to recognise TCNZ as the home network despite the home SID/NID being correct. Now, bam, connected, and suddenly up pops the EVDO signal!
Right, I figure, that's a bloody good sign. Tried to connect it, and it sat there for some five minutes before determining it couldn't. Tried repeatedly, only got on 1x. Fie, thought I. No-one else had mentioned whether their devices did this yet still registered the EVDO, so I assumed that might've been the problem everyone else was facing - phone registers EVDO and just fails to connect to it. But one soft-reset later, and I'm enjoying all the bonuses of Rev-A.
How odd.. Everyone who's been discussing the Okta Touch above, and how a temporary ESN change fixed several authentication problems, may have had the solution to the Titan owners' problem in the palm of their hands as it were.
So! Anyone else tried ESN changing to another EVDO-capable device, letting it connect to EVDO, and then changing the ESN back to the Titan? Could just do the trick!
Can check any HDR settings on mine if anyone needs the reference, just shoot me a PM!
- onslaught86