Telecom NZ - Upgrade Issues (and fixs)

[Silk]

Originally Posted by cogent

closure at last:
http://www.telecom.co.nz/oktatouchupgrade

YES it restores a lost HDR user/pass
YES it is winmo 6.1
YES it is official

Just curious, how did you hear about this? I tried to find some information about it by searching the telecom web site, but stuffed if I could find any.

So is there a web page on the telecom site(s) about it?

Thanks.

[fillup]

Installed the official TNZ 6.1 update on my Touch tonight, but have no GPS :S. Everything else seems to have worked fine though. Tried installing google maps and enabling 'use gps' but it just times out. Live search just doesn't have any GPS settings in it.

Tried letting 'GPS Test' but it fails to find anything. Additionally, there are no changes to the GPS settings from 6.0, nor any new programs installed that would indicate that it's functional.

Have tried running the cabs here http://forum.xda-developers.com/show...87#post2143987 with no success

Any ideas?

[DisturbedNZ]

Originally Posted by fillup

Installed the official TNZ 6.1 update on my Touch tonight, but have no GPS :S. Everything else seems to have worked fine though. Tried installing google maps and enabling 'use gps' but it just times out. Live search just doesn't have any GPS settings in it.

Tried letting 'GPS Test' but it fails to find anything. Additionally, there are no changes to the GPS settings from 6.0, nor any new programs installed that would indicate that it's functional.

Have tried running the cabs here http://forum.xda-developers.com/show...87#post2143987 with no success

Any ideas?

Have you gone to Start->Settings->Phone->Services->Location Setting hit "Get Settings" and ensure that this is set to "ON". The GPS update is definatley there. You check if it has installed properly, Go To Start->Settings->System-> Device Settings and your radio version should be something like "3.41.00", if it is then the GPS is all there now, jsut a settings issue we need to resolve. If your still hvaing no luck just PM me. I can confirm this works 100% tho, as i was using tomtom 7 on my touch just today to navigate my way round Palmerston North.

Cheers

[fillup]

Radio Version 3.41.00

And Location Services is 'On'.

Will try leaving outside again for a while with Google Maps looking for GPS...

Update ** This time Google maps timed out quite quickly, after saying 'Initializing GPS', instead of the number of fixes that it had shown previously (always 0 though). Then goes to error page 'No GPS reciever was found'

What hardware version do you have? I am paranoid that my version 0001 may not have GPS, even though i've read others that do.

[Jeffster]

Hey all.

I've tried to access www.telecom.co.nz/oktatouchupgrade to get the ROM files but I keep getting taken back to Telecom's Homepage??

Where do I get these files now? Have Telecom removed them?

[ali3nfr3ak]

im uploading now will paste link when ready


http://cid-0d316441be87b15a.skydrive...px/PPC/TELECOM its in 3 parts just unrar and it will unrar all 3 files, then activesync then run RUU_Vogue_TNZ_WWE_3.00.781.3_Radio_3.41.00_Ship, be warned you will lose phone/text capabilities, but all you have to do is have a spare phone, thats not connected to network , ring telecom and tell then you have just upgraded with the offical okta upgrade, they may ask where yoy got it from (u say www.telecom.co.nz/oktatouchupgrade.zip , then tell them u want to do a esn swap, which means put your okta phone number onto the spare phone, make sure you can ring out on the phone then ask to swap your number back to the okta. takes 5 mins

[onslaught86]

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

[Damager]

Originally Posted by onslaught86

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

Ha! Yes talk about raising the titanic but this is still a relevant topic worth discussing!

Normally when the Titan is upgraded, the HDR AN AUTH password field is blank. Has this field now populated itself in your security settings?

I sold my Titan that was flashed without recording the HDR password, although i told the buyer that if i ever found a way to restore the password , i'd let him know.

[onslaught86]

Intriguing, I hadn't actually checked the HDR password field in the EPST security menu until just now - username has populated, password has not.

The username is just [My ESN]@evdo.jamamobile.co.nz. This is in the NAI field in the M.IP field also.

The other day it spat the dummy and wouldn't connect to EVDO upon several attempts, but worked fine when tested several times since. Odd, hopefully a one-off. Otherwise works snazzily. Have yet to test out the GPS, heh.

[Damager]

Originally Posted by onslaught86

Intriguing, I hadn't actually checked the HDR password field in the EPST security menu until just now - username has populated, password has not.

The username is just [My ESN]@evdo.jamamobile.co.nz. This is in the NAI field in the M.IP field also.

The other day it spat the dummy and wouldn't connect to EVDO upon several attempts, but worked fine when tested several times since. Odd, hopefully a one-off. Otherwise works snazzily. Have yet to test out the GPS, heh.

Interesting! So when you hit the net, the EvDo icon remains, it doesnt change to 1X at all?

The EvDo icon when not on the net, just indicates that youre in an area where EvDo mobile broadband is available, so should always show, unless you've forced the phone to be in 1X mode.

When you connect to the net, in an area where EvDo is available, the phone by default presents the HDR username and the HDR password. If this unsuccessful, eg either one of the username is missing or incorrect, the phone then presents the ppp username = mobile@jamamobile and ppp password = telecom, the phone then connects to 1X broadband.

If you do a speedtest on EvDo, you should be able to get something like at least 800kB/s.

On 1X, the max speed is about 150ish kB/s.

Keep me posted!