OKTA Touch WM 6.1 Official Update ROM From Telecom Is Available Now

By tonyhughes Hughes, in , posted: 5-Mar-2009 09:00

Weighing in at about 70MB, update can be found here: www.telecom.co.nz/oktatouchupgrade

Instructions provided by PatDude.

The upgrade was actually meant as a maintenance release and there are some key steps that need to be taken in order for the ugrade to be sucessfully applied.

Also please don't download the upgrade using your mobile, download it to a PC. Aside from the fact that at 70Mb it'll cost you a packet, it wont work if you try and run it from your Okta Touch. The upgrade is meant to be installed from a PC to an Okta Touch connected by a USB cable and Active Sync

Here's some instructions to follow

Before Running the ROM Upgrade Utility Before you run the ROM Upgrade Utility (RUU), make sure you check and do the following first:

1.    USB sync cable is connected to the computer.

2.    The standby and hibernation modes are disabled on the computer.

3.    All running applications on the computer have been closed.

4.    USB sync cable is connected to the Mobile Device to establish an ActiveSync connection with the computer.

5.    Do not interact with your Mobile Device unless instructed to do so.

General Procedure on Installing the ROM Update


1.    Back up your personal data from the Mobile Device to your computer using ActiveSync if you want to ensure you don’t lose any of your data.

2.    On your computer, run the ROM Update Utility (RUU) to install the ROM update to your Mobile Device. (The next section provides a detailed procedure on how to install the ROM Update).

3.    Restore your personal data back to your Mobile Device using ActiveSync.
(Optional)

How to Install the ROM Update Note: Before running the RUU, back up any personal data from the Mobile Device to the computer first using ActiveSync.

Navigate to www.telecom.co.nz/oktatouchupgrade and download the RUU upgrade file.

1.  On the Welcome Screen, click Next to begin the ROM update installation.

2. 
On the next screen, follow the listed instructions in the dialog box first. When you are done, click Next to proceed.
Note: You should read and follow all the instructions listed before clicking Next.

3.  The following message "Verifying The information on your PDA Phone...PLease Wait" will be displayed, indicating that the utility is verifying and acquiring information about the device as preparation for the update process. Wait for this verification process to finish.

4. 
Current information about the device, such as the model ID, image version and language will then be displayed. Click Update to proceed.

5. 
Below the device information, information about the new ROM update will then be displayed. If you are certain that you want to install the Mobile Device with the new ROM update, click Next to proceed.

6. 
A confirmation message then appears and shows the length of time it will take to copy the necessary files (including radio image) to the device. Click Next to begin the update.

A progress bar will run through the screen during the update process.
Note: In the middle of the update process, the progress bar may stop running. This is normal as the RUU is adjusting itself to complete the update process automatically. 

7. A screen congratulating you on the update should appear, click Finish to exit the utility.

Troubleshooting and Error Recovery
 Almost all RUU related errors can be recovered. When an error occurs, the utility will display an error message and provide recovery measures to allow you to continue with the update process.   After errors are recovered, do the following to continue with the update process:

1.       Disconnect the Mobile Device from the USB cradle/cable.

2.       Reset the Mobile Device.

3.       Reconnect the Mobile Device to the USB cradle/cable.

4.       Check that the communication cradle/cable is connected properly.

5.       Return to the ROM Update Utility to continue with the update.

If errors cannot be recovered, please refer to Q&A section for more details.

ERROR [202, 204] : CONNECTION
 This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.  

ERROR [260] : CONNECTION
 This error occurs when there is an “open port error” before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again. 

ERROR [206] : MEMORY ALLOCATIONERROR [280] : UPDATE ERROR When you see any of these error messages, close other running programs on the computer and run RUU again.

ERROR [208] : FILE OPENERROR [210] : FILE READ These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.

ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITEERROR [222, 224] : DEVICE NOT RESPONDING These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.

ERROR [220] : MAIN BATTERY POWER
 This error message will appear when the device’s battery power is not sufficient.  Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).

ERROR [238] : FILE READ
 This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.

ERROR [240] : FILE OPEN
 When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.

ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL IDERROR [294] : INVALID VENDER IDERROR [296] :  UPGRADE ONLY One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.

ERROR [246] : DEVICE NOT RESPONDING
 This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.

ERROR [262, 276, 284, 302] : UPDATE ERROR
 This error occurs during the CE ROM code upgrade process.  Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue. Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.

ERROR [300] :  INVALID UPDATE TOOL
 This error message will appear when you use the incorrect RUU version to upgrade.

ERROR [330] : ROM IMAGE ERROR This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.

Q & A for RUU Upgrade 

1.   Q: How long will it take for the verification process to finish? A: It will take about 1 minute, but it also depends on the speed of your computer.

2.   Q: What should I do if I see the progress bar turn red on the Mobile Device?A: Do not do anything. This is normal as the RUU is adjusting itself to complete the process. You should not interrupt it by pulling the device out of the cradle unless being prompted.

3.     Q: During the upgrade, the progress bar is moving. If the error message (ERROR [262] : UPDATE ERROR) appears, what should I do?A: This may occur when the connection is lost, without power supply, computer host is down, or due to other unexpected cases. You will see that there’s still one progress bar displayed on the device but it is not moving any more. The device cannot get into the Wince screen, so you cannot connect with ActiveSync. This problem usually can be recovered. You just need to follow the instructions in the error message box, reset the device, and run RUU again. RUU will re-flash the whole image again.
Note: You should remove the battery and reset the Mobile Device.

5.   Q: If I encounter ERROR [260] : CONNECTION, what should I do?A: You can reset the device and run RUU again. If you still encounter the same ERROR again, reset the computer PC and try again.

6.   Q: If I encounter ERROR [300] :  INVALID UPDATE TOOL, what should I do?A: This error message will appear when you use the incorrect RUU to upgrade. Please make sure you use the correct RUU version to upgrade.

7.   Q: If I encounter ERROR [220] : MAIN BATTERY POWER, what should I do?A: , This error message appears when your device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure your device has enough power to upgrade the radio.

8.   Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It’s normal and can be recovered.

Please follow the instructions below to reset your device and to establish a connection with the computer.

1.   Disconnect your Mobile Device from the USB cradle/cable.

2.   Reset your Mobile Device.

3.   Reconnect your Mobile Device to the USB cradle/cable.

4.   Check that the communication cradle/cable is connected properly.

5.   Return to the ROM Update Utility.Note: You should ignore the ActiveSync connection.

Other related posts:
How to update your XT Galaxy S to Android 2.2 Froyo
Download Samsung KIES 2.0
Running an Android Task Killer? Get rid of it, and get your battery back.








Comment by KevDaly, on 5-Mar-2009 15:38

Thanks...I just installed it about an hour ago.

The only problem I encountered (other than noting that my installation of WMDC has no backup option) was right at the beginning: once it'd zapped the existing ROM configuration Windows decided it needed to install some new USB drivers to talk to the device, at which point the installation failed, with the device screen in a state not unlike a raibow-coloured brick.
Luckily just running the installation again did the trick.

I was disappointed to see that 6.1 apparently doesn't include .NETCF3.5 in ROM (Windows Mobile  + Compact Framework continues to be a farce...Come on guys, sort yourselves out). I'll have to give the browser a bit of a workout later to see if there are any improvements other than the welcome zoomy feature.

I've noticed that performance seems noticeably snappier, but that could be the result of what amounts to a defrag.


Comment by Mike T, on 6-Mar-2009 20:01

Tony thanks for the note. Tried the same and although everything went OK with the upgrade (see note) I now do not have phone service. Get a recorded voice when I try to dialling out telling me it can take up to 4 hours for my phone to activate. 48 hours later and still no go tried upgrade again, same result. Checked my phone with 3 other at work using the ## option to get to the settings lists and there is nothing missing. The internet acces works, just the phone no go. No text no icoming or outgoing calls possible. Note: on first run up once in 6.1 an error came up about can't run startkey.exe, subsiquent boots ok.


Comment by Mike T, on 8-Mar-2009 15:44

Rang Telecom mobile faults last night and they got me to re-input my phone number and some other number. Can't remember the sequence but it was a hash followed by several digits and it came to a screen that only had 2 entries (as above). Reboot and ...... and same problem still. Phone goes back to our agent Monday and they can tell me whats wrong with it. IF they do I will update here.


Comment by Mike T, on 9-Mar-2009 20:44

Phone sent back to agent today. They could not see anything wrong so have sent it wherever Telecom phones go to get repaired. Temporary phone (same type) received whilst mine is away, pleasant surprise. The temporary phone is running 6.1. Love the threaded texts makes life a lot easier. Phone seems a little snappier but time will tell if the weird GUI bugs have gone. Never measured the response but with voice dialing disabled the interface seems a little speedier as well (same on previous version). Anyway, I will update with the outcome.


Comment by patdude, on 12-Mar-2009 16:57

Tony - Thanks for posting this link, Unfortunately as you've not posted any instructions along with the link, people are likely to experience problems performing the upgrade.

The upgrade was actually meant as a maintenance release and there are some key steps that need to be taken in order for the ugrade to be sucessfully applied.

I have upgraded at least a dozen Okta Touches with no problems by following the instructions you've omitted. Could you either please include the instructions with the link or remove it before any more Okta Touches are damaged by people not performing the correct steps to the upgrade. 

Also please don't download the upgrade using your mobile, download it to a PC. Aside from the fact that at 70Mb it'll cost you a packet, it wont work if you try and run it from your Okta Touch. The upgrade is meant to be installed from a PC to an Okta Touch connected by a USB cable and Active Sync

Here's some instructions to follow

Before Running the ROM Upgrade Utility Before you run the ROM Upgrade Utility (RUU), make sure you check and do the following first:1.    USB sync cable is connected to the computer.2.    The standby and hibernation modes are disabled on the computer.3.    All running applications on the computer have been closed.4.    USB sync cable is connected to the Mobile Device to establish an ActiveSync connection with the computer.5.    Do not interact with your Mobile Device unless instructed to do so. General Procedure on Installing the ROM Update 1.    Back up your personal data from the Mobile Device to your computer using ActiveSync if you want to ensure you don’t lose any of your data.2.    On your computer, run the ROM Update Utility (RUU) to install the ROM update to your Mobile Device. (The next section provides a detailed procedure on how to install the ROM Update).3.    Restore your personal data back to your Mobile Device using ActiveSync. (Optional) How to Install the ROM Update Note: Before running the RUU, back up any personal data from the Mobile Device to the computer first using ActiveSync. Navigate to www.telecom.co.nz/oktatouchupgrade and download the RUU upgrade file. 1.  On the Welcome Screen, click Next to begin the ROM update installation.2.  On the next screen, follow the listed instructions in the dialog box first. When you are done, click Next to proceed.
Note: You should read and follow all the instructions listed before clicking Next3.  The following message "Verifying The information on your PDA Phone...PLease Wait" will be displayed, indicating that the utility is verifying and acquiring information about the device as preparation for the update process. Wait for this verification process to finish.
4. 
Current information about the device, such as the model ID, image version and language will then be displayed. Click Update to proceed.
5. 
Below the device information, information about the new ROM update will then be displayed. If you are certain that you want to install the Mobile Device with the new ROM update, click Next to proceed.
6. 
A confirmation message then appears and shows the length of time it will take to copy the necessary files (including radio image) to the device. Click Next to begin the update.

A progress bar will run through the screen during the update process.
Note: In the middle of the update process, the progress bar may stop running. This is normal as the RUU is adjusting itself to complete the update process automatically.  7. A screen congratulating you on the update should appear, click Finish to exit the utility. Troubleshooting and Error Recovery Almost all RUU related errors can be recovered. When an error occurs, the utility will display an error message and provide recovery measures to allow you to continue with the update process.   After errors are recovered, do the following to continue with the update process:1.       Disconnect the Mobile Device from the USB cradle/cable.2.       Reset the Mobile Device.3.       Reconnect the Mobile Device to the USB cradle/cable.4.       Check that the communication cradle/cable is connected properly.5.       Return to the ROM Update Utility to continue with the update. If errors cannot be recovered, please refer to Q&A section for more details. ERROR [202, 204] : CONNECTION This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.  ERROR [260] : CONNECTION This error occurs when there is an “open port error” before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.  ERROR [206] : MEMORY ALLOCATIONERROR [280] : UPDATE ERROR When you see any of these error messages, close other running programs on the computer and run RUU again. ERROR [208] : FILE OPENERROR [210] : FILE READ These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again. ERROR [212] : FILE CREATEERROR [214] : FILE WRITEERROR [222, 224] : DEVICE NOT RESPONDING These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again. ERROR [220] : MAIN BATTERY POWER This error message will appear when the device’s battery power is not sufficient.  Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio). ERROR [238] : FILE READ This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again. ERROR [240] : FILE OPEN When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again. ERROR [242] : INVALID LANGUAGEERROR [244] : INVALID MODEL IDERROR [294] : INVALID VENDER IDERROR [296] :  UPGRADE ONLY One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade. ERROR [246] : DEVICE NOT RESPONDING This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance. ERROR [262, 276, 284, 302] : UPDATE ERROR This error occurs during the CE ROM code upgrade process.  Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue. Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode. ERROR [300] :  INVALID UPDATE TOOL This error message will appear when you use the incorrect RUU version to upgrade. ERROR [330] : ROM IMAGE ERROR This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
 Q & A for RUU Upgrade  1.   Q: How long will it take for the verification process to finish? A: It will take about 1 minute, but it also depends on the speed of your computer. 2.   Q: What should I do if I see the progress bar turn red on the Mobile Device?A: Do not do anything. This is normal as the RUU is adjusting itself to complete the process. You should not interrupt it by pulling the device out of the cradle unless being prompted. 3.     Q: During the upgrade, the progress bar is moving. If the error message (ERROR [262] : UPDATE ERROR) appears, what should I do?A: This may occur when the connection is lost, without power supply, computer host is down, or due to other unexpected cases. You will see that there’s still one progress bar displayed on the device but it is not moving any more. The device cannot get into the Wince screen, so you cannot connect with ActiveSync. This problem usually can be recovered. You just need to follow the instructions in the error message box, reset the device, and run RUU again. RUU will re-flash the whole image again.
Note: You should remove the battery and reset the Mobile Device. 5.   Q: If I encounter ERROR [260] : CONNECTION, what should I do?A: You can reset the device and run RUU again. If you still encounter the same ERROR again, reset the computer PC and try again. 6.   Q: If I encounter ERROR [300] :  INVALID UPDATE TOOL, what should I do?A: This error message will appear when you use the incorrect RUU to upgrade. Please make sure you use the correct RUU version to upgrade. 7.   Q: If I encounter ERROR [220] : MAIN BATTERY POWER, what should I do?A: , This error message appears when your device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure your device has enough power to upgrade the radio. 8.   Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It’s normal and can be recovered. Please follow the instructions below to reset your device and to establish a connection with the computer.1.   Disconnect your Mobile Device from the USB cradle/cable.2.   Reset your Mobile Device.3.   Reconnect your Mobile Device to the USB cradle/cable.4.   Check that the communication cradle/cable is connected properly.5.   Return to the ROM Update Utility.Note: You should ignore the ActiveSync connection. 


Comment by Khozi, on 13-Mar-2009 11:56

Hi, Does this ROm enable the GPS.


Comment by Mike T, on 16-Mar-2009 20:36

Hmmm still waiting for my phone to come back. Loan OKTA has 6.1 on and no weird GUI issues as yet so it looks like the fixes in 6.1 release removed some of the erratic behavior. Khozi - the loaner phone has Google Maps on it and I have tried the GPS option with no success. Outside or inside times out without finding a satellite. If it does enable the GPS then there must be some further magic required to get it to work. GPS is set to automatic for Windows to manage.


Comment by Mike T, on 20-Mar-2009 11:44

Got my phone back from our agent. They had sent it to Telelogisitcs. Telelogistics could not reproduce the fault. Their fault log says they reflashed and cleaned aerial contacts. We have had other phones (not OKTA) come back with the same fault details. I think its a standard template. I can not believe that they could not fault it. I flashed it several times and althoguh it all looked 100% it would not go. Internet worked so the aerial clean is a red herring. Very disappointed that they will not say what the problem is as others are having the same experience, so there is a problem somewhere. But they hold the power so not much can be done. If you are going to upgrade your phone be prepared to need to send it back for it to be "fixed". Depending whether or not you are near an agent it could take weeks (2 weeks for me). Also they may try and make you pay. Could be a rock and a hard place for some. Good luck and sorry could not post some useful detail to avoid service loss.


Comment by jack williamson, on 20-Mar-2009 12:29

if your okta has a hardware version of 0001 this update will result in only data calls working. the update only works 100% on phones with hardware version 0002


Comment by Mike T, on 21-Mar-2009 12:20

Jack thanks for the valuable information. I can confirm that "Settings/Device Information" shows hardware version 0001. I will check our other OKTA's at work and warn the owners. Do you know what they do to "make" it work? Have been trying Android Cupcake and it is much easier to use than windows. Obviously still has some porting issues but even still the web access and viewing is much smarter. Not quite ready yet to commit to it but still playing. http://it029000.massey.ac.nz/vogue/


Comment by jack williamson, on 21-Mar-2009 21:58

it is possible to make these 0001 version oktas work simply by transfering the number to another phone, wait until the other phone works then transfer it back again. however this methood isnt a 100% reliable fix. it does work about 80% of the time though.


Comment by Shane S, on 28-Mar-2009 16:12

Mine is hardware version 0001, upgraded fine, no problem with it so far.


Comment by Mike T, on 2-May-2009 17:19

Moved to Android permanently.(Not the cupcake version.) The only thing I need daily is my Outlook scheduling and thats done by syncing Outlook using the Google Gmail plugin for Outlook to my gmail account (works both ways). My PC at work is updated by Gmail via Android. For contacts export from Outlook to CSV and then import to gmail. If Telecom bring out an Android device on the XT network I will likely buy one if price is reasonable. Or on Vodafone with the HTC Magic.


Comment by buy ipod touch, on 14-Oct-2009 15:51

good article


Add a comment

Please note: comments that are inappropriate or promotional in nature will be deleted. E-mail addresses are not displayed, but you must enter a valid e-mail address to confirm your comments.

Are you a registered Geekzone user? Login to have the fields below automatically filled in for you and to enable links in comments. If you have (or qualify to have) a Geekzone Blog then your comment will be automatically confirmed and shown in this blog post.

Your name:

Your e-mail:

Your webpage:



Subscribe To My RSS Feed